Hi there,
I was trying to install Lightheart 1.0 OS in my SM-G930F after having LineageOS 17.1 installed for some time. I flashed the ROM and also Magisk (although I couldnt flash Gapps as Error 20 appeared). Both the ROM and Magisk seemed to flash ok. After doing all of that, I went on and, although I saw the message of NO OS INSTALLED, I swiped right as for some reason I though that it was gonna be installed anyway (or smth, idk too much about this :silly:.
Now the phone is stuck on the initial loading SAMSUNG GALAXY S7 page, without TWRP access nor download mode access (prior to flashing, I erased DALVIK, CACHE, DATA and SYSTEM). I have tried to flash TWRP with odin, but as there is no download mode access, I had no luck.
I´m reading more about what could I do, however right now I´m a bit lost and I dont know what are my options.
I would greatly appreciate any help or advice. Thanks.
EDIT: no need of help anymore.
Related
Hi,
Just for you to know:
Model: r7plusf
Recovery: TWRP 3.0.2-0
----------------------------------------
So earlier today I did an OTA update (cm-14.1-20161205-NIGHTLY-r7plus.zip), but couldn't get my phone to boot.
So naturally, I tried wiping Cache and ART cache, but was still bootlooping.
Thought there might be someting wrong with my ROM and data, so I formated data and Installed ROM and GAPPS again after ADB pushing them onto my phone.
Now, and although CM14.1 and GAPPS are successfully installed on my Oppo R7 Plus, I can't boot into the OS. Every time I try reboot system, whether through POWER_BUTTON, RECOVERY or ADB, I just boot into Recovery.
Worst of all, for some unknown reason, I can't get into BOOTLOADER, neither through button combination, nor through Recovery nor ADB.
I found this article (http://forum.xda-developers.com/tmobile-lg-g3/general/fix-recovery-loop-twrp-computer-t2873386) in the LG G3 thread about executing some shell commands, but I haven't tested testing it with my phone's variables because it might hard brick it...
Please Help!
[EDIT] I now have access to fastboot but still recovery looping like crazy.
I installed the same update via CyanDelta , worked like a charm ! hopefully you get back up and running.
[UPDATE] strangely I tried to flash stock recovery and boot CM13 and it worked!
Will try to flash twrp again and insall CM14
keep you up to date
Same thing happened to me! Where did you get a copy of the stock recovery? Link?
resverse said:
[UPDATE] strangely I tried to flash stock recovery and boot CM13 and it worked!
Will try to flash twrp again and insall CM14
keep you up to date
Click to expand...
Click to collapse
I had the same problem. Can't remember exactly how I resolved it. But I think, I use CM recovery to flash nightly. Then flash TWRP to flash gapps. For some strange reason, using CM recovery also show no enough disk space whenever I try to flash opengapps. But TWRP recovery can flash opengapps successfully.
Don't use the OTA, use adb sideload to flash the nightly next time. So far, adb sideload has not given me any issue to flash nightly.
Same problem...
I tried a lot of things nothing works and now I've installed the cm recovery but I have the "unauthorized phone" in terminal when I try to flash the ROM... I can do nothing because I can't enable the usb debugging. I don't know what to do.
If somebody can help I appreciate.
corbalan12 said:
Same problem...
I tried a lot of things nothing works and now I've installed the cm recovery but I have the "unauthorized phone" in terminal when I try to flash the ROM... I can do nothing because I can't enable the usb debugging. I don't know what to do.
If somebody can help I appreciate.
Click to expand...
Click to collapse
Since then I found how to fix it :
first of all I flashed cm13 through TWRP,
Then I flashed the stock recovery (Google it, I found it in OPPO forums) with fastboot,
After that I did a factory reset in the stock recovery,
Booted cm13 with stock recovery,
Then re-flashed TWRP,
From TWRP, I wiped both data and system partitions,
Then fresh installed cm14 and Gapps
And it worked!
Not sure if those are the exact steps I followed because all I did was a hole lot of messing around and trying absurd things out, but think this is how I fixed it.
Let me know if it worked for you or if you still can't fix your problem
Best of luck
Resverse
resverse said:
Since then I found how to fix it :
first of all I flashed cm13 through TWRP,
Then I flashed the stock recovery (Google it, I found it in OPPO forums) with fastboot,
After that I did a factory reset in the stock recovery,
Booted cm13 with stock recovery,
Then re-flashed TWRP,
From TWRP, I wiped both data and system partitions,
Then fresh installed cm14 and Gapps
And it worked!
Not sure if those are the exact steps I followed because all I did was a hole lot of messing around and trying absurd things out, but think this is how I fixed it.
Let me know if it worked for you or if you still can't fix your problem
Best of luck
Resverse
Click to expand...
Click to collapse
Thank you very much!!!! I'll try tomorrow and tell you.
I appreciate a lot!
First of all now works but to be honest, I don't know if the way I fix makes sense or if is correct but not for the same reason I do but I'll try to explain...
I had cm-14.1-20161218-NIGHTLY and I tried to update via OTA to 20161220 the phone reboot and I get the bootloop. The first I thought, install again the ROM making wipe data and blabla... nothing work.
I tried to "reflash" the recovery, nothing. Flashed cm recovery, it always gave me error trying to flash the rom. I tried to install with stock recovery, errors too.
I was reading hundred of post looking for my issues, device unauthorized, "error 7" in twrp... I was crazy.
At last I thought, I've been trying to install from SDcard, if I try to install from internal memory? and I install again the twrp to transfer the ROM and Gapps to the internal memory and... it worked!!!!
Long story but with happy ending.
Thank you for your help I appreciate and sorry for my english.First of all now works but to be honest, I don't know if the way I fix makes sense or if is correct but not for the same reason I do but I'll try to explain...
I had cm-14.1-20161218-NIGHTLY and I tried to update via OTA to 20161220 the phone reboot and I get the bootloop. The first I thought, install again the ROM making wipe data and blabla... nothing work.
I tried to "reflash" the recovery, nothing. Flashed cm recovery, it always gave me error trying to flash the rom. I tried to install with stock recovery, errors too.
I was reading hundred of post looking for my issues, device unauthorized, "error 7" in twrp... I was crazy.
At last I thought, I've been trying to install from SDcard, if I try to install from internal memory? and I install again the twrp to transfer the ROM and Gapps to the internal memory and... it worked!!!!
Long story but with happy ending.
Thank you for your help I appreciate and sorry for my english.
So let's start the story. I rooted my phone with KingRoot, all was good. Replaced it through the "Terminal Emulator for Android" app to SuperSU (The SuperSume app didn't work for me because "Your system is incompatible with this version"), all was good. Wanted to install Lineage OS. Installed it without GApps (I forgot it...), all was good. Downloaded the stock GApps for my phone, and flashed with Lineage OS through TWRP. It was working, but the Google app and Google Play Services were crashing every second. I searched that up and I found an article that said that I should just flash the GApps again (with no wipe needed), tried it but still no help. So i thought to download the mini GApps package. I wiped everything that was needed (Dalvik cache, Cache, System, Data) and flashed them both. since then, it never booted up. It showed the LineageOS boot animation, and that's it. waited and hour, but still nothing. tried to shut it down by pressing the power button for long time, and then turn it on again, but it doesn't help. Problem is, for some reason I can't get to the recovery! I press the power,home and volume up, and it just boots up normally, but that wasn't working also before flashing lineageOS. When i go to download mode, (which i can, but can't to the recovery) and connect it to Windows pc and Odin, it says "USB wasn't recognized" and doesn't work. i also tried another pc, but no luck. Of course USB Debugging is disabled, because i never had a chance to turn it on. I do have a Nandroid backup from TWRP, but i can't get to the recovery, so that's not helping. Can someone help me fix it?
Info about the phone:
Samsung Galaxy S3 i9300
Original android 4.3
Russian firmware (It had a problem with the GPS, so we fixed it there when we been there, and they replaced the motheboard with a russian one)
Running TWRP custom recovery
If any more info needed, tell me and i'll add.
Thanks for helping me.
R3t0nix7 said:
So let's start the story. I rooted my phone with KingRoot, all was good. Replaced it through the "Terminal Emulator for Android" app to SuperSU (The SuperSume app didn't work for me because "Your system is incompatible with this version"), all was good. Wanted to install Lineage OS. Installed it without GApps (I forgot it...), all was good. Downloaded the stock GApps for my phone, and flashed with Lineage OS through TWRP. It was working, but the Google app and Google Play Services were crashing every second. I searched that up and I found an article that said that I should just flash the GApps again (with no wipe needed), tried it but still no help. So i thought to download the mini GApps package. I wiped everything that was needed (Dalvik cache, Cache, System, Data) and flashed them both. since then, it never booted up. It showed the LineageOS boot animation, and that's it. waited and hour, but still nothing. tried to shut it down by pressing the power button for long time, and then turn it on again, but it doesn't help. Problem is, for some reason I can't get to the recovery! I press the power,home and volume up, and it just boots up normally, but that wasn't working also before flashing lineageOS. When i go to download mode, (which i can, but can't to the recovery) and connect it to Windows pc and Odin, it says "USB wasn't recognized" and doesn't work. i also tried another pc, but no luck. Of course USB Debugging is disabled, because i never had a chance to turn it on. I do have a Nandroid backup from TWRP, but i can't get to the recovery, so that's not helping. Can someone help me fix it?
Info about the phone:
Samsung Galaxy S3 i9300
Original android 4.3
Russian firmware (It had a problem with the GPS, so we fixed it there when we been there, and they replaced the motheboard with a russian one)
Running TWRP custom recovery
If any more info needed, tell me and i'll add.
Thanks for helping me.
Click to expand...
Click to collapse
Greetings and welcome to assist. Does kies/smartswitch recognise your phone in download mode ? You could use the emergency firmware recovery option or you can try and use adb to reboot the phone into recovery
Good Luck
Sawdoctor
Nope, not working
Hi,
I recently got custom rom- cm13 on my note 8.0 Gt-N5100. I wasnt able to use snapchat so I decided to use magisk,
I installed the magisk manager and it wouldnt open up and all my apps didnt respond. After a lot of reading articles and stuff i flashed the magisk zip through TWRP but nothing happened, I then flashed Super Su zip and now i am in this situation where The marshmallow boot screen just keeps popping up (i guess that is what is called as boot loop).I cant go pass the marshmallow loading screen. I wiped dalvik cache and did factory reset through TWRP. Is there anything I can do about this, PLz help.
Yeah I messed up, bad. So I'll give as much info as I can. First off I am incredibly newbie at all this. I have a samsung galaxy j7 sm-j700p (j7ltespr) through virgin mobile. I originally had my phone rooted with the most recent version of magisk, and twrp. I attempted flashing smalipatcher and got stuck in a bootloop. I first tried recovering my backup, but was still stuck in a bootloop. My dumbass then went into twrp and did an advanced wipe ticking all boxes, thinking this would fix my issue. Whole OS gone. So I tried using Odin to flash stock firmware and everyone I tried failed. After that I tried flashing lineage but got a kernel is not seandroid enforcing error or something like that. So I'm lost at this point, I've been up and down the web, these forums, anywhere i could find, And everything I tried has failed. Can anyone possibly help me out, or point me in the right direction?
Do you still have accesss to twrp? If yes, wipe internal storage and system, dont wipe RECOVERY, that is twrp, then flash a custom rom, later if you want, you can install a official rom with odin
Edit: system means OS,sorry.
Hi everyone,
I've been trying to get TWRP to stick for a while now, but still haven't been able to get it to install. A while ago I managed to flash Resurrection Remix using Lineage recovery which does work, but since Lineage recovery is quite limited, I really wanted to get TWRP to work. Since TWRP 3.5.0 released yesterday, I gave it another shot hoping that they fixed the issue, to no success.
I can get into TWRP just fine by temp booting it with fastboot, but after flashing the installer zip, any recovery that was previously installed gets wiped and the device will reboot when trying to get into recovery. I can still boot my phone otherwise.
The steps I took to get to this point:
Unlocked bootloader
fastboot boot twrp.img
Decrypt using screen pattern (successfully)
Flashed twrp installer zip (no error messages, process finishes successfully)
Reboot into recovery (both from twrp and bootloader at a later point)
Things I've tried:
Use a different TWRP version. Same problem as described above on both 3.4.x and 3.5.x, can't get it to decrypt on lower versions due to Android 10.
Install to recovery ramdisk, this just breaks things even more, probably because it's an A/B device?
Try a different recovery. Lineage recovery works just fine, but it's very very limited. Would really like to get TWRP working.
Trying to flash the zip results in no error messages, but any previously installed recovery gets wiped and magisk is uninstalled, which leads me to believe that it has done at least something to the boot img.
Thank you in advance.
EDIT 25.02.2021:
- Attached TWRP log
EDIT 12.03.2021:
- Log didn't want to attach, they can be found here: https://pastebin.com/awnhHDBU
Same question here. It seems that you can only boot from TWRP, not install it.
Tried installing again today, to no avail. However, I was smart enough to save the log this time. I have attached it to the main post, would be much appreciated if someone could check it out.