nexus 4 is running cm11 snapshot for a few days now, and i woke up to my phone in a boot loop. when i enter recovery mode the internal memory is completely empty, so .zips, backups, etc. i tried using adb sideload to reflash the rom but that doesnt help. the only thing weird thing that ive noticed is when i wipe data/factory reset i get the the following "E: unknown volume "/sdcard/.android_secure" nexus 4". Help?
Make sense that it can't find .android_secure if it can't find SD partition
Boot to fastboot and reformat
fastboot erase system -w
fastboot erase boot
And just for fun erase and flash a new recovery
fastboot erase recovery
fastboot flash recovery nameofrecovery.img
Now boot back to recovery and try to sideload a new ROM, something known stable maybe slimbean4.3
If you get errors note them
If this won't work than you'll need to flash bootloader and radio and then repeat the process above
Sent from my Nexus 7 using XDA Premium 4 mobile app
Related
Okay, so yesterday I was flashing from SlimBean to stock 4.3 on my Nexus 7. Okay, good no problem. After that I was using WugFresh's toolkit to update from 4.3-4.4 since my bootloader is unlocked and it wouldn't take the OTA. The cmd prompt said something akin to:
boot.sig not in archive
Recover.sig not in archive
And then it froze, for a bit before giving me the end message about the first reboot taking 5-10 minutes. OK, cool. I was still in fastboot mode, so I went ahead and volume upped to start. The Google image flashed, along with the unlock symbol, and in very tiny text at the top right says Booting Failed.... On the same screen off to the right is the arrow that says start, just like in bootloader. I'm freaking out because this is basically brand new, and I don't wanna NAFTA buy another.
Oh, and it's the 2012 Grouper/Nasaki WiFi only model.
Thanks in advance for any and all advice.
Sent from my GNEX running SlimBean
Just boot back to bootloader and flash a custom recovery through fastboot
Then boot back to this recovery and flash ROM of choice
If you want to go back to stock fully then drop the tool kits and just flash stock and relock bootloader
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
Just boot back to bootloader and flash a custom recovery through fastboot
Then boot back to this recovery and flash ROM of choice
If you want to go back to stock fully then drop the tool kits and just flash stock and relock bootloader
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Alright I did that, erasing the non existent recovery as well. Now when I try to boot, its stuck at the Google logo. When I enter bootloader and select reboot recovery, it just goes to the screen with Google logo and the fastboot arrow
Sent from my GNEX running SlimBean
So through fastboot you ran
fastboot erase recovery
fastboot flash recovery recovery.img
And output said OK to both and the recovery you used was for grouper correct? The md5sum checked out right?
If so you may need to flash a factory image from google
https://developers.google.com/android/nexus/images
This time
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot update nameofupdate.zip
Oh and you may need to relock bootloader before update
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
So through fastboot you ran
fastboot erase recovery
fastboot flash recovery recovery.img
And output said OK to both and the recovery you used was for grouper correct? The md5sum checked out right?
If so you may need to flash a factory image from google
https://developers.google.com/android/nexus/images
This time
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot update nameofupdate.zip
Oh and you may need to relock bootloader before update
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Alright, so after i flashed the recovery, I attempted to boot into recovery. I am stuck at the google logo. But let me try the rest of the commands you gave me really quick.
Oh, and when I downloaded the factory image, I got a .tgz file, not a zip.
Sent from my GNEX running SlimBean
So the recovery.img you are flashing through fastboot says it worked but when you boot to it you get nothing? Is this correct? What recovery image are you flashing?
Can you try
fastboot boot recovery.img
Sent from my Nexus 7 using Tapatalk 2
Alright, I figured it out. The recovery was flashing right, but the file I had wouldn't stick for some reason. So I found the grouper TWRP .IMG file, flashed it, and it stayed. After that, it was as simple as pushing the file and flashing it all. Thank you so much for all of your help in this matter. Hope to see ya around the forums!!!
Sent from my Nexus 7 using xda app-developers app
I unlocked the boot loader, then I rebooted my phone, then rebooted into recovery mode. Once I install either a custom rom, or supersu, even if it works to install, once i try to reboot, it only reboots to TWRP. Even when I reboot to system it still does that. Is my phone just bricked?
bobbymacy said:
I unlocked the boot loader, then I rebooted my phone, then rebooted into recovery mode. Once I install either a custom rom, or supersu, even if it works to install, once i try to reboot, it only reboots to TWRP. Even when I reboot to system it still does that. Is my phone just bricked?
Click to expand...
Click to collapse
No its not bricked.. maybe soft bricked, but not bricked bricked how are you flashing recovery? are you using
fastboot flash recovery twrp.img
or
fastboot flash boot twrp.img
2nd way is incorrect. Try
fastboot flash recovery twrp.img
fastboot erase cache
then boot to twrp and flash rom and let me know what happens. Make sure you are using correct gsm twrp if you are on an att phone.
He probably followed these instructions here which direct you to flash twrp to boot instead of recovery just like you said above.
I don't know why he leaves it up there like that but seeing as it's the first link on Google when you search "root att HTC one m8" , he needs to change it cause I'm sure it's causing plenty of headaches.
Sent from my HTC One_M8 using Tapatalk
an0ther said:
No its not bricked.. maybe soft bricked, but not bricked bricked how are you flashing recovery? are you using
fastboot flash recovery twrp.img
or
fastboot flash boot twrp.img
2nd way is incorrect. Try
fastboot flash recovery twrp.img
fastboot erase cache
then boot to twrp and flash rom and let me know what happens. Make sure you are using correct gsm twrp if you are on an att phone.
Click to expand...
Click to collapse
I did
./fastboot flash recovery twrp.img
because I'm using mac. I didn't erase the cache though. Also on twrp, it says my phone has no os, and installing a custom rom failed to install.
I get backup error everytime when i try to make backup with TWRP ?? Any ideas why this happeing to me ?
PS: I try it 2 versions of twrp for jb
The only recovery that Im able to use is Fixed by Atis...
Did you erase cache after fastboot flashing the TWRP?
Sent from my Desire X using XDA Premium 4 mobile app
I use those comands:
call fastboot flash recovery recovery.img
call fastboot erase cache
pause
PS:
After few restarts everything seems to be OK.
Here is the problem : After flashing a rom, I got encryption unsuccessful, then I go back to recovery and wipe. as it took long I force reboot using power and vol-. Now the phone always boot on TWRP which stuck on splash and sometimes it boot the rom but has encryption unseccessful. I do not have DL as there is TWRP as well with the same problem. I can boot to fastboot but the command : fastboot erase recovery alway get unknown command. I also tried flash the laf.img via fastboot but it doesn't work.
Need help please.
I get it solve by using fastboot oem lock. It wiped userdata and cache and unfreeze TRWR, then unlock bootloader again. Everything works like charm
I have unlocked my bootloader using official Asus tool, I then went on to flash TWRP 5.3.x.x. using fastboot and also formatted userdata and cache from fastboot itself to remove encryption. Recovery works fine.
I have tried flashing both these ROMs. [links below]
[ROM][OFFICIAL][11.0][X01AD] Arrow OS
[ROM][11][5.R] Project Sakura [2021/03/19][UNOFFICIAL]
I followed the instructions, formatted data using TWRP, wiped system, vendor, cache, data, dalvik.
I then flashed the ROM from TWRP itself, and I have also tried to install it through ADB sideloading. Then I wipe dalvik/cache.
Both instances, the installation happens fine but when I reboot phone gets stuck in fastboot mode. I resolve that by flashing 'vbmeta.img'.
Then phone starts booting but gets stuck in a loop bootloader-->ASUS logo-->"Powered by Android"-->bootloader
So basically, it does not boot into system.
I have even flashed stock A10 firmware from here Stock Vendor and Firmware images for Asus Max M2 but still no resolution.
I have also tried manually mounting system partition from TWRP, doesn't work.
Any help would be much appreciated.
Connect phone and PC via USB-cable and in Windows command prompt run this command sequence
Code:
fastboot devices
fastboot reboot
to take back phone to it's normal ANDROID mode.
arko2000 said:
I have unlocked my bootloader using official Asus tool, I then went on to flash TWRP 5.3.x.x. using fastboot and also formatted userdata and cache from fastboot itself to remove encryption. Recovery works fine.
I have tried flashing both these ROMs. [links below]
[ROM][OFFICIAL][11.0][X01AD] Arrow OS
[ROM][11][5.R] Project Sakura [2021/03/19][UNOFFICIAL]
I followed the instructions, formatted data using TWRP, wiped system, vendor, cache, data, dalvik.
I then flashed the ROM from TWRP itself, and I have also tried to install it through ADB sideloading. Then I wipe dalvik/cache.
Both instances, the installation happens fine but when I reboot phone gets stuck in fastboot mode. I resolve that by flashing 'vbmeta.img'.
Then phone starts booting but gets stuck in a loop bootloader-->ASUS logo-->"Powered by Android"-->bootloader
So basically, it does not boot into system.
I have even flashed stock A10 firmware from here Stock Vendor and Firmware images for Asus Max M2 but still no resolution.
I have also tried manually mounting system partition from TWRP, doesn't work.
Any help would be much appreciated.
Click to expand...
Click to collapse
hello did you finally find the solution? I also can't move on any custom rom starts in fastboot mode
Is it possible that no one has a solution to this problem? I've been getting annoyed for three days and trying...
Is there any resolution anyone found out? I am stuck at the same problem for days. @N3I3 @arko2000
@Drigio @N3l3 @arko2000
FIX "BOOTLOOP ISSUE" AFTER FLASHING CUSTOM FIRMWARE IN ANDROID 10
Click to expand...
Click to collapse
Requirements:
vbmeta.img (For A10)
ADB & Fastboot (In case you don't have one)
Instructions:
Install ADB-and-Fastboot++_v1.0.6.exe and run.
Copy the commands below.
Commands:
Code:
fastboot erase vbmeta
- OPTIONAL
Code:
fastboot flash --disable-verity vbmeta 'location of vbmeta'
- OR DRAG THE A10 vbmeta
Code:
fastboot reboot
Hope this helps!
I HAVING ALSO SAME PROBLEM CAN ANY ONE FIX IT..