Database Users

[HowTo][Temporary] Fix stuck at Boot from Downgrading Android 4.4.4 to 4.4.2

If you Softbricked your phone and are stucked at the Google Unlocked Logo you're right here... the major point of this is to unbrick the phone and not to set it in derivation condition and btw.... unbrick flashing etc at your own risk
Download:
https://drive.google.com/file/d/0B6IdzeLKSZoGX1NzZTlmNVdKeWM/edit?usp=sharing
THIS IS THE GERMAN STOCK ROM MOTOROLA XT1032! IT'S REPORTED THAT THERE COULD BE NO GSM SIGNAL & WIFI!!!!
Hey Guys,
i dont know if this is posted somehere here at the MotoG XDA section....
I tried the MotoG GPe Rom and received an OTA Update to Android 4.4.4 and installed it. After reverting to Motorola stock rom or GPe 4.4.2 the phone stucks in the boot logo and won't boot up anymore.
So here's is MY fix for the problem and i hope i can help some... it's a temporal fix right now to unbrick the half-bricked MotoG for further development
1. Restart Phone in Bootloader
Power + Volume down to enter the bootloader mode and flash the GPe Recovery as *.img file from Philz with fastboot command​
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
2. Enter the Recovery Mode
Enter the recovery mode with selecting "Recovery" and hit the volume up to enter it.
In recovery mode you will get some error messages like in the attached phote below. To fix these messages:​
Mounts and Storage --> hit "format /cache" and "format /data and /data/media (/sdcard)"
Click to expand...
Click to collapse
3. Push CWM Backup to /sdcard
You have to push a cwm Backup to the /sdcard to restore it later
Download my package with adb and cwm backup and unzip it wherever you want after the extraction and double click at "111 push cwm files to sdcard.bat" to push all need files to tranfer them to the sdcard​
adb push boot.img /sdcard/clockworkmod/backup/2014/boot.img
adb push cache.context /sdcard/clockworkmod/backup/2014/cache.context
adb push cache.ext4.tar /sdcard/clockworkmod/backup/2014/cache.ext4.tar
adb push cache.ext4.tar.a /sdcard/clockworkmod/backup/2014/cache.ext4.tar.a
adb push data.context /sdcard/clockworkmod/backup/2014/data.context
adb push data.f2fs.tar /sdcard/clockworkmod/backup/2014/data.f2fs.tar
adb push data.f2fs.tar.a /sdcard/clockworkmod/backup/2014/data.f2fs.tar.a
adb push nandroid.md5 /sdcard/clockworkmod/backup/2014/nandroid.md5
adb push recovery.img /sdcard/clockworkmod/backup/2014/recovery.img
adb push recovery.log /sdcard/clockworkmod/backup/2014/recovery.log
adb push system.context /sdcard/clockworkmod/backup/2014/system.context
adb push system.ext4.tar /sdcard/clockworkmod/backup/2014/system.ext4.tar
adb push system.ext4.tar.a /sdcard/clockworkmod/backup/2014/system.ext4.tar.a
Click to expand...
Click to collapse
4. Restore CWM Backup
Restore the CWM backup from "Restore from /sdcard" select the 2014 folder and confirm... after sucessful restoring you are able to boot up your MotoG​
I hope this worked as a temporal fix Feedback or critics are welcome!!!!

fl4m3y said:
Download link will follow in 1 or 2 hours... it's still uploading to my gdrive
Hey Guys,
i dont know if this is posted somehere here at the MotoG XDA section....
I tried the MotoG GPe Rom and received an OTA Update to Android 4.4.4 and installed it. After reverting to Motorola stock rom or GPe 4.4.2 the phone stucks in the boot logo and won't boot up anymore.
So here's is MY fix for the problem and i hope i can help some... it's a temporal fix right now to unbrick the half-bricked MotoG for further development
1. Restart Phone in Bootloader
Power + Volume down to enter the bootloader mode and flash the GPe Recovery as *.img file from Philz with fastboot command​
2. Enter the Recovery Mode
Enter the recovery mode with selecting "Recovery" and hit the volume up to enter it.
In recovery mode you will get some error messages like in the attached phote below. To fix these messages:​
3. Push CWM Backup to /sdcard
You have to push a cwm Backup to the /sdcard to restore it later
Download my package with adb and cwm backup and unzip it wherever you want after the extraction and double click at "111 push cwm files to sdcard.bat" to push all need files to tranfer them to the sdcard​
4. Restore CWM Backup
Restore the CWM backup from "Restore from /sdcard" select the 2014 folder and confirm... after sucessful restoring you are able to boot up your MotoG​
I hope this worked as a temporal fix Feedback or critics are welcome!!!!
Click to expand...
Click to collapse
I haven't had the need to try this but I think its good I'm going to stick with CWM for a while until the update for non GPE devices is out or android L..
Sent from my Moto G using XDA Free mobile app

will have a link

Waiting the downlod link :good:

cecoicov said:
will have a link
Click to expand...
Click to collapse
borimol said:
Waiting the downlod link :good:
Click to expand...
Click to collapse
Download Link is online...

Phone works, but does not recognize the SIM card and no WIFI

cecoicov said:
Phone works, but does not recognize the SIM card and no WIFI
Click to expand...
Click to collapse
Can you now flash official 4.4.2 stock (non GPE)?

cecoicov said:
Phone works, but does not recognize the SIM card and no WIFI
Click to expand...
Click to collapse
works fine for me
borimol said:
Can you now flash official 4.4.2 stock (non GPE)?
Click to expand...
Click to collapse
no... flashing with fastboot wont work until we get the GPe Factory Image (I hope) or another fix... this is a "work around" but the problem isn't fixed

after flash with official stock 4.4.2 (non GPE) does phone not start again

cecoicov said:
after flash with official stock 4.4.2 (non GPE) does phone not start again
Click to expand...
Click to collapse
Fastboot flashes doesn't work until there is a real fix... if the stuck on boot logo persist just follw my tutorial to unbrick the phone

Ок, thanks for the help but I guess I will seek another solution

cecoicov said:
Phone works, but does not recognize the SIM card and no WIFI
Click to expand...
Click to collapse
Same issue occurred to me, the IMEI paste seems to be gone rendering the phone useless for (data) network usage. There's no way to restore the IMEI at the moment.

ok this worked for me
started cyanogenmod????????
i could not test wifi or network
but off course i am dumb, and had to try to restore a nandroid backup of gep 4.4.4, i did and phone ask for password (because of encryption of file system), then i tried again to recover using this method and did not worked, used adb gpe 4.4.2, then again this method and nothing
what the hell
firts time could recover, now it wont recover anymore, stays on google logo lol
--------------
some time latter i managed to boot it again
it started stock android in german?'
i believe there is no signal

maurocds said:
some time latter i managed to boot it again
it started stock android in german?'
i believe there is no signal
Click to expand...
Click to collapse
It's the open german version without any provider stuff... i cant upload th english version because i cant flash via fastboot. the only possibility is to install an english custom rom via cwm. therfore you need to replace the GPe CWM recovery to normal philz recovery because of the filesystem

fl4m3y said:
It's the open german version without any provider stuff... i cant upload th english version because i cant flash via fastboot. the only possibility is to install an english custom rom via cwm. therfore you need to replace the GPe CWM recovery to normal philz recovery because of the filesystem
Click to expand...
Click to collapse
hey man, i sent you a PM, read it fast
-----------
ok i booted my phone again after flashing this, then flashing gpe, then this again lol
you have to be patient while pushing the data, it takes a lot, then after that, you must disable md5 on recovery or else it will fail, then you can restore cwm fine and boot
firmware is stock 442 german, but you can change into english
thanks, no matter what i tried i never could boot
at least the phone work,
have to test more about signal stuff

Due to some personal information (google account) i was forced to deactivate the public access to the file.... password changed of my account and now it should be fine
so download is activated again

Hey,
I´ve been using GPE 4.4.4 recently too and I wanted to go back to German retail 4.4.2. in order to try to catch an OTA. It´s quite easy to do, just beware of one thing. You have to RETAIN the partition table (gpt.bin) from GPE. Do not flash gpt.bin from the target firmware - 4.4.2 in this case, just avoid the step "fastboot flash partition gpt.bin". If you did it already, you can try following: extract gpt.bin from GPE 4.4.4 OTA zip and copy it and replace gpt.bin in your 4.4.2 firmware folder and then flash it using standard procedure.
Also maybe the same thing applies to logo.bin, but of this one I´m not sure. I avoided to flash it too just in case. Now I´m on fully working German retail 4.4.2. No OTA yet, though, but that´s another story.

anyone has the gpt.bin from the GPe 4.4.4????
I want to flash via fastboot the GPe 4.4.2 Version and after the OTA Update to 4.4.4
and btw... thank you for the hint!!!!

View attachment gpt.7z
fl4m3y said:
anyone has the gpt.bin from the gpe 4.4.4????
I want to flash via fastboot the gpe 4.4.2 version and after the ota update to 4.4.4
and btw... Thank you for the hint!!!!
Click to expand...
Click to collapse
from ota gpe 444

drfr said:
Hey,
I´ve been using GPE 4.4.4 recently too and I wanted to go back to German retail 4.4.2. in order to try to catch an OTA. It´s quite easy to do, just beware of one thing. You have to RETAIN the partition table (gpt.bin) from GPE. Do not flash gpt.bin from the target firmware - 4.4.2 in this case, just avoid the step "fastboot flash partition gpt.bin". If you did it already, you can try following: extract gpt.bin from GPE 4.4.4 OTA zip and copy it and replace gpt.bin in your 4.4.2 firmware folder and then flash it using standard procedure.
Also maybe the same thing applies to logo.bin, but of this one I´m not sure. I avoided to flash it too just in case. Now I´m on fully working German retail 4.4.2. No OTA yet, though, but that´s another story.
Click to expand...
Click to collapse
THIS DID NOT WORK FOR ME
I AM ON 4.4.4 gpe
AND JUST WANTED TO TEST
so i put the 4.4.4 ota gpt.bin in the stock 4.4.2 image , and the stock gpe 4.4.2, and both flashes were stuck on logo, did not booted,

[INFO] [GUIDE] [HOW TO] Nexus 6 OTA help desk

Here is a dedicated thread for Q&A and general info on OTA's for the Motorola Nexus 6. Please feel free to discuss all things OTA related and ask any questions you may have.
*Bootloader lock status has no effect on OTA pass or fail.*
To summarize, an OTA (Over The Air) is a software update pushed to nexus devices directly from Google. You will receive a notification when one is available for your device. The files are generally large in size and downloading via WiFi is recommended.
With Android 5.0 and up, OTA updating has changed significantly from previous versions. In the past, you could be stock, rooted, with stock recovery and OTA's would flash successfully. This is no longer possible in lollipop. Absolutely no system or kernel modifications can be present in order for the OTA to flash. This means that if you have unencrypted the stock kernel, the OTA will fail. The phone must be in a "out of box" state.
As always, you are not required to take the OTA as there are other options available. If you are already rooted, unlocked and using a custom recovery, you can use an updated custom ROM provided by the amazing development community here at XDA. Factory images are released by Google prior to OTA's being pushed out so most, if not all, of the custom ROMs are updated before you'll even see an OTA notification. Also, there are stock, rooted ROMs available as well.
*Factory images*
You can always update or return to stock via factory images direct from Google. Link to this guide provided in post #2
*Sideloading*
Another feature available to use is the sideload option. With the use of a few simple ADB commands, you can apply the OTA via sideload. Sideloading will require connecting to your PC and a working ADB/fastboot connection. Directions for sideloading are in post #3.
*Updating while rooted, unlocked, and having a custom recovery via fastboot*
This is quite simple with basic knowledge of fastboot/ADB. Download the factory image, extract the system image and flash with fastboot. Then flash TWRP and SuperSU again. You can also flash the boot image if desired. However if you are unencrypted, this will encrypt the device.
Many, MANY thanks to the development community, themers, modders and other talented people here at XDA.
Thanks @El Daddy for guidance and advice.​

Helpful links:
*Please hit the thanks button for the OP's of the XDA threads below if the threads were helpful in any way.*
Beginners guide:
Thanks @xBeerdroiDx
http://forum.xda-developers.com/showthread.php?t=2948481
Setting up and using ADB and fastboot:
Thanks @rootSU
http://forum.xda-developers.com/showthread.php?t=3006500
Factory images installation instructions:
(Including the fastboot flash method for flashing individual images):
Thanks @Mr hOaX
http://forum.xda-developers.com/showthread.php?t=2954008
OTA files:
Thanks @oldblue910
http://forum.xda-developers.com/showthread.php?t=2906493
*For rooted/unlocked users only*
OTA zip files and radio files (TWRP flashable):
Thanks @Q9Nap
http://forum.xda-developers.com/showthread.php?t=3066052
Radio thread (fastboot flashable):
Thanks @zephiK
http://forum.xda-developers.com/showthread.php?t=2969380​

Directions for sideloading
*These directions are based on Android SDK, Windows OS and a 100% stock Nexus 6*
This is just a simple, well known, user guide to using sideload.
Make sure your SDK is updated!​
Download the OTA file to your PC, rename it to update.zip and transfer into the platform-tools folder of your SDK.
Connect your Nexus to your PC with your OEM USB cable.
Hold shift and right click on platform-tools folder and select open command prompt here.
Type: adb devices
If your serial number comes up, you are good to go. If not, check out your drivers in device manager. You may need to manually point your PC to their location. Also, you may need to uninstall any other Android drivers that are not associated with your Nexus.
Type: adb reboot bootloader
Select recovery mode from your phone using the volume down key. Once you've highlighted recovery mode, press power to select it.
It looks like a restart but the the dead android appears with red exclamation point. When that happens, hold power button and press volume up once.
Once in recovery, use the volume down key to select apply update from adb and push power to select it.
When your phone says now send file,
type: adb sideload update.zip
If all goes well, you'll see things progress and your Nexus will restart when complete. If you encounter the device not found error after beginning, unplug your USB and reconnect. I had to do it twice, but it works.

How do we install ota zip

if you are running stock you should be able to use wug toolkit and have it flash this zip file

What about stock-ish? I'm assuming since I'm rooted with my device unencrypted, that I can't flash this, right?

Flashing now. Will post back when done.
EDIT: Flash went perfect ^.^ 5.1 is all set.

knitler said:
Flashing now. Will post back when done.
EDIT: Flash went perfect ^.^ 5.1 is all set.
Click to expand...
Click to collapse
Were you completely stock?
Sent from my Nexus 6 using XDA Premium 4 mobile app

instructions for mac
http://www.androidcentral.com/how-manually-upgrade-your-nexus#slide5

I have a modded boot image and it failed to install. Guess ill have to nuke and start over to get this OTA in place.

http://www.androidpolice.com/2015/0...gs-android-5-1-ota-roundup-for-nexus-devices/ I just want to flash the radio but it looks line it's 20 MB bigger than the last

Is anyone creating a flashable zip that works with TWRP?

@oldblue910,
Thank you very much. ADB sideload went flawlessly (completely stock 5.0.1 of course).

I probably already know the answer but here is my situation... I am on the stock image but unlocked boot loader, rooted, and twrp recovery. The only way I can remain stock and not lose my current state other than root and a few apps that rely on root is to... Unroot, relock boot loader and put back stock recovery... Then OTA or side load? Theres no other option right?

I think I'm on the same situation as edif30
Stock image
rooted
unlocked bootloader
TWRP recovery
How can i sideload w/o losing root?

edif30 said:
I probably already know the answer but here is my situation... I am on the stock image but unlocked boot loader, rooted, and twrp recovery. The only way I can remain stock and not lose my current state other than root and a few apps that rely on root is to... Unroot, relock boot loader and put back stock recovery... Then OTA or side load? Theres no other option right?
Click to expand...
Click to collapse
You could flash the 5.0.1 factory image except for the userdata.img and radio.img and side load the OTA. Or you can wait for the 5.1 factory image and remove the "-w" from the flash-all script.
You will lose root and TWRP. but your data will remain intact.

So I'm all stock, unrooted, with a still-locked bootloader. I can flash the OTA without unlocking and without losing my data, right?

stevexyz0 said:
So I'm all stock, unrooted, with a still-locked bootloader. I can flash the OTA without unlocking and without losing my data, right?
Click to expand...
Click to collapse
Yep, just use ADB sideload.

So I had stock 5.0.1 with a custom kernel. I flashed the stock boot.img from the factory image using TWRP and I unrooted from in the SuperSU app, so I should be stock all around except for recovery. When I try to flash the OTA in TWRP it gives the following error message:
Package expects build fingerprint of google/shamu/shamu:5.0.1/LRX22C/1602158:user/release-keys or google/shamu/shamu:5.1/LMY47D/1743759:user/release-keys; this device has google/omni_shamu/shamu:5.0.2/LRX22G/dees_troy01130854:eng/test-keys.
Any idea why TWRP would think I was running 5.0.2?

cam30era said:
@oldblue910,
Thank you very much. ADB sideload went flawlessly (completely stock 5.0.1 of course).
Click to expand...
Click to collapse
Mine too but how long did it stay on the GOOGLE screen before booting?

MotoX OTA Update - XT1060 Blur_Version.212.166.3.ghost_verizon.Verizon.en.US .zip

Edit: The attached zip in post #2 in a minor update the original 4.4.4 release for XT1060 FXZ. Below are the instructions. This is NOT the Full 4.4.4 OTA update.
Instructions to flash
1.) Move zip file from /cache folder to /sdcard folder if you received OTA (Zip file in 2nd post if you do not have it.)
2.) To be safe, disable xposed framework (if you have it running).
3.) Reboot into bootloader
4.) Use mfastboot to flash stock recovery (if not running it)
mfastboot flash recovery recovery.img
Click to expand...
Click to collapse
5.) Boot into recovery from bootloader
6.) Hold Power + Up Button to get recovery menu.
7.) Flash zip file from sdcard.
8.) When complete reboot, then boot into bootloader.
9.) Use mfastboot to flash custom recovery (aka twrp)
mfastboot flash recovery <twrp file name>.img
Click to expand...
Click to collapse
10.) Reboot and enable xposed framework.
11.) Done.
Another suggestion by @KidJoe
After mfastboot flash recovery <recoveryyouwant>.img its long been suggested to do a mfastboot reboot-bootloader then go into recovery, before doing anything else.
We've seen many instances where skipping the reboot-bootloader and enter recovery giving symptoms like the flash of recovery didn't work... (i.e. "old" recovery was still on the phone)
Click to expand...
Click to collapse

just received the update as well but haven't installed

Zip attached.

Maintenance update.

Maintenance update. Does not break root.

911 bug fix, as mentioned in three other threads

WhammyDroid said:
Zip attached.
Click to expand...
Click to collapse
You flash this through RSD lite? I couldn't flash it through my TWRP recovery on my Moto X Developer Edition.
Cindy

cindylike24 said:
You flash this through RSD lite? I couldn't flash it through my TWRP recovery on my Moto X Developer Edition.
Cindy
Click to expand...
Click to collapse
I believe you have to have stock recovery to flash.

dannyxiii said:
I believe you have to have stock recovery to flash.
Click to expand...
Click to collapse
Well then, I'll have to put this on my to do list for when I get home tonight. No biggie.
Cindy

It's far, far more than a 911 bug fix ... there's 2500 lines in the updater script, touching dozens (if not hundreds) of app and files.

Does this require removal of root/xposed or just needs stock recovery?

TheDave1022 said:
Does this require removal of root/xposed or just needs stock recovery?
Click to expand...
Click to collapse
I generally disable xposed and flash stock recovery but root should be fine. Anyone have a copy of the stock recovery? I'm on the dev edition. OTA's are so infrequent on this device that I forget where I stash the stock recovery all the time.

I got the notification last night, and hid it this morning (turned off notifications for the Moto Updater app). I am on an XT1060 Moto Maker, with an unlocked bootloader. In the past I've flashed /system and /recovery to update (from 4.4.2 to 4.4.4) with the OTA, then reflashed TWRP and flashed SuperSU from there. Do I need to do all that, or just stock recovery?
I do have Xposed, Cerberus and App Ops installed as System Apps, I believe.

I found the recovery for myself at the following link:
http://motofirmware.center/files/file/47-vzw_xt1060_444-kxa2112-l126_cfc_1ffxmlzip/
Might help someone else...You can verify your build by going to About phone. I had Build number KXA21.12-L1.26

Maverick0984 said:
I found the recovery for myself at the following link:
http://motofirmware.center/files/file/47-vzw_xt1060_444-kxa2112-l126_cfc_1ffxmlzip/
Might help someone else...You can verify your build by going to About phone. I had Build number KXA21.12-L1.26
Click to expand...
Click to collapse
That's the exact model number on my phone! Thank you for putting this link up there!!
Cindy

For some reason, I cannot use either mfastboot or fastboot to flash the stock recovery. When flashing it, I get the android icon with the red triangle.
Its been a while since I have had to flash back to stock recovery. What am I missing? I have the stock recoverystored for the last official FXZ.

when android with red triangle appears, press vol up for 3 seconds and you will be given option to flash from sd card.

Well, this has locked me out of re-flashing custom recovery, which - of course - means there's nothing that can be done beyond that.
Any version of TWRP up to, and including, the latest flashes without error ... but when you boot, it's still got stock recovery on it.
So no way to root, apply supersu, or do anything.
---------- Post added 3rd June 2015 at 12:04 AM ---------- Previous post was 2nd June 2015 at 11:37 PM ----------
Anyone got the fxz for this yet?

Ok, figured this out ...
(was able to back down to the original 4.4.4 w/rsd-lite and regain TWRP and develop these steps)
So the following can be done to upgrade to this new version, and retain TWRP (plus you have the new recovery later on for 5.1 when it comes along ...)
First, the presumption here is you are unlocked. If you are not, none of this will work.
Also, you will need RSD-Lite installed and operational.
Download :
https://dl.dropboxusercontent.com/u...RIZON_4.4.4_KXA21.12-L1.26-3_cid2_1FF.xml.zip
https://dl.dropboxusercontent.com/u...4.4.4_KXA21.12-L1.26-3/twrp-2.8.6.0-ghost.img
https://dl.dropboxusercontent.com/u/22067374/GHOST_VERIZON_4.4.4_KXA21.12-L1.26-3/servicefile.xml
Unpack the GHOST zip file, and overwrite the "servicefile.xml" in the unpacked folder w/the one you downloaded, then copy the twrp .img in there.
Fire up RSD-Lite, put your phone in fastboot, and apply this update by loading the servicefile.xml as the update.
It will update everything, installing the TWRP instead of the new stock recovery.
Note: you can delete the twrp line in servicefile.xml if you wish to retain your existing custom recovery.
When done, you should reboot, update, and be up and running with the new 4.4.4 and TWRP ... so easy path back to root via TWRP.

FYI... its already confirmed that you do NOT have to disable Xposed... All you need is stock recovery.
See -> http://forum.xda-developers.com/moto-x/moto-x-qa/ota-custom-recovery-t3124492

Request for information: Update rooted Honor 7 on 5.0.2 TWRP recovery to 6.0.1

Hi. My phone status:
PLK-L01
PLK-L01C432B180
EMUI version 3.1
5.0.2
rooted with TWRP boot recovery.
I'm looking for steps to update to android version 6.0.1 without losing all of my data, and keeping phone rooted and same recovery.
Is this something which is possible?
The only steps I have found is to how to replace stock recovery to update OTA.
I expect I would then need to root phone again afterwards.
Is this the recommended way of updating, or can I manually perform the update safely, and are there tried and tested instructions for this?
Many Thanks in advance for any responses.
M.

unroot before updating and flash stock recovery

hoodoo_mc said:
Hi. My phone status:
PLK-L01
PLK-L01C432B180
EMUI version 3.1
5.0.2
rooted with TWRP boot recovery.
I'm looking for steps to update to android version 6.0.1 without losing all of my data, and keeping phone rooted and same recovery.
Is this something which is possible?
The only steps I have found is to how to replace stock recovery to update OTA.
I expect I would then need to root phone again afterwards.
Is this the recommended way of updating, or can I manually perform the update safely, and are there tried and tested instructions for this?
Many Thanks in advance for any responses.
M.
Click to expand...
Click to collapse
Completely unroot from settings menu in SuperSU app, Download latest firmware that is B380, use Huawei update extractor to extract stock recovery from update.app which you will get by extracting firmware, flash it in bootloader mode.
Copy update.app to dload folder in SD card, turn off your phone. Press and hold power, Vol up, vol down until a reboot. Let go of power after booting but keep other two pressed for five, six sec more.

muradulislam said:
Completely unroot from settings menu in SuperSU app, Download latest firmware that is B380, use Huawei update extractor to extract stock recovery from update.app which you will get by extracting firmware, flash it in bootloader mode.
Copy update.app to dload folder in SD card, turn off your phone. Press and hold power, Vol up, vol down until a reboot. Let go of power after booting but keep other two pressed for five, six sec more.
Click to expand...
Click to collapse
Hi. Many thanks for the prompt response.
That all seems straight forward, I just have one step I'd like you to confirm, if you would, and an additional question:
"flash it in bootloader mode"
So, after unrooting the phone, I will still have TWRP recovery available to use?
And, once I am at latest 6 firmware, do I need to use something like SRK Tools to reroot, or will SuperSU app still be installed and able to perform the re-root?
Thanks,
M.

hoodoo_mc said:
Hi. Many thanks for the prompt response.
That all seems straight forward, I just have one step I'd like you to confirm, if you would, and an additional question:
"flash it in bootloader mode"
So, after unrooting the phone, I will still have TWRP recovery available to use?
And, once I am at latest 6 firmware, do I need to use something like SRK Tools to reroot, or will SuperSU app still be installed and able to perform the re-root?
Thanks,
M.
Click to expand...
Click to collapse
After the unroot, the twrp recovery will still be there. You need to replace it with stock recovery by flashing it in bootloader mode, only then you can upgrade.
After upgrading to 6.0 you need to flash twrp again (in bootloader mode) and then flash SuperSU 2.62 (in twrp, for a root). Don't flash any other version.

muradulislam said:
After the unroot, the twrp recovery will still be there. You need to replace it with stock recovery by flashing it in bootloader mode, only then you can upgrade.
After upgrading to 6.0 you need to flash twrp again (in bootloader mode) and then flash SuperSU 2.62 (in twrp, for a root). Don't flash any other version.
Click to expand...
Click to collapse
Many Thanks.
I think I know what I'm doing now.
(famous last words)

hoodoo_mc said:
Many Thanks.
I think I know what I'm doing now.
(famous last words)
Click to expand...
Click to collapse
Don't worry mate, we will all be here

muradulislam said:
Don't worry mate, we will all be here
Click to expand...
Click to collapse
Thanks for the support.
OK, I'm going to leave it for today, and try again tomorrow.
Basically, I go through the steps to flash the stock recovery but can't complete this first step ;
By the way, there are 2 files in the update.app - recovery.img and recovery2.img. Does it matter which one I use?
And does the header file need to be in the same location, or can that be ignored for this step?
Anyhoo, after flashing via command line, and then do the final 'fastboot reboot' the phone just goes into a continuous boot loop until I interrupt by holding down all of the buttons.
Am I doing something wrong here?
I seem to remember I had this same issue when I first got the phone and was trying to get TWRP recovery installed using this method, and can't for the life of me remember how I got through it

@hoodoo_mc
you have to use recovery.img for the system recovery partition! >>> fastboot flash recovery recovery.img
recovery2.img is for the e-recovery partition only!
the header files could be ignored!
But you should flash the boot.img also! >>> fastboot flash boot boot.img >>> because SuperSU has made some changes to your boot partition!!!
to be absolutely save, you should flash the system.img to prevent other problems at last! >>> fastboot flash system system.img
If you use the B380 file to update, you will not loose your data! But it could be clever to backup your personal data and your files with the HUAWEI Backup app!
Good Luck!

non-toxic said:
@hoodoo_mc
you have to use recovery.img for the system recovery partition! >>> fastboot flash recovery recovery.img
recovery2.img is for the e-recovery partition only!
the header files could be ignored!
But you should flash the boot.img also! >>> fastboot flash boot boot.img >>> because SuperSU has made some changes to your boot partition!!!
to be absolutely save, you should flash the system.img to prevent other problems at last! >>> fastboot flash system.img system
If you use the B380 file to update, you will not loose your data! But it could be clever to backup your personal data and your files with the HUAWEI Backup app!
Good Luck!
Click to expand...
Click to collapse
Thank you so much guys @non-toxic and @Mansehra
Using your help I successfully upgraded to B380 and have my phone rooted again with TWRP recovery, and no data lost.
Cheers,
M.

hoodoo_mc said:
Thank you so much guys @non-toxic and @Mansehra
Using your help I successfully upgraded to B380 and have my phone rooted again with TWRP recovery, and no data lost.
Cheers,
M.
Click to expand...
Click to collapse
Enjoy your phone buddy... Don't forget to get greenify and titanium backup.
I love these two apps.

;
muradulislam said:
Don't forget to get greenify and titanium backup.
Click to expand...
Click to collapse
where is it for if you can use TWRP and HUAWEI Update together??
BTW: Had compared greenify with Lollipop and MM and for me greenify makes no sense!
Power consumption was the same as without! (on my device = 6%/24h! -GSM2 -no WLAN -no GPS -noBT -no DATA sync)

non-toxic said:
;
where is it for if you can use TWRP and HUAWEI Update together??
BTW: Had compared greenify with Lollipop and MM and for me greenify makes no sense!
Power consumption was the same as without! (6%/24h!)
Click to expand...
Click to collapse
For me it does make sense as I don't want Facebook and similar apps to run in the background nagging me with updates. I want them to run and update myself when I have time and tap on them. For battery, it does save some juice for me.
What's the comment about TWRP and Huawei update.
I am not sure what you mean by it.

ah, ok i see... it is neccesarry for YOU!
BtT. and thx bro:good:

Need stock Ascend XT recovery

Does anyone have a copy of the stock recovery? I'm trying to upgrade to b150 (both automated via the setting menu and manually by secret menu) but every time it tries to flash the firmware, the phone just reboots to TWRP and sits there.
Any help would be appreciated.

The directions you should be following have a copy of the stock recovery, don't they? If not, post a link to those directions.
Bill R said:
Does anyone have a copy of the stock recovery? I'm trying to upgrade to b150 (both automated via the setting menu and manually by secret menu) but every time it tries to flash the firmware, the phone just reboots to TWRP and sits there.
Any help would be appreciated.
Click to expand...
Click to collapse

divineBliss said:
The directions you should be following have a copy of the stock recovery, don't they? If not, post a link to those directions.
Click to expand...
Click to collapse
The first attempt was not following a guide. It was by going into the AT&T Software Update settings applet (my phone is on b140 and b150 was downloaded this way). That would start to load the update, reboot the phone into TWRP and then sit there. Subsequent booting into the OS would only re-attempt to install the update which would again reboot to TWRP.
After recovering my phone from a pre-update backup I tried, somewhat, following this method:
https://forum.xda-developers.com/android/development/guide-how-to-update-b130-to-b140-b150-t3555254
I was able to install the stock b140 image from my SD card but where it said TWRP would be gone, mine still had it. Attempting the secret menu would start the firmware update which would, again, boot to TWRP and sit there.

The stock ROMs in that guide thread should have stock recovery images. Just restore one of those stock recovery images using TWRP. Does your phone still have root?
Bill R said:
The first attempt was not following a guide. It was by going into the AT&T Software Update settings applet (my phone is on b140 and b150 was downloaded this way). That would start to load the update, reboot the phone into TWRP and then sit there. Subsequent booting into the OS would only re-attempt to install the update which would again reboot to TWRP.
After recovering my phone from a pre-update backup I tried, somewhat, following this method:
https://forum.xda-developers.com/android/development/guide-how-to-update-b130-to-b140-b150-t3555254
I was able to install the stock b140 image from my SD card but where it said TWRP would be gone, mine still had it. Attempting the secret menu would start the firmware update which would, again, boot to TWRP and sit there.
Click to expand...
Click to collapse

divineBliss said:
The stock ROMs in that guide thread should have stock recovery images. Just restore one of those stock recovery images using TWRP. Does your phone still have root?
Click to expand...
Click to collapse
I checked when you asked and surprisingly it does not. I'm surprised because I thought I re-installed it when I flashed the b140 ROM from that thread.
I'll try again this evening.

Also, if you followed the rooting guides, you should have your own copy of the stock recovery in your first TWRP backup.
Bill R said:
I checked when you asked and surprisingly it does not. I'm surprised because I thought I re-installed it when I flashed the b140 ROM from that thread.
I'll try again this evening.
Click to expand...
Click to collapse

Bill R said:
I checked when you asked and surprisingly it does not. I'm surprised because I thought I re-installed it when I flashed the b140 ROM from that thread.
I'll try again this evening.
Click to expand...
Click to collapse
The roms do NOT include Stock Recovery or any recovery for that matter ...Roms don't flash recovery (none that I have ever flashed anyway)
If you need B140 Stock recovery it's here B140.Stock.recovery.img
The Guide kind of assumes you just did the B130 to B140 update and you already have stock recovery installed
and yes if your phone was B140 when you rooted it you should already have your own stock backup of B140

I have to confess to a case of cranial flatulence. I had made a stock recovery backup. I'll proceed to banging my head on my desk now.
Back to business. So, after breaking my phone three times today, I finally got it back to the stock b140 (H1611C07B140) from the other thread and I'm ready to try the firmware upgrade again. I still have TWRP on it though so I'm wondering if I should reinstall the stock recovery first before trying the firmware upgrade. The other thread states that the b140-to-b150 firmware should overwrite the recovery but for me every time I do the firmware it boots to TWRP and sits there.

Bill R said:
I have to confess to a case of cranial flatulence. I had made a stock recovery backup. I'll proceed to banging my head on my desk now.
Back to business. So, after breaking my phone three times today, I finally got it back to the stock b140 (H1611C07B140) from the other thread and I'm ready to try the firmware upgrade again. I still have TWRP on it though so I'm wondering if I should reinstall the stock recovery first before trying the firmware upgrade. The other thread states that the b140-to-b150 firmware should overwrite the recovery but for me every time I do the firmware it boots to TWRP and sits there.
Click to expand...
Click to collapse
Yes I corrected the Guide
Flash stock recovery before doing the dload/ update.app flash
as soon as the firmware update is done boot to the bootloader
fastboot boot H1611.TWRP.New.img
then mount cust / system and data and flash the B150.Stock.rom
also flash Supersu and reboot

Thanks guys! I was finally able to get the b150 on with the additional instructions. Key was a couple of items:
Me confusing TWRP that I already had with H1611.TWRP.New.img.
Needing to go back to the stock recovery for the firmware upgrade
Discovering, by chance, that to get to fastboot mode with the power + volume down button it had to be connected to the PC via USB. It doesn't work if not connected.
Tomorrow I will get to where I've been wanting by installing the ROM to get rid of the AT&T bloat.
So thanks again!

Bill R said:
Thanks guys! I was finally able to get the b150 on with the additional instructions. Key was a couple of items:
Me confusing TWRP that I already had with H1611.TWRP.New.img.
Needing to go back to the stock recovery for the firmware upgrade
Discovering, by chance, that to get to fastboot mode with the power + volume down button it had to be connected to the PC via USB. It doesn't work if not connected.
Tomorrow I will get to where I've been wanting by installing the ROM to get rid of the AT&T bloat.
So thanks again!
Click to expand...
Click to collapse
It's pretty clear in the guide
When it's done it will reboot the phone so now boot to the bootloader with power + volume down while hooked to the PC via USB
Click to expand...
Click to collapse
Anyway congratulations
I hope you Enjoy the CleanRom