So today I had a problem with an app not opening correctly so I rebooted the device. The device was stuck in the kit kat boot sequence. I turned it off and charged it. Tried booting to no avail. So I go into stock recovery mode and wiped cache and then proceeded to wipe/factory reset. It then got stuck on factory reset. I let it sit there on the charger for awhile and it was still stuck on factory reset. So i rebooted to attempt again. Now it won't even go into recovery mode. It'll boot to the fastboot screen but when trying to go into recovery it gets stuck on the white Google logo. Is there anything I can do or do I need to send it back? I bought it in July-ish so it should still be on warranty.
It should be easy to restore the stock ROM. Do you have the device drivers installed and a copy of fastboot?
http://developer.android.com/sdk/win-usb.html
http://www.xda-developers.com/andro...ng-fast-adb-fastboot-and-driver-installation/
Boot your Nexus 7 to the fastboot screen, then connect it to your PC. Open a command prompt window with administrator privileges, cd to the fastboot directory (let me know if you need help here), then type the following commands:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
This will wipe everything on your Nexus 7, preparing it for a full flash of the stock recovery and ROM. You can download the stock ROM from here, and there's a "flash-all.bat" file inside that will restore recovery and the ROM all by itself.
https://developers.google.com/android/nexus/images#razor
Pandae said:
It should be easy to restore the stock ROM. Do you have the device drivers installed and a copy of fastboot?
http://developer.android.com/sdk/win-usb.html
http://www.xda-developers.com/andro...ng-fast-adb-fastboot-and-driver-installation/
Boot your Nexus 7 to the fastboot screen, then connect it to your PC. Open a command prompt window with administrator privileges, cd to the fastboot directory (let me know if you need help here), then type the following commands:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
This will wipe everything on your Nexus 7, preparing it for a full flash of the stock recovery and ROM. You can download the stock ROM from here, and there's a "flash-all.bat" file inside that will restore recovery and the ROM all by itself.
https://developers.google.com/android/nexus/images#razor
Click to expand...
Click to collapse
when trying any commands in adb it says waiting for device and hangs on that.
Use adb if your tablet is booted into Android, and use fastboot if you're only at the bootloader.
Do you have the drivers installed? At a command prompt (again must be administrator permissions), type "fastboot devices" and see if it gives a response.
Pandae said:
Use adb if your tablet is booted into Android, and use fastboot if you're only at the bootloader.
Do you have the drivers installed? At a command prompt (again must be administrator permissions), type "fastboot devices" and see if it gives a response.
Click to expand...
Click to collapse
fastboot devices does nothing. I am in the fastboot directory. I thought I had the drivers installed, but in device manager it shows up as Android with an exclamation mark
OK, that explains it. Delete the driver by hitting Del, and just to be safe, click "View" at the top, then select to show hidden devices. Delete anything else that might be for any Android devices. Then install the drivers I linked to. They're generic drivers that work with either Nexus 7 generation, plus other Nexus devices.
Pandae said:
OK, that explains it. Delete the driver by hitting Del, and just to be safe, click "View" at the top, then select to show hidden devices. Delete anything else that might be for any Android devices. Then install the drivers I linked to. They're generic drivers that work with either Nexus 7 generation, plus other Nexus devices.
Click to expand...
Click to collapse
ok done now fastboot devices shows something, typed in fastboot erase boot and it says erasing boot...seems like it is stuck on this command
wildside84 said:
ok done now fastboot devices shows something, typed in fastboot erase boot and it says erasing boot...seems like it is stuck on this command
Click to expand...
Click to collapse
Couldn't you just try to boot a recovery IMG?
fastboot boot recovery path/to/recovery.img
That will let you run recovery without flashing it
Sent from my Nexus 7 using Tapatalk 4 Pro
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Erasing boot shouldn't take too long. Hopefully the partition isn't damaged.
SwoRNLeaDejZ, I believe he couldn't get into recovery. For problems like this, I like to erase recovery and everything else anyway, especially since flash-all.bat will restore stock recovery as part of the process.
Pandae said:
Erasing boot shouldn't take too long. Hopefully the partition isn't damaged.
SwoRNLeaDejZ, I believe he couldn't get into recovery. For problems like this, I like to erase recovery and everything else anyway, especially since flash-all.bat will restore stock recovery as part of the process.
Click to expand...
Click to collapse
no commands work. on erase recovery command it says failed command write failed invalid argument
edit: fastboot boot recovery fails also "command write failed unknown error"
edit: i get a lot of fastboot.exe has stopped working errors on windows. redownloaded platform tools and still happens. I'm at a loss I guess I have to get Google to replace it entirely
I may have taken something for granted. Did you unlock the bootloader?
fastboot oem unlock
Pandae said:
I may have taken something for granted. Did you unlock the bootloader?
fastboot oem unlock
Click to expand...
Click to collapse
no and whats funny is I just got done trying that before i read your message. i restarted the device and my computer and just decided to see if it would dirty flash the flash-all.bat and it was actually going through not giving the write errors but did say bootloader is locked. so i typed fastboot oem unlock and the screen popped up on the device to say yes or no. i selected yes and it, again, got stuck for 10-15 minutes on erasing data...rebooted the device, unlock appears to have failed. argh
If you power down and reboot back into the bootloader, it still says unlocked? What if you try unlocking again?
Pandae said:
If you power down and reboot back into the bootloader, it still says unlocked? What if you try unlocking again?
Click to expand...
Click to collapse
it says the bootloader is locked. i am trying again right now. i get to the yes no screen, select yes and on the command prompt it is stuck on erasing userdata
I've never seen it take very long. Let it sit for a while, maybe plug it in and just wait?
Pandae said:
I've never seen it take very long. Let it sit for a while, maybe plug it in and just wait?
Click to expand...
Click to collapse
ill let it sit, but i think there is something wrong with the device. i had a similar prob with a gs2 and it wouldnt erase or write anything to partition. would usb debugging have to have already been enabled? i cant remember if that was checked or not. or does that matter?
USB debugging is necessary for connecting once the tablet has booted into Android, but it isn't needed for fastboot and the bootloader level. At this point I fear there's more corruption than can be fixed, but let's wait a little while and see.
Pandae said:
USB debugging is necessary for connecting once the tablet has booted into Android, but it isn't needed for fastboot and the bootloader level. At this point I fear there's more corruption than can be fixed, but let's wait a little while and see.
Click to expand...
Click to collapse
Just received an email from Google support. They are unwilling to help because I purchased the device from Best Buy rather than Google Play...WTH? Best Buy won't help either I won't even bother. At this point I'll have to hope Asus will take it in for repair. That kind of bummed me out about Google. Not sure if I want to buy another nexus device again now.
wildside84 said:
no commands work. on erase recovery command it says failed command write failed invalid argument
edit: fastboot boot recovery fails also "command write failed unknown error"
edit: i get a lot of fastboot.exe has stopped working errors on windows. redownloaded platform tools and still happens. I'm at a loss I guess I have to get Google to replace it entirely
Click to expand...
Click to collapse
use usb jig and flash via odin nice work :good:
wildside84 said:
Just received an email from Google support. They are unwilling to help because I purchased the device from Best Buy rather than Google Play...WTH? Best Buy won't help either I won't even bother. At this point I'll have to hope Asus will take it in for repair. That kind of bummed me out about Google. Not sure if I want to buy another nexus device again now.
Click to expand...
Click to collapse
Is Google writing the book "How Not to Stand Behind Your Product"? Sheesh!
Sorry I couldn't be of more help. Good luck and speedy repairs to you. I must admit that with the touchscreen problems, and that it took someone who isn't a Google employee to fix it for a lot of people, all while Google is still silent, I myself don't care to buy another product by Google and/or Asus.
---------- Post added at 12:24 AM ---------- Previous post was at 12:18 AM ----------
VerlyAnanda said:
use usb jig and flash via odin nice work :good:
Click to expand...
Click to collapse
Odin is for Samsung devices, unless something's happened I didn't hear about.
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is a tutorial on how to return your Galaxy Nexus to stock if needed. This method uses the official images from Google
I am not to be held responsible if anything goes wrong when attempting this. This includes bricking your phone, flashing a bad image, causing WW3 etc. I am also not responsible for any files in this tutorial. They were all provided by other people.
There may be inaccuracies in this post that may lead to various things such as bricked devices so be warned. Let someone check it over first! If you see anything wrong, let me know and I will edit it!
What you need
Samsung Galaxy Nexus GSM Version
All the usual fastboot & ADB drivers etc
Fastboot
Official Google Image
Google Images
https://developers.google.com/android/nexus/images
Fastboot
DOWNLOAD
1) Take a Nandroid Backup if you have CWM installed
2) Extract the content of the Google Image
3) Copy the contents of the Fastboot download to the same folder as where you extract the Google Image too.
4) Boot your phone into the Bootloader mode
5) Open up Command Prompt or Terminal, navigate to the folder you've extracted it all too and enter the following commands waiting for each to finish
Windows
fastboot-windows flash bootloader bootloader-maguro-primekk15.img
fastboot-windows reboot-bootloader
fastboot-windows flash radio radio-maguro-i9250xxkk6.img
fastboot-windows reboot-bootloader
fastboot-windows -w update image-yakju-icl53f.zip
Linux
./fastboot-linux flash bootloader bootloader-maguro-primekk15.img
./fastboot-linux reboot-bootloader
./fastboot-linux flash radio radio-maguro-i9250xxkk6.img
./fastboot-linux reboot-bootloader
./fastboot-linux -w update image-yakju-icl53f.zip
OSX
./fastboot-mac flash bootloader bootloader-maguro-primekk15.img
./fastboot-mac reboot-bootloader
./fastboot-mac flash radio radio-maguro-i9250xxkk6.img
./fastboot-mac reboot-bootloader
./fastboot-mac -w update image-yakju-icl53f.zip
6) The last step is to lock the bootloader. Restart the phone into the bootloader
7) Open CMD in the location of Superboot and type:
fastboot-windows oem lock
Click to expand...
Click to collapse
Anyone other than the OP try this yet? If so, what state were you starting from (cwm installed, which custom rom etc) and did it work? did you need to do anything differently?
It works, can confirm!!
1. copy the extracted rom folder to clockworkmod\backup\maguro_4.0.1 on your internal storage
2. boot in too cwm
3. (what i do) in mount and storage menu, format system/data/cache
4. install super wipe lite zip file
5. restore the maguro_4.0.1 rom
phone boot up, everything fine, first run wizard start..
6. reboot to fastboot
7. flash the stock recovery "fastboot flash recovery recover.img"
8. boot in to recovery to test
9. reboot the phone
i didnt lock the bootloader while i will only root the device and other things let on stock.
i came from unlocked bootloader, clockworkmod recovery and android revolution hd rom..
Brilliant news.
I've updated the tutorial to include the latest updates
so you cant just do a erase all content and setting like you can on the iphone?
TroyBoy30 said:
so you cant just do a erase all content and setting like you can on the iphone?
Click to expand...
Click to collapse
Even on a jailbroken iPhone, when you do a factory reset you get all your settings reset but the phone is still jailbroken.
Same thing applies with Android. You need to flash the stock files to get back to stock.
@evostance
Another possibility (as yours relies on having access to a backup/nandroid as well as somehow being able to access the SDCARD partition) which some people may not have
would be Peter Alfonsos "return to stock"way
http://www.peteralfonso.com/2011/11/download-100-stock-fastboot-images-for.html
flash it via fastboot and you are golden
All you need is fastboot and the image
Evostance said:
Even on a jailbroken iPhone, when you do a factory reset you get all your settings reset but the phone is still jailbroken.
Same thing applies with Android. You need to flash the stock files to get back to stock.
Click to expand...
Click to collapse
ah i got ya. so when you say stock you mean unrooted, etc? So if i never root I can simply wipe data
Thyrus said:
@evostance
Another possibility (as yours relies on having access to a backup/nandroid as well as somehow being able to access the SDCARD partition) which some people may not have
would be Peter Alfonsos "return to stock"way
http://www.peteralfonso.com/2011/11/download-100-stock-fastboot-images-for.html
flash it via fastboot and you are golden
All you need is fastboot and the image
Click to expand...
Click to collapse
I tried that and it trashed my phone, so I had to restore to the zip above and all way fixed.
I think Peter might have changed his files now but not sure
guys have one problem, after i sucessdully restore the stock rom over the method i wrote i try it over fastboot with the original oem files from peter, erase system and user partition over fastboot and flash it again with the files on his site.. everything seems to work, and i finish with the setup from my device bit then i see in google account my calendar didnt sync, there is no entry for it.. i try to delete the account and recreate it but without success.. anybody here a idea what can ne the problem?? any suggestions how to fix that?? i dont want make the whole proceess over recovery, i like this method more while they are really empty images and not a nandroid backup..
many thanks!!
Sent from my Galaxy Nexus using XDA App
and a seccond problem.. when im listening music over power amp, when the screen goes off, the sound didnt play correct, like a scratch on a cd, jumps little bit.. here any sugestions?? (sorry for my english)
Sent from my Galaxy Nexus using XDA App
m_adnan said:
guys have one problem, after i sucessdully restore the stock rom over the method i wrote i try it over fastboot with the original oem files from peter, erase system and user partition over fastboot and flash it again with the files on his site.. everything seems to work, and i finish with the setup from my device bit then i see in google account my calendar didnt sync, there is no entry for it.. i try to delete the account and recreate it but without success.. anybody here a idea what can ne the problem?? any suggestions how to fix that?? i dont want make the whole proceess over recovery, i like this method more while they are really empty images and not a nandroid backup..
many thanks!!
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
I had the same issues hence why I wrote this tutorial as doing it this way was the only guaranteed way of getting it back to perfect stock
Evostance said:
I had the same issues hence why I wrote this tutorial as doing it this way was the only guaranteed way of getting it back to perfect stock
Click to expand...
Click to collapse
ok, im flashing now the one from paul obrian and go then back to stock recovery.. thanks
right then - officially from google
http://code.google.com/android/nexus/images.html
howto: http://groups.google.com/group/andr...a058a737b9/43c3a418144fc6c5?#43c3a418144fc6c5
Thank you
been waiting for official images
Thyrus said:
right then - officially from google
http://code.google.com/android/nexus/images.html
howto: http://groups.google.com/group/andr...a058a737b9/43c3a418144fc6c5?#43c3a418144fc6c5
Click to expand...
Click to collapse
Excellent. I'll update when home
Sent from my Galaxy Nexus using Tapatalk
Thyrus said:
right then - officially from google
http://code.google.com/android/nexus/images.html
howto: http://groups.google.com/group/andr...a058a737b9/43c3a418144fc6c5?#43c3a418144fc6c5
Click to expand...
Click to collapse
Nice of them to include the volume fix
anybody care to explain the "how to" a lil' bit more than JBQ? I'm kinda lost w/ fastboot commands
hi there..
i report a small bug whit poweramp when the screen goes off, its very easy to fix it:
- start poweramp and go to settings
- press on audio engine
- press advanced twaks
- press audio buffer size
- i choose **large (+250ms)**
after them it plays very well..
---------- Post added at 08:41 AM ---------- Previous post was at 08:39 AM ----------
Thyrus said:
right then - officially from google
http://code.google.com/android/nexus/images.html
howto: http://groups.google.com/group/andr...a058a737b9/43c3a418144fc6c5?#43c3a418144fc6c5
Click to expand...
Click to collapse
but can we flash that on lte devices??
So, when I restore my Galaxy Nexus with this method, I will have my full warranty back?
Hello, how can i boot in recovery without hardware buttons they are broken? and another thing i dont have any rom instaled, the phone i s-off with 4ext touch recovery. please help. THX:crying:
turn on the phone (u should just get stuck at white htc splash screen) then plug in to pc and open command window and type
adb devices
if ur device shows up then type
adb reboot recovery
it doesn¨t work when i turn on the phone i get to fastboot or hboot...?
capone5 said:
it doesn¨t work when i turn on the phone i get to fastboot or hboot...?
Click to expand...
Click to collapse
oh rite, thats a balls. Dont think theres any other way. Try taking the phone apart and cleaning the buttons. ul be surprised at the dust there. Hopefully that will work. If it dont then the only other way is to flash an ruu via bootloader. What does ur phone say in bootloader?
capone5 said:
it doesn¨t work when i turn on the phone i get to fastboot or hboot...?
Click to expand...
Click to collapse
Did you try running the adb commands that jmcclue listed above while in hboot?
Maybe try running fastboot commands such as "fastboot devices" to see if its recognized.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Try "fastboot devices"
capone5 said:
http://img40.imageshack.us/img40/3765/desireintrouble.jpg[/IMG ]i have install adb and when start the process i cant find device as you can see from the picture...i get in fastboot and hboot menu but i cant navigate any futher, is there a way to flash rom threw windows beyond recovery? because i do a full wipe and i dont have any rom instaled on my precious desire :(...[/QUOTE]
Hi Capone5,
One way to do it, is by downloading a recovery img ([url]http://forum.xda-developers.com/showthread.php?t=1791371[/url] or [url]http://forum.xda-developers.com/showthread.php?t=1474327[/url]) unzip and put it in the fasboot folder, plug phone in fastboot mode and type 'fastboot boot [filename].img'
Hope this helps
Click to expand...
Click to collapse
here are the pictures...when i turn on the phone it immediately go on this screen http://img708.imageshack.us/img708/9121/img20130602212615.jpg and when i try fastboot devices in cmd
capone5 said:
here are the pictures...when i turn on the phone it immediately go on this screen http://img708.imageshack.us/img708/9121/img20130602212615.jpg and when i try fastboot devices in cmd
Click to expand...
Click to collapse
You dont do "adb fastboot devices". You do "fastboot devices"
adb only works when phone is booted or stuck at boot animation, thats why i said try turning on phone then try adb while it bootloops r stuck at splash screen but his phone boots straight into bootloader. Also there is no command for fastboot to reboot recovery. Personally i would take phone apart and clean buttons, worth a shot.
@ op what boes it say in ur bootloader ?
jmcclue said:
adb only works when phone is booted or stuck at boot animation, thats why i said try turning on phone then try adb while it bootloops r stuck at splash screen but his phone boots straight into bootloader. Also there is no command for fastboot to reboot recovery. Personally i would take phone apart and clean buttons, worth a shot.
@ op what boes it say in ur bootloader ?
Click to expand...
Click to collapse
Would fastboot work without selecting it in hboot? If fastboot is able to detect the phone, then he can use "fastboot boot recovery.img" to boot into a touch based recovery like 4ext (without actually flashing it).
Heres his bootloader:
this i get when just trying fastboot devices
jmcclue said:
adb only works when phone is booted or stuck at boot animation, thats why i said try turning on phone then try adb while it bootloops r stuck at splash screen but his phone boots straight into bootloader. Also there is no command for fastboot to reboot recovery. Personally i would take phone apart and clean buttons, worth a shot.
@ op what boes it say in ur bootloader ?
Click to expand...
Click to collapse
the buttons of volume are broken and i try everything to just press - and nothing hapened...how can i load a new recovery threw fastboot?
Check your android-sdk/platform-tools/ directory to make sure the fastboot.exe is there.
If its not there, redownload the sdk and setup adb/fastboot using this guide. Also make sure you install these fastboot drivers
Then try "fastboot devices" again and hope that the phone shows up. If it does you can boot a recovery by doing this:
-Download the 4ext recovery img from here
-Extract the zip and put the recovery img in your android-sdk/platform-tools/ directory
-Run "fastboot boot recovery.img"
If its not showing up in fastboot im not really sure that you have any options, other than to do what jmcclue suggested.
capone5 said:
this i get when just trying fastboot devices
Click to expand...
Click to collapse
have u got the fastboot drivers installed on ur computer?
follow this guide to install them. u cant use fastboot unless u do.
ADB & Fastboot
chromium96 said:
Check your android-sdk/platform-tools/ directory to make sure the fastboot.exe is there.
If its not there, redownload the sdk and setup adb/fastboot using this guide. Also make sure you install these fastboot drivers
Then try "fastboot devices" again and hope that the phone shows up. If it does you can boot a recovery by doing this:
-Download the 4ext recovery img from here
-Extract the zip and put the recovery img in your android-sdk/platform-tools/ directory
-Run "fastboot boot recovery.img"
If its not showing up in fastboot im not really sure that you have any options, other than to do what jmcclue suggested.
Click to expand...
Click to collapse
i just put recovery.img in android sdk/tools folder then ran the command fastboot boot recovery.img
and guess what? im in recovery. Nice 1 chromium, it works
heres a pic
jmcclue said:
i just put recovery.img in android sdk/tools folder then ran the command fastboot boot recovery.img
and guess what? im in recovery. Nice 1 chromium, it works
Click to expand...
Click to collapse
Yep it works. Im trying to compile TWRP for the desire, so i use that command to temporarily test it rather than actually flashing it.
chromium96 said:
Yep it works. Im trying to compile TWRP for the desire, so i use that command to temporarily test it rather than actually flashing it.
Click to expand...
Click to collapse
its handy to know coz im pretty sure hardly anyone knows that and i bet u cant find it on the old interweb lol
Hi guys,
Sorry if this is in the wrong forum. I've searched around but can't find anyone with quite the same issue as myself.
I returned to my desk at work to find that my nexus 7 2013, latest stock Android OS installed, was stuck on the Google logo screen. It was switched on previously and charging via my work PC at the time.
A few points about what is happening with the Nexus:
I can get to the bootloader but it says "E: failed to mount /cache (invalid arguement), E: can't mount /cache recovery log, E: can't open /cache recovery/log..." you get the idea
The third line from the end says "e: failed closing /dev/block/platform/msm_sdcc.1/by-name/misc (i/o error), e: failed to mount cache (invalid arguement).
if I select wipe cache from the bootloader I see the same error
I selected wipe data and this seems to work, before giving me the above error again
I've seen about the Wugfresh and Unified toolkit and I have tried them. But the big problem seems to be that neither my work PC or home laptop detects that my Nexus is plugged into them via USB. If I could solve that I think I'd be able to restore, right?
I'm also really intrigued as to how this happened. I've never rooted this Nexus. The most advanced thing I've done with it is to install Nova Launcher and that was over 6 months ago. Weird how it can just suddenly go wrong.
Any help would be greatly appreciated.
Just to add, with the Wug/Nexus Toolkit I've been through the driver installation program and whilst I can get the ADB Interface driver to install, when I'm in the bootloader the Nexus doesn't show in Device Manager and using the "Soft-bricked" option and then "Flash Stock + Unroot" I get an error that no fastboot device could be found.
Have you checked your control panel inside device manager? Your nexus 7 could be listed as a unknown device under other devices, or listed as a nexus 7.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If so. it's a matter of just installing the right drivers, you can install the official Google drivers and choose the bootloader driver when installing.
http://developer.android.com/sdk/win-usb.html
If you get some compatibility error while installing the drivers, just ignore it and continue.
edit: just noticed your 2nd post. nevermind.
Maverick-DBZ- said:
Have you checked your control panel inside device manager? Your nexus 7 could be listed as a unknown device under other devices, or listed as a nexus 7.
If so. it's a matter of just installing the right drivers, you can install the official Google drivers and choose the bootloader driver when installing.
If you get some compatibility error while installing the drivers, just ignore it and continue.
edit: just noticed your 2nd post. nevermind.
Click to expand...
Click to collapse
Thanks for trying! Yep, nothing shows up if I'm in bootloader mode.
I've installed the adb interface driver and if I reboot the Nexus and leave it for a while *sometimes* an "Android Device" will display in Device Manager.
All the instructions say enable USB debugging, disable MTP but I can't do that because it won't turn on! I am pretty much saying this - "I installed the drivers but it still says ADB/Fastboot device not found! What should I do?" which is a page on wugfresh, but I'm new and can't post links- but even this doesn't cover if the device won't boot at all.
teamcooperuk said:
Thanks for trying! Yep, nothing shows up if I'm in bootloader mode.
I've installed the adb interface driver and if I reboot the Nexus and leave it for a while *sometimes* an "Android Device" will display in Device Manager.
All the instructions say enable USB debugging, disable MTP but I can't do that because it won't turn on! I am pretty much saying this - "I installed the drivers but it still says ADB/Fastboot device not found! What should I do?" which is a page on wugfresh, but I'm new and can't post links- but even this doesn't cover if the device won't boot at all.
Click to expand...
Click to collapse
Ok, I was being dumb.
I was starting up using power+volume up. Realised power+volume down gets me to bootloader and that I was in recovery mode before.
So I used the Wugfresh "Flash Stock and Unroot" option. This seemed to be going well except I get told my bootloader is locked.
The I tried to use the Unlocker tool in Wugfresh. This tells me it can't detect an ADB device, but when I hit cancel the unlock bootloader screen opens. And then hangs when I select unlock!
What can I try next?!
Do you know how to use ADB manually with a dos prompt? Kits are nice and they help a lot, but sometimes they don't work right and get in the way.
Code:
fastboot oem unlock
The above command is what you need to unlock your bootloader. If you see a little lock below the Google logo at startup, you've unlocked your bootloader. You're on a Nexus 7 2013 Wi-Fi right?
If it still freezes when unlocking, you could try opening the tablet and disconnecting the battery for a little bit, and then putting everything back together again. For some reason it seems to work for some people.
Maverick-DBZ- said:
Do you know how to use ADB manually with a dos prompt? Kits are nice and they help a lot, but sometimes they don't work right and get in the way.
Code:
fastboot oem unlock
The above command is what you need to unlock your bootloader. If you see a little lock below the Google logo at startup, you've unlocked your bootloader. You're on a Nexus 7 2013 Wi-Fi right?
If it still freezes when unlocking, you could try opening the tablet and disconnecting the battery for a little bit, and then putting everything back together again. For some reason it seems to work for some people.
Click to expand...
Click to collapse
I don't - do I just open a cmd prompt window, navigate to where fastboot is and run that command with the Nexus connected via USB and in the bootloader?
I tried an alternative toolkit, the unified one. The UI of that is a cmd prompt window. That shows me that it hangs during the unlock bootloader process where it is "erasing user data", I left it for 8 hours overnight and it was still hanging.
Does it sound totally bricked?
teamcooperuk said:
I don't - do I just open a cmd prompt window, navigate to where fastboot is and run that command with the Nexus connected via USB and in the bootloader?
I tried an alternative toolkit, the unified one. The UI of that is a cmd prompt window. That shows me that it hangs during the unlock bootloader process where it is "erasing user data", I left it for 8 hours overnight and it was still hanging.
Does it sound totally bricked?
Click to expand...
Click to collapse
Yes, correct.
As a possible solution, run the below fastboot command. Must be in bootloader menu for this to work. See image below.
Code:
fastboot format cache
Then boot to recovery and do a factory reset.
If it still hangs, try downgrading to a lower android version, 4.3 is a good start. If the process fails, post on what step it failed.
Maverick-DBZ- said:
Yes, correct.
As a possible solution, run the below fastboot command. Must be in bootloader menu for this to work. See image below.
Code:
fastboot format cache
Then boot to recovery and do a factory reset.
If it still hangs, try downgrading to a lower android version, 4.3 is a good start. If the process fails, post on what step it failed.
Click to expand...
Click to collapse
I'm getting an error when I try to run these commands. It complains that ADBwinAPI.dll isn't installed. Tryed using regsvr32 to do so but that also gives me an error.
Trying to use Eclipse to run these commands now but it looks like this could be a wormhole of settings beyond my technical ability!
Just to add, I tried to format the cache using the power+volume up screens. I just get the cache errors listed in the original post.
Maverick-DBZ- said:
Yes, correct.
As a possible solution, run the below fastboot command. Must be in bootloader menu for this to work. See image below.
Code:
fastboot format cache
Then boot to recovery and do a factory reset.
If it still hangs, try downgrading to a lower android version, 4.3 is a good start. If the process fails, post on what step it failed.
Click to expand...
Click to collapse
teamcooperuk said:
I'm getting an error when I try to run these commands. It complains that ADBwinAPI.dll isn't installed. Tryed using regsvr32 to do so but that also gives me an error.
Trying to use Eclipse to run these commands now but it looks like this could be a wormhole of settings beyond my technical ability!
Just to add, I tried to format the cache using the power+volume up screens. I just get the cache errors listed in the original post.
Click to expand...
Click to collapse
Ok, found the adb client in the platform-tools sdk directory. Running the unlock I get the same problem, the hang on erasing userdata:
Code:
C:\Users\xxxxxxxx\Documents\Google_Drivers\adt-bundle-windows-x86_64-20140702\sdk\pl
atform-tools>fastboot oem unlock
...
(bootloader) Unlocking bootloader...
(bootloader) erasing userdata...
Just kicked off the erasing cache command...looks like that's hanging too after 30 seconds....should finsih pretty quickly, right?
Off to Asus I go I think!
No need to run the bootloader command. If it still hangs after the below command and nothing else, then it's time to call Asus and RMA it. :crying:
Code:
fastboot format cache
Part of your NAND is likely toast and why the cache partition won't erase.
So I'm an idiot. I deleted everything off my Nexus 7 then I was going to flash to a new ROM, didn't work, I don't know why but it won't install. I have nothing else to install, not any other ROMs and no backups. To make the whole entire thing worse, my Nexus wont connect to my computer. Before you say to reinstall the drivers or plug it into another computer, I have, I've tried everything and nothing works. So my question is; Am I screwed or is there somehow a way to install a new ROM (seems impossible) or put the stock ROM back on? I tried the adb sideload method but I was completely unsuccessful as well as every other method I've seen/could come up with. After trying weeks to get anything back on my Nexus 7 I'm just about ready to toss this paperweight in my drawer and forget abaout it
Which modes can you get into?
TWRP allows you to mount USB OTG. Try flashing something from there.
Press Thanks If I Helped You!
Sent from my dead Nexus 7 2013 LTE! ???
Yes, like aniket0317 wrote: if all else has failed, put a ROM on a flash drive, connect it with a USB OTG adapter, and use TWRP.
I've lately had trouble getting my N7 recognized while in recovery mode, though everything's fine while in the bootloader and Android. But with TWRP it's easy to mount external flash storage and install from that.
RecklessBrandon said:
So I'm an idiot. I deleted everything off my Nexus 7 then I was going to flash to a new ROM, didn't work, I don't know why but it won't install. I have nothing else to install, not any other ROMs and no backups. To make the whole entire thing worse, my Nexus wont connect to my computer. Before you say to reinstall the drivers or plug it into another computer, I have, I've tried everything and nothing works. So my question is; Am I screwed or is there somehow a way to install a new ROM (seems impossible) or put the stock ROM back on? I tried the adb sideload method but I was completely unsuccessful as well as every other method I've seen/could come up with. After trying weeks to get anything back on my Nexus 7 I'm just about ready to toss this paperweight in my drawer and forget abaout it
Click to expand...
Click to collapse
are you able to go into fastboot mode? if so you still have hope
kmaq said:
are you able to go into fastboot mode? if so you still have hope
Click to expand...
Click to collapse
I'm not allowed to post pictures yet but I believe I can get in fastboot mode and I am sure that I can get into ClockworkMod Recovery
RecklessBrandon said:
So I'm an idiot. I deleted everything off my Nexus 7 then I was going to flash to a new ROM, didn't work, I don't know why but it won't install. I have nothing else to install, not any other ROMs and no backups. To make the whole entire thing worse, my Nexus wont connect to my computer. Before you say to reinstall the drivers or plug it into another computer, I have, I've tried everything and nothing works. So my question is; Am I screwed or is there somehow a way to install a new ROM (seems impossible) or put the stock ROM back on? I tried the adb sideload method but I was completely unsuccessful as well as every other method I've seen/could come up with. After trying weeks to get anything back on my Nexus 7 I'm just about ready to toss this paperweight in my drawer and forget abaout it
Click to expand...
Click to collapse
RecklessBrandon said:
I'm not allowed to post pictures yet but I believe I can get in fastboot mode and I am sure that I can get into ClockworkMod Recovery
Click to expand...
Click to collapse
download the 4.4.4 image
go to fastboot mode, connect the usb cable to laptop/pc
open command prompt and go to the folder where you have extracted the 4.4.4 image
fastboot oem unlock
type flash-all.bat
if all goes well device should reboot (initally will take some time) if it took more time, reboot again into fastboot mode
this time you can try manually commands one by one
in the folder where you have extracted the 4.4.4 image you will fine "image-razor-ktu84p.zip", extract this zip file as well
execute the following commands one by one:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot reboot-bootloader
fastboot flash bootloader bootloader-flo-flo-04.02.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash system system.img
fastboot reboot
device should reboot and if it displays language screen then cool complete the wizard, reboot in to fastboot mode again to lock the bootloader
fastboot oem lock
fastboot reboot
and enjoy!!! do report back what happens.
fastboot -w update stockrom.zip
I'm a little confused on the instructions, also, as mentioned, my Nexus isn't recognized by my computer no matter what I try.
How does it appear in Device Manager? Have you downloaded and installed the drivers?
http://developer.android.com/sdk/win-usb.html
RecklessBrandon said:
I'm a little confused on the instructions, also, as mentioned, my Nexus isn't recognized by my computer no matter what I try.
Click to expand...
Click to collapse
in the fastboot mode, after connecting your device to laptop/pc,
if you type "fastboot reboot-bootloader" in the command prompt
what happens?
I am having the exact same problem, it was installing got stuck on "erasing userdata" for over 2 hours and now nothing will work except for fastboot, and some how the device locked itself again. Only thing i can get to is fastboot mode, the computer recognizes the device. When I try to unlock it, it gets stuck in "erasing userdata" I let it run over night last night hoping it would some how work with no luck. I am unsure of what to do. Is there anyway to install a factory OS without unlocking? Every guide I've searched for has me doing an fastboot oem unlock and then the tablet freezes on erasing userdata. Any help would be greatly appreciated. Thanks!
kmaq said:
in the fastboot mode, after connecting your device to laptop/pc,
if you type "fastboot reboot-bootloader" in the command prompt
what happens?
Click to expand...
Click to collapse
Reread your initial instructions, and it worked! Thank you so much!!!
Does anyone have the MSMTOOL for LE2120? bricked my phone when trying to patch the boot.img to magisk version...
Now totally stuck... even adb commands to restore does not work...
danjcxie said:
Does anyone have the MSMTOOL for LE2120? bricked my phone when trying to patch the boot.img to magisk version...
Now totally stuck... even adb commands to restore does not work...
Click to expand...
Click to collapse
What did you do to try to patch it? Why are you in adb? Does fastboot work?
craznazn said:
What did you do to try to patch it? Why are you in adb? Does fastboot work?
Click to expand...
Click to collapse
Patched the boot.img using magisk and then flashed it. After patching, it totally cant boot and can only boot to bootloader.
tried alot of version of MSMtool and it will always fail with param preload error...
Then tried manually recover via extracting the payload using python then using adbtools to wipe and flash but it will also fail because some img files are unable to flash over to the phone...
Any other solutions?
U not able to flash boot the stock boot.img?
i am able to flash the stock boot.img to the phone but some critical img files will come out with
FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
You need to be in fastbootd,
Code:
fastboot reboot fastboot
craznazn said:
You need to be in fastbootd,
Code:
fastboot reboot fastbootd
Click to expand...
Click to collapse
Nope not working too...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
danjcxie said:
Nope not working too...
View attachment 5281163
Click to expand...
Click to collapse
Sorry, fastboot reboot fastboot (without the d)
@danjcxie
To be honest, I would download the rom and boot with the recovery image instead, I'll upload the image collection...
Will post a link here once it's up.
Actually, just noticed there isn't a recovery image, so boot to the default boot.img using fastboot, then see if the storage shows on your computer, copy the latest default rom over to the main storage folder then then go into Settings > System > System Updates and use the cog to do a local update using the rom zip.
That should re-install everything back to default, you might get lucky and still have all your data
My collection is for the Europe build FYI:
OP9P_Image_Collection_BA_11.2.3.3.zip | by djsubterrain for OnePlus 9 Pro
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
MD5 : 00227014483b4913a2624fac6f492434
So you would reboot the phone into fastboot mode by holding vol up during boot
Once you are in fastboot mode connect the phone to your computer
Test that the computer can see it properly using fastboot devices
You should see a number returned, if so then your computer is recognising the phone, if you don't then try installing the latest drivers from here
If fastboot can see the device properly then copy the default boot.img to the same folder as your fastboot.exe and type the following :
fastboot boot boot.img
You should see a message saying it's transferring it to the phone, then it should boot the phone using it, it's slower than a normal boot but, if everything else on the phone is ok, then you should see it booted and it should accept your lock method
Once you get into the phone using that boot.img, try connecting the phone to your computer and see if it's recognised, if it is then copy over the latest stock rom to your main storage folder, then go to Settings > System > System Updates and use the cog to do a local update using the rom zip
I'm guessing it should let you because it will see a difference between your boot image and the one from the rom.
MSM tool for LE2125 - 11.2.2.2.LE15AA
User Type of Others for login MSM Tool for LE2125 - 11.2.2.2.LE15AA Drivers Mirrors: (provided by @djsubterrain) MSM Tool : https://sourceforge.net/projects/djsubterrain/files/OnePlus 9 Pro/OP9P_MSM_Tool.zip/download MD5 ...
forum.xda-developers.com
New problem... After i did fastboot reboot fastboot, it shows low battery whole day and is unable to charge totally... it has been charging the whole day now and totally cant turn on at all.
it keeps showing the lightning sign in the centre of the circle keeps blinking and dies off
danjcxie said:
New problem... After i did fastboot reboot fastboot, it shows low battery whole day and is unable to charge totally... it has been charging the whole day now and totally cant turn on at all.
it keeps showing the lightning sign in the centre of the circle keeps blinking and dies off
View attachment 5281971
Click to expand...
Click to collapse
Turn it off and try charging it
Also "fastboot reboot fastboot" isn't a valid command, there is an adb command "adb reboot bootloader" but that can only be run from within your rom from when you are in recovery with the phone connected
See here :
Fastboot Commands: A Beginner’s Guide
With this guide of ours, you'll be able to learn all the fastboot commands and their syntax. We've also posted some hidden commands which you never knew.
android.tutorials.how
#To reboot your device
fastboot reboot
#To reboot your device to fastboot mode
fastboot reboot-bootloader
Click to expand...
Click to collapse
djsubterrain said:
Turn it off and try charging it
Click to expand...
Click to collapse
Yup tried. Everytime you just plug in the charging cable, it will just auto boot up and show the charging sign
danjcxie said:
Yup tried. Everytime you just plug in the charging cable, it will just auto boot up and show the charging sign
Click to expand...
Click to collapse
Yeah that symbol isn't what I get, I get a blue lightning sign with the percentage underneath. Are you running OxygenOS or ColorOS?
I think it might be time for you to contact OnePlus support
djsubterrain said:
Turn it off and try charging it
Also "fastboot reboot fastboot" isn't a valid command, there is an adb command "adb reboot bootloader" but that can only be run from within your rom from when you are in recovery with the phone connected
See here :
Fastboot Commands: A Beginner’s Guide
With this guide of ours, you'll be able to learn all the fastboot commands and their syntax. We've also posted some hidden commands which you never knew.
android.tutorials.how
Click to expand...
Click to collapse
Wtf are you talking about. fastboot reboot fastboot is literally the only way to get into fastbootd if you can't get to recovery or boot normally.
Regarding battery, that I'm not sure, hopefully someone can help
craznazn said:
OP
Wtf are you talking about. fastboot reboot fastboot is literally the only way to get into fastbootd if you can't get to recovery or boot normally.
Regarding battery, that I'm not sure, hopefully someone can help
Click to expand...
Click to collapse
OK, firstly, who the hell do you think you're talking to?
Secondly, did you look at the link I posted?
djsubterrain said:
OK, firstly, who the hell do you think you're talking to?
Secondly, did you look at the link I posted?
Click to expand...
Click to collapse
Who the hell are you? Why the hell are you linking "tutorials.how"?
fastboot/fastboot.cpp - platform/system/core - Git at Google
android.googlesource.com
Lines 2178, source tells you to reboot fastbootd by reboot fastboot.
Show me it's not a valid command, go on
craznazn said:
Who the hell are you? Why the hell are you linking "tutorials.how"?
fastboot/fastboot.cpp - platform/system/core - Git at Google
android.googlesource.com
Lines 2178, source tells you to reboot fastbootd by reboot fastboot.
Show me it's not a valid command, go on
Click to expand...
Click to collapse
Go ahead and help the guy solve his problem.
Just remember it's fastboot, not fastbootd.
Now, how do you block people on here again?
danjcxie said:
Does anyone have the MSMTOOL for LE2120? bricked my phone when trying to patch the boot.img to magisk version...
Now totally stuck... even adb commands to restore does not work...
Click to expand...
Click to collapse
use the MSM Tool with the latest drivers
QDLoader HS-USB Driver_64bit_Setup
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
danjcxie said:
Does anyone have the MSMTOOL for LE2120? bricked my phone when trying to patch the boot.img to magisk version...
Now totally stuck... even adb commands to restore does not work...
Click to expand...
Click to collapse
This just worked for me minutes ago
OP9Pro - Repository of MSM Unbrick Tools (TMO, EU, GLO, IN)
By using these tools, you accept full responsibility for your actions. Your warranty is void should you run any of these utilities without OnePlus support present. I am not responsible for bricks, fires, nuclear war, etc. If you modified any...
forum.xda-developers.com
i downloaded Indian Variant LE2121 while my phone is LE2120 ant it worked