Related
Hi all,
I was trying to downgrade my HTC Flyer (3G and WiFi EU version, HTC_001) to gingerbread. Everything seemed to work as instructed but I'm now stuck on the white loading screen with the HTC logo on it, and can neither boot or communicate with the device.
For the downgrade I followed the instructions on this thread really carefully:
http://forum.xda-developers.com/showthread.php?t=1428104
I was using the 2.23.405.3 RUU.
To begin with, I'd upgraded to honeycomb by following Paul's guide, that had all been working fine for the last 6 months or so.
I've managed to power down the flyer through the adb fastboot, but that's as far as I can get. I'm not very experienced with this, so if anyone can make some suggestions on steps I could take to get my flyer working again I'd really appreciate it.
Many thanks,
Andii
Get into hboot and tell me your hboot version and if it says unlocked. I think you followed the wrong procedure and likely have hc hboot with gb system or something like that
Hi,
Thank you for replying. My Hboot is 6.11.1111
Does it say unlocked at the top or s off
Sent from my HTCEVOV4G using xda premium
I don't know, because it won't turn on now...
when I went through the process of the downgrade, at one point it gave me an instruction which involved locking. The command prompt said it was "already locked".
If it is not charging you will have to try to charge the battery independent of your flyer. There are some threads showing how to do this. Google it. I think you were soff hc and you flashed gb. The ruu can not overwrite the soff hboot so you are left with miss match parts thus no charge
Sent from my HTCEVOV4G using xda premium
Thanks so much for your help. I've found some of those threads; I've gotta say, It looks pretty complex and I think taking it apart is way beyond my capacity to sort. Rather regretting getting into this now, lesson learned! Is there no other option? If I send it off, obviously my warranty is voided, but will they repair it (at my cost of course)?
I'll read the charging threads thoroughly, but am really anxious about the process.
They should be able to repair it easily
Sent from my HTCEVOV4G using xda premium
Greets,
I've more or less exactly the same problem. I was on some Leedroid Custom HC version. For upgrading to a newer Leedroid Version I was downgrading back to Gingerbread using globatrons Downgrade Thread.
Worked fine until first reboot.
First I used RUU_Flyer_TMO_DE_2.27.111.1 (cause I have a 3G/Wifi T-Mobile branded device)
and later I tried again via this RUU_Flyer_HTC_WWE_2.23.405.3 (Stock version?!)
Still not working.
Here some details:
I still can access this revolutionary Bootloader (Vol Down + Power) and I think fastboot commands are still useable.
Here's what is written there
FLYER PVT SHIP S-OFF RL
HBoot Version is 6.11.1111
MICROP-0950
RADIO-3809.07.04.06_M
eMMC-boot
You have an idea how to fix it?
Thanks in advance !
Which downgrade did you use? Link the thread
mcord11758 said:
Which downgrade did you use? Link the thread
Click to expand...
Click to collapse
Hej,
I used the downgrade procedure from this thread http://forum.xda-developers.com/showpost.php?p=18508210&postcount=1 starting from "Downgrade".
I didn't create a goldcard, I was "just" using the RUUs mentioned in my last post.
Thx!
Your hboot said s off. To me that means you had s off hc which could not be downgraded using the method you tried. You likely have hc hboot and gb system. Go to easy s off hc thread and look at post 3. Download the correct downgrade package, 3G or wifi, follow instructions. Then flash gb ruu or gb rom
mcord11758 said:
Your hboot said s off. To me that means you had s off hc which could not be downgraded using the method you tried. You likely have hc hboot and gb system. Go to easy s off hc thread and look at post 3. Download the correct downgrade package, 3G or wifi, follow instructions. Then flash gb ruu or gb rom
Click to expand...
Click to collapse
This Post http://forum.xda-developers.com/showpost.php?p=19607833&postcount=3 or you mean a different one?
That is it
mcord11758 said:
That is it
Click to expand...
Click to collapse
Hey Mcord,
thank you very much for your help, worked fine for me!
Now I just set up the gingerbread base (in S-OFF) on which I can install my ROM, didn't I?
It's written in the post that I can use the base for installing a HC Custom ROM (which was my intention) - can I just drop the Leedroid-ROM-ZIP on my SDcard and install it right away via the Bootloader?
Thanks again!
You have me all confused now. You were on hc with s off, why were you looking to go back to gingerbread? You could of just flashed the rom. Now you are on gb s off. To be able to flash hc roms use light package in op of same thread to get back to hc s off then flash lee rom.
What made you think you had to go back to gingerbread
I read somewhere in here http://www.modaco.com/topic/345950-...g-honeycomb-on-your-flyer-the-complete-guide/ that you need to go back to Gingerbread before installing another HC custom release. I was wondering a bit myself, though.
In Leedroid FAQ also globatron's instructions (http://forum.xda-developers.com/showpost.php?p=19607802&postcount=1) are linked at the Install FAQ. So I was just working off the instructions. First time flashing to Honeycomb was also more or less like this - I was on some GB version and I had to downgrade to a lesser version number of GB before actually going to Leedroids HC release; so this time I was not questioning myself for a sense behind it ^^
With light package I guess you mean the Instructions Part 2 in http://forum.xda-developers.com/showpost.php?p=19607802&postcount=1 this thread?
3 has the light updates meant to be used if you intend on flashing a rom immediately. You got confused a bit with s off and htc dev unlock. You were s off and free to flash roms
Hello everybody
The new ICS update for the ROGERS EVO 3D just came out yesterday, so I restored my phone to the original firmware (via restoring the backup I did in the recovery) and then proceeded to download the OTA update. After it finished, the phone rebooted into the recovery (i have 4-ext touch recovery) and started installing. After it finished, the phone rebooted and then got stuck on the white HTC screen. I managed to enter the recovery again and restore the original firmware again. What is that I'm doing wrong here? Here is some helpful info:
Rogers EVO 3D, GSM version
Unlocked bootloader (HTCDEV method), S-ON
carrier unlocked
HBOOT 1.49.0008
OS is rooted
I'm in the same boat but I'm not able to do a recovery. I went through the update process and when the phone rebooted it got stuck on the white htc screen. I can get it into the bootloader menu but when i choose recovery it starts but then i get an error with a pic of the device and the red yield sign. If i choose factory reset it just gets stuck at the white htc. I read some other posts and I saw that having an unlocked bootloader may cause issues with updates so that may be your issue as for me, I'm not sure what I can do. I may just need the actual update file to redo the update but I'm not sure where to find it.
Same here, but I don't get half way through the ota update before I see the red triangle and exclamation mark. Phone will boot into stock recovery (which I would assume you need instead of modded recovery) and the update starts, but doesn't complete. I pull the battery and the phone boots up normally. Just can't seem to get through the update. Could be something to do with being s-off I would guess.
EJ
madmajd said:
Hello everybody
The new ICS update for the ROGERS EVO 3D just came out yesterday, so I restored my phone to the original firmware (via restoring the backup I did in the recovery) and then proceeded to download the OTA update. After it finished, the phone rebooted into the recovery (i have 4-ext touch recovery) and started installing. After it finished, the phone rebooted and then got stuck on the white HTC screen. I managed to enter the recovery again and restore the original firmware again. What is that I'm doing wrong here? Here is some helpful info:
Rogers EVO 3D, GSM version
Unlocked bootloader (HTCDEV method), S-ON
carrier unlocked
HBOOT 1.49.0008
OS is rooted
Click to expand...
Click to collapse
Same problem but whit s-off
I have been predicting that this would happen... ICS failures with non-standard HBOOTs. Good luck.
Probably will have to wait for an RUU or custom.
I'd recommend using the GB ruu to get you back to full stock. Always found Rogers ota updates (possibly all carriers?) won't install if you're rooted or using a custom recovery.
I had to install the ruu via renaming the rom.zip to PG86IMG.zip and copying it to the sd card so that the bootloader would auto flash it. Running the ruu exe tossed up all kinds of errors.
It will put everything back to Rogers stock. After that just setup wifi and do the 2 Rogers OTA updates.
Once in ICS, it's easy peasy to get recovery and root back.
Also, for what it's worth, Go Backup is awesome for going rom to rom and not needing a full backup. Use it on rooted rom, then use it to restore after rooting new rom. Will do all your apk's and everything.
1st post here after years of lurking. Yay.
wikkid said:
I'd recommend using the GB ruu to get you back to full stock. Always found Rogers ota updates (possibly all carriers?) won't install if you're rooted or using a custom recovery.
I had to install the ruu via renaming the rom.zip to PG86IMG.zip and copying it to the sd card so that the bootloader would auto flash it. Running the ruu exe tossed up all kinds of errors.
It will put everything back to Rogers stock. After that just setup wifi and do the 2 Rogers OTA updates.
Once in ICS, it's easy peasy to get recovery and root back.
Also, for what it's worth, Go Backup is awesome for going rom to rom and not needing a full backup. Use it on rooted rom, then use it to restore after rooting new rom. Will do all your apk's and everything.
1st post here after years of lurking. Yay.
Click to expand...
Click to collapse
Alright thanks a lot
Just an update on what I did. I was able to reload the stock gb rom for rogers using the exe file, then I went through the 2 updates that came up when checking and ics is now up and running on my phone. However in my attempts of trying to fix the original problem, I managed to re-lock my bootloader before flashing to stock rom and I had s-on the whole time. hope this help.
i switched to stock like.. a week back?
jus got ota on 4th
i WAS rooted and using juopunutbear's hboot *u can jus get the hboot from their website*
so i jus flashed back stock recovery.. and updated.. and success.. lost root though.. and i was back to stock bootloader..
used the PG86IMG with juopunutbear's bootloader and 4ext recovery.. and flashed cwm supersu.. v0.91 i think.. i dunno.. latest one.. and bam.. im on stock.. rooted.. and works perfectly..
Possible sollution
Maybe try flashing one of the customized ROMs that are based on the latest OTA update. I'm sure Anryl's newest rom is blazing-fast and stable. You can find it in the gsm android development forum and flash it via recovery. Make sure you have the latest 4ext recovery installed, though.
where can a i find that stock rogers rom i modified mine and that might be the reason i get a security failure in hboot. s is on. when i run the ruu file in windows to downgrade i get error 155. when i run the the update from about phone. it locks up with blue android guy and yellow exclamation mark. i remove the battery and she boots fine with no changes.
I am trying to do same. Get stuck on HTC screen. I have S-ON. Was on cobra 2.4 prior.
If anyone can give details on how to fix it, it would be great! Please no saying "install exe". I need to know which exe etc.
just wanted to tell everyone that in order for the ota update to work properly, you need to be running stock unrooted firmware with a locked bootloader. Just relock your bootloader, reinstall the stock firmware, upgrade to ics via ota, then re-unlock and re-root.
Hi
I have a HTC EVO 3D from Rogers that was got messed up during changing networks... rooted the phone for no apparent reason... to now get a update for it for ics from the provider and it bricked the phone.
It's stuck at HTC boot screen, can get fastboot USB from bootloader. recovery gets a ! in a triangle and factory reset doesn't work, freezes at splash screen after restarting the phone. Was stupid not making a backup or searching for programs to back it up before I went ahead and clicked update
It has HTC boot-loader 1.49 s-on but is rooted.
I am looking for clear(fix my evo for dummies) step by step instructions with correct installation for my model of phone, HTC EVO 3D Rogers GSM, or anything that could replace the os to get my phone to be useful again I'm currently using my backup phone a HTC G1 HTC ftw
Try kingcobra's rom, ota from rogers will not boot due to the fact that your phone is rooted, kingcobra's rom is based on rogers ota, flash it and leave it.
Sent from my HTC EVO 3D X515m using xda premium
Davideichler7 said:
Hi
I have a HTC EVO 3D from Rogers that was got messed up during changing networks... rooted the phone for no apparent reason... to now get a update for it for ics from the provider and it bricked the phone.
It's stuck at HTC boot screen, can get fastboot USB from bootloader. recovery gets a ! in a triangle and factory reset doesn't work, freezes at splash screen after restarting the phone. Was stupid not making a backup or searching for programs to back it up before I went ahead and clicked update
It has HTC boot-loader 1.49 s-on but is rooted.
I am looking for clear(fix my evo for dummies) step by step instructions with correct installation for my model of phone, HTC EVO 3D Rogers GSM, or anything that could replace the os to get my phone to be useful again I'm currently using my backup phone a HTC G1 HTC ftw
Click to expand...
Click to collapse
Go to the gsm development forum and download the RUU for the phone, and restore it to stock unrooted OS. Before you do that though, make sure that your phone's BOOTLOADER IS LOCKED. Look up how to re-lock your bootloader. After you relock your bootloader, you can proceed with restoring the phone.
Soooo.... basically, what I'm getting from this is, if you like having a locked bootloader, CWM and root, don't bother trying to install this OTA update because it's a headache. Agree?
The phone's not mine, it's my wife's, and she doesn't want anything special or like the idea of me messing around in her phone.
I was about to install this late last night, just about to hit that button, then I thought, "what about the bootloader? what about root? what about the fact that it's now unlocked and being used on a carrier other than Rogers?"
Hello,
Right, I am aware that I've probably made a huge mistake, but I thought, "hey, warranty void because of my screen, why not?", but I have searched and searched and was up until three this morning trying to find a solution, but I only kept getting confused (bare in mind I'm only sixteen).
I rooted my phone using the HTCDev method, and flashed the LoLic Sense ROM, it worked and I turned my phone back on and it got stuck on the bootscreen. So, I downloaded the RUU and tried to go back to stock, and it kept failing. I even tried the PG86IMG.zip and even that didn't work. So, I downgraded to the LEEDroid ROM that came with the revolutionary package I'd used before the official update to ICS, and now I can't even get past the initial HTC screen.
Please can anybody help me get back to stock on my phone? I've managed it before, but this time I keep seeming to come up short.
Thank you
EDIT:
I'm on HBOOT 1.53.0007 - after updating to the official ICS.
I've tried downgrading using the Gingerbread RUU and it won't install on the phone. I can't S-OFF using the wire trick because I'm afraid to break it even more.
I've tried flashing the rooted GB zip in clockworkmod and it says its installed, but I can't turn the phone on and it only gets to the first white HTC screen and then turns itself off.
I'm terrified that I may have broken my only phone and I don't know what to do, please can somebody help me?
If you are S-ON HTC Dev unlocked you need 4ext with smartflash or fastboot flash boot boot.img to install the kernel.
Ok, so long story short, I got fed up with the latest update (4.05.605.14) downloading onto my phone and then failing every time it tried to install itself. Deferring didn't work and it would do it about 5 times a day. So I decided to try and manually install it. That was a mistake, as I think I used a method that was for S-Off instead. I ended up with a phone that wouldn't boot past the 4G LTE screen. I have searched the forums all day and tried everything I could, including trying to install the 3.14.605.12 RUU to take me back to stock. Even locked I can't get it to flash. It checks the PH98IMG.zip but when it installs it fails and says that the "Main Version is older!" So at this point I'm lost. If any of you have any ideas and can help me get my phone back it would be so great.
Thanks in advance.
S-On
Locked
HBOOT: 2.28.0000
Radio: 2.2310.0123r/2.23.10.0124r
Recovery Amon Ra 3.14
You might just need to flash the proper kernel. Pull the boot.img from the ROM based on the OTA (linked below) and flash it and see if that does it. s-off phones don't need to flash kernel separately.
fastboot flash boot boot.img
http://forum.xda-developers.com/showpost.php?p=40949419&postcount=11
no boot
Here on xda is Hassoon's Rezound All-In-One kit #3.2.
It has a tool to set main version for you. And more.
Do it in Fastboot.
michaelbsheldon said:
Here on xda is Hassoon's Rezound All-In-One kit #3.2.
It has a tool to set main version for you. And more.
Do it in Fastboot.
Click to expand...
Click to collapse
Is that going to work for an RUU? The RUU will want to actually change the hboot version to an older one.
I think I saw an RUU feature in Hassoon's Rezound Toolkit as well.
You can always flash just a radio or hboot later if you want.
It does have a Mainver Error Fix listed so it would be worth a try. Also downloading the kernel to try and flash that. Thank you both for the suggestions. Hopefully they keep coming in because I've tried about everything I've seen in the forums to date...
well neither of those worked. The all in one couldn't even find the phone. Guess I severely borked it... :crying:
borkness
Gonna be a lot of work, but you may have to re-educate your phone with
RUU 3.14.xxxx.xx.
After that, install AmonRa recovery. Then mebbe a custom rom or your old nandroid backup.
That's all assuming you can get into fastboot-usb.
I have no problem getting into fastboot usb. It's about the only thing I don't have a problem with. How does one reducate a phone?
There's no RUU that you can run since you have a newer hboot than all of them.
Try flashing the ROM linked in my post #2 above. It's stock based on the OTA. That worked for someone else who was having issues with other methods. Flash the boot.img after you flash the ROM.
Yep
What Feralicious said...
This might help
kirkman81 said:
Ok, so long story short, I got fed up with the latest update (4.05.605.14) downloading onto my phone and then failing every time it tried to install itself. Deferring didn't work and it would do it about 5 times a day. So I decided to try and manually install it. That was a mistake, as I think I used a method that was for S-Off instead. I ended up with a phone that wouldn't boot past the 4G LTE screen. I have searched the forums all day and tried everything I could, including trying to install the 3.14.605.12 RUU to take me back to stock. Even locked I can't get it to flash. It checks the PH98IMG.zip but when it installs it fails and says that the "Main Version is older!" So at this point I'm lost. If any of you have any ideas and can help me get my phone back it would be so great.
Thanks in advance.
S-On
Locked
HBOOT: 2.28.0000
Radio: 2.2310.0123r/2.23.10.0124r
Recovery Amon Ra 3.14
Click to expand...
Click to collapse
Hi, I had similar issues. ROM and Kernel weren't matching. See this thread where I got some great help. Hopefully it gets you on your way too.
http://forum.xda-developers.com/showthread.php?p=41261391&posted=1#post41261391
Thanks for the suggestions, all. I had to switch phones finally because nothing was working but I'll give the last two suggestions a try when I have some time. I'll let you know if anything worked.
Sent from my DROID BIONIC using xda app-developers app
Hi guys.
I was trying to do one of two things. Either get to stock ICS with the RUU or get to an older stock version so that my phone would update itself.
I ran the ICS RUU and ran into an issue. Im on Hboot 2.28 Radio 2.23.10.0123r/2.23.10.0124r
I am S-On and relocked to get run the RUU.
I got an error as it said the Hboot version is older. Now I am stuck on the Bootloader with TAMPERED, RELOCKED, and Security Warning.
I should have known that I potentially had a leaked Hboot version but it was so long ago I forgot.
What can I do? Iv been googling and searching threads without much luck. Do I have to S-off? Can I S-off from this position? The other issue I keep running into is dead file links.
brownsfan said:
Hi guys.
I was trying to do one of two things. Either get to stock ICS with the RUU or get to an older stock version so that my phone would update itself.
I ran the ICS RUU and ran into an issue. Im on Hboot 2.28 Radio 2.23.10.0123r/2.23.10.0124r
I am S-On and relocked to get run the RUU.
I got an error as it said the Hboot version is older. Now I am stuck on the Bootloader with TAMPERED, RELOCKED, and Security Warning.
I should have known that I potentially had a leaked Hboot version but it was so long ago I forgot.
What can I do? Iv been googling and searching threads without much luck. Do I have to S-off? Can I S-off from this position? The other issue I keep running into is dead file links.
Click to expand...
Click to collapse
So I think I found out what I did. 2.28 is the Global version. I must of rooted that version and flashed roms. I wanted to unroot and get back to stock software version.
Where should I go from here? Is there an RUU for the ICS Global? I can not seem to find one.
Have you tried unlocking the bootloader again?
Edit: I searched for a long time (a few days ago) but couldn't find any information on S-Off, not going back to stock for people on the latest OTA. I'm not the best person to give advice, but if you're on the current OTA, I don't think you can use the RUU.exe.
Also, you can't downgrade if you're S-On - only upgrade..
Sent from my ADR6425LVW using xda app-developers app
Thingula said:
Have you tried unlocking the bootloader again?
Edit: I searched for a long time (a few days ago) but couldn't find any information on S-Off, not going back to stock for people on the latest OTA. I'm not the best person to give advice, but if you're on the current OTA, I don't think you can use the RUU.exe.
Also, you can't downgrade if you're S-On - only upgrade..
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
Yes I can unlock again and that does get me unstock from the boot screen but still cant get where I want. Hmm.
I wonder if you can fastboot-flash the older kernels, using a computer, then flash the old stock ROM, lock the bootloader, then run an RUU.. Can anyone confirm this? Sounds too simple to work on an HTC phone.
Edit: No, of course that doesn't work. Sorry, I can't really offer any more help.. I'll have to just hope that someone more knowledgeable can take over.
Sent from my ADR6425LVW using xda app-developers app
Be prepared, I get rather long winded.
If you were on the most current 4.05.605.14 with S-on which based on what you list as the radios and hboot is what it appears you were on, then you are in a difficult spot. The really bad news is the only RUU you would be able to use is the 4.05.605.14 and no one has admitted to being able to get ahold of. The most current one available is 3.14.605.12 but that is useless to you. You would have to S-off to go back to stock but would have to have a working rom to do it. It's not impossible but it aint easy. I just had to do it about a month ago when I was trying to S-off my replacement Rezound. It came with the most current stock ROM and I didn't bother reading up on the current ControlBear method. In the past, you had to have a rooted rom in order to S-off. So of course, I unlocked the bootloader, flashed AmonRa 3.15 and then used superuser to root it and then went about trying to S-off. I couldn't find my previous windows based versions of ControlBear so I went about making a live cd ubunto disk and trying to S-off. It wouldn't work. Then I read the unlimited.io site instructions and found that the current version needs the unrooted stock rom to succeed. I really never paid attention to unrooting before because if I had to do it, I could always just run the factory wipe and root would be gone but not this time. It kept showing that I was rooted. So I tried wiping data, cache, dalvik cache, and after that didn't work, I wiped the system. Very bad move on my part. Now I couldn't get past the bootloader. I thought I was done for because I knew with S-on, there was no going back and the global rom RUU was still not available.
After trying all kinds of things I ended up
1. downloading the 4.05.605.14 stock rooted rom listed HERE (Thanks MicroMod777) in the Rezound Development section.
2. Then downloaded the current firmware.zip from HERE (Thanks Flyhalf205) and then extracted the recovery.img along with the hboot .nb0 file from it.
3. I then created 2 separate custom ph98img.zip for each so I could always reinstall the stock hboot and the stock recovery.img.
4. I extracted the boot.img from the rooted rom and flashed that first. I don't remember if I did it via adb in fastboot usb or with another ph98img.zip and then
5. I made sure that my bootloader was unlocked and then installed AmonRa as the recovery
6. Then used AmonRa to flash the stock rooted zip file. I then wiped the cache 3 times and the dalkvik cache 3 times.
I let the phone reboot and I was back to a working phone.!!! Then I found out that it was rooted with SuperSu which gives you the option of doing a full permanent unroot which I did. I then put that ph98img that I had made that had the stock recovery.img on it and flashed that in the bootloader. After rebooting I now had a fully stock phone and proceeded to do the S-off. I left the bootloader unlocked as directed by the unlimited.io site. I had limited experience with ubunto but found THIS PAGE that helped walk me through it. I followed it exactly and ended up with an S-off phone. One thing that wasn't clear to me was how to open a terminal in ubunto but I figured that out after trial and error. IIRC, I clicked on the home tab on the left and then in the search box, typed terminal. The first icon that was shown was a terminal emulator and I used that for the commands.
Now I still wasn't finished. I ended up relocking the bootloader but didn't like the relocked and tampered flags that were showing. So I ended up running the most recent RUU (3.14.605.12 found HERE and I now had a ***LOCKED*** bootloader and then let the phone reboot. After it rebooted, I hit the home key and bypassed the setup. I then got into settings and then into software update and let it update. It did a small update and then had to repeat the reboot, bypass setup, and software update. This time it did the global update. I let it reboot but this time, I ran the setup. Once I was up and running, I again went into bootloader and reinstalled AmonRa and used the 3.16 version and made sure to do a nandroid before doing anything further. After that, I got ahold of SuperSu 1.51 and flashed that in the AmonRa recovery. I now had a ***LOCKED*** stock rooted Rezound and several nandroid backups of both fully stock and rooted. Which turned out to be a great idea because not even 3 weeks later after this, the phone started malfunctioning (power button) and a problem with the camera so it got replaced and I had to put it back fully stock. I was already setup for this. I unrooted, put the stock recovery back on, and made it S-on. When the replacement came, I immediately unlocked it, did the S-off (only took one try), relocked, ruu'd back to 3.14.605.12, updated to global rom, flashed AmonRa, and restored with my most recent rooted nandroid. and I am back up and running a whole lot sooner...
I hope this helps.
Very much so! Thank you. If I could hit the thanks button 10x I would.
Im sure im not the only only to have the Hboot 2.28 issue.
hey man you still around ? i need some help with a situation like this
dust906 said:
hey man you still around ? i need some help with a situation like this
Click to expand...
Click to collapse
I replied to you in your thread.
S-On Locked stock !
mikeyk101 said:
Be prepared, I get rather long winded.
If you were on the most current 4.05.605.14 with S-on which based on what you list as the radios and hboot is what it appears you were on, then you are in a difficult spot. The really bad news is the only RUU you would be able to use is the 4.05.605.14 and no one has admitted to being able to get ahold of. The most current one available is 3.14.605.12 but that is useless to you. You would have to S-off to go back to stock but would have to have a working rom to do it. It's not impossible but it aint easy. I just had to do it about a month ago when I was trying to S-off my replacement Rezound. It came with the most current stock ROM and I didn't bother reading up on the current ControlBear method. In the past, you had to have a rooted rom in order to S-off. So of course, I unlocked the bootloader, flashed AmonRa 3.15 and then used superuser to root it and then went about trying to S-off. I couldn't find my previous windows based versions of ControlBear so I went about making a live cd ubunto disk and trying to S-off. It wouldn't work. Then I read the unlimited.io site instructions and found that the current version needs the unrooted stock rom to succeed. I really never paid attention to unrooting before because if I had to do it, I could always just run the factory wipe and root would be gone but not this time. It kept showing that I was rooted. So I tried wiping data, cache, dalvik cache, and after that didn't work, I wiped the system. Very bad move on my part. Now I couldn't get past the bootloader. I thought I was done for because I knew with S-on, there was no going back and the global rom RUU was still not available.
After trying all kinds of things I ended up
1. downloading the 4.05.605.14 stock rooted rom listed HERE (Thanks MicroMod777) in the Rezound Development section.
2. Then downloaded the current firmware.zip from HERE (Thanks Flyhalf205) and then extracted the recovery.img along with the hboot .nb0 file from it.
3. I then created 2 separate custom ph98img.zip for each so I could always reinstall the stock hboot and the stock recovery.img.
4. I extracted the boot.img from the rooted rom and flashed that first. I don't remember if I did it via adb in fastboot usb or with another ph98img.zip and then
5. I made sure that my bootloader was unlocked and then installed AmonRa as the recovery
6. Then used AmonRa to flash the stock rooted zip file. I then wiped the cache 3 times and the dalkvik cache 3 times.
I let the phone reboot and I was back to a working phone.!!! Then I found out that it was rooted with SuperSu which gives you the option of doing a full permanent unroot which I did. I then put that ph98img that I had made that had the stock recovery.img on it and flashed that in the bootloader. After rebooting I now had a fully stock phone and proceeded to do the S-off. I left the bootloader unlocked as directed by the unlimited.io site. I had limited experience with ubunto but found THIS PAGE that helped walk me through it. I followed it exactly and ended up with an S-off phone. One thing that wasn't clear to me was how to open a terminal in ubunto but I figured that out after trial and error. IIRC, I clicked on the home tab on the left and then in the search box, typed terminal. The first icon that was shown was a terminal emulator and I used that for the commands.
Now I still wasn't finished. I ended up relocking the bootloader but didn't like the relocked and tampered flags that were showing. So I ended up running the most recent RUU (3.14.605.12 found HERE and I now had a ***LOCKED*** bootloader and then let the phone reboot. After it rebooted, I hit the home key and bypassed the setup. I then got into settings and then into software update and let it update. It did a small update and then had to repeat the reboot, bypass setup, and software update. This time it did the global update. I let it reboot but this time, I ran the setup. Once I was up and running, I again went into bootloader and reinstalled AmonRa and used the 3.16 version and made sure to do a nandroid before doing anything further. After that, I got ahold of SuperSu 1.51 and flashed that in the AmonRa recovery. I now had a ***LOCKED*** stock rooted Rezound and several nandroid backups of both fully stock and rooted. Which turned out to be a great idea because not even 3 weeks later after this, the phone started malfunctioning (power button) and a problem with the camera so it got replaced and I had to put it back fully stock. I was already setup for this. I unrooted, put the stock recovery back on, and made it S-on. When the replacement came, I immediately unlocked it, did the S-off (only took one try), relocked, ruu'd back to 3.14.605.12, updated to global rom, flashed AmonRa, and restored with my most recent rooted nandroid. and I am back up and running a whole lot sooner...
I hope this helps.
Click to expand...
Click to collapse
This guide was FREAKING AWESOME. It led me to finally after 2 years go S-Off (wire trick) to do RUU, etc. Have to return phone and have already got replacement. Crossed my fingers and everything looks stock stock stock !