Alright, I'm DirtyRacun S-Off hboot 1.15 and I went to update my firmware because I want to run JellyMEAN ROM, I get the PJ75IMG - No kernel, hBoot or recovery from this thread http://forum.xda-developers.com/showthread.php?t=2045935&highlight=3+15+firmware Go into bootlader update and everything seems to be fine. I then grab the kernel from that same thread go back to bootloader (Yes after deleting the firmware PJIMG) everything looks to update fine it went to reboot and it never booted. I tried to get back to bootloader nothing. I plug it into my PC and the charging light doesn't even light up. The only thing the phone does it the bottom lights will flash and when I plug it into my PC it will make the USB connected sound. I'm really hoping someone can get be back up and running.
Quick update... I was able to get into hboot and now in recovery. I'm just kind of nervous about rebooting. Anyone have any recommendations?
Why don't u flash meanbean rom.
Sent from my EVO using xda premium
Dude, you can't run new kernel on old base..reflash old one or flash meanbean
Sent from my EVO using xda premium
mrlakadaddy said:
Dude, you can't run new kernel on old base..reflash old one or flash meanbean
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Yup, figured that out after I calmed down a bit and thought about everything in order
Ok, this can be closed. I am up in running. Just flashed MeanBEAN and it's running like a champ. I have no idea how I got into the bootloader when it was unresponsive I just mashed a ton of buttons.
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.
Hope this is the correct place to ask, but quick question. So (short form) I relocked bootloader, reflashed the RUU, unlocked boot loader, installed ROM and it works great UNTILL I insert my SIM card, then it just keeps restarting. Why does this happen? What do I need to do, start all over and reflash everything? Please help!
Did you flash ruu twice.....it doesn't flash everything the first time through
Sent from my ADR6425LVW using XDA
This is gonna sound retarded, but I think so. The first time it installed the RUU, it was a blue status bar on the right, the 2nd time it was a brown status bar. But, I had already installed the ROM prior to seeing the brown bar...Does that make any since? I used to be decent at this, but it's been a while...
relock and reflash the ruu twice... then flash recovery and then flash a rom
Worst case flash the ruu again...watch it do each step successfully...that's what I would do. When I did the first flash using scoslers instructions I needed to do a battery pull since it was stuck at white htc screen...
Sent from my ADR6425LVW using XDA
ericsignals said:
Worst case flash the ruu again...watch it do each step successfully...that's what I would do. When I did the first flash using scoslers instructions I needed to do a battery pull since it was stuck at white htc screen...
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
Ok, we'll try and see what happens. I was hoping that it was something small. lol
It could be something else...but when I am not sure on something I start from scratch and try again lol
Sent from my ADR6425LVW using XDA
ok, so that did the trick for the SIM, but now I lost root and cant get it back...ugh! I've tried thru recovery and using Rezound_All-In-One_Kit_v2.0, but it dont work either. phone works for now though...so better than nothing. If yall got any ideas on how to get root back I would be thankful...yall know alot more about this than I do..haha
bskarpa said:
ok, so that did the trick for the SIM, but now I lost root and cant get it back...ugh! I've tried thru recovery and using Rezound_All-In-One_Kit_v2.0, but it dont work either. phone works for now though...so better than nothing. If yall got any ideas on how to get root back I would be thankful...yall know alot more about this than I do..haha
Click to expand...
Click to collapse
You need to HTC dev unlock again then flah amon ra
Sent from my Dinc... I mean Rezound
yojoe600 said:
You need to HTC dev unlock again then flah amon ra
Sent from my Dinc... I mean Rezound
Click to expand...
Click to collapse
+1 Its like starting all over again.
One more post for my ten
I was trying to update firmware to 2.13 thru hboot. It flashed ok and asked to reboot. Rebooted and now nothing. Windows does pick up the
phone and tries to install QHSUSB_DLOAD driver. I have tried to run the EVO unbricker using Ubuntu 32 bit but it cannot find the device.
I was running Mean Rom, 1.12 Hboot, S-OFF, TWRP.
had the same thing happen to me when I took 1.22 ota from my phone and it was toast I had to return it to best buy and get it replaced I know this does not help you but if the unbricking tool does not see the phone there is not much else you can do I spent hours trying to get mine to work but had no success
Why are you all taking the OTA to begin with? Clearly you guys should have at least attempted to learn the basics behind root and flashing.
I did not take the OTA. I was flashing the firmware upgrade only thru bootloader
d2kss2250 said:
I was trying to update firmware to 2.13 thru hboot. It flashed ok and asked to reboot. Rebooted and now nothing. Windows does pick up the
phone and tries to install QHSUSB_DLOAD driver. I have tried to run the EVO unbricker using Ubuntu 32 bit but it cannot find the device.
I was running Mean Rom, 1.12 Hboot, S-OFF, TWRP.
Click to expand...
Click to collapse
Damn that sucks! I'm almost sure you'll get a hboot 1.15 or above which means no s-off.. Make sure if and when you get the new to NOT let them activate it for you! You might get lucky with a hboot 1.12
Did you check the md5? Maybe you had a bad download.
Sent from my EVO using xda premium
I did check md5 and it was right
Have you tried the unbricker
yes, I tried the unbricker. I cannot get it to connect to the device. It is possible that I am doing something wrong.
d2kss2250 said:
yes, I tried the unbricker. I cannot get it to connect to the device. It is possible that I am doing something wrong.
Click to expand...
Click to collapse
No. Even with the qhsusb drivers and qpst it can not be unbricked. I gave up tonight after two days of trying
Same scenario...was rolling back firmware to previous version
Sent from my SPH-L710 using xda app-developers app
I am bricked also with no connectivity. I wasent updating any firmware tho or ota update. Was running CM10/Paranoid android. All a sudden while pluggin phone on charger at 7% I started bootlooping for no reason. I caught it the 3rd time and got to recovery. However I selected reboot system and phone hasent came back on since. No led lights, no Qusb, no connectivity at all. Sucks so bad. If anyone has any ideas, please let me know
Ladicx said:
I am bricked also with no connectivity. I wasent updating any firmware tho or ota update. Was running CM10/Paranoid android. All a sudden while pluggin phone on charger at 7% I started bootlooping for no reason. I caught it the 3rd time and got to recovery. However I selected reboot system and phone hasent came back on since. No led lights, no Qusb, no connectivity at all. Sucks so bad. If anyone has any ideas, please let me know
Click to expand...
Click to collapse
Plug your phone into a usb port and let it charge for 3~8 hours. Then hold down power button for 60 seconds.
On my evo the battery meter was constantly off by 5 or more %. It did exactly what you describe and was only doing it because it was out of juice.
Sent from my SPH-L710 using xda app-developers app
Can u get to recovery or bootloader?
Sent from the depths of hell
Just wondering what version TWRP you guys may of been on ?
wileout said:
Can u get to recovery or bootloader?
Sent from the depths of hell
Click to expand...
Click to collapse
I do make the assumption that when someone says the phone won't come back on,no lights,no qhsusb that there is no power to the device.
That assumption made,pretty simple to also assume they can not get into recovery or bootloader.
Twrp version does not matter. The phone just needs to charge.
Someone really needs to look more into this...I see 3~4 of these a day
Sent from my SPH-L710 using xda app-developers app
I ended up taking it to Sprint and they gave me a new one, Luckly it is hboot 1.12
d2kss2250 said:
I ended up taking it to Sprint and they gave me a new one, Luckly it is hboot 1.12
Click to expand...
Click to collapse
Sweeeet!
Sent from my SPH-L710 using xda app-developers app
I received a replacement Rezound today and have messed it up beyond my repair. When I powered the new phone on it was on the old GB software. I manually searched for an update which was finally found. I downloaded the update and went through the process of installing it. About half way through the update, a red triangle with an exclamation point appeard. I tried this process twice and then decided to run the RUU that I had installed on my sd card from my prior phone. The RUU was the most recent ICS.
At this point I was not S-off or rooted, but completly stock. The RUU did not fully run but it did update my HBOOT and Radio's. When I boot the phone, it is still on GB software. I have some how changed my bootloader to show Tampered as well.
I was able to flash a zip file of AmonRa 3.15 and was able to flash ViperRom 1.03. I thought this would correct the problems and allow me to S-Off but it did not.
I thought that if I could S-off I could maybe get this all straight. But I am not sure.
At this point, I have a phone that reboots after a few short minutes.
Any help will be greatly appreciated!!
Romans8vs1 said:
I received a replacement Rezound today and have messed it up beyond my repair. When I powered the new phone on it was on the old GB software. I manually searched for an update which was finally found. I downloaded the update and went through the process of installing it. About half way through the update, a red triangle with an exclamation point appeard. I tried this process twice and then decided to run the RUU that I had installed on my sd card from my prior phone. The RUU was the most recent ICS.
At this point I was not S-off or rooted, but completly stock. The RUU did not fully run but it did update my HBOOT and Radio's. When I boot the phone, it is still on GB software. I have some how changed my bootloader to show Tampered as well.
I was able to flash a zip file of AmonRa 3.15 and was able to flash ViperRom 1.03. I thought this would correct the problems and allow me to S-Off but it did not.
I thought that if I could S-off I could maybe get this all straight. But I am not sure.
At this point, I have a phone that reboots after a few short minutes.
Any help will be greatly appreciated!!
Click to expand...
Click to collapse
If it tanked doing the OTA ICS update right out of the box, I'd call VZW for another phone...
Thank you for the reply, but my hboot now says tampered and relocked. I do not think I could send the phone back in this condition and get a new one.
Anyone else have any ideas?
Un-lock using HTC unlock then s-off your phone using some wire tied to a couple thumb tacks. Run latest ruu again, then install recovery, then flash Rom.
Sent from my ADR6425LVW using xda app-developers app
iHateWebOS said:
Un-lock using HTC unlock then s-off your phone using some wire tied to a couple thumb tacks. Run latest ruu again, then install recovery, then flash Rom.
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
Why on earth do you hate WebOS?!?
I wasted a lot of life thinking it was the greatest....... Lies! Lies! Do you have any idea how lucky android users are to have on device recovery? When ya boot loop a webos phone ya need to hook up to a computer no matter what ya did wrong. Now I just restore a nandroid....I was so happy when I upgraded to a pre 2.... Now I just feel dumb for staying with webos for so long
Sent from my ADR6425LVW using xda app-developers app
AshtonTS said:
Why on earth do you hate WebOS?!?
Click to expand...
Click to collapse
Why do you not hate webOS? Awful.
In case anyone else has this problem, I was able to re-lock and flash the RUU through adb to get everything corrected. I'm now rooted, S-off, and running inef 1.2!
I installed TWRP last night and proceeded to flash JellyBAM. The issue now though, is that my phone won't get past the booting screen if I try to just let it turn on.
I cannot get into Recovery either. Last time I was able to, the back up file wasn't working.
I'm keeping calm at the moment because this is not the first time, but I could still use some help.
I'm trying to get the phone to recognize the PJ75IMG file, but it keeps failing to load.
If there's a thread I missed to see, please let me know. I'm headed to work soon so couldn't dig enough last night
Currently:
Tampered
Relocked
If you're S-on you have to flash the boot.img (kernel) separately from the ROM. You also need to go back and unlock your bootloader, since it's relocked. Hit the link in my sig for more info.
Sent from my EVO using XDA Premium 4 mobile app
FinZ28 said:
If you're S-on you have to flash the boot.img (kernel) separately from the ROM. You also need to go back and unlock your bootloader, since it's relocked. Hit the link in my sig for more info.
Sent from my EVO using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Okay, looks like that did the trick =O. I've rebooted the phone and it is currently in the jellyBAM splash screen. Loading. Taking quite a bit of time, but at least it's past the htc splash lol
Read the sticky threads in Q&A and general
SENT FROM MY LTEVO