my friend had rooted my ONEX created a backup . i am currently running ARHD want to back to stock to enjoy OTA update. bt the problem is that in the clockworkmod recovery there are two backups. i dnt knwo which one is of stock .
Try just restoring any one of the nandroid backups and check in settings to see if it is the right one. Nandroid backups don't take a long time to restore so don't worry.
Sent from my HTC One X using xda app-developers app
diamond225 said:
Try just restoring any one of the nandroid backups and check in settings to see if it is the right one. Nandroid backups don't take a long time to restore so don't worry.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
can u give me the steps on how to restore.. plss
Copy the boot.img from the nandroid backup and flash it with fastboot commands then do a full wipe in recovery and then restore the nandroid
Mr Hofs said:
Copy the boot.img from the nandroid backup and flash it with fastboot commands then do a full wipe in recovery and then restore the nandroid
Click to expand...
Click to collapse
i am noob and i am flashing it for the first time just want to ask i have to use fastboot commands in bootloader
do i need to flash the recovery ..?
juliethakkar90 said:
i am noob and i am flashing it for the first time just want to ask i have to use fastboot commands in bootloader
do i need to flash the recovery ..?
Click to expand...
Click to collapse
You have to flash the boot.img with fastboot commands and yes the phone has to be in the bootloader/fastboot usb mode
Then a full wipe in the custom recovery and restore the nandroid ! After that you check the phone works and that the rom is stock .....
Then you flash back the stock recovery to be able to update , because the custom recovery won't let you update officially !
I have it for you ... I just need the software number when you are done
Mr Hofs said:
You have to flash the boot.img with fastboot commands and yes the phone has to be in the bootloader/fastboot usb mode
Then a full wipe in the custom recovery and restore the nandroid ! After that you check the phone works and that the rom is stock .....
Then you flash back the stock recovery to be able to update , because the custom recovery won't let you update officially !
I have it for you ... I just need the software number when you are done
Click to expand...
Click to collapse
kk wil do in an hour. m just charging my phone.
juliethakkar90 said:
my friend had rooted my ONEX created a backup . i am currently running ARHD want to back to stock to enjoy OTA update. bt the problem is that in the clockworkmod recovery there are two backups. i dnt knwo which one is of stock .
Click to expand...
Click to collapse
You can prolly check the dates on both updates - worst case scenario just do another nandroid and try restoring both its just 2 options so your 50%-50%
Mr Hofs said:
You have to flash the boot.img with fastboot commands and yes the phone has to be in the bootloader/fastboot usb mode
Then a full wipe in the custom recovery and restore the nandroid ! After that you check the phone works and that the rom is stock .....
Then you flash back the stock recovery to be able to update , because the custom recovery won't let you update officially !
I have it for you ... I just need the software number when you are done
Click to expand...
Click to collapse
i did backup came back to my stock ROM
i did my veriosn is 1.29.751.12 wantt a recovery
No problem
http://db.tt/W5IJ8asG
Mr Hofs said:
No problem
http://db.tt/W5IJ8asG
Click to expand...
Click to collapse
Mr.Hofs i should flash this in bootloader and i should type
fastboot flash recovery Stock recovery 1.29.img ??
and thank you MR. hofs :good:
juliethakkar90 said:
Mr.Hofs i should flash this in bootloader and i should type
fastboot flash recovery Stock recovery 1.29.img ??
and thank you MR. hofs :good:
Click to expand...
Click to collapse
Yes that's correct, i dont know of the command accept spaces in the recovery name otherwise you have to rename the file to recovery.img
Fastboot flash recovery recovery.img
You know what i mean
You might want to rename it without the spaces, or maybe stick quotes around the filename, or use tab completion of the filename to properly escape the spaces.
BenPope said:
You might want to rename it without the spaces, or maybe stick quotes around the filename, or use tab completion of the filename to properly escape the spaces.
Click to expand...
Click to collapse
done ... and thank you both of you and is there a way to know i did everything correct..
If fastboot said success, it succeeded, if it said failed, it failed.
BenPope said:
If fastboot said success, it succeeded, if it said failed, it failed.
Click to expand...
Click to collapse
i went to the recovery and there is 3 green icons and 1 red icon.. ??
Explain a bit more the steps you took, is this happening while updating ? Or just entering the recovery from the bootloader ?
Mr Hofs said:
Explain a bit more the steps you took, is this happening while updating ? Or just entering the recovery from the bootloader ?
Click to expand...
Click to collapse
i jst went in to recovery from the bootloader ... thn i saw icons ..
No problem, just warning signs that you are entering a part we actually shouldn't
More important is :
Can you update now ? Check in settings info software
Mr Hofs said:
No problem, just warning signs that you are entering a part we actually shouldn't
More important is :
Can you update now ? Check in settings info software
Click to expand...
Click to collapse
i will update 2mrw morning (INDIA) and thank you ben :good:
Related
Hi, so just yesterday i decided that I wanted to go back to my stock rom, so i read up and learnt that I needed to flash stock recovery to successfully install the OTA update. I was rooted and the update didnt work so I flashed the recovery image for sense 4.0. It then allowed me to update to sense 4.1. There was then a minor update, 1.28 mb i believe and after that i was able to download the Jellybean OTA. When I download the jellbean OTA and try to install it through my stock recovery however, it comes up with an error saying E: error in OTA_ENDEAVOR_U_JB_45_S_Optus_AU_3.14.980.27-2.17.980.6_release_299170pamoph3dsqv4al9a and then it comes up with an error saying error opening E:/sdcard/external or something like that. I really have no idea what the problem is, my phone is not bricked, im just stuck on sense 4.1. My software information is listed below
My HTC one X is an optus branded phone and its CID is OPTUS_001
android version- 4.0.4
htc sense version- 4.1
software number- 2.17.980.6
htc sdk api level- 4.2.3
kernel version- [email protected] #1SMP PREEMPT
baseband version- 2.1204.135.20
Any advice or help would be GREATLY appreciated, i cant find anyone else who has the same problem
Which recovery did u flash back .... With what number did it start with ?
Mr Hofs said:
Which recovery did u flash back .... With what number did it start with ?
Click to expand...
Click to collapse
it was a recovery for 2.17, i got it from here https://www.dropbox.com/s/wbav46spkbznovp/stock recovery 2.17.img
http://forum.xda-developers.com/showthread.php?t=2043818&page=2 the problem that is happening at the top of page 2 is exactly what is happening to me, do you know where I could find an RUU for optus?
Yeah that's the right one (my link)
Did you change anything to the rom when it was rooted .... removing apps/bloatware ?
Ow and you can't install an ota by yourself in a stock recovery so the error messagges are in place.
Did u try to check software updates in the settings menu of the phone again and try to install it again from there ?
Mr Hofs said:
Yeah that's the right one (my link)
Did you change anything to the rom when it was rooted .... removing apps/bloatware ?
Ow and you can't install an ota by yourself in a stock recovery so the error messagges are in place.
Did u try to check software updates in the settings menu of the phone again and try to install it again from there ?
Click to expand...
Click to collapse
OHHH i was worried that the error messages were meaning that my phone needed to be re-flashed or something i am redownloading the OTA update now and I will try and install it, i will re post when its done. I didnt remove any bloatware from the stock rom, it is completely stock, all that is changed is I updated it to sense 4.1 then there was a minor update that said it had a few bug fixes and some power improvements
:thumbup:
Mr Hofs said:
:thumbup:
Click to expand...
Click to collapse
i was also wondering if you might know, when i updated to sense 4.1, it completely wiped my "sd card", all my files were gone except from the default ones, was that meant to happen?
Euhm well i can't recall really, at least when i went from 4.0.4 to 4.1 it certainly did not wipe my sdcard.
And i can't really say if it wipes the phone blank because i updated from a clean stock rom without any extra apps on it
But beware the chance is big that it will indeed puts the phone to a stock JB rom
Mr Hofs said:
Euhm well i can't recall really, at least when i went from 4.0.4 to 4.1 it certainly did not wipe my sdcard.
And i can't really say if it wipes the phone blank because i updated from a clean stock rom without any extra apps on it
But beware the chance is big that it will indeed puts the phone to a stock JB rom
Click to expand...
Click to collapse
oh ok, no problem. So i just downloaded and attempted to install the OTA for jellybean, in the bootloader it got to about 1/4 then came up with the red triangle. I then pressed the volume up and power button and it showed me what happened, this is in order
finding update package...
opening update package...
verifying update package...
installing update...
copying fotaboot to /data/system for customize reload...
verifying current system...
assert failed: apply_patch_check("/system/lib/libGLESv1_CM.so". "edc4c7834196831836c73d0374529a0278c". a52756f5a63c9827632587d025ee28f67739bd97")
E:error in /interna;_sdcard/download/OTA_ENDEAVOR_U_JB_45_s_Optus_AU_3.14.980.27-2.17.980.6_release_299170pamoph3dsqv4a19a.zip
(status 7)
installation aborted.
Any ideas on whats the problem?
Hmm no don't know that error code, did you install some other boot.img (a custom one) like one with sweep to wake feature or such ?
It goes wrong at patching, so my guess its rom related
Can you do these fastboot commands
Fastboot getvar version-main
and
Fastboot oem readcid
Post them please.....
You van try this one more time, reboot the phone and check the download folder with a Explorer app like es file explorer. If there is the OTA file, delete it and try once more
Mr Hofs said:
Hmm no don't know that error code, did you install some other boot.img (a custom one) like one with sweep to wake feature or such ?
It goes wrong at patching, so my guess its rom related
Can you do these fastboot commands
Fastboot getvar version-main
and
Fastboot oem readcid
Post them please.....
You van try this one more time, reboot the phone and check the download folder with a Explorer app like es file explorer. If there is the OTA file, delete it and try once more
Click to expand...
Click to collapse
Ok my version main is 2.17.980.6 and my CID is OPTUS001, as for the boot image, it is the one that i used for my stock rom back when it was still sense 4.0
Another option is if it keeps on failing ! (Because i really am starting to think that the rom is not completely stock, wether you know it or not)
Download the corresponding nandroid backup here
http://forum.xda-developers.com/showthread.php?t=1975140
Its there i just checked.......
Flash back the custom recovery (this one)
http://db.tt/Krlm4dPs
Rename it to recovery.img and flash it with fastboot command
Fastboot flash recovery recovery.img
Fastboot erase cache
Then copy the boot.img from that nandroid and flash it also
Fastboot flash boot boot.img
Enter the recovery and do a full wipe, except sdcard
Mount the sdcard as a usb drive in the recovery and copy the nandroid to the phones sdcard looking like this
Clockworkmod\backup\date and time folder\backup files from the nandroid
Then restore the nandroid and reboot to check if the rom boots up ....
after that you flash the 2.17 stock recovery back and you can update again.
This way you are 100% stock ! :thumbup:
I'm off to bed now, going for a holiday but i will check in on how you are doing sometime in the morning......the last method i described can't go wrong ! When the update fails after that then there is something serious wrong with the phone or a longshot ..... the OTA from the carrier is corrupted somehow
Mr Hofs said:
Another option is if it keeps on failing ! (Because i really am starting to think that the rom is not completely stock, wether you know it or not)
Download the corresponding nandroid backup here
http://forum.xda-developers.com/showthread.php?t=1975140
Its there i just checked.......
Flash back the custom recovery (this one)
http://db.tt/Krlm4dPs
Rename it to recovery.img and flash it with fastboot command
Fastboot flash recovery recovery.img
Fastboot erase cache
Then copy the boot.img from that nandroid and flash it also
Fastboot flash boot boot.img
Enter the recovery and do a full wipe, except sdcard
Mount the sdcard as a usb drive in the recovery and copy the nandroid to the phones sdcard looking like this
Clockworkmod\backup\date and time folder\backup files from the nandroid
Then restore the nandroid and reboot to check if the rom boots up ....
after that you flash the 2.17 stock recovery back and you can update again.
This way you are 100% stock ! :thumbup:
I'm off to bed now, going for a holiday but i will check in on how you are doing sometime in the morning......the last method i described can't go wrong ! When the update fails after that then there is something serious wrong with the phone or a longshot ..... the OTA from the carrier is corrupted somehow
Click to expand...
Click to collapse
i did everything on the list, but when it boots up, it goes past the optus logo, then does that little HTC one x animation, then stays on theat screen
Then you didn't do a full wipe, did u also wiped the dalvik cache ?
And flashed the correct boot.img from the nandroid backup ? Did it confirm that flashing was oke
And for how long did u wait already, when it changed to that screen ? May take a while
You can't flash an OTA manually, you have to get it booting with the nandroid backup and then replace CWM with the stock recovery and then relock the bootloader to get the OTA (relock might not be needed but I would do it just in case)
EddyOS said:
You can't flash an OTA manually, you have to get it booting with the nandroid backup and then replace CWM with the stock recovery and then relock the bootloader to get the OTA (relock might not be needed but I would do it just in case)
Click to expand...
Click to collapse
Look 2 posts above and the 4th post
Mr Hofs said:
Then you didn't do a full wipe, did u also wiped the dalvik cache ?
And flashed the correct boot.img from the nandroid backup ? Did it confirm that flashing was oke
And for how long did u wait already, when it changed to that screen ? May take a while
Click to expand...
Click to collapse
ok, first i flashed the boot.img, then i did a factory reset from clockwork mod, then i wiped the cache partition, then i wiped the dalvik cache, i tried restoring it again, everything goes fine, but when i boot up it just does a bootloop, it seems theres something wron with the boot.img
Mr Hofs said:
Look 2 posts above and the 4th post
Click to expand...
Click to collapse
umm.........i just realised something..........what version of HBoot am i meant to have? or does it not matter? because mine is crrently 1.12 and ive been reading that for jellybean roms you need newer
Thats very strange ! One problem I had a while back was that the nandroid was not properly copied to the sdcard ! Can you check if the nandroid folder on the phone is the same size as the nandroid you downloaded to the computer. The nandroid actually restored itself but it also went in a bootloop......the guy was 2 days busy already to get it straight !!!
---------- Post added at 01:00 PM ---------- Previous post was at 12:51 PM ----------
When you are on HBoot 1.12 you can only flash ics roms, but i assume you are restoring the 2.17 based nandroid with the same cid as yours ? 2.17 is the ics based version that belongs to your hboot
Mr Hofs said:
Thats very strange ! One problem I had a while back was that the nandroid was not properly copied to the sdcard ! Can you check if the nandroid folder on the phone is the same size as the nandroid you downloaded to the computer. The nandroid actually restored itself but it also went in a bootloop......the guy was 2 days busy already to get it straight !!!
Click to expand...
Click to collapse
yep theyre both the same size :/ i was wondering would my bootloader have to be locked to get the OTA on my stock rom that was working? and also would trying out the RUU method http://forum.xda-developers.com/showthread.php?t=2054979 here be a good idea? that too says the bootloader should be locked
Hello to everyone.
I was having custom ICS rom, when I found out that there is OTA to JB for my HOX. So I reverted to stock using RUU method and got the OTA update. I had the stock JB rom. I made the nandroid backup and wanted to flash custom JB rom (ViperX Rom). I unlocked my bootloader again, got custom recovery (CWM 5.8.4.0). Then I flashed the boot.img from the rom's zip package and erased cache. I made a full wipe using CWM. Then, using recovery I flashed the custom rom (Viper). The whole process went without any problems, but after rebooting I got stuck oh the white htc logo.
Reverting to stock using my backup ended up on the white logo again. I cannot flash any rom (tried Sense and CM roms) coz every time I got that f...g white screen.
My bootloader is unlocked, hboot 1.36, S-ON model. Custom recovery (CWM 5.8.4.0). I've been trying for four days to get my HOX back to life.
Can anyone, please help me with that.
I don't know what's wrong with your phone, but if you just want to revert back to your backed up ROM, try flash boot from your backup first, and then restore backup. Or try reinstall RUU, maybe...
Die you use the right command for flashing the boot.img ?
Fastboot flash boot boot.img
and NOT
Fastboot boot boot.img ?
TommY.KillER said:
I don't know what's wrong with your phone, but if you just want to revert back to your backed up ROM, try flash boot from your backup first, and then restore backup. Or try reinstall RUU, maybe...
Click to expand...
Click to collapse
I tried to flash the stock boot.img before restoring backup - with no luck
I cannot reinstal RUU, coz I cannot find one, ie RUU 3.16.69.2 (if I am right).
@Mr Hofs
Yes, I used the proper command: fastboot flash boot boot.img and erased cache. It seems that I do everything right, but I still get the bootloop.
Oke, so now the bootloader is unlocked ?
Re-copy the boot.img file from the nandroid folder to the fastboot folder...just to be sure
Flash it with fastboot command and enter the recovery
Then
Wipe data/factory reset
Wipe cache partition
Advanced - wipe dalvik cache
Mounts & storage - format cache, data, system
Then restore the nandroid again !
Sent from my HTC One X using xda premium
Mr Hofs said:
Oke, so now the bootloader is unlocked ?
Re-copy the boot.img file from the nandroid folder to the fastboot folder...just to be sure
Flash it with fastboot command and enter the recovery
Then
Wipe data/factory reset
Wipe cache partition
Advanced - wipe dalvik cache
Mounts & storage - format cache, data, system
Then restore the nandroid again !
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Did what you said. Still nothing
bartdeli said:
Did what you said. Still nothing
Click to expand...
Click to collapse
hmmm so all the steps are covered, could you do me a favour ? flash a new custom ICS rom from scratch....sounds stupid but i had a case a while back that had the updated hboot but also got several errors ....
Mr Hofs said:
hmmm so all the steps are covered, could you do me a favour ? flash a new custom ICS rom from scratch....sounds stupid but i had a case a while back that had the updated hboot but also got several errors ....
Click to expand...
Click to collapse
Hey, you are THE MAN. Seems to be working. I am on viper 2.6 now!!!
What now?
Give me your main version number
Fastboot getvar version-main
Sent from my HTC One X using xda premium
Mr Hofs said:
Give me your main version number
Fastboot getvar version-main
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
2.17.69.2 - I have that RUU if that's what you mean
Yes but the ruu is crap because you already have the 1.36 hboot. Try this
Do a full wipe again and get your 2.17.69 nandroid from here
http://forum.xda-developers.com/showthread.php?t=1975140
Restore it with its boot.img
Then flash back this 2.17 stock recovery
http://db.tt/U5CK4noo
And start updating again and again .....
Mr Hofs said:
Yes but the ruu is crap because you already have the 1.36 hboot. Try this
Do a full wipe again and get your 2.17.69 nandroid from here
http://forum.xda-developers.com/showthread.php?t=1975140
Restore it with its boot.img
Then flash back this 2.17 stock recovery
http://db.tt/U5CK4noo
And start updating again and again .....
Click to expand...
Click to collapse
OK. Will start tomorrow (or today in the morning, coz it's after midnight )
Thank you for your help so far.
No problem ! I hope to see some good news tomorrow
Sent from my HTC One X using xda premium
Mr Hofs said:
No problem ! I hope to see some good news tomorrow
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
I cannot revert to stock recovery. I got an error: cannot load "recovery.img"
My command was fastboot flash recovery recovery.img. The file is in the fastboot folder.
When I was trying to get back to stock for the first time I also had that error. That is why I had to use the RUU to revert to stock.
What now?
did you rename my file to recovery.img ?
Mr Hofs said:
did you rename my file to recovery.img ?
Click to expand...
Click to collapse
yes
are you hiding extensions in windows for the filenames, so that it's not called
recovery.img.img ? seen that problem also before !
Mr Hofs said:
are you hiding extensions in windows for the filenames, so that it's not called
recovery.img.img ? seen that problem also before !
Click to expand...
Click to collapse
No, I do not hide the extensions. I can see the extensions for all the files.
My fastboot folder below.
Ow yeah i see, what could be the problem here ?!
Does the nandroid work ? Except for the stock recovery ?
Try this ... enter the recovery and wipe the cache partition and dalvik cache ....
Then reboot into the bootloader
Adb reboot bootloader (works when you are in recovery)
Keep the phone there and reboot the pc and try again .....
Mr Hofs said:
Ow yeah i see, what could be the problem here ?!
Does the nandroid work ? Except for the stock recovery ?
Try this ... enter the recovery and wipe the cache partition and dalvik cache ....
Then reboot into the bootloader
Adb reboot bootloader (works when you are in recovery)
Keep the phone there and reboot the pc and try again .....
Click to expand...
Click to collapse
yes, I am on stock with custom recovery.
That "adb reboot bootloader" shall I write in cmd in fastboot usb?
hi i realise there are soo many threads on this but not quite similar to my situation. my bootloader is unclocked with CWM and when it came to flashing a new rom i installed the .zip then flashed the rom but didnt have enough battery no i cant flash any boot.img and my HOX wont charge however i do have a nandroid backup from a few minutes before i installed the rom but it doesnt work, i dont have a windows pc so i cant run the .bat file that restarts your phone any help would be greatly appreciated
benny_w95 said:
hi i realise there are soo many threads on this but not quite similar to my situation. my bootloader is unclocked with CWM and when it came to flashing a new rom i installed the .zip then flashed the rom but didnt have enough battery no i cant flash any boot.img and my HOX wont charge however i do have a nandroid backup from a few minutes before i installed the rom but it doesnt work, i dont have a windows pc so i cant run the .bat file that restarts your phone any help would be greatly appreciated
Click to expand...
Click to collapse
It should charge in recovery
nogotaclue said:
It should charge in recovery
Click to expand...
Click to collapse
well this is a bit of a problem because i have CWM 5.8.2.7 and from what i have read i doesnt support charging in recovery mode, my phone doesnt charge in recovery mode anyway
Power down the phone from the bootloader menu. Charge it a bit and flash a new recovery
Mr Hofs said:
Power down the phone from the bootloader menu. Charge it a bit and flash a new recovery
Click to expand...
Click to collapse
thanks so much didnt even think that it would charge when it was off but i flashed the new CWM but i am also faced with another problem, when i reboot after restoring from nandroid it doesnt boot the same happens when i install a new rom even though i know i am installing them properly just wondering if there is anything i can do
benny_w95 said:
thanks so much didnt even think that it would charge when it was off but i flashed the new CWM but i am also faced with another problem, when i reboot after restoring from nandroid it doesnt boot the same happens when i install a new rom even though i know i am installing them properly just wondering if there is anything i can do
Click to expand...
Click to collapse
Flashed the boot.img from the rom or the nandroid backup ???
What is your hboot number. Usually when you have that old recovery the hboot needs an update too
Give me the outcome of
Fastboot getvar version-main
Mr Hofs said:
Flashed the boot.img from the rom or the nandroid backup ???
What is your hboot number. Usually when you have that old recovery the hboot needs an update too
Give me the outcome of
Fastboot getvar version-main
Click to expand...
Click to collapse
ah so my hboot is 1.39.000 if thats what your after but yeah when i tired to restore a nandroid backup i got stuck in loop. i also tried flash 3 other roms to my device and it got the same result however i managed to flash a version of leedroid so should be good for now
Strange.......
Performed a real good full wipe before installing the rom ?
benny_w95 said:
ah so my hboot is 1.39.000 if thats what your after but yeah when i tired to restore a nandroid backup i got stuck in loop. i also tried flash 3 other roms to my device and it got the same result however i managed to flash a version of leedroid so should be good for now
Click to expand...
Click to collapse
the result from getvar version-main was 3.17.728.1 by the way
I also have the same base and it's the latest... if you want to go stock then there's a nandroid backup available : http://d-h.st/7oA
Unfortunately, no RUU available for us...
Make sure you do 'fastboot erase cache' each time after flashing something via fastboot to rectify booting issues!
Hi all. I just bought this phone and for some reason it comes with the bootloader unlocked and a custom software. I was unable to update my phone so i was searching here and over there. Mr Hofs from this forum gave me some advices which i will quote.
My phone data is readcid: HTC__622
Fastboot getvar version-main : 3.14.708.28
He suggested me to: 1: download this RUU RUU_ENDEAVOR_U_JB_45_S_hTC_Asia_HK_3.14.708.28_Radio_5.1204.162.29_release_299865_signed.exe
2: charge the battery to 100%
3: put the phone in the bootloader and relock it (if it is unlocked)
Fastboot oem lock
4: keep the phone in the relocked bootloader
5: right click on the ruu and select "run as administrator"
6: follow on screen info (phone and pc)
7: fingers crossed
8: back to stock it is
But the procces failed, it said i had to dowload the proper version and signed. Now my phone is stuck in the bootloader which is relockked. Please help me getting this back to life.
Thanks in advanced.
By some reason I can't explain, the phone came with the software called Android Revolution 6 by mike1986 :/
Try running this RUU from a different PC, it should work if your bootloader is locked! This is the correct RUU for your phone!
However, if you still can't get to your OS, then restore a nandroid backup via recovery!
Download this nandroid backup : https://docs.google.com/file/d/0BwEZB8sRo0DSdTRrN3FSSk5fUE0/edit?pli=1
Recovery : http://htcfanboys.com/download/seadersn/?action=list&file=4944
Now firstly unlock your bootloader
Code:
fastboot flash unlocktoken unlock_code.bin
Now flash the recovery you had just downloaded...(rename it to recovery.img)
Code:
fastboot flash recovery recovery.img
fastboot erase cache
Now boot into recovery and go to mounts and storage and mount USB. Copy the files of the nandroid backup zip to /clockworkmod/backup/ and paste it there...
Transfer the boot.img into the fastboot folder, boot into fastboot USB and flash the boot.img
Code:
fastboot flash boot boot.img
fastboot erase cache
Now go back to recovery and wipe data/cache partition/dalvic
Now go to Back up and restore and restore the nandroid backup you had just copied to your phone! and then REBOOT!
---------- Post added at 01:01 PM ---------- Previous post was at 12:58 PM ----------
If you want to go full stock to receive OTA updates, then you also need to flash the stock recovery.. Download this : https://www.dropbox.com/s/ms7vd18vb9watr8/stock recovery 3.14.img
boot into fastboot mode and flash the recovery and then lock your bootloader!
Thanks for your reply, but which RUU? Seems like you forgot the link.
My bootloader doesnt say locked, it say relocked. Is the same?
Thanks so much for your help.
By the way. I have downloaded the Android SDK but it wont install at all.
Edited: I've tried with the same ruu in other PC and nothing.
Maybe its because it had a custom rom? It came with Android Revolution 6 or someting
CM17X said:
Thanks for your reply, but which RUU? Seems like you forgot the link.
My bootloader doesnt say locked, it say relocked. Is the same?
Thanks so much for your help.
By the way. I have downloaded the Android SDK but it wont install at all.
Edited: I've tried with the same ruu in other PC and nothing.
Maybe its because it had a custom rom? It came with Android Revolution 6 or someting
Click to expand...
Click to collapse
I meant to say that the RUU given by Mr Hofs is correct one for your device! It should work...
Yes, relocked = locked bootloader...
Don't download the whole android sdk... you just need the fastboot folder and HTC Sync Manager (for the drivers) to run fastboot commands:
Here are the links:
Fastboot folder: http://d-h.st/8Jr
HTC Sync Manager: http://www.htc.com/www/support/software/htc-sync-manager.aspx
Nope, regardless of the rom your currently on, the RUU will work.. Don't know why your not able to finish it... Hmmm
I dont know. It just wont work
Im finishing downloading the files you suggestted me but i have a doubt in the step when you say to wipe the cache. How? From the phone or by deleting its contect on PC?
I'm a dumb, i know :/
Thanks for help me
vin4yak said:
I meant to say that the RUU given by Mr Hofs is correct one for your device! It should work...
Yes, relocked = locked bootloader...
Don't download the whole android sdk... you just need the fastboot folder and HTC Sync Manager (for the drivers) to run fastboot commands:
Here are the links:
Fastboot folder:
HTC Sync Manager:
Nope, regardless of the rom your currently on, the RUU will work.. Don't know why your not able to finish it... Hmmm
Click to expand...
Click to collapse
CM17X said:
I dont know. It just wont work
Im finishing downloading the files you suggestted me but i have a doubt in the step when you say to wipe the cache. How? From the phone or by deleting its contect on PC?
I'm a dumb, i know :/
Thanks for help me
Click to expand...
Click to collapse
Go to your custom recovery(CWM) and select
Wipe Cache Partion>Wipe Cache
Wipe Data/factory reset>Wipe data
Advanced>Wipe dalvic cache>Wipe dalvic
In the first step, it says "cant upload unlock_code.bin" Where is that file?
What i did was place the recovery.img into the fastboot folder
CM17X said:
In the first step, it says "cant upload unlock_code.bin" Where is that file?
What i did was place the recovery.img into the fastboot folder
Click to expand...
Click to collapse
Oh ohkk You got your phone with bootloader unlocked right? Skip that step! Go on with the next one!
If your bootloader is locked then you will have to go to htcdev.com and register there and follow the steps to unlock your bootloader. You will get a file via email (unlock_code.bin)... flash that to unlock your bootloader!
vin4yak said:
Oh ohkk You got your phone with bootloader unlocked right? Skip that step! Go on with the next one!
If your bootloader is locked then you will have to go to htcdev.com and register there and follow the steps to unlock your bootloader. You will get a file via email (unlock_code.bin)... flash that to unlock your bootloader!
Click to expand...
Click to collapse
Kinda late. I managed to get the unlocker.bin file and i unlocked it again and my phone is back to life. HOW CAN I KISS YOU?
I will wait for it to charge at 100 and then i will follow the steps.
What should i do next? THANKS SO MUCH FOR YOUR HELP (Also Mr Hofs)
CM17X said:
Kinda late. I managed to get the unlocker.bin file and i unlocked it again and my phone is back to life. HOW CAN I KISS YOU?
I will wait for it to charge at 100 and then i will follow the steps.
What should i do next? THANKS SO MUCH FOR YOUR HELP (Also Mr Hofs)
Click to expand...
Click to collapse
ah! Great! Your phone is booting to OS now right? ARHD? or have you back on stock??
vin4yak said:
ah! Great! Your phone is booting to OS now right? ARHD? or have you back on stock??
Click to expand...
Click to collapse
Is into the OS right now. Ill follow the steps for put it back to stock with the nandroid backup. May i?
Hi guys ! Don't know what's happening with the ruu's these days. Getting a lot of issues with people who run them. Its a driver/HTC sync problem somewhere !
But yeah try the nandroid backup thing. That should work
Say a prayer for me, please, gonna try!
Mr Hofs said:
Hi guys ! Don't know what's happening with the ruu's these days. Getting a lot of issues with people who run them. Its a driver/HTC sync problem somewhere !
But yeah try the nandroid backup thing. That should work
Click to expand...
Click to collapse
CM17X said:
Say a prayer for me, please, gonna try!
Click to expand...
Click to collapse
Burning a candle
CM17X said:
Is into the OS right now. Ill follow the steps for put it back to stock with the nandroid backup. May i?
Click to expand...
Click to collapse
Yes you may... :silly:
Mr Hofs said:
Burning a candle
Click to expand...
Click to collapse
loolllllllll
Something is wrong.
I have placed the files which are into the nadroid backup into clockwork/backup, not the package itself, and after wip the cache and stuff, i tried to restore but nothing happens, it just put me back in the sme menu.
Now the phone is locked in the Android logo :/ What should i do?
Mr Hofs said:
Hi guys ! Don't know what's happening with the ruu's these days. Getting a lot of issues with people who run them. Its a driver/HTC sync problem somewhere !
But yeah try the nandroid backup thing. That should work
Click to expand...
Click to collapse
vin4yak said:
Yes you may... :silly:
loolllllllll
Click to expand...
Click to collapse
The folder on the sd should look like this
Clockworkmod\backup\*time and date folder*\all separate backup files
By time and date you mean 2013-01-08.00.15.16 3.14.708.28_cwm_root ?
I messed it up, i did Clockworkmod\backup\all separate files.
Now the phone is stuck in android logo. What should i do?
Mr Hofs said:
The folder on the sd should look like this
Clockworkmod\backup\*time and date folder*\all separate backup files
Click to expand...
Click to collapse
Ah go back into the recovery
Factory reset
Wipe cache partition
Advanced - wipe dalvik cache
Mounts & storage - format cache,data,system
Then restore the nandroid
Haha, sorry for the noob questions, I had to learn android stuff in 2 hours due the rush thinking I was getting a brick.
The phone is working now, thank you so much, guys.
Only strange things are that I don't have more languages than Taiwanese and English, not Spanish (system language); also the nandroid was rooted and I have root now, and the splash screen says "HTC one" lol
Again, you're the best. Thanks for help me out, ill see you around while learning
Sent from my HTC One X using Tapatalk 2
I've unlocked my Three (3) branded M8, installed TWRP and rooted my device (I've also tried out MaximusHD Rom, but decided to restore my original ROM from recovery as I couldn't get some software to load with it).
Three are now pushing out the updates for the M8 and I've tried to install it but it fails. Could someone tell me what I need to do? Back on my One X i needed to re-install stock recovery and re-lock the bootloader. Will I need to do this also?
Only flash the stock recovery if you can get one. Relocking the bootloader is not needed.....
Mr Hofs said:
Only flash the stock recovery if you can get one. Relocking the bootloader is not needed.....
Click to expand...
Click to collapse
Thanks. I'll try that now. So I am guessing once, I've completed doing that. I can then re-flash the TWRP and I'll probably need to root the phone again. Will let you know how it goes. There is a stock recovery that someone posted previously.
What you said worked perfectly, and funny enough I got the original stock recovery from your Thread. Can I ask how I would go about getting a backup of my current recovery now that I've updated my phone?
I tried what you mentioned in your thread about fastboot boot recovery recovery-name.img (yes i did put the recovery name in) but just got an error stating "cannot load 'recovery'".
Thanks for all your help.
Update: I notice that I can still boot into the system and have root even though I'm on the stock recovery, as if I go into Recovery I end up with the HTC Phone and red triangle. Does this mean there is no real reason for me to re-install TWRP? As all I really cared about was having Root.
What you have now is the stock rom and recovery + root. No reason to flash a custom one if you don't want to flash any mods or themes.
To create a new backup you can put the custom recovery in the fastboot folder and indeed perform the command :
Fastboot boot recovery recoveryname.img
If it can't load the recovery you either typed the wrong recovery name or it's not in the fastboot folder. And the f you have a stock nand to share in my thread would be awesome !
Mr Hofs said:
What you have now is the stock rom and recovery + root. No reason to flash a custom one if you don't want to flash any mods or themes.
To create a new backup you can put the custom recovery in the fastboot folder and indeed perform the command :
Fastboot boot recovery recoveryname.img
If it can't load the recovery you either typed the wrong recovery name or it's not in the fastboot folder. And the f you have a stock nand to share in my thread would be awesome !
Click to expand...
Click to collapse
Note that the command is fastboot boot recovery.img
The 'recovery' command will not register. I did it last night
Also, for future reference, I can perform a factory reset with the stock recovery and it will return me to stock even if I have rooted my device? I elected not to install TWRP, but instead just run it temporarily so that I could root leaving my stock recovery intact. Seems like a pretty straightforward answer which is 'yes' but just want to clarify. I have the stock ROM installed (AT&T)
Fastboot boot recovery recovery.img
Yes that's what i wrote right ?
Can you elaborate more on the not registered part ?
And yes factory reset will set it back to stock. Not sure if it will delete root. But all accounts and data will be gone !
Mr Hofs said:
Fastboot boot recovery recovery.img
Yes that's what i wrote right ?
Can you elaborate more on the not registered part ?
And yes factory reset will set it back to stock. Not sure if it will delete root. But all accounts and data will be gone !
Click to expand...
Click to collapse
You wrote: fastboot boot recovery recovery.img
The command is: fastboot boot recovery.img (You do not need to specify the 'recovery' before 'recovery.img')
And by not register I suppose I just mean its an unknown command if you specify a partition/kernel before the 'recovery.img' portion. I'm not sure if I'm using the vocabulary correctly
TheEmpyre said:
You wrote: fastboot boot recovery recovery.img
The command is: fastboot boot recovery.img (You do not need to specify the 'recovery' before 'recovery.img')
And by not register I suppose I just mean its an unknown command if you specify a partition/kernel before the 'recovery.img' portion. I'm not sure if I'm using the vocabulary correctly
Click to expand...
Click to collapse
Ah i see the mistake, thank you....was overlooking that part !
Mr Hofs said:
Ah i see the mistake, thank you....was overlooking that part !
Click to expand...
Click to collapse
No problem I meant no disrespect! I was actually surprised you don't need to specify the partition for a temporary image....From my research it looks like they have may have changed that fastboot command from Android 4.3
TheEmpyre said:
No problem I meant no disrespect! I was actually surprised you don't need to specify the partition for a temporary image....From my research it looks like they have may have changed that fastboot command from Android 4.3
Click to expand...
Click to collapse
haha disrespect ? no no all oke, i was wrong and you where right....you corrected me and thats great ! I also have to learn :good:
Mr Hofs, in my scenario where I have returned to stock recovery, installed the update from three. How would I go about backing up my current recovery? I've tried what you have done in your thread but there is no recovery file in the back up.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Yeah that's a strange thing. The backup from fisha21 didn't have a recovery either yet the ones made by guywithdesire1992 did have ?! I'm confused about that ! Can you check certain options in twrp maybe ?
Okay, will make a back up over to my computer and then try again. Will report back.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
gaiden0000 said:
Okay, will make a back up over to my computer and then try again. Will report back.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If it doesn't work you can also try philz touch, see if there is a difference ?
Mr Hofs said:
If it doesn't work you can also try philz touch, see if there is a difference ?
Click to expand...
Click to collapse
Yep did it with Philz touch and it now includes a recovery.img although it's filesize is 21MB compared to the regular ones. But now at least I have a backup of the recovery. Will upload to a location and post on your thread soon.
Thats awesome ! Really appreciate it
So to be clear, you booted philz and made a nandroid. So the recovery should be the stock HTC one ?
One way to check is to flash the recovery.img that's in the backup folder and enter it. If it gives a phone icon its stock