So, yeah! I tried to flash the Factory Images of 4.4 to my nexus 10 via fastboot and now its stuck in a bootloop. I tried to flash a custom recovery (twrp-2.6.3.1) and I was able to flash it. But, it says that the device is encrypted and that I need to enter the password in order to mount anything. I can mount my flashdrive, where I keep all my backups, via usb-otg and TWRP is able to recognize it but nothing can be flashed because, again, none of the partitions can be mounted... Can anybody help?
Related
I recently just picked up a nexus 4 and i'm trying to get a custom ROM on it. I updated it to 4.3 and that was fine. Went to install custom recovery and every since it will not boot! I've reverted to factory 4.3 using fastboot, and relocked it and locked it but still will not boot. It gets stuck at the X logo. Left it for an hour and won't get past it. If i install a custom recovery, it'll boot into the custom recovery no problem, but won't install root as it can't mount the SD card. I can get to fastboot mode no problem and flash stuff in fastboot but will never boot up. I'm puzzled as to what to do. I'm going to try 4.2.2 factory image here shortly and see if i can get it to take. I forgot to enable USB debugging so i think thats why i can't get custom recoveries to work. I tried pushing a ROM using ADB push but it wouldn't get there. Maybe it did as it said it did on the computer but the recovery won't read the memory. Any ideas as to what to do
UPDATE: Ok after flashing stock 4.2.2 from fastboot it boots.
UPDATE: turns out just having USB debugging was the culprit of everything. So make sure USB debugging is enabled before starting the whole process!
hard reset my phone via twrp recovery and i accidentally wiped the system too. now when i try to reboot my device, it's just stuck on google logo. bootloader is still unlocked. fastboot and twrp are working perfectly too. i just can't figure out a way to push zip file to my phone. i trie using a couple of toolkits and all of them were stuck on device not found. any help would be greatly appreciated.
Boot into twrp, connect phone to the computer, copy rom to the phone, and flash from twrp.
audit13 said:
Boot into twrp, connect phone to the computer, copy rom to the phone, and flash from twrp.
Click to expand...
Click to collapse
i'm a windows user & my laptop doesn't recognize my device when i connect it. probably because it requires usb debugging to br turned on which i can't do because no os.
Hello, i have a problem with this device zenfone z00ed. When i turn on i saw the procedure of upgrade, but stuck ad 24%. So i try to go to recovery mode but not work, only in fastboot. I try to push recovery image or boot but i get error (seems is not signed). However i have a idea (maybe bad idea) i reset all with fastboot -w.
After it i try to turn on, but i have bootloop with logo asus. So i found the right recovery image, and i go to recovery for push via adb the file http://dlcdnet.asus.com/pub/ASUS/Ze...user.zip?_ga=1.73637138.1491728547.1480409858
But not work , so i copy the file into the microsd and the phone installed the firmware , after it i get the error : can't load invalid boot image
What can i do?
Flash the .43 recovery image then go to stock recovery and try to update from SD card the .44 version from your link.
And make sure your file isn't corrupted.
Thanks for reply. Well i try as you tell me. I used another microSD. So i downloaded the .43 on the web site. Put into the microSD and into the phone. Hard reset and installed the new update file. Reboot. ... Same problem. Hard reset. Same problem. I used another more old update zip from the website. Same problem. Maybe i Need to flash another file? Is strange that problem. The boot-loader isn unlock (however)
How did yout flash the recovery and boot image?
Recovery im sure..like fastboot flash recovery recovery.img...
However.. i follow another istruction to fastboot with twrp (not flash) so i unlocked the boot-loader. After if the phone reboot and automatically works. For now.
Atleast you can use your phone now
Use adb sideload via asus recovery
I have the MetroPCS xt1765 running lineageos 14.1. When unlocking and doing all that jazz, the guide said that you can't flash twrp, only boot it. But I got annoyed that /data wouldn't mount so I just tried to flash it anyway and it worked. On cmd it said that the file wasn't signed or corrupt, but it still wrote to the device. I thought nothing about it at first but when I tried to boot the device it automatically when into twrp. I tried to reboot to system again, and the same thing happened.
Eventually /data successfully mounted and I was able to format it and install linage. I hoped that would fix the problem but it's still there. I believe I would need the stock boot image and probably stock recovery as well. I hope someone out there has these files.
Also when booting with factory mode, my data isn't working at all. The apn setting are right and all, but it's not working.
ZacharyTheUmbreon said:
I have the MetroPCS xt1765 running lineageos 14.1. When unlocking and doing all that jazz, the guide said that you can't flash twrp, only boot it. But I got annoyed that /data wouldn't mount so I just tried to flash it anyway and it worked. On cmd it said that the file wasn't signed or corrupt, but it still wrote to the device. I thought nothing about it at first but when I tried to boot the device it automatically when into twrp. I tried to reboot to system again, and the same thing happened.
Eventually /data successfully mounted and I was able to format it and install linage. I hoped that would fix the problem but it's still there. I believe I would need the stock boot image and probably stock recovery as well. I hope someone out there has these files.
Also when booting with factory mode, my data isn't working at all. The apn setting are right and all, but it's not working.
Click to expand...
Click to collapse
When it was booting to twrp only, you just select reboot bootloader and in bootloader select start and you will get system. This twrp doesn't read and clear bootloader control block (BCB) properly which causes this. There is a fix. I'll find the link.
Do you mean fastboot/bootloader mode? If yes, try this
Hi,
I have been using my P Smart (FIG-LX1) for a while with LineageOS 16 and decided to move on to Android 10. Installed LineageOS 17.1 (found it on this forum) and pph-Magisk 20.3 for root - it did work, but the system was unstable so i decided to try AOSP 10.0 instead. I entered TWRP, wiped cache,dalvik,system and data, flashed the ROM, gapps etc. It was advised to now flash stock recovery and use it to do a factory reset - and now i'm stuck here.
After flashing the recovery_ramdisk img the phone stopped being able to enter any recovery at all. The system itself does not boot (stuck on the "Your device has been unlocked (...) Your device is booting now..." screen forever), the recovery never appears (previously in the start screen with 'unlocked device' warning it used to suggest pressing volume UP to enter recovery, now it only shows "Your device is booting now"). As i can still access fastboot, I tried flashing TWRP again - the TWRP splash screen does appear, but the phone gets stuck on it. Also tried flashing another system's img - nothing changed.
Is there anything I can do or did i just brick it completely?
Thanks for help!
SOLVED:
Apparently running fastboot erase on system and userdata partitions made me able to boot into recovery/erecovery again. I do have another problem now, but it's not connected with this one so I will create another thread for that.
Could you try help me? I can't even get ADB to work anymore