I installed 2 mods last nigh on my vivid and it messed up phone. I am trying to go back to Stock Firmware but when i run the RUU for my phone it tells me the current firmware is GT-P7510-user an will not install the RUU. Any one have a idea how to fix it.I have tried other RUU's and the same thing.
Thanks
Can we say "Idiot" I had my tablet plugged in now it works
Lol that's awesome
Related
Does anyone know what the new HBoot version is with the newest 2.1 official leak? I installed Damages SprintUpdate2.zip and my phone still reboots after it falls asleep. A problem I have had with any 2.1 ROM I have every tried to install. I have always believed it was the Hboot version that was installed with the first 2.1 test leak. 1.47.0000 (HERO20000) is what It says now on my phone. I have never been able to change that version from my phone.
Thanks for your time.
How do you even check?
Kcarpenter said:
How do you even check?
Click to expand...
Click to collapse
you check by turning off your phone and turn it back on by holding down on the vol- key and the power button
Chaid said:
Does anyone know what the new HBoot version is with the newest 2.1 official leak? I installed Damages SprintUpdate2.zip and my phone still reboots after it falls asleep. A problem I have had with any 2.1 ROM I have every tried to install. I have always believed it was the Hboot version that was installed with the first 2.1 test leak. 1.47.0000 (HERO20000) is what It says now on my phone. I have never been able to change that version from my phone.
Thanks for your time.
Click to expand...
Click to collapse
I have the same exact rom on my phone but i still have the original hboot 1.41 did you happen to try and run a 2.1 RUU before? bc alot of ppl have been saying thats what happens when you use it ( meaning it switches to 1.47 )
xjreyes said:
I have the same exact rom on my phone but i still have the original hboot 1.41 did you happen to try and run a 2.1 RUU before? bc alot of ppl have been saying thats what happens when you use it ( meaning it switches to 1.47 )
Click to expand...
Click to collapse
Yes, Xjreves, back in April I ran the 2.1 Test RUU and my phone has been ****ed up ever since. Well, F'ed up in that I can't use any 2.1 ROMS. I was able to get it back to stock minus the 1.47 HBoot. I rerooted and can flash any ROM I want. 2.1 ROMs cause my phone to reboot if it falls asleep, so I have been using Gumbo 1.5 which runs flawless. Once the NEW official leak came out, I was excited that it might fix my phone. So I waited till Damage came out with a flashable ROM. But once I used it, I had the same problem of rebooting. And I'm scared to try the new 2.1 Official RUU, because if it doesn't change the HBoot and I still have the rebooting problem after, I'm REALLY screwed, as the RUU makes phone UN-rootable.
Chaid said:
Yes, Xjreves, back in April I ran the 2.1 Test RUU and my phone has been ****ed up ever since. Well, F'ed up in that I can't use any 2.1 ROMS. I was able to get it back to stock minus the 1.47 HBoot. I rerooted and can flash any ROM I want. 2.1 ROMs cause my phone to reboot if it falls asleep, so I have been using Gumbo 1.5 which runs flawless. Once the NEW official leak came out, I was excited that it might fix my phone. So I waited till Damage came out with a flashable ROM. But once I used it, I had the same problem of rebooting. And I'm scared to try the new 2.1 Official RUU, because if it doesn't change the HBoot and I still have the rebooting problem after, I'm REALLY screwed, as the RUU makes phone UN-rootable.
Click to expand...
Click to collapse
Just so you know, the new hboot from the leaked RUU is not causing your problem of rebooting. Many people, myself included, have the 1.47 hboot and the phones work just fine.
If I were you I would wait till the release the official update to 2.1, run the RUU that they give us and then take the phone into sprint and tell them that you have a bad phone.
I have this problem too.
HeroMeng said:
I have this problem too.
Click to expand...
Click to collapse
So what have you done? Are you back to stock? Have you had any luck with 2.1 ROMS? I'm extremely curious how you have handled the situation.
I have been lurking on these forums since my wife and I received our Heros about one year ago. The information on here as been wonderful and I have yet to really run into any big problems. I generally experiment on my phone first, and then after I find a good stable setup, I reflash and rebuild my wife's phone. Thus far, life has been good
However, I recently had both phones "turned" S-OFF using the unrevoked method, followed by the ENG-SPL. I tested my hero first by flashing a working HERCIMG that flashed the latest CWM, which worked without incident after an RUU. For the life of me, I cannot get my wife's phone to flash a HERCIMG. I have tried my own, downloaded several HERCIMG.zips around these forums. Tried reflashing unrevoked and ENG-SPL again. Nothing!
I've tried searching around for the past two nights to only find possibly one other person who MAY have had a problem (though I have been drinking, therefor no longer focused and cannot find the thread...will look for it in the morning). Both phones use CWM (latest generally, unless updating PRL, etc...), run some variant of CM7 (nightly or stable) and use firerat's (have removed and reflashed recoveries just in case this was conflicting). I cannot get it at all get this phone to flash a HERCIMG, anyone have any suggestions on something I am missing? Thanks!!
I was just told today that some phones that flash the eng-spl won't flash hercimg. Perhaps your wife's is one of them. I'm also told that ruu-ing the phone will remove the eng-spl and you should be able to flash a hercimg through hboot without eng-spl.
Edit: I'll also say that this information is less than 24 hours old for me, I'm no expert.
Drummerboy527 said:
I have been lurking on these forums since my wife and I received our Heros about one year ago. The information on here as been wonderful and I have yet to really run into any big problems. I generally experiment on my phone first, and then after I find a good stable setup, I reflash and rebuild my wife's phone. Thus far, life has been good
However, I recently had both phones "turned" S-OFF using the unrevoked method, followed by the ENG-SPL. I tested my hero first by flashing a working HERCIMG that flashed the latest CWM, which worked without incident after an RUU. For the life of me, I cannot get my wife's phone to flash a HERCIMG. I have tried my own, downloaded several HERCIMG.zips around these forums. Tried reflashing unrevoked and ENG-SPL again. Nothing!
I've tried searching around for the past two nights to only find possibly one other person who MAY have had a problem (though I have been drinking, therefor no longer focused and cannot find the thread...will look for it in the morning). Both phones use CWM (latest generally, unless updating PRL, etc...), run some variant of CM7 (nightly or stable) and use firerat's (have removed and reflashed recoveries just in case this was conflicting). I cannot get it at all get this phone to flash a HERCIMG, anyone have any suggestions on something I am missing? Thanks!!
Click to expand...
Click to collapse
When you say you can't get it to flash, what stage is failing? Does the bootloader not recognize the HERCIMG? Will it not install the .img? A little more detail, pls.
I have ruu-ed to remove ENG-SPL and attempted to flash under 1.47.000...no difference.
The bootloader does not recognize HERCIMG; it boots up the same with the same text output whether the file is there or not.
Drummerboy527 said:
I have ruu-ed to remove ENG-SPL and attempted to flash under 1.47.000...no difference.
The bootloader does not recognize HERCIMG; it boots up the same with the same text output whether the file is there or not.
Click to expand...
Click to collapse
If you ruu'd you took away your ability to flash through the bootloader, unless you used regaw's method to gain s-off. Does your bootloader show s-off at the top?
Another thought . . . you said you ruu'd, did you use 2.27.651.7 to ruu? If so, you may need to use a HERCIMG with an android-info.txt that has version 2.27.xxx in it instead of version 2.31.xxx. Check your HERCIMG and see what version is in there.
Sorry my mistake, I should have clarified that comment Yes, I used Regaw's method originally for S-OFF, which is still S-OFF even after the RUU as it should be.
This was originally how I ran into this problem as the HERCIMG was not flashing even as S-OFF 1.47.0000. So I flashed ENG-SPL to try something different with no change, then RUU-ed and tried again. Still nothing. Had to reroot and restore
Drummerboy527 said:
So I flashed ENG-SPL to try something different with no change . . .
Click to expand...
Click to collapse
Are you saying you still had 1.47.0000 after you ran the eng-spl? If so, I ran into that same problem. I initially had 1.46.xxx after eng-spl. Then I had to ruu to fix a problem and when I came back I flashed eng-spl again and my bootloader stayed at 1.47.0000. I am convinced Sprint figured out a way to muck with eng-spl, but this is just a conspiracy theory.
24601 said:
Another thought . . . you said you ruu'd, did you use 2.27.651.7 to ruu? If so, you may need to use a HERCIMG with an android-info.txt that has version 2.27.xxx in it instead of version 2.31.xxx. Check your HERCIMG and see what version is in there.
Click to expand...
Click to collapse
I used ruu 2.27.651.6. I actually saw this happening in another thread (still cannot find it) and so I tried that also. I have a HERCIMG with both a 2.27.xxx and a 2.31.xxx. Here is what I did with my phone:
Ruu-ed with 2.27.651.6, applied OTA update to 651.7, then applied the next update .2. Flashed the HERCIMG with a 2.27.xxx android-info.txt that was the latest CWM from jasonmaloney's thread (renamed as recovery.img). Worked like a charm!
My wife's phone:
Prior to Ruu (An RUU has actually never been done on this since we originally purchased it), I actually attempted to flash the latest CWM since the current version was 2.5.0.7 thru HERCIMG to test it out. No luck!
Thought that maybe ENG-SPL was causing the problem so I RUU-ed 651.6. Attempted to flash HERCIMG under S-OFF 147.0000 which the bootloader ignored.
I never updated beyond that as I couldn't get some of the newer methods of rooting to work so I rooted .6 and restored the nandroid while I continue the research.
24601 said:
Are you saying you still had 1.47.0000 after you ran the eng-spl? If so, I ran into that same problem. I initially had 1.46.xxx after eng-spl. Then I had to ruu to fix a problem and when I came back I flashed eng-spl again and my bootloader stayed at 1.47.0000. I am convinced Sprint figured out a way to muck with eng-spl, but this is just a conspiracy theory.
Click to expand...
Click to collapse
I actually ran into this problem initially going S-OFF...sort of-ish. I flashed Regaw on the phone with turned it S-OFF but ENG-SPL would not flash to 1.46.xxx. I had to remove firerats to get it to work. Not sure if it was related or not but afterward it worked.
After RUU-ing, Since S-OFF 1.47.xxx didn't work, I reflashed eng-spl and it went back to 1.46.xxx, though I was not using firerats at this point.
Drummerboy527 said:
I actually ran into this problem initially going S-OFF...sort of-ish. I flashed Regaw on the phone with turned it S-OFF but ENG-SPL would not flash to 1.46.xxx. I had to remove firerats to get it to work. Not sure if it was related or not but afterward it worked.
After RUU-ing, Since S-OFF 1.47.xxx didn't work, I reflashed eng-spl and it went back to 1.46.xxx, though I was not using firerats at this point.
Click to expand...
Click to collapse
The member you saw mention this issue is vayman, he has literally the exact same issue having followed the exact same steps a few days ago. I hope you can figure it out.
sent from a series of tubes.
Hi all,
I have been around a long time though i have never had trouble like this before..
i got a Incredible S PG32130 - HBOOT 2.0000.00 - Australian Delivered OPTUS002
I tried to follow the downgrade path so i could get S-OFF found here:
http://forum.xda-developers.com/showthread.php?t=1373697
Everything went fine so i proceeded with the older RUU flash to get back to 1.13 so can then run revoutionary..
Though the older RUU flash failed leaving the device hanging quietly brilliant.
Tried a few methods to get it back online to no avail.
So i htcdev unlocked the bootloader.. worked fine. still couldnt flash anything though. so put on CWM Recovery 5.0.2.0 which also worked fine..
I could then install custom ROMS.. So i tried IceColdSandwich though that wouldnt boot.. flashed the X4 kernel without issue.. so i assume it's cause the radio is still old and from what i gather i cant flash a new radio without S-OFF (i have tried through CWM and via Fastboot and via PG32IMG autoload in the bootloader and all fail.
So i tried an AOSP GB ROM still no luck.. Though neither of these would actually flash. get an communication error.. (could that be because ADB is not working? - am i missing a driver?)
And even tried a of legit WWE and CM7 both fail to install as well.
RUU_VIVO_ICS_35_S_HTC_WWE_4.10.405.1_Radio_20.74.30.0833U_3831.18.00.11_M_release_266013_signed
From my limited knowledge Radio is independent of AOSP/Sense/GB/ICS though Kernel is dependant. Though the only thing i havent been able to flash is the radio.. will the wrong radio stop you booting?
What are my options here to get S-OFF? I cant adb the device no matter what i do though i do have working recovery and fastboot.
Little help would be greatly appreciated.
damn..
http://forum.xda-developers.com/showthread.php?t=1337105
this fixed me.. the manual flashing of the boot.img was the problem..
ffs.. i have spent hours and read so many guides and that one was the only one that mentioned that you had to manually flash boot.img.
thanks all.
Sage said:
damn..
http://forum.xda-developers.com/showthread.php?t=1337105
this fixed me.. the manual flashing of the boot.img was the problem..
ffs.. i have spent hours and read so many guides and that one was the only one that mentioned that you had to manually flash boot.img.
thanks all.
Click to expand...
Click to collapse
Do you still require s-off? What error message did the ruu return when it failed?
the RUU error is simply USB Connection ERROR though this happens after it has erased and sent the package to the phone.
I think it maybe due to not being able to use ADB.. so prob a driver issue. either way i dont really need S-OFF and after the hours i have spent on this i am reluctant to play more
It aint even my phone! Mine is Sensation which is already S-OFF'd
Thanks for the offer though.
MOD: please feel free to move this to Q&A, my bad.
I've tried PACman, I've tried CM10, I've tried tried the Stock ish. CM10 and PACman get to the initial setup screen where I choose a language and when I hit start, or activate USB mass storage, it freezes for a moment then reboots. On the Stock ish one it gets to the Beats logo or AT&T and freezes, then reboots. I've tried the RUU executable and it errors out (but all it says is there's an error, try the correct one executable). Does anyone know what's likely the cause of my problems, and how to fix it so I can just get my phone working? I've been working on it for 18 hours straight, I haven't even eaten anything in nearly 24 hours, and it has been stuck and incapable of rebooting for nearly 12 hours.
Additional details: I was attempting to install PACman and I had some issues, then I used the RUU for Gingerbread (because I didn't realize it was Gingerbread) and got my phone working again. The Bootloader is JB, and it's S-OFF.
this should have been posted in the q&a section. but your bootloader is jb? if you used the RUU for gingerbread it should all be gingerbread. you now have to use the ics RUU to upgrade because it will give you problems like it is now. Use the ics RUU and then flash an ics/jb rom
ZeRo2o9 said:
this should have been posted in the q&a section. but your bootloader is jb? if you used the RUU for gingerbread it should all be gingerbread. you now have to use the ics RUU to upgrade because it will give you problems like it is now. Use the ics RUU and then flash an ics/jb rom
Click to expand...
Click to collapse
Neither the ICS nor the GB RUU will work. It just says there was an error, and to please try the right RUU.
EDIT: So I'm guessing that basically I need to get the GB RUU to work, then OTA update to ICS, then continue with everything. How do I get the GB RUU to work? How do I even troubleshoot the fact that it's not working?
EDIT 2: I was wrong, it's giving ERROR [156]: IMAGE ERROR.
EDIT 3: I think I found the problem. The RUU is blank when it says what image ROM it's going to update the device to. Anyone know how to fix that?
EDIT 4: the RUU says its current version is the same as the ICS RUU.
have you tried downloading from a different source? try just using the ics RUU so you don't need to OTA update. maybe the download is just corrupted
Zero's got the right idea!
yup...that's exactly what I'd do, even if it were a stock AT$T RUU rom...better than nothing...
ZeRo2o9 said:
have you tried downloading from a different source? try just using the ics RUU so you don't need to OTA update. maybe the download is just corrupted
Click to expand...
Click to collapse
They both worked earlier today. The problem shouldn't be with the files.
EDIT: are JB HBOOT and WCX recovery both completely compatible with the stock ROM? Is there a way to replace WCX and JB HBOOT with the original versions of each just to try and get everything back to the way it was?
EDIT 2: That's weird. I downloaded a new copy of the ICS RUU and it worked. Thanks for all your help and time, everyone!
HopelesRomantc91 said:
They both worked earlier today. The problem shouldn't be with the files.
EDIT: are JB HBOOT and WCX recovery both completely compatible with the stock ROM? Is there a way to replace WCX and JB HBOOT with the original versions of each just to try and get everything back to the way it was?
EDIT 2: That's weird. I downloaded a new copy of the ICS RUU and it worked. Thanks for all your help and time, everyone!
Click to expand...
Click to collapse
I had a sneaking suspicion your original RUU was corrupt...Glad it all turned out
just a heads up if you are using Chrome to download these files.. i personally have had TONS of issues downloading large files with Chrome and would recommend using FireFox to download files bigger than 200MB maybe even smaller.. and the RUU's if i remember correctly are around 400MB.. just for future reference since you've already fixed your issue..
To anyone who can help me. I've been rooted but running stock on my Sprint HTC One for about six months now and I wanted to drop back down to being unrooted and completely on stock so I can update to 4.3. I've unrooted my phone before but now it isnt working. Somehow I've managed to delete TWRP recovery from it and I'm on 1.31.651.2 which I'm pretty sure I updated to over top of root. I may be mistaken about that. Anyways, I tried using the RUU and that's when I realized that the 1.31.651.2 RUU hasn't been released yet so I went a different route.
Tried using the All-In-One Toolkit but my computer doesnt seem to be recognizing my phone.
As of right now the phone is powered on and able to view the homesceen and blinkfeed. Tried checking for update and now it is saying that my phone is up to date but is still on 4.1.2. Any help would be greatly appreciated as I have been sitting in front of my computer trying to fix this for more than 3 hours.
Check PM