My coworker has a T989 with CWM 6.xxx touch that he acquired from the forums. He flashed CM 10 stable but was stuck in
a bootloop. We went back to recovery and flash the darksider scripts which as known to many here shouldn't be used in anything
higher than cwm 5.xx. Any action done in recovery now hangs and freezes. My solution to this would be to go into download mode
and odin a recovery or return the phone to stuck. Now the big problem is the USB port on the phone doesn't work. With properly installed
drivers the phone is not detectable in download mode, nor when the phone was working.
Any suggestions on getting out of this?
Warbuff said:
My coworker has a T989 with CWM 6.xxx touch that he acquired from the forums. He flashed CM 10 stable but was stuck in
a bootloop. We went back to recovery and flash the darksider scripts which as known to many here shouldn't be used in anything
higher than cwm 5.xx. Any action done in recovery now hangs and freezes. My solution to this would be to go into download mode
and odin a recovery or return the phone to stuck. Now the big problem is the USB port on the phone doesn't work. With properly installed
drivers the phone is not detectable in download mode, nor when the phone was working.
Any suggestions on getting out of this?
Click to expand...
Click to collapse
Hhhmm, I have used the darkside super wipe before in CWM 6 and have not seen anything like this [I don't anymore no real need for now it as everything cleans up nice under CWM just use mounts and storage and tap to format /system and /data and then just wipe cache and dalvick cahce and install ROM then install GApps.
You sure you used the right CM10 image [listed under the device name Hercules?
I didn't think we had an official stable CM 10 only nightlies.
If you flashed CM10 that you used on a different device then it replaced some critical files that probably caused this.
If I were you keep trying to get to download mode [there is a trick to it, it is like getting in to recovery manually on boot EXCEPT you need to plug in the USB cable right as you see SAMSUNG logo] and even though I have done it countless times there are those times when it takes me several good tries to get back there.
If you can get in to recovery DONT TOUCH THE DEVICE JUST GET IT THERE then plug in a USB cable and see if you can get to adb
if in windows be sure to run cmd [command prompt] as admin
if you can run adb shell and if it comes up with either just $ or # or a bunch of text then $ or # then...
If it is a $ then type in "su" [no quotes]
that way you get #
If it says # then type [again without quotes]: "restart download"
You should even be able to run the following command without opening the shell first but if it defaults to a user shell and not an admin shell [$ is a user shell and # is an admin shell] it may refuse to follow the command:
[again without quotes] "adb restart download"
This should get the phone to restart to download mode without using hardware keys
If you can get in to recovery and can adb shell to it on the computer that may give you a way to run commands and do things manually, but you will need to find guides on exactly how to run recovery via ADB [I have seen cases where you can copy a recovery to the temp section via adb and then manually run a command in adb shell and basically get the device to use the new file until the next restart.
The darkside scripts will bork any CWM that isn't CWM 5. A much quicker way is to download TWRP recovery and flash it. The recovery will lock up in the the flashing process, but after actually finishing the install. Once it locks up, hold the power button for 10 seconds to reboot. Once the vibration is felt hold both volume buttons and voila! You should be in TWRP recovery now.
I've personally done this myself as I'm the person who actually discovered that the darkside scripts are the cause for borked CWM 6 recoveries. Just don't use them unless you're on CWM 5 or TWRP.
Sent from my SAMSUNG-SGH-T989 using xda premium
RushAOZ said:
The darkside scripts will bork any CWM that isn't CWM 5. A much quicker way is to download TWRP recovery and flash it. The recovery will lock up in the the flashing process, but after actually finishing the install. Once it locks up, hold the power button for 10 seconds to reboot. Once the vibration is felt hold both volume buttons and voila! You should be in TWRP recovery now.
I've personally done this myself as I'm the person who actually discovered that the darkside scripts are the cause for borked CWM 6 recoveries. Just don't use them unless you're on CWM 5 or TWRP.
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Yeah but keep in mind myself and sevral others have had issues with TWRP not formatting partitions correctly [I almost threw a Nexus 7 through the wall for it] and it would boot loop over several different ROM flashes for a whole weekend.until I got tired of it and in a last ditch effort changed back to CWM [this was only a version or 2 ago, oh and one of the TWRP devs tried to convince me their /data wipe should also wipe /sdcard [/data/media in JB] and there was no way around that when in CWM I can go to mounts and storage and wipe /data without touching my user data on sdcard [I say SDCard to differentiate the user data housed in internal storage mounted as /sdcard and not just the user data in /data I know there is no actual SDCard in a Nexus 7] so that didn't inspire a ton of confidence in me.
I NEVER recommend TWRP to new users as it has also incorrectly hosed my boot partition on a flash and bricked my device and I had to get a replacement [This was a few versions ago].
Not saying you will get the same trouble just saying to me it is not worth the gamble when talking about my awesome T989 or Nexus 7.
Not to mention TWRP has a tendency when a JB ROM is installed to mirror the legacy mount points on to the /SDCard [in JB for backwards compatibility you get /storage/emulated/0/sdcard that has to be used by recoveries and when I used TWRP it would create that directory structure on to my SDCard when in fact it is only supposed to be a hard link [the directory /storage/emulated/0/sdcard exists but not on the SDCard it is just a pointer]
so essnetially you would end up with a double copy of your SDCard storage back on your SDCard [files still listed under /sdcard but then on sdcard would be a directory 0 that should not be there and in that would be /SDCard/ and another copy of what was on my SD]. I dunno if that bug has yet to be addressed or not [I think so but have not checked].
If you really want to flash TWRP just use market to download GooManager in Android and open and grant root
Once done hit settings button so you see its menu and tap Open Recovery and it will go through flashing TWRP [Similiar to how ROM Manager can flash CWM recovery for you from inside Android [must have Super User access first or they can't do so and you would then need to use Odin and flash it that way]]. Keep in mind your recovery should never freeze and CWM has never done so for me even as part of any install process.
RealPariah said:
Yeah but keep in mind myself and sevral others have had issues with TWRP not formatting partitions correctly [I almost threw a Nexus 7 through the wall for it] and it would boot loop over several different ROM flashes for a whole weekend.until I got tired of it and in a last ditch effort changed back to CWM [this was only a version or 2 ago, oh and one of the TWRP devs tried to convince me their /data wipe should also wipe /sdcard [/data/media in JB] and there was no way around that when in CWM I can go to mounts and storage and wipe /data without touching my user data on sdcard [I say SDCard to differentiate the user data housed in internal storage mounted as /sdcard and not just the user data in /data I know there is no actual SDCard in a Nexus 7] so that didn't inspire a ton of confidence in me.
I NEVER recommend TWRP to new users as it has also incorrectly hosed my boot partition on a flash and bricked my device and I had to get a replacement [This was a few versions ago].
Not saying you will get the same trouble just saying to me it is not worth the gamble when talking about my awesome T989 or Nexus 7.
Not to mention TWRP has a tendency when a JB ROM is installed to mirror the legacy mount points on to the /SDCard [in JB for backwards compatibility you get /storage/emulated/0/sdcard that has to be used by recoveries and when I used TWRP it would create that directory structure on to my SDCard when in fact it is only supposed to be a hard link [the directory /storage/emulated/0/sdcard exists but not on the SDCard it is just a pointer]
so essnetially you would end up with a double copy of your SDCard storage back on your SDCard [files still listed under /sdcard but then on sdcard would be a directory 0 that should not be there and in that would be /SDCard/ and another copy of what was on my SD]. I dunno if that bug has yet to be addressed or not [I think so but have not checked].
If you really want to flash TWRP just use market to download GooManager in Android and open and grant root
Once done hit settings button so you see its menu and tap Open Recovery and it will go through flashing TWRP [Similiar to how ROM Manager can flash CWM recovery for you from inside Android [must have Super User access first or they can't do so and you would then need to use Odin and flash it that way]]. Keep in mind your recovery should never freeze and CWM has never done so for me even as part of any install process.
Click to expand...
Click to collapse
Oh don't mistake my comment Lola I only said to flash TWRP over CWM just so he can have a fully working recovery again. Once that step is done flash back over to CWM 6 again. I myself prefer CWM or TWRP. This is just a method of dumping a borked CWM installation.
Sent from my SAMSUNG-SGH-T989 using xda premium
RushAOZ said:
Oh don't mistake my comment Lola I only said to flash TWRP over CWM just so he can have a fully working recovery again. Once that step is done flash back over to CWM 6 again. I myself prefer CWM or TWRP. This is just a method of dumping a borked CWM installation.
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Well Lola as you say, so would opening ROM Manager from inside Android and just tapping to flash the Recovery from the app without having to worry about ADB and manual commands and a run around [as long as you have root access of course].
RealPariah said:
Well Lola as you say, so would opening ROM Manager from inside Android and just tapping to flash the Recovery from the app without having to worry about ADB and manual commands and a run around [as long as you have root access of course].
Click to expand...
Click to collapse
Haha sorry about that. I meant lol if he can get into his ROM, then why hasn't he done so yet? I assumed what happened to him is what happened to me. Flashed dark side wipe, formatted phone, then every install afterwards failed.
Sent from my SAMSUNG-SGH-T989 using xda premium
RushAOZ said:
Haha sorry about that. I meant lol if he can get into his ROM, then why hasn't he done so yet? I assumed what happened to him is what happened to me. Flashed dark side wipe, formatted phone, then every install afterwards failed.
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
I figured you meant LoL but Lola was funner so I used it again. I was not sure if originally he was one of the posts that siad he could have booted back or not [depends onn where the script froze in recovery as to whether Android boots].
If he can't then the easier way for most folks without having to go in to ADB running cmd as admin if using Windows, the commands and all
I would just say grab good ol Odin and CWM Recovery flash [Odin compatible usually is cwm-hercules-blah.md5 [in this case is not a text file with MD5 hash check it is the actual recovery] and have them flash it via Odin and fix it all up at once and besides they can get CWM touch for free if using Odin and searching the forums because if you dont mind flashing with Odin CWM touch is offered free here whereas if you use ROM Manager and try to flash Touch version of CWM that way it will charge you $2 per device [if you choose market pay option it should be tied to your account and that devices ID and allow future installs without charge [at least how it is for me had to pay once for my T989 once for my 8G Nexus 7 and the n once when I upgraded to 32G Nexus 7, but multiple installs on each individual device don't prompt me after I paid once [I have plenty of times where I may need to flash my recovery without computer access [and I know Koush myself so I like to donate his way he really does bust his ass ] so the ability to just flash the touch version via ROM Manager is great for myself.
I tried adb when I had the device. The Usb port I believe is damaged. I also tried using a flashable twrp and it stopped right before installation. When I restarted cwm was still there. Odin doesn't detect the phone even with the right drivers. It detects a gs3 and a skyrocket. To answer the question above there is a a cm10 stable for the Hercules. Do you think maybe I'm using the wrong flashable twrp. It just gets stuck on installing.
Sent from my Nexus 4 using xda app-developers app
Warbuff said:
I tried adb when I had the device. The Usb port I believe is damaged. I also tried using a flashable twrp and it stopped right before installation. When I restarted cwm was still there. Odin doesn't detect the phone even with the right drivers. It detects a gs3 and a skyrocket. To answer the question above there is a a cm10 stable for the Hercules. Do you think maybe I'm using the wrong flashable twrp. It just gets stuck on installing.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I believe I had TWRP 2.3.0.0. You should be able to find a zip somewhere or you can PM casonswag and ask him for it. He's the one who's been making flashable TWRP zips. Just make sure its for the Hercules.
One question though, does the phone have a ROM you can boot into or is it wiped.completely? Cuz if so, you can download goomanager or rommanager and flash a new recovery that way.
Sent from my SAMSUNG-SGH-T989 using xda premium
Only have access to the messed up recovery. No rom available to boot into.
Sent from my Nexus 4 using xda app-developers app
Warbuff said:
Only have access to the messed up recovery. No rom available to boot into.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Try PMing casonswag for twrp 2.3.0.0. That's what I used and it worked. If not.. man I really don't know :-/
Sent from my SAMSUNG-SGH-T989 using xda premium
Thanks for your help. I've contacted him and awaiting reply. In the meantime my coworker already got a new gs2 from tmo through warranty.
Sent from my Xoom using xda app-developers app
Related
Well.. in a nutshell, I installed CWM recovery, rooted the phone by installing the update from the "SD Card" when it was really the phone's internal memory, and all worked well. The original idea was to edit some .prop file in /system through a root file explorer. Basically, I changed a value as one stupid tutorial suggested which ended up causing the phone to boot in to a black screen. The phone goes in to recovery and D/l mode, but the problem is flashing ANY type of ROM to the phone. Odin is useless because you can only attach .tar, .gzip, .smd,... etc.. and the roms are usually in a .zip format. This means I need to get the .zip rom on to the phone's "Sd card" which is just internal memory and should clearly specify so. I can't exactly access my phone's memory afaik since.. you know.. the phone doesn't have any OS to boot up.
Now what is it that I can do to get a rom on the phone? Android commander is another useless program right now, also. Aside from the program always telling me my rooted phones aren't rooted, the program doesn't even detect the phone while it's in dl mode, recovery mode, bricked mode, garabge mode,... you get the point. I'm just a little irritated after trying for two days to get in to my own internal storage. If anyone has anything to share, and decides to share it, thanks a lot.
bump it would be nice for someone to help....
Nothing is flashing because you changed the ro.build props. There are stock Odin roms floating atound, or you can remove the device check from the updater script in the zips you download and then try to flash.
Sent from my SGH-T999 using xda premium
Or if you have adb you can push back stock build prop back to /system
Sent from my SGH-T999 using xda premium
All these suggestions I read on googled pages from people having similar issues are just such perfect ideas. I wish they worked, though. I have tried pretty much everything.
Since my last post I:
- Wiped every cache you can dream of
- Flashed boot-stock-tmobile-sgh-t999 probably 4 different times, and did the above step after each failure.
- Tried every possible way to get in the "external sd card" meaning "my phone's internal memory"
- Tried pulling the build.props, however without a valid operating system, I'm not going to get very far.
- Looked ALL OVER the internet for a STOCKY RECOVERY ROM in a .tar format. I don't see why it's too much to ask to be able to simply flash a rom from the pc odin since I'm pretty sure I won't be using odin mobile without first getting adroid booted up some how.
Yes, I disabled auto reboot in odin, I've tried pretty much everything and I really don't know where else to turn.
In android updater scripts there is a check into make sure you're flashing the correct phone. If the file is missing, it's going to fail this check and not flash.
If you unzip a Rom and modify this it should work.
On second thought,
You should follow the thread about returning to stock. That has an Odin flash able image that should get you booting again and then you can restart the process to root your phone.
Sent from my SGH-T999 using xda premium
I had that same problem I was only able to go to download mode so I used Odin and flashed stock tmo file to unroot the phone I can't remember exactly what it was called and it worked just fine and now I'm rooted again on cm10 and it works perfectly
Sent from my SGH-T999 using xda app-developers app
boot into recovery with the phone plugged into your computer. then open cmd (if in windows) and cd to the directory with a different rom then do
adb push xxx.zip /sdcard/
wait for it to finish then reboot recovery and flash the rom.
jellydroid13 said:
boot into recovery with the phone plugged into your computer. then open cmd (if in windows) and cd to the directory with a different rom then do
adb push xxx.zip /sdcard/
wait for it to finish then reboot recovery and flash the rom.
Click to expand...
Click to collapse
It's failing getprop ro.build.device
It's gonna do that even with pushing a new Rom to the sdcard unless those lines are removed from updater script.
Sent from my SGH-T999 using xda premium
similar problem, but long story short I can't boot into recovery and flashing through ODIN gets me an "unsupport dev_type" message and no results. Any suggestions?
The super obvious suggestion is to just restore your nandroid backup. Before any mod always make one that's in good shape. Every guide tells you to do this but you didn't mention it. Did you not make one? If you can get into recovery and/or DL mode then I'm pretty sure you are not bricked though.
the-Mike_D said:
If you can get into recovery and/or DL mode then I'm pretty sure you are not bricked though.
Click to expand...
Click to collapse
exactly. something's not being done right.
dyuhas1 said:
similar problem, but long story short I can't boot into recovery and flashing through ODIN gets me an "unsupport dev_type" message and no results. Any suggestions?
Click to expand...
Click to collapse
After seeing this OP, are you saying you can NOT get into d/l mode? also, look under devices on win machine, do you see an entry QLOAD*** if so you can NOT and will not get to d/l mode. It is hard bricked. time to get a jtag service. Stop wasting time looking for an answer and get it fixed. again, if you can not get into d/l mode, this is my suggestion. I HAVE BEEN THERE, DONE THAT. BTW, I have the usb jig, IT WILL NOT WORK on hard brick. hehe used it several times on soft bricks though.
Good luck.
Here is a French company doing that rescue service for bricked Galaxy S3 by JTAG
Réparer brick Galaxy S3
Wow, here is a quick and fast service. Get the usbjiig also for future soft-bricks.
MobileTechVideos.COM
http://mobiletechvideos.mybigcommerce.com/
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.
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.
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.
Early this morning I decided to try to get root and flash a custom rom, either CyanogenMod or Omni. I was able to flash touch recovery and wiped system files and cache. All custom firmwares failed to load. Now when the phone boots up, it goes into OTA activation, activates, does a PRL update, and reboots. Touch recovery repeats the system restore, unattended, and the loop repeats infinitely.
I am looking for a process that will help me cure the reboot loop to let me return to using the stock 4.3, but because of some bugginess I was experiencing, I would prefer a method that rids the knox bootloader and other protections so that I can gain root access and load custom firmwares.
I found a similar thread for a different model number, but I'm sure I'll need specific instructions for this model. Any help is greatly appreciated, as I'd rather not have to figure out a way to destroy the phone to get an insurance replacement. I'm also 23 days away from my upgrade date.
I am offering a $50 bounty for now, and when I upgrade, if possible to retain my phone while getting the upgrade price, you can have the note 2 that you helped fix.
cjkline83 said:
Early this morning I decided to try to get root and flash a custom rom, either CyanogenMod or Omni. I was able to flash touch recovery and wiped system files and cache. All custom firmwares failed to load. Now when the phone boots up, it goes into OTA activation, activates, does a PRL update, and reboots. Touch recovery repeats the system restore, unattended, and the loop repeats infinitely.
I am looking for a process that will help me cure the reboot loop to let me return to using the stock 4.3, but because of some bugginess I was experiencing, I would prefer a method that rids the knox bootloader and other protections so that I can gain root access and load custom firmwares.
I found a similar thread for a different model number, but I'm sure I'll need specific instructions for this model. Any help is greatly appreciated, as I'd rather not have to figure out a way to destroy the phone to get an insurance replacement. I'm also 23 days away from my upgrade date.
I am offering a $50 bounty for now, and when I upgrade, if possible to retain my phone while getting the upgrade price, you can have the note 2 that you helped fix.
Click to expand...
Click to collapse
Try this
Flash twrp recovery zip
Custom wipe system, data, cache
Install this http://forum.xda-developers.com/showthread.php?p=36388145
Install the root zip located in that op
Do not wipe anything else
Reboot it should act weird then reboot
After about 5-10 mins it will finish booting
Now flash philz 6.07.9 recovery via odin
Then boot into recovery factory reset/clean for new rom
Under mounts format data/media (internal sd)
Reboot into recovery
Flash your 4.4 rom
Sent from my SPH-L900 using XDA Premium 4 mobile app
Pending Testing
jlmancuso said:
Try this
Flash twrp recovery zip
Custom wipe system, data, cache
Install this http://forum.xda-developers.com/showthread.php?p=36388145
Install the root zip located in that op
Do not wipe anything else
Click to expand...
Click to collapse
Yeah, I wiped everything when I got home from work (don't know what I was thinking, really). TWRP even warned me no OS was installed, and I was like "so?". Anyway, as soon as it got stuck on the Samsung Galaxy Note II screen, I started the download of that rom you linked to. Still has 10 minutes left (big file is big). I'll come back with an update once I complete these first set of steps.
[Pending:]
Reboot it should act weird then reboot
After about 5-10 mins it will finish booting
Now flash philz 6.07.9 recovery via odin
Then boot into recovery factory reset/clean for new rom
Under mounts format data/media (internal sd)
Reboot into recovery
Flash your 4.4 rom
====================================
ADB Sideload
Since the device is not bootable, and I don't have an adapter to copy to my SD card via a usb reader, I struggled, but got the ADB Sideload function of the Android Development Toolkit to work once I upgrade to Team Win Recovery 2.7.0.0 via ODIN.
sideload log is as follows:
Code:
Updating partition details...
Full SELinux support is present.
Starting ADB sideload feature...
Installing '/data/media/0/sideload.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
UnRooted MC2 Stock Restore by blizzard412
Formatting /system and installing..
This will take a while
...Flashing temp special recovery
...Again just in case
Installing Radio...
Flashing firmware...
Flashing garwrnn & -EViL-KoNCEPTz- carrier partition fix...
You will automatically reboot to twrp to finish up...
[COLOR="Red"]E:Unable to mount '/preload'[/COLOR]
Should I be worried about the preload error?
Edit: rebooted but currently in a reboot loop without the startup sound. I'm going to let this go for about 10 minutes before I try to wipe and re-sideload? Before TouchWin rebooted it asked me if I wanted to install SU-SuperUser for root. Should I not install the root at this time?
Edit 2 THANK YOU!
[Pending:]
Reboot it should act weird then reboot
After about 5-10 mins it will finish booting
Now flash philz 6.07.9 recovery via odin.
Click to expand...
Click to collapse
I could not get this to flash via ODIN. The stock recovery kept loading instead
Decided to just try and move down the list.
Then boot into recovery factory reset/clean for new rom
Under mounts format data/media (internal sd)
Click to expand...
Click to collapse
Phone is now out of reboot loop once I cleared the data and cache. Text messages immediately came in after OTA activation and PRL update. I am now running stock rooted 4.1.2 without KNOX.
Reboot into recovery
Flash your 4.4 rom
Click to expand...
Click to collapse
Might wait on that for a minute. So thankful to at least have a working device again. Thanks for your help. Would you like the bounty? Please PM me a paypal address or your preferred methods.
The preload error is normal with twrp and is not an issue. Now you have lots going on so let me ask you this. Do you have a custom recovery and/or root as of now?
Sent from my SPH-L900 using XDA Premium 4 mobile app
Systems nominal
jlmancuso said:
The preload error is normal with twrp and is not an issue. Now you have lots going on so let me ask you this. Do you have a custom recovery and/or root as of now?
Sent from my SPH-L900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes, I had a rooted stock rom, replied to my texts from the day, then loaded rom manager, installed clockwork recovery. downloaded omni directly to the phone from their website, rebooted into clockwork, flashed, and things were fine. Booted into rooted kitkat 4.4.2, and now I'm flashin the gapps update to enable google services. network and wifi working fine under omni.
Can't thank you enough for helping me out of that hole from earlier.
In case you dont know omni rom does not come rooted.
Sent from my SPH-L900 using XDA Premium 4 mobile app
jlmancuso said:
In case you dont know omni rom does not come rooted.
Sent from my SPH-L900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yep, I flashed SuperSU in CWM and fixed that. Things are running great. Just need to see what the battery life is like now on a new rom.