I am an idiot.
Today I decided I would play around with some different ROMs. All was going well. I was becoming adept at flashing, booting, restoring, repeat.
All the ROMs I had tried up to this point were 4.3. I decided to go with something different. I installed OmniRom, which went okay, other than the fact it wouldn't recognize WiFi signals.
As any modern-day geek would do, I took to Google. I found a pretty promising solution that had me flash a firmware zip. This the point at which I made my mistake. As I should have remembered, firmware is DEVICE SPECIFIC. I did not bother to look at what device it was for as I had included "2013 Nexus 7" in my Google search.
The zip I flashed was for the Oppo Find 5. Facepalm.
My device will now not boot at all. I have tried charging for an hour or two from a computer, then a wall charger. The computer does not recognize the device. I've tried every possible button combination to get into recovery, fastboot, normal boot, etc. None have worked.
Anyone have any ideas?
What kind of firmware was it? Bootloader?
Sent from my Nexus 7 (2013) using Tapatalk 4
Muikkuman said:
What kind of firmware was it? Bootloader?
Sent from my Nexus 7 (2013) using Tapatalk 4
Click to expand...
Click to collapse
It was just firmware to help with network, called "modem-4.1.zip"
Blockerville said:
I am an idiot.
Today I decided I would play around with some different ROMs. All was going well. I was becoming adept at flashing, booting, restoring, repeat.
All the ROMs I had tried up to this point were 4.3. I decided to go with something different. I installed OmniRom, which went okay, other than the fact it wouldn't recognize WiFi signals.
As any modern-day geek would do, I took to Google. I found a pretty promising solution that had me flash a firmware zip. This the point at which I made my mistake. As I should have remembered, firmware is DEVICE SPECIFIC. I did not bother to look at what device it was for as I had included "2013 Nexus 7" in my Google search.
The zip I flashed was for the Oppo Find 5. Facepalm.
My device will now not boot at all. I have tried charging for an hour or two from a computer, then a wall charger. The computer does not recognize the device. I've tried every possible button combination to get into recovery, fastboot, normal boot, etc. None have worked.
Anyone have any ideas?
Click to expand...
Click to collapse
I was able to experience a HARD BRICK myself but it was because I flashed a 4.3.1 update on top of a 4.3 once which led me to go into the TWRP recovery and delete my SYSTEM AND INTERNAL STORAGE by accident.
Don't fret my friend. If you're experiencing the supposed HARD BRICK I experienced before (wherein it does not turn on at all), all you have to do is this:
- download the WugFresh N7 toolkit and look for a thread/try to discover how to unbrick your device using that. (they have a specific option for that actually; THANK YOU WUGFRESH)
- download the necessary factory image of your choice and binaries from this page (courtesy of google https://developers.google.com/android/nexus/images)
- You will see a button for at the WugFresh toolkit with instructions on how to unbrick your thing.
Hit thanks if this helps and if you have any more questions, feel free to reply
MartCLEANRFr said:
I was able to experience a HARD BRICK myself but it was because I flashed a 4.3.1 update on top of a 4.3 once which led me to go into the TWRP recovery and delete my SYSTEM AND INTERNAL STORAGE by accident.
Don't fret my friend. If you're experiencing the supposed HARD BRICK I experienced before (wherein it does not turn on at all), all you have to do is this:
- download the WugFresh N7 toolkit and look for a thread/try to discover how to unbrick your device using that. (they have a specific option for that actually; THANK YOU WUGFRESH)
- download the necessary factory image of your choice and binaries from this page
- You will see a button for at the WugFresh toolkit with instructions on how to unbrick your thing.
Hit thanks if this helps and if you have any more questions, feel free to reply
Click to expand...
Click to collapse
There's an option for a soft-bricked device (will turn on, just stuck in a bootloop). However, I don't see the option for a hard-bricked device.
Anyway, I'll try the soft-bricked solution and see if that works.
EDIT: Yep, doesn't seem to be working. It requires the tablet to be in Fastboot mode, which I cannot get into, because the tablet will not boot at all.
Which option did you use to unbrick your tablet?
Still no luck. Any ideas?
Did you try to start into bootloader ?
Nexus off, press volume buttons and power simultaneously.
lapocompris said:
Did you try to start into bootloader ?
Nexus off, press volume buttons and power simultaneously.
Click to expand...
Click to collapse
Yes, I tried that multiple times.
You could try to download the factory image (https://developers.google.com/android/nexus/images), extract the files into the adb platform-tools folder, open a command window and run flash-all.bat
lapocompris said:
You could try to download the factory image (https://developers.google.com/android/nexus/images), extract the files into the adb platform-tools folder, open a command window and run flash-all.bat
Click to expand...
Click to collapse
I will try that. However I do not think it will work, considering the tablet will not boot, so adb will probably not work.
But it's worth a try.
lapocompris said:
You could try to download the factory image (https://developers.google.com/android/nexus/images), extract the files into the adb platform-tools folder, open a command window and run flash-all.bat
Click to expand...
Click to collapse
Yeah doesn't work. adb doesn't see the Nexus.
Blockerville said:
Yeah doesn't work. adb doesn't see the Nexus.
Click to expand...
Click to collapse
Just an update -- sending in the tablet to SquareTrade as I purchased an extended warranty. However I only have $60 coverage at the moment because I already had the screen repaired. If they can't repair it, I'll be getting $60 to put toward buying a new Nexus. I hope all goes well :fingers-crossed:.
So, Nexus devices aren't unbrickable after all?
antypas said:
So, Nexus devices aren't unbrickable after all?
Click to expand...
Click to collapse
They usually are, but if you jack up the boot loader then you're done for.
prshosting.org
Hey Blockerville,
Have you tried this: http://forum.xda-developers.com/showthread.php?t=2381582 ?
Hey guys... i have almost the same problem. I have hard-bricked my nexus 7.
I can go to the Bootloader, but i'm not able to make the pc see the device. I tried installing usb drivers in all the ways, but when in the terminal i go in the sdk directory, and i write "adb devices", it doesn't see anything.......
Is there a way to solve this problem..?
Thanks in advances.
met97 said:
Hey guys... i have almost the same problem. I have hard-bricked my nexus 7.
I can go to the Bootloader, but i'm not able to make the pc see the device. I tried installing usb drivers in all the ways, but when in the terminal i go in the sdk directory, and i write "adb devices", it doesn't see anything.......
Is there a way to solve this problem..?
Thanks in advances.
Click to expand...
Click to collapse
While in bootloader mode, try:
fastboot devices
...not adb devices.
mdamaged said:
While in bootloader mode, try:
fastboot devices
...not adb devices.
Click to expand...
Click to collapse
IT WORKS!
Writing the command "fastboot devices" it sees the device. Now what should i do? I just want to wipe all, reinstal the recovery and flash the factory image... What command i have to write?
PS: Currently recovery doesn't work, for that i need to reinstall it..
met97 said:
IT WORKS!
Writing the command "fastboot devices" it sees the device. Now what should i do? I just want to wipe all, reinstal the recovery and flash the factory image... What command i have to write?
Click to expand...
Click to collapse
Whoa, whoa, I can't tell you what to do next until I know what you've already done, or didn't do.
Please answer the following:
Did you get the correct factory image? <-- very very important
What device do you have (FLO or DEB), I'll assume you know for sure you have the Nexus 7 2013 and NOT the Nexus 7 2012 model.
Which image did you download (so I can check). FLO is wifi, DEB has the LTE.
You do know it will revert your device to like how you got it? So make backups if possible. (you can edit the batch file and remove the -w to prevent wiping).
The following is for when you make sure you have everything right, do not do the following if you are not sure, you should answer those questions above first and I will let you know if it is ok to proceed to the stuff below.
You will need at least these files in a directory before you can do it:
From the factory tgz (once unzipped):
bootloader-flo-flo-04.02.img
flash-all.bat
flash-all.sh
flash-base.sh
image-razor-kot49h.zip
And at least these files from the dev kit:
fastboot.exe
You don't need the following for this operation, but it does not hurt:
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
If all that checks out and you verified everything is right, you just do:
flash-all.bat
That will flash EVERYTHING, bootloader, recovery, system, data, cache and userdata.
mdamaged said:
Whoa, whoa, I can't tell you what to do next until I know what you've already done, or didn't do.
Please answer the following:
Did you get the correct factory image? <-- very very important
What device do you have (FLO or DEB), I'll assume you know for sure you have the Nexus 7 2013 and NOT the Nexus 7 2012 model.
Which image did you download (so I can check). FLO is wifi, DEB has the LTE.
You do know it will revert your device to like how you got it? So make backups if possible. (you can edit the batch file and remove the -w to prevent wiping).
You will need at least these files in a directory before you can do it:
From the factory tgz (once unzipped):
bootloader-flo-flo-04.02.img
flash-all.bat
flash-all.sh
flash-base.sh
image-razor-kot49h.zip
And at least these files from the dev kit:
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot.exe
If all that checks out and you verified everything is right, you just do:
flash-all.bat
That will flash EVERYTHING, bootloader, recovery, system, data, cache and userdata.
Click to expand...
Click to collapse
Yes, you're right........
Well: i got the right factory image, but, sorry for that, when i was searching a solution for my problem, i have found this thread, and i didn't notice that this is for the 2013 model..... well, i've got the 2012 model. And thank you for asking that........ =S
It is the wifi model...
About the backup... i don't really care about the files, i don't actually need to do a back up.
This files:
From the factory tgz (once unzipped):
bootloader-flo-flo-04.02.img
flash-all.bat
flash-all.sh
flash-base.sh
image-razor-kot49h.zip
Click to expand...
Click to collapse
can be in a casual directory? Or they should be in the sdk directory?
the command to flash is....?
Related
Hi I attempted to root my phone, got SU but was having problems flashing any roms, using any apps that required /root or accessing recovery. Figured something might not have worked and tried to unroot and start again. All steps were followed via http://forums.androidcentral.com/ve...-root-unroot-unlock-your-vz-galaxy-nexus.html
I'm stuck in the Google bootscreen with my only other option being bootloader, it still says Locked State - Unlocked. But my computer can't see my phone, Odin doesn't work and I still don't have a definitive method of restoring my phone via a MAC.
This ISN'T Resolved. I get errors when attempting to fastboot the stock image
~/Desktop/adb-fastboot/adb reboot bootloader
brings about the following error
"error: device not found"
I was already in bootloader and tried:
~/Desktop/adb-fastboot/fastboot flash boot ~/Desktop/adb-fastboot/boot.img
I get:
error: cannot load '/Users/grnmons/Desktop/adb-fastboot/boot.img'
If anybody has any ideas please let me know, I really don't know what to do at this point.
grnmons said:
Hi I attempted to root my phone, got SU but was having problems flashing any roms, using any apps that required /root or accessing recovery. Figured something might not have worked and tried to unroot and start again. All steps were followed via http://forums.androidcentral.com/ve...-root-unroot-unlock-your-vz-galaxy-nexus.html
I'm stuck in the Google bootscreen with my only other option being bootloader, it still says Locked State - Unlocked. But my computer can't see my phone, Odin doesn't work and I still don't have a definitive method of restoring my phone via a MAC.
If anybody has any ideas please let me know, I really don't know what to do at this point. Plan B is to use a PC which I can only access later in the week. If you know someone, or have a link I would really appreciate it. Also ask me anything if it can help make this clearer.
Thanks
Click to expand...
Click to collapse
Okay your bootloader is unlocked which is good, but your MAC doesn't see your phone in bootloader mode?
grnmons said:
Plan B is to use a PC which I can only access later in the week.
Click to expand...
Click to collapse
Can you bootcamp or use a virtual machine?
grnmons said:
Hi I attempted to root my phone, got SU but was having problems flashing any roms, using any apps that required /root or accessing recovery. Figured something might not have worked and tried to unroot and start again. All steps were followed via http://forums.androidcentral.com/ve...-root-unroot-unlock-your-vz-galaxy-nexus.html
I'm stuck in the Google bootscreen with my only other option being bootloader, it still says Locked State - Unlocked. But my computer can't see my phone, Odin doesn't work and I still don't have a definitive method of restoring my phone via a MAC.
If anybody has any ideas please let me know, I really don't know what to do at this point. Plan B is to use a PC which I can only access later in the week. If you know someone, or have a link I would really appreciate it. Also ask me anything if it can help make this clearer.
Thanks
Click to expand...
Click to collapse
Wrong section..but
I would def use a PC and use Odin ! Make your life easier...it takes like 3-5 Mins..takes it to stock!
Sent from my Galaxy Nexus using xda premium
All you have to do is fastboot flash those stock images of 4.0.2 google gave us. There's not even any need for Odin. You can do this right on your Mac.
Sent from my Galaxy Nexus using Tapatalk
Please uninstall and reinstall your phones drivers. Your just soft bricked is all. Once your computer sees the device you should be good.
sent from the Almighty One himself....
borgey said:
All you have to do is fastboot flash those stock images of 4.0.2 google gave us. There's not even any need for Odin. You can do this right on your Mac.
Click to expand...
Click to collapse
I can't seem to figure out how to do that. Seems like that's what got me here in the first place, the mac version might be missing files I'm missing the steps to actually do that.
Can't find any forum/site/guide that tells me how to do that. Does anybody have this?
grnmons said:
I can't seem to figure out how to do that. Seems like that's what got me here in the first place, the mac version might be missing files I'm missing the steps to actually do that.
Can't find any forum/site/guide that tells me how to do that. Does anybody have this?
Click to expand...
Click to collapse
fastboot flash (google on how to use these)
you do them when you're in bootloader mode. you need to have a ADB/Fastboot environment set up (look at root guides and do step one of it..... verifying the part of getting the environment, ignore drivers)
stock images are here: http://code.google.com/android/nexus/images.html
zephiK said:
fastboot flash (google on how to use these)
you do them when you're in bootloader mode. you need to have a ADB/Fastboot environment set up (look at root guides and do step one of it..... verifying the part of getting the environment, ignore drivers)
stock images are here: http://code.google.com/android/nexus/images.html
Click to expand...
Click to collapse
Thanks. Can you confirm that these are the steps?
1) Download the latest stock image( i will leave finding that image to you since this post can become outdated)
2) Unzip the files, and place the images into the adb-fastboot folder you created on your desktop above.
3) Open a terminal and use the following commands:
Code:
~/Desktop/adb-fastboot/adb reboot bootloader
4) Wait for bootloader to reboot on phone.
5) Then, in terminal use the following commands:
~/Desktop/adb-fastboot/fastboot flash boot ~/Desktop/adb-fastboot/boot.img
~/Desktop/adb-fastboot/fastboot flash system ~/Desktop/adb-fastboot/system.img
~/Desktop/adb-fastboot/fastboot flash recovery ~/Desktop/adb-fastboot/recovery.img
~/Desktop/adb-fastboot/fastboot flash userdata ~/Desktop/adb-fastboot/userdata.img
~/Desktop/adb-fastboot/fastboot erase cache
~/Desktop/adb-fastboot/fastboot oem lock
6) Reboot to System, and you should be returned to Stock and Unrooted
~/Desktop/adb-fastboot/adb reboot bootloader
brings about the following error
"error: device not found"
I was already in bootloader and tried:
~/Desktop/adb-fastboot/fastboot flash boot ~/Desktop/adb-fastboot/boot.img
I get:
error: cannot load '/Users/grnmons/Desktop/adb-fastboot/boot.img'
anybody have any other suggestions to this? or a follow up?
It should be easy to fix. You do not seem to have the correct driver installed.
Sent from my Galaxy Nexus using xda premium
Understood, I think I definitely did a few things wrong here. But my problem requires some kind of steps to solve. I don't mean to sound lazy but I've been running around the forums for awhile and I'm in way over my head, I was hoping someone could just list a few steps, links, SOMETHING. I'm looking for solvency here.
grnmons said:
Understood, I think I definitely did a few things wrong here. But my problem requires some kind of steps to solve. I don't mean to sound lazy but I've been running around the forums for awhile and I'm in way over my head, I was hoping someone could just list a few steps, links, SOMETHING. I'm looking for solvency here.
Click to expand...
Click to collapse
reinstall the android sdk from here that will get your drivers in order so your computer can see your phone
then fastboot flash recovery
then manually flash su (attached)
ogdobber said:
reinstall the android sdk from here that will get your drivers in order so your computer can see your phone
then fastboot flash recovery
then manually flash su (attached)
Click to expand...
Click to collapse
Thanks muchly, I feel like I'm getting closer but could you elaborate on the manual flash su step? My **** is all over the place now, my desktop is littered with files, should I be in recovery for this or still fastboot? and what is the command if you have?
grnmons said:
Thanks muchly, I feel like I'm getting closer but could you elaborate on the manual flash su step? My **** is all over the place now, my desktop is littered with files, should I be in recovery for this or still fastboot? and what is the command if you have?
Click to expand...
Click to collapse
download the gnex-su.zip and put in in the root of your sd card. then in recovery select "-install zip from sdcard" then "-choose zip from sdcard" then select the gnex-su.zip. this will give you root and install the superuser app
not to get ahead (previous post), but after your computer recognizes the phone you need to flash clockwork recovery
you need to open a terminal in the platform-tools folder of the sdk (also put the recovery.img there) and then
Code:
fastboot flash recovery name-of-recovery.img
Thanks for your help ogdobber, I'm incredibly frustrated and you must be too trying to help me, but I must have done something wrong as after I flash recovery, i still cannot access it - it continues to hang out in the Google screen.
Let me go through my steps with you and you tell me what I might have done wrong. So with my bricked phone, 1. I clicked your link and updated my SDK.
There's no indication that I did anything right here, it just shows that everything is installed and that's all I think I need here.
2. Opened up terminal fastboot flash boot (in this case) bootloader-toro-primekk15.img DONE!
3. Fastboot flash recovery (in this case) recovery-clockwork-5.0.2.0-crespo.img
DONE!
Then... nothing. Recovery doesn't load for me. Just get a boot loop. Anything I might have done wrong prior or inbetween these steps? Also, besides flashing and running commands off terminal - i assume this is considered computer recognizes my phone. Could the problem be there?
Just got your last post, I'm unfamiliar with SDK but I've since put the recovery file in there, not sure how to flash recovery. I have tried flashing recovery through terminal and surprisingly it says "-bash: fastboot: command not found"
grnmons said:
Thanks for your help ogdobber, I'm incredibly frustrated and you must be too trying to help me, but I must have done something wrong as after I flash recovery, i still cannot access it - it continues to hang out in the Google screen.
Let me go through my steps with you and you tell me what I might have done wrong. So with my bricked phone, 1. I clicked your link and updated my SDK.
There's no indication that I did anything right here, it just shows that everything is installed and that's all I think I need here.
2. Opened up terminal fastboot flash boot (in this case) bootloader-toro-primekk15.img DONE!
3. Fastboot flash recovery (in this case) recovery-clockwork-5.0.2.0-crespo.img
DONE!
Then... nothing. Recovery doesn't load for me. Just get a boot loop. Anything I might have done wrong prior or inbetween these steps? Also, besides flashing and running commands off terminal - i assume this is considered computer recognizes my phone. Could the problem be there?
Click to expand...
Click to collapse
that is for the nexus s
check your pm
ogdobber said:
that is for the nexus s
check your pm
Click to expand...
Click to collapse
If you are still having problems ...like I said before ...use Odin......since the simple process of fastboot is not working properly for you.Odin makes things so Much easier
Sent from my Galaxy Nexus using xda premium
Hi everyone, i have medium to advanced experience with flashing tools, android drivers, adb, fastboot, recovery mode and so on.
This evening once i installed the OTA Update for my Galaxy Nexus (which was running Android 4.2) the process failed at the end (as usual -.-) and i got stuck at bootloader.
I've wiped it completely ending up with no OS installed on it, nothing on SDCARD (Internal storage in this case).
The problem is that, i have no drivers installed on my PC for this phone.
I've already downloaded the latest version of Android 4.2 to flash (.zip), but there's no way i can transfer the file to the phone without the drivers.
I already tried GNex toolkit but it's stuck on "waiting adb device" (i have no fastboot drivers installed and can't install them because i can't find a easy way to do so).
NexusRootToolkit fails on pushing the zip to the phone and flash also won't work.
Any idea of what can i do now?
I may even pay on paypal for a quick help to get my phone back on working
Get into the bootloader and use fastboot, or if you have a custom recovery installed (sounds like you don't) then you can adb push from there. ADB doesn't exist in the bootloader, only fastboot. Those are your options.
ttabbal said:
Get into the bootloader and use fastboot, or if you have a custom recovery installed (sounds like you don't) then you can adb push from there. ADB doesn't exist in the bootloader, only fastboot. Those are your options.
Click to expand...
Click to collapse
Actually i do have a custom recovery which is CMW, but i can't seem to get my internal storage mounted using i'ts options.
I will try to push the .zip using the ADB on the recovery mode.
After checking the logs i can now see :
Enable to mount /usb-otg
(Using NexusRootToolkit i just flashed TWRP as recovery mode)
Solved : adb push <romname.zip> /sdcard/<romname.zip>
After the push was completed, i flashed the new .zip using TWRP in recovery mode.
Has anyone found a solution to this? Same thing has happened to me and I'm freaking out.
NPasta said:
Has anyone found a solution to this? Same thing has happened to me and I'm freaking out.
Click to expand...
Click to collapse
You mean besides the post right above yours?
Solved : adb push <romname.zip> /sdcard/<romname.zip>
After the push was completed, i flashed the new .zip using TWRP in recovery mode.
Click to expand...
Click to collapse
Save the pain, just flash the stock ROM from fastboot already....
Mach3.2 said:
Save the pain, just flash the stock ROM from fastboot already....
Click to expand...
Click to collapse
This. I don't see what the problem is here.
marcelloLins said:
i have medium to advanced experience with flashing tools, android drivers, adb, fastboot, recovery mode and so on.
I already tried GNex toolkit but it's stuck on "waiting adb device" (i have no fastboot drivers installed and can't install them because i can't find a easy way to do so).
NexusRootToolkit fails on pushing the zip to the phone and flash also won't work.
Click to expand...
Click to collapse
If you have the experience you say you have why do you use a Toolkit? Just learning for myself.
Look for efrant posts, they are the best and most comprehensive even for medium-advanced experience.
With him you will learn everything you need to know, including getting out of trouble and out of.............toolkit.
Just in case (you never know in life) do you have android-sdk installed on your pc?
Good luck in your learning curve ( I am still and will always be in it)
help-a-noob
Having similar problem: no OS installed. Got bootloader and TWRP. adb push doesn't work: computer can't find device. how do I get to fastboot? HALP!
HALP...
That's classic..
Read this:
http://forum.xda-developers.com/showthread.php?t=1812959
Then follow this:
http://forum.xda-developers.com/showthread.php?t=1626895
gunner1937 said:
If you have the experience you say you have why do you use a Toolkit? Just learning for myself.
Look for efrant posts, they are the best and most comprehensive even for medium-advanced experience.
With him you will learn everything you need to know, including getting out of trouble and out of.............toolkit.
Just in case (you never know in life) do you have android-sdk installed on your pc?
Good luck in your learning curve ( I am still and will always be in it)
Click to expand...
Click to collapse
Yep, i do have it installed, mainly because i'm a developer myself ; )
I've solved it already, as i've said, pushing the rom using ADB.
The upgrade to 4.2.1 probably failed because i've had the phone rooted.
Thanks for all the support and links by the way
marcelloLins said:
The upgrade to 4.2.1 probably failed because i've had the phone rooted.
Click to expand...
Click to collapse
You are mistaken, root doesn't stop a system update. I can vouch for that myself, even though i know that it doesnt matter just from reading some people's posts around here.
You weren't exactly explicit on your first post, so I presume you didnt/dont have the correct baseband version for that specific OTA to apply. Very common.
Oh and if you've never been able to OTA update successfully, it's not "usual" for the rest of us. You should work towards becoming more verbose and objective when troubleshooting. That will make you more experienced.
Sent from my i9250
marcelloLins said:
Yep, i do have it installed, mainly because i'm a developer myself ; )
I've solved it already, as i've said, pushing the rom using ADB.
The upgrade to 4.2.1 probably failed because i've had the phone rooted.
Thanks for all the support and links by the way
Click to expand...
Click to collapse
Hey, I have this exact problem. My os is gone and all i have is my cwm.
I am also having trouble installing adb, my comp doesn't recognize my nexus.
Please help, thanks!
dicksonjoe said:
Hey, I have this exact problem. My os is gone and all i have is my cwm.
I am also having trouble installing adb, my comp doesn't recognize my nexus.
Please help, thanks!
Click to expand...
Click to collapse
Try installing the ADB Drivers manually in order for your PC to recognize it.
Have you tried putting it other modes such as Download Mode and check if your pc installs any driver?
You will have to ADB PUSH the OS image to your internal memory and use CW to flash the rom from the sdcard, but you will need the drivers installed or adb wont be able to see your phone
i have the same problem you had...
i read some stuff and installed adb, sdk and whatever...
im trying the " adb push" command, but i think im doing something wrong.
the rom is on c:\users\edgar\downloads
rom name is abc.zip (i renamed)
what is the correct command format i must type??
thanks guys...
edgarzin said:
i have the same problem you had...
i read some stuff and installed adb, sdk and whatever...
im trying the " adb push" command, but i think im doing something wrong.
the rom is on c:\users\edgar\downloads
rom name is abc.zip (i renamed)
what is the correct command format i must type??
thanks guys...
Click to expand...
Click to collapse
Use "adb sideload c:\users\edgar\downloads\abc.zip". "adb push" is for transferring files from PC to phone, not flashing.
AndyYan said:
Use "adb sideload c:\users\edgar\downloads\abc.zip". "adb push" is for transferring files from PC to phone, not flashing.
Click to expand...
Click to collapse
thanks, but isnt it what am i supposed to do? transfer the zip file to sdcard and then flash using twrp?
for example usb mount via twrp dont work for me
edgarzin said:
thanks, but isnt it what am i supposed to do? transfer the zip file to sdcard and then flash using twrp?
Click to expand...
Click to collapse
adb sideload does both transferring and flashing within a single command. The "sideloaded" ZIP gets saved as "sideload.zip" under the root of the storage.
Sent from Samsung Galaxy Nexus @ CM11
AndyYan said:
adb sideload does both transferring and flashing within a single command. The "sideloaded" ZIP gets saved as "sideload.zip" under the root of the storage.
Sent from Samsung Galaxy Nexus @ CM11
Click to expand...
Click to collapse
Thanks!! Now its working! in twrp, advanced mode, adb sideload, then i executed the command you told me!!! saved my phone
Hey there,
i have a Nexus 7 (2013) with android 4.4.2 (KOT49H). I unlocked the bootloader with wugfresh´s toolkit - so far no problems. Then i tried to root... The toolkit installed TWRP and launched into recovery to install the needed root files, but the device remained there...and nothing happened. On the PC the process froze showing the message "waiting for device". I rebooted the device manually from recovery. After the reboot i had no root access.
Because of these problems i decided to use the "Flash Stock + Unroot" option in the toolkit. First i completely reinstalled all related drivers with the full driver intallation guide and i got the "Success" message after testing. I enabled usb-debugging and went through the restore process. Then i got the message "FAILED (data transfer failure (Too many links))". My device remained in bootloader mode. At least it is possible to boot into bootloader mode every time. But when i try to start the device normal it freezes on the google logo, because the rom is partially wiped.
What can i do to get my device to stock firmware without to exacerbate the situation? Should i enable "Force Flash Mode"?
Please help me, thank you very much!
I attached the log below...
Ditch the toolkit. Download the Google revert to stock package, unzip it, connect your device in fastboot and run the flash all batch file
Sent from my Nexus 7 using Tapatalk
---------- Post added at 03:36 PM ---------- Previous post was at 03:32 PM ----------
Refer to this guide http://www.androidpolice.com/2013/0...stock-using-a-full-factory-image-and-root-it/
Sent from my Nexus 7 using Tapatalk
SwoRNLeaDejZ said:
Ditch the toolkit. Download the Google revert to stock package, unzip it, connect your device in fastboot and run the flash all batch file
Sent from my Nexus 7 using Tapatalk
---------- Post added at 03:36 PM ---------- Previous post was at 03:32 PM ----------
Refer to this guide http://www.androidpolice.com/2013/0...stock-using-a-full-factory-image-and-root-it/
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Thanks! I will try this method. Is it necessary to install some further specific fastboot drivers or are the ones installed by the toolkit sufficient? USB-Debugging was checked before in developer options but the android os is partially wiped. So will this be a problem? Is there a possibility to control if the device is recocnized correctly before i run the batch file. I think i don´t have to remove the "-w" from the fastboot update command because everything has to be wiped.
Just follow the tutorial, you should be good to go. And the adb and fastboot drivers are the same.
Sent from my LG-MS770 using Tapatalk
SwoRNLeaDejZ said:
Just follow the tutorial, you should be good to go. And the adb and fastboot drivers are the same.
Sent from my LG-MS770 using Tapatalk
Click to expand...
Click to collapse
Ok i started the batchfile but it said that the fastboot command couldn´t be found. Then i copied the 5 files of the unpacked factory image into the sdk -> platform tools directory. Am i right? Now when i run the flash-all file it says "waiting for device" I do this for the first time so i´m a little bit uncertain. Is all i have to do now to connect my nexus in fastboot mode? Thank you very much again!
Here are some screenshots...
Have you looked in Device Manager from Windows if the hardwaredriver of device is correctly installed. While in recovery and usb-connected type 'adb devices' in Command Window to see if there is connnection before flashing.
I had the same problem in Windows 8 first time flashing. Only way to get driver and device in recovery mode working in my case: In Device manager I clicked 'update driver' of 'unknown device', browsed to unpacked driver Folder and let Windows install correctly.
Verstuurd vanaf mijn Nexus 7 met Tapatalk
juliatan said:
Have you looked in Device Manager from Windows if the hardwaredriver of device is correctly installed. While in recovery and usb-connected type 'adb devices' in Command Window to see if there is connnection before flashing.
I had the same problem in Windows 8 first time flashing. Only way to get driver and device in recovery mode working in my case: In Device manager I clicked 'update driver' of 'unknown device', browsed to unpacked driver Folder and let Windows install correctly.
Verstuurd vanaf mijn Nexus 7 met Tapatalk
Click to expand...
Click to collapse
In the driver manager there is an android device connected "Google Nexus BootLoader Interface" but when i run the command "adb devices" i don´t get an device listed although i am connected in bootloader mode. Recovery isn´t working anymore (shows android with triangle), because of the bad factory reset with the toolkit. So what can i do to get my device recognized? Actually the needed drivers should be okay, because the universal drivers were installed via the toolkit and i was able to unlock the bootloader etc. What i´m doing wrong?
Thank you for help.
I appologize, but this is out of ny league. I would first try that toolkit-thread. I am sure there will be a repair thread too. Good luck.
Verstuurd vanaf mijn Nexus 7 met Tapatalk
Blizzard300 said:
In the driver manager there is an android device connected "Google Nexus BootLoader Interface" but when i run the command "adb devices" i don´t get an device listed although i am connected in bootloader mode. Recovery isn´t working anymore (shows android with triangle), because of the bad factory reset with the toolkit. So what can i do to get my device recognized? Actually the needed drivers should be okay, because the universal drivers were installed via the toolkit and i was able to unlock the bootloader etc. What i´m doing wrong?
Thank you for help.
Click to expand...
Click to collapse
When you are connected to the computer in the bootloader (on the N7), what does it say when you type "fastboot devices"? (without the quotation marks)
juliatan said:
I appologize, but this is out of ny league. I would first try that toolkit-thread. I am sure there will be a repair thread too. Good luck.
Verstuurd vanaf mijn Nexus 7 met Tapatalk
Click to expand...
Click to collapse
Thanks, i will do that. After reading some indications in the toolkit thread i found out that i am able to access stock recovery
charesa39 said:
When you are connected to the computer in the bootloader (on the N7), what does it say when you type "fastboot devices"? (without the quotation marks)
Click to expand...
Click to collapse
Thanks, i think you found the solution When i use the command "fastboot devices" i get this: 08f34cbd
Does it mean everything is correctly installed and i´m ready to flash the factory image? I am also asking me if it was right to extract all the files of the razor-kot49h factory image into the platform tools directory of sdk, but otherwise when i just executed the flash-all file somewhere on the computer there were failure messages, so i assume it should be right this way. Thank you!
Blizzard300 said:
Thanks, i think you found the solution When i use the command "fastboot devices" i get this: 08f34cbd
Does it mean everything is correctly installed and i´m ready to flash the factory image? I am also asking me if it was right to extract all the files of the razor-kot49h factory image into the platform tools directory of sdk, but otherwise when i just executed the flash-all file somewhere on the computer there were failure messages, so i assume it should be right this way. Thank you!
Click to expand...
Click to collapse
Yes it does! Nothing was coming up when you typed "adb devices" because that's only when you're in the OS after it completely boots into it's ROM. Fastboot is for when it's in the bootloader menu. And yes, you are correct regarding the factory image zip. Extract everything out of the zip (I can't remember if there's a zip inside that zip, but I think there is). Make sure you unzip that as well if there is. Then, place all the image files into that platform-tools folder. So you should have image files for Bootloader, System, Userdata, Boot, Recovery and Cache. I don't think the cache is necessary, but I suppose it wouldn't hurt to flash it as well.
I followed these steps when restoring the factory image on my N7: http://forum.xda-developers.com/showthread.php?t=2513701
I used Method 2 from the OP. Obviously, those instructions are for the Nexus 5, but it'll work. Just skip over the part where it says "flashboot flash radio". So fastboot flash the bootloader, reboot bootloader, fastboot system, fastboot userdata, fastboot boot, fastboot recovery, fastboot erase cache (or fastboot cache if you want to flash the cache image from the factory image zip). Then, manually select "Recovery Mode" on the phone using the volume buttons on the N7. It'll show that Android on it's back with the red exclamation mark. Hit Power + Vol Up at the same time and it'll show the stock recovery menu. Select "Wipe data/Factory data reset" and reboot. You should be good to go.
Unzip the tar.gz and then double click flash all, no need to unzip anything inside the tar.gz. and yes, adb commands only work from inside the os, you need to use fastboot commands when in the bootloader. I would suggest reading up on it, very useful information.
Sent from my LG-MS770 using Tapatalk
Yeah, all went perfectly well! After the factory image was restored i flashed twrp with fastboot, installed super su over sideload and then busy box from the playstore. I immediately did a full backup in the recovery At this point i want to say thank you to all who helped me! You are awesome!
First i was afraid that my nexus couldn´t be repairable anymore. So i´m really happy now that everything worked.
Blizzard300 said:
Yeah, all went perfectly well! After the factory image was restored i flashed twrp with fastboot, installed super su over sideload and then busy box from the playstore. I immediately did a full backup in the recovery At this point i want to say thank you to all who helped me! You are awesome!
First i was afraid that my nexus couldn´t be repairable anymore. So i´m really happy now that everything worked.
Click to expand...
Click to collapse
Glad it all worked out for you. :thumbup:
Sent from my Nexus 5 using xda app-developers app
Earlier today I used the Nexus Root Tool Kit to flash stock and flash the factory image for 5.0.
At erasing User Data it seemed to get stuck, it was there for over 40 minutes. While looking at the device I accidentally knocked the USB cable out and it said failed. Upon rebooting the device I got the Google logo and the bootloader unlocked icon and then the bugdroid with the gear like it's doing an update (THIS: http://scottiestech.info/wp-content/uploads/2013/03/Android_Update_Screen.jpg[1] ). It stayed like this for another 40 minutes. I forced it to shut down and tried to get into the bootloader but holding down vol up+vol down+power for almost 60 seconds did nothing.
I then booted it up normally again to the gear bugdroid and left it like that before I went out for almost 6 hours. When coming home it was the same and still stuck on that.
I rebooted again and held down to boot into the bootloader but again it did not boot in over 60 seconds.
So am I hard bricked and should toss this out with the trash tonight or can this be restored somehow.
Are you able to connect to your device using fastboot?
Assuming you have fastboot installed and the drivers installed, open a command prompt and from the directory where your SDK files are (unless you added the directory to your system PATH), type "fastboot devices" without the quotes. What do you get back? If you get back a serial#, you should be able to flash the individual files manually
(Download the factory image from google's site, and extract the files into a folder, and run the flash-all.bat This will wipe all your data out, and assumes your bootloader is already unlocked)
Edit: follow the instructions here - http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
These are for Nexus 5, but the same steps apply for Nexus 7 as well. Just make sure you download the right factory image for your Nexus 7. Use Method 1
jj14 said:
Are you able to connect to your device using fastboot?
Assuming you have fastboot installed and the drivers installed, open a command prompt and from the directory where your SDK files are (unless you added the directory to your system PATH), type "fastboot devices" without the quotes. What do you get back? If you get back a serial#, you should be able to flash the individual files manually
(Download the factory image from google's site, and extract the files into a folder, and run the flash-all.bat This will wipe all your data out, and assumes your bootloader is already unlocked)
Edit: follow the instructions here - http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
These are for Nexus 5, but the same steps apply for Nexus 7 as well. Just make sure you download the right factory image for your Nexus 7. Use Method 1
Click to expand...
Click to collapse
Well I can get it into fastboot but I'm getting errors when it tries to flash the bootloader or boot.
what's the error message?
jj14 said:
what's the error message?
Click to expand...
Click to collapse
originally there was none, it just said failed and completed. now i'm getting invalid arguments.
I'm still in fastboot mode but literally nothing will flash.
*edit* just tried to use tookit again and
writing 'bootloader'
FAILED <remote: flash write failure>
finished.
Seeing a couple people mention that they fixed errors like this just from using a different usb port or cable. going to try that.
Why didn't you use adb to flash factory image from the get-go? It's the safest way to flash. I would be so mad on your place if device would render useless. But that might be just me since i'm poor. I really hope you manage to fix it.
neo5468 said:
Why didn't you use adb to flash factory image from the get-go? It's the safest way to flash. I would be so mad on your place if device would render useless. But that might be just me since i'm poor. I really hope you manage to fix it.
Click to expand...
Click to collapse
I knew of that way but the Nexus Tool Kit has always been perfect and I've never had any issues with it so I figured I'd just do it that way to make it easier and well, it didn't happen.
I'm hoping because I can get into fastboot that it's not actually bricked yet but if so then oh well i guess.
I have a stock Pixel 2xl running android 10. Can't root it, no matter what i try. Any help would be greatly appreciated. Thanks
grunt0300 said:
I have a stock Pixel 2xl running android 10. Can't root it, no matter what i try. Any help would be greatly appreciated. Thanks
Click to expand...
Click to collapse
Is your bootloader unlocked?
Badger50 said:
Is your bootloader unlocked?
Click to expand...
Click to collapse
Yes it is.
grunt0300 said:
Yes it is.
Click to expand...
Click to collapse
Ok. So you've installed the latest platform-tools on your pc?
Downloaded the factory image that coincides with your current build?
Extracted the factory image, then extracted the image.zip, and moved the boot.img to your phones internal storage?
Magisk manager is installed on your phone. Then you patched the boot.img, and then moved it to your pc platform-tools?
Put your phone into bootloader mode, opened a command prompt on you platform-tools folder, typed in "fastboot devices" to make sure your pc recognizes your phone?
Then fastbooted your patched boot.img to both slots with...
fastboot flash boot magisk_patched.img --slot=all
And then booted up with root?
What happens when you run the fastboot command "fastboot flashing unlock"?
Badger50 said:
Ok. So you've installed the latest platform-tools on your pc?
Downloaded the factory image that coincides with your current build?
Extracted the factory image, then extracted the image.zip, and moved the boot.img to your phones internal storage?
Magisk manager is installed on your phone. Then you patched the boot.img, and then moved it to your pc platform-tools?
Put your phone into bootloader mode, opened a command prompt on you platform-tools folder, typed in "fastboot devices" to make sure your pc recognizes your phone?
Then fastbooted your patched boot.img to both slots with...
fastboot flash boot magisk_patched.img --slot=all
And then booted up with root?
Click to expand...
Click to collapse
Sorry, i've been trying to root this phone all afternoon and i'm burnt out. Maybe tomorrow. Thanks
OK, i tried to root it again, and this is what i got....Your device is corrupt. It can't be trusted and may not work properly. The phone is not recognized by my pc. I can get into "bootloader mode", but can't do a thing with it. I could sure use some help. In the meantime, i'll pop the sim card into my trusty nexus 6, and wait to hear from one of you nice people. Thanks.
grunt0300 said:
OK, i tried to root it again, and this is what i got....Your device is corrupt. It can't be trusted and may not work properly. The phone is not recognized by my pc. I can get into "bootloader mode", but can't do a thing with it. I could sure use some help. In the meantime, i'll pop the sim card into my trusty nexus 6, and wait to hear from one of you nice people. Thanks.
Click to expand...
Click to collapse
Go to the guide in my signature, follow the step by step instructions there.
Make sure you have done the following:
-SDK tools are up to date,
-the proper platform folders are unzipped (there are two),
-you have a couple different USB cables handy.
Az Biker said:
Go to the guide in my signature, follow the step by step instructions there.
Make sure you have done the following:
-SDK tools are up to date,
-the proper platform folders are unzipped (there are two),
-you have a couple different USB cables handy.
Click to expand...
Click to collapse
I just put the sim card back into the pixel 2xl, and it booted up as if it was brand new. Plugged it into pc, got into bootloader mode, typed in command "adb devices", and it recognized the phone. I have all those files downloaded onto my desktop, so what's my next move?
grunt0300 said:
I just put the sim card back into the pixel 2xl, and it booted up as if it was brand new. Plugged it into pc, got into bootloader mode, typed in command "adb devices", and it recognized the phone. I have all those files downloaded onto my desktop, so what's my next move?
Click to expand...
Click to collapse
Like @Az Biker said, follow the guide in his signature :good:
Badger50 said:
Like @Az Biker said, follow the guide in his signature :good:
Click to expand...
Click to collapse
Doesn't work. I can't "fastboot" into anything. When i try, the pc stops recognizing the phone.
grunt0300 said:
Doesn't work. I can't "fastboot" into anything. When i try, the pc stops recognizing the phone.
Click to expand...
Click to collapse
Did you try a different usb cable? And you activated "developer options" and turned on usb debugging?
Also, try typing CMD in the url line from within the same platform tool folder where the platform tools application is located.
Az Biker said:
Did you try a different usb cable? And you activated "developer options" and turned on usb debugging?
Also, try typing CMD in the url line from within the same platform tool folder where the platform tools application is located.
Click to expand...
Click to collapse
OK, after waiting an hour, i tried typing into that command line that popped up within the platform tools folder. I tried adb devices, and my phone was recognized. Now, my phone is not in fastboot mode, and i don't have the sim card in it. What's my next move, please.
grunt0300 said:
OK, after waiting an hour, i tried typing into that command line that popped up within the platform tools folder. I tried adb devices, and my phone was recognized. Now, my phone is not in fastboot mode, and i don't have the sim card in it. What's my next move, please.
Click to expand...
Click to collapse
Have you patched the boot.img with magisk yet? If you look a few posts ago, I gave you exact instructions on how to patch and flash the modified boot.img
Also, adb devices is a command while your in your OS. You need to power off the phone, then enter bootloader mode manually by holding the power + volume down button until you enter the bootloader screen.
Then plug your phone in, open the command prompt on your platform-tools folder, and type in "fastboot devices". If you see your phone's ID number, then you have a good interface. Then you can fastboot the patched boot.img :good:
https://forum.xda-developers.com/pixel-2-xl/help/rooting-pixel-2xl-t4033453/post81455679
Badger50 said:
Have you patched the boot.img with magisk yet? If you look a few posts ago, I gave you exact instructions on how to patch and flash the modified boot.img
Also, adb devices is a command while your in your OS. You need to power off the phone, then enter bootloader mode manually by holding the power + volume down button until you enter the bootloader screen.
Then plug your phone in, open the command prompt on your platform-tools folder, and type in "fastboot devices". If you see your phone's ID number, then you have a good interface. Then you can fastboot the patched boot.img :good:
https://forum.xda-developers.com/pixel-2-xl/help/rooting-pixel-2xl-t4033453/post81455679
Click to expand...
Click to collapse
Can't get into "recovery mode". I have all the files in the file mgr on the phone. Do i have to put the sim card back into the phone in order for this to work?
grunt0300 said:
Can't get into "recovery mode". I have all the files in the file mgr on the phone. Do i have to put the sim card back into the phone in order for this to work?
Click to expand...
Click to collapse
Recovery mode? You need to be in bootloader mode. What files exactly do you have on your phone that your talking about? Just curious, but have you read through any of the directions that myself and @Az Biker have given you? Things seem to be getting lost in translation.
Badger50 said:
Recovery mode? You need to be in bootloader mode. What files exactly do you have on your phone that your talking about? Just curious, but have you read through any of the directions that myself and @Az Biker have given you? Things seem to be getting lost in translation.
Click to expand...
Click to collapse
Right now, i'm so confused that i don't know what day it is. I've got files all over my desktop. If i can get this phone up and running, i'll sell it and use the money towards a Note 9(USA version). I still have my rooted Nexus 6, and i NEVER had this trouble rooting it. Anyway, i'm done with this for now. If you want, i'll send you the Pixel 2xl, and when you get it working send it back to me, and we'll figure out the compensation. Thanks for trying.
grunt0300 said:
Right now, i'm so confused that i don't know what day it is. I've got files all over my desktop. If i can get this phone up and running, i'll sell it and use the money towards a Note 9(USA version). I still have my rooted Nexus 6, and i NEVER had this trouble rooting it. Anyway, i'm done with this for now. If you want, i'll send you the Pixel 2xl, and when you get it working send it back to me, and we'll figure out the compensation. Thanks for trying.
Click to expand...
Click to collapse
Please follow the step by step guide in my sig.
It explains EVERYTHING from step one all the way through the final reboot.
If your SDK tools are up to date (link provided), and your have multiple USB cables (trust me it's a known, unexplained issue) and you've unzipped the platform tools folder AND unzipped the second platform tool folder (this is the one where you type CMD in the url line) and then follow each step as written, you should have NO problem at all.
If you skip steps or go ahead using your own or another process there's no guarantee, but if you follow the steps in the guide, you should have no problems at all. This guide has been followed by myself and many others with ZERO issues, so I know the written process works.
Az Biker said:
Please follow the step by step guide in my sig.
It explains EVERYTHING from step one all the way through the final reboot.
If your SDK tools are up to date (link provided), and your have multiple USB cables (trust me it's a known, unexplained issue) and you've unzipped the platform tools folder AND unzipped the second platform tool folder (this is the one where you type CMD in the url line) and then follow each step as written, you should have NO problem at all.
If you skip steps or go ahead using your own or another process there's no guarantee, but if you follow the steps in the guide, you should have no problems at all. This guide has been followed by myself and many others with ZERO issues, so I know the written process works.
Click to expand...
Click to collapse
Did i mention that i already have android 10 on the phone?
grunt0300 said:
Did i mention that i already have android 10 on the phone?
Click to expand...
Click to collapse
The guide process works the same for 9x and Android 10.
In the guide, it is stated:
NOTE: On Android 10, when flashing TWRP Installer, kernels, magisk , etc. in TWRP, ignore the warning "FAILED TO MOUNT '/system' (invalid argument) this is a known issue with TWRP + 10 but affects nothing
Once you verify 'fastboot devices' on command prompt
Type flash-all to install factory image (allow it to install, and boot into system)
Hold vol down and power button to boot into bootloader
Fastboot into twrp 3.3.0-0.IMG
Flash the twrp installer 3.3.0-0.ZIP,
Flash Cust Kernel (I use Flash -not supported after 3.19 Nov 2018 or Sultan Kernel or Elemental X (EX) kernel) BE SURE TO SELECT THE CORRECT 9X OR ANDROID 10 KERNEL
Let the system boot up to verify.
Reboot back into twrp and flash latest magisk
Reboot to system
Profit
I guess I'm confused as to why you are simply not just following the guide from step one.........