So I have been trying to follow Rooting instructions using the toolkit for the Nexus 7 4.2.2 from these forums and while I've got it into USB Debug mode and unlocked the bootlocker deleting my memory. I've attempted the 1 click option, just standard Rooting at the 4.1 which appears to work for my version according to other Google searches, and the Root+Install BusyBox thing and they all stop at the attached screen. I'll start to install the boot img, complete 2 files and then says "Waiting for Device" where it will take my tablet out of debug mode and launch the full OS where it continues recovering my apps.
Am I doing something wrong? Do I need to be completely recovered in order to root my N7? How long do you have to wait for your device and what is it waiting for?
Related
The phone is unlocked, with clockworkmod recovery 6.0.1.0 and stock rooted 4.1.1 ROM.
I'm using Windows 7 x64 SP1.
When the phone is ON and the debug mode is activated, it shows correctly under "device manager" and adb works right, but when I reboot in bootloader ADB doesn't see any attached device even if it shows correctly under device manager.
I tried to update the USB driver of the Android SDK but dosn't work
I then uninstalled it and tried to install the Universal Naked Driver (almost all of the nexus or samsung types) but doesn't work
I uninstaleld it and tried another USB driver found on the forum but doesn't work.
I tried to install Android SDK on another PC with Windows 7 x86 SP1 and repeat all the steps but it's the same.
How can I unroot and lock the device if it doesn't shows when in bootloader mode?
You don't use adb in bootloader. You use fastboot.
Locking the bootloader does not unroot by the way.
crespo80 said:
The phone is unlocked, with clockworkmod recovery 6.0.1.0 and stock rooted 4.1.1 ROM.
I'm using Windows 7 x64 SP1.
When the phone is ON and the debug mode is activated, it shows correctly under "device manager" and adb works right, but when I reboot in bootloader ADB doesn't see any attached device even if it shows correctly under device manager.
I tried to update the USB driver of the Android SDK but dosn't work
I then uninstalled it and tried to install the Universal Naked Driver (almost all of the nexus or samsung types) but doesn't work
I uninstaleld it and tried another USB driver found on the forum but doesn't work.
I tried to install Android SDK on another PC with Windows 7 x86 SP1 and repeat all the steps but it's the same.
How can I unroot and lock the device if it doesn't shows when in bootloader mode?
Click to expand...
Click to collapse
Have you tried the Nexus Root Toolkit by WugFresh? It is an application that takes you in several easy steps in installing drivers, rooting, and lock/unlock your device. For installing drivers there are several additional steps when installing them seems unsuccessful.
Leauwie said:
Have you tried the Nexus Root Toolkit by WugFresh? It is an application that takes you in several easy steps in installing drivers, rooting, and lock/unlock your device. For installing drivers there are several additional steps when installing them seems unsuccessful.
Click to expand...
Click to collapse
This is true, I've used Wugfresh toolkit too but I had some problem...
I've Nexus S 9023, with wug toolkit I had no problem to install driver with its very complete guide, this part can solve your problem but make attention on other function, for example with it I've also unlocked my phone but when I tried to root my device freeze.
So maybe that not all toolkit function will work well on all Nexus S.
Please stop with this toolkit nonsense.
Its not a driver issue at this point. Its the user using ADB instead of fastboot.
Remove this and that when he is just using the wrong command. This is the nonsense you see when all people know is some toolkit.
Yeah, I'm an idiot, that was not a driver issue
it's just because I usually root/unroot/unlock/lock my android phones once in a while (when I first buy and when I sell them), so I always forget some basic procedures and searching through the forums is always a mess, I spent three hours doing that, before posting...
I had forgotten ADB and fastboot weren't the same... anyway, I solved with WugFresh (I didn't know it, thanks for the tip) but I could have solved even with plain fastboot commands, I know
Anyway, I'm surprised to realize that the real stock ROM is more stable than the rooted and deodexed stock ROM I was using before, now the 3G/2G/airplanemode swithing is blazing fast and the performance drops on some games are gone... I'll never figure out this Android world
Thanks for all your help :victory:
Wondering if someone has an hour or so to spare to walk me through the steps of making my phone work again. Last night I did these steps in this order; Revolutionary S-off, CWM, Permanent root, Install custom rom. I installed an AOKP rom and phone kept freezing at the initial setup welcome screen, after reflashing it twice I tried Cyanogen and got the same result. Now I am stuck at the Cyanogen screen and after researching I hear that it is best for me right now to restore my phone to stock through RUU? I am not sure how to go about that as I am looking at the guide and it requires SDK installed. I go to the SDK instructions and it says that I should enable my phone for USB debugging so SDK drivers can install successfully however my phone is in bootloop, how am i suppose to enable usb settings?
Still stuck, I do not think SDK installed successfully on my PC. If any developer has free time I am begging, please message me
what is your fw version?
I signed on really quick just to reply, I will be able to post later today (including my FW version)
I have read all types of forums to Reboot Bootloader. Yeah, I know stuck at the beginning, not a good sign.Any way I went to Developer.android and got SDK. Followed various suggestions and have it on machine. However the windows 7 won't recognize device. I downloaded Motorola Device Manager for the drivers (I beleive this may be the issue) and it found no updates. I have debugged checked on Xoom, but jellybean icon shows up intermittently. When I type in CMD prompt to adb reboot bootloader, it doesn't recognize the device.
Other CMD commands suggested during instruction video worked verifying I had ADB installed coirrectly. I checked the device in control panel and it is unidentfied.Device properties has this error" Windows has stopped this device because it has reported problems. (Code 43)"
Please, can someone assist. I think that I need the drivers, but the motorola Device manager is the only tool I can find and I dont think it has the drivers, I could be wrong, but this is what I'm guessing.
Ok. I found online that the new USB 3.0 has issues with this process. I plugged into a 2.0 USB and I'm in business. I've gone through unlocking. Now I can't locate the Universal Xoom Root Zip. All tutorial links that I could find go to a link that no longer has the file. can someone point me in the right direction or send me a link to the file- Thanks for the help
Ok status update. I was able to find the file and have successfully Rooted. The question, now is I restarted and I have an Green Android robot on my screen with Tiamat engraved on front stomach area. I believe I was in recovery last. IS the Xoom doing anything in the background. I don't want to interrupt something if it is running. I have downloaded BiGPART and Omni 4.4 components but I seem to be stuck
Wow... Not one response. I was able to figure it out and now am the owner of 4.4
So this is my first post on XDA, due to the lack of information on this particular device. Here I'll try to explain how I managed to root this device after trying several methods available here and all over the web. First I'll explain what didn't work:
VROOT (*)
Framaroot
Motochopper
SRS Root
MTK Toolkit
Nearly every solution on the web
After trying every method above, I noticed none of them were working. They all were giving false positives. No ROOT at all. I was kinda frustrated, 'cause I had followed every instruction possible, without success. I double checked my PC drivers, and I noticed something odd: Every time I changed the USB connection type on the L50, Windows installed different drivers for the device. I'm saying this was odd because I installed the drivers from LG drivers pack, so I was a bit confused. So, after Windows Installed the drivers for MTP, Modem, PTP and LG mode, I tried VROOT and... VOILĂ! I had ROOT:laugh::laugh:
So here are the steps I followed, and the tools I used:
Download VROOT (a.k.a. as IRoot) from w w w. mgyun. c o m / en / getvroot (without spaces)
Enable DEBUG MODE (Surf the web if you don't know on how to do it).
Plug your device to your PC and wait until Windows Installs the drivers for the connection type.
Without unplugging the device, Change the USB connection type to the next one. Wait 'till windows finishes installation.
Repeat the previous step untill you finish with all connection types.
Check Device Manager for missing drivers. If you have some missing, repeat steps above.
Open VROOT/IROOT and plug your device to the PC. Follow on-screen instructions and wait.
ENJOY!
Now, I have to find a Custom Recovery that works with L50... so if you guys know where I can get one, I'll appreciate your help.
Your Thread will be moved to appropriate Section.
So I tried to make a recovery for this phone, but it cannot boot. It says boot certification error, and the phone reboots normally.
So is it possible that the bootloader is locked? I want recovery for this phone too.
someone know how i can do a nandroid backup on LG L50 ?
Thank you so much. Worked on D213AR
Can you confirm if there is a way to unlock NFC hidden option on my phone?
jam66 said:
someone know how i can do a nandroid backup on LG L50 ?
Click to expand...
Click to collapse
If you managed to get Root (with the steps described on the OP) You can use Titanium Backup.
THE Ghost2 said:
So I tried to make a recovery for this phone, but it cannot boot. It says boot certification error, and the phone reboots normally.
So is it possible that the bootloader is locked? I want recovery for this phone too.
Click to expand...
Click to collapse
same for me i made cwm for it cant boot to it because it has locked boot loader
So is it possible to root the phone with the official rom?
Or am i missing something?
I accidently wiped everything in twrp when trying to install an OTA. I tried using the guides however I can't get my device to show up as qualcommm in device manager. Instead it appears under kedacom usb device android bootloader interface. What can I do from here? Thanks for any help