Develop Bugs

Flashed android rev hd rom 12 now in boot loop!

Flashed android rev hd rom 12 now in boot loop!
I followed the guide and flashed the boot.img first but keeps on boot looping. I have flashed rooms before on previous android phones so have a bit of experience. My version number starts 2.17 maybe I am missing something.
Any help is much appreciated
Thanks

You need to flash the new firmware first. With that you need compatible CID.

If you don´t wanna flash the new firmware use ARHD 9.72.

Hello and thanks for the replies. I may of read the instructions wrong bit I thought it said flash boot img then run superwipe and then flash the rom from CWM. my cid is VODAP001 and wanted the jb Rom. Is 9.7.2 jb? I was thinking of going back to stock ruu but dont think it has been released yet as cannot find my version. When I rooted the phone when it was on stock I made a backup via Rom manager but even when I try to run this in CWM it states files not found!
Sorry to be a pain your help is much appreciated
Sent from my HTC One X using xda app-developers app

Sg231179 said:
Flashed android rev hd rom 12 now in boot loop!
I followed the guide and flashed the boot.img first but keeps on boot looping. I have flashed rooms before on previous android phones so have a bit of experience. My version number starts 2.17 maybe I am missing something.
Any help is much appreciated
Thanks
Click to expand...
Click to collapse
1+ me2 am in bootloop

Your phone is branded and therefore you cannot flash JB Sense ROMs, 9.7.2 is Ice cream sandwich.

u can have jb only when ur operator release it. what for official update from htc for ur model(cid)
now if u have backup of ur stock rom , just restore it. and if it is still bootlooping flash stock kernel modules.

mwanksh takes
faxel said:
u can have jb only when ur operator release it. what for official update from htc for ur model(cid)
now if u have backup of ur stock rom , just restore it. and if it is still bootlooping flash stock kernel modules.
Click to expand...
Click to collapse
thanks for your reply on this. I cannot restore my backup as when I enter CWM recovery either manually or by rom manager and locate the backup I have made it will not restore. When i try to restore it just states files not found!! I have checked on the phone SD storage and it is clearly there but for whatever reason it won't restore. Not sure what else I can do now. If I have to wait for my carrier Vodafone to release the official OTA jellybean update that's fine I will do that no problem, but how can I get back to stock rom? I have checked and there is no official RUU for my version yet so I cannot get back to stock and wait for the official OTA update even if I wanted too.
Maybe I am missing something i'm not sure but if you could help that would be much appreciated
thanks again

Dont Worry!
Just Go to Recovery and mount ur sd card.
Put Someother ROM(ICS) and its boot.img and flash that

aman360elite said:
Just Go to Recovery and mount ur sd card.
Put Someother ROM(ICS) and its boot.img and flash that
Click to expand...
Click to collapse
ya. just like he said if u have custom recovery download a rom like viperX and put it htcstorage (storage card),(Just Go to Recovery and mount ur sd card.)
remember to follow the instruction given by the rom devoloper in his rom thread (how to install rom)

aman360elite said:
Just Go to Recovery and mount ur sd card.
Put Someother ROM(ICS) and its boot.img and flash that
Click to expand...
Click to collapse
Hello
Thanks for your help. Just to clarify, I have the ARHD 9.72 (ICS) ROM on my SD card along with the superwipe that i was advised to run before flashing this ROM. With regards to boot.img it was advised to run this via fastboot type command before then running superwipe and then flashing the rom via CWM. Do i need to perform this boot.img via fastboot command before mounting the SD card and then flashing the ROM?
thanks

Sg231179 said:
Hello
Thanks for your help. Just to clarify, I have the ARHD 9.72 (ICS) ROM on my SD card along with the superwipe that i was advised to run before flashing this ROM. With regards to boot.img it was advised to run this via fastboot type command before then running superwipe and then flashing the rom via CWM. Do i need to perform this boot.img via fastboot command before mounting the SD card and then flashing the ROM?
thanks
Click to expand...
Click to collapse
before going to recovery u have to go fastboot and erase cache and flash the boot,img
phone hboot connect to pc
in pc using cmd type "fastboot flash boot boot.img"(u should keep ur boot.img in fastboot folder)
than type "erase cache"
than go to recovery and mount sdcard. copy rom to it. than flash it after full wipe

faxel said:
before going to recovery u have to go fastboot and erase cache and flash the boot,img
phone hboot connect to pc
in pc using cmd type "fastboot flash boot boot.img"(u should keep ur boot.img in fastboot folder)
than type "erase cache"
than go to recovery and mount sdcard. copy rom to it. than flash it after full wipe
Click to expand...
Click to collapse
thanks for the reply, i will try this yonight when i get home and reply back to you and let you know how i get on if that's ok? I am in work so don't have access to fastboot etc just my phone.
thanks

That's exactly what happened to me two days ago.. flashed the 12.0, then boot looped, then flashed the recovery but the stock rom boot looped too and my pc wouldn't recognize the phone so I adb pushed 9.7.2 and flashed it but it boot looped as well, so what I did was to download HTC SYNC and have the drivers, then flash boot.img first and then flash the rom, still didn't work so I tried the opposite - first flash the rom and only then flash the boot.img, and IT WORKED!!!!!

MaorSwan said:
That's exactly what happened to me two days ago.. flashed the 12.0, then boot looped, then flashed the recovery but the stock rom boot looped too and my pc wouldn't recognize the phone so I adb pushed 9.7.2 and flashed it but it boot looped as well, so what I did was to download HTC SYNC and have the drivers, then flash boot.img first and then flash the rom, still didn't work so I tried the opposite - first flash the rom and only then flash the boot.img, and IT WORKED!!!!!
Click to expand...
Click to collapse
hello, glad to hear it's not just me....and you got sorted out! I will have a go at this tonight. The only concern I do have now though is how I would get back to stock rom if needed to receive OTA Jelly bean update when it is released. I cannot find any RUU for my vodafone UK branded version 2.17 CID VODAP001
THANKS

aman360elite said:
Just Go to Recovery and mount ur sd card.
Put Someother ROM(ICS) and its boot.img and flash that
Click to expand...
Click to collapse
Hello
Just wanted to update you on this issue. I have tried again to restore from my backup saved on the SD card storage but no luck. I went into recovery and mounted the sd card but still whener i try to flash the backup i get 'no files found!'
I have managed to get ARHD 9.7.2 installed at the minute but would prefer stock to get h OTA update do you have any ideas please? I have checked the files in my backup and I have the following but just cannot restore the phone from this backup!
boot.img
nandroid.md5
recovery.img
cache.ext4.tar
data.ext4.tar
system.ext4.tar
Your help is much appreciated

Sg231179 said:
Hello
Just wanted to update you on this issue. I have tried again to restore from my backup saved on the SD card storage but no luck. I went into recovery and mounted the sd card but still whener i try to flash the backup i get 'no files found!'
I have managed to get ARHD 9.7.2 installed at the minute but would prefer stock to get h OTA update do you have any ideas please? I have checked the files in my backup and I have the following but just cannot restore the phone from this backup!
boot.img
nandroid.md5
recovery.img
cache.ext4.tar
data.ext4.tar
system.ext4.tar
Your help is much appreciated
Click to expand...
Click to collapse
Did you changed the name of the folder in any way ?
It must be clockworkmod\backup\the files ....
Verstuurd van mijn HTC One X

MarcelHofs said:
Did you changed the name of the folder in any way ?
It must be clockworkmod\backup\the files ....
Verstuurd van mijn HTC One X
Click to expand...
Click to collapse
hello and thanks for your reply, the details of the backup are as below
clockworkmod/backup/2012-10-30-22.50.49
hope this helps, maybe it's something simple i'm not doing as unsure.
thanks

Sg231179 said:
hello and thanks for your reply, the details of the backup are as below
clockworkmod/backup/2012-10-30-22.50.49
hope this helps, maybe it's something simple i'm not doing as unsure.
thanks
Click to expand...
Click to collapse
ANY help is much appreciated from you guys on this issue. It's doingy head in...got the back up files in CWM/backup folder on sd card i have seen them but cannot flash. CWM appears to show all the folders that are on the sd card so this looks like it is seeing the sd card but when tying to flash recovery I always get the 'file not found' error...everytime!
thanks again

Sg231179 said:
hello and thanks for your reply, the details of the backup are as below
clockworkmod/backup/2012-10-30-22.50.49
hope this helps, maybe it's something simple i'm not doing as unsure.
thanks
Click to expand...
Click to collapse
Ah oké sorry the folder name should be fine ! Somehow corrupted maybe
Verstuurd van mijn HTC One X

[q] not updating through stock recovery

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

[Q] Stuck on the white htc logo :(

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?

[Q] getting back from AOSPA to stock JB

hi all,
i need help getting back to stock rom please.
i have my stock online nandroid backup files tried to flash stock boot.img then proceeding to restore using TWRP 2.4.4 but it fails.
i tried paranoid android 3.10 last night and it looks great with my best feature "swipe to lock/unlock" , unfortunately no wifi , it just can not be turned on, tried another kernel "repacked xm"
and still no wifi and gsm signal,
now i flashed RC19 it is working great , only some issues with notification LED and camera/gallery stability , but i still want to know how to get back to stock.
any help will be appreciated.

Flash the boot.img file from the stock nandroid backup. Enter the recovery and perform a full wipe then restore the backup. Should get you back to stock rom.
Twrp has a different boot.img named boot.emmc.win .....flash it
Fastboot flash boot boot.emmc.win
Fastboot erase cache

Mr Hofs said:
Flash the boot.img file from the stock nandroid backup. Enter the recovery and perform a full wipe then restore the backup. Should get you back to stock rom.
Twrp has a different boot.img named boot.emmc.win .....flash it
Fastboot flash boot boot.emmc.win
Fastboot erase cache
Click to expand...
Click to collapse
thanks, i will try and get back

in the wipe menu i have many choices :
cache - delvik cache - factory reset - system - external storage - android secure
i usually do : cache - delvik cache - factory reset
do i need to do one of the other choices? and why?

I always do all of them except external storage . Just to be sure you have no complications ! There is nothing better then a good cleansweep

still not working, gives me Failed message

Do a fastboot command
Fastboot getvar version-main
Post the outcome please

3.16.415.4

Oke get yourself a new nandroid backup from here
http://forum.xda-developers.com/showthread.php?t=1975140
Its taken with clockworkmod recovery. So flash that first. Look for cwm 5.8.4.0 and flash it. You probably have no touch because of the 3.16 base you are on. Just use the volume and power button.
Download the nandroid and unpack it to the right folder
Clockworkmod\backup\time & date folder\backup files
Then wipe ALL of this
Factory reset
Wipe cache partition
Advanced - wipe dalvik cache
Mounts & storage - format cache, data, system
Restore the nandroid backup and after that you open the command window on the pc and type
adb reboot bootloader (the phone goes from the recovery to the bootloader)
Flash the boot.img from the new nandroid
Fastboot erase cache
Fastboot flash boot boot.img
Fastboot erase cache
Fastboot reboot
This should work fine.

thanks for your great support , one other thing i want to know , how to access the correct directory without having a working system on the device?

ok i managed to access it

Go in the recovery to mounts and storage and select : mount as mass storage device .....it pops up on the pc as a usb diskdrive

Mr Hofs said:
Oke get yourself a new nandroid backup from here
http://forum.xda-developers.com/showthread.php?t=1975140
Its taken with clockworkmod recovery. So flash that first. Look for cwm 5.8.4.0 and flash it. You probably have no touch because of the 3.16 base you are on. Just use the volume and power button.
Download the nandroid and unpack it to the right folder
Clockworkmod\backup\time & date folder\backup files
Then wipe ALL of this
Factory reset
Wipe cache partition
Advanced - wipe dalvik cache
Mounts & storage - format cache, data, system
Restore the nandroid backup and after that you open the command window on the pc and type
adb reboot bootloader (the phone goes from the recovery to the bootloader)
Flash the boot.img from the new nandroid
Fastboot erase cache
Fastboot flash boot boot.img
Fastboot erase cache
Fastboot reboot
This should work fine.
Click to expand...
Click to collapse
hi i have this problem i think. i installed the boot.img via fastboot then in recovery wiped everything then installed the rom and gapps and the wifi just wont turn on. i slide it across and it says turning wifi on but does nothing?

anandyaa98 said:
hi i have this problem i think. i installed the boot.img via fastboot then in recovery wiped everything then installed the rom and gapps and the wifi just wont turn on. i slide it across and it says turning wifi on but does nothing?
Click to expand...
Click to collapse
A nandroid backup NEVER comes together with a install of gapps. Don't know what you are trying to do ? A nandroid backup is restored including flashing the boot.img. that's all to it.

Mr Hofs said:
A nandroid backup NEVER comes together with a install of gapps. Don't know what you are trying to do ? A nandroid backup is restored including flashing the boot.img. that's all to it.
Click to expand...
Click to collapse
i mean i dont want to back up or go to any other rom i just want to fix whatever i have done. so right now ive installed paranoid android and gapps but wifi wont turn on. how do i fix this? sorry if i posted it in the wrong section just kinda panicking .

anandyaa98 said:
i mean i dont want to back up or go to any other rom i just want to fix whatever i have done. so right now ive installed paranoid android and gapps but wifi wont turn on. how do i fix this? sorry if i posted it in the wrong section just kinda panicking .
Click to expand...
Click to collapse
Don't know really ! If you did all you needed to do there should be no problem. What's your hboot number ?
Wipe ALL again. Flash the boot.img from the paranoid rom. Go to the recovery and install the rom.zip and gapps.zip.....then reboot. Otherwise try another rom

i think it is a kernel issue, that's why i tried to repack with xm kernel , but no use, so i flashed RC19.

Mr Hofs said:
Don't know really ! If you did all you needed to do there should be no problem. What's your hboot number ?
Wipe ALL again. Flash the boot.img from the paranoid rom. Go to the recovery and install the rom.zip and gapps.zip.....then reboot. Otherwise try another rom
Click to expand...
Click to collapse
i think its htc001. yeah its what i do for every rom. ive been off my htc for about 4 months so thought there was something to do with the different version of android jelly bean??? i used to be on ARHD18 which worked perfectly. i did what i said above and this happened. ive tried installing miui from ARHD18 and that failed aswell. it had no lockscreen and stuff generally didnt work.
---------- Post added at 12:41 AM ---------- Previous post was at 12:22 AM ----------
Mr Hofs said:
Don't know really ! If you did all you needed to do there should be no problem. What's your hboot number ?
Wipe ALL again. Flash the boot.img from the paranoid rom. Go to the recovery and install the rom.zip and gapps.zip.....then reboot. Otherwise try another rom
Click to expand...
Click to collapse
sorry thats my CID i think. its 1.31. ive seen a hboot on 1.36 should i upgrade to that and try again? does it require a special cwm?

Mr Hofs said:
Oke get yourself a new nandroid backup from here
http://forum.xda-developers.com/showthread.php?t=1975140
Its taken with clockworkmod recovery. So flash that first. Look for cwm 5.8.4.0 and flash it. You probably have no touch because of the 3.16 base you are on. Just use the volume and power button.
Download the nandroid and unpack it to the right folder
Clockworkmod\backup\time & date folder\backup files
Then wipe ALL of this
Factory reset
Wipe cache partition
Advanced - wipe dalvik cache
Mounts & storage - format cache, data, system
Restore the nandroid backup and after that you open the command window on the pc and type
adb reboot bootloader (the phone goes from the recovery to the bootloader)
Flash the boot.img from the new nandroid
Fastboot erase cache
Fastboot flash boot boot.img
Fastboot erase cache
Fastboot reboot
This should work fine.
Click to expand...
Click to collapse
DONE , thanks alot Mr Hofs for your help and knowledge you share with us, i am learning alot from you , appreciate your time

anandyaa98 said:
i think its htc001. yeah its what i do for every rom. ive been off my htc for about 4 months so thought there was something to do with the different version of android jelly bean??? i used to be on ARHD18 which worked perfectly. i did what i said above and this happened. ive tried installing miui from ARHD18 and that failed aswell. it had no lockscreen and stuff generally didnt work.
---------- Post added at 12:41 AM ---------- Previous post was at 12:22 AM ----------
sorry thats my CID i think. its 1.31. ive seen a hboot on 1.36 should i upgrade to that and try again? does it require a special cwm?
Click to expand...
Click to collapse
Do these 2 fastboot commands :
Fastboot getvar version-main
Fastboot oem readcid
Post them back please !
---------- Post added at 05:56 AM ---------- Previous post was at 05:55 AM ----------
teravers said:
DONE , thanks alot Mr Hofs for your help and knowledge you share with us, i am learning alot from you , appreciate your time
Click to expand...
Click to collapse
Thanks mate ! At least one case solved in here now

[Q] My HOX always not respond

Dear all, recently i found my HOX always not response on touch screen, but it works on all button (eg power, volume button). When there is a call coming, it rang but cut the line off.:crying:.
I need to perform several restart and only it backs to normal. I do try flash new rom, format SD card and reset factory setting. None of it help, the issues might come back few days later.:silly:
I really not sure what is the root cause it is. If I send back to repair centre and the problem not appear during that time, they won't do anything i guess.. Could you please help to advise or any of you guys here experience the same issue before? Thanks in advance:good:

Tell us,
Are you on Stock Rom? If yes, then I don't know how to help you, but I'm sure Mr. Hofs will
If No,
1. What ROM are you on?
2. What kernel are you on?
3. Do you have sweep2wake enabled?
4. Have you installed any mods?
5. What is the version of your hboot?
Sent from my HTC One X using xda premium

1. What ROM are you on?
InsertCoin One X Ver 17
2. What kernel are you on?
[email protected]#1 (the one come with ROM)
3. Do you have sweep2wake enabled?
sweep2unlock = Yes
4. Have you installed any mods?
ya, Dougi's Custom LOCKS V.5.2-IC
5. What is the version of your hboot?
1.36.0000
Hope this details help.. thanks

Yep......send it in for warranty repair. If it is happening on different custom roms, and on the original stock rom too then there is nothing we can do. You did all there is to it already.

Mr Hofs, I had not try ori stock ROM yet as I lost my backup when updated to custom ROM.. Haha.. damn!! I see you help a lots of ppl on put back HOX to original stock Rom and maybe I'm might be one of them.
My HOX Version-main: 3.19.401.1 and cid: HTC_044 getting from "CID Getter" Anymore info required for RUU restoration?

I haven't try to restore Original Stock Rom since my backup is gone when I first perform custom ROM. Could you help me on this Mr Hofs for Ruu restoration step?
CID Getter
Version-main: 3.19.401.1
cid: HTC_044
let me know any more info required. Thanks

Get a new 3.14.401 nandroid backup. Don't look at the cids at that point. Not important. Restore the 3.14.401 nandroid and also flash back the 3.14 stock recovery
After that you can update the phone with official ota.
http://forum.xda-developers.com/showthread.php?t=1975140
A 3.19 ruu is not available ! :thumbup:

I getting 3.14.401.31 CID HTC__001 download and try the following as below: let me know if i miss out some step. Thanks
Copy the nandroid backup to the phone Sdcard, copy the boot.img from inside the backup folder to the fastboot folder on the pc. The folder should look like this
Clockworkmod\backup\*date and time folder*\*backup files*
Flash the boot.img with the phone in fastboot usb mode using these commands
Fastboot flash boot boot.img
Fastboot erase cache
Then unplug the cable and enter the recovery, do a full wipe there. Wipe all caches and dalvik cache. Under the advanced button you find - format data, format system, format cache (just wipe it al except sdcard) and even do a factory reset
Then press backup & restore and restore the complete backup
Then reboot the phone to see if it works....confuse at this part... if it does or doesn't? i will need to follow the following step?
I have to put the phone back in fastboot usb mode and flash the stock recovery .....this one
Rename this file into RECOVERY.IMG
phone in fastboot usb menu again and use this command
fastboot flash recovery recovery.img
After this you only have to relock the bootloader with the fastboot command
Fastboot oem lock (ofcourse again with the phone in fastboot usb menu)
Reboot and you have a full stock phone

btw, disable sweep2wake, it works fine for these since yesterday. Will monitor for few more day before back to original stock.. Thanks

pagne666 said:
btw, disable sweep2wake, it works fine for these since yesterday. Will monitor for few more day before back to original stock.. Thanks
Click to expand...
Click to collapse
take a look at this
http://forum.xda-developers.com/showthread.php?p=40070347#post40070347