After updating my phone with an update I got about 1 hour ago my phone now reboots to recovery mode like a minute after booting up. my phone is a XT1526. How do i fix this?
What is your status code in the Bootloader?
{
"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"
}
To get into that start while holding down power + volume down (let go when it loads)
treypop said:
After updating my phone with an update I got about 1 hour ago my phone now reboots to recovery mode like a minute after booting up. my phone is a XT1526. How do i fix this?
Click to expand...
Click to collapse
Is this the Sprint prepaid XT1526? Is your bootloader unlocked?
xpmule said:
What is your status code in the Bootloader?
To get into that start while holding down power + volume down (let go when it loads)
Click to expand...
Click to collapse
Modified
JulesJam said:
Is this the Sprint prepaid XT1526? Is your bootloader unlocked?
Click to expand...
Click to collapse
Yes it is a Sprint prepaid XT1526 and yes the bootloader is unlocked.
treypop said:
Yes it is a Sprint prepaid XT1526 and yes the bootloader is unlocked.
Click to expand...
Click to collapse
Sounds like you weren't completely stock when you took the OTA, correct? Were you rooted or did you have a custom recovery installed when you took the OTA?
What version of the bootloader are you running?
JulesJam said:
Sounds like you weren't completely stock when you took the OTA, correct? Were you rooted or did you have a custom recovery installed when you took the OTA?
What version of the bootloader are you running?
Click to expand...
Click to collapse
I am rooted and I have TWRP. I don't know how to check version of the bootloader I'm using.
treypop said:
I am rooted and I have TWRP.
Click to expand...
Click to collapse
You are lucky you don't have a hard brick on your hands - NEVER take an OTA without being COMPLETELY STOCK!
Do you know how to get into the bootloader mode from recovery? If so, then get into the bootloader and tell me what version it is. Is it 80:0F?
JulesJam said:
You are lucky you don't have a hard brick on your hands - NEVER take an OTA without being COMPLETELY STOCK!
Do you know how to get into the bootloader mode from recovery? If so, then get into the bootloader and tell me what version it is. Is it 80:0F?
Click to expand...
Click to collapse
It is 80.0F
The OTA failed to install then my phone stopped rebooting in to recovery.
treypop said:
It is 80.0F
Click to expand...
Click to collapse
I was able to flash the Boost firmware to my Sprint XT1526 and it works fine. You could try flashing just the system partition and see if that works then you would need to reroot of course.
Or you could try installing all of the firmware and wiping cache/userdata, but you would lose everything on your phone then.
The boost firmware is here:
http://firmware.center/firmware/Motorola/Moto E (2nd gen-2015)/Stock/XT1526/
This is the latest version I could find:
XT1526_SURNIA_BOOST_5.1_LPI23.29-18-S.11_cid9_subsidy-DEFAULT_CFC.xml.zip
You would unzip it, get into bootloader mode and just flash the system files:
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
If that doesn't work, then you would need to return completely to stock by flashing the entire firmware, following these instructions that I just posted:
http://forum.xda-developers.com/showpost.php?p=66278442&postcount=3
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot oem config carrier spr
fastboot oem fb_mode_clear
Presumably this is the latest version of the firmware since it says my software is up to date when I hit System Update to try to check for updated firmware.
---------- Post added at 09:54 PM ---------- Previous post was at 09:45 PM ----------
treypop said:
The OTA failed to install then my phone stopped rebooting in to recovery.
Click to expand...
Click to collapse
But you can get into both the bootloader mode and into recovery correct? And is TWRP still installed? And did you make a nandroid ever?
JulesJam said:
You are lucky you don't have a hard brick on your hands - NEVER take an OTA without being COMPLETELY STOCK!
Do you know how to get into the bootloader mode from recovery? If so, then get into the bootloader and tell me what version it is. Is it 80:0F?
Click to expand...
Click to collapse
Agreed and he dodged the question LOL
Does it say "Modified" ? ..then there is your problem.
xpmule said:
Agreed and he dodged the question LOL
Does it say "Modified" ? ..then there is your problem.
Click to expand...
Click to collapse
He did answer later, he said he was rooted with custom recovery TWRP installed when he took the OTA. I think the only reason he didn't brick is because it was a small security update AFAIK. If it had been a more extensive update, I think he would have hard bricked.
He should be able to flash the boost XT1526 firmware and hopefully just the system, maybe he would need to do the kernel too but even so, he wouldn't lose everything on his device. The boost XT1526 firmware is working fine on my Sprint XT1526 using it on Ring Plus.
If he made a nandroid through TWRP he could try restoring that too through TWRP if it is still functional. If not, as long as he can get into bootloader mode and he could b/c he could tell me the version of the BL he was on, he can use the Boost XT1526 firmware to get a functional device, although he may lose his data/texts/photos.
JulesJam said:
He did answer later, he said he was rooted with custom recovery TWRP installed when he took the OTA. I think the only reason he didn't brick is because it was a small security update AFAIK. If it had been a more extensive update, I think he would have hard bricked.
He should be able to flash the boost XT1526 firmware and hopefully just the system, maybe he would need to do the kernel too but even so, he wouldn't lose everything on his device. The boost XT1526 firmware is working fine on my Sprint XT1526 using it on Ring Plus.
If he made a nandroid through TWRP he could try restoring that too through TWRP if it is still functional. If not, as long as he can get into bootloader mode and he could b/c he could tell me the version of the BL he was on, he can use the Boost XT1526 firmware to get a functional device, although he may lose his data/texts/photos.
Click to expand...
Click to collapse
I tried taking the 5.1 ota update on my sprint xt1526 after unlock/root/twrp on 5.0.2 just to see what would happen. The answer was, nothing. Install attempts just dumped me back to twrp with an install error.
Sent from my XT1526 using Tapatalk
dandrumheller said:
I tried taking the 5.1 ota update on my sprint xt1526 after unlock/root/twrp on 5.0.2 just to see what would happen. The answer was, nothing. Install attempts just dumped me back to twrp with an install error.
Click to expand...
Click to collapse
If the person who writes the OTA script puts the proper checks in the OTA, that is the outcome. If the person who writes the OTA script doesn't put the proper checks in the OTA, you can end up with a bricked device. If you have the firmware for your device, can get into bootloader mode and fastboot command is working, you can recover from a soft brick. We don't have the firmware for the Sprint XT1526, but luckily the devices work with the firmware for the Boost XT1526. Idk why there is no firmware for the Sprint XT1526.
I think the only time I have seen a hard brick from an OTA was when people had upgraded to a higher version of the bootloader and/or partition table, then downgraded and took the OTA. That is what happened to people with Moto X 2014's and it really sucks because there are no blankflash files to restore the bootloader. Since you can't downgrade the PT or BL but can downgrade everything else, in those cases, the OTA script only checked the system version but didn't check the bootloader/partition table version and instead of failing, it tried to patch the higher versions of bootloader.img and gpt.bin as if they were the lower versions, resulting in a hard brick. It was poor coding on Motorola's part that there weren't the proper checks in the OTA script.
In the US, Motorola honored the warranty on the Moto X 2014 Pure Editions that were hard bricked by the OTAs even if the bootloader was unlocked and would replace the device. But in Latin America, Motorola would not fix the devices under warranty so those unfortunate souls were SOL.
For the Moto X 2015 Pure Editions, Motorola has stated that they will not honor the warranty if you unlocked the bootloader since these are not considered developer devices. If the issue you are having is unrelated to unlocking the bootloader they have to by law honor the warranty and they have acknowledged that. But bricks from OTAs may be considered related to unlocking the bootloader since it is a software issue. And since the Moto E is not a developer device, if your bootloader is unlocked and you hard brick from an OTA, I doubt Motorola will honor the warranty.
You never know ahead of time whether the OTA script was coded properly to simply fail instead of bricking your device when you try to take an OTA and aren't completely stock. We only learn after people start bricking their devices and report that on the forums.
Because you can't know what is in the OTA script prior to taking it, it is BEST TO NEVER TRY TO TAKE AN OTA UNLESS YOU ARE COMPLETELY STOCK. In the case of OP, he has a soft brick but since he can get into bootloader mode and flash the Boost XT1526 firmware, he can recover from it. He may lose everything that was on his device though.
The Moto E is a low end device so if you brick it, it may not be a problem for you to buy another one. But the more expensive devices like the Moto X, it really sucks if you brick it and can't get it fixed under warranty. I personally don't see the point in risking taking an OTA while still rooted and with a custom recovery installed. Just flash back to stock and avoid the risk all together.
I've read that FlashFire could work to install the OTA ( http://www.howtogeek.com/192402/why-androids-ota-updates-remove-root-and-how-to-keep-it/ ). Would it work?
Related
Passing my P3 on to my wife and need to get it back to stock.
Got as far as loading the 3.2 firmware from sammobile using fastboot as Odin won't flash.
It recognises an OTA update but fails to download the update. I actually think that it fails to install but in any event it get stuck.
The kernel is still at 2.6.36.3 and baseband is the P7500 one.
I think that the kernel is located in the boot.img but it doesn't look like I am able to overwrite it with fastboot.
The bootloader seems to be replaced but I still have a unlocked bootloader.
Any ideas?
Thanks
GaryWS said:
Passing my P3 on to my wife and need to get it back to stock.
Got as far as loading the 3.2 firmware from sammobile using fastboot as Odin won't flash.
It recognises an OTA update but fails to download the update. I actually think that it fails to install but in any event it get stuck.
The kernel is still at 2.6.36.3 and baseband is the P7500 one.
I think that the kernel is located in the boot.img but it doesn't look like I am able to overwrite it with fastboot.
The bootloader seems to be replaced but I still have a unlocked bootloader.
Any ideas?
Thanks
Click to expand...
Click to collapse
You need to restore the stock recovery as well, ClockworkMod Recovery wont handle OTA updates.
Do fastboot flash recovery [recovery img] to reflash the stock recovery.
To re-lock the bootloader, try fastboot oem lock (not tried).
Note that it appears that even if relocking the bootloader, manufacturers have ways of knowing if the bootloader has been unlocked. However, since the purpose is to give it to someone else with possibly less technical skills (that does not require the feature), a locked bootloader is an added security.
pruano said:
You need to restore the stock recovery as well, ClockworkMod Recovery wont handle OTA updates.
Do fastboot flash recovery [recovery img] to reflash the stock recovery.
To re-lock the bootloader, try fastboot oem lock (not tried).
Note that it appears that even if relocking the bootloader, manufacturers have ways of knowing if the bootloader has been unlocked. However, since the purpose is to give it to someone else with possibly less technical skills (that does not require the feature), a locked bootloader is an added security.
Click to expand...
Click to collapse
thx pruano, the stock firmware contains a recovery image. This writes ok ... I also tried locking the bootloader - it locks ok but with the same results
It looks like the kernel might be the problem ...
GaryWS said:
thx pruano, the stock firmware contains a recovery image. This writes ok ... I also tried locking the bootloader - it locks ok but with the same results
It looks like the kernel might be the problem ...
Click to expand...
Click to collapse
Did you flashed ALL the imgs (boot.img, recovery.img and system.img) from the PDA archive?
You can always erase/format the partitions with fastboot erase/format [boot|recovery|system] before re-flashing the images... (important note: if you erase/format the boot partition, do not leave recovery without flashing a new boot img).
I would also restore the stock modem (you need the one from P7100BUKE2, as P7100BULB4 does not have it) - for this you will need Odin.
pruano said:
Did you flashed ALL the imgs (boot.img, recovery.img and system.img) from the PDA archive?
You can always erase/format the partitions with fastboot erase/format [boot|recovery|system] before re-flashing the images... (important note: if you erase/format the boot partition, do not leave recovery without flashing a new boot img).
I would also restore the stock modem (you need the one from P7100BUKE2, as P7100BULB4 does not have it) - for this you will need Odin.
Click to expand...
Click to collapse
Pruano, using fastboot, the erase command seems to work but format does not. Why do you say that I need Odin to flash the modem? I have done this with fastboot previously using "fastboot flash radio modem.img" ...
Edit: Pruano, you put me onto the right track. The modem was the problem. Once I got the original modem from P7100BUKE2 installed it all worked fine - even with unlocked bootloader.
and just for interest i had to use: "fastboot flash modem modem.img"
GaryWS said:
Why do you say that I need Odin to flash the modem? I have done this with fastboot previously using "fastboot flash radio modem.img" ...
Edit:and just for interest i had to use: "fastboot flash modem modem.img"
Click to expand...
Click to collapse
Did not know fastboot would recognize that partition, not on the docs.
Always learning.
GaryWS said:
Edit: Pruano, you put me onto the right track. The modem was the problem. Once I got the original modem from P7100BUKE2 installed it all worked fine - even with unlocked bootloader.
Click to expand...
Click to collapse
Yes, unlocked bootloaders do not interfere with OTAs
Regarding the modem, in truth it was a long shot, just a step to restore to pristine state.
The knowledge that the P7500 modem works best with custom ROMs and flashing it as a common procedure is relatively new, no wonder one had to guess that it would interfere with OTAs (as its not obvious, probably the OTA install does some kind of background safety check using the modem firmware as base); good to know for the future.
Okay, this is my story about my baby.
BEFORE UNLOCKING MY BOOTLOADER:
1) I had 4.4.2, then got the OTA to 4.4.4
2) Then got Invitation to Soak Test.... Got 5.0.2 and received two versions (forgot the versions)
3) Got kicked out of MFN for sharing info
4) Till received the 3rd and final 5.0.2 OTA (22.27.1 maybe)
Got tired with waiting with a buggy 5.0.2
One fine day, unlocked my bootloader.... the fun started
AFTER UNLOCKING MY BOOTLOADER:
1) Installed TWRP 2.8.6 and safely backed up my Stock ROM
2) Installed Custom ROMS one after another (CM12.1, PA, AOSP)
3) Used PA for a long time as it had really very less bugs
4) Stumbled upon Euphoria OS
5) Now Euphoria is my current OS
Okay, enough stories.....
My Question is.... How to revert to 4.4.4 in the safest way possible....?
I don't want to brick it.....
Seen many posts here in XDA but all are confusing.... having mixed user reviews.... Most hard bricked.... Others Happy
So, please help me.
http://forum.xda-developers.com/moto-e/general/video-tutorial-downgrade-moto-e-android-t3032738
follow this guide !
ChaTy said:
http://forum.xda-developers.com/moto-e/general/video-tutorial-downgrade-moto-e-android-t3032738
follow this guide !
Click to expand...
Click to collapse
I remember very well something mentioned about flashing gpt.bin, boot.img and something else.
I've read somewhere in this forum, that without flashing these, we can have our phone up and running KitKat 4.4.4.\
Also these files are responsible for the bricking process.... Can you please confirm?
Just don't flash gpt.bin and motoboot.bin, or you cuold just flash any KitKat ROM
emilio1625 said:
Just don't flash gpt.bin and motoboot.bin, or you cuold just flash any KitKat ROM
Click to expand...
Click to collapse
Didn't get you... What do you mean by flashing any KitKat ROM?
Download Full 4.4 xml Formatted ROM from filefactory and flash files one by one without gpt,bin and motoboot.bin
Adarsh1998 said:
Download Full 4.4 xml Formatted ROM from filefactory and flash files one by one without gpt,bin and motoboot.bin
Click to expand...
Click to collapse
Okay let me get this straight....
1) GPT is the partition info right? So flashing it will brick? Will it get flashed?
Or, will it show an error?
2) What about motoboot? What is that file? I know that boot.img is the kernel.
What has motoboot got to do with bricking?
Just being curious... please don't mind
You cannot skip any commands while downgrading from 5.0.2 to 4.4.4..if you do it correctly just as mentioned,then you will have kitkat running as before..
And btw you mentioned that most guys on xda here hardbricked while flashing kk image,which is false..most guys succeed and the ones who brick their phone post about it on xda so it looks like almost everyone is hardbricking their phone...
and just make sure that you are flashing 4.4.4 and not 4.4.2 image,ota'ing to .4 from .2 messes up the gpt/bootloader which leads to hardbrick
Sent from my condor using Tapatalk
Faiz Syed said:
You cannot skip any commands while downgrading from 5.0.2 to 4.4.4..if you do it correctly just as mentioned,then you will have kitkat running as before..
And btw you mentioned that most guys on xda here hardbricked while flashing kk image,which is false..most guys succeed and the ones who brick their phone post about it on xda so it looks like almost everyone is hardbricking their phone...
and just make sure that you are flashing 4.4.4 and not 4.4.2 image,ota'ing to .4 from .2 messes up the gpt/bootloader which leads to hardbrick
Sent from my condor using Tapatalk
Click to expand...
Click to collapse
I get you.... And now I am back to 4.4.4 with a huge problem
My boot loader is unlocked!!!
I try to enter the command fastboot oem lock begin
It says something like "(bootloader) ready to flash signed images"
I tried first only fastboot oem lock..... It said something like failed to verify system image signature!
So decided, to first type in
fastboot oem lock begin
fastboot flash gpt gpt.bin
fastboot flash motoboot motoboot.img
At this point both failed to flash just like before..... So I went to
fastboot flash logo logo.bin (Success)
Now when I type
fastboot flash system system.img_sparsechunk.0
It says, signature validation failed.
So what to do? How to relock my phone? Or id doesn't need relocking.
Just suggest me a way to remove that "Boot Loader Unlocked warning"
Rohitagni said:
I get you.... And now I am back to 4.4.4 with a huge problem
My boot loader is unlocked!!!
I try to enter the command fastboot oem lock begin
It says something like "(bootloader) ready to flash signed images"
I tried first only fastboot oem lock..... It said something like failed to verify system image signature!
So decided, to first type in
fastboot oem lock begin
fastboot flash gpt gpt.bin
fastboot flash motoboot motoboot.img
At this point both failed to flash just like before..... So I went to
fastboot flash logo logo.bin (Success)
Now when I type
fastboot flash system system.img_sparsechunk.0
It says, signature validation failed.
So what to do? How to relock my phone? Or id doesn't need relocking.
Just suggest me a way to remove that "Boot Loader Unlocked warning"
Click to expand...
Click to collapse
You can only relock bootloader after flashing the entire stock rom including the gpt ,bootloader and all..if you want to remove the bootloader unlock warning just follow this link,download one of the bootlogos you like and flash it in twrp.
http://forum.xda-developers.com/moto-e/themes-apps/boot-logo-t2836629
Sent from my condor using Tapatalk
Faiz Syed said:
You can only relock bootloader after flashing the entire stock rom including the gpt ,bootloader and all..if you want to remove the bootloader unlock warning just follow this link,download one of the bootlogos you like and flash it in twrp.
http://forum.xda-developers.com/moto-e/themes-apps/boot-logo-t2836629
Sent from my condor using Tapatalk
Click to expand...
Click to collapse
Can't I fully flash the ROM?
I mean.... There has to be a way.....
And also, I have to tell you I won't flash twrp right now.
UPDATE: I managed to flash a custom logo via fastboot..... Can't I flash the original one?
You should wiping the cache from fastboot and doing it again
Sent from my condor using Tapatalk
Faiz Syed said:
You should wiping the cache from fastboot and doing it again
Sent from my condor using Tapatalk
Click to expand...
Click to collapse
I figured it out bro...
U can't relock on .XML signed zip factory images.... Also, the logo.bin in the zips are absolutely stock, not modified to replace the warning boot loader unlocked message.
Hence, it was showing...
But I might as well stay unrooted.
Rohitagni said:
I figured it out bro...
U can't relock on .XML signed zip factory images.... Also, the logo.bin in the zips are absolutely stock, not modified to replace the warning boot loader unlocked message.
Hence, it was showing...
But I might as well stay unrooted.
Click to expand...
Click to collapse
Great then,as you were planning to lock i thought you were selling your phone thats why you wanted an oem lock......just flash another bootlogo and nobody will be able know unless they get into the bootloader[emoji6]
Sent from my condor using Tapatalk
I tried to flash a downgrade image to my moto e 2nd gen. Now Im stuck in bootloader and a warning message for unlocked bootloder. Ive tried to flash logo.bin, and other images aswell with no luck. It keeps asking me to install a valid signed images, I don't know where to find these images. Please help!
You need to do exactly what it's asking you to do - flash valid signed images. Which model do you have (XT152x)? Which region are you in? Which version were you downgrading from?
Just so you know, downgrading the stock ROM is very highly discouraged as it can cause bricking in certain circumstances. In particular, never try to downgrade the stock ROM when the bootloader is locked. You can try flashing back the upgraded images and seeing if your phone accepts them. Be aware that the signed images must match your model number and region.
squid2 said:
You need to do exactly what it's asking you to do - flash valid signed images. Which model do you have (XT152x)? Which region are you in? Which version were you downgrading from?
Just so you know, downgrading the stock ROM is very highly discouraged as it can cause bricking in certain circumstances. In particular, never try to downgrade the stock ROM when the bootloader is locked. You can try flashing back the upgraded images and seeing if your phone accepts them. Be aware that the signed images must match your model number and region.
Click to expand...
Click to collapse
Thanks for reply.
I don't have these images, where to get them? My model is xt1524reteuall, I'm in europe/sweden and I downgraded from stock Lollipop 5.0.2
I did unlock the bootloader via motorolas site.
pemhak said:
Thanks for reply.
I don't have these images, where to get them? My model is xt1524reteuall, I'm in europe/sweden and I downgraded from stock Lollipop 5.0.2
I did unlock the bootloader via motorolas site.
Click to expand...
Click to collapse
Hmm, so you went from a newer 5.0.2 build to an old 5.0.2 build? What were you downgrading to?
Go to this folder: https://mega.nz/#F!rMIhDLgR!oq5Cz_XbgZLEEysmqoYtcA
Navigate to Surnia ->5.0.2
Look for the file XT1524_RETEUALL_MOTOE2... (it's near the middle of the list)
Download and try flashing everything it in using fastboot.
squid2 said:
You need to do exactly what it's asking you to do - flash valid signed images. Which model do you have (XT152x)? Which region are you in? Which version were you downgrading from?
Just so you know, downgrading the stock ROM is very highly discouraged as it can cause bricking in certain circumstances. In particular, never try to downgrade the stock ROM when the bootloader is locked. You can try flashing back the upgraded images and seeing if your phone accepts them. Be aware that the signed images must match your model number and region.
Click to expand...
Click to collapse
Thanks for reply.
I don't have these images, where to get them? My model is xt1524reteuall, I'm in europe/sweden and I downgraded from stock Lollipop 5.0.2
I did unlock the bootloader via motorolas site.
I got my device back!! I did succeed to flash it with this rom "surnia_stock_5.0.2.zip" with TWRP. I did not have the patience to wait at the Motorola logo when booting, I have to wait 2-3 min and 2-3 min for services to start. for the device to boot. But now it doesn't register any sim card when at desktop?!?
squid2 said:
Hmm, so you went from a newer 5.0.2 build to an old 5.0.2 build? What were you downgrading to?
Go to this folder:
Navigate to Surnia ->5.0.2
Look for the file XT1524_RETEUALL_MOTOE2... (it's near the middle of the list)
Download and try flashing everything it in using fastboot.
Click to expand...
Click to collapse
I was downgrading to kitkat 4.4.4 due to poor battery in lollipop 5.0.2. I'm downloading a xt1524reteuall rom right now but ir is going slowly.
pemhak said:
I was downgrading to kitkat 4.4.4 due to poor battery in lollipop 5.0.2. I'm downloading a xt1524reteuall rom right now but ir is going slowly.
Click to expand...
Click to collapse
Oh, you must have flashed something really wrong then. There are no 4.4.4 ROMs for this device. You would have flashed something totally incompatible and highly risky if you flashed 4.4.4 from somewhere. That may have wrecked your modem software too. Download and flash the proper XT1524-specific software with the correct modem. If you are unhappy with the performance of the stock ROM, you can flash scritch007's CM12.1.
squid2 said:
Oh, you must have flashed something really wrong then. There are no 4.4.4 ROMs for this device. You would have flashed something totally incompatible and highly risky if you flashed 4.4.4 from somewhere. That may have wrecked your modem software too. Download and flash the proper XT1524-specific software with the correct modem. If you are unhappy with the performance of the stock ROM, you can flash scritch007's CM12.1.
Click to expand...
Click to collapse
Ok, thanks. I will wait for download to complete and flash that image.
pemhak said:
Ok, thanks. I will wait for download to complete and flash that image.
Click to expand...
Click to collapse
Hi! Did you solve your problem? I'm kind of stuck on same problem and with no working solution yet.
EDIT: I tried the @squid2 with no success. Maybe I will send the phone to waranty....
Noeljunior said:
Hi! Did you solve your problem? I'm kind of stuck on same problem and with no working solution yet.
EDIT: I tried the @squid2 with no success. Maybe I will send the phone to waranty....
Click to expand...
Click to collapse
I did solve the problem with these steps.
1. Find and download the files for your region.
2. Unzip files to a folder with fastboot and adb.
3. Create stock.bat with these commands and run stock.bat within the same folder as above files.
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot oem config carrier vzw
fastboot oem fb_mode_clear
fastboot reboot
(4. I needed to reunlock my Moto E 2nd Gen at Motorolas site, because i did relock it.)
5. Get into bootloader menu and flash this TWRP image (i can email it to you) within the same folder and flash it with fastboot.
6. Restart phone. Wait 2-3 minutes so it boots into android.
7. Hope I made it clear enough to follow the instructions, if you got questions please reply and I try to answer them. Sorry for my poor english.
pemhak said:
I did solve the problem with these steps.
1. Find and download the files for your region.
2. Unzip files to a folder with fastboot and adb.
3. Create stock.bat with these commands and run stock.bat within the same folder as above files.
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot oem config carrier vzw
fastboot oem fb_mode_clear
fastboot reboot
(4. I needed to reunlock my Moto E 2nd Gen at Motorolas site, because i did relock it.)
5. Get into bootloader menu and flash this TWRP image (i can email it to you) within the same folder and flash it with fastboot.
6. Restart phone. Wait 2-3 minutes so it boots into android.
7. Hope I made it clear enough to follow the instructions, if you got questions please reply and I try to answer them. Sorry for my poor english.
Click to expand...
Click to collapse
And I'm back with my Moto E! Thank you! I wasn't doing some of those commands and with all those commands it works! Thank you!
Just flashed the the new images from MHC19I but left my recovery and userdata partition untouched. Before booting into system i booting into TWRP and was greeted with the enter password to decrypt the data partition.
The new Twrp is out now 3.0.0-1 HERE
Let me know if this helps guys and gals.
jerflash said:
Just flashed the the new images from MHC19I but left my recovery and userdata partition untouched. Before booting into system i booting into TWRP and was greeted with the enter password to decrypt the data partition. This never happened to me before so it must be something in the new bootloader image or boot image that is causing this.
Does anyone else see this? I was going to test downgrading the bootloader later on today to see if the block is gone but it looks like the "default password" for encryption may have changed.
Let me know guys.
Click to expand...
Click to collapse
New TWRP test builds already out there that take care of the issue.
rebretz000 said:
New TWRP test builds already out there that take care of the issue.
Click to expand...
Click to collapse
yes i see that and i am going to flash it now. i had to read through that whole thread though. i will post it above for others.
Thanks. The TWRP fix did the trick for me. To summarize for others, these are the steps I took after d/ling the new factory image:
adb reboot bootloader
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-03.51.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-03.61.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
fastboot reboot-bootloader
fastboot flash recovery twrp-test1-3.0.0-0-angler.img
fastboot reboot-bootloader
boot into TWRP -> Flash SuperSU
Reboot System -> Wait for cache to build
(optional) Open ElementalX app and install
Profit
johnny2678 said:
Thanks. The TWRP fix did the trick for me. To summarize for others, these are the steps I took after d/ling the new factory image:
adb reboot bootloader
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-03.51.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-03.61.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
fastboot reboot-bootloader
fastboot flash recovery twrp-test1-3.0.0-0-angler.img
fastboot reboot-bootloader
boot into TWRP -> Flash SuperSU
Reboot System -> Wait for cache to build
(optional) Open ElementalX app and install
Profit
Click to expand...
Click to collapse
I noticed that after flashing MHC19I (and N preview) I lost TWRP every time I booted into the system. Have you seen this? Over on another MHC19I thread, someone suggested renaming 'recovery-from-boot.p' from TWRP to avoid this.
This did happen to me with a broken system though, so maybe there were some checks triggered that made the system flash stock recovery again.
Awesome test build! It works like a charm
havanahjoe said:
I noticed that after flashing MHC19I (and N preview) I lost TWRP every time I booted into the system. Have you seen this? Over on another MHC19I thread, someone suggested renaming 'recovery-from-boot.p' from TWRP to avoid this.
This did happen to me with a broken system though, so maybe there were some checks triggered that made the system flash stock recovery again.
Click to expand...
Click to collapse
this happens because you booted into Android before flashing SuperSu or disabling the recovery-from-boot
when you flash the last item, in my case it was vendor.img, i clicked volume down on my phone, and went into recovery. i then selected SuperSu2.68 and flashed that. Then rebooted.
chaco81 said:
this happens because you booted into Android before flashing SuperSu
Click to expand...
Click to collapse
That would explain it. I didn't know SuperSu took care of this. Thank you
Is SuperSU 2.68 systemless as well? I'm on 2.67 still because I haven't seen any confirmation otherwise. Thanks!
Yes. I use the same version.
allen099 said:
Is SuperSU 2.68 systemless as well? I'm on 2.67 still because I haven't seen any confirmation otherwise. Thanks!
Click to expand...
Click to collapse
Just a quick question. Why does everyone suggest fastboot flashing with IMG files one by one? Why not just use the batch file included in the main Nexus image download? Assuming that most would want to keep apps and data intact, you simply need to remove the "-w" from the batch file as I understand it. In doing so, you keep all data/apps/SD card info, correct?
floepie said:
Just a quick question. Why does everyone suggest fastboot flashing with IMG files one by one? Why not just use the batch file included in the main Nexus image download? Assuming that most would want to keep apps and data intact, you simply need to remove the "-w" from the batch file as I understand it. In doing so, you keep all data/apps/SD card info, correct?
Click to expand...
Click to collapse
I was also wondering the same
Sent from my Nexus 6P using Tapatalk
floepie said:
Just a quick question. Why does everyone suggest fastboot flashing with IMG files one by one? Why not just use the batch file included in the main Nexus image download? Assuming that most would want to keep apps and data intact, you simply need to remove the "-w" from the batch file as I understand it. In doing so, you keep all data/apps/SD card info, correct?
Click to expand...
Click to collapse
mickyw1980 said:
I was also wondering the same
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
If you do that it will flash all of the images.... That includes the userdata.img which also wipes your device. This is something most people updating do not want. Plus it just gives you more control.
Sent from my Nexus 6P using Tapatalk
johnny2678 said:
Thanks. The TWRP fix did the trick for me. To summarize for others, these are the steps I took after d/ling the new factory image:
adb reboot bootloader
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-03.51.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-03.61.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
fastboot reboot-bootloader
fastboot flash recovery twrp-test1-3.0.0-0-angler.img
fastboot reboot-bootloader
boot into TWRP -> Flash SuperSU
Reboot System -> Wait for cache to build
(optional) Open ElementalX app and install
Profit
Click to expand...
Click to collapse
This allows you to keep encryption?
jerflash said:
If you do that it will flash all of the images.... That includes the userdata.img which also wipes your device. This is something most people updating do not want. Plus it just gives you more control.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
No, it doesn't. If you remove the -w from the batch file, it won't overwrite your userdata. That's common knowledge here.
floepie said:
No, it doesn't. If you remove the -w from the batch file, it won't overwrite your userdata. That's common knowledge here.
Click to expand...
Click to collapse
That may be true but if you don't know to do that it will wipe everything. Just always been safer to do it individually.
Sent from my Nexus 6P using Tapatalk
gts24 said:
This allows you to keep encryption?
Click to expand...
Click to collapse
Looks like it does. Is there another way to tell?
{
"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"
}
Sent from my Nexus 6P using Tapatalk
I always flash system, boot, vendor through fastboot. Sometimes I also update the bootloader and the radio if there is a newer version available. All other IMG files are not necessary. It´s true that flashing the stuff one by one gives you more control ( and a dirty flash is also great for lazy guys like me who want to keep all their Apps, settings etc. ).
johnny2678 said:
Looks like it does. Is there another way to tell?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I just followed your flow chart , worked here as far as I can tell as well. (proper thanks button clicked )
When I flashed this morning and entered TWRP recovery it must of tripped something as the yellow "cannot check for corruption" warning changed to a red "Your device is corrupt" message. It still only shows for a few seconds before booting like normal. I can't really try anything until I get home, but will flashing the patched TWRP and booting into it be enough to change that back to the old yellow warning? Or do I need to reflash the system/boot packages again?
Hello, the question is very simple: does anyone who has installed the rom 26S in x722 have been able to then unlock the bootloader or install another rom?
We know that in the rom 20S with the one that comes from the factory you can unlock the bootloader and install twrp, we know you can upgrade to the 26S, we know that there are people who have upgraded to 26S, but no one who has upgraded to 26S has Commented that it was able to install another rom then, only comment that the bootloader is blocked with the 26S.
All those who have updated to 26S you have to stay with her because you can not change?
Well if someone has succeeded, it would be nice to say how he did it.
Greetings.
*** TODAY, THE ONLY WAY TO LEAVE OFFICIAL 26S IS TO INSTALL THE ROM 01D, THAT UNLOCK THE BOOTLOADER AND ALLOWS US TO INSTALL ANY OTHER ROM. ***
My phone came with 20s shoprom and the bootloader is unlocked. I checked. So I will wait for a twrp before I update to 26s. Is the x720 twrp compatible with our phone to flash?
I have not tried it, but according to the comments of this and other forums, with the 20S factory version it is easy to unlock by ADB, and it allows you to install twrp from x720 which by comment works fine.
The problem is that if you upgrade to version 26S, the bootloader can no longer be unlocked and as the recovery is changed to the stock, you can not reinstall Twrp or any other ROM (I suppose you can install another official ROM, but The only one that exists is the 26S, there is not even the 20S with which it comes from the factory)
In short, if you upgrade to version 26S, the bootloader is blocked, and you can not reinstall twrp or anything that is not official, and for the moment there is nothing more.
Greetings.
It's not like there are so many ROMs
The bootloader changes in 26s and it makes device bootloader locked.
I would suggest to stay on 20s until a workaround is available for unlocking bootloader also on 26s.
I guess anyone who already has the 26S version will have to wait. But for the one who has a hard-brick with the blocked bootloader should try to get a copy of bootloader of 20S and with some flash tool try to change it.
Also it could be that with a flash tool install the rom 26S and before restarting change the bootloader by the 20S version. In some terminals, this has worked.
Greetings.
I have a nandroid copy of 20S Shop ROM boot. I made nandroid copies of all major partitions (the same ones that have stock ROM) before installing 26S Stock. I used the TWRP of the X722 version to install the ROM. Everything worked. Then I installed the GApps and gave it some error and rebooted. Now I have the bootloader locked, it does not go into recovery mode and it does not start the system. Totally brick.
And the worst: QFIL does not work here. I have tested on different versions, different computers, different drivers and nothing. He always gives this error:
Code:
15:47:28: ERROR: function: rx_data:247 Error occurred while reading from COM port
15:47:28: ERROR: function: sahara_main:924 Sahara protocol error
15:47:28: ERROR: function: main:303 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Fail:Process fail
And Windows emits the disconnected device sound.
Here is a detailed log using the command to send the FireHose through the CMD:
Log.txt
Does anyone have any idea what this error is? And how to solve it?
Hello DK Boneco, I can not tell you how to solve it, but I can give you an idea.
The fault is because the bootloader is locked.
Look for another tool that does not use qfil and that allows you to flash with locked bootloader. Surely there must be some.
And by the way, if you have a copy of the complete 20S version, I would try to flash this one.
Greetings.
DK Boneco said:
I used the TWRP of the X722 version to install the ROM.
Click to expand...
Click to collapse
Can you please post a link
ziaba said:
Can you please post a link
Click to expand...
Click to collapse
Hi, this thread talks about "unlock bootloader with rom 26S" not from twrp.
Anyway there is no twrp for x722 but it works for x720.
Query in twrp threads or create one in section x722 for more information.
Greetings.
F.J.V said:
The fault is because the bootloader is locked.
Click to expand...
Click to collapse
A friend who has the same smartphone with unlocked bootloader did the same process and the exact same error happened.
F.J.V said:
Look for another tool that does not use qfil and that allows you to flash with locked bootloader.
Click to expand...
Click to collapse
Do you know another method? All that I looked for, ending up using the background QFIL to get the job done.
---------- Post added at 12:34 AM ---------- Previous post was at 12:33 AM ----------
ziaba said:
Can you please post a link
Click to expand...
Click to collapse
Here's the link: https://twrp.me/devices/leecolepro3.html
DK Boneco said:
A friend who has the same smartphone with unlocked bootloader did the same process and the exact same error happened.
Click to expand...
Click to collapse
The hard brick came from gapps on top of 26s. Never flash Gapps on top of stock ROMs. Never.
The 26s firmware locked bootloader blocking the CRITICAL partition, so you must unlock it first, then unlock the bootloader.
Try this sequence, in fastboot mode:
fastboot devices
fastboot device info
- when in fastboot device info, check CRITICAL partition unlock status. if FALSE, then try
fastboot flashing unlock_critical
fastboot device info
- now CRITICAL partition unlock status should be TRUE, try unlocking
fastboot oem unlock-go
- if you succeded unlocking, check status with
fastboot device info
fastboot reboot or fastboot flash recovery twrp.img
- if you still cannot unlock, you could try flashing a different emmc_appsboot.mbn file. You can extract emmc_appsboot.mbn from x722 20s firmware or from x720 firmware.
In fastboot mode
fastboot flash aboot emmc_appsboot.mbn
- if flashing is successful
fastboot reboot
adb devices
adb reboot bootloader
fastboot oem unlock-go
- if unlock is succesful
fastboot device info
fastboot reboot or fastboot flash recovery twrp.img
Flounderist said:
The hard brick came from gapps on top of 26s. Never flash Gapps on top of stock ROMs. Never.
The 26s firmware locked bootloader blocking the CRITICAL partition, so you must unlock it first, then unlock the bootloader.
Click to expand...
Click to collapse
I tried this and several other ways to try to unlock the bootloader. I could not find a way. It does not allow flash any partition.
{
"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"
}
DK Boneco said:
I tried this and several other ways to try to unlock the bootloader. I could not find a way. It does not allow flash any partition.
Click to expand...
Click to collapse
Would you try
fastboot format userdata
fastboot format data
fastboot reboot bootloader
fastboot device info
Check if (bootloader) is_allow_unlock: changed from 0 to 1. If it is still on 0 try
fastboot erase userdata
fastboot erase data
fastboot reboot bootloader
fastboot device info
If still on 0....try also formatting or erasing cache.
It seems that kernel does not allow any tampering attempt if value is =0, hence critical partitions are locked.
Hello DK Boneco, the error is reading the COM port.
Is the phone charged?
It appears that the phone is disconnected or exits EDL mode.
It may be a driver problem, or some phones exit EDL mode within a few seconds if the flash has not started.
Try not to take more than 4 or 5 seconds from the time the phone enters EDL until the flash starts.
You can also try the flash with MiFlash Xiaomi, say that can flash any modern phone and is quite effective, look for a manual and test.
Greetings.
DK Boneco said:
And Windows emits the disconnected device sound.
Click to expand...
Click to collapse
You may need to install drivers to your pc to recognize your, thats why it emits the disconnected device sound.
Hello DK Boneco, try these steps:
1. Method published with flashone2.0 and zip qfil.
2. When the fault appears, disconnect the USB phone.
3. Reconnect the phone in EDL mode (vol + and vol- and connect to USB)
4. Without losing time, in flashone2.0 press the "Refresh" button, select the COM port, press the "Flash" button and then "NO" (do not unzip it again).
From connecting the phone to USB until you press the "NO" button as fast as possible, without wasting time.
I hope it serves as something, what I see is that the phone goes out of EDL mode and that's why it fails.
Greetings.
To be sure to stay in EDL mode, you can type
fastboot reboot edl or fastboot reboot-edl
Be sure to install Qualcomm driver properly on PC.
Anyway it seems that QFIL is missing for X722 device. I assume that this device lacked a lot of development due to company failure, or it was developed exclusively for CN market (no google play support and locked bootloader from kernel to avoid any hacking activity).
Qfil is a Qualcomm tool for any Qualcomm smartphone, no matter brand or development.
Qfil should work for any phone with chip qualcomm, another thing is that the phone requires some specific configuration, or that the zip that is intended to flash is not correct.
Greetings.