Hey guys, I forgot to flash Gapps when flashing the Exodus rom and now I'm stuck on the boot screen. It won't boot into recovery (stock or TWRP) and adb debugging is not turned on so I can't adb into recovery. I can only get into fastboot. If you can point me in the right direction I'd appreciate it.
Thanks
Try "fastboot boot twrp.img"
Related
Hey guys,
I have an stock, unlocked and rooted xt905 lying here with stock recovery right now.
For several times now I tried to flash either cwm or twrp but had no luck.
Thats what I did:
- complete backup
- unlock bootloader
- restore backup
- fastboot flash boot twrp.img
- fastboot reboot
Flashing twrp doesnt throw up any error but as soon as I say reboot, the phone reboots into twrp instead of booting the system.
If I try to reboot to system within twrp, it reboots to twrp again. Booting to recovery from twrp brings me to stock recovery.
Its the same thing with cwm and I dont have any clue why, as other users are saying that twrp is working fine.
Till now I tried several different versions of fastboot, twrp and cwm and none of them worked.
Any ideas?
You're using the wrong fastboot command.
By typing "fastboot flash boot twrp.img" you are flashing TWRP in place of the boot.img. You need to type "fastboot flash recovery TWRP.img."
RikRong said:
You're using the wrong fastboot command.
By typing "fastboot flash boot twrp.img" you are flashing TWRP in place of the boot.img. You need to type "fastboot flash recovery TWRP.img."
Click to expand...
Click to collapse
OMG....
I am working on this phone since yesterday and couldnt figure it out....till now.
Embarrassing! I flashed about a dozen phones before and never had any problems whatsoever and now this.....
Thanks anyway! I am glad that I didnt brick the phone with flashing the wrong partition.
Hi,
I have multirom installed and tried to install a android 5.0 rom. After installation I had some kind of boot loop: google logo -> restart
After that I rebooted via fastboot to recovery, but after the splash screen it rebootet and I got again the boot loop.
My next step was to try fastboot boot with the multirom recovery image and my default boot.img, but no success...
Then I noticed that I need for this 5.0 rom the 4.23 bootloader, so I upgraded from 4.13 (I think).
Same after that...
Then I tired fastboot boot with a stock TWRP recovery image for nexus 7 (2012) and I got a new kind of bootloop after that: google logo -> TWRP Logo -> restart
And now it tries to boot TWRP every time I turn on the devices and can't boot to fastboot (via vol - button) and adb is not working too...
Any ideas?
Download factory image and do a clean flash with wug tool kit. This will fix it.
To install the factory image, I need fastboot and I can't enter fastboot mode.
ThauExodus said:
Hi,
I have multirom installed and tried to install a android 5.0 rom. After installation I had some kind of boot loop: google logo -> restart
After that I rebooted via fastboot to recovery, but after the splash screen it rebootet and I got again the boot loop.
My next step was to try fastboot boot with the multirom recovery image and my default boot.img, but no success...
Then I noticed that I need for this 5.0 rom the 4.23 bootloader, so I upgraded from 4.13 (I think).
Same after that...
Then I tired fastboot boot with a stock TWRP recovery image for nexus 7 (2012) and I got a new kind of bootloop after that: google logo -> TWRP Logo -> restart
And now it tries to boot TWRP every time I turn on the devices and can't boot to fastboot (via vol - button) and adb is not working too...
Any ideas?
Click to expand...
Click to collapse
I was stuck the same way yesterday. Use the WUGS Nexus Root Toolkit. http://forum.xda-developers.com/showthread.php?t=1766475
I had to fool around with it before it would see the device, but once it did, I flashed the LRX21P and was off and running.
When I want to use in the toolkit "Back to Stock (Soft-Bricked/Bootloop) it asks me to tsrat into fastboot mode... but I can't... but I can get the device into apx mode...
Bump...
ThauExodus said:
When I want to use in the toolkit "Back to Stock (Soft-Bricked/Bootloop) it asks me to tsrat into fastboot mode... but I can't... but I can get the device into apx mode...
Click to expand...
Click to collapse
You mention TWRP - are you able to boot into TWRP, or does it just show the splash and reboot again? If you can get into TWRP, you could conceivably use ADB mode and sideload something...
Splash and reboot... I already tried to get adb access, but no success...
Wanted to flash a new ROM, so did a full wipe. Now when I tried to flash the ROM it says need twrp 3.1.x
So rebooted into fastboot and flashed latest twrp.
Now I can't reboot to recovery also NO OS too.
Tried the manual method holding power+volume up it just boots up gets stuck in bootlogo.
Any kinda help would be appreciated.
You know you can just do fastboot boot (blabla).img, right?
All you need is to put your phone into fastboot and the fastboot tool that you get when downloading adb.
NathanBrake said:
You know you can just do fastboot boot (blabla).img, right?
All you need is to put your phone into fastboot and the fastboot tool that you get when downloading adb.
Click to expand...
Click to collapse
Yea that worked.
Bear with me, I had an older version and maybe just my method but I had messed up the custom rom I had on so I went to put a new one on and wanted to update TWRP at same time.
I installed the new custom rom, then installed TWRP and correctly clicked recovery.
However now recovery just goes into fastboot mode, I went into the dev settings and put usb debugging on, authorised it but each time it goes into fastboot it is not recognised and when I reboot into phone usb debugging has been disabled.
So now I can't get into recovery to flash a new rom, nor can I put twrp on by fastboot.
Stuck at what to do
Using Havoc OS
Try booting into the recovery from fastboot
Boot into fastboot and type
Fastboot boot recovery.img (recovery.img is the file saved on your pc)
Hi I had LOS19.1 installed running quite well. I wanted Magisk, so I went to the TWRP website, selected my device, and downloaded latest
twrp-3.7.0_12-1-cheeseburger_dumpling.img
at https://dl.twrp.me/cheeseburger_dumpling/ ...
Booted into fastboot mode, renamed the img to twrp.img, then per the instructions I did...
$ fastboot flash recovery twrp.img this took a minute
$ fastboot reboot
Then when I tried to reboot into recovery it would show the TWRP loading screen for like 30 seconds and phone would shut off... Tried again and same...
Frustrated I thought I would try the oldfashion way and try to boot into the image...
$ fastboot flash boot twrp.img
Same thing happened again with the TWRP loading screen. But it wont boot into the OS now... I got to fastboot and selected START, starts the TWRP loading and powerdown again.
Oh **** did I just overwrite my ROM install? What do I do?
you know the difference between recovery and boot partition? restore the backup of boot.img
read the instructions for installing TWRP
https://forum.xda-developers.com/t/...-a12-cheeseburger-dumpling-25-12-2022.4351795
for rooting device with Magisk, read the instructions for installing Magisk
https://github.com/topjohnwu/Magisk
alecxs said:
you know the difference between recovery and boot partition? restore the backup of boot.img
read the instructions for installing TWRP
https://forum.xda-developers.com/t/...-a12-cheeseburger-dumpling-25-12-2022.4351795
for rooting device with Magisk, read the instructions for installing Magisk
https://github.com/topjohnwu/Magisk
Click to expand...
Click to collapse
Im assuming boot has to do with booting the OS or bootloader... You mind commenting your thoughts on my mistake and what I should do?
on your second attempt, you flashed recovery into boot partition. you need to restore the boot.img now, otherwise you will boot into TWRP every time.
alecxs said:
on your second attempt, you flashed recovery into boot partition. you need to restore the boot.img now, otherwise you will boot into TWRP every time.
Click to expand...
Click to collapse
lol like in the other thread where would I get the boot.img? (yes I have these 2 devices with these 2 seperate problems). Appreciate your help so far..