Database Users

[Q] Stuck in Bootloader

Hi all,
my nexus wont start after (failed?!) flashing with factory image. bootloader and recovery mode are accessable. i have no backup so i need to flash a new img, but my tablet wont be recognized by my computer anymore(adb drivers not working?!). i tried to deinstall and reinstall the adb drivers alrdy. Device manager shows nexus 7 as Android Phone with "Android Bootloader interface" i cant install adb drivers while in bootloader. in recovery mode i succeeded installing the adb drivers and the tablet is shown correctly in device manager... i need help dont know what to do :crying: .. any suggestions ?

ADB and fastboot drivers are different.

Pirateghost said:
ADB and fastboot drivers are different.
Click to expand...
Click to collapse
yes .. what are u trying to tell me? dont get it.. i used nexus root toolkit to help me apply those drivers.. but it wont work for bootloader/fastboot mode.. i cant flash my tablet because my device wont be recognized by my pc.. im stuck at the bootloaderscreen/fastbootmode....

http://bit.ly/Zqk7pm

and what do u want me to type in there ? i alrdy used google for the last 7 hours ?

oads said:
and what do u want me to type in there ? i alrdy used google for the last 7 hours ?
Click to expand...
Click to collapse
SMH
i filled it in for you.....

Pirateghost said:
SMH
i filled it in for you.....
Click to expand...
Click to collapse
ok sry wasnt patient enough to see... ya well this all makes sense to someone who knows what hes doing but to a noob like me? i thought i alrdy installed fastboot drivers since i unrooted the device a month ago? do i need to deinstall the driver "Android Phone with "Android Bootloader interface"" in device manager first, before applying the new fastboot drivers? pls help me through this i think i damaged enough alrdy ..

no. ADB and fastboot require separate drivers. just install the drivers required for n7 fastboot. there was a link in that list.
there are tutorials here on xda, as well as youtube videos and tutorials on other sites. take a little initiative and learn the ropes. it will help you out later on.

oads said:
ok sry wasnt patient enough to see... ya well this all makes sense to someone who knows what hes doing but to a noob like me? i thought i alrdy installed fastboot drivers since i unrooted the device a month ago? do i need to deinstall the driver "Android Phone with "Android Bootloader interface"" in device manager first, before applying the new fastboot drivers? pls help me through this i think i damaged enough alrdy ..
Click to expand...
Click to collapse
Just relax and take your time.
If your tablet can go into fastboot mode, it is fine and will get better; the only thing standing between it's current state and being brought back to life is a little learning on your part.
Now you see what the problems are with using a toolkit - because they hide all the gory details from you, when the smallest thing goes wrong you are totally helpless due to a lack of understanding about what things are going on underneath the hood. And as it turns out, what "goes on under the hood" isn't really all that complicated either if you do things the full manual way.
Which is not to say that you can not simply just use the toolkit again; if you previously successfully installed drivers that allowed you to talk to the tablet in all of these modes:
- fastboot
- adb w/ custom recovery booted
- adb with Android booted
then it is not evident that you need to be fooling with drivers.
I suggest you read this thread, from start to finish
[GUIDE] Flashing a Factory Image with fastboot / return to stock
Then, go over to your toolkit thread and read it from start to finish. You will see that there are & have been plenty of people in circumstances nearly identical to yours.
good luck

hey thx for ur replies! im a lil more calm now than i was 30 min !
the big problem i still have is that my tablet will show up as Androidphone/Android Bootloader Interface not as an unknown device or as the Nexus 7 it is when i plug it in.. so i cant install the drivers am i correct? well i tried it a few times .. deinstalled and reinstalled .. the problem persists? anyone familiar with that? when i change into Recovery Modus it will show up as Androidphone/Google Nexus ADB Interface.. so my first steps to get rid of this mess would be ...?

oads said:
hey thx for ur replies! im a lil more calm now than i was 30 min !
the big problem i still have is that my tablet will show up as Androidphone/Android Bootloader Interface not as an unknown device or as the Nexus 7 it is when i plug it in.. so i cant install the drivers am i correct? well i tried it a few times .. deinstalled and reinstalled .. the problem persists? anyone familiar with that? when i change into Recovery Modus it will show up as Androidphone/Google Nexus ADB Interface.. so my first steps to get rid of this mess would be ...?
Click to expand...
Click to collapse
that does not sound like a problem to me at all.
You communicate with the device using the "fastboot" program when it is in bootloader/fastboot mode, and with the "adb" program when it is in custom recovery boot.
What you see in the device manager appears to be completely normal - In different modes it shows up in different places. It's not supposed to show up with the same driver in different modes.
Code:
fastboot devices
will show you whether you are communicating successfully with the device when it is in bootloader/fastboot mode, and
Code:
adb devices
will show you whether you are communicating successfully with the device in recovery mode.
I suppose your toolkit has some stoopid menu or buttons someplace that will allow you to test for exactly the same thing. Now all you need to do is stop posting here and read a little bit.
good luck

bftb0 said:
Now all you need to do is stop posting here and read a little bit.
good luck
Click to expand...
Click to collapse
well i did read quite a lot today :crying: i cant find my device when i type in adb devices, im pretty sure i have the right drivers installed since i followed the instructions step by step.
this guy seems to have the same problem: http://forum.xda-developers.com/showthread.php?t=1808076
could someone tell me if this could be a possible solution :http://stackoverflow.com/questions/...e-over-usb-via-adb-devices-from-windows-7-x64
also would it be possible to just get into the bootloader (since thats the purpose of adb drivers and i can do this) and just proceed with fastboot commands ? if i type in fastboot devices the tablet will show up...

In your first post, you indicated that you couldn't connect to the tablet that was in bootloader mode with adb.
And then you were told - once vaguely and once quite specifically - that *nobody* can communicate with the tablet using adb when the tablet is in bootloader/fastboot mode.
As stated previously, use the "fastboot" program when the tablet is in bootloader mode, and use the "adb" program when the tablet is booted to the custom recovery (or the regular android boot if USB debugging has been enabled).
You can use either one of these modes to effect a rescue so long as they are working correctly - they don't need to both be working. Eventually you would want that to be the case, but for the moment why don't you just stick with what is working for you.
If you get a device ID printed when you execute "fastboot devices" when the tablet is in boot loader/fastboot mode, that is all you need to reinstall a factory ROM, using nothing but fastboot.

thx for pointing me in the right direction! so i started flashing with the fastboot commands... as soon i get to: fastboot flash radio radio-tilapia-1231_0.17.0_1025.img
i receive:
error: cannot load 'radio-tilapia-1231_0.17.0_1025.img': No error
any clues? thx in advance
edit:using 4.2.2 factory rom for nexus 7 3g

oads said:
thx for pointing me in the right direction! so i started flashing with the fastboot commands... as soon i get to: fastboot flash radio radio-tilapia-1231_0.17.0_1025.img
i receive:
error: cannot load 'radio-tilapia-1231_0.17.0_1025.img': No error
any clues? thx in advance
edit:using 4.2.2 factory rom for nexus 7 3g
Click to expand...
Click to collapse
Well, I can't see what instructions you are following, and there is a possibility of sensitivity to an exact sequence. In particular, is a
fastboot reboot-bootloader
performed after the bootloader is flashed, but before the radio is flashed? It might be important that you are performing the radio flash from one bootloader vs. the other. Just a guess. (Along the same lines, do you see something unexpected happening, such as a boot to the recovery after the radio flash command?)
There are some other threads on this I think. (I have a grouper device not tilapia) But I thought that those threads were about problems with radio flashing when a custom recovery (rather than a stock recovery) was on the phone, but that was for applying the OTA package for tilapia rather than flashing directly from fastboot.
-------------------------------------------------------
[Edit] whoops, wait a minute.... "cannot load"
When you run fastboot from the command line, the file names you give are relative to the current directory. Did you move those image files into the same directory that you are executing the "fastboot" command from?
Alternately you can specify the full pathname to wherever you unpacked the files, for instance
fastboot flash radio C:\myfolder\unpacked\googlen7\4.2.2\radio-tilapia-1231_0.17.0_1025.img

hi! basically im following this guide http://forum.xda-developers.com/showthread.php?t=1907796!
GSM/HSPA+ devices (nakasig)
Code:
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
> fastboot flash bootloader bootloader-tilapia-4.18.img
> fastboot reboot-bootloader
> fastboot flash radio radio-tilapia-1231_0.17.0_1025.img
> fastboot reboot-bootloader
> fastboot -w update image-nakasig-jdq39.zip
its all good till i want to flash the radio. The .img is in the correct folder, just tried it again... could it be broken? should i try a other factory update like 4.2.1?

oads said:
hi! basically im following this guide http://forum.xda-developers.com/showthread.php?t=1907796!
GSM/HSPA+ devices (nakasig)
Code:
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
> fastboot flash bootloader bootloader-tilapia-4.18.img
> fastboot reboot-bootloader
> fastboot flash radio radio-tilapia-1231_0.17.0_1025.img
> fastboot reboot-bootloader
> fastboot -w update image-nakasig-jdq39.zip
its all good till i want to flash the radio. The .img is in the correct folder, just tried it again... could it be broken? should i try a other factory update like 4.2.1?
Click to expand...
Click to collapse
I would complete the rest of the steps first and see if everything is still working. Your device *should* still work just fine with an old radio firmware. (Boot it up and see what radio firmware the OS reports on the Settings... about device... status page).
I'll pull down the tilapia image and tell you what MD5 I observe for the radio image.

just to verify, you actually have the 3g/4g model? or just the wifi only model. if wifi only, there is no radio

Pirateghost said:
just to verify, you actually have the 3g/4g model? or just the wifi only model. if wifi only, there is no radio
Click to expand...
Click to collapse
yes

SHA1
0798439d363beb145d9223a42ed9edf3de1a30f4 nakasig-jdq39-factory-0798439d.tgz
bb824d449f44d2ad43c5d2a463fe1244d2faf525 nakasig-jdq39/radio-tilapia-1231_0.17.0_1205.img
f406ae9133c56200306d5c7d64d151f21e0be3c4 nakasig-jdq39/image-nakasig-jdq39.zip
MD5
ee8db1ed6ff1c007fe12136d4bc65cd8 nakasig-jdq39-factory-0798439d.tgz
276cb738e5b9e18a088b6a3eef8155ad nakasig-jdq39/radio-tilapia-1231_0.17.0_1205.img
4cfa996b6513a7fa53db7cbfd1134396 nakasig-jdq39/image-nakasig-jdq39.zip
radio image is 16,777,216 bytes long
---------- Post added at 05:43 PM ---------- Previous post was at 05:40 PM ----------
the google - provided instructions (flash-all.sh) have 10 second sleeps after the bootloader resets - are you waiting long enough?
fastboot oem unlock
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-tilapia-4.18.img
fastboot reboot-bootloader
sleep 10
fastboot flash radio radio-tilapia-1231_0.17.0_1205.img
fastboot reboot-bootloader
sleep 10
Also - something to check since you are rebooting the bootloader - does the device show up correctly in the Windows device manager? (Sometimes with soft reboots I have found the need to pull the USB cable and plug it back in to the PC).

Updating to 4.3 Image with fastboot failed.

Hi guys
I was trying to update to 4.3 using fastboot and after finishing i got stuck with the google on the screen. So i went on to try it again, this time installing each .img in the zip manually. While i was sending the System.img the usb connection broke and i tried again to no avail. So i was like lets do this again. So i went i started all over again with erasing boot, now the terminal is stuck on that and not going forward. Im out of options. Really need help, im helpless here. Please.
Thank You

Cantacid said:
Hi guys
I was trying to update to 4.3 using fastboot and after finishing i got stuck with the google on the screen. So i went on to try it again, this time installing each .img in the zip manually. While i was sending the System.img the usb connection broke and i tried again to no avail. So i was like lets do this again. So i went i started all over again with erasing boot, now the terminal is stuck on that and not going forward. Im out of options. Really need help, im helpless here. Please.
Thank You
Click to expand...
Click to collapse
Is that a Mac? There is another thread with a guy having issues flashing system.img using a Mac. Not sure if he was able to fix it or not. He was able to flash all the other images just not system.img.
For reference from Efrant's thread on flashing image files if your phone hangs during first boot try this:
Note that some users indicate that they can't get past the X on boot. If this happens to you, reboot into the bootloader and select recovery. Then, when you see the Android with the red exclamation mark, hold power and press volume up to take you to the menu. Wipe cache. If that still doesn't work, boot back into recovery and do a factory reset.
http://forum.xda-developers.com/showthread.php?t=2010312
I had the boot issue when I first flashed the images and just formatting the cache fixed it for me. I later had to do a factory reset as the phone was reporting the wrong storage size, 8 GB instead of 16 GB and the reset fixed it.
Here is the other guys Mac thread, not sure it will help you or not.
http://forum.xda-developers.com/showthread.php?t=2377647

kzoodroid said:
Is that a Mac? There is another thread with a guy having issues flashing system.img using a Mac. Not sure if he was able to fix it or not. He was able to flash all the other images just not system.img.
For reference from Efrant's thread on flashing image files if your phone hangs during first boot try this:
Note that some users indicate that they can't get past the X on boot. If this happens to you, reboot into the bootloader and select recovery. Then, when you see the Android with the red exclamation mark, hold power and press volume up to take you to the menu. Wipe cache. If that still doesn't work, boot back into recovery and do a factory reset.
http://forum.xda-developers.com/showthread.php?t=2010312
I had the boot issue when I first flashed the images and just formatting the cache fixed it for me. I later had to do a factory reset as the phone was reporting the wrong storage size, 8 GB instead of 16 GB and the reset fixed it.
Here is the other guys Mac thread, not sure it will help you or not.
http://forum.xda-developers.com/showthread.php?t=2377647
Click to expand...
Click to collapse
And the thing about cleaning caches is locking and unlocking bootloader does the same. Tried, i cant install recovery and system .img for some reason.
Thank you for the quick reply, seems the like the guy is having the same issue. Will post it there as well.
The issue is to fastboot the system.img

Cantacid said:
And the thing about cleaning caches is locking and unlocking bootloader does the same. Tried, i cant install recovery and system .img for some reason.
Thank you for the quick reply, seems the like the guy is having the same issue. Will post it there as well.
The issue is to fastboot the system.img
Click to expand...
Click to collapse
I see you are in the other thread too but I will post this here also.
According to this thread when using a Mac you don't flash the system or kernel (boot) images.
http://forum.xda-developers.com/showthread.php?t=2377691

kzoodroid said:
I see you are in the other thread too but I will post this here also.
According to this thread when using a Mac you don't flash the system or kernel (boot) images.
http://forum.xda-developers.com/showthread.php?t=2377691
Click to expand...
Click to collapse
Yeah you do. I just did this on my Mac for my Nexus 4 and Nexus 7 last night with absolutely no issues.
The procedure I used is as follows...
1.1) Download the factory image and ensure all .img files are extracted to the "platform-tools" folder
1.2) Boot phone into fastboot mode by powering it down then holding volume down/power at the same time until the fastboot screen appears
2) Plug the phone into the computer via USB cable
3) Open terminal and type: fastboot devices (if it recognizes your phone's serial number you are ready to move forward)
4) Reboot by typing: fastboot reboot-bootloader (I do this just to test the connection but it's not 100% necessary)
5) Flash the bootloader: fastboot flash bootloader /Users/kevin/Desktop/Android/sdk/platform-tools/bootloader.img
6) Reboot: fastboot reboot-bootloader
7) Flash the radio: fastboot flash radio /Users/kevin/Desktop/Android/sdk/platform-tools/radio.img
8) Reboot: fastboot reboot-bootloader
9) Flash the system partition: fastboot flash system /Users/kevin/Desktop/Android/sdk/platform-tools/system.img
10) Flash the data partition: fastboot flash userdata /Users/kevin/Desktop/Android/sdk/platform-tools/system.img (Note: this command will wipe your device)
11) Flash the kernel/ramdisk: fastboot flash boot /Users/kevin/Desktop/Android/sdk/platform-tools/boot.img
12) Flash the recovery partition: fastboot flash recovery /Users/kevin/Desktop/Android/sdk/platform-tools/recovery.img
13) Erase the cache partition: either a) fastboot erase cache OR b) fastboot format cache <<== (the second option seems to work better for most people and it's what I used)
14) Reboot: fastboot reboot
After completing step 14 your phone should reboot to the initial setup screen. If you follow those steps vigorously you won't have any issues. If it doesn't work you did something wrong and should start over. If it doesn't work on a second try then I'd re-download the system image from HERE again just to be sure the .img files you are ultimately trying to use aren't corrupt somehow.

sn0warmy said:
Yeah you do. I just did this on my Mac for my Nexus 4 and Nexus 7 last night with absolutely no issues.
The procedure I used is as follows...
1.1) Download the factory image and ensure all .img files are extracted to the "platform-tools" folder
1.2) Boot phone into fastboot mode by powering it down then holding volume down/power at the same time until the fastboot screen appears
2) Plug the phone into the computer via USB cable
3) Open terminal and type: fastboot devices (if it recognizes your phone's serial number you are ready to move forward)
4) Reboot by typing: fastboot reboot-bootloader (I do this just to test the connection but it's not 100% necessary)
5) Flash the bootloader: fastboot flash bootloader /Users/kevin/Desktop/Android/sdk/platform-tools/bootloader.img
6) Reboot: fastboot reboot-bootloader
7) Flash the radio: fastboot flash radio /Users/kevin/Desktop/Android/sdk/platform-tools/radio.img
8) Reboot: fastboot reboot-bootloader
9) Flash the system partition: fastboot flash system /Users/kevin/Desktop/Android/sdk/platform-tools/system.img
10) Flash the data partition: fastboot flash userdata /Users/kevin/Desktop/Android/sdk/platform-tools/system.img (Note: this command will wipe your device)
11) Flash the kernel/ramdisk: fastboot flash boot /Users/kevin/Desktop/Android/sdk/platform-tools/boot.img
12) Flash the recovery partition: fastboot flash recovery /Users/kevin/Desktop/Android/sdk/platform-tools/recovery.img
13) Erase the cache partition: either a) fastboot erase cache OR b) fastboot format cache <<== (the second option seems to work better for most people and it's what I used)
14) Reboot: fastboot reboot
After completing step 14 your phone should reboot to the initial setup screen. If you follow those steps vigorously you won't have any issues. If it doesn't work you did something wrong and should start over. If it doesn't work on a second try then I'd re-download the system image from HERE again just to be sure the .img files you are ultimately trying to use aren't corrupt somehow.
Click to expand...
Click to collapse
In the other walk through flash system image and boot image is replaced by "./fastboot update image-occam-jwr66v.zip". This could help those who are having problems flashing the system image file. I've also seen this method used for windows in that all you flash is the bootloader image then the update image and your done.

-w is to clear the userdata, but the problem is its not pushing the system.img on the phone! Tried without -w and yet the same issue! I have restored my previous rom and madea nandroid for 4.2.2 stock! Might go back to that and try updating ota! Can somebody confirm if i have to lock bootloader and lose root to get an update!
I have no clue why the same steps work for 4.2.2 but not 4.3 image files!
Sent from my Nexus 4 using Tapatalk 4 Beta

One thing I don't think anyone has mentioned (which may actually be the core solution to this problem for everyone) is that you need to update your SDK Platform from 17 to 18 and you need to install "Android Support Repository" in order for 4.3 to properly flash. To do this open terminal and paste the path to the "android" executable file found under sdk/tools. My path was:
/Users/kevin/Desktop/Android/sdk/tools/android
After pasting the appropriate path into terminal hit enter. This will open the SDK Manager. Once SDK Manager is open it will ask to update outdated drivers. One of the drivers being updated is SDK Platform. Before hitting the update button scroll down to the 'Extras' folder and check the box next to "Android Support Repository". Now hit the update button.
After doing this, reboot the computer (may or may not be necessary) and try flashing again by following the steps I provided in post #5. Let me know if that solved it.

Well, i may try that! But as if now, went to bootcamp, installed drivers and sideloaded 4.3. I may still try updating sdk, just in case i may neeed to do this again!
Where is this sdk/tools?
Sent from my Nexus 4 using Tapatalk 4 Beta

Cantacid said:
Well, i may try that! But as if now, went to bootcamp, installed drivers and sideloaded 4.3. I may still try updating sdk, just in case i may neeed to do this again!
Where is this sdk/tools?
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
sdk/tools is located wherever you extracted the .zip file to. In my case I just put it all in a parent folder on the desktop called "Android".

N7 3G 32 Booting failed

I know there is many topic like this, but I need urgent help. We go to holiday on saturday and I have to decide what to do.
Today got I back my N7 from Brno/Czech from warranty repair. Than the device shut down and I couldn't power on, they replaced my charger and sent back the device. I sent on 26th in July with an RMA number.
When I got back the device I started by the courier and it booted into Android. About 10 minutes later it showed me an update to 4.3 and I allowed it. It restarted and when it was ready the device didn't powered on again. It remained on the Google logo. Now - when I tried to wipe/Hard reset - it only shows the Google logo in the middle and a Start sing on the upper right corner.
I can do:
- recovery
- ADB sees the device
- Nexus 7 toolkit sees too
- Nexus Root Tools sees too
- I can install recovery (TWRP-CWM-stock) it works
- bootloader lock/unlock
but
I cant install
- system/image
- boot
- bootloader
- radio
- etc...
It looks like the flash storage is injured. 20 minutes before I sent a command: flash radio now the device in fastboot and on the upper left corner there is a white text: "Booting downloaded image" It doesn't respond...
I need an advice how to forward, send it back or is there any sollution'

bigsee said:
I know there is many topic like this, but I need urgent help. We go to holiday on saturday and I have to decide what to do.
Today got I back my N7 from Brno/Czech from warranty repair. Than the device shut down and I couldn't power on, they replaced my charger and sent back the device. I sent on 26th in July with an RMA number.
When I got back the device I started by the courier and it booted into Android. About 10 minutes later it showed me an update to 4.3 and I allowed it. It restarted and when it was ready the device didn't powered on again. It remained on the Google logo. Now - when I tried to wipe/Hard reset - it only shows the Google logo in the middle and a Start sing on the upper right corner.
I can do:
- recovery
- ADB sees the device
- Nexus 7 toolkit sees too
- Nexus Root Tools sees too
- I can install recovery (TWRP-CWM-stock) it works
- bootloader lock/unlock
but
I cant install
- system/image
- boot
- bootloader
- radio
- etc...
It looks like the flash storage is injured. 20 minutes before I sent a command: flash radio now the device in fastboot and on the upper left corner there is a white text: "Booting downloaded image" It doesn't respond...
I need an advice how to forward, send it back or is there any sollution'
Click to expand...
Click to collapse
need not to worry man...its a common problem...i have xperienced more than 50 times than while doing fastboot it doesnot respond after a certain period of time and when u power off and start the defice it goes into fastboot mode
solution:
for device: enter in fastboot mode
chose power off then leave it for five minutes till then do the instructions for laptop or computer as mentioned below
for computer/laptop:
shutdown (do not restart, it should be shutdown)
then power on ur computer wait for it to finish booting
plug the usb cable in other port (other than the previous port u were trying)
then power on ur device let it go to fastboot
then plug the usb cable to it
wait for 2-3 minutes
then flash the stock factory image by clicking on flashall.bat
hopefully it will take 5-10 minutes to do the work
and if it exists more than 20 minutes...disconnect ur device and repeat the procedure...till u suceed...
sorry mate but this is the only solution to it...
i have tried it many times...
if u succeed...do reply and hit thx...or if u face another problem...just post the reply:good:

dr.sushant said:
need not to worry man...its a common problem...i have xperienced more than 50 times than while doing fastboot it doesnot respond after a certain period of time and when u power off and start the defice it goes into fastboot mode
solution:
for device: enter in fastboot mode
chose power off then leave it for five minutes till then do the instructions for laptop or computer as mentioned below
for computer/laptop:
shutdown (do not restart, it should be shutdown)
then power on ur computer wait for it to finish booting
plug the usb cable in other port (other than the previous port u were trying)
then power on ur device let it go to fastboot
then plug the usb cable to it
wait for 2-3 minutes
then flash the stock factory image by clicking on flashall.bat
hopefully it will take 5-10 minutes to do the work
and if it exists more than 20 minutes...disconnect ur device and repeat the procedure...till u suceed...
sorry mate but this is the only solution to it...
i have tried it many times...
if u succeed...do reply and hit thx...or if u face another problem...just post the reply:good:
Click to expand...
Click to collapse
Thank you for the answer! I'm trying-I'm trying and trying, but none...
I got two error messages, the first is when it sends the radio to the device:
sending 'radio' <16384KB>...
OKAY [2.078s]
writing 'radio'...
FAILED <remote: <BadParameter>>
finished. total time: 2.094s
the second at the end:
checking version-baseband...
FAILED
Device version-baseband is 'N/A'.
Update requires '1231_0.17.0_1205'
When I hit The Anykey (I didnt find it at first ) nothing happens... so I'm sad again...
What can I do yet?

bigsee said:
Thank you for the answer! I'm trying-I'm trying and trying, but none...
I got two error messages, the first is when it sends the radio to the device:
sending 'radio' <16384KB>...
OKAY [2.078s]
writing 'radio'...
FAILED <remote: <BadParameter>>
finished. total time: 2.094s
the second at the end:
checking version-baseband...
FAILED
Device version-baseband is 'N/A'.
Update requires '1231_0.17.0_1205'
When I hit The Anykey (I didnt find it at first ) nothing happens... so I'm sad again...
What can I do yet?
Click to expand...
Click to collapse
What factory image have you tried?
Update requires '1231_0.17.0_1205'
Click to expand...
Click to collapse
I think this one can be dodged by installing the 4.2.2 factory image (I remember that 4.2.2 had 1205 BB so this should install it) from here. Also have a look here for how to return to stock. It also worked for me upgrading to 4.3.
I hope it helps

al3x1393 said:
What factory image have you tried?
I think this one can be dodged by installing the 4.2.2 factory image (I remember that 4.2.2 had 1205 BB so this should install it) from here. Also have a look here for how to return to stock. It also worked for me upgrading to 4.3.
I hope it helps
Click to expand...
Click to collapse
Hy!
This image: nakasig-jdq39-factory-0798439d.img unzipped to the directory of fastboot in c:\
I tried this:
Code:
- unpacking the .zip file
fastboot format system
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format cache
fastboot format userdata
(optionally: fastboot flash userdata userdata.img)
from here:
http://forum.xda-developers.com/showthread.php?p=44317341#post44317341
And it was succes! The tablet booted in, I could set it up, but there is a minor (major?) problem: it has lost 75% os the storage capacity, the storage is 6.02 GB.. it is a 32 GB 3G version...
I dont dare to upgrade now
edit: oopppsss I forgot: I made the above commands in a machine: winXP32 - 768 MB RAM - and a Blackberry USB cable!!!

bigsee said:
Hy!
This image: nakasig-jdq39-factory-0798439d.img unzipped to the directory of fastboot in c:\
I tried this:
Code:
- unpacking the .zip file
fastboot format system
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format cache
fastboot format userdata
(optionally: fastboot flash userdata userdata.img)
Click to expand...
Click to collapse
It sounds like one or more partitions are not mounted by android (either they are not formatted properly or i don't know, but android can't see it/them).
I think you can try erasing them at all...however when I upgraded it to 4.3 I used that flashall.bat (or something like that) you can find inside the archive downloaded from Google website. You can try that too, it's basically the same thing as typing them by yourself, but you know...just to be sure everything it's ok.
Also from what i see in your code, you don't flash the radio (baseband) image at all and because of that your baseband/radio problem will persist at a further update. You formatted user data so you don't care about your files, so you can perform a full wipe and erase everything just to get things done well.
However, if you want to do it by yourself try theese full wipe instructions (OF COURSE YOU HAVE TO CHANGE bootloader-tilapia-4.23.img AND radio-tilapia-1231_0.18.0_0409.img AND image-nakasig-jwr66v.zip WITH YOUR 4.2.2 ONES (THEESE ARE FOR 4.3)):
Code:
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
> fastboot flash bootloader bootloader-tilapia-4.23.img
> fastboot reboot-bootloader
> fastboot flash radio radio-tilapia-1231_0.18.0_0409.img
> fastboot reboot-bootloader
> fastboot -w update image-nakasig-jwr66v.zip

al3x1393 said:
It sounds like one or more partitions are not mounted by android (either they are not formatted properly or i don't know, but android can't see it/them).
I think you can try erasing them at all...however when I upgraded it to 4.3 I used that flashall.bat (or something like that) you can find inside the archive downloaded from Google website. You can try that too, it's basically the same thing as typing them by yourself, but you know...just to be sure everything it's ok.
Also from what i see in your code, you don't flash the radio (baseband) image at all and because of that your baseband/radio problem will persist at a further update. You formatted user data so you don't care about your files, so you can perform a full wipe and erase everything just to get things done well.
Full wipe instructions (OF COURSE YOU HAVE TO CHANGE bootloader-tilapia-4.23.img AND radio-tilapia-1231_0.18.0_0409.img AND image-nakasig-jwr66v.zip WITH YOUR 4.2 ONES (THEESE ARE FOR 4.3)):
Code:
>fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
> fastboot flash bootloader bootloader-tilapia-4.23.img
> fastboot reboot-bootloader
> fastboot flash radio radio-tilapia-1231_0.18.0_0409.img
> fastboot reboot-bootloader
> fastboot -w update image-nakasig-jwr66v.zip
Click to expand...
Click to collapse
Thanks! I store this method but I wait a little bit more because I started a new RMA by Asus. Now I'm waiting for their answer.

bigsee said:
Thanks! I store this method but I wait a little bit more because I started a new RMA by Asus. Now I'm waiting for their answer.
Click to expand...
Click to collapse
As you wish

At least it came back from repair - from Brno - with a JOP40D FW and a working 4.2.1.
After update - to 4.2.2. - it showed an error but it could boot into the former system ... 4.2.1...
I had to reflash to the JWR66Y FW without the correct recovery...
Currently my Nexus 7 is living with a working 4.3 but without a recovery

I played with N7 a little bit. I discovered that I can only be succes if I erase boot/recovery/system/userdata and than flash these img's individually anyway I get a "booting failed" message w/o working recovery and/or android. Nor the flash-all.bat nor the bootloader/radio/update doesn't work.
Q: Philos64 wrote a super howto (here: http://forum.xda-developers.com/showthread.php?t=2175086) to flash the stock and he says: "Reboot to your recovery for confirm the install - You will see the progress bar moving. When it's done, the tab will automatically reboot into normal mode[, if your Nexus doesn't reboot itself, reboot yourself!" I never do it because of the missing recovery... Should I/can I write only the BL or radio end at the end and step into recovery to finish or levye it on the present state?

Did you tried boot into stock recovery then via fastboot?

No I didnt. I enjoyed the working system...
Tapatalk 2-vel küldve az én Nexus 7-ről

[Q] Back to stock help???

So I recently grabbed me a Grouper recently to *cough* remember my first Android powerhouse (before I met the Optimus G) and decided to tinker with it as usual. I've owned 6 (now 7) different Groupers in this lifetime and have great experience with it, how to get those pesky drivers working, etc. This is my first 32GB model ever. Anyways, I unlocked the BL, rooted and flashed TWRP (thanks to WugFresh's toolkit) and decided to play with the newer roms (last time I owned one, KitKat was a rumor) and kernel combos. Anyways, I decided I prefer its stock performance and battery, and that maybe I'd use Xposed to tweak apperance instead. My mistake was, I should have flashed a flashable stock rom. But NOOOOO...I decided to flash it back to stock with the fastboot method (which we have various threads on, and toolkits including WugFresh's). Trying the manual method, I followed the following guide using a 4.4 image zip file:
http://forum.xda-developers.com/showthread.php?t=1907796
Claims that the sysem.img doesnt exist when it gets to that part. I extracted the entire file and it DOES exist. Anyways, I tried WugFresh's tk and sort of gives me the same ending (after literally almost an hour of waiting TWICE due to my old PC).
THERE WAS A GUIDE I SAW SOMEWHERE while Googling "how to" get back to stock on Google which actually point ou how to MANUALLY flash each .img yourself one by one via fastboot, which I really intended on doing instead of the above methods (DIY anyone?) but I can't find that guide and I'm not even sure if the post was here on XDA or Android Central. I should have done all Google search on the PC instead but ATM the tablet seemed more convenient for a search.
Anybody know the guide I am mentioning or know what I am talking about? I am assuming that method will solve my dilemma, and I like doing these things manually at times anyways....
EDIT: To my disappointment, found the post, but no good:
http://www.androidbeat.com/2013/11/flash-factory-image-nexus-device/
Apperantly everything flahes fine until it gets to the system.img part...adb/fastboot just freezes there and wont budge at all. Since I noticed that it did flash things, I've decided to flash TWRP and just flash a rom from my flash drive (thanks to a USB OTG) but I would still like to actually FIX the thing properly and return it 100% stock. Any ideas?

Crossvxm said:
I should have flashed a flashable stock rom. But NOOOOO...I decided to flash it back to stock with the fastboot method
Click to expand...
Click to collapse
I'm not sure what you mean by stock. Are you trying to flash a "Stock" rom from the community or the stock images provided by google?
If you are using nakasi-ktu84p image, the flash script contains:
Code:
fastboot oem unlock
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-grouper-4.23.img
fastboot reboot-bootloader
sleep 10
fastboot -w update image-nakasi-ktu84p.zip
You can see here the exact process of getting back to stock.
The boot, cache, recovery, system, and userdata are erased.
Then an attempt to flash the bootloader. This will fail on nakasi-ktu84p and several images back.
Google has been negligent in addressing this issue.
I was able to find success with bootloader-grouper-4.23.img which I extracted from nakasi-krt16s.
You could save time and bandwidth from acquiring it here.
This bootloader also failed to flash for me!
If you have flashed a custom bootloader in the past, you may need to go all the way back to JDQ39 bootloader-grouper-4.18.img.
fastboot flash that, and then you will be able to flash 4.23 from krt16s.
Once you have passed this small ordeal you should be able to install the latest ROM.
In summary, you should be able to do the following from a system that has the fastboot binary:
Code:
EXTRACT nakasi-ktu84p-factory-76acdbe9.tgz
OVERWRITE bootloader-grouper-4.23.img with one acquired from krt16s
Code:
nakasi-ktu84p bootloader-grouper-4.23.img
MD5 = 5bdb2e87370cdb1a7ea14bb0c3e21390
krt16s bootloader-grouper-4.23.img
MD5 = df53028033c9eccf4fe5ba7bc198ce24
Code:
run flash-all.sh or flash-all.bat
PS.
I have been lured by the idea of stock stability, performance, and battery life. Something about Xposed seems dirty to me.
Battery life and Performance have always been better on a custom ROM / Kernel in my experience.
Stability can be rock solid when you've got a good system.
My favourite solution is to have the stock image installed and stripped down for size. This always you to boot in and update your apps from playstore.
I then install a custom ROM alongside via multiRom. This rom also has extras stripped out and no gapps installed.
From Rom 1 you can copy your apks into Rom 2 as needed.
I tend to avoid any apps that would be incompatible with this method!

crache said:
I'm not sure what you mean by stock. Are you trying to flash a "Stock" rom from the community or the stock images provided by google?
If you are using nakasi-ktu84p image, the flash script contains:
Code:
fastboot oem unlock
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-grouper-4.23.img
fastboot reboot-bootloader
sleep 10
fastboot -w update image-nakasi-ktu84p.zip
You can see here the exact process of getting back to stock.
The boot, cache, recovery, system, and userdata are erased.
Then an attempt to flash the bootloader. This will fail on nakasi-ktu84p and several images back.
Google has been negligent in addressing this issue.
I was able to find success with bootloader-grouper-4.23.img which I extracted from nakasi-krt16s.
You could save time and bandwidth from acquiring it here.
This bootloader also failed to flash for me!
If you have flashed a custom bootloader in the past, you may need to go all the way back to JDQ39 bootloader-grouper-4.18.img.
fastboot flash that, and then you will be able to flash 4.23 from krt16s.
Once you have passed this small ordeal you should be able to install the latest ROM.
In summary, you should be able to do the following from a system that has the fastboot binary:
Code:
EXTRACT nakasi-ktu84p-factory-76acdbe9.tgz
OVERWRITE bootloader-grouper-4.23.img with one acquired from krt16s
Code:
nakasi-ktu84p bootloader-grouper-4.23.img
MD5 = 5bdb2e87370cdb1a7ea14bb0c3e21390
krt16s bootloader-grouper-4.23.img
MD5 = df53028033c9eccf4fe5ba7bc198ce24
Code:
run flash-all.sh or flash-all.bat
PS.
I have been lured by the idea of stock stability, performance, and battery life. Something about Xposed seems dirty to me.
Battery life and Performance have always been better on a custom ROM / Kernel in my experience.
Stability can be rock solid when you've got a good system.
My favourite solution is to have the stock image installed and stripped down for size. This always you to boot in and update your apps from playstore.
I then install a custom ROM alongside via multiRom. This rom also has extras stripped out and no gapps installed.
From Rom 1 you can copy your apks into Rom 2 as needed.
I tend to avoid any apps that would be incompatible with this method!
Click to expand...
Click to collapse
Your on the right track that's exactly what I was looking for, but to me it doesn't work on the system.img flashing part, it stays stuck there forever without a hint of movement at all. I left it flashing from 4am to 7am with no progress. I though it was working as the Windows Task Manager was showing fast boot constantly changing in CPU usage as it does when its at work. But sadly, it gets stuck there for good. Then closing fast boot won't work, I have to shut down the PC in order for it to leave

Crossvxm said:
Your on the right track that's exactly what I was looking for, but to me it doesn't work on the system.img flashing part, it stays stuck there forever without a hint of movement at all. I left it flashing from 4am to 7am with no progress. I though it was working as the Windows Task Manager was showing fast boot constantly changing in CPU usage as it does when its at work. But sadly, it gets stuck there for good. Then closing fast boot won't work, I have to shut down the PC in order for it to leave
Click to expand...
Click to collapse
I'm not familiar with the tools you are using. Have you used the commands directly from the command line, and what is the output?

crache said:
I'm not familiar with the tools you are using. Have you used the commands directly from the command line, and what is the output?
Click to expand...
Click to collapse
WugFresh is a toolkit made to root, unlock boot loader, relock, restore to stock, etc. And yeah I used the fastboot erase and fastboot flash commands via ADB/fast boot and as I said, everything goes well except the part where its time to flash the system.img, it just hangs there doing nothing. Tried and left it for several hours and still nothing

Try a different USB port on you computer or a different USB cable... or both.
Crossvxm said:
...
....it doesn't work on the system.img flashing part, it stays stuck there forever without a hint of movement at all.
...
Click to expand...
Click to collapse
Hi, Crossvxm...
This seems to be a relatively common problem, and I always seem to have it myself when fastboot flashing factory stock.
I've no idea why, but the fastboot connection seems to 'time-out' when fastboot flashing 'system.img'.
Now normally, and just prior to running any fastboot flash commands, you should run this command...
Code:
fastboot devices
This command doesn't actually do anything; it's essentially just diagnostic and is used to confirm you have a viable fastboot connection prior to flashing anything. If do you have a fastboot connection, you should see something like this (with the N7 booted into the bootloader)...
Code:
015d2d42xxxxxxxx fastboot
This is the Nexus 7's unique serial number followed by the word 'fastboot'. If you don't see this, then you likely have a driver problem...
...BUT HOWEVER, I KNOW I DON'T HAVE A DRIVER PROBLEM.. so when having problems with 'sending system', and upon opening a second command prompt window on my Windows laptop, and typing fastboot devices again, the Nexus 7's serial number now no longer appears... and this is AFTER the bootloader and boot img's have been sent and written successfully.
At this point, I can only conclude, and that for unknown reasons, my fastboot connection has 'died'... and 'sending system' is now permanently 'stuck'.
And the fastboot flash attempt has failed.
-----------------------------------------------------
The solution for me, was to change to a different USB port on my laptop. Another possibility might be to try a different USB cable... I haven't tried this... just a change of USB port on my laptop was sufficient, and the problem with flashing system.img was resolved.
Either way, reboot the N7's bootloader using a differerent USB port on your computer or a different USB cable... and attempt the flash again.
One final point... 'sending system' does take longer than the other .img's, probably due to it's size... but it really should take no longer than around 5 minutes... 10 minutes maximum.
Hope this helps... and good luck.
Rgrds,
Ged.

[Solved] I'm afraid I really bricked my Shield TV 2015

Hi everyone,
As mentionned in the title I'm afraid I bricked my Shield TV (model 2015, 16GB).
It was previously running StockRestyle 3.0 Marshmallow (from zulu99: https://forum.xda-developers.com/shield-tv/development/rom-t3321787) and all was fine with it.
But since Nvidia announced Nougat for the Shield TV, I wanted to give it a try.
Thus, I tried to flash the official recovery images from Nvidia, but I think I made the mistake to flash the Nougat version instead of the Marshmallow one.
So, here is what I've done:
- I copied the official Nougat recovery images on my PC in my adb folder
- I ran the flash-all.bat
- it started all right, but was then stuck for several minutes
- the shield TV rebooted itself but was stuck on the Nvidia logo
- after several minutes without change nor messages on the command, I quit the command terminal.
Later, I tried to start the process again without success.
Now, I can have access to the bootloader using the hardware procedure (long-press on the power button).
Unfortunately, it says on the top "Production mode: fused" (see the attached pictures).
From the bootloader, I tried "Forced recovery" -> I got a black screen -> Fail
I also tried the "Boot recovery kernel" -> I got the screen image with the android robot down with an warning symbol (see the attached pictures)
I tried adb and fastboot without success.
When I reboot the bootlaoder, with the shield connected to my PC with an OTG cable, the shield is detected but there is a warning message on my PC (it's not well recognized).
Also, "fastboot devices" returns nothing.
Technically, the shield is l still under warranty since it's less than 2 years old, but I'm afraid this "Production mode: fused" message would void it!
Any similar situation or suggestion?
Thank you in advance and have a nice day.

Hi, that production mode: fused is normal. I checked and I have it. I think it is there since I unlocked the bootloader. I run Full Android Nougat from @zulu99 without issues.
Do not keep trying to flash things just to flash. While you be able to boot into bootloader you can recover it (remember this) but is also true that if you mess with the bootloader you can brick your device. You're just soft bricked not hard bricked.
First, post the complete version of the bootloader, in the screenshot I can't see the whole version.
For later (do not attempt to flash anything until we go thru some checks):
Try with another known working USB cable and/or reinstalling fastboot drivers. And do not use flashall.bat, you will do it command by command.
Enviado desde mi Moto X mediante Tapatalk

That's what happens when you don't follow directions

Here is a picture with the complete version of the bootloader.
I followed quite well the instructions a year ago when I was trying to evaluate the pros and cons of Stock ROM, Stock Restyle and Full Android. Unfortunately @zulu99 posts have been closed since then.
Thus I forgot I had to revert back to standard Marshmallow first ;-(

I also tried two others USB OTG cables.
With on of them I managed to get "fastboot devices" recognizing a device, and I don't have this warning message on my PC (it's not well recognized) when starting the bootloader.
What should I do next?

Problem solved!
Since I guess the issue was mainly due on the suddenly defective OTG cable (it worked in the beginning of my last try, since I managed to flash some parts), I started the procedure again with with the official recovery 5.0.2.
- I started the bootloader using the HW method: long-press on the power button during powering up, until the bootloader appears
- Then,
* fastboot -w
- Then, again, I had to start the bootloader using th HW method
- Then, I followed most of the points described in the flash-all.bat files (except the adb commands)
* fastboot flash staging blob
* fastboot flash boot boot.img
* fastboot reboot
- Again, I had to start the bootloader using th HW method
- Then,
* fastboot flash recovery recovery.img
* fastboot flash system system.img
* fastboot flash vendor vendor.img
* fastboot reboot
- and voilà: I got Nougat running. Then the time it took me to enter my email credentials and so on, the OTA update to 5.1 was downloaded and ready to install.
A few minutes and a reboot later, I have the latest version running.
Thanks guys.

Your issue was the USB cable, if there is no good connection the flash can be incomplete thus corrupted. It is better to run the commands manually one by one so you know if it was successful on each flash or identify where it got stuck. Your lucky it didn't fail while flashing blob.
Probably failed after the boot flashing and fastboot reboot.
I suggest you get another USB cable, always use high quality cables. The internet is flooded with Shield TV users with TWRP, flashing issues and bricked devices because of a bad USB cable.
Enviado desde mi Moto X mediante Tapatalk

I tried doing the same thing and i got errors when flashing system and vendor files. It says that data is too large.