Related
OK, so I'm a bit of a n00b here, and I need just a quick hand.
I'd flashed Myn's Warm TwoPointTwo a few days ago and was attempting to use metamorph to tweak the battery icon. Ran a Nand backup beforehand. Something went wrong with the metamorph and I was stuck in a bootloop afterwards.
So I hit power and held down on the volume rocker, hoping to get into my Nand.
Instead, it wouldn't let me select anything, went through its own update/recovery process, and now that it's done, I'm back to stock (complete with sprint bloatware) and totally unrooted. I DLed Rom Manager off the market and tried to get into Amon_Ra recovery, but it keeps telling me I don't have permission (thus I deduce I've lost root access.)
Is there anyway I can flash my Nand at this point, or do I need to go back through the rooting process?
Thanks for your help.
MadDogMaddux said:
OK, so I'm a bit of a n00b here, and I need just a quick hand.
I'd flashed Myn's Warm TwoPointTwo a few days ago and was attempting to use metamorph to tweak the battery icon. Ran a Nand backup beforehand. Something went wrong with the metamorph and I was stuck in a bootloop afterwards.
So I hit power and held down on the volume rocker, hoping to get into my Nand.
Instead, it wouldn't let me select anything, went through its own update/recovery process, and now that it's done, I'm back to stock (complete with sprint bloatware) and totally unrooted. I DLed Rom Manager off the market and tried to get into Amon_Ra recovery, but it keeps telling me I don't have permission (thus I deduce I've lost root access.)
Is there anyway I can flash my Nand at this point, or do I need to go back through the rooting process?
Thanks for your help.
Click to expand...
Click to collapse
To get a recovery on your phone, you need to have root.
To get root need superuser permissions and/or nand unlock
To get nand unlock and superuser permissions you need to go through the rooting process.
If you've used unrevoked 3.21 and have S-OFF. You can flash recoveries and superuser permissions without having to go through any rooting process.
So I guess then what I need to understand is how would I go about flashing the superuser?
edit: at this point I've already gone through the whole rooting process, including unrevokedforever.zip and the additional ENG bootloader. I get into ROM manager, and go to recovery, but the clockworkmod recovery doesn't see my most recent backup. Reflashing to RA recovery, it finds it, but tells me I have to run the recovery via ADB. ???
Pretty sure what happened is that you left a stock pc36img.zip on your sd card, leftover from your rooting process. When you booted into hboot, it loaded it automatically and you must have hit update. Not sure what caused your bootloop though.
Check your sd card, and if theres a pc36img.zip on it, delete it. Look for the superuser app in your app drawer, and also check your hboot to see if you're s-off. If you are in fact back to unrooted stock, you can always run unrevoked to quickly root and then you can restore your nandroid, just make sure you have the same recovery that you used to make the nandroid.
MadDogMaddux said:
So I guess then what I need to understand is how would I go about flashing the superuser?
Click to expand...
Click to collapse
When you go into the loader (Vol Down + Power) does it say S-Off in the first line?
If it does then you still have root and you can flash the custom recovery's .zip and you will be able to load back into recovery.
If you have S-Off read this: http://forum.xda-developers.com/showpost.php?p=8285266&postcount=1
Flashable SuperUser is located here: http://forum.xda-developers.com/showthread.php?t=682828
_MetalHead_ said:
Pretty sure what happened is that you left a stock pc36img.zip on your sd card, leftover from your rooting process.
Click to expand...
Click to collapse
Definitely. So now I need to get my microSD card reader and remove it. Can do.
Any idea why both Clockworkmod and Amon_RA are unable to load my backup? Versions for RA should be the same, and I think the same for Clockwork as well.
OK, I deleted PC36IMG.zip, now it just stays stuck in bootloader.
looks like I'm hosed, but here's what I'm learning on Freeza's thread, where I DLed the PC36IMG.zip in the first place:
freeza said:
UPDATE: It appears as though everyone is getting stuck in bootloader after this procedure. You can get out of this by reflashing your current ROM (without wiping) and/or restore a nandroid backup. Some have reported errors when trying to restore a nandroid backup. YMMV
Karadorde has put together a package that works. Read his instructions below:
First and foremost it seems that if you get stuck in the Bootloader (no matter what method you are using) then your Nandroid backups are broken. I don't know that anyone has been able to successfully restore from one of those yet.
The file in the OP allows you to apply just the engineering HBOOT.img (hboot_0.76.2000.img) This works flawlessly for some but not so well for others.
The file in Post 71 and Post 91 allows you to apply a full PC36IMG.zip that contains the engineering HBOOT.img (hboot_0.76.2000.img) This is a fix for some who have gotten stuck in the Bootloader after using the file from the OP. At the same time this has also caused the some of the same issues people were having with getting stuck in the Bootloader from the OP. This file will not downgrade any part of your phone, however, it will wipe the phone. Also it is reported that it broke root on one phone. I believe this only happened to one person, need confirmation on if it happened to multiple.
If you get stuck in the Bootloader you can re-flash your Kernel to fix the issue. Not sure if this works with the stock Kernel or if you have to have a custom Kernel. Looking for feedback on this.
If you get stuck in the Bootloader reflash your current rom. Need feedback on this as well.
Link to Karadorde's updated package: http://www.freeza-inc.com/PC36IMG.zip
Click to expand...
Click to collapse
With the text I've put in bold, looks like I'm hosed in that regard. So I'll just work on rebuilding it piecemeal.
Heh, first time I've tried to recover from a Nand, too. *sigh*
MadDogMaddux said:
looks like I'm hosed, but here's what I'm learning on Freeza's thread, where I DLed the PC36IMG.zip in the first place:
With the text I've put in bold, looks like I'm hosed in that regard. So I'll just work on rebuilding it piecemeal.
Heh, first time I've tried to recover from a Nand, too. *sigh*
Click to expand...
Click to collapse
If you reflash using the RUU from stock roms .com will that reset your hboot back to the non-dev hboot?
Sent from my Evo using XDA App.
xNotta said:
If you reflash using the RUU from stock roms .com will that reset your hboot back to the non-dev hboot?
Sent from my Evo using XDA App.
Click to expand...
Click to collapse
i do believe so, but someone correct me if im wrong, i do know when i unrooted a few weeks ago with the RUU i went to the newest hboot, but now that i'm rooted again im back to the ENG .76 version.
Running a RUU will put you at full stock, including radios and hboot.
If you are still stuck, try running the most current RUU and then rerooting.
http://forum.xda-developers.com/showthread.php?t=800582
_MetalHead_ said:
Running a RUU will put you at full stock, including radios and hboot.
If you are still stuck, try running the most current RUU and then rerooting.
http://forum.xda-developers.com/showthread.php?t=800582
Click to expand...
Click to collapse
RUU's solve everything. No? haha
Igotsanevo4g said:
RUU's solve everything. No? haha
Click to expand...
Click to collapse
They've sure helped me out of more than a couple binds
I know I've seen other people with this problem, but I don't think I've seen a fix but I'm hoping I'm wrong.
Installed CM7 RC2 and everything works great for a month. Some random reboots but no big deal. Today I get a reboot but instead of reloading it hangs on the CM7 boot logo. I go into clockwork recovery, do a full wipe, and reboot. From then on, all I can do is loop in the white HTC screen. No ROM, no Recovery.
I've tried to flash Amon Ra recovery and a stock RUU via at PCImag file. No love. Any ideas?
BrashL said:
I know I've seen other people with this problem, but I don't think I've seen a fix but I'm hoping I'm wrong.
Installed CM7 RC2 and everything works great for a month. Some random reboots but no big deal. Today I get a reboot but instead of reloading it hangs on the CM7 boot logo. I go into clockwork recovery, do a full wipe, and reboot. From then on, all I can do is loop in the white HTC screen. No ROM, no Recovery.
I've tried to flash Amon Ra recovery and a stock RUU via at PCImag file. No love. Any ideas?
Click to expand...
Click to collapse
I posted directions in reply to your PM. Here's the first thing to try. See if you can flash this, it's Amon Ra recovery v2.3
k2buckley said:
I posted directions in reply to your PM. Here's the first thing to try. See if you can flash this, it's Amon Ra recovery v2.3
Click to expand...
Click to collapse
DONT FLASH IT.
Put in root of sdcard, boot into bootloader, update, let it boot or boot into recovery.
Lol, I gave him detailed instructions on how to flash it using the bootloader, don't worry. I was pm ing with him.
Sent from my PC36100 using XDA App
r916 said:
DONT FLASH IT.
Put in root of sdcard, boot into bootloader, update, let it boot or boot into recovery.
Click to expand...
Click to collapse
He uploaded a recovery image in a PC36IMG, so it NEEDS to be flashed in the bootloader.
Ive had the same problem for two days now and have tried everything in the book it seems. Using fastboot or manually from the bootloader, every pc36img.zip fails with an error at (8) partition update failed! or remote : 51 partition update fail. I can get the newest ruu to get me stuck at the four triangle error and then I have to flash PC36IMG_AmonRA-v2.3-hausmod_revA.zip just to get back to the htc boot screen loop (which at least lets me get back to bootloader to start the vicious cycle again) . ANY help would be greatly appreciated. Heck, even any way to make it presentable at a sprint store would even work at this point (since it says s-off I'm guessing someone in the line of repair will realize its been rooted.
p.s. I have never had any problem with my phone and have flashed just about every rom out there and I always do a full wipe and usually a format_all too. This happened about two hours after I flashed Kings UNleashed Ultra Blakk R3 ( it just did a reboot on its own and its been in this mess ever since)
100proof said:
Ive had the same problem for two days now and have tried everything in the book it seems. Using fastboot or manually from the bootloader, every pc36img.zip fails with an error at (8) partition update failed! or remote : 51 partition update fail. I can get the newest ruu to get me stuck at the four triangle error and then I have to flash PC36IMG_AmonRA-v2.3-hausmod_revA.zip just to get back to the htc boot screen loop (which at least lets me get back to bootloader to start the vicious cycle again) . ANY help would be greatly appreciated. Heck, even any way to make it presentable at a sprint store would even work at this point (since it says s-off I'm guessing someone in the line of repair will realize its been rooted.
p.s. I have never had any problem with my phone and have flashed just about every rom out there and I always do a full wipe and usually a format_all too. This happened about two hours after I flashed Kings UNleashed Ultra Blakk R3 ( it just did a reboot on its own and its been in this mess ever since)
Click to expand...
Click to collapse
Once you've gotten back into recovery, specifically, amon RA 2.3, use the MS-USB menu and copy the contents of your SD card onto an external disk drive. Afterwards, use amon RA to partition and reformat your card. When you're done, copy only the Rom and amon RA (PC36IMG) file to your SD card. Shut down your device. Now while pressing the down volume key, press the power button to enter the hboot screen and pay attention to see whether or not you still have S-OFF. If you do not, you need to re-root. If you do, great. Reflash amon RA and afterwards, reboot into recovery and flash the rom.
Just Me, D
via the XDA Premium app
Think we have different problems. Every time I try to flash something new it completes fine, but it still boot loops. Hell, yours might be fixable.
I've tried everything now with no luck. Everything updates and completes but has absolutely no effect on the boot looping. This is really insane and my advice to anyone would be to stop using CM7 immediately as it seems to be confined to that ROM.
If anyone else has had this exact problem please post, I want to get a tally of how many people are affected and try to find a commonality.
Bootlooping is caused by incorrectly flashing, or flashing something that the phone "doesn't like," whether it be a kernel, a theme, ect.
teh roxxorz said:
Bootlooping is caused by incorrectly flashing, or flashing something that the phone "doesn't like," whether it be a kernel, a theme, ect.
Click to expand...
Click to collapse
But my phone ran for a month without any problems except for some random reboots which seem to be common with this phone in general. I didn't add software or flash anything before this happened, it just happened. That seems to be the experience most people are having, the only thing in common is that they were running CM7 or had been running it recently and tried to flash to a different rom.
What software problem wouldn't be corrected by a successfully completed reflash with a stock RUU? That's the major question.
Hmm, that is awkward; at that point, I would just take it in if you're still getting random reboots. Been on CM7 for the longest and no random reboots on my end.
teh roxxorz said:
Bootlooping is caused by incorrectly flashing, or flashing something that the phone "doesn't like," whether it be a kernel, a theme, ect.
Click to expand...
Click to collapse
EXACTLY! and thus the reason I wanted the OP to follow the directions I gave. Being that he or she would have had a completely fresh recovery, a freshly partitioned & formatted SD card and only the rom on the card to flash, barring a mechanical issue, the only possible explanation would be a corrupted rom zip file or a corrupted nandroid backup if that is what was being used. Corruption happens. The OP should re-download a fresh copy of the rom, re-wipe and re-flash, at least in my opinion....
dougjamal said:
EXACTLY! and thus the reason I wanted the OP to follow the directions I gave. Being that he or she would have had a completely fresh recovery, a freshly partitioned & formatted SD card and only the rom on the card to flash, barring a mechanical issue, the only possible explanation would be a corrupted rom zip file or a corrupted nandroid backup if that is what was being used. Corruption happens. The OP should re-download a fresh copy of the rom, re-wipe and re-flash, at least in my opinion....
Click to expand...
Click to collapse
I agree, that is exactly what they should.
dougjamal said:
EXACTLY! and thus the reason I wanted the OP to follow the directions I gave. Being that he or she would have had a completely fresh recovery, a freshly partitioned & formatted SD card and only the rom on the card to flash, barring a mechanical issue, the only possible explanation would be a corrupted rom zip file or a corrupted nandroid backup if that is what was being used. Corruption happens. The OP should re-download a fresh copy of the rom, re-wipe and re-flash, at least in my opinion....
Click to expand...
Click to collapse
I would love to, but I can't load any recovery. I've tried to flash amon ra and clockwork, and all seem to flash ok, but on reboot it's back to boot loop even if I try to go into recovery.
BrashL said:
I would love to, but I can't load any recovery. I've tried to flash amon ra and clockwork, and all seem to flash ok, but on reboot it's back to boot loop even if I try to go into recovery.
Click to expand...
Click to collapse
Try flashing amon_ra 2.3....place on sdcard, go into the bootloader, update,reboot, then try the bootloader. But before you do, select clear storage, which will do a factory reset, to see if that helps.
teh roxxorz said:
Try flashing amon_ra 2.3....place on sdcard, go into the bootloader, update,reboot, then try the bootloader. But before you do, select clear storage, which will do a factory reset, to see if that helps.
Click to expand...
Click to collapse
Already tried it, no dice. Goes through fine but then keeps bootlooping. On a side note, is there a way to get S-On through the bootloader since I can't access recovery?
You would have to download the RUU exe and then run the phone in fastboot while connected to the pc.
teh roxxorz said:
You would have to download the RUU exe and then run the phone in fastboot while connected to the pc.
Click to expand...
Click to collapse
Did that buy still S-Off
http://www.shipped-roms.com/shipped/Supersonic/ Did you run the right RUU for your software version?
And I'm heading tot he gym for ~1hr; you can pm me in the meantime and I'll answer when I get back if you still need assistance.
dougjamal said:
Once you've gotten back into recovery, specifically, amon RA 2.3, use the MS-USB menu and copy the contents of your SD card onto an external disk drive. Afterwards, use amon RA to partition and reformat your card. When you're done, copy only the Rom and amon RA (PC36IMG) file to your SD card. Shut down your device. Now while pressing the down volume key, press the power button to enter the hboot screen and pay attention to see whether or not you still have S-OFF. If you do not, you need to re-root. If you do, great. Reflash amon RA and afterwards, reboot into recovery and flash the rom.
Just Me, D
via the XDA Premium app
Click to expand...
Click to collapse
I'm sorry I wasn't clear . Days of reading every post in any thread I can find has left me running on no sleep. The huge problem is that no matter what recovery rom is flashed it wont let me boot into RECOVERY MODE. It flashes fine whether it is from the sd or through cmd using fastboot (Ive tried almost every version including the newest of both Amen RA and Clockwork). This gets me stuck in the white HTC screen boot loop. If I flash a RUU it will at least hang with a partition error and get stuck in the four triangle error, which will at least let you charge the battery so I can start all over again. Is there maybe a way to wipe the partition or reformat in fastboot as that is really the only thing working (regular adb wont detect). It seems a ton of people have been popping up with this same problem out of the blue the last few days.
I loaded a backup of CM7 and when it rebooted it went into a bootloop and I cant get into recovery. I've tried everything even flashing CWM again and also the stock ROM image. Still bootloop!
Please help
You didnt brick it, if you bricked it, it wouldnt start. You should still be able to get into recovery, by holding the power button and volume at the same time, and getting into Hboot, then go to recovery. Im also guessing it happened because you didnt whipe cache or data before you did this. First time i ever installed a new rom i got a bootloop,
Thank you for responding. I cant get into recovery it starts bootlooping once I select recovery. I tried loading the PB image of CWM and I also tried flashing the stock RUU. Cant get past HBOOT or initial bootloop. I CAN get into fastboot ADB though. Tried flashing a backup system.img, boot.img, data.img but boot.img said error
Your welcome, im not perfect at all this so excuse me a bit lol. So your saying when you select recovery, it boots up normally to the splash screen, or am i wrong? If your able to flash things them im pretty sure your able to get into recovery. Maybe also try another version of CM7? Transferring it to your phone.
No I select recovery in HBOOT and it goes straight to the white HTC INCREDIBLE screen and begins the bootloop process. I've pushed the CWM 3.0.0.8 in a pb13img file and still wont go into recovery. I cant get the phone past HBOOT
Thats really really weird that it wont go into recovery and it starts the boot. Hopefully someone can come with some extra assistance. It isnt bricked tho, i know that. So did you try formating data and cache then before doing anything either?
No I was busy and messed up. applied a backup without wiping data/cache. Came back to a powered off phone. Tried turning it on and it was bootlooping. I cant do anything now. Even if I can get S-ON i'll just get a replacement
There's a data wipe option in hboot, have you tried that?
Sent from my ADR6300 using XDA App
Goto Doug piston's web site and follow the go back to stock. You should be able to put the stock RUU on the root of your sd card named pb31img (not sure the exact file name but it is on dougs site). When you load in HBOOT, it should recognize the file and install. If I am not mistaken, this will unroot your phone as well.
http://dougpiston.com/?page_id=108
Pb31img file is there.
I tried the stock rom PB31IMG.zip and it continues to bootloop. If I cant get it fixed I want to at least get S-On
Probably aren't gonna be able to get S-ON cause that needs to be done in recovery..
Sent from my ADR6300 using XDA App
There is also the unrevoked forever s-on tool which you flash through recovery
Sent from my DROIDX using XDA App
Yeah cant get to recovery so I'm boned.
I got VZW to send me a replacement and also got Asurion to get my an Inc2. Not sure which to send back. Free replacement with a gamble getting caught S-On, or $99 free upgrade to Inc2
what radio were you running
try flashing alternate recovery?
i also seem to remember there being a way to root through adb isnt there a way to unroot like that too?
I tried amon ra and a another one no difference. I also tried everything I could adb wise to flash different systems and erase everything. Im running the new GB radio
I may be wrong but I don't think you can apply the RUU with that radio installed. Go back to the stock radio and I think you may be able to flash ythe RUU successfully.
Sent from my ADR6300 using XDA App
CSamson said:
I may be wrong but I don't think you can apply the RUU with that radio installed. Go back to the stock radio and I think you may be able to flash ythe RUU successfully.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
I got excited thinking there was a way to unbrick because of a step I missed. So I went to make sure the radio was right. I HAD the GB Leak 2.15.10.05.06
Right now in HBoot it shows 2.15.00.07.28
I know its not considered a brick because it still turns on but there is NOTHING I can do to get it out of bootloop or past HBoot
hmm new GB radio this has been happening with thunderbolt users to.....but in greater numbers.....I'd advise against using the GB leaked radio...
Your backup. Rec2.x. and now. 3.x?
Sent from my Optimized Inc using XDA App
Hello all. My girlfriends E4G(my old phone before I got me E3D) is having some issues.
Its hboot 6.17
TWRP 2.0
Any ROM I flash it gets stuck at the HTC EVO 4G logo. A few ROMs will boot once but once you reboot, it gets stuck at the HTC logo again. Her current ROM(Swag) is an older version, and shes wanting to "try something different" because she sees all the ROMs for my E3D.
When I had the phone, I didn't have any issues with flashing ROMs. I ran CM7 for a while, then Swag. This was MONTHS ago, so I'm not sure what changed since I switched to my E3D.
I've tried 7 different ROMs, I can't upgrade hboot or radios(the files I have downloaded here wont work with the PC36IMG. The boot loader sees it, then asks to reboot.)
What I want to do is completely return phone to stock, S-SON, install a stock Sprint software, run OTA to update everything(to the newest OTA), then re-S-OFF and figure out the best recovery to use.
I've tried following the S-On tool, but it didnt work for me. Maybe I'm missing something, but any help would be appreciated.
66 views and nobody can help?
Go here http://forum.xda-developers.com/showthread.php?t=1218386
Scroll down to the facts. Follow the "is it possible to restore everything to stock" to the letter. Download that file to the SD card somehow and load up your boot loader. It worked for me. Best of luck.
You can simply flash the newer version of the twrp 2 recovery, or flash amon ra; it seems your recovery isn't wiping.
teh roxxorz said:
You can simply flash the newer version of the twrp 2 recovery, or flash amon ra; it seems your recovery isn't wiping.
Click to expand...
Click to collapse
+1
There may be a possible bug in TWRP so just update your recovery. There is a newer version released revently. Try that first.
Sent from my DECK'ed out EVO
Well, I put it back to s-on, flashed latest ota, updated everything, redid s-off used amonra, tried to flash a rom and still had the same issue. I even wiped everything three times.
Sent from my PG86100 using Tapatalk
http://forum.xda-developers.com/showthread.php?t=1400645
Sent from my V6 Supercharged Evo.
Get rid of twrp 2.0 it's been bricking phones and for the time being has been discontinued by the devs
Sent from my iCS'd out EViL4G, soaking in a bowl of Ramen Noodles
still happens with amon ra recovery...
I'm having some major trouble with my Evo. I tried flashing from Classic v005 finale to v006 and I wiped everything 3 times. Now, I'm stuck in hboot and my recovery won't start. i have a PC36IMG file (TWRP 2) in my sdcard and says it updates but it really isn't. When I try to restart the phone, I get pushed back into fastboot. What can I do to fix my phone?
Twrp2 may have perm bricked your phone its done it to quite a few ppl hope you have ins cuz you'll need to flash a stock ruu thru hboot and send it in for replacement
ok. how do i push an ruu if i can't boot?
You'll have to put it on root of SD as a pc36img and boot to hboot/bootloader and run the update it should put your hboot back to a stock version so u can return it twrp2 had issues for several ppl and bricked their phones
Edit: does your hboot mysteriously say s-on now?
No, it doesn't. I might be screwed though because the only thing my computer sees when I plug in is the bootloader interface. Won't pick up the sdcard
try flashing a RUU for your phone and then Amon Ra recovery
Sounds like twrp2 borked it some ppl had s-on after but the not reading the phone on USB is a pretty sure sign twrp2 bricked it it was causing problems with bad blocks or something during the flash not sure what exactly it did to the phones but they were unrecoverable afterwards it screwed something up that wouldn't allow it to rewrite to the internal memory or be recognized by fastboot commands or adb
SprintLTE said:
ok. how do i push an ruu if i can't boot?
Click to expand...
Click to collapse
I've never used an RUU, but I believe it's an .exe file. I think you can run it from your PC while plugged into fastboot......from what I've seen posted over the years.
Until someone more knowledgeable gets back to you. Or if you have a SD card reader, do pc36img method, as was mentioned.
sent from xda app on drews ics
Try downloading shipped rom zip file. Load it on your root. Use a card reader if phone won't connect to PC. If it works you should still be s off. Just flash you custom rom back over it after you reflash a new recovery. I use amon.3.11.
See if that will work.
Shipped zip will over write recovery and should fix your problem.
ok I ran an ruu.exe so it's bootable now but I'm still getting random reboots and I can't mount my sdcard. any ideas?
It's broke. Call sprint they'll replace it with or without insurance. If your s-on running stock they won't know that you're rooted. Also sometimes stores will replace it as well. Be prepared to possibly get a upgrade for the phone.
Sent from my PC36100 using xda premium
SprintLTE said:
ok I ran an ruu.exe so it's bootable now but I'm still getting random reboots and I can't mount my sdcard. any ideas?
Click to expand...
Click to collapse
Did you flash a new recovery?
If so, wipe everything.
Try mounting via recovery.
Does it mount SD there?
You may try to partition your card again and see if that helps.
Did you already wipe and try custom rom again?
Isubbie said:
It's broke. Call sprint they'll replace it with or without insurance. If your s-on running stock they won't know that you're rooted. Also sometimes stores will replace it as well. Be prepared to possibly get a upgrade for the phone.
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
It will still be s off even after running ruu I think.
To get s on you will need to flash s on before you take it back.
I would try to partition SD or wipe and flash new rom after amon recovery.
When I run the Factory Resets in Amon RA, it skips over everything on the sd card, saying, "E:Can't mount /dev/block/mmcblk0p1". The phone seems fried to me. Luckily, I have the insurance. lol, "oops I dropped it in the sink"
That sux twrp2 was a pretty neat looking recovery I'm glad I read about it after I installed it and had several failed backup attempts cuz I don't have ins so luckily I didn't attempt to proceed with flashing anything or I'd be in the same boat as you up the same creek only I wouldn't have a paddle lol
When will people check the TWRP thread and realize its a bad product ? Great idea, bad product.
Edit: I mean even after installing twrp, when will they check back to see it's hosed, before they get hosed?. This isn't a comment about you, OP. Just meant, too bad there's not a way to let all users of it know to change recoveries IMMEDIATELY.
sent from xda app on drews ics
After the backup failed twice I figured something was wrong since I had already backed up the same setup in amon ra just fine
If you ran the RUU, then either your SD Card is bad, or you're back to stock, so just take it to Sprint