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.
Related
Mod delete
I'd suggest booting to fast boot and run an RUU or to bootloader and load an official PG86IMG file
http://forum.xda-developers.com/showthread.php?t=1092957&highlight=ruu
Although Don't shoot the messenger if i'm wrong.. I haven't had this complication
r0cky0790 said:
While everyone is having fun with s-off, I'm a sitting duck. I managed to successfully root my 3D but once I rebooted and made it to the handsfree activation window it instantly goes into bootloop. Im not a noob so by me having experience I tried to do a few things to fix it. First I tried cache wiping and it didnt work. Next I tried to back up, wipe phone, then restore and that didnt work as well and after doing that, now I can't get pass the first HTC screen. Anyone, PLEASE shed some light. This is very fustrating.
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
Have you tried redoing the root?
neopolotin75 said:
Have you tried redoing the root?
Click to expand...
Click to collapse
I'm already permanently rooted.
Sent from my HERO200 using XDA App
r0cky0790 said:
I'm already permanently rooted.
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
I was thinking maybe a re flash would fix was was causing the bootloop....Im not sure of the exploit they used but I figured that was worth a shot....kinda like when people were flashing Virus kingdom ROM twice....just a thought
Guess its time to head over to feenode #revolutionary. The Devs are hanging around there.
I think its the stock Rom. I've tried to backup and restore but ever since I wiped my data I can't get past the the splash screen. Im downloading a Rom to flash that I found in the dev section. If that doesn't work I'm going to try the RUU thing. Im made because the only thing I have to work with is a hero, and it downloads **** so slow. I had the fastest internet in the house until this happened.
Sent from my HERO200 using XDA App
r0cky0790 said:
I think its the stock Rom. I've tried to backup and restore but ever since I wiped my data I can't get past the the splash screen. Im downloading a Rom to flash that I found in the dev section. If that doesn't work I'm going to try the RUU thing. Im made because the only thing I have to work with is a hero, and it downloads **** so slow. I had the fastest internet in the house until this happened.
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
You'll get it back up and running. If you're downloading the TI-X rom by dc13, you're going to want to hold off on flashing that for now. He said it won't flash yet, and he's working on fixing it. If you're not talking about that one, then nevermind. I would think that running an RUU would fix it, but I'm not quite sure yet if there is anything you need to do before running the RUU, as far as the bootloader goes.
k2buckley said:
You'll get it back up and running. If you're downloading the TI-X rom by dc13, you're going to want to hold off on flashing that for now. He said it won't flash yet, and he's working on fixing it. If you're not talking about that one, then nevermind. I would think that running an RUU would fix it, but I'm not quite sure yet if there is anything you need to do before running the RUU, as far as the bootloader goes.
Click to expand...
Click to collapse
Yeah I just tried that Rom and it didnt flash. So now I have to wait another decade for this RUU to download. Hopefully everything works out.
Sent from my HERO200 using XDA App
r0cky0790 said:
Yeah I just tried that Rom and it didnt flash. So now I have to wait another decade for this RUU to download. Hopefully everything works out.
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
I would guess it'll only be a matter of hours before some stock rooted roms start appearing. I'm not sure if running the RUU will overwrite your hboot. I think I read that it will not, but don't know for sure.
k2buckley said:
I would guess it'll only be a matter of hours before some stock rooted roms start appearing. I'm not sure if running the RUU will overwrite your hboot. I think I read that it will not, but don't know for sure.
Click to expand...
Click to collapse
Well at this point I just need the stock system data to write so I could get pass the splash screen. So do I just name it PG38IMG.zip and try to load it through hboot?
Sent from my HERO200 using XDA App
r0cky0790 said:
Well at this point I just need the stock system data to write so I could get pass the splash screen. So do I just name it PG38IMG.zip and try to load it through hboot?
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
ok, off to bed. got it working.
RUU 1-15 version here:
http://forum.xda-developers.com/showthread.php?t=1092957
get the ZIP, not exe. i tried exe and it failed.
-rename file to PC86IMG.zip
-boot into bootloader, ruu will work itself.
boot back into stock rom.
-you will still have S-OFF, but i could not flash custom recovery. HBOOT looks like it reverted. trying to fastboot cwm/twrp recoveries failed.
-re s-off using rev (didnt fail even though i had S-OFF already, prev failed when i tried to rerun rev having S-OFF)
-HBOOT got changed to new version thru rev S-OFF
-was able to flash twrp using fastboot. tried cwm, worked. went back to twrp recovery.
-flashed fixed su zip (to enable root) and was able to boot back into stock rom.
-tested titanium, works.
-tested autokiller, works.
thanks for the help guys.
i am currently running an ICS rom and need to return mine for another device since it is defected.
Can i just htcdev LOCK then flash the ruu renamed as PH98IMG.zip to get back to stock?
You can do that cause I think ruu is different than just flashing stock. I had an og evo and I flashed the stock and I still had s-off so best advice make sure there is an s-on utility for ur device then use the ruu to return to stock
Sent from my Nexus S 4G using xda premium
v36sedan said:
i am currently running an ICS rom and need to return mine for another device since it is defected.
Can i just htcdev LOCK then flash the ruu renamed as PH98IMG.zip to get back to stock?
Click to expand...
Click to collapse
That will work fine. You can also relock then run the RUU on a windows PC, but pretty much the same thing will be accomplished.
i flashed back to gb then did waht i stated in the op and all it did was lock me in the bootloader and now my phone is stuck no matter what it do.
v36sedan said:
i flashed back to gb then did waht i stated in the op and all it did was lock me in the bootloader and now my phone is stuck no matter what it do.
Click to expand...
Click to collapse
I'm in the same place as you. I'm on ics and need return it since its defrctive. Please let me know how you get it to work. Someone toke me I had to flash gb kernel and Rom then relock and flash ruu
Sent from my ADR6425LVW using Tapatalk
I'm no expert but I think (if you made a Nandroid) you can extract the boot.img from the Nandroid then flash it and restore your stock Backup. I would also wipe / factory reset in recovery.
If you don't have a Nandroid backup you can download the RUU or a boot.img from a Rom like Scott's GB ROM and use one of those after you extract the boot.img.
I just did this today, I first flashed back to a gingerbread rom, then i unzipped the ruu and took the boot_signed.img from it, renamed it to boot than flashed it from fastboot. Then I put the ruu zip on my memory card (renamed it to ph98img) and fastboot OEM locked the device. I then rebooted the bootloader and applied the update.
Sent from my ADR6425LVW using Tapatalk
Bradh024 said:
I just did this today, I first flashed back to a gingerbread rom, then i unzipped the ruu and took the boot_signed.img from it, renamed it to boot than flashed it from fastboot. Then I put the ruu zip on my memory card (renamed it to ph98img) and fastboot OEM locked the device. I then rebooted the bootloader and applied the update.
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
which GB rom? and where can you get the ruu zip? i thought RUU was a program where you can format it.
ahh lol there needs to be a tutorial.
thanks ill do some more research though!
jackpot08 said:
which GB rom? and where can you get the ruu zip? i thought RUU was a program where you can format it.
ahh lol there needs to be a tutorial.
thanks ill do some more research though!
Click to expand...
Click to collapse
I got it from scottsroms.com, I just downloaded the zip file in the ruu section, as for reverting back to a gingerbread Rom, I'm sure anyone of them would work (scotts clean rom has always done me well). I only say that because once you flash the boot image, your ics rom won't boot, so you can't place the ruu on the memory card, unless you have another way to mount your sd card to the computer (i.e. adapter, or another phone)
Sent from my ADR6425LVW using Tapatalk
I wanna go back to gb just cause I'm getting tired of the ics bugs. But im still confused on how to do so... Can anyone help?
Sent from my ADR6425LVW using xda premium
tbgreen89 said:
I wanna go back to gb just cause I'm getting tired of the ics bugs. But im still confused on how to do so... Can anyone help?
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
I believe all you have to do is pick the rom you want, install it and your good. The majority of them automatically takes you to hboot to flash the kernal, but not all of them, so make sure you read the instructions before you flash.
Sent from my ADR6425LVW using Tapatalk
Bradh024 said:
I just did this today, I first flashed back to a gingerbread rom, then i unzipped the ruu and took the boot_signed.img from it, renamed it to boot than flashed it from fastboot. Then I put the ruu zip on my memory card (renamed it to ph98img) and fastboot OEM locked the device. I then rebooted the bootloader and applied the update.
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
Your method worked great! I was running Scotts Senseless ICS, used your method and now back on Scotts CleanRom 1.5.5! Thanks man!
Wait I thought even if you relocked the bootloader it said "relocked" or something at the top so Verizon could tell no matter what. That's the only reason i haven't unlocked yet because i just got a new device and want to make sure there are no bugs with it.
Sent from my ADR6425LVW using XDA App
werdna87 said:
Wait I thought even if you relocked the bootloader it said "relocked" or something at the top so Verizon could tell no matter what. That's the only reason i haven't unlocked yet because i just got a new device and want to make sure there are no bugs with it.
Sent from my ADR6425LVW using XDA App
Click to expand...
Click to collapse
That is correct. It will show re locked.
tbgreen89 said:
That is correct. It will show re locked.
Click to expand...
Click to collapse
Then wouldn't it be very easy for Verizon to tell? Also, does anyone know if they actually care?
Sent from my ADR6425LVW using XDA App
werdna87 said:
Then wouldn't it be very easy for Verizon to tell? Also, does anyone know if they actually care?
Sent from my ADR6425LVW using XDA App
Click to expand...
Click to collapse
I wondered this as well. Most csr's don't seem to be as knowledgeable as the people here on xda. They also don't seem to have a lot of knowledge on particular devices besides the obvious specs. I really don't think anyone is going to boot into fastboot to see it's been relocked, or even know what that means.
I'm gonna gamble with it, I'm tired of the noise coming from the headphone Jack whenever I play music.
Sent from my ADR6425LVW using Tapatalk
Please if someone is successful post a guide or instructions on how to get back to.stock
Sent from my ADR6425LVW using Tapatalk
werdna87 said:
Then wouldn't it be very easy for Verizon to tell? Also, does anyone know if they actually care?
Sent from my ADR6425LVW using XDA App
Click to expand...
Click to collapse
I just spoke with a Verizon tech on the phone last night, he told me that simply unlocking the phone would NOT void the warranty considering HTC is allowing it via their website. However he did say that any rooting/roms would void it immediately (if they can detect it of course).
So basically just put it back to stock and you are good?
Sent from my ADR6425LVW using XDA App
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
So this morning I decided to update my firmware from the PJ75IMG.zip. I booted back to and while I was in the bootload a factor reset was done by accident. Now my operating system is now erased. S-off'ed with lazy panda. Also, i have no backup because my Vista crashed a week ago. Sprint will replace my phone, but is there any possibility of unbricking now?
Sent from my PC36100 using XDA
thanosart said:
So this morning I decided to update my firmware from the PJ75IMG.zip. I booted back to and while I was in the bootload a factor reset was done by accident. Now my operating system is now erased. S-off'ed with lazy panda. Also, i have no backup because my Vista crashed a week ago. Sprint will replace my phone, but is there any possibility of unbricking now?
Sent from my PC36100 using XDA
Click to expand...
Click to collapse
Can you get into recovery?
Im guessing people dont understand the term bricked.....
Bricked- A device state in which you can NOT get to bootloader, Recovery or standard installed OS.
leo72793 said:
Im guessing people dont understand the term bricked.....
Bricked- A device state in which you can NOT get to bootloader, Recovery or standard installed OS.
Click to expand...
Click to collapse
If you are referencing my post, the op did not provide many details to determine if he is really "bricked" or not.
There have been quite a few cases of this.
You can try the lazypanda unbricker but it probably wont work
Yeah, recovery isn't the problem. Although it is showing relocked and I was going to reroot. just thought is was worth a shot posting.
Sent from my PC36100 using XDA
thanosart said:
Yeah, recovery isn't the problem. Although it is showing relocked and I was going to reroot. just thought is was worth a shot posting.
Sent from my PC36100 using XDA
Click to expand...
Click to collapse
You still haven't really explained what the issue is? If you can get to recovery then just flash the stock rooted update.
bad flash
njfoses said:
You still haven't really explained what the issue is? If you can get to recovery then just flash the stock rooted update.
Click to expand...
Click to collapse
so its there a way to reboot the phone after a bad flash, i plug the phone and my pc said that it needs to install the qcl... something drivers so that means the phone its on... how i can make it to get into recovery mod again... repeat black screen... i can not do anything else... by the way i tried to flash the new radio
Sorry to hear that. I believe you're gonna need a pc to try to do anything towards fixing it. Try an RUU. You can always get a replacement before they start giving out refurbs.
via eVo.
thephantom007 said:
so its there a way to reboot the phone after a bad flash, i plug the phone and my pc said that it needs to install the qcl... something drivers so that means the phone its on... how i can make it to get into recovery mod again... repeat black screen... i can not do anything else... by the way i tried to flash the new radio
Click to expand...
Click to collapse
Try running the ruu or the lazypanda unbricker tool.
njfoses said:
You still haven't really explained what the issue is? If you can get to recovery then just flash the stock rooted update.
Click to expand...
Click to collapse
Do you mean the ruu or a stock ROM. Will that recover the operation system files.? Basically I have nothing on my internal card.
Sent from my PC36100 using XDA
i tryed the lazypanda unbricker, but did not work it said it couldnt find the device and the ruu... where do i find the link?
thanosart said:
Do you mean the ruu or a stock ROM. Will that recover the operation system files.? Basically I have nothing on my internal card.
Sent from my PC36100 using XDA
Click to expand...
Click to collapse
If you can access recovery you can flash a rom. Your other option would be to run the ruu. You will never get your data back though.
---------- Post added at 09:48 PM ---------- Previous post was at 09:47 PM ----------
thephantom007 said:
i tryed the lazypanda unbricker, but did not work it said it couldnt find the device and the ruu... where do i find the link?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1655733
I'll give both the stock ROM and then the ruu if that doesn't work. I just thought having wiped everthing on the internal SD card would have removed crucial information. Will report back. Thanks for the help.
Sent from my PC36100 using XDA
Ok, so I flashed flex's 1.78 because that was the only stock Rom left on my ext sd card. Back in business. S-off, recovery, and rooted. Thanks rjfoses for the info.
Mods please delete.
Sent from my EVO using xda premium
leo72793 said:
Im guessing people dont understand the term bricked.....
Bricked- A device state in which you can NOT get to bootloader, Recovery or standard installed OS.
Click to expand...
Click to collapse
This...the most common being trying to flash back to the old firmware
Completely unresponsive no lights no power hard bricked
Rxpert said:
There have been quite a few cases of this.
You can try the lazypanda unbricker but it probably wont work
Click to expand...
Click to collapse
looks like he was soft bricked
Sent from my SPH-L710 using xda app-developers app
Wow this was one of the more confusing threads ive read...is the issue resolved if not please give some details i.e twrp version soff son?what you were flashing? Rom?
Sent from the depths of hell
thanosart said:
Ok, so I flashed flex's 1.78 because that was the only stock Rom left on my ext sd card. Back in business. S-off, recovery, and rooted. Thanks rjfoses for the info.
Mods please delete.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
He had a bad flash soft brick.
He fixes it
The end
Sent from my SPH-L710 using xda app-developers app
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.