So I was on weta rom flashed benzo latest with vendor and bootlooped my device. Got worried so I downloaded NRD90U factory image and fastboot flashed stock and format userdata, but phone still boot loops.
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
fastboot format userdata
fastboot format cache
fastboot reboot
I can go into the bootloader and then went to recovery get the android red exclamation mark guy so stock recovery has been flashed. I just don't know why it's bootlooping?
Did you backup and restore EFS at any point. If so you're bricked.
AndrewM3 said:
I can go into the bootloader and then went to recovery get the android red exclamation mark guy so stock recovery has been flashed. I just don't know why it's bootlooping?
Click to expand...
Click to collapse
And if you are bricked (TWRP 3.0.2-1 EFS restore?) you need to erase those partitions via ADB to fix it.
Sent from my Nexus 6P using Tapatalk
Gytole said:
Did you backup and restore EFS at any point. If so you're bricked.
Click to expand...
Click to collapse
no i didn't backup efs, wait when I was on benzo I tried to restore a twrp backup I had but it said it failed, i left all the boxes checked marked to restore
ok so i'm getting the jist that I am hard bricked, my phone is still under warranty from google what is the best way to explain to them what happened so not to void warranty
ultyrunner said:
And if you are bricked (TWRP 3.0.2-1 EFS restore?) you need to erase those partitions via ADB to fix it.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
ok what is the command to do this. I put my phone in bootloader and what command do I fastboot. and would I reflash the factory image afterwards. thank you
how do i erase efs partition
so I have stock recovery how would I erase my efs partition?
Solved
thanks to @ ultyrunner I flashed twrp and then ran the follwing adb commands to make my phone boot up and it worked. you sir are my hero!
If you have been bricked you NEED to Erase the EFS partitions and that will fix it immediately.
For the Nexus 6P go to TWRP. Then on PC Open Command Prompt with access to ADB ( Android Debug Bridge) and execute the following commands:
ADB shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst1 bs=16384
and
ADB shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst2 bs=16384
This should fix it for ANY Nexus 6P users.
from the thread http://forum.xda-developers.com/nexus-6p/help/announcement-twrp-3-0-2-1-fatal-bug-t3453119
AndrewM3 said:
thanks to @ ultyrunner I flashed twrp and then ran the follwing adb commands to make my phone boot up and it worked. you sir are my hero!
If you have been bricked you NEED to Erase the EFS partitions and that will fix it immediately.
For the Nexus 6P go to TWRP. Then on PC Open Command Prompt with access to ADB ( Android Debug Bridge) and execute the following commands:
ADB shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst1 bs=16384
and
ADB shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst2 bs=16384
This should fix it for ANY Nexus 6P users.
from the thread http://forum.xda-developers.com/nexus-6p/help/announcement-twrp-3-0-2-1-fatal-bug-t3453119
Click to expand...
Click to collapse
Glad it worked. Grab the unofficial 3.0.2-3 update and avoid further headache
Sent from my Nexus 6P using Tapatalk
---------- Post added at 01:41 PM ---------- Previous post was at 12:54 PM ----------
AndrewM3 said:
so I have stock recovery how would I erase my efs partition?
Click to expand...
Click to collapse
You can run ADB commands on stock recovery. You need to ensure you have current ADB/fastboot drivers installed and that your computer recognizes your device.
Once that's working, do some research on the exact process but in a nutshell boot into bootloader, reboot into stock recovery and get into the recovery menu, use the rocker to select "update over ADB" and then you can doublecheck your computer recognizes your device and should be able to issue the commands to erase the EFS.
Related
Alright first off, I can boot into recovery and bootloader. However, I have no CWM backups or any ROMs on my sd card.
I have no ROM currently installed so it will not get past the splash screen. I went into bootloader, but doing the command "adb devices" nothing is found.
I have tried using the Toolkits but it still doesn't recognize my device. It would just say "waiting for device" and nothing happens.
Any help would be appreciated.
kkl1993 said:
Alright first off, I can boot into recovery and bootloader. However, I have no CWM backups or any ROMs on my sd card.
I have no ROM currently installed so it will not get past the splash screen. I went into bootloader, but doing the command "adb devices" nothing is found.
I have tried using the Toolkits but it still doesn't recognize my device. It would just say "waiting for device" and nothing happens.
Any help would be appreciated.
Click to expand...
Click to collapse
the bootloader is for fastboot. i dont know about cwm, but twrp recovery has an adb sideload option. you connect to adb, press the button, type the command shown, and load the rom from your desktop to your device. you can fastboot the twrp recovery via your bootloader and fastboot.
Alternatively if you have an otg cable and a flash drive you should be able to flash the ROM through recovery via external SD.
Also on other devices I have flashed ROMs via fastboot, haven't tried on this but I'm sure it easy. If you have a nandroid on PC in the yaffs2 format then you can use this (most recoveries make tar backups which won't work through fastboot.
Boot to fastboot and open cmd in the folder of the nandroid, then type
fastboot erase system -w
fastboot erase boot
fastboot flash userdata data.img
fastboot flash system system.img
fastboot flash boot boot.img
fastboot reboot
If you don't have a nandroid on PC or its not yaffs2 then flash a update.zip
fastboot erase system -w
fastboot erase boot
fastboot update superawesomerom.zip
(Replace superawesomerom with the name of the ROMs .zip)
Again I've both methods with plenty of other android devices and it should work just fine with the nexus7 but haven't bothered to try. Will soon if anyone needs confirmation
Sent from my Nexus 7 using xda premium
demkantor said:
Alternatively if you have an otg cable and a flash drive you should be able to flash the ROM through recovery via external SD.
Also on other devices I have flashed ROMs via fastboot, haven't tried on this but I'm sure it easy. If you have a nandroid on PC in the yaffs2 format then you can use this (most recoveries make tar backups which won't work through fastboot.
Boot to fastboot and open cmd in the folder of the nandroid, then type
fastboot erase system -w
fastboot erase boot
fastboot flash userdata data.img
fastboot flash system system.img
fastboot flash boot boot.img
fastboot reboot
If you don't have a nandroid on PC or its not yaffs2 then flash a update.zip
fastboot erase system -w
fastboot erase boot
fastboot update superawesomerom.zip
(Replace superawesomerom with the name of the ROMs .zip)
Again I've both methods with plenty of other android devices and it should work just fine with the nexus7 but haven't bothered to try. Will soon if anyone needs confirmation
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I tried to do that but it seems like it wont communicate with my computer. all it says is fastboot: command not found
demkantor said:
Alternatively if you have an otg cable and a flash drive you should be able to flash the ROM through recovery via external SD.
Also on other devices I have flashed ROMs via fastboot, haven't tried on this but I'm sure it easy. If you have a nandroid on PC in the yaffs2 format then you can use this (most recoveries make tar backups which won't work through fastboot.
Boot to fastboot and open cmd in the folder of the nandroid, then type
fastboot erase system -w
fastboot erase boot
fastboot flash userdata data.img
fastboot flash system system.img
fastboot flash boot boot.img
fastboot reboot
If you don't have a nandroid on PC or its not yaffs2 then flash a update.zip
fastboot erase system -w
fastboot erase boot
fastboot update superawesomerom.zip
(Replace superawesomerom with the name of the ROMs .zip)
Again I've both methods with plenty of other android devices and it should work just fine with the nexus7 but haven't bothered to try. Will soon if anyone needs confirmation
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
also i do have an OTG cable and obviously a flash drive, how do i install a ROM through it
For fastboot you will either need to add a path for adb.exe and fastboot.exe in environmental variables or put files needed in same folder as fastboot.exe and of course have proper drivers
Haven't used clockwork for any android in years (not the biggest fan) but I believe when you choose to flash a zip it will allow you to choose where to, including an external SD.
if it doesn't use fastboot to flash twrp and that definitely does have the option. Of course you will need to get fastboot up and running
Sent from my Nexus 7 using xda premium
I'm selling my Nexus 7 and I think I got a little click happy while clearing it out.
I had reinstalled 4.3 and then for some reason I formatted the data. Got stuck in a boot loop.
When I try to install the image again I get the following:
Updating partition details...
E:error opening '/data/media'
E:error: no such file or directory
Any help would be appreciated!
"90% of the time, when someone says something's bricked, the only brick is their head." - Koush
All this means is that your userdata partition got all jacked up. It's restored when you boot into a rom, but of course you can't boot into a rom cause something else must have also went awry. So I suggest you wipe everything and start over. Follow along with me, this will be fun!
Boot into fastboot, send fastboot unlock command if your bootloader isn't already unlocked "fastboot oem unlock." Accept on screen. Reboot back into bootloader/fastboot. Issue FASTBOOT ERASE USERDATA, FASTBOOT ERASE RECOVERY, FASTBOOT ERASE CACHE, FASTBOOT ERASE SYSTEM. Then flash TWRP recovery using FASTBOOT FLASH RECOVERY [NAME OF TWRP GROUPER IMG]. Then adb push your rom and gapps back to your tablet using ADB PUSH [FILE] /SDCARD, then flash your rom and enjoy a fresh clean tablet!
That's why I prefixed with 'possible'...
Thanks - I followed this guide later in the evening and got it all up and going again.
http://goo.gl/BsiewY
0vermind said:
"90% of the time, when someone says something's bricked, the only brick is their head." - Koush
All this means is that your userdata partition got all jacked up. It's restored when you boot into a rom, but of course you can't boot into a rom cause something else must have also went awry. So I suggest you wipe everything and start over. Follow along with me, this will be fun!
Boot into fastboot, send fastboot unlock command if your bootloader isn't already unlocked "fastboot oem unlock." Accept on screen. Reboot back into bootloader/fastboot. Issue FASTBOOT ERASE USERDATA, FASTBOOT ERASE RECOVERY, FASTBOOT ERASE CACHE, FASTBOOT ERASE SYSTEM. Then flash TWRP recovery using FASTBOOT FLASH RECOVERY [NAME OF TWRP GROUPER IMG]. Then adb push your rom and gapps back to your tablet using ADB PUSH [FILE] /SDCARD, then flash your rom and enjoy a fresh clean tablet!
Click to expand...
Click to collapse
Ideas on what is going on?
I have heard that maybe doing a
Code:
fastboot flash recovery "twrp 3.0.0-1".img
fastboot format userdata
fastboot reboot recovery
might work but i am just wanting to boot it and not wipe my data.
JustusIV said:
Ideas on what is going on?
I have heard that maybe doing a
Code:
fastboot flash recovery "twrp 3.0.0-1".img
fastboot format userdata
fastboot reboot recovery
might work but i am just wanting to boot it and not wipe my data.
Click to expand...
Click to collapse
It should be - fastboot flash recovery twrp-3.0.0-0-angler.img
and, fastboot reboot recovery, is not a command under fastboot.
Don't you have a TWRP backup? Why's it matter if it wipes the data?
Im on stock N.
I just want to boot twrp without flashing but it hangs. I am starting to think its a known issue and will be resolved later.
http://forum.xda-developers.com/apps/supersu/wip-android-n-preview-t3335726
But as TWRP isn't working yet on all N Preview devices either
Click to expand...
Click to collapse
While following DirtySanta's guide I believe I may have accidentally copy/paste the whole post and it may have read these commands:
fastboot erase system
fastboot reboot
In TRWP Recovery it shows no OS installed.
Am I SOL?
Hey, I accidentally corrupted my persist partition, the phone is unusable; the WiFi doesn't work, and it restarts every 2 Minutes. I tried flashing persist
fastboot flash persist persist.img
FAILED (remote: Error: This image isn't allow download)
I already tried erasing persist, but it won't let me.
Can someone please tell me a method to unlock the persist partition for download so I can flash persist.img? Please note that I can't flash TWRP either, says partition table doesn't exist. Is there a way to maybe flash it through Mi Flash Tool?
boot to twrp
enable mtp from twrp if not enabled
copy persist.img to root of your phone storage
open terminal in twrp
and give the following command
dd if=/sdcard/persist.img of=/dev/block/mmcblk0p27
and done
now persist partition will be restored
reboot your phone
No twrp
raaz1431994 said:
boot to twrp
enable mtp from twrp if not enabled
copy persist.img to root of your phone storage
open terminal in twrp
and give the following command
dd if=/sdcard/persist.img of=/dev/block/mmcblk0p27
and done
now persist partition will be restored
reboot your phone
Click to expand...
Click to collapse
As I said earlier, I can't flash a custom recovery, tells me that partition table does not exist.
Hi man!.
do you flash with factory_reset.bat?, if the answer is yes, you have to flash tissot 7.23 with the attachment (change the txt extension to bat and start the phone in fastboot, when it finish, start the phone in fastboot and unlock the bootloader and try to flash the persist partition again in fastboot, if didnt work, boot the TWRP recovery (yes, boot it with fastboot boot recovery.img ) and flash the persist image with adb shell, dd if=/sdcard/persist.img of=/dev/block/bootdevice/by-name/persist , the persist image must be in the internal memory (you can copy it with MTP) when the phone starts, you can change the WLAN and Bluetooth mac addres in /persist/wlan_mac.bin, /persist/bluetooth/.nv_bluetooth, to change the serial numer /persist/.sn
Hope it works to you
PD. If you flash the factory_reset.bat, probably you lost the IMEI to and that would be a problem.
do not flash twrp
just boot to twrp using fastboot command
fastboot boot twrp.img
---------- Post added at 12:49 AM ---------- Previous post was at 12:48 AM ----------
CoolPlushBear said:
As I said earlier, I can't flash a custom recovery, tells me that partition table does not exist.
Click to expand...
Click to collapse
do not flash twrp
just boot to twrp using fastboot command
fastboot boot twrp.img
CoolPlushBear said:
As I said earlier, I can't flash a custom recovery, tells me that partition table does not exist.
Click to expand...
Click to collapse
Did you ever solve this issue or find a work around? I have same issue.....
If you don't flash the backup of your persist partition and use instead someone else's backup, you'll mess up your phone.
- # dd if=/sdcard/persist.img of=/dev/block/mmcblk0p27
dd: writing '/dev/block/mmcblk0p27': No space left on device
2049+0 records in
2048+0 records out
1048576 bytes (1 .0MB) copied, 0.114366 seconds, 8.7MB/s
FAIL~~
CoolPlushBear said:
Hey, I accidentally corrupted my persist partition, the phone is unusable; the WiFi doesn't work, and it restarts every 2 Minutes. I tried flashing persist
fastboot flash persist persist.img
FAILED (remote: Error: This image isn't allow download)
I already tried erasing persist, but it won't let me.
Can someone please tell me a method to unlock the persist partition for download so I can flash persist.img? Please note that I can't flash TWRP either, says partition table doesn't exist. Is there a way to maybe flash it through Mi Flash Tool?
Click to expand...
Click to collapse
Don't try to flash persist.img You can encounter more trouble
You can Lost IMEI and sensor, try this metodo:
https://forum.xda-developers.com/mi-a1/how-to/tool-persist-resurrector-v1-0-0-0-t3781095
carlosorta said:
Hi man!.
do you flash with factory_reset.bat?, if the answer is yes, you have to flash tissot 7.23 with the attachment (change the txt extension to bat and start the phone in fastboot, when it finish, start the phone in fastboot and unlock the bootloader and try to flash the persist partition again in fastboot, if didnt work, boot the TWRP recovery (yes, boot it with fastboot boot recovery.img ) and flash the persist image with adb shell, dd if=/sdcard/persist.img of=/dev/block/bootdevice/by-name/persist , the persist image must be in the internal memory (you can copy it with MTP) when the phone starts, you can change the WLAN and Bluetooth mac addres in /persist/wlan_mac.bin, /persist/bluetooth/.nv_bluetooth, to change the serial numer /persist/.sn
Hope it works to you
PD. If you flash the factory_reset.bat, probably you lost the IMEI to and that would be a problem.
Click to expand...
Click to collapse
what is tissot 7.23?
raaz1431994 said:
boot to twrp
enable mtp from twrp if not enabled
copy persist.img to root of your phone storage
open terminal in twrp
and give the following command
dd if=/sdcard/persist.img of=/dev/block/mmcblk0p27
and done
now persist partition will be restored
reboot your phone
Click to expand...
Click to collapse
still working in 2020. Thanks for your post. Small thread but powerful. :dynamite: