Develop Bugs

[Q] Boot loop after stock recovery TWRP

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

[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] ONE V stuck to boot nt going to recovery also

hiee friendz my htc one v stuck in boot process need help
let me explain problem ----- i rooted my device a month ago installed su and some more apps few days before it stuck so i went in recovery CWM 5.8 and restored every thing goes smoothly and i was happy nut 2-3 days before when it was not showing network so i think to airplane mode on or off but when i changed mode off to on it stuck then i tried to reboot it and problem came out it just stuck in booting (screen stuck htc logo and some red message of legal warning then goes to reboot )
then i tried to restore (as i did few days before )
now actual problem comes it is not going to recovery option then i flashed boot.img and recovery.img but nothing happened so i searched a lot in XDA and tried (Titanum KISS, hellboy, stock kernel and one boot img in my recovery folder and for recovery CWM 6.0 TWRP and some more ) but the problem still cant be solved i tried to stock RUU but due to hboot older version in downloaded RUU.ZIP could not .....
i want permanent solution for this problem because in last two month it happened 2-3 times..... plz solve asap and let me know what is the actual problem ...thanks
and one more thing i tried 2 install PACMAN v23 with boot.img which was in zip file that stats failed in HTC ONE V AIO kit so if i want to try pacman v23 what should i do .........

rakeshc554 said:
hiee friendz my htc one v stuck in boot process need help
let me explain problem ----- i rooted my device a month ago installed su and some more apps few days before it stuck so i went in recovery cwm 5.8 and restored every thing goes smoothly and i was happy nut 2-3 days before when it was not showing network so i think to airplane mode on or off but when i changed mode off to on it stuck then i tried to reboot it and problem came out it just stuck in booting (screen stuck htc logo and some red message of legal warning then goes to reboot )
then i tried to restore (as i did few days before )
now actual problem comes it is not going to recovery option then i flashed boot.img and recovery.img but nothing happened so i searched a lot in xda and tried (titanum kiss, hellboy, stock kernel and one boot img in my recovery folder and for recovery cwm 6.0 twrp and some more ) but the problem still cant be solved i tried to stock ruu but due to hboot older version in downloaded ruu.zip could not .....
I want permanent solution for this problem because in last two month it happened 2-3 times..... Plz solve asap and let me know what is the actual problem ...thanks
and one more thing i tried 2 install pacman v23 with boot.img which was in zip file that stats failed in htc one v aio kit so if i want to try pacman v23 what should i do .........
Click to expand...
Click to collapse
still no help is der nyone to help me >>>>>>

rakeshc554 said:
hiee friendz my htc one v stuck in boot process need help
let me explain problem ----- i rooted my device a month ago installed su and some more apps few days before it stuck so i went in recovery CWM 5.8 and restored every thing goes smoothly and i was happy nut 2-3 days before when it was not showing network so i think to airplane mode on or off but when i changed mode off to on it stuck then i tried to reboot it and problem came out it just stuck in booting (screen stuck htc logo and some red message of legal warning then goes to reboot )
then i tried to restore (as i did few days before )
now actual problem comes it is not going to recovery option then i flashed boot.img and recovery.img but nothing happened so i searched a lot in XDA and tried (Titanum KISS, hellboy, stock kernel and one boot img in my recovery folder and for recovery CWM 6.0 TWRP and some more ) but the problem still cant be solved i tried to stock RUU but due to hboot older version in downloaded RUU.ZIP could not .....
i want permanent solution for this problem because in last two month it happened 2-3 times..... plz solve asap and let me know what is the actual problem ...thanks
and one more thing i tried 2 install PACMAN v23 with boot.img which was in zip file that stats failed in HTC ONE V AIO kit so if i want to try pacman v23 what should i do .........
Click to expand...
Click to collapse
Okay, if you can get into hboot mode please write down the parameters of the phone (like radio hboot etc)
do you use CDMA or GSM OneV?
If you know the CID of the phone write it down too.
If the phone cannot past the bootloader screen (with the red text thing you see) it is most probably kernel problem I think, but want to be sure. Also you MUST NOT install boot.img-s in the ROM zips.

******unlocked****
PRIMOU PVT SHIP S-ON RL
HBOOT-1.18.0000
RADIO-3831.19.00.120
eMMC-BOOT
JUL 2 2012 , 20.51.45
CID HTC-038 INDIA VERSION GSM
DEFAULT STOCK ROM RECOVERY MADE BY CWM 5.8 IF I CAN GO IN RECOVERY THEN WILL BE ABLE TO RESTORE
I THINK THESE ARE ENOUGH OR SHOULD I PROVIDE OTHER INFO
WHAT I HAVE TO DO PLEASE ........

rakeshc554 said:
******unlocked****
PRIMOU PVT SHIP S-ON RL
HBOOT-1.18.0000
RADIO-3831.19.00.120
eMMC-BOOT
JUL 2 2012 , 20.51.45
CID HTC-038 INDIA VERSION GSM
DEFAULT STOCK ROM RECOVERY MADE BY CWM 5.8 IF I CAN GO IN RECOVERY THEN WILL BE ABLE TO RESTORE
I THINK THESE ARE ENOUGH OR SHOULD I PROVIDE OTHER INFO
WHAT I HAVE TO DO PLEASE ........
Click to expand...
Click to collapse
NO one is der to help me out ....................................................................................

rakeshc554 said:
NO one is der to help me out ....................................................................................
Click to expand...
Click to collapse
OK I suggest you download the latest version of Shpongled by IceBox, and either the iron man kernel or the latest Hellboy kernel. It is important that you download the most recent versions of all of these so we can skip version incompatibility problems. Feel free to take your pick of the recovery you want to use from the latest releases on the forum, so long as it is for the PrimoU phone.
Next boot into the boot loader then fastboot
fastboot flash boot boot.img
fastboot flash recovery recovery.img
I would do all of this through the cmd menu, but feel free to us the AIO
then try and reboot into recovery
let me know what happens
kind regards

Try re flash the recovery as there might be a problem with recovery partition .. U know how to go to fastboot then flash recovery ... Might help you
Sent from my One V using xda premium

ijayesh said:
Try re flash the recovery as there might be a problem with recovery partition .. U know how to go to fastboot then flash recovery ... Might help you
Sent from my One V using xda premium
Click to expand...
Click to collapse
tried various recovery programs as CWM5.8.4.5/cwm 6.0 twrp but unable to go in recovery mode if i can go there then i can restore from backup and every thing will be fine

mcgi5sr2 said:
OK I suggest you download the latest version of Shpongled by IceBox, and either the iron man kernel or the latest Hellboy kernel. It is important that you download the most recent versions of all of these so we can skip version incompatibility problems. Feel free to take your pick of the recovery you want to use from the latest releases on the forum, so long as it is for the PrimoU phone.
Next boot into the boot loader then fastboot
fastboot flash boot boot.img
fastboot flash recovery recovery.img
I would do all of this through the cmd menu, but feel free to us the AIO
then try and reboot into recovery
let me know what happens
kind regards
Click to expand...
Click to collapse
i downloaded SHpongled by IceBoxbut cannot install because unable to go in recovery where i have to choose option install zip from sd card in other hand i tried iron man kernel/hellboy kernel both recovery CWM 6.0 touch/non touch CWM 5.8.4.8 and twrp but still cant load recovery now when i choose recovery option in bootloder it restart until HTC LOGO and RED TEXT and then it goes to loop no way to go in recovery

rakeshc554 said:
i downloaded SHpongled by IceBoxbut cannot install because unable to go in recovery where i have to choose option install zip from sd card in other hand i tried iron man kernel/hellboy kernel both recovery CWM 6.0 touch/non touch CWM 5.8.4.8 and twrp but still cant load recovery now when i choose recovery option in bootloder it restart until HTC LOGO and RED TEXT and then it goes to loop no way to go in recovery
Click to expand...
Click to collapse
please click on reply and I get a message about that anything happened here, I'm not in front of xda 24/7
The thing you have written down looks more like a bootloader problem for me, first thing you should try to RUU your phone, but as I see you have the 1.18 hboot, so no luck for you, because there is no RUU for that version yet.
Altough you can try to return for stock kernel first and flash latest TWRP recovery then try to install THIS (if you can get than into recovery mode, stock backup for the 1.18 hboot indian V) then go back to bootlader and flash stock recovery (or not)
So it will like this:
-flash the linked kernel (which is the stock for indian 1.18 hboot version) with fastboot command (try to do it without AIO) fastboot flash boot boot.img
-flash twrp also with command prompt: fastboot flash recovery twrp.img or the name that recovery has.
-don't reboot as of yet! type in fastboot erase cache, then fastboot reboot-bootloader
-now try to get into recovery
With this the phone will be absolute stock with a firmware that is compatible with 1.18 indian hboot. Othet then this there is nothing I can probably think of except RUU, but this is out of question for you atm...

Ken-Shi_Kun said:
please click on reply and I get a message about that anything happened here, I'm not in front of xda 24/7
The thing you have written down looks more like a bootloader problem for me, first thing you should try to RUU your phone, but as I see you have the 1.18 hboot, so no luck for you, because there is no RUU for that version yet.
Altough you can try to return for stock kernel first and flash latest TWRP recovery then try to install THIS (if you can get than into recovery mode, stock backup for the 1.18 hboot indian V) then go back to bootlader and flash stock recovery (or not)
So it will like this:
-flash the linked kernel (which is the stock for indian 1.18 hboot version) with fastboot command (try to do it without AIO) fastboot flash boot boot.img
-flash twrp also with command prompt: fastboot flash recovery twrp.img or the name that recovery has.
-don't reboot as of yet! type in fastboot erase cache, then fastboot reboot-bootloader
-now try to get into recovery
With this the phone will be absolute stock with a firmware that is compatible with 1.18 indian hboot. Othet then this there is nothing I can probably think of except RUU, but this is out of question for you atm...
Click to expand...
Click to collapse
bro still dont work m unable to load recovery what to do

rakeshc554 said:
bro still dont work m unable to load recovery what to do
Click to expand...
Click to collapse
It's hard to tell, because without RUU for your phone this can't be resolved easily. This could be a brick as of now in my opinion, the phone isn't in front of me, so it's hard to tell. Only warranty and HTC service is plausible for me ATM.

Ken-Shi_Kun said:
please click on reply and I get a message about that anything happened here, I'm not in front of xda 24/7
The thing you have written down looks more like a bootloader problem for me, first thing you should try to RUU your phone, but as I see you have the 1.18 hboot, so no luck for you, because there is no RUU for that version yet.
Altough you can try to return for stock kernel first and flash latest TWRP recovery then try to install THIS (if you can get than into recovery mode, stock backup for the 1.18 hboot indian V) then go back to bootlader and flash stock recovery (or not)
So it will like this:
-flash the linked kernel (which is the stock for indian 1.18 hboot version) with fastboot command (try to do it without AIO) fastboot flash boot boot.img
-flash twrp also with command prompt: fastboot flash recovery twrp.img or the name that recovery has.
-don't reboot as of yet! type in fastboot erase cache, then fastboot reboot-bootloader
-now try to get into recovery
With this the phone will be absolute stock with a firmware that is compatible with 1.18 indian hboot. Othet then this there is nothing I can probably think of except RUU, but this is out of question for you atm...
Click to expand...
Click to collapse
bro unfotunatly i am able to go in recovery right now but i cannot restore from your back up file plz let me explain how to restore from your back up files
thank you

rakeshc554 said:
bro unfotunatly i am able to go in recovery right now but i cannot restore from your back up file plz let me explain how to restore from your back up files
thank you
Click to expand...
Click to collapse
This is twrp backup, so cannot say a thing because I use cwm, you need to push it to your sd card in a directory for twrp backups (the backup is not made by me, I'm from Europe) then go to recovery and recover or backup button.

[Q] Reverting ROM: Phone gets stuck on bootscreen.

Hi XDA-developers,
Recently, I tried some new ROMs. I started by going from stock to ARHD and then switched over to Cyanogenmod. I now want to revert back to Cyanogenmod, but I've had no luck getting my phone to work. Here's what I have:
My HTC One X runs ClockWorkMod as recovery, I have three nandroid-backups: Stock, ARHD and Cyanogenmod.
I first erased my phone in CWM. I then restored the ARHD nandroid-backup and that completed succesfully. But when I tried to boot up the phone, it got stuck at the boot-screen where the phone says 'One' in big letters. I tried to wipe it again and load the stock ROM but that also got me stuck on the boot-screen. Finally, I tried reflashing the Cyanogenmod nandroid-backup but that gave me a MD5 Mismatch error...
I tried fixing the MD5 error by following this guide: http://forum.xda-developers.com/showthread.php?t=1835914 but got the 'File '*img' not found' error.
Results from fastboot get-var version-main: 3.20.401.1
If you need any additional info, I will try to provide it. Thanks for reading my question. :good:
~Willem

Willemnz said:
Hi XDA-developers,
Recently, I tried some new ROMs. I started by going from stock to ARHD and then switched over to Cyanogenmod. I now want to revert back to Cyanogenmod, but I've had no luck getting my phone to work. Here's what I have:
My HTC One X runs ClockWorkMod as recovery, I have three nandroid-backups: Stock, ARHD and Cyanogenmod.
I first erased my phone in CWM. I then restored the ARHD nandroid-backup and that completed succesfully. But when I tried to boot up the phone, it got stuck at the boot-screen where the phone says 'One' in big letters. I tried to wipe it again and load the stock ROM but that also got me stuck on the boot-screen. Finally, I tried reflashing the Cyanogenmod nandroid-backup but that gave me a MD5 Mismatch error...
I tried fixing the MD5 error by following this guide: http://forum.xda-developers.com/showthread.php?t=1835914 but got the 'File '*img' not found' error.
Results from fastboot get-var version-main: 3.20.401.1
If you need any additional info, I will try to provide it. Thanks for reading my question. :good:
~Willem
Click to expand...
Click to collapse
Did you flash matching boot.img (kernel) after each nandroid backup flash?

hpnxfox said:
Did you flash matching boot.img (kernel) after each nandroid backup flash?
Click to expand...
Click to collapse
No, because I thought the boot.img was flashed with the Nandroid-backup (according to the log that is displayed in CWM).
But I just downloaded a stock Nandroid-backup so I'll extract the boot.img from that and flash it and see if that works!

Willemnz said:
No, because I thought the boot.img was flashed with the Nandroid-backup (according to the log that is displayed in CWM).
But I just downloaded a stock Nandroid-backup so I'll extract the boot.img from that and flash it and see if that works!
Click to expand...
Click to collapse
yes cwm does that but not with one x because of S-ON thing!

hpnxfox said:
yes cwm does that but not with one x because of S-ON thing!
Click to expand...
Click to collapse
Oh, that's why. I have read about S-ON but I don't know anything about it as the One X apparently does not support it. I'll flash corresponding boot.imgs in the future!
My phone works now, I flashed a boot.img from a stock nandroid-backup. Thanks for the fast replies!

Willemnz said:
Oh, that's why. I have read about S-ON but I don't know anything about it as the One X apparently does not support it. I'll flash corresponding boot.imgs in the future!
My phone works now, I flashed a boot.img from a stock nandroid-backup. Thanks for the fast replies!
Click to expand...
Click to collapse
Good to hear! and yes, every rom (or nandroid backup) exchange require also their boot.img flashing!

[Q] Bricked HTC One need help please

So tonight around 6pm EST I noticed that there was a Cyanogen mod nightly for my wife's Verizon htc one. I also noticed that there was an update function so I decided to give it a try. However, I didn't realize I had yet to make a backup of her current ROM. I thought I had done this when I originally rooted the phone... HUGE MISTAKE NUMBER 1. Once the update was flashed it gave me an error and began boot looping. I tried to find the original version of Cyanogen but could not locate it on the device. Since the HTC One doesn't have an SD card and I Don't have the special OTG USB I couldn't get the storage to mount to add a new ROM. After 2 hours of searching I was finally able to Push a ROM to her device but I kept getting an E: Error executing updater binary... <--- this error I researched only to find that I couldn't flash the rom I was trying to lash in the latest TWRP recovery.
ALL I want to do now is to flash a new recovery to the phone so I can install a ROM and get this paperweight working again.
Can someone please explain to me STEP by STEP what to do here?

volumebmx15 said:
So tonight around 6pm EST I noticed that there was a Cyanogen mod nightly for my wife's Verizon htc one. I also noticed that there was an update function so I decided to give it a try. However, I didn't realize I had yet to make a backup of her current ROM. I thought I had done this when I originally rooted the phone... HUGE MISTAKE NUMBER 1. Once the update was flashed it gave me an error and began boot looping. I tried to find the original version of Cyanogen but could not locate it on the device. Since the HTC One doesn't have an SD card and I Don't have the special OTG USB I couldn't get the storage to mount to add a new ROM. After 2 hours of searching I was finally able to Push a ROM to her device but I kept getting an E: Error executing updater binary... <--- this error I researched only to find that I couldn't flash the rom I was trying to lash in the latest TWRP recovery.
ALL I want to do now is to flash a new recovery to the phone so I can install a ROM and get this paperweight working again.
Can someone please explain to me STEP by STEP what to do here?
Click to expand...
Click to collapse
It depends on what you are trying to do. You said you wanted to flash a new recovery, so go ahead and do it.
http://forum.xda-developers.com/showthread.php?t=2416431
If you want to revert back to stock, go ahead and do that too.
http://forum.xda-developers.com/showthread.php?t=2475216
But I say your best bet is to just push a ROM in recovery. Are you S-Off?
Also, what commands are you doing to push a ROM? Is the E: drive where your SDK toolkit located?

Karn101,
What ROM and RECOVERY would you suggest I flash?
I had the TWRP 2.6.3.4 touch recovery installed but for some reason it would not allow me to install the following 2 ROMS
1. Google Edition HTC One VZW [KITKAT]
2. Inverted-EclipticONE-KitKat-v1.2
When I did this I kept getting the E: Error executing updater binary which really had me as a loss.
To answer your question I am S-OFF it says UNLOCKED M7_WLV PVT SHIP S-OFF RH @ the bootloader screen.
HBOOT Version is 1.54.000
Also when I was pushing a ROM I was using some commands I found in a guide here: http://forum.xda-developers.com/showthread.php?t=2354259
I followed some of the steps on here with no luck...
Also I attempted to flash several recoveries from Fast boot with the Fastboot flash recovery recovery.img in the command promt. It shows that the files was sent but the phone just get stuck at the bootloader saying loading recovery at the top in blue font.
Can you walk me through each step on this? I need to get a recovery on there first them push a ROM to the device and install it via the recovery.... I am assuming that would be the easiest method.

If your s-off can't you flash the Ruu in fastboot? Maybe that will help
sent from my JAVA CARD S-OFF FAUX HBOOT BLUE HTC ONE using xda premium app.

Tigerstown said:
If your s-off can't you flash the Ruu in fastboot? Maybe that will help
sent from my JAVA CARD S-OFF FAUX HBOOT BLUE HTC ONE using xda premium app.
Click to expand...
Click to collapse
I suggest this as well.
also
"brick" means phone is dead. you're phone turns on..
not a brick.

what i did once when i couldnt flash RUU was it should work S-On and well Its got to work on S-Off
1-Download TWRP recovery also the System.img and boot.img
2-Rename TWRPRecovery6.3xx.img to Recovery.img
3-Flash recovery in fastboot fastboot flash recovery Recovery.img
4-boot into recovery via fastboot fastboot boot recovery.img
This will boot your device into the custom recovery
5-press Backup
6-swipe to confirm
7-after it's done making a backup
8-navigate back to the home screen
9-press Advanced
10-press Mount
11-check the box next to USB-OTG
This will allow to mount your sdcard into the computer and you can copy the system.img from the RUU
12-open folder TWRP open folder BACKUPS ETC ETC until you get to the folder with the backup you just made
13-delete the system.ext4.win delete the system.ext4.win.md5
14-copy the system.img here abd rename it to
15-system.ext4.win
16-then unmount
17-then navigate back to the home page in the recovery and
18-press Restore
19-then choose that backup and swipe to confirm
20-also recommend fastbooting the boot.img
this is what i did when i couldnt get any rom to flash any roms via recovery nor a i could do a RUU saved my phone.