Hey all,
So I seem to have soft bricked my tablet (Nexus 7 2013 LTE). I can get into fastboot mode (but not into the recovery menu) then I am stuck on the Google logo. Does this mean the device is repairable?
Device manager on Windows shows the tablet as
- an unknown device (no drivers installed / Samsung (Wugfresh) / Google drivers)
- Android bootloader interface (Snoop05's tool)
- Android ADB Interface (PDAnet (Wugfresh)).
On all of them the driver is not correctly installed and I have the exclamation mark showing on device manager. I am unable to access the tablet via fastboot or ADB at this time.
I have tried every permutation I can think of so am turning to the hive mind for advice.
To compound matters I am in Turkey and I don't speak Turkish. I've been in an internet cafe for about 5 hours now and it's 1am (Turkish keyboards have an ı where i should be and you can imagine how many times I have mistyped). I am on a year long cycle tour and the tablet has my music, books, guidebooks and dictionaries on it so I am pretty hacked off. Especially given that I've only just arrived...
I did manage to connect via ADB yesterday but ran out of time as I was borrowing someone's computer and can't replicate the steps. Gah!
I have backups of all my data so essentially I would just like to factory reset. Any help gratefully received!
Thanks,
Don
Well, I found the right combination of drivers (Snoop05's tool then PDANet on Wugfresh) and can now see the device via fastboot so I have unlocked it. However whenever I try and flash boot / system / recovery, etc via fastboot I'm receiving an error 'remote: partition table doesn't exist'. Any ideas, people?
Probably useful to add that the problem was initially caused when I removed the SIM card whilst the unit was switched on. I received a message asking me to reboot and it has been bricked since. Also, I was runing stock unrooted.
Thanks
I have now tried every toolkit I can find but still no joy. I seem to have corrupted my partition table which is preventing me writing anything to the device.
To confirm - I can boot into fastboot mode and can see the device via fastboot using command line and can unlock it using 'fastboot oem unlock'. I have the images to write using 'fastboot flash boot/recovery/system [image location] but nothing will let me write to the device without receiving the error 'FAILED - remote: partition table doesn't exist'.
I have searched everywhere and can't find very much. Is the device recoverable or have I fecked it...? I need to get out of internet cafes and onto my bike...
Cheers in advance
Gulp! 100+ views and no replies...does no-one want to break it to me that my lovely tablet is beyond help! Is the only solution some wizardry using GParted or something? I'm already in way over my head.
I'm only bugging you all as I am running out of time in town and need to head off into the wilds. I have tonight and that's it for at least a week. It would be nice to have some company ie books and music...oh and a Turkish dictionary and translator...poor attempt to drum up sympathy I know.
I'll be honest, I've never seen such an issue as yours but it's worth a try since you got fastboot to do fastboot format of all your partitions and see if it helps to flash factory image. Something like fastboot format system for example.
Sorry I can't be more help
Nexus 7 LTE
Carbon Rom
Faux Kernel
dondelion said:
I have now tried every toolkit I can find but still no joy. I seem to have corrupted my partition table which is preventing me writing anything to the device.
To confirm - I can boot into fastboot mode and can see the device via fastboot using command line and can unlock it using 'fastboot oem unlock'. I have the images to write using 'fastboot flash boot/recovery/system [image location] but nothing will let me write to the device without receiving the error 'FAILED - remote: partition table doesn't exist'.
I have searched everywhere and can't find very much. Is the device recoverable or have I fecked it...? I need to get out of internet cafes and onto my bike...
Cheers in advance
Click to expand...
Click to collapse
Remove Wug's drivers and what ever other old drivers you have and follow this tutorial http://forum.xda-developers.com/showthread.php?t=2381582 make sure your getting for the data and not WiFi only. Get them old drivers out of there first.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Raverbunny said:
I'll be honest, I've never seen such an issue as yours but it's worth a try since you got fastboot to do fastboot format of all your partitions and see if it helps to flash factory image. Something like fastboot format system for example.
Sorry I can't be more help
Nexus 7 LTE
Carbon Rom
Faux Kernel
Click to expand...
Click to collapse
Fastboot format still appears to require an intact partition table as I still receive an error - 'FAILED (command write failed (invalid argument))' but thank for the response.
LinearEquation said:
Remove Wug's drivers and what ever other old drivers you have and follow this tutorial http://forum.xda-developers.com/showthread.php?t=2381582 make sure your getting for the data and not WiFi only. Get them old drivers out of there first.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I tried this but same problem - no partition table so unable write anything to the device, thanks...
don, did you ever solve this?
I am having a similar problem but cannot unlock the device.
i have the same problem ....i just usedf flo-ebb clamours repartition and it wiped out all my partions i can only access fast boot but cant install anything as it says " no such partition "
Is your bootloader unlocked? If so, you should be able to flash the factory image in fastboot.
If not, you should be able to sideload the OTA in recovery.
Related
Model: GT-I9250T
Original Android version 4.04.
Root method: Gained root without having to unlock or overwrite the vanilla boot-loader and used OTA RootKeeper to backup su.
Long story short: My phone recently updated to 4.2.1 OTA. I restored root using OTA RootKeeper without issue. However when I went to restore The LBE Privacy app service, it caused my Nexus to enter a loop the moment it finishes booting and the lock screen appears.
Behavior:
After booting to the lock screen, the screen flashes and goes black then gets back to desktop and starts all over again in a loop. Once it does that about 3 or 4 times, it'll eventually get to a totally black screen except for the Android robot guy lying down with his belly open and an exclamation mark coming out. It'll then sit like that for about a minute and then the phone will reboot from scratch and the whole process repeats.
Apparently i'm not the only one either: url = badappreviews.com/apps/23315
From the linked site it looks like someone fixed it by using clockworkmod. However I don't see how that's possible as there is no way to enable usb debugging or copy any files to the sdcard as you can't boot the phone properly in the first place. I also noticed that I can no longer get into fastboot using the volume up and power button. However I can get into Odin mode.
Any ideas???
Install CWM or TWRP, wipe it clean, mount sdcard from there or adb sideload a ROM.
Sent from my Galaxy Nexus using Tapatalk 2
iLeopard said:
Install CWM or TWRP, wipe it clean, mount sdcard from there or adb sideload a ROM.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
But how do I do that if I can't get usb debugging or get it connected to a computer or fastboot as mentioned?
Edit: nvm, looks like i am able to get into fastboot after all.Now here's hoping I can install it without having usb debugging enabled.
.DCCXVIII said:
But how do I do that if I can't get usb debugging or get it connected to a computer or fastboot as mentioned?
Edit: nvm, looks like i am able to get into fastboot after all.Now here's hoping I can install it without having usb debugging enabled.
Click to expand...
Click to collapse
Just flash the android stock image through adb and go from there. You don't need debugging access when you're in fast boot
Have I helped? Don't forget to make love to that "Thanks" button!
Download stock images and flash em via fastboot, but you will lose everything. Its the freshest start you can get.
Sent from my Nexus Prime
Seriously, do you need to 'enable debugging' to be able to use adb in recovery?? It's a completely different and independent partition.
And fastboot doesn't need any enabling at all.
So, boot to recovery
mounts and storage
mount sd card
open up a DOS box (or terminal if you're on a mac or linux)
<path to adb>/adb shell
...
profit
The ... is where you go and uninstall the app/service, like the example you found mentioned above.
Usually this would be removing a .apk from either /system/app or /data/app
Thanks for all the help, however i am unable to get the adb drivers installed. I tried both Samsung's and Google's and they both fail (Windows doesn't even recongise a driver even after pointing it to: \sdk\extras\google\usb_driver. Anyone got any other sources for a working driver? Win7 64bit.
Edit: Managed to connect it using the pdanet drivers. Then proceeded to try to load CWM using: "fastboot flash recovery *file name*.img", but just got an error: "FAILED (remote: invalid argument)". I noticed that on my fastboot menu, it says lock state: Locked. Is this why it's failing? The boot loader is still locked? Because I tried "fastboot oem unlock" and that didn't work: "FAILED (unknown status code)".
Edit: Looks like my phone just needed a reboot. Because once I did, I was able to use the fastboot oem unlock command with success! However, before I proceed with unlocking the bootloader, can someone please confirm for me that I need to do so in order to install CWM? Many thanks.
Yes, but unless you have a play store gnex, this will probably wipe your phone anyway.
Sent from my brain using telepathy
m.is.for.michael said:
Yes, but unless you have a play store gnex, this will probably wipe your phone anyway.
Sent from my brain using telepathy
Click to expand...
Click to collapse
OK, i've managed to successfully unlock the bootloader, flash CWM and used the "fix permissions" function. I lost all my data/apps etc but I now have a working phone! Many thanks to all that helped!
My Galaxy Nexus reboots a few seconds after starting up. I don't have anything other than stock installed and I've tried following several guides here trying to flash it myself since the built-in recovery mode wipe data/factory reset does nothing.
I did notice something strange which following a guide, when I oem unlock and reboot the fastboot mode it locks itself again like I didn't do anything at all. This was a problem when I was using the Android Toolkit too but I managed to over ride my own fastboot oem unlock commands in between its batch file commands and got to an error "FAIL Exceed Buffer Size"
I believe if I can fix or know what to do with that error I can successfully bring my phone back to factory defaults I just don't know what to do! I tried looking for the error on this forum and it came up with 0 results and google isn't helping much either.
I'd appreciate any help regarding this, even if it means my phone is beyond repair I just want to know!
Thanks guys!
celeadyne said:
My Galaxy Nexus reboots a few seconds after starting up. I don't have anything other than stock installed and I've tried following several guides here trying to flash it myself since the built-in recovery mode wipe data/factory reset does nothing.
I did notice something strange which following a guide, when I oem unlock and reboot the fastboot mode it locks itself again like I didn't do anything at all. This was a problem when I was using the Android Toolkit too but I managed to over ride my own fastboot oem unlock commands in between its batch file commands and got to an error "FAIL Exceed Buffer Size"
I believe if I can fix or know what to do with that error I can successfully bring my phone back to factory defaults I just don't know what to do! I tried looking for the error on this forum and it came up with 0 results and google isn't helping much either.
I'd appreciate any help regarding this, even if it means my phone is beyond repair I just want to know!
Thanks guys!
Click to expand...
Click to collapse
best advice,flash back to stock,root the phone,and use bootunlock on your phone to unlock it,it wont wipe your data,then download a recovery.img and flash it with the flashify app,almost everything done with apps and no data loss.
pattyboi:) said:
best advice,flash back to stock,root the phone,and use bootunlock on your phone to unlock it,it wont wipe your data,then download a recovery.img and flash it with the flashify app,almost everything done with apps and no data loss.
Click to expand...
Click to collapse
I can't flash the phone to stock because of that FAIL error, and I can't root the phone because it reboot loops before I can enable USB debugging in the OS.
celeadyne said:
I can't flash the phone to stock because of that FAIL error, and I can't root the phone because it reboot loops before I can enable USB debugging in the OS.
Click to expand...
Click to collapse
i mean not using toolkit,using actual fasboot. BTW: do you have a custom recovery? if so you could just adb sideload & if you can get the phone into fastboot mode and just flash a recovery then adb sideload after wiping all partitions && did you try using odin to flash back to stock (i dunno if there are odin images available,i apoligize if not)
Earlier today I used the Nexus Root Tool Kit to flash stock and flash the factory image for 5.0.
At erasing User Data it seemed to get stuck, it was there for over 40 minutes. While looking at the device I accidentally knocked the USB cable out and it said failed. Upon rebooting the device I got the Google logo and the bootloader unlocked icon and then the bugdroid with the gear like it's doing an update (THIS: http://scottiestech.info/wp-content/uploads/2013/03/Android_Update_Screen.jpg[1] ). It stayed like this for another 40 minutes. I forced it to shut down and tried to get into the bootloader but holding down vol up+vol down+power for almost 60 seconds did nothing.
I then booted it up normally again to the gear bugdroid and left it like that before I went out for almost 6 hours. When coming home it was the same and still stuck on that.
I rebooted again and held down to boot into the bootloader but again it did not boot in over 60 seconds.
So am I hard bricked and should toss this out with the trash tonight or can this be restored somehow.
Are you able to connect to your device using fastboot?
Assuming you have fastboot installed and the drivers installed, open a command prompt and from the directory where your SDK files are (unless you added the directory to your system PATH), type "fastboot devices" without the quotes. What do you get back? If you get back a serial#, you should be able to flash the individual files manually
(Download the factory image from google's site, and extract the files into a folder, and run the flash-all.bat This will wipe all your data out, and assumes your bootloader is already unlocked)
Edit: follow the instructions here - http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
These are for Nexus 5, but the same steps apply for Nexus 7 as well. Just make sure you download the right factory image for your Nexus 7. Use Method 1
jj14 said:
Are you able to connect to your device using fastboot?
Assuming you have fastboot installed and the drivers installed, open a command prompt and from the directory where your SDK files are (unless you added the directory to your system PATH), type "fastboot devices" without the quotes. What do you get back? If you get back a serial#, you should be able to flash the individual files manually
(Download the factory image from google's site, and extract the files into a folder, and run the flash-all.bat This will wipe all your data out, and assumes your bootloader is already unlocked)
Edit: follow the instructions here - http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
These are for Nexus 5, but the same steps apply for Nexus 7 as well. Just make sure you download the right factory image for your Nexus 7. Use Method 1
Click to expand...
Click to collapse
Well I can get it into fastboot but I'm getting errors when it tries to flash the bootloader or boot.
what's the error message?
jj14 said:
what's the error message?
Click to expand...
Click to collapse
originally there was none, it just said failed and completed. now i'm getting invalid arguments.
I'm still in fastboot mode but literally nothing will flash.
*edit* just tried to use tookit again and
writing 'bootloader'
FAILED <remote: flash write failure>
finished.
Seeing a couple people mention that they fixed errors like this just from using a different usb port or cable. going to try that.
Why didn't you use adb to flash factory image from the get-go? It's the safest way to flash. I would be so mad on your place if device would render useless. But that might be just me since i'm poor. I really hope you manage to fix it.
neo5468 said:
Why didn't you use adb to flash factory image from the get-go? It's the safest way to flash. I would be so mad on your place if device would render useless. But that might be just me since i'm poor. I really hope you manage to fix it.
Click to expand...
Click to collapse
I knew of that way but the Nexus Tool Kit has always been perfect and I've never had any issues with it so I figured I'd just do it that way to make it easier and well, it didn't happen.
I'm hoping because I can get into fastboot that it's not actually bricked yet but if so then oh well i guess.
So I completely bricked my tablet, cant even get my PC to recognize the tablet, and the only screen i have up is the Google and the unlock padlock. and if i try a hard reset, all i get is android on his back and the red triangle. I have decided to buy a used motherboard, I see from ifixit.com that they are easy to repair, will this solve my dilema? I found used mobo's on ebay, made sure to get the correct one, is this the answer to not buying a new tablet?
My nexus 7 lte is in the exact same state(that's why I've posted here instead of starting new thread)...by using nrt to try updating to marshmellow as per site's instructions...wondering if anyone can offer a solution???
(bought at google play almost 2 years ago and they already sent me a free refurb replacement...but I still wanna try getting the old one going before sending it back if possible...worth a try before buying a replacement mobo)
here some details of my situation:
ran this on my nexus 7 2013 lte...failed on the first try...tried again..it wiped everything and then failed on install...now I have bootloader (accessible by volume down and power button simultaneously) only and no functional recovery(get the android with red triangle and asterisk when I select Recovery)...the only Android device listed in Device manager is Android Bootloader Interface.
If I start from fastboot mode:
gives a driver failed to load error from windows" and also, now in Device Manager my Android Device Listed changed from "Android Bootloader Interface" to "Android Composite ADB Interface", as well, there is now a Portable Device listed also but it's the driver that failed to load I guess "MTP USB Device" with a yellow asterisk.
If I run the flash-all.bat in the image download that the NRT got on the first attempt, everything goes fine until I get to "sending system"...this fails with unknown data transfer error...
when I download the latest image from developers google.com and extract it I get just one big file with no extension...shouldn't there be a bunch of files including a flashhall.bat file?
^Yes, inside the main image zip is the bootloader (+ radio in your case) and another zip of the actual partition images.
Run fastboot devices from the bootloader just to be sure it's detected. If not uninstall all traces from your pc and start fresh.
Flash the new bootloader, reboot bootloader, flash the radio, reboot bootloader then flash each .img individually with fastboot. Don't use any toolkits.
You should get the "OKAY" after flashing each image. Is it only system that fails? Do you get the okay with boot and recovery? If system only I don't know.
ronf1011 said:
So I completely bricked my tablet, cant even get my PC to recognize the tablet, and the only screen i have up is the Google and the unlock padlock. and if i try a hard reset, all i get is android on his back and the red triangle. I have decided to buy a used motherboard, I see from ifixit.com that they are easy to repair, will this solve my dilema? I found used mobo's on ebay, made sure to get the correct one, is this the answer to not buying a new tablet?
Click to expand...
Click to collapse
The android with the red triangle with exclamation is what happens with stock recovery, you need to press power, volume up and down quickly all at the same time to get in. Usually takes a few tries. If you can get into recovery you could factory reset. It could be another problem though. You have to describe what you previously did to it if you really wan't help.
rma
Thanks for the reply...was never able to get the system image to load...google play is supposed to reemburse me once they receive my original nexus 7 (already got a pristine refurb from them..updated to marshmellow..will be staying away from NRT with this one...)
Thanks again for the reply and suggestions!
system image can't be written
Exactly the same happened to me. After a successful update to MM with Wugfresh's NRT 2.0.5 (with no root) I tried to root my device with 2.0.6 which was released in the meantime.
But that failed because NRT thinks my bootloader is locked, while in fastboot mode I can see that it is unlocked. With fastboot commands I can relock and re-unlock but for NRT it makes no difference.
It seemed to me that a manual reflash of bootloader (FLO-04.05), kernel, cache, system and data should solve this, but no way. The flashall. bat reports a write error of the system.img. A direct fastboot flash system system.img command leads to FAILED (remote: unknown chunk type).
I couldn't find any information about chunk types. I am afraid that somewhere in the process the partitioning was affected. Is that a possibility and can anything be done to fix this? Or are there other solutions for the chunk type error?
Hey Everyone,
I have a Find 7 (X9076). A while back I updated to the "stable version " of ColorOSi and ever since my usb doesn't charge the phone and vol down key doesn't work. Additionally it is being misread by the computer device manager as a "Samsung Android Device" when it is in boot loader mode.
I suspected it was a software/kernel issue because when I checked the registry I found the original oppo drivers, so I attempted to flash a new kernel to the device and ended up soft bricking it (no image). Now even though it is soft bricked I am still able to get into boot loader mode (no image). Please Help?
I have used Find 7 recovery installer and FASTBOOT (CMD) as well as trying to use ADB and a Find 7 unbricking tool in Windows 7 test mode the last two didn't work/didn't recognize my phone at all. I refuse to abandon my device so what do I do?
Given you have adb access, you could extract the contents of the current (2.x?) color os image, and fastboot flash the partitions manually.
I recently did this and 'recovered' my device.
adb didnt recognize my device -but how do I do that just in case I'm able to get it working?
Midnight247 said:
adb didnt recognize my device -but how do I do that just in case I'm able to get it working?
Click to expand...
Click to collapse
I flashed a kernel once and the phone just died. I fixed it by following the unbrick thread in oppo forum.
ADB, FastBoot and the USB
I don't know if I was clear in my explanation as to how and when my device (FIND7 X9076) is recognized ONLY by the following: my Computer (Windows 7), the Device Manager, Fast-Boot and on the FIND7 Recovery Installer. I have been able to enter fast-boot mode on any version of the ColorOS I flashed, 1.2 - 2.5.1, (stable version) and work within the confines of that mode. However when the USB is connected in anything other mode (recovery-main OS) it ceases functionality (sending information to comp for recognition, charging, etc.). Also the charger doesn't work and nor does the notification light. Now I may be wrong, but for these reasons I believe the problem is likely software related. I am open to any opinions and advice.
-Thank You Everyone
tropical cactus said:
I flashed a kernel once and the phone just died. I fixed it by following the unbrick thread in oppo forum.
Click to expand...
Click to collapse
If this http://community.oppo.com/en/forum.php?mod=viewthread&tid=23067&extra= is the guide you are referring to I have downloaded the tool but I cannot seem to get it to recognize my device. I went into test mode downloaded and installed all of the drivers but my FIND7 still doesn't show. Have you had this problem?? What should I do??
Midnight247 said:
If this http://community.oppo.com/en/forum.php?mod=viewthread&tid=23067&extra= is the guide you are referring to I have downloaded the tool but I cannot seem to get it to recognize my device. I went into test mode downloaded and installed all of the drivers but my FIND7 still doesn't show. Have you had this problem?? What should I do??
Click to expand...
Click to collapse
Try the guide by cpthero on pg 28. It worked for me but didn't for the last person who tried it. You have to keep trying. For me, installing drivers was the hard part. After that, it just sailed through. Good luck.
tropical cactus said:
Try the guide by cpthero on pg 28. It worked for me but didn't for the last person who tried it. You have to keep trying. For me, installing drivers was the hard part. After that, it just sailed through. Good luck.
Click to expand...
Click to collapse
Okay, I will. To be honest that is one of the struggles I have been having (drivers installing). I am about to try erasing the false drivers that keep popping up ("Samsung Android Device") from my windows registry. Did you go this far? What did you do to resolve the problem? Thank you for your feedback, I will keep everyone posted.
Midnight247 said:
Okay, I will. To be honest that is one of the struggles I have been having (drivers installing). I am about to try erasing the false drivers that keep popping up ("Samsung Android Device") from my windows registry. Did you go this far? What did you do to resolve the problem? Thank you for your feedback, I will keep everyone posted.
Click to expand...
Click to collapse
Step 7-9 is crucial. If not done, the rest of the process cannot be carried out. Remove battery as well.
tropical cactus said:
Step 7-9 is crucial. If not done, the rest of the process cannot be carried out. Remove battery as well.
Click to expand...
Click to collapse
hmm okay, i see I will keep you posted
**IMPORTANT UPDATE**
***MAKE OPPO FIND 7 OPERABLE****
following commands in fastboot mode:
fastboot flash boot boot.img
fastboot flash userdata userdata.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
By using the afformentioned commands in fastboot (of course) I was able to restore my phone to almost full functionality. It operates noramally and I fixed the notication light, But I say almost because I cannot charge my phone or have it recognized by my computer through any charger or usb connection when it is on normally or in recovery mode so if any one is familiar with this problem please respond or simply voice ideas.
If you got enough functionality to use it, is it on ColorOS? If so, can it be updated? If you have stock recovery you could flash it with AOSP or Spectrum, get full function back then work toward whichever ROM you really want.
RobboW said:
If you got enough functionality to use it, is it on ColorOS? If so, can it be updated? If you have stock recovery you could flash it with AOSP or Spectrum, get full function back then work toward whichever ROM you really want.
Click to expand...
Click to collapse
I do, have full functionality : ) everything but the USB is performing properly, but to be honest I dont know what AOSP is.....also this will repair functionality to the USB?