Hi! Noob here, but I have successfully rooted several times using XDA-guides. This time I got nothing.
I just bought a Samsung Nexus 10 with Android 4.4.2 Kitkat (KOT49H) and was looking to root it. Since I did't see any guides here on XDA with 4.4.2 i searched other places and found several guides which recommended CWM-recovery as root method. This one for example: www[dot]teamandroid.com/2013/12/10/root-nexus-10-android-442-kot49h-install-cwm/2
I have done everything by the book, and finally I unlocked the bootloader and then flashed with CWM 6.0.4.3. All seems to work but when I enter recovery mode CWM cant mount or open files or install zip's or anything. I tried to reflash several times but get the same problem. Fastboot and recovery still works, but on normal reboot i get stuck in the google logo loop.
Should I just reflash with factory os or what can I do?
Hi,
Try flashing another recovery, like TWRP.
Hope this helps,
~Lord
"Time is too short to cry, long enough to try." - March of Time (Helloween)
Sent from my KitKat Nexus 10
Related
Hello guys, first time posting here, I'm pretty sure it's a silly question, sorry if it is but I couldn't find the answer anywhere. I have an unlocked and rooted device, I installed the last 4.3 update this morning, and usually TWRP let me automatically fix the root just after install the update. But this time it just installed it and booted the tablet, and when I try to enter the recovery mode to fix the root in TWRP, I only see the droid with the exclamation mark.
So the problem is that I don't have root, and I cannot enter TWRP to fix it. TWRP went away with the latest update?. For entering the TWRP I pressed vol+ vol- and power and the pick recovery... is it correct?
Thank you in advance for the great community we have in android and sorry for my english
The same thing happened to me, I resolved it by:
- download a recovery image such as TWRP to a desktop/laptop and then flash it via abd
- now boot into recovery and flash SuperSU 1.51 or higher (1.55)
From what I read you probably did this once before. The 4.3 update overwrote your recovery image and root.
3DSammy said:
The same thing happened to me, I resolved it by:
- download a recovery image such as TWRP to a desktop/laptop and then flash it via abd
- now boot into recovery and flash SuperSU 1.51 or higher (1.55)
From what I read you probably did this once before. The 4.3 update overwrote your recovery image and root.
Click to expand...
Click to collapse
Same for me, Starting have some problems as I tried a "reboot to recovery" apk and got it stuck in the bootloader screen and it wasnt going anywhere.. still had TWRP but reflashing things wasnt working..
Used Wug's Nexus Root Toolkit to bring it back to life..
All good
I reflashed the recovery image and rooted again with Wug's Root Toolkit. All good!! Thank you for your answers guys!! Cannot find the way to put SOLVED in the thread title...
prezeus said:
I reflashed the recovery image and rooted again with Wug's Root Toolkit. All good!! Thank you for your answers guys!! Cannot find the way to put SOLVED in the thread title...
Click to expand...
Click to collapse
Nice that it is solved but please do nog use toolkits anymore. I respect the effort and time people take to make them but learning fastboot is just way better. Maybe harder but hard work pays off. Almost everyone will tell the same.
For people who want to use fastboot:
1. Flash custom recovery via fastboot.
2. Boot into recovery.
3. Flash latest supersu.
You can put solved in the title by edeting it.
Sent from my Galaxy Nexus using XDA Premium HD app
same
Good time . I have a similar problem : after a recent update missing root. I tried to flash a custom recovery by fastboot, but the process hangs at downloading recovery.img to nexus. I tried using other drivers and a different version of fastboot, but to no avail.
Ps: by same drivers and fastboot I got the root before.
Hi!
It is not the first time I root phones but this time seems I cannot manage it.
I have updated and re-rooted my nexus in every ROM update with no problems. Today I received the OTA 4.4 update and did a re-root of my phone BEFORE applying the update (don't ask me why I did it before... I'm just dumb).
I used the Nexus root toolkit as other times (I once uploaded cyanogen in a ZTE Skate through CWM but found the root kit more straight for my nexus). Now I'm stuck in the 'Pushing root files to your device' stage and the program is 'not working'. I still have it plugged and don't know what to do. Since it was rooted before I hope it has CWM still there. Should I unplug it and repeat the process or do I have a brick now?
Any advices would be appreciated. Thanks in advance.
(yes, I feel stupid)
Seems solved.
Since it was rooted and I didn't check the flash bootloader option only rebooting returned the phone to its previous state.
Next time...
Next time, flash temproraly (until next reboot) CWM or TWRP recovery And choose SuperSU-UPDATE zip. Its safe for OTA.
msihp said:
Next time, flash temproraly (until next reboot) CWM or TWRP recovery And choose SuperSU-UPDATE zip. Its safe for OTA.
Click to expand...
Click to collapse
I see... always the hard way seems beetter. My thought was that if I updated superSU before the OTA I wouldn't have to re-root again but I see those kits doesn't always work.
The CWM still scaries me although I used it before. I guess I will have to deal with it.
Thanks for your advice
Hi guys I just wannted to share my expierence with my Galaxy Tab 3. From 4.1.2 to 4.4.2 I encoutered many problems and created solutions to fix them. And here are some.
The first thing that I had a problem with was when I unrooted and left busybox installed. When I did a factory data reset, the device became so laggy and almost unusable. I I could not root my device for some reason. To fix this, just simply reflash the stock room using odin. After I fixed this, I upgraded to Kit-kat and looked for a custom recovery to install. I went for clockwormod and found my self getting stuck in a cwm bootloop. To fix this, download the latest version of TWRP and install via odin. I strongly recomend to use TWRP as it does not go into a recovery bootloop unlike CWM. Now for Xposed I noticed that the boot up is way slower then before. A simple install of the module boot manager can help.
That's it. I hope I can help some new users with problems on the galaxt tab 3. If you have any other problems, just let me know and I'll do my best to help.
Sent from my SM-T210 using XDA Free mobile app
I flashed TWRP and got a recovery boot loop.
hen I flashed Clockwork, which didn't loop.
So, use most recent one which resets the switch for booting into recovery! Doesn't matter for this problem which one, as long as it is the lastest loader.
So, here is the deal,
I was rooting my nexus player though the normal process (by flashing the root.img via fastboot, just like in the tutorial) and everything was looking good, so when the device rebooted I looked for the superSU app but it wasn´t there. So I went to the play store dowloaded the superSu app directly from there (thinking better kind of a noob move ). It installed and asked to update the binaries, I accepted ( through normal, not with the custom recovery), after a while it notified me that the process was unsuccessfull and asked me to reboot and try again later, so I did it.
After that the device entered in a bootloop, and now I have nothing but access to the bootloader and the stock recovery...
ps: I had successfully installed the Cyanogen recovery, before it happened
ps2: Sorry by the bad english, it isn´t my main language
Flash the supersu maybe? From recovery?
There is talk about this in a few threads and it has work arounds
I did it!!
So, I took the weekend, to cool my head and today I came up with a fairly simple answer, I used the Nexus Root Toolkit by Wugfresh ( http://forum.xda-developers.com/showthread.php?t=1766475 ), and the process couldn´t be simpler. I just put the NP in bootloader, opened the toolkit and used the option to flash stock.
I've been in a Google bootloop for ages now, I've tried every toolkit and every flash-all.bat. Updates my drivers, used more than 4 different USB cables, more than 3 different computers and more than 5 stock images, sat at "formatting /data..." for more than 12 hours. None have saved my Nexus 10 from bootlooping. Flashing any recovery doesn't have any effect, the recovery seems to be stuck at LMY48X.
My only option left is using Odin, although I cant find any information on using Odin with the nexus 10.
Can anyone upload the AP and or PIT files for me?
Help me Odin you're my only hope.
Although the N10 is made by Samsung, I don't think there is anything "Samsungy" about it, and I'm not aware that Odin has been used or is usable on it.
That said, I know you said you've used every toolkit, but I've never had the WugFresh toolkit fail me. What recoveries have you successfully flashed?
tjupille said:
Although the N10 is made by Samsung, I don't think there is anything "Samsungy" about it, and I'm not aware that Odin has been used or is usable on it.
That said, I know you said you've used every toolkit, but I've never had the WugFresh toolkit fail me. What recoveries have you successfully flashed?
Click to expand...
Click to collapse
I've had twrp and cwm on the tablet before, but in my efforts to unbootloop it I've not been able to flash any recovery. The commands go through but when I try to boot into recovery via bootloader it goes to the stock recovery. Temporary recoveries work but trying to flash twrp from wugs toolkit didnt work.
I had similar issue perviously that whatever i flashed via recovery wouldn't take.
Also I was unable to actually perform anything att all via the recovery.
The only thing that worked for me was to flash the factory images (found here https://developers.google.com/android/nexus/images#mantaray). I used the first build to be safe. (https://dl.google.com/dl/android/aosp/mantaray-jdq39-factory-d79f489e.tgz)
Unfortunately I had to go through the painstakingly slow process to flash each delta update until i finally reached some point where i could actually flash the recovery with TWRP and then CM12.
How about fastboot? Have you tried to use fastboot to load images onto nexus 10?
Sent from my SHIELD Tablet K1 using XDA-Developers mobile app