Hey guys, I think I've bricked my N9. What happened was I rooted it successfully, but then on flashing a custom recovery, I used the wrong image file. Instead of using the flounder image, I mistakenly flashed the volantis one. And then I flashed twrp for flounder. But after that, the recovery could not mount anything and ADB Sideload did not work. After that, I when and restore everything back to stock with factory image, however I cannot boot into system. I am effectively stuck in bootloader, and that's where I am. I tried rooting and flashing twrp recovery, and again, it could not mount and ADB Sideload is not working. I tried everything. Is my N9 done for? Or can someone point me in the right direction and get my N9 back?
I once bricked my lg g2 pretty badly, couldn't use adb or recovery.
I managed to repair it by booting a linux and manually overwrite the partitions with the factoy image.
There is a thread with instructions here on xda in the g2 forum, could work with the nexus to.
nexus 9
DoeBoi said:
Hey guys, I think I've bricked my N9. What happened was I rooted it successfully, but then on flashing a custom recovery, I used the wrong image file. Instead of using the flounder image, I mistakenly flashed the volantis one. And then I flashed twrp for flounder. But after that, the recovery could not mount anything and ADB Sideload did not work. After that, I when and restore everything back to stock with factory image, however I cannot boot into system. I am effectively stuck in bootloader, and that's where I am. I tried rooting and flashing twrp recovery, and again, it could not mount and ADB Sideload is not working. I tried everything. Is my N9 done for? Or can someone point me in the right direction and get my N9 back?
Click to expand...
Click to collapse
just look for the image for your device on recovery. as long as you have fastboot it can be saved. just look for your version flounder custom recovery and it should work
MoooN said:
I once bricked my lg g2 pretty badly, couldn't use adb or recovery.
I managed to repair it by booting a linux and manually overwrite the partitions with the factoy image.
There is a thread with instructions here on xda in the g2 forum, could work with the nexus to.
Click to expand...
Click to collapse
I don't have a Linux system and looking through thread seems too advance for me. I can't relate it to the N9. However, there seems to be something wrong partition, because I can't mount storage.
matt4787 said:
just look for the image for your device on recovery. as long as you have fastboot it can be saved. just look for your version flounder custom recovery and it should work
Click to expand...
Click to collapse
I can flash custom recovery, but I can't push files or adb sideload, therefore I can't do anything in recovery anyway.
Did you try to use the nexus toolkits flying around here?
Maybe they could be of some help..
@DoeBoi you need to flash the factory image. This should help http://forum.xda-developers.com/showthread.php?p=58956577
Sent from my Nexus 5 using XDA Free mobile app
Does the Google Logo flash for a second or so before it goes to bootloader?
nexus 9
Try to get into bootloader by holding power and volume down.
MoooN said:
Did you try to use the nexus toolkits flying around here?
Maybe they could be of some help..
Click to expand...
Click to collapse
I will look in to it, thank you.
jd1639 said:
@DoeBoi you need to flash the factory image. This should help http://forum.xda-developers.com/showthread.php?p=58956577
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I already tried one version of the image, which didn't work, will try to flash the others.
scrosler said:
Does the Google Logo flash for a second or so before it goes to bootloader?
Click to expand...
Click to collapse
restart - sometimes yes and sometimes no, if plug into computer - no, if not plugged - yes,
matt4787 said:
Try to get into bootloader by holding power and volume down.
Click to expand...
Click to collapse
you mean power + volume up, but yes, no problem getting there, also adb is working
thanks for all your help, I will try different factory image and flashing from OTG
The problem is your kernel is not loading or mismatched to the operating system. I have experienced this a lot on HTC devices when I screw something up... I mean "experiment"
You need to flash the boot system and vendor image from the latest factory ROM.
You need to do it manually...
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
Then reboot to recovery and wipe data. Not factory rest but actually wipe all of /data partition.
That should get you back. If not post back results.
If you are not familiar with fastboot then state so and I will help you.
Yes! I got it booting again, thank you everyone for helping. Apparently, the problem was, I think, wiping manually, that is, system, cache, recovery, boot, user data, and vendor didn't erase everything. What did the trick was [fastboot -w], I did this instead of erasing one by one. Thank you so much guys!
DoeBoi said:
Hey guys, I think I've bricked my N9. What happened was I rooted it successfully, but then on flashing a custom recovery, I used the wrong image file. Instead of using the flounder image, I mistakenly flashed the volantis one. And then I flashed twrp for flounder. But after that, the recovery could not mount anything and ADB Sideload did not work. After that, I when and restore everything back to stock with factory image, however I cannot boot into system. I am effectively stuck in bootloader, and that's where I am. I tried rooting and flashing twrp recovery, and again, it could not mount and ADB Sideload is not working. I tried everything. Is my N9 done for? Or can someone point me in the right direction and get my N9 back?
Click to expand...
Click to collapse
First question - Did you flash a bad bootloader? If no, then you cannot have possibly bricked your nexus 9. I do believe this is the ONLY way you could brick a nexus. If you still have access to fastboot mode, you are totally fine. I would recommend flashing the factory images and just starting fresh. Depending on which nexus 9 you have, either the wifi only or LTE variant, you can download the appropriate packages at https://developers.google.com/android/nexus/images . Basically, you need to extract the package into a folder, boot your device into fastboot mode, and run the flashall.bat (windows) or flashall.sh(linux). As long as you have fastboot and ADB properly installed into your $PATH or atleast have fastboot and adb in your working folder, everything should be ok. If you run into any problems, contact me via PM or I can be found on IRC (Network freenode, #android, #cyanogenmod, #android-root). Good luck
bynarie said:
First question - Did you flash a bad bootloader? If no, then you cannot have possibly bricked your nexus 9. I do believe this is the ONLY way you could brick a nexus. If you still have access to fastboot mode, you are totally fine. I would recommend flashing the factory images and just starting fresh. Depending on which nexus 9 you have, either the wifi only or LTE variant, you can download the appropriate packages at https://developers.google.com/android/nexus/images . Basically, you need to extract the package into a folder, boot your device into fastboot mode, and run the flashall.bat (windows) or flashall.sh(linux). As long as you have fastboot and ADB properly installed into your $PATH or atleast have fastboot and adb in your working folder, everything should be ok. If you run into any problems, contact me via PM or I can be found on IRC (Network freenode, #android, #cyanogenmod, #android-root). Good luck
Click to expand...
Click to collapse
Um, he's got it fixed.
Sent from my Nexus 5 using XDA Free mobile app
I too thought I bricked my device and found this thread. Using the recovery from Google I was getting "sending sparse 'system' FAILED (status read failed (Protocol error))" until I used "fastboot -w" like the post above mentioned. Leaving this here in case someone else runs into the problem.
sototallycarl said:
I too thought I bricked my device and found this thread. Using the recovery from Google I was getting "sending sparse 'system' FAILED (status read failed (Protocol error))" until I used "fastboot -w" like the post above mentioned. Leaving this here in case someone else runs into the problem.
Click to expand...
Click to collapse
Thanks for paying it forward.
I have a similar problem my nexus 9 wont turn on and would freeze in the optimizing apps screen after going past the nexus logo but i can get to the fastboot and recovery. But i cannot flash the factory image because my bootloader is locked and i didn't enable developer options prior to the problem. I'm thinking about sideloading the latest ota would that help me ? And is there anyway to unlock bootloader if i can't boot the device?
---------- Post added at 10:10 PM ---------- Previous post was at 10:07 PM ----------
sototallycarl said:
I too thought I bricked my device and found this thread. Using the recovery from Google I was getting "sending sparse 'system' FAILED (status read failed (Protocol error))" until I used "fastboot -w" like the post above mentioned. Leaving this here in case someone else runs into the problem.
Click to expand...
Click to collapse
Can you please explain to me what fastboot w- command means ?
It erases userdata and cache. Often needed if you run into bootloops. But it does wipe your data so backup off your device first.
Bricked N9
Hi everyone, well my problem is that i was trying to flash Android 6.0 but i accidentally execute the flash-all.bat file while i was trying to open it in the note block. It was booting normally but it seems that my N9 was encrypted, so it said that the Unencrypted was incorrect so it forced me to hard reset my tablet. i did this but it was taking like 20 min to erase my file (the android appeared and it was over a message that was "Wiping" -it was in spanish borrando-) so i turn it off and now my tablet is on a bootloop, after it appears the Google logo the 4 dots start to move but then the tablet turn off and repeat that cycle. Apparently i dont have recovery (appears the android laid down with a red triangle with an exclamation mark) and when i try to enter the hard reset the bootloop happens, the same if i try to reboot, i cant activate usb debugging i can only use the fastboot mode, my pc doesnt reconize my N9.
Thanks
PD: Sorry about my english, im from mexico, but i expect i had explained myself.
emi.guego said:
Hi everyone, well my problem is that i was trying to flash Android 6.0 but i accidentally execute the flash-all.bat file while i was trying to open it in the note block. It was booting normally but it seems that my N9 was encrypted, so it said that the Unencrypted was incorrect so it forced me to hard reset my tablet. i did this but it was taking like 20 min to erase my file (the android appeared and it was over a message that was "Wiping" -it was in spanish borrando-) so i turn it off and now my tablet is on a bootloop, after it appears the Google logo the 4 dots start to move but then the tablet turn off and repeat that cycle. Apparently i dont have recovery (appears the android laid down with a red triangle with an exclamation mark) and when i try to enter the hard reset the bootloop happens, the same if i try to reboot, i cant activate usb debugging i can only use the fastboot mode, my pc doesnt reconize my N9.
Thanks
PD: Sorry about my english, im from mexico, but i expect i had explained myself.
Click to expand...
Click to collapse
I had the same problem... I had to manually flash each image through fastboot starting with the recovery img
Sent from my HTC One M9 using XDA Free mobile app
But how can I do it if I can't enable USB debugging?
Enviado desde mi Moto MAXX mediante Tapatalk
Related
For use on Verizon variant HTC ONE MAX only!!!
S-off users only!!!!
Software version 1.11.605.4
Stock Recovery-
http://www.androidfilehost.com/?fid=23252070760974293
flash via fastboot
fastboot flash recovery recovery.img
Stock Kernel (insecure)-
http://www.androidfilehost.com/?fid=23252070760974294
flash via fastboot
fastboot flash boot boot.img
System Image (must unrar first to get system.img)
http://www.androidfilehost.com/?fid=23252070760974295
flash via fastboot
fastboot flash system system.img
Flashable radio-
download this:
https://www.mediafire.com/?ucj15e2zavewnbq
vzw_max_radio.zip ba7f0302040731949a4db3cb0c9c4e98
double check the md5 matches above.
flash in ruu mode:
-phone in fastboot
-open cmd
-enter:
fastboot devices
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip vzw_max_radio.zip
fastboot reboot-bootloader
if you see a baseband in the bootloader screen now,thats a good sign
fastboot reboot
Credits- Scotty1223 for working his radio magic
Jiggity Janx - afh mirrors
Awesome sauce, thank you :good:
@dottat is it possible to write a script for those for the n00bs that may be the faint of heart type? Like a flash-all deal? I'm good with manually flashing them all individually but for those that aren't that would be dope.. Can you even do that with the .img's for HTC devices?
Murrda said:
@dottat is it possible to write a script for those for the n00bs that may be the faint of heart type? Like a flash-all deal? I'm good with manually flashing them all individually but for those that aren't that would be dope.. Can you even do that with the .img's for HTC devices?
Click to expand...
Click to collapse
dottat worked with the Flashify dev to get it working with the One Max. Recommend everyone use that.
HELP !!!
I tried flashing the system img, but keep on getting this error msg below. Can't do anything else but go into Custom Recovery.
error: cannot load 'system.img': Not enough space
---------- Post added at 09:27 PM ---------- Previous post was at 09:15 PM ----------
mustangmao said:
HELP !!!
I tried flashing the system img, but keep on getting this error msg below. Can't do anything else but go into Custom Recovery.
error: cannot load 'system.img': Not enough space
Click to expand...
Click to collapse
When sending boot image after i use fastboot erase boot commend, it just stuck on sending 'boot' <16384 kb> and nothing happens. Any help suggestion?
...Send boot.img when flashing boot. Send system when sending system. Can't flash system into boot partition
The boot partition is only 16 megs so if you try to flash a 2 gig file into it you'll prolly hang.
Flashing the 2gig system.img to the system partition properly will likely take some time. You have screenshots?
Sent from my HTC6600LVW using Tapatalk 4
That's exactly what i did following your instruction. Here's the steps i did (BTW: I will take screenshots as soon as i am home)
1) Went into TWRP and performed a wipe (Data, cache and system)
2) Connect MAX to PC (Win 7 64bit)
3) Go into Fastboot mode (tested using Fastboot devices and results came back with serial number)
4) Copied System and Boot img into the same folder as Fastboot/ADB
5) Issue commend: fastboot flash boot boot.img ---- Error: 1st it was stuck on sending, nothing happens for like 10 minutes, unplug then tried Run CMD with local admin, got a different error msg, this time it says FAILED (remote: not allowed)
6) Then I tried flash just system.img using fastboot flash system system.img --- got error: cannot load 'system.img': Not enough space
I then went back into TWRP, basically did a complete wipe of everything (lucky TWRP was intact), went back into Fastboot mode and did another erase.
1) Enter Fastboot mode and issued: Fastboot erase boot, recovery and system -- All went fine
2) Then tried flash individual recovery/boot/system into its partition, same error msg as above
I thought i am toast for sure, but upon rebooting, i still have TWRP and Thank God i had a Full Backup stored on my external SD card, I just did a restore and everyone is back to where i left off..
thanks for your quick response
---------- Post added at 12:29 AM ---------- Previous post was at 12:08 AM ----------
mustangmao said:
That's exactly what i did following your instruction. Here's the steps i did (BTW: I will take screenshots as soon as i am home)
1) Went into TWRP and performed a wipe (Data, cache and system)
2) Connect MAX to PC (Win 7 64bit)
3) Go into Fastboot mode (tested using Fastboot devices and results came back with serial number)
4) Copied System and Boot img into the same folder as Fastboot/ADB
5) Issue commend: fastboot flash boot boot.img ---- Error: 1st it was stuck on sending, nothing happens for like 10 minutes, unplug then tried Run CMD with local admin, got a different error msg, this time it says FAILED (remote: not allowed)
6) Then I tried flash just system.img using fastboot flash system system.img --- got error: cannot load 'system.img': Not enough space
I then went back into TWRP, basically did a complete wipe of everything (lucky TWRP was intact), went back into Fastboot mode and did another erase.
1) Enter Fastboot mode and issued: Fastboot erase boot, recovery and system -- All went fine
2) Then tried flash individual recovery/boot/system into its partition, same error msg as above
I thought i am toast for sure, but upon rebooting, i still have TWRP and Thank God i had a Full Backup stored on my external SD card, I just did a restore and everyone is back to where i left off..
thanks for your quick response
Click to expand...
Click to collapse
BTW: Reason I need to flash the Stock Rom is because my One Max has this weird charging problem, where once the phone is turned on, it only charges to 35-37% and it stops, however if I leave it powered off and charge, it charges to 100% all the way. It must be a software issue and since I am using it on AT&T, Verizon CS and retail store doesn't even want to offer at help. So, i am kinda stuck with fixing the issue myself.
mustangmao said:
That's exactly what i did following your instruction. Here's the steps i did (BTW: I will take screenshots as soon as i am home)
1) Went into TWRP and performed a wipe (Data, cache and system)
2) Connect MAX to PC (Win 7 64bit)
3) Go into Fastboot mode (tested using Fastboot devices and results came back with serial number)
4) Copied System and Boot img into the same folder as Fastboot/ADB
5) Issue commend: fastboot flash boot boot.img ---- Error: 1st it was stuck on sending, nothing happens for like 10 minutes, unplug then tried Run CMD with local admin, got a different error msg, this time it says FAILED (remote: not allowed)
6) Then I tried flash just system.img using fastboot flash system system.img --- got error: cannot load 'system.img': Not enough space
I then went back into TWRP, basically did a complete wipe of everything (lucky TWRP was intact), went back into Fastboot mode and did another erase.
1) Enter Fastboot mode and issued: Fastboot erase boot, recovery and system -- All went fine
2) Then tried flash individual recovery/boot/system into its partition, same error msg as above
I thought i am toast for sure, but upon rebooting, i still have TWRP and Thank God i had a Full Backup stored on my external SD card, I just did a restore and everyone is back to where i left off..
thanks for your quick response
---------- Post added at 12:29 AM ---------- Previous post was at 12:08 AM ----------
BTW: Reason I need to flash the Stock Rom is because my One Max has this weird charging problem, where once the phone is turned on, it only charges to 35-37% and it stops, however if I leave it powered off and charge, it charges to 100% all the way. It must be a software issue and since I am using it on AT&T, Verizon CS and retail store doesn't even want to offer at help. So, i am kinda stuck with fixing the issue myself.
Click to expand...
Click to collapse
Are you unlocked? Because remote not allowed word indicates you are not. Can you confirm?
If your kernel is what got hosed you always flash my boot.IMG using the app flashify from the market from a booted rooted rom....assuming you are unlocked. Otherwise you will have create a flashable 0p3img.zip file and flash your kernels from hboot.
Sent from my HTC6600LVW using Tapatalk 4
dottat said:
Are you unlocked? Because remote not allowed word indicates you are not. Can you confirm?
If your kernel is what got hosed you always flash my boot.IMG using the app flashify from the market from a booted rooted rom....assuming you are unlocked. Otherwise you will have create a flashable 0p3img.zip file and flash your kernels from hboot.
Sent from my HTC6600LVW using Tapatalk 4
Click to expand...
Click to collapse
Yes, i am unlocked and S-OFF and rooted.
Tried another PC and using factory HTC cable, still the same error when flashing system.
Now, if the issue is with my OS, all i need to flash is just System.img and nothing else, right?
mustangmao said:
Yes, i am unlocked and S-OFF and rooted.
Tried another PC and using factory HTC cable, still the same error when flashing system.
Now, if the issue is with my OS, all i need to flash is just System.img and nothing else, right?
Click to expand...
Click to collapse
Load flashify (free) from the app store. Copy the boot.IMG to your SD card and flash boot from that app and report back.
Sent from my Nexus 7 using Tapatalk 4
dottat said:
Load flashify (free) from the app store. Copy the boot.IMG to your SD card and flash boot from that app and report back.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Flash boot.img from SDcard, everything went fine, just rebooted the phone, no issues. Now, how do i flash the System.IMG, which is the key to hopfully solve the battery charing issue? thanks
It should be via fastboot...but your fast boot install doesn't seem to like flashing anything to your phone. Do you have any other pcs you can try and can you see if your charging issue was fixed before proceeding ?
Sent from my Nexus 7 using Tapatalk 4
dottat said:
It should be via fastboot...but your fast boot install doesn't seem to like flashing anything to your phone. Do you have any other pcs you can try and can you see if your charging issue was fixed before proceeding ?
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Wow, i am amazed, just flashing the boot.img and my phone starts chargin pass 37% now while the phone is powered on. Maybe i don't need to flash system.img after all. You rocks dude, thanks so much. Keep up the good work !!!
for what its worth,ive never been able to fastboot flash system system.img ive always gotten that space error.
ive just skimmed thru this,but the easiest way7 for you guys to flash this is to just open the radio zip and add the other images to it. then you can use those directions(oem rebootRUU,etc) and flash them all in one shot.
i could work with you guys to dump the relevant images that usually come in an ruu if you want to make up a full(unsigned) ruu.
I also had the charging issue.(wouldn't charge past 37%....Switched charger and the issue is no more.
sent from my humongous VZW HTC ONE MAX
mustangmao said:
Wow, i am amazed, just flashing the boot.img and my phone starts chargin pass 37% now while the phone is powered on. Maybe i don't need to flash system.img after all. You rocks dude, thanks so much. Keep up the good work !!!
Click to expand...
Click to collapse
Sorta figured that would happen...good deal.
Sent from my HTC6600LVW using Tapatalk 4
scotty1223 said:
for what its worth,ive never been able to fastboot flash system system.img ive always gotten that space error.
ive just skimmed thru this,but the easiest way7 for you guys to flash this is to just open the radio zip and add the other images to it. then you can use those directions(oem rebootRUU,etc) and flash them all in one shot.
i could work with you guys to dump the relevant images that usually come in an ruu if you want to make up a full(unsigned) ruu.
Click to expand...
Click to collapse
Lets make that
Sent from my HTC6600LVW using Tapatalk 4
I know someone was working on decrypting the verizon ruu. He said recently he had gotten busy with some other stuff. So itbis out there and somewhat done already. Just didnt want you guys to put a lotbinto it when there may be other avenues.
Jiggity Janx said:
I know someone was working on decrypting the verizon ruu. He said recently he had gotten busy with some other stuff. So itbis out there and somewhat done already. Just didnt want you guys to put a lotbinto it when there may be other avenues.
Click to expand...
Click to collapse
Good to know, thanks for the heads up.
Jiggity Janx said:
I know someone was working on decrypting the verizon ruu. He said recently he had gotten busy with some other stuff. So itbis out there and somewhat done already. Just didnt want you guys to put a lotbinto it when there may be other avenues.
Click to expand...
Click to collapse
any idea where it is? I hadn't seen one but there's an app for decrypting
OK, so I was rolling along just fine...
Got Fastboot up and running, got myself an unlocked bootloader, got myself the latest TWRP image, and no matter WHAT I DO, I can not get TWRP to flash to my device, and it is driving me absolutely INSANE. Below is what i am getting from command prompt. Any help is GREATLY appreciated.
Code:
C:\Users\saltam\Downloads\TWRP>fastboot flash recovery recovery.img
sending 'recovery' (13186 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.000s
I am pulling what little hair I have out over here, and I am no beginner when it comes to this stuff. Please help if you can.
Only a couple of things I can think, which I'm sure you've already done. Have you re-downloaded the image file and you have renamed it recovery.img?
Edit, is your bootloader unlocked?
Sent from my Nexus 5 using XDA Free mobile app
Boot loader is unlocked, tried everything besides a different computer. Tried different cord, different USB port, everything. It's like once I unlocked the boot loader the tablet stopped communicating with fast boot. Anything I try to do hangs until I hit reboot fast boot then it fails. Irritating the hell out of me...
have you tired using the wugs Nexus root toolkit? http://forum.xda-developers.com/nexus-9/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2945451
I was having some trouble TWRP installing as well., and it was able to install TWRP just fine
Close any other running programs, especially Chrome. Then if still not doing it, install CWM Recovery instead, and if you still want TWRP flash it from CWM Recovery.
My N5 won't let me have TWRP, so if you just want the functions of a recovery, try a different one.
blakeslee14 said:
have you tired using the wugs Nexus root toolkit? http://forum.xda-developers.com/nexus-9/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2945451
I was having some trouble TWRP installing as well., and it was able to install TWRP just fine
Click to expand...
Click to collapse
Tried Wug's, and got the same result when I got to it sending the fast boot commands. Prompt just hangs until I select reboot fast boot.
craig.buckie said:
Close any other running programs, especially Chrome. Then if still not doing it, install CWM Recovery instead, and if you still want TWRP flash it from CWM Recovery.
My N5 won't let me have TWRP, so if you just want the functions of a recovery, try a different one.
Click to expand...
Click to collapse
I'm at my end right now, because I want to remove all this dumb Google bloatware so badly. Was thinking about trying to flash stock image, or relock and unlock boot loader again to see if that does anything, but I'm very nervous that those options might not work because of the fact that fast boot commands aren't working. Certainly don't want to end up with a $400 paperweight...
SwoRNLeaDejZ said:
Tried Wug's, and got the same result when I got to it sending the fast boot commands. Prompt just hangs until I select reboot fast boot.
I'm at my end right now, because I want to remove all this dumb Google bloatware so badly. Was thinking about trying to flash stock image, or relock and unlock boot loader again to see if that does anything, but I'm very nervous that those options might not work because of the fact that fast boot commands aren't working. Certainly don't want to end up with a $400 paperweight...
Click to expand...
Click to collapse
I assume you're on 5.0.1. Flash the boot or recovery image from the factory image in fastboot. See if that works. That might rule out a fastboot issue. If it flashed it won't do anything negative to your device
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
I assume you're on 5.0.1. Flash the boot or recovery image from the factory image in fastboot. See if that works. That might rule out a fastboot issue. If it flashed it won't do anything negative to your device
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Going to give this a shot now..
Worth mentioning, I ran an OEM Lock command, and successfully relocked the bootloader, so it appears fastboot is at least partially working. Going to attempt to flash the bootloader in the image from Google, because that is all there is. Just bootloader and image, no recovery image. I will post results here. I don't know why fastboot commands are broken after unlocking bootloader, but there is one thing that seems odd to me:
When I run fastboot devices, it returns the following (has been like this from the beginning):
Code:
C:\Users\saltam\Downloads\TWRP>fastboot devices
???????????? fastboot
Thoughts?
Something's not right. Do you have the newest fastboot?
di11igaf said:
Something's not right. Do you have the newest fastboot?
Click to expand...
Click to collapse
Yes, recently updated it via the minimalist fastboot/adb tool. This is REALLY irritating the hell out of me at this point... Been trying to get recovery on this stupid tablet all damn day...
I am starting to think this is a read/write error.. It is getting the error whenever it tries to write to the tablet... (sending boot.img results in the error every time)... Anyone know of fastboot/adb commands to check/fix read and write errors
**EDIT**
So, much to my chagrin, it appears to just be my computer... Tried on a different laptop, and was able to get it rooted.. For some odd reason though, I don't think TWRP is installing correctly ??
I am going to try and boot into recovery, but every time i try to flash it with fastboot flash recovery recovery.img it says it was successful, but a boot into recovery mode comes up as the dreaded NO COMMAND laying down Android icon. Super frustrating..
**EDIT 2**
So after much trying of different methods, I was able to successfully flash TWRP with Flashify. Not sure why I couldn't do it manually through fastboot but I'm good now. Thanks for all the replies and suggestions. This can be marked as closed or solved. Thanks!
SwoRNLeaDejZ said:
I am starting to think this is a read/write error.. It is getting the error whenever it tries to write to the tablet... (sending boot.img results in the error every time)... Anyone know of fastboot/adb commands to check/fix read and write errors
**EDIT**
So, much to my chagrin, it appears to just be my computer... Tried on a different laptop, and was able to get it rooted.. For some odd reason though, I don't think TWRP is installing correctly ??
I am going to try and boot into recovery, but every time i try to flash it with fastboot flash recovery recovery.img it says it was successful, but a boot into recovery mode comes up as the dreaded NO COMMAND laying down Android icon. Super frustrating..
**EDIT 2**
So after much trying of different methods, I was able to successfully flash TWRP with Flashify. Not sure why I couldn't do it manually through fastboot but I'm good now. Thanks for all the replies and suggestions. This can be marked as closed or solved. Thanks!
Click to expand...
Click to collapse
To your first edit, twrp is probably working correctly. Lollipop forces the stock recovery. There are two files, one in /system and one in /system/bin that force the stock recovery upon boot. You can remove those files or first
fastboot boot twrp.img
Then flash supersu in twrp, then
fastboot flash recovery twrp.img
Sent from my Nexus 9 using XDA Free mobile app
Got the right USB driver
Dirty Unicorns /Uber / Beanstalk Yuga adm.
xtcdk said:
Got the right USB driver
Dirty Unicorns /Uber / Beanstalk Yuga adm.
Click to expand...
Click to collapse
Kind of mystified with your response... Had nothing to do with the USB drivers. Found out afterward that the problem was the security that my company had setup on my laptop (was using my company thinkpad). Switching laptops solved the problem.
Hello,
I just purchased this phone knowing that it has this problem and I am trying to fix it but I do not know much about the original firmware or anything except of the following:
SKU: 6233A, MFG: 2014/05/30, HW: R1.6
I need to restore the Firmware and preferably be able to use the Dock Station (reason I bought it).
I also like to use it with T-Mobile and do not know if these phones are locket to ATT or not.
I am not a developer but have good technical knowledge.
Any advice will be appreciated.
Thank you
Mike
MH928 said:
Hello,
I just purchased this phone knowing that it has this problem and I am trying to fix it but I do not know much about the original firmware or anything except of the following:
SKU: 6233A, MFG: 2014/05/30, HW: R1.6
I need to restore the Firmware and preferably be able to use the Dock Station (reason I bought it).
I also like to use it with T-Mobile and do not know if these phones are locket to ATT or not.
I am not a developer but have good technical knowledge.
Any advice will be appreciated.
Thank you
Mike
Click to expand...
Click to collapse
Hopefully you can enter in to fastboot mode.
Try to reflash this ATT_userdebug rom from TWRP recovery, and then restore this backup.
1. Turn on the fastboot mode(vol up + power), plug in the cable to PC, open CMD, Boot in to twrp(fastboot boot recoveryyouchoose.img) and use "adb push filename.zip /sdcard"
2. install .zip then reboot
3. boot up, then boot back to TWRP recovery, make a backup.
4. boot up, copy the downloaded backup, boot back to recovery
5. restore it.
hope it works
paleszgergo said:
Hopefully you can enter in to fastboot mode.
Try to reflash this ATT_userdebug rom from TWRP recovery, and then restore this backup.
1. Turn on the fastboot mode(vol up + power), plug in the cable to PC, open CMD, Boot in to twrp(fastboot boot recoveryyouchoose.img) and use "adb push filename.zip /sdcard"
2. install .zip then reboot
3. boot up, then boot back to TWRP recovery, make a backup.
4. boot up, copy the downloaded backup, boot back to recovery
5. restore it.
hope it works
Click to expand...
Click to collapse
The second link (to restore) redirects to another Thread but most of the links there do not work, can you send me a direct link to the file?
MH928 said:
The second link (to restore) redirects to another Thread but most of the links there do not work, can you send me a direct link to the file?
Click to expand...
Click to collapse
I think he meant these for the second link.
http://forum.xda-developers.com/showpost.php?p=60403709&postcount=34
Edit: you must use twrp to flash these backups after user debug.
Justatechie said:
I think he meant these for the second link.
http://forum.xda-developers.com/showpost.php?p=60403709&postcount=34
Edit: you must use twrp to flash these backups after user debug.
Click to expand...
Click to collapse
Yeah, thats what i mean!
Please help. the same problem. Invalid boot. TWRP recovery i have already. please help step by step...
(why invalid boot? i flashed new recovery from Quarx to a boot partition )
Sirocco.ukr.lviv said:
Please help. the same problem. Invalid boot. TWRP recovery i have already. please help step by step...
(why invalid boot? i flashed new recovery from Quarx to a boot partition )
Click to expand...
Click to collapse
Is your Bootloader unlocked?
Justatechie said:
Is your Bootloader unlocked?
Click to expand...
Click to collapse
Locked bootloader. Where i can see for sure?
When VolUp+Power i can see this window
I need adb driver.
TWRP that i have on this phone is old one ported from nexus device and it can't see SD card.
Sirocco.ukr.lviv said:
Locked bootloader. Where i can see for sure?
When VolUp+Power i can see this window
I need adb driver.
TWRP that i have on this phone is old one ported from nexus device and it can't see SD card.
Click to expand...
Click to collapse
To find out, you have to put your phone into fastboot.
To do that power down your phone, then hold volume up and power button at the same time. There, the asus logo will pop up like normal and hang on that screen to show that you are in fastboot mode.
Open up command prompt and verify your device is connected, by typing in fastboot devices.
If it shows up good then all you have to do is type in fastboot oem device-info.
If it says device unlocked: true that means your BL is unlocked.
If its not, you have to download crowlock from the cm12 thread and flash it.
It works better with cwm but since you are stuck its worth a shot to flash it under old twrp.
Then check the BL status again, if its good great.
You could restore your device from some backups posted or if you could find a boot.img from the stock image, you could use the new version of twrp to flash the boot image under image flashing.
This is the adb/fastboot driver I use http://forum.xda-developers.com/showthread.php?t=2588979
Justatechie you are only one who help. i appreciate it. god bless you!
i've done it. unlocked already. i watched bootloop so i wiped everything. what rom to install?
del
Nice to hear that.
Well it depends if you want to install one or you want to keep it stock.
For keeping it stock unfortunately you must restore from backups posted.
If its custom well Cm is a good way, just the dock does not work, but it will work hopefully soon when the developer receives it soon.
Justatechie said:
Nice to hear that.
Well it depends if you want to install one or you want to keep it stock.
For keeping it stock unfortunately you must restore from backups posted.
If its custom well Cm is a good way, just the dock does not work, but it will work hopefully soon when the developer receives it soon.
Click to expand...
Click to collapse
My asus padfone x T00D with full wipes identifies like T00N (padfone s) and reboots on first welcome screen on your rom...
please see video:
https://www.youtube.com/watch?v=aMB9Ctvrk0Q
Sirocco.ukr.lviv said:
My asus padfone x T00D with full wipes identifies like T00N (padfone s) and reboots on first welcome screen on your rom...
please see video:
https://www.youtube.com/watch?v=aMB9Ctvrk0Q
Click to expand...
Click to collapse
Dont worry about the asus_toon, it will turn back into padfone x when you are finally able to restore to the at&t factory rom
What is very strange,is that you cannot wipe certain things, I guess It may be due to a tampered bootloader. (something must have tripped it up)
My bootloader is unlocked but not tampered.
But the reason why it says ASUS_T00N is because you installed cm or miui and it changed build prop and the partitions. (all of quarx roms are built from the pfs source but work on the pfx too) its not a big deal don't worry.
Have you tried any other recoveries, perhaps the older version of twrp Here
Try booting them through fastboot using the fastboot boot filename.img (of the recovery file that should be located inside a folder containg fastboot/adb files)
See if they can wipe cache data(no media) and system. Remember, booting from fastboot is just temporary
Then try flashing a rom, doesnt matter what it has to be but it should work after its done. Maybe flash without gapps, it could sometimes cause a random problem and besides you can always install it later.
I never had to use fastboot to wipe cache either because well I could do that in recovery, plus its safer
Hi guys, after 10 hours of trying to get my P760 to life I finally, as a last resort, decided to open this threadh. Heres the deal, my friend gave me his P760 which was stuck at the boot logo, I firstly tried to fix it with LG mobile support tool but it got stuck at 15% after countless tries. Then I tried fixing it with Lg flash tool but it also gave me some errors "omap factory download fail lg p760". After that I couldnt access S/W mode anymore nor did the phone turn on, only black screen. When I connect it to my pc it just makes sounds of new device connected/disconnected. I tried this fastboot method http://forum.xda-developers.com/showthread.php?t=2292828 but couldnt make it work. Is the phone completely dead or is there anything more I can try? Any help is appreciated, thank you very much.
What was done to brick it in the first place?
Sent from my KYOCERA-C6745 using Tapatalk
I am not sure, my friend brought it to me and he didnt know the reason. Anyway I managed to get into fastboot on another computer and i tried to flash x loader and uboot with the bulit in options and i get the following error "FAILED (remote partition doesnt exist). What can I do next? Thank you for the reply.
EDIT I have tried to get the phone in S/W mode using this guide http://forum.xda-developers.com/showpost.php?p=44325657&postcount=4 but I couldnt do it.
I am sure I have to flash something in fastboot so it would be great if someone could point me to exactly what. Thanks again.
EDIT 2 I tried to flash xloader and u boot from post #7 http://forum.xda-developers.com/showthread.php?t=2242444 and it gave me the remote partition error failed again. Is the phone "officially" dead?
My experience with this phone is that it is basically unbrickable, at least software wise, thanks to omap4boot. Fastboot is basically telling you the partition you specified doesn't exist. Check you are using the correct syntax. It should be fastboot flash u-boot u-boot.img and fastboot flash x-loader x-loader.img (I am assuming the files are named u-boot.img and x-loader.img).
Another possibility is that the partition table of the phone somehow got corrupted. In my opinion this is very unlikely, but it could happen if the phone is disconnected while flashing the GTP table with LGFlashTool. Let's hope that's not the case.
Good luck.
@EdwinMoq thanks for the reply. I checked and I was using the correct syntax altough the files were named p1 and p2 both in bin format so I typed fastboot flash u-boot p1.bin and p2.bin respectively. Ive just noticed that they are from ICS and I am not sure what android version was installed prior to the brick. Can you point me where to find the JB files so I can try them if it makes any difference.
Maha23 said:
@EdwinMoq thanks for the reply. I checked and I was using the correct syntax altough the files were named p1 and p2 both in bin format so I typed fastboot flash u-boot p1.bin and p2.bin respectively. Ive just noticed that they are from ICS and I am not sure what android version was installed prior to the brick. Can you point me where to find the JB files so I can try them if it makes any difference.
Click to expand...
Click to collapse
I don't think the u and x boot version makes any difference. The fastboot script here comes with with the files for both p760 and p769. Or you can ask a p760 user with the jb boot to dump them and post it here.
EdwinMoq said:
I don't think the u and x boot version makes any difference. The fastboot script here comes with with the files for both p760 and p769. Or you can ask a p760 user with the jb boot to dump them and post it here.
Click to expand...
Click to collapse
Well using that script was the first thing I did after I couldn access S/W mode and I got the partition error, I tried both ICS and JB. Well it would be great if someone could dump their JB boot so I can try that, if it doesnt work I guess Ill throw the phone away
Maha23 said:
Well using that script was the first thing I did after I couldn access S/W mode and I got the partition error, I tried both ICS and JB. Well it would be great if someone could dump their JB boot so I can try that, if it doesnt work I guess Ill throw the phone away
Click to expand...
Click to collapse
I'm seeing you using lelus method to fastboot...
1) Be sure you are in fastboot whith this command: fastboot devices
2) if the l9 is still in lg logo, just flash a recovery img into boot and recovery partition:
a) fastboot flash boot recovery.img
b) fastboot flash recovery recovery.img3)reboot the device, it must enter in recovery mode by force.
4) once in recovery just flash a custom rom as you wish
Yes i am using lelus method and I see the device when I enter fastboot devices, the phone wont turn so there is no lg logo and I can not enter S/W mode. Where can I find the recovery.img and boot.img ?
EDIT Okay I tried this too http://forum.xda-developers.com/showthread.php?t=2585161 but when I issue the erase command it just gives me the remote partition error again. The chances that this is a hardware issue are pretty big.
Sent from my LG-D855 using XDA-Developers mobile app
A few tricks that might help:
-After a failed attempt to enter D/L mode via the volume key, force hard reset. Then switch on phone for an extra time and perform the hard reset again. This really makes a difference.
-If after unbricking the phone with a stock rom the puny LG recovery dialog resides on screen, perform the stock rom installation for a second time, phone should perform a normal boot then. Otherwise there's trouble with rooting and TWRP installation later.
-Fastboot still does not work for me(all?) in Win10, as it didn't in Win8.1,but did in Win7.
The only method to go on seems to root stock rom with Kango Root or a similar tool, then install Twrp, with Rashr or flashify.
lecorbusier said:
A few tricks that might help:
-After a failed attempt to enter D/L mode via the volume key, force hard reset. Then switch on phone for an extra time and perform the hard reset again. This really makes a difference.
-If after unbricking the phone with a stock rom the puny LG recovery dialog resides on screen, perform the stock rom installation for a second time, phone should perform a normal boot then. Otherwise there's trouble with rooting and TWRP installation later.
-Fastboot still does not work for me(all?) in Win10, as it didn't in Win8.1,but did in Win7.
The only method to go on seems to root stock rom with Kango Root or a similar tool, then install Twrp, with Rashr or flashify.
Click to expand...
Click to collapse
Thanks for the reply. How do I perform the force hard reset? Yes, I couldnt get fastboot to work on win 10, on win 7 it works flawlessly.
Sent from my LG-D855 using XDA-Developers mobile app
Hello,
I have exactly the same problem with my p760, fastboot works so far but remote partition error and the phone stays always completely black.
Is there someone who has a new idea to fix it?
Hey,
I found this: http://massimoronca.it/2016/03/17/fastboot-failed-remote-partition-does-not-exist.html
but i dont really understand it, can someone help me?
Maha23 said:
Yes i am using lelus method and I see the device when I enter fastboot devices, the phone wont turn so there is no lg logo and I can not enter S/W mode. Where can I find the recovery.img and boot.img ?
EDIT Okay I tried this too http://forum.xda-developers.com/showthread.php?t=2585161 but when I issue the erase command it just gives me the remote partition error again. The chances that this is a hardware issue are pretty big.
Sent from my LG-D855 using XDA-Developers mobile app
Click to expand...
Click to collapse
readme again... try to flash a recovery.img into the boot partition
fastboot flash boot recovery.img
and then reboot... this foce the l9 to enter in recovery and then you can fotmat partitions in wipe options
---------- Post added at 08:55 PM ---------- Previous post was at 08:52 PM ----------
Elsewhere you must need a technician with a box like octopus box to recompone ESD partitions of the L9 phone
Hard reset is 10s power.
Such a swap of recovery and kernel could have happened after unbricking the phone, when the key combo for fastboot produces the LG recovery. That's why I flash stock twice, then it's right again & ready to root, install TWRP etc.
Thanks for the help guys, I tried everything possible...I think I did, but the phone just wouldnt unbrick so it is going into parts. Thanks again.
Maha23 said:
Thanks for the help guys, I tried everything possible...I think I did, but the phone just wouldnt unbrick so it is going into parts. Thanks again.
Click to expand...
Click to collapse
you must need a technician with a box like octopus box to recompone ESD partitions of the L9 phone
puntoazul said:
fastboot flash boot recovery.img
Click to expand...
Click to collapse
Srsly?
recovery partition image on boot?
Probably true. That would explain the strange behaviour of the key combos during boot, after unbricking the phone for the first time. The recovery has replaced the kernel, but the phone can still boot. Strange. Fastboot is unavailable, and the key combo for the recovery shows the "dead droid" and performs a factory reset.
Groszexxx said:
Srsly?
recovery partition image on boot?
Click to expand...
Click to collapse
Yes... is an effective method to boot by forced on TWRP or other recovery and then proceed to format all partitions and flash any rom consecutively. After flashing any rom the boot partition is rewrited by the boot.img of the rom.
I did this before on my own L9 for repair and other friends devices. Is totally safe
By the way, I'm not in warn
I was using Corvus OS (Android 10). After updating few apps on play store, one of them was maybe android framework related my phone stopped responding and got black screen errors. (I think a system UI crash). So i tried rebooting, got stuck on boot animation. when i went back to orangefox recovery, the phone was simply not responding to any touch even though i could see the files on my phone (orange fox homescreen). Please help ASAP. Thank You.
If someone is actually listening, i ended up clearing everything, installed new recovery, no luck. and sideloading rom returns with "error closed"
I really need some help guys. Please respond.
Sp_3ctr_3 said:
If someone is actually listening, i ended up clearing everything, installed new recovery, no luck. and sideloading rom returns with "error closed"
I really need some help guys. Please respond.
Click to expand...
Click to collapse
Did you format the data partition?
DarthJabba9 said:
Did you format the data partition?
Click to expand...
Click to collapse
#To format system partition
fastboot format system
#To format boot partition
fastboot format boot
#To format cache partition
fastboot format cache
#To format user data partition
fastboot format userdata
#To format recovery partition
fastboot format recovery
did all of these. thanks for responding almost lost all hopes.
DarthJabba9 said:
Did you format the data partition?
Click to expand...
Click to collapse
i managed to install twrp since i could only file .img of it. while trying to install my os using adb shell twrp sideload, the phone just disconnects when it starts installing vendor files after installing data ones.
Also, the adb shell returns Total Xfer 1.00x
Sp_3ctr_3 said:
i managed to install twrp since i could only file .img of it. while trying to install my os using adb shell twrp sideload, the phone just disconnects when it starts installing vendor files after installing data ones.
Also, the adb shell returns Total Xfer 1.00x
Click to expand...
Click to collapse
Yep, your system is well and truly messed up. Your best bet is to download a fastboot MIUI ROM and flash it with the Mi Flash tool. Just make sure that you don't accidentally lock your boot loader again (hint - after unpacking the fastboot ROM, first delete all .bat and .sh files with "lock" in their names before trying anything with Mi Flash).
https://play.google.com/store/apps/details?id=com.google.android.webview&hl=en_IN
I think this was the app that i update and later caused the crashes.
DarthJabba9 said:
Yep, your system is well and truly messed up. Your best bet is to download a fastboot MIUI ROM and flash it with the Mi Flash tool. Just make sure that you don't accidentally lock your boot loader again (hint - after unpacking the fastboot ROM, first delete all .bat and .sh files with "lock" in their names before trying anything with Mi Flash).
Click to expand...
Click to collapse
Alright, i will try that and respond. thanks for the reply.
DarthJabba9 said:
Yep, your system is well and truly messed up. Your best bet is to download a fastboot MIUI ROM and flash it with the Mi Flash tool. Just make sure that you don't accidentally lock your boot loader again (hint - after unpacking the fastboot ROM, first delete all .bat and .sh files with "lock" in their names before trying anything with Mi Flash).
Click to expand...
Click to collapse
Did this, succesfully flashed with Bootloader intact. Still touch is not responsive, all i can see is a black screen with "This Device is Locked, for security reasons you need to enter the password to verify the device" but i cant select any option since it wont respond to touch.
DarthJabba9 said:
Yep, your system is well and truly messed up. Your best bet is to download a fastboot MIUI ROM and flash it with the Mi Flash tool. Just make sure that you don't accidentally lock your boot loader again (hint - after unpacking the fastboot ROM, first delete all .bat and .sh files with "lock" in their names before trying anything with Mi Flash).
Click to expand...
Click to collapse
Woohoo thank you, my phone is working again t. Although i had to reinstall mi flash tool with bootloader back to off or locked, but atleast now i have a working phone. It seems during login screens sometimes the scree still remains unresponsive, but gets back to normal after 4-5 lock unlock screen routine. I will miss using root and other customization, but i guess it is what it is. Thanks again.
Have a nice day.
Sp_3ctr_3 said:
Woohoo thank you, my phone is working again t. Although i had to reinstall mi flash tool with bootloader back to off or locked, but atleast now i have a working phone. It seems during login screens sometimes the scree still remains unresponsive, but gets back to normal after 4-5 lock unlock screen routine. I will miss using root and other customization, but i guess it is what it is. Thanks again.
Have a nice day.
Click to expand...
Click to collapse
It is good that you have your device back! With regard to the bootloader, you can always go through the unlock procedure again.
PS: updating something from the Play Store should not cause a problem like this. It looks like corruption of the firmware, and/or the persist partition. Flashing a fastboot ROM via Mi Flash (the "flash all" option) should have solved the problem completely. If it didn't, then this might actually be a sign of impending hardware failure, rather than a mere corruption of partitions.
Which version of MIUI did you install?