I rooted via Qbkings method. Odin 3.04, I left auto reboot checked, and unchecked f. Reset time. Loaded the clockworkmod tar in the pda slot and loaded. I pulled the cord and battery as soon as it said passed. Reinstalled the battery and into recovery. Clockwork recovery. Then I flashed the clockwork zip. Reboot.
Then I downloaded and installed busybox, and opened superuser and updated the binary.
Problem is when I power the device off and reboot into recovery, the stock android recovery loads instead of Clockwork.
Any help with what I may have done wrong? I did download the Samsung usb drivers and everything installed fine.
Thanks
Rob the plumber said:
I rooted via Qbkings method. Odin 3.04, I left auto reboot checked, and unchecked f. Reset time. Loaded the clockworkmod tar in the pda slot and loaded. I pulled the cord and battery as soon as it said passed. Reinstalled the battery and into recovery. Clockwork recovery. Then I flashed the clockwork zip. Reboot.
Then I downloaded and installed busybox, and opened superuser and updated the binary.
Problem is when I power the device off and reboot into recovery, the stock android recovery loads instead of Clockwork.
Any help with what I may have done wrong? I did download the Samsung usb drivers and everything installed fine.
Thanks
Click to expand...
Click to collapse
You need to get rid of the recovery-from-boot.p file located in the system. Flashing this will do it for you
http://k0nane.info/rom/ecm/TeamEpic-Root-from-Recovery-v5.zip
Thanks! I tried for a couple hours to figure it out. Thanks again
Sent from my SPH-L710 using Tapatalk 2
Related
Hi i have the following error :
When i try to click on WI-FI button comes up the following
prevention information
the device has detected an application attempting unppermitted actions and has stopped loading.To protect your device it is recomended you reboot.
I have rooted my phone using the topic here
http://forum.xda-developers.com/showthread.php?t=2258633
i had to load the
http://k0nane.info/rom/SGH-M919-UVUAMDB-k0nane.7z
file first cos i was getting an failure when installing the superuser using odin 3.0.7
my recovery is TWRP 2.5.0.0 and i am on wicked v1
Anyone else have this issue?
I had the same issue if you check the build number and the baseband version they are not the same. If you re-odin the MDL build http://k0nane.info/rom/M919UVUAMDL_M919TMBAMDL_TMB.zip again then WIFI should work again. I got it rooted after that by doing the following:
1. Load the OUDHS CWM-Based Recovery 1.0.3.3 for T-Mo GS4, via odin uncheck auto reboot and goto to recovery http://k0nane.info/rom/OUDHS-Recovery-jfltetmo-1.0.3.3.tar
2. Install Chainfire's SuperSU http://www.shabbypenguin.com/Android/Scripts/Nexus-Files/Root/SuperSU-v1.25+.zip then
3 Install [KERNEL] Stock Touchwiz MDB - SetUID Restriction Removed http://d-h.st/GcM
Between installs make sure you wipe the cache and davik cache
then you reboot you should be rooted with the newest update MDL minus the kernel lock
yes its not same the build and the baseband
Is it possible to be done using the twrp?
other recovery was little difficult?
can u send me the links i need please i just don't want to mess around and brick my phone
Thanks a lot
kaniebas said:
yes its not same the build and the baseband
Is it possible to be done using the twrp?
other recovery was little difficult?
can u send me the links i need please i just don't want to mess around and brick my phone
Thanks a lot
Click to expand...
Click to collapse
Check my post again, I couldn't get TWRP to work at first but it maybe i did not uncheck the the auto reboot box when I did that. Once the the recovery is loaded via odin you need to pull the battery then do the home-up volume-power to get into the recovery. I notice TWRP was a bit too sensitive and could not scroll down the list of folders to get to the zip files
dhonzik said:
Check my post again, I couldn't get TWRP to work at first but it maybe i did not uncheck the the auto reboot box when I did that. Once the the recovery is loaded via odin you need to pull the battery then do the home-up volume-power to get into the recovery. I notice TWRP was a bit too sensitive and could not scroll down the list of folders to get to the zip files
Click to expand...
Click to collapse
i manage to install CWM using odin and when i rooted it i install goo manager ant now i am on TWRP
I've tried installing all three recoveries using Odin, but for some reason none are working and now when I try and boot into recovery it just restarts the phone. Anyone know what I should do?
oasad92 said:
I've tried installing all three recoveries using Odin, but for some reason none are working and now when I try and boot into recovery it just restarts the phone. Anyone know what I should do?
Click to expand...
Click to collapse
You need to uncheck the auto reboot box in odin, after the recovery transfer is complete pull the battery and unplug from your computer then do a boot into recover by holding the volume up-home-power button. If not rooted follow the instructions in my post above at the very least you need to load the kernel file
dhonzik said:
You need to uncheck the auto reboot box in odin, after the recovery transfer is complete pull the battery and unplug from your computer then do a boot into recover by holding the volume up-home-power button. If not rooted follow the instructions in my post above at the very least you need to load the kernel file
Click to expand...
Click to collapse
So I did that with all 3 recoveries like 2 or 3 times each, nothing was working I unchecked reboot then would just pull battery after reboot and hold vol up and power to try and get into recovery. Sometimes the litlte blue would appear in the top left corner saying "recovery booting" and would just stay there forever other times that would appear and then the phone would just reboot itself.
Anyway finally found instructions that allowed said to try checking auto reboot and f time reset so did that with a TWRP recovery tar and then it finished and rebooted. I then shut the phone off and held power and vol up to get into recovery and it loaded fine. I was then able to flash the chainfire superuser and kernel you posted. So Thanks a bunch man!
I have tried over and over to root my device and install Jedi S4. I am going through the process for the updated S4 for the UDID problem.
I have ODIN'd TWRP, then installed MDB-SetUIDOff.zip then SuperSU. At this point everything is fine. Then when I install JediS4 it appears to go okay but not very quickly, I hit reboot and I am hit with a "It appears your device is not rooted" would you like to install superuser?.......
If I hit no and reboot it just sits at samsung screen.... What am I doing wrong here?
I have tried the file T-Mobile_OUDHS-Recovery-jfltetmo.tar in ODIN as outlined by another site to no avail as well. It apparently places the stock recovery with the UDID issues fixed then roots the device.
Would appreciate any assistance in this matter.
Thank you,
CJ
Just use the RootUVUAMDL zip in recovery and that's it. All I did was flash cwm in odin then once I rebooted into recovery I flashed the Root zip I have been straight every since then.
Sent from my SGH-M919 using Tapatalk 2
jtkknj said:
I have tried over and over to root my device and install Jedi S4. I am going through the process for the updated S4 for the UDID problem.
I have ODIN'd TWRP, then installed MDB-SetUIDOff.zip then SuperSU. At this point everything is fine. Then when I install JediS4 it appears to go okay but not very quickly, I hit reboot and I am hit with a "It appears your device is not rooted" would you like to install superuser?.......
If I hit no and reboot it just sits at samsung screen.... What am I doing wrong here?
I have tried the file T-Mobile_OUDHS-Recovery-jfltetmo.tar in ODIN as outlined by another site to no avail as well. It apparently places the stock recovery with the UDID issues fixed then roots the device.
Would appreciate any assistance in this matter.
Thank you,
CJ
Click to expand...
Click to collapse
When it says "would you like to install superuser" have you tried hitting yes? Also, if all you're seeking is root I would say to try flashing CF-Auto-Root in Original Android Development. If you want the custom recovery too, then either download and flash the Odin flashable TWRP recovery or boot into the ROM and installi Goo Manager and let it install TWRP for you.
Try CF auto root. Or if ur using the custom recovery tar in Odin, uncheck auto reboot and pull out the battery after u flash it in Odin. Then u will able to get to the custom recovery.
Sent from my GT-I9505G using xda premium
Hi everyone. Last night I went to install S3Rx 4.3 TW ROM,i went through the AROMA installer like I have in the past, at the end it went to reboot and got stuck on the "Samsung Galaxy s3" screen, I gave it 15 min's to load. When it didn't load, I rebooted into my recovery which is TWRP (not sure which version" the blue "TeamWin" screen came up and it rebooted, it did this every time I tried to boot into recovery. I then downloaded the newest and some older versions of TWRP to flash via Odin. They all showed that the install passed but the same thing happens every time I try to boot into recovery. Since I updated the bootloader to use the 4.3 TW ROM I can't flash a stock ROM and start over again correct? Any help would be appreciated, i'm at my wits end here and don't know what else to do. Thanks everyone.
Try flashing the latest versio of Philz Touch via Odin.
audit13 said:
Try flashing the latest versio of Philz Touch via Odin.
Click to expand...
Click to collapse
All I could find were img files, will that still work?
Install the latest tar version from here: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2att
Do not unzip the file. Just put it in PDA, disable auto reboot, install, disconnect USB cable from the computer when you see Reset in the status window, pull the battery, replace the battery, and boot into recovery.
audit13 said:
Install the latest tar version from here: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2att
Do not unzip the file. Just put it in PDA, disable auto reboot, install, disconnect USB cable from the computer when you see Reset in the status window, pull the battery, replace the battery, and boot into recovery.
Click to expand...
Click to collapse
You are most definitely the man! That worked and I got a ROM installed. I went 17 hours without a phone, I think that's the longest i've gone in a long time. Thanks for the fast response and fix!:good:
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.
Hi
I followed this thread here http://forum.xda-developers.com/showpost.php?p=33278472&postcount=2
I downloaded Odin3-v1.85.zip and 2013.05.20 --- CF-Auto-Root (root package)
ran odin
click the PDA button, and select CF-Auto-Root-....tar.md5
put note II in download mode (volume button, home, power)
click start
wait a couple secs
odin says pass
phone reboots and then does some more rooting stuff and reboots again
runs root checker and shows its not rooted
help???
I just use CyanogenMod Installer and it's easy as cake! Plus you can also have a TW rom ready to go if TW is what you want
booandroids said:
Hi
I followed this thread here http://forum.xda-developers.com/showpost.php?p=33278472&postcount=2
I downloaded Odin3-v1.85.zip and 2013.05.20 --- CF-Auto-Root (root package)
ran odin
click the PDA button, and select CF-Auto-Root-....tar.md5
put note II in download mode (volume button, home, power)
click start
wait a couple secs
odin says pass
phone reboots and then does some more rooting stuff and reboots again
runs root checker and shows its not rooted
help???
Click to expand...
Click to collapse
I had to use this method a few days ago and I got it to work with the latest Odin3 3.09. Anything else and it would fail for me.
ItsLasher said:
I had to use this method a few days ago and I got it to work with the latest Odin3 3.09. Anything else and it would fail for me.
Click to expand...
Click to collapse
I downloaded Odin v 3 09 and tried to root it again... no success.
Odin says PASS but root checker says its not rooted.
booandroids said:
I downloaded Odin v 3 09 and tried to root it again... no success.
Odin says PASS but root checker says its not rooted.
Click to expand...
Click to collapse
After Odin say passed are you rebooting into recovery and flashing Philz and SU or are you just rebooting into the phone OS like normal?
IF the above auto reboots back to the phone.
Uncheck the auto reboot and once it's all done and says passed reboot into recovery and complete the flashing needed.
ItsLasher said:
After Odin say passed are you rebooting into recovery and flashing Philz and SU or are you just rebooting into the phone OS like normal?
IF the above auto reboots back to the phone.
Uncheck the auto reboot and once it's all done and says passed reboot into recovery and complete the flashing needed.
Click to expand...
Click to collapse
I seem to have figured out the problem.. just updated SuperSU and root checker says my phone is rooted now. Now you said something about flashing Philz.. how do I do that and what does flashing Philz do to my phone?
booandroids said:
I seem to have figured out the problem.. just updated SuperSU and root checker says my phone is rooted now. Now you said something about flashing Philz.. how do I do that and what does flashing Philz do to my phone?
Click to expand...
Click to collapse
if it says youre rooted then youre good. i dont think you need philz. i had the same problem. my recovery was cwm so.i dont think philz is a must.
if i remember correctly, it has something to do with supersu not matching or being up to date or something. hence your simple fix.
speaking only from experience
Noutafun said:
if it says youre rooted then youre good. i dont think you need philz. i had the same problem. my recovery was cwm so.i dont think philz is a must.
if i remember correctly, it has something to do with supersu not matching or being up to date or something. hence your simple fix.
speaking only from experience
Click to expand...
Click to collapse
Ok thanks
so now that I installed Philz & rooted phone, how do I install custom rom?
booandroids said:
Ok thanks
so now that I installed Philz & rooted phone, how do I install custom rom?
Click to expand...
Click to collapse
Download the rom you want to use, onto your phone.
Check it's md5 (i use md5 checker from the play store)
Boot into recovery and make a backup (i also reboot, go back into recovery and restore/boot into my backup just to make sure it's good)
Back In recovery, wipe to install a new rom.
Install your rom .zip
Reboot (and hopefully) profit.
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2