Related
I am s-off with jboot running rezrom 3.4. For some reason for the last two or 3 weeks i have lost amon ra 4 or 5 times. It just randomly disappears and i have to reflash it. Any idea on why this keeps happening?
hardfallen87 said:
I am s-off with jboot running rezrom 3.4. For some reason for the last two or 3 weeks i have lost amon ra 4 or 5 times. It just randomly disappears and i have to reflash it. Any idea on why this keeps happening?
Click to expand...
Click to collapse
This is nearly impossible, what ar you flashing?
I've heard this on moto phones but they would force instal the stock recovery on boot so you had to remove that script
As far as I know HTC phones don't do this
Sent from my ADR6425LVW using Tapatalk 2
its happend with both 3.14 and 3.15. ive never had a problem until a few weeks ago then all of a sudden mysteriously it disappears. i cant figure out whats going on.
I read that happening a couple times but never saw a solution. I decided not to flash jboot and stick with reg hboot
Sent from my ADR6425LVW using Tapatalk 2
Evocm7 said:
I read that happening a couple times but never saw a solution. I decided not to flash jboot and stick with reg hboot
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
The first time I lost it I was not using jboot. I tried to reflash recovery but it would fail everytime so i flashed jboot and it worked, but I still keep randomly losing recovery
Later tonight I'm going to give a shot in making a script the installs a recovery on boot
Sent from my ADR6425LVW using Tapatalk 2
Did you happen to leave an RUU on the SD card? Would only be a problem every time you boot into hboot, but still...
socal87 said:
Did you happen to leave an RUU on the SD card? Would only be a problem every time you boot into hboot, but still...
Click to expand...
Click to collapse
Nope. the very first thing i do after flashing anything is delete the file immediately when i boot back up.
What do you mean "lose" recovery? You can't boot to recovery, as in it just hangs at the splashscreen, or you boot to HTC recovery?
tekhna said:
What do you mean "lose" recovery? You can't boot to recovery, as in it just hangs at the splashscreen, or you boot to HTC recovery?
Click to expand...
Click to collapse
Whether i hit reboot to recovery or manually try to boot to recovery with a battery pull and volume down and power the phone will just boot up normally without ever going to recovery. I then have to reflash amon via fastboot and it works again.
hardfallen87 said:
Whether i hit reboot to recovery or manually try to boot to recovery with a battery pull and volume down and power the phone will just boot up normally without ever going to recovery. I then have to reflash amon via fastboot and it works again.
Click to expand...
Click to collapse
Post the command you are using to flash recovery
Sent from my ADR6425LVW using Tapatalk 2
Would having fastboot checked cause this? Just thinking out loud.
Sent from my ADR6425LVW using xda premium
Fastboot flash recovery (name of file). I can flash it fine it just eventually disappear. And fastboot is not checked.
I'm lost as to what could cause this..... Have you tried CWM recovery and see if same thing happens? I doubt it matters. Just throwing things out there
Sent from my ADR6425LVW using Tapatalk 2
Are you s-off?
Which Rom are you running ?
Sent from my ADR6425LVW using Tapatalk 2
No I haven't tried cwm I'm not a fan of it. I am s off running rezrom 3.4. I've ran it forever with no problems till recently. I'm completely stumped.
That's so odd. Try downloading quick boot from the market and seeing if it will help getting you into recovery. It can't be disappearing completely can it?
Sent from my ADR6425LVW using Tapatalk 2
It'll be there for anywhere from a couple days to a week and then vanish. My nandroid folder will still be there but no recovery
hardfallen87 said:
No I haven't tried cwm I'm not a fan of it. I am s off running rezrom 3.4. I've ran it forever with no problems till recently. I'm completely stumped.
Click to expand...
Click to collapse
I know. I don't like it either. I meant trying it to see if the same thing still happens, not to replace amon ra.
Sent from my ADR6425LVW using Tapatalk 2
I'll try it out tomorrow and twrp to see what happens
Hi, ever since last night my wife's Amaze has been stuck in a boot loop. The white HTC logo screen comes up and then it reboots and the same thing happens over and over. It was running firmware 2.14.531.3. I was able to boot into hboot and re-lock the bootloader with fastboot to flash the RUU and I flashed the latest one which is RUBY_ICS_35_S_TMOUS_2.14.531.3_R2 but still the same thing happens I even flashed it a second time but no dice. I'm really not sure what to do here. Did some other things too like take out the battery put it back in after a few minutes, charged it while the phone was off. If anyone has any ideas please help. Thank you
So no one has any ideas?
Sent from my Nexus 7 using Tapatalk 2
rock7632 said:
So no one has any ideas?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Try factory resetting in the stock recovery, then reloading the ruu via hboot.
(reboot into stock recovery from hboot, volume up and power button to bring the menu up so you can wipe the device)
Though reloading a stock ruu should wipe everything, are you getting any errors when reloading the stock ruu? And which one of the ruu files are you using to reload?
rock7632 said:
So no one has any ideas?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
You don't flash the ruu.. you need to put the file in root of ur SD and rename it to ph85img or something like that and reboot in the bootloader
Sent from my HTC_Amaze_4G using xda app-developers app
Dark Nightmare said:
Try factory resetting in the stock recovery, then reloading the ruu via hboot.
(reboot into stock recovery from hboot, volume up and power button to bring the menu up so you can wipe the device)
Though reloading a stock ruu should wipe everything, are you getting any errors when reloading the stock ruu? And which one of the ruu files are you using to reload?
Click to expand...
Click to collapse
I can try that. and no I didn't get any errors when loading the ruu. the one I did was the latest one for T-Mobile us 2.14.531.3_R2.
Perry977 said:
You don't flash the ruu.. you need to put the file in root of ur SD and rename it to ph85img or something like that and reboot in the bootloader
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
uhh yes that's what I did
Sent from my Galaxy Nexus using Tapatalk 2
rock7632 said:
I can try that. and no I didn't get any errors when loading the ruu. the one I did was the latest one for T-Mobile us 2.14.531.3_R2.
uhh yes that's what I did
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Did you try different kernel?
Sent from my HTC_Amaze_4G using xda app-developers app
Perry977 said:
Did you try different kernel?
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
RUU flashed the stock kernel when he reloaded.
Dark Nightmare said:
RUU flashed the stock kernel when he reloaded.
Click to expand...
Click to collapse
yeah and even prior to that I had the stock kernel
Sent from my Nexus 7 using Tapatalk 2
rock7632 said:
yeah and even prior to that I had the stock kernel
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Do u still have the custom recovery?
Sent from my HTC_Amaze_4G using xda app-developers app
Are you s-off? SuperCID? you need to set both back to the original values and reflash stock ROM from bootloader.
Perry977 said:
Do u still have the custom recovery?
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
no i flashed the stock recovery before i loaded the RUU.
olegy said:
Are you s-off? SuperCID? you need to set both back to the original values and reflash stock ROM from bootloader.
Click to expand...
Click to collapse
I'm s-on
Sent from my Nexus 7 using Tapatalk 2
rock7632 said:
no i flashed the stock recovery before i loaded the RUU.
I'm s-on
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Even if, you didn't need to reflash anything, apparently the fact that the ruu wipes and restores everything to stock still hasn't sunk in yet, anyways, we're missing some info here, what else happened before this issue that you're not telling me, since bootloop issues are easily resolved by a stock reload via hboot but yours seems to be on the same loop no matter what, are you giving it the time to boot after reloading via hboot? First boot takes a bit of time, patience is very vital.
Dark Nightmare said:
Even if, you didn't need to reflash anything, apparently the fact that the ruu wipes and restores everything to stock still hasn't sunk in yet, anyways, we're missing some info here, what else happened before this issue that you're not telling me, since bootloop issues are easily resolved by a stock reload via hboot but yours seems to be on the same loop no matter what, are you giving it the time to boot after reloading via hboot? First boot takes a bit of time, patience is very vital.
Click to expand...
Click to collapse
Ya like he^^ said, it does take a very long to boot up after flashing an ruu, could take a good 10 mins or maybe more...
Now if you did wait and it still just bootlooped after flashing the ruu, either the ruu is bad, or u did something wrong, OR u got some serious software problems going on
Due to the fact, atleast from reading your first post, it sounds like it was running fine then suddenly just started bootlooping. And then flashing an ruu didn't fix it. Sounds to me like ur phone has some serious issues
sent from my NRGized Amaze,
powered by faux kernel v.13
Dark Nightmare said:
Even if, you didn't need to reflash anything, apparently the fact that the ruu wipes and restores everything to stock still hasn't sunk in yet, anyways, we're missing some info here, what else happened before this issue that you're not telling me, since bootloop issues are easily resolved by a stock reload via hboot but yours seems to be on the same loop no matter what, are you giving it the time to boot after reloading via hboot? First boot takes a bit of time, patience is very vital.
Click to expand...
Click to collapse
That's just it, after loading the ruu via hboot the phone asks for a reboot and when I do it it barely takes 5 seconds on the HTC logo white screen then the phone reboots again and the same thing happens. And as far as anything happening before, nothing really happened. The battery died a couple of days ago and the when we charged it and tried to turn on the phone this started happening
Sent from my Galaxy Nexus using Tapatalk 2
I've tried everything I could think of. Loaded 2 different ruu's, manually wiped everything from recovery and nothing has worked, its still doing the exact same thing. I really don't understand how it can be bricked just out of nowhere
Sent from my Nexus 7 using Tapatalk 2
rock7632 said:
I've tried everything I could think of. Loaded 2 different ruu's, manually wiped everything from recovery and nothing has worked, its still doing the exact same thing. I really don't understand how it can be bricked just out of nowhere
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I think Im having an issue similar to yours. Is there any interaction after it begins to flash the RUU? I found a video for the thunderbolt where it asks you to approve the update before it finishes. My phone does the update then jumps back to the fastboot screen.
Need some help. I gave a friend of mine my old thunderbolt. I had it running the latest version of Nusense that was based off the ics ota. Now for some unknown reason my buddy brings phone to someone else to have his down grade it or something. Needless to say whatever he did or whatever program he ran turned the phone from rooted to unlocked and now its s-on. I've tried a few things, but cant seem to get anything to work. Think the main problem is I can seem to get the computer to recognize the phone. It shows up in devices but not as a drive. Tried drivers, but nothing. Tried all in one tool, but it keeps coming up error-no device. I turn phone on and it comes up to the white screen with the htc logo for a few minutes then shuts off. I can get into hboot/bootloader with no problem and the phone will stay on. here is what it says.
Unlocked
mecha xd ship s-on
microp-/
radio-1.48.00.0930w3
emmc-boot
My sd card has nothing on it except su zip and 4ext recovery...can get into that with no problem. Just want to be able to get the phone working again. Any help would be great
Thanks
Sounds like he attempted to update the phone with the ota. That is the only way I can think that you would stay unlocked but s on. The revolutionary h boot wasn't able to be overwritten by the new h boot but the update was still somehow able to put the phone into s off.
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
Sounds like he attempted to update the phone with the ota. That is the only way I can think that you would stay unlocked but s on. The revolutionary h boot wasn't able to be overwritten by the new h boot but the update was still somehow able to put the phone into s off.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
I got some maore info, turns out he tried to use the htc all in one tool to put in back to stock. Now i had it running a rom based off the ota along with the ics radios. From what I was told all was good until the ruu uploaded. It rebooted, and then got stuck on the white screen with the htc logo. He then went back in and realized that the phone was locked and s-on...used htcdev to get it unlocked again, but couldnt do anything else with it. Ive tried all I can think of with no luck...any ideas, suggestions.
Thanks
Try going here http://www.forums.infectedrom.com/showthread.php?p=67914
I'm not sure this will work or help you but it may. This is the only current method to root the ota.
Sent from my ADR6400L using Tapatalk 2
Thanks for the root, I've tried that first. I get to the part were you open a cms prompt and try and do the PGO5img.zip file, but it says waiting on device. I have drivers installed , but for some reason my computer know there is a device connected...shows up in devices, but not as a drive. Not sure what to do
Sent from my DNA using Tapatalk
That is probably because you can't enable debugging because of the state it is in. What happens when it is connected and you type adb devices?
Sent from my ADR6400L using Tapatalk 2
Probably a dumb question, but were would I type that and how
Sent from my DNA using Tapatalk
In the command prompt.... Get familiar with it because it is needed for that guide. If you don't have adb installed on your pc it won't work.
Sent from my ADR6400L using Tapatalk 2
Had it, not sure if still do. If not will down load again and let u know. Thanks for the help.
Sent from my DNA using Tapatalk
Think its still on my system. Typed inc:\android>adv devices.
It checks and comes back with some numbers and letters and says off line. Did I do this correctly
Sent from my DNA using Tapatalk
Sorry spellings off today..trying to do to many things at once...typed in adb devices...friggin spell check.
Sent from my DNA using Tapatalk
Was that with the phone connected?
Sent from my ADR6400L using Tapatalk 2
Yes
Sent from my DNA using Tapatalk
Boot into the bootloader and select fastboot. Then connect the USB, open the command prompt and this time try fastboot devices.
Sent from my ADR6400L using Tapatalk 2
It says ht11zs007516. Fastboot
Sent from my DNA using Tapatalk
That's a good sign then. At least fastboot sees your device. Can you still access recovery?
Sent from my ADR6400L using Tapatalk 2
Yes...I have 4ext recovery and am still able to get in
Sent from my DNA using Tapatalk
Have you tried clearing caches? Also try a full wipe and reflash of the stock ics ota
Sent from my ADR6400L using Tapatalk 2
Cleared caches and I tried the nusense Rom I originally had on phone and got nothing...it seems to go through the motions in recovery like its loading Rom, but when I reboot, same white screen. Can try again....side note, radios no longer listed as ics radios, now 930w3...part of what other guy did.
Sent from my DNA using Tapatalk
Hmmm what does your h boot show
Sent from my ADR6400L using Tapatalk 2
Ok, trying to figure out how to restore to stock. Phone was rooted last night, bootloader unlocked, S-ON. some things happened, phone got reformatted. No OS on. Cygenomod will install, but stops at the loading screen. I'm leaving from spring break tomorrow and this is my step dad's phone, so I need a quick fix. S-off is out of the question, as we do not have Ubuntu, and I'm trying to get this fixed in the next half hour or so. I've tried downloading stock RUU's and sending it through fast boot, it's a nogo. Currently I've relocked the bootloader, which has broken the TWRP recovery, so everything is going through command promp. Can anyone A) provide me with the downloads to the current RUU file, and B) give me a list of commands to (hopefully) just BOOM, recovered and fixed back to stock?
jthensley said:
Ok, trying to figure out how to restore to stock. Phone was rooted last night, bootloader unlocked, S-ON. some things happened, phone got reformatted. No OS on. Cygenomod will install, but stops at the loading screen. I'm leaving from spring break tomorrow and this is my step dad's phone, so I need a quick fix. S-off is out of the question, as we do not have Ubuntu, and I'm trying to get this fixed in the next half hour or so. I've tried downloading stock RUU's and sending it through fast boot, it's a nogo. Currently I've relocked the bootloader, which has broken the TWRP recovery, so everything is going through command promp. Can anyone A) provide me with the downloads to the current RUU file, and B) give me a list of commands to (hopefully) just BOOM, recovered and fixed back to stock?
Click to expand...
Click to collapse
Your best bet would be to re unlock using the token they gave you and install mean bean as it has a son installer.
Sent from my EVO using Tapatalk 2
thicklizard said:
Your best bet would be to re unlock using the token they gave you and install mean bean as it has a son installer.
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
And then read the stickies about flashing the kernel if not S-off.
Sent from my EVO using xda premium
I flashed NOS 7 2.0.3 and i was put in to roaming. i went back to previous rom and still stuck in roaming. It is really bugging me. Does anyone know what to do. I am begging for help.
hello
Something similar happened to me when I flashed one of the aosp roms but I couldn't even get past the activation. What I did to fix it was to do a clean flash of the same rom, I think it was pac, start the phone up without the sim card in but connected to wifi, finish the activation, then go into the networks setting and change the cdma subscription to RUIM/SIM.
I'm not sure if this will help you but it's worth a shot I suppose.
Sent from my HTC6435LVW using Xparent Skyblue Tapatalk 2
I had the same thing happen twice flashing a cm10.1 rom. What I did to fix it was install stock hboot 1.15, and run the stock RUU to go all the way back to stock. Make sure you relock your boot loader before running RUU. Get back to stock, go into boot loader and do a factory reset. Fixed mine twice. Maybe the long way of doing things, but it worked. Then you'll have to unlock boot loader and install custom recovery. Hope that helps.
Sent from my HTC6435LVW using xda app-developers app
jgraves12 said:
Something similar happened to me when I flashed one of the aosp roms but I couldn't even get past the activation. What I did to fix it was to do a clean flash of the same rom, I think it was pac, start the phone up without the sim card in but connected to wifi, finish the activation, then go into the networks setting and change the cdma subscription to RUIM/SIM.
I'm not sure if this will help you but it's worth a shot I suppose.
Sent from my HTC6435LVW using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
I'm having the same issue. I just tried to flash carbon and bam.... Roaming. Went back to stock backup but it too was in roaming. Going to try or fix.
Sent from my Nexus 7 using xda app-developers app
Gr8Jeepin said:
I'm having the same issue. I just tried to flash carbon and bam.... Roaming. Went back to stock backup but it too was in roaming. Going to try or fix.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Right above you is how to fix it, lock up and ruu back to stock, its worked for quite a few users.
Tapatalked from my HTC DNA - Carbon
you don't need to relock bl if s-off
I just moonshined this morning. First time i tried to put a rom on and this. I hate to be a pain but is there a procedure for completing this? I followed your moonshine and it worked great on the first try. sorry for the noodness.
beaups said:
you don't need to relock bl if s-off
Click to expand...
Click to collapse
I thought the ruu wouldn't run against an unlocked boot loader? I had to lock mine to get it to run, may have been another issue that happened to clear up when I did it, too.
Tapatalked from my HTC DNA - Carbon
pio_masaki said:
I thought the ruu wouldn't run against an unlocked boot loader? I had to lock mine to get it to run, may have been another issue that happened to clear up when I did it, too.
Tapatalked from my HTC DNA - Carbon
Click to expand...
Click to collapse
If s-off you can ruu when unlocked. Doesn't matter, tho.
Sent from my HTC6435LVW using Tapatalk 4 Beta
beaups said:
If s-off you can ruu when unlocked. Doesn't matter, tho.
Sent from my HTC6435LVW using Tapatalk 4 Beta
Click to expand...
Click to collapse
Good info, saves an extra step or two.
Tapatalked from my HTC DNA - Carbon
Ok... Im at a lose. Im still roaming. Im at 2.04 firmware. In bootloader it says "unlocked" at the top and S-ON. I've trying to update to current OTA with no luck. I've heard of issues with the SIM. I havent had any speciffic SIM card faults. If thats the issue i'll just get another SIM.
Thanks again guys
Edit: the SIM has been verified to work in original phone (broken screen). So maybe I'll swap it back in new phone.
Edit 2 [solved] Factory reset from bootloader. Thanks to c0ruptiv3 for having the issue before me.
beaups said:
you don't need to relock bl if s-off
Click to expand...
Click to collapse
To ruu back to stock, if s-off, you just run the ruu as an administrator? Do you have to change the splash screen if custom?
Sent from my HTC6435LVW using Tapatalk 2
i would like to bring this thread back up because I am still having the same issue. i ruu'ed and everthing
ThatFool said:
i would like to bring this thread back up because I am still having the same issue. i ruu'ed and everthing
Click to expand...
Click to collapse
This happened to me a little while back. I flashed back to 1.15 hboot, ruu'd back, rebooted, skipped through the setup and let it sit for a little while, rebooted into recovery, did a factory reset, rebooted again and I was roam free!
did the same but tried booting into recovery there is no recovery installed. not even stock android
Stuck in roam
I am not able to get my computer to recognize my DNA therefor I cant do any of these steps any help would be awesome.
Try *#*#4636#*#* and Phone Information. If you are on Verizon it should be cdma/LTE. Also your phone should not be in Global Mode in Mobile Network settings. Last time I was stuck on roaming this was why.
planedoc said:
I had the same thing happen twice flashing a cm10.1 rom. What I did to fix it was install stock hboot 1.15, and run the stock RUU to go all the way back to stock. Make sure you relock your boot loader before running RUU. Get back to stock, go into boot loader and do a factory reset. Fixed mine twice. Maybe the long way of doing things, but it worked. Then you'll have to unlock boot loader and install custom recovery. Hope that helps.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Ditto! Had the same thing happen to me, this was the only way I could get out of roaming. Doing the factory reset from stock recovery was key for me. I did everything, relock everything, flashed the RUU and was still roaming, it was only after factory reset from stock recovery did it come out of roaming.
Sent from my HTC6435LVW using xda app-developers app
Factory reset from RUU is the way I fixed mine when it happened to me. I did not relock bootloader before RUU though. Maybe make sure you put the stock splash screen back on and go back to original hboot before RUU.