Hi,
I have a 920T with 5.1.1 android version and I'm having a hell of a time installing TWRP. I root fine verified root and the whole thing is beautiful. Every root app I try says im rooted, titanium backup works fine and super user does as well. So I know i'm rooted correctly.
Now I download TWRP from the market place and set up a recovery, I pick "twrp 2.8.6.0 zeroflte" and go through the steps. Again no problem, says it is set up correctly would you like to go into recovery mode. I say yes and then I get stuck in a boot loop forever, I can't do anything but go into download mode and redo my stock rom which I don't want. My end wish is to get http://forum.xda-developers.com/tmob...n-1-0-t3088032 that on my phone as I'd love to bypass selinux which I can't on a stock rom.
I should note I also tried installing TWRP through odin and that boot loopd my phone as well. Am I missing something here? Wrong step? wrong app? wrong something?
bump bump bump
Related
hey all, currently have a g2x rooted with cm7, and i've been looking to unroot;
just to make sure i dont do anything stupid, i wanna run this through with you guys:
first i would flash the stock 2.3.3 ota rom for g2x
then use the http://forum.xda-developers.com/showthread.php?t=1056847 (one click nv flasher) to get back to lg stock recovery by clicking 'flash stock recovery' (do i need to dl anything extra for this?)
then im done, correct? if i boot up, ill get all the stock rom and apps and bloatware and etc back right?
thanks!
edit: how do i know which version of clockwork mod i have installed? im not sure if i did the external sd support or not...
You've gone back to a stock ROM, you've gone back to the stock recovery, but you haven't actually unrooted.
Whichever method you used to root, you should be able to use that same method to unroot.
UPDATE:
I was originally under the assumption that your 2.3.3. ROM was rooted. If it is stock you should be fine.
sorry for bump, but i read in tga_gunmans post that ppl should flash a rooted 2.3.3 rom and use superoneclick to unroot...would my method work too?
No your way would not work because the stock OTA by xboarder is rooted. Do what tga_gunman said. Flash the rom, use my unroot zip in CWM (deletes root files) and then flash the stock recovery. Busybox will still be on the phone but nobody should be looking for that.
Unroot zip: http://www.mediafire.com/?2vr7cmgg7qcdn14
Easiest way to confirm if your not rooted would be to install Superuser from the market. It'll tell you if the phone's not rooted.
There is an app on the market called Root Checker which is free. It will tell you if you are rooted or not.
A little extra help for me?
jboxer said:
No your way would not work because the stock OTA by xboarder is rooted. Do what tga_gunman said. Flash the rom, use my unroot zip in CWM (deletes root files) and then flash the stock recovery. Busybox will still be on the phone but nobody should be looking for that.
Unroot zip:
Click to expand...
Click to collapse
Thanks for your help jboxer. Forgive my noob-like understanding of rooting/unrooting terminology. Hopefully you'll be able to understand what I did.
Last night I went ahead with the unrooting process on my G2X which was running Gingerbread & CM7 following this youtube video (can't post link due to noobiness: watch?v=ryGIv8KQVIE), the order that this guy goes in is:
1. Wiping all cache/user data/formatting in CWM recovery
2. Restore to a barebones stock data in CWM recovery
3. Flash to go back to Stock using OneClickRecovery
4. SuperOneClick to unroot phone
What I ended up doing was restoring my phone to the backup that I created on my sd card when first rooting my phone rather than download that zip file in the video description which is a completely fresh start.
However, whenever I flashed to go back to stock using OneClickRecovery, it gave me that total barebones fresh start where I had to completely set up my Android from the first start screen and I lost my backup. Also, when I go to unroot the phone with that zip file, I don't know how to 'install from zip' after I've lost CWM Recovery menu. So, I flashed back to CWM so I could recover my backup from my SD Card again and install the 'unroot.zip' that you linked and it ran alright and I restarted, but I still had 'SuperUser' in my App drawer telling me that I was still rooted.
I ended up calling it good last night after spending two hours on it. I left my phone rooted, with CWM recovery still on my phone, but I at least I had my backup Gingerbread image with no CM7 mod. So, my phone is functional, but I would like to complete this process of unrooting completely.
Could you perhaps give a little guidance and clarity to what I'm missing or not understanding? I'd love to unroot/flash back to stock recovery/remove all evidence of rooting AND keep my recovered backup that I have before I even started rooting my phone.
Thank you so much for all your help, everybody.
Hi there,
I got a brand new Galaxy Note 10.1 this weekend and tried to get my hands dirty on rooting it just yesterday. So I got Odin3, CWM and SuperSU, installed Samsung Kies and thought I were good to go. Unfortunately, after doing what some guides tell me to do, I'm still on official device status.
Before I go into detail: I had to manually edit the Odin3 INI file to force the device NOT to auto reboot after flashing the CWM - the checkboxes in Odin3 were disabled and greyed out. Can someone explain why and if that might be the cause of my problems?
HoPi` said:
Hi there,
I got a brand new Galaxy Note 10.1 this weekend and tried to get my hands dirty on rooting it just yesterday. So I got Odin3, CWM and SuperSU, installed Samsung Kies and thought I were good to go. Unfortunately, after doing what some guides tell me to do, I'm still on official device status.
Before I go into detail: I had to manually edit the Odin3 INI file to force the device NOT to auto reboot after flashing the CWM - the checkboxes in Odin3 were disabled and greyed out. Can someone explain why and if that might be the cause of my problems?
Click to expand...
Click to collapse
Download a clean copy of Odin and install .
Auto Reboot is normal .
Root and Recovery TWRP
http://forum.xda-developers.com/showthread.php?t=1851548
Root and Recovery CWM
http://forum.xda-developers.com/showthread.php?t=1831173
jje
Thanks, but that didn't help either. Auto-Rebooting brings me back to stock, device state official. I tried to install CWM-SuperSU-v0.99.zip manually via CWM, but a reboot later it's still "official" and apps that need root access either run forever ("checking...") or freeze the tablet. But since this is getting off topic, I might be better off asking in other threads.
Thanks anyway!
HoPi` said:
Thanks, but that didn't help either. Auto-Rebooting brings me back to stock, device state official. I tried to install CWM-SuperSU-v0.99.zip manually via CWM, but a reboot later it's still "official" and apps that need root access either run forever ("checking...") or freeze the tablet.
Click to expand...
Click to collapse
Then you are not understanding instructions .
What is your intention .
Root or flash a stock rom .
Root via either method i posted .
Stock rom direct flash tar file via Odin.
ODIN flash is a tar not a zip.
Custom rom via a rooted phone with recovery zip file from ext sd card or sd card .
jje
Come on, the instructions are pretty clear boot in Odin Mode, click a button in Odin, let it restart, finished. The SuperSU zip file is from another guide, where the tar-file didn't include it. So I tried to manually install it via CWM (I think it was 6.0.2.7 or 8), but that didn't work either. Whenever the device reboots, Root Checker Basic runs for a few minutes and says "Sorry, the device does not have proper root access". If it helps, I used this guide:
http://www.android-hilfe.de/root-cu...ly-root-fuer-anfaenger-n8000-n8010-n8020.html
Even though it's in german, the screenshots are pretty obvious.
Sorry never ever seen any method with those sort of instructions.Personally not a clue what they mean .
I have used two methods as posted to root note 4 or 5 times. Rooted standard Samsung phones with cwm and root hundreds of times without any of those instructions.
Even run one standard cwm root via Odin to allow a specific rom install followed by a reroot using TWRP this afternoon .
jje
Sent from my GT-N8010 using xda premium
Thanks to Darkman, I finally got it. The problem was the current firmware update from Samsung. I reflashed with the version from January, followed his tutorial (like I did before - wow, after doing this 3-4 times, it certainly becomes second nature), and BAM, the device is rooted. Thanks anyway JJegan
So here is my problem. I was rooted on JB,and getting propmts to update to KK. After some research I found out that is it now rootable/unlockable, so I downloaded the .183 update and used RSD Lite to get on the update. That went well. Used towelroot and motoapocalypse to get rooted and unlocked. Also went well. Used Flashify to install TWRP. Well again. Heres where things fell apart. I booted into recovery to backup my stock ROM. After I did that I moved the backup to my SD card like an idiot not knowing it couldn't be restored from there. So I downloaded Validus 5.2 and Gapps. When I flashed them I was stuck in a boot loop on start up. Power down and tried again, still looping. Fastbooted to Recovery to restore my backup, but it was not there cuz it was only reading from internal storage (oops). So I was screwed. Then I read that CM had updated the modem or something and that you had to update stuff to use it. Still not sure about all that, but anyway. I thought maybe that was the problem, so I downloaded an older version of CarbonROM from June that was before the CM changes thinking I would be good now, but when I flashed it the same thing happened. Boot loop. So I went back into fastboot and flashed the RSD Lite stuff again. Rooted with towelroot. Unlocked with motoapocalypse. Verified status code 3 in fastboot. Verified root with Root Checker. Installed Flashify, but I haven't installed a recovery yet. Was TWRP my problem? Why am I boot looping on custom ROMs? Can someone help me out, or point out something Ive missed here?
ilinimud said:
So here is my problem. I was rooted on JB,and getting propmts to update to KK. After some research I found out that is it now rootable/unlockable, so I downloaded the .183 update and used RSD Lite to get on the update. That went well. Used towelroot and motoapocalypse to get rooted and unlocked. Also went well. Used Flashify to install TWRP. Well again. Heres where things fell apart. I booted into recovery to backup my stock ROM. After I did that I moved the backup to my SD card like an idiot not knowing it couldn't be restored from there. So I downloaded Validus 5.2 and Gapps. When I flashed them I was stuck in a boot loop on start up. Power down and tried again, still looping. Fastbooted to Recovery to restore my backup, but it was not there cuz it was only reading from internal storage (oops). So I was screwed. Then I read that CM had updated the modem or something and that you had to update stuff to use it. Still not sure about all that, but anyway. I thought maybe that was the problem, so I downloaded an older version of CarbonROM from June that was before the CM changes thinking I would be good now, but when I flashed it the same thing happened. Boot loop. So I went back into fastboot and flashed the RSD Lite stuff again. Rooted with towelroot. Unlocked with motoapocalypse. Verified status code 3 in fastboot. Verified root with Root Checker. Installed Flashify, but I haven't installed a recovery yet. Was TWRP my problem? Why am I boot looping on custom ROMs? Can someone help me out, or point out something Ive missed here?
Click to expand...
Click to collapse
You have to ensure the ROM you are using is built for the KK kernel. Not all ROMs work with the KK kernel.
Here is a list of ROMs that work with KK:
http://www.droidrzr.com/index.php/topic/48909-kitkat-roms-list/
Anything else will result in what you are experiencing - bootloops.
Ok so thanks ahead of time for any help given, here is my story. I have a E980 with the latest AT&T 4.4.2 on it and should have done a little more reading before I installed a custom recovery. I used a one click rooting app for pc which worked great and root was achieved with no problems. Then not knowing about needing a lokified recovery for this I used FREEGEE and CM Rom Manager to attempt to install a custom recovery which both said they were successful and according to CM Rom manager i am running CM recovery 6.0.3.8. My phone still works fine but I can't factory restore or boot into recovery without getting the secure booting error Cause: boot certification verify. I have looked for the last two days on this form and others trying to find a way to get back into recovery. Everything I have read on this error ends up leading back to me using the recovery to flash another rom or another recovery which I can't do. From what I have read the people with this error normally can't do anything on there phones. I do have Android studio installed (although don't really know how to use it) on my PC in hopes that there is some way I can fix this. Please if anyone can lead me in the right direction so I can get back into a recovery and load the lokified one it would be greatly appreciated.
Thanks again for any help given!
Bump
Hi,
I have a 920T with 5.0.2 android version and I'm having a hell of a time installing TWRP. I root fine verified root and the whole thing is beautiful. Every root app I try says im rooted, titanium backup works fine and super user does as well. So I know i'm rooted correctly.
Now I download TWRP from the market place and set up a recovery, I pick "twrp 2.8.6.0 zeroflte" and go through the steps. Again no problem, says it is set up correctly would you like to go into recovery mode. I say yes and then I get stuck in a boot loop forever, I can't do anything but go into download mode and redo my stock rom which I don't want. My end wish is to get http://forum.xda-developers.com/tmo...ent/rom-xtrestolite-pure-edition-1-0-t3088032 that on my phone as I'd love to bypass selinux which I can't on a stock rom.
I should note I also tried installing TWRP through odin and that boot loopd my phone as well. Am I missing something here? Wrong step? wrong app? wrong something?
bump bump