Hi guys,
I converted my GSM HTC one (international) to the google play edition following the instructions in the official thread (4.4.2). I used CWM to root and moonshine for S-Off. I installed the stock (non rooted) version.
The phone boots normally and everything seems to work, except that recovery doesn't work anymore. (This is the screen i get)
Is this because I installed a non rooted version?
Basically after this conversion I don't really need root anymore, all I wanted is google play edition, I do not have further need to run apps that require root. (and I would like to receive future ota's). If all goes well I'll never see the fastboot menu again, but even though I'm done modding it seems risky to leave the recovery non working. Any suggestions?
That's no special
You only must flash a recovery with fastboot again
You flashed a RUU this include the system, the Hboot and the revocery. On your picture you see the Stock recovery of Vanilla Android
Mucky2 said:
That's no special
You only must flash a recovery with fastboot again
You flashed a RUU this include the system, the Hboot and the revocery. On your picture you see the Stock recovery of Vanilla Android
Click to expand...
Click to collapse
Ok, thanks for the info. But why doesn't the stock recovery work anymore then? Why is this normal?
Which recovery should I flash next?
Just flash the latest TWRP 2.3.6.4
Gesendet von meinem One mit Tapatalk
Hi everybody,
after reading about how to upgrade & root the Xperia SP on the 4.3 firmware I followed the guides to get everything set up.
Now, after being nearly there I'm stuck with a black booting screen.
Here follow the steps I did undertake so far, any help to resolve my issue would be very welcome.
I started with firmware 12.0.A.2.245 rooted with Doomlords method (flash old kernel, root, flash .245 kernel again)
1 backup contacts/messages etc
2 do TA partition Backup with Backup-TA
3 update firmware using PC-Companion
4 unlock bootloader with official sony guide
5 fastboot flash cwm / superSU
---> everything worked fine so far (phone was operational), now I wanted to get the screen mirroring working - meaning the bravia engine. So I went for
6 Backup-TA check backup integrity with dry restore
7 Backup-TA restore TA partition
last step of the restore was: reboot device, which got me to the black screen - which is where I am stuck now.
All I managed so far is entering the fastboot mode, I could confirm this working by issuing a "fastboot devices" which listed the phone as available.
Anyone got any ideas to what went wrong and how to fix this?
update: after going through the unlock bootloader procedure again the phone boots normally again ( fastboot.exe -i 0x0fce oem unlock 0x[...] ) . Now the last problem is getting the TA partition back.
Is this even possible while keeping root?
Flash stock kernel .266 before restoring TA partition.
go to flashmode and flash the kernel.ftf, links of which can be found by searching.
this problem has been posted as FAQ in Bootloader unlocking relocking thread.
Thanks! I'll try this. I thought you only had to reflash the stock kernel if you wanted to relock the bootloader
Hi.
I have an XT1092, i turn it into XT1095 and flash the Lollipop OTA, everything ok, and works fine but......
Now i flash TWRP (to restore my EFS, and did it) and i can enter into my recovery but when i restart my phone i loose the TWRP recovery ¿?, i need to flash it again (and with the stock recovery i have the same problem)
So, if i want to hace a recovery i need to flash it, enter and work on it, because if a restart the phone i can´t.
What can be the problem with my recovery? i can enter in it.
thx
Not sure with TWRP but the stock recovery has changed. It is not at the green damage android you hold power for a couple seconds then tap volume up.
Sent from my XT1095 using Tapatalk
thx
works¡¡¡ with the stock recovery, thx a lot dude
Glad I was of some help.
Sent from my XT1095 using Tapatalk
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