i have a symphony roar a50 (Bangladesh). it was running everything stock and updated with twrp 2.8.7.0 without root. bootloader was unlocked.
i was trying to root the device with the AIO from this thread:
http://forum.xda-developers.com/cro.../android-one-toolkit-unlocks-relocks-t3294448
the phone suddenly rebooted in the middle of the process and was stuck in a bootloop. i tried to factory reset it but it still didn't work. was still on boot loop.
then i tried to flash the appropriate stock firmware but that didn't help it wont boot. stuck on the boot logo for 1.5 hrs. then tried CM13 nightlies and the cyanpop roms. still nothing.
i am currently in a state of shock as this is a fairly a new phone and i am to travel to Chittagong in ~11 hours.
please help
don't you take a backup ?
and don't you wipe every thing before flashing the cm13 ?
mithun mpk said:
don't you take a backup ?
and don't you wipe every thing before flashing the cm13 ?
Click to expand...
Click to collapse
yes i had a nandroid backup. but twrp says it is corrupt or some reason. and yes i wiped everything before cm13
downgrade twrp2.8.7 to 2.8.4.... 2.8.7 has problem with backup and recovery
https://www.androidfilehost.com/?fid=24389512218018336 twrp 2.8.8.x beta 3
btw this thread is wrong section
I too Had the same Problem once as I Tried Rooting My Android One through the same method as u did, So for fixing it I prefer that U FLASH The Stock MM ROM for Ur Device through STOCK Recovery ( Remember to Wipe Cache and Data b4 Flashing ) AND then ur Device mst be Fixed ( This method worked for me ) And Dude if u want to root Ur Device Follow This Method : -
1) FLASH TWRP RECOVERY
2) Reboot into Recovery and FLASH Thunderzap 5.1 Kernel through Recovery
3) Then FLASH SUPERSU ZIP from Recovery
4) Reboot And Done ! Ur Device is Rooted ! ?
@RoxAndroid how did you fallback to stock recovery from twrp? I'm stuck.
Tanzim Abir said:
@RoxAndroid how did you fallback to stock recovery from twrp? I'm stuck.
Click to expand...
Click to collapse
So......to do that Follow these Steps :-
Download Stock Recovery from here http://forum.xda-developers.com/crossdevice-dev/android-one-general/stockrecoveryandroid-one-t2917457
1) Make sure u have Installed ADB drivers ( If Already did, Skip Step 2)
2) To install ADB drivers first Unable USB debugging From the developer Options in the Setting ( If there is No Developer Options Goto-Setting-About Phone-Tap Build Number 7 Times and go back to settings and Open Developer Options and Unable USB debugging) And then Connect Your Phone to PC and Open ADB DRIVER executable File And Install Drivers.
3) Once Drivers are installed Download ADB AND FASTBOOT from here http://drive.google.com/file/d/0B1nu6Ydzrmi-dWdmS00tWjE1WHM
4)Extract the zip and open the folder and then HOLD SHIFT+Right Click and then click on Open Command Window here
5)And then boot your phone to Fastboot Mode, To do that Power Off the Device and HOLD POWER AND VOLUME UP key at the same time and then navigate to the Fastboot Mode by Volume UP button and and Click Volume Down button to select. Once you are in Fastboot Mode connect your Device to PC and go back to PC
6)Once Command Window is opened type following Command :-
Code:
fastboot devices
Code:
fastboot oem unlock
Code:
fastboot format userdata
Code:
fastboot flash recovery <Name of the Recovery in ur PC>
Code:
fastboot boot <Name of the Recovery in ur PC>
6) DONE ! STOCK RECOVERY IS FLASHED and Remember to keep Stock Recovery img file in the ADB AND FASTBOOT FOLDER
Thanks I'll try this asap currently on a train..
Okay.. I've shipped it to the customer care. They said I'll have to wait 3 days for it to get back. I'll report back then.
Thank you everyone for your input.
Closed as this has run its course.
Hi,
Few days ago I bought used Nexus 6, which was come with locked bootloader and stock Android 7.1.
I wanted to flash some custom ROM. First I tried to unlock a bootloader.
I was using an XDA Video Tutorial showing how to unlock and root the Nexus 6 and a tutorial on LineageOS site. I could unlock the bootloader quite easily but unfortunately I forgot to reboot the device (eg. with command "fastboot reboot") and I strightly tried flash a custom recovery.
It flashed well (as described in command line window) but couldn't get into TWRP recovery. Device showed dead green android with description.
System is booting normal and the bootloader is unlocked. But unfortunately I can't flash the custom recovery. I reinstalled all android drivers (I installed full Android Studio with packages suggested by the tutorial). After flash there is no custom recovery - still dead android and possibility to launch stock recovery. Once I could launch TWRP, when I do not reboot phone after flashing recovery and strightly go to recovery (from bootloader). But when I reboot to system and try launch TWRP again - again no custom recovery...
There is also a problem when I try to root the device using CF-Root - it shows some error and device is still not rooted, also without a SU icon in system.
Is there any solution for that? Are these problems a reason of my mistake with not rebooting the phone after unlocking the bootloader?
Thanks a lot for any suggestions and help. If it necessary I can update my post with more details.
Wysłane z mojego Transformer TF101 przy użyciu Tapatalka
Well, the first thing that stands out is you using CF-Autoroot. Kind of putting the cart before the horse there. Also unnecessary, for once TWRP is installed you can simply flash a root solution through it.
Anyway, when you have the N6 in bootloader mode, what happens when you type "fastboot flash recovery recovery.img"? Any error messages? The output of the command will be useful here.
The fact you didn't reboot between commands does not mean you did any damage. Simply start over again.
I am adding photos of bootloader and command line windows after flashing the recovery. It looks that there aren't any errors.
Maybe this is happening because of encrypted device? I saw that my phone is encrypted but i don't doing this before, I restored it to factory settings.
Your images are unreadable. Perhaps it's my data connection.
Encryption has nothing to do with this. Regardless, if you didn't see any errors, what happens now when you enter the bootloader, scroll down to recovery mode, and press power?
OK, I add this images again and I hope it would be readable now.
When I entered the recovery from bootloader a dead android appears with description "No command" below. Then I could press and hold the power button to reboot the device or press and hold for a second VOL+ and POWER to enter the stock recovery...
Maybe your twrp is installed correctly, and you just use the wrong method to start it?
The best way to start it is to reboot with all buttons pressed, and then select recovery.
Edit: didn't see you new post
Hmm, maybe something is wrong with the drivers and maybe with Windows. Maybe I will try flashing recovery on Linux.
I'll tell you right now, nothing is wrong with the drivers. Apparently you typed everything correctly, but humor me on this one please? Rename your TWRP image from its current name to "twrp.img", then flash it via fastboot. What I'm trying to see is if a potential keypunch error is causing your problem. "fastboot flash recovery twrp.img" is a lot easier to type than the default.
Also, what happens when you execute the command, "fastboot boot twrp.img"?
Your bootloader screen looks like mine, except that your serial number has a different structure.
Mine is dd123456 (real numbers replaced). Notice the small letters at the beginning, whereas yours has capitals mixed with numbers, and is longer.
I don't know if we can conclude anything from that.
@runekock: You can't. Mine is ZY222***** and installing TWRP here has never been a problem. I'm almost certain this is a simple userspace issue.
After flashing TWRP are you going directly into recovery mode before rebooting? I seem to recall that some ROMS will replace a custom recovery with the stock recovery unless you boot in to TWRP before booting into the OS.
I have already tried many combinations like flashing older versions, renaming (twrp.img and recovery.img) and rebooting device after flashing or going strightly to recovery after flashing. Only the last option could launch TWRP recovery, but even if I swipe to allow modifications the recovery is missing after reboot. It looks exactly like the original stock ROM is still replacing this custom recovery.
I also tried flashing on Linux and without any changes. I also tried updating recovery on my old Moto G and it was succesful operation - so it is probably not a problem with a computer or with drivers.
Maybe I should do something like that - flash TWRP, go to it directly after flashing, copy custom ROM or SuperSU file to the memory, wipe and flash ROM or SuperSU. Maybe that could help? What do you think, is it safe to try?
Wysłane z mojego Transformer TF101 przy użyciu Tapatalka
fastboot boot recovery.img doesn't install the recovery, but does let you conduct recovery operations on the device. In this case it also verifies that the TWRP image isn't somehow corrupt.
Unfortunately, after confirming that there's nothing at fault with the PC, nothing at fault with ADB and Fastboot, and nothing at fault with the device itself, the only thing that is left is...you.
If you haven't taken a look at the Nexus 6 All-in-one Flashing Guide in Nexus 6 General, I suggest you do so. It's a very good thread and has a lot of advice that might be useful to you.
In this guide there's the note about how important is rebooting the device after unlocking bootloader...
But I see on the Internet similar problems as mine.
0sA said:
I have already tried many combinations like flashing older versions, renaming (twrp.img and recovery.img) and rebooting device after flashing or going strightly to recovery after flashing. Only the last option could launch TWRP recovery, but even if I swipe to allow modifications the recovery is missing after reboot. It looks exactly like the original stock ROM is still replacing this custom recovery.
I also tried flashing on Linux and without any changes. I also tried updating recovery on my old Moto G and it was succesful operation - so it is probably not a problem with a computer or with drivers.
Maybe I should do something like that - flash TWRP, go to it directly after flashing, copy custom ROM or SuperSU file to the memory, wipe and flash ROM or SuperSU. Maybe that could help? What do you think, is it safe to try?
Wysłane z mojego Transformer TF101 przy użyciu Tapatalka
Click to expand...
Click to collapse
Occasionally I have had the same issue of the ROM replacing TWRP with the stock recovery. At that point I just do:
adb reboot bootloader
fastboot flash recovery recovery.img (twrp renamed to recovery.img)
adb reboot bootloader
press the down arrow twice to reboot into recovery
I DO NOT allow modifications
select reboot and reboot into recovery again
select reboot and boot into the OS (reboot system)
Some of those steps may not be necessary but that is what has worked for me.
It looks like I found a solution. I flashed TWRP, reboot bootloader and entered recovery directly from bootloader. I copied Chainfire's SuperSU to the phone, unplugged it from PC and flashed this SuperSU (and also wipe cache after flash). Reboot the phone and system is rooted! I updated TWRP Official App from Play Store and permited root privileges, downloaded latest TWRP recovery and flashed it from this app. When I entered the recvery (from bootloader) it was TWRP! Even if I reboot the device, the TWRP recovery seems not missing.
Wysłane z mojego Transformer TF101 przy użyciu Tapatalka
Hello,
I tried the latest V11.0.6.0.QFAEUXM ROM but I didn't like it and so I booted into my TWRP recovery and restored the latest fullbackup I made from 2 days ago, then rebooted.
Now I'm stuck in Fastboot loop.
$ fastboot reboot
and
$ fastboot reboot recovery
... have literally no effect, still the phone is stuck in fastboot mode uppon restart.
I read in another thread "just use MiFlash tool and revert to stock rom, do everything all over to rescue your phone".
OK, fine. I start MiFlash, it asks me to unlock my phone... I click unlock. Nothing happens, I click again "try unlock again", then "no need to repeat unlock" appears, nothing happens, the usual menu with the options to flash or install TWRP are missing.
:good: really good! Just as expected. Very user friendly.
Now what?
I had twrp-3.3.1-37-cepheus-mauronofrio.img (SHA-1: A3230E7918A9E3D3D939AA8619B40E47A54F645D) as recovery and my ROM was xiaomi.eu_multi_MI9_V11.0.4.0.QFACNXM_5e64190eb9_v11-10.zip (SHA-1: 714BD02A5D52720C2733E2FDA9730EECE441AE09) before I tried to flash miui_CEPHEUSEEAGlobal_V11.0.6.0.QFAEUXM_1647340073_10.0.zip (SHA-1: BAC6307DA99F766E35A6EDBB0B74D02F73AD2782) and everything went downhill from there.
MiFlash version: miflash_unlock-en-3.5.719.27.zip
Is there more info I can provide?
EDIT / UPDATE:
I've been following the instructions from a Youtube video (links below) by the letter and now at least I'm back in a sane / stock ROM state where I can (have to) redo everything fromm the beginning.
Sources:
https://www.youtube.com/watch?v=GuAHNFjK--o
Instructions:
https://highonandroid.com/android-s...rick-unroot-xiaomi-android-stuck-on-fastboot/
Download site:
https://xiaomifirmware.com/roms/download-official-miui-roms-for-xiaomi-mi-9/
(I downloaded & used "cepheus_eea_global_images_V10.2.17.0.PFAEUXM_20190327.0000.00_9.0_eea_b2470d1b08.tgz")
I chose "clean all" as flash method in that XiaomiMiFlash Tool.
It will reboot into Stock ROM, in my case I chose the EU version.
From there you can activate Developer Options & USB-Debugging again and you're set to go customizing again.
Ohhh looks not amazing
Did you've tried to flash recovery via adb?
Laptapper said:
Ohhh looks not amazing
Did you've tried to flash recovery via adb?
Click to expand...
Click to collapse
I tried:
$ fastboot flash recovery twrp-3.3.1-37-cepheus-mauronofrio.img
$ fastboot reboot recovery
It boots straight into Fastboot again.
I don't even know what to say at this point. I literally only wanted to restore a fullbackup. How can this possibly happen in the first place?
I'm really close to smashing this phone in 1000 pieces...
anthropaki said:
I tried:
$ fastboot flash recovery twrp-3.3.1-37-cepheus-mauronofrio.img
$ fastboot reboot recovery
It boots straight into Fastboot again.
I don't even know what to say at this point. I literally only wanted to restore a fullbackup. How can this possibly happen in the first place?
I'm really close to smashing this phone in 1000 pieces...
Click to expand...
Click to collapse
What I suggest you to do is flash the latest TWRP from Mauronofrio which is 3.3.1-52.
After successfully flashing the recovery, immediately press vol up + power button until it reboots.
Do not reboot using the command line or turn off your phone.
In TWRP, flash the xiaomi.eu ROM version that your backup is based on.
Then perform a restore from the backup that you had made.
Sent from my MI 9 (Cepheus) using Tapatalk
Thanks, but I fixed it already.
As I described / updated in the OP there is a tool with which you can use some firmware roms in tgz format to flash over the fastboot state to get a "stock rom-ish" state back.
Once in the stock rom you have to go through the basic setup routine and then activate USB Debugging, then you can install TWRP, other Roms as per usual.
I followed the steps mentioned in the below link to root my Mi 5 phone and now my phone is stuck with Mi logo upon reboot to system.
rootmygalaxy.net/root-xiaomi-mi-5-install-twrp-recovery
Things I did:
1. Enabled USB debugging and OEM unlock option
2. Installed ADB v1.3
3. Unlocked bootloader using mi 5 flash unlock tool
4. Downloaded twrp-3.2.3-0-gemini and renamed as twrp.img
5. Installed twrp recovery via fastboot using the following commands
adb reboot bootloader
fastboot flash recovery twrp.img
fastboot boot twrp.img
6. Copied SuperSU-v2.82-201705271822 to phone's internal memory
7. Booted device into twrp recovery. Under wipe option, did a factory reset. Installed SuperSu successfully. Clicked 'swiped to wipe' under wipe cache\delvik.
8. Then rebooted to system from twrp main menu
After the above steps, my phone didn't reboot and got stuck in Mi logo. This is the first time I tried rooting my phone .
Could you please suggest some idea to recover my phone? Thanks in advance.
It's likely not a big deal at all. Look up putting your device to EDL mode and flashing stock image with xiaomiflash. If you choose the correct stock image, everything will be fine.
I'm getting stuck on fastboot mode everytime i flash derpfest rom , i've tried ''fastboot reboot'' i've tried to install ''twrp'' or boot to it , nothing works everything i try takes me back to the fastboot logo although the install of the rom was succesfull , i've tried with TWRP-3.3.1-8-siankatabg and also with regular TWRP and also with ORANGE FOX recovery , i'm on miui 11.0.7 EU version , can anyone help me
In TWRP, format data and then flash derpfest ROM. Take note that your data will be wiped though.
sangbuana said:
In TWRP, format data and then flash derpfest ROM. Take note that your data will be wiped though.
Click to expand...
Click to collapse
I did just that I placed the ROM in /tmp/ using TWRP file manager then I formated system and cash and data and then I did the data format by writing "Yes" then went back and erased everything a second time for good measure but still after flashing the ROM I get stuck on fastboot with no ability to boot to recovery or use commands like "fastboot reboot" the only solution for me that time is to reuse mi flash to flash stock rom which doesn't work but lets me boot into recovery which i use to flash miui 11.0.7 zip which apparently works just fine .
Also the basics are covered I made sure to allow usb debuging and update TWRP and all of that
1. flash using miflash
2.setup ur phone
3.enable dev optmake sure oem unlock too
4.going for twrp
5. wipe
6. flash ur rom
7.dont go reboot to system
8.format data then rebot to system
In case nothing else helps you can try to flash vbmeta first, following these instructions.
Cheers
Toscha