I had some issue with twrp and it got stuck on The teamwin screen. So I restore lg os using the lg flash tool. After I update it to lollipo and install autorec d852 lollipop so I can install twrp. It install succesfully. I went on twrp and the problem started. It was stuck on it. I decided to get into fastboot mode by removing download mode ( I have a back up of it) and I did these following commends
Fastboot erase recovery
Fastboot flash recovery cyanogenmod 12.1 recovery for d852..
I flash the cyanogenmod recovery so I could install a aosp. I install cm13 and it damage my micro SD card. I finally fix it . After I flash blisspop because it was limited the customization of cm13 compare to other aosp roms. Once finish setting up everything on my internal storage, I tried flashing again twrp by auto rec ... It didn't work , so I tried flashify but it also got stuck on teamwin screen and I could access anything option. I started looking online if someone had experience something similar but no one had this type of problem that after doing a full reset and reinstalling it, it wouldn't work. So I went on fastboot mdoe ( I don't know how to get download mode back so I stuck in fastboot mode instead of download mode ) and did the previous comments that I did to flash cyanogenmod and I flash the cyanogenmod recovery because I need a working recovery. Since then I have been trying to fix the teamwin screen problem.
I NEED HELP WITH MY 2 PROBLEMS.
-I can't find a way to enter download mode again
- Can't get twrp to work
Someone help me please
Related
I installed CM 11 on my Xiaomi redmi 1s,everything was working fine except for 2 or 3 little things but a major problem occurred when I thought of flashing another ROM and now I CANT ACCESS RECOVERY MODE no matter what I try. I tried the button combination(power switch+volume up), tried adb and even tried apps like ROM Manager and, TWRP Manager and quick boot but haven't found any luck. Whenever I try to boot into recovery the phone gets stuck on the MI boot logo. I need to flash another rom and can't seem to find any other way to wipe y phone data, cache and dalvik cache and so I need help to counter this issue.
Please help me.
Dishagra said:
I installed CM 11 on my Xiaomi redmi 1s,everything was working fine except for 2 or 3 little things but a major problem occurred when I thought of flashing another ROM and now I CANT ACCESS RECOVERY MODE no matter what I try. I tried the button combination(power switch+volume up), tried adb and even tried apps like ROM Manager and, TWRP Manager and quick boot but haven't found any luck. Whenever I try to boot into recovery the phone gets stuck on the MI boot logo. I need to flash another rom and can't seem to find any other way to wipe y phone data, cache and dalvik cache and so I need help to counter this issue.
Please help me.
Click to expand...
Click to collapse
Flash any custom recovery via fastboot mode
Download .img format of custom recovery
Boot into fastboot mode n run this command on CMD
fastboot flash recovery <filename>.img
Filename can be anything depending on name of image file you download
Not Working for me
RajGopi said:
Flash any custom recovery via fastboot mode
Download .img format of custom recovery
Boot into fastboot mode n run this command on CMD
fastboot flash recovery <filename>.img
Filename can be anything depending on name of image file you download
Click to expand...
Click to collapse
I am afraid this solution doesn't work for me. My thoughts are that I have somehow lost my recovery partition. I accidently installed CM 11 without first installing a custom recovery. My bad! but have yet to find a solution that works.
Try flashing a recovery using Rashr-flashtool
And boot to recovery (Vol up + Power , for 10s even after screen is on )
Solved
Shahi00 said:
Try flashing a recovery using Rashr-flashtool
And boot to recovery (Vol up + Power , for 10s even after screen is on )
Click to expand...
Click to collapse
I solved my problem by using Flashify app but I had to use it every time as recovery would not stick. I flashed trwp and installed stock (english version) rom and stock recovery and everything is working fine again. I will not make the same mistake again. I have since installed CWM recovery through stock recovery so now I can flash roms in peace again.
Waxwrong said:
I solved my problem by using Flashify app but I had to use it every time as recovery would not stick. I flashed trwp and installed stock (english version) rom and stock recovery and everything is working fine again. I will not make the same mistake again. I have since installed CWM recovery through stock recovery so now I can flash roms in peace again.
Click to expand...
Click to collapse
i have the same problem how to solve it please describe it briefly ^^
Edit:
I installed some LG Drivers from a root article and now the phone is recognized. I can update to V20G and test it again, hope it works!
Hello!
I was running CM14.1 on my LG G4 and a few days ago I decided to install a new update but from within the phone itself. Sadly, it just rebooted to the recovery and didn't install anything. And from there, it always rebooted into the recovery no matter what I did. I also did a full wipe and installed CM14.1 clean but it still rebooted to the recovery and didn't want to go past that. I made a Reddid thread - https://www.reddit.com/r/cyanogenmod/comments/5gcap3/g4_h815_cm_141_help_i_cant_boot_outside_of/.
So I got help with that - I got into Download Mode and flashed the stock software via LGUP. Sadly, after I did this, I can no longer install a custom recovery. The phone is not rooted and LGUP and LG Bridge don't recognize the device anymore and the phone says there isn't a new update available but it's on the 5.1 stock ROM.
Whenever I flash the TWRP image via fastboot and I reboot into recovery, it doesn't boot into TWRP but it boots into some kind of other fastboot mode. And I've tried to issue `fastboot boot twrp-x-x-x.img` but it fails to do so and shows `FAILED (remote: dtb not found)`.
Is there a way to fix this so I can flash CM again?
Thanks in advance!
Peshyy said:
Hello!
I was running CM14.1 on my LG G4 and a few days ago I decided to install a new update but from within the phone itself. Sadly, it just rebooted to the recovery and didn't install anything. And from there, it always rebooted into the recovery no matter what I did. I also did a full wipe and installed CM14.1 clean but it still rebooted to the recovery and didn't want to go past that. I made a Reddid thread - https://www.reddit.com/r/cyanogenmod/comments/5gcap3/g4_h815_cm_141_help_i_cant_boot_outside_of/.
So I got help with that - I got into Download Mode and flashed the stock software via LGUP. Sadly, after I did this, I can no longer install a custom recovery. The phone is not rooted and LGUP and LG Bridge don't recognize the device anymore and the phone says there isn't a new update available but it's on the 5.1 stock ROM.
Whenever I flash the TWRP image via fastboot and I reboot into recovery, it doesn't boot into TWRP but it boots into some kind of other fastboot mode. And I've tried to issue `fastboot boot twrp-x-x-x.img` but it fails to do so and shows `FAILED (remote: dtb not found)`.
Is there a way to fix this so I can flash CM again?
Thanks in advance!
Click to expand...
Click to collapse
The bootloop to recovery is a known issue of one the December nightlies of CM 14. Head over to the CM thread and search for bootloop and twrp. They provided a solution to solve this too.
Besides that: which twrp version do you tried to fastboot? H811 or h815? Taken from the official download site?
.
steadfasterX said:
The bootloop to recovery is a known issue of one the December nightlies of CM 14. Head over to the CM thread and search for bootloop and twrp. They provided a solution to solve this too.
Besides that: which twrp version do you tried to fastboot? H811 or h815? Taken from the official download site?
.
Click to expand...
Click to collapse
twrp-3.0.2-1-h815.img, H815 as the title says and from the official website as I've always done. As for the thread - I don't have TWRP and I can't even flash it as I've written in my post. That's what I'm struggling with.
Edit:
I installed some LG Drivers from a root article and now the phone is recognized. I can update to V20G and test it again, hope it works!
Hello, I flashed CM14 Nougat 7.1.1 and everything worked fine until I tried to boot into recovery to get access to TWRP. If I try and boot into recovery I get the 1+ logo and then just a black screen and i have to hard reboot the phone to use it again. After the hard reboot it just goes back to nougat. I downloaded the TWRP APK to try and restore my previous save but it just does the same thing.
Can anyone help?
Thank you.
I get the same problem. This is WHY we should BACKUP it first. but I didd't, and so are you. I was having lots of works and did not check much news about CM for a long time. but yes, I get the rumors about CM getting shut down. and I check the news. Today I found out CM is shutting down, and my phone is not working.
But, hey, who am I. OnePlus 3 User with lots of experience.
So I tried CM recovery, the newest version works, but there is no backup option, I tried old CM13 recovery. it also black screen. This confirm my theory, this is due to Android 7.1 or CM14.1 upgrade
How to solve this problem?
I found this
https://forum.xda-developers.com/oneplus-3/development/rom-hydrogenos-h2os-beta-edition-oct-t3482259
go to this thread, and download modified TWRP.
BACKUP.
Install your new ROM via any XDA rom. not the CM14.1 build on Dec 25.
Note: If you want Android 7.xx, you could flash the Official Beta ROM(above), or download modem from
https://forum.xda-developers.com/oneplus-3/how-to/radio-modem-collection-flashable-zips-t3468628
Happy New Year.
YungKremer said:
Hello, I flashed CM14 Nougat 7.1.1 and everything worked fine until I tried to boot into recovery to get access to TWRP. If I try and boot into recovery I get the 1+ logo and then just a black screen and i have to hard reboot the phone to use it again. After the hard reboot it just goes back to nougat. I downloaded the TWRP APK to try and restore my previous save but it just does the same thing.
Can anyone help?
Thank you.
Click to expand...
Click to collapse
boot into fastboot mode and give following commands
fastboot erase recovery
fastboot flash recovery twrp-xxxx.img
now reboot to recovery...
Please confirm if this works
I was running an unlocked one plus 3 on OxygenOS 4.0.2 (Android Nougat) and have TWRP installed. As 4.0.3 got released yesterday, i tried installing it today but i accidentally hit install on the OTA update setting which caused my phone to reboot. Now my phone won't boot into the os, i get a black screen after 'powered by Android'. I tried getting into Recovery however i get the same response, a black screen. I do not think it is hardbricked as the Fastboot still works and when i go into fashtboot it states that the OEM is 'unlocked'. I have personal data on this device pls can someone help. I do not know what i should do> How do i boot into recovery without crashing?
Is it possible to install twrp again with the PC? I had once also the same problem, install it again and after that it booted again into recovery.
Just install TWRP from fastboot, then you'll have access to internal storage by TWRP
It's happening because it's trying to send you to recovery which is twrp 3. 0.4-1which is bugged so just go to fastboot and flash twrp 2.0.4-1 and then try booting in.. You can even update the phone by flashing the update zip by oneplus from recovery
Hello,
I'm sorry if this is a retype of a thread but i didn't found one. I've searched far and wide with no success.
Before i dig into the unbricking thread and reinstalling everything i just wanted to ask if this happend to anyone and if there is a simple solution for it.
I have zenfone 2 551ml with ressurection remix Remix nougat 7.1.2_r2
The phone is still working but i have no recovery. One day (dont ask me why) i wanted to update twrp just by flashing another twrp image in the twrp recovery. It didnt get updated but after i rebooted the phone, the next time there was no more recovery. I tried to flash it via fastboot with fastboot flash recovery command but still nothing. The device is detected both in adb and in fastboot.
Any ideas?
Thank you
I solved it
The thing is that i had to flash the stock recovery. Than i could sideload stock rom and now i continue.