Related
Hi everyone,
I've found the information in these forums to be very helpful and have never posted on anything before, but I have a question that I'm not finding a good answer for.
I successfully unlocked my bootloader and rooted last night and am now running scrosler's CleanROM. However I want to return to stock using the RUU from here:
http://forum.xda-developers.com/showthread.php?t=1338916
When I run the RUU I am getting stuck at the HTC recovery screen, and the windows installer tells me that the RUU is not compatible. I tried extracting the rom.zip, renamed it to PH98IMG.zip, copied it to the SDcard and load it in HBOOT, but it won't work either.
Any ideas? I mainly just want to make sure I have a working method to return to stock just in case I accidentally brick the phone at some point, but otherwise I'm good for now.
You run the ruu from your pc if it's like other htcs
sent from my newly unlocked Rezound
phackney said:
Hi everyone,
I've found the information in these forums to be very helpful and have never posted on anything before, but I have a question that I'm not finding a good answer for.
I successfully unlocked my bootloader and rooted last night and am now running scrosler's CleanROM. However I want to return to stock using the RUU from here:
http://forum.xda-developers.com/showthread.php?t=1338916
When I run the RUU I am getting stuck at the HTC recovery screen, and the windows installer tells me that the RUU is not compatible. I tried extracting the rom.zip, renamed it to PH98IMG.zip, copied it to the SDcard and load it in HBOOT, but it won't work either.
Any ideas? I mainly just want to make sure I have a working method to return to stock just in case I accidentally brick the phone at some point, but otherwise I'm good for now.
Click to expand...
Click to collapse
You need to have a recovery backup. Then you can always go back.
Sent from my Galaxy Tab 10.1
Neither of these answers attempt to address the issue of why the RUU doesn't work.
Have you tried both?
sent from my newly unlocked Rezound
Here's a more specific account of what happens when I run the RUU.
I get the progress bar that says "Sending......." but then after a few seconds I get the following error:
Error [155] unknown error
The ROM Update Utility cannot update your Android phone
Please get the correct ROM Update Utility and try again
I've spent the last hour Googling this error and have found that it is a known error with other HTC devices but can't find any info on the Rezound.
Found this helpful thread for a similar issue with the Desire:
http://forum.xda-developers.com/showthread.php?t=1029401
Tried starting the RUU with the phone already in fastboot but that didn't change anything.
What does it do when you copy the zip to the sd card and run it?
marclile said:
What does it do when you copy the zip to the sd card and run it?
Click to expand...
Click to collapse
I get the little progress bar in the upper right corner of HBOOT that shows it is reading the file, however it doesn't present me with the option to flash it. Instead it just skips to the HBOOT menu.
phackney said:
I get the little progress bar in the upper right corner of HBOOT that shows it is reading the file, however it doesn't present me with the option to flash it. Instead it just skips to the HBOOT menu.
Click to expand...
Click to collapse
Interesting, I wonder if anyone has ran it this ruu successfully
Solved
Figured it out. On a hunch I re-locked the bootloader and tried running the RUU using the Windows installer and it worked. It must be some sort of security check thing. I'll just unlock the bootloader again after it's done flashing. It might be good for someone with more seniority on the forum to make this information more visible in case anyone else runs into this issue.
phackney said:
Figured it out. On a hunch I re-locked the bootloader and tried running the RUU using the Windows installer and it worked. It must be some sort of security check thing. I'll just unlock the bootloader again after it's done flashing. It might be good for someone with more seniority on the forum to make this information more visible in case anyone else runs into this issue.
Click to expand...
Click to collapse
I agree. It probably needs to be added to the post that has the ruu files and it.
Glad you got it working.
Sent from my Galaxy Tab 10.1
marclile said:
I agree. It probably needs to be added to the post that has the ruu files and it.
Click to expand...
Click to collapse
Can you make that happen?
phackney said:
Can you make that happen?
Click to expand...
Click to collapse
i can't change the post but i'll post something in that thread.
Any idea on how to get the phone to relock if "fastboot oem lock" goes to "waiting for device" without responding?
I'm in a similar situation, but I cannot seem to get my phone to relock.
Nevermind. I forgot to get into bootloader mode via adb.
phackney said:
Figured it out. On a hunch I re-locked the bootloader and tried running the RUU using the Windows installer and it worked. It must be some sort of security check thing. I'll just unlock the bootloader again after it's done flashing. It might be good for someone with more seniority on the forum to make this information more visible in case anyone else runs into this issue.
Click to expand...
Click to collapse
Thank you. Had the same error. Felt like an idiot when I read your post. Can't believe I didn't think of that first.
So how do you re-lock? Thanks
Fastboot oem lock
Sent from my ADR6425LVW using XDA
10 characters
Gave my Evo 3d to my borother a few months back, but hes come back to me today saying it was stuck in bootloop.
He booted into the bootloader and did a factory reset, but it was still stuck in bootloop.
I tried to get into recovery to flash a new rom, but when i select recovery from the bootloader, that also goes into a bootloop.
Used adb to push the recovery onto the phone again but still just keeps bootlooping.
Not sure if its important but the phone is s-off. Any ideas on whats going on or how to fix?
Apologies, supposed to put this in Q&A forum
While you're at bootloader, connect USB and then flash a stock RUU.
androidcdma said:
While you're at bootloader, connect USB and then flash a stock RUU.
Click to expand...
Click to collapse
Thanks for the reply. Will i lose s-off with this?
Tones1971 said:
Gave my Evo 3d to my borother a few months back, but hes come back to me today saying it was stuck in bootloop.
He booted into the bootloader and did a factory reset, but it was still stuck in bootloop.
I tried to get into recovery to flash a new rom, but when i select recovery from the bootloader, that also goes into a bootloop.
Used adb to push the recovery onto the phone again but still just keeps bootlooping.
Not sure if its important but the phone is s-off. Any ideas on whats going on or how to fix?
Apologies, supposed to put this in Q&A forum
Click to expand...
Click to collapse
You didn't say what version of the Evo 3D you have (CDMA or GSM) or what bootloader is installed, but if it's a Sprint CDMA model I would recommend flashing the Sprint ICS RUU.exe from Windows after putting the phone into fastboot mode in the bootloader. You may have to relock the bootloader with the "fastboot oem lock" command first if it shows "***UNLOCKED***" at the top of the screen.
That will fix a lot of problems, especially when the phone is in an indeterminate state. After flashing the RUU you can HTC unlock, flash a custom recovery and then root the stock ROM or flash a rooted ROM.
ramjet73
Sorry it is a UK GSM (Europe). I have revolutionary bootloader installed. Got an RUU to try now thanks.
androidcdma said:
While you're at bootloader, connect USB and then flash a stock RUU.
Click to expand...
Click to collapse
Tones1971 said:
Thanks for the reply. Will i lose s-off with this?
Click to expand...
Click to collapse
^^^^ He got it first with the short version.
No, you won't lose S-OFF and won't need to relock the bootloader first if that's your current status.
And if it's a GSM model everything still applies, you just need a different RUU, which you already have.
ramjet73
Thanks ramjet. Thought this was going to be straightforward but cant get ruu to install. Error 170. Ill keep plugging away / googling away, hopefully come up with something
Tones1971 said:
Thanks ramjet. Thought this was going to be straightforward but cant get ruu to install. Error 170. Ill keep plugging away / googling away, hopefully come up with something
Click to expand...
Click to collapse
Error 170 means that the RUU utility can't find the phone. There's a readme.doc for running the RUU here, and the error codes are towards the end of that.
Are you putting it into "fastboot" mode in the bootloader, which should change to "fastboot usb" when it is connected to a computer? You also need to have the HTC USB drivers active, which can be accomplished by installing HTC Sync.
ramjet73
Tones1971 said:
Used adb to push the recovery onto the phone again but still just keeps bootlooping.
Click to expand...
Click to collapse
adb push into a bootlooping phone?
do you have the drivers for the phone? (if not download and install HTC Sync as they come with it)
did you try flashing a custom recovery img through fastboot? (go to bootloader select fastboot, connect USB, type "fastboot flash recovery nameOfYourRecoveryImg.img")
Yeah have tried installing custom recovery through fast boot again, and im in fastboot ok when trying to run the RUU. Also have HTC Sync installed from when i had the phone.. Drivers seemed to be ok as i was able to install the custom recovery with adb, alhough i still got bootloop after that.
Ive a few other things to try when i get home from work. Im sure it shouldnt be too difficult to resolve. Hopefully anyway.
Well this isnt going smoothly at all. Used another PC and was able to get the RUU to run.
However it now comes up with Error 131 Customer ID problem. The RUU was for HTC Europe (non branded). The phone was sim free. When i posted months back my cid was HTC_001. I checked it here: http://forum.xda-developers.com/showpost.php?p=22394863&postcount=172
However now when i get my CID it is showing as CID0202. Any way i can get an RUU to install? Any idea how a CID could change?
EDIT: noticed i used a different command last time.
fastboot getvar cid shows CID0202
adb shell getprop ro.cid now shows device not found (previously showed CID_001)
Thats typing both commands in same window, one after the other. One gets CID0202, the other device not found???
There's a change cid command in fastboot, fastboot oem writecid or something along those lines... however i believe the cid check is in the updater scripts of the ruu in which case a fastboot flash of all the img files should avoid it entirely... i don't remember the procedure for extracting the img files from the ruu but i believe ur supposed to run it and then dig through your temp files...
dessolator666 said:
There's a change cid command in fastboot, fastboot oem writecid or something along those lines... however i believe the cid check is in the updater scripts of the ruu in which case a fastboot flash of all the img files should avoid it entirely... i don't remember the procedure for extracting the img files from the ruu but i believe ur supposed to run it and then dig through your temp files...
Click to expand...
Click to collapse
Thanks for this. Ill see if i can find anything else out about it. So saves running the RUU exe and no cid check done then?
Need to bump this as im not getting anywhere. No RUU's will install, error 31 customer error. Have flashed recovery via ADB and through PG86IMG.ZIP, but still cant get in to recovery as it just continually reboots.
S-OFF with revolutionary. Anybody any ideas please?
Got bigger problems than i thought. Finally got an RUU to install after 4 days of trying, by first using fastboot oem writecid 11111111. But when the phone rebooted it was back bootlooping again. Is there any hope for my phone?
Tones1971 said:
Got bigger problems than i thought. Finally got an RUU to install after 4 days of trying, by first using fastboot oem writecid 11111111. But when the phone rebooted it was back bootlooping again. Is there any hope for my phone?
Click to expand...
Click to collapse
You need to stop cross posting in the d3rp Q&A thread and your own thread if you want more help. Cross-posting is stongly discouraged on XDA and it's really confusing when you are asking for help in one thread while getting different advice in another.
It sounds to me like all the CID changes on your phone have left it in an indeterminate state and I'm not sure at this point what is the correct CID and RUU for your model. If you could detemine that, set the CID correctly and flash the right RUU the phone should work, but it might be too late if you have in fact been flashing firmware that doesn't match your phone because the right RUU may not back that out properly.
That's all I can offer at this point, but since I don't know the history of your phone and how it got the various CID's you have reported, you will probably be the one that needs to figure it out.
ramjet73
Okay I have made a thread about this before, but no one had an answer for me, so I will try again, but I will be more descriptive of my issue.
So the other day, my Evo 3D, which is flashed to MetroPCS, lost its carrier settings when I was flashing a ROM. So I had to go home and use QPST to edit some files in the nvm/num folder (Using EFS). While I was editing, the program crashed, and I was forced to unplug my Evo.
Now, after it rebooted, it would go past the HTC Screen, and flash the boot animation for a split second, then shut off and restart. It would loop like this no matter how long I left it.
So I went into 4-EXT recovery, and formatted system, boot, data etc, and then flashed a ROM. Rebooted and got the same thing. So in a last ditch effort, I downloaded the latest ICS RUU for this phone, and tried all three methods to install. I ran the .exe, the program ran as expected, and the phone showed the progress bar on a black HTC Screen as updating, it rebooted when done, and then just continued to bootloop. I also pulling the rom.zip and renaming it to PG86IMG.zip and flashing it from fastboot. It worked and once it rebooted, did the same thing. I also ran it from fastboot usb, and got the same result.
However, I extracted the rom.zip and tried to use fastboot to flash individual .img files, and on EVERY one, I got "FAILED - Error: (remote: not allowed).
I had previously used the wiretrick to get S-OFF on my Hboot 1.58.
It says "Unlocked" at the top of the bootloader.
I really need to get my phone working, can someone PLEASE point me in the correct direction or at least help me out? Is my phone ruined? Is there a way I can clear the NV memory or something to truly reset the phone?
Once again, I will repeat, RUUs will not work!, I am S-OFF on HBOOT 1.58, my bootloader says "unlocked." No matter what I do it will bootloop. I can flash a recovery, but if I flash a rom it does the same stuff.
When you ran the ruu.exe, did you lock the bootloader first? If you don't, the ruu won't work.
coal686 said:
When you ran the ruu.exe, did you lock the bootloader first? If you don't, the ruu won't work.
Click to expand...
Click to collapse
I don't remember, but wouldn't the RUU fail if it was unlocked? Because it didn't fail, it just didnt work.
So now I screwed up, I got it to be able to erase/write in fastboot, I used fastboot erase instead of fastboot format and now my partitions are gone, how do I get those back?
AtmosFEAR4701 said:
I don't remember, but wouldn't the RUU fail if it was unlocked? Because it didn't fail, it just didnt work.
Click to expand...
Click to collapse
Sounds like a similar thing that happened to me when trying to flash a JB rom with a kernal that was not compatable....no matter what I did I could not get it out of the boot loop...I am Hboot 1.58 HTC unlocked and wire trick S-off...I finally flashed an old backup I had with a stock kernal and it fixed it all...dont know if this helps you at all but try wiping everything possible and flashing a stock kernal or an old backup you may have...
coal686 said:
When you ran the ruu.exe, did you lock the bootloader first? If you don't, the ruu won't work.
Click to expand...
Click to collapse
His s-off so doesn't matter if its locked or not.
iTzLOLtrain said:
His s-off so doesn't matter if its locked or not.
Click to expand...
Click to collapse
Good to know. I always thought you had to lock the bootloader anyway but leave it s-off. I learn something new everyday. :beer:
coal686 said:
Good to know. I always thought you had to lock the bootloader anyway but leave it s-off. I learn something new everyday. :beer:
Click to expand...
Click to collapse
Ok so I had accidenatly did "fastboot erase" and lost my partitions. I flashed the RUU again and now they are back, but if I try to use fastboot format, it says "Failed - Error: (remote: unknown command)." and it also said something about cannot determine partition type or something. I really need some help lol.
AtmosFEAR4701 said:
Ok so I had accidenatly did "fastboot erase" and lost my partitions. I flashed the RUU again and now they are back, but if I try to use fastboot format, it says "Failed - Error: (remote: unknown command)." and it also said something about cannot determine partition type or something. I really need some help lol.
Click to expand...
Click to collapse
Why are you using fastboot commands like "erase" and "format". Partitions should be formatted in recovery, not the bootloader.
If the RUU ran successfully it should reboot into the stock ROM when it finished. Did that work?
ramjet73
ramjet73 said:
Why are you using fastboot commands like "erase" and "format". Partitions should be formatted in recovery, not the bootloader.
If the RUU ran successfully it should reboot into the stock ROM when it finished. Did that work?
ramjet73
Click to expand...
Click to collapse
My first post says that I have run the RUU countless times and it still bootloops.
Nevermind... I sold it.
AtmosFEAR4701 said:
Nevermind... I sold it.
Click to expand...
Click to collapse
That's one way to solve the problem.
Sorry we couldn't figure it out.
coal686 said:
That's one way to solve the problem.
Sorry we couldn't figure it out.
Click to expand...
Click to collapse
It's okay. I am not buying another Evo 3D though. I am a MetroPCS customer so I buy flashed phones a lot, and I have a low budget so I'll either grab a flash Galaxy S2, or possibly grab the MetroPCS Galaxy S3 when I get some money.
Hello,
I was recently given a bootlooping Evo 4G Lte. I have been trying to figure out how to get this thing out of a bootloop and havent been able to do it. I, unfortunately, have no history on what happened to this device. Currently, it bootloops on the "Mean Bean" loading screen but will go no further. I can get into the bootloader, which says it is Unlocked, S-On, but I am unable to boot it into a recovery, it just returns back to bootloader. I have tried fastbooting twrp, but it fails (remote: image update error), and I have tried fastbooting the Mean Bean kernel thinking maybe thats all it needs, but that failed as well. Anybody have an insight? Much appreciated! Thanks.
Mike
I would run the 3.17 RUU. Hit the top link in my sig and look at the last post in the thread. You can run it from the bootloader. You'll need to re-root afterwards but it should get your phone back in working condition.
Sent from my HTC EVO 4G LTE
FinZ28 said:
I would run the 3.17 RUU. Hit the top link in my sig and look at the last post in the thread. You can run it from the bootloader. You'll need to re-root afterwards but it should get your phone back in working condition.
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
Thanks for the quick reply. I downloaded the RUU and ran it. However it sits and says "Waiting for bootloader" then errors out with "USB connection issue". The usb is working. The reason I never ran the RUU in teh first place was because i thought i read that you cant RUU with and unlocked bootloader. Is that not true? or is that my problem?
Mike
Not 100% sure but I will check with someone who used this tool recently and see if they were still unlocked at the time. Were you connected via Fastboot USB? Sounds more like a driver issue.
Sent from my HTC EVO 4G LTE
FinZ28 said:
Shouldn't matter. I know of a couple of users who were having phone issues and had unlocked bootloaders when they ran this tool. Were you connected via Fastboot USB? Sounds more like a driver issue.
Click to expand...
Click to collapse
Yeah I was connected and it said fastboot USB. It said rebooting to bootloader and rebooted, still said fastboot USB. Then it sat at a screen that said "waiting for bootloader" and after a while error ed out.
You can try relocking. You just need to run the command "fastboot oem relock" from a command line while connected via fastboot USB mode.
Sent from my HTC EVO 4G LTE
FinZ28 said:
You can try relocking. You just need to run the command "fastboot oem relock" from a command line while connected via fastboot USB mode.
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
I have since tried relocking to see if that was it, and it did the same thing.
Mike
Hopefully @YoFayce can shed some light on the matter since he recently used this on his phone.
Sent from my HTC EVO 4G LTE
FinZ28 said:
Hopefully @YoFayce can shed some light on the matter since he recently used this on his phone.
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
crazymike1234 said:
I have since tried relocking to see if that was it, and it did the same thing.
Mike
Click to expand...
Click to collapse
you can use the stock RUU and you can leave the bootloader unlocked as it will not affect anything.. it will fix your looping problem (Amongst others) as in gps not working ect.. once your done you will need to fastboot over your TWRP and from there mod as normal Good Luck! and ill be watching if you need any help!
YoFayce said:
you can use the stock RUU and you can leave the bootloader unlocked as it will not affect anything.. it will fix your looping problem (Amongst others) as in gps not working ect.. once your done you will need to fastboot over your TWRP and from there mod as normal Good Luck! and ill be watching if you need any help!
Click to expand...
Click to collapse
Problem is the ruu keeps error in out. I am beginning to think it may still be a driver problem. Someday I will get this done!
Mike
crazymike1234 said:
Problem is the ruu keeps error in out. I am beginning to think it may still be a driver problem. Someday I will get this done!
Mike
Click to expand...
Click to collapse
When in doubt update your android SDK remove the htc drivers reboot install drivers reboot and you should be good to go! Check the integrity of your USB cable and if possible use a rear USB port (More Power) Painful process yes but well worth it.. HTC drivers act strange till you reboot OOOh and make sure your using the proper HTC drivers for windows 32 bit or 64 bit!
YoFayce said:
When in doubt update your android SDK remove the htc drivers reboot install drivers reboot and you should be good to go! Check the integrity of your USB cable and if possible use a rear USB port (More Power) Painful process yes but well worth it.. HTC drivers act strange till you reboot OOOh and make sure your using the proper HTC drivers for windows 32 bit or 64 bit!
Click to expand...
Click to collapse
The drivers seem to be ok, but I am still not able to get any further. The RUU finds my phone, then reboots again to bootloader, but it just sits there saying "Waiting for bootloader" until it errors out due to "USB Connection error". I have tried a few different cables, and different USB ports. Not sure what the problem is but it just wont go any further. I re-unlocked my bootloader with htcdev. I have tried fastbooting a recovery to the phone but it errors out. I just cant get anything to work so I can boot anything. I really just want to get something working...anything! Any other ideas? Thanks.
Mike
use an sd card put a recovery image on the root of the sd boot into bootloader apply the recovery you should then have a recovery if you did it right, go into twrp mount device add a rom flash in recovery viola.
Sinistertensai said:
use an sd card put a recovery image on the root of the sd boot into bootloader apply the recovery you should then have a recovery if you did it right, go into twrp mount device add a rom flash in recovery viola.
Click to expand...
Click to collapse
Sinister,
Thanks for the reply. I put TWRP on the sdcard (named PJ75IMG, right?) and tried to apply that when I rebooted to recovery last night and it failed. It tries to load it but gives a few errors quick (No Image) Did I do it wrong?
Mike
crazymike1234 said:
Sinister,
Thanks for the reply. I put TWRP on the sdcard (named PJ75IMG, right?) and tried to apply that when I rebooted to recovery last night and it failed. It tries to load it but gives a few errors quick (No Image) Did I do it wrong?
Mike
Click to expand...
Click to collapse
make sure the file is just the PJ75IMG no additional text and it should be .zip If I recall correctly. make sure its on the root of the sdcard not internal but sd or external and it should be at the top level e.g. sdcard/ make sure its not in any other folders after you do that hold power and vol down get to hboot screen itll scan and then just follow the instructions.
Sinistertensai said:
make sure the file is just the PJ75IMG no additional text and it should be .zip If I recall correctly. make sure its on the root of the sdcard not internal but sd or external and it should be at the top level e.g. sdcard/ make sure its not in any other folders after you do that hold power and vol down get to hboot screen itll scan and then just follow the instructions.
Click to expand...
Click to collapse
Thats exactly what I did. It is the only thing on the sdcard. It says no gift file, Loading, no image for 4 different things. Then returns to the bootloader.
Mike
crazymike1234 said:
Thats exactly what I did. It is the only thing on the sdcard. It says no gift file, Loading, no image for 4 different things. Then returns to the bootloader.
Mike
Click to expand...
Click to collapse
zip files probably corrupt then. download another do the same process make sure you've got a good file use md5 checks
Sinistertensai said:
zip files probably corrupt then. download another do the same process make sure you've got a good file use md5 checks
Click to expand...
Click to collapse
Hmmm, Ill try download again. I got it from the main TWRP site.
crazymike1234 said:
Hmmm, Ill try download again. I got it from the main TWRP site.
Click to expand...
Click to collapse
careful on the vol down press you might be holding it too long and its canceling the update.
Sinistertensai said:
careful on the vol down press you might be holding it too long and its canceling the update.
Click to expand...
Click to collapse
Well, which recovery file should I be using? When I use the main TWRP ones (ie openrecovery-twrp-2.6.0.0-jewel.img) it gives me the errors like I said above. I now see they have a few labeled like this PJ75IMG-twrp-2.3.1.0-jewel.zip. When I use these, it tries to continue but says "Main Version Is Older. FAILED"
someone please help
im not sure what part did the damage. but i was trying to flash a new rom. it screwed up. didnt work. kept trying a few things. but long story short i accidently formated my external containing my back up, and nothing else worked on my phone.
end result, phones not recognized by Adb but can be seen on fastboot it has no OS and somehow its now S-ON and im stuck with out a phone.
i just redownloaded all my sprint drivers, sdk including, also have a fresh version of htc sync manager.
im lost. dont know what to do. this is my last resort till smash it and claim insurance
sirbrixalot said:
someone please help
im not sure what part did the damage. but i was trying to flash a new rom. it screwed up. didnt work. kept trying a few things. but long story short i accidently formated my external containing my back up, and nothing else worked on my phone.
end result, phones not recognized by Adb but can be seen on fastboot it has no OS and somehow its now S-ON and im stuck with out a phone.
i just redownloaded all my sprint drivers, sdk including, also have a fresh version of htc sync manager.
im lost. dont know what to do. this is my last resort till smash it and claim insurance
Click to expand...
Click to collapse
What os and firmware version? Its fixable dude.
dottat said:
What os and firmware version? Its fixable dude.
Click to expand...
Click to collapse
honestly, im not even sure, im not wicked unto this stuff, just want a functioning phone. i was trying to get a better radio driver.
but as of right now, i just want this back to stock.
sirbrixalot said:
honestly, im not even sure, im not wicked unto this stuff, just want a functioning phone. i was trying to get a better radio driver.
but as of right now, i just want this back to stock.
Click to expand...
Click to collapse
What is your availability tomorrow morning for a team viewer session?
dottat said:
What is your availability tomorrow morning for a team viewer session?
Click to expand...
Click to collapse
morning is zero. i have to work from 6-2 eastern time. what do you suspect that i ****ed up so aybe i can look. id gladly do a team view tho
sirbrixalot said:
morning is zero. i have to work from 6-2 eastern time. what do you suspect that i ****ed up so aybe i can look. id gladly do a team view tho
Click to expand...
Click to collapse
Well...since you are Sprint you probably unlocked via HTC dev. You can flash your unlock token again which will allow you to flash a custom recovery. You can then flash the current rooted Rom and use sunshine to s off again. The hard option is flashing an older Rom to use firewater as doing so will make your phone reboot about every thirty seconds because of the firmware mismatch. I can help you get it done that way if you want...up to you. Six of one half dozen of the other. You can almost always fix a phone that still boots to hboot and is unlockable. You won't have adb in the current mode either btw....
dottat said:
Well...since you are Sprint you probably unlocked via HTC dev. You can flash your unlock token again which will allow you to flash a custom recovery. You can then flash the current rooted Rom and use sunshine to s off again. The hard option is flashing an older Rom to use firewater as doing so will make your phone reboot about every thirty seconds becaui se of the firmware mismatch. I can help you get it done that way if you want...up to you. Six of one half dozen of the other. You can almost always fix a phone that still boots to hboot and is unlockable. You won't have adb in the current mode either btw....
Click to expand...
Click to collapse
i noticed adb wont work. lol'
i already used anothe runlock token, but it wouldnt take another rom how ever, i tried the guru reset via twrp install and a maximushd rom. neither of which took, im lost man, exhaused my options in my knowlage base, i need help; i eventried a ruu.exe but it wouldnt take due to some kind of unknown error. and tried a ruu hboot flash of the same **** and that didnt keep either
sirbrixalot said:
i noticed adb wont work. lol'
i already used anothe runlock token, but it wouldnt take another rom how ever, i tried the guru reset via twrp install and a maximushd rom. neither of which took, im lost man, exhaused my options in my knowlage base, i need help; i eventried a ruu.exe but it wouldnt take due to some kind of unknown error. and tried a ruu hboot flash of the same **** and that didnt keep either
Click to expand...
Click to collapse
You are on the current firmware... So you would need a current ruu to do that. Does your phone show unlocked now?
sirbrixalot said:
i noticed adb wont work. lol'
i already used anothe runlock token, but it wouldnt take another rom how ever, i tried the guru reset via twrp install and a maximushd rom. neither of which took, im lost man, exhaused my options in my knowlage base, i need help; i eventried a ruu.exe but it wouldnt take due to some kind of unknown error. and tried a ruu hboot flash of the same **** and that didnt keep either
Click to expand...
Click to collapse
hi
if you're bootloader showing unlocked try to install twrp recovery image
and then try to download stock nandroid rom for you're Sprint mobile then place it in you're mobile using adb push command then restore the the rom that you have placed at the end flash the image boot from the bootloader and you're done.
dottat said:
You are on the current firmware... So you would need a current ruu to do that. Does your phone show unlocked now?
Click to expand...
Click to collapse
yeah im fairly sure it says unlocked and tampered at the top of hboot, and it also says s-on some how. i tried fastboot command oem unluck and that didnt change it, i feel like this s-on nonsense is my main problem.
sirbrixalot said:
yeah im fairly sure it says unlocked and tampered at the top of hboot, and it also says s-on some how. i tried fastboot command oem unluck and that didnt change it, i feel like this s-on nonsense is my main problem.
Click to expand...
Click to collapse
Flash this. Let me know.
https://www.androidfilehost.com/?fid=23486521113837641
ahmedj31 said:
hi
if you're bootloader showing unlocked try to install twrp recovery image
and then try to download stock nandroid rom for you're Sprint mobile then place it in you're mobile using adb push command then restore the the rom that you have placed at the end flash the image boot from the bootloader and you're done.
Click to expand...
Click to collapse
hi friend,
if you had read the above posts you would know i dont have adb suppot thanks tho
dottat said:
Flash this. Let me know.
https://www.androidfilehost.com/?fid=23486521113837641[/
how should i go about it? twrp?
Click to expand...
Click to collapse
sirbrixalot said:
dottat said:
Flash this. Let me know.
https://www.androidfilehost.com/?fid=23486521113837641[/
how should i go about it? twrp?
Click to expand...
Click to collapse
Twrp
Click to expand...
Click to collapse
dottat said:
sirbrixalot said:
Twrp
Click to expand...
Click to collapse
tried that just now. it only said fail, no reason.
Click to expand...
Click to collapse
sirbrixalot said:
dottat said:
tried that just now. it only said fail, no reason.
Click to expand...
Click to collapse
What version twrp do you have and what did you do prior to flashing in twrp (wipe etc)?
Click to expand...
Click to collapse
dottat said:
sirbrixalot said:
What version twrp do you have and what did you do prior to flashing in twrp (wipe etc)?
Click to expand...
Click to collapse
i thinki just got a new version. 2.8.0.1 and i tried a wipe and cache wipe and allthat jazzz
Click to expand...
Click to collapse
sirbrixalot said:
dottat said:
i thinki just got a new version. 2.8.0.1 and i tried a wipe and cache wipe and allthat jazzz
Click to expand...
Click to collapse
Don't wipe system especially. Reboot to boot loader. Choose reboot boot loader. Go back into recovery and flash. Don't wipe anything
Click to expand...
Click to collapse
dottat said:
sirbrixalot said:
Don't wipe system especially. Reboot to boot loader. Choose reboot boot loader. Go back into recovery and flash. Don't wipe anything
Click to expand...
Click to collapse
says unable to open zip file on that try
Click to expand...
Click to collapse
dottat said:
sirbrixalot said:
Don't wipe system especially. Reboot to boot loader. Choose reboot boot loader. Go back into recovery and flash. Don't wipe anything
Click to expand...
Click to collapse
i got a hammer on one hand and my laptop(s) in the other. this hammer idea is looking pretty good hahaha
Click to expand...
Click to collapse