I have my first android device, the nexus 4, and I rooted it. I used the Nexus toolkit, being new to android and rooting and all. I now need to send my phone back to Google and I can't relock the bootloader! I managed to unroot it but now I just need to relock it and get rid of the padlock. I have tried everything that I have found online and nothing has worked!
I am really becoming annoyed with this! Can anyone help please?!
Thanks, LJ.
It should be an easy thing to do from fastboot. I think the command is something like fastboot oem lock. The toolkit should be able to do this action also. Once that command is complete then reboot fastboot and it should be completed.
Sent from my Nexus 4 using Tapatalk 4 Beta
That is exactly the command.
fastboot oem lock
Sent from my Nexus 4 using xda app-developers app
Being "new to android and rooting and all" is the biggest reason not to use a toolkit. You just press a button, have no to little idea what exactly happens to your phone and then go "pls my phone doesnt work and is eating my cat pls help" when something goes wrong...
Sure, everything seems easier when you use a toolkit, but you end up having no idea what to do when the toolkit fails
Just sayin'.
vanmarek said:
Being "new to android and rooting and all" is the biggest reason not to use a toolkit. You just press a button, have no to little idea what exactly happens to your phone and then go "pls my phone doesnt work and is eating my cat pls help" when something goes wrong...
Sure, everything seems easier when you use a toolkit, but you end up having no idea what to do when the toolkit fails
Just sayin'.
Click to expand...
Click to collapse
this.
and for any nexus device, rooting the right way is just as easy if not easier than a toolkit. the only difference is that youll need to read up a little, get familiar. im mean how easy is this to root..
1. fastboot oem unlock
2. fastboot flash a custom recovery
3. flash either the su binaries or a custom rom
4. reboot and profit.
then to lock the bootloader just fastboot oem lock.
thats all that is needed for any nexus.
I have been using a nexus as well. Download nexus toolkit v2.0 it does it all. I flashed half a dozen ROMs and unrooted and relocked bootloader and re rooted it
Download it and enjoy
Sent from my Nexus 4 using xda app-developers app
abhijitsohoni said:
I have been using a nexus as well. Download nexus toolkit v2.0 it does it all. I flashed half a dozen ROMs and unrooted and relocked bootloader and re rooted it
Download it and enjoy
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I have tried using the toolkit v2.0 but still no success I am really becoming annoyed about this!
LJGDY said:
I have tried using the toolkit v2.0 but still no success I am really becoming annoyed about this!
Click to expand...
Click to collapse
Are you getting any commands to work when you are in fastboot? Like fastboot reboot or flashing a recovery img? I'm just wondering if you have fastboot setup correctly. If you can do those other commands, relocking shouldn't be an issue.
Sent from my Nexus 4 using Tapatalk 4 Beta
eqjunkie829 said:
Are you getting any commands to work when you are in fastboot? Like fastboot reboot or flashing a recovery img? I'm just wondering if you have fastboot setup correctly. If you can do those other commands, relocking shouldn't be an issue.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I have also followed efrans guide, step by step, and was typing all commands into the command prompt. The phone was responding too. When I booted it up, I was stock rom again but the boot loader would not lock. Strange! :/
LJGDY said:
I have also followed efrans guide, step by step, and was typing all commands into the command prompt. The phone was responding too. When I booted it up, I was stock rom again but the boot loader would not lock. Strange! :/
Click to expand...
Click to collapse
Follow that guide but instead of entering the first command for returning to stock now just type in "fastboot oem lock"
Sent from my Nexus 4 using xda app-developers app
LJGDY said:
I have my first android device, the nexus 4, and I rooted it. I used the Nexus toolkit, being new to android and rooting and all. I now need to send my phone back to Google and I can't relock the bootloader! I managed to unroot it but now I just need to relock it and get rid of the padlock. I have tried everything that I have found online and nothing has worked!
I am really becoming annoyed with this! Can anyone help please?!
Thanks, LJ.
Click to expand...
Click to collapse
Trickster Mod has an option to Lock/UnLock your Bootloader as long as you are rooted and you use a kernel which supports such extravagances. (i.e.Franco-r210, for example)
I'd recommend getting familiar to fastboot would be the best option, too. If it's not working, what is the exact error or is there none?
You could try this app to lock it, too, if the phone is still rooted
Related
So I can't root my nexus s I don't know why I have had all the great androids since day one but this baby wont budge. Will any of those one.click apps work never tried one?
Sent from my Nexus S using XDA App
dskyers said:
So I can't root my nexus s I don't know why I have had all the great androids since day one but this baby wont budge. Will any of those one.click apps work never tried one?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
There's no one click method I know of for the Nexus S.
What do you mean you can't root & it won't budge? This phone is about as easy they come (without some one click app): http://forum.xda-developers.com/showthread.php?t=931865
Install the android sdk on your computer.
Put the su.zip file on your sdcard partition of the phone.
Put the phone in fastboot mode.
Fastboot flash the recovery.
Select recovery.
Select install zip from sdcard.
Flash it.
Reboot.
You're done.
If your computer doesn't recognize the phone while it's in the bootloader, you gotta install the google Nexus S drivers or the one from PDAnet. That was where I got stuck at 1st when I tried rooting. Fastboot couldn't find my phone because I had the generic windows drivers.
Also if you have PDANet on, turn it off before putting your phone in fastboot mode.
Actually there is a one click method...brb with it
http://www.theandroidsoul.com/easy-one-click-root-for-nexus-s-full-guide/
Or search superboot nexus s
Here on xda
Either will work PC or mac.
Sent from my Nexus S using XDA App
vapor311 said:
Actually there is a one click method...brb with it
http://www.theandroidsoul.com/easy-one-click-root-for-nexus-s-full-guide/
Or search superboot nexus s
Here on xda
Either will work PC or mac.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Interesting. So the steps on the referenced one-click method you posted are:
1) put your phone in fastboot
2) do the fastboot oem unlock command manually.
3) run a batch file that contains two lines (fastboot-windows.exe flash boot boot.superboot.img & fastboot-windows.exe reboot).
I guess that's easier than putting your phone in fastboot directly and typing in a command to flash clockwork, then selecting a zip file to install from clockwork, but not much.
The drawbacks here are of course that it's superboot, and that it requires you to unlock the bootloader. I guess it's useful if you're really noob, but it only saves you typing one command.
The noob part is very true. However I prefer my bootloader unlocked anyhow.
Sent from my Nexus S using XDA App
vapor311 said:
The noob part is very true. However I prefer my bootloader unlocked anyhow.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Why do you prefer it unlocked?
I like the unlocked lock! No seriously custom roms etc.
Sent from my Nexus S using XDA App
main reason i think there is no one click root is because its so simple to do on this phone
vapor311 said:
I like the unlocked lock! No seriously custom roms etc.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
You do not need an unlocked bootloader (currently) to use custom roms, or to root, or to flash clockwork recovery, etc...
On day one that wasn't a known entity.
Sent from my Nexus S using XDA App
vapor311 said:
On day one that wasn't a known entity.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Of course, but since you contradicted my statement earlier that one disadvantage to the posted method here was that it had you unlock the bootloader by replying that you like having yours unlocked, I was trying to pin down if there was an advantage to unlocking the bootloader that had been discovered that I hadn't heard yet.
There's indication on git for our phone that the next update includes a change to the bootloader being able to use the fastboot boot command while locked. Unknown what that will actually do in terms of just fastboot flashing clockwork to apply root and custom roms.
I c wut u did there. I'm not sure how the update is going to affect things ATM. I keep it unlocked for "in case sh*t" happens. Never know what an update will bring in changes to rom management.
Sent from my Nexus S using XDA App
Hey everyone, I joined xda to see if someone could help me with my problem. So recently I rooted my nexus 7 using wugfresh's root toolkit. I then installed aokp after i tried out paranoidandroid......i flashed gapps each time. I then wanted the old tv style screen off animation and using that toolkit, so i extracted the framework-res.apk ...........and i don't know what went wrong. Now all i can do is boot into the bootloader. When i try to go to recovery, it shows an open android with a caution sign in it. it just keeps bootlooping the aokp animation. I can't find any solution....help! i just want to go completely stock and lock the bootloader. it wont work with wug's toolkit.
Are you plugged in to your PC using the USB cable?
Yeah. Using the OEM cable from Asus. It charges and everything.....what do I do? I'm stuck and stressing about it.
Sent from my SCH-I510 using xda app-developers app
AndroidNinjaReview said:
Yeah. Using the OEM cable from Asus. It charges and everything.....what do I do? I'm stuck and stressing about it.
Sent from my SCH-I510 using xda app-developers app
Click to expand...
Click to collapse
Don't worry we will help you get it figured out. It's very fixable, mostly take some deep breaths and destress. When you start to panic then you have more of a chance of messing something up.
What happens when you use the command adb reboot recovery? what's the message you get? I'm guessing if you're extracting framework you're real familiar with ADB but if not use the toolkit.
Did ADB work before on your same computer you're on?
AndroidNinjaReview said:
Hey everyone, I joined xda to see if someone could help me with my problem. So recently I rooted my nexus 7 using wugfresh's root toolkit. I then installed aokp after i tried out paranoidandroid......i flashed gapps each time. I then wanted the old tv style screen off animation and using that toolkit, so i extracted the framework-res.apk ...........and i don't know what went wrong. Now all i can do is boot into the bootloader. When i try to go to recovery, it shows an open android with a caution sign in it. it just keeps bootlooping the aokp animation. I can't find any solution....help! i just want to go completely stock and lock the bootloader. it wont work with wug's toolkit.
Click to expand...
Click to collapse
reflash your recovery via fastboot, not with a toolkit. then reflash your rom/gapps. if its still a no go, wipe then reflash your rom/gapps.
CharliesTheMan said:
Don't worry we will help you get it figured out. It's very fixable, mostly take some deep breaths and destress. When you start to panic then you have more of a chance of messing something up.
What happens when you use the command adb reboot recovery? what's the message you get? I'm guessing if you're extracting framework you're real familiar with ADB but if not use the toolkit.
Did ADB work before on your same computer you're on?
Click to expand...
Click to collapse
The message I get is error: device not found when I use the adb reboot recovery. And I'm not familiar with it at all. I was trying to get that TV off animation and I was following a guide. This is my first root. So far....not a good experience.
Sent from my SCH-I510 using xda app-developers app
simms22 said:
reflash your recovery via fastboot, not with a toolkit. then reflash your rom/gapps. if its still a no go, wipe then reflash your rom/gapps.
Click to expand...
Click to collapse
Can you tell me how to do this without the toolkit? I'm lost....
Sent from my SCH-I510 using xda app-developers app
help!
CharliesTheMan said:
Don't worry we will help you get it figured out. It's very fixable, mostly take some deep breaths and destress. When you start to panic then you have more of a chance of messing something up.
What happens when you use the command adb reboot recovery? what's the message you get? I'm guessing if you're extracting framework you're real familiar with ADB but if not use the toolkit.
Did ADB work before on your same computer you're on?
Click to expand...
Click to collapse
Please help! I need this fixed asap and it seems like you know exactly what to do! Aghh. Im stressed...this is my first tablet andi just want it to work :crying:
AndroidNinjaReview said:
Please help! I need this fixed asap and it seems like you know exactly what to do! Aghh. Im stressed...this is my first tablet andi just want it to work :crying:
Click to expand...
Click to collapse
So i think all i need to do is flash the factory image. how would i go about doing this?
After i tryed flashing kaos droid i think ive managed to brick my nexus 7. It just boots into cwm v6.0.1.0. Ive tryed a number of times holding down the power and the volume buttons together and i CANT get into the bootloader ): . No matter what i do it just boots into the recovery even if i flash another rom it goes back to cwm. I dont know what to do please help? I cant even shut the screen off its been in cwm for over 3 hours now \:
And i was rooted and unlocked before this. Tab was working fine till i flashed kaos droid
Sent from my myTouch 4G Slide using Tapatalk 2
Just use recovery to restore your backup.
Sent from my Nexus 7 using xda premium
This is about the 15th post I've seen this week about someone screwing up their n7. If there already isn't one there needs to be a step by step video for the correct way to unlock, root, and flash Roms. I suggest others read heavily before doing any flashing. Its bad enough the boot loader is already screwy.
The toolkit does everything for you. All in one method and you're done.
I'm sure its his .img
Sent from my Nexus 7 using xda premium
I had this problem happen with my Xoom.
Boot into the bootloader from recovery. There should be an option to do so.
In the bootloader flash a different recovery.
Then reinstall your ROM. It should boot.
If that doesn't work I would suggest flashing the stock images in fastboot and starting over.
Sent from my Nexus 7 using xda premium
El Daddy said:
I had this problem happen with my Xoom.
Boot into the bootloader from recovery. There should be an option to do so.
In the bootloader flash a different recovery.
Then reinstall your ROM. It should boot.
If that doesn't work I would suggest flashing the stock images in fastboot and starting over.
I will try using the toolbox but i dont think i have access to fastboot from the recovery? I mean im telling you guys my screen has been on for over 4 hours because it just reboots and wont turn off.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I can not boot into the bootloader my nexus 7 boots directly into cwm. I tryed wiping caches, wiping system, formating everything, restoring a nandroid, flashing another rom..... Nothing is working
When i get home. To my computeer im going to try using the toolkit hopefully it works
Sent from my myTouch 4G Slide using Tapatalk 2
nemesis93 said:
I can not boot into the bootloader my nexus 7 boots directly into cwm. I tryed wiping caches, wiping system, formating everything, restoring a nandroid, flashing another rom..... Nothing is working
Sent from my myTouch 4G Slide using Tapatalk 2
Click to expand...
Click to collapse
I had a similar problem on my og evo. Try seeing if you can flash the recovery from a computer while booted into cwm. Then it'll reboot into new recovery, you flash rom, and you stop sharding your pants
nemesis93 said:
I can not boot into the bootloader my nexus 7 boots directly into cwm. I tryed wiping caches, wiping system, formating everything, restoring a nandroid, flashing another rom..... Nothing is working
Sent from my myTouch 4G Slide using Tapatalk 2
Click to expand...
Click to collapse
Even choosing "reboot bootloader" in recovery?
If that doesn't work, connect to you your computer and using adb type the command
Code:
adb reboot bootloader
kieso said:
This is about the 15th post I've seen this week about someone screwing up their n7. If there already isn't one there needs to be a step by step video for the correct way to unlock, root, and flash Roms. I suggest others read heavily before doing any flashing. Its bad enough the boot loader is already screwy.
Click to expand...
Click to collapse
And to you sir I have read and watched other videos/tutorials whatever you may call them. I post on here as a last resort when "i dont know what to do". I cant understand people who post but dont really have nothing helpful to say about the topic. All im asking for is some help please and thank you
Sent from my myTouch 4G Slide using Tapatalk 2
El Daddy said:
Even choosing "reboot bootloader" in recovery?
If that doesn't work, connect to you your computer and using adb type the command
Code:
adb reboot bootloader
Click to expand...
Click to collapse
I dont have a reboot bootloader option but when i go to reboot system it goes straight into cwm like i said.
Also fastboot/adb is not working. When i run a command it says "waiting for device" on my computer
Sent from my myTouch 4G Slide using Tapatalk 2
On a side note, i had tryed everything i formated the sd in cwm and now it appears on cwm as if theres "No files found" but on my computer everything i had previously is still there.
So there is a connection to the storage part of the device but not adb or fastboot
Sent from my myTouch 4G Slide using Tapatalk 2
nemesis93 said:
I dont have a reboot bootloader option but when i go to reboot system it goes straight into cwm like i said.
Also fastboot/adb is not working. When i run a command it says "waiting for device" on my computer
Sent from my myTouch 4G Slide using Tapatalk 2
Click to expand...
Click to collapse
Hmmm. You should have a working adb while booted into a custom recovery. Are your drivers installed correctly?
Also, the reason why you computer sees the files is because with mtp it caches the files.
Sent from my Nexus 7 using xda premium
El Daddy said:
Even choosing "reboot bootloader" in recovery?
If that doesn't work, connect to you your computer and using adb type the command
Code:
adb reboot bootloader
Click to expand...
Click to collapse
So far i got adb to work finally! Happy im making some progress.
Now im able to boot into the bootloader so i can run fastboot commands. I currently have NO rom whatsoever installed so im waiting to flash the stock rom using the toolkit. Thank you for your help
Also when i booted into twrp it said i had 3% battery left lol so im just hoping it will work now.
Sent from my myTouch 4G Slide using Tapatalk 2
OP will stop making threads like this if people stop recommending toolkits......................
And definition of brick is beyond repair - unable to boot up, e.g. Black screen when power button is pressed, not even the Google screen.
Will the next nexus have a longer screen?
Mach3.2 said:
OP will stop making threads like this if people stop recommending toolkits......................
And definition of brick is beyond repair - unable to boot up, e.g. Black screen when power button is pressed, not even the Google screen.
Will the next nexus have a longer screen?
Click to expand...
Click to collapse
Well it was beyond repair for the moment being if i did NOT have access to adb, fastboot, nor the Bootloader i said that three times already.
But whatever i finally got adb to work and was able to fastboot flash a stock image. Thank you so much el daddy for your help i really appreciate it.
Sent from my myTouch 4G Slide using Tapatalk 2
nemesis93 said:
Well it was beyond repair for the moment being if i did NOT have access to adb, fastboot, nor the Bootloader i said that three times already.
But whatever i finally got adb to work and was able to fastboot flash a stock image. Thank you so much el daddy for your help i really appreciate it.
Sent from my myTouch 4G Slide using Tapatalk 2
Click to expand...
Click to collapse
No problem. I'm glad you got it to work.
And thank you for flashing with fastboot and not a toolkit
Sent from my Nexus 7 using xda premium
El Daddy said:
No problem. I'm glad you got it to work.
And thank you for flashing with fastboot and not a toolkit
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Yeah i tryed at first because i was lazy and it didnt work so i did it through fastboot.
Thanks again
Sent from my myTouch 4G Slide using Tapatalk 2
Glad you got it working
nemesis93 said:
And to you sir I have read and watched other videos/tutorials whatever you may call them. I post on here as a last resort when "i dont know what to do". I cant understand people who post but dont really have nothing helpful to say about the topic. All im asking for is some help please and thank you
Sent from my myTouch 4G Slide using Tapatalk 2
Click to expand...
Click to collapse
Sorry I wasn't trying to bust your stones. I haven't rooted yet because of all of the posts like yours. I've just seen more problems with flashing on this device then any other that I have with my past Droid devices. What we really need is apx (spelling?) Drivers and n7 files for a sure fire recovery from any disaster
Hopefully I don't have to start another thread.
I too think I bricked my Nexus 7.
I was having trouble and I accidentally cleared a file from the System UI app (its a system required app) which caused me to loose the 3 buttons on the bitten of the screen.
So I went to CWM to do a restore which said it failed.
After that it would not boot.
Its just stuck with the Google logo on the screen.
I held down the power up & down volume buttons and I get a screen that gives me that START button on the top right of the screen with the text in small size on the bottom left.
I can use the up and down volume to make the start button change to recovery mode or bootloader but activating them just goes to Google logo.
Can I recover or is it totally lost?
I also don't remember if I left the Nexus 7 in Debug mode which is usually required to perform custom Roms
Thanks
Rob
Sent from my SPH-D710 using Tapatalk 2
I see a couple of different tools here to unlock and root my Nexus 7. What are the differences between them?
I do not want to flash ROMs; just unlock, root and install cwm recovery.
Nate2 said:
I see a couple of different tools here to unlock and root my Nexus 7. What are the differences between them?
I do not want to flash ROMs; just unlock, root and install cwm recovery.
Click to expand...
Click to collapse
fastboot oem unlock, fastboot flash cmm recovery, flash the su binaries, reboot and profit.
Search for wugfresh nexus root toolkit. Very simple to use.
Sent from my Nexus 7 using xda premium
frozenspark said:
Search for wugfresh nexus root toolkit. Very simple to use.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Don't use tools for rooting with the Nexus devices, it's useless in my opinion. Try to understand the basics behind rooting, recovery and fastboot, do it manually and you will be able to help yourself even if something is not working as expected.
Sent from my Nexus 7 using xda app-developers app
Use this: http://forum.xda-developers.com/showthread.php?t=1809195
This is the best tool for Nexus 7.
AndDiSa said:
Don't use tools for rooting with the Nexus devices, it's useless in my opinion. Try to understand the basics behind rooting, recovery and fastboot, do it manually and you will be able to help yourself even if something is not working as expected.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Even though I know how fastboot, recovery and rooting works, I still use this tool without any of those commands. And it serve the purpose for me quickly. Of course using such tools will not stop you from learning more afterwards.
I wouldn't say its useless.
Sent from my Nexus 7 using xda premium
frozenspark said:
Even though I know how fastboot, recovery and rooting works, I still use this tool without any of those commands. And it serve the purpose for me quickly. Of course using such tools will not stop you from learning more afterwards.
I wouldn't say its useless.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
then you should br helping out all the people that mess up their devices afyer using toolkits and dont know how to fix it. i havent seen you help out, yet you are still recommending toolkits. why is that?
I used the steps outlined at http://rootzwiki.com/topic/28544-guide-nexus-7-bootloadersrecoveriesrootback-to-stock/ to guide me.
I must say it might not be trivial for the non-software-developer types.
I was a Java developer for many years, so I didn't have much problems setting up Java,
Android-sdk, etc.
My N7 was recognized by adb when booted normally, but after I flashed cwm, I could not do 'adb shell' to mount the /system partition and rename the recovery-from-boot.p file to prevent the recovery from getting reset to stock each time.
I ended up installing the ROM Manager app to enable me to boot into cwm recovery.
I have done the obligatory cwm backup. I believe this is the nandroid backup?
Edit:
I used my Linux box to re-flash the bootloader and cwm recovery images to the Nexus 7, and I could 'adb shell' and rename the recovery-from-boot.p file. So I'm all set now.
I just needed to run 'adb start-server' and 'fastboot' using sudo, so it might have been a permissions issue on my Windows box.
Sent from my unrooted DroidX using Tapatalk
I used Wug's Root Toolkit. Both of the toolkits seem good, but that was just the first one I saw. The Wug's Toolkit is an application and the other one is in a CMD.
Sent from my SGH-T989 using xda premium
Linexus said:
Use this: http://forum.xda-developers.com/showthread.php?t=1809195
This is the best tool for Nexus 7.
Click to expand...
Click to collapse
+1
Absolutely brilliant ToolKit, very simple, fast and works like a charm.
I rooted my N7 with this, and had no issues to date.
Only took a couple of minutes.
BRILLIANT!
Looks like I'm not all set, after all Today, right before I plan to take the JB 4.1.2 OTA update, I notice my tablet won't boot into CWM, like it did a couple of days ago. I did rename the one file and things looked normal. What could have happened to my CWM?
Edit:
So there are 2 files that need to be renamed, not 1?
/system/recovery-from-boot.p
/system/etc/install-recovery.sh
And there was a bug in JB 4.1.1 that prevented booting into cwm recovery unless the device was plugged into USB??
Sent from my Nexus 7 using Tapatalk
I re-flashed the same cwm recovery img, reinstalled the same su zip, and I'm back to normal
Gotta watch out for those OTA updates, I tell ya.
Use the fastboot commands
Good to see you alright!
This is like asking "Should I get an automatic or manual car?"
veeman said:
This is like asking "Should I get an automatic or manual car?"
Click to expand...
Click to collapse
In the early days, automatic transmissions were more problematic and much more expensive. Today they are pretty efficient, even though a manual transmission gives you better control over the car, which most people don't really need for everyday driving.
If you frequently get stuck in stop-and-go traffic, you'll wish you had an automatic transmission.
Look at these lazy people..
Beamed from my Grouper.
Nate2 said:
Looks like I'm not all set, after all Today, right before I plan to take the JB 4.1.2 OTA update, I notice my tablet won't boot into CWM, like it did a couple of days ago. I did rename the one file and things looked normal. What could have happened to my CWM?
Edit:
So there are 2 files that need to be renamed, not 1?
/system/recovery-from-boot.p
/system/etc/install-recovery.sh
And there was a bug in JB 4.1.1 that prevented booting into cwm recovery unless the device was plugged into USB??
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Yes there was a bootloader bug on the nexus 7 and most people could not boot into CWM recovery without plugging it into their computer.
I however used TWRP back then [have since switched back to CWM touch, now that the bug is fixed] and had no issues. Now I have no issues with CWM touch, I can boot it directly from fastboot menu, or "reboot -> recovery" when booted.
Nate2 said:
I re-flashed the same cwm recovery img, reinstalled the same su zip, and I'm back to normal
Gotta watch out for those OTA updates, I tell ya.
Click to expand...
Click to collapse
exactly what I would have done! sounds like you're getting the hang of it. and yes, I definitely recommend manual rooting/fastbooting to a toolkit.
Wilks3y said:
+1
Absolutely brilliant ToolKit, very simple, fast and works like a charm.
I rooted my N7 with this, and had no issues to date.
Only took a couple of minutes.
BRILLIANT!
Click to expand...
Click to collapse
Yes that's my favorite too. It does it all and more. It slices, it dices, it'll even cut a can!
Nate2 said:
In the early days, automatic transmissions were more problematic and much more expensive. Today they are pretty efficient, even though a manual transmission gives you better control over the car, which most people don't really need for everyday driving.
If you frequently get stuck in stop-and-go traffic, you'll wish you had an automatic transmission.
Click to expand...
Click to collapse
Yeah, that's what I'm saying. They both have their ups and downs. If you're willing to learn a little about how Android works and learn some adb and fast boot commands then you should definitely do it manually.
If you just want to be a "1337 Haxorz" and aren't willing to learn then just use a toolkit.
OK, just one sub-question on rooting. I see no real reason to root except maybe to get more tablet interface than nexus has. Kinda like when the wifi indicator is at the bottom, since there are those !$#$$ back/home buttons already and a lot of wasted space Anyways, the question.
I bougth N7 16Gb and upgraded via forced OTA to 4.1.2. Do all these root methods work with 4.1.2?
Thanx,
D.
when i was unlocking my nexus 4, the reboot process was taking far too long and a friend told me to restart so i held down the power button to restart it. After i did that, it would either bootloop on the colors or just stay on 'Google' screen! I have access TWRP but i can't fastflash anything! and when i look around TWRP, it says i have no OS installed! TWRP allowes the option to ADB but im not sure if it's properly installed. Please help!!!!
I'd re flash factory images with a tool kit
Zehlek said:
I'd re flash factory images with a tool kit
Click to expand...
Click to collapse
i have wugfresh's Nexus Root Toolkit installed on my computer and tried to use those options but it won't do anything cause i dont have fastflash
datninjakyle said:
i have wugfresh's Nexus Root Toolkit installed on my computer and tried to use those options but it won't do anything cause i dont have fastflash
Click to expand...
Click to collapse
Google 15 second adb install xda. That'll setup fastboot on your pc. Then flash the factory image in fastboot
Sent from my Nexus 9 using XDA Free mobile app
Yup do that
Sent from my Nexus 4 using XDA Free mobile app