OK, so I need some help
When I first unlocked my DX, I made a CWM backup of the ROM.
Recently I noticed that there are a few newer JB ROMS that Id like to try, but Im on HBOOT 1.24.0000, and whilst using the Custom ROM, unable to update via OTA.
Ive spent a hour or so trying to restore the backup and run OTA, which has worked up to a point.
Heres what Ive done so far.
- Restored by CWM backup (had to fix a MD5 problem)
- Rebooted and OTA downloaded OTA_PROTO_U_ICS_40A_hTC_Asia_WWE_1.18.707.3-1.18.707.1_release_300978id119tizxreo6g0l.zip
- Asked if wanted to update...YES!! I said
- Restarted into CWM and an error about not being able to mount SDCARD
- tried to flash the ZIP file manually and get the check_cid asset failed error (CID mismatch I think).
My CID is HTC_044, but if Im using a backed up ROM from my phone, and OTA is downloading it, why wont it install?
I've also tried relocking (fastboot oem lock) and all it does it reboot back into fastboot (assume there must be something wrong with the ROM backup?).
I can see there are no official region 044 RUU's so what can I do (if anything)?
Can anyone help me out?
Thanks
chocyman said:
OK, so I need some help
When I first unlocked my DX, I made a CWM backup of the ROM.
Recently I noticed that there are a few newer JB ROMS that Id like to try, but Im on HBOOT 1.24.0000, and whilst using the Custom ROM, unable to update via OTA.
Ive spent a hour or so trying to restore the backup and run OTA, which has worked up to a point.
Heres what Ive done so far.
- Restored by CWM backup (had to fix a MD5 problem)
- Rebooted and OTA downloaded OTA_PROTO_U_ICS_40A_hTC_Asia_WWE_1.18.707.3-1.18.707.1_release_300978id119tizxreo6g0l.zip
- Asked if wanted to update...YES!! I said
- Restarted into CWM and an error about not being able to mount SDCARD
- tried to flash the ZIP file manually and get the check_cid asset failed error (CID mismatch I think).
My CID is HTC_044, but if Im using a backed up ROM from my phone, and OTA is downloading it, why wont it install?
I've also tried relocking (fastboot oem lock) and all it does it reboot back into fastboot (assume there must be something wrong with the ROM backup?).
I can see there are no official region 044 RUU's so what can I do (if anything)?
Can anyone help me out?
Thanks
Click to expand...
Click to collapse
Since you are now on a Stock ROM, You just have to flash the Stock Recovery then the OTA will install else it will keep restarting into the custom recovery.
chocyman said:
OK, so I need some help
When I first unlocked my DX, I made a CWM backup of the ROM.
Recently I noticed that there are a few newer JB ROMS that Id like to try, but Im on HBOOT 1.24.0000, and whilst using the Custom ROM, unable to update via OTA.
Ive spent a hour or so trying to restore the backup and run OTA, which has worked up to a point.
Heres what Ive done so far.
- Restored by CWM backup (had to fix a MD5 problem)
- Rebooted and OTA downloaded OTA_PROTO_U_ICS_40A_hTC_Asia_WWE_1.18.707.3-1.18.707.1_release_300978id119tizxreo6g0l.zip
- Asked if wanted to update...YES!! I said
- Restarted into CWM and an error about not being able to mount SDCARD
- tried to flash the ZIP file manually and get the check_cid asset failed error (CID mismatch I think).
My CID is HTC_044, but if Im using a backed up ROM from my phone, and OTA is downloading it, why wont it install?
I've also tried relocking (fastboot oem lock) and all it does it reboot back into fastboot (assume there must be something wrong with the ROM backup?).
I can see there are no official region 044 RUU's so what can I do (if anything)?
Can anyone help me out?
Thanks
Click to expand...
Click to collapse
Here is all the info you need to run OTA (In the first 3 posts):
http://forum.xda-developers.com/showthread.php?t=2210619&highlight=nandroid+ics
GtrCraft said:
Here is all the info you need to run OTA (In the first 3 posts):
http://forum.xda-developers.com/showthread.php?t=2210619&highlight=nandroid+ics
Click to expand...
Click to collapse
Thanks you
And thanks for the OP - ckpv5 - for writing that excellent guide.
It all worked flawlessly :good:
Related
Hi,
I traded a phone with someone and the rom they had was acting up.. the Infected Rom (cdma verizon)... When I got the phone, I told him he could keep his SD card and I could keep mine.. i guess the P something image file was on there and now Im just rooted with Teamwin recovery and not able to flash any rom or restore the Infected rom i nandroid backed up.
I have fastboot 1.50 S On but unlocked
Now imma be at work and not have a working phone. This isn't cool. PLEASE GET BACK TO ME IF YOU CAN HELP peeps. I would really appreciate it.
I also tried the unlocking method all over again but the Java SDK wont install.. it tells me to disable my virus protection (I did) and then it says unable to install it. This is just a mess man.
stepinmyworld said:
Hi,
I traded a phone with someone and the rom they had was acting up.. the Infected Rom (cdma verizon)... When I got the phone, I told him he could keep his SD card and I could keep mine.. i guess the P something image file was on there and now Im just rooted with Teamwin recovery and not able to flash any rom or restore the Infected rom i nandroid backed up.
I have fastboot 1.50 S On but unlocked
Now imma be at work and not have a working phone. This isn't cool. PLEASE GET BACK TO ME IF YOU CAN HELP peeps. I would really appreciate it.
I also tried the unlocking method all over again but the Java SDK wont install.. it tells me to disable my virus protection (I did) and then it says unable to install it. This is just a mess man.
Click to expand...
Click to collapse
If you're interested in reverting back to completely stock, the RUU files are available at http://www.goo-inside.me/shooter/ruu . Both the PG86IMG.zip and the .exe files are available there.
Interesting the device is flashed to verizon, at least you mention the device is on CDMA verizon. The only issues I can forsee here will be 3G data/MMS might not work via Verizon if using a stock Sprint ROM.
Of course, these *might* work and they can also be *tweaked* but I doubt, out of the box, they will work. Phone calls and SMS should work over verizon using the stock sprint ROM.
Here is my usual lecture, reading this will save you a lot of time and headache, regarding flashing a ROM and kernels on the EVO 3D with hboot 1.5 and htc's unlock method:
Essentially, if you're looking to flash a kernel or ROM (which many times also include a kernel), there are three basic methods (two seem the easier) with hboot 1.50 and htc's unlock method:
1) For Kernel Flashing: From Android mode, using my application, Flash Image GUI. Put the kernel .zip file on your sdcard, select from inside the application and flash.
For ROM Flashing: Pull out the kernel file (usually named boot.img) out of the ROM .zip and push to sdcard. Flash using Flash Image GUI.
If you're away from a computer and want to flash any kernel, this is a great tool!
2) Load the custom recovery, NOT using the traditional method (reboot recovery, bootloader -> recovery, etc), but a specific method for Hboot 1.5. From the prompt use: fastboot boot c:\downloads\cwm-recovery.img.
This will temporarily boot the custom recovery image and the HTC unlock method will grant it write access to the boot partition while in this mode.
In this temporarily booted recovery mode, when a full ROM (with kernel included) is flashed, the kernel will flash correctly.
3) Boot into recovery using the traditional methods, reboot recovery, bootloader -> recovery, etc, and after the custom recovery has loaded, flash the ROM. Reboot into fastboot mode and then separately flash the kernel from the computer: fastboot flash boot c:\boot.img.
Downside to this method would be if a zImage is included instead of the boot.img for the kernel, won't flash correctly.
Being without a phone is rough now a days! Hope that helps and points in the right direction!
so sorry.. i meant to say CDMA Sprint.. i probably was so frustrated and typed verizon. I am about to read what you post completly.
Thank you so much for the reply! I purchased the GUI App from the market a few days ago and I wasnt sure if it would work on my phone because that PG86IMG.zip wasn't on the root of my SD card (it's on the other guy's sd card) I will try your method to flash a ROM.
I was able to get the Rom restored from the nandroid backup someone last night.. I still need a new rom because this one has touch screen problems. Thanks again
I got my DNA back in December, unlocked with S-ON, rooted, and flashed a lightly modified stock ROM. It's been super stable, so I figured I wouldn't mess with it, and I've been running it since.
Yesterday, I was trying to free up some space on my device by integrating updates of system apps through Titanium Backup, and it jacked stuff up pretty royally. I figured, this is a great chance to install a new Sense 5 ROM.
I went through TWRP, installed the new ROM, cleared data, and when it restarted, it hung at the white HTC screen. Undeterred, I tried again through recovery. Then through sideloading a different ROM. Then by restoring a backup, downloading a new ROM and trying through recovery. Then installing CWM instead of TWRP and trying that way. Then by sideloading through CWM.
Every single method by which I've tried to install a new ROM has resulted in the phone hanging indefinitely at the white HTC screen.
I have obviously searched repeatedly for a fix for the white screen issue, and while I can restore an old backup and get the phone running, I can't seem to find a solution that gets me up and running on a new ROM. I'd hate to go through all the work (my phone's been unusable since around 8 PM last night) and not come out of it with a new ROM.
Am I missing something? Maybe I should be installing a new kernel before installing the ROM?
you are s-on you must flash the kernel boot.img via fastboot then flash kernel modules via recovery
copy boot.img from rom.zip
in command prompt goto folder with boot.img and enter
fastboot flash boot boot.img
then create a flashable module.zip and flash via recovery or adb eacxh module into system folder or just s-off your device and re flash rom.zip
The best way to fix ur phone now is to go through RUU, first relock the bootloader through fastboot, then enter RUU again through fastboot nd run the RUU from ur pc, ur good to go.
The reason it's getting stuck thr is becoz the system partition isn't getting mounted
As soon as I typed "S-On" in that original post, I started getting suspicious that might be the problem, but none of the ROMs I was trying specifically mentioned the need to be S-Off. But that does make sense.
So I spent the afternoon getting it S-Off, which was a bit of a hassle, and now in about three minutes, I see if I can indeed flash a ROM. I feel pretty optimistic, though.
Update: Success. I am now a very happy person.
congrats hope you enjoy
now no need for anything special to flash roms or kernels.
Model:XT1521 Retasia(Indian)
So let's get on with the story
I own a moto e 2 4g variant. I unlocked the bootloader of the device,installed a custom recovery and flashed a custom ROM. Everything went well;I was trying a new ROM almost everyday(5.1.1 and 6.0.1) until one day when I decided to go back to stock ROM.I downloaded the official 6.0 stock ROM,installed it and started the device.The phone booted,went straight to recovery and showed erasing.The problem starts here.It showing eraseing and rebooted after some time and I thought that it's going to boot up into stock 6.0.But I was wrong.The phone booted and again did the same thing and this went on in a loop.So I decided to try it once more.This time I did two more things prior to installing the ROM;
Fastboot erase all
Fastboot erase system - w
Till then in bootloader it showed official in software status.But after those two erase commands it started showing modified.
Even then the result was the same I.e.showing erasing and rebooting.So I thought that I will go back to custom ROM for the time being.all went well,phone booted up but there was no signal.The phone was not accepting any Sims. I went to bootloader and immediately found out the cause.It was showing not found under baseband.So I seperately flashed a modem but to no luck.As of now I have tried all stock rims available(5.0.2,5.1.1,6.0) but the device is not booting up.
Any help will be highly appreciated.
Thanks in advance.
This happened to me with CM13, the same thing happened with the baseband number, and I couldn't even enter in the recovery, so I had to manually flash the Stock ROM via adb. It happened to me again when I tried to root my phone even with the systemless root, the phone just doesn't boot up, I'd recommend you to flash the basebands found in the forums, if that doesn't fix it, you'll have to manually flash the stock rom via adb or you can use the easy tool, it's fairly simple if you follow the steps, I'll leave the links bellow.
Easy tool flasher
Basebands
Filz0r said:
This happened to me with CM13, the same thing happened with the baseband number, and I couldn't even enter in the recovery, so I had to manually flash the Stock ROM via adb. It happened to me again when I tried to root my phone even with the systemless root, the phone just doesn't boot up, I'd recommend you to flash the basebands found in the forums, if that doesn't fix it, you'll have to manually flash the stock rom via adb or you can use the easy tool, it's fairly simple if you follow the steps, I'll leave the links bellow.
Easy tool flasher
Basebands
Click to expand...
Click to collapse
Used the flashing tool.But in every mode of flashing,the bootloader flashing and boot.img flashing is showing some error.But rest all are flashing succesfully.Still in bootloader it is showing baseband not found.And when I boot the device,the bootloader screen comes up,followed by a black screen and the cycle repeats.Any help would be appreciated.
Edit:My moto e 2015 is a LTE RETASIA(Indian) model.In the baseband link you provided,XT1521 RETASIA version's baseband is not available.
Fastboot flash bootloader bootloader. Img
Rename motoboot img
Sent from my MotoG3 using XDA-Developers mobile app
first.act.line said:
Fastboot flash bootloader bootloader. Img
Rename motoboot img
Sent from my MotoG3 using XDA-Developers mobile app
Click to expand...
Click to collapse
Thanks I will try that.
gauthamkithu said:
Model:XT1521 Retasia(Indian)
So let's get on with the story
I own a moto e 2 4g variant. I unlocked the bootloader of the device,installed a custom recovery and flashed a custom ROM. Everything went well;I was trying a new ROM almost everyday(5.1.1 and 6.0.1) until one day when I decided to go back to stock ROM.I downloaded the official 6.0 stock ROM,installed it and started the device.The phone booted,went straight to recovery and showed erasing.The problem starts here.It showing eraseing and rebooted after some time and I thought that it's going to boot up into stock 6.0.But I was wrong.The phone booted and again did the same thing and this went on in a loop.So I decided to try it once more.This time I did two more things prior to installing the ROM;
Fastboot erase all
Fastboot erase system - w
Till then in bootloader it showed official in software status.But after those two erase commands it started showing modified.
Even then the result was the same I.e.showing erasing and rebooting.So I thought that I will go back to custom ROM for the time being.all went well,phone booted up but there was no signal.The phone was not accepting any Sims. I went to bootloader and immediately found out the cause.It was showing not found under baseband.So I seperately flashed a modem but to no luck.As of now I have tried all stock rims available(5.0.2,5.1.1,6.0) but the device is not booting up.
Any help will be highly appreciated.
Thanks in advance.
Click to expand...
Click to collapse
u have to flash a official rom with propper way and remember u cannot flash old bootloader on the new bootloader it will definatly brick ur phone so if ur bootloader working do not replace it with old one for more info u can go in official rom section of this site and bootloader section.....good luck
vishalgupta.vns said:
u have to flash a official rom with propper way and remember u cannot flash old bootloader on the new bootloader it will definatly brick ur phone so if ur bootloader working do not replace it with old one for more info u can go in official rom section of this site and bootloader section.....good luck
Click to expand...
Click to collapse
Thanks buddy but unfortunately I have tried that.:crying:
OK guys, thread cleaned.
No more flame from anyone please, no more garbage.
OP please provide as much details as possible. Everyone else, you can ignore the OP if you want, but do not come in here just to flame.
Thanks.
Hi, just wondering if anyone can share his/her signed boot.img from stock rom RETMX, the one I tried to flash with fasboot ends in: (bootloader) signed with bad key. The phone boots, and i can flash roms with twrp and stuff, but when in stock, trying to install OTA gets in error due to the bad key.
edit: Going into more reasoning, I realize that the main cause of the OTAS not installing, is because i've already taken the last update, and that probably messed with the gpt.bin, because when trying to flash it, the fastboot console says that I'm trying to downgrade, and aborts. So my only hope to restore this to total stock is if someone with an untouched twrp backup can share his backup with me. It needs to be in the latest update of RETMX. I would really apreciate it. Thanks.
Hi experts!
Is there an available factory image of the latest firmware for griffin xt1650-03 for download? I unlocked my boot loader and tried to flash custom firmware now I am stuck in boot loop. My phone was nougat and updated via OTA last week before I decided to unlock boot loader. I tried loading the latest image I got from firmware.center but I am getting Downgrade version and verification failed when flashing stock partition and not loader. Please help
Note: I did this my wifi became unusable after my last OTA (mac 02:00:00:00) and thought using custom firmware would help
And I did not make a back up
Get it in fastboot mode, flash TWRP and root it. That might work.
I am in exactly the same position as OP, although I have successfully installed TWRP and have open bootloader from which I can boot into TWRP no probs. I didnt do a backup (will never again make this error!!)
The problem arises when I try to flash (any) files over to device I get the "Downgrade version and verification failed" like OP when flashing stock Telus rom (telus phone) or any other rom/files.
Rebooting brings me back to the moto unlocked bootloader page (horrible!) and the only way out is to get key combo or fastboot into bootloader/recovery etc.
Tried flashing multiple images as whole or bit by bit, always get the same bad validation message. Finding it hard to believe this 700dollar phone is a brick after literally following MotoS own 'unlock your bootloader' instructions. Never had issues like this on OPO, S6, S7, LG etc.
PC shows android device connected, nothing in the two empty folders that appear. TWRP confirms I have no OS installed and throws me back to bootloader.Wondering if locking bootloader again will allow me to install 'stock' ROM or at least recovery? I have reached my android knowledge limit and am not sure where to go from here, any help much appreciated!
OK. This happened to me. The way that I solved it was by flashing the RETUS NPL86.25.15 and then flashing the OTA 25.17-3-3 through twrp. Although I think I could've saved the headache if the original instructions included flashing the OEM.bin but anyways. That's what I did. Hope it helps.
Thanks. I did try flashing the oem.bin but got partition name error.
Can you link to the files you mention I think it's a kernel and then an OTA image? Thanks again in advance.
What I mean is that when I first started flashing the RETUS rom the instructions skipped that part so I ended up flashing most of the file system without something so it would never boot but it wouldn't loop it'd just hang. So basically you flash everything and then include the OEM.bin after you do the system chunks