Hi all,
I have a Rogers Galaxy S3 i747M and I tried installing clockworkmod several times on it. Each time Odin showed 'success' and the binary counter increased however whenever I would go into recovery it would go into the stock s3 recovery mode. Any solutions or similar experiences?
Thanks!
The S3 has a fail safe where by when it detects you have flashed a custom recovery it will automaticly restore the stock one when you try to reboot the phone.
As explained here by teamepic http://www.epiccm.org/2012/06/cwm-recovery-on-all-sgs3-lte-variants.html Under step 9 their root files includes a removal of the automatic restore of the stock recovery so it will maintain your custom one. And the way to actually push whatever kind of root method you wish you need to make sure Odin is not set to auto reboot. When done flashing do a battery pull then do the Vol Up+Power+Home key method of booting directly into recovery this gets you into the custom one and not activate the restore feature. (however once you reboot normally the restore gets triggered so you will need to use team epics method to get rid of it or:
Alternatively you could also manually copy the custom recovery via the Disk Dupe command, and the restore feature does not get activated when doing it this way. (requires a rooted device)
Thanks bro, The procedure worked,
Now installing CM10 on my second S3
I'm a newbie and I am in trouble. I have a rooted Nexus 7 2013 and I have a TWRP Nandroid backup which I had copied to my WIndows PC.
Now my Nexus 7 crashed and won't go beyond the X on bootup. The Nandroid and Titanium backups are on my windows PC.
How do I restore the Nexus 7 to working status by restoring from the Nandroid backup and data I have copied to the PC?
Please help. Thanks.
Guys, someone please help.
I don't know how to get out of this mess. I'm still stuck on X.
I can power off the Nexus 7 and power to the recovery screen where I find Teamwin's menu.
I restored (several times) the nandroid backups I found on this menu (they were all done after the last reset) but rebooting then just gets me back to the X screen and no further.
I have a good nandroid backup on my PC but no way to get it into the tablet so TWRP can restore from it. Is there a way to transfer a file to or from the tablet when it will not boot completely?
The advanced screen of the Teamwin recovery menu lets me access a file manager. Is there any way I can use it to move files on or off the tablet to "anything" else?
The last time the boot froze on the X screen, I was able to go to the recovery screen with the android on his back and an X and from there to a reset. But this time I cannot get there and the recovery screen gets me to the Teamwin recovery menu. This has a wipe option. Will this reset the Nexus if selected. Will it remove root? I don't want to go through rooting it all over again.
Essentially I just want to do 2 things:
a) extract data from the stuck Nexus 7
b) reset and restore the nandroid backup I have on my pc.
Please help.......
Bill235 said:
Guys, someone please help.
I don't know how to get out of this mess. I'm still stuck on X.
I can power off the Nexus 7 and power to the recovery screen where I find Teamwin's menu.
I restored (several times) the nandroid backups I found on this menu (they were all done after the last reset) but rebooting then just gets me back to the X screen and no further.
I have a good nandroid backup on my PC but no way to get it into the tablet so TWRP can restore from it. Is there a way to transfer a file to or from the tablet when it will not boot completely?
The advanced screen of the Teamwin recovery menu lets me access a file manager. Is there any way I can use it to move files on or off the tablet to "anything" else?
The last time the boot froze on the X screen, I was able to go to the recovery screen with the android on his back and an X and from there to a reset. But this time I cannot get there and the recovery screen gets me to the Teamwin recovery menu. This has a wipe option. Will this reset the Nexus if selected. Will it remove root? I don't want to go through rooting it all over again.
Essentially I just want to do 2 things:
a) extract data from the stuck Nexus 7
b) reset and restore the nandroid backup I have on my pc.
Please help.......
Click to expand...
Click to collapse
Just choose the wipe option in twrp.
That should allow you to start android.
Then copy your backup from PC to virtual sdcard, reboot to twrp, and restore.
You can copy files while in recovery but it is more involved so I would try this first.
sfhub said:
Just choose the wipe option in twrp.
That should allow you to start android.
Then copy your backup from PC to virtual sdcard, reboot to twrp, and restore.
You can copy files while in recovery but it is more involved so I would try this first.
Click to expand...
Click to collapse
But will it remove the root I worked so hard to get?
If you worked hard to get root on a Nexus device you did something wrong. It should be as simple as unlocking the bootloader (already done), flashing a custom recovery (already done), and flashing the SuperSU ZIP file (this is the only step you'd need to repeat).
That said, doing a factory reset should not remove root. Even if it does, it would be restored when you restored your rooted Nandroid.
raptir said:
If you worked hard to get root on a Nexus device you did something wrong. It should be as simple as unlocking the bootloader (already done), flashing a custom recovery (already done), and flashing the SuperSU ZIP file (this is the only step you'd need to repeat).
That said, doing a factory reset should not remove root. Even if it does, it would be restored when you restored your rooted Nandroid.
Click to expand...
Click to collapse
Easy for an expert. I'm a newbie. I used the WUGfresh toolkit and it took multiple frustratng attempts and forever for it to finally download the correct adb drivers that would recognize the Nexus 7. Then all went smoothly.
But back to the present. I'm all fine now (till the next time the Nexus 7 crashes on me). For other newbies like me who run into this problem and need simple instructions here is what I did.
The first time this crash with the boot stuck on the X screen happened, going to the recovery screen (Power button + Volume up simultaneously) showed me the android on his back with a red triangle. Pressing power button and briefly volume up gave me the option to reset the tablet without removing root. Because I was traveling and did not have my TWRP backups with me (they were on my laptop 1,000 miles away) this removed all my data and I had to re-install all my apps and everything again.
The second time this happened, the recovery screen took me to the TWRP recovery screen. TWRP recovery had apparently survived the crash. I needed to save my data before reseting the tablet again. By trial and error I discovered that the TWRP menu has under the Advanced Tab a file manager. also discovered that if you connect a flash device to the tablet's usb port the TWRP file manager could read and write to it (!!!) in a folder called usb-otg (but not to my windows laptop). I copied what I wanted to save to the flash drive. Then I used the "wipe" tool to return the tablet to android.
I installed a free app, Recovery Manager, to reinstall TWRP recovery. Copied my previous TWRP nandroid backup to the tablet and restored everything as it was.
Easy as pie if you know how. I hope this helps some other befuddled user.
sfhub and raptir: Do you know what can be done to prevent this from happening again? Could Google Play being conected to in Europe after it was used to being to conected to in the US cause the problem? Both times the crashes happened shortly after I used the tablet in Europe and the the second time after I used it for the first time in the US.
Bill235 said:
sfhub and raptir: Do you know what can be done to prevent this from happening again? Could Google Play being conected to in Europe after it was used to being to conected to in the US cause the problem? Both times the crashes happened shortly after I used the tablet in Europe and the the second time after I used it for the first time in the US.
Click to expand...
Click to collapse
I can't say for sure what is happening in your case, but in my experience getting stuck on X means your user data got corrupted. The cases I've seen fall into 2 categories:
1) faulty EMMC flash memory. Sometimes if you wipe a couple of times the bad blocks get locked out and you don't see the problem anymore. Other times, they keep coming back. In the latter case, return/exchange/rma the unit
2) android crashes (random reboot) and unfinished writes are not completed corrupting the user data. They put in code in the latest ROM to mitigate this so if you think you are suffering from this type of corruption, install the latest ROM if you haven't done so already.
Thank you for the excellent and clear reply. I'll hope the 2 wipes I did may have gotten rid of my bad blocks.
I'll update to the latest stock rom too.
Thank you.
Bill235 said:
Thank you for the excellent and clear reply. I'll hope the 2 wipes I did may have gotten rid of my bad blocks.
I'll update to the latest stock rom too.
Thank you.
Click to expand...
Click to collapse
The updating part got me in trouble.......
I accepted the system update and am now running android 4.3 but lost root.
So I went back to the WUGfresh Nexus Root kit. Updated everything, am now on version 1.7.3 of the toolkit, followed all the instructions (uninstalled and re-installed driveers) and got stuck on the same problem I had the first time I tried rooting: the adb : step3 of the full driver test. adb device not found .
I did reboot twice, am using the oem asus cable, etc. What a pain!!
Unfortunately I am dependant on the toolkit because I do not know enough to root manually.
Suggestions? Thanks.
Bill235 said:
The updating part got me in trouble.......
I accepted the system update and am now running android 4.3 but lost root.
So I went back to the WUGfresh Nexus Root kit. Updated everything, am now on version 1.7.3 of the toolkit, followed all the instructions (uninstalled and re-installed driveers) and got stuck on the same problem I had the first time I tried rooting: the adb : step3 of the full driver test. adb device not found .
I did reboot twice, am using the oem asus cable, etc. What a pain!!
Unfortunately I am dependant on the toolkit because I do not know enough to root manually.
Suggestions? Thanks.
Click to expand...
Click to collapse
So you're stock 4.3 now? Rooting manually isn't hard bud, setting up the toolkit is harder IMO.
You just need to download and install the Android SDK. Then download a custom recovery .img file, and a SuperSU flashable zip. Put the SuperSu flashable zip on your /sdcard. You'll then boot into the bootloader, open a command prompt and change directories to your Android SDK (Ex. mine is at C:\sdk\platform-tools) and run the command: fastboot flash <name of recovery file>.img
Then reboot into recovery, flash the SuperSU zip, reboot, done. You're rooted. There are plenty of How To's stickied in the General Forums for the N7 here.
RMarkwald said:
So you're stock 4.3 now? Rooting manually isn't hard bud, setting up the toolkit is harder IMO.
You just need to download and install the Android SDK. Then download a custom recovery .img file, and a SuperSU flashable zip. Put the SuperSu flashable zip on your /sdcard. You'll then boot into the bootloader, open a command prompt and change directories to your Android SDK (Ex. mine is at C:\sdk\platform-tools) and run the command: fastboot flash <name of recovery file>.img
Then reboot into recovery, flash the SuperSU zip, reboot, done. You're rooted. There are plenty of How To's stickied in the General Forums for the N7 here.
Click to expand...
Click to collapse
Will look into your suggestions later because I am rooted again. It was the adb drivers again. The universal ones just would not work for me. The Samsung signed drivers on the other hand worked smoothly and then the toolkit ran smoothly and I am rooted. But it wiped out my TWRP recovery so I will re-install that next.
Thanks for the help.
About your advice, than you. But as a newbie I need clearer instructions. "download and install the Android SDK". Where? to the pc or the tablet? etc.
I need to learn more so I don't keep getting into these ridiculous binds!
Bill235 said:
Will look into your suggestions later because I am rooted again. It was the adb drivers again. The universal ones just would not work for me. The Samsung signed drivers on the other hand worked smoothly and then the toolkit ran smoothly and I am rooted. But it wiped out my TWRP recovery so I will re-install that next.
Thanks for the help.
About your advice, than you. But as a newbie I need clearer instructions. "download and install the Android SDK". Where? to the pc or the tablet? etc.
I need to learn more so I don't keep getting into these ridiculous binds!
Click to expand...
Click to collapse
Review the General forum for the N7 2013 here, as there are threads stickied to the top of that forum which has write-ups and video how to's that'll explain it all. I suggest to review those FIRST before you try doing things just so you can get a picture of what's going on. It may seem like a lot, but once you do it, it really is not.
The Android SDK is installed on your computer.
I rooted my phone via Kingo and installed TWRP. Everything was fine. Installed various roms (CM 11, Jedi, Slim, Wicked, etc) Anyways I decided I wanted to go back to factory unrooted state. So I had put up a message on the forum asking how. Odin seemed like the popular and easiest way so I download the stock rom and put my phone into download mode. Clicked on PDA and selected the md5 file. Ran Odin and it said it was successful (Said Pass when done). Anyways my phone rebooted and now it goes through the Samsung logo and into the T Mobile logo where I hear the T-Jingle but it just stays on that screen. I did try and redo Odin and ran into the same results. I can get into Download Mode and Recovery Mode. By the way Recovery is back to the stock version.
Any help would be appreicated.
I figured it out. I went into the stock recovery and wiped everything and then installed the stock rom via zip and it worked fine after that .
Sent from my SM-N900T using Tapatalk
Hello everyone,
I'm relatively new at rooting and just so happen the note 10.1 2014 is my first guinea pig.
First off, I have successful rooted my note via Odin 3.09 with CF-autoroot with autorootp600mj4.tar.md5 and stockrecoverymj4.tar.md5. Rootchecker shows that it's rooted.
Next I installed Titanium backup and back up and then uninstall all 5 files of Knox securities.
Next I installed GooManager and installed TWRP from OpenSourceRecovery option and then rebooted with recovery.
So now is where the problem starts. Whenever I tried rebooting into recovery, I keep getting the Android recovery system (with red triangle sign and a laying down android picture).
Here's some method that I did to try and fix this.
1. Manually reboot recovery ( Did not work) goes into Android recovery system again.
2. I reinstalled TWRP again using GooManager, still doesn't work.
3. Downloaded the appropriate TWRP .tar files for Samsung galaxy note 10.1 2014 from TWRP main site and flash with Odin. I got a Pass!. Then when I do a reboot recovery, it goes into the Android recovery system again.
So far I don't know what I'm doing wrong. I've checked to make sure every step is correct, especially when I was rooting (E.g. making sure USB debugging is enabled, open source is enable, and so on)
I've tried to find my solution via google but to no avail. If you have any suggestions, it will be greatly appreciated. Thank you.:good:
I had same issue. You have to install it with Odin.
Sent from my SM-P600 using XDA Premium HD app
Simply flash via Odin, but untick " Auto Reboot " within odin before flashing.
Reboot manually into recovery , you will get a permanent TWRP
Got it
Thank for reassuring me that it can be done.
I found out the problem. The tar files from TWRP that I donwloaded was the wrong version. TWRP version was openrecovery-twrp-2.6.3.3-lt03wifiue.img. And I used that to flash on Odin and it worked thereafter. I hope this will help other people who have similar issues.
I have a Samsung Galaxy S3 AT&T and for about a year and a half always wanted to root it but had no idea how. I had an iPhone a while back and used to jailbreak it I became an expert at it. Rooting is not so easy compared at least with the problems I've been experiencing
I started by watching hundreds of root videos and ended up rooting it with Odin and Kit Kat tar file im not sure of the specific file but I'm almost 100% it was my version 4.4.2 that I flashed.
After I did this I downloaded the basics and tried to get TWRP but gooManager wasnt working for some reason.
I tried to flash the Cyanongen 11 onto my phone using the installer for the comp and on google play store and it worked up until the end I got the dead droid symbol for a bit and it finished downloading to show the "ROM may flash stock recover on boot. Fix?" error message and I selected no and "Root Access Possibly Lost Fix?" I also selected no. My phone booted with no custom rom still rooted and most of my apps are unresponsive and close randomly except facebook and youtube.
I decided I wanted to return it to stock rom and try again but when I downloaded the stock tar file and tried to flash it I got this
I'm not sure what to do because I cant return it to stock rom, clockmod recovery has stopped working, and every video I watch about how to fix it is only making it worse.
If you have any idea what I can do or what I'm doing wrong let me know.
Odin failed because you cannot flash older firmware. Your best bet is to reflash recovery via Odin, then if you want stock go to enewman17's stock rom/system dump thread in development and flash the rom and factory reset.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
DocHoliday77 said:
Odin failed because you cannot flash older firmware. Your best bet is to reflash recovery via Odin, then if you want stock go to enewman17's stock rom/system dump thread in development and flash the rom and factory reset.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
I tried to flash cwm recovery onto my phone usb debugging selected and now odin doesnt even show that my phones recognized. This is so frustrating.
I suggest installing Philz Touch recovery via Odin and using Philz to flash a custom ROM to at least get your phone up and running.
devito35 said:
I tried to flash cwm recovery onto my phone usb debugging selected and now odin doesnt even show that my phones recognized. This is so frustrating.
Click to expand...
Click to collapse
If Kies is on your computer, remove it. Have you tried reinstalling drivers?
Sent from my SAMSUNG-SGH-I747 using Tapatalk