Hello all,
Quick background - my wife's T-Mobile S4 went kaput on our honeymoon last night, but I was at least able to save some of her data. The problem now goes to installing a new ROM on her device.
I have wiped EVERYTHING and formatted the data, but when I install ANY ROM (I've tried multiple), I always get the E: Unable to mount '/data" error. Normally, I would just ODIN the stock tar, then install a custom recovery again and then the ROM, but I only have my work computer for the rest of my honeymoon and I don't have administrative access to run ODIN (you might not think it requires it, but if you're only a standard user then you cannot bypass UAC to run it).
Does anyone have any ideas on how to get this to mount? The phone will not boot past the "Samsung Galaxy S4" screen. I've tried going into TWRP and mounting Data but it will not work.
Any help is greatly appreciated! Please keep in mind that I don't have access to ODIN!
- Taxmaster
Taxmaster said:
Hello all,
Quick background - my wife's T-Mobile S4 went kaput on our honeymoon last night, but I was at least able to save some of her data. The problem now goes to installing a new ROM on her device.
I have wiped EVERYTHING and formatted the data, but when I install ANY ROM (I've tried multiple), I always get the E: Unable to mount '/data" error. Normally, I would just ODIN the stock tar, then install a custom recovery again and then the ROM, but I only have my work computer for the rest of my honeymoon and I don't have administrative access to run ODIN (you might not think it requires it, but if you're only a standard user then you cannot bypass UAC to run it).
Does anyone have any ideas on how to get this to mount? The phone will not boot past the "Samsung Galaxy S4" screen. I've tried going into TWRP and mounting Data but it will not work.
Any help is greatly appreciated! Please keep in mind that I don't have access to ODIN!
- Taxmaster
Click to expand...
Click to collapse
Sounds like a twrp issue. Try grabbing the cwm flash able zip and adb push to the sd card and then use twrp to install it. I've read so many issues about twrp. I recommend staying away from it. Philz touch recovery is really awesome too.
Sent from my SGH-M919 using Tapatalk 2
elesbb said:
Sounds like a twrp issue. Try grabbing the cwm flash able zip and adb push to the sd card and then use twrp to install it. I've read so many issues about twrp. I recommend staying away from it. Philz touch recovery is really awesome too.
Sent from my SGH-M919 using Tapatalk 2
Click to expand...
Click to collapse
Hello! I actually downloaded Philz touch recovery in both .zip and in .md5, so that is what I intend to go with. The issue is how I push it using adb, as I believe I need to install something in order to do so, but I don't have any administrative privileges! This is what's preventing me from running ODIN in the first place!
Can you confirm that I can push using adb without installing anything?
Thank you! - Taxmaster
I had this issue. Odin flashing and then booting into "STOCK RECOVERY" after flashing and then a factory reset in the stock recovery followed by a fresh re-flash from Odin worked to get my phone back up and running again.
I don't know how you are going to be able to fix it by just flashing a recovery. I tried for hours and could not get it to boot from just recovery alone.
Monkz said:
I had this issue. Odin flashing and then booting into "STOCK RECOVERY" after flashing and then a factory reset in the stock recovery followed by a fresh re-flash from Odin worked to get my phone back up and running again.
I don't know how you are going to be able to fix it by just flashing a recovery. I tried for hours and could not get it to boot from just recovery alone.
Click to expand...
Click to collapse
What you noted would be my plan if I had admin rights to my computer, but since I cannot get ODIN, I'm screwed at the moment. I'm hoping someone can assist with the "adb" proposal, however I'm not sure one can download/run adb without installation or prompt from UAC
Taxmaster said:
What you noted would be my plan if I had admin rights to my computer, but since I cannot get ODIN, I'm screwed at the moment. I'm hoping someone can assist with the "adb" proposal, however I'm not sure one can download/run adb without installation or prompt from UAC
Click to expand...
Click to collapse
I don't believe admin is required for adb... You could always try it... worst thing that could happen would be nothing.
lordcheeto03 said:
I don't believe admin is required for adb... You could always try it... worst thing that could happen would be nothing.
Click to expand...
Click to collapse
Using ADB does not require admin privelages, however, if your computer does not have the necessary drivers to detect the device in recovery, then you will have to install the drivers, which then yes UAC is required. HOWEVER, if you have another phone or device that supports MicroSD cards, you can just pop in the MicroSD into a working device and transfer the zip that way, then transfer back the sd card and flash
elesbb said:
Using ADB does not require admin privelages, however, if your computer does not have the necessary drivers to detect the device in recovery, then you will have to install the drivers, which then yes UAC is required. HOWEVER, if you have another phone or device that supports MicroSD cards, you can just pop in the MicroSD into a working device and transfer the zip that way, then transfer back the sd card and flash
Click to expand...
Click to collapse
I did exactly what's noted above --> took out the SDcard, put it in another phone, transferred over the .zip, put it back in her phone, went to TWRP, wiped everything on the device, installed the .zip, and rebooted into recovery from TWRP, and then the new recovery booted! I did another wipe/factory reset and then installed a ROM, but when I hit reboot, it didn't reboot past the Samsung Galaxy S4 splash screen , and to make matters worse, when I go to enter recovery pressing home+up+power, it says "Recovery Booting ...." in the top left corner but it won't boot into recovery!!!
Thoughts?
If someone could strip administrative privileges off of a version of ODIN v3 for me, that would be great! I don't see how else to get around this now!
-Taxmaster
Taxmaster said:
I did exactly what's noted above --> took out the SDcard, put it in another phone, transferred over the .zip, put it back in her phone, went to TWRP, wiped everything on the device, installed the .zip, and rebooted into recovery from TWRP, and then the new recovery booted! I did another wipe/factory reset and then installed a ROM, but when I hit reboot, it didn't reboot past the Samsung Galaxy S4 splash screen , and to make matters worse, when I go to enter recovery pressing home+up+power, it says "Recovery Booting ...." in the top left corner but it won't boot into recovery!!!
Thoughts?
If someone could strip administrative privileges off of a version of ODIN v3 for me, that would be great! I don't see how else to get around this now!
-Taxmaster
Click to expand...
Click to collapse
Out of curiosity, are you flashing a ROM for the T-Mobile S4? If no, are you using a T-Mobile kernel? I only ask because a kernel for a different device will normally cause you to not be able to pass the initial Galaxy S4 screen... Also, as far as TWRP goes, sometimes it doesn't go right into recovery. If it fails to enter recovery after a reasonable amount of time, just hold power to turn it off and try again. I've had to do it 2-3 times at least just to successfully enter TWRP.
lordcheeto03 said:
Out of curiosity, are you flashing a ROM for the T-Mobile S4? If no, are you using a T-Mobile kernel? I only ask because a kernel for a different device will normally cause you to not be able to pass the initial Galaxy S4 screen... Also, as far as TWRP goes, sometimes it doesn't go right into recovery. If it fails to enter recovery after a reasonable amount of time, just hold power to turn it off and try again. I've had to do it 2-3 times at least just to successfully enter TWRP.
Click to expand...
Click to collapse
I am installing a T-Mobile S4 ROM that uses a custom kernel. The ROM before was the same ROM just a lower revision, same kernel.
With respect to TWRP, I thought it was all gone now that I installed the CWM touch version. I've tried doing it a million times and cannot get back into either TWRP or CWM. At this point, the only thing I can do is turn on the device to see the "Samsung Galaxy S4" screen, attempt booting into recovery but never make it past the screen saying "Recovery Booting", or enter Download Mode but I cannot use it since I can't run ODIN on my work laptop .... stupid admin privileges!
Taxmaster said:
I am installing a T-Mobile S4 ROM that uses a custom kernel. The ROM before was the same ROM just a lower revision, same kernel.
With respect to TWRP, I thought it was all gone now that I installed the CWM touch version. I've tried doing it a million times and cannot get back into either TWRP or CWM. At this point, the only thing I can do is turn on the device to see the "Samsung Galaxy S4" screen, attempt booting into recovery but never make it past the screen saying "Recovery Booting", or enter Download Mode but I cannot use it since I can't run ODIN on my work laptop .... stupid admin privileges!
Click to expand...
Click to collapse
Not sure what happened there.. very strange. But seems as if you have no recovery xD lol Maybe heimdall will work. Never used it not sure if it needs UAC to work. But dont use TWRP anymore
As far as your situation goes, maybe if you have the time and fast enough internet, see if you can download a linux distro (i recommend fedora as it is small and light) then make a bootable USB from that distro (if you have a flash drive) then use Heimdall in linux to flash the tar image.
Or just wait to get home. not sure how long your honeymoon is xD
elesbb said:
Not sure what happened there.. very strange. But seems as if you have no recovery xD lol Maybe heimdall will work. Never used it not sure if it needs UAC to work. But dont use TWRP anymore
As far as your situation goes, maybe if you have the time and fast enough internet, see if you can download a linux distro (i recommend fedora as it is small and light) then make a bootable USB from that distro (if you have a flash drive) then use Heimdall in linux to flash the tar image.
Or just wait to get home. not sure how long your honeymoon is xD
Click to expand...
Click to collapse
I think I just need to accept that fact that I have been had and that the only thing I can do is wait until I'm home to use ODIN. Absolutely asinine in my opinion, however it seems the only logical conclusion at this point.
If anyone else cares to chime in with suggestions, please let me know!
-Taxmaster
I have had the same problem several times. The only way I have been able to boot up is to completely format data and either restore from backup or reflash a new ROM. If I wipe the dalvik cache after doing so however, it will not boot (hangs at the galaxy s4 screen like you said) and I will have to reflash or restore a 2nd time. (I'm using twrp too, but will switch to cwm if this happens again)
I m curious. Have you run into this problem again? Seems like every time my phone shuts off and tries to boot I have to restore from a backup that is days or weeks old. Super annoying. The first time this happened I restored to stock from Odin and did not use any backups in the hope that it would solve my problem and prevent it from happening again. No such luck.
coolastar said:
I have had the same problem several times. The only way I have been able to boot up is to completely format data and either restore from backup or reflash a new ROM. If I wipe the dalvik cache after doing so however, it will not boot (hangs at the galaxy s4 screen like you said) and I will have to reflash or restore a 2nd time. (I'm using twrp too, but will switch to cwm if this happens again)
I m curious. Have you run into this problem again? Seems like every time my phone shuts off and tries to boot I have to restore from a backup that is days or weeks old. Super annoying. The first time this happened I restored to stock from Odin and did not use any backups in the hope that it would solve my problem and prevent it from happening again. No such luck.
Click to expand...
Click to collapse
I ended up having to wait until I got home to use ODIN. I ODIN'd up the stock .tar and then installed Philz touch recovery (CWM-based), then I did a full wipe of everything and installed a ROM. Problem solved.
With that noted, I abandoned TWRP and am now only using CWM on my wife's phone.
Taxmaster said:
I ended up having to wait until I got home to use ODIN. I ODIN'd up the stock .tar and then installed Philz touch recovery (CWM-based), then I did a full wipe of everything and installed a ROM. Problem solved.
With that noted, I abandoned TWRP and am now only using CWM on my wife's phone.
Click to expand...
Click to collapse
Same, TWRP just has too many problems.
CWM is much more reliable.
Sent from my SGH-M919 using xda premium
Taxmaster said:
I ended up having to wait until I got home to use ODIN. I ODIN'd up the stock .tar and then installed Philz touch recovery (CWM-based), then I did a full wipe of everything and installed a ROM. Problem solved.
With that noted, I abandoned TWRP and am now only using CWM on my wife's phone.
Click to expand...
Click to collapse
If you were using TWRP 2.6.0, that could have been the problem. I reverted back to 2.5.0.2 and like many others, have had no issues. If you had a TWRP backup, that might have fixed it early on.
Related
Galaxy S3 from at&t, i rooted my phone as soon as got it several months ago, I've flashed colockwordmode 3 times in the last day or so and i cannot make to work, i followed the steps exactly as described, Odin is showing the green pass, the binary cont is increasing every time I've tried but i can't get the phone to start in recovery mode by holding volume up, home and power! it just reboot and turns the phone on or it goes into the Samsung recovery mode (blue screen). Very frustrating!, anyone can please help.
BTW, when i rooted my phone i installed clockwordmode then and it worked fine, i had not has to use it since, I'm running the stock ROM i want to flash another ROM, before i do that i need to use clockworkmode and that's when i realized that it was not working anymore, then tried to flash it 3 times but no success. I still have root.
Have you tried twrp?
athens71 said:
Galaxy S3 from at&t, i rooted my phone as soon as got it several months ago, I've flashed colockwordmode 3 times in the last day or so and i cannot make to work, i followed the steps exactly as described, Odin is showing the green pass, the binary cont is increasing every time I've tried but i can't get the phone to start in recovery mode by holding volume up, home and power! it just reboot and turns the phone on or it goes into the Samsung recovery mode (blue screen). Very frustrating!, anyone can please help.
BTW, when i rooted my phone i installed clockwordmode then and it worked fine, i had not has to use it since, I'm running the stock ROM i want to flash another ROM, before i do that i need to use clockworkmode and that's when i realized that it was not working anymore, then tried to flash it 3 times but no success. I still have root.
Click to expand...
Click to collapse
This will happen until you load a custom rom I believe. Same thing happened to me then when I installed a rom it started being able to boot into cwm
Sent from my SGH-I747 using xda premium
athens71 said:
Galaxy S3 from at&t, i rooted my phone as soon as got it several months ago, I've flashed colockwordmode 3 times in the last day or so and i cannot make to work, i followed the steps exactly as described, Odin is showing the green pass, the binary cont is increasing every time I've tried but i can't get the phone to start in recovery mode by holding volume up, home and power! it just reboot and turns the phone on or it goes into the Samsung recovery mode (blue screen). Very frustrating!, anyone can please help.
BTW, when i rooted my phone i installed clockwordmode then and it worked fine, i had not has to use it since, I'm running the stock ROM i want to flash another ROM, before i do that i need to use clockworkmode and that's when i realized that it was not working anymore, then tried to flash it 3 times but no success. I still have root.
Click to expand...
Click to collapse
flash recovery again in odin but make sure the "auto reboot" box is NOT checked. once its done flashing, unplug it and remove the battery for a second. replace the battery and immediately hold down vol up+home+power. this should take you into cwm if it flashed correctly
this could happen when you didn't root it properly
anyways, if you are rooted(as you said), get twrp and see
+1 for twrp
athens71 said:
I still have root.
Click to expand...
Click to collapse
If you still have root, you might want to try installing CWM directly from your phone, using the dd terminal command to copy CWM into the right partition:
Download the latest CWM .img file from CWM's site: http://www.clockworkmod.com/rommanager
Put the file in your phone. For simplicity reason, I would suggest you put it in the root of your internal SD card. And because you will need to type the whole path+filename in the terminal in your phone, I would also suggest you rename the file to something simple, like cwm.img;
If you don't already have it, install Android Terminal Emulator;
Now, open the terminal emulator, and type the following commands:
Code:
su
dd if=/sdcard/cwm.img of=/dev/block/mmcblk0p18
(That is, if you rename the CWM file to "cwm.img" and you actually put it in the root of your internal SD card. If you put it somewhere else or did not rename your file, you will need to adapt the "if=" part of the command.)
Profit.
athens71 said:
Galaxy S3 from at&t, i rooted my phone as soon as got it several months ago, I've flashed colockwordmode 3 times in the last day or so and i cannot make to work, i followed the steps exactly as described, Odin is showing the green pass, the binary cont is increasing every time I've tried but i can't get the phone to start in recovery mode by holding volume up, home and power! it just reboot and turns the phone on or it goes into the Samsung recovery mode (blue screen). Very frustrating!, anyone can please help.
BTW, when i rooted my phone i installed clockwordmode then and it worked fine, i had not has to use it since, I'm running the stock ROM i want to flash another ROM, before i do that i need to use clockworkmode and that's when i realized that it was not working anymore, then tried to flash it 3 times but no success. I still have root.
Click to expand...
Click to collapse
Just curious: are you trying to flash CWM via Odin? If so where did you get it from? Did you install a botched version of stock recovery maybe (or one that is from another model of S3)? Try TWRP from here http://forum.xda-developers.com/showpost.php?p=28019751&postcount=1. It is at the bottom of the post and it is labeled "Odin Flashable TWRP Recovery" under Miscellaneous files. Download and install via Odin.
And if you are on Jelly Bean, your flash counter will increment in your dealings with custom recoveries and roms. You only option at this point (if you have root still) is to get Triangle Away and run it in order to reset the counter. However, even if you clear your flash counter, if you go back into recovery it will trip again.
drock212 said:
This will happen until you load a custom rom I believe. Same thing happened to me then when I installed a rom it started being able to boot into cwm
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
I'm still using stock ROM, i'd like to install a custom ROM but i'm reading that you have to have Clockworkmod to do a successful install.
When i check in the files of the phone (sd card) i can see the clockwordmod folder in there there but still can't get it to boot into cwm recovery, only the Samsung recovery and I've tried the volume up home and power button so many times but no success.
Why do you think it worked when i first rooted the phone and not now?
this is frustrating, thanks for the help.
aybarrap1 said:
Just curious: are you trying to flash CWM via Odin? If so where did you get it from? Did you install a botched version of stock recovery maybe (or one that is from another model of S3)? Try TWRP from here http://forum.xda-developers.com/showpost.php?p=28019751&postcount=1. It is at the bottom of the post and it is labeled "Odin Flashable TWRP Recovery" under Miscellaneous files. Download and install via Odin.
And if you are on Jelly Bean, your flash counter will increment in your dealings with custom recoveries and roms. You only option at this point (if you have root still) is to get Triangle Away and run it in order to reset the counter. However, even if you clear your flash counter, if you go back into recovery it will trip again.
Click to expand...
Click to collapse
Yes I've tried 3 times via Odin, i can't remember where i got the cmw file from, it's a tar file (clockworkmod.TAR), the part i don't understand is why when i first rooted the phone in August cwm worked, i used it to install the root and now after trying to install it again 3 times i can't get it to work.
I'm using the stock ROM, not jelly bean.
thanks for any help
xBeerdroiDx said:
flash recovery again in odin but make sure the "auto reboot" box is NOT checked. once its done flashing, unplug it and remove the battery for a second. replace the battery and immediately hold down vol up+home+power. this should take you into cwm if it flashed correctly
Click to expand...
Click to collapse
I've tried it with "auto reboot" check and without but still no luck. Like i said it reboots in the Samsung rm.
androidsavage23 said:
Have you tried twrp?
Click to expand...
Click to collapse
No i have not, i can't find where to get it for galaxy S3 at&t! would you know where i could find it?
Thank you
athens71 said:
No i have not, i can't find where to get it for galaxy S3 at&t! would you know where i could find it?
Thank you
Click to expand...
Click to collapse
Download goo manager app and open that. There will be an option to "install open recovery" in the menu. Voilà a superior recovery that's easier to use
You can even use it to boot into recovery or install the new update for it.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
athens71 said:
No i have not, i can't find where to get it for galaxy S3 at&t! would you know where i could find it?
Click to expand...
Click to collapse
Easiest way to install TWRP is using GooManager from the Play Store.
1. Open GooManager.
2. Press the menu key to open the contextual menu, and select Install OpenRecoveryScript.
3. The app will ask you to confirm you really want to install a new recovery image.
4. GooManager searches for the correct TWRP build for your device. Look at the Filename line, it should display openrecovery-twrp-2.4.1.0-d2att.img for AT&T or openrecovery-twrp-2.4.1.0-d2can.img for Rogers/Bell/Telus. Again, confirm the installation.
5. Wait for the download to begin. TWRP will install. Done.
If it does not work or if GooManager does not find the correct build for your device -- in this latter case, this should raise a flag for you, as you may not have a SGH-i747/SGH-i747M; double check your phone model --, you can always install TWRP manually. From TWRP website (http://www.teamw.in/project/twrp2), you can grab the IMG file to manually install from the terminal emulator, and a TAR file to install using ODIN.
athens71 said:
I've tried it with "auto reboot" check and without but still no luck. Like i said it reboots in the Samsung rm.
Click to expand...
Click to collapse
Did you try it exactly as i said to?
drock212 said:
This will happen until you load a custom rom I believe. Same thing happened to me then when I installed a rom it started being able to boot into cwm
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
So if that's the case (This will happen until you load a custom ROM) how can i back up my stuff before installing a new ROM? that's the reason i was trying to make cwm work so i could back my stuff.
Is there a different way to do a full back up?
thanks
xBeerdroiDx said:
Did you try it exactly as i said to?
Click to expand...
Click to collapse
Yes i did, when i tried to flash cmw 3 times yesterday, the description was exactly like yours.
thanks you
athens71 said:
Yes i did, when i tried to flash cmw 3 times yesterday, the description was exactly like yours.
thanks you
Click to expand...
Click to collapse
if you have root, download Rom Manager and install cwm from the menu.
i've also heard that, if rooted, you can erase /system/recovery-from-boot.p and /system/etc/install-recovery.sh (using ES File Explorer or Root Explorer) an that will make cwmstick. this is due to newer software versions overwriting your stock recovery on reboot.
xBeerdroiDx said:
if you have root, download Rom Manager and install cwm from the menu.
i've also heard that, if rooted, you can erase /system/recovery-from-boot.p and /system/etc/install-recovery.sh (using ES File Explorer or Root Explorer) an that will make cwmstick. this is due to newer software versions overwriting your stock recovery on reboot.
Click to expand...
Click to collapse
By installing cwm from the app store (ROM manger) will i get the same back up as i would with Odin install of cwm, in other words do i risk loosing my back up ROM using "ROM manager?"
thanks
athens71 said:
By installing cwm from the app store (ROM manger) will i get the same back up as i would with Odin install of cwm, in other words do i risk loosing my back up ROM using "ROM manager?"
thanks
Click to expand...
Click to collapse
you've created a backup already? if not, install cwm from ROM Manager, boot into cwm recovery and make your nandroid there. then you'll be all set to to try a new ROM
I have a rooted Galaxy S3 that is running the ATT Jelly Bean update.
Last night, while looking at ROM manager I got a popup saying there is a newer version of CWM and did I want to install it.
After installing it, the phone will only boot into recovery. I cannot get it to start. And when I tried to restore from a backup that I have used successfully before, I got an error while restoring data.
At this point, I am thinking that I might have bricked this phone. Searching on the ATT Galaxy S3 forum hasn't turned up anything relevant.
Does anyone have an idea what I can try next?
Thanks
northstar7 said:
I have a rooted Galaxy S3 that is running the ATT Jelly Bean update.
Last night, while looking at ROM manager I got a popup saying there is a newer version of CWM and did I want to install it.
After installing it, the phone will only boot into recovery. I cannot get it to start. And when I tried to restore from a backup that I have used successfully before, I got an error while restoring data.
At this point, I am thinking that I might have bricked this phone. Searching on the ATT Galaxy S3 forum hasn't turned up anything relevant.
Does anyone have an idea what I can try next?
Thanks
Click to expand...
Click to collapse
If you a can boot into recovery than you aren't bricked.
You can do a factory reset that might clear it up.
Worst case go into download mode and use Odin to reinstall the stock ROM.
Sent from my SGH-I747 using xda app-developers app
northstar7 said:
I have a rooted Galaxy S3 that is running the ATT Jelly Bean update.
Last night, while looking at ROM manager I got a popup saying there is a newer version of CWM and did I want to install it.
After installing it, the phone will only boot into recovery. I cannot get it to start. And when I tried to restore from a backup that I have used successfully before, I got an error while restoring data.
At this point, I am thinking that I might have bricked this phone. Searching on the ATT Galaxy S3 forum hasn't turned up anything relevant.
Does anyone have an idea what I can try next?
Thanks
Click to expand...
Click to collapse
Im assuming you powered down, did a battery pull and powered back up? Factory reset?
What error message is displayed when trying to restore a backup?
The latest cwm release is 6.0.2.8. If you came from 6.0.2.3, I would download a cwm flashable zip of that recovery and flash that. Perhaps try a reboot then. If it's still a no-go, try restoring a backup with the cwm you had just downloaded and flashed to see if it will restore without an error message
Different CWM
xBeerdroiDx said:
Im assuming you powered down, did a battery pull and powered back up? Factory reset?
What error message is displayed when trying to restore a backup?
The latest cwm release is 6.0.2.8. If you came from 6.0.2.3, I would download a cwm flashable zip of that recovery and flash that. Perhaps try a reboot then. If it's still a no-go, try restoring a backup with the cwm you had just downloaded and flashed to see if it will restore without an error message
Click to expand...
Click to collapse
Thanks very much for the advice.
For the record, my phone is displaying "ClockworkMod Recovery v6.0.2.9"
I just has this happen to me as well. I just put the s3 in download mode and used Odin to re flash cwm. I'm using the same version cwm.
Sent from my SAMSUNG-SGH-I747 using xda premium
I as well. Tried everything and no go. Will try ODIN and see if it works.
Domoo said:
I just has this happen to me as well. I just put the s3 in download mode and used Odin to re flash cwm. I'm using the same version cwm.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
stranglely pressing the recovery button combo fixed it and im back in CM10.1 #lolwut?
In the end I got the phone working again
For whatever reason, after getting that update to ClockworkMod, the phone would not boot.
I followed the Beginners' Guide to Rooting the Galaxy S3 forum. When I was finished I immediately got an OTA update from ATT.
So now the phone is running again, but I've lost most of my customization and personal data.
What is with this CWM "upgrade?" Or is the problem with ROM Manager?
More likely is that I did something wrong.
At least I can make calls now.
Same here, stay away from that update! Bad things!
This also happened to me. Cwm is showing up as .9 instead of .8. I flashed a previous version of twrp and it still proceeded to go into recovery mode after selecting reboot. I did a factory reset and re flashed aokp and also cm10.1 (along with gapps of course) and it still did it. So I pulled the battery and put it into download mode and reset it from there. That's the only way to get the phone to boot up. From what I see here, is the basic fix for this problem flashing an older cwm in Odin?
Having the same issue, version .9 No amount of clearing data/wipe/reflash/restore will do anything for me either. So much for a lunchtime AOKP update...
I've looked in several different forums on xda and the general fix seems to be flashing a previous version of cwm. No need to reset your phone and flash roms all day long.
Download prior cwm release (.tar)
pull battery and replace
boot to download mode
connect to pc and flash cwm
Disconnect, pull battery, reboot
Here's the 6.0.2.3 release. You can grab the .8 in the Android dev section if you wish
https://www.dropbox.com/s/sfkjtndn7k0urmh/recovery-clockwork-6.0.2.3-d2att.tar
Let me know if this does not work. If your device is not recognized by your pc, you can try flashing this cwm zip in recovery itself (if you have a micro sd card):
http://d-h.st/8qP
I flashed with the same version of cwm I had previously before this issue (6.0.28). It seems to be an issue with 6.0.29 if so many people have this same issue.
Sent from my SAMSUNG-SGH-I747 using xda premium
xBeerdroiDx said:
I've looked in several different forums on xda and the general fix seems to be flashing a previous version of cwm. No need to reset your phone and flash roms all day long.
Download prior cwm release (.tar)
pull battery and replace
boot to download mode
connect to pc and flash cwm
Disconnect, pull battery, reboot
Here's the 6.0.2.3 release. You can grab the .8 in the Android dev section if you wish
https://www.dropbox.com/s/sfkjtndn7k0urmh/recovery-clockwork-6.0.2.3-d2att.tar
Let me know if this does not work. If your device is not recognized by your pc, you can try flashing this cwm zip in recovery itself (if you have a micro sd card):
http://d-h.st/8qP
Click to expand...
Click to collapse
I flashed the CMW-recovery_ATT-6.0.2.3_zip directly from the external sd card to the phone and the phone is now working. but I did have to reboot phone twice. the first time it stayed in recovery.
THANK YOU!!
xBeerdroiDx said:
I've looked in several different forums on xda and the general fix seems to be flashing a previous version of cwm. No need to reset your phone and flash roms all day long.
Download prior cwm release (.tar)
pull battery and replace
boot to download mode
connect to pc and flash cwm
Disconnect, pull battery, reboot
Here's the 6.0.2.3 release. You can grab the .8 in the Android dev section if you wish
https://www.dropbox.com/s/sfkjtndn7k0urmh/recovery-clockwork-6.0.2.3-d2att.tar
Let me know if this does not work. If your device is not recognized by your pc, you can try flashing this cwm zip in recovery itself (if you have a micro sd card):
http://d-h.st/8qP
Click to expand...
Click to collapse
I believe this can even be simplified a bit more. At least for me, some people may find Odin to be the simple way to do things. So you're stuck at recovery:
Hold the power button for 10 seconds to power off.
Boot to download mode by holding volume down and home. The phone will probably start to boot right away after releasing the power button. If it doesn't go to download, then your timing is off, try again.
Hold the power button for 10 seconds to power off and reboot.
It should boot regularly now.
Flash a new recovery. You can download CWM 6.0.2.8 or use this as an opportunity to move to TWRP. Once you have the img file on your phone, go to a terminal and (after su, if needed) run dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18 (replace "/sdcard/recovery.img" with the path and name of the img file you downloaded. You can also flash the recovery using whatever other on-phone method you prefer.
The CWM download page is now showing that 6.0.2.8 is the newest version for many of the S3 variants, so they've certainly noticed the bug.
J M L said:
I believe this can even be simplified a bit more. At least for me, some people may find Odin to be the simple way to do things. So you're stuck at recovery:
Hold the power button for 10 seconds to power off.
Boot to download mode by holding volume down and home. The phone will probably start to boot right away after releasing the power button. If it doesn't go to download, then your timing is off, try again.
Hold the power button for 10 seconds to power off and reboot.
It should boot regularly now.
Flash a new recovery. You can download CWM 6.0.2.8 or use this as an opportunity to move to TWRP. Once you have the img file on your phone, go to a terminal and (after su, if needed) run dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18 (replace "/sdcard/recovery.img" with the path and name of the img file you downloaded. You can also flash the recovery using whatever other on-phone method you prefer.
The CWM download page is now showing that 6.0.2.8 is the newest version for many of the S3 variants, so they've certainly noticed the bug.
Click to expand...
Click to collapse
How is this simpler? There are left out bits and errors all through your instructions. My steps were for odin so I'm not sure why you thought they were not.
First, never use GooManager to flash TWRP, to soft brick your phone is very likely, if soft bricked your phone, you need to use odin to flash TWRP.
Second, don't use TWRP 2.6.3.0 on our T989/T989D, I have found the following problems:
1: in recovery mode - after advanced wipe is done, the "return" button (right bottom corner) it's not sensitive, you need to press a few times to get back to previous screen
2: after flash new ROM, it usually takes at least 30 seconds to reboot the device, you may think your device is powered off, but it is not, just take too long.
3: No usb mount button in mount screen, not sure why, so you cannot mount your phone in recovery mode, you have to use adb to push file.
4: after you flash the ROM successfully, the newly flashed ROM may enter "bootloop" mode, it happened to me many times, same ROM, I have to flash at least 4-5 times to by pass the bootloop.
5: if you are lucky, and your newly flashed ROM booted, you may experience various problems, e.g. reboot, hangs, lag.... etc. Happened to me.
So, you better stick with TWRP 2.6.1.0, however 2.6.1.0 is prefect, it cannot wipe /preload, but at least, it doesn't have the above problems.
brisk5181 said:
First, never use GooManager to flash TWRP, to soft brick your phone is very likely, if soft bricked your phone, you need to use odin to flash TWRP.
Second, don't use TWRP 2.6.3.0 on our T989/T989D, I have found the following problems:
1: in recovery mode - after advanced wipe is done, the "return" button (right bottom corner) it's not sensitive, you need to press a few times to get back to previous screen
2: after flash new ROM, it usually takes at least 30 seconds to reboot the device, you may think your device is powered off, but it is not, just take too long.
3: No usb mount button in mount screen, not sure why, so you cannot mount your phone in recovery mode, you have to use adb to push file.
4: after you flash the ROM successfully, the newly flashed ROM may enter "bootloop" mode, it happened to me many times, same ROM, I have to flash at least 4-5 times to by pass the bootloop.
5: if you are lucky, and your newly flashed ROM booted, you may experience various problems, e.g. reboot, hangs, lag.... etc. Happened to me.
So, you better stick with TWRP 2.6.1.0, however 2.6.1.0 is prefect, it cannot wipe /preload, but at least, it doesn't have the above problems.
Click to expand...
Click to collapse
You can wipe preload in 2.6.1.0 by going to settings and ticking use rm -rf instead of formatting.
The no USB mount is the worst problem for me. I wonder if @Dees_Troy can shed some light on that.
I wonder if there are such issues then why there are more than 1800 hits on 2.6.3? And also if it has issue then why TWRP released it without properly checking it? Im oberserving TWRP is doing this from a long time and infact i have to search on internet to check if latest version is perfect or not
brisk5181 said:
First, never use GooManager to flash TWRP, to soft brick your phone is very likely, if soft bricked your phone, you need to use odin to flash TWRP.
Second, don't use TWRP 2.6.3.0 on our T989/T989D, I have found the following problems:
1: in recovery mode - after advanced wipe is done, the "return" button (right bottom corner) it's not sensitive, you need to press a few times to get back to previous screen
2: after flash new ROM, it usually takes at least 30 seconds to reboot the device, you may think your device is powered off, but it is not, just take too long.
3: No usb mount button in mount screen, not sure why, so you cannot mount your phone in recovery mode, you have to use adb to push file.
4: after you flash the ROM successfully, the newly flashed ROM may enter "bootloop" mode, it happened to me many times, same ROM, I have to flash at least 4-5 times to by pass the bootloop.
5: if you are lucky, and your newly flashed ROM booted, you may experience various problems, e.g. reboot, hangs, lag.... etc. Happened to me.
So, you better stick with TWRP 2.6.1.0, however 2.6.1.0 is prefect, it cannot wipe /preload, but at least, it doesn't have the above problems.
Click to expand...
Click to collapse
When you re-flashed several times for the new ROM, did you do a wipe everytime? or did you just re install??
HQuser said:
I wonder if there are such issues then why there are more than 1800 hits on 2.6.3? And also if it has issue then why TWRP released it without properly checking it? Im oberserving TWRP is doing this from a long time and infact i have to search on internet to check if latest version is perfect or not
Click to expand...
Click to collapse
There's plenty of documented issues with it....maybe for some devices its fine, but not all devices seem to be created equal.
Why is twrp doing nothing about it....probably because our aging device is under their radar, or they just aren't concerned with a few people with issues. Again....it may be flawless on every other device, so they aren't concerned with our old phone.
That's my guess.
Battery problems? No matter the rom or android version.... >>>> http://forum.xda-developers.com/showthread.php?t=2461864
I have had these same problems, but thy only started when I flashed 4.3. That is slim bean and paranoid android. It will boot after the flash, bit any attempt to reboot after that is met with a boot loop.
Thing is, I don't remember which version of TWRP I am using, and I would like to avoid rebooting since I don't want to reflash just yet. Is there a way to check on the version without a reboot? I know a reflash is inevitable if I want to install another version of TWRP.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Johndoe9990 said:
I have had these same problems, but thy only started when I flashed 4.3. That is slim bean and paranoid android. It will boot after the flash, bit any attempt to reboot after that is met with a boot loop.
Thing is, I don't remember which version of TWRP I am using, and I would like to avoid rebooting since I don't want to reflash just yet. Is there a way to check on the version without a reboot? I know a reflash is inevitable if I want to install another version of TWRP.
Click to expand...
Click to collapse
I can confirm that TWRP 2.6.1.0 causes no bootloop after flashing a ROM.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Where do I find a ODIN flashable file of the 2.6.1.0? I'm new to the Samsung side of things. I have looked all over and all I find at Goo and TWRP sites as .img and .tar files. I know .img files have to use dd to use now is the .tar files can be used with Odin? If so please let me know don't want to brick my new / used S2.
michaelcrossland said:
Where do I find a ODIN flashable file of the 2.6.1.0? I'm new to the Samsung side of things. I have looked all over and all I find at Goo and TWRP sites as .img and .tar files. I know .img files have to use dd to use now is the .tar files can be used with Odin? If so please let me know don't want to brick my new / used S2.
Click to expand...
Click to collapse
Yes, the tar files are for Odin.
I got a replacement GS3 through insurance and rooted it yesterday. Instead of flashing CWM I tried going with TWRP this time but didn't realize that TWRP doesn't read external SD cards and my roms were all saved on the external SD. And of course, this was after I wiped everything. So I tried unrooting and flashing back the stock firmware but it keeps failing in ODIN. So I tried re-rooting and flashing CWM which works but none of the roms will flash. I keep getting a system 7 error or something to that effect when I try flashing any rom. So now I can either get to recovery mode, or download mode. If I power the phone on it gets stuck on the Galaxy S3 screen. Any thoughts as to processes to try? Links? Threads? I've tried just about everything I could find.
kinjo1023 said:
I got a replacement GS3 through insurance and rooted it yesterday. Instead of flashing CWM I tried going with TWRP this time but didn't realize that TWRP doesn't read external SD cards and my roms were all saved on the external SD. And of course, this was after I wiped everything. So I tried unrooting and flashing back the stock firmware but it keeps failing in ODIN. So I tried re-rooting and flashing CWM which works but none of the roms will flash. I keep getting a system 7 error or something to that effect when I try flashing any rom. So now I can either get to recovery mode, or download mode. If I power the phone on it gets stuck on the Galaxy S3 screen. Any thoughts as to processes to try? Links? Threads? I've tried just about everything I could find.
Click to expand...
Click to collapse
Since when does TWRP not read external SD cards? It see's mine just fine, for well over a year. Where is your nandroid backup, you know the one you made before you did anything just incase it didn't go as planned? In any case you didn't give much information to help troubleshoot. 'I tried unrooting' - if you were going to flash a stock ROM there is no need to unroot anything as the stock firmware is just that, stock. How did it fail in ODIN? Did it say why it failed, what file were you trying to flash? More often than not the system 7 error is caused from an out of date recovery, normally i would tell you to start there but given the fact you admitted to just randomly attempting to flash things to the device you are going to want to start from stock. The second sticky thread in this sub-forum is where you should start reading, because based on your post you either need a refresher or never have read it to begin with.
dntesinfrno said:
Since when does TWRP not read external SD cards? It see's mine just fine, for well over a year. In any case you didn't give much information to help troubleshoot. 'I tried unrooting' - if you were going to flash a stock ROM there is no need to unroot anything as the stock firmware is just that, stock. How did if fail in ODIN? Did it say why it failed, what file were you trying to flash? More often than not the system 7 error is caused from an out of date recovery, normally i would tell you to start there but given the fact you admitted to just randomly attempting to flash things to device you are going to want to start from stock. http://forum.xda-developers.com/showthread.php?t=1725839
Click to expand...
Click to collapse
For whatever reason, TWRP wouldn't read my sd card. And when I said I tried unrooting - I just meant flashing back to the stock ROM. Odin fails when it gets to system write. It goes down a bunch of lines of code successfully but when it gets to system write, it fails every time. I've downloaded a few different stock ROM versions for AT&T and tried switching USB ports around my laptop. I've also tried a few different versions of ODIN but I'm not coming up with anything but a soft bricked phone still.
kinjo1023 said:
For whatever reason, TWRP wouldn't read my sd card. And when I said I tried unrooting - I just meant flashing back to the stock ROM. Odin fails when it gets to system write. It goes down a bunch of lines of code successfully but when it gets to system write, it fails every time. I've downloaded a few different stock ROM versions for AT&T and tried switching USB ports around my laptop. I've also tried a few different versions of ODIN but I'm not coming up with anything but a soft bricked phone still.
Click to expand...
Click to collapse
Did you have usb debugging enabled before you attempted to flash via ODIN? It sounds like it doesn't have permission to write to the /system partition. You can try doing a factory reset from recovery to get past the bootloader and make sure, or use Kies to flash to stock via this thread.
dntesinfrno said:
Did you have usb debugging enabled before you attempted to flash via ODIN? It sounds like it doesn't have permission to write to the /system partition. You can try doing a factory reset from recovery to get past the bootloader and make sure, or use Kies to flash to stock via this thread.
Click to expand...
Click to collapse
I could have swore I made sure to check before I started the process but I cant' check now because the phone won't boot. Can't flash back to stock. Can't flash any roms. I can get into download mode and recovery though. It's weird. I've reverted other phones back to stock plenty of times. It just keeps failing no matter what I do with this.
dntesinfrno said:
Did you have usb debugging enabled before you attempted to flash via ODIN? It sounds like it doesn't have permission to write to the /system partition. You can try doing a factory reset from recovery to get past the bootloader and make sure, or use Kies to flash to stock via this thread.
Click to expand...
Click to collapse
Here's another question for you, I've looked all over for the newest CWM in .tar format but everything comes in .img format. I can't use the .img in ODIN to flash to the phone and can't boot my phone to use the CWM app to flash. I suppose I could try TWRP again but when I flashed the first time - TWRP wouldn't read my EXT SD card.....
kinjo1023 said:
Here's another question for you, I've looked all over for the newest CWM in .tar format but everything comes in .img format. I can't use the .img in ODIN to flash to the phone and can't boot my phone to use the CWM app to flash. I suppose I could try TWRP again but when I flashed the first time - TWRP wouldn't read my EXT SD card.....
Click to expand...
Click to collapse
if you could wipe everything get on odin with 4.1.2 update reboot use cf root to root it (if you dont have root) after reboot download ROM Manager from Play Store install CWM recovery (easiest way to root) hope this works
tl:dr I've been trying to flash the stock firmware using Odin but nothing seems to change after I reboot.
SGH-T889
TWRP v2.6.3.1
Devil Kernel
Jedi X Rom (20)
I had this setup for a few months until this morning when my phone had shut off on its own some time while I was sleeping. Turning on the phone would only load up to the Devil Kernel Splash screen. I can get into TWRP but it asks me for a password that I never set. After some searching, I'm assuming that this is because my data partition has possibly been corrupted.
I've tried doing a factory reset in TWRP, it says it's successful but practically there is no change. The console states that it is unable to mount /efs, /cache, and /system.
I tried using 'Format Data', but choosing this options only seems to reset TWRP because I see the TWRP splash screen and then am asked for a password again. From my understanding, shouldn't formatting the data should remove any encryption?
I tried to just reflash the stock firmware to reset everything but every time I finish flashing in Odin, Odin states that everything is fine but there is no change on my phone. I still only see the kernel splash screen on boot.
I've tried doing an Emergency Firmware Recovery through Kies but Kies is unable to do anything after it detects my device version.
kyang321 said:
tl:dr I've been trying to flash the stock firmware using Odin but nothing seems to change after I reboot.
SGH-T889
TWRP v2.6.3.1
Devil Kernel
Jedi X Rom (20)
I had this setup for a few months until this morning when my phone had shut off on its own some time while I was sleeping. Turning on the phone would only load up to the Devil Kernel Splash screen. I can get into TWRP but it asks me for a password that I never set. After some searching, I'm assuming that this is because my data partition has possibly been corrupted.
I've tried doing a factory reset in TWRP, it says it's successful but practically there is no change. The console states that it is unable to mount /efs, /cache, and /system.
I tried using 'Format Data', but choosing this options only seems to reset TWRP because I see the TWRP splash screen and then am asked for a password again. From my understanding, shouldn't formatting the data should remove any encryption?
I tried to just reflash the stock firmware to reset everything but every time I finish flashing in Odin, Odin states that everything is fine but there is no change on my phone. I still only see the kernel splash screen on boot.
I've tried doing an Emergency Firmware Recovery through Kies but Kies is unable to do anything after it detects my device version.
Click to expand...
Click to collapse
Odin the UVALJ1 ROM (i use the Mr. Robinson rooted version). I have been down that road before. I had to flash 2x before it fixed my devices file system.
Then install the current TWRP recovery as 2.6.3.1 is not the best option. From there you should be able to get started again.
Coug76 said:
Odin the UVALJ1 ROM (i use the Mr. Robinson rooted version). I have been down that road before. I had to flash 2x before it fixed my devices file system.
Then install the current TWRP recovery as 2.6.3.1 is not the best option. From there you should be able to get started again.
Click to expand...
Click to collapse
I tracked down the ROM that you're referring to by mrRobinson but after trying another 4 times I'm still getting the same results.
Can you clarify your second line about TWRP recovery? I tried seeing if TWRP was the problem since I could not format data but I cannot flash any new recoveries (stock, CWM, or older versions of TWRP). Does anyone know of any alternate means other than flashing through Odin?
Thanks for the reply though, hearing that other people have had similar problems gives me some hope.
kyang321 said:
I tracked down the ROM that you're referring to by mrRobinson but after trying another 4 times I'm still getting the same results.
Can you clarify your second line about TWRP recovery? I tried seeing if TWRP was the problem since I could not format data but I cannot flash any new recoveries (stock, CWM, or older versions of TWRP). Does anyone know of any alternate means other than flashing through Odin?
Thanks for the reply though, hearing that other people have had similar problems gives me some hope.
Click to expand...
Click to collapse
Try the UVUCMK7 version. That might do it.
Your version of TWRP is old. Try the current version for better results. My first issues with corruption involved 2.6.3.1 though I can't implicate it directly.
Coug76 said:
Try the UVUCMK7 version. That might do it.
Your version of TWRP is old. Try the current version for better results. My first issues with corruption involved 2.6.3.1 though I can't implicate it directly.
Click to expand...
Click to collapse
Thanks again for the response! Flashing recoveries in Odin isn't giving me any results so I'll try getting an external sd card and flashing version 2.7.2.0 from within TWRP.
kyang321 said:
Thanks again for the response! Flashing recoveries in Odin isn't giving me any results so I'll try getting an external sd card and flashing version 2.7.2.0 from within TWRP.
Click to expand...
Click to collapse
Coug76 said:
Try the UVUCMK7 version. That might do it.
Your version of TWRP is old. Try the current version for better results. My first issues with corruption involved 2.6.3.1 though I can't implicate it directly.
Click to expand...
Click to collapse
So I can't seem to change my recovery. Odin will supposedly pass but the version stays the same in my phone. Within TWRP I cannot mount my external sd card so I can't flash from there either.
I tried to see if I could do something with ADB but TWRP won't let me go into ADB side load because it cannot mount /cache.
Any ideas?
Download the ODIN flashable version of TWRP and flash from within ODIN. That will get you at least a new recovery. From there you can restore/etc. I had a similar issue a few weeks back. My partitions got corrupted and doing the standard full ODIN, regardless of which ODINversion/firmware combo I used, resulted in me having a stock recovery with literally nothing else. System, cache, data....nothing would mount. I thought I was permanently soft bricked. Each ODIN flash seemed to go well, but upon booting up, the phone would immediately go into stock recovery with those mounting errors. I used the ATT version of twrp 2.7.2.2...or whatever the latest version was because it had the partition repair option that the TMO version hasn't been updated to yet.
Install the recovery from ODIN.
Boot into recovery.
Click the wipe tab. Then do the advanced wipe...select one partition at a time then click on the 'repair partition' option. I think only cache, system and data can be repaired. The others won't let you repair. Will give an error saying failed or not repairable or something like that.
That's what helped me get out of my dilemma. Fortunately, I had a stock backup on an SD card I was able to restore at that point. If you don't, flash a new ROM, log in, then download Mobile ODIN from the market. You can then flash full firmwares from within the phone itself and get back to 100% stock, minus boot loader. But if you're already on the 4.3 bootloader then there won't be any problems.
I'll check back to see if you had any success. It worked for me, but I offer no guarantees.
Good luck.
carlz28 said:
Download the ODIN flashable version of TWRP and flash from within ODIN. That will get you at least a new recovery. From there you can restore/etc. I had a similar issue a few weeks back. My partitions got corrupted and doing the standard full ODIN, regardless of which ODINversion/firmware combo I used, resulted in me having a stock recovery with literally nothing else. System, cache, data....nothing would mount. I thought I was permanently soft bricked. Each ODIN flash seemed to go well, but upon booting up, the phone would immediately go into stock recovery with those mounting errors. I used the ATT version of twrp 2.7.2.2...or whatever the latest version was because it had the partition repair option that the TMO version hasn't been updated to yet.
Install the recovery from ODIN.
Boot into recovery.
Click the wipe tab. Then do the advanced wipe...select one partition at a time then click on the 'repair partition' option. I think only cache, system and data can be repaired. The others won't let you repair. Will give an error saying failed or not repairable or something like that.
That's what helped me get out of my dilemma. Fortunately, I had a stock backup on an SD card I was able to restore at that point. If you don't, flash a new ROM, log in, then download Mobile ODIN from the market. You can then flash full firmwares from within the phone itself and get back to 100% stock, minus boot loader. But if you're already on the 4.3 bootloader then there won't be any problems.
I'll check back to see if you had any success. It worked for me, but I offer no guarantees.
Good luck.
Click to expand...
Click to collapse
I already have TWRP 2.6.3.1. In trying to see if that version is a problem, I've tried flashing a different version through Odin but it doesn't have any effect (the version will always stay as 2.6.3.1 regardless of what I flash through Odin).
So it's been a week since my issue started and I haven't gotten any further since I started.
I've tried flashing a new pit file to no avail (stuck on get pit file mapping). I've also tried doing a nand rewrite but I get a nondescript error.
As of this point I've given up and am just going to use an old phone lying around until my contract is up. If you've found this thread because you've had similar issues I wish you better luck than I had.