First off let me start by saying this, I have looked at the other threads, I have been searching for the past 6 hours and the other threads about their Rezounds not booting are all different. Last night I unlocked my phone and flashed amon Ra, made a back up, wiped almost all of the data, and then flashed the ROM Nils' Business ICS 4.0.3 Sense 3.6. After doing so my phone rebooted, it made it past the white HTC screen but once it was at the black screen it does not do anything. I am able to get it into the bootloader, however I can not go into recovery after I hit recovery it loads for a little while and then it has a picture of a phone with a red triangle with an exclamation mark in it, I did not flash the RUU (i overlooked that part) and when i try to flash or do anything i am not able to because the way i learned how (from my computer) i am unable to do so because when i type "adb devices" it does not recognize any devices (even if i am in the bootloader with fastboot) i have tried taking the sd card out, doing a factory rest, and I am fairly certain all i have to do is flash a new kernel but i have no idea how to do that when i am not able to get into recovery or when my computer doesnt recognize it as a device, Let me know if I should leave any more information for you guys and any help you guys could offer would be much appreciated
Try this:
Pull the battery
Put the battery back in and hold power + volume down
This should boot you into HBOOT.
Plug into your PC
If you need to, relock (fastboot oem lock)
Run the RUU
Re-unlock
Re-install AmonRa
Re-ROM
If you want to go back to an old ROM.
Make sure you don't have a PH98IMG.zip on your SD,
Go into recovery
Flash your ROM/backup
Flash the kernel in HBOOT
Reboot
How can I run the RUU? Is there a way to get it on my phone now? After i connected it and typed in a command for the phone in the command line it said "waiting for device" and it stayed in that state for a long time, before, when i tried a command it kept saying "no device found" immediately , so there was a bit of improvement!
galloway2323 said:
How can I run the RUU? Is there a way to get it on my phone now? After i connected it and typed in a command for the phone in the command line it said "waiting for device" and it stayed in that state for a long time, before, when i tried a command it kept saying "no device found" immediately , so there was a bit of improvement!
Click to expand...
Click to collapse
Are you in HBOOT? Does the phone say "FASTBOOT USB" ? If so, are you using the fastboot commands vs adb commands?
I was not in fastboot now the fastboot commands work!(i only tried "fastboot reboot-bootloader" but im assuming the rest will work) but how would i install RUU from the command line? sorry i just started researching how to put ROMs on and Root my phone yesterday and decided to jump into it before fully knowing what i was doing...needless to say that caused an unnecessary problem
Ok, so have you removed your SD Card and put made sure you don't have a PH98IMG.zip on the root? That would be a possible reason you can't get into recovery. I would try that before anything else because you'd still have the same issue later. If you don't have another device to clear the SD card you might have to wipe the SD.
i do not have a PH98IMG file, I tried to reinstall the Amon ra, and i was able to get to recovery, I restored my phone with the backup i had!! So i am basically back to square 1 (well square 2, at least i am unlocked still) But i have NO service at all, normally i even have 4g where i am, will that be fixed if i install a new Rom? and a little off topic (sorry) but what Rom would you guys suggest?
Rezrom... lllboredlll is an android developing beast. Some of the "other" roms the systemui doesnt report battery % correctly
galloway2323 said:
i do not have a PH98IMG file, I tried to reinstall the Amon ra, and i was able to get to recovery, I restored my phone with the backup i had!! So i am basically back to square 1 (well square 2, at least i am unlocked still) But i have NO service at all, normally i even have 4g where i am, will that be fixed if i install a new Rom? and a little off topic (sorry) but what Rom would you guys suggest?
Click to expand...
Click to collapse
No service is probably either having the back cover off(antennas are located there) or by having the wrong kernel ver.
I would suggest Scott's or Nils or Team BAMF's ROM as they're very well tested and stable.
Alright thanks to everyone who replied and helped me out! I was thinking of BAMF so i will give that a try, Any idea why they would put the antennas in the back cover? that was the issue but i have never heard of the antennas being in the cover, that just sounds strange to me...?
I had the same thing happen to me, it wasnt till a day later i figured it out. I kept the battery out because i assumed i screwed up the flash. Finnally i was like screw it, threw it all together and went a buddies house where i looked at my phone and i had perfect signal
Sent from my INCREDIBLE, faster than a THUNDERBOLT, REZOUND!
galloway2323 said:
Alright thanks to everyone who replied and helped me out! I was thinking of BAMF so i will give that a try, Any idea why they would put the antennas in the back cover? that was the issue but i have never heard of the antennas being in the cover, that just sounds strange to me...?
Click to expand...
Click to collapse
The antenna connection are on the back plate so that the least amount of material is in between the signal and the antenna. It actually makes really good sense lol. And works well best signal I have ever had on a phone is my rezound I always have service even when my wife's tbolt dont.
Sent from my ADR6425LVW using XDA
Haha well when it is put that way, it makes a lot of sense to have it on the back cover, the more I think about it, I dont think i have lost service(accept for when the back cover is off) since I got the Rezound!
Related
I just acquired a Droid Eris from my buddy of mine, when you turn it on it just stays at the screen with the 3 androids on skateboard(if I turn it on with it plugged into usb It makes the connection noise though). I can Also get into hboot and recovery but no matter what I do it will not install anything, everything just fails. Also its say its S-ON. Any help would be great, thanks.
glitch666 said:
I just acquired a Droid Eris from my buddy of mine, when you turn it on it just stays at the screen with the 3 androids on skateboard(if I turn it on with it plugged into usb It makes the connection noise though). I can Also get into hboot and recovery but no matter what I do it will not install anything, everything just fails. Also its say its S-ON. Any help would be great, thanks.
Click to expand...
Click to collapse
Well, you didn't really say what "everything just fails" means. How about giving us an error message?
While you are at it, what version of recovery is on the phone - Amon_RA v1.6.2, or some version of Clockwork?.
Same deal for the bootloader - how about an exact version number - 1.49.0000, 1.47.0000, or other?
Because your phone is already "soft-bricked", and you got it for free, and because your recovery boots up, you can try flashing "ErisMTDNuke_v0.9.zip". You can find it at this post:
http://forum.xda-developers.com/showpost.php?p=11651122&postcount=21
It has an an assert() in it that tries to block it from running on ClockworkMod, but depending on what version of recovery you have, that may not matter. Let me know if you get any errors running it. If it runs, you should be back in business; it leaves the /system, /data, and "boot" partitions of the ROM blank, so you will need to flash a ROM afterwards. Also, if you have ClockworkMod recovery on the phone, you should consider getting it off of there, and putting one of the two Amon_RA recovery variants on there.
You might find the entire thread that contains the above post very useful, as it describes a method for installing the S-OFF bootloader using the "SoSickWiTiT" rooting method, as well as other tricks such as using fastboot to soft-load recoveries without writing them to flash; that full thread is here:
http://forum.xda-developers.com/showthread.php?p=11652502
Please provide full details on what works / doesn't work, particularly with "ErisMTDNuke_v0.9.zip" - it has only been used on 3 phones so far (worked on all three, though).
cheers
bftb0
I dont think the phones been rooted(my friend has no idea what that even is). It has hboot 1.49.0000, and the recovery is not a custom one, its Android recovery 2e. If I try to Install an update through recovery its says installation aborted. Also if I use pb00img.zip it loads in hboot but says previous version is older and to reboot.
glitch666 said:
I dont think the phones been rooted(my friend has no idea what that even is). It has hboot 1.49.0000, and the recovery is not a custom one, its Android recovery 2e. If I try to Install an update through recovery its says installation aborted. Also if I use pb00img.zip it loads in hboot but says previous version is older and to reboot.
Click to expand...
Click to collapse
OK, that is completely different. It is impossible to load a dev ROM using the stock recovery <2e>
Did you try the "wipe data/factory reset procedure" of the recovery menu, or have you already done that and then the phone hangs at the three droids?
bftb0
If the stock ( <2e> ) recovery factory reset does not work, then the method of last resort is going to be to try and get the S-OFF bootloader onto the phone using the "SoSickWiTiT" rooting method.
Generally what happens - if you have corrupted flash memory partitions - is that parts of this install will fail, but getting the engineering bootloader (1.49.2000 S-OFF) onto the phone will succeed - and from there you can leverage the behaviors of the S-OFF bootloader to get a custom recovery running (by using fastboot). Once that happens, you can run the ErisMTDNuke_v0.9.zip flash to erase the /system, /data, and "boot" partitions, so that a subsequent ROM flashing operation will succeed (probably, no guarantees).
The way the "SoSicWiTiT" rooting method works, you run the "Official 2.1 RUU" Utility on the PC - but just before it is ready to start writing to the phone (after it has unpacked all it's temporary files and installed drivers for you), you take the "Root PB00IMG.ZIP" file, rename it to "rom.zip", and replace the "rom.zip" file unpacked in the temporary file area of the RUU. This gets the S-OFF bootloader installed (at a minimum, possibly the whole rom if your problem is not flash memory page corruption).
The thread I mentioned above has more details; ask questions if you don't understand something.
bftb0
PS You should be doing all of these operations with a well charged battery - 100% is a good place to start. Don't let the phone sit in HBOOT or FASTBOOT mode for extended periods of time - the battery will discharge rapidly, even if the phone is plugged in to the charger.
Thank you for the quick and to the point replies, I will try this later tonight and will post and let you know if it works out. I have tried the factory reset and it doesn't work, but hey it was free if I screw it up Its no big issue lol. Im not new to rooting its just I have no experience with this particular phone, so thank you =].
glitch666 said:
Thank you for the quick and to the point replies, I will try this later tonight and will post and let you know if it works out. I have tried the factory reset and it doesn't work, but hey it was free if I screw it up Its no big issue lol. Im not new to rooting its just I have no experience with this particular phone, so thank you =].
Click to expand...
Click to collapse
OK. Good luck.
The Root PB00IMG.ZIP and the "Official 2.1 RUU" can be found here:
Consolidated HTC RUU, Leak, and OTA Downloads
Amon_RA's original (v1.6.2) recovery is located here
If you don't have a version of fastboot on your PC/workstation already, you can find different platform versions of it a short distance down the HTC's developer page for the ADP.
If you can get the S-OFF bootloader onto the phone, then you can flash Amon_RA's recovery from the PC with a single command:
Code:
fastboot flash recovery recovery-RA-eris-v1.6.2.img
If you don't already have USB drivers installed on your PC, the RUU utility should be able to do it for you automatically (although ymmv depending on your Xp/Vista/Win7/x32/x64 variety).
Let me know how things go.
bftb0
PS It is worth repeating - make sure your phone is well charged when you are doing any flashing.
Yeah I know fastboot like the back of my hand(g1 and other phones that I love dearly but no longer have), im giving this a shot right now, thank bud.
glitch666 said:
Yeah I know fastboot like the back of my hand(g1 and other phones that I love dearly but no longer have), im giving this a shot right now, thank bud.
Click to expand...
Click to collapse
Standing by.
No matter what the official 2.1 RUU gives me a bootloader mismatch error 140 with either the actual rom.zip or the root rom renamed to rom.zip and placed in the temp folder, let me try some more things. Edit RUU says Im going from 2.37.605.4 to 2.36.605.1. Ok so this leads me to believe it has the 4th OTA on it right?
PS -
I might have mentioned it in that other thread, but anyway: the RUU utility will get the phone to cooperate if the phone is put into fastboot mode (or RUU mode). Normally it is expected that the phone will be booted normally when you start up the RUU... but that (obviously) isn't an option for a soft-bricked phone.
cheers
glitch666 said:
No matter what the official 2.1 ruu gives me a bootloader mismatch error 140 with either the actual rom.zip or the root rom renamed to rom.zip and placed in the temp folder, let me try some more things.
Click to expand...
Click to collapse
Rats. Does that happen immediately after the RUU starts up, or only when you tell it to begin the flashing operation?
Here's another wild straw to grasp at.
If you plug the phone into your PC, and then cold-start it (normal boot), do you hear 2 USB sequences at about 5 and 9 seconds, respectively? If the kernel is alive, but looping on something.... and the prior user had USB debugging enabled, and it's a 2.1 ROM, we can probably still root it by hand across ADB.
does "adb devices" give you anything 15 or more seconds after boot-up, or does your (Windows) device manager indicate a "Composite Interface"?
bftb0
Edit RUU says Im going from 2.37.605.4 to 2.36.605.1. Ok so this leads me to believe it has the 4th OTA on it right?
Click to expand...
Click to collapse
Sure sounds that way. Normally that info (the "Main Version") is stored in the misc partition, and it rather surprises me that an OTA install would cause that to happen; but I can't argue with what you are seeing.
That might mean that neither RUU nor PB00IMG.ZIP installs will work without being able to modify the RUU program to ignore version checks.
How about the adb angle - does anything come up on the USB when the 3 skating droids are showing?
No it goes all the way to the flashing processes after the phone goes into bootloader mode. then stops and gives me the error, now with adb when I turn the phone on I hear one chime and then get a device not recognized and no output from adb. Did you see my last post on the other page I edited it about the bootloaders, its says its going from 2.37.605.4 to 2.36.605.1. Sorry you posted before me so ignore this last tid bit.
Long shot, but check your HBOOT screen again - is it still S-ON (1.49.0000) ?
BTW, when you say "bootloader mode" - do you mean FASTBOOT or RUU mode? (The RUU mode is just a graphic with the HTC logo in the middle of the screen, sometimes with small arrows in each of the 4 corners of the screen. FASTBOOT mode says either "FASTBOOT" or "FASTBOOT USB" right on the screen).
I would think that you are starting the process with the phone in FASTBOOT mode, right?
bftb0 said:
Sure sounds that way. Normally that info (the "Main Version") is stored in the misc partition, and it rather surprises me that an OTA install would cause that to happen; but I can't argue with what you are seeing.
That might mean that neither RUU nor PB00IMG.ZIP installs will work without being able to modify the RUU program to ignore version checks.
How about the adb angle - does anything come up on the USB when the 3 skating droids are showing?
Click to expand...
Click to collapse
I am not getting anything from adb.
bftb0 said:
Long shot, but check your HBOOT screen again - is it still S-ON (1.49.0000) ?
Click to expand...
Click to collapse
Yup it stayed the same.
bftb0 said:
Long shot, but check your HBOOT screen again - is it still S-ON (1.49.0000) ?
BTW, when you say "bootloader mode" - do you mean FASTBOOT or RUU mode? (The RUU mode is just a graphic with the HTC logo in the middle of the screen, sometimes with small arrows in each of the 4 corners of the screen. FASTBOOT mode says either "FASTBOOT" or "FASTBOOT USB" right on the screen).
Click to expand...
Click to collapse
First I put the phone into fastboot mode, then fire up RUU and it kicks the phone to a black screen with an htc logo in the middle and trys to flash it(the RUU says its putting the phone into bootloader mode so I guess thats what its in when it restarts to the htc logo).
Don't Quote me but I know the Eris is Almost like my Hero, and with the Hero there's a way to Get it into the Fastboot I Think by Holding Volume Up and Powering on the Phone! Then you Should be Able to Run the Latest RUU for the Eris... Hopefully that will get you back Right!!
Good Luck!
Sent from my Hero using XDA App
Hi Everybody,
I have seen the recent posts and guides regarding unrooting especially the guide from Twolazyg. Only problem is, I am already running the stock Sprint 651.3 rom. I always backed up my stock rom and would switch back to update it and I did just that this time to get 651.5 without the pesky CIQ software. I am aware of how to relock the bootloader as per htc instructions but then again I'm not sure of what to do. When I rooted I installed cwm 4.0.1.4 through the method at htcevohacks.com then TWRP came out and I flashed twrp 2.0.0RC0 over cwm. Never had a problem with TWRP so I know it isn't the recovery. I didn't get Flashimage GUI so I was always using fastboot to install roms. Also, I never used the android sdk (at least I think I didn't because its not on my computer) so not too sure when someone says use adb in the instructions. Oh yea, I'm also a noob so take it easy if you can lol.
Initially, I installed a custom rom after rooting and unlocking my bootloader via htc method. Then I wasn't too happy with the roms and just decided to stay rooted but keep my stock rom. I installed app quarantine to freeze some of the unused system apps like friendstream, peep, stocks, etc.. Before I did the update I brought all the apps out of quarantine incase anything screwy happened with app updates.
Fast forward to today, and now after 651.5 update my phone is literally restarting. It keeps booting up to my lock screen and it holds for 1 minute then it just restarts. It's sitting in front of me right now and as I type it has restarted at least 10 times as I have been watching it. It actually started acting up after I let out all the apps from app quarantine yesterday so 651.3 was already screwy with system apps unquarantined.
So I'm trying to unroot and relock so I can send this baby back to Sprint and get a replacement. Already did a master a reset three times and nothing works in terms of stopping the constant rebooting.
I'm just wondering where do I start with any of the steps. Should I just follow the guide exactly or do I have to take different steps???
Thanks
Hiya Buddy said:
Hi Everybody,
I have seen the recent posts and guides regarding unrooting especially the guide from Twolazyg. Only problem is, I am already running the stock Sprint 651.3 rom. I always backed up my stock rom and would switch back to update it and I did just that this time to get 651.5 without the pesky CIQ software. I am aware of how to relock the bootloader as per htc instructions but then again I'm not sure of what to do. When I rooted I installed cwm 4.0.1.4 through the method at htcevohacks.com then TWRP came out and I flashed twrp 2.0.0RC0 over cwm. Never had a problem with TWRP so I know it isn't the recovery. I didn't get Flashimage GUI so I was always using fastboot to install roms. Also, I never used the android sdk (at least I think I didn't because its not on my computer) so not too sure when someone says use adb in the instructions. Oh yea, I'm also a noob so take it easy if you can lol.
Initially, I installed a custom rom after rooting and unlocking my bootloader via htc method. Then I wasn't too happy with the roms and just decided to stay rooted but keep my stock rom. I installed app quarantine to freeze some of the unused system apps like friendstream, peep, stocks, etc.. Before I did the update I brought all the apps out of quarantine incase anything screwy happened with app updates.
Fast forward to today, and now after 651.5 update my phone is literally restarting. It keeps booting up to my lock screen and it holds for 1 minute then it just restarts. It's sitting in front of me right now and as I type it has restarted at least 10 times as I have been watching it. It actually started acting up after I let out all the apps from app quarantine yesterday so 651.3 was already screwy with system apps unquarantined.
So I'm trying to unroot and relock so I can send this baby back to Sprint and get a replacement. Already did a master a reset three times and nothing works in terms of stopping the constant rebooting.
I'm just wondering where do I start with any of the steps. Should I just follow the guide exactly or do I have to take different steps???
Thanks
Click to expand...
Click to collapse
Well first off, Flash Image GUI is a great program, so I want to provided my biased opinion as the author!
Off the top of my head, I am really temped to say your currently rebooting issue could very well be software related and not hardware related.
Moving around system applications, "freezing" and "unfreezing", I personally don't view as the most reliable method.
I view returning the device as the last ditch effort and giving up because everything else has failed and the issue is most likely hardware related.
If you're interested in troubleshooting the issue further, running the RUU, should return the system partition and the kernel back to a completely stock state at which point the rebooting should stop.
If the rebooting stops, then you'll know the issue was trigger by something software related and not hardware related.
Many of the RUU files for the EVO 3D are located at http://www.goo-inside.me/shooter/ruu . The directions/guides are posted all over the place on how to properly process an RUU but they are really fairly simple and bring the device back to 100% stock state.
Hope that helps and good luck!
Thanks for your input joey but weird thing is, when I have my evo 3d plugged in to my pc it does not continuously reboot. For the hour or so I've had it plugged in, it hasn't rebooted at all. It is completely usable. After unplugging it, the reboot cycle begins and it is unusable.
I wanted ask for some help because I never installed android sdk or did anything through adb at all. So if someone says "do it via ADB" I will have no clue as to what to do to fix my phone. I have installed sdk and platform tools to try and relock my bootloader but I'm not sure what to do. I mean, I went back to htc dev step 14, which is to relock I just have to type in fastboot oem lock but because I never did it via sdk method. So I guess I should follow the same method in my TWRP 2.0 folder then? Because I see a file called adb.exe
So, based on Twolazyg's instructions, would I have to put my phone in recovery via fastboot. Then type in the command prompt adb reboot bootloader. Then go to Hboot to flash the RUU and finally type in fastboot oem lock. Is this right???
I tried the instructions provided by Twolazyg but I can't get the first step to work...
So, I hold power + volume down and select fastboot.
Connect to pc with usb cable.
Open up cmd.exe and type in:
cd Desktop\Evo3DTwrp
Then follow instructions.
I type in adb reboot bootloader and then nothing happens.
I get this message on my computer:
* daemon not running. starting it now *
* daemon started sucessfully *
error: device not found
What am I doing wrong???
All I wanna do is unroot so I can return this phone for a new one...
Nevermind people, figured it out lol
Was about to Rage Quit but it works.
Got the RUU working and no longer have superuser and bootloader says relocked
Will now try the update to 651.5 then contemplate a return...
You da man joeykrim! My problem has been resolved
Hiya Buddy said:
Thanks for your input joey but weird thing is, when I have my evo 3d plugged in to my pc it does not continuously reboot. For the hour or so I've had it plugged in, it hasn't rebooted at all. It is completely usable. After unplugging it, the reboot cycle begins and it is unusable.
I wanted ask for some help because I never installed android sdk or did anything through adb at all. So if someone says "do it via ADB" I will have no clue as to what to do to fix my phone. I have installed sdk and platform tools to try and relock my bootloader but I'm not sure what to do. I mean, I went back to htc dev step 14, which is to relock I just have to type in fastboot oem lock but because I never did it via sdk method. So I guess I should follow the same method in my TWRP 2.0 folder then? Because I see a file called adb.exe
So, based on Twolazyg's instructions, would I have to put my phone in recovery via fastboot. Then type in the command prompt adb reboot bootloader. Then go to Hboot to flash the RUU and finally type in fastboot oem lock. Is this right???
Click to expand...
Click to collapse
regarding "adb", this binary is kept inside the android-sdk directory and under the subdirectory platform-tools.
many times ppl extract the adb.exe and the accompanying .dll file, package these two up into their "one click" tools and distribute.
personally, i prefer to grab the official android-sdk from google and their associate adb.exe instead of using copies distributed by other users.
hopefully that helps clarify some of the details around adb!
Hiya Buddy said:
You da man joeykrim! My problem has been resolved
Click to expand...
Click to collapse
always good to hear. another evo 3d saved!
glad it worked out. if any guides/posts were specifically helpful to you, feel free to post back your solution in case anybody else comes across this thread with the same issue.
never stops amazing me how many ppl end up with the exact same issue and these posts can be helpful!
glad to hear the issue was resolved!
@joeykrim
Everything works, but back to rooting for me until Sprint gets their **** together with 651.5 update. I took my phone in for service today after unrooting and relocking the bootloader. I was curious as to why my 3g speeds hover around 100kbps when they're usually at 800-1000kbps. According to the tech, who was running a custom rom on his Epic 4G Touch, he told me the update contained a prl that was screwy and it caused speed issues. I can confirm this with the other two evo 3ds on my account that have never been rooted/modded because they're just as slow with loading up web pages and working with apps. It was prl 21083 that is just not working out with data speed.
On Speed Test, I would put up a screen shot but I'm currently working on rooting lol, the latency would always be around 800ms and the fastest speed I got was 121kbps. There are no outages in my area because I called CS yesterday to set up my appointment and they said the towers are working normally. So it seems the 651.5 update is adds a snappyness to the UI but instead of speeding up the internet, it makes for a rather unpleasant internet experience and makes one question their "truly unlimited data and premium data fee."
So I'm gonna put TWRP back on my phone and pick a new rom based on 651.3 because of the screwed up prl unless I can keep my 651.5 and change the prl.
@Hiya buddy
I have a Sprint evo 3d flashed to reliance (carrier in india). I was on a sense 3.5 rom. I heard about this update and i restored my nandroid of stock ROM. Then i relocked it and flashed RUU (2.08.651.3). And accepted the OTA. Everything is working fine for me. No PRL's / Settings changed. My phone still works on reliance........
I did the same thing, restoring my nandroid backup of OTA 651.3 and did the update. After update 3g speeds are atrocious on Sprint, as for the software the phone is a bit snappier and more fluid than before.
hboot 1.5 s-off. Is this a true s-off or whats the deal
This past weekend I rooted my 3D evo and my girlfriends 3D evo. I had a bunch of problems during the process with mine. receiving 4g on the blackened rom, had to go into the msl settings a couple times, ect.... then when all was said and done, at the boot menu it said s-off.
On the other hand, when i rooted my girlfriends evo 3D, I had no issues at all went through really easily then at the end her's said s-on! I was baffled, I had used the same process, and both of our phones have hboot 1.5?
Does this mean I can install roms from recovery? I have a the full (I think it's revolutionary) recovery on it. Options to install from zip and all.
However I did try and install a custom kernal from kernal manager and had to reinstall the blackened rom (Which is awsome btw) because I couldn't get 4G or wifi. (RCMIX Kernal). When i tried to flash a new kernal over the rcmix, it went through the process rebooted...then nothing still had the RCMIX kernal? So I reinstalled blackened. Totally fine, everything working 100%.
Any explainations, I haven't been able to find anyone with 1.5 hboot s-off doing a google search, only people who say it's coming soon. I also figured this would be the best place to post this considering there is no hboot 1.5 general section. if there is please move this there.
Thanks in advance
sag04463 said:
This past weekend I rooted my 3D evo and my girlfriends 3D evo. I had a bunch of problems during the process with mine. receiving 4g on the blackened rom, had to go into the msl settings a couple times, ect.... then when all was said and done, at the boot menu it said s-off.
On the other hand, when i rooted my girlfriends evo 3D, I had no issues at all went through really easily then at the end her's said s-on! I was baffled, I had used the same process, and both of our phones have hboot 1.5?
Does this mean I can install roms from recovery? I have a the full (I think it's revolutionary) recovery on it. Options to install from zip and all.
However I did try and install a custom kernal from kernal manager and had to reinstall the blackened rom (Which is awsome btw) because I couldn't get 4G or wifi. (RCMIX Kernal). When i tried to flash a new kernal over the rcmix, it went through the process rebooted...then nothing still had the RCMIX kernal? So I reinstalled blackened. Totally fine, everything working 100%.
Any explainations, I haven't been able to find anyone with 1.5 hboot s-off doing a google search, only people who say it's coming soon. I also figured this would be the best place to post this considering there is no hboot 1.5 general section. if there is please move this there.
Thanks in advance
Click to expand...
Click to collapse
Hboot 1.5 s-off is not possible at the moment. Probably wouldn't be worth it to the devs at this point in time with ICS around the corner. That OTA update will most likely change the bootloader.
sent from America....F__k yeah!
@sag04463 Jabawockee is right, that doesn't seem possible. And your issue is a common problem with Hboot 1.5. You gotta get the Flashimage GUI from joeykrim or you could do it via fastboot and remember a few simple commands. That 4G/Wifi issue seems to only be problematic with Hboot 1.5 because HTC didn't fully unlock the bootloader or something (Experts, take it easy on me I'm not sure about this) and it doesn't allow for the installation of custom kernels.
So I decided I needed to update my phone. I installed the new firmware and everything went perfect. I decided on this rom (I am S-ON). After installing the rom I ran the other zip for S-On users. It then told me my Main Version was too old. I remember doing a fix for this months ago and saying I won't have this issue again. Now I am sitting at a white HTC screen thinking my phone is completely done for. With the firmware leak and all that all my backups seem to have been deleted. Any suggestions?... I am in dire need.
-Still sitting staring at this white htc screen. I literally am out of ideas. I did everything perfect and this happened, I'm so sad. I specifically remember doing something regarding MainVer's awhile back so I would never have this problem and now I am here with a broken phone. This blows ... Suggestions?!
SHIDOOBY said:
So I decided I needed to update my phone. I installed the new firmware and everything went perfect. I decided on this rom (I am S-ON). After installing the rom I ran the other zip for S-On users. It then told me my Main Version was too old. I remember doing a fix for this months ago and saying I won't have this issue again. Now I am sitting at a white HTC screen thinking my phone is completely done for. With the firmware leak and all that all my backups seem to have been deleted. Any suggestions?... I am in dire need.
-Still sitting staring at this white htc screen. I literally am out of ideas. I did everything perfect and this happened, I'm so sad. I specifically remember doing something regarding MainVer's awhile back so I would never have this problem and now I am here with a broken phone. This blows ... Suggestions?!
Click to expand...
Click to collapse
If you are s-on, it is nearly impossible to be "done for". Probably user error (no offense) but you probably had a file named incorrectly or it didn't flash properly. I just got to work and can't really help you right now, but i know someone can. Just don't worry, you'll be fine. Like i said, it's far from "done for".
tCizler said:
So I decided I needed to update my phone. I installed the new firmware and everything went perfect. I decided on this rom (I am S-ON). After installing the rom I ran the other zip for S-On users. It then told me my Main Version was too old. I remember doing a fix for this months ago and saying I won't have this issue again. Now I am sitting at a white HTC screen thinking my phone is completely done for. With the firmware leak and all that all my backups seem to have been deleted. Any suggestions?... I am in dire need.
Click to expand...
Click to collapse
Easy fix.
If you don't have the ROM on your computer anymore, download it again. Extract it and copy the boot.img to your ADB directory (if you don't have ADB, you need to get it lol.) Plug your phone into your computer, then just boot your phone into your bootloader, go into recovery, wipe everything 3X to be safe. Install the ROM, reboot into bootloader (make sure you're in fastboot USB mode.) Open up command prompt, CD to your ADB directory and type in fastboot flash boot boot.img. Reboot, and enjoy. If you have any issues, let me know.
In addition to Chyrux's useful post, I'd recommend keeping backups of your phone's storage on PC and possibly cloud storage.
If you got the time, or a spare SD card to get phone running in the meantime, might want to try a recovery program to get those nandroid backups and files off the SD card. I'd suggest Piriform Recuva for Windows, use the Deep Scan option.
I used to have ADB but don't anymore and downloaded the "noob proof" thing that allows you to do everything. Although you can't really use it without your phone turning on. When I press the volume down button it tries to install a kernel and said "Main Version Old" and makes me press the power button to reboot. I do have Amon Ra installed. I haven't really messed with the whole phone thing in awhile and have tried to educate myself by reading and reading and am a bit of a perfectionist. I don't know where I went wrong.
-I do know that I am on the new firmware w/ ICS
-I do know that Amon Ra is installed.
-I don't have a backup because everything seems to have been deleted.
-I suppose something went wrong during the installation process with RezRom S4 2.5
-I currently have no idea what I am doing. I am not stupid, nor do I expect handouts. I am fully capable of reading threads and usually fixing all my problems on my own. But, without a backup and me not being completely familiar with adb and my phone stuck on a white htc screen it makes me a bit timid to do anything else without some direction.
SHIDOOBY said:
I used to have ADB but don't anymore and downloaded the "noob proof" thing that allows you to do everything. Although you can't really use it without your phone turning on. When I press the volume down button it tries to install a kernel and said "Main Version Old" and makes me press the power button to reboot. I do have Amon Ra installed. I haven't really messed with the whole phone thing in awhile and have tried to educate myself by reading and reading and am a bit of a perfectionist. I don't know where I went wrong.
-I do know that I am on the new firmware w/ ICS
-I do know that Amon Ra is installed.
-I don't have a backup because everything seems to have been deleted.
-I suppose something went wrong during the installation process with RezRom S4 2.5
-I currently have no idea what I am doing. I am not stupid, nor do I expect handouts. I am fully capable of reading threads and usually fixing all my problems on my own. But, without a backup and me not being completely familiar with adb and my phone stuck on a white htc screen it makes me a bit timid to do anything else without some direction.
Click to expand...
Click to collapse
Lol I feel your pain. I don't have an SD card reader, so situations like this usually blew. But, there's a bright side: you have an internal storage unit. Let's try something basic. Take out your SD card and plug your phone into your computer. Reboot into your recovery and mount your USB storage. Tell me if you can see your internal and can access it.
So this is where I get stuck at; I appreciate that idea and will try it shortly (at work at the moment). I basically have no access with my computer and phone via usb because i am unable to get past hboot.
2 things happen as of right now:
-I press the power button and it sits at the HTC white screen forever
-I hold volume down and the power button and it tries to flash a kernel and says my Main Version is old. (When in fact, I know I did the MainVer fix while back; frustrating)
So with those 2 things only happening, is your suggestion still to yank out the external? I wish I had a microSD reader to wipe it and put a new rom on there and then figure out how to access amon ra and get passed this mess.
I took 2 min off work to yank the card out(the external, that is) -- I was able to reach recovery. I went into the mounting section of Amon Ra where I was able to see /sd-ext and /sdcard, both of which I got the message. "E: Can't mount /dev/block/mmcblk1p1) (No such file or directory)
Chyrux said:
Lol I feel your pain. I don't have an SD card reader, so situations like this usually blew. But, there's a bright side: you have an internal storage unit. Let's try something basic. Take out your SD card and plug your phone into your computer. Reboot into your recovery and mount your USB storage. Tell me if you can see your internal and can access it.
Click to expand...
Click to collapse
And for that matter, I have gotten in the habit of lifting my battery out at an angle, pressed into the contacts still to remove and insert my SD card on the fly for when I get these lingering PH98IMG.zip files. Pop out, go to recovery with a ninja grip on phone, and pop SD in lol.
I know Amon Ra Revamped 3.15 recovery has an option to delete those zips.
http://forum.xda-developers.com/showthread.php?p=23169557
Need to try reflashing that zip again in recovery perhaps, maybe RUU undid your Misc partition Mainver fix.
In any case... What your white bootloader screen says would help troubleshoot.
(Sorry for constant edits)
When you flash a new kernel the mainver is changed to what that kernel's is. I'd it's a newer number then when you try to flash something with a older number it won't flash. So every time you flash a kernel it is a good idea to go ahead and redo the main version fix
Sent from my ADR6425LVW using Tapatalk 2
*** TAMPERED ***
*** UNLOCKED ***
VIGOR PVT SHIP S-ON RL
HBOOT 2.21. 0000
RADIO-1.2.22.10. 0310r/1.22.10.0308r
OpenDSP-v13.6.0.7611.00.0104
eMMC-Boot
Mar 11 2012,22:16:16
HBOOT
<VOL UP> to previous menu
<VOL DOWN> to next item
<POWER> to select item
FASTBOOT
RECOVERY
FACTORY RESET
CLEAR STORAGE
SIMLOCK
IMAGE CRC
- How would I flash the Mainver fix when I can't even communicate with my computer through usb?
- Would adb help(I haven't used in a LONG time)
- I'm sitting at the screen I just took about 20 min to type out up above.
The white screen text I showed you was without the external sd card in. I feel like the only solution right now is to buy another external SD card.. put a rom on it, and then flash it... maybe that's the solution since I can't access this SD card and it seems to be ****ed with a mainver problem? Although, even with a new SD card I don't know how I would flash the mainver fix?
SHIDOOBY said:
*** TAMPERED ***
*** UNLOCKED ***
VIGOR PVT SHIP S-ON RL
HBOOT 2.21. 0000
RADIO-1.2.22.10. 0310r/1.22.10.0308r
OpenDSP-v13.6.0.7611.00.0104
eMMC-Boot
Mar 11 2012,22:16:16
HBOOT
<VOL UP> to previous menu
<VOL DOWN> to next item
<POWER> to select item
FASTBOOT
RECOVERY
FACTORY RESET
CLEAR STORAGE
SIMLOCK
IMAGE CRC
- How would I flash the Mainver fix when I can't even communicate with my computer through usb?
- Would adb help(I haven't used in a LONG time)
- I'm sitting at the screen I just took about 20 min to type out up above.
Click to expand...
Click to collapse
Okay, you are following the guide of the RezROM to a tee I take it. Have to ask which AmonRa version did you install? I got the same mounting errors once and had to re-flash the recovery to AmonRa 3.14 to detect the mount points properly.
And yes, should be able to use fastboot commands with ADB to push the recovery, the Mainver fix, etc. That is the key communication tool you have barring any other access in your situation.
I'm am not anywhere remotely close to a PC and a bit rusty too, will try and find the ADB commands for that.
PhantasmRezound said:
Okay, you are following the guide of the RezROM to a tee I take it. Have to ask which AmonRa version did you install? I got the same mounting errors once and had to re-flash the recovery to AmonRa 3.14 to detect the mount points properly.
And yes, should be able to use fastboot commands with ADB to push the recovery, the Mainver fix, etc. That is the key communication tool you have barring any other access in your situation.
I'm am not anywhere remotely close to a PC and a bit rusty too, will try and find the ADB commands for that.
Click to expand...
Click to collapse
Those lines I typed were without the SD card in the actual phone. I did install the newer version of AmonRa (3.15 for ICS and GB) In the actual recovery with the External SDcard out I did some scoping around where you're able to delete the kernel install, but that would leave me still with a broken phone. I need to be able to access my SD card and put a new rom on it i'm guessing? I don't even know what the **** I'm doing anymore.
wow.
put THIS file on your sd card. then do the update in HBOOT. once your are back up and running flash the main version fix. then get s-off
*EDIT* just saw where you can go into recovery. Okay. Here comes the fun part. I'm not well-versed in the mainver issue and this method can brick your phone, so be careful. Just what I have for now.
Start by having your SD card out (but on your desk, just make sure you have it lol.) Boot up your phone into the bootloader and go to where you can access your recovery, but don't. Here's where you can brick your phone. Pop out your battery and leave the cable plugged in (you'll have power still going to your phone.) Now, put your SD card back in and put your battery back in as well. Boot into your recovery and mount USB storage. From there, delete the update file using My Computer.
SHIDOOBY said:
So I decided I needed to update my phone. I installed the new firmware and everything went perfect. I decided on this rom (I am S-ON). After installing the rom I ran the other zip for S-On users. It then told me my Main Version was too old. I remember doing a fix for this months ago and saying I won't have this issue again. Now I am sitting at a white HTC screen thinking my phone is completely done for. With the firmware leak and all that all my backups seem to have been deleted. Any suggestions?... I am in dire need.
-Still sitting staring at this white htc screen. I literally am out of ideas. I did everything perfect and this happened, I'm so sad. I specifically remember doing something regarding MainVer's awhile back so I would never have this problem and now I am here with a broken phone. This blows ... Suggestions?!
Click to expand...
Click to collapse
Delete the PH98IMG.zip off your sdcard, download and flash THIS and then try flashing the rom and kernel again. should work. Worked for me.
try this link: http://forum.xda-developers.com/show...57&postcount=4
tmettler5 said:
Delete the PH98IMG.zip off your sdcard, download and flash THIS and then try flashing the rom and kernel again. should work. Worked for me.
try this link: http://forum.xda-developers.com/show...57&postcount=4
Click to expand...
Click to collapse
I think his issue is that he can't access his SD card because he doesn't have a reader/other device to use.
Ah... That makes sense. Maybe another sdcard, then? I'll put the set mainver low file in the dropbox later today and send a link. If you can use a second sd card and put it on that he can fix it. I think.
Sent from my ADR6425LVW using XDA
tmettler5 said:
Ah... That makes sense. Maybe another sdcard, then? I'll put the set mainver low file in the dropbox later today and send a link. If you can use a second sd card and put it on that he can fix it. I think.
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
Nah, he won't have to. Granted, my method is a bit...unsafe lol, but it worked fine for me. he just has to be careful and he'll be able to take the file off. Glad you have the fix cause I don't, though. So hopefully my trick will work and then he can use the fix.
If you get to the point where you can get into recovery, flash this: http://dl.dropbox.com/u/79523435/SetMainVersionLOW.zip
Then flash your rom and kernel as per normal.
I cannot get into regular bootloader. It just either sits and stalls, goes to HTC screen, or just straight to recovery. This has happened on and off before but I was always able to get it after a few tries. I've been trying for 2 days since the new ICS was released by Sprint but it's been no go.
I believe I have 1.5 Hboot, but I can't tell for sure because I can't access it. I had to take the long route when I had to root with the HTC unlock thing, etc.
I've tried to get to HBoot using QuickBoot app and using the menu option within TWRP 1.1 and now 2.2 (thought that might be the problem, but guess not)...still just stalls and nothing happens after reset
I've been using only rooted OTA's on my phone and only rooted for bloatware removal and wifi tether. No custom roms. No ICS leak.
The buttons of course work. As soon as I take my finger off of the Down volume button, the phone will activate and boot up normal in some cases.
I don't know if this is causing other issues with my phone as it self reboots or freezes a few times a week. I was looking forward to ICS update because I was hoping it would fix the reboots and freezing. Everything else works fine with the phone.
Any help would be greatly appreciated.
try "adb reboot bootloader" and see if your phone gets into bootloader.
mnomaanw said:
try "adb reboot bootloader" and see if your phone gets into bootloader.
Click to expand...
Click to collapse
Don't you have to be in Bootloader to get the adb commands to work? I tried using fastboot to connect and no go.
brokenmouse said:
Don't you have to be in Bootloader to get the adb commands to work? I tried using fastboot to connect and no go.
Click to expand...
Click to collapse
Look under settings/battery or power saver and uncheck fastboot?
Then you can actually get into hboot.
AFAIK, adb commands work in android, fastboot commands work in bootloader.
just make sure USB DEBUGGING is checked in settings.
When that happens to me, I remove the battery for about a minute, put it back in, hold down volume down, then hold power. It will boot right to bootloader.
Save the Drama for your Mama with Tapatalk 2
coal686 said:
When that happens to me, I remove the battery for about a minute, put it back in, hold down volume down, then hold power. It will boot right to bootloader.
Click to expand...
Click to collapse
This caused a lot of trouble for me trying to flash MeanRom and Tribulattifather's ICS OTA with 4EXT because it kept trying to go into bootloader after the install to do the "smart install" or whatever. The phone would just black out upon reboot and sit there or if I tried doing bootloader manually, it would go straight to recovery again. I was up until 4 in the morning trying to get my phone to fully boot last night...never did.
Brought my phone to work today and left it off nearly all day. I thought I was seriously screwed and would have to do a RUU update/unbrick from work. Lo and behold it went into bootloader first try.
I'm restoring a backup now through TWRP 2.2 (because it doesn't have the smart install feature). We'll see if
What do you think is causing these problems? I don't want anything crazy...just a solid ICS rom or rooted OTA. Most ROMs I read suggest using 4EXT to flash, but I'm afraid of running into this again. Any suggestions or thoughts?
as mentioned above, installed the TWRP 2.2 from bootloader and restored a backup (that worked a long time ago). Now i'm having the same issue I had last night. It won't boot up at all except to recovery again.
For most people, being s-off is the best thing to do. S-on and ICS tend to bootloop. For some reason, 4ext and flash image GUI don't seem to work well in ICS either for some.
Have you tried flashing a GB ROM?
Save the Drama for your Mama with Tapatalk 2
I'm going to have to figure out how to get back to complete stock. Everytime I flash a rom...doesn't matter what it is, the phone will say the flash is done, then reboot to...NOTHING...just a black screen. I've let it sit and nothing happens.
Followed a guide on androidcentral that had a nice restore to stock guide. Did the RUU from my computer and now it's acting normal again. It must've been really messed up because when I had it talking to ADB and did the reboot reloader command (as someone stated), the screen was solid black, though the RUU still saw it.
Hello all, I need some help if there are any ideas what could be going on with this phone. I can usually fix my own phone problems, but this one has stumped me...
I bought a rezound dirt cheap that was stuck on the white HTC screen and would not boot into the stock rom. At the time I bought it, it was s-on and I could get in the HBOOT and run fastboot commands.
Since buying it, I have tried many things to get this thing working. I've tried to RUU (with PH98IMG and .exe) and apparently after it completes it is once again in a boot loop on the white HTC screen. I have been able to unlock and flash a custom recovery onto it (amon-ra) and install any cm/aokp rom onto it and boot into that. The only issue with that is when in the rom, my wifi and bluetooth will not connect at all. It wont even toggle on in settings and it is not greyed out. 4G and everything else seems to work ok.
At this time, I'm thinking there is some kind of hardware failure but I'm open to suggestions.
In summary...
I have been able to s-off
I have tried different firmware combos of HBOOTs/radios
I have flashed custom recoveries and roms and can boot into them without wifi or bluetooth
I have been unsuccessful to RUU to anything stock, it'll just boot loop the white HTC screen
Right now, I have installed Tron 2.1 onto it. I did notice post:http://forum.xda-developers.com/showthread.php?t=2272781&highlight=no+wifi
When I go into system/lib, there was no /modules folder. I went ahead and created it and put in bcmdhd.ko and rebooted, but still no go. I'm not sure why the /modules folder was missing, but this reaches the extent of my knowledge on what is supposed to be there.
I believe I have tried everything and done fairly thorough searches to get this phone working properly and am at a loss what to do next. If anybody has a thought of something to try, I'm all for it. Fortunately if this phone doesnt work out, its not a big deal to me.
I don't want this to sound like another "stuck on HTC screen" thread. I have been through all those and this doesn't seem like the same problem.
Your help is greatly appreciated!
tacoman said:
Hello all, I need some help if there are any ideas what could be going on with this phone. I can usually fix my own phone problems, but this one has stumped me...
I bought a rezound dirt cheap that was stuck on the white HTC screen and would not boot into the stock rom. At the time I bought it, it was s-on and I could get in the HBOOT and run fastboot commands.
Since buying it, I have tried many things to get this thing working. I've tried to RUU (with PH98IMG and .exe) and apparently after it completes it is once again in a boot loop on the white HTC screen. I have been able to unlock and flash a custom recovery onto it (amon-ra) and install any cm/aokp rom onto it and boot into that. The only issue with that is when in the rom, my wifi and bluetooth will not connect at all. It wont even toggle on in settings and it is not greyed out. 4G and everything else seems to work ok.
At this time, I'm thinking there is some kind of hardware failure but I'm open to suggestions.
In summary...
I have been able to s-off
I have tried different firmware combos of HBOOTs/radios
I have flashed custom recoveries and roms and can boot into them without wifi or bluetooth
I have been unsuccessful to RUU to anything stock, it'll just boot loop the white HTC screen
Right now, I have installed Tron 2.1 onto it. I did notice post:http://forum.xda-developers.com/showthread.php?t=2272781&highlight=no+wifi
When I go into system/lib, there was no /modules folder. I went ahead and created it and put in bcmdhd.ko and rebooted, but still no go. I'm not sure why the /modules folder was missing, but this reaches the extent of my knowledge on what is supposed to be there.
I believe I have tried everything and done fairly thorough searches to get this phone working properly and am at a loss what to do next. If anybody has a thought of something to try, I'm all for it. Fortunately if this phone doesnt work out, its not a big deal to me.
I don't want this to sound like another "stuck on HTC screen" thread. I have been through all those and this doesn't seem like the same problem.
Your help is greatly appreciated!
Click to expand...
Click to collapse
i would like you to do the following.
flash this http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
2 times. it will make sure we have a solid base to work on.
after that has ran 2 times. boot into the stock rom one time.
after that flash this https://dl.dropboxusercontent.com/u/12405441/new.global.firm.PH98IMG.zip
once this is done let it boot into the rom.
from here you should be good to flash any rom that is out there to date. (note please dont restore any system data, only app data)
ALSO MAKE SURE YOU HAVE 100% battery. doing an ruu can brick the phone if its interrupted.
report back when done
Thanks for replying. I have flashed that RUU several times in a row in the past, but I'm redownloading it now to make sure my copy isnt corrupt. Earlier experience when I double flashed this it still remained a white HTC screen loop.
Currently estimated at 6hrs to download, so I wont be able to reply for a bit with my findings...
tacoman said:
Thanks for replying. I have flashed that RUU several times in a row in the past, but I'm redownloading it now to make sure my copy isnt corrupt. Earlier experience when I double flashed this it still remained a white HTC screen loop.
Currently estimated at 6hrs to download, so I wont be able to reply for a bit with my findings...
Click to expand...
Click to collapse
When the Rezound first came out a bunch of people had boot loop problems because the phone was set to wcdma or some such thing instead of cdma. I'm just a noob hack but that's my memory of it. The cure was to boot without the back cover on which contains the antenna and then change the setting.
Ok, I have re downloaded the AndroidPolice RUU and flashed twice, but was not able to boot into it no matter how long I waited (20 min+). It would just loop the HTC white screen. I then went ahead and flashed your global update firmware and have the same result after waiting (20 min+), it just loops the HTC white screen.
I have tried this process several times last night, but still no progress.
As the phone sits now:
*** UNLOCKED ***
VIGOR PVT SHIP S-OFF RL
HBOOT-2.28.0000
RADIO-2.23.10.0123r/2.23.10.0124r
OpenDSP-v14.6.0.7708.00.0507
eMMC-boot
Sep 20 2012, 17:40:22
tacoman said:
Ok, I have re downloaded the AndroidPolice RUU and flashed twice, but was not able to boot into it no matter how long I waited (20 min+). It would just loop the HTC white screen. I then went ahead and flashed your global update firmware and have the same result after waiting (20 min+), it just loops the HTC white screen.
I have tried this process several times last night, but still no progress.
As the phone sits now:
*** UNLOCKED ***
VIGOR PVT SHIP S-OFF RL
HBOOT-2.28.0000
RADIO-2.23.10.0123r/2.23.10.0124r
OpenDSP-v14.6.0.7708.00.0507
eMMC-boot
Sep 20 2012, 17:40:22
Click to expand...
Click to collapse
You need stock recovery and a locked bootloader
- "Is it dark in there?"
drynyks said:
You need stock recovery and a locked bootloader
- "Is it dark in there?"
Click to expand...
Click to collapse
S/he ran the RUU so they are stock.
Sounds like the symptoms of a kernel issue. Try pulling the boot.img from this stock OTA ROM and flashing it.
http://forum.xda-developers.com/showthread.php?t=2260154
fastboot flash boot boot.img
I have the exact same you. Been this way for months. Maybe once a month BT/Wifi will turn on but only for a few hours maybe. Phone will reboot itself and come back up with the 2 broken again.
feralicious said:
S/he ran the RUU so they are stock.
Sounds like the symptoms of a kernel issue. Try pulling the boot.img from this stock OTA ROM and flashing it.
http://forum.xda-developers.com/showthread.php?t=2260154
fastboot flash boot boot.img
Click to expand...
Click to collapse
Well I finally booted into stock sense after flashing that boot.img which is a big step from before. For a brief moment, it saw wifi networks in my office but when I went to connect to one, wifi died and it no longer sees any wifi network. Bluetooth appears to still be an issue as well, i.e. will not turn on.
Flyhalf205 said:
I have the exact same you. Been this way for months. Maybe once a month BT/Wifi will turn on but only for a few hours maybe. Phone will reboot itself and come back up with the 2 broken again.
Click to expand...
Click to collapse
Unfortunatly that doesnt sound very good for me if you've been battling this wifi/BT problem for months.
synisterwolf said:
i would like you to do the following.
flash this http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
2 times. it will make sure we have a solid base to work on.
after that has ran 2 times. boot into the stock rom one time.
after that flash this https://dl.dropboxusercontent.com/u/12405441/new.global.firm.PH98IMG.zip
once this is done let it boot into the rom.
from here you should be good to flash any rom that is out there to date. (note please dont restore any system data, only app data)
ALSO MAKE SURE YOU HAVE 100% battery. doing an ruu can brick the phone if its interrupted.
report back when done
Click to expand...
Click to collapse
can you explain what you mean by flash the ruu twice once I have saved it to the root of my sd card? Does that just mean get to the bootloader, watch as it reads the the ph98img file and let it do that twice, or do I need to reboot in between, or do I need to put in a command?
fivedezs said:
can you explain what you mean by flash the ruu twice once I have saved it to the root of my sd card? Does that just mean get to the bootloader, watch as it reads the the ph98img file and let it do that twice, or do I need to reboot in between, or do I need to put in a command?
Click to expand...
Click to collapse
when you let hboot flash the zip, the first time is super short. it updates hboot, stock recovery, and splash i think. then it will reboot back to bootloader and ask to be flashed again. this time it will take some time to update because it does the whole system.
---------- Post added at 08:25 AM ---------- Previous post was at 08:24 AM ----------
tacoman said:
Well I finally booted into stock sense after flashing that boot.img which is a big step from before. For a brief moment, it saw wifi networks in my office but when I went to connect to one, wifi died and it no longer sees any wifi network. Bluetooth appears to still be an issue as well, i.e. will not turn on.
Click to expand...
Click to collapse
something doesnt seem right. the RUU would have flashed the boot.img for you. can you link me to the downloaded ruu that you have? also before you run the ruu did you do fastboot oem lock the bootloader?
Edit:
i remember an old trick from the inc days. after the RUU boot back into hboot and do a "factory reset" then boot into the phone. it use to fix the radio errors somewhere getting after a RUU. no clue why we did it. it just worked. try that when you are on stock recovery locked bootloader
Here is the RUU I have re downloaded. It was also the original I used in the past on my other Rezound
https://www.dropbox.com/s/1570h8l0ba1u7qp/rezound_AndroidPolice_4.03.605.2_PH98IMG.zip
I have also tried the RUU 3.14.605.12.exe and a couple other different RUU versions, but have the same issue with that as well. Even on MicroMod777's OTA-Global-Stock-4.05.605.14 710RD-Rooted 5/1/13 flashed through amon-ra, I get the bootloop. I have done these as locked and unlocked bootloader with no difference. I have also tried the factory reset with locked bootloader.... no go with that either.
I was only able to finally boot in to stock by fastboot flashing the boot.img, and that is where this phone sits now. My major issue at this point is I dont have wifi or bluetooth and have dug through numerous posts and tried different things, and nothing is working on it. What was strange as I said in my previous post, the very first time I was able to boot into stock sense by flashing the boot.img, it briefly saw wifi networks but disappeared and disabled as soon as I tried to connect to one. I have not been able to replicate that since then.
On a sidenote and possibly related, since this phone has been sitting at my desk I decided to try and flash Newt's NOS JB v1.0.0 ROM and it bootloops also at the droid eye screen. I never was able to get it going on this phone. My other rezound boots this just fine.
I think I have reached the limits of my android knowledge of what to try on this thing. I am satisfied with it not having wifi/bluetooth since my wife wont be using those features. I would like to understand what the heck is going on though.