So I successfully unlocked my bootloader and flashed custom ROM and recovery, first boot it was okay, I was able to setup Android and installed apps, now when I rebooted it, it only boots to recovery. Phone can still be detected by my PC, can also get detected in fastboot when in bootloader. So I think there's really a workaround for this I just didn't know how and I am now hesitant to follow web tutorials if it isn't an official forum just like this.
Things I already did:
Reinstall ROM
Reflashed custom recovery
Cleared Data/Dalvik/Cache
Factory Reset
Flash the stock firmware by SP Flash Tool, it'll help to revert back to stock and stop boot loop!
Related
I followed all of the instructions in the Nexus 6 Guide to unlock, root and flash a custom recovery.
I was trying to sideload a rom into my phone and was doing advanced wipe in TWRP. I accidentally choose system thinking it would be fine since I am flashing a new rom anyway.
I think I force shut down the phone and now it just stays and hangs on the google logo. I can only get into the bootloader/fastboot. When I try getting into TWRP recovery it just flashes for a second and then attempts to reboot.
I figure I should try flashing a rom via adb bootloader/fastboot but I attempted a few times and failed. Can someone help walk me through this?
Edit: I can access TWRP recovery now... I tried doing sideload several more times but for some reason I keep getting loading rom.zip cannot read rom.zip
Well i going to geuss you know to to get to recovery though bootloader thought your phone
But your phone is semi Bricked
You can download wugs toolkit
And i will show unroot/flash stock you will click bootloop/ bricked and go though the steps
And it will download the stock software and reovery and go though the steps you will be fine
If you want use the same toolkit and root and install twrp again
Do you use a USB otg drive? If you don't you can send a rom to twrp using some commands.
Try to redownload the ROM that won't work and put it on the phone via a USB otg drive or using your pc and don't forgot gaps.
If you're not, use the WUG toolkit to reflash the stock ROM. Then you can use that to flash your new ROM
Unless im missing somethimg, why not just flash the factory image through fastboot and start over?
Like mentioned above, or just flash TWRP in fastboot. Then boot into TWRP, and flash ROM.
So this is what happened:
I wanted to flash a custom rom on my xperia Z.
I did what i have to do like unlocking the bootloader, rooting and installing a custom recovery.
I already downloaded my desired custom rom. When I entered into custom recovery I wiped everything as in everything under the Wipe menu of TWRP. After that I went to reboot to recovery. Unfortunately the phone did not reboot anymore. Just stucked at the sony logo. Now it cannot go to fastboot, flashmode or custom recovery. My computer cannot detect the phone as well.
Is there any way that I can still flash rom into my phone with the above situation?
Any help is much appreciated. Tia!
fitcho9 said:
So this is what happened:
I wanted to flash a custom rom on my xperia Z.
I did what i have to do like unlocking the bootloader, rooting and installing a custom recovery.
I already downloaded my desired custom rom. When I entered into custom recovery I wiped everything as in everything under the Wipe menu of TWRP. After that I went to reboot to recovery. Unfortunately the phone did not reboot anymore. Just stucked at the sony logo. Now it cannot go to fastboot, flashmode or custom recovery. My computer cannot detect the phone as well.
Is there any way that I can still flash rom into my phone with the above situation?
Any help is much appreciated. Tia!
Click to expand...
Click to collapse
Are u sure you've installed the correct drivers (fastboot, flashmode, adb)? If so, fastboot any custom kernel (with recovery) and you'll have recovery.
You wiped system, but I assume you had xzdualrecovery installed, and since it installs in system you lose recovery after wiping system and reboot.
Kernel with recovery is best option, you can safely wipe since kernel does not get wiped (only overwritten by rom or other kernel)
Hi langveld! Thank you for your reply..But i cannot go into fastboot.. Will it still do?
fitcho9 said:
Hi langveld! Thank you for your reply..But i cannot go into fastboot.. Will it still do?
Click to expand...
Click to collapse
i guess you can only use the flashtools now, first try selecting kernel only for flashing without wiping anything. And if that doesnt work, then you have to flash the whole firmware. try holding vol down when connecting, i got into fastboot mode like that last time. good luck
fitcho9 said:
So this is what happened:
I wanted to flash a custom rom on my xperia Z.
I did what i have to do like unlocking the bootloader, rooting and installing a custom recovery.
I already downloaded my desired custom rom. When I entered into custom recovery I wiped everything as in everything under the Wipe menu of TWRP. After that I went to reboot to recovery. Unfortunately the phone did not reboot anymore. Just stucked at the sony logo. Now it cannot go to fastboot, flashmode or custom recovery. My computer cannot detect the phone as well.
Is there any way that I can still flash rom into my phone with the above situation?
Any help is much appreciated. Tia!
Click to expand...
Click to collapse
try flashing stock firmware (it doesnt matter that your computer doesnt recognize your phone just do it)
i have the same problem...please help
i had unlocked bootloader , twrp recovery ....i tried to install a custom rom.....so before installing the custom rom , i wiped everything......now i dont have os or recovery or fastboot....just sony logo
Today I bought a Moto G 2nd generation spoiled, she said she was with software problem, I thought reinstalling the stock rom solved, right? not when I received the phone it was freezed in the screen of bootloader unlocked, i tried reinstalling the stock rom the bootloader showed all results ok but when the phone restarted he kept freezed, I can still access the bootloader, recovery etc .. but I couldn't install a custom recovery the results ok but when I enter the recovery nothing more than the stock recovery
Sorry for bad english
Why do you want to install a custom recovery? Do you want to flash a custom rom?
You can try to flash the stock rom via fastboot. When it keeps freezed, try to do a Factory Reset.
i can't install stock rom via fastboot, i can't flash custom recovery and i can't flash any custom rom via stock recovery, there is no rom stock to install via stock recovery ?(OTA Update compatible)
Whenever my recovery is TWRP I am not able to boot into any type of ROM. Every time I reboot my phone it will be past the "your bootloader is unlock" and always boots straight into TWRP. When I flash stock recovery I am stuck at a image of a Android and it just stays at "erasing..." till it reboots itself. I have attempted to flash different types of roms by sideloading through TWRP and also attempted to flash stock recovery through fastboot with no luck at all.
The issue started whenever I was on stock 6.0 and flashed TWRP. Once I was in TWRP at the end when I was rebooting my phone I said yes to install supersu, which I know now was a mistake. Afterwards I was stuck in a bootloop were I finally attempted to do a factory reset which seemed to have made things worse. That was when I was stuck at the "erasing..." whenever I attempted to boot through stock recovery. Not sure what else to try at this point.
Any help would be great at this point.
I'm in the same boat. Exact same problem with no idea how to fix. I can get into fastboot screen, but that's it. Suggestions? Thanks in advance.
Hi,
I was running Oxygen 4.0.0 and a beta build of TWRP 3.0.3 which works with new encryption. I used the android update mechanics to get the 4.0.1 OTA. System rebooted to recovery, recovery threw an error (zip file corrputed) and since then I am not able to boot the system. Whatever I do I land in TWRP recovery.
Things I did so far:
- Tried installing the full 4.0.1 zip. Install worked without errors, device still boots to recovery.
- Tried to get stock recovery, since another post (https://forum.xda-developers.com/oneplus-3t/help/stuck-recovery-mode-t3532524) indicates stock recovery might fix the problem
--> stock recovery is not obtainable anymore. Seems deleted from all the download links I could find. Example is here: https://forum.xda-developers.com/oneplus-3t/how-to/zip-flashable-firmware-modem-t3509015
- Wipe cache and dalvik cache in the hopes, the instruction to boot to recovery is there somewhere.
I did not do the unbrick tool, since I run linux and didnt want to fiddle with windows yet.
I did make a nandroid backup, so once my system boots again I should be fine.
Any Idea where to either get a mirror of stock recovery or how to fix this problem otherwise?
I had this same problem, and I solved downloading the unbrick tool and extracting the recovery from there. Here is the file
https://drive.google.com/file/d/0BwaafKaXbak3d1RFblFOWVd5eGs/view?usp=sharing
Also locking the bootloader worked for me. Booted into system then unlocked again.
Thanks a lot for the stock recovery. That worked!
Once it booted, installing TWRP and SuperSU again.
mad-murdock said:
Thanks a lot for the stock recovery. That worked!
Once it booted, installing TWRP and SuperSU again.
Click to expand...
Click to collapse
Does your TWRP boot correctly? I flashed it and when I restarted I still had the stock recovery, so I used fastboot boot and it booted, but it is stuck in the loading screen.
Edit: After rebooting and reflashing totally random, it worked.
mariospizza said:
Does your TWRP boot correctly? I flashed it and when I restarted I still had the stock recovery, so I used fastboot boot and it booted, but it is stuck in the loading screen.
Edit: After rebooting and reflashing totally random, it worked.
Click to expand...
Click to collapse
Yeah, worked totally normal as it should.
My educated guess about this whole dilemma is, the system sets a flag to boot to recovery which TWRP doesn't clear and only stock recovery clears. Usually those flags should be in cache partition, but in this case isn't.
Tldr: don't use build in update mechanisms if you modified Rom and recovery.