Related
Hello all,
I am facing problems with my SIII right now. I was running AOKP but due to the bluetooth not being able to sync with my stereo, I decided to go back to stock rooted. I just flashed back the stock rooted image using Odin, but now my phone sits at the Samsung screen with the blue notification light on. I have tried rebooting, and it gets to this point (after the rethink possible screen) and just sits. I am thinking another flash in Odin is in order? Is there a stock, non root image I can flash via odin? I am just really lost for ideas right now and any input would be appreciated! Thanks!
Update:
I tried flashing with odin again and this time I got a failed. It was in the process of flashing the "system". I am kinda starting to freak out. I am hoping that it's just the file I'm using (though it just worked not even a few days ago.) I am trying again and if this one bombs out, I think I am going to try a different file. The one I am downloading to try next is the "stock unroot" from the how-to video. Anyone have any luck with this?
Another Update:
I just re-flashed with odin, this time it says it successfully completed but once again it's stuck at the flashing Samsung logo with the indicator led on.... I am starting to really freak out lol. I have another file downloading that is supposedly just stock, no root or anything...
rakhov said:
Hello all,
I am facing problems with my SIII right now. I was running AOKP but due to the bluetooth not being able to sync with my stereo, I decided to go back to stock rooted. I just flashed back the stock rooted image using Odin, but now my phone sits at the Samsung screen with the blue notification light on. I have tried rebooting, and it gets to this point (after the rethink possible screen) and just sits. I am thinking another flash in Odin is in order? Is there a stock, non root image I can flash via odin? I am just really lost for ideas right now and any input would be appreciated! Thanks!
Update:
I tried flashing with odin again and this time I got a failed. It was in the process of flashing the "system". I am kinda starting to freak out. I am hoping that it's just the file I'm using (though it just worked not even a few days ago.) I am trying again and if this one bombs out, I think I am going to try a different file. The one I am downloading to try next is the "stock unroot" from the how-to video. Anyone have any luck with this?
Click to expand...
Click to collapse
Actually have the exact same situation going on right now, I will post if I can find a fix. Downloading an alternate stock build I found now and will let you know how it goes.
Glad to have a partner in crime
http://galaxys3root.com/galaxy-s3-unroot/how-to-unroot-att-galaxy-s3-sgh-i747/
This is the file/procedure I am going to try next. Good luck and I will stay posted with any info, likewise!
rakhov said:
Glad to have a partner in crime
http://galaxys3root.com/galaxy-s3-unroot/how-to-unroot-att-galaxy-s3-sgh-i747/
This is the file/procedure I am going to try next. Good luck and I will stay posted with any info, likewise!
Click to expand...
Click to collapse
Thats exactly what Odin is working on loading now, Download had just finished.
avarize said:
Thats exactly what Odin is working on loading now, Download had just finished.
Click to expand...
Click to collapse
Wicked, well good luck solider....Does anyone know the signifigince of the led being on? It looks like it is slightly pulsating too...I hope this isn't the "sorry, you just broke it" notification XD
rakhov said:
Wicked, well good luck solider....Does anyone know the signifigince of the led being on? It looks like it is slightly pulsating too...I hope this isn't the "sorry, you just broke it" notification XD
Click to expand...
Click to collapse
I've always noticed the LED being on during boot (or some of the boot) and it was also on when I had a bootloop during cm9 so I don't think it means anything.
Fair enough, I guess I never paid that much attention till now when things don't work heh. I do recall reading about someone else having the similar issue using odin...I am trying to find the post and if there was any follow up on it.
rakhov said:
Fair enough, I guess I never paid that much attention till now when things don't work heh. I do recall reading about someone else having the similar issue using odin...I am trying to find the post and if there was any follow up on it.
Click to expand...
Click to collapse
Didn't seem to have any luck with that download/odin. Still stuck, Trying a few more things, although I am a bit lost as to what to do from here.
---------- Post added at 02:52 AM ---------- Previous post was at 02:51 AM ----------
avarize said:
Didn't seem to have any luck with that download/odin. Still stuck, Trying a few more things, although I am a bit lost as to what to do from here.
Click to expand...
Click to collapse
Correction : Used that link you had posted, it was still stuck so I loaded up the toolkit and used option 20 for reboot options to force it into default recovery, wiped data & cache from there and let it reboot, it seemed to have hung but waited a few minutes and it came back to life. Back to complete stock here now, hope it works for you.
avarize said:
Didn't seem to have any luck with that download/odin. Still stuck, Trying a few more things, although I am a bit lost as to what to do from here.
---------- Post added at 02:52 AM ---------- Previous post was at 02:51 AM ----------
Correction : Used that link you had posted, it was still stuck so I loaded up the toolkit and used option 20 to force into default recovery, wiped data & cache from there and let it reboot, it seemed to have hung but waited a few minutes and it came back to life. Back to complete stock here now, hope it works for you.
Click to expand...
Click to collapse
When you say toolkit are you talking about the one from the thread labled [SAMSUNG GALAXY S3 QCOM TOOLKIT V2.3] Drivers Backup Root CWM BusyBox + MORE [ATT]? And if so you just opened it and used option 20? nothing else? This sounds great if it works hehe.
rakhov said:
When you say toolkit are you talking about the one from the thread labled [SAMSUNG GALAXY S3 QCOM TOOLKIT V2.3] Drivers Backup Root CWM BusyBox + MORE [ATT]? And if so you just opened it and used option 20? nothing else? This sounds great if it works hehe.
Click to expand...
Click to collapse
Should have explained a bit better. Yes that toolkit
While it was stuck at samsung screen.
1 For AT&T (Obviously)
20 For reboot options
1 For recovery.
Then wipe data/cache
Then wiped cache (no idea why)
then rebooted.
When i did an Odin to stock I also froze on the Samsung logo. I had to boot to recovery and do a factory reset I side recovery to get it to boot. Keep in mind everything will be deleted though
Sent from my SAMSUNG-SGH-I747 using xda premium
That is exelent. I am downloading the toolkit right now and will report back shortly.
Once you got it to boot, did you still have root? I am wondering if you flashing the "stock rom" that I posted, if that had any impact. I have only pushed the root66 file, so I am expecting root when(if XD) I get this thing going again. I appreciate you being more thorough with your instructions, and will report back with my results as soon as I get some
Also, are we loners on this? I am not seeing any other posts about going back to stock/stock rooted from modded roms using odin? I am trying to figure out the best method to go back to stock. I made a nandroid and I am sure that would work, but all of this word about having to flash different kernels and bluetooth/wifi drivers to get stock working properly makes me wonder if just using odin is the easiest method, as it restores everything on the phone (to my knowledge).
crash822 said:
When i did an Odin to stock I also froze on the Samsung logo. I had to boot to recovery and do a factory reset I side recovery to get it to boot. Keep in mind everything will be deleted though
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
That is great, this may sound a little silly, but how do I boot to recovery? Thanks!
UPDATE:Nvm, google hehe. I just did the factory reset...Things are looking good so far, the haptic lights turned on at least...BOOM! We are good gentlemen. It looks like all it took was the recovery wipe. This is great news! I will try to figure out how to mark this as solved, and you crash822, you get a thanks
NP sir. We all have to start somewhere. Luckily for me I was already planning on doing a full wipe so I backed up everything I wanted to keep from my phone onto my computer before using odin.
I seem to be having the same issue. I've downloaded the toolkit as you guys have suggested. are you guys in download mode on the phone while you use this? it seems to want me to be in debugging mode and i can't get to that. I've tried a factory reset with no luck.
Dodged a bullet yesterday. FreeGee unlock, chose TWRP and then went to flash stock v9 odex. Wiped Cache/Dalvick and then flashed. Upon reboot I saw LG screen then black and nothing. Tried to LGPNST from download mode with LG driver and could not detect phone. After messing around in TWRP for about 2 hours where I performed about every function available (just before throwing the phone into the fireplace), I queued the z9 odex twice let TWRP flash it twice and everything worked. Here's the thing, my wife's phone is incessantly prompting to update, so I need to flash her phone. Should I use clockwork? Anyway to avoid a similar issue and near total bricking of her phone?
Same thing using Clockwork on wife's phone. Now I'm trying everything to get it back. Still have recovery, but unable to complete system reboot. Black screen. Used to flash evo all the time, never an issue. Now I'm 0 for 2 with a miraculous boot and update on my phone. This one doesn't look like I'm going to get as lucky. CWM is a bigger pain too. Frustrated. Not looking forward to lgpnst (still not sure how it all works) and then trying this mess again.
I had a similar problem to yours last night to. Except I didn't really do anything to it. It was just sitting there charging and I took it off the charger and it was doing some kind of boot loop, But every so often it would just stop on a black screen. I lgnpst about six times back but after running root and freegee I would try to get into bootloader and it would do it again. Eventually I tried doing freegee with clockwork instead and it did it again, Than I forced the phone off and pluged it in to my computer to get ready to lgnpst again so I could at least use the phone. All of a sudden I look at the screen and there was a battery charging animation. And then unpluged it and for kicks turned it on and it booted up no problem. Then I tried booting into bootloader and all works now. It was really strange, I did put twrp back though. I like it better then clockwork. I think I sore you asking questions in irc while I was in there asking question to ha.
-Frank
MikeDroid said:
Same thing using Clockwork on wife's phone. Now I'm trying everything to get it back. Still have recovery, but unable to complete system reboot. Black screen. Used to flash evo all the time, never an issue. Now I'm 0 for 2 with a miraculous boot and update on my phone. This one doesn't look like I'm going to get as lucky. CWM is a bigger pain too. Frustrated. Not looking forward to lgpnst (still not sure how it all works) and then trying this mess again.
Click to expand...
Click to collapse
I had the same thing happen and couldn't figure it out so I took it back to sprint told them I did the update and it messed up so they gave me a new phone for 35 bucks and from now on im staying STOCK.........................
DId you try to lgnpst back yet? That may help you.
-Frank
Frank...yup that's how mine worked. Just not sure how to do this. I don't think my failed lgpnst attempts did anything, b/c mine took the update eventually. I'll keep trying. This phone is so temperamental. Does Shellnut have some input on this problem? I can't figure out why some phones take and others don't when doing the same thing.
Talk to Shelnut2 over pm or find him in irc. I just found out there is a special version of freegee that may fix the problem. I seem to have fixed mine but I sent him a pm asking some questions about the problem. I think you are going to need to lgnpst back. Then root and run the special version of freegee. You have to get it from him because it does some things different that may brick the phone permanently. Thats why you have to ask for it. From what I understand it fixes that kind of problem.
-Frank
I will. I'm going to see if this thing will self correct. Otherwise I will check with him on that. The LGPNST is something I'm not looking fwd to doing.
LGPNST is not detecting phone in dl mode but does detect when in recovery. This SUCKS. Frustrated and out of ideas.
When you installed lgnpst did you install the file that says auto-lgnpst? Also did you run install.bat as administrator?
-Frank
frankt2012 said:
When you installed lgnpst did you install the file that says auto-lgnpst? Also did you run install.bat as administrator?
-Frank
Click to expand...
Click to collapse
Not sure if I ran as administrator. Assumed that I did. As a casual hack, I'm in over my head.
Sent from my LG-LS970 using xda app-developers app
Ok. Ran as admin. Won't even detect device. Anyone in DFW area proficient in this stuff who I could pay to lgpnst this thing?
Bricked OG
MikeDroid said:
Ok. Ran as admin. Won't even detect device. Anyone in DFW area proficient in this stuff who I could pay to lgpnst this thing?
Click to expand...
Click to collapse
I've been working on mine for a day and a half. I can't figure out the thing with renaming the ".tot" file to ".bin" because I don't even see a .tot file. After I unzipped the big ZV7 there was only one file without an extension so I can't figure out if thats the one I'm supposed to rename. Can you point me in the right direction?:crying:
[ I figured it out, I had to go into Preferences on my file explorer and set it to show all file types...DUHHH ]
In Windows, go to control panel, file settings, show file extensions. Something like that.
Sent from my LG-LS970 using xda premium
Finally got bit working. No more issues. Non of this stuff is very intuitive when your in panic mode. All is good now though.
Sent from my LG-LS970 using xda app-developers app
Apps
MikeDroid said:
Dodged a bullet yesterday. FreeGee unlock, chose TWRP and then went to flash stock v9 odex. Wiped Cache/Dalvick and then flashed. Upon reboot I saw LG screen then black and nothing. Tried to LGPNST from download mode with LG driver and could not detect phone. After messing around in TWRP for about 2 hours where I performed about every function available (just before throwing the phone into the fireplace), I queued the z9 odex twice let TWRP flash it twice and everything worked. Here's the thing, my wife's phone is incessantly prompting to update, so I need to flash her phone. Should I use clockwork? Anyway to avoid a similar issue and near total bricking of her phone?
Click to expand...
Click to collapse
Always backup your phone before tinkering with system files, and experimenting with launchers, kernals etc.
Titanium backup in WORTH the investment to upgrade to PRO.
Rom manager is a good one to boot directly into recovery without fiddling in the fastboot menu. And for backing up settings and roms.
Always KNOW what your doing. lol. sometimes even the big guys forget this. RESEARCH!
So I've had the S4 for 1 month now and at first I really didn't want to root or change the ROM. I actually like the TW interface and think it's great as it is. I've been rooting and changing ROMs going back to the MyTouch, but for some reason the S4 had me worried. I debated over and over about doing it, but after getting tired of the bloatware, constant ads being displayed and wanting to stop the horrible startup/shutdown music, the time came for me to root it.
So, after pouring over many hours of reading and deciding the method, I went with the Chainfire route. I chose this because from what I read (and this may have been where I misunderstood something??), if I ONLY root the phone, don't install a custom recovery then I will still be able to receive OTAs (when and IF they come from TMO). So after a couple of heart-stopping moments at 2am last night with about 4 ODIN fails, I finally got it rooted. Turns out, the USB cable I was using might have been the problem. I went out to the car and got the original cable that came with the phone and it worked on the first try with that. I thought for sure I had hard bricked the phone when it came up with an error message at startup regarding a firmware problem.
Anyhow, to make a long story short, after doing the rooting, I checked the update option in settings and it's telling me the phone has been modified and is unable to receive updates. I then ran the triangle away program to reset the binary counter back to Samsung Official/Official, which it's reporting now instead of Custom, but then checking the updater it still reports the same thing. This is what I didn't want to have happen!
Any suggestions on how to rectify this or have I crossed that line and might as well just go ahead and put a recovery on there and do a backup and leave it at that until the day comes I decide to slap a custom ROM on it?
Thanks for letting me rant, but I would like some assistance if possible.
patriot1973 said:
So I've had the S4 for 1 month now and at first I really didn't want to root or change the ROM. I actually like the TW interface and think it's great as it is. I've been rooting and changing ROMs going back to the MyTouch, but for some reason the S4 had me worried. I debated over and over about doing it, but after getting tired of the bloatware, constant ads being displayed and wanting to stop the horrible startup/shutdown music, the time came for me to root it.
So, after pouring over many hours of reading and deciding the method, I went with the Chainfire route. I chose this because from what I read (and this may have been where I misunderstood something??), if I ONLY root the phone, don't install a custom recovery then I will still be able to receive OTAs (when and IF they come from TMO). So after a couple of heart-stopping moments at 2am last night with about 4 ODIN fails, I finally got it rooted. Turns out, the USB cable I was using might have been the problem. I went out to the car and got the original cable that came with the phone and it worked on the first try with that. I thought for sure I had hard bricked the phone when it came up with an error message at startup regarding a firmware problem.
Anyhow, to make a long story short, after doing the rooting, I checked the update option in settings and it's telling me the phone has been modified and is unable to receive updates. I then ran the triangle away program to reset the binary counter back to Samsung Official/Official, which it's reporting now instead of Custom, but then checking the updater it still reports the same thing. This is what I didn't want to have happen!
Any suggestions on how to rectify this or have I crossed that line and might as well just go ahead and put a recovery on there and do a backup and leave it at that until the day comes I decide to slap a custom ROM on it?
Thanks for letting me rant, but I would like some assistance if possible.
Click to expand...
Click to collapse
If you've reset your binary counter and have modified nothing else, just unroot and you should be able to receive updates again.
Go into the Triangle Away app and check system modified workaround and problem solved
Sent from my SGH-M919 using Tapatalk 2
jbreeze228 said:
Go into the Triangle Away app and check system modified workaround and problem solved
Sent from my SGH-M919 using Tapatalk 2
Click to expand...
Click to collapse
This. It explains this right in the app.
jbreeze228 said:
Go into the Triangle Away app and check system modified workaround and problem solved
Sent from my SGH-M919 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for pointing me in the right direction. I went ahead and got SuperSU Pro because that's the only way the feature in Triangle Away will work. It was after 2am when I was rooting and having problems so I wasn't too sharp.
Thanks!
I turned my s3 off for about a month while I used my note2. When I turned it off it was rooted with twr recovery and running a custom Rom. When I turned it back on the Rom was still running however I did loose all the widgets I was using. Over night titanium tried to run the scheduled backup redo. Then in the morning I noticed titanium said it could not gain root access. I tried other apps that require root and none will gain access. The super user app is still there but says there is no root. It's simple enough to re-root but I'm really curious as to what happened. Any ideas?
Sent from my SGH-T999 using XDA Premium 4 mobile app
Please Specify Rom and Android Version.
In short, if your TWRP recovery is intact try a factory reset from there.
Thanks Persius, I haven't tried to go into recovery since I have to do it manually cause I'm not sure what will happen if it's not there. My computer is broke right now so I'm limited. It's been since the s3 first came out that I installed the Rom so I'm not really sure which one I'm on but it says JZO 54, and it's 4.1.2 Thanks again for your help
bls2633 said:
Thanks Persius, I haven't tried to go into recovery since I have to do it manually cause I'm not sure what will happen if it's not there. My computer is broke right now so I'm limited. It's been since the s3 first came out that I installed the Rom so I'm not really sure which one I'm on but it says JZO 54, and it's 4.1.2 Thanks again for your help
Click to expand...
Click to collapse
Say... Are you sure we talking about an SIII or an S-II ?? That sounds like the 4.1.2 Stock of an S II. What does it say under Settings > About Phone > Model Number ?
Turn off completely then Hit Volumn Up + Home +Power all at the same time. Wait for 3 minutes or so with all 3 pressed. You will see Recovery come on. Let go of all 3 buttons and then do a Factory Reset in the recovery.
Thanks again, under build that's what it says, jzo 54, I think it might be Liquid Smooth. And it is an s3. I will try to go into recovery if you don't think anything will happen if that's not there either. Something else weird I just thought of is I also had some strange kiddie like themes and apps I never put there. It's like someone else used my phone but that's not possible as I saw it every day and live alone. Strange. Any way, thanks again
bls2633 said:
Thanks again, under build that's what it says, jzo 54, I think it might be Liquid Smooth. And it is an s3. I will try to go into recovery if you don't think anything will happen if that's not there either. Something else weird I just thought of is I also had some strange kiddie like themes and apps I never put there. It's like someone else used my phone but that's not possible as I saw it every day and live alone. Strange. Any way, thanks again
Click to expand...
Click to collapse
Yes its safe to Go into Recovery. Go ahead and do a Factory Reset. Let me know how that goes.
Ok, did the factory reset and went ahead and did the ota update to 4.0 I'm going to root again. Do you have any suggestions on a good Rom? Also what is the best way to root these days and best recovery? Thanks Perseus I appreciate your help and advice
Sent from my SGH-T999 using XDA Premium 4 mobile app
I am confused. Wasn't (or shouldn't it be ) your S3 already on the JB 4.1 ? What did you mean by OTA update to 4.0 ? Are you referring to the OTA Update to 4.3 ?
I can not comment on Rooting unless I know which os version you have.
Sorry, was a misprint. Yes, went to 4.3
Sent from my SGH-T999 using XDA Premium 4 mobile app
So if you still have TWRP then flash Superuser from Recovery. Lookup its thread here on XDA.
However, with the Knox being present and SELinux in Enforcing state, your chances of Rooting are slim.
Please don't brick your device.
i'm going to start by addressing my phone. i have a HTC m8 it is rooted and i have updated it to 5.0.1. but during that process i ran across some issues that might have caused issues in other areas. when t- mobile release the lollipop update i goggle how to get it on a rooted phone and basically what i got from it was i had to replace custom recovery with stock recovery to get the update and if i wanted to go back i had to do the opposite. when i watch the video i didn't realize the video was old and had not been updated until i got to the part of the screen(on my device) where it was a red triangle. so make a long story short i found the correct stock recovery and installed it but when i did. It said i lost su and i need to re install and that became a problem as while because i could not found nothing that was helpful. so i just tried uninstalling xposed framework mode and when i restarted my phone. It was stuck in a boot-loop. so it took me a minute to get out of that and all it took was me installing su again. so now that's out of the way when my phone came back on i realize a lot of my app force closing and maybe i thought it was minor bugs form the new update but after awhile nothing change. so at this point i'm done with this i'm ready to go back to stock and i cant because my internal storage is missing and i know all of my flies is there because when i boot into recovery i see them but when i connect my phone to my PC it shows a limit of files and on my phone in certain apps it shows files and in others apps it doesn't. i just need to know how to fix it so i can unroot.
Sir,
Please wait until mods will move this thread to the device specific forum for more relevant answers.
Stand by
Good luck
fletcherboy said:
i'm going to start by addressing my phone. i have a HTC m8 it is rooted and i have updated it to 5.0.1. but during that process i ran across some issues that might have caused issues in other areas. when t- mobile release the lollipop update i goggle how to get it on a rooted phone and basically what i got from it was i had to replace custom recovery with stock recovery to get the update and if i wanted to go back i had to do the opposite. when i watch the video i didn't realize the video was old and had not been updated until i got to the part of the screen(on my device) where it was a red triangle. so make a long story short i found the correct stock recovery and installed it but when i did. It said i lost su and i need to re install and that became a problem as while because i could not found nothing that was helpful. so i just tried uninstalling xposed framework mode and when i restarted my phone. It was stuck in a boot-loop. so it took me a minute to get out of that and all it took was me installing su again. so now that's out of the way when my phone came back on i realize a lot of my app force closing and maybe i thought it was minor bugs form the new update but after awhile nothing change. so at this point i'm done with this i'm ready to go back to stock and i cant because my internal storage is missing and i know all of my flies is there because when i boot into recovery i see them but when i connect my phone to my PC it shows a limit of files and on my phone in certain apps it shows files and in others apps it doesn't. i just need to know how to fix it so i can unroot.
Click to expand...
Click to collapse
Try this
All you have to do is type in these 2 lines in your terminal emulator on your android device:
Su
restorecon -FR /data/media/0
And your storage will be back to normal
Click to expand...
Click to collapse
I've tried it but nothing happened.
Sent from my HTC One_M8 using XDA Free mobile app
Did I do something wrong ?
Sent from my HTC One_M8 using XDA Free mobile app
fletcherboy said:
Did I do something wrong ?
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
There's a blank between FR and /
HTCOneM8 by ViperOne M8
Got it. Thanks
Sent from my HTC One_M8 using XDA Free mobile app
clsA said:
Try this
Click to expand...
Click to collapse
You're a god sent! Lots of thanks!!!!