*URGENT* Tablet wont boot and is bricked - Shield Tablet Q&A, Help & Troubleshooting

Hello my Nvidia Shield Tablet (original WIFI) is dead i think
I can get into fastboot and TWRP recovery.
TWRP shows Internal memory as 0mb and is unable to mount anything
I also tried flashing stock images but no luck as it keeps failing and tablet wont boot
Any solution? please help:fingers-crossed:

what did you do to get it to this state? try format data and wipe data in twrp. might take a few tries. could also try flashing stock in twrp rather then fastboot. I've seen similar on my phone (involves encryption error) but never on my shield.
Sent from my SAMSUNG-SM-N900A using Tapatalk

lafester said:
what did you do to get it to this state? try format data and wipe data in twrp. might take a few tries. could also try flashing stock in twrp rather then fastboot. I've seen similar on my phone (involves encryption error) but never on my shield.
Sent from my SAMSUNG-SM-N900A using Tapatalk
Click to expand...
Click to collapse
Hi this happened after i flashed 5.1 blob from Optimized Rom thread

Try reflashing OTA 5.2 blob as the blob is not just the bootloader but also the GPT partition setup too
Sent from my pa_osprey using Tapatalk

hacktrix2006 said:
Try reflashing OTA 5.2 blob as the blob is not just the bootloader but also the GPT partition setup too
Sent from my pa_osprey using Tapatalk
Click to expand...
Click to collapse
Hello man thanks for the suggestion can you please guide me through this i am not sure about the GPT partition setup?
I just dont want to go wrong thanks

Right using the following commands for flashing the device.
Code:
fastboot flash staging blob
fastboot erase boot
fastboot flash boot boot.img
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot format system
fastboot flash system system.img
fastboot format userdata
fastboot format cache
This is how i flash mine when returning to stock.

hacktrix2006 said:
Right using the following commands for flashing the device.
Code:
fastboot flash staging blob
fastboot erase boot
fastboot flash boot boot.img
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot format system
fastboot flash system system.img
fastboot format userdata
fastboot format cache
This is how i flash mine when returning to stock.
Click to expand...
Click to collapse
Ok i will try this again and update you

Dalbin Reji said:
Ok i will try this again and update you
Click to expand...
Click to collapse
Ok so i tried flashing this in an unconventional way by rebooting fastboot everytime it failed and then it worked after
but still after i press continue, it says booting failed...
Whats wrong?

Which shield do you have? Original or K1
Sent from my pa_osprey using Tapatalk

Dalbin Reji said:
Ok i will try this again and update you
Click to expand...
Click to collapse
hacktrix2006 said:
Which shield do you have? Original or K1
Sent from my pa_osprey using Tapatalk
Click to expand...
Click to collapse
I have the original WIFI

Make sure your using factory images for that device and not the K1 version
Sent from my pa_osprey using Tapatalk

hacktrix2006 said:
Make sure your using factory images for that device and not the K1 version
Sent from my pa_osprey using Tapatalk
Click to expand...
Click to collapse
Nope man i used the Factory images for Wifi version im sure

Dalbin Reji said:
Nope man i used the Factory images for Wifi version im sure
Click to expand...
Click to collapse
https://developer.nvidia.com/gameworksdownload#?search=Shield Tablet Wifi
Did you use that one?

hacktrix2006 said:
https://developer.nvidia.com/gameworksdownload#?search=Shield Tablet Wifi
Did you use that one?
Click to expand...
Click to collapse
Yep that one exactly, this all happened after i flashed 5.0 blob from an optimized custom rom thread i believe ?

Looks like you have corrupted the boot-loader then hence the issue you have, the chances of recovering from that is very slim. Best to speak to nvidia see if they can help.

hacktrix2006 said:
Looks like you have corrupted the boot-loader then hence the issue you have, the chances of recovering from that is very slim. Best to speak to nvidia see if they can help.
Click to expand...
Click to collapse
Is there no way i can fix it? Probably not then aw

Only Nvidia will be able to fix boot loader issues as they have the magic key for lower level access.
Sent from my SHIELD Tablet K1 using Tapatalk

Maybe you have bricked internal memory eMMC chip

Dalbin Reji said:
I can get into fastboot and TWRP recovery.
TWRP shows Internal memory as 0mb and is unable to mount anything
I also tried flashing stock images but no luck as it keeps failing and tablet wont boot
Click to expand...
Click to collapse
Internal memory as 0mb, and failure to mount anything, often are signs that the internal storage has been corrupted.
Try going to TWRP Wipe section, and tap the button to "Format data". Obviously, you will lose your data. But your data is probably beyond that point, anyway.
Formatting the storage, will often fix corruption issues.

redpoint73 said:
Internal memory as 0mb, and failure to mount anything, often are signs that the internal storage has been corrupted.
Try going to TWRP Wipe section, and tap the button to "Format data". Obviously, you will lose your data. But your data is probably beyond that point, anyway.
Formatting the storage, will often fix corruption issues.
Click to expand...
Click to collapse
Sorry man but when i try @format data it gaves me the same error ''unable to mount.... storage'' etc
Any other method to fix corrupted bootloader?

Related

[Q] AT&T HTC One X Bricked and need advice

Hi,
I have an AT&T HTC One X with no OS. I wiped it when I was trying to flash a custom ROM.
I only have access to bootloader and TWRP. Fastboot is working fine but TWRP is not. It does
mount properly, and adb sideload fails as well. I am using a Windows 7 PC and used a USB 2.0 port.
I installed some HTC Drivers from here:
http://forum.xda-developers.com/showthread.php?t=2217396
but it still says "device drivers failed to install" when I boot into recovery.
When I try to mount, it does not let me mount the sdcard. I see an E: drive on my
PC but it is inaccessible.
I have S-On, my bootloader is unlocked, and I have hboot version 2.14 if that info helps.
Does anybody have any suggestions as to what I can try next?
First thing you need to do is clear your post up a bit. You said you have access to TWRP but it isn't working, can you elaborate on that please?
You also said that it does mount, but then you said later it doesn't mount, which is it?
Have you performed a factory reset from the bootloader at any point?
Exactly which ROM(s) did you try to install? I need the exact filename(s) please.
Did you remember to flash the boot.img with fastboot after flashing the ROM?
Do you have a TWRP backup on your phone?
Please answer all questions with as much relevant detail as possible, that'll aid me to help you properly.
Sent from my Evita
I helped him over teamviewer so I can clarify the situation. He can't mount in TWRP, it must of been a typo. It seems he cleared everything when he was trying to wipe to flash a rom. I believe it was ViperXL. He has no backup and sideload does not work as well. Hopefully that will clear things up a little bit more. I installed some newer HTC Drivers since the ones he had were old. The only thing that works seems to be fastboot at this point.
Sent from my HTC One X using Tapatalk
timmaaa said:
First thing you need to do is clear your post up a bit. You said you have access to TWRP but it isn't working, can you elaborate on that please?
You also said that it does mount, but then you said later it doesn't mount, which is it?
Have you performed a factory reset from the bootloader at any point?
Exactly which ROM(s) did you try to install? I need the exact filename(s) please.
Did you remember to flash the boot.img with fastboot after flashing the ROM?
Do you have a TWRP backup on your phone?
Please answer all questions with as much relevant detail as possible, that'll aid me to help you properly.
Sent from my Evita
Click to expand...
Click to collapse
Sorry it was a Typo, I was not able to mount at all. The error said "unable to mount /sdcard"
Yes I have tried performing a factory reset from bootloader but the phone restarts and comes back to TWRP and then same thing.
I tried installing the ViperXL ROM but was not successful.
I was not able to flash the ROM and I tried to fix that but meanwhile looks like I wiped all what I had on my Phone, so no but I did try to flash a new boot.img after and it didnt work.
I dont think I have any TWRP backup on my phone, even though I tried flashing new TWRP but all failed.
Ok first thing, don't ever perform a factory reset from the bootloader because it corrupts your sd card. That's why you're experiencing problems now. You need to wipe the sd card/internal storage using TWRP 2.6 to make it usable again. If you don't currently have TWRP 2.6 installed you'll need to do that. Download it from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you should be able to mount your sd card using TWRP and copy a ROM across to flash.
Sent from my Evita
timmaaa said:
Ok first thing, don't ever perform a factory reset from the bootloader because it corrupts your sd card. That's why you're experiencing problems now. You need to wipe the sd card/internal storage using TWRP 2.6 to make it usable again. If you don't currently have TWRP 2.6 installed you'll need to do that. Download it from . Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you should be able to mount your sd card using TWRP and copy a ROM across to flash.
Sent from my Evita
Click to expand...
Click to collapse
So I followed all the above steps as noted; I had TWRP 2.6.3.0 earlier, I flashed the new TWRP 2.6.0.0 from the link you provided.All
successfully done.
-------------------------------------------------------------------------------------------------------
C:\Fastboot>fastboot devices
HT29WW300913 fastboot
C:\Fastboot>fastboot flash recovery "openrecovery-twrp-2.6
.0.0-evita.img"
sending 'recovery' (8000 KB)... OKAY [ 1.530s]
writing 'recovery'... OKAY [ 1.900s]
finished. total time: 3.430s
C:\Fastboot>fastboot erase cache
erasing 'cache'... OKAY [ 0.120s]
finished. total time: 0.120s
C:\Fastboot>fastboot reboot-bootloader
rebooting into bootloader... OKAY [ 0.070s]
finished. total time: 0.070s
---------------------------------------------------------------------------------------------------------
I rebooted into recovery, still came up as TWRP 2.6.3.0, then I went to TWRP reboot and chose Recovery, phone rebooted into TWRP 2.6.0.0
Tried mounting (could not select /sd card and /cache(expected as we erased it)) and ADB sideload, got the same errors as before. Unable to mount /sdcard.
Rebooted again and it displayed TWRP 2.6.3.0
Did you wipe the sd card/internal storage like I said before trying to mount it?
Sent from my Evita
timmaaa said:
Did you wipe the sd card/internal storage like I said before trying to mount it?
Sent from my Evita
Click to expand...
Click to collapse
Yes I did
And which recovery is currently installed?
Sent from my Evita
timmaaa said:
And which recovery is currently installed?
Sent from my Evita
Click to expand...
Click to collapse
Its 2.6.3.0, but in recovery when I go into option TWRP reboot and chose Recovery button, phone reboots into TWRP 2.6.0.0 and when I reboot it again, its 2.6.3.0
That's really screwy. I think you should try installing recovery again. What happens when you boot the phone normally?
Sent from my Evita
timmaaa said:
That's really screwy. I think you should try installing recovery again. What happens when you boot the phone normally?
Sent from my Evita
Click to expand...
Click to collapse
Ok good news, something happened, I tried all the steps again carefully and now I see TWRP 2.6.0.0 on boot and I am able to mount the sdcard and my computer now recognises the phone and I can manually copy files on to it.
Now in order to not mess it up anymore, should I just copy ViperXL ROM or should I use ADB sideload?
tapukakababa said:
Ok good news, something happened, I tried all the steps again carefully and now I see TWRP 2.6.0.0 on boot and I am able to mount the sdcard and my computer now recognises the phone and I can manually copy files on to it.
Now in order to not mess it up anymore, should I just copy ViperXL ROM or should I use ADB sideload?
Click to expand...
Click to collapse
Either one should be fine. If you have S-ON and the phone gets stuck on the HTC screen, you have to flash the boot.img. here's how to do it.
1. On your PC in the ViperXL.zip, take out the boot.img and put it in the directory where you have the adb and fastboot files.
2. Boot into fastboot.
3.Open cmd. Change the directory to the folder where you have those files.
4.type "fastboot flash boot boot.img"
5. Reboot the phone.
The phone should boot.
Sent from my One Xl using Tapatalk
Definitely install through TWRP. You shouldn't need to flash a boot.img because Viper uses an aroma installer which does that for you. But, if for some reason it doesn't work just flash the boot.img via fastboot.
Sent from my Evita
timmaaa said:
Definitely install through TWRP. You shouldn't need to flash a boot.img because Viper uses an aroma installer which does that for you. But, if for some reason it doesn't work just flash the boot.img via fastboot.
Sent from my Evita
Click to expand...
Click to collapse
So I flashed the boot image, then copied ViperXL and installed it through TWRP, it failed.
Exactly which error is it giving you? Did you check the md5 of the downloaded file? Are you still on TWRP 2.6?
Sent from my Evita
timmaaa said:
Exactly which error is it giving you? Did you check the md5 of the downloaded file? Are you still on TWRP 2.6?
Sent from my Evita
Click to expand...
Click to collapse
No I did not check the MD5, yes I'm on TWRP 2.6.0.0 and the errors it gives are as follows:
unable to mount '/cache'
unable to open zip
Error flashing zip
Always check the md5. It's possibly corrupt.
Sent from my Evita
timmaaa said:
Always check the md5. It's possibly corrupt.
Sent from my Evita
Click to expand...
Click to collapse
Yup redownloaded the file, checked/compared MD5, copied it back to the phone, removed the previous bad copy, flashed ROM successfully..., as per the message but system reboots to recovery.. is that expected?
And I still see both the TWRP's 2.6.3.0 and 2.6.0.0 the phone needs couple reboots in order to get to TWRP 2.6.0.0 but automatic reboot is in TWRP 2.6.3.0 whats the deal here?
I have no idea why your recovery is acting like that. Hopefully someone else can chime in on that.
Sent from my Evita

[Q] TWRP issue: E:Unable to mount storage.

Help. I have the this error when I start TWRP
Code:
E:Unable to mount storage.
This stop me from doing backup in TWRP..
I have tried to re-flash TWRP. I have also tried flash the recovery.img from Google, and then flash TWRP. The problem still there.
I even try to nearly did a factory the full factory image by doing
Code:
fastboot flash bootloader bootloader-hammerhead-HHZ11d.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-hammerhead-m8974a-1.0.25.0.23.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase cache
fastboot flash cache cache.img
and then restart phone,. booth into phone, and reboot to recovery and flash TWRP...
Are there anything else that I can do? Please help...
Are you using twrp 2.6.3.4? Go into wipe and then format data. Backup first
jd1639 said:
Are you using twrp 2.6.3.4? Go into wipe and then format data. Backup first
Click to expand...
Click to collapse
He's not able to backup. That's the point of his problem. Still trying wiping dalvik and cache first. Then try data. If that don't work trying flashing cwm or Philz's touch recovery.
I tried to wiping dalvik and cache... the problem remains.
I then tried to wipe data but preserve /data/media, which is the default action. The problem remains...
I really don't want to reset my phone to factory state with internal memory completely wiped... any help, please?
leoncheong said:
I tried to wiping dalvik and cache... the problem remains.
I then tried to wipe data but preserve /data/media, which is the default action. The problem remains...
I really don't want to reset my phone to factory state with internal memory completely wiped... any help, please?
Click to expand...
Click to collapse
Don't think you have a choice if you want the phone to work. You're going to have to format the data.
Sound like you missed a reboot before installing custom recovery after unlocking boot.
WR
Sent from my Nexus 5
I solve it flashing to stock rom and re installing the recovery.. It is the only way.. I had the same problem
Inviato dal mio Nexus 7 utilizzando Tapatalk
Thanks for all your suggestions! I took the pain to wipe the phone.
jd1639 said:
Don't think you have a choice if you want the phone to work. You're going to have to format the data.
Click to expand...
Click to collapse
I wanna format my N5, leave it really clean, coz it has the same problem about not mounting storage. But i wanna do it by commands. Can u tell me how can I do that? By adb or fastboot?
tinaag said:
I wanna format my N5, leave it really clean, coz it has the same problem about not mounting storage. But i wanna do it by commands. Can u tell me how can I do that? By adb or fastboot?
Click to expand...
Click to collapse
I'm not sure but you could try adb shell wipe data. Any reason you don't want to do it through twrp?
Sent from my [device_name] using XDA-Developers Legacy app

Can't get past Google Screen

I just restored from the official google 4.4.2 images and my phone cant get past the Google screen. Please help!
bobyum said:
I just restored from the official google 4.4.2 images and my phone cant get past the Google screen. Please help!
Click to expand...
Click to collapse
You flashed the factory images?
bobyum said:
I just restored from the official google 4.4.2 images and my phone cant get past the Google screen. Please help!
Click to expand...
Click to collapse
Do a data factory reset and wipe the cache both in recovery and reboot bro.
gee2012 said:
Do a data factory reset and wipe the cache both in recovery and reboot bro.
Click to expand...
Click to collapse
Thinking the same thing. But.. I can admit getting in a hurry and flashing the wrong image! :laugh:
I made sure that I was using the right image and it still wont go past the Google screen. Any other ideas?
edit: okay the phone can't even write the recovery to the phone through fastboot! Any other thoughts?
bobyum said:
I made sure that I was using the right image and it still wont go past the Google screen. Any other ideas?
Click to expand...
Click to collapse
Long press the power button force it to reboot. As soon as the screen goes black hold down the volume down button. That will boot you into the bootloader, from there you can get to recovery. Factory reset, wipe cache.
You flashed stock recovery?
If you have stock recovery go to the bootloader like I said earlier. Choose recovery. Then you will see android laying down. Press volume up and power button at the same time. Do a factory reset.
bobyum said:
I made sure that I was using the right image and it still wont go past the Google screen. Any other ideas?
edit: okay the phone can't even write the recovery to the phone through fastboot! Any other thoughts?
Click to expand...
Click to collapse
If you flashed the whole image inclusing userdata.img it should boot usualy, never xperienced it did not personaly. So besides a wipe have no idea bro, you might try to reflash the rom again. Are you using a Toolkit?
gee2012 said:
If you flashed the whole image inclusing userdata.img it should boot usualy, never xperienced it did not personaly. So besides a wipe have no idea bro, you might try to reflash the rom again. Are you using a Toolkit?
Click to expand...
Click to collapse
I did this with the flashh-all.bat provided by the official image. I can't even do that anymore because it just gets stuck when writing the bootloader. Totally out of ideas right now. Is there any way I can reformat the partition through fastboot? Would that help?
bobyum said:
I did this with the flashh-all.bat provided by the official image. I can't even do that anymore because it just gets stuck when writing the bootloader. Totally out of ideas right now. Is there any way I can reformat the partition through fastboot? Would that help?
Click to expand...
Click to collapse
Try this:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
After that flash the rom again with flash.all.batt
maybe flash each part individually (not using flashall)
Sent from my Nexus 5 using Tapatalk
gee2012 said:
Try this:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
After that flash the rom again with flash.all.batt
Click to expand...
Click to collapse
Unfortunately, it didnt help Still stuck at writing bootloader...
beaver2233 said:
maybe flash each part individually (not using flashall)
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yup, that might work better maybe
hmm so in which order should i flash them in?
edit: I honestly think the flash storage failed. Ill just apply for RMA then. Do you guys know if I bought my phone in early December, will I still be eligible?
bobyum said:
hmm so in which order should i flash them in?
edit: I honestly think the flash storage failed. Ill just apply for RMA then. Do you guys know if I bought my phone in early December, will I still be eligible?
Click to expand...
Click to collapse
How to flash a factory image. Erasing everything in fastboot should have done the trick. Erase everything then do method 2. You have to reboot the bootloader after flashing the bootloader and again after flashing the radio. One year to RMA. .
---------- Post added at 02:14 AM ---------- Previous post was at 01:57 AM ----------
These are the commands I would use. The name of the images for the bootloader and radio are for 4.4.2.
fastboot flash bootloader bootloader-hammerhead-hhz11k.img
fastboot reboot-bootloader
fastboot flash radio radio-hammerhead-m8974a-1.0.25.0.23.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format cache
fastboot reboot
Thanks all for the help! Will try it tomorrow. Hopefully it works
wantabe said:
How to flash a factory image. Erasing everything in fastboot should have done the trick. Erase everything then do method 2. You have to reboot the bootloader after flashing the bootloader and again after flashing the radio. One year to RMA. .
---------- Post added at 02:14 AM ---------- Previous post was at 01:57 AM ----------
These are the commands I would use. The name of the images for the bootloader and radio are for 4.4.2.
fastboot flash bootloader bootloader-hammerhead-hhz11k.img
fastboot reboot-bootloader
fastboot flash radio radio-hammerhead-m8974a-1.0.25.0.23.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format cache
fastboot reboot
Click to expand...
Click to collapse
I'd go one better and look to do a COMPLETE reflash - userdata and all! I'd also rename bootloader-hammerhead-hhz11k.img to bootloader.img and radio-hammerhead-m8974a-1.0.25.0.23.img to radio.img as it means there's less to get wrong! SO, to recap:
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot-bootloader
fastboot flash userdata userdata.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot reboot-bootloader
fastboot format cache
I'd then boot into the stock recovery and perform a factory reset to make sure everything is in order and then reboot. I've done this exact method a number of times on my Nexus 5 and it works every time
EddyOS said:
I'd go one better and rename bootloader-hammerhead-hhz11k.img and radio-hammerhead-m8974a-1.0.25.0.23.img to just bootloader.img and radio.img to make it easier - less to type out and get wrong!
Click to expand...
Click to collapse
I usually do the same thing too but I left the names as a hint to verify that he had the correct images.
I almost never flash userdata and recovery unless I'm selling a device. I've also never rebooted the bootloader between every image Except after the bootloader and radio images but I agree that your method is covering all the bases!
wantabe said:
I usually do the same thing too but I left the names as a hint to verify that he had the correct images.
I almost never flash userdata and recovery unless I'm selling a device. I've also never rebooted the bootloader between every image Except after the bootloader and radio images but I agree that your method is covering all the bases!
Click to expand...
Click to collapse
As I hardly have any data to backup bar some custom ring tones I always reflash the userdata partition to be thorough. As for the reboots, I've just done it from habit, again just to be thorough. If it still doesn't work after that then it's goosed!
Try using the backup bootloader. Press and hold both volume buttons with the power button. That will take you into the backup bootloader.
Thanks to everyone for helping but I could not even get past writing the bootloader to the phone. I honestly think the flash storage and failed so will be RMAing. Hopefully they will accept it...

[Q] recovery/bootloader issues

after i got my tf700 tablet i unlocked the bootloader and put cwm and cm11 on it, without any problems.
then i tried the same thing on my brothers tf300 i accidentally bricked it, after we bought another one i used the nvflash bricksafe setup on my tf700 so the same thing would not happen to me. then i changed from cwm to philz. later i tried to change the wallpaper in philz and my device froze, so i rebooted and found myself bricked. so i used apx to recover. i got android functionality back but now i have some issues.
1. i cant access recovery, selecting the rck command results in an error: unrecoverable bootloader error (0x00000000)
2. i cant make fastboot flash commands work to reflash a recovery, because the tablet freezes after i hit enter
i have used the "fastboot erase recovery" command too, which seemed to work...
recovery mode usability needs to be restored and possibly a fresh install of the bootloader too.
any help putting it back together either through apx recovery or the android system would be much appriciated!
Did you try to flash the stock blob? Sounds to me like a case for buster99's method:
http://forum.xda-developers.com/showthread.php?t=2179759&page=2
berndblb said:
Did you try to flash the stock blob? Sounds to me like a case for buster99's method:
http://forum.xda-developers.com/showthread.php?t=2179759&page=2
Click to expand...
Click to collapse
Buster99 said:
Reset your device with a paperclip/needle (about 2 cm down of your sdcard slot) and hold vol-down to enter fastboot
(the folowing i did at least 10 times already but didn't erase misc)
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system c:\adb\TF300t\blob (this is my path - your's may vary depending where you stored your blob) ((also this was the first time i saw the loading bar while flashing)*
fastboot -i 0x0B05 reboot
Click to expand...
Click to collapse
thanks for the instructions but i think i will leave this as a last resort as i would rather not have to redo everything i have already done to my device, i hate starting over
A nandroid would have done the trick
Sometimes you have to learn the hard way...
I'm talking about myself: made a nandroid of my CROMi-X installation before flashing CROMBi-KK and then formatted data - without copying the nandroid to microSD - DOH!
Sent from my K00C using Tapatalk
berndblb said:
A nandroid would have done the trick
Sometimes you have to learn the hard way...
I'm talking about myself: made a nandroid of my CROMi-X installation before flashing CROMBi-KK and then formatted data - without copying the nandroid to microSD - DOH!
Sent from my K00C using Tapatalk
Click to expand...
Click to collapse
i have a nandroid, on an external source too,
but if you cant get into recovery there is no way to use (or at lease not one that i know)
kirbyonwarpstar said:
i have a nandroid, on an external source too,
but if you cant get into recovery there is no way to use (or at lease not one that i know)
Click to expand...
Click to collapse
In that case, it's easy:
Flash system blob
Flash custom recovery
Restore nandroid
Sent from my K00C using Tapatalk

[Q] Partition Problem on my Nexus 5 (32GB before, 16GB after)

Hello sorry for my bad English I speak Spanish.
I have a Nexus 5 32 GB but now it is 16GB ...
Last month I updated my smartphone to Android 5.1.0 (manually) from bootloader:
fastboot flash bootloader bootloader-hammerhead-hhz12f.img
fastboot reboot-bootloader
fastboot flash radio radio-hammerhead-m8974a-2.0.50.2.25.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot-bootloader
fastboot flash userdata userdata.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot erase cache
fastboot flash cache cache.img
fastboot reboot
When I tried to copy my music I received the "Insufficient memory storage" message :crying:. I checked the Storage menu and it says that my smartphone has only 16GB now . I don't understand what happened because I always update my smartphone from bootloader.
Do a factory reset in the stock recovery and clear cache. This is a common problem. Back up first
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Do a factory reset in the stock recovery and clear cache. This is a common problem. Back up first
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
I forgot tell you but I tried flashing Android 4.4 and other official ROMs but I still have the same problem.
hectorkrrillo said:
I forgot tell you but I tried flashing Android 4.4 and other official ROMs but I still have the same problem.
Click to expand...
Click to collapse
That is why you have to do a factery reset in stock recovery.
Problem
I have some problem :/
pipo406 said:
I have some problem :/
Click to expand...
Click to collapse
Do a factory reset in stock recovery
If factory reset does not work (didn't for me for some reason), install TWRP recovery, go to Wipe and choose Format Data. This worked for me. Of course all your data will be lost, but if you backed up, no harm done.
eross said:
If factory reset does not work (didn't for me for some reason), install TWRP recovery, go to Wipe and choose Format Data. This worked for me. Of course all your data will be lost, but if you backed up, no harm done.
Click to expand...
Click to collapse
Ohhh!! Thanks! My phone has 32GB again! :good::good::good:.... I had root on my Nexus 5 and TWRP recovery, I did just "Format Data" from TWRP and wala! 32GB is back... I didn't try to apply factory reset from ROM because I have root.
hectorkrrillo said:
Ohhh!! Thanks! My phone has 32GB again! :good::good::good:.... I had root on my Nexus 5 and TWRP recovery, I did just "Format Data" from TWRP and wala! 32GB is back... I didn't try to apply factory reset from ROM because I have root.
Click to expand...
Click to collapse
Glad to hear that :good:

Categories

Resources