so my nexus 7 (original) was getting laggy so i tried reflashing the factory image. It wasn't working, so i downloaded the nexus root toolkit and tried flashing the stock ROM. It erases the boot, cache, system, etc, but it keeps getting stuck on the "sending bootloader" part. It just says:
sending 'bootloader' <2100 KB>...
what should i do? is it my computer? i really don't want a bricked nexus. please help...
Try flashing in boot loader
Type : flash fastboot boot boot.img
in C:\Andriod or path of the adb
no one help you - if you can not get access to fastboot - buy new nexus
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
leeamsi97 said:
so my nexus 7 (original) was getting laggy so i tried reflashing the factory image. It wasn't working, so i downloaded the nexus root toolkit and tried flashing the stock ROM. It erases the boot, cache, system, etc, but it keeps getting stuck on the "sending bootloader" part. It just says:
sending 'bootloader' <2100 KB>...
what should i do? is it my computer? i really don't want a bricked nexus. please help...
Click to expand...
Click to collapse
The solution here is at least in part not to use the toolkit so you can see for yourself what is going wrong. Download the appropriate factory image for your device and the Android platform tools, and then you can use fastboot to flash the relevant images over.
The bigger question is what state your device is in. Are you able to kick the machine into fastboot mode still?
sambistt said:
no one help you - if you can not get access to fastboot - buy new nexus
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
This is possibly one of the most useless posts I have yet seen here. We don't even know the status of the OP's device.
This is possibly one of the most useless posts I have yet seen here. We don't even know the status of the OP's device.
Click to expand...
Click to collapse
my post help him, your post just waste of time
- if him can`t access device via fastboot - how can it resolve command from it?
don`t bully this user - you cann`t help him - its not soft bricked !!!
sambistt said:
my post help him, your post just waste of time
- if him can`t access device via fastboot - how can it resolve command from it?
don`t bully this user - you cann`t help him - its not soft bricked !!!
Click to expand...
Click to collapse
Him no say him no can use fastboot. You assume too much and obviously have no clue what you're talking about.
Sent from my Nexus 7 using xda app-developers app
sambistt said:
my post help him, your post just waste of time
- if him can`t access device via fastboot - how can it resolve command from it?
don`t bully this user - you cann`t help him - its not soft bricked !!!
Click to expand...
Click to collapse
I'm not "bullying" anyone, I'm pointing out that your post is based off of nothing but conjecture right now. If OP killed even fastboot then yes, his options are limited, but your post is inviting an even larger waste of time based on inadequate information-- which is exactly how these problems occur.
Solved
Thanks everyone. I got it to work. I should have mentioned that i did use flashboot initially but used the toolkit when it didn't work. In the end, I finally got fastboot to flash the image. Thanks again for replying.
As the title says I'm getting stuck on:
sending 'bootloader' (2100 KB)
when trying to flash a stock image to return the tablet to stock. the tablet is basically dead, i can get into the bootloader, which freezes anytime i try to flash the stock image, and i can't boot into recovery or android itself.
i am desperate for help right now. was trying to sell this today and now i feel like an asshole since i now soft bricked it on the day he was suppose to buy it. I've done factory restores on 2 GNex, a G4 and the 2013 N7 and NEVER had any issues like this. hell never had any issues of any kind with those devices.
*edit* well i finally got it to flash, only took 20 tries. don't know wtf that was all about but glad i'm getting rid of this thing.
neok44 said:
As the title says I'm getting stuck on:
sending 'bootloader' (2100 KB)
when trying to flash a stock image to return the tablet to stock. the tablet is basically dead, i can get into the bootloader, which freezes anytime i try to flash the stock image, and i can't boot into recovery or android itself.
i am desperate for help right now. was trying to sell this today and now i feel like an asshole since i now soft bricked it on the day he was suppose to buy it. I've done factory restores on 2 GNex, a G4 and the 2013 N7 and NEVER had any issues like this. hell never had any issues of any kind with those devices.
*edit* well i finally got it to flash, only took 20 tries. don't know wtf that was all about but glad i'm getting rid of this thing.
Click to expand...
Click to collapse
Well, it just happened to me too and while in fastboot, well mine was in fastboot while this was happening, I just used to volumn button to get to boot to recovery. Once in recovery I had it reboot to the bootloader. After I was back in fastboot and started the install again, it worked.
Hey here goes my nexus 7 grouper has some how got corrupted and the only thing that is still working is fastboot, However the usual recovery using the google stock roms i ether get signature mismatch or unknown error code (really useful error code).
Currently running bootloader 4.23 and was using stock android 4.4.3 before it all went oh so wrong.
I have tried flashing it back to stock with the nexus root toolkit and the flash batch file provided by google and both have failed.
Is there a way to force a flash to ignore all signatures and i will go back to an earlier rom from google that worked properly?
or do i need a new tablet as Asus support has been less than useful?
Cheers
Support
ScoTTisH-GingeR said:
Hey here goes my nexus 7 grouper has some how got corrupted and the only thing that is still working is fastboot, However the usual recovery using the google stock roms i ether get signature mismatch or unknown error code (really useful error code).
Currently running bootloader 4.23 and was using stock android 4.4.3 before it all went oh so wrong.
I have tried flashing it back to stock with the nexus root toolkit and the flash batch file provided by google and both have failed.
Is there a way to force a flash to ignore all signatures and i will go back to an earlier rom from google that worked properly?
or do i need a new tablet as Asus support has been less than useful?
Cheers
Click to expand...
Click to collapse
Hello,
Hvae you tried flashing a recovery though fastboot? Once you have done this you should be able to sideload a new rom and BAM your done.
See here for fastboot flashing a new recovery: http://teamw.in/project/twrp2/103
See here for sideloading in recovery: http://teamw.in/ADBSideload
[email protected] said:
Hello,
Hvae you tried flashing a recovery though fastboot? Once you have done this you should be able to sideload a new rom and BAM your done.
See here for fastboot flashing a new recovery
See here for sideloading in recovery:
Hey Scott cheers for the reply here is the result of the attempting to flash twrp.
C:\nexus\4.4.4>fastboot flash recovery openrecovery-twrp-2.7.1.1-grouper.img
sending 'recovery' (8502 KB)...
OKAY [ 1.039s]
writing 'recovery'...
FAILED (remote: (FileWriteFailed))
finished. total time: 3.863s
Any more ideas or am i binning my nexus?
Click to expand...
Click to collapse
ScoTTisH-GingeR said:
Hey here goes my nexus 7 grouper has some how got corrupted and the only thing that is still working is fastboot, However the usual recovery using the google stock roms i ether get signature mismatch or unknown error code (really useful error code).
Currently running bootloader 4.23 and was using stock android 4.4.3 before it all went oh so wrong.
I have tried flashing it back to stock with the nexus root toolkit and the flash batch file provided by google and both have failed.
Hello,
My August 2012 Nexus 7 got same issue.
Boot loop up to animated circles or Android update.
Rooted. CWM recovery. Stock ROM 4.4.3
General remark/ the device was getting really slow in spite of regular use of Lagfix.
Fastboot OK. That is in fact the only way to power off the device.
Wipe Data / Factory reset had no effect on bootloop.
Errors trying to flash official Factory image through adb: example " recovery.sig files not found". I tried to flash them individually
I tried the Nexus Toolkit: Error trying to load a factory image. Error trying to return to stock recovery.
I suspect a memory issue.
Finally I just return this morning the device to ASUS France, after requesting a Return Agreement.
No more warranty; I wonder if the resulting cost are worst this action if tablet is not reparable.
I am really upset.
Click to expand...
Click to collapse
Hello,
Have you tried the steps to flash a system imagem, all you need is to have access to fastboot. Please visit: https://developers.google.com/android/nexus/images for instructions on how to do this.
I hope these steps help, If you need further assistance you can email me at [email protected]. Be sure to place case number N140811561 in the subject line for reference.
Regards,
Scott
ASUS Customer Loyalty
Motherboard issue
[email protected] said:
Hello,
Have you tried the steps to flash a system imagem, all you need is to have access to fastboot. Please visit: https://developers.google.com/android/nexus/images for instructions on how to do this.
I hope these steps help, If you need further assistance you can email me at [email protected]. Be sure to place case number N140811561 in the subject line for reference.
Regards,
Scott
ASUS Customer Loyalty
Click to expand...
Click to collapse
-----------------------------------------------------------------------------------------------------------
I just got the answer from Ename, ASUS repair contractor in France.
Motherboard got problems. Need replacement.
Total cost 192 €.
Basically I have better to buy a new one.
That is really bitter after just 2 years .....!!!!!
Is the 2013 model more robust?
marcelin99 said:
-----------------------------------------------------------------------------------------------------------
I just got the answer from Ename, ASUS repair contractor in France.
Motherboard got problems. Need replacement.
Total cost 192 €.
Basically I have better to buy a new one.
That is really bitter after just 2 years .....!!!!!
Is the 2013 model more robust?
Click to expand...
Click to collapse
Hello,
The Nexus 7 21013 is slightly lighter, has a better resolution (1920 x 1200 pixels), adds a rear camera and sports the Qualcomm Snapdragon S4 Pro APQ8064 with 2048 MB RAM. So it is a nice increase in the specs. With a your repair cost of 192 it might be better to consider upgrading your Nexus experience. If you need further support feel free to email me at [email protected] with case number in the N140820223 subject line.
Regards,
Scott
ASUS Customer Loyalty
I could really use some help. I'm at the edge of my patience and have tried pretty much everything I can think of. I say near brick cause a phone without WiFi and BT is kinda useless.
Here's the back story. I had my previous xt1575 stolen. I purchased a used one off ebay. I received it, only to find it was bootloader unlocked, rooted. Not an issue in theory but I wasn't told that. Ok, upon trying the phone it worked but the battery would last 3 hours, it would have random reboots and would run so hot i could hardly hold the phone. I figured it was a faulty kernel. I flashed a new kernel and stock rom. Battery life went back to almost perfect but was off by about 20%. The random reboots were still an issue, but everything else seemed to work. A randomly rebooting phone is far from ideal. I figured I'd keep trying. Maybe it was a software issue. I would get random results with different roms. And the rebooting really seemed to occur when I had all my apps downloaded. So, I decided to run to flash again and run lean and see if with just the default apps whether it would reboot. After the flash, I waited a few hours, then BT and WiFi just stopped working. No go. The actual toggles revert to off position essentially immediately and neither turn on. I've since tried FDRs, different roms, different kernels, no luck. No idea what to do at this point. It could be hardware, obviously. It could be that the wifi chip was faulty and causing the overheating/battery drain from before, and finally after running so hot that one day before I flashed, it just did final damage to the chip that came to pass 3 days later. I don't know. It's possible but i somehow feel like it's a SW issue. I could send it back but it's complicated and i would really prefer to see if I can get this resolved. I've reflashed the modem bin files of stock roms, etc. Another issue i get often is when i try flashing, I get the writing 'boot'... (bootloader) Preflash validation failed FAILED (remote failure) and other such failures. Additionally, TWRP often just disappears. Aside from that, the OS, usually runs fine. I can't download apps obviously due to no WiFi, but everything else seems fine and I haven't had any reboots since the wifi/bt stopped working. I don't know if it's a partition issue, or hardware or what. I could use some advice. I'm at the limit of my patience and my knowledge here.
Let me know what you guys need and thanks ahead of time for your help.
vijn said:
I could really use some help. I'm at the edge of my patience and have tried pretty much everything I can think of. I say near brick cause a phone without WiFi and BT is kinda useless.
Here's the back story. I had my previous xt1575 stolen. I purchased a used one off ebay. I received it, only to find it was bootloader unlocked, rooted. Not an issue in theory but I wasn't told that. Ok, upon trying the phone it worked but the battery would last 3 hours, it would have random reboots and would run so hot i could hardly hold the phone. I figured it was a faulty kernel. I flashed a new kernel and stock rom. Battery life went back to almost perfect but was off by about 20%. The random reboots were still an issue, but everything else seemed to work. A randomly rebooting phone is far from ideal. I figured I'd keep trying. Maybe it was a software issue. I would get random results with different roms. And the rebooting really seemed to occur when I had all my apps downloaded. So, I decided to run to flash again and run lean and see if with just the default apps whether it would reboot. After the flash, I waited a few hours, then BT and WiFi just stopped working. No go. The actual toggles revert to off position essentially immediately and neither turn on. I've since tried FDRs, different roms, different kernels, no luck. No idea what to do at this point. It could be hardware, obviously. It could be that the wifi chip was faulty and causing the overheating/battery drain from before, and finally after running so hot that one day before I flashed, it just did final damage to the chip that came to pass 3 days later. I don't know. It's possible but i somehow feel like it's a SW issue. I could send it back but it's complicated and i would really prefer to see if I can get this resolved. I've reflashed the modem bin files of stock roms, etc. Another issue i get often is when i try flashing, I get the writing 'boot'... (bootloader) Preflash validation failed FAILED (remote failure) and other such failures. Additionally, TWRP often just disappears. Aside from that, the OS, usually runs fine. I can't download apps obviously due to no WiFi, but everything else seems fine and I haven't had any reboots since the wifi/bt stopped working. I don't know if it's a partition issue, or hardware or what. I could use some advice. I'm at the limit of my patience and my knowledge here.
Let me know what you guys need and thanks ahead of time for your help.
Click to expand...
Click to collapse
What image are you using? Make sure you are using MPH24.49-18-4 (the -4 is important and newer than the one that ends in 18-18 on Moto's site) with the May 1, 2016, security update from here and flashing each step manually using this post's instructions.
I could explain most of the issues individually you are seeing, unless you are already using the specific version I referenced, since they all seem to relate to improper or old version flashing, but it doesn't really matter because the answer to all of them is the same... Reflash the proper version making sure each steps results in an OKAY.
If I am way off base, then it is likely a hardware problem.
acejavelin said:
What image are you using? Make sure you are using MPH24.49-18-4 (the -4 is important and newer than the one that ends in 18-18 on Moto's site) with the May 1, 2016, security update from here and flashing each step manually using this post's instructions.
I could explain most of the issues individually you are seeing, unless you are already using the specific version I referenced, since they all seem to relate to improper or old version flashing, but it doesn't really matter because the answer to all of them is the same... Reflash the proper version making sure each steps results in an OKAY.
If I am way off base, then it is likely a hardware problem.
Click to expand...
Click to collapse
Well, first off thanks a lot for your help. I had installed that particular version, though it wasn't the one currently installed. But I followed all the instructions and steps and got success writes for all and it booted up but didn't recognize any wifi networks and i tried to toggle on the wifi and same as before. Nothing happens. Wifi simply won't turn on. Same for bluetooth. Looking more like a HW problem isn't it?
vijn said:
Well, first off thanks a lot for your help. I had installed that particular version, though it wasn't the one currently installed. But I followed all the instructions and steps and got success writes for all and it booted up but didn't recognize any wifi networks and i tried to toggle on the wifi and same as before. Nothing happens. Wifi simply won't turn on. Same for bluetooth. Looking more like a HW problem isn't it?
Click to expand...
Click to collapse
I mean I know HW can die at any time, and maybe it was already dying from before which caused the initial issues when I got the phone, but I just have this sneaking suspicion that it's not HW related. I can't shake that feeling. But every SW based solution I try doesn't seem to do the trick.
acejavelin said:
I could explain most of the issues individually you are seeing, unless you are already using the specific version I referenced, since they all seem to relate to improper or old version flashing, but it doesn't really matter because the answer to all of them is the same... Reflash the proper version making sure each steps results in an OKAY.
Click to expand...
Click to collapse
Actually when u have a chance, I'd love this. Been rooting, modding my phones for years but I've never gone past a certain level of understanding. I'm not by nature a code guy though I have enjoyed playing around with custom roms and stuff. Anyway, ya, no pressure and my priority is to see if I can get this fixed or should just send it back, but if you do have time afterwards, would love to know what the deal is.
Still hoping someone can help me out with this. Any ideas? I'd really appreciate it.
vijn said:
Still hoping someone can help me out with this. Any ideas? I'd really appreciate it.
Click to expand...
Click to collapse
us the restore to stock tool, then install twrp and flash trupure and without booting flash the updated modem
unitz0mbie said:
us the restore to stock tool, then install twrp and flash trupure and without booting flash the updated modem
Click to expand...
Click to collapse
Hmm. Definitely willing to try that. You wouldn't happen to have links to Trupure and the updated modem would you? And the Restore to stock tool is this I assume: CLARK_RETUS_5.1.1_LPH23.116-18_cid9_subsidy-DEFAULT_CFC.xml_SHAWN5162. Not sure what Trupure is. It's a custom ROM?
vijn said:
Hmm. Definitely willing to try that. You wouldn't happen to have links to Trupure and the updated modem would you? And the Restore to stock tool is this I assume: CLARK_RETUS_5.1.1_LPH23.116-18_cid9_subsidy-DEFAULT_CFC.xml_SHAWN5162. Not sure what Trupure is. It's a custom ROM?
Click to expand...
Click to collapse
https://forum.xda-developers.com/moto-x-style/development/rom-trupurex-fast-smooth-t3237155
scroll down u will find a link for a modem, and u just flash it aswell
trick is to to flash the rom and modem without booting. if u only boot rom u will no wifi/bt etc
unitz0mbie said:
https://forum.xda-developers.com/moto-x-style/development/rom-trupurex-fast-smooth-t3237155
scroll down u will find a link for a modem, and u just flash it aswell
trick is to to flash the rom and modem without booting. if u only boot rom u will no wifi/bt etc
Click to expand...
Click to collapse
That's so weird. Never heard of that before but will definitely try it. Thanks a lot.
unitz0mbie said:
https://forum.xda-developers.com/moto-x-style/development/rom-trupurex-fast-smooth-t3237155
scroll down u will find a link for a modem, and u just flash it aswell
trick is to to flash the rom and modem without booting. if u only boot rom u will no wifi/bt etc
Click to expand...
Click to collapse
And Trupure? That's a ROM I assume. Know where I can find that? I could research it obviously, but figured there's likely a couple different versions of it. Would rather get the one you recommend. - nevermind. I see that the link you provided was for trupure. Thanks a lot. Will let you know how it goes.
unitz0mbie said:
https://forum.xda-developers.com/moto-x-style/development/rom-trupurex-fast-smooth-t3237155
scroll down u will find a link for a modem, and u just flash it aswell
trick is to to flash the rom and modem without booting. if u only boot rom u will no wifi/bt etc
Click to expand...
Click to collapse
The thing is, I'm on 6.0. Secondly my TWRP keeps getting deleted. And I just tried flashing twrp again and now I'm getting this: sending 'recovery' (34434 KB)...
OKAY [ 0.753s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.773s
Not sure how to proceed. Not much I can do without a working recovery. Any ideas?
vijn said:
That's so weird. Never heard of that before but will definitely try it. Thanks a lot.
Click to expand...
Click to collapse
no problem, if u still have no bt u can find the specific files u need to flash
---------- Post added at 11:41 PM ---------- Previous post was at 11:39 PM ----------
vijn said:
The thing is, I'm on 6.0. Secondly my TWRP keeps getting deleted. And I just tried flashing twrp again and now I'm getting this: sending 'recovery' (34434 KB)...
OKAY [ 0.753s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.773s
Not sure how to proceed. Not much I can do without a working recovery. Any ideas?
Click to expand...
Click to collapse
what version of twrp are u using
---------- Post added at 11:43 PM ---------- Previous post was at 11:41 PM ----------
vijn said:
The thing is, I'm on 6.0. Secondly my TWRP keeps getting deleted. And I just tried flashing twrp again and now I'm getting this: sending 'recovery' (34434 KB)...
OKAY [ 0.753s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.773s
Not sure how to proceed. Not much I can do without a working recovery. Any ideas?
Click to expand...
Click to collapse
try using the restore to stock tool, it will remove twrp
and then u can reflash twrp
unitz0mbie said:
no problem, if u still have no bt u can find the specific files u need to flash
---------- Post added at 11:41 PM ---------- Previous post was at 11:39 PM ----------
what version of twrp are u using
Click to expand...
Click to collapse
3.0.2 i think. can't really check but i think that's what i remember from the last time i loaded it
Here's the thing, there seems to be a consistent issue writing to the boot partition and TWRP never lasts. I don't know all that much about this but I feel as though there's a part of the software that is constantly being deleted/overwritten and that may explain why the modem never stays and twrp never stays. Does that make any sense?
The return to stock tool gives the following 2 errors:
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.378s
and
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 149.569s
Obviously the second error is the end of the process. Can't go any further if it can't write the system. Super confused. Every time I install a new ROM another issue pops up.
unitz0mbie said:
no problem, if u still have no bt u can find the specific files u need to flash
---------- Post added at 11:41 PM ---------- Previous post was at 11:39 PM ----------
what version of twrp are u using
---------- Post added at 11:43 PM ---------- Previous post was at 11:41 PM ----------
try using the restore to stock tool, it will remove twrp
and then u can reflash twrp
Click to expand...
Click to collapse
Managed to get the restore to stock working. Restarted bootloader. Tried to flash twrp, and same error: writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.779s
vijn said:
Managed to get the restore to stock working. Restarted bootloader. Tried to flash twrp, and same error: writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.779s
Click to expand...
Click to collapse
is your bootloader locked?
unitz0mbie said:
is your bootloader locked?
Click to expand...
Click to collapse
to be honest, I don't even know any more. I've locked and unlocked it a bunch of times. Some tools I've used automatically lock or unlock it. At this point i just tried to unlock is using my key and got the following error: error: Command length (142) exceeds maximum size (64). So, ya, i have no idea what's going on. The bootloader page says device:locked, but the prebootloader page says bootloader unlocked.
unitz0mbie said:
is your bootloader locked?
Click to expand...
Click to collapse
I have to step away for a couple hours. I will be back. But regardless of how this goes, I just wanted to say thanks for trying to help with this stuff. I've never had so many issues with a phone before. My previous ones would occasionally give me some headaches, but not to this extent. Anyway, hopefully you'll still be around when i get back or will have some other recommendations.
sounds like your BL is locked man.