I unrooted and relocked the bootloader to install Lollipop. Succeeded and installed the soak test version.
Here's where I screwed up. I tried downgrading to 4.4.4 using the factory firmware and now I'm unable to mount any partition or install any boot image. Every time I try installing an img via fastboot I get a "Prefetch validation failed". When I start the phone I get "Invalid boot image header".
What works:
Recovery (TWRP) - Can't install anything because cache, data, system cannot be mounted.
Followed these steps:
http://forum.xda-developers.com/moto-e/general/video-tutorial-downgrade-moto-e-android-t3032738
I was able to install TWRP. But these are not mounting - cache, system, data.
I was able to flash gpt.bin.
Can someone please give links to 5.0.2 firmware? Why am I not able to flash the 4.4.4 firmware?
how did you install lollipop ..through stock recov or twrp.
Did it from recovery via adb sideload.
I'm able to flash all the images except: motoboot.img and gpt.bin.
I have a running android system but the SIM card is not getting detected at all.
Shredder333 said:
Did it from recovery via adb sideload.
I'm able to flash all the images except: motoboot.img and gpt.bin.
I have a running android system but the SIM card is not getting detected at all.
Click to expand...
Click to collapse
I think you should clean install Soak lollipop update from ADB sideload again... Maybe it will help...
Or try Custom Roms! like cm12 or PAC... But remember, Do flash a rom of lollipop... and forget kitkat for now!1!!!
Regards
Andy
Shredder333 said:
Did it from recovery via adb sideload.
I'm able to flash all the images except: motoboot.img and gpt.bin.
I have a running android system but the SIM card is not getting detected at all.
Click to expand...
Click to collapse
motoboot.img and gpt.bin are not supposed to b flashed..................as for ur SIM, maybe u flashed the wrong firmware..............
I tried installing the lollipop firmware through ADB but it aborts after verification. I've tried other ROMs, everything works fine except that the SIM doesn't detect at all.
System, modem, recovery, boot all get flashed fine. Except motoboot and gpt.bin which fail to flash saying "preflash validation failure". Is the SIM not detecting because these 2 images fail to get flashed?
moto r hard brick
heloo guys i have MOTO E i updates it to LOLIPOP.. wch ws soak version realized..!!
after a time downgraded it 4.4.2 wia fastboot going in moto e bootloader menu..!!
it ws successful..!! afterwards i updated it to 4.4.4 from OTA .. and while updateing phn went into recovery, and turn off!!
n it dint start again ..!! and now it does not turn onn.. the led blinks when i connect it to charger..!!
i also tried the BLANKFLASH way.. but the files given are for MOTO G..!!! my cell was DEAD ..!!
so i went to the SERVICE CENTER and told them that my cell is in WARENNTY and it does not turn on since i updatedet to 4.4.4
they ACCEPTED and they are going to change my MOTHERBOARD in FREE of cost..!!!
SO THOSE WHO HAVE BRICKED THEIR MOTO PLZ RUN TO SREVICE CENTER ASAP.!!!!
HARD LUCK...!!!!
Shredder333 said:
I tried installing the lollipop firmware through ADB but it aborts after verification. I've tried other ROMs, everything works fine except that the SIM doesn't detect at all.
System, modem, recovery, boot all get flashed fine. Except motoboot and gpt.bin which fail to flash saying "preflash validation failure". Is the SIM not detecting because these 2 images fail to get flashed?
Click to expand...
Click to collapse
sim card not working...seems like a efs partition problem.do u have a back up of your efs partition.
Related
I'm not new to flashing custom roms and rooting Android devices, so I don't think I'm a noob at this. I decided to help my friend unleash the power in his HTC One S by rooting it and giving it a custom recovery, I went through the right processes, Unlocked the phone's bootloader, and flashed the superuser zip and the twrp image, as it didn't seem like a clockworkmod image was compatible with the phone.
I then booted into recovery, wiped/factory reset and then flashed the latest CM11 nightly and got an error in TWRP recovery about the bootloader not been interoperable something like "
Code:
2.15==2.13"
in the error message , fine, I rebooted back into fastboot and checked the HBOOT Version and found out the phone was on HBOOT 1.13 and I think CM11 requires the most recent HBOOT version to work on HTC devices. The phone has got S-Off though.
Now I'm stuck in a bootloop cause I already wiped the OS in TWRP, I have everything in place, the right drivers and all that, I also tried re-installing the stock rom by downloading an HTC One S's RUU file but the device wasn't recognized at all by the RUU installer, I also tried to flash a stock 4.0.x rom as a zip file, no Joy. Now the phone is stuck at the point where it doesn't have an OS to boot into at all.
I'll really appreciate the community's support helping me fix this issue.
geek-x said:
I'm not new to flashing custom roms and rooting Android devices, so I don't think I'm a noob at this. I decided to help my friend unleash the power in his HTC One S by rooting it and giving it a custom recovery, I went through the right processes, Unlocked the phone's bootloader, and flashed the superuser zip and the twrp image, as it didn't seem like a clockworkmod image was compatible with the phone.
I then booted into recovery, wiped/factory reset and then flashed the latest CM11 nightly and got an error in TWRP recovery about the bootloader not been interoperable something like "
Code:
2.15==2.13"
in the error message , fine, I rebooted back into fastboot and checked the HBOOT Version and found out the phone was on HBOOT 1.13 and I think CM11 requires the most recent HBOOT version to work on HTC devices. The phone has got S-Off though.
Now I'm stuck in a bootloop cause I already wiped the OS in TWRP, I have everything in place, the right drivers and all that, I also tried re-installing the stock rom by downloading an HTC One S's RUU file but the device wasn't recognized at all by the RUU installer, I also tried to flash a stock 4.0.x rom as a zip file, no Joy. Now the phone is stuck at the point where it doesn't have an OS to boot into at all.
I'll really appreciate the community's support helping me fix this issue.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2322755
You need that. Luckily you're already S-Off, so shouldn't be terrible to get going again. Just update the firmware, reinstall TWRP and re-flash CM11. Should be good to go afterwards.
es0tericcha0s said:
http://forum.xda-developers.com/showthread.php?t=2322755
You need that. Luckily you're already S-Off, so shouldn't be terrible to get going again. Just update the firmware, reinstall TWRP and re-flash CM11. Should be good to go afterwards.
Click to expand...
Click to collapse
Thank you so much for the reply, does it matter that I don't have an OS to boot into as I already wiped and factory reset the phone for installation of a new rom.?
geek-x said:
Thank you so much for the reply, does it matter that I don't have an OS to boot into as I already wiped and factory reset the phone for installation of a new rom.?
Click to expand...
Click to collapse
Nah, shouldn't. The firmware we're referring to here is independent of the OS.
es0tericcha0s said:
Nah, shouldn't. The firmware we're referring to here is independent of the OS.
Click to expand...
Click to collapse
At the end of the guide, should help fix the issue, there's a part where I'm supposed to install the new CM kernel from the CM .zip package, how do I flash a kernel from Fastboot?
geek-x said:
At the end of the guide, should help fix the issue, there's a part where I'm supposed to install the new CM kernel from the CM .zip package, how do I flash a kernel from Fastboot?
Click to expand...
Click to collapse
Since you are S-Off, needing fastboot to install the boot.img is not necessary. It will install through recovery.
But, for future reference, you would boot to the bootloader screen, select fastboot, then assuming you have fastboot set up on the PC and the boot.img in the directory of said fastboot, you would use this command:
fastboot flash boot boot.img
then
fastboot reboot
es0tericcha0s said:
Since you are S-Off, needing fastboot to install the boot.img is not necessary. It will install through recovery.
But, for future reference, you would boot to the bootloader screen, select fastboot, then assuming you have fastboot set up on the PC and the boot.img in the directory of said fastboot, you would use this command:
fastboot flash boot boot.img
then
fastboot reboot
Click to expand...
Click to collapse
I tried flashing the firmware.zip file from the thread but I got a FAILED: (remote: not allowed) error in command prompt at the end of the process, what did I do wrong?
UPDATE: I was able to update the bootloader version successfully, as I forgot the part where I was to boot into RUU mode with fastboot oem rebootRUU and worked perfectly the second time.
I rebooted and found out the boot loader was updated to HBoot 2.15, and I also updated twrp to the latest S4 version but now in recovery I get errors about twrp been unable to mount the /data partition. Do I flash another recovery image?
UPDATE:
Thank you so much es0tericcha0s, I really appreciate the support, I got the /data mount issue fixed finally. I just had to flash an older twrp recovery image and then reflashed the new one in fastboot and I could then flash CM successfully.
I can't believe I finally unbricked this phone, its been bricked since Sunday. Once again, es0tericcha0s, Thank you!
geek-x said:
UPDATE: I was able to update the bootloader version successfully, as I forgot the part where I was to boot into RUU mode with fastboot oem rebootRUU and worked perfectly the second time.
I rebooted and found out the boot loader was updated to HBoot 2.15, and I also updated twrp to the latest S4 version but now in recovery I get errors about twrp been unable to mount the /data partition. Do I flash another recovery image?
Click to expand...
Click to collapse
You might need to RUU back then. If you have issues with the RUU exe, then you can extract the rom.zip and install it like you did the firmware. There are quite a few tutorials on how to extract it, or there might already be a version floating around for your phone.
Hi, my brothers xt 1022 its bricked on initial looping.
The original bootloader works, i try hard reset, wipe data, but doesnt work.
I got unlock bootloader, because debug is disable, i dont be twrp or cwm or stock recovery works.
In the last time i try most tutorials for recovery with fasboot, .bat files, but doesnt worked.
i try send stock recovery in the update via sideload.
In this mode adb devices show the xt but returns error closed on adb usb.
I try kill-server but error closed persist
The sideload of zip rom goes to 100% but xt returns error to update.
Please help me
updating
in fastboot in try to twrp = incomplete boot image for booting.
how do i give the backup files via sideload, to try move the files and try recovery like a backup via side load, its possible?
update 2
I edit the adb_usb.ini and include id of device in recovery update adb and in fastboot. with the 2 adress include the name in managment device change to faastboot condor S. But still dont work the install twrp etc
Help
Hi, with fastboot these comands i have sucsses
fastboot flash partition gpt.bin
version downgraded for primary gpt
fastboot flash motoboot motoboot.img
downgraded for tz
fastboot flash boot boot.img
downgraded for boot
the outhers comand for flash doesnt work
Please help me with unbricked theses paper holder moto e
In android device info
show my device
condor_niibr_ds-user 4.4.4 KXC21.5-44 2 release-keys
kxc21.5-44
Anybody show me one rom .zip , to sideload from stock recovery. Or this rom to reinstal via sideload
Thanks
Hey guys i tried to install latest Android version on my Surnia (XT1527) but i bricked it, only i can get into bootloader (the bootloader is locked) my pc can't recognize the COM Qualcomm port (i'm trying hard to use QFIL), so i was thinking on use another moto E XT1527 to retrieve a full image of the system to flash it on my device, but i don't know how to do that or what i need for that, trying to flash some stock firmwares keep giving an error (preflash validation failed).
Can you help me with that??
QFIL never worked for me.
Check https://forum.xda-developers.com/showthread.php?t=2759495.
Forget the adb part, just check if fastboot recognizes your device and try the steps.
I think you can also install custom recovery without unlocking the bootloader. Ones that is done you can try to install your custom rom.
rk92 said:
QFIL never worked for me.
Check https://forum.xda-developers.com/showthread.php?t=2759495.
Forget the adb part, just check if fastboot recognizes your device and try the steps.
I think you can also install custom recovery without unlocking the bootloader. Ones that is done you can try to install your custom rom.
Click to expand...
Click to collapse
Did you solve the 'preflash validation error'?? mine keeps giving that error and i tried all the versions of the ROM, all i need is to install a custom recovery without unlocked bootloader, can you help me explaining what have you done? thanks
With locked bootloader you cannot flash custom recovery(even boot).
You can try to flash the newest stock rom without commands:
fastboot flash bootloader...
fastboot flash partition...
So it's my second attempt to flash lineage os (unofficial) on my Realme XT. First time I was a little careless and bricked my device (had to go to the service center for that). Second time I took all the precautions still I'm having almost same problem, but this time its not yet bricked.
I unlocked the bootloader. It went fine.
Flashed unofficial TWRP and booted back to stock os.
When I tried booting to TWRP again I realized it was reset back to stock recovery. So I flashed it again and made backup of all the partitions (stupidly on internal storage). Booted back to system to check that backup is showing on internal storage. Again booted to TWRP and wiped everything except internal storage, flashed lineage and gapps. Wiped dalvik/cache rebooted to system. I was greeted with system partition destroyed error screen.
I flashed vbmeta.img via fastboot, the error was gone but still i was not able to boot to lineage. (I directly flashed vbmeta.img via fastboot. Didn't use the "fastboot --disable-verity --disable-verification" command.)
Now I'm having a different kind of problem.
I can boot into TWRP but I can not boot to system (lineage os). Can't go back to stock as well because the internal storage is encrypted i think (all the folders have random names). After flashing vbmeta.img (via fastboot) now I am not able to connect my phone via fastboot.
Without fastboot TWRP backup is the only option for me to get it back in a working state. If anyone reading this has stock color os with TWRP, It would be great help if you could give me a TWRP backup of system.
Also, I would ilke to know where I messed up while unlocking/flashing, so that I can avoid this in the future.
Okay I managed connect it via fastboot again and flashed the stock fastboot image but it didn't help. I'm still stuck at fastboot mode and can boot to TWRP as well but not to system.
While flashing system.img and vendor.img i'm getting error "Invalid sparse file format at header magi".
If anyone can can provide me stock realme recovery, then I can flash official update ozip to get back to stock os (and get out of the bootloop).
naushad.016 said:
If anyone can can provide me stock realme recovery, then I can flash official update ozip to get back to stock os (and get out of the bootloop).
Click to expand...
Click to collapse
There is a flashable twrp stock rom.. in guides section. Flash it in twrp.
Thanks I'll try that!
naushad.016 said:
Okay I managed connect it via fastboot again and flashed the stock fastboot image but it didn't help. I'm still stuck at fastboot mode and can boot to TWRP as well but not to system.
While flashing system.img and vendor.img i'm getting error "Invalid sparse file format at header magi".
Click to expand...
Click to collapse
How you managed to get fastboot ?
naushad.016 said:
If anyone can can provide me stock realme recovery, then I can flash official update ozip to get back to stock os (and get out of the bootloop).
Click to expand...
Click to collapse
You cannot flash the StockRomXYZ.ozip file directly via TWRP or OrangeFox recovery but if you want to flash COLOR OS then use this link - https://forum.xda-developers.com/realme-xt/how-to/official-ota-update-rmx1921ex11-11-26-t3993041 to download and flash directly otherwise convert the .ozip file into .zip file before flashing. Try the steps mentioned in the link to convert - https://forum.xda-developers.com/realme-2-pro/how-to/convert-ozip-to-zip-installing-stock-t4065277 . After conversion, copy the .zip into storage and always use the Clean Flash method to flash the firmware.
Hope you got it.
Hi,
XT1527 surnia_retca_cus 2016-11-18
this phone doesn't seem to allow flashing a custom recovery (fastboot flash went ok but still boots into stock no matter what). Fastboot boot with twrp image didn't work either (stuck on splash screen)
I now tried flashing a stock rom but couldn't find exact same model. Phone is now bricked (flashing gpt.img fails).
Any suggestions? Thanks
Foldback said:
Hi,
XT1527 surnia_retca_cus 2016-11-18
this phone doesn't seem to allow flashing a custom recovery (fastboot flash went ok but still boots into stock no matter what). Fastboot boot with twrp image didn't work either (stuck on splash screen)
I now tried flashing a stock rom but couldn't find exact same model. Phone is now bricked (flashing gpt.img fails).
Any suggestions? Thanks
Click to expand...
Click to collapse
Flash the twrp and the boot into it and allow modification to keep twrp then flash any custom rom
riyan65 said:
Flash the twrp and the boot into it and allow modification to keep twrp then flash any custom rom
Click to expand...
Click to collapse
Ok, I managed to flash both the twrp.img and the boot.img from a "surnia_retca...similar but not same...cid14" onto it but it still fails to start twrp, saying as before "Error: failed to load kernel! Boot up failed".
Foldback said:
Ok, I managed to flash both the twrp.img and the boot.img from a "surnia_retca...similar but not same...cid14" onto it but it still fails to start twrp, saying as before "Error: failed to load kernel! Boot up failed".
Click to expand...
Click to collapse
Are you on stock rom or custom???
If on stock you need to flash the firmware again, if on custom just flash the custom ROM again, it will fix your problem.
riyan65 said:
Are you on stock rom or custom???
If on stock you need to flash the firmware again, if on custom just flash the custom ROM again, it will fix your problem.
Click to expand...
Click to collapse
I originally only had the stock rom, which would not go into twrp as recovery after flashing (going into stock recovery instead).
I did not back up this stock rom and tried a similar, but slightly older one (XT1527_SURNIA_RETCA_6.0_MPI24.65-39_cid14_subsidy-DEFAULT_CFC.xml.zip) which failed the gpt stage of flashing and after that the stock was gone.
It now only has the bootloader working, with the above problems.
Foldback said:
I originally only had the stock rom, which would not go into twrp as recovery after flashing (going into stock recovery instead).
I did not back up this stock rom and tried a similar, but slightly older one (XT1527_SURNIA_RETCA_6.0_MPI24.65-39_cid14_subsidy-DEFAULT_CFC.xml.zip) which failed the gpt stage of flashing and after that the stock was gone.
It now only has the bootloader working, with the above problems.
Click to expand...
Click to collapse
You were lucky as your device didn't get hard Bricked, if you flash a older firmware then the device has, then it going to hard brick and you won't get bootloader too. So it just a paperweight.
If you want to flash stock rom then flash the ROM by removing the gpt and bootloader command, if any error occurs keep going and then reboot the device. Your device will work.
That worked, thanks very much! Using the XT1527_SURNIA_RETCA_6.0_MPI24.65-39_cid14_subsidy-DEFAULT_CFC.xml.zip, it gave an error for the mfastboot erase customize line, but then booted into Android and stock recovery was back as well.
I am now back to the problem of getting the device to run the twrp recovery. It flashes OK but gives "Error: failed to load kernel! Boot up failed" when rebooting and going into Recovery from bootloader. Stock recovery is gone after this new attempt. What's going wrong? I am using twrp-3.3.1-0-condor.img
Foldback said:
That worked, thanks very much! Using the XT1527_SURNIA_RETCA_6.0_MPI24.65-39_cid14_subsidy-DEFAULT_CFC.xml.zip, it gave an error for the mfastboot erase customize line, but then booted into Android and stock recovery was back as well.
I am now back to the problem of getting the device to run the twrp recovery. It flashes OK but gives "Error: failed to load kernel! Boot up failed" when rebooting and going into Recovery from bootloader. Stock recovery is gone after this new attempt. What's going wrong? I am using twrp-3.3.1-0-condor.img
Click to expand...
Click to collapse
Your using different twrp for different devices which cause the issue of kernal. Flash this twrp and it going to work.
https://twrp.me/motorola/motorolamotoelte.html
riyan65 said:
Your using different twrp for different devices which cause the issue of kernal. Flash this twrp and it going to work.
https://twrp.me/motorola/motorolamotoelte.html
Click to expand...
Click to collapse
You're a star! Surnia twrp is working. When I started I didn't know about the different Moto E's (I was looking at the /e/ fork of LineageOS for Moto E, and they officially only list condor). Hence I only tried condor...
Luckily there is an unofficial /e/ build for surnia. This installed successfully by adb sideload. Mission accomplished, thanks again for your help!
PS.
Check out https://doc.e.foundation/what-s-e
it's a very good idea.