Hello, I've been looking in the forums and in Google for a few days to see if I can fix this particular issue and I still haven't had any luck. I hope that some developers out there that have crossed with this issue can help me out.
Lately all the ROMs I've tried to install via recovery in my Flo device haven't been installing completely, they've been all installing only the system partition in recovery and nothing else, not presenting any errors on the flashing process. By doing this, most of the ROMs run on my device, but they only run barebones, meaning that they miss out on those particular features that identifies each ROM.
I've tried flashing several stock images via fastboot to see if this resolves the issue and no luck, and recently tryed installing Multirom seeing that it seemed to resolve the issues in This Thread but still no luck, the ROMs all install with the same problem if I try to flash them via recovery.
I've only had luck with ROMs flashed via fastboot, like a stock image or Cyanogenmod via the installer app that flashes trough fastboot. I should also mention that I've tried using all the available recoveries out there (CWM, TWRP, Phil's, Modified TWRP) but still no luck. Also I should point out that I noticed the issues starting since I accidentally installed 5.1.1 OTA.
Any thoughts?
ejrm13 said:
Hello, I've been looking in the forums and in Google for a few days to see if I can fix this particular issue and I still haven't had any luck. I hope that some developers out there that have crossed with this issue can help me out.
Lately all the ROMs I've tried to install via recovery in my Flo device haven't been installing completely, they've been all installing only the system partition in recovery and nothing else, not presenting any errors on the flashing process. By doing this, most of the ROMs run on my device, but they only run barebones, meaning that they miss out on those particular features that identifies each ROM.
I've tried flashing several stock images via fastboot to see if this resolves the issue and no luck, and recently tryed installing Multirom seeing that it seemed to resolve the issues in This Thread but still no luck, the ROMs all install with the same problem if I try to flash them via recovery.
I've only had luck with ROMs flashed via fastboot, like a stock image or Cyanogenmod via the installer app that flashes trough fastboot. I should also mention that I've tried using all the available recoveries out there (CWM, TWRP, Phil's, Modified TWRP) but still no luck. Also I should point out that I noticed the issues starting since I accidentally installed 5.1.1 OTA.
Any thoughts?
Click to expand...
Click to collapse
Well, firstly give me more details. Are you on unlocked bootloader.
Can you provide me with a screenshot of how the flashing looks like ? Do you have the latest recovery ?
Have you tried repairing your device with WUGFRESH TOOL kit or manually downloaded Nexus Image and flashing it ?
Quote me in case you expect a reply!
Good Luck
Related
Ok guys I am a noob (also new to these forums) and I'm having a lot of trouble with my phone. The other day, I rooted my phone using towelroot and confirmed it using root checker. then, I downloaded ROM manager as advised by a friend. i followed the instructions and installed Clockworkmod Recovery onto my AT&T Galaxy S3. Feeling I was finally ready to install a ROM, i tried to download Cyanogenmod 10.3.1 only to have it be "downloading" for over 14 hours without it completing. From there, i did some research and decided to utilize the Cyanogenmod Installer. it seemed to work perfectly, even showing the cyanogenmod logo under when my devicec turned on, until it told me to reboot my device. i entered clockworkmod recovery mode to officially reboot it. when i selected "reboot system now" it said "Root access possibly lost. Fix?". i was given the options to say "No" and "Yes - Fix root (/system/xbin/su). no matter which one i try, my phone boots to the stock touchwiz OS. I have installed and reinstalled both superuser, superSU, and ROM manager to no success. What am i doing wrong?
Try flashing Philz Touch via Odin and use that to flash a custom ROM.
From what I recall, CM ROMs are already rooted.
audit13 said:
Try flashing Philz Touch via Odin and use that to flash a custom ROM.
From what I recall, CM ROMs are already rooted.
Click to expand...
Click to collapse
CM is already rooted? What does that mean? I have a feeling that I will be unable to flash any ROMs due to my "possible loss of root access." Thank you for your patience as I am a noob and am very stressed out as this is my only phone.
I see two areas that are potential problems for flashing that rom. If it took 14 hours to download, its highly likely a corrupted download. But also, you may be on too new firmware. Cm uses asserts in the updater-script to check that you have the right base firmware/bootloader build. They dont update this so when newer firmware is released it will no longer flash because the script doesn't see it as allowed.
Anytime you have issues flashing something in recovery, you should copy the recovery log to sd. This will tell you what happened. I suspect it simply didn't flash, but without the log, theres no way we can tell what happened.
Also, you do not need to be rooted to flash anything from recovery. Just flash the recovery, then flash a rom from there. Nearly all roms you will ever see are already rooted. Non rooted roms are very rare and are generally only used as an alternate way to revert to stock.
I dont use cwm, but if im not mistaken, it seems to always ask to fix root. I dont know why, but I see people ask about it frequently.
I use TWRP, so try that, or philz as suggested by audit13. Just watch the flash progress for any errors and copy the log.
Hi guys.
I'm having a problem. This is my second Flo. I unlocked the bootloader and attempted to Flash TWRP 2.8.7. It appeared successful. But when I attempt to restart the bootloader, or wipe, or do anything I get errors telling me directories don't exist. On the restart it claims there is no OS installed. I use the Nexus Root Toolkit to resintall stock Kernel. It installs and boots fine. Ive tried two previous versions of TWRP. I am on 4.05 bootloader.
Any help would be extremely appreciated. I am my wits end. I've troubleshooted for hours to no avail.:crying:
http://forum.xda-developers.com/nexus-7-2013/nexus-7-2013-qa/mount-recovery-t3064562
Click to expand...
Click to collapse
Apparently the issue was with TWRP which may rest around "anti theft" shananagans. I installed this custom TWRP and the issue has resolved itself.
Thank you. Please marked as solved.
Hello everyone.
I have issue with my lg l70.
I recently tried to install custom rom because i got angry with bloatware (it is rooted and i deleted some of for me useless sys apps) and restriction to 4.4.2 os. I wanted to put 5.0+ or even 6.0 on him custom rom.
The problem is that this device is not supported on cwm and i tried to flash it with some img file so i can make cwm work for my device and hopefully update phone with custom one. I ended up with soft brick. I can use phone normally but since then i cannot do factory reset because it pops up with purple error screen.
If you can help me solve some stuff i would be very pleased.
So here are the things i would like to do:
I want to flash it back with all standard apps and roms and whatever else i want to have clean phone like it was when i bought it without purple screen on hard reset.
Second thing that i want is to put custom rom on it.
Hello,
Since you have installed the wrong recovery IMG you can either search for a stock recovery for your device and flash it (on the phone or by PC), find a custom recovery specific to the device or look up tutorials on porting a custom recovery for the device, Good luck!
Rooted Droid said:
Hello,
Since you have installed the wrong recovery IMG you can either search for a stock recovery for your device and flash it (on the phone or by PC), find a custom recovery specific to the device or look up tutorials on porting a custom recovery for the device, Good luck!
Click to expand...
Click to collapse
Thanks ive fixed it.
Ive used Lg Flash tool 2014 and D320n10c_00.kdz (searched it on goole and dl it.)
Now since ive unbricked it i will try to put a custom rom. I am not sure how but i hope i will not brick it again
No problem, glad you were able to get your device back! Make sure to make a backup through recovery to be able to revert if anything goes wrong. Good luck installing custom Roms
Rooted Droid said:
No problem, glad you were able to get your device back! Make sure to make a backup through recovery to be able to revert if anything goes wrong. Good luck installing custom Roms
Click to expand...
Click to collapse
I did it no problem, and installed CyanogenMod 6.0.1
Had some problems with gapps but i solved it on my own
I've seen this problem mentioned in a few threads but not seen any definitive fix.
My current install :
Stock NPD35K system, vendor, bootloader
Xceede's v8.01 kernel
TWRP 3.02 v6.0
Encrypted data partition
I currently get bootloops every time I boot into TWRP. After using TWRP and attempting to reboot it will then bootloop into recovery refusing to boot the system.
I have found it can be fixed by rebooting into fastboot and the "fastboot reboot" command. But this is frustrating if I don't have a laptop handy.
This happens every time I need to boot into recovery to install or update via TWRP. Is anyone else getting the same bootloops and has anyone found a permanent fix?
Thanks guys.
Sent from my Nexus 6P using Tapatalk
Hi Jake,
I had exactly the same issue since NPD35K except the fastboot reboot solution did not work for me.
What i could find was that if you flash the default vendor, recovery and cache partition via fastboot and then put off the tablet, it should after all of this boot correctly to the system.
Cheers,
Mathieu
You are not alone ..
I had the recovery bootloop once myself.
I did the "fastboot reboot" command and since then the Pixel C is booting fine again.
Did several installations afterwards .. no problems anymore.
Just once ..
But if you get it every reboot this a real problem.
Right now I am not able to help you .. just don't know the root cause and how to fix it.
As it looks like, it helps if you go back to stock recovery, like mentioned above.
I can not confirm this .. as I don't have the problem.
Good luck !
Thanks for the advice guys.
As I said it only bootloops immediately after boating into TWRP (even if I don't install anything), if I reboot from system it's fine.
At the moment I prefer to keep TWRP installed and reboot from fastboot if I need to use TWRP. I don't see an advantage to installing the stock recovery. It would be great to pinpoint what's causing this though.
Sent from my Pixel C using Tapatalk
I'm still getting this TWRP bootloop. I've tried several versions - 3.0.0, 3.0.21, 3.0.23. I've tried numerous times re-flashing stock using NRT and then flashing the recovery again. I've also tried fastboot-reboot.
I'm on stock 7.1.1 - NMF26H. If i need to install a different version for this to work I can do that.
Is there perhaps some particular version of TWRP that everyone but me is using? Or are there some specific versions of other files that I also need to flash along with TWRP? From what I've read if I get past this once that's probably it.
Thanks
badwiring said:
I'm still getting this TWRP bootloop. I've tried several versions - 3.0.0, 3.0.21, 3.0.23. I've tried numerous times re-flashing stock using NRT and then flashing the recovery again. I've also tried fastboot-reboot.
I'm on stock 7.1.1 - NMF26H. If i need to install a different version for this to work I can do that.
Is there perhaps some particular version of TWRP that everyone but me is using? Or are there some specific versions of other files that I also need to flash along with TWRP? From what I've read if I get past this once that's probably it.
Thanks
Click to expand...
Click to collapse
Pls install latest bootloader and latest factory image via fastboot, manually.
Pls use latest fastboot binaries from Google.
Pls install 3.0.2-23 via fastboot as well.
Reboot directly into TWRP and not into system in between.
Install SuperSu.zip v2.79 in TWRP.
Reboot into system.
The first time the system will boot twice .. it's normal.
followmsi said:
Pls install latest bootloader and latest factory image via fastboot, manually.
Pls use latest fastboot binaries from Google.
Pls install 3.0.2-23 via fastboot as well..
Click to expand...
Click to collapse
Thank you. I'll try this today. If I use s tool like NRT to flash "stock" to the device, does that cover what's described in the first step - latest bootloader and latest factory image - or is there something else I need to flash at that step?
Thanks
badwiring said:
Thank you. I'll try this today. If I use s tool like NRT to flash "stock" to the device, does that cover what's described in the first step - latest bootloader and latest factory image - or is there something else I need to flash at that step?
Thanks
Click to expand...
Click to collapse
Maybe your problem is related to the tool itself
For this reason I recommend to use the official google fastboot tool for complete flashing of factory image including bootloader.
To have a proper base to continue ..
Good luck !
EDIT: .. no need to wipe data here. Just a fresh system, vendor, cache and boot image from factory image.
followmsi said:
Maybe your problem is related to the tool itself
For this reason I recommend to use the official google fastboot tool for complete flashing of factory image including bootloader.
To have a proper base to continue ..
Good luck !
Click to expand...
Click to collapse
I think that answers my question - the original factory image including the bootloader.
I'll try it in a few hours. Thank you very much!
That worked! I was currently on stock 7.1.1 so I tried it first without re-flashing, although I was prepared to go back to that step if it didn't work.
First I downloaded SuperSU 2.79 and copied the ZIP to my device.
I used Minimal ADB and Fastboot (which I think is taken from the official Google source) and flashed recovery-twrp-3.0.2.23.followmsi-ryu.img.
Then I rebooted into recovery - not system - and flashed SuperSU.
Finally I rebooted into system.
The Google logo appeared for a moment and then it booted again (exactly as you said.) Then it booted normally.
Finally! Thank you very much! Hopefully this will help someone else too. It can be the smallest detail we miss that makes the difference.
badwiring said:
That worked! I was currently on stock 7.1.1 so I tried it first without re-flashing, although I was prepared to go back to that step if it didn't work.
First I downloaded SuperSU 2.79 and copied the ZIP to my device.
I used Minimal ADB and Fastboot (which I think is taken from the official Google source) and flashed recovery-twrp-3.0.2.23.followmsi-ryu.img.
Then I rebooted into recovery - not system - and flashed SuperSU.
Finally I rebooted into system.
The Google logo appeared for a moment and then it booted again (exactly as you said.) Then it booted normally.
Finally! Thank you very much! Hopefully this will help someone else too. It can be the smallest detail we miss that makes the difference.
Click to expand...
Click to collapse
You are welcome ..
``
tried numerous times to flash TWRP to my Pixel C 8.0.0 (OPR1.170623.032, Nov 2017) every time with bootloop in to recovery...
most recently hoping twrp-3.2.0-0-dragon would work
---------- Post added at 07:44 PM ---------- Previous post was at 07:29 PM ----------
tried to reflash ryu-opr1.170623.032-factory-020f1cf9's boot.img and it still bootlooped.
Tried to flash the recovery and now its bootlooping into stock recovery. Any ideas?
for a stock google device, this things a nightmare to work with compared to my nexus devices
i have tried to install twrp on my 5x, 6, and 6p, with the same results "do loop". doing a twrp backup of the stock rom doesn't work as flashing it results in the same "do loop". is there a good "how to" on backing up my stock rom to my pc without twrp? i have lineage 15.1 on my 6p but doing the twrp format cleans all.
I don't see the point of backing up stock rom in first place, and I don't really know what's your problem, explain... more precisely. Your twrp can't stick in stock rom, or phone bootloop after restoring backup? Answering last question: you can get factory system image right from google's servers.
i had trouble flashing the stock rom, i keep getting errors, i thought if i saved the one on the phone to my pc i might have a better chance at restoring it. installing twrp resulted in the stock rom either doing a twrp reboot or forever hung on the google logo. when i flashed lineage it starts to load but boots back to twrp. i got it to install on my 6p after wipe and format. i will try that on the 5x, will it work? just looking for a fall back position.
dr1445 said:
i had trouble flashing the stock rom, i keep getting errors, i thought if i saved the one on the phone to my pc i might have a better chance at restoring it. installing twrp resulted in the stock rom either doing a twrp reboot or forever hung on the google logo. when i flashed lineage it starts to load but boots back to twrp. i got it to install on my 6p after wipe and format. i will try that on the 5x, will it work? just looking for a fall back position.
Click to expand...
Click to collapse
Just curious what type of "errors" you are having with flashing the stock ROM? Is it possible you need to download a newer version of fastboot/adb?
@73 the old memory is not that great but i seem to recall format error. when i got the phone from ebay i did the full stock setup up to the latest 8.1. i recorded that info and that was my first google firmware flash with no joy. i had to go back to android 6 before i found one that would flash. i am running linux xubuntu, which i keep updated.
If the stock image won't flash using fastboot or OTA, it seems like your phone is faulty.
nowster said:
If the stock image won't flash using fastboot or OTA, it seems like your phone is faulty.
Click to expand...
Click to collapse
as noted in my last post, it finally did flash after trying several versions. i am hardly any kind of expert on the subject, but there seems to be problem with the twrp software on the nexus 5x and i add the 6p where the same deal occurs.
dr1445 said:
as noted in my last post, it finally did flash after trying several versions. i am hardly any kind of expert on the subject, but there seems to be problem with the twrp software on the nexus 5x and i add the 6p where the same deal occurs.
Click to expand...
Click to collapse
Why are you trying to use TWRP to flash the stock ROM (granted, I've seen the option to flash ".img" files but never used for anything other than "boot.img"). You should be using a pc and "fastboot".
For flashing stock you should be using fastboot, or the stock recovery and an OTA image.