Flashed TWRP and now won't boot - Nexus 10 Q&A, Help & Troubleshooting

Hello,
I was attempting to root and install a custom ROM yesterday. I first unlocked my bootloader via ADB. Then flashed TWRP in fastboot mode using ADB. I then booted to TWRP and my internal memory said "0 GB." I wasn't able to do a backup or flash a ROM.
When I went to reboot my system it became stuck in the booting screen with the moving dots. What did I do wrong??! PLEASE HELP!

Rossco_Pee said:
Hello,
I was attempting to root and install a custom ROM yesterday. I first unlocked my bootloader via ADB. Then flashed TWRP in fastboot mode using ADB. I then booted to TWRP and my internal memory said "0 GB." I wasn't able to do a backup or flash a ROM.
When I went to reboot my system it became stuck in the booting screen with the moving dots. What did I do wrong??! PLEASE HELP!
Click to expand...
Click to collapse
Did you solve your problem ?
Once you unlock bootloader you loose all your data.
Have a try to "format" your data partition inside TWRP.
Afterwards install the custom ROM ..
Cheers

Related

Cannot flash TWRP. Stock recovery is persistent

Hi,
In order to update my phone to oxygenOS 2.2. I flashed oxygenOS 2.1.1 full rom and installed the OTA update for 2.2. Because of this the phone switched back to stock recovery. So I tried to install TWRP recovery through fastboot. The installation was successful but after reboot, it looks like the phone is keep switching back to stock recovery. I have tried this many times but same result everytime.
Note1: I did turned on the USB debugging before this.
Note2: Bootloader is unlocked.
Any help would be great. Thanks in advance!!
When TWRP asks you to modify system partition give it permission to do so at the start of booting to recovery
Akhil701 said:
When TWRP asks you to modify system partition give it permission to do so at the start of booting to recovery
Click to expand...
Click to collapse
The problem is that I dont see TWRP even once after flashing it. After flashing when I reboot to recovery, it directly shows me default recovery. When I said its switching back to stock recovery, because the flashing of twrp was successful, I am assuming that it is switching back to stock recovery.
Dreckk said:
The problem is that I dont see TWRP even once after flashing it. After flashing when I reboot to recovery, it directly shows me default recovery. When I said its switching back to stock recovery, because the flashing of twrp was successful, I am assuming that it is switching back to stock recovery.
Click to expand...
Click to collapse
I also experienced this the first time. But I just ran fastboot flash recover openrecover-twrp-2.8.7.0.img one more time and then rebooted the phone and pressed volume down until it entered TWRP.
pitrus- said:
I also experienced this the first time. But I just ran fastboot flash recover openrecover-twrp-2.8.7.0.img one more time and then rebooted the phone and pressed volume down until it entered TWRP.
Click to expand...
Click to collapse
Did that many times, but it keeps getting entering in the default recovery.
What happens when you boot twrp with fastboot instead of flashing?
Also probably shouldn't flash an ota 2 versions different than the full. If that was the full version you already had, should have flashed 2.1.2 ota then the 2.2.0 ota.
I'm having the same issue. I was able to boot into TWRP once from Fastboot, flashed SuperSU it said it was successful, then I rebooted. Root was not available, and stock recovery was back.
Chris_el said:
I'm having the same issue. I was able to boot into TWRP once from Fastboot, flashed SuperSU it said it was successful, then I rebooted. Root was not available, and stock recovery was back.
Click to expand...
Click to collapse
Don't know if will work... but boot to twrp from fastboot then flash twrp from within twrp.
khaos64 said:
Don't know if will work... but boot to twrp from fastboot then flash twrp from within twrp.
Click to expand...
Click to collapse
Hmm i'll give that a shot when I get home from work. Thanks.
Chris_el said:
Hmm i'll give that a shot when I get home from work. Thanks.
Click to expand...
Click to collapse
fastboot boot /path/to/twrp
then Swipe to allow modifications!
Yash98 said:
fastboot boot /path/to/twrp
then Swipe to allow modifications!
Click to expand...
Click to collapse
I get the error "FAILED remote: dtb not found'

Lost recovery, cant boot, only fastboot

Guys... when i tried to flash oos 3.0 on my op2 through twrp, i first wiped the data to install new rom, then install oos 3.0, it failed. I then flashed the recovery i downloaded from the thread, then restart the recovery
I cant boot into the recovery.
System can't boot
Is it called "brick"?
So i tried to flash stock recovery in pc by command, but it says "remote: device is locked. cannot flash images". any solution to this problem?
I can boot into fastboot mode
You need to run the phone in Qualcomm mode on a PC and run the recovery tool to fix you bootloader.
I did the same and it was a royal ball ache trying to find out how to fix it
Don't do what rosswaa said
Why not?
What you should do is boot your phone into fastboot mode, connect it to your pc. Flash this modified TWRP recovery img to your phone https://www.androidfilehost.com/?fid=24459283995297945. After that you have to flash this modified SuperSU (through the new recovery) https://www.androidfilehost.com/?fid=24459283995297946.
The normal recovery doesn't work in OOS 3.0 (just like in HOS) and it's the SuperSU that gives you the soft brick. A dirty flash of the modified SuperSU should fix it.
I also had your problem and I did what rosswaa said which shouldn't be necessary (I lost all my data and backups).
I didn't lose anything, but I tried doing what you said and my bootloader was screwed so wouldn't take a flashed recovery or anything (yes the modified one)
Wish I hadnt been so excited and just flashed but all sorted now
Hmm okay, if it doesn't work with flashing the new recovery img then do what rosswaa said and after that follow this post https://forums.oneplus.net/threads/installation-instructions-faqs-oxygenos-3-0-0.439108/
Obviously try what green says first, if it works then happy days
first i am really glad that someone give some advices on me. But since i am a noob, how can i flash twrp in fastboot mode? using command? "fastboot flash recovery xxx.img"? thx
SPiCa39's said:
Guys... when i tried to flash oos 3.0 on my op2 through twrp, i first wiped the data to install new rom, then install oos 3.0, it failed. I then flashed the recovery i downloaded from the thread, then restart the recovery
I cant boot into the recovery.
System can't boot
Is it called "brick"?
So i tried to flash stock recovery in pc by command, but it says "remote: device is locked. cannot flash images". any solution to this problem?
I can boot into fastboot mode
Click to expand...
Click to collapse
1 Install official TWRP 3.x via fastboot twrp.me/devices/oneplustwo.html
Reboot to recovery
2 install this modified version of TWRP
forum.xda-developers.com/oneplus-2/development/recovery-teamwin-recovery-project-3-0-0-t3310713
Reboot to recovery
3 install oos3 (And supersu)
Sorry i can't post link

Fu**ed up during first twrp installation, forgot to flash supersu before reboot

On xiaomi 3s during first twrp installation, forgot to flash supersu before reboot now i am stuck on MI logo, can access fastboot but not twrp. tried re-flashing twrp (wich i can do) but the phone still stuck with no twrp acess, tried to flash fastboot (flash boot twrp.img) also does nothing.ùi am quite the noob, please help?
redsjack said:
On xiaomi 3s during first twrp installation, forgot to flash supersu before reboot now i am stuck on MI logo, can access fastboot but not twrp. tried re-flashing twrp (wich i can do) but the phone still stuck with no twrp acess, tried to flash fastboot (flash boot twrp.img) also does nothing.ùi am quite the noob, please help?
Click to expand...
Click to collapse
Boot into TWRP. Goto Advanced --> Disable DM-Verify. Reboot device. Done.
now i installed the supersu but when i reboot the phone it always boots to TWRP i think because i flashed
fastboot flash boot twrp.img (yes i am a idiot)
if i want to boot the system what should i do?
redsjack said:
now i installed the supersu but when i reboot the phone it always boots to TWRP i think because i flashed
fastboot flash boot twrp.img (yes i am a idiot)
if i want to boot the system what should i do?
Click to expand...
Click to collapse
As far as I read this thread you forgot to turn off the DM-Verify option in TWRP after install and rebooted immediately.....
Hate to break it to you but your currently installed OS is now pretty much dead now. Had the same issue when I first tried it.
You need to install a clean MIUI ROM first via fastboot and MIFlash-Tool. Then proceed to install TWRP again. When TWRP is booted the first time it will ask your permission to Modify the System. Swipe to confirm that (needed for most operations TWRP is able to do).
After you allow the system modify part, you are in TWRPs main menu. Tap on "Advanced", then tap on "Disable DM-Verify". Once again swipe to confirm.
After that, you should be able to have TWRP on your device and should be able to boot normally to MIUI... or you go straight ahead and flash a new Custom Rom.
thank you.
So i will need to download a new rom (any suggestion on which one is good? i did install twrp because my vendor rom didn't work with local 3g and LTE) and install it with the miui flash tool. Than repeat the twrp installation but disable dm-verify first, (than reinstall super su?),and at the end reboot.
No need to clear anything?
i flashed the global stable rom from the xiaomi flash tool it say successful and took just a second but i am stuck still on mi logo....
Is your phone unlocked?
In fastboot fastboot oem device-info
i unlocked it just one day before with permission message from xiaomi.
Next time used cofface twrp for redmi 3S: http://en.miui.com/thread-244098-1-1.html
Sent from my Redmi 3S using Tapatalk
Ez. Go to fastboot mode, flash again the whole ROM and flash your TWRP again. Don't forget to disable DM-verify. It stuck at logo not because of you forgot to root your device, is because of you forget to disable DM-verify.

[H870] Phone keeps rebooting into Fastboot Mode

Dear readers,
I've no idea what happened but after trying to root my phone with Supersu I got stuck into this bootloop.
So what happened?
I flashed TWRP on my phone.
Once in TWRP I tried to install Supersu but unfortunately I couldn't find the zip file.
I restarted my phone.
This time I downloaded Supersu and put it in a location I would be able to find.
Once again flashed TWRP.
Got into TWRP.
Had to decrypt by password which I was unable to do.
So now TWRP was unable to read my internal storage (0mb internal storage).
Reading the forums I ended up backingup my device.
Then used the formatting function in TWRP.
Restored back my backup.
Still couldn't find the Supersu file.
Rebooted to stystem.
Now whatever I do I can't get out of Fastboot Mode.
Tried adb command: Fastboot reboot
No results.
I believe that I somehow should get the stock ROM (?) on my phone?
Fixed it!
Used adb to push the Supersu download to my phone in recovery. After that everything worked!

Stuck in fastboot, did I brick my phone?

Hey there,
sorry, noob here.
Trying to get an old Redmi 7A up and running again:
Unlocked the bootloader
entered fastboot mode
flashed TWRP
booted successfully into TWRP
wiped data
rebooted into twrp
wiped system, data, dalvik and cache
twrp is gone, stock recovery returned
reflashed twrp
fastboot reboot recovery
back in fastboot
power off, power on
automcatically back in fastboot
I cannot access anything but fastboot now.
What am I missing, what did I do wrong?
Thank you very much!
If you're stuck into fastboot try reflashing the stock rom from the official xiaomi site here
Select the fastboot version of your rom, then use MiFlash Tools to revert back your rom using the flash_all_lock.bat file.
To make miflash to work I had to add a log folder and inside an empty [email protected] file before launching it otherwise you'll get errors.
i think your mistake was wiping before installing custom rom. Follow the instruction closely

Categories

Resources