I've got a quick question and need some help please.
I've got a stock unlocked g5 plus that I'm going to root but before I do I want to back up my recovery partition. When I use fastboot to boot (not flash) twrp I can't mount anything or run the backup. Is this because it's encrypted? Just wondering what the correct way to do this is.
Can't boot into TWRP
I restored my RR 5.8.4 and cant authenticate, i looked for soluions but all i can see is booting into twrp and deleting the specified files. Problem is i cant get into recovery. Long press on the homescreen just reboots my phone, brings me back to the lockscreen. Can somebody please help me out?
Edit: Through the lockscreen i can see that USB debugging is enabled. Any hopes with ADB?
Related
Heeelp
I tried to install Cataclysm ROM, and then it went into some sort of installer, after that I tried to reboot, but TWRP said it didn't have any OS?? So i tried to boot it up anyway? but nothing, just stucked on Google Logo. After that I tried to boot into TRWP agian. But then TWRP says "Mount Decrypt Data" and then i have to enter a password?? but i removed my pattern lock before flashing. Because i made a Nandroid and i read i had to remove the password before making a backup. But then i just press cancel. Then it says " Unmodified System Partition" "Swipe to Allow Modifications" and i do that. Now i have nothing on my SD card?? Then i thought i could flash stock through Fastboot/ADB, but now it won't see my device in ADB? I have updated my drivers, both by Google and Intel (Read they helped someone else) But nothing? so i cant retutn to stock and can't boot up.
Please help, highly appreciated
Some how i got i to reboot by an ADB command and then i could flash factory imgs and return to stock.
That very same thing happened to me the 1st time I tried to install Cataclysm. Somehow my SD card got wiped.
I had to start from scratch with the factory image.
I don't know what happened but I have since successfully installed Cataclysm.
I need some help.
Last night I was updating to lineageOS' new nightly update with TWRP in recovery mode. I also like to run a custom kernel on of that for battery life reasons. In doing so, I mindlessly flashed the custom kernel (blackscreen 3.6.2) to the system image partition instead of the boot partition, then went back and flashed SuperSU, wiped the cache as I normally do.
My problem is that when I rebooted the phone it hangs on the stock LeEco boot logo without going past it. In addition I cant get it to go into fastboot or recovery no matter what button combination I use. In addition, I can't get adb or fastboot to detect it from my PC to do anything from there either. My PC does detect a "Portable Devices", listed as a D:\ drive, but this isn't helpful.
I could really use some help. I'd hate to think I bricked my phone with such a mindless mistake. If you know what's up or another post that can help me, please post it.
Pls disregard this post, I managed to boot into recovery when I plugged it in to my PC and turned it on with volume up and power
BlocforLife said:
Pls disregard this post, I managed to boot into recovery when I plugged it in to my PC and turned it on with volume up and power
Click to expand...
Click to collapse
thanks,bro.I have same problem, it work for me.
I have the MetroPCS xt1765 running lineageos 14.1. When unlocking and doing all that jazz, the guide said that you can't flash twrp, only boot it. But I got annoyed that /data wouldn't mount so I just tried to flash it anyway and it worked. On cmd it said that the file wasn't signed or corrupt, but it still wrote to the device. I thought nothing about it at first but when I tried to boot the device it automatically when into twrp. I tried to reboot to system again, and the same thing happened.
Eventually /data successfully mounted and I was able to format it and install linage. I hoped that would fix the problem but it's still there. I believe I would need the stock boot image and probably stock recovery as well. I hope someone out there has these files.
Also when booting with factory mode, my data isn't working at all. The apn setting are right and all, but it's not working.
ZacharyTheUmbreon said:
I have the MetroPCS xt1765 running lineageos 14.1. When unlocking and doing all that jazz, the guide said that you can't flash twrp, only boot it. But I got annoyed that /data wouldn't mount so I just tried to flash it anyway and it worked. On cmd it said that the file wasn't signed or corrupt, but it still wrote to the device. I thought nothing about it at first but when I tried to boot the device it automatically when into twrp. I tried to reboot to system again, and the same thing happened.
Eventually /data successfully mounted and I was able to format it and install linage. I hoped that would fix the problem but it's still there. I believe I would need the stock boot image and probably stock recovery as well. I hope someone out there has these files.
Also when booting with factory mode, my data isn't working at all. The apn setting are right and all, but it's not working.
Click to expand...
Click to collapse
When it was booting to twrp only, you just select reboot bootloader and in bootloader select start and you will get system. This twrp doesn't read and clear bootloader control block (BCB) properly which causes this. There is a fix. I'll find the link.
Do you mean fastboot/bootloader mode? If yes, try this
Hi everyone, I tried to use this guide to root my phone.
Can confirm it's International, so Exynos.
Used Odin 3.12 and TWRP image 3.1.1 for hero2lte, which is the correct version.
Everything flashed perfectly - Got the OK from Odin, so can't see any problems that side.
Now the problem I'm getting:
When booting into recovery, I get installing updates... then 'No command' screen, like in this thread
I have factory reset via the recovery I DO have (I don't think this is TWRP, there's no touch interface, and it's all controlled via volume + power keys). This allows me to boot into the OS.
I have the option to boot into bootloader, and this takes a little while to do, but seems to fail and boot into the OS anyway.
I have no way of trying to reflash TWRP that I'm aware of, and I'm kinda stuck... could anyone help me from this point on please? Thank you!
EDIT: I'm trying to install custom ROMs and tweaks (Not sure if things like busybox/gravitybox/xPosed framework etc. exist anymore - haven't touched custom stuff for 3 years now! If you know, please let me know too!) So are there OTHER steps I should be aware of/know if I wanna proceed?
(just posting reply so I can see this thread later on, gonna do the same thing after exams, if I get same issue, this will be helpful)
P.S: By the way, when flashing TWRP, deselect auto reboot and see if you can go to recovery without booting it first. Sorry can't think of more options :S
after disabled auto reboot, then holding vol up and home and boot it booted to twrp.
Flash each of the checkboxes individually or it will send you back to download mode
Only one checkbox at a time also make sure ur oem unlock is enabled
Hi everybody. I need a little help here. I bought used LG G6 to practice installing custom roms. So I unlock bootloader and now I trying to install TWRP (at this moment without root beacuse obviously with my luck on my phone doesnt work any program like kingo ROOT or something like this) and when flashing recovery with ADB is done I unplugg smartphone and enter to menu with wipe all data because in every corner in internet I was people say when I choose ..Yes" twice then TWRP would launch. Not this time. And whats strange that when I boot smartphone normally then all the data is still on it. Power key+volume down doesnt do anything, volume up too. I dont know what to do next.
My answer may be too late but it sounds like the recovery you flashed is broken in some way.
When I installed my custom recovery I had to enter into recovery IMMEDIATELY after flashing the recovery image from terminal, in fastboot mode. Upon entering the recovery I had to install a .zip file named "no-verity-opt-encrypt.zip". This is the .zip that prevents the recovery partition to be reflashed by the phone's OS back to stock. This "back to stock" flashing is done by the OS at boot time. If you fail to boot into recovery and let the phone boot up before installing the .zip, you may have the experiences you just described. I'll search for the thread I followed.
Edit: Here is a thread I found useful:
Wich twrp actually work on h870?
Hello. I've been trying to get twrp(official) working on h870 for some time. The only version that at least boots up is 3.1.1.0 I know that in order to make it "stick" I have to flash magisk or custom rom. However I don't want to do that prior to...
forum.xda-developers.com
And here is the one I *probably* followed:
https://forum.xda-developers.com/t/recovery-twrp-v3-2-3-1-for-h870-h872-us997-unofficial.3828254/
Sadly I can't say 100% sure if it was the thread I followed back in the day.