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
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 ****
Okay i've been looking since last night for the answer to this question and found out nothing but everyone helping gives up and stops answering the question. Thus the thread is left with answered question.
But here goes. Currently on hboot. 1.50 s-on
Rooted my phone last night and download "mean" ics rom. Put it on the root of my sd card and went to recovery to boot the rom.
the rom wasnt downloading to the system and i dropped the phone by accident onto my bed and the battery fell out. (the back wasnt on it, not a hard fall)
attemped to install the rom again and by accident installed the "viper" ics rom
rebooted phone from recovery and phone will not go further than the htc logo boot.
any suggestions?
i can still go into hboot and recovery if i take my battery out. so i do not think its bricked since i can use my power button.
I think the dropped phone thing is coincidence. I'm pretty certain the issue is ICS and being hboot 1.5 s-on. For some reason, being s-on causes ICS to bootloop for most people. I highly recommend you go s-off. See: http://forum.xda-developers.com/showthread.php?t=1585846
Save the Drama for your Mama with Tapatalk 2
Go s off so no more bootlooping and when the phone fell it didnt affect the bootloop
Sent from my HTC EVO 3D X515m using xda premium
Will try right now
Koozyk said:
Will try right now
Click to expand...
Click to collapse
okay after reviewing the directions on how to do this, i am utterly confused at what i am supposed to do.i hate bother people with these noob questions. Not entirely sure how to turn s-off or what i am supposed to download
So is no one going to help me? i dont understand the terminology in the instructions...
Comments withdrawn
zcink said:
I wrote up a little tutorial for GSM but there is enough there to do it for CDMA. In fact the video shows CDMA.
http://forum.xda-developers.com/showthread.php?t=1777614
Click to expand...
Click to collapse
okay the problem with this is i cant get to my basic phone functions, im stuck with htc boot logo screen, bootloader/recovery
like i start the controlbearRelease program and it try to take me from bootloader to the main phone functions which it wont do. Like getting to the main phone functions would leave me with no problem
okay at thes point since so many people have seen it, im guessing im s.o.l?
Comments withdrawn
zcink said:
If you can get to recovery, then just Flash a stock rooted rom for your CDMA.
That will boot you up and you can s-off.
Yank the battery and put it back in. Then hold the down volume and press the power button while continuing to hold the down volume button until it boots into bootloader. From there you can get to recovery.
From recovery you can flash a stock rooted rom.
Then the rest should be easy.
After you are s-off you can flash any rom you want to for CDMA and you can flash the new Firmware and Radio.
Click to expand...
Click to collapse
you sir have just saved my phones life. You have no idea how thankful i am right now
Comments withdrawn
zcink said:
Let me know how it all turns out.
I'm not much help when it comes to CDMA because I've always used GSM.
Click to expand...
Click to collapse
This worked out perfecctly, took me a while to get the wire trick to work but i have a nice rom on my 3vo now. Thanks again.
how does this happen? solutions? im also not able to flash an ruu for some reason...stumped and have been working on this for an hour or so
rezin said:
how does this happen? solutions? im also not able to flash an ruu for some reason...stumped and have been working on this for an hour or so
Click to expand...
Click to collapse
Tampered is normal. Did you try flashing it with a ph98img, or as an .exe
It happens after you unlock and install a custom recovery I believe. Are you re-locked when you try to ruu?
Sent from my ADR6425LVW using Tapatalk 2
big_mike_2k6 said:
And are you re-locked when you try to ruu?
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Yeah make sure your bootloader is relocked
i was in the middle of doing s-off when the phone froze and corrupted the mem card...so i tried redoing the whole process over and i havent been able to get past the hboot...im still unlocked and have access to recovery and hboot but i cant flash a rom and boot into it...i cant run an ruu but the phone is not technically bricked...its an odd predicament...i just flashed a rom and i still cant get it to get past the hboot
Have you tried re-locking the bootloader and then run the ruu?
Sent from my ADR6425LVW using Tapatalk 2
i was hesitant to do anything else aside from the things i mentioned incase i was unable to get those back...gonna let the phone recharge and try again later tonight...any ideas are welcome in the mean time...and ill go ahead and relock it and try later
rezin said:
i was hesitant to do anything else aside from the things i mentioned incase i was unable to get those back...gonna let the phone recharge and try again later tonight...any ideas are welcome in the mean time...and ill go ahead and relock it and try later
Click to expand...
Click to collapse
just run the latest ruu in hboot if you are s-off it will make the phone like it was from factory.
if you are s-on but unlocked you will need to do the "fastboot oem lock" then runn the ruu.
in both cases the ruu will nuke the internal storage. first pass with install a new hboot and stock recovery along with 2 other items, then the phone will reboot into fastboot and install the rest. i recommend that you have a 60% or more battery life.
synisterwolf said:
just run the latest ruu in hboot if you are s-off it will make the phone like it was from factory.
if you are s-on but unlocked you will need to do the "fastboot oem lock" then runn the ruu.
in both cases the ruu will nuke the internal storage. first pass with install a new hboot and stock recovery along with 2 other items, then the phone will reboot into fastboot and install the rest. i recommend that you have a 60% or more battery life.
Click to expand...
Click to collapse
Yeah I already got it up n running...between being unlocked and having a slightly dead battery I wasn't even being given the option to run an ruu...its running now but I still need to do s-off again, and of course my sd card is corrupted so ill work on that tonight
The same thing happened to me, glad I found your thread! Were you trying to s-off on the official ICS? That's what I was trying. I ran the .12 RUU and had unlocked, rooted and was trying to get S-off. I did the wire trick I was getting an HTC logo instead of Jbear logo. Right now I just relocked and it's running the RUU so I hope I can get back up and running.
I guess I should have just S-offed before running the ICS RUU
Edit: I am back up and running!
willdo7474 said:
The same thing happened to me, glad I found your thread! Were you trying to s-off on the official ICS? That's what I was trying. I ran the .12 RUU and had unlocked, rooted and was trying to get S-off. I did the wire trick I was getting an HTC logo instead of Jbear logo. Right now I just relocked and it's running the RUU so I hope I can get back up and running.
I guess I should have just S-offed before running the ICS RUU
Edit: I am back up and running!
Click to expand...
Click to collapse
Hey, I didn't have to do this, but if you noticed, controlbear makes backup copies of stuff like boot.img (forget what else) and puts them on your computer. If you crap out you ought to be able to fastboot flash boot [bootimgfilename.img] and be able to boot up your phone. I saw where one person did this to get going again after a failed soff.
Yeah well happened in my case is that I was already s-offed and then I flashed the ruu to go back to stock...then I relocked my phone cuz I'm having an issue with one of the pins on phone (the terminal that connects to battery).so I was gonna get it exchanged, I wanted it to look absolutely stock...so the "relocked" status wasn't good enough, so someone suggested doing s-off again so it will show locked in hboot...well that's where everything went wrong, the phone froze at the wire trick and then the entire memory card was corrupted which is normal...so when I went to redo the whole s-off procedure again I kept rebooting into the blank screen with the arrow...could not get past that, so I resorted to putting my real sd card in...I had no backups for that card cuz that one has my actual personal stuff so I figures it'd be ok since I used a spare to do s-off anyway...well upon powering on the phone it was also corrupted...so Ive actually given up on s-off and getting my phone restored and replaced for a while...I don't know why s-off has always given me problems I've watched and read every vid or post about s-off and am in no way tech illiterate but I've always had problems with s-off (i lost all my pics and documents the first time I did s-off even thought I backed everything up cuz the only way to get it right was to eliminate every file in the folder and rerun it again cuz it didn't back up my sd correctly If at all)...its beyond infuriating
well that didnt last long...i just unlocked and s-offed my phone again, only to be returned to s-on and fully locked (indistinguishable from brand new in box), as i originally intended...im gonna miss this particular phone but it has to be done
I rooted my evo 4g lte. I was having issues with data today and updating the profile. so I was going to unroot and try it stock. I relocked the bootlader, and somehow my rom image is gone!!!! i cant flash the ruu, it keeps failing error 155. someone please help me
Wrong thread. Need to be posted in q&a
sent from my EVO LTE with it's security flags down.
jrgalioto said:
I rooted my evo 4g lte. I was having issues with data today and updating the profile. so I was going to unroot and try it stock. I relocked the bootlader, and somehow my rom image is gone!!!! i cant flash the ruu, it keeps failing error 155. someone please help me
Click to expand...
Click to collapse
Similar thing happened to me. I have hboot 1.15. I relocked the the phone ran the RUU. Phone booted up normal with the everything stock. I then took the OTA and when it rebooted it was updating then it rebooted and the phone never turned on again. I sent it to HTC for warranty. They will get it tuesday. I'll see how this goes.
Okay guys... Enough with the flaming. If you can help, post! If not, don't. Grow up. It was posted in the wrong section. Use the report button in the upper-right corner of the post and report it.
Now, let me see if I can actually help you.
You're getting this error because you're trying to flash an older RUU on the phone than what's already on there. You'll need to flash the same RUU version or higher. If you took the latest OTA update, there may not be one available yet. I'd suggest you go through the HTCDev unlock again until that RUU makes it to the internet.
Team Nocturnal posted a couple of the older RUU versions.
http://www.androidfilehost.com/main/EVO_4G_LTE_Developers/Team.Nocturnal/RUU/
~co~
closeone said:
Okay guys... Enough with the flaming. If you can help, post! If not, don't. Grow up. It was posted in the wrong section. Use the report button in the upper-right corner of the post and report it.
Now, let me see if I can actually help you.
You're getting this error because you're trying to flash an older RUU on the phone than what's already on there. You'll need to flash the same RUU version or higher. If you took the latest OTA update, there may not be one available yet. I'd suggest you go through the HTCDev unlock again until that RUU makes it to the internet.
Team Nocturnal posted a couple of the older RUU versions.
http://www.androidfilehost.com/main/EVO_4G_LTE_Developers/Team.Nocturnal/RUU/
~co~
Click to expand...
Click to collapse
Here is the issue with that though. When i run the RUU, it says my current image is........nothing. i have tried to flash the newest and the oldest versions.
jrgalioto said:
Here is the issue with that though. When i run the RUU, it says my current image is........nothing. i have tried to flash the newest and the oldest versions.
Click to expand...
Click to collapse
Hi there jrgalioto. Can you do me a favor, and boot into your bootloader for me? I'd like you to check the green text.
What Radio version does it say you have?
Also, if you can connect the phone up to your computer and run the fastboot command (in FASTBOOT USB mode):
Code:
fastboot getvar mainver
What number comes back? (If you can't run the command, don't worry about it)
---
If I might ask, why did you relock the phone?
---
I'm looking into trying to get you a link to a current RUU. One has been posted, but I can't access it because of Filefactory's restrictions. Hopefully somebody will post a mirror to the download soon.
~co~
closeone said:
Hi there jrgalioto. Can you do me a favor, and boot into your bootloader for me? I'd like you to check the green text.
What Radio version does it say you have?
Also, if you can connect the phone up to your computer and run the fastboot command (in FASTBOOT USB mode):
Code:
fastboot getvar mainver
What number comes back? (If you can't run the command, don't worry about it)
---
If I might ask, why did you relock the phone?
---
I'm looking into trying to get you a link to a current RUU. One has been posted, but I can't access it because of Filefactory's restrictions. Hopefully somebody will post a mirror to the download soon.
~co~
Click to expand...
Click to collapse
I relocked because I needed to bring it back to Sprint for service, so I needed to unroot it, because I wasn't receiving data to it. But I got it figured out now. I was able to unlock the bootloader again and my recovery was still there. So i reflashed a custom ROM, so I at least had something on my phone. When I called Sprint, I told them it was not a phone issue, they updated my username in the system, then I was able to ##72786# to get the hands free activation to complete without error 1012. So I am now back in business. However, If I ever do have to unroot again, I will be in the same boat.
jrgalioto said:
I relocked because I needed to bring it back to Sprint for service, so I needed to unroot it, because I wasn't receiving data to it. But I got it figured out now. I was able to unlock the bootloader again and my recovery was still there. So i reflashed a custom ROM, so I at least had something on my phone. When I called Sprint, I told them it was not a phone issue, they updated my username in the system, then I was able to ##72786# to get the hands free activation to complete without error 1012. So I am now back in business. However, If I ever do have to unroot again, I will be in the same boat.
Click to expand...
Click to collapse
For future ref...sprints tep policy covers rooted phones
Of course the first variable that could be the issue in any given situation is the fact that a phone is rooted
Sent from my SPH-L710 using xda app-developers app
00mred00 said:
For future ref...sprints tep policy covers rooted phones
Of course the first variable that could be the issue in any given situation is the fact that a phone is rooted
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
That was the 1st thought I had. What if the root is causing the issue. It, however was not the case. and all is now right with the world, and I am no longer a brick...for now...
jrgalioto said:
That was the 1st thought I had. What if the root is causing the issue. It, however was not the case. and all is now right with the world, and I am no longer a brick...for now...
Click to expand...
Click to collapse
Hi jrgalioto,
I was able to get a link to the new RUU for you. This one should work fine for you.
~co~
Yep...... sprint doesnt care that you're rooted.
I frequently tell them mine is so they dont go messing with things they shouldnt be
OK I just cleaned this thread of a bunch of GARBAGE.
If you don't want to help, post on a blog.
The guy is looking for help.
Seriously .
il Duce said:
OK I just cleaned this thread of a bunch of GARBAGE.
If you don't want to help, post on a blog.
The guy is looking for help.
Seriously .
Click to expand...
Click to collapse
Sorry duce
Sent from the depths of hell
Hey I try to help and I have even written a guide with a ton of info, I even went so far as to write down troubleshooting stuff and they still post the exact same stuff over and over, some times its a bit frustrating. I even gave instructions on what they need to do should they completely ruin the file tree, when have you seen anyone completely destroy the internal memory lol
closeone said:
Hi there jrgalioto. Can you do me a favor, and boot into your bootloader for me? I'd like you to check the green text.
What Radio version does it say you have?
Also, if you can connect the phone up to your computer and run the fastboot command (in FASTBOOT USB mode):
Code:
fastboot getvar mainver
What number comes back? (If you can't run the command, don't worry about it)
---
If I might ask, why did you relock the phone?
---
I'm looking into trying to get you a link to a current RUU. One has been posted, but I can't access it because of Filefactory's restrictions. Hopefully somebody will post a mirror to the download soon.
~co~
Click to expand...
Click to collapse
Any luck on the mirror for the new RUU download? I'm using the latest one I can find and I am stuck and can't get my phone to reboot, shutdown or anything. I can't run fastboot either. all I see is ***Tampered*** unlocked*** ....RUU update fail!
My phone won't respond to the volume down and power button either.
any suggestions?