Upgraded from Kitkat to Lollipop. Just. Need some help rooting.

So not being very experienced at Rooting/Flashing Roms this may come across strange.

Here is a little background to my problem.

I had a rooted Note 3 running KitKat before I decided to flash to Lolipop. I downloaded the Vodafone (UK) variant of the ROM from Sammobile not thinking anything of it at the time (As I am on Vodafone) I went through the usual procedure of going into download mode running Odin as admin and then connecting my phone, adding the Rom files to Odin and then Flashing. Flashing started fine as it got towards the end it Failed on Hidden(Something).
I panicked didn't know what to do so I unplugged my device and tried to reboot. It didn't. It said something along of the lines as there is a firmware error and got stuck on that screen. Panicked some more, decided I would try to google a fix. Came across one which required me to flash CWM Recovery onto my phone. I thought I would try it, Once it flashed which went fine I was told too try and boot straight into recovery mode once the phone starts and reboot through there. I took out my battery put it back in and then went ahead and tried to boot into recovery which worked. Once on CWM I went to reboot the phone As I hit yes too reboot It took me to another screen where it said I wasn't rooted and if I would like to reroot. I decided to click NO and restart the phone. It got stuck on a boot loop, I did a factory reset and cache wipe and it booted into life. (And working fine so far)

So here is where the problem is.

I am looking to get root back to the device. I think I have a locked boot loader as I installed the Vodafone variant of the 5.0 Rom. Would I be able to Flash the BTU Rom onto my device without bricking it, and after that would I be able to root Via CFAutoRoot which seems to be the easiest way to so. Or could I flash with CFAutoRoot Straight onto this ROM.

Info:
BTU ROM:
Date Country/Carrier Version PDA CSC
2015-07-01 United Kingdom 5.0 N9005XXUGBOF1 N9005BTUGBOD2

ROM I INSTALLED:
Date Country/Carrier Version PDA CSC
2015-06-01 United Kingdom (Vodafone) 5.0 N9005XXUGBOD6 N9005VFGGBOD2

Thanks for any help in advance.

Just upgraded to CM 12.1 from stock JB ROM - Storage space running out problem

Hello

I'm having a little trouble understanding what is going on because this never occurred to me. I have just installed to new CM 12.1 Nightly on my old Galaxy S2 (I9100 Model). I came from the just ROM JB 4.1.3 as I was sure this phone could handle much more than that. Expectations were high and they were met. Although I had some problems installing the KitKat compatible recovery, I eventually did it and it all works well for now - well, except one little annoying thing: after installing about 10 apps the phone started complaining about the internal storage running out.

First thing I do is to check the 'Storage' option in Settings to make sure about the actual space being used. I have 1,96GB total space and at this point the bar was almost filled showing that, in fact, I had about 100MB free space left. I then go to the 'Apps' option to move as many as I could to the SD card. All could be moved except for Google Play Services which itself takes about 200MB. To my surprise, although the apps were supposedly moved to SD card, if I go check the each App Info I still see that almost all space the Apps take is still being stored in the 'internal storage'. Almost nothing is stored in the SD card even if the app was "moved". I also made sure I cleaned the cache of every app.

I go ahead and check the 'Storage' option again. This time I paid attention to the actual details it shows. Once I enter this option the following screen appears: dnuno. pt (slash)outros(slash)screen2. png

After a while of "calculations" the bar changes and I end up with this: dnuno. pt(slash)outros(slash)screen3.png

(Please add www to the front of the links, remove the spaces and add the \ as I don't have the permission to post outside links yet)

No other statistics other than 'Available space' and 'Apps' appear and as the bar indicates I still have a lot of space left at least 1GB. With the previous JB ROM I started running out of space only much later and I had lots of other apps installed.

Somehow the available space is stuck on that value (166MB) even after all the calculations have been made.

I wasn't able to find any reference to this particular version of the 'storage space running out' problem and I'm unaware of possible solutions to this as well. I hope someone can redirect me to some other thread, post or something that could help me out. Also I couldn't post in the original CM 12.1 thread for I9100 because I have just registered.

Thank you in advance.

[6039] - ***GUIDE*** - How to return the fastboot commands on already upgraded device

Your warranty is void. I'm not responsible if your device is hard bricked by using the procedure below. The method described below has been tested on 6039Y and is confirmed that it works.
What to expect on successful completion:
- you will have access to the fastboot commands (removed by the latest upgrade).
- you should be able to check for OTA updates and to download them, but you will not be able to install them.

What's needed:
-------------------
1. I hate when I must say this ... but ... a Windows PC.
2. QPST version 2.7.422 (you can find it on the net as 2.7 build 422). This is a link to one such version (found through Google). If there are problems with this link please let me know. I will try to find another one (you can do it yourself too).
3. Drivers in order the device to be recognized when is in Download mode. Install Mobile Upgrade Q 4.8.7 the necessary drivers are installed with it. It can be downloaded from here.
4. The files from the archives below. Please use the archive which is especially for your device ... in theory if you use the archive for different device (e.g. the archive for 6039S on 6039Y (with the standard partitions)) you should have a repartitioned device at the end, and only the resize2fs command should be enough to start to utilize the whole memory chip ... but you will loose the possibility to sweat a little bit when do the repartitioning by following the guide for it :p.
- 6039Y (8GB stock partition sizes) (md5sum: 860789bedb63da5c5976c24825c29d47)
- 6039Y (repartitioned by following the repartitioning guide) (md5sum: 9dcf609707f3d0ffceef13b7d769a17e)
- 6039S (md5sum: dfd04067230b5709729c70cac61ffd52)

How to proceed:
--------------------
1. Install all the necessary software.
2. Unpack the downloaded archive for your device.
3. Power off the device. Connect it with the USB cable to the PC. Wait the battery symbol to disappear and hold both volume keys and the power button. You should see a red screen with a warning sign and a scheme. Then hold the volume up button. The display will stay lit but nothing will be shown on it from now on until the end of the procedure.
4. When the device is in Download mode under the windows device manager -> Ports (COM & LPT) you should see Android HS-USB QDLoader 9008 (COMXX)
5. Open the windows explorer and find the installation folder of QPST (mine is under Program Files (x86)\Qualcomm\QPST). From the bin sub-directory start QFIL as administrator.
6. In QFIL the COM port number as seen under the windows device manager should be selected automatically.
7. The rest must be done from QFIL:
- Programmer path: _____ - Click on the Browse button against it and from the extracted archive select prog_emmc_firehose_8916.mbn
- Search Path: _____ - if the path is not selected automatically after the programmer selection click on the Browse button against it and select the folder where the archive has been extracted.
- Load XML - click on it and first select rawprogram0.xml from the archive, then the patch0.xml file.
- Click on the Download button. The process should finish quickly (few seconds ... up to a minute). If everything is OK the phone will be restarted automatically and the fastboot commands will be available again.

(If you feel unsure to proceed or not but your device is already in download mode ... disconnect the USB cable and hold both volume keys and the power button to restart it).
Screenshots from QFIL is possible to be provided later ...

on 10b SEA and want the upgraded EU

hi guys im on SEA singapore 10b, and im seeing a few people who flashed the EU version and upgraded to 10f or 10e. can someone post which varaint exaclty to FLASH? what is alowed?:confused: maybe post a link? :D. im afraid to flash the wrong one and to brick my phone.
also after flashing will i still get OTA updates from that variant?
thanks for helping :)

Upgraded to 5.0.2, can't disable vibration

I'm a long time Android user so I'm familiar with the sometimes weird and tricky places that you need to disable secondary (or tertiary) vibration settings. I factory reset my phone yesterday before the upgrade to 5.0.2 so this is essentially a clean slate.

I've rebooted the phone, I've cleared the cache in various apps, I've quadruple checked every place where there's a vibration setting and no luck. I've used a 3rd party app like Audio Guru which is great for a complete "silence mode" and even then the phone vibrates (the icon in the top bar shows as Silent btw). I even got a vibration alert for an email coming into an Exchange account, which in my 2+ years owning this phone didn't think was possible.

Maybe it's a new setting that I'm missing in 5.0.2? At this point I don't know what else to try besides factory resetting again. Anyone have any tips before I devote another 3+ hours to a factory reset and configuring my whole phone again?

[Q&A] Accidentally upgraded to OF1 Help downgrade to OC1

Q&A for Accidentally upgraded to OF1 Help downgrade to OC1

Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.

Before posting, please use the forum search and read through the discussion thread for Accidentally upgraded to OF1 Help downgrade to OC1. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.

Thanks for understanding and for helping to keep XDA neat and tidy! :)

Accidentally upgraded to OF1 Help downgrade to OC1

I am having no luck downgrading the software on my verizon S4 to OC1 from OF1.

I used odin 3.09 and odin 3.10.16 with it failing.

Any advice would be greatly appreciated.

-D

Freaking problems after upgraded to 5.1 lollipop

To all you guys who had upgraded to 5.1 and not located in the US, did you faced these 3 problems?

1) when dialing 1800 numbers, the stupid phone app automatically input a + in-front of the 1800 and straightaway dialed to the US. Is there anyway to prevent the phone from adding the "+" sign whenever it detected "1"? I know this is a verizon phone but is there a way to fix this nonsense? I have been billed for overseas calls so many times even after hanging up the phone within 1-2 secs upon hearing American accent voice msgs.

2) battery drain problem had became more severed. Left 10% after 7 hrs of usage. Before 5.1, still got 40% after a whole day usage.

3) When the phone is locked and someone called, the phone will ring but no way to pick up the call until the phone is unlock.

Damn pissed off at motorolo for releasing a half-f*** update. Until now it is almost two months and still no fixes.