Related
Hello everyone. The other day i used revolutionary to Perma-root my evo 3d. Everything was fine, till my text messages were not sending. So i took out the battery and popped it back in, and all i got was the HTC logo, then a dimmed black screen. Yes i can get into hboot, but i have clockworkmod recovery. I seem to be having a difficult time flashing the official sprint evo 3d rom. Any help is appreciated.
Download the pg86100.zip to revert back to stock in the dev section then go into hboot and let it update and you will start back at the stock ROM
Sent from my PG86100 using XDA App
xSpAzzZAttAcK said:
Hello everyone. The other day i used revolutionary to Perma-root my evo 3d. Everything was fine, till my text messages were not sending. So i took out the battery and popped it back in, and all i got was the HTC logo, then a dimmed black screen. Yes i can get into hboot, but i have clockworkmod recovery. I seem to be having a difficult time flashing the official sprint evo 3d rom. Any help is appreciated.
Click to expand...
Click to collapse
try hboot flashing twrp recovery. then if you can boot up update your prl and profile, also make a phone call to see if you got that error 16 thing. Also, did you by chance try to replace your bootanim? If you did, and something like wrong permissions were set, it would still be booting with a black screen, maybe try leaving it alone while it's booting for a bit?
I did the twrp recovery, but i still get the dim black screen. after the dim black screen it goes black for a few seconds, then goes to the HTC logo again. I didnt try to change anything either...
nuggyunlimited said:
Download the pg86100.zip to revert back to stock in the dev section then go into hboot and let it update and you will start back at the stock ROM
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
Above is your best solution. From there you can decide to either root again or wait a bit longer. But that should fix the issue and keep you from a boot loop of just the HTC screen.
Well thats where you are wrong. I am still in the boot loop after doing the stock HTC EVO 3d flash.
So the bootloader scanned and flashed the PG86IMG file and you are still showing just the HTC screen?
Did you follow the directions here http://forum.xda-developers.com/showthread.php?t=1194053
Hi where exactly do the adb and fastboot files go when you start to run commands?
Well no i still get the boot loop. guess i have a bricked phone...
xSpAzzZAttAcK said:
Well no i still get the boot loop. guess i have a bricked phone...
Click to expand...
Click to collapse
A brick is when the phone is completely unresponsive and won't boot or give you a charging led. If you can get to hboot you're not bricked. I would do a factory wipe from hboot menu (choose clear storage), and then either run an RUU with your phone in fastboot usb mode, or use a PG86IMG.zip
of an RUU to flash back to stock. That should hopefully fix the loops.
Sent from my PG86100 using XDA App
**** YES! I used the RUU.exe from sprint and now my phone works.
k2buckley said:
A brick is when the phone is completely unresponsive and won't boot or give you a charging led. If you can get to hboot you're not bricked. I would do a factory wipe from hboot menu (choose clear storage), and then either run an RUU with your phone in fastboot usb mode, or use a PG86IMG.zip
of an RUU to flash back to stock. That should hopefully fix the loops.
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
From past experiences like this, wipe, flash the bare stock rooted ROM in the development section. Do this in recovery mode. Before wiping you could try just flashing the bare Rom over. That usually worked for me.
Sent From My HTC Evo 3D Using Tapatalk On The Now Network From Sprint!
xSpAzzZAttAcK said:
**** YES! I used the RUU.exe from sprint and now my phone works.
Click to expand...
Click to collapse
Sorry, was a min too late. Glad it works again!
Sent From My HTC Evo 3D Using Tapatalk On The Now Network From Sprint!
xSpAzzZAttAcK said:
**** YES! I used the RUU.exe from sprint and now my phone works.
Click to expand...
Click to collapse
Sweet, glad you got it booting. Now that you've ran the RUU, you'll probably need to run Revolutionary again and then flash TWRP recovery. You should be good to go then. I think your hboot will still be S-off after the RUU, but from reports of other people it acts like it's still S-on and won't let you flash anything, so running Revolutionary again is necessary.
Well i cant use revolutionary...
My device is not supported?
And now i cant make calls or text messages, i get error 16.
any help?
xSpAzzZAttAcK said:
Well i cant use revolutionary...
My device is not supported?
And now i cant make calls or text messages, i get error 16.
any help?
Click to expand...
Click to collapse
Call Sprint. . they can fix it. . .it's actually a common problem after the root. Try to make a call. . .you will get the error message. . .you should hang on the line for a few minutes and it will direct you to sprint. They will call you on another line. . that's not your phone, and have you power the phone off. . .they will wait a few minutes then tell you to turn it on and make a test call. . .they may have you go thru a few things, but I didn't. . .and it will work.
http://forum.xda-developers.com/showthread.php?t=1194460 this forum should answer the question
Help!
I feel like such a freakin noob. My EVO3D is not quite bricked but I think i broke my recovery img AND my ROM. All I can do is turn on Hboot. Tried the stock Sprint RUU to go back to stock and i keep getting an error message everytime it tries to update the ROM image. Have no idea what to do now without being able to go into recovery. Suggestions?
My phone is doing the exact same thing, cept running the ruu.exe didn't fix it. Anyone else have some more ideas?
My original thread http://forum.xda-developers.com/showthread.php?t=1281565
hi im having strange issues, i though was the rom i was using, but i change from rom and my issue persist, when i leave iddle my phone, suddenly or reboots or shutdown :S i guess this its since i update radio to latest, anyone have this issue? i want update all firmware but i read from some, the cellphones are bricked.
im using in mexico.
any help? thanks a lot
Im having this same issues and its getting really annoying . I had a htc screen loop problem so i re locked the phone and ruu'd back to stock of the latest update (or rather flashed the PGIMG86 file or whatever) and the phone literally now reboots its self whenever it feels like , most noticeable if i leave it alone for a little while or press the power button to turn the display off. I re rooted and am now on freshrom and its still doing it occasionally. I think it might have been doing it before i ever did that relock though, too. Is this a problem with the new firmware? Is there anyway to downgrade , like an odin type of application?
this sounds like a kernel issue. the first guy (OP) i assume you are on GSM being out of the united states... i'm not sure i can provide you a whole lot of help there because i am not familiar with the GSM version of the EVO 3D. however, random rebooting can usually be attributed to a few general things, so either of you can trouble shoot and start here....
bad download of boot.img (files were corrupted somewhere)
-you should try flashing another kernel/ROM combo where users are NOT reporting
any issues whatsoever. also, try re-downloading your existing .zip just to make
sure the one you are using is not corrupted.
remove your micro SD card...
-most people don't think of this, but a bad SD card can cause random reboots. it is
a disk, and if your device is getting errors or something when trying to read it, it
will reboot to check the disk. start by moving apps OFF the SD card, then removing
the SD card entirely. if the reboots go away, that was your issue, and time for a
new SD card. i had this same issue when i first got my Evo, thought it was the
phone, turned out it was a bad card.
that's a good place to start. come back with questions/results.
i just deleted everything off of the sd card and it happened again afterwards. also it was happening before re - locking of the bootloader , and across several roms and kernels. totally lost. i also had it happen earlier today with no sd card in the phone , too. It was even happening on complete stock.
was it happening when you first got the phone? if so, time to take it to sprint
Sent from EVO 3D using XDA premium
its a replacement from asurion , im all out of insurance claims with them , lol . it was my gf's and she wanted a shift so she purchased one off of craigslist and gave me the 3d because my sgs2 has a damaged usb port. as soon as she got it in the mail she imeediatley gave it to me and i rooted it right away , lol , so im really not sure. id like to return it to factory stock before the ota update ,as i have a strange feeling it has something to do with it . i had it for a couple hours completley stock no nothing , then took the ota update and proceeded to root. i dont recall a reboot before that.
cobraboy85 said:
this sounds like a kernel issue. the first guy (OP) i assume you are on GSM being out of the united states... i'm not sure i can provide you a whole lot of help there because i am not familiar with the GSM version of the EVO 3D. however, random rebooting can usually be attributed to a few general things, so either of you can trouble shoot and start here....
bad download of boot.img (files were corrupted somewhere)
-you should try flashing another kernel/ROM combo where users are NOT reporting
any issues whatsoever. also, try re-downloading your existing .zip just to make
sure the one you are using is not corrupted.
remove your micro SD card...
-most people don't think of this, but a bad SD card can cause random reboots. it is
a disk, and if your device is getting errors or something when trying to read it, it
will reboot to check the disk. start by moving apps OFF the SD card, then removing
the SD card entirely. if the reboots go away, that was your issue, and time for a
new SD card. i had this same issue when i first got my Evo, thought it was the
phone, turned out it was a bad card.
that's a good place to start. come back with questions/results.
Click to expand...
Click to collapse
I'm using CDMA as well, my carrier has CDMA, and this it's new I tried other roms,I was thinking maybe ROM, but I'm using mean ROM that uses stock kernel, so I noticed this happens only when I'm not using my phone, and start happens since y flash new radio (coincidence maybe? ) but it's annoying I will check if it's happen again I'm this ROM, only happens once in this(turn it off)
.......................................................
Sent from my loved EVO 3D ;D
zen kun said:
I'm using CDMA as well, my carrier has CDMA, and this it's new I tried other roms,I was thinking maybe ROM, but I'm using mean ROM that uses stock kernel, so I noticed this happens only when I'm not using my phone, and start happens since y flash new radio (coincidence maybe? ) but it's annoying I will check if it's happen again I'm this ROM, only happens once in this(turn it off)
.......................................................
Sent from my loved EVO 3D ;D
Click to expand...
Click to collapse
exact same situation as me man , it mostly happens when i let the phone go idle , although it just happened when i was trying to edit the bookmarks widget on my home screen , and it seems to have happened after i updated the radio except i didnt flash i took the ota update.....for me its every rom , rooted or unrooted too
Ok happens again with different ROM, so I guess it's the radio, bit the weird thing is turn off the phone, no just reboot
So anyone knows how to revert to .9 radio? Or any solution? Thanks
.......................................................
Sent from my loved EVO 3D ;D
If you guys are both cdma and hboot 1.5 already.. Why don't you wipe everything in recovery just not your SD cards...
Hboot 1.5 S-ON
Then relock your phone run the RUU 2.17 exe and let it do it's thing then update your profile and so on.
Then just unlock your phone again with the unlock code should fix you guys up....
How are you guys flashing also? What recovery do you use?
I was having the same issues. Random reboots and random shut downs. Really getting frustrating. So I figured I would unroot my phone and take it into Sprint. I followed scrosler's guide to unroot but I used the latest PG86IMG.zip from Mr. Esp's thread. Of course this brought me up to hboot 1.5 but the random restarts and shut downs have stopped.
reaper24 said:
If you guys are both cdma and hboot 1.5 already.. Why don't you wipe everything in recovery just not your SD cards...
Hboot 1.5 S-ON
Then relock your phone run the RUU 2.17 exe and let it do it's thing then update your profile and so on.
Then just unlock your phone again with the unlock code should fix you guys up....
How are you guys flashing also? What recovery do you use?
Click to expand...
Click to collapse
I'm on hbot 1.4 I don't want lose s-off and if I upgrade I will do it but safe since I read some files was causing some bricks that's why I only update radio
.......................................................
Sent from my loved EVO 3D ;D
you can always go back to your previous radio too man.
also, flashing from 1.4 hboot you will not lose s-off with freezas all in one zip... I just did it today, no issues at all.
Sent from EVO 3D using XDA premium
cobraboy85 said:
you can always go back to your previous radio too man.
also, flashing from 1.4 hboot you will not lose s-off with freezas all in one zip... I just did it today, no issues at all.
Sent from EVO 3D using XDA premium
Click to expand...
Click to collapse
thanks i will try perhaps i read in freeza all in one some dudes get bricked
zen kun said:
thanks i will try perhaps i read in freeza all in one some dudes get bricked
Click to expand...
Click to collapse
no no... the ones that were bricked were the ones that tried to flash parts of TrevE's package. nobody had issues with freezas if I remember correctly... but... you should read before you flash it
Sent from EVO 3D using XDA premium
reaper24 said:
If you guys are both cdma and hboot 1.5 already.. Why don't you wipe everything in recovery just not your SD cards...
Hboot 1.5 S-ON
Then relock your phone run the RUU 2.17 exe and let it do it's thing then update your profile and so on.
Then just unlock your phone again with the unlock code should fix you guys up....
How are you guys flashing also? What recovery do you use?
Click to expand...
Click to collapse
I did everything you suggested here , down to a tee . I re locked the phone , except for i used the PG86IMG.zip file for 2.17 and loaded it in the bootloader to go back to stock after re locking. I let it sit for a day and then got bored and unlocked and rooted again and am on FreshRom. My original recovery was clockwork but now im on TW , hoping that itd help. Guess im gonna have to re-lock again and RUU back to an older base instead of 2.17. I waanna see if that fixes this problem.
cobraboy85 said:
no no... the ones that were bricked were the ones that tried to flash parts of TrevE's package. nobody had issues with freezas if I remember correctly... but... you should read before you flash it
Sent from EVO 3D using XDA premium
Click to expand...
Click to collapse
i'm also hboot 1.4 and flashed freezas and everything went perfect, just do it man
twister99403 said:
i'm also hboot 1.4 and flashed freezas and everything went perfect, just do it man
Click to expand...
Click to collapse
oh right "crosses finger", they must be flashed on recovery??? i have the "touch" clockworkmod recovery
zen kun said:
oh right "crosses finger", they must be flashed on recovery??? i have the "touch" clockworkmod recovery
Click to expand...
Click to collapse
NO!! lol put the zip file on the "root" of your sd card and reboot into BOOTLOADER will ask to update, click yes...
make sure to take it off your sd card after updated...
twister99403 said:
i'm also hboot 1.4 and flashed freezas and everything went perfect, just do it man
Click to expand...
Click to collapse
Ya I remember the mess with that it caused for folks that screwed something up they didn't read the directions....
Hello everyone
I am new to this forum, well I have been downloading roms for about 6 months but I registered today, anyhow I took my evo 3d to the sprint repair center the other day because my lcd went out, that's what the sprint employee had told me anyway and so two days later I received a replacement evo 3d, it was hboot 1.5 obviously and I took it home and installed the 2.17.651.5 RUU because sprint puts a version of the 2.17.651.5 ruu on their evo 3d's that does not communicate well during the unlock process of HTCdev.com, so here is my problem, after flashing the ruu I unlocked my bootloader via the htcdev unlock method, and began to flash my first custom rom, and I have run into the same problem over and over, I would boot into clockwordmod recovery via fastboot and then flash the rom after performing a super-wipe and every single time I would get a boot loop, no matter which rom I used, it would boot up and get to the setup screen and boot loop constant boot loop, every single rom I tried, I have not experienced this before when flashing roms, I then looked at a few threads of the roms I tried to flash and one recommended that I extract the boot.img from the zip and flash it via fastboot, some people say that you are required to do that with hboot 1.5 but in the past when I used my old evo 3d I never had to do that and it was hboot 1.5 s-on, please if someone has an answer I would gladly appreciate it, thanks in advance
UndefinedUser said:
Hello everyone
I am new to this forum, well I have been downloading roms for about 6 months but I registered today, anyhow I took my evo 3d to the sprint repair center the other day because my lcd went out, that's what the sprint employee had told me anyway and so two days later I received a replacement evo 3d, it was hboot 1.5 obviously and I took it home and installed the 2.17.651.5 RUU because sprint puts a version of the 2.17.651.5 ruu on their evo 3d's that does not communicate well during the unlock process of HTCdev.com, so here is my problem, after flashing the ruu I unlocked my bootloader via the htcdev unlock method, and began to flash my first custom rom, and I have run into the same problem over and over, I would boot into clockwordmod recovery via fastboot and then flash the rom after performing a super-wipe and every single time I would get a boot loop, no matter which rom I used, it would boot up and get to the setup screen and boot loop constant boot loop, every single rom I tried, I have not experienced this before when flashing roms, I then looked at a few threads of the roms I tried to flash and one recommended that I extract the boot.img from the zip and flash it via fastboot, some people say that you are required to do that with hboot 1.5 but in the past when I used my old evo 3d I never had to do that and it was hboot 1.5 s-on, please if someone has an answer I would gladly appreciate it, thanks in advance
Click to expand...
Click to collapse
the problem is just that.....youre s-on..you either must do the wire trick...or unknownforces downgrade method to obtain s-off and then flashing will be easier bc of permissions needed to write to the boot partition...
wloftus said:
the problem is just that.....youre s-on..you either must do the wire trick...or unknownforces downgrade method to obtain s-off and then flashing will be easier bc of permissions needed to write to the boot partition...
Click to expand...
Click to collapse
That may be true but there are a lot of users on this forum who are s-on and still flash plenty of roms, most roms do not require you to be s-off and it's not a normal boot loop, the phone starts up and then gets to the setup screen and that's when it reboots, most boot loops occur at the boot animation, so why is this happening now when my old when which was hboot 1.5 s-on worked fine when flashing roms, someone please help
UndefinedUser said:
That may be true but there are a lot of users on this forum who are s-on and still flash plenty of roms, most roms do not require you to be s-off and it's not a normal boot loop, the phone starts up and then gets to the setup screen and that's when it reboots, most boot loops occur at the boot animation, so why is this happening now when my old when which was hboot 1.5 s-on worked fine when flashing roms, someone please help
Click to expand...
Click to collapse
youre right they do flash...they use an app called flash gui...unless you want to manually go and flash the boot image through fastboot
wloftus said:
youre right they do flash...they use an app called flash gui...unless you want to manually go and flash the boot image through fastboot
Click to expand...
Click to collapse
I know all of that, you are clearly not understanding me, I owned an evo 3d that was rooted and was hboot 1.5 s-on, I flashed roms for 4-5 months, I am not a noob, my replacement evo 3d that I got through sprint and unlocked the boot loader, I am flashing roms exactly the same way and I am getting boot loops at the setup screen for every rom, maybe next time you will read my entire post and not just skim through it
UndefinedUser said:
I know all of that, you are clearly not understanding me, I owned an evo 3d that was rooted and was hboot 1.5 s-on, I flashed roms for 4-5 months, I am not a noob, my replacement evo 3d that I got through sprint and unlocked the boot loader, I am flashing roms exactly the same way and I am getting boot loops at the setup screen for every rom, maybe next time you will read my entire post and not just skim through it
Click to expand...
Click to collapse
well then...maybe you should also try scanning the posts better... if youre upset that you have 2.17 and think thats the issue...do a downgrade...oh wait..you already knew that now if you had 2.17 before and had no problems maybe its not the phone...oh btw...my phone is a replacement from asurion as well...i had no issues doing what i needed.. now maybe...JUST maybe someone might know a bit more than you and you should try not to argue with them
UndefinedUser said:
I know all of that, you are clearly not understanding me, I owned an evo 3d that was rooted and was hboot 1.5 s-on, I flashed roms for 4-5 months, I am not a noob, my replacement evo 3d that I got through sprint and unlocked the boot loader, I am flashing roms exactly the same way and I am getting boot loops at the setup screen for every rom, maybe next time you will read my entire post and not just skim through it
Click to expand...
Click to collapse
I didn't really believe that all evo 3d's act differently until I got my replacement. Now I know that their not all the same, even when they have the same hardware version. I'm sure you can see that too. You just have to figure out what works for that phone. I think a sure fire way to get a good install when you have s-on is to use fastboot to boot to recovery. Have you tried that yet? It doesn't sound like you've got a normal bootloop and I haven't encountered your issue before but fastbooting to recovery is worth a try. I'm sure you've heard this a lot but I'm gonna suggest it anyway, get s-off, you won't regret it.
Also, does the phone reboot like that after you run an ruu?
wloftus said:
well then...maybe you should also try scanning the posts better... if youre upset that you have 2.17 and think thats the issue...do a downgrade...oh wait..you already knew that now if you had 2.17 before and had no problems maybe its not the phone...oh btw...my phone is a replacement from asurion as well...i had no issues doing what i needed.. now maybe...JUST maybe someone might know a bit more than you and you should try not to argue with them
Click to expand...
Click to collapse
I was not trying to argue, I was trying to get my point across, I know all about flashing on hboot 1.5 with s-on, like I said I owned a device that was not downgraded, all I am asking is for a simple answer to original problem, what is different about this device? if anyone could help I would appreciate it
UndefinedUser said:
I was not trying to argue, I was trying to get my point across, I know all about flashing on hboot 1.5 with s-on, like I said I owned a device that was not downgraded, all I am asking is for a simple answer to original problem, what is different about this device? if anyone could help I would appreciate it
Click to expand...
Click to collapse
What wikdNoob said. Some phones do fine flashing ICS ROMs with S-on, but from my reading of the forums, many phones bootloop when flashing ICS ROMs with S-on. Since you are 1.5 S-on, you should do the wire trick to get S-off.
I've read so many times how people use the same procedures to flash the same ROM with the same radios, hboot, etc where one gets bootloops and the other does not. Each phone is different.
coal686 said:
What wikdNoob said. Some phones do fine flashing ICS ROMs with S-on, but from my reading of the forums, many phones bootloop when flashing ICS ROMs with S-on. Since you are 1.5 S-on, you should do the wire trick to get S-off.
I've read so many times how people use the same procedures to flash the same ROM with the same radios, hboot, etc where one gets bootloops and the other does not. Each phone is different.
Click to expand...
Click to collapse
I just decided to do the wire trick and now i'm s-off, I love being s-off, I feel so free now
UndefinedUser said:
I just decided to do the wire trick and now i'm s-off, I love being s-off, I feel so free now
Click to expand...
Click to collapse
see how much easier that was now...?
wloftus said:
see how much easier that was now...?
Click to expand...
Click to collapse
yes I should not have argued with your logic, thanks for the help
UndefinedUser said:
I know all of that, you are clearly not understanding me, I owned an evo 3d that was rooted and was hboot 1.5 s-on, I flashed roms for 4-5 months, I am not a noob, my replacement evo 3d that I got through sprint and unlocked the boot loader, I am flashing roms exactly the same way and I am getting boot loops at the setup screen for every rom, maybe next time you will read my entire post and not just skim through it
Click to expand...
Click to collapse
Its A Problem With Certain Phones Because I Have A Replacement Right Now And I Can Flash ICS Roms With Ease But On My Purchased Phone I Would Get Bootloops.
NexusS4gFreak said:
Its A Problem With Certain Phones Because I Have A Replacement Right Now And I Can Flash ICS Roms With Ease But On My Purchased Phone I Would Get Bootloops.
Click to expand...
Click to collapse
I am now s-off, I feel so free, no more boot loops ever, I am so happy that I can flash roms with ease and in my own custom recovery, I don't ever have to touch fastboot again!
UndefinedUser said:
I am now s-off, I feel so free, no more boot loops ever, I am so happy that I can flash roms with ease and in my own custom recovery, I don't ever have to touch fastboot again!
Click to expand...
Click to collapse
Lol Congrats, I Was Thinking About S-OFF But With My Replacement I Dont Need To!
UndefinedUser said:
I am now s-off, I feel so free, no more boot loops ever, I am so happy that I can flash roms with ease and in my own custom recovery, I don't ever have to touch fastboot again!
Click to expand...
Click to collapse
Now that you're s-off you can change your boot splash screen, a lot of choices in the the themes and apps section. You can check mine out from the link in my Sig.
NexusS4gFreak said:
Lol Congrats, I Was Thinking About S-OFF But With My Replacement I Dont Need To!
Click to expand...
Click to collapse
you really should go s-off, I thought the wire trick method would be difficult it was literally the easiest thing I have ever done, I don't know if you are familiar with JTAG xboxes, I used to jtag a **** load xbox's back in the day, in high school, so all this **** is easy, no soldering involved with this ****
Heya everyone. So i failed the jbear s-off and now everytime i remove my battery i end up in a bootloop and the only thing to do is boot into bootloader and select the "recovery" option and it goes thru a loading bar and boots up. I tried running the RUU and everytime i do and then boot back up the problem is still happening...bootlooping when the battery is removed. Should i re-unlock, root, and attempt s-off again?
AGoogleUser said:
Heya everyone. So i failed the jbear s-off and now everytime i remove my battery i end up in a bootloop and the only thing to do is boot into bootloader and select the "recovery" option and it goes thru a loading bar and boots up. I tried running the RUU and everytime i do and then boot back up the problem is still happening...bootlooping when the battery is removed. Should i re-unlock, root, and attempt s-off again?
Click to expand...
Click to collapse
I thought you gave up after the last post in this thread.
Creating more threads and posts about the same problems isn't going to make them any more likely to get solved. If you have dropped your phone and done your own repairs there is most likely something wrong with the phone, as Sprint already pointed out.
ramjet73
ramjet73 said:
I thought you gave up after the last post in this thread.
Creating more threads and posts about the same problems isn't going to make them any more likely to get solved. If you have dropped your phone and done your own repairs there is most likely something wrong with the phone, as Sprint already pointed out.
ramjet73
Click to expand...
Click to collapse
There hasn't been any problems with the phone at all its life until the s-off failure. Its gotta be something from when I failed the s-off. I have never heard of bootlooping when the battery is removed. Or why the ruu won't do anything So I thought I'd ask around.
Sent from my PG86100 using xda app-developers app
Hi guys ive got my htc rezound here with 4.0.3 ics and ive unlocked it and i used scottys guide to root it everything was in place i even got superuser user to install. i decided i wanted to s-off it so i got a peice of cat 6 cable it seemed it would work being an ethernet cable. i used
JuopunutBear S-OFF and everything came up as said i did the wire trick a few times i failed and decided to try again. it went to reboot my phone and now my phone wont boot at all it only does 2 things. goes into the JuopunutBear menu which i can do nothing in. or goes into the boot loader and says tampered and unlocked at the top. i can not go into recovery. now the JuopunutBear apparently backed up my files. i do not know where they are or what to do with them. can someone help me get my phone working again much thanks.
Everything you need is here:
http://unlimited.io/jbtroubleshooting.htm
shrike1978 said:
Everything you need is here:
Click to expand...
Click to collapse
caZSe
thanks man really appreciate now to try again lol
xsouthernburnx said:
caZSe
thanks man really appreciate now to try again lol
Click to expand...
Click to collapse
Shoot me a PM if you need some help, no question is a dumb question so take your time and hit me up with anything you're not real sure about.
I'm guessing if you had problems it's either because of drivers, or you had like the gingerbread firmware and hboot and an ICS rom and patch, because that causes jp bear to look at your phone and say "WTF"