Related
Bought a new Nexus 7 because my wife and I have them and love them. We had bought our daughter a cheap 'funtab' from walmart just so she could play a few games she loves and hopefully leave ours alone, the funtab was a complete POS so it was returned to WM and just bought her a N7 instead.
When booted, the tablet it immediately notified me of the update from 4.1.2 to 4.2.1. Each time it tried to update it would fail partially through, not sure why. So I thought I'd download and use the toolkit to force the update. After unlocking, rooting, installing busybox and so on. I choose the option to flash stock image. The update process started OK there but part way through gave an error, something about needing to be 'X' but is instead 'x' before going back to the home screen. Now the tablet is stuck in fastboot mode, and cant boot to either recovery or android. I think I may be in trouble here.... Any suggestions?
#1 reason why people shouldn't use tool kits to root. You have no idea what went wrong or where the problem occurred.
I'm assuming that your tablet is unlocked so you need to download a custom recovery and install it via fastboot.
Then download the Stock 4.2.1 ROM from the Android development section and flash it in the recovery.
This should give you an idea of how to do it.
http://www.androidcentral.com/how-unlock-bootloader-and-root-your-nexus-7
Sent from my Nexus 7
I've done more research and I'm currently working on getting the android sdk going. I've downloaded it, jdk, the proper factory image (i think I f'd up by accidentally downloading the factory image for the hspa model). My question now is can the factory image be flashed from what appears to be fastboot mode, or do i need to flash custom recovery first (via the sdk)? I can confirm that the bootloaded is unlocked.
Ok so I was able to flash the stock image using the instructions found at http://forum.xda-developers.com/showthread.php?t=1907796
This process went extremely well once I had all my ducks in a row. Thanks for the help.
I had a windows 7 PC perfectly working in booting a Nexus 7 to flash and root etc, it did a Nexus 4 last week.
There is some problem with drivers and 4.2.2. specifically. My story was it was 4.1.2. rooted and it was refusing to OTA update but I wasn't bothered due to the bugs/performance in 4.1.1 so I waited til 4.2.2. came along. The N7 refused to take OTA 4.2.2. I got the Android icon with the Red icon out its belly and it would boot back as 4.1.2 every time.
So using Nexus Rootkit I did a "stock flash+unroot" to 4.2.1 and then let it did a OTA to 4.2.2 and that worked so I have a stock 4.2.2 but not it won't root, it would do that ADB bootloader type stuff. I've tried updating driving umpteen times but it like it simply won't obey ADB type commands? I'm not a rooting expert I just used the toolkit and howtos.
So stuck.
In hindsight as it WAS doing ADB at 4.2.1 I should have rooted and then otarootkeeper then OTA to 4.2.2. but I didn't know 4.2.2 rooting fails.
Any ideas?
same for me!!!
Help...
Well, the OTA for 4.2.2 would fail every time because of version diffs in the files. You had to be on 4.2.1 to accept the OTA.
1. Out of curiosity, did you remember to re-enable USB debugging?
2. Did you update you SDK for 4.2.2?
If you still have issues after enabling debugging, then try the Universal Naked driver. It was the only one to work on my Win7 box. Also, make sure only 1 instance of ADB is running.
At least you don't have a super weird issue like me where flashing stock recovery refuses to stick, but TWRP flashes with no problem.
Sent from my Nexus 7 using Tapatalk 2
can root a stock 4.2.2 - it works!
I fixed it!
I'd been trying toolkit all of its options and none worked. So I followed this guide which contains an error which is irrelevant.
http://m.ibtimes.co.uk/root-nexus7-official-android422-jdq39-jellybean-ota-434720.html
Do its step 1. It downloads the Google USB drivers - THEY WORK. This is the problem with other guides they point to drivers which don't work.
Ignore its step 2 because you find step 1 includes fastboot so you don't need to get it separate. I lost a lot of time on that one problem because the link to that shared file fastboot.zip won't download so I hunted and found another and when I was going to copy to the required destination in step 2 I found the fastboot file alreadt there! So ignore step 2
Step 3. Now I downloaded it on the Nexus 7 itself and mine was in /sdcard/Downloads or you can copy on the PC and then copy it over to the N7 via USB cable.
Step 4. Press and hold power off you get option select power off.
Step 5. At the step 1 you'll see WHERE it is installing the SDK to, you need to go to that folder in this step 5 as described.
Step 6. As describe, press vol down and power button together and keep them hold. Then a menu screen shows mine had been unlocked from before. Now dont't touch the N7. Go to Windows machine.
Step 7. My Windows Pc doesn't have command prompt option inside a folder so I opened command prompt and CD down to where step 1 was.
Step 8. Type that command. Mine simply worked fperfectly first time. It had a copying type command which looked happy.
Step 9. Back on the N7 hit the vol up button til you see a "recovery" type word on screen.
Step 10 and 11 as described.
Step 12. Now is the next area where howto guide is wrong / misleading, I had on my screen some gibberish folders and an "update.zip" not the supersu zip from step 3. Initially I tried the update.zip and it went crazy but fortunately a hard power-off got me fixed so then next time I looked around for the supersu zip. So of the stuff on-scren where was like 0/ type folder so I selected that THEN I could see the sdcard/download folder I could go down to and then select the zip file. The /sdcard folder isn't showing firstly you have to go /0 and then you see it.
Step 13 do it.
Then get it booted and then go into Supersu app and run it and then make sure you install voodoo root keeper app and select it to preserve root.
So I've got a vanilla 4.2.2. with root and so far it all works. Features which kept me on 4.1.2 like PPP-widget simply work.
Phew.
I've spent about 15 hours on this trying to eliminate my own dumbness as the cause.
I think basically the ADB drivers in the Toolkits are bumb, ignore them they don't work I think the Android SDK with its Google USB drivers are the ones which work with 4.2.2 I guess the Toolkits need to be updated.
nikon120 said:
Well, the OTA for 4.2.2 would fail every time because of version diffs in the files. You had to be on 4.2.1 to accept the OTA.
1. Out of curiosity, did you remember to re-enable USB debugging?
2. Did you update you SDK for 4.2.2?
If you still have issues after enabling debugging, then try the Universal Naked driver. It was the only one to work on my Win7 box. Also, make sure only 1 instance of ADB is running.
At least you don't have a super weird issue like me where flashing stock recovery refuses to stick, but TWRP flashes with no problem.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
The problem seems to be drivers. The N7 stock 4.2.2 simply refuses to respond to Root Toolkit its drivers are simply not working, the N7 is ignoring to get into fastboot. I figured it out see my later post.
I think 4.2.2. is too new for toolkits and people's 4.2.2. rooting guides are buggy and relate to old old instructioned since outdated and in error. By trial+error I figured it.
nikon120 said:
Well, the OTA for 4.2.2 would fail every time because of version diffs in the files. You had to be on 4.2.1 to accept the OTA.
1. Out of curiosity, did you remember to re-enable USB debugging?
2. Did you update you SDK for 4.2.2?
If you still have issues after enabling debugging, then try the Universal Naked driver. It was the only one to work on my Win7 box. Also, make sure only 1 instance of ADB is running.
At least you don't have a super weird issue like me where flashing stock recovery refuses to stick, but TWRP flashes with no problem.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Addtional my N7 did OTA receive the 4.1.2 to 4.2.2 update I even went into the /cache and the file name had version names to match so OTA was thinking itself capable. I think in some unlock / root past event I'd something screwed something up and OTA simply weren't working full stop. I did though manage to use Toolkit to get to stock 4.2.1 and then the drivers in the toolkit then don't work with 4.2.2, that's the broken bit. If you use Android SDK Google USB drivers, they work and you have to use command prompt fastboot as in the HOWTO I just posted to get it all working.
Toolkit drives broken with 4.2.2.
dont use a root toolkit. do it the right way, there arent any issue.
fastboot oem unlock, fastboot flash a recovery, flash the su binaries or a custom rom, reboot. thats it.
FYI - I've found that to use the toolkit (the 4.0.0 toolkit is what I used), you need to replace the adb-toolkit.exe (or whatever adb.exe is called in your toolkit) with the adb.exe that comes in the SDK (after you've updated your SDK, of course).
Otherwise, ADB shows as "offline" in the toolkit menu.
Hope that helps someone...
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
The issue is what you typed is gibberish to most including me.
Sent from my Nexus 7 using xda app-developers app
Hello. 1 month ago i use Nexus 7 Toolkit for flash 4.2.1 stock firmware, because 4.2.2 don't wanna install without some default APK's.
So, I decided download at once 4.2.2, not 4.2.1, and i download it from developers.google.com and put archive in put_google_factory_image_here folder, run flash, and after flashing i get "Booting failed" message, i do not know what i must do, so i decided reboot nexus, power off and that's all. Nexus is a brick. Only crappy APX mode. I go to service center and today they fix it - change motherboard, lol.
And few mins ago i decided flash that 4.2.2 stock AGAIN, lol. Download from developers google com 4.2.2 archive, put it in special folder in nexus toolkit, and start flashing. AND AGAIN GOT "Booting failed" lol!
So, now i don't power off nexus, i put all files from firmware archive in fastboot folder, run flash-all.bat from stock firmware archive... and... ALL IS FINE!
If you download firmware from developers.google.com and when you flash it with nexus toolkit that's will brick your nexus. Why? I don't know. Flash-settings from google and from toolkit server are same. byte by byte.
That problem start only when 4.2.2 released. With flashing before 4.2.2 (when 4.2.1 will stable release) all will is fine.
Peka73Rus said:
Hello. 1 month ago i use Nexus 7 Toolkit for flash 4.2.1 stock firmware, because 4.2.2 don't wanna install without some default APK's.
So, I decided download at once 4.2.2, not 4.2.1, and i download it from developers.google.com and put archive in put_google_factory_image_here folder, run flash, and after flashing i get "Booting failed" message, i do not know what i must do, so i decided reboot nexus, power off and that's all. Nexus is a brick. Only crappy APX mode. I go to service center and today they fix it - change motherboard, lol.
And few mins ago i decided flash that 4.2.2 stock AGAIN, lol. Download from developers google com 4.2.2 archive, put it in special folder in nexus toolkit, and start flashing. AND AGAIN GOT "Booting failed" lol!
So, now i don't power off nexus, i put all files from firmware archive in fastboot folder, run flash-all.bat from stock firmware archive... and... ALL IS FINE!
If you download firmware from developers.google.com and when you flash it with nexus toolkit that's will brick your nexus. Why? I don't know. Flash-settings from google and from toolkit server are same. byte by byte.
That problem start only when 4.2.2 released. With flashing before 4.2.2 (when 4.2.1 will stable release) all will is fine.
Click to expand...
Click to collapse
Well.. I've never had any problems fastboot flashing 4.2.2 myself.
------
I would suggest you don't use toolkits...at all... period!
Learn FASTBOOT...
...and be extremely cautious when it comes to FLASHING the BOOTLOADER...
A corrupted BOOTLOADER flash will 'hardbrick' the device in a heartbeat - make sure you have a secure USB connection...
Test along these lines..
Code:
fastboot flash boot <a boot.img>
or
fastboot flash recovery <a recovery.img>
If these go across, the new BOOTLOADER probably will.
The worst that's going to happen (with these two) is a 'softbrick' - a headache at worst.
A headache you can get over...
Hardbrick is death - and nobody get's over that.
Rgrds,
Ged.
I know this. Thanks.
I flash 4.2.2 with fastboot. Because nexus 7 toolkit is buggy, when i upgrade android from 4.2.1 to 4.2.2 with toolkit i got brick. Just read my 1 post
I give link to this thread creator of toolkit, maybe he fix this bug. Maybe no, anyway, start from this day i will flash firmwares ONLY with fastboot.
Good decision, i never used this kind of tool for flashing something.
Its a very presumptuous statement to say the Toolkit will brick your device if you flash a stock image using it. The toolkit has been used many many thousands of time to flash stock images and I test it extensively on both my nexus 7 devices when there is a new image released. The toolkit also uses exactly the same routine as the batch file included with the image so I know there isn't any problem with the code but regardless of that I will look at it later and see if any extra safety protocols can be added to prevent mistakes.
It would have helped if you listed exactly what you did and if there were any errors displayed when the images were being flashed via the Toolkit.
Mark.
mskip said:
Its a very presumptuous statement to say the Toolkit will brick your device if you flash a stock image using it. The toolkit has been used many many thousands of time to flash stock images and I test it extensively on both my nexus 7 devices when there is a new image released. The toolkit also uses exactly the same routine as the batch file included with the image so I know there isn't any problem with the code but regardless of that I will look at it later and see if any extra safety protocols can be added to prevent mistakes.
It would have helped if you listed exactly what you did and if there were any errors displayed when the images were being flashed via the Toolkit.
Mark.
Click to expand...
Click to collapse
I can't give you list of "errors" etc, just because i don't wanna again "brick" my nexus :/
What i did:
1. I enter in toolkit
2. Choose version (4.2.1 or 4.2.2, don't matter, i got "brick" on both versions)
3. Choose "download and flash stock"
4. Download stock from toolkit, or from google developers site
5. Flash downloaded firmware
After this i got "Booting failed".
Then i flash stock 4.2.2 with FastBoot - and all is ok. But when i again try to flash stock 4.2.2 with toolkit - im again got Booting failed.
That's all.
Ofcourse i have last ver. of toolkit.
Current ToolKit [V4.3.7], Latest Available [V4.3.7]
Current Mods Section [V2.5.0], Latest Available [V2.5.0]
Click to expand...
Click to collapse
I'm getting this samething to happen to me except I can't even get manual fast boot to work either. Both are giving errors about no such device found or timeouts.
I used the toolkit to flash stock and all was fine for me... Weird.
Sent from my Nexus 7 using xda app-developers app
nexus 7 toolkit, works 100% on me and my sis tablet no errors at all..
walliester said:
nexus 7 toolkit, works 100% on me and my sis tablet no errors at all..
Click to expand...
Click to collapse
Hicksy994 said:
I used the toolkit to flash stock and all was fine for me... Weird.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Do you use toolkit for flashing stock 4.2.2?
Never, ever had a problem with Wug's toolkit, that thing is written brilliantly and it has saved my ass more times than I can care to count.
I was totally new to android development before I tried the nexus toolkit. Now I have a rooted n7 and prime, though I gotta say, rooting the prime took from me more time. I would suggest that you run the test-like driver check before attempting the one click magic.
Sent from my Nexus 7 using xda premium
The sequel of flashes you made is confusing for me but you should flash stock no matter the version 4.1 or 4.2 cuz you can get to latest by OTA updater.
Sent from my Nexus 7 using Tapatalk 2
In last update:
+Added MD5 hash checks before flashing for ALL stock images to avoid bad flashes
+Added selection to flash Radio images in the Flash Image section (gsm models)
Good, any1 can test?
No problem for me, I used last tookit to return stock rom 4.2.2 from cyanogenmod 10.0.1 with franco r65kernel.
I desired to return factory rom, because of low charging issue and fast battery drain.
Peka73Rus said:
Hello. 1 month ago i use Nexus 7 Toolkit for flash 4.2.1 stock firmware, because 4.2.2 don't wanna install without some default APK's.
So, I decided download at once 4.2.2, not 4.2.1, and i download it from developers.google.com and put archive in put_google_factory_image_here folder, run flash, and after flashing i get "Booting failed" message, i do not know what i must do, so i decided reboot nexus, power off and that's all. Nexus is a brick. Only crappy APX mode. I go to service center and today they fix it - change motherboard, lol.
And few mins ago i decided flash that 4.2.2 stock AGAIN, lol. Download from developers google com 4.2.2 archive, put it in special folder in nexus toolkit, and start flashing. AND AGAIN GOT "Booting failed" lol!
So, now i don't power off nexus, i put all files from firmware archive in fastboot folder, run flash-all.bat from stock firmware archive... and... ALL IS FINE!
If you download firmware from developers.google.com and when you flash it with nexus toolkit that's will brick your nexus. Why? I don't know. Flash-settings from google and from toolkit server are same. byte by byte.
That problem start only when 4.2.2 released. With flashing before 4.2.2 (when 4.2.1 will stable release) all will is fine.
Click to expand...
Click to collapse
Peka73Rus said:
Hello. 1 month ago i use Nexus 7 Toolkit for flash 4.2.1 stock firmware, because 4.2.2 don't wanna install without some default APK's.
So, I decided download at once 4.2.2, not 4.2.1, and i download it from developers.google.com and put archive in put_google_factory_image_here folder, run flash, and after flashing i get "Booting failed" message, i do not know what i must do, so i decided reboot nexus, power off and that's all. Nexus is a brick. Only crappy APX mode. I go to service center and today they fix it - change motherboard, lol.
And few mins ago i decided flash that 4.2.2 stock AGAIN, lol. Download from developers google com 4.2.2 archive, put it in special folder in nexus toolkit, and start flashing. AND AGAIN GOT "Booting failed" lol!
So, now i don't power off nexus, i put all files from firmware archive in fastboot folder, run flash-all.bat from stock firmware archive... and... ALL IS FINE!
If you download firmware from developers.google.com and when you flash it with nexus toolkit that's will brick your nexus. Why? I don't know. Flash-settings from google and from toolkit server are same. byte by byte.
That problem start only when 4.2.2 released. With flashing before 4.2.2 (when 4.2.1 will stable release) all will is fine.
Click to expand...
Click to collapse
I HAVE flashed stock using the toolkit multiple but no problem for me.....
More, I wanna tell you guys that battery so slow in charging issue is solved after flashed stockrom 4.2.2 from google server. B4 with Cm 10.1 and franco r65, I have to charge it more than 10 hours to full, but now only 5 and half hour with Stockrom 4.2.2 . Problem is relevant to custom rom and modded kernel as I think
hassam_tariq2003 said:
I HAVE flashed stock using the toolkit multiple but no problem for me.....
Click to expand...
Click to collapse
Nexus 7 Turn On Problem
mskip said:
Its a very presumptuous statement to say the Toolkit will brick your device if you flash a stock image using it. The toolkit has been used many many thousands of time to flash stock images and I test it extensively on both my nexus 7 devices when there is a new image released. The toolkit also uses exactly the same routine as the batch file included with the image so I know there isn't any problem with the code but regardless of that I will look at it later and see if any extra safety protocols can be added to prevent mistakes.
It would have helped if you listed exactly what you did and if there were any errors displayed when the images were being flashed via the Toolkit.
Mark.
Click to expand...
Click to collapse
Dear I am facing the same problem I tried to update it with Adnroid 4.3 official. First time it showed boot img failure. I again tried to flash it through Tool Kit and it gave me some error. I tried to restart bootloader and shut it down by pressing power button. After that nothing happens. Now when I connect it to my Computer it shows me unrecognized USB. Does this mean its not dead and there is any option to get it turn on?
It will be highly obliged if you could reply me with the solution. I am in Pakistan and we don't have any service center.
saqibyk said:
Dear I am facing the same problem I tried to update it with Adnroid 4.3 official. First time it showed boot img failure. I again tried to flash it through Tool Kit and it gave me some error. I tried to restart bootloader and shut it down by pressing power button. After that nothing happens. Now when I connect it to my Computer it shows me unrecognized USB. Does this mean its not dead and there is any option to get it turn on?
It will be highly obliged if you could reply me with the solution. I am in Pakistan and we don't have any service center.
Click to expand...
Click to collapse
I'm in the same boat exactly the same thing. i hope there is a fix for this.
ChrisHRocks said:
I'm in the same boat exactly the same thing. i hope there is a fix for this.
Click to expand...
Click to collapse
You should flash the stock bootloader, when connected, find this amongst the advanced utilities, and if the drivers are not working then use the driver diagnostic tool. You will not lose your apps doing this.
One other thing is that once your bootloader is returned to stock, you can use the Google Framework cache and data clearance mthod, described in other posts, to force the 4.3 Update. This really does work, and means that your apps and data remain intact.
Hi.
So, a quick overview. My laptop suddenly stopped recognizing my Nexus 10 while in the midst of transferring some files over. I decided to finally root. I used the cf-autoroot tool for Nexus 10 Lollipop. The last step of the rooting involves an automatic reboot. Now my Nexus 10 is stuck in the boot.
Details:
theunlockr (DOT) com/2014/11/22/how-to-root-the-nexus-10-on-android-5-0/
That is the guide I used, including the linked cf-autoroot. Sorry for the formatting, I don't have enough posts to post links.
My Nexus 10 is stuck on the step where it shows the four circles moving around. Not sure if that's important.
The cf-autoroot appeared to work successfully except for a piece in the middle that reads:
Same problem. The procedure seemed to go well, except maybe the mounting failed? It says:
Mounting...
- System
- Cache
--- Fail
I tried using the tool several times on two computers, and did my best to update drivers directly from Google (it appears the drivers are all up to date).
My Nexus 10 was on Lollipop. As far as I know, it was up to date, so I think that means it was on 5.0.1
Help?
Hello autoroot is no longer required. Supersu from recovery is enough.
You could just reflash original kernel
Does
Fastboot boot boot. Img works? It boots on the given image without flaging. The boot image is located in the archive to update
Sent from my Xiaomi MI2s
Khaon said:
Hello autoroot is no longer required. Supersu from recovery is enough.
You could just reflash original kernel
Does
Fastboot boot boot. Img works? It boots on the given image without flaging. The boot image is located in the archive to update
Sent from my Xiaomi MI2s
Click to expand...
Click to collapse
This is what I have come here to find out. I'm receiving my Nexus 10 in the mail today. I'm familiar with Nexus devices so I just assume everything is the same with the Nexus 10. But I know since Lollipop came out, there have been changes to how to root on certain devices. Are you saying that everything has been fixed to where I can just install the latest TWRP and flash the latest beta SuperSU on stock ROM and I will be good? If so, then it's the same as my Nexus 5 so I shouldn't have any issues.
jsgraphicart said:
This is what I have come here to find out. I'm receiving my Nexus 10 in the mail today. I'm familiar with Nexus devices so I just assume everything is the same with the Nexus 10. But I know since Lollipop came out, there have been changes to how to root on certain devices. Are you saying that everything has been fixed to where I can just install the latest TWRP and flash the latest beta SuperSU on stock ROM and I will be good? If so, then it's the same as my Nexus 5 so I shouldn't have any issues.
Click to expand...
Click to collapse
Yep, just flash once SU through twrp(in order to get the su binary in the system partition) and then you can use play store to update the binary and the program itself.
CM12 has built in su and nighties are official now.
Khaon said:
Yep, just flash once SU through twrp(in order to get the su binary in the system partition) and then you can use play store to update the binary and the program itself.
CM12 has built in su and nighties are official now.
Click to expand...
Click to collapse
Thanks. I just wanted to double check before I went jumping into it. I'm looking forward to tinkering with it when I get home from work.
Khaon said:
Yep, just flash once SU through twrp(in order to get the su binary in the system partition) and then you can use play store to update the binary and the program itself.
CM12 has built in su and nighties are official now.
Click to expand...
Click to collapse
So I attempted to do all this when I got home yesterday. I found that after unlocking the bootloader, I got stuck in a boot loop. After doing some research I found that this has been an issue with the Nexus 10. Is there a reason for this? I read that locking the bootloader again fixed it, which it did. But I didn't want it locked. So I researched more and found that a a factory reset in stock recovery would fix it. I still had a boot loop. I managed to somehow get everything straightened out with a series of random tries and after installing TWRP and rooting and, again, getting the boot loop I attempted to go back into recovery but accidentally did a simple restart. For some reason, it booted right up after the restart so now I think everything is fine. But why is the Nexus 10 being so difficult? I never had these issues with other Nexus devices. Maybe some of this info will help the OP as well.
Hm unlocking the bootloader does erase whole content but I guess you are already aware of that.
How long did you wait? First boot can take ages much longer than before.
I never had any issues and I have my bootloader unlocked
Khaon said:
Hm unlocking the bootloader does erase whole content but I guess you are already aware of that.
How long did you wait? First boot can take ages much longer than before.
I never had any issues and I have my bootloader unlocked
Click to expand...
Click to collapse
I let it sit for a while. I own a Nexus 5 and I'm familiar with the long first boot. It just seemed like a long time to me. I thought maybe since it was a two year old device that it may take longer. The device is new to me so I'm not familiar with boot times and all that are specific to it yet. But compared to the boot time after I relocked the boot loader, there was a big difference. After re-locking, it booted up in about a minute or two. Flashing TWRP even seemed to mess up some stuff. I think it may have deleted the OS or something. It couldn't mount anything afterwards and even selecting reboot boot loader gave me the prompt that there was no OS installed. So I flashed the system.img, cache.img and userdata.img manually. Which seemed to fix it. And even after I got everything straightened out, it boot up in about a minute or two again. The only time I had issues with getting it to boot is unlocking the boot loader coming from complete stock.
nexus 10 stuck on bootload up
jsgraphicart said:
I let it sit for a while. I own a Nexus 5 and I'm familiar with the long first boot. It just seemed like a long time to me. I thought maybe since it was a two year old device that it may take longer. The device is new to me so I'm not familiar with boot times and all that are specific to it yet. But compared to the boot time after I relocked the boot loader, there was a big difference. After re-locking, it booted up in about a minute or two. Flashing TWRP even seemed to mess up some stuff. I think it may have deleted the OS or something. It couldn't mount anything afterwards and even selecting reboot boot loader gave me the prompt that there was no OS installed. So I flashed the system.img, cache.img and userdata.img manually. Which seemed to fix it. And even after I got everything straightened out, it boot up in about a minute or two again. The only time I had issues with getting it to boot is unlocking the boot loader coming from complete stock.
Click to expand...
Click to collapse
I getting the exact same thing after following instructions to root the machine
I'm not the most experience but I did my nexus 4 & 7 on 4.4.4. now on this 5.0 it seemed a lot hard this time around
I left it on boot load up screen for 3hrs and its still going round? what do I do?
Quick update: I press power +vol up + down and it comes up with the screen saving its unlocked. but the recovery mode just comes up with a android and red exclamation mark.
please help?
regards
Tom
tomistrouble said:
I getting the exact same thing after following instructions to root the machine
I'm not the most experience but I did my nexus 4 & 7 on 4.4.4. now on this 5.0 it seemed a lot hard this time around
I left it on boot load up screen for 3hrs and its still going round? what do I do?
Quick update: I press power +vol up + down and it comes up with the screen saving its unlocked. but the recovery mode just comes up with a android and red exclamation mark.
please help?
regards
Tom
Click to expand...
Click to collapse
Once you get in recovery mode with the android and the red explanation mark, hit all three buttons (Vol up , down and power) until (It can be tricky keep trying) you get a menu. Then use the volume buttons to select "Wipe Data/Factory rest" let it do its thing and reboot. Allow it to boot for 5-10 minutes.
Good luck
Hi hope I have come to the right place for help. My Nexus 7 16GB 2012 wifi is freezing after the google logo during the boot animation of the spinning circles and stays like this. I have done some reading and I can get into recovery mode and would like to retrieve pictures/personal data but I have not enabled USB debugging, have a stock rom kitkat, but not sure which version, and have a locked bootloader, not rooted. Is it possable to still get the data off of the device. If someone could point me in the right direction it would be much appreciated.
Thanks in advance for a response
Sent from my GT-I9100 using XDA Free mobile app
alscott51 said:
High hope I have come to the right place for help. My daughters Nexus 7 16GB 2012 wifi is freezing after the google logo when booting at the spinning circles and stays like this. I have done some reading and I can get into recovery mode and would like to retrieve pictures/personal data but I have not enabled USB debugging, have a stock rom kit kat, but not sure which version, and have a locked bootloader, and not rooted. Is it possable to still get the data off of the device. If someone could point me in the right direction it would be much appreciated.
Thanks in advance for a response
Sent from my GT-I9100 using XDA Free mobile app
Click to expand...
Click to collapse
Use adb pull command
Ok Im not familiar with this programme but have read a bit about it. I will try and venture into this alien world of abd and see what happens.
Sent from my GT-I9100 using XDA Free mobile app
Installed Minimal ADB and Fastoot, connected the Nexus installed the ADB driver from Asus in device manager. Booted into the bootloader and when I used "Fastboot devices" I can see my devices seial number. When I try "ADB devices" nothing is seen. I have read I need USB debugging selected and the device booted to use ADB, both of which I can not do as I am stuck in a boot loop.
Sent from my GT-I9100 using XDA Free mobile app
You can't use adb in fastboot mode. It seems possible to pull files with fastboot, but it isn't fun.
Maybe you can flash something via fastboot to make it boot again? That would be the best way imho.
alscott51 said:
Installed Minimal ADB and Fastoot, connected the Nexus installed the ADB driver from Asus in device manager. Booted into the bootloader and when I used "Fastboot devices" I can see my devices seial number. When I try "ADB devices" nothing is seen. I have read I need USB debugging selected and the device booted to use ADB, both of which I can not do as I am stuck in a boot loop.
Sent from my GT-I9100 using XDA Free mobile app
Click to expand...
Click to collapse
Go to recovery and try adb commands. In bootloader you can use only fastboot commands.
Ok I booted to the bootloader, from here selected recovery where the little Android is laying on its back. Now device manager showed nothing connected. Used the power + volume-up combo to get to the four recovery options, still nothing in device manager. Selected side load adb option and bingo welcome sound of device being connected. Windows didn't find a driver so downloaded adb driver from Asus but device manager refused to use it. Did some reading and downloaded Koush's universal driver and now device manager showed device connected and driver installed. The ADB devices command now shows the Nexus info. Now to learn the pull command. ....
Sent from my GT-I9100 using XDA Free mobile app
Done lots if reading on this and think I am beat. From what I have read the with the Nexus 7 in its current state (stock, locked bootloader, unrooted, no usb debugging) the sdcard is not reachable through the stock recovery sideload option in any way. I had a ray of hope from the above link to pull files via fastboot but I have read the thread and it seems the person says it was misleading information that they posted. I followed information in another thread and tried extracting boot, recovery and system files from a nexus factory image and flash them via fastboot but it fails stating the bootloader is locked. If I unlock the bootloader I will lose the sdcard data I want, as I will have to perform a factory reset. So as suggested I could install a CWM/TWRP recovery, but to do this via fastboot I need to unlock the bootloader......
I am thankful for people taking the time to help and for all suggestion posted but unfortunately I can not find a fix. I would be sooo grateful if someone could prove my finding wrong....
Off to do some reading about mounting the sdcard via adb shell but don't think this will work via stock recovery
Sent from my GT-I9100 using XDA Free mobile app
Install and configure any ftp/sftp/ssh server from Google play and download data wireless.
jkkk88 said:
Install and configure any ftp/sftp/ssh server from Google play and download data wireless.
Click to expand...
Click to collapse
Can't get the nexus to boot up, just bootloader and recovery accessible so don't think I'll be able to do this.
Sent from my GT-I9100 using XDA Free mobile app
Fixed it and saved all data.
Sent from my GT-I9100 using XDA Free mobile app
Sideload fix
Managed to fix this without losing anything (sdcard, docs, pictures, apps, setting etc). Took a while mostly due to lack of understanding of fastboot and ADB sideload from the recovery options.
Lots of posts advising to boot into the bootloader and use adb and fastboot. Everything I read to do with using fastboot commands via the nexus bootloader (insatalling boot/system/recovery etc) involved having an unlocked bootloader or having to unlock it as in my situation. This of course involves a factory reset of the Nexus resulting in a loss of the data that I was trying to retrieve, so i ruled this option out.
As suggested I should try the ADB pull command, but because I had not previosly enabled the USB debugging option via the setting menu everything I read said this was not an option. Read in one forum post something like "As you have not enabled USB debugging ADB is dead to you, just flash a factory image via recovery".... and lose all your data... this is not what I wanted to hear so I abandoned this option aswell.
Then I discovered sideloading. With this you can manually install an OTA update (the ones that pop up in your notification window saying something like "System update available") via the Nexus recovery option "apply update from adb". This does not invlove wiping any data , apps etc as it would just install the differences between what you are currently running eg. 4.4.2 and the updated android you want to go to eg 4.4.3. This is different to flashing a full factory image via fastboot were everything would be erased/formatted and an entirely new install would be flashed. Of course... simple when you know what the option is for and what you are doing. Of course I had had no clue what sideloading was all about.
So with my new knowledge I downloaded an OTA update from here:
http://forum.xda-developers.com/showthread.php?t=1745781&highlight=4+23
but wasnt sure what version of KitKat was running prior to the bootloop. I knew it was somewhere around 4.4.2.. so took a chance and tried KTU48L from KOT49H (4.4.3 from 4.4.2) and copied it to the Minimal ADB folder.
I booted the Nexus to the recovery mode and selected "apply update from adb". The tablet then conected to the PC (windows) as shown by Device manager. (I used Koush's universal ADB driver as windows failed to find anything of use). https://plus.google.com/103583939320326217147/posts/BQ5iYJEaaEH
I opened Minimal ADB downloaded from here
http://forum.xda-developers.com/showthread.php?t=2317790
and typed "adb devices" which showed the Nexus was connected.
I then typed "adb sideload nexus OTA file name.zip"
Lots of sending files messages appeared in the adb window the Nexus disconnected from the PC and showed this...
Finding update package...
Opening update package...
Verifying update package...
Insatlling update...
Verifying current system...
Removing unneeded files...
Patching system files...
Patching boot image....
Unpacking new files...
Unpacking new recovery...
Symlinks and permissions..
Patching remaining system files...
script succeeded: result was [/system]
Install fromADB complete.
All looked good so I rebooted the Nexus but I was still stuck in a bootloop at the four spinning circles. I tried clearing the cache from the recovery menu several times powering it down and leaving it to boot but after half an hour accepted failure.
So I tried downloading KTU84P from KTU84L (4.4.4 from 4.4.3) and repeated the procedure. this time not as much files seemed to be sent to the Nexus, I guess this was just a small update. Again it showed "script succeeded" but still failed to get past the spinning circles of the boot animation.
Thinking I was defeated again I was going to give up but tried downloading LRX21P from KTU84P (5.0 from 4.4.4). This time when I sideloaded a mass of files were sent to the Nexus much much more then the other two updates, obviously KitKat 4.4.4 to lollipop 5.0 was a big update. Again I got the "script succeeded" but this time I got the new Lollipop boot animation and the Nexus fully booted.
I can only guess that the big update to Lollipop removed or replaced files or did something to replace the faultly part of my install that other OTA updates did not change.
Anyway I did not find any other fix that advised sideloading an OTA update to fix a bootloop, maybe I just looked in the wrong places. I tried to write this in laymans terms for non techie people in the hope that it may help someone else in the same situation who like me knows very little about android.
Thanks to the forum for the information...
Also link here with some info about half way down page on effects of usb debugging being enabled for sideloading, and near the bottom of the page a good link to a sideload pdf guide.
https://productforums.google.com/forum/#!topic/nexus/Fhl6VVb0kio