[Q] Need Help please with strange bootloop problem - One (M7) Q&A, Help & Troubleshooting

A friend has asked me to try and fix there M7 ul. It was. Completely stock on O2 UK. They got a notification for system update (4.4.2 Sense6.0). While installing they left the phone and when they came back it was off. After some fiddling they managed to get it to come on but it would only boot to the bootloader which had Tampered and Locked flags.
This is where I came in so I tried booting to stock recovery to see if the OTA would complete but it was a no go. The screen just stayed black for ages then eventually would show the phone picture with red exclamation. Using volume up+power to get the recovery menu to reset cache returned it to the normal picture with green arrows. But reboot and repeat So I tried fastboot erase cache and attempted ota again with same results.
At this point I told them that anything more I tried may void the warranty so better to send it in but there is no warranty so asked me to do whatever I can. Naturally for me the next step was to unlock the bootloader to regain some control. First I just let the phone boot this time no bootloader screen but it just looped on the HTC splash screen.(i kind of expected that). So next I reboot bootloader and flash twrp2.6.3.3 erase cache and boot recovery. ARHD rom was already in my android folder so pushed it strait over. Ran into some pitfalls trying to flash the rom like instant reboots when flashing started and disappearing zip files fixed with e2fsck, zip failed message fixed with Format data and eventually got the rom installed. I know first boot normally takes a while but this seemed longer than expected but eventually booted the rom and everything seemed to be working fine.
After setting up the basics and testing a few things (installing and running apps. Playing music and so on) I rebooted the phone but again it bootloops on HTC splash screen. Tried everything to get it to boot like wipeing cache/dalvik, dirty flash, clean install even fix permissions nothing worked except Format Data in Twrp Full wipe, re-push rom re-flash rom. Phone took a while but booted and again worked perfectly while setting up and using the phone. So tried restart and again bootloop on HTC splash
So I'm now at a point where I think I've narrowed it down to the Kernel or Ramdisk or atleast the partition there installed on. Since if I use the Superwipe script to wipe only the boot partition cache/dalvik then refresh the boot.img or flash a kernel from recovery (i've been using bulletproof kernel) the phone will boot with the rom and settings intact.
If there is a problem with this partition I do not know how to fix it. I know mmcblk0p33 is the boot partition but is it where the boot.img actually lives or is that the bootloader partition?
If it is the boot.img partition can I repair it with mke2fs or e2fsck or some other tool?
There is an ruu available for the device so if I can just stop the bootloop I could s-off and then ruu and return it to stock. But firewater won't work and I think it's because of the procedure involved in getting the phone to boot is interfering with the push somehow. Firewater will push ok and chmod works but when I try to run firewater nothing happens and then the firewater file disappears and I have to push it again which means re-wipeing and flashing the kernel. I'm really not sure where to go from here any help or suggestions would be most appreciated thanks in advance :fingers-crossed:

Ok so s-off is out of the question since this phone has emmc cid 9001 best I can hope for now is a firmware.zip. I did keep trying firewater and eventually got it to run but sure enough I got Whelp this sucks!!
Would using cwm to format boot be any different to what superwipe dose? It says Format Boot but dose it actually format it or just wipe the data from it? I haven't used cwm since my galaxy ace days.

Danny201281 said:
Ok so s-off is out of the question since this phone has emmc cid 9001 best I can hope for now is a firmware.zip. I did keep trying firewater and eventually got it to run but sure enough I got Whelp this sucks!!
Would using cwm to format boot be any different to what superwipe dose? It says Format Boot but dose it actually format it or just wipe the data from it? I haven't used cwm since my galaxy ace days.
Click to expand...
Click to collapse
you could try a full wipe firmware.zip and HBOOT, you will have to use the one you currently have on the device or the next newer one due to s-on, it will / should re-write your partitions, try looking here:
(searching for link)

Seanie280672 said:
you could try a full wipe firmware.zip and HBOOT, you will have to use the one you currently have on the device or the next newer one due to s-on, it will / should re-write your partitions, try looking here:
(searching for link)
Click to expand...
Click to collapse
Thanks for reply.
Yep I've been looking for a firmware.zip it on 5.12.206.3 all I can find is an ruu.exe but it's the version before. I searched the updates thread and no one seems to have captured the OTA file so can't even extract from there.

Danny201281 said:
Thanks for reply.
Yep I've been looking for a firmware.zip it on 5.12.206.3 all I can find is an ruu.exe but it's the version before. I searched the updates thread and no one seems to have captured the OTA file so can't even extract from there.
Click to expand...
Click to collapse
trouble is, you will need the full firmware, not just an OTA, and the wipe version, usually I see the page with the HBOOTs and firmwares everywhere, do you think I can find it now I need it...........
found it finally, check see if yours is in there, full wipe section: https://docs.google.com/spreadsheets/d/1LQDLpVZYyUpXPgC2sh1BvAS9Oo8B-fTiZU_JhpIH-fU/pubhtml#
---------- Post added at 01:50 PM ---------- Previous post was at 01:40 PM ----------
trouble is too, you cant s-off without a working rom on it, unless you can find someone who can do it by java card for you which is all done from the bootloader.

Seanie280672 said:
trouble is, you will need the full firmware, not just an OTA, and the wipe version, usually I see the page with the HBOOTs and firmwares everywhere, do you think I can find it now I need it...........
found it finally, check see if yours is in there, full wipe section: https://docs.google.com/spreadsheets/d/1LQDLpVZYyUpXPgC2sh1BvAS9Oo8B-fTiZU_JhpIH-fU/pubhtml#
Click to expand...
Click to collapse
Thanks for looking I'll start searching for it now. I hope there's something out there. :fingers-crossed:

Danny201281 said:
Thanks for looking I'll start searching for it now. I hope there's something out there. :fingers-crossed:
Click to expand...
Click to collapse
is it the HTC one ? or the HTC one Mini ?

Danny201281 said:
Thanks for looking I'll start searching for it now. I hope there's something out there. :fingers-crossed:
Click to expand...
Click to collapse
I can get a working rom no problem but it will only boot if I superwipe the boot partition and reflash kernel. Other wise it just bootloops.
But I've already had the whelp this sucks message so no s-off that's why's I need a matching firmware.

Seanie280672 said:
is it the HTC one ? or the HTC one Mini ?
Click to expand...
Click to collapse
HTC one M7_UL

Danny201281 said:
HTC one M7_UL
Click to expand...
Click to collapse
The only RUU I could find is 4.xx.206.xx, you really need s-off to sort it, as you cant use that RUU, there is no RUU for your current version as its all ota's to get to that point, you may have some luck if you can find the next one up which will be 6.06.206.xx.
however, if you are in the UK and can live without your phone for a few days, then give these guys a call, book your phone in with them, and send it to them, they will s-off it by java card and send it back the same day, overall it takes about 3 or 4 days, its who I used, they were very helpful and friendly bunch of guys, best £15 quid ive ever spent.
http://www.fonefunshop.co.uk/Unlocking/htc_s-off_service.htm
---------- Post added at 02:09 PM ---------- Previous post was at 02:01 PM ----------
actually, im over thinking things, have you tried this, it should also re-write your partitions: http://forum.xda-developers.com/showthread.php?t=2770684

Seanie280672 said:
actually, im over thinking things, have you tried this, it should also re-write your partitions: http://forum.xda-developers.com/showthread.php?t=2770684
Click to expand...
Click to collapse
Yes I remember this thread starting up I had considered this but not sure it would work as phone isn't in qhusb dload plus no evidence so far (i've still got some posts to read) it works with s-on. But I'll definitely give it a try if all else fails. Thanks again

Well I don't know if it's from the repeated wiping and flashing of the kernel or what but the phone seems to boot every time without the need to reflash the kernel now. Only it takes about 20mins looping once or twice on the splash screen. Once it gets past that from the boot animation onwards it works flawlessly. I can't get my head around it.

Just to put some closure to this. It's determined to be a hardware problem. Possibly a damaged memory chip. I did manage to return it to stock before handing it back to the owner with the bad news. But it will not boot the stock Rom at all just loops endlessly on the HTC LOGO splash screen.
Case closed
Sent from my HTC One M7 ARHD 71.1 (Minus Purple tint) using TapaTalk

Related

Need help fixing my phone, stuck on htc screen.

Well after installing few games and reflashing my recovery after accidentally putting an older version on, I somehow in turn corrupted my boot loader, system files, data etc, so much so that my backups would boot once but never a second time, clearing my cache and dalvik only made it stuck on htc screen and afterwards it just repeatedly booted into clockwork over and over. This all happening after trying to also make a new nand backup where it hung at system for 30 minutes only to eat up my battery from 100 to 10.
it does charge, I tried using the buttons to boot into fastboot and hboot but it doesn't seem to work, but fastboot usb comes up with I turn it on while connected to the computer but sadly I keep getting error 171 when I try to RUU it.
Have you tried the ruu in zip format??? .
Found here
forum.xda-developers.com/showthread.php?t=804692
#Root/Hack_Mod-Always®
laie1472 said:
Have you tried the ruu in zip format??? .
Found here
forum.xda-developers.com/showthread.php?t=804692
#Root/Hack_Mod-Always®
Click to expand...
Click to collapse
When I try to go into hboot mode I get no change on the screen it stays at the htc logo.
try this then try RUU
http://forum.xda-developers.com/showthread.php?t=843544
il Duce said:
try this then try RUU
http://forum.xda-developers.com/showthread.php?t=843544
Click to expand...
Click to collapse
my doesn't get past htc screen, how would I use that?
gigermunit said:
When I try to go into hboot mode I get no change on the screen it stays at the htc logo.
Click to expand...
Click to collapse
If your not s-off flash darch's eng/spl. Then try the ruu in zip format. Look in hero dev section for darchs method. I posted a working zip on that thread.
Darchs spl s-off
http://forum.xda-developers.com/showthread.php?t=765237
ruu in zip format
http://forum.xda-developers.com/showthread.php?t=804692
#Root/Hack_Mod-Always®
laie1472 said:
If your not s-off flash darch's eng/spl. Then try the ruu in zip format. Look in hero dev section for darchs method. I posted a working zip on that thread.
Darchs spl s-off
http://forum.xda-developers.com/showthread.php?t=765237
ruu in zip format
http://forum.xda-developers.com/showthread.php?t=804692
#Root/Hack_Mod-Always®
Click to expand...
Click to collapse
no recovery to flash a zip.
if you mean something else mind linking me? Ive been searching through xda and ppcgeek along with google since 10am est, it's 3:49pm now.
gigermunit said:
no recovery to flash a zip.
if you mean something else mind linking me? Ive been searching through xda and ppcgeek along with google since 10am est, it's 3:49pm now.
Click to expand...
Click to collapse
I hope you're not making time sensitive demands.....
Try this link and the zip near the end of the thread, if it doesn't work try the other link I put up earlier.
http://forum.xda-developers.com/showthread.php?t=958968
EDIT: are you s-off, and if so which method did you use?
il Duce said:
I hope you're not making time sensitive demands.....
Try this link and the zip near the end of the thread, if it doesn't work try the other link I put up earlier.
http://forum.xda-developers.com/showthread.php?t=958968
Click to expand...
Click to collapse
I'm not and I am having the exact same issues as
http://forum.xda-developers.com/showthread.php?t=788894
I called sprint and was told since I have had the phone for less than a year I can get a free one from htc just need to go to sprint and let them fiddle with it, if they can fix it then it's a free repair if they can't its a free replacement, I am supposing no traces of rooting can even be seen the phone literally has nothing on it, it nuked itself while I went to take a leak, left it on updating 10 applications, backing up the others and flashing my cw3 recovery, after that it was acting up, kept booting to recovery than after flashing things and formatting it nuked everything else recovery and all.
gigermunit said:
I'm not and I am having the exact same issues as
http://forum.xda-developers.com/showthread.php?t=788894
I called sprint and was told since I have had the phone for less than a year I can get a free one from htc just need to go to sprint and let them fiddle with it, if they can fix it then it's a free repair if they can't its a free replacement, I am supposing no traces of rooting can even be seen the phone literally has nothing on it, it nuked itself while I went to take a leak, left it on updating 10 applications, backing up the others and flashing my cw3 recovery, after that it was acting up, kept booting to recovery than after flashing things and formatting it nuked everything else recovery and all.
Click to expand...
Click to collapse
Well, maybe you have a brick. Cool you have the warranty. And if xda can't find a way to fix it, sprint almost surely cannot, lol. I would say get the new one sent to you, that way when you send the old one back it will be too late for them to tell at you - IF they figure it out.
sent from a series of tubes.
il Duce said:
Well, maybe you have a brick. Cool you have the warranty. And if xda can't find a way to fix it, sprint almost surely cannot, lol. I would say get the new one sent to you, that way when you send the old one back it will be too late for them to tell at you - IF they figure it out.
sent from a series of tubes.
Click to expand...
Click to collapse
Yeah, I may not post alot but that's due to college and church, otherwise I would be making guides and helping out in Q&A instead of asking for it now haha, I tried so many things and nothing worked so I concluded a brick, sadly I'll never know why my phone randomly nuked itself, I didn't do anything I normally don't was so odd.
Update: they couldn't fix it so they are sending me a new phone.

Stock RUU's Download Here >

​
This is an update on a previous post, this time however you don't have to sieve through Chinese websites to get them....i have spent time to get them for you!
This Will revert your HTC Salsa to Stock​​
By using these you will wipe everything you have done. Recovery will be wiped, unknown about lock/unlocked boot-loader as i haven't attempted this with unlocked boot-loader before as.i had s-off at the time.
You do this at your own risk, i take no responsibility at all for anything that may or may not happen lol​​
Instructions for use.
HTC SYNC installed but not running, you want the cable driver mainly.
Instead of following on screen instruction via the RUU, set your phone into fastboot mode yourself then activate/run the RUU.exe you require, i would suggest run as administrator (right click on application)
This will take some time to install, i did it on 3rd attempt, first 2 were relying on the RUU to boot the phone for me...3rd i booted into fastboot/bootloader myself and away it went.
if for any reason it doesn't respond to you or it doesn't install stock or freezes, whip out the battery and do it all again!
Below are the RUU's please find the correct region your in and download accordingly. EU RUU is a common one if the others don't work. all roms are based of this version.
RUU_Icon_G_HTCCN_CHS_1.24.1400.4_Radio_47.14.35.3030H_7.47.35.17_release_204455_signed.exe
RUU_Icon_G_HTC_Europe_1.12.401.1_R_Radio_47.14.35.3030H_7.47.35.17_release_193257_signed.exe
RUU_Icon_G_O2_UK_1.18.206.2_Radio_47.14.35.3030H_7.47.35.17_release_198160_signed.exe
RUU_Icon_G_hTC_Asia_HK_1.16.708.3_Radio_47.14.35.3030H_7.47.35.17_release_197702_signed.exe
RUU_Icon_G_hTC_Asia_India_1.12.720.2_Radio_47.14.35.3030H_7.47.35.17_release_193467_signed.exe
RUU_Icon_G_HTC_TUR_1.18.468.2_Radio_47.14.35.3030H_7.47.35.17_release_199341_signed.exe
RUU_Icon_G_Hutch_AUS_1.18.861.1_Radio_47.14.35.3030H_7.47.35.17_release_197619_signed.exe
RUU_Icon_G_Voda-Hutch_AU_1.17.862.2_Radio_47.14.35.3030H_7.47.35.17_release_198433_signed.exe
RUU_Icon_G_Chunghwa_1.13.751.1_Radio_47.14.35.3030H_7.47.35.17_release_193940_signed.exe
RUU_Icon_G_hTC_Asia_WWE_1.12.707.2_Radio_47.14.35.3030H_7.47.35.17_release_193464_signed.exe
as the link in the lower post suggested you can also try this
*this wasn't provided by me please don't blame me if anything goes wrong*
1. Download your RUU
2. Extract and copy the system.img AND boot.img to the same directory as your fastboot tools "C:/fastboottools" ( make sure to copy both files )
3. Enter the fastboot mode on your phone by pressing volume down + power button after the device has been turned off.
4. Choose fastboot on the phone by pressing power button, and then connect your phone to your PC
5. Using fastboot tools, open the Command prompt and navigate to "C:\fastboottools" then run this command on cmd: "fastboot flash system system.img"
6. Dont reboot, Using fastboot tools, run this command on cmd: "fastboot flash boot boot.img"
( The two commands in step 5 and 6 are different, make sure to type each one correctly and to do them straight after each other )
7. Reboot phone. let it boot up, you will still get bootloop or error message.
8. Take out the battery.
9. Boot back into bootloader ( Volume down + power ).
10. Now choose recovery.
11. Phone should now reboot itself and bam, all should now work fine.​
Well it seems a lot of you shadows hiding away wanted these lol, as the downloads in 1 day surprised me lol.
BigBear is using Xparent Tapatalk Purple
I managed to revert back to stock using this method http://forum.xda-developers.com/showthread.php?t=1631121
Now I am running 2.3.3
Now i just want to update to 2.3.5 if possible, haven't been able to get OTA updates. Do you know how i can go about it?
CWM recovery is still intact.
Thanks
The salsa will never have 2.3.5 ota. HTC stopped at 2.3.3 and discontinued updates for us. well the stopped producing the salsa and totally dropped it.
that's why we have 2.3.5 roms that are not meant for us...ie no FB button that works correctly, no mirror or front facing camera.
and this is probably why noone is still running stock roms anymore
BigBear is using Xparent Tapatalk Purple
getting error 155 again and again. Used RUU_Europe, RUU_UK, RUU_Asia_WWE, RU_Asia_India. Rebooted to the fastboot screen myself but the RUU takes over from the white screen and fastboot menu and goes into the black screen with HTC written. Tried letting RUU boot itself but still same error.
EDIT:
I have previously unlocked bootloader to gain Root Access since I had S-ON on my device. Need help urgently. Can I revert back to a locked Bootloader or anything ?
Now I have relocked the bootloader and tried the Europe Salsa RUU.... It is giving me Error 140 now claiming the bootloader version is invalid.
HBOOT is updated and I notice that the Radio version mentioned on Fastboot Bootloader screen is different than mentioned in the RUU.
Mine says:
*** Relocked ***
ICON_G PVT SHIP S-ON RL
HBOOT-1.08.0000
MICROP-0558
RADIO-7.51.35.19
Dec 16 2011,16:12:07
razasohail said:
getting error 155 again and again. Used RUU_Europe, RUU_UK, RUU_Asia_WWE, RU_Asia_India. Rebooted to the fastboot screen myself but the RUU takes over from the white screen and fastboot menu and goes into the black screen with HTC written. Tried letting RUU boot itself but still same error.
EDIT:
I have previously unlocked bootloader to gain Root Access since I had S-ON on my device. Need help urgently. Can I revert back to a locked Bootloader or anything ?
Click to expand...
Click to collapse
Did you take a nandroid backup in recovery at all?, if so restore it.if recovery isn't there reinstall recovery and restore your backup.
BigBear is using Xparent Tapatalk Purple
Get the phone to Stock
Hi..
Where can I get these files
system.img and boot.img
2. Extract and copy the system.img AND boot.img to the same directory as your fastboot tools "C:/fastboottools" ( make sure to copy both files )
arekapudi said:
Hi..
Where can I get these files
system.img and boot.img
2. Extract and copy the system.img AND boot.img to the same directory as your fastboot tools "C:/fastboottools" ( make sure to copy both files )
Click to expand...
Click to collapse
this guide wasn't provided by me, i do know what this means but its hard to explain to a newbie...
for the more technical side of go here >http://forum.xda-developers.com/showthread.php?t=1631121, it may help you...
ok after of hours of fiddling around with this, I have come to the point where I really need the system.img and boot.img files
my phone is stuck at the htc boot screen with white background.
I have installed htc cable driver and got fastboottools files created and did some googling and found out that the only other way to install this is by running the exe while in fastboot and have to bootloader "relocked"
I tried to extract them from the executable using 7-zip but can't see them there.
Any help is greatly appreciated. thanks.
Saturn007 said:
ok after of hours of fiddling around with this, I have come to the point where I really need the system.img and boot.img files
my phone is stuck at the htc boot screen with white background.
I have installed htc cable driver and got fastboottools files created and did some googling and found out that the only other way to install this is by running the exe while in fastboot and have to bootloader "relocked"
I tried to extract them from the executable using 7-zip but can't see them there.
Any help is greatly appreciated. thanks.
Click to expand...
Click to collapse
in all fairness mate, i can't help on this. these guides were provided by others and has been known to work for us. i have not tried this and will not be trying this either as i have no desire to revert. what i do mention in all rom threads is this. take a backup of your stock rom in recovery before you tamper or change anything, this way you can revert straight back to your stock rom, no questions asked.
i would think though you may not have either installed correctly or its the wrong ruu, but i can't tell
BigBearEvo said:
in all fairness mate, i can't help on this. these guides were provided by others and has been known to work for us. i have not tried this and will not be trying this either as i have no desire to revert. what i do mention in all rom threads is this. take a backup of your stock rom in recovery before you tamper or change anything, this way you can revert straight back to your stock rom, no questions asked.
i would think though you may not have either installed correctly or its the wrong ruu, but i can't tell
Click to expand...
Click to collapse
I am not holding you responsible for any of my actions mate. I do appreciate all the info you provided here.
I attempted to do a backup but the SD card got full in the middle of the process. My luck.
I was just asking if anyone (not necessarily you) would have a copy of these files as I attempted to download the files from the other thread, http://forum.xda-developers.com/showthread.php?t=1631121, but the links are dead. I was hoping someone might have them and would like to share with us. That's all.
Saturn007 said:
I am not holding you responsible for any of my actions mate. I do appreciate all the info you provided here.
I attempted to do a backup but the SD card got full in the middle of the process. My luck.
I was just asking if anyone (not necessarily you) would have a copy of these files as I attempted to download the files from the other thread, http://forum.xda-developers.com/showthread.php?t=1631121, but the links are dead. I was hoping someone might have them and would like to share with us. That's all.
Click to expand...
Click to collapse
tel me what you want and ill get it, but you have to tell me which file to get it from and ill host it up for you. ie you want the system.img and boot.img but from which ruu?
BigBearEvo said:
tel me what you want and ill get it, but you have to tell me which file to get it from and ill host it up for you. ie you want the system.img and boot.img but from which ruu?
Click to expand...
Click to collapse
Hi i am getting error 140 aswell after relocking my bootloader..???can someone help me as im trying to restore and im struggeling...
any help will be appreciated but i tried some other tutorials but they require a zip version of the RUU.. ;(
gagan313 said:
Hi i am getting error 140 aswell after relocking my bootloader..???can someone help me as im trying to restore and im struggeling...
any help will be appreciated but i tried some other tutorials but they require a zip version of the RUU.. ;(
Click to expand...
Click to collapse
you won't get a zip version ruu only stock as i listed rom wise. now did you lock the bootloader before trying to add stock back on?
if you did there's part of your problem.
unlock it again, go find stock.zip in stock rom thread in android development section and flash it....then lock the bootloader. if you lock the loader again please note root etc won't work/function correctly again. to have any root privilege's you require either s-off or unlocked bootloader.
BigBearEvo said:
you won't get a zip version ruu only stock as i listed rom wise. now did you lock the bootloader before trying to add stock back on?
if you did there's part of your problem.
unlock it again, go find stock.zip in stock rom thread in android development section and flash it....then lock the bootloader. if you lock the loader again please note root etc won't work/function correctly again. to have any root privilege's you require either s-off or unlocked bootloader.
Click to expand...
Click to collapse
ok i will try that now
---------- Post added at 09:53 PM ---------- Previous post was at 09:41 PM ----------
nope... it dosnt work... it says bootloader version error
(which came up before..)
just so you know.. i am S-ON and hboot 1.8.00000 or somthing...
---------- Post added at 10:34 PM ---------- Previous post was at 09:53 PM ----------
could it be posssible that i have the wrong RUU??
i am definatly on EURO but when i go through the ruu install wizard it says:
Verify that you want to update the ROM version:
From:
Image version:
1.28.0.0
To:
Image version:
1.12.401.1_r
could i have the wrong one?? or is this normal??
gagan313 said:
ok i will try that now
---------- Post added at 09:53 PM ---------- Previous post was at 09:41 PM ----------
nope... it dosnt work... it says bootloader version error
(which came up before..)
just so you know.. i am S-ON and hboot 1.8.00000 or somthing...
---------- Post added at 10:34 PM ---------- Previous post was at 09:53 PM ----------
could it be posssible that i have the wrong RUU??
i am definatly on EURO but when i go through the ruu install wizard it says:
Verify that you want to update the ROM version:
From:
Image version:
1.28.0.0
To:
Image version:
1.12.401.1_r
could i have the wrong one?? or is this normal??
Click to expand...
Click to collapse
tends to be normal that, but just to let you know...i have only ever reset using the ruu once before and it took along time to do it! since then ive never gone back. ive flashed stock.zip which gave me back stock...but its not for me.
so flash my stock.zip nothing else.
if it is just Facebook your having issues with then don't just swap roms or go back to stock, it won't help, it will probably make it worse to be honest. im using a new black Facebook as i hosted in the thread in android apps section and have no problems with it.
just make sure you have Facebook installed and moved to sd only.
BigBearEvo said:
tends to be normal that, but just to let you know...i have only ever reset using the ruu once before and it took along time to do it! since then ive never gone back. ive flashed stock.zip which gave me back stock...but its not for me.
so flash my stock.zip nothing else.
if it is just Facebook your having issues with then don't just swap roms or go back to stock, it won't help, it will probably make it worse to be honest. im using a new black Facebook as i hosted in the thread in android apps section and have no problems with it.
just make sure you have Facebook installed and moved to sd only.
Click to expand...
Click to collapse
thats just the thing you see....
for some reason, if i try the stock.zip i always have wifi issues as well as facebook issues and well... i have tried all the facebooks from 1.9.9 to the black one and it dosnt seem to sign in... evern after i have unin installed and moved to sd card using links2sd....:crying:
as for stock....
what i think is that there is a problem with my hboot... and error massage came up saying my hboot is newer than the one im trying to install... any way i can downgrade? (sorry for asking for so much of you)
gagan313 said:
that's just the thing you see....
for some reason, if i try the stock.zip i always have WiFi issues as well as Facebook issues and well... i have tried all the Facebook from 1.9.9 to the black one and it doesn't seem to sign in... even after i have uninstalled and moved to sdcard using link2sd....:crying:
as for stock....
what i think is that there is a problem with my hboot... and error massage came up saying my hboot is newer than the one im trying to install... any way i can downgrade? (sorry for asking for so much of you)
Click to expand...
Click to collapse
no way to downgrade sorry.
it has been noted elsewhere that this Facebook issue tends to fail when its installed on normal internal memory or as an update on-top of the system Facebook already installed.
you can tell if this is the case by going into link2sd and looking at Facebook.apk, it may have a green updated next to it. you can remove this update by uninstalling it.
i don't have this problem as it works fine on CM7.
you can try and uninstall the Facebook you have, go into recovery wipe cache/dalvik and reboot, apparently this removes all traces it was there.
reboot and install Facebook 2.0 or black which ever.
using link2sd move it to the sdcard and then try it.
i am gonna try this on other roms when i can to see if this works or not.
BigBearEvo said:
no way to downgrade sorry.
it has been noted elsewhere that this Facebook issue tends to fail when its installed on normal internal memory or as an update on-top of the system Facebook already installed.
you can tell if this is the case by going into link2sd and looking at Facebook.apk, it may have a green updated next to it. you can remove this update by uninstalling it.
i don't have this problem as it works fine on CM7.
you can try and uninstall the Facebook you have, go into recovery wipe cache/dalvik and reboot, apparently this removes all traces it was there.
reboot and install Facebook 2.0 or black which ever.
using link2sd move it to the sdcard and then try it.
i am gonna try this on other roms when i can to see if this works or not.
Click to expand...
Click to collapse
ok ill give it a shot

[Q] Velocity 4G (VODAP120) boot loop / can't RUU

Hello all,
I'm sorry to interrupt you all, but this is rather important!
I tried to root my girlfriends Velocity 4G which she got with her contract with A1 (austrian carrier).
I already flashed a One S and knew of the complications a root for HTC could bring.
So I tried to get everything together before flashing and then I did it...
Got the bootloader unlocked, installed TWRP and flashed sun_dreams rom.
Don't worry, I wiped all clean and think I did it the right way (already flashed 4 other phones, but samsungs').
But I seem to have missed something as I got in a neverending bootanimation (white background with green htc logo).
I know, that you sometimes have to wait a few minutes, but after about 5 minutes or so, I thought I was stuck on boot loop.
So I rebooted, flashed it again and rebooted and nothing changed.
I then read about the boot.img... So I extracted the boot.img and did a full wipe, then installed it, after that the rom and then (just to be safe) three times again the boot.img.
Rebooted and now I got the reboot loop (white background with green logo, then black, then white background again and so on)
I tried everything and as I was about to give up, read about the final solution: the RUU or PH39IMG.zip.
Now the problem is: I cant get either of them to work. At all. When trying to flash the RUU (with bootloader relocked), the programm says: "ERROR 170: No device connected".
I read about some other people having the same problem, so I tried the solution given to them: go to the first screen, then to your temp data, extract the rom.zip, rename it and flash that one, via putting it on the external sd and booting into bootloader.
Didn't work either: Wrong CID. Same for all RUUs I could find even closely related to my phone.
As I couldn't find the real correct RUU, I tried to cheat and use the goldcard to overgo the cid-problem.
Because I couldn't boot up the Velocity 4G I tried to make one with my own Galaxy S2, which worked.
Seems to be the wrong way, since it's the wrong CID anyways, when trying to install the PH39IMG (still all RUUs say ERROR 170).
I might need to mention I didn't do the S-OFF thing, as I didn#t want to mess with the hardware... Is that necessary for my problem to getting fixed?
Maybe I just need the one correct RUU for my model, but I can't find it anywhere!
please help me somebody, as I feel very guilty because of wrecking my girlfriends phone! :crying:
any help is appreciated!!!
greetings
deweini said:
Hello all,
I'm sorry to interrupt you all, but this is rather important!
I tried to root my girlfriends Velocity 4G which she got with her contract with A1 (austrian carrier).
I already flashed a One S and knew of the complications a root for HTC could bring.
So I tried to get everything together before flashing and then I did it...
Got the bootloader unlocked, installed TWRP and flashed sun_dreams rom.
Don't worry, I wiped all clean and think I did it the right way (already flashed 4 other phones, but samsungs').
But I seem to have missed something as I got in a neverending bootanimation (white background with green htc logo).
I know, that you sometimes have to wait a few minutes, but after about 5 minutes or so, I thought I was stuck on boot loop.
So I rebooted, flashed it again and rebooted and nothing changed.
I then read about the boot.img... So I extracted the boot.img and did a full wipe, then installed it, after that the rom and then (just to be safe) three times again the boot.img.
Rebooted and now I got the reboot loop (white background with green logo, then black, then white background again and so on)
I tried everything and as I was about to give up, read about the final solution: the RUU or PH39IMG.zip.
Now the problem is: I cant get either of them to work. At all. When trying to flash the RUU (with bootloader relocked), the programm says: "ERROR 170: No device connected".
I read about some other people having the same problem, so I tried the solution given to them: go to the first screen, then to your temp data, extract the rom.zip, rename it and flash that one, via putting it on the external sd and booting into bootloader.
Didn't work either: Wrong CID. Same for all RUUs I could find even closely related to my phone.
As I couldn't find the real correct RUU, I tried to cheat and use the goldcard to overgo the cid-problem.
Because I couldn't boot up the Velocity 4G I tried to make one with my own Galaxy S2, which worked.
Seems to be the wrong way, since it's the wrong CID anyways, when trying to install the PH39IMG (still all RUUs say ERROR 170).
I might need to mention I didn't do the S-OFF thing, as I didn#t want to mess with the hardware... Is that necessary for my problem to getting fixed?
Maybe I just need the one correct RUU for my model, but I can't find it anywhere!
please help me somebody, as I feel very guilty because of wrecking my girlfriends phone! :crying:
any help is appreciated!!!
greetings
Click to expand...
Click to collapse
OK... Vodafone is still on gingerbread...
Soooo... You need a gingerbread ROM... And a gingerbread boot.img... Then get it to boot...
After that I would s-off, super cid, get to ICS hboot... Then flash the ROM of your choice
rignfool said:
OK... Vodafone is still on gingerbread...
Soooo... You need a gingerbread ROM... And a gingerbread boot.img... Then get it to boot...
After that I would s-off, super cid, get to ICS hboot... Then flash the ROM of your choice
Click to expand...
Click to collapse
So far so good... but where do I get it from?
I have this one:
RUU_HOLIDAY_SENSE3_5_Vodafone_DE_2.38.162.1_Radio_3.02.4740.09_34.20.701040.19_release_241518_signed
But this one won't work either...
What complicates the search, is that this phone goes by so many different names (vivid, velocity, holiday, raider, etc...)
Should I post a getvar all?
Concerning your further steps: I would be very happy to get it to run at all, maybe then think of reflashing something.
I don't know if I manage that s-off thing and I don't want to hard brick it and give it the final punch...
anyways, thanks for the fast response!
Can you get the ph39img from it?
Sent from my Vivid 4G using Tapatalk
rignfool said:
Can you get the ph39img from it?
Sent from my Vivid 4G using Tapatalk
Click to expand...
Click to collapse
I already did that with all the RUUs I found, but none worked...
EDIT: so I tried a solution offered by another poster in another forum which said to install CM10 on a clean wipe.
did that and it booted in the cm boot screen and loads the "first install wizard"... well, at least to the language selection screen, then it freezes and reboots again.
but at least we bought us some time at the start.
deweini said:
I already did that with all the RUUs I found, but none worked...
EDIT: so I tried a solution offered by another poster in another forum which said to install CM10 on a clean wipe.
did that and it booted in the cm boot screen and loads the "first install wizard"... well, at least to the language selection screen, then it freezes and reboots again.
but at least we bought us some time at the start.
Click to expand...
Click to collapse
Its because of a wrong hboot...
It will happen with all of the ICS+ ROMs...
I wish you hadn't relocked your bootloader...
Can you reunlock...
Iirc there is a thread with hboot updated... Maybe try that... Or download the Wcxroot thingy and flash the juopenut hboot...
Sent from my Vivid 4G using Tapatalk
rignfool said:
Its because of a wrong hboot...
It will happen with all of the ICS+ ROMs...
I wish you hadn't relocked your bootloader...
Can you reunlock...
Iirc there is a thread with hboot updated... Maybe try that... Or download the Wcxroot thingy and flash the juopenut hboot...
Sent from my Vivid 4G using Tapatalk
Click to expand...
Click to collapse
so, you're basically saying i might be able to get it to work without any RUUs or PH39IMGs?
Wow, that would be good news at last.
I already reunlocked before i flashed the CM10 rom and i didn't forget to flash the boot.img afterwards and even went back again to recovery to wipe cache and dalvik and fixed permissions.
Which one should i try?
thank you for your help!! :good:
is updating the hboot even possible without s-off?
so it seems i have to obtain s-off to flash anything else than stock rom...
as far as i read you have to be on stock ruu to obtain s-off, is that correct?
because that would be bad, as i don't have the stock ruu for my phone.
is it possible to acquire s-off without being on stock rom and would it be possible with the state my phone is in?
deweini said:
is updating the hboot even possible without s-off?
so it seems i have to obtain s-off to flash anything else than stock rom...
as far as i read you have to be on stock ruu to obtain s-off, is that correct?
because that would be bad, as i don't have the stock ruu for my phone.
is it possible to acquire s-off without being on stock rom and would it be possible with the state my phone is in?
Click to expand...
Click to collapse
I think homeslice s-offed his phone on a non stock ROM...
Sent from my Vivid 4G using Tapatalk
rignfool said:
I think homeslice s-offed his phone on a non stock ROM...
Sent from my Vivid 4G using Tapatalk
Click to expand...
Click to collapse
i already wrote a pm. do you have any ideas left? maybe try and install a gb rom and then try that ruu again?
ps: i did manage to start the ruu.exe (by reinstalling the htc sync) and it stopped with the error 131. installing the rom.zip (or PH39IMG.zip) still won't work as it says customer id check failed...
deweini said:
i already wrote a pm. do you have any ideas left? maybe try and install a gb rom and then try that ruu again?
ps: i did manage to start the ruu.exe (by reinstalling the htc sync) and it stopped with the error 131. installing the rom.zip (or PH39IMG.zip) still won't work as it says customer id check failed...
Click to expand...
Click to collapse
Okay, so I did manage to fix it, as it seems... :laugh:
This is what I did:
1. reunlocked bootloader
2. installed TWRP and booted into recovery
3. mounted the internal SD as mass storage
4. copied over VJRaiders GB rom
5. did a full wipe
6. installed VJRaiders rom
7. rebooted into bootloader
8. fastboot flashed the kernel found in the rom thread (twice)
9. rebooted and it worked...
I don't know how and why, but the problem seemed to be that I always tried to flash non-GB roms. As simple as that.
I have no idea why the RUU and PH39IMG didn't work tho...
Well. I won't touch that thing for a looong time, as it works and I had enough problems getting there!
The reason that you had problems with ics and upward roms is because your phone still has the gb hboot. This is because boss never released the ics update. To install ics roms you need the ics hboot.
Sent from my HTC One
WildfireDEV said:
The reason that you had problems with ics and upward roms is because your phone still has the gb hboot. This is because boss never released the ics update. To install ics roms you need the ics hboot.
Sent from my HTC One
Click to expand...
Click to collapse
Which I'm only able to attain with s-off, am I right?
Correct, I believe. If you didn't get an official update to ICS, you'll have to S-Off. It's honestly not as bad as it sounds, I did mine with some speaker wire...probably the worst part of it is getting the cover off of the section where you have to ground out the point. Just take your time, and make sure you're in a well lit area, with a little bit of working space, and you'll be fine.
well, the problem is, that we are not longer on a stock rom and can't seem to flash the original ruu, as we don't find it anywhere...
and as far as i know it is not recommended or possible to go s-off without being on stock rom!?
AFAIK it is UNTESTED... Not impossible
Sent from my Vivid 4G using Tapatalk
If this is anything like other HTC devices, i'd say your best shot if you're willing to try an untested idea, would be to give it a shot with a sense rom, as they tend to be (under the hood anyways) a lot closer to stock than non sense roms.

EMEI is 00000000 after upgrade to 4.3, what is my next step

Hi there,
I have searched high & low on the interwebs for a possible solution to my problem but have yet to yield any significant results.
I was on 4.2.2 Stock, Rooted, with bulletproof, and I had started to get random reboots and then 4 nights ago during the night it decided to get into a reboot loop. It would power up for about 20 mins and then restart again & again so when I woke up it was super hot.
So I thought it was time to update it to 4.3 now in the hope that this would resolve the issue but it didn't. I obtained the relevant RUU (Guru Reset M7 2.24.980.2 for HTC__039) from htc1guru and since I was only wanting to get the OTA in the hope that this would fix any other software issues, I only flashed the recovery. I then proceeded to do the large OTA update. This was successful. Then the reboots started again.
Time for a factory reset now, (which I realise I should have just done in the first place) but after setting up my details in the phone I am unable to get network over 3G/4G and when I go into look at the APNs, it says that no sim card is installed when it definitely is. When I go into Phone Info, it states that my EMEI is 00000000.
After looking around for what feels like hours, I read somewhere that I might need to flash the radio but I only have the radio from the previous RUU(Guru Reset M7 2.24.980.2) or can I use that since I can not find anything around RUUs for 3.63.980.2.? I don't want to make the situation any worse than it already is.
I am hoping that there is a simple explanation and fix & any help or guidance would be much appreciated.
Thanks in advance :good:
So you think the problem is that your software is upgraded and not your firmware? If so, you can solve that by dowgrading your software. If you can't find an updated RUU (nothing except a signed file from HTC should be called a RUU), there is still a solution:
- Find a system dump from a phone that is your CID and the version of Android you want. It will be a CWM or TWRP backup.
- Flash the appropriate custom recovery.
- Push the files to your phone in the appropriate directory (you may need to make a backup just to see what the right directory is).
- Restore the backup you just pushed to your phone.
Then factory reset and install the stock recovery. You may need to re-lock the bootloader (I'm not sure). Try to get the correct OTA. If you can't find it, try to download one and save as /sdcard/update.zip. Use the stock recovery to flash it. (You'll need to search for instructions on how to do that. It involves key combinations.) Finally, unlock the bootloader, make a backup, and (optionally) root. Don't install a custom kernel. If your problem persists, you likely have a hardware problem.
Thanks for your reply.
I have no idea if its software/firmware but its showing its on 4.3. I was speculating on the radio possibly needing to be reflashed due to one comment I read on a forum I randomly came across?
So I could use my very first backup I used through TWRP and push that to the phone?
While I am fairly new to Android(had to switch for the HTC ONE), I have been around idevices for a long time and have learnt to always keep multiple backups just in case
I left the bootloader unlocked as most guides say that you don't need to have it locked to get the OTA. I actually tried to find the manual OTA file and do it the way you suggested but at the time I had no luck.
I'll see what I can accomplish tonight.
Apologies on the noobness in regards to RUU.
Is it possible to use a RUU for lets say T-Mobile on an international variant? I see HTC released an RUU for T-Mobile for 4.3 but as far as I can see there isn't any others.
[email protected] said:
So I could use my very first backup I used through TWRP and push that to the phone?
Click to expand...
Click to collapse
That's the first thing I'd try, yes. But I'm guessing just as much as you are.
fenstre said:
That's the first thing I'd try, yes. But I'm guessing just as much as you are.
Click to expand...
Click to collapse
Hahahaha Well I trust your guess way more then mine
Would I need s-off to copy the previous backup back onto the phone or would I only need s-off if I had to push something to system(which I do not need to do)?
I tried last night to run rumrunner and it continually failed and basically told me I had 2 different scenarios to resolve it(the following is coming from memory and its very hazy). One was to use a different kernel and the other was to use another ROM, but that wasn't the preferred option.
At work now so will try and restore my original backup tonight at home. Thanks for your help.
[email protected] said:
Would I need s-off to copy the previous backup back onto the phone or would I only need s-off if I had to push something to system(which I do not need to do)? .
Click to expand...
Click to collapse
Sorry for my late response. You only need s-off to flash firmware that is older, for a different phone CID, or modified by a third party. Or to change other hidden partitions, like to modify the "TAMPERED" flag or to change the CID. Unlocking the bootloader is for changing partitions from fastboot mode: recovery, and maybe also system and boot. You do not need an unlocked bootloader to change these partitions from recovery if you already have a custom recovery installed. (You can definitely modify system and boot, but I'm not sure about modifying recovery with a locked bootloader.)
fenstre said:
Sorry for my late response. You only need s-off to flash firmware that is older, for a different phone CID, or modified by a third party. Or to change other hidden partitions, like to modify the "TAMPERED" flag or to change the CID. Unlocking the bootloader is for changing partitions from fastboot mode: recovery, and maybe also system and boot. You do not need an unlocked bootloader to change these partitions from recovery if you already have a custom recovery installed. (You can definitely modify system and boot, but I'm not sure about modifying recovery with a locked bootloader.)
Click to expand...
Click to collapse
No need to apologise, I'm just happy that someone has been able to assist me.
I have used one of my previous TWRP backups, unfortunately I couldn't use my very very first one as it was missing some files, it obviously didn't copy it all across for some reason
I now have my EMEI back (woohoo) but I think the backup I used has something wrong in the kernel as I think it has bulletproof installed. I am going to return it to stock but following a procedure here as I need to return it to HTC as the phone will not read any sim cards. I have tried 3 different sim cards and have also tested them in a firends HTC ONE and they all work in his. SO it looks like I do have an actual hardware issue with the phone which isn't cool just before Xmas.
I already have major withdrawals from being able to play ingress :crying:
Thanks heaps for your help.

[Q] Changing CID back to original

Im sending my phone back to HTC for repair.
I have two questions...
Would they look at the CID?
Can I change it back to my original CID if I've already installed a RUU that doesn't allow my CID? (sounds like a dumb question)
stanny2k said:
Im sending my phone back to HTC for repair.
I have two questions...
Would they look at the CID?
Can I change it back to my original CID if I've already installed a RUU that doesn't allow my CID? (sounds like a dumb question)
Click to expand...
Click to collapse
I read your other post http://forum.xda-developers.com/showthread.php?t=2599739 and probably a lot of others too, no answer because I have none.
So here's a small summary:
1- you're S-ON again, so changing CID cannot be done
2- you have a .401. software version which means it cannot be CID H3G, so HTC__001 is correct for that software version
3- you've removed TAMPERED and set to LOCKED (not relocked)
4- I don't know how the service center will react, and whether they would bother checking CID, etc. (from what I've seen the UK centers are quite lenient)
If you really want to go back fully to your carrier version, and "out of the box", you can take a look at my guide: http://forum.xda-developers.com/showthread.php?t=2541082
but that means starting the procedure all the way from the start again, ie
-- unlocking (and you're gonna have to do that with HTCdev)
-- s-off using rumrunner.
then follow the rest of the guide.
Don't know if it's worth the hassle; but if you need help with it, post back there.
cheers
nkk71 said:
I read your other post http://forum.xda-developers.com/showthread.php?t=2599739 and probably a lot of others too, no answer because I have none.
So here's a small summary:
1- you're S-ON again, so changing CID cannot be done
2- you have a .401. software version which means it cannot be CID H3G, so HTC__001 is correct for that software version
3- you've removed TAMPERED and set to LOCKED (not relocked)
4- I don't know how the service center will react, and whether they would bother checking CID, etc. (from what I've seen the UK centers are quite lenient)
If you really want to go back fully to your carrier version, and "out of the box", you can take a look at my guide: http://forum.xda-developers.com/showthread.php?t=2541082
but that means starting the procedure all the way from the start again, ie
-- unlocking (and you're gonna have to do that with HTCdev)
-- s-off using rumrunner.
then follow the rest of the guide.
Don't know if it's worth the hassle; but if you need help with it, post back there.
cheers
Click to expand...
Click to collapse
Thanks for taking the time in responding mate. The issue I have is that I can't get a stock RUU for my H3G CID... It just doesn't seem to exist anywhere... I think a few other people are asking the same question... Which is why I've had to change my CID to HTC__001..
stanny2k said:
Thanks for taking the time in responding mate. The issue I have is that I can't get a stock RUU for my H3G CID... It just doesn't seem to exist anywhere... I think a few other people are asking the same question... Which is why I've had to change my CID to HTC__001..
Click to expand...
Click to collapse
Well if you checked my guide, you'd see that method 3 (CWM Backup), works, and there is a H3G__001 backup out there; as a matter of fact, the example I used was for H3G__001.
nkk71 said:
Well if you checked my guide, you'd see that method 3 (CWM Backup), works, and there is a H3G__001 backup out there; as a matter of fact, the example I used was for H3G__001.
Click to expand...
Click to collapse
In that case, I take that back I'm going to follow your guide again tonight.
The last thing I want is for HTC to say No, they cant do my repair cause I've messed about with my phone...
Oh, and have a "thanks"
stanny2k said:
In that case, I take that back I'm going to follow your guide again tonight.
The last thing I want is for HTC to say No, they cant do my repair cause I've messed about with my phone...
Oh, and have a "thanks"
Click to expand...
Click to collapse
I'm going to recommend this CWM recovery, just cause the newer versions are taking close to an hour to backup/restore:
recovery-clockwork-touch-6.0.3.2-m7--v2.img 7.2 MB
https://mega.co.nz/#!6E8RiIrQ!GF5LyhmEdg8OQJxuQVVjwSxBljxhW7xsZAHLzjVACsc
MD: 1c6afb14db3f305b0ad7d85d5af80bef
Also, please follow the instruction properly, no jumping, skipping or adding steps
The only slightly tricky part (as mentioned), is in Step 6, where when the phone reboots to "stock recovery" it could hang somewhere between 25% to 50%, and you have to manually reboot, and (possibly) again towards the end, and you have to reboot manually again.
This is a known side effect because stock recovery is not exactly the same as your version, but it's not a problem.
After the FIRST (and only the FIRST) OTA update, should you go back S-On, because hboot 1.55 has a patch that will force TAMPERED to come back if you go from s-off to s-on.
NB: after the first OTA, you're phone will be 100% stock.
If you have any trouble (hopefully not), post back in my thread, as I get instant notifications on that (and if i'm still awake, i'm 2 hours ahead), and I'll try to help out.
Cheers.
---------- Post added at 06:50 PM ---------- Previous post was at 06:48 PM ----------
stanny2k said:
Oh, and have a "thanks"
Click to expand...
Click to collapse
Thanks, I like those
nkk71 said:
I'm going to recommend this CWM recovery, just cause the newer versions are taking close to an hour to backup/restore:
recovery-clockwork-touch-6.0.3.2-m7--v2.img 7.2 MB
https://mega.co.nz/#!6E8RiIrQ!GF5LyhmEdg8OQJxuQVVjwSxBljxhW7xsZAHLzjVACsc
MD: 1c6afb14db3f305b0ad7d85d5af80bef
Click to expand...
Click to collapse
Ok, I'll grab this!
nkk71 said:
Also, please follow the instruction properly, no jumping, skipping or adding steps
Click to expand...
Click to collapse
Will do! Don't worry, word for word!
nkk71 said:
The only slightly tricky part (as mentioned), is in Step 6, where when the phone reboots to "stock recovery" it could hang somewhere between 25% to 50%, and you have to manually reboot, and (possibly) again towards the end, and you have to reboot manually again.
This is a known side effect because stock recovery is not exactly the same as your version, but it's not a problem.
Click to expand...
Click to collapse
Noted.
nkk71 said:
After the FIRST (and only the FIRST) OTA update, should you go back S-On, because hboot 1.55 has a patch that will force TAMPERED to come back if you go from s-off to s-on.
NB: after the first OTA, you're phone will be 100% stock.
Click to expand...
Click to collapse
When you say "should you go back S-On" do I let the first OTA update install, then manually go back to S-ON, then let the other updates install once I've got S-ON back?
nkk71 said:
If you have any trouble (hopefully not), post back in my thread, as I get instant notifications on that (and if i'm still awake, i'm 2 hours ahead), and I'll try to help out.
Cheers.
Click to expand...
Click to collapse
Appreciate it, thank you
stanny2k said:
When you say "should you go back S-On" do I let the first OTA update install, then manually go back to S-ON, then let the other updates install once I've got S-ON back?
Click to expand...
Click to collapse
yep, exactly, after the 1st OTA, your phone will be 100% "out-of-the-box"; once the OTA updates successfully it will mean
1- your entire firmware was updated (hboot, recovery, kernel, radio, etc)
2- your ROM will also be updated, proving everything is 100%
otherwise, the OTA would not be able to complete.
Now due to a patch in later hboots (in particular 1.55 as far as i know), going from s-off to s-on, will (after a few reboots) result in "tamper detected - rebooting" and TAMPERED is back.
so in summary, if you really need to go S-On, you do so after first successful OTA (using the command mentioned in my guide), and then you can take any OTAs you like.
hope that makes sense
Perfect sense!
I'll have a bash at this tonight! Thanks a lot
Well, that was an eventful evening
Followed your guide to the letter. Everything went ok apart from a few things..
Pushing files via adb whilst in recovery causes me no end of issues... I kept getting no device found, luckily I was able to boot up and transfer the files manually.
I then flashed the wrong stock recovery (recovery 1.28.401.7.img) so I had to unlock the bootloader again to flash a different one, thankfully the one I did flash (recovery 2.24.771.3 - TRE.img), which matched the first OTA update, everything installed fine after that
Thanks a lot mate. I'll happy to send my device away for repair with no worries now.
Regards, Ryan
stanny2k said:
Well, that was an eventful evening
Followed your guide to the letter. Everything went ok apart from a few things..
Pushing files via adb whilst in recovery causes me no end of issues... I kept getting no device found, luckily I was able to boot up and transfer the files manually.
I then flashed the wrong stock recovery (recovery 1.28.401.7.img) so I had to unlock the bootloader again to flash a different one, thankfully the one I did flash (recovery 2.24.771.3 - TRE.img), which matched the first OTA update, everything installed fine after that
Thanks a lot mate. I'll happy to send my device away for repair with no worries now.
Regards, Ryan
Click to expand...
Click to collapse
Sorry to hear you had some troubles , are you on Windows 8 or 8.1, is that why adb wasn't working.
Also have a two questions about stock recovery you used,
1- when you used 1.28.401.7 the OTA didnt work, or you didnt try?
2- when you used 2.24.771.3 did the OTA hang at any point, or did it reboot (twice, I believe), correctly and by itself?
would be nice if you could give me some more info, it would probably be helpful to others too.
Thanks
nkk71 said:
Sorry to hear you had some troubles , are you on Windows 8 or 8.1, is that why adb wasn't working.
Also have a two questions about stock recovery you used,
1- when you used 1.28.401.7 the OTA didnt work, or you didnt try?
2- when you used 2.24.771.3 did the OTA hang at any point, or did it reboot (twice, I believe), correctly and by itself?
would be nice if you could give me some more info, it would probably be helpful to others too.
Thanks
Click to expand...
Click to collapse
I'm on Windows 7 mate. It just seemed really intermittent. May have been my USB lead/port.
1.28.401.7 - Downloaded the OTA fine, when the phone rebooted to install, it just hung on the "Entering Recovery" screen... Didnt get past that.
2.24.771.3 - Downloaded the OTA fine, booted into Recovery fine, hung on the first quarter (had to manually reboot) after that it installed straight away.
Hope this helps.
stanny2k said:
I'm on Windows 7 mate. It just seemed really intermittent. May have been my USB lead/port.
1.28.401.7 - Downloaded the OTA fine, when the phone rebooted to install, it just hung on the "Entering Recovery" screen... Didnt get past that.
2.24.771.3 - Downloaded the OTA fine, booted into Recovery fine, hung on the first quarter (had to manually reboot) after that it installed straight away.
Hope this helps.
Click to expand...
Click to collapse
hmm: it just hung on the "Entering Recovery" screenit just hung on the "Entering Recovery" screen
did you do a "fastboot erase cache", after flashing it? that's usually the only reason it could get stuck (or perhaps a corrupt download, did you check MD5; i've had some issues downloading from dev-host sometimes).
But thanks anyway, glad all worked out, and hope you get your device back soon
cheers.
nkk71 said:
hmm: it just hung on the "Entering Recovery" screenit just hung on the "Entering Recovery" screen
did you do a "fastboot erase cache", after flashing it? that's usually the only reason it could get stuck (or perhaps a corrupt download, did you check MD5; i've had some issues downloading from dev-host sometimes).
But thanks anyway, glad all worked out, and hope you get your device back soon
cheers.
Click to expand...
Click to collapse
Yup, I did fastboot erase cache before and after flashing it, both were successful as well. I didnt check the MD5, I just installed it after I downloaded it.. it was midnight by the time I got that far! I was tired!
Yeah and thanks a lot for your help mate. Really appreciate it.
I'll let you know the outcome with HTC Hopefully they find nothing untoward!
stanny2k said:
I'm on Windows 7 mate. It just seemed really intermittent. May have been my USB lead/port.
1.28.401.7 - Downloaded the OTA fine, when the phone rebooted to install, it just hung on the "Entering Recovery" screen... Didnt get past that.
2.24.771.3 - Downloaded the OTA fine, booted into Recovery fine, hung on the first quarter (had to manually reboot) after that it installed straight away.
Hope this helps.
Click to expand...
Click to collapse
Sorry, one last question, when you manually rebooted, did you have to keep holding VOLDOWN during boot-up, or did it enter stock recovery by itself
nkk71 said:
Sorry, one last question, when you manually rebooted, did you have to keep holding VOLDOWN during boot-up, or did it enter stock recovery by itself
Click to expand...
Click to collapse
I'm not sure if it enters recovery by itself as I just followed your guide of holding VOLDOWN
My thumbs were killing me by the end of the night!
stanny2k said:
I'm not sure if it enters recovery by itself as I just followed your guide of holding VOLDOWN
My thumbs were killing me by the end of the night!
Click to expand...
Click to collapse
finger gymnastics :laugh:
stanny2k said:
Well, that was an eventful evening
Pushing files via adb whilst in recovery causes me no end of issues... I kept getting no device found, luckily I was able to boot up and transfer the files manually.
Click to expand...
Click to collapse
Looks like I have to express my apologies on that, I believe I found the problem; the "quicker way"
I really should avoid those shortcuts, until I've tested them 100% (or at least 98%).... I'll let you know what the problem was / is when i update the guide, and sorry again for the headache!!
nkk71 said:
Looks like I have to express my apologies on that, I believe I found the problem; the "quicker way"
I really should avoid those shortcuts, until I've tested them 100% (or at least 98%).... I'll let you know what the problem was / is when i update the guide, and sorry again for the headache!!
Click to expand...
Click to collapse
:laugh: thats alright mate. No issues.
Let me know once you've updated the guide and I'll take a look at it
stanny2k said:
:laugh: thats alright mate. No issues.
Let me know once you've updated the guide and I'll take a look at it
Click to expand...
Click to collapse
problem is with the CWM i recommended, works just fine when flashed, but when using "fastboot boot CWM.img" looks like 6.0.3.2 doesnt work properly with adb, 6.0.4.5 on the other hand works with "fastboot boot"
I'll update my guide with some more "visuals" whenever I get a chance....

Categories

Resources