Database Users

[GUIDE] Comprehensive "Rooted Android 2.3.4 with unlocked bootloader" instructions

[GUIDE] Comprehensive "Rooted Android 2.3.4 with unlocked bootloader" instructions
This is a guide on how to go from Froyo to rooted Gingerbread. Also, I'm on AT&T. Others beware. I take no responsibility if you hard or soft brick your phone.
I went from a rooted install running Gingerblur v4.5, but this will likely work regardless of what you have installed, since fastboot overwrites everything.
I didn't actually discover or develop any of this, but I figured someone might like to have a comprehensive guide, instead of searching through 500 different threads like I did.​Known/potential issues:
- Fingerprint scanner not functional False alarm
- Avoid using RSDLite for *anything* if you installed the OTA 2.3.4 build
- Battery reading is sometimes inaccurate
- If you have a limited RAM issue, read here http://forum.xda-developers.com/showthread.php?t=1169409​Step 0 - BACK UP EVERYTHING. Use Titanium backup, or just copy everything off your phone, whatever. This will leave you with an unlocked, rooted, but otherwise stock Motorola phone. Once this is done, set your USB mode to "None"
Step 1 - Install moto drivers
For x64 windows, use these: http://forum.xda-developers.com/attachment.php?attachmentid=634880&d=1308872277
For x32, http://www.multiupload.com/QNFILE4F07 (I havent tested these, I run Win7 x64)
Step 2 - Unlock your bootloader Note: some have hard bricked using RSDLite to install 1.8.3 over 4.5.91. Read warning here: http://forum.xda-developers.com/showthread.php?t=1160408
Download latest moto-fastboot from here: http://forum.xda-developers.com/showthread.php?t=1138092 *the win32 version worked for me, and I run 64bit windows 7*
Follow instructions here: http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
Step 3 - Flash stock Gingerbread image (you can do this without restarting your phone from the unlock bootloader step)
Follow instructions here: http://forum.xda-developers.com/showthread.php?t=1163342
Step 4 - Flash CWM Recovery
Instructions here: http://forum.xda-developers.com/showthread.php?t=1138541
Step 5 - Install root
Instructions here: http://forum.xda-developers.com/showthread.php?t=1159572
Note: I used my phone's USB Mass Storage mode to put the .zip on my external SD card. To get to recovery mode, shut down the phone. Then hold the power and volume up buttons until you see "fastboot." Use the volume down key to cycle through until you see "Android Recovery" then press volume up again. This will get you into the CWM environment, where you can navigate the menus to install the root .zip.
Step 6 - Restore your stuff
Now you should have a factory fresh Gingerbread / MotoBlur installation (didn't you miss the bloat?), with the addition of the superuser app. For tethering, I use Barnacle (requires root). I used Titanium Backup to uninstall any apps I don't want (anything beginning with AT&T, Blockbuster, Y!, etc.) and to reinstall all of my apps.​
Feel free to make any corrections, or ask questions. Hopefully someone finds this useful. All credit to the OP of each thread I linked to.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Nice for you to localize everything, ATT users will be grateful.

I went from a rooted install running Gingerblur v4.5, but this will likely work regardless of what you have installed, since fastboot overwrites everything.
Click to expand...
Click to collapse
Does this include the official 4.5.91? So many warnings about hard bricking since people flashed it.

From what I can tell, hard bricking only occurs when you use RSDLite to flash an older motorola SBF once you've gone to gingerbread. But someone else should chime in on that one - I never got a notice for an OTA update.

humjaba said:
From what I can tell, hard bricking only occurs when you use RSDLite to flash an older motorola SBF once you've gone to gingerbread. But someone else should chime in on that one - I never got a notice for an OTA update.
Click to expand...
Click to collapse
I didn't either. I downloaded a .zip and installed via stock recovery from a thread in the General Atrix forum.

Deggy said:
Does this include the official 4.5.91? So many warnings about hard bricking since people flashed it.
Click to expand...
Click to collapse
Nope, this one is the completely safe one.
Kennethpenn said:
"These are completely safe to flash. They don't mess with your bootloader like the OTA or SBF."
In the thread.

Magnetox said:
Nope, this one is the completely safe one.
Kennethpenn said:
"These are completely safe to flash. They don't mess with your bootloader like the OTA or SBF."
In the thread.
Click to expand...
Click to collapse
Just to clarify. I can NOT proceed to unlock my BL. Is that correct?

Deggy said:
Just to clarify. I can NOT proceed to unlock my BL. Is that correct?
Click to expand...
Click to collapse
What firmware did you flash? Can you link me to the thread you downloaded from?

Magnetox said:
What firmware did you flash? Can you link me to the thread you downloaded from?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1159604

Deggy said:
http://forum.xda-developers.com/showthread.php?t=1159604
Click to expand...
Click to collapse
Ah you have the deadly firmware
You simply cannot use RSD to flash down to 1.83 or 1.26 etc.
Or you will brick.
Clarify in Q&A, make your own thread with your question.
Taken from this thread kennethpenn said:
"What if I already flashed the official 4.5.91?
If you flashed the official update from XDA or by downloading through a dev-blur server (note: this excludes this ROM), you should avoid flashing SBF files in RSD Lite. We've confirmed this problem exists when users flash the 1.8.3 build specifically. It may happen with other SBF files, though."
So it looks like you can flash 2.3.4 builds via CWM. But double check by asking in Q&A.

Check out this thread.
http://forum.xda-developers.com/showthread.php?t=1163009
Fruit cakes basically dont touch your bootloader, they're basically modified sbf files that only contain the needed files to flash stuff. There's a 1.8.3 fruitcake in there as well as a 2.3.4 fruitcake.
An HKTW fruitcake is in development.
Fruitcake is the .sbf equivalent file that is flashable via CWM.

The big question is this - can you RSDflash the unlocked bootloader SBF by itself once you have the firmware of death? Once you have the bootloader unlocked, everything is gravy.
I don't know the answer

theres the moto-fastboot file i was looking for!
much appreciated.

Now there's a guide
I just did this like 3 hours before this guide came out. Though it at least seems like I was going to all the right threads that are in this guide anyways.

humjaba said:
The big question is this - can you RSDflash the unlocked bootloader SBF by itself once you have the firmware of death? Once you have the bootloader unlocked, everything is gravy.
I don't know the answer
Click to expand...
Click to collapse
From my understanding, if you flashed the official firmware of death you CANNOT use RSD in any way. All of your flashing has to be done via CWM and fruitcakes. Full .sbfs will brick your phone. Hard brick. As in #@$% ME hard brick.

humjaba said:
Step 6 - Restore your stuff
Now you should have a factory fresh Gingerbread / MotoBlur installation (didn't you miss the bloat?), with the addition of the superuser app. For tethering, I use Barnacle (requires root). I used Titanium Backup to uninstall any apps I don't want (anything beginning with AT&T, Blockbuster, Y!, etc.) and to reinstall all of my apps.
Click to expand...
Click to collapse
Weren't there some reports of issues restoring via TB after flashing Ken's beta 4.5? I'd have to search through his thread, but I thought it presented an issue or two.

So I guess no sweet Roms for me. Still haven't found a good thread to root my phone. I'm not sure if the FOD would mess with the rooting part of it.

SoberGuy said:
Weren't there some reports of issues restoring via TB after flashing Ken's beta 4.5? I'd have to search through his thread, but I thought it presented an issue or two.
Click to expand...
Click to collapse
I chose the batch "Restore missing apps with data" option from Ti Backup and it worked flawlessly.

humjaba said:
I chose the batch "Restore missing apps with data" option from Ti Backup and it worked flawlessly.
Click to expand...
Click to collapse
Perhaps it was settings then and not apps. Appreciate the information. I'll be doing that tonight

after i unlocked the bootloader
i flashed CWM
then i use CWM to flash 2.3.4 GB beta 4 zip from kenn
i like it better my way

[Guide] Upgrade Bell phone to Bell 2.3.4

This is a rough guide to help you upgrade your Bell phone to 2.3.4. This has been tested and it works.
*Usual disclaimer: I am not responsible for any damage to your phone.
This isn't detailed but should be enough to get you going.
You must have a Bell phone and your bootloader must be unlocked. Assume you will lose all data and BACKUP!!
1) Restore Bell System
Use NFHimself's GobStopper CWM zip to restore your phone to stock Bell 2.2.2 - at this link:
http://forum.xda-developers.com/showthread.php?t=1185171
2) Install 2.3.4 and root
- Download 2.3.4 zip from this link and copy to your sdcard:
http://forum.xda-developers.com/showthread.php?t=1166362
- Download root cwm zip from this link and copy to your sdcard:
http://forum.xda-developers.com/showthread.php?t=1159572
- Install edgan's kernel if you have d100 device
http://forum.xda-developers.com/showthread.php?t=1173225
- Install faux's d1100 kernel if you have d1100 device
http://forum.xda-developers.com/showthread.php?t=1156040
- Install CWM Recovery (attachment on first post):
http://forum.xda-developers.com/showthread.php?t=1185171
- go into CWM Recovery and install 2.3.4 zip from sdcard
- install Root zip from sdcard
Done!
Thanks to NFHimself, MagentoX , y2whisper and everybody who helped with this.

Plemen, thank you for your help so far. I have done everything you mentioned, and once I get to CWM installing the 2.3.4 over the Bell 2.2.2 (which I used NFHimself's script to get back to) I get the following error.
Any ideas? (Please see attached image)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

awryter said:
Plemen, thank you for your help so far. I have done everything you mentioned, and once I get to CWM installing the 2.3.4 over the Bell 2.2.2 (which I used NFHimself's script to get back to) I get the following error.
Any ideas? (Please see attached image)
Click to expand...
Click to collapse
I've had this error while upgrading and it was because the base ROM on the phone isn't "Bell enough".
Did you flash the French SBF or just use NFS script from OrangeFR (Option 1 or 2)?

Well, let's see:
I went from Bell stock to French SBF originally (via RSD) to Gingerblur. I then went back to stock French SBF and from French SBF to bootloader unlock (via IHOP) to fastboot OrangeFR (d001), though I didn't update the Webtop at all (except maybe during Gingerblur) which is where this error is originating from.
So I went from OrangeFR back to Bell stock 2.2.2 through NF's script (which went fine, no errors at all). I did a factory reset in the ROM itself (not through CWM) which was fine, and once I got back into the stock Bell 2.2.2 complete clean I did your steps.
1) Put the Bell 2.3.4 zip and CWM_root zip on the SD card.
2) Flashed IHOP with RSD
3) Flashed recovery via fastboot
4) Went into recovery and tried the .zip file.
That's where we stand. Should I wipe data/cache before flashing, or will that just put me further in the ****hole?
Thanks again.
plemen said:
I've had this error while upgrading and it was because the base ROM on the phone isn't "Bell enough".
Did you flash the French SBF or just use NFS script from OrangeFR (Option 1 or 2)?
Click to expand...
Click to collapse

What did you do, then, to make the ROM more "Bell-like"?
plemen said:
I've had this error while upgrading and it was because the base ROM on the phone isn't "Bell enough".
Did you flash the French SBF or just use NFS script from OrangeFR (Option 1 or 2)?
Click to expand...
Click to collapse

awryter said:
Plemen, thank you for your help so far. I have done everything you mentioned, and once I get to CWM installing the 2.3.4 over the Bell 2.2.2 (which I used NFHimself's script to get back to) I get the following error.
Any ideas? (Please see attached image)
Click to expand...
Click to collapse
when you did step one did it say it downloaded the files prior to updating the device? this step takes approx an hour to complete.

So it looks like one of your partitions isn't close enough to bell. When I ran into this issue I went with option 1 - I flashed the French SBF and then ran NFS script to root and then restore to install the Bell partitions and checked for OTA. Now that NFS has updated his script to restore 2.2.2 partitions, the OTA may not find any updates which is fine.
awryter said:
What did you do, then, to make the ROM more "Bell-like"?
Click to expand...
Click to collapse
awryter said:
Well, let's see:
I went from Bell stock to French SBF originally (via RSD) to Gingerblur. I then went back to stock French SBF and from French SBF to bootloader unlock (via IHOP) to fastboot OrangeFR (d001), though I didn't update the Webtop at all (except maybe during Gingerblur) which is where this error is originating from.
So I went from OrangeFR back to Bell stock 2.2.2 through NF's script (which went fine, no errors at all). I did a factory reset in the ROM itself (not through CWM) which was fine, and once I got back into the stock Bell 2.2.2 complete clean I did your steps.
1) Put the Bell 2.3.4 zip and CWM_root zip on the SD card.
2) Flashed IHOP with RSD
3) Flashed recovery via fastboot
4) Went into recovery and tried the .zip file.
That's where we stand. Should I wipe data/cache before flashing, or will that just put me further in the ****hole?
Thanks again.
Click to expand...
Click to collapse

Hi,
If you are using my restore phone option, be aware that it overwrites all the partitions except for partition 3 which is you pds partition, data, which is 2 GB and can be generated with a factory reset, and cache, which is a 600MB temp storage space which can be wiped as well. It isn't just system and boot. It restores partitions that sbfs may not write to but doesn't update any bootloaders or radios.
The only thing that the French sbf might do to make things work is to flash an older bootloader. It is also possible that some portion of your pds partition gets modified. Most likely it's a signature in the bootloader or command line options being passed to the kernel that don't apply. There have been reports of phones bricking on ATT when they go back to their older bootloader, however, there have been anecdotal reports that this isn't the case for Bell. Be careful and be prepared for the worst.
Cheers!

If I do this, will I still have an unlocked bootloader?

once the entire process is complete, yes.

y2whisper said:
once the entire process is complete, yes.
Click to expand...
Click to collapse
So then could this be a permanent fix to the RAM issue?

Thanks for the detailed info on the scripts - it's great to get it from the horses mouth
NFHimself said:
Hi,
If you are using my restore phone option, be aware that it overwrites all the partitions except for partition 3 which is you pds partition, data, which is 2 GB and can be generated with a factory reset, and cache, which is a 600MB temp storage space which can be wiped as well. It isn't just system and boot. It restores partitions that sbfs may not write to but doesn't update any bootloaders or radios.
The only thing that the French sbf might do to make things work is to flash an older bootloader. It is also possible that some portion of your pds partition gets modified. Most likely it's a signature in the bootloader or command line options being passed to the kernel that don't apply. There have been reports of phones bricking on ATT when they go back to their older bootloader, however, there have been anecdotal reports that this isn't the case for Bell. Be careful and be prepared for the worst.
Cheers!
Click to expand...
Click to collapse

First of all...Can anyone who has been using the new 2.3.4 tell me is there any significant differences in the performance of the phone in everyday use?
Second: Will the WebTop without the Dock MOD work with this new ROM?
Third: If I do this will I be able to install Bell official OTA when it comes out officially or it will brick my phone?

I Am already on 2.3.4 on a bell Atrix, I can honestly say the upgrade does about 0 ... now with that said the real thing that we need is a market fix so we can finally play order and chaos in Canada.
I give this Guide a 1/10 because its redundant and is not as cohesive as the other guides that are already available.
Edit: no unlock in this guide?! whats the point?!
Edit2: nvm you didt write a guide... my mistake, you just posted a bunch of links for lazy people

hate when i hit thanks instead of reply.....
anyways thanks ray of sunshine for that post. the thread was created by request, but if you do have a more detailed breakdown feel free to contribute.
@sservati
I have noticed quite the difference with 2.3.4. outside of the added features like gtalk w/video, there are little tweaks like being able view your contacts by your google groups. as well as some performance tweaks live wallpaper still seems laggy but other transitions are very smooth. as long as you are comfortable with unlocking your bootloader etc, this is something I recommend. if you are overly nervous about doing that. then stick to what you have.

The most important thing to note when installing FR orange is to fastboot flash the boot.img that is appropriate for your phone (1100 / d00 ) before you flash the system.img otherwise you will boot loop! Its not clearly indicated in the linked thread from OP.
Carrion
P.S. I do like 2.3.4 more then 2.2.3 ... im just ticked cuz i lost a transparent widget, because for some ungodly reason its now incompatible?!

didn't know about the timing, but yes make sure you follow that guide as well.
ah sorry to hear that.
Did you try doing the spare parts fix? (download spare parts and turn off compatibility mode)

Why are you installing the FR Orange (2.3.4)? The 1100/d00 issue is dealt with in the unlock guides - this thread clearly notes the steps are for unlocked phones only to install Bell 2.3.4.
Anyhow, there are some great threads on unlocking international phones and folks should really consult those to unlock.
Carrion332 said:
The most important thing to note when installing FR orange is to fastboot flash the boot.img that is appropriate for your phone (1100 / d00 ) before you flash the system.img otherwise you will boot loop! Its not clearly indicated in the linked thread from OP.
Carrion
P.S. I do like 2.3.4 more then 2.2.3 ... im just ticked cuz i lost a transparent widget, because for some ungodly reason its now incompatible?!
Click to expand...
Click to collapse

Gonna try that now... thing is i don't have the apk,Ii need to download it from the market, i have already purchased it but its now no longer visable?! I have tried market enabler... this did nothing... i would really like the ability to see and use all the apps in the app market, i know this is a bit off topic though.

Carrion332 said:
Gonna try that now... thing is i don't have the apk,Ii need to download it from the market, i have already purchased it but its now no longer visable?! I have tried market enabler... this did nothing... i would really like the ability to see and use all the apps in the app market, i know this is a bit off topic though.
Click to expand...
Click to collapse
I'm having the same issue with a couple apps that i've purchased.
Anyways back on topic, I was on on cherryblur 0.5 and i managed to get to the bell GB following most of this guide. I tried to do a restore of a nandroid backup i made before going to GB, but for some reason the phone wouldn't boot. It would just stay at the moto symbol. Im assuming it was because of the boot.img. I tried for a few hours to get it to work, but then gave up and flashed the 2.1.1 french sbf, and then used NFHimselfs system restore script to get me back to the stock bell rom. It worked very well, just took a long time.
Personally I really like this Bell rom, works very well for me. Battery life has increased, its FAST, and there's no ram issues. As for the Webtop stuff, im not sure about. I rarely use it.
Just noticed that after flashing the bell_ihop.sbf to unlock the blootloader, the ram goes back down to 300mb. I wonder if someone can dig deeper into the bell_ihop bootloader and possibly fix the ram issues.

Save a copy of 4.5.91 sbf

if you are still on 1.8.3 stock, you can get a copy of 4.5.91.sbf file by using Motorola Software Update, handy if you need to flash a clean version of 4.5.91 on 4.5.40 or 4.5.91(OTA upgraded).
by default, the sbf file is saved to:
C:\Program Files (x86)\Motorola\Software Update\firmwares\1FF-olympus-user-2.3.4-4.5.91-110625-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011.sbf.gz
copy it to somewhere else before Motorola Software Update finishes flashing or it will get deleted automatically.

erasen1 said:
if you are still on 1.8.3 stock, you can get a copy of 4.5.91.sbf file by using Motorola Software Update, handy if you need to flash a clean version of 4.5.91 on 4.5.40 or 4.5.91(OTA upgraded).
by default, the sbf file is saved to:
C:\Program Files (x86)\Motorola\Software Update\firmwares\1FF-olympus-user-2.3.4-4.5.91-110625-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011.sbf.gz
copy it to somewhere else before Motorola Software Update finishes flashing or it will get deleted automatically.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
Have you flashed it yet? I sent Kennithpenn a pm about this and he asked me not to release it. He also told me it is not safe to flash via rsd!!

flashing ...

erasen1 said:
flashing ...
Click to expand...
Click to collapse
Are you using Motorola Software Update tool or RSD 5.3.1 to flash it? Also was you bl already unlocked before or after you did it?

NYG-SBXLII said:
Are you using Motorola Software Update tool or RSD 5.3.1 to flash it? Also was you bl already unlocked before or after you did it?
Click to expand...
Click to collapse
at first, I used Motorola Software Update tool to flash, it flashed successfully - as expected
then I tried to flash it using RSD Lite v5.0, also flashed successfully, it actually did not erase user & data partition, retaining all apps & settings.

NYG-SBXLII said:
Are you using Motorola Software Update tool or RSD 5.3.1 to flash it? Also was you bl already unlocked before or after you did it?
Click to expand...
Click to collapse
the phone was BL unlocked before, I flashed from 4.5.40 back to 1.8.3 sbf, then " fastboot oem lock" ( not sure if it locks the phone back), then Motorola Software Update tool & RSD.

erasen1 said:
at first, I used Motorola Software Update tool to flash, it flashed successfully - as expected
then I tried to flash it using RSD Lite v5.0, also flashed successfully, it actually did not erase user & data partition, retaining all apps & settings.
Click to expand...
Click to collapse
Ok, well 4.5.40 was never released so thats probably why you where able to downgrade to 1.83. Im not sure if it is a good idea to flash this after 4.5.91 though. probably not a good idea to release unless someone has the ball's to flash it from 4.5.91 bl unlock.
edit: well you flashed it via rsd after you used Motorola Software Update. So it might be all good..
edit: **** it, i've got insurance, im going to give a go... I was bl unlocked and flashed leaked ota
edit: confirmed, 1FF-olympus-user-2.3.4-4.5.91-110625-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011.sbf is safe via rsd 5.3.1 after ota bl unlocked 4.5.91!
edit: this seems to be a service sbf as it does not wipe data!

NYG-SBXLII said:
I sent Kennithpenn a pm about this and he asked me not to release it.
Click to expand...
Click to collapse
What do you mean he told you not to release it. The upgrade file is freely available from Motorola now. You can download direct to your PC from the software updater.

Would this work for me if after pulling the OTA I am stuck at the Motorola M with Dual Core? Could I flash this SBF and get my phone back up and running? I tried using the Motorola Software Update software but not sure what mode to connect my phone for it to recognize it.. Connected via Fastboot the software says:
"Motorola Software Update is unable to identify you device at this time. Please Try again"
Thank you in advance

NYG-SBXLII said:
Ok, well 4.5.40 was never released so thats probably why you where able to downgrade to 1.83. Im not sure if it is a good idea to flash this after 4.5.91 though. probably not a good idea to release unless someone has the ball's to flash it from 4.5.91 bl unlock.
edit: well you flashed it via rsd after you used Motorola Software Update. So it might be all good..
edit: **** it, i've got insurance, im going to give a go... I was bl unlocked and flashed leaked ota
edit: confirmed, 1FF-olympus-user-2.3.4-4.5.91-110625-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011.sbf is safe via rsd 5.3.1 after ota bl unlocked 4.5.91!
edit: this seems to be a service sbf as it does not wipe data!
Click to expand...
Click to collapse
NYG, Thanks for experimenting..
Question: So if I do the OTA update, then I MOD the hell out of it. I can use this SBF file and RSD to go back to stock and my phone will be like nothing ever changed...???

you shouldn't install this directly, but it is very handy to have (in order to extract images)
my method is to download it through the program but disconnect the phone as soon as it starts to download. when it finishes, you should have the file there, copy/move it whatever and exit the program.

b30sam said:
NYG, Thanks for experimenting..
Question: So if I do the OTA update, then I MOD the hell out of it. I can use this SBF file and RSD to go back to stock and my phone will be like nothing ever changed...???
Click to expand...
Click to collapse
Yes, but just like the ota, after you flash this, you can never flash firmware lower than 4.5.91 again or you will get a hard brick. Also depending on what ROM you are on before you flash this you may have to manually wipe data because this sbf does not.

franciscojavierleon said:
you shouldn't install this directly, but it is very handy to have (in order to extract images)
my method is to download it through the program but disconnect the phone as soon as it starts to download. when it finishes, you should have the file there, copy/move it whatever and exit the program.
Click to expand...
Click to collapse
This file can now be downloaded from the dev section. http://forum.xda-developers.com/showthread.php?t=1181932

5.1.1 root tips / tutorial?

Hi,
trying to root a phone of a friend, z1 compact.
He has 5.1.1 installed.
Should i wait or root now, because i heard there is a new update for z1compact? Do i need to unlock the bootloader to root it? New version is not stable yet i read and causes bootloops.
What is the easiest way i should root it, step by step?
I am not that experienced with android myself, so any tips are welcome. He just wants his phone rooted to control internet/data access for some apps, and have more control over the apps installed....
Thanks in advance!

m123456789 said:
Hi,
trying to root a phone of a friend, z1 compact.
He has 5.1.1 installed.
Should i wait or root now, because i heard there is a new update for z1compact? Do i need to unlock the bootloader to root it? New version is not stable yet i read and causes bootloops.
What is the easiest way i should root it, step by step?
I am not that experienced with android myself, so any tips are welcome. He just wants his phone rooted to control internet/data access for some apps, and have more control over the apps installed....
Thanks in advance!
Click to expand...
Click to collapse
Someone here - http://forum.xda-developers.com/sony-xperia-z1-compact/general/root-14-6-0-368-via-kingroot-t3242735 - says they got kingroot method working on 5.1, but not yet able to switch to SuperSU, (https://www.google.com/url?q=http:/...bskDFQ&usg=AFQjCNEbOT7fDsBIA-flXO3m6zakipqSLw). I haven't heard of that working on 5.1 up till now. Besides that with locked bl, only root is this - http://forum.xda-developers.com/son...ck-step-step-to-rooted-lollipop-14-6-t3213465.
Doesn't seem to be any reason to wait. The last update is still 5.1, and the last news is that there will be no M for Z1c, - (http://forum.xda-developers.com/son...al/marshmallow-upgrade-z1-z1-compact-t3218903).

levone1 said:
Someone here - http://forum.xda-developers.com/sony-xperia-z1-compact/general/root-14-6-0-368-via-kingroot-t3242735 - says they got kingroot method working on 5.1, but not yet able to switch to SuperSU, (https://www.google.com/url?q=http:/...bskDFQ&usg=AFQjCNEbOT7fDsBIA-flXO3m6zakipqSLw). I haven't heard of that working on 5.1 up till now. Besides that with locked bl, only root is this - http://forum.xda-developers.com/son...ck-step-step-to-rooted-lollipop-14-6-t3213465.
Doesn't seem to be any reason to wait. The last update is still 5.1, and the last news is that there will be no M for Z1c, - (http://forum.xda-developers.com/son...al/marshmallow-upgrade-z1-z1-compact-t3218903).
Click to expand...
Click to collapse
(So i use this tutorial: http://forum.xda-developers.com/showpost.php?p=62222794&postcount=37)
So i need to:
1. Somehow downgrade device to stock kitkat (that is 4.4 right?), then root it
2. and then update to 5.1.1 again?
In step 2, would you recommend update to a prerooted version like this one? 14.6.A.1.216 http://forum.xda-developers.com/son...03-14-6-1-216-customized-ce5-central-t3243035

m123456789 said:
(So i use this tutorial: http://forum.xda-developers.com/showpost.php?p=62222794&postcount=37)
So i need to:
1. Somehow downgrade device to stock kitkat (that is 4.4 right?), then root it
2. and then update to 5.1.1 again?
In step 2, would you recommend update to a prerooted version like this one? 14.6.A.1.216 http://forum.xda-developers.com/son...03-14-6-1-216-customized-ce5-central-t3243035
Click to expand...
Click to collapse
I haven't yet tried .216. Its new as of a couple of days ago. I also haven't yet tried PRFs. I've read a few threads that seem to indicate occasional problems with them. Since I have unlocked bl, I've been able to root the easy way, so I'm not sure what options or limitations there are with that rooting method. From my experience, I would recommend RockZ1 ROM, (.368). It has anything you would want included, and may well update to the new fw anytime soon...

Don't unlock the bootloader many functions will be lost if you are trying to keep the stock rom.
Sent from my C6902 using XDA Premium 4 mobile app

The device is now in Boot Loop after trying to go from the 5.1.1 to 4.4.4 using Sony Mobily Flasher and then trying to install 14.4.A.0.157 ...
What did I do wrong, what can i do now?
Thanks for any help

I just turned phone off, loaded 14.4.A.0.157 with Sony Mobile Flasher, plugged in with volume down key. Then it was flashing and finished. Then unplugged and started.
And now it keeps restarting at startup (when the "waves" appear). That's a bootloop right? I turned it off with the small red button now.
I tried flashing again with same method. And it is still bootlooping after it......
Any expert could help? Or is the phone broken forever now

Did you wipe data / cache?

Steffe89 said:
Did you wipe data / cache?
Click to expand...
Click to collapse
No, where or how should i do that?
Edit: did some research. Should i have selected something in SonyMobileFlasher?
Because I don't find cache i only have these 2 options:
APPS_LOG
USERDATA
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://i.imgur.com/RCJNhRO.jpg

Repair the phone via PC Companion.
Sent from my C6902 using XDA Premium 4 mobile app

DetmL said:
Repair the phone via PC Companion.
Sent from my C6902 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
PC Companion does not recognize the phone. When i plug it in, it says searching, but then... "no phone connected"
But in windows i see it connected as a drive which i can not use

m123456789 said:
No, where or how should i do that?
Edit: did some research. Should i have selected something in SonyMobileFlasher?
Because I don't find cache i only have these 2 options:
APPS_LOG
USERDATA
http://i.imgur.com/RCJNhRO.jpg
Click to expand...
Click to collapse
Yes, check the 2 'wipe' boxes, and flash again. I bet that will do it. The same thing happened to me with . 216

levone1 said:
Yes, check the 2 'wipe' boxes, and flash again. I bet that will do it. The same thing happened to me with . 216
Click to expand...
Click to collapse
Just tried with another version. Bootloop aswell. Now i noticed in log, that i should have enabled unknown sources and debugging? But i can't enable it now, because it does not boot.
09/000/2015 02:00:46 - INFO - Flashing finished.
09/000/2015 02:00:46 - INFO - Please unplug and start your phone
09/000/2015 02:00:46 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
Trying your method now, with the 2 wipes selected
Edit: with wipe it now boots. thanks! trying to install .108 now, because other is not rootable.
and after rooting kitkat4.4.4 .108, i try to update to a prerooted 5.1.1

I am on a rooted 4.4.4 .108 now.
How do i proceed?
For example, how can i load this prerooted 5.1.1 http://forum.xda-developers.com/son...03-14-6-1-216-customized-ce5-central-t3243035 ?

m123456789 said:
Just tried with another version. Bootloop aswell. Now i noticed in log, that i should have enabled unknown sources and debugging? But i can't enable it now, because it does not boot.
09/000/2015 02:00:46 - INFO - Flashing finished.
09/000/2015 02:00:46 - INFO - Please unplug and start your phone
09/000/2015 02:00:46 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
Trying your method now, with the 2 wipes selected
Edit: with wipe it now boots. thanks! trying to install .108 now, because other is not rootable.
and after rooting kitkat4.4.4 .108, i try to update to a prerooted 5.1.1
Click to expand...
Click to collapse
The msg about unknown sources, etc. comes after the flash bc now your phone is stock, so by default they're not checked. It wouldn't have flashed if they weren't checked in the first place. You'll probably hit some bumps, but don't give up. There's almost always a fix...

On rooted 4.4.4 with Superuser installed. Then trying to load the prerooted 5.1.1 zip.
So rebooted with volume down and installed the prerooted zip file from SD. With CWRM
Everything seems to work, but at the end of flashing i saw some message like:
"set_perm some changes failed"
Then after restart all apps get optimized and i am on 5.1.1.
However, i think i lost root, also no SuperUser installed? And the Superuser was included in the zip prerooted file.

Don't worry, seems to work fine after installing lockeddualrecovery.
How exactly do i install the
xposed-v75-sdk22-arm.zip ?
thanks in advance

m123456789 said:
I am on a rooted 4.4.4 .108 now.
How do i proceed?
For example, how can i load this prerooted 5.1.1 http://forum.xda-developers.com/son...03-14-6-1-216-customized-ce5-central-t3243035 ?
Click to expand...
Click to collapse
It's not worth it to update, believe me

m123456789 said:
Don't worry, seems to work fine after installing lockeddualrecovery.
How exactly do i install the
xposed-v75-sdk22-arm.zip ?
thanks in advance
Click to expand...
Click to collapse
Open recovery > select 'install' > choose file. You'll get a long reboot and the whole 'optimizing' thing again.

Yes, after installing xposedv75, it rebooted and loaded addiotional ~+100 apps But it seems to work.
What program would you guys recommend in terms of saving data, restricting internet access of apps (and maybe even ads). And some other for spoofing/restricting requested usage access of certain apps?
(I tried Xprivacy, but it is pretty advanced. It did not seem to block inapp ads or internet access, even when you denied it. Also it only lists apps which are newly installed, not preinstalled ones.
Maybe it is easy but I just didn't understand it yet )

[Discussion] Dumb attempt to upgrade to Marshmallow with TWRM in osprey

Hi everyone, posting this as a information about something you should NOT try: upgrade your OTA rom with custom recovery installed, in my case TWRP.
I did this with ignorance of not think that (or search about) the custom rom could interfere at the normal process of OTA upgrade from Lollipop to MarshMallow. Actually I remembered that I was unlocked and rooted the phone but I did not remember I was using custom recovery. AFAIK at this device is impossible to root without unlocking and custom recovery.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you are on TWRP don't do this!
For those don't know about TWRP and OTA updates, read this:
https://twrp.me/faq/officialota.html
In short terms: don't try OTA updates (official updates) if you installed custom rom such as TWRP. "Installing official updates from your manufacturer or carrier is not supported by TWRP." "[This] may result in unexpected behavior" "Most of the time the best way to get a new update onto your device is to simply wait a couple of days for ROM makers for your device to come up with ROMs that are based on the new update that you can safely and easily install."
But I did it. And now I'm reporting it for those who are curious. So, what's happened?
Fortunately the device is not bricked as I thought when it reboot to TWRP for flashing the OTA update instead of the stock recovery process! I thought that I messed everything when I see the frozen TWRP for something about 10 minutes or less. After the long 10 minutes of frozen TWRP image I got the recovery working and checked the log:
Of course, errors on the log.
Rebooted and got a frozen background image, after a while a permanent black. When the screen turn off the notification system shows the battery as dead (and it as not). But I could turn it off and gain access to the recovery holding power and volume down buttons.
After two failed reboots to the system with the same result I tried to make a screenshot using the hard buttons and it works (screenshoted the black screen) and suddenly the lock screen shows up. I got into, everything working slow meaning that there was a lot things working in the background. Got some error messages from google service and MMS/SMS communication and minutes later it automatically reboots and booted the TWRP again.
This turned to a loop. I stopped this by going to the system setup - about the device - check for updates. And got a message "the update has failed". Good. After a while the message offering the update shows again... No, thanks...
I rebooted to TWRP and fixed the permissions, maybe this solve some problems.
Right now the phone is working but the rebooting process has unexpected behaviors, some tries result in a normal fast process and other tries result in a long black image and the system/launcher just don't arm up for some minutes, but after a while it works. I'm not confident. Already backed up apps with Titanium backup.
I'm planning to restore everything from the stock using this guide:
http://forum.xda-developers.com/mot...e-restore-moto-e-2015-stock-firmware-t3054303
And them, maybe, update the OTA to marshmallow. Before doing that, I will search and get to know if it is possible to re-root the phone with marshmallow in osprey (that means re-unlock and install TWRP again). Rooted device it's a need for me.
This is what happened to my device when tried to OTA update with TWRP. I had luck not bricking this.

+1 on the dumb attempt. Early morning, excited for the release, upgrade please! Yeah, no good. Is restoring our only option? Seems the upgrade has not even started so what about deleting the downloaded image file or trying to kill the process attempt?

did you really had to make a new thread with that huge wall of text? haha come on man, common knowledge that to take the OTA you need stock recovery ?
Sent from my Nexus 6 using Tapatalk

Seems the upgrade has not even started so what about deleting the downloaded image file or trying to kill the process attempt?
Click to expand...
Click to collapse
Yeah, DON'T proceed with the update! Deleting the downloaded files just break the process... My advise is to make a backup before deleting this.

sgloki77 said:
did you really had to make a new thread with that huge wall of text? haha come on man, common knowledge that to take the OTA you need stock recovery
Click to expand...
Click to collapse
Ok, sorry about the huge wall of text.

No need to adb stock image. A simple factory reset worked for me. Next time will have more caffiene before attempting anything major with my phone.

golgiapp said:
No need to adb stock image. A simple factory reset worked for me. Next time will have more caffiene before attempting anything major with my phone.
Click to expand...
Click to collapse
:good:
Good to know that a factory reset could fix the problems caused by the OTA update with TWRP. But after this it should remain with custom recovery and not possible to OTA update. for stock MM

i downloaded the 24.11.25.en.US ota update not installed yet becuase i want to find it first and save it on my pc.
any idea what folder is saved ??

gonzodesigns said:
i downloaded the 24.11.25.en.US ota update not installed yet becuase i want to find it first and save it on my pc.
any idea what folder is saved ??
Click to expand...
Click to collapse
Not sure, but take a look at /cache

gonzodesigns said:
i downloaded the 24.11.25.en.US ota update not installed yet becuase i want to find it first and save it on my pc.
any idea what folder is saved ??
Click to expand...
Click to collapse
/data/data/com.motorola.ccc.ota/app_download

hp420 said:
/data/data/com.motorola.ccc.ota/app_download
Click to expand...
Click to collapse
found it!!
thanks extracted ok !!
its a zip flashable,can it be converted to install like the oem recovery images using the adb method?

gonzodesigns said:
i downloaded the 24.11.25.en.US ota update not installed yet becuase i want to find it first and save it on my pc.
any idea what folder is saved ??
Click to expand...
Click to collapse
Thank you for the warning
---------- Post added at 12:58 AM ---------- Previous post was at 12:54 AM ----------
Thank you for the warning

I experience this today, I flashed a stock rom again so I can have the OTA update, but what I can't do is root my device, I flash the custom recovery and then I flash the beta version of SuperSU, and when I reboot my device it bricks in the Motorola Logo, anybody knows how to fix this, or should I wait a little bit longer to root my phone? as the OP I need root too

Use the latest 2.62 superSU zip. And never root with the TWRP option before reboot.
Sent from my MotoG3 using Tapatalk

nelsonw said:
Use the latest 2.62 superSU zip. And never root with the TWRP option before reboot.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Never done that, I tried flashing the superSU 2.52 from a bunch of tutorials I found on Google, but all it does is bricking my phone on the Motorola Logo, then I have to do all the downgrade and update process again

VicSanRED said:
Never done that, I tried flashing the superSU 2.52 from a bunch of tutorials I found on Google, but all it does is bricking my phone on the Motorola Logo, then I have to do all the downgrade and update process again
Click to expand...
Click to collapse
this is a known issue with the mm update. Use 2.61 or newer, only. These are the new systemless root zips.

hp420 said:
this is a known issue with the mm update. Use 2.61 or newer, only. These are the new systemless root zips.
Click to expand...
Click to collapse
I tried with the latest version 2.66 and still the same issue. Don't know what to do now.

So its posible to root MM ?? Safe ,stable?
Supersu v 2.62??

Yeah, 2.62 is the only one working. This worked for me BETA-SuperSU-v2.62-20151210170034
Sent from my MotoG3 using Tapatalk

nelsonw said:
Yeah, 2.62 is the only one working. This worked for me BETA-SuperSU-v2.62-20151210170034
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Can you post a little tutorial?, I wanna be sure I'm doing everything OK.