Hi everyone,
I rooted my phone and played around with some custom roms, but I need to send my phone to get it repaired. I attempted to unroot and revert back to stock.
I followed a video, but I can't link it.
The steps were:
Flash the stock recovery.img
Relock the phone
Install the RUU
It was all going smoothly, until I realised my phone is on 2.17 and not 1.26, the RUU didn't work, and now it is stuck in the fastboot menu.
My CID is OPTUS001, is there anything I can do? I've been frantically searching, but I'm a bit of a noob when it comes to this.
All help is incredibly appreciated!
Yeah mate, get your Optus 001 2.17 nandroid backup here
http://forum.xda-developers.com/showthread.php?t=1975140
Unpack it to the right backup folder on the sdcard (read the OP of the thread please)
Flash the boot.img from the nandroid backup, perform a full wipe in the recovery and restore the backup. Once its up and running you also grab the 2.17 stock recovery from the OP of that same thread and flash it. Relock the bootloader and you are as stock as you can get.
OK, this sounds like it could be good. Currently downloading the nandroid backup.
Do I need to be unlocked and have CWM installed? Because currently my phone is relocked and I have the stock recovery installed, I can't access CWM. So I think I need to re-unlock and install CWM, right?
Yes correct
Ok thanks, this will be interesting to try and to this...
Well, I followed the instructions, but when I went to restore the RUU in CWM it wouldn't work so I tried rebooting back into the bootloader. I failed, now I'm stuck with the boot logo and in an endless boot loop. So another problem. I am so close to throwing this phone out the window. Pretty sure it's bricked.
Hold the power button and the volume - button together as long as it takes to get into the bootloader. From there you can enter the recovery.
What went wrong with the restore ? And its not a ruu.....its a nandroid backup.
Did you unpack it and put the files in the right folder ?
And no its not bricked.
Yeah I meant nandroid backup. Scratch that last post. Was just a minor meltdown, got the backup working now, think I'm good.
Thanks so much for your help
No problem ! :thumbup:
CASE CLOSED !
Related
Hi guys. trying to restore back to my backup stock rom. then want to update via OTA. So i restored back but i am stuck on HTC quietely brilliant screen.
I can get into HBOOT. any ideas on please what i need to do to get this working again please?
Thanks
You can get to Recovery from HBOOT surely? Just scroll down one.
You need to flash stock boot.img as nandroid restore will not restore the stock boot.img. You're still on the last boot.img that you flashed, that is why it is stuck on splash/bootloop
ckpv5 said:
You need to flash stock boot.img as nandroid restore will not restore the stock boot.img. You're still on the last boot.img that you flashed, that is why it is stuck on splash/bootloop
Click to expand...
Click to collapse
thanks. just managed to get the boot.img from a thread on Development section and just flashed it through fastboot. many thanks to you both. kinda had me there for a minute. still alot to learn on this side of the forums..many thanks
I rooted my phone and tried coredroid but decided that i preferred the stock rom and everything in it so decided to flash back. I had made a nandroid backup, so flashed it, and restored the recovery and relocked the device, however. now when trying to select music to play or to try and change the ringtone, the phone will crash and reboot. this happens every time, am downloading the RUU now to see if that will fix it, but does anyone have any ideas, any help would be much appreciated
i experienced that before and it was late when i realized it was because of the boot.img that you flashed from the custom rom, since you restored back to stock rom your boot.img file your using is still the custom rom that you used, try to post from the thread of coredroid and ask for the boot.img to be flashed for you to use your stock rom and remove the restart issues
Just extract the boot.img from your nandroid backup and flash it via fastboot (you'll need to unlock your bootloader again if you've already relocked it)
THANKS!!!
OMG thanks it worked, i dunno why the CWM didnt flash the boot.img as well, anyway it works now, thanks both of you for the help
Aidsy said:
OMG thanks it worked, i dunno why the CWM didnt flash the boot.img as well, anyway it works now, thanks both of you for the help
Click to expand...
Click to collapse
CWM can't write to the boot partition without S-OFF, which is why you have to manually flash a boot.img through fastboot when you install a new ROM. But it also means you have to do the same thing when restoring a backup.
I have searched to find the answer to this but the going from 1.29 to 1.28 bit is confusing me.
I have an HTC One X that was on T-Mobile UK 1.26. I usedthe HTC Dev and clockwork and ended up with the LeeDroid Rom with 1.29 firmware.
I have the phone for sale and have someone local who wants it, but he says he wants the standard rom on it or a stock HTC one. Don't ask why, I don't know.
What exactly can I do to get it back...I have some backups I made via the option in Recovery all the way back to the T-Mobile rom...with options to restore boot.img
Or can't I go back because I am on 1.29 ?
monkeyphonix said:
I have searched to find the answer to this but the going from 1.29 to 1.28 bit is confusing me.
I have an HTC One X that was on T-Mobile UK 1.26. I usedthe HTC Dev and clockwork and ended up with the LeeDroid Rom with 1.29 firmware.
I have the phone for sale and have someone local who wants it, but he says he wants the standard rom on it or a stock HTC one. Don't ask why, I don't know.
What exactly can I do to get it back...I have some backups I made via the option in Recovery all the way back to the T-Mobile rom...with options to restore boot.img
Or can't I go back because I am on 1.29 ?
Click to expand...
Click to collapse
You can go back; it's only if you'd done an official update (OTA or RUU) that you'd be stuck, because they also update the bootloader and you can't downgrade that.
Since you've got backups I would just restore the backup of the T-Mobile ROM, flash the boot.img which is in the nandroid backup folder, then (if he's wanting it completely stock), flash the stock recovery and lock the bootloader again.
Alternatively, if you can find a T-Mobile RUU you can just lock the bootloader then run the RUU to write everything back to stock, but it seems a waste of time downloading a full RUU when you've got a backup of the software you want already sitting there.
Hey thanks, will give that a try..cheers
I flashed the original backup from April in recovery and it just hangs at a white screen on reboot.
monkeyphonix said:
I flashed the original backup from April in recovery and it just hangs at a white screen on reboot.
Click to expand...
Click to collapse
Did you flash the boot.img via fastboot as well?
Does that have to be done on my pc ? I just flashed the boot.img then the actual backup. Via the phone
Unless you're s-off you can't write to the boot partition from recovery, so you need to do it from your computer using fastboot. Exactly the same as when you're flashing a ROM.
I never used a pc for anything to get it to the Leedroid...I'll have to look for a guide to do what you said. Apart from when I did the HTC Dev unlock thing.
Thanks for your help.
monkeyphonix said:
I never used a pc for anything to get it to the Leedroid...I'll have to look for a guide to do what you said. Apart from when I did the HTC Dev unlock thing.
Thanks for your help.
Click to expand...
Click to collapse
Interesting; I'm impressed your ROM's been working, seeing as you've seemingly been using the stock 1.26 boot.img with the 1.29 ROM.
Anyway, it's a similar (red identical) process to the one you used to unlock the bootloader. Assuming you've still got the fastboot executable on your PC from when you unlocked, and a copy of the boot.img from the backup you're trying to restore:
1) copy boot.img into the same folder as the fastboot binary
2) turn your phone on in fastboot mode (turn it off, hold vol-down and power on and it should boot into bootloader; select 'fastboot' from the menu if it doesn't automatically load into fastboot mode)
3) connect the phone to the PC via USB (the text on the phone should now say "fastboot USB")
4) on your PC open a command prompt and navigte to the folder containing your boot.img and the fastboot binary
5) run the following command: fastboot flash boot boot.img
6) run the following command: fastboot erase cache
7) run the following command: fastboot reboot
I've just reverted back to stock recovery instead of the original boot for some reason, been at a wedding and am a bit very drunk still, so I really need to get the stock boot.img file from somewhere don't I.
Edit, I found it in clockwork folder by connecting to pc and it is 8mb from April.
I did what you said and it all worked, great thanks. I am now back on stock boot.img abd back to tmobile 1.26....but still with the clockwork recovery and still rooted.
I know how to revert back to the stock recovery as I just did it by mistake...should I be d-rooting it or whatever you call it...and will I have wiped out my sim unlock I paid for ?
Also it is offering me an update of 28 or so mb, is this safe to install ? I am on 1.26 right now. Or do I want to get rid of clockworkd and revert to stock recovery first ?
The 28mb update will be the 1.28 update; you would need to restore the stock recovery and lock the bootloader again to install that (it will just download and fail if you try to install it now).
If the person you're selling it to wants it completely back to stock, then flash your stock recovery, then go back into fastboot (same process as before) and use the command fastboot oem lock to lock the bootloader again. Then accept the update and it'll be back to stock and updated to 1.28.
No idea about SIM-unlocks, sorry. I imagine it would still hold (otherwise everyone who's flashing ROMs, updates or backups would need to keep re-doing it), but I'm honestly just guessing at this point so don't take any of that as anything conclusive.
Ok I did all that and relocked it just about to do the update. Thanks very much for your help.
Hi All,
Been having issues with my HTC One X for the past week now and haven't been able to solve it via google or searching this forum, so was hoping one of you kind people can assist a bit.
I do apologise if this issue has already been posted and I missed it, if you can link me I'll be eternally grateful.
Basically, had a few issues annoying me with my HTC so wanted to stick a custom ROM on it. Did some searching about, eventually got a plan together to unlock and root it. All went fine, unlocked it (S-On still) got TWRP recovery on it (Chose this as the ROM I was looking at claimed to be not compatible with CWR) and was booted back into my stock droid.
First thing I did after a successful boot was to go back into recovery and make a full backup (I may have not ticked the Cache and _android.secure)
Played about with the phone again a bit, getting some of the apps back on as it had been wiped, then made a second backup (This one I know I ticked all the boxes for)
Next I tried putting CleanROM on, but could get past the white HTC screen boot loop, after various reflashing the Boot.IMG and clearing cache, so fired up TWRP and restored back to my second backup. All back to normal.
Used the phone as normal for a day or so then I tried flashing another ROM (ViperX) same thing as CleanROM (White HTC screen boot loop) and then went on to try Team Baked's ROM. Managed to get this working successfully, however the ROM was not to my liking and decided to go back to my stock backup. Here's where the issue started.
Now, when restoring the backup the phone boots as far as displaying my background and the status bar at the top, however I cannot pull the status bar down and the ring to unlock the phone with doesn't appear. It sits here for a few second and then reboots. Boot loop.
I've tried clearing cache, restoring various different ways and restoring the boot.img (though I'm not sure I have the right one) but nothing works.
The last variation I tried for restoring involved:
1. Clearing the phone via TWRP (System Restore/Clear Cache/Clear Davik/Clear System/Clear SD Card (heard this can cause issues)/Clearing Android.Secure in that order)
2. Reboot into recovery
3. Repeat step 1 (in case of locked files)
4. Reboot into Recovery
5. full restore (With MD5 check enable)
6. Clear Cache and Dalvik (Tried with just cache, also done Fastboot clear cache in another attempt)
7. Attempt to boot into OS.
As I mentioned earlier, I'm not sure if I have the right boot.IMG for my phone Model/kernal/other, to be honest I'm not entirely sure of the requirements. The details of my phone I've collected so far are:
Getvar version-main (Not sure if this is kernal or what) = 2.17.771.3
hBoot = 1.12.0000
radio = 2.1204.135.20H
CID = H3G_001
Basically, as far as I can tell from the masses of reading I've been doing, I won't be able to update to custom JB for a while so want to get back to my stock ICS and then OTA to JB when my carrier releases their version, then maybe sometime in the future when the ROM specific to my phone has been cracked consider switching to a custom.
on a final note, I've tried flashing both my backups, same result. I've also tried restoring the stock recovery and doing a system recovery with that. It appears to go through the motions (phone with green arrows? Also had the red exclamation mark, but only once of the 3 attempts) then reboots and it's still the same issue.
Thanks for reading through, any advice would be much appreciated. Used to love my phone but now can barely stand to look at it.
Cheers,
Sean
Ok, so I've now downloaded a different boot.img which should be for stock ics and after flashing that, then flashing stock recovery and doing a system restore via bootloader I will 50% of the time get the lock screen and when I unlock it I see the white HTC screen of the initial setup, then it sticks there a while and reboots. It also reboots after left at the lock screen.
To me this seems like it's doing a check or looking for a certain piece of software/file that's missing but is required to finish the start-up process. Anyone any ideas?
Even if someone can point me in the right direction for an RRU for my phone as football's RRU's seem to be the only one that has the one I need but as of 5 days before all this happened the site they're hosted on doesn't allow 500+MB downloads for free members
Cheers,
Sean
**EDIT** Just done a full device wipe then restored only the SYSTEM partition and manually flashed the boot, then when I restarted it sat on the white HTC on the device setup but eventually loaded up, allowed me to complete the device setup and then loaded into the OS. All seemed fine aside from the phone being stuck in turning off airplane mode. Rebooted it to see if that would clear it up and now I'm back to bootloops before the lock screen appears (I just get my background and status bar)
So you have a nandroid backup ! Then do this
Wipe all in recovery and i mean ALL except the sdcard obvious ! system,data,caches,dalvik cache...
Then boot back into fastboot usb mode and flash the boot.img from the nandroid. Taken with TWRP the boot.img is called something like
Emmc.boot.win (or at least similar to this)
You can flash this file with fastboot command
Fastboot flash boot name of the boot.img (.win in this case)
Then enter the recovery and full wipe if you didn't o that already !
Restore the nandroid and boot it up :thumbup:
Should work
Perfect! Thanks so much man, I never even thought to flash the .wim, thought it had to be .img. Just successfully booted fully back into my old system. Hopefully will stay stable the next hour or so but looking good!
Thanks again,
Sean
Need help!!!
I'm facing the same problem with my device, i have ulocked bootloader from HTCdev and flash TWRP recovery, was trying to flash Maximus but unfortunately after flashing Maximus in TWRP my device stuck on boot logo.
Hboot: 1.12.0000
CID: HTC__J15
version-main: 2.17.415.2
Please help.
Did you flash boot.img through fastboot?
Sent from my HTC One X
TToivanen said:
Did you flash boot.img through fastboot?
Sent from my HTC One X
Click to expand...
Click to collapse
Yes, the one came with Android_Fastboot_KIT_V12.x
And make sure you flash a 2.17 based ICS rom. You can not run the maximus JB rom on that 1.12 hboot !
Mr Hofs said:
And make sure you flash a 2.17 based ICS rom. You can not run the maximus JB rom on that 1.12 hboot !
Click to expand...
Click to collapse
Then, i have done the mistake there. Now, please guide me what i need to do to get out of this problem.
I have forget to mention my device still S-ON
Please guide, sorry for troubling.
Download a 2.17 ics Rom and copy it to the phone (mount the sdcard within the recovery as a usb disk)
Take the boot.img file from that rom and copy it to the tool you used to flash it
Then enter the recovery and wipe EVERYTHING except sdcard ofcourse !!! (Cache,dalvik cache, system and data)
Then install the Rom.zip
Mr Hofs said:
Download a 2.17 ics Rom and copy it to the phone (mount the sdcard within the recovery as a usb disk)
Take the boot.img file from that rom and copy it to the tool you used to flash it
Then enter the recovery and wipe EVERYTHING except sdcard ofcourse !!! (Cache,dalvik cache, system and data)
Then install the Rom.zip
Click to expand...
Click to collapse
Thank you so much.
No problem mate ! :thumbup:
If you're looking for a Rom, I've got hboot 1.12 as well and tried a few ROMs and only ones I got working were:
Team Baked, based on jellybean though still works with 1.12. No Sense though, and a few things weren't to my liking (to name a couple,backlights on buttons didn't work and multitask button was switched back to menu button like in older devices)
SkyDragon, ics ROM with sense. Only had this a short while but appeared to be an exact stock ROM, everything working the way it should, and with a few added extra improvements.
Good luck
Slaverty said:
If you're looking for a Rom, I've got hboot 1.12 as well and tried a few ROMs and only ones I got working were:
Team Baked, based on jellybean though still works with 1.12. No Sense though, and a few things weren't to my liking (to name a couple,backlights on buttons didn't work and multitask button was switched back to menu button like in older devices)
SkyDragon, ics ROM with sense. Only had this a short while but appeared to be an exact stock ROM, everything working the way it should, and with a few added extra improvements.
Good luck
Click to expand...
Click to collapse
Is there anyway to restore it to the backup i have made with TWRP which is still in the sdcard???
sfawad81 said:
Is there anyway to restore it to the backup i have made with TWRP which is still in the sdcard???
Click to expand...
Click to collapse
Yes.
Copy the boot.img from the backup to your PC (you can mount SD card as USB from TWRP), flash it:
fastboot flash boot boot.img
And restore backup from TWRP.
Yeah, if you follow Mr hofs 1st post on the 1st page he describes all the steps required to restore. Worked perfectly for me
Slaverty said:
Yeah, if you follow Mr hofs 1st post on the 1st page he describes all the steps required to restore. Worked perfectly for me
Click to expand...
Click to collapse
Thanks alot, got it back as it was before.
Need to clear a doubt; will I be able to update my device with the OTA, as my device is unlocked, S-ON & TWRP installed?
I hope so, I'm in the same boat as you. From what I've been reading, it should still be possible as long as you put back the stock recovery and relock the bootloader.
This website offers links to download the stock recovery
http://www.androidauthority.com/one-x-revert-stock-recovery-76854/
As for relocking the bootloader, I think the process is to run this command whilst in Fast Boot USB mode
fastboot oem lock
After it's run there should be a purple "RELOCKED" at the top of your bootloader menu.
Remember to flash the recovery BEFORE you relock the bootloader
You do not have to lock the bootloader, just the stock recovery is needed ....
Stock rom (out of the box stock)
Stock boot.img
Stock recovery
Here is the 2.17 based stock recovery for those who needs it
http://db.tt/U5CK4noo
Hi
I recently tried to update a stock handset from 3 to the Android Revolution HD 18.2 ROM, but have failed and now cant get it to boot at all.
I have CID: H3G__001 and HBOOT 1.12, i think i may have jumped the gun and not updated my hboot but could be wrong.
I am using a mixture of Hasoon2000 v2.3 tools and some adb commands found while searching for solutions, but nothing i try seems to restore it.
When i first rooted / unlocked it, i installed TWRP 2.4.1.0 from Hasoon's tool, and did a backup.
I have tried restoring from this backup but all i get is stuck at the 3 logo, rather than the HTC one.
I tried to re-lock the bootloader and reboot, clear all the cache but still nothing....
I have spent hours now searching for possible solutions before finally calling out for help, as i think i am now likely to do more damage than good.
I even tried to download a full backup from Matt's collection http://forum.xda-developers.com/showthread.php?t=1975140 but this failed to install
HELP !!!! Phone is now dead
Hi.
You need to update your hboot in order to flash ARHD 18.x.
Your backup failed to boot because you didn't flash the boot.img of it. Get the boot.img at /sdcard/TWRP/ and flash it.
TToivanen,
Thanks for such a fast response.
I have tried searching for the correct files to use to update my hboot, but the list from http://forum.xda-developers.com/showthread.php?t=2153777&highlight=hboot just confuses me as i cant seem to work out the correct one to use (if any).
Do you know where i could get the right hboot for my cid ?
If i update the hboot and re-flash the ARHD 18.x. - if this fails again, will i still be able to recover to stock using TWRP recovery and your method of locating the boot.img from the sdcard/TWRP ?
Many thanks, its just i have been going round in circles for ages and gave my other phone to a friend so now desperate to get back up and running again.
I think you have more succes in this thread
http://forum.xda-developers.com/showthread.php?t=1927048
And yes you can always return to a backup or another rom ....
Oké so download the firmware.zip from the link above and do these fastboot commands. Note that you will need the original Unlock_code.bin because this method involves locking and reunlocking the bootloader. Search for it in your email inbox.
fastboot oem lock
fastboot oem rebootRUU
fastboot flash zip firmware.zip (do two or three times if it fails)
fastboot flash unlocktoken Unlock_code.bin
fastboot flash recovery openrecovery-twrp-xxxx.img
Thanks all, managed to un-brick it, now time to play and see what it can do.
Updated hboot by following the instructions http://forum.xda-developers.com/showthread.php?t=1927048
Then went back to install the Android Revolution HD 18.2 ROM and boot.img and all working again.
Not sure if its the best ROM for this device but i thought its a reasonable place to start. Going to install Titanium backup first and also do a full nand backup just in case something goes wrong, or i feel brave enough to try a different ROM.
Thanks again.
You're welcome!