Software v1.4.0
Root messed up in middle of running nookandzergy.bat. Got to the part where it says GG Rooted or whatever and it wouldn't go past that (I allowed ample time for reboot of device also). Apparently it thinks it's rooted but gapps and launcher weren't installed. I tried doing the 1 click unroot, the zip file to sd card, nomoarzergys, erase/restore and failed boot restore multiple times and it still seems to think i have a root on the tablet
When I try 1 click unroot it wont let me run it as a superuser and I get a could not echojava.lo.ioexception: error running exec(). Command: [su] working Directory: null environment: null error
When I try nomoarzergys I get error: device not found rooting to unroot! error: device not found
Any help would be appreciated.
I have read that the failed boot has to function correctly 8 times in a row to work take you back to stock. Did you go that many times. I'm interested as mine is under the tree and rooting is the first thing I will do.
miniblue said:
I have read that the failed boot has to function correctly 8 times in a row to work take you back to stock. Did you go that many times. I'm interested as mine is under the tree and rooting is the first thing I will do.
Click to expand...
Click to collapse
This is correct. The 9th boot it will automatically go into a full reset mode. You have to release the n button on that time round too.
if failed boot restore doesnt work, manually download and install super user apk and then use unroot app.
dodgepot said:
This is correct. The 9th boot it will automatically go into a full reset mode. You have to release the n button on that time round too.
Click to expand...
Click to collapse
+1 on using the 9th boot method. Other unrooting strats did not work for me.
Additionally, if you followed Indirect's rooting directions, make sure you have the updated rooting script file.
miniblue said:
the failed boot has to function correctly 8 times in a row to work take you back to stock. Did you go that many times.
Click to expand...
Click to collapse
Mine did a factory restore after 2 failed boots. Assuming I'm doing it correctly. Powered off then upon restart I held power and home to turn off and then it asks me if i would like to restore. It is still recognized as being rooted though.
dodgepot said:
Additionally, if you followed Indirect's rooting directions, make sure you have the updated rooting script file.
Click to expand...
Click to collapse
Yep, it is updated
albertwertz said:
if failed boot restore doesnt work, manually download and install super user apk and then use unroot app
Click to expand...
Click to collapse
Upon restore I can get the rooting script to re-root the nook but super user apk doesn't work. I even tried deleting super user and reinstalling and every time I try the unroot.apk i dont have an option to run as super user.
I have tried the unroot script also but it doesnt detect a root installation.
sounds like you never rooted then. Make sure when you tried to run the root process, you actually extracted the files and ran them in the location you extracted them to
vickca86 said:
Mine did a factory restore after 2 failed boots. Assuming I'm doing it correctly. Powered off then upon restart I held power and home to turn off and then it asks me if i would like to restore. It is still recognized as being rooted though.
Yep, it is updated
Upon restore I can get the rooting script to re-root the nook but super user apk doesn't work. I even tried deleting super user and reinstalling and every time I try the unroot.apk i dont have an option to run as super user.
I have tried the unroot script also but it doesnt detect a root installation.
Click to expand...
Click to collapse
It was likely the data wipe, because the factory restore doesn't kick in until 9th or 10th forced reset/boot interrupt. I'd try again for the restore.
albertwertz said:
sounds like you never rooted then. Make sure when you tried to run the root process, you actually extracted the files and ran them in the location you extracted them to
Click to expand...
Click to collapse
Well, I know it was rooted bc I was using adw launcher and was able to install the unroot.apk
HMG10 said:
It was likely the data wipe, because the factory restore doesn't kick in until 9th or 10th forced reset/boot interrupt. I'd try again for the restore.
Click to expand...
Click to collapse
You're right, I see that now, finally got the factory restore. Going from there to try to asses whether or not the root is still on there.
vickca86 said:
Well, I know it was rooted bc I was using adw launcher and was able to install the unroot.apk
You're right, I see that now, finally got the factory restore. Going from there to try to asses whether or not the root is still on there.
Click to expand...
Click to collapse
After a factory restore, root is gone. You have to start over for the root process, and customizing/loading apps. Just pretend you opened it up out of the packaging brand new, and go from there.
Rooting was successful, tested unroot.apk just to make sure superuser permissions worked and it did. I'm good to go.
Thanks for the help guys, miniblue my confusion about factory restore was that I kept getting a prompt to restore after doing the boot process kill 2 or 3 times and I was doing that instead of going to 8 boot process kills and letting it automatically do a factory restore.
vickca86 said:
Rooting was successful, tested unroot.apk just to make sure superuser permissions worked and it did. I'm good to go.
Thanks for the help guys, miniblue my confusion about factory restore was that I kept getting a prompt to restore after doing the boot process kill 2 or 3 times and I was doing that instead of going to 8 boot process kills and letting it automatically do a factory restore.
Click to expand...
Click to collapse
Yeah, the data wipe, which I've been calling a factory reset, only clears user data and deregisters the device. A factory restore basically fixes most problems short of messing with the hardware itself.
Related
Rooted last night, superuser was working fine but this morning I lost all superuser access. Uninstalled SU and reinstalled it. Rom manager gained access but others won't. Now even when I try to flash CWM recovery it says "an error occurred while attempting to run privileged commands!". Any ideas?
you might have to look in this thread, and get the working SU that way
http://forum.xda-developers.com/showthread.php?t=1003088
magneticzero said:
you might have to look in this thread, and get the working SU that way
http://forum.xda-developers.com/showthread.php?t=1003088
Click to expand...
Click to collapse
Thanks, I was reading over that a few minutes ago. I'll give it a try
Tried to flash that patch but I can't boot into recovery. It boots into the bootloader, I select recovery and it just goes back to the white bootloader screen. Am I missing something?
since su works with rom manager, press menu and clear cache and try to push clockwork back on your phone. also there is a option to wipe clockwork mod everytiem you update it. alot of people have success with that.
magneticzero said:
since su works with rom manager, press menu and clear cache and try to push clockwork back on your phone
Click to expand...
Click to collapse
I did that, rebooted like 10 times trying to get into recovery and for some reason I know have su permissions again.... I dunno what happened.
But how do I get into cwm to install rom's and backup/restore? I keep getting the white bootloader screen for some reason.
Sorry, double post....
ugadroid said:
I did that, rebooted like 10 times trying to get into recovery and for some reason I know have su permissions again.... I dunno what happened.
But how do I get into cwm to install rom's and backup/restore? I keep getting the white bootloader screen for some reason.
Click to expand...
Click to collapse
there is an option in rom manager to boot into clockwork recovery, but i edited my last post.. maybe you need to push clockwork again if it isnt going into recovery the manual way, might not be loading the files properly
magneticzero said:
there is an option in rom manager to boot into clockwork recovery, but i edited my last post.. maybe you need to push clockwork again if it isnt going into recovery the manual way, might not be loading the files properly
Click to expand...
Click to collapse
Seems like something might have gotten messed up. Now I lost all su permissions again. lol. I probably should unroot and do the process over again. I've tried the option in rom manager but it takes me to the bootloader screen and when I select recovery it just takes me right back.
I also had this same exact problem. The reason was I had messed something up during the root process. What happened to me is I switched the RUU's around and ended up with the wrong one. My opinion would be to re-root using the original ADB method and make sure you are using the correct RUU. If you need assistance just PM me and I will guide you step through step to re-rooting your T-Bolt.
stedrocklp said:
I also had this same exact problem. The reason was I had messed something up during the root process. What happened to me is I switched the RUU's around and ended up with the wrong one. My opinion would be to re-root using the original ADB method and make sure you are using the correct RUU. If you need assistance just PM me and I will guide you step through step to re-rooting your T-Bolt.
Click to expand...
Click to collapse
I thought for sure I used the right RUU files but it was late so I could have messed up. I would appreciate any help, I used the windows one click method. Not too familar with ADB but I have played with it a lil. PM me when ever you get a chance. Thanks bro.
Mad props to stedrocklp for all the help last night. The help that people give on this site is why it's the best.
ok so i got my replacement thunderbolt and tried to use the 3 step root tool on here and i think something went wrong. i made it to step 3, it says s off and seemed ok. i rebooted, tried to fix permissions to test and it failed. now all i get is the HTC white boot screen and thats it. i can go into bootloader (the screen with hboot, recovery, etc) and i can load up recovery but when i try to do a restore (backup from the old phone) i get an error and it fails. is it screwed? what can i do to correct this? thanks guys!
[email protected]|ice said:
ok so i got my replacement thunderbolt and tried to use the 3 step root tool on here and i think something went wrong. i made it to step 3, it says s off and seemed ok. i rebooted, tried to fix permissions to test and it failed. now all i get is the HTC white boot screen and thats it. i can go into bootloader (the screen with hboot, recovery, etc) and i can load up recovery but when i try to do a restore (backup from the old phone) i get an error and it fails. is it screwed? what can i do to correct this? thanks guys!
Click to expand...
Click to collapse
If you can get into recovery, wipe EVERYTHING (data/cache/dalvik). Then mount USB and put a rom on your SD. Flash that. If you tried to fix permissions BEFORE you installed a ROM, then you kinda skipped a step mate.
DO NOT RERUN THE ROOT METHOD. IF you have S-OFF, jut flash a ROM
cj2566 said:
If you can get into recovery, wipe EVERYTHING (data/cache/dalvik). Then mount USB and put a rom on your SD. Flash that. If you tried to fix permissions BEFORE you installed a ROM, then you kinda skipped a step mate.
DO NOT RERUN THE ROOT METHOD. IF you have S-OFF, jut flash a ROM
Click to expand...
Click to collapse
thank you for the quick reply! so there is some hope for this thing then, woohoo!
yes i have wiped everything you mentioned. how does one mount usb from that menu? from within recovery? i saw a usb option on that (is it called bootloader?) is that what your speaking of?
now as a rom i DO have the gingerjane rom from jcase on there somewhere, is that safe to flash on there to fix this? thanks again!
If you have access to recovery (as you said you do) just load it, wipe, and flash any Thunderbolt rom you put on your sdcard (or already have in your case). Whether the rom you flash will fully works or not depends on whether it is compatible with your current radio.
But as long as you have access to recovery, you are set.
it booted! thank you both.
now im positive the root failed but it says s-off and superuser does show in the app drawer. im gonna try to d/l rom manager since its not on here anymore and see if it works.
if root failed am i safe to do the three step process again?
just don't flash roms with Rom Manager. It's known to cause problems with the Thunderbolt..
[email protected]|ice said:
it booted! thank you both.
now im positive the root failed but it says s-off and superuser does show in the app drawer. im gonna try to d/l rom manager since its not on here anymore and see if it works.
if root failed am i safe to do the three step process again?
Click to expand...
Click to collapse
Not sure what "3 step process" you are referring to but I'm gonna say no.
You have recovery. You can clearly flash roms. The roms contain Superuser.apk and su binaries which means THEY are rooted. Flash a good copy of a rooted rom from recovery and you will have working SU.
If that means you have to download another copy of a rom and put it on your sdcard then do it. Point is, roms are "rooted" not the phone. You can't "root" something that doesn't have an OS. Common misconception but I'm leaving it at that.
Everything is working great now, thank you all for your guidance and support. Love my android community. Can't thank you enough.
Randomly my phone restarted (again) for no reason. After it restarted it got stuck at the loading screen with the message "failed to boot 2. starting rsd mode". So I followed the steps to flash the SBF file and it fixed it. But after restart nothing recognized super user as installed anymore (even though it was in my app drawer). So after trying to reinstall root with gingerbreak and it not working I decided the only option left was a factory reset and wiping my SD card/internal storage, and a cache wipe. Now gingerbreak gives me the message "Not sure what happened here. Either the exploit failed or the reboot failed. Please reboot manually and see if you have SuperUser". I rebooted, and no superuser. I am not sure what else I can do, gingerbreak is the only way to currently root it.
I love the hardware on this phone, but the software is as buggy as duck. I need it rooted and hacked so things work properly and it stops restarting randomly 1-4 times a day. Soooo, can someone please help me to figure out how to re-root it given my situation. What can I do next?
Thanks in advance.
mathelli said:
Randomly my phone restarted (again) for no reason. After it restarted it got stuck at the loading screen with the message "failed to boot 2. starting rsd mode". So I followed the steps to flash the SBF file and it fixed it. But after restart nothing recognized super user as installed anymore (even though it was in my app drawer). So after trying to reinstall root with gingerbreak and it not working I decided the only option left was a factory reset and wiping my SD card/internal storage, and a cache wipe. Now gingerbreak gives me the message "Not sure what happened here. Either the exploit failed or the reboot failed. Please reboot manually and see if you have SuperUser". I rebooted, and no superuser. I am not sure what else I can do, gingerbreak is the only way to currently root it.
I love the hardware on this phone, but the software is as buggy as duck. I need it rooted and hacked so things work properly and it stops restarting randomly 1-4 times a day. Soooo, can someone please help me to figure out how to re-root it given my situation. What can I do next?
Thanks in advance.
Click to expand...
Click to collapse
This May Sound Redundant, But Try SBF'ing Again Then Wipe Data/Cache. Maybe Something Didn't Get Put Back Right And It Doesn't Hurt To Try. I Don't Think The Gingerbreak.apk Is Corrupted But It's Possible To Download Another One Just To Make Sure First.
Not sure if this matters, but....
I am running on version of Android 2.2.2. I forgot to mention that, I am not sure if that matters. Either way I will try your idea and see.
MikeJ92YJ said:
This May Sound Redundant, But Try SBF'ing Again Then Wipe Data/Cache. Maybe Something Didn't Get Put Back Right And It Doesn't Hurt To Try. I Don't Think The Gingerbreak.apk Is Corrupted But It's Possible To Download Another One Just To Make Sure First.
Click to expand...
Click to collapse
I had to SBF back to stock - after you sbf you will have to boot into stock recovery and wipe data
Root with Gingerbreak
Install recovery apk
Wipe data & cache
Install ROM
Install my apps
these steps should work for you
Wrong forum, please post in the correct sections.
Tried that several times, no luck still. I also reflashed the sbf file 5 times and wiped everything and reset to factory several times too. I am not sure what else to do at this point.
mathelli said:
Tried that several times, no luck still. I also reflashed the sbf file 5 times and wiped everything and reset to factory several times too. I am not sure what else to do at this point.
Click to expand...
Click to collapse
PLEASE PLEASE PLEASE Don't Take This The Wrong Way, When You're SBF'ing You're Leaving It Plugged In Until It's Restarted And Has Said 100% For 30-60 Seconds Just To Be Sure? Also Your USB Cable Is It Plugged Into The Back Ports Of The Computer And Not The Front Or Top?
MikeJ92YJ said:
PLEASE PLEASE PLEASE Don't Take This The Wrong Way, When You're SBF'ing You're Leaving It Plugged In Until It's Restarted And Has Said 100% For 30-60 Seconds Just To Be Sure? Also Your USB Cable Is It Plugged Into The Back Ports Of The Computer And Not The Front Or Top?
Click to expand...
Click to collapse
I was hoping plugging the USB into the back of the computer was the piece I was missing, but I tried that now along with formatted everything, factory reset, etc, and it still won't work.
So to answer all of your questions MikeJ92YJ:
Yes to everything, but still no possibility of rooting it using Gingerbreak.
mathelli said:
I was hoping plugging the USB into the back of the computer was the piece I was missing, but I tried that now along with formatted everything, factory reset, etc, and it still won't work.
So to answer all of your questions MikeJ92YJ:
Yes to everything, but still no possibility of rooting it using Gingerbreak.
Click to expand...
Click to collapse
This Is My Last Thought. Use ADB And Push It On.
http://forum.xda-developers.com/showpost.php?p=13084221&postcount=2
I changed from an iPhone 4 in May to the Samsung Note. On my iPhone I would immediately jailbreak and install MyWi. In my research to do the same on the note I ran across a rooting tutorial for my device and followed the instructions http://www.androidauthority.com/galaxy-note-att-i717-root-without-increasing-flash-counter-61325/ (I am not positive, but I feel confident this is the one I followed). I installed Superuser and Titanium Backup, did a backup of ATT connection manager, then removed it. Tethering worked like a charm. This has worked and I had no issues until Friday June 14th.
On Friday, everytime I opened an app on my phone I would get a Force Close. I restarted the phone and watched as it repeatedly happened after every cycle. Believing that installing Droid VNC Server was the issue, the last app I had installed, I removed it successfully and included others I didn’t use. Upon reboot, I noticed the notification of App Updates and a missed call. Checked the application list and noticed that all of the apps I had just removed were still there. I have a ton of pics and videos and thought that I should back them up immediately before I deleted them, prepared for the worst. I was able to do that. I deleted them all, nothing in the gallery. When the phone crapped out again and rebooted, all apps and all pictures back.
I formatted the USB Storage, seemed to delete nothing and also showed the same amount of used space as before.
Time for a restore. I know now that the recovery partition is gone and so a Wipe/reset is fruitless. No problem. I know how to flash the rom. I used this method with Odin. http://forum.xda-developers.com/showthread.php?t=1506330
Everything seemed to work successfully, but upon reboot I get the same app updates notification and the same missed call notification. The same frozen state my phone was in when the issue started on Friday. WTH!
I have everything backed up. How do I get back to stock? I could care less about the counter. I just want my phone to be usable again.
ryantaylor16 said:
I changed from an iPhone 4 in May to the Samsung Note. On my iPhone I would immediately jailbreak and install MyWi. In my research to do the same on the note I ran across a rooting tutorial for my device and followed the instructions http://www.androidauthority.com/galaxy-note-att-i717-root-without-increasing-flash-counter-61325/ (I am not positive, but I feel confident this is the one I followed). I installed Superuser and Titanium Backup, did a backup of ATT connection manager, then removed it. Tethering worked like a charm. This has worked and I had no issues until Friday June 14th.
On Friday, everytime I opened an app on my phone I would get a Force Close. I restarted the phone and watched as it repeatedly happened after every cycle. Believing that installing Droid VNC Server was the issue, the last app I had installed, I removed it successfully and included others I didn’t use. Upon reboot, I noticed the notification of App Updates and a missed call. Checked the application list and noticed that all of the apps I had just removed were still there. I have a ton of pics and videos and thought that I should back them up immediately before I deleted them, prepared for the worst. I was able to do that. I deleted them all, nothing in the gallery. When the phone crapped out again and rebooted, all apps and all pictures back.
I formatted the USB Storage, seemed to delete nothing and also showed the same amount of used space as before.
Time for a restore. I know now that the recovery partition is gone and so a Wipe/reset is fruitless. No problem. I know how to flash the rom. I used this method with Odin. http://forum.xda-developers.com/showthread.php?t=1506330
Everything seemed to work successfully, but upon reboot I get the same app updates notification and the same missed call notification. The same frozen state my phone was in when the issue started on Friday. WTH!
I have everything backed up. How do I get back to stock? I could care less about the counter. I just want my phone to be usable again.
Click to expand...
Click to collapse
did you try wiping Catche and Dav?
Wipe Catch > Wife Davlik > Fix Permision, then reboot ..
see what happens ..
Not a noob, but here is where i am lost
I booted in to recovery, chose to Wipe/Erase . I see no option to Wipe Davlik except for in SuperUser and there it is a paid option, not sure where to find Fix Permission and then reboot?
I am assuming these are all options for CWM. I attempted to put CWM on an SD card last night and install from ZIP, but Recovery does not seem to see the SD card.
Are these options that are available for CWM, if so I will push through until I get it to work, but I have had no luck to this point.
UltimateEnd said:
did you try wiping Catche and Dav?
Wipe Catch > Wife Davlik > Fix Permision, then reboot ..
see what happens ..
Click to expand...
Click to collapse
ryantaylor16 said:
I booted in to recovery, chose to Wipe/Erase . I see no option to Wipe Davlik except for in SuperUser and there it is a paid option, not sure where to find Fix Permission and then reboot?
I am assuming these are all options for CWM. I attempted to put CWM on an SD card last night and install from ZIP, but Recovery does not seem to see the SD card.
Are these options that are available for CWM, if so I will push through until I get it to work, but I have had no luck to this point.
Click to expand...
Click to collapse
no need to go back to stock .
try reflashing whichever ROM you desire...
its always wise to follow every little STEP given by the DEV .
to wipe dav you go to advance and it should be there..
Sorry, still need assist
UltimateEnd said:
no need to go back to stock .
try reflashing whichever ROM you desire...
its always wise to follow every little STEP given by the DEV .
to wipe dav you go to advance and it should be there..
Click to expand...
Click to collapse
I have attempted to Flash ROMs I don't desire just to move forward. They all flash and pass in Odin but on reboot I still have my default screen. Unfortunately, I want to go back to stock. I have done plenty of research and need something more to push on to the next thing. I am looking at phone and there is not an Advanced option in recovery. I have read there are options in CWM but I am looking at what I believe is the stock recovery options.
ryantaylor16 said:
I have attempted to Flash ROMs I don't desire just to move forward. They all flash and pass in Odin but on reboot I still have my default screen. Unfortunately, I want to go back to stock. I have done plenty of research and need something more to push on to the next thing. I am looking at phone and there is not an Advanced option in recovery. I have read there are options in CWM but I am looking at what I believe is the stock recovery options.
Click to expand...
Click to collapse
after you are rooted ,
you should have nothing to do with Odin.
and also, if you were stuck on your phone trying to boot up, chances are you keep downloading a bad ROM..
happen to me before..a ROM that was suposed to be 192MB,
would finish on 158MB
someone else may be able to help you get back to stock ROM..i havent had the chance to ever wanna go back to stock so i wouldnt know for sure.
sorry and good luck .
Still Worried. Still Stuck
ryantaylor16 said:
Time for a restore. I know now that the recovery partition is gone and so a Wipe/reset is fruitless. No problem. I know how to flash the rom. I used this method with Odin to undo root. http://forum.xda-developers.com/showthread.php?t=1506330
Everything seemed to work successfully, but upon reboot I get the same app updates notification and the same missed call notification. The same frozen state my phone was in when the issue started on Friday. WTH!
I have everything backed up. How do I get back to stock? I could care less about the counter. I just want my phone to be usable again.
Click to expand...
Click to collapse
OK, I am still stuck and so I will wait for someone else to reply. Thanks for your help though
ryantaylor16 said:
OK, I am still stuck and so I will wait for someone else to reply. Thanks for your help though
Click to expand...
Click to collapse
U need to do what he said he is every well known on xda...install cwm to ur internel memory not sd card and ur phone has to see it!
Btw if u want to get back to bare bone stock look for att b4 tar file if u cant find it let me know ill link it
cm9
Use this?
JB calhoun said:
U need to do what he said he is every well known on xda...install cwm to ur internel memory not sd card and ur phone has to see it!
Btw if u want to get back to bare bone stock look for att b4 tar file if u cant find it let me know ill link it
cm9
Click to expand...
Click to collapse
Would you say this is a good tutorial to follow?
http://rootgalaxynote.com/galaxy-no...-on-att-galaxy-note-sgh-i717-belltelusrogers/
So, maybe I am a newb. I have followed the instructions to install CWM on my device and it even says it was successful. I am doing it from ODIN. See the file I downloaded here. Says it was successful but holding the volume up and then power button. NO CWM.
I am truly frustrated but I want my phone back. Can someone link me to the stupid people posts so I can get my phone working again?
bump
CWM Problems
Hi,
Have you looked at these posts? Sounds like you may be using the
wrong key combo to start CWM?
http://forum.xda-developers.com/showthread.php?t=1586223
http://forum.xda-developers.com/showthread.php?t=1483113
Are you confident that your uSD card hasn't been corrupted?
Peter
ryantaylor16 said:
So, maybe I am a newb. I have followed the instructions to install CWM on my device and it even says it was successful. I am doing it from ODIN. See the file I downloaded here. Says it was successful but holding the volume up and then power button. NO CWM.
I am truly frustrated but I want my phone back. Can someone link me to the stupid people posts so I can get my phone working again?
Click to expand...
Click to collapse
ryantaylor16 said:
bump
Click to expand...
Click to collapse
You now have a custom recovery(according to Odin). The problem is, you're doing the wrong key combo as stated above. You can also go to the market and grab FJ's power tool. You can boot into recovery directly from the app. Good luck.
Certainly I am not this dumb..... am I
froidroid said:
You now have a custom recovery(according to Odin). The problem is, you're doing the wrong key combo as stated above. You can also go to the market and grab FJ's power tool. You can boot into recovery directly from the app. Good luck.
Click to expand...
Click to collapse
Still having issues. Here is the deal.
I have the phone in Download mode
https://www.dropbox.com/s/dnk6ekjqp9vddev/2012-06-19 19.40.01.jpg
I load the CWM Recovery in the PDA box. Start the flash, get a pass. All looks good to me.
https://www.dropbox.com/s/5q4hayf35mm26wr/odin-success.PNG
I immediately attempt to access CWM Recovery by holding the power, vol+ and vol- and still get the default recovery
https://www.dropbox.com/s/d176blydonlvrlu/2012-06-19 20.13.42.jpg
I am so confused as to what I am doing wrong.
Unfortunately those pics aren't loading for me. Try again with the pic of recovery and the file you're flashing. Thanks. If you still have stock recovery then maybe that's what you're flashing in error.
Try volume up + down and power button. When phone vibrates, release power button but keep holding volume buttons until you are in cwm.
I would use Odin to flash cwm touch recovery from pda, then load a rom via cwm. Using that method you don't even need to root because it's all done at bootloader level and root is built in to the custom rom you flash
SGH-i717 mesosphere-remix
I took the OTA MJ7 4.3 update and then tried doing the M1I root technique and soft bricked my phone. I know some have tried that and others have just had issues where their phone won't boot after taking the OTA. I will share the steps I did that fixed my phone!
1. Place the update.zip from this thread (http://forum.xda-developers.com/showthread.php?t=2502591) on an SD card. You may have to put it in another phone or into an SD card reader.
2. Press and hold volume up + home button for a couple of seconds
3. While still holding those buttons press and hold the power key until the phone vibrates, then release the power key only
4. Your phone should boot into Android System Recovery. Go to Apply update from external sd card.
5. Select update.zip and apply it
6. It will reboot your phone, it will still not boot properly. Remove the battery and follow steps 2-3 again.
7. This time, select Wipe data/factory reset.
8. Once complete reboot your phone, it will boot this time!
I'm so excited my S4 works again!! Hope this helps you guys!
antisomnic said:
I took the OTA MJ7 4.3 update and then tried doing the M1I root technique and soft bricked my phone. I know some have tried that and others have just had issues where their phone won't boot after taking the OTA. I will share the steps I did that fixed my phone!
1. Place the update.zip from this thread (http://forum.xda-developers.com/showthread.php?t=2502591) on an SD card. You may have to put it in another phone or into an SD card reader.
2. Press and hold volume up + home button for a couple of seconds
3. While still holding those buttons press and hold the power key until the phone vibrates, then release the power key only
4. Your phone should boot into Android System Recovery. Go to Apply update from external sd card.
5. Select update.zip and apply it
6. It will reboot your phone, it will still not boot properly. Remove the battery and follow steps 2-3 again.
7. This time, select Wipe data/factory reset.
8. Once complete reboot your phone, it will boot this time!
I'm so excited my S4 works again!! Hope this helps you guys!
Click to expand...
Click to collapse
Cool! Glad you are up and running.
The MI1 root method flashed a MI1 ROM, so if you are on MJ7, you create a soft brick by trying to root.
Don't do that!!!!
Right. I figured that out the hard way. At least there is a solution
Sent from my SCH-I545 using xda app-developers app
Were you able to boot into android recovery while soft bricked? I experienced the same issue and booted into recovery (volume up, center button, and power button while power is off) and simply did a factory reset. I was able to keep root and fix whatever had gone wrong.
Nevermind, read wrong.
Can be deleted.
tried this.
instead of recovery i get : firmware upgrade encountered an issue. please select recovery mode in kies
slackwaresupport said:
tried this.
instead of recovery i get : firmware upgrade encountered an issue. please select recovery mode in kies
Click to expand...
Click to collapse
I had this happen too. I had to use ODIN to restore to factory MI1 then did OTA to MJ7.
teinwhite said:
I had this happen too. I had to use ODIN to restore to factory MI1 then did OTA to MJ7.
Click to expand...
Click to collapse
just tried to flash ml1.. failed on system.img.ext4
slackwaresupport said:
just tried to flash ml1.. failed on system.img.ext4
Click to expand...
Click to collapse
Did you take the MJ7 update and then try to go back to Ml1? I thought that is the error you get if you do try to go back.
-Lawless said:
Did you take the MJ7 update and then try to go back to Ml1? I thought that is the error you get if you do try to go back.
Click to expand...
Click to collapse
I was in that boat. Took the OTA and foolishly tried Root de la Vega. Couldn't flash back to MI1 (failed as described) but the new no-wipe MJ7 Odin file saved the day. Good as new (but still unrooted).
http://forum.xda-developers.com/showthread.php?t=2507217
I got root with this post: http://forum.xda-developers.com/showpost.php?p=47187227&postcount=84
As other say, it seems to be bad.
I cleared this post and if you wish, you can check the first line and open the post to see how it goes.
TheJumpingBean said:
You will prolly get banned for this! LOL Either way, it does work. I did it on mine, and all of that is true.
Click to expand...
Click to collapse
Why would i get banned ? Did i do something wrong by sharing the knowledge? I have not taken credit for this and also added the link to the post so it can be verified ;
OK, i removed the link and whoever needs it, can use Google to find it.
Trak-X said:
Why would i get banned ? Did i do something wrong by sharing the knowledge? I have not taken credit for this and also added the link to the post so it can be verified ;
OK, i removed the link and whoever needs it, can use Google to find it.
Click to expand...
Click to collapse
No there were some xda admins or w/e that said the links 2 this root arent allowed on XDA ne more. Not sure why... I used it and it worked perfectly. oh well. Sowwy
Moderator @Naddict posted this one post prior in that thread. Read up and learn about the risk you are exposing yourself to.
Be aware that as of this moment XDA has deemed the Kingo root method and Vroot method are not allowed on XDA. There are concerns with the information which is collected during the root method by the exploit. It is not about a continuous malware which may affect your device but about important information shared about your device, serial numbers etc during the root process which could be huge securities issues. You have all been warned.
Click to expand...
Click to collapse
This post, courtesy of open1your1eyes, provides some detail from the bright guys that keep us rooted and happy.
We finally have some details on these root methods:
https://twitter.com/TeamAndIRC/status/397767301811802112
TLDR: Uses "Romaster" root method
Click to expand...
Click to collapse
I would take their caution to heart if I was in your position.
--OctOS Powered VZW GS4 Dev Edition
Nice to see the wheels turning here guys. Thumbs up
I dont know what to think of this. I did the root the first day, and haven't had any problems. I have talked to a few devs and Android engineers who have checked it out and don't think its a threat. I did manage to update mine to SuperSU from the chinese superuser, just in case...
So, I dont know enough to tell you if it is or isnt dangerous, but I can tell u that Im on like day 5 with no issues. I went ahead the first day and installed DroidWall. DroidWall doesnt have any records of su or the chinese superuser trying to access anything, and netstat doesnt show that the su or superuser apps are listening for connections.
I kinda wish we could get some closure on whats happening...
teinwhite said:
I had this happen too. I had to use ODIN to restore to factory MI1 then did OTA to MJ7.
Click to expand...
Click to collapse
Im go the problem where it says Firmware upgrade encountered an issue. how do i fix this? and can u provide a link for the stock firmwares please the mi1 and mj7.
TheJumpingBean said:
I dont know what to think of this. I did the root the first day, and haven't had any problems. I have talked to a few devs and Android engineers who have checked it out and don't think its a threat. I did manage to update mine to SuperSU from the chinese superuser, just in case...
So, I dont know enough to tell you if it is or isnt dangerous, but I can tell u that Im on like day 5 with no issues. I went ahead the first day and installed DroidWall. DroidWall doesnt have any records of su or the chinese superuser trying to access anything, and netstat doesnt show that the su or superuser apps are listening for connections.
I kinda wish we could get some closure on whats happening...
Click to expand...
Click to collapse
How'd you get supersu to work and remove Chinese superuser?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Hey all, I got a Verizon Galaxy S4 16 gigs. I did the 4.3 OTA, then tried to go back to 4.2.2. I guess that soft bricked it. So do I have to use the MJ7 firmware to make my phone usable again? And if that works, is there any way to go back to 4.2.2? What do I do if it doesn't work?
Update: This worked beautifully, I'm now back to 4.3.