Yet another bootloop thread. So I had HTC stock rom for 2 years and last saturday I rooted the phone and installed cyanogenmod 7.2.0 (all instructions from CM forums). It worked fine for 3 days until I enabled wifi. Wifi didin't connect ("network disabled") so I rebooted. After typing in the pin code the phone reboots. From this on the phone reboots after about 10-30 secs after booting cyanogen.
I got the wifi to disabled again but no use. I got logcat and dmesg dumps but there wasn't anything that points out (at least not to me).
Things I tried:
- I have checked that currently the wifi is disabled
- Factory reset in clockworkmod (didn't work)
- Re-flashing the cyanogen 7.2.0 stable (worked for about 30 minutes, then rebooted by itself) without any additional software installed (except google apps, of course)
- re-flashing the downgraded firmware from CM forums via hboot -> no reboot!
Versions:
VISION PVT SHIP S-OFF
HBOOT-0.85.0005
MICROP-0425
RADIO-26.03.02.18_M3
eMMC-boot
It says SHIP, shouldn't I have ENG as I installed the engineering hboot as in the CM forum instructions? I would like to use CM so what should I try next?
Also, should I update the radio? The thread at developer section has lots of radios but mine is (about phone) 12.28b.60.140eU_26.03.02.18_M3. All the radios in the thread are "e" but no "U". So just to make sure that I don't brick my phone, are those "e" radios ok?
I cannot post links so I can't link the CM forum instructions.
When downgrading again you lost your engineering SPL, just reflash it with fastboot
http://forum.xda-developers.com/showthread.php?p=27796375
As far as the radio goes its hard to say what is best, different for anyone but theoretically all should work to some degree, I would suggest to try one of the newer ones as it may be the cause to one of your issues
Sent from my Nexus 7 using xda premium
Hmm I tried to re-do the cyanogenmod wiki downgrade & root but after running
/data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
I get lots of errors "An error occurred while running the exploit (-1) (errno: 25)". Didin't flash the hboot yet with fastboot. Maybe I should try that next.
Actually that won't work as you don't have many fastboot commands available to you with current SPL, you'll need to flash via bootloader, go to the thread I linked and at the bottom of the op there is a link to a couple pc10img.zips I made, read instructions and flash one of those
Sent from my Nexus 7 using xda premium
demkantor said:
Actually that won't work as you don't have many fastboot commands available to you with current SPL, you'll need to flash via bootloader, go to the thread I linked and at the bottom of the op there is a link to a couple pc10img.zips I made, read instructions and flash one of those
Click to expand...
Click to collapse
OK, I downloaded DZ_PC10IMG.zip from dropbox. I see there's a radio.img in the zip. What version is it and/or should I use it (is it a "e" radio)? If not, any special instructions on how to remove it and repackage the zip? Oh and thanks for your help.
Just flash the whole pc10img.zip as is, don't remove for now as changing radio might also help you and kits easy to switch back as needed, follow directions in that post or read the readme.txt from the drop box link
Sent from my Nexus 7 using xda premium
thdaie mills
I've flashed the DZ_PC10IMG.zip and now I have VISION PVT ENG S-OFF and 4ext recovery touch. Radio is 12.62.60.27U_26.13.04.19_M. I've lost the "e" in radio version. I've heard that it needs to be "e" for Europe(?). Time for radio update? The stock android boots fine.
Try phone as is, if everything works well then leave of be, if you feel your old radio was better than use fastboot to flash it back
Sent from my Nexus 7 using xda premium
Well the stock android is the downgraded firmware from cyanogen wiki. It's useless, language is only english thai or singapore etc. I could use a stock android, just had to find out where to get one. Or try cyanogen again with the new radio. Any special instructions to flash via the 4ext?
Edit: Hmm virtuous ROM could be nice if I wanted a stock rom.
So at this point everything is working as it should? Just looking to change radios? Or just looking for a ROM that's stock and has your language?
Sent from my Nexus 7 using xda premium
With the downgraded stock rom I get full bars on cell reception but nothing on 3g, i.e. doesn't connect to the internet. I have no wifi at the moment to test it.
Edit. In the settings it says "mobile network, connection failed"
Related
Hi, I have posted this before but it got deleted because I very stupidly posted it in the wrong place.
My question has been answered before due to searching but no one else happens to be in my EXACT situation and I don't want to mess up my phone.
Basically my Desire HD is rooted etc and I want to flash the Android Revolution ROM, but I havent flashed any ROM's since my OLD G1 and now everyone talks about S-OFF etc and I don't understand these, on my G1 it was simply rooting and flashing a Recovery and then flashing a ROM, so basically what do I need to flash this ROM
My situation:
I am running the stock ROM (permroot on 1.32.405.6)
I have stock radio
I have Clockwork mod 3.0.0.6
and Buzz Sense 1.3 + OC (OC'd 1.6Ghz) kernel.
(+Ever since I downgraded from 1.72 I have lost wi-fi, it connected to my wi-fi but I get no internet access through it, its definitely a problem with the phone and nothing else because I have tested my router etc, all my other devices have connectivity through my router)
We all were in your exact situation. The Desire HD employs an extra level of security to prevent users messing with their handsets, S-ON.
You need to turn this off, Ideally ENG (Engineering) S-OFF, before you can make persistent changes to your system.
Have a read through the very helpful guides in the Dev section. They also contain the tools you need. Turning S-OFF should be a one time process only, i.e once you've done it there is no need to repeat it to flash another ROM.
Hope that helps.
andyharney said:
We all were in your exact situation. The Desire HD employs an extra level of security to prevent users messing with their handsets, S-ON.
You need to turn this off, Ideally ENG (Engineering) S-OFF, before you can make persistent changes to your system.
Have a read through the very helpful guides in the Dev section. They also contain the tools you need. Turning S-OFF should be a one time process only, i.e once you've done it there is no need to repeat it to flash another ROM.
Hope that helps.
Click to expand...
Click to collapse
Sorry I forgot to mention that I have SHIP S-OFF and I'm unable to get ENG S-OFF because when I used the Easy S-OFF tool it can only give me SHIP S-OFF for some reason, I cant do anything now since its incompatible with my kernel as well. Can I flash a ROM with just SHIP S-OFF? I don't want to flash any radios because I bricked my G1 about 4 million times when flashing radios.
It you run a 1.32 WWE RUU and revert back to stock you can then reapply ENG S-OFF. A bit of a ball ache I know.
Most ROMs will work just fine with SHIP S-OFF but ENG is usually preferred.
To flash a radio you need Radio S-OFF another beast entirely. However there is a very good too to do it with. No bricks so far and your DHD will then have super CID and be SIM unlocked.
didge3 said:
Sorry I forgot to mention that I have SHIP S-OFF and I'm unable to get ENG S-OFF because when I used the Easy S-OFF tool it can only give me SHIP S-OFF for some reason, I cant do anything now since its incompatible with my kernel as well..
Click to expand...
Click to collapse
Just tick the "I have radio s-off" box and it becomes compatible with everything.
follow my guide in the sig and skip to eng s-off and radio s-off part, or skip to whatever comes next if you've already done them
Tried that, I get a "Connection Error", I have made sure its fully connected as "Disk Drive" and I allow the Super User request when I do it, but it still doesn't work, plus the radio tool just says "Incompatible kernel" - or something like that.
I mainly want to know, can I flash Android Revolution in my current situation, can I flash with just SHIP S-OFF and my current kernel, or do I have to go back to stock kernel, flash the ROM and then flash my kernel back?
and why should I have ENG S-OFF, if it makes a lot of difference I will give it ago, but I mainly want to just flash this ROM to see if it fixes my wifi issue and my camera doesn't drop so many frames! (known issue in 1.32, fixed in 1.7X)
Disk Drive. Yeah, read the guide again more carefully, mate... And change the tool, why are you using easy radio tool!? It won't give you ENG S-OFF. My ENG S-OFF tool will give you that. And it most definitely will not say incompatible kernel if you just tick the box I talked about.
You can flash ARHD now. Do not mess around with it's kernel after flashing, because it comes with the best kernel out there. The kernel has been made to fit ARHD's needs.
jkoljo said:
Disk Drive. Yeah, read the guide again more carefully, mate... And change the tool, why are you using easy radio tool!? It won't give you ENG S-OFF. My ENG S-OFF tool will give you that. And it most definitely will not say incompatible kernel if you just tick the box I talked about.
You can flash ARHD now. Do not mess around with it's kernel after flashing, because it comes with the best kernel out there. The kernel has been made to fit ARHD's needs.
Click to expand...
Click to collapse
I get the same as every other time, downloads the Easy S-OFF tool, "Pushing stuff to SD" Phone says "Unknown has been granted su access" and then the tool says "Error: Connection Problem!" - I get this every time, I have tried re-downloading this software every time, removing the "Unknown" in super user and then re-allowing it when it asks, I still get the same error...
Does it matter that I'm using Windows 7 64-bit?
EDIT: I think I've done it now, I downloaded the latest 2.3 SDK (I had 2.2) which updated my ADB drives, I didn't get the error this time, will boot into H-BOOT and check now.
Are you still using that disk drive mode? Because you should not.
THANKS
I have thanked everyones post, I can confirm my H-BOOT Now says PVT ENG S-OFF, one last thing, I'm all good to flash now? I can just put the ROM (sense version) on my SD card and flash it in CWM, with my current kernel, even though it will over write it with the one included for Android Revolution, I dont have to go back to stock kernel or anything first right?
Thanks again
Have you flashed ClockworkMod Recovery yet? If not download ROM Manager from the Market and flash it from there.
Once that is complete, download ROM, put on SD Card, Recovery, Wipe, Flash, Enjoy.
didge3 said:
Hi, I have posted this before but it got deleted because I very stupidly posted it in the wrong place.
My question has been answered before due to searching but no one else happens to be in my EXACT situation and I don't want to mess up my phone.
Basically my Desire HD is rooted etc and I want to flash the Android Revolution ROM, but I havent flashed any ROM's since my OLD G1 and now everyone talks about S-OFF etc and I don't understand these, on my G1 it was simply rooting and flashing a Recovery and then flashing a ROM, so basically what do I need to flash this ROM
My situation:
I am running the stock ROM (permroot on 1.32.405.6)
I have stock radio
I have Clockwork mod 3.0.0.6
and Buzz Sense 1.3 + OC (OC'd 1.6Ghz) kernel.
(+Ever since I downgraded from 1.72 I have lost wi-fi, it connected to my wi-fi but I get no internet access through it, its definitely a problem with the phone and nothing else because I have tested my router etc, all my other devices have connectivity through my router)
Click to expand...
Click to collapse
andyharney said:
Have you flashed ClockworkMod Recovery yet? If not download ROM Manager from the Market and flash it from there.
Once that is complete, download ROM, put on SD Card, Recovery, Wipe, Flash, Enjoy.
Click to expand...
Click to collapse
Note the very first post "Clockword mod 3.0.0.6" so in answer, yes.
Your good to go then, happy flashing.
I have a fairly strange problem. My wife got tired of the Verizon bloatware on her Dinc2 so I offered to root and flash it to a nice rom. Her only requirements were that it work both as a phone and as a camera. After an uneventful downgrade, s-off, root and CWM, we tried aeroevan's unofficial CM9. We found that the camcorder was broken. Next we tried the MikRoms Incredible 2 HD Rls1. This worked beautifully in every respect except one: when I rebooted the phone, it went into a loop. The phone would boot to the opening lock screen.. in some cases I could even unlock it.. and then either turn off or reboot (which one seemed random). After getting back into the bootloader, I tried all the obvious things:
Wiping all partitions
Reloading the ROM
Trying a different ROM
Flashing back to a Stock ROM + root
Flashing back to stock 2.3.3.
In every case, the phone works perfectly with the new ROM up until it is rebooted, after which it goes into a loop at the lockscreen. The only ROM that DOES work is aeroevan's unofficial CM9. It reboots without any issues, but of course the camcorder and camera flash are busted there. At least it's usable as a phone again.
I've looked and looked, and either my google-fu is failing me utterly or this is a fairly unusual problem. Does anyone have the faintest idea what's going on here and how I can work at fixing it?
This is a well known issue with 605.05 software phones (and several other threads already about this). There is a PSA in Development warning this issue exists. Only guaranteed ROMs without issue are AOSP ROMs. If you want working camera, flash CM7.
I have also heard that flashing the radio packaged with the latest software may fix the issue, you can give that a try. You could also try flashing Condemned Soul's 6.xx ROM in development section.
Sent from my ADR6425LVW using Tapatalk 2
Yah, right after I posted this I saw this:
http://forum.xda-developers.com/showthread.php?t=1746490
Sorry about that. Thanks for the info!
I can confirm that flashing the radio to version 1.09.01.0312 as detailed here resolved the reboot-at-locksceen issue. Using the Incredible 2 HD Rls 1.1 ROM, we now have a working phone, a working camera, and a happy wife!
Thanks!
Verteiron said:
I can confirm that flashing the radio to version 1.09.01.0312 as detailed here resolved the reboot-at-locksceen issue. Using the Incredible 2 HD Rls 1.1 ROM, we now have a working phone, a working camera, and a happy wife!
Thanks!
Click to expand...
Click to collapse
I bet the biggest plus is the happy wife part huh?
Sent from my Incredible 2 using xda app-developers app
Verteiron said:
I can confirm that flashing the radio to version 1.09.01.0312 as detailed here resolved the reboot-at-locksceen issue. Using the Incredible 2 HD Rls 1.1 ROM, we now have a working phone, a working camera, and a happy wife!
Thanks!
Click to expand...
Click to collapse
Glad flashing the new radio got it sorted out!
fsiddique said:
Glad flashing the new radio got it sorted out!
Click to expand...
Click to collapse
Perhaps you can help me sort out an issue. I tried rooting and getting S-Off by using the tacoroot, and flashing a new radio method. I got to the radio part, and got the radio onto the root of the sdcard as per the instructions. The phone boots into fastboot, and it checks the radio file, but it says incorrect file a few times, and then returns to the fast boot menu. I didn't know if it worked, or not so i tried to reboot the phone normally but at the lock screen it reboots.
I tried pushing the radio file using adb but it doesnt seem to want to connect to the phone anymore.
I followed these instructions http://forum.xda-developers.com/showthread.php?t=1751796
After going through some fastboot options I flashed the recovery from fastboot and it booted up and stayed booted, i'm assuming i have to start over, which I don't care about, I just need some advice about what is up with the radio not wanting to flash.
wexx2504 said:
Perhaps you can help me sort out an issue. I tried rooting and getting S-Off by using the tacoroot, and flashing a new radio method. I got to the radio part, and got the radio onto the root of the sdcard as per the instructions. The phone boots into fastboot, and it checks the radio file, but it says incorrect file a few times, and then returns to the fast boot menu. I didn't know if it worked, or not so i tried to reboot the phone normally but at the lock screen it reboots.
I tried pushing the radio file using adb but it doesnt seem to want to connect to the phone anymore.
I followed these instructions http://forum.xda-developers.com/showthread.php?t=1751796
After going through some fastboot options I flashed the recovery from fastboot and it booted up and stayed booted, i'm assuming i have to start over, which I don't care about, I just need some advice about what is up with the radio not wanting to flash.
Click to expand...
Click to collapse
Check the md5sum, might be a bad download. You won't need to start over if you're S-OFF already, you can always flash an AOSP ROM to get it working and go from there.
prototype7 said:
Check the md5sum, might be a bad download. You won't need to start over if you're S-OFF already, you can always flash an AOSP ROM to get it working and go from there.
Click to expand...
Click to collapse
Thanks for the quick reply!
I don't know how to check the md5 without adb. Can I do that without communication to the phone.
How can I determine if I'm S-OFF, or flash a rom? For that matter, how do i start over if i need to.
wexx2504 said:
Thanks for the quick reply!
I don't know how to check the md5 without adb. Can I do that without communication to the phone.
How can I determine if I'm S-OFF, or flash a rom? For that matter, how do i start over if i need to.
Click to expand...
Click to collapse
You can check the md5sum from the phone, just use terminal emulator (might need busybox installed). To check if you are S-OFF, boot into the bootloader and it should say S-OFF.
Sent from my Incredible 2 using Tapatalk 2
I've noticed that I can use fastboot commands, (sorry, never had this complex of a root job before. Normally they are one-clicks) Anyway, I look at the top of the screen when its sitting in the fastboot screen and it says VIVO_W XB Ship S-ON RL I assume that means I'm not S-OFF, and its back to square one. Right?
wexx2504 said:
I've noticed that I can use fastboot commands, (sorry, never had this complex of a root job before. Normally they are one-clicks) Anyway, I look at the top of the screen when its sitting in the fastboot screen and it says VIVO_W XB Ship S-ON RL I assume that means I'm not S-OFF, and its back to square one. Right?
Click to expand...
Click to collapse
Yep. What's the hboot version?
Sent from my Incredible 2 using Tapatalk 2
prototype7 said:
Yep. What's the hboot version?
Sent from my Incredible 2 using Tapatalk 2
Click to expand...
Click to collapse
HBOOT 0.98.0000
in case you want this info too.
Radio - 1.09.01.1111
I tried going back to stock using the following guide http://forum.xda-developers.com/showthread.php?t=1599767
now i have ***LOCKED*** when i boot into fastboot,and i still have the crazy reboot issue when the phone displays the lock screen.
wexx2504 said:
HBOOT 0.98.0000
in case you want this info too.
Radio - 1.09.01.1111
I tried going back to stock using the following guide http://forum.xda-developers.com/showthread.php?t=1599767
now i have ***LOCKED*** when i boot into fastboot,and i still have the crazy reboot issue when the phone displays the lock screen.
Click to expand...
Click to collapse
\
I am at this exact same radio, firmware version, hboot version and situation too any help would be greatly appreciated. Trying to help a co-worker fix his wife's device.
After many hours of reading threads and trying different things, I am posting this.
I have HTC Incredible
Incredible XC Ship S-On
HBoot 0.92.0000
Radio: 2.15.10.07.07
Recovery: CWM v2.5.0.5
Was running Cyanogenmod 7
All was great with this phone (about 1 year) until it randomly started to constantly reboot 1 month ago. I tried to follow some other threads by downloading PB31IMG files, adding them to FAT32 sd card and running in HBOOT. I tried first upgrading the cyanogenmod7, then going to froyo 2.2 and a GB one. Some threads mentioned changing radio version first, tried that but nothing.
When I load PB31Img files from SD, froyo 2.2 says something along the lines of main version old.
When I try to change radio, PB31Img starts to load but does not let me continue and returns to HBoot with no new radio.
I am really not familiar with any phone and I would like to get this back to working. Any help is appreciated, but please be very clear. All I want is this phone to go back to stock, unrooted is fine. Anything to make it work.
Thanks,
griplegraple
griplegraple said:
After many hours of reading threads and trying different things, I am posting this.
I have HTC Incredible
Incredible XC Ship S-On
HBoot 0.92.0000
Radio: 2.15.10.07.07
Recovery: CWM v2.5.0.5
Was running Cyanogenmod 7
All was great with this phone (about 1 year) until it randomly started to constantly reboot 1 month ago. I tried to follow some other threads by downloading PB31IMG files, adding them to FAT32 sd card and running in HBOOT. I tried first upgrading the cyanogenmod7, then going to froyo 2.2 and a GB one. Some threads mentioned changing radio version first, tried that but nothing.
When I load PB31Img files from SD, froyo 2.2 says something along the lines of main version old.
When I try to change radio, PB31Img starts to load but does not let me continue and returns to HBoot with no new radio.
I am really not familiar with any phone and I would like to get this back to working. Any help is appreciated, but please be very clear. All I want is this phone to go back to stock, unrooted is fine. Anything to make it work.
Thanks,
griplegraple
Click to expand...
Click to collapse
Since you're s-on, it's useless to try flashing radios. You're very limited as to what you can do, as you're finding out. Your best bet would be to try the latest RUU (also known as PB31IMG.zip) from here:
http://dinc.does-it.net/Stock_Images/4.08.605.15/
You should be able to flash that through HBOOT even though you are s-on, as it is a stock image.
If you can't get any of the stock images to flash, the next line of attack would be to upgrade HBOOT and unlock the bootloader using HTCdev, as described in this guide:
http://forum.xda-developers.com/showthread.php?t=1600904
If you follow the instructions for downgrading, you will be able to flash the stock image of your choice. Then, re-lock the bootloader using HTCdev and you will be back to stock. Of course, if you follow the whole guide and get s-off, you'll have a lot more options of ways to tackle problems like this.
musical_chairs said:
Since you're s-on, it's useless to try flashing radios. You're very limited as to what you can do, as you're finding out. Your best bet would be to try the latest RUU (also known as PB31IMG.zip) from here:
http://dinc.does-it.net/Stock_Images/4.08.605.15/
You should be able to flash that through HBOOT even though you are s-on, as it is a stock image.
If you can't get any of the stock images to flash, the next line of attack would be to upgrade HBOOT and unlock the bootloader using HTCdev, as described in this guide:
http://forum.xda-developers.com/showthread.php?t=1600904
If you follow the instructions for downgrading, you will be able to flash the stock image of your choice. Then, re-lock the bootloader using HTCdev and you will be back to stock. Of course, if you follow the whole guide and get s-off, you'll have a lot more options of ways to tackle problems like this.
Click to expand...
Click to collapse
The first option above worked in my case. Phone is able to load up and seems to be working fine.
Thread moved. Please post all question threads here in Q&A in future.
Thanks
AvRS
Sent from my Nexus 4 using xda premium
griplegraple said:
Thanks for the reply. I will try the first option, but one thing I have noticed before is that when I use the adb method, I can't get "adb devices" command to work. It outputs "List of devices attached". In my device manager, I have ADB Interface ->HTC Bootloader with the android USB driver installed... Not sure if you can help on this.
Click to expand...
Click to collapse
That could be caused by having adb or the drivers improperly set up on your computer, or it could be because you didn't have USB debugging enabled in the phone's settings. You could try booting your phone into recovery and seeing if you can access it with adb from there if all else fails.
Hi all, I followed Prototype7's method for gaining root and S-OFF via Tacoroot. I then proceeded to install Revolutionary with the CWM recovery.
I am now trying to go back to stock following CondemnedSoul's method, but whenever the PG32IMG.zip update installs, it skips [3] Bootloader and says "Bypassed". It also says "Bypassed" for [7] TP.
The update will say "Complete...", I can boot the phone once and use it normally, but every subsequent attempt to reboot the phone results in boot loops!
What am I doing wrong? Is there some way to flash the bootloader separately? Does my SD card need to be reformatted? Thanks in advance...
swenpro said:
Hi all, I followed Prototype7's method for gaining root and S-OFF via Tacoroot. I then proceeded to install Revolutionary with the CWM recovery.
I am now trying to go back to stock following CondemnedSoul's method, but whenever the PG32IMG.zip update installs, it skips [3] Bootloader and says "Bypassed". It also says "Bypassed" for [7] TP.
The update will say "Complete...", I can boot the phone once and use it normally, but every subsequent attempt to reboot the phone results in boot loops!
What am I doing wrong? Is there some way to flash the bootloader separately? Does my SD card need to be reformatted? Thanks in advance...
Click to expand...
Click to collapse
Did you flash a new radio? Can you tell us what radio you are on (settings > about phone > baseband version).
I did nothing more than the instructions given in the links I posted. To gain root via the tacoroot method I had to flash the 1.09.01.0312_vivow_Radio_PG32IMG.zip after flashing the initial RUU. But note that my radio and everything else, except the bootloader, was successfully updated using the stock image provided by CondemnedSoul.
swenpro said:
I did nothing more than the instructions given in the links I posted. To gain root via the tacoroot method I had to flash the 1.09.01.0312_vivow_Radio_PG32IMG.zip after flashing the initial RUU. But note that my radio and everything else, except the bootloader, was successfully updated using the stock image provided by CondemnedSoul.
Click to expand...
Click to collapse
I didn't use tacoroot (I rooted before it was needed), so I'm not 100% familiar with it. You'll probably have to wait for someone more familiar with it. I was just suggesting something that I've read about other users doing that tripped them up. Good luck with it, you shouldn't have to wait long for someone more helpful to come along.
Thanks for your effort.
Anyone able to help me on this?
Not sure what the [7] is, but the bootloader gets bypassed by Revolutionary's custom hboot so it can't be overwritten by an RUU or OTA, which is why you don't lose S-OFF unless you manually overwrite the hboot partition.
Sent from my SCH-I535 using Tapatalk 2
---------- Post added at 07:49 AM ---------- Previous post was at 07:43 AM ----------
As for your issue, reflash the .0312 (or .0320, that's the one from the ICS leak) radio, the one from CS's image isn't an upgrade even though it probably is version .0622 or something like that, HTC has some weird version naming scheme that they don't even follow half the time.
Sent from my SCH-I535 using Tapatalk 2
prototype7 said:
Not sure what the [7] is, but the bootloader gets bypassed by Revolutionary's custom hboot so it can't be overwritten by an RUU or OTA, which is why you don't lose S-OFF unless you manually overwrite the hboot partition.
Sent from my SCH-I535 using Tapatalk 2
---------- Post added at 07:49 AM ---------- Previous post was at 07:43 AM ----------
As for your issue, reflash the .0312 (or .0320, that's the one from the ICS leak) radio, the one from CS's image isn't an upgrade even though it probably is version .0622 or something like that, HTC has some weird version naming scheme that they don't even follow half the time.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thank you! Flashing the new radio (.0312) seems to have fixed the problem, so far no bootlooping anymore.
By the way, I was on a .1111 radio after flashing the stock image. I would have wrote that sooner, but did not know until I had reflashed the phone once again where I could look at the baseband version, since it was bootlooping.
This is not a necessity, but... I was wondering how a person would flash the stock bootloader and turn it back to S-ON? Just in case I decide to sell my phone in the future, it would be "all stock".
swenpro said:
Thank you! Flashing the new radio (.0312) seems to have fixed the problem, so far no bootlooping anymore.
By the way, I was on a .1111 radio after flashing the stock image. I would have wrote that sooner, but did not know until I had reflashed the phone once again where I could look at the baseband version, since it was bootlooping.
This is not a necessity, but... I was wondering how a person would flash the stock bootloader and turn it back to S-ON? Just in case I decide to sell my phone in the future, it would be "all stock".
Click to expand...
Click to collapse
There's a guide in the general section, basically you have to flash the RUU, then extract the hboot and manually write it to the partition, it's fairly easy to do, easier than rooting it.
Sent from my SCH-I535 using Tapatalk 2
Thanks again! There are so many sections to this forum I had never noticed that sticky. Appreciate the help.
My silly n00b Question(s)
prototype7 said:
There's a guide in the general section, basically you have to flash the RUU, then extract the hboot and manually write it to the partition, it's fairly easy to do, easier than rooting it.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Ok, i can't figure out what a sticky is, nevermind where to find the one you reference... Sorry.
I love XDA, it helped me root my dInc2 replacement, and that one's replacement (both after the previous phone's charge port died), and i just love it, BUT i've never had to use it except these two times, so i haven't figured out the forum stuff - like stickies - especially since i usually use NoScript normally and i don't really understand the general vs Q&A distinctions between groups of threads...
In any case - i haven't been able to find the sticky you referenced, and my searches have failed to find recent instructions regarding manually flashing the Hboot -- everything i found had download links that didn't work, except CS's stock ROM (as mentioned by the OP in this thread) - and now i've got that installed on my phone-to-send-back, so i've have successfully returned the ROM to a stock 2.3.4 GB using CS's post here on XDA, and from what i can tell/remember, flashing the HBOOT to stock (.97) will put it back exactly how it was when i got it last year - as i had to downgrade the OS but i don't think i had to touch the HBOOT (i got this phone in late March 2012)
So i'm now trying to rectify the issue that i don't know where to get the Hboot to manually flash, and, even if i had the file, i haven't found out if there is a ADB over TCP-IP that works when your USB/charge port has basically disconnected itself from the motherboard.
I was hoping that someone here might be able to help me either find the hboot file or extract what i need from CondemnedSoul's RUU (as seems to be described in prototype7's post), and give me the commands i need to do the manual flash...
If i could also get ADB over TCPIP advice, that would be awesome, but the former would be a good start...
Verizon has started to nag me for not returning the old phone sooner...
Thank you!
Also - thanks to Prototype7 for his awesome guide to s-off methods/rooting the Dinc2 -- was a life-saver for rooting the new phone so i could make use of my clockworkrecovery backup... (after some boot-looping horror, when i got an error during the update of the radio using the tacoroot method -- i restarted again from a different windows machine and it worked fine - i think the issue was the drivers on the other machine -- i'd used it to root the earlier phone, and i think it had weird drivers or something)
wntrequinx said:
Ok, i can't figure out what a sticky is, nevermind where to find the one you reference... Sorry.
I love XDA, it helped me root my dInc2 replacement, and that one's replacement (both after the previous phone's charge port died), and i just love it, BUT i've never had to use it except these two times, so i haven't figured out the forum stuff - like stickies - especially since i usually use NoScript normally and i don't really understand the general vs Q&A distinctions between groups of threads...
In any case - i haven't been able to find the sticky you referenced, and my searches have failed to find recent instructions regarding manually flashing the Hboot -- everything i found had download links that didn't work, except CS's stock ROM (as mentioned by the OP in this thread) - and now i've got that installed on my phone-to-send-back, so i've have successfully returned the ROM to a stock 2.3.4 GB using CS's post here on XDA, and from what i can tell/remember, flashing the HBOOT to stock (.97) will put it back exactly how it was when i got it last year - as i had to downgrade the OS but i don't think i had to touch the HBOOT (i got this phone in late March 2012)
So i'm now trying to rectify the issue that i don't know where to get the Hboot to manually flash, and, even if i had the file, i haven't found out if there is a ADB over TCP-IP that works when your USB/charge port has basically disconnected itself from the motherboard.
I was hoping that someone here might be able to help me either find the hboot file or extract what i need from CondemnedSoul's RUU (as seems to be described in prototype7's post), and give me the commands i need to do the manual flash...
If i could also get ADB over TCPIP advice, that would be awesome, but the former would be a good start...
Verizon has started to nag me for not returning the old phone sooner...
Thank you!
Click to expand...
Click to collapse
This is the guide I was referencing: http://forum.xda-developers.com/showthread.php?t=1466295
For ADB over TCPIP, I use ADBWireless off the market, but instead of using the adb connect command with the info it shows, use your phone's IP address shown under About phone>Status (I think that's where it is).
prototype7 said:
This is the guide I was referencing: http://forum.xda-developers.com/showthread.php?t=1466295
For ADB over TCPIP, I use ADBWireless off the market, but instead of using the adb connect command with the info it shows, use your phone's IP address shown under About phone>Status (I think that's where it is).
Click to expand...
Click to collapse
YOU ROCK. - thanks for the quick reply.
I read the guide you referenced - but the links are down, so i'll add a reply and see if that thread's OP can re-upload. If that seems to still be the correct way to un-root/S-on, then i'll see what i can do..
I had a bunch of questions, but i think I figured out the answers... i just need to go home from work and actually try out following those directions...
wntrequinx said:
YOU ROCK. - thanks for the quick reply.
I read the guide you referenced - but the links are down, so i'll add a reply and see if that thread's OP can re-upload. If that seems to still be the correct way to un-root/S-on, then i'll see what i can do..
I had a bunch of questions, but i think I figured out the answers... i just need to go home from work and actually try out following those directions...
Click to expand...
Click to collapse
See my reply in that thread, gave you updated links.
I am at a loss of things to try with this Evo which I have no history of.
After initially being stuck at 4-triangles. I managed to flash the ENG 0.76 bootloader. Found out that:
S-OFF
Radio: 2.15.00.09.08 -some sort of Chinese radio?
I've tried it many different ways with RUUs, fastboot and PH36IMG, but RADIO_V2 repeatedly fails to flash.
I can also flash any recovery, but it fails to load, getting stuck at the Evo splashscreen, so that is also a problem. Most partitions flash nicely in fastboot. A successful system flash will result in a stuck Evo splashscreen, though.
Is there any way out of this? Perhaps by using one of the elevated commands in the ENG bootloader? I don't know how to get ADB running either, since I'm stuck in fastboot and have no idea whether USB debugging was on earlier. I do have a Linux box if that helps.
Any help would be greatly appreciated. Thanks!
Its a PC36IMG* not PH36IMG
Sent from my SPH-L710 using xda premium
Typo, sorry.
Sent from my Galaxy Nexus using xda premium
I might need to clarify a little.
I have absolutely zero history of this phone. None whatsoever.
1. Currently on ENG 0.76. I received the phone with no access to the bootloader, stuck at the HTC screen with triangles in each corner. I flashed the ENG 0.76 hboot via fastboot and that's what I'm on right now. Works fine.
2. I have no idea how it got to this radio version. Seems like a Chinese UIM radio. Got the phone from a friend who got it from an auction in Burma.
4. Flashing any radio in hboot will result in [see attachment]. Flashing in fastboot- see 2nd screenshot above. Fails either way, and I've tried multiple radios. Tried under multiple hboots, too. No dice.
5. Stock or custom recovery will flash fine but will get stuck at the white splashscreen if I try to enter it.
6. Bootloader is perfect. Works like a charm.
The only idea I can come up with is using an elevated command in fastboot oem which could reformat my radio partition somehow. I don't know whether I have ADB either. I have some experience with diag mode and JET on the HOX.
Any ideas?
Have you tried an RUU? That may work and give you an entire stock unrooted and fully working system. If not, try flashing a different radio. That one could be out of date or even corrupt.
Sent from my SPH-L710 using xda premium
death-by-soap said:
Have you tried an RUU? That may work and give you an entire stock unrooted and fully working system. If not, try flashing a different radio. That one could be out of date or even corrupt.
Click to expand...
Click to collapse
I've tried countless RUUs, both Froyo and GB, Windows exe and PC36IMG. Nothing works. All partitions flash fine BUT the radio.
temuryusuf said:
I've tried countless RUUs, both Froyo and GB, Windows exe and PC36IMG. Nothing works. All partitions flash fine BUT the radio.
Click to expand...
Click to collapse
Is it possible for you to update the hboot to something 2.10? It may be the bootloader is preventing that flash.
Sent from my SPH-L710 using xda premium
death-by-soap said:
Is it possible for you to update the hboot to something 2.10? It may be the bootloader is preventing that flash.
Click to expand...
Click to collapse
Obviously this is not the only hboot I've tried. I've gone to 2.10, even 2.18, tried there, come back down to ENG, tried again; it's just repeatedly failing. I'm not giving up hope due to the simple fact that the bootloader works and there MUST be a way out. Like I mentioned earlier I'm thinking one of the high level commands, but I have no idea what to do with them. Could anybody lead me in the right direction?
Flashing the engineering Hboot 0.76 will only work on the older Evos with the older hardware partitions without causing permanent damage. If you have one of the newer ones, then your phone is already done.
Sent from my SAMSUNG-SGH-I747 using xda premium
shortydoggg said:
Flashing the engineering Hboot 0.76 will only work on the older Evos with the older hardware partitions without causing permanent damage. If you have one of the newer ones, then your phone is already done.
Click to expand...
Click to collapse
I've only recently put 0.76 on after trying the newer Hboot versions. I found out that I was on 2.02 initially when I had the 4 triangles- I had to RUU because there was no accessible Hboot to fall back upon anyway. I then found a 2.02 img and flashed that through fastboot, which is when the bootloader actually started working. I'm using 0.76 now because it just seems to work better with commands.
What exactly does "permanent damage" imply in this case? Because the problem remains either way- RADIO_V2 fails to flash. All other partitions have not a single problem between them.
Is there a way where I can completely clear out the emmc, repartition it correctly and take steps from there?
At this point of time I'm rather certain mine is an older HW revision. How do I find out anyway?
The newer hardware started with Hboot 2.02 while the old ended with 0.97. You would never OTA to 2.02 from 0.97, but have went directly to 2.10 unless you flashed a Hboot with 2.02 or ran a RUU with that Hboot version. I actually made a post about a year and a half ago on how to tell, so if you phone ever boots again, I could point you to that post.
Right now, it's good that Hboot 0.76 seems to be doing something, but I'm afraid the radio may have been flashed with something that did not want to be there.
Sent from my SAMSUNG-SGH-I747 using xda premium