Hi guys, I did something really dumb and I can't seem to learn from my mistakes. Basically I rooted my 1+ with TWRP recovery. Everything was going great until I get these really bad lags. So I decided to do a factory reset but it didn't work! It booted me into TWRP recovery every time I tried to do that. So this is where the stupid mistakes begin. I wiped everything, I mean everything while I was in TWRP, without any backups. Now I get this message in TWRP "No OS installed" and my phone is stuck in the 1+ loading screen. I have tried doing a fastboot oem flash stock recovery but that didn't work. It said that my "device is not unlock, cannot flash or erase." I also have tried flasing 25R in TWRP, it said successful, but when I go to reboot, it still give me the message "No OS installed." I tried doing adb sideload, but i'm not quite familiar with that. It gave me some error in cmd prompt. Is there anything else I can try to fix this issue? Sorry, I am such a noob at this.
******************************* FIXED
In my last attempt before I give up on this phone, I downloaded all the ROMs I came across and flashed them through TWRP. All the one's I tried did not work but it finally work with the last one. I don't know how or what happened there but I'm glad it work again!
**tears of joy
Can you please tell us what rom you used? Thank you
Related
I did a factory image install of the latest from nVidia then let it update to 5.01. Made sure it was unlocked, put CWM on it, was able to go from bootloader into CWM, installed SuperSU, rebooted. No root. Went into recovery ... and it's the stock recovery ("No command"). Tried this multiple times in multiple ways and no matter what happens, once it boots into the system, CWM is gone.
Is this something I've done wrong or is this something to do with 5.01? I don't understand how it can be the latter given that I'm not seeing anyone else with this problem. Help!
Solved
Okay, I am an idiot. The problem is that I wasn't using the beta SuperSU (BETA-SuperSU-v2.42.zip) which is needed for Lollipop if you're not using a custom boot.img. I was doing neither.
kmellis said:
Okay, I am an idiot. The problem is that I wasn't using the beta SuperSU (BETA-SuperSU-v2.42.zip) which is needed for Lollipop if you're not using a custom boot.img. I was doing neither.
Click to expand...
Click to collapse
can you help me out? Im getting the image of the android on its back with a red triangle and "no command" under it.
not sure if im even doing it correctly
EDIT: Never mind I got it working just had to use the cmd prompt to flash once I did "adb reboot bootloader" from there I followed the steps. thank you everyone who made this possible.
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.
It's stuck on the "WARNING BOOTLOADER UNLOCKED" message and there's nothing to do to fix it. I tried a tutorial and now I can't even get into TWRP anymore, an error comes up (saying failed to startup). I really need help with this. Not sure what I'd do if I've messed up my phone for good.
EDIT:
Nevermind I managed to flash the factory image but omg did that have me worried and frustrated. I still want to root my phone but now I'm scared of breaking it again.
Ya bro it happens when you flash superuser on stock android not all versions of supersu are supported but some such as v 2.76,2.46 may work not sure because after customroms never had been to stock.hope it works
danz997 said:
It's stuck on the "WARNING BOOTLOADER UNLOCKED" message and there's nothing to do to fix it. I tried a tutorial and now I can't even get into TWRP anymore, an error comes up (saying failed to startup). I really need help with this. Not sure what I'd do if I've messed up my phone for good.
EDIT:
Nevermind I managed to flash the factory image but omg did that have me worried and frustrated. I still want to root my phone but now I'm scared of breaking it again.
Click to expand...
Click to collapse
Give some description of your device, maybe i can help.
do not wipe anything after flashing the SU binary and before the first boot. Meaning
-Flash it
-Reboot
Hello all, this is my first post so I apologize if anything isn't right.
I recently flashed my Mate 9 to stock Nougat B19x through a method I found on this site and then decided I wanted root. Bootloader was already unlocked so I flashed TWRP and then tried to flash a couple different root methods that all failed... So I factory reset through TWRP and tried again but they still failed so on the initial boot everything worked except the screen was blank except for the soft keys. I rebooted and the same again so I put it in fastboot and tried to re-install Nougat through the same method that worked before. It went through the whole process seemingly fine and finished with 'Update should start automatically' but then the phone boot into error mode. I've looked through everything I can find here and done everything I can think of myself but nothing has worked. I can boot into to fasboot but nothing else, not even after flashing any recoveries or stock images extracted from UPDATE.app.
Func no is 14 and error no is 1.
It's a MHA-L09 and I really need to fix it as I can't really afford anything else right now. Any help would be really appreciated and I'm happy to add more info if I've missed anything.
Thanks guys!!!
BUMP
Sorry if it's not very concise, just really need help!
What commands are you using to flash the stock files?
CandyFoxJ said:
What commands are you using to flash the stock files?
Click to expand...
Click to collapse
Standard fastboot flash recovery/system/boot
Not sure if I'm flashing all the right files or if huawei needs different commands.
Follow this guide.
https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
Thanks for your help. That's the one that I used in the first place but everytime I try again, TWRP either doesn't flash even though it says success or I can't get into recovery.
Everytime I try to access recovery using the hardware keys it boots to error mode so is there another way??
I've been looking into this some more and have found it could be a motherboard issue. Is this correct? And if so how much would that kind of repair cost and would it even be possible considering I've unlocked the bootloader?
Thanks again.
Hi.
A friend gave me his Moto G1 2013 to install Linage OS but I'm really having troubles with it, first of all it doesn't allow me to install TWRP, when I type fastboot flash recovery recovery.img it says that it installs but it doesn't, when I try to boot on it it just doesn't boot, the way I had access to TWRP was typing fastboot boot recovery.img...
When I got in I did the first step when you install a new Custom ROM that is wipe system, cache and dalvik cache, then I tried to install the ROM zip file but it gave me "error 7" I looked for solutions and I found one that is modifying updater-script file, I did it but it gave me another error about mount system, I looked for solutions too and I found one that is modifying file system format to anotherone and then bringing it back to the original format but still having the same error.
After that I decided to go back to stock ROM, I have flashed many times the stock ROM with fastboot commands but it just doesn't boot into the OS, when I try to boot the phone it boots into bootloader again... Any solution to this? Is it a hardware problem? Please help me I'm so embarrased with my friend.
Same thing happened to me!
Basidialfiddle said:
Hi.
A friend gave me his Moto G1 2013 to install Linage OS but I'm really having troubles with it, first of all it doesn't allow me to install TWRP, when I type fastboot flash recovery recovery.img it says that it installs but it doesn't, when I try to boot on it it just doesn't boot, the way I had access to TWRP was typing fastboot boot recovery.img...
When I got in I did the first step when you install a new Custom ROM that is wipe system, cache and dalvik cache, then I tried to install the ROM zip file but it gave me "error 7" I looked for solutions and I found one that is modifying updater-script file, I did it but it gave me another error about mount system, I looked for solutions too and I found one that is modifying file system format to anotherone and then bringing it back to the original format but still having the same error.
After that I decided to go back to stock ROM, I have flashed many times the stock ROM with fastboot commands but it just doesn't boot into the OS, when I try to boot the phone it boots into bootloader again... Any solution to this? Is it a hardware problem? Please help me I'm so embarrased with my friend.
Click to expand...
Click to collapse
Hi! I tried something similar with a similar result. I first unlocked my Moto G's bootloader. Then installed TWRP using fastboot. After that I tried flashing Resurrection Remix rom which failed. I've been stuck in a kind of bootloop since then. My handset powers up, finds something wrong, tries to go into recovery, fails and does this over and over again.
Since I am able to boot into bootloader mode, I tried to flash the stock rom by following instructions from this thread https://forum.xda-developers.com/showthread.php?p=47820707#post47820707
I have tried different variations from many different forums (fora?) all with the same result. Still stuck in the bootloop-thingie.
Btw, I also tried the unbricking guide from this thread
https://forum.xda-developers.com/moto-g/help/how-to-unbrick-moto-g-falcon-t3394788 without any success. My phone shows up as a Motorola ADB device and also as XT1033 in Device Manager when its plugged in.
Anyone know anything to help me out?
gaurav.kar said:
Hi! I tried something similar with a similar result. I first unlocked my Moto G's bootloader. Then installed TWRP using fastboot. After that I tried flashing Resurrection Remix rom which failed. I've been stuck in a kind of bootloop since then. My handset powers up, finds something wrong, tries to go into recovery, fails and does this over and over again.
Since I am able to boot into bootloader mode, I tried to flash the stock rom by following instructions from this thread https://forum.xda-developers.com/showthread.php?p=47820707#post47820707
I have tried different variations from many different forums (fora?) all with the same result. Still stuck in the bootloop-thingie.
Btw, I also tried the unbricking guide from this thread
https://forum.xda-developers.com/moto-g/help/how-to-unbrick-moto-g-falcon-t3394788 without any success. My phone shows up as a Motorola ADB device and also as XT1033 in Device Manager when its plugged in.
Anyone know anything to help me out?
Click to expand...
Click to collapse
Hi, I found the solution time ago, sorry for answering to late, hope I can still be helpful.
Well, what I did is, I booted into TWRP, then I did a total format to the storage, after that I did something kind of crazy, I switched my storage format to anotherone and then I turned it back to how it was before (example: I was on fat32, I switched to exFAT and then I switched again to fat32) after doing that I tried to flash LinageOS and it allowed me, it booted and now my friend has Android Oreo on his Moto G1
Hope it works for you mate, those situations are very frustrating, good luck