I've got this wierd issue.. I decided to give a try CM12, so I updated TWRP to 2.8.5.0 and flashed cm-12-20150301-NIGHTLY-falcon.zip, all great, worked like a charm :good: but video playback was bugged so I returned to my KitKat nandroid.. yesterday I tried to flash cm-12-20150304-NIGHTLY-falcon.zip to see if there were any changes to video playback, I did the flashing process using a 8GB pendrive (OTG) but the problem was that it got stuck on a bootloop (phone never entered Android nor restarted, just the bootanimation logo animation) so I said it might be the ROM, tried cm-12-20150301-NIGHTLY-falcon.zip (the one that worked for me on the first try) and flashed it via OTG, but again the same problem.. okay so OTG must be the problem, reinstalled cm-12-20150301-NIGHTLY-falcon.zip via internal storage AND THE SAME PROBLEM! I tried a lot of Lollipop ROM's but all have the same problem.. so did OTG mess up something? Is there any 'repair' script for this?
Before every attempt I do a nandroid of my current ROM and format System, Cache, Dalvik and Data, flash ROM and then gapps, reboot and stuck on bootlogo.
Any help would be appreciated :fingers-crossed:
Feche said:
I've got this wierd issue.. I decided to give a try CM12, so I updated TWRP to 2.8.5.0 and flashed cm-12-20150301-NIGHTLY-falcon.zip, all great, worked like a charm :good: but video playback was bugged so I returned to my KitKat nandroid.. yesterday I tried to flash cm-12-20150304-NIGHTLY-falcon.zip to see if there were any changes to video playback, I did the flashing process using a 8GB pendrive (OTG) but the problem was that it got stuck on a bootloop (phone never entered Android nor restarted, just the bootanimation logo animation) so I said it might be the ROM, tried cm-12-20150301-NIGHTLY-falcon.zip (the one that worked for me on the first try) and flashed it via OTG, but again the same problem.. okay so OTG must be the problem, reinstalled cm-12-20150301-NIGHTLY-falcon.zip via internal storage AND THE SAME PROBLEM! I tried a lot of Lollipop ROM's but all have the same problem.. so did OTG mess up something? Is there any 'repair' script for this?
Before every attempt I do a nandroid of my current ROM and format System, Cache, Dalvik and Data, flash ROM and then gapps, reboot and stuck on bootlogo.
Any help would be appreciated :fingers-crossed:
Click to expand...
Click to collapse
You should go to fast boot and
mfastboot erase userdata
Plz make a backup in advance and then you can flash anything via. A custom recovery
Lucas Eugene said:
You should go to fast boot and
mfastboot erase userdata
Plz make a backup in advance and then you can flash anything via. A custom recovery
Click to expand...
Click to collapse
I lost my photos but not big deal, now it's working, thanks! :good:
Tried using Twrp 2.7.1 and 2.8.1 as mentioned in the first post still getting the error failed ,also i am able to flash other roms perfectly fine currently trying to flash latest nightly help me out with this guys..
it shows unable to mount '/system'
now tried another nightly aslo ,also i was am using paranoid android which uses ext4 does this roms works on ext4 or it requires f2fs file system
update tried with phliz recovery too same error
Sent from my Moto G using XDA Premium 4 mobile app
Related
Hello Everyone. i wiped everything from CWM. Then tried to flash a CM based rom but I couldn't managed to. the problem is i cant mount data, system etc. I flashed twrp recovery to try again but nothing happens still cant mount. I was on 4.2 bootloader. I flashed twrp 2.4.4.0 but still cant mount.
I can only flash official asus rom through download mode. How can i solve my problem ?
gravis502 said:
Hello Everyone. i wiped everything from CWM. Then tried to flash a CM based rom but I couldn't managed to. the problem is i cant mount data, system etc. I flashed twrp recovery to try again but nothing happens still cant mount. I was on 4.2 bootloader. I flashed twrp 2.4.4.0 but still cant mount.
I can only flash official asus rom through download mode. How can i solve my problem ?
Click to expand...
Click to collapse
I've got a similar problem. I was on twrp 2.7.0.0 and had been running 4.4.4 Crombi for awhile but it started getting really laggy so I decided to just wipe cache and dalvik in recovery. When I rebooted, I noticed the tablet had gone into bootloop which is weird. Anyway, when I booted back to recovery again, I noticed I couldn't mount sdcard or anything else except external. I have tried flashing various twrps and cwms with no luck.
I've been able to NVFlash back all the blobs of the Asus stock 10.6.1.27 and the tablet runs fine but when I boot into recovery, it cannot mount anything. Just the weirdest thing. I guess the good thing is the tablet is working but I'd really like to be able to flash a custom ROM again...
Can anyone shed light on this issue?
Thanks
X
Update: Well...I turned on USB debugging and when I booted into recovery...everything mounted. That is the weirdest thing ever. This issue is closed for me...
Hello! I've been running the CM13 nightly from Dec 26.
Today i downloaded the Dec 30 nightly.
I had the phone in airplane mode when I rebooted into TWRP to flash the nightly along with the xposed v78 sdk23.
After rebooting my simcard wasn't detected anymore.
It clearly is a software problem, and rebooting or wiping cache/dalvik didn't solve my problem.
I hope you can help me
Same boat. No SIM
No SIM card detected here as well after the 123015 update. I am not using the custom kernel nor was I in airplane mode when I flashed.
Tried rebooting a couple times. Removed SIM card and replaced. Couldn't get it to recognize.
Same problem here with the 123015 update. Reverting to old roms did not work.
just use search ...
you probably use twrp 2.8.6.1 or greater, so new modem firmware in 30/12 nightly is not updated correctly, if you use cm, use cm recovery too or twrp 2.8.6.0! and update rom again
reflash old firmware and it will be back.
its a combination of bad luck and bad flash on the recovery you are using.
use twrp 2.8.7.6.0.
That one is not prone to bad flashes of firmware
no need to restore efs cause the bad flash can be corrected
Sent from my A0001 using Tapatalk
Startlinger said:
reflash old firmware and it will be back.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Where do I find the 'old firmware'
deleted
just back to 29/12 nightly, flash correct recovery and again flash 30/12
I'm also having this issue, but it happened under different circumstances:
I was using the last CM12.1 nightly (2015-11-21).
On a previous occasion I had clean-flashed the CM13 nightly (2015-12-10), however it was freezing and crashing quite a lot so I decided to wait a bit, and restored my CM12.1 build (after making a nandroid back-up of my CM13 build).
Yesterday (2015-12-30) I thought I'd see how the CM13 builds were going, so restored my CM13 backup... This is when my phone refused to recognise my sim card. On top of this, it would randomly reboot for no apparent reason. I updated to the latest CM13 nightly (2015-12-30) but these problems weren't fixed.
I then decided to restore my CM12.1 build (which was backed up right before I attempted any of this), however the problems remained. It wouldn't recognise my sim card and would reboot at random.
Since then I have wiped cache + dalvik, cache + dalvik + data, cache + dalvik + system + data + internal memory, done a fresh install, and still the problems persist.
After reading the above posts I'm going to try and roll back my TWRP to 2.8.6.0, but needless to say it's been a very frustrating experience!
If anyone can see anything I'm doing amazingly wrong, please let me know.
twrp-2.8.6.0
NoSyt15 said:
I'm also having this issue, but it happened under different circumstances:
I was using the last CM12.1 nightly (2015-11-21).
On a previous occasion I had clean-flashed the CM13 nightly (2015-12-10), however it was freezing and crashing quite a lot so I decided to wait a bit, and restored my CM12.1 build (after making a nandroid back-up of my CM13 build).
Yesterday (2015-12-30) I thought I'd see how the CM13 builds were going, so restored my CM13 backup... This is when my phone refused to recognise my sim card. On top of this, it would randomly reboot for no apparent reason. I updated to the latest CM13 nightly (2015-12-30) but these problems weren't fixed.
I then decided to restore my CM12.1 build (which was backed up right before I attempted any of this), however the problems remained. It wouldn't recognise my sim card and would reboot at random.
Since then I have wiped cache + dalvik, cache + dalvik + data, cache + dalvik + system + data + internal memory, done a fresh install, and still the problems persist.
After reading the above posts I'm going to try and roll back my TWRP to 2.8.6.0, but needless to say it's been a very frustrating experience!
If anyone can see anything I'm doing amazingly wrong, please let me know.
Click to expand...
Click to collapse
in your case your efs may have gotton corrupt, next to a bad flash. Do if flashing old firmware doesnt fix it, restore the backup of efs if you made one to make more confusing you may need a special twrp version to have made the backup on in first place. to make more confusing.
Try this first,official twrp doesnt backup the firmware, so chance is highest you are running cm13firmware and cm12 rom. flash and reboot on recovery official 2.8.6.0, clean and repair system, data, cache. Flash old cm13 and let it boot. Note you should have no(maybe just 2) lines which state after "Writing radio image...")"already up to date
All functioning then score! Proceed with latest nightly
All not functioning efs restore should help. Never made one, follow above and flash back the cm12 rom you have. Same case with firmware updating and booting
Sent from my A0001 using Tapatalk
fronzinator said:
Hello! I've been running the CM13 nightly from Dec 26.
Today i downloaded the Dec 30 nightly.
I had the phone in airplane mode when I rebooted into TWRP to flash the nightly along with the xposed v78 sdk23.
After rebooting my simcard wasn't detected anymore.
It clearly is a software problem, and rebooting or wiping cache/dalvik didn't solve my problem.
I hope you can help me
Click to expand...
Click to collapse
Use 2.8.6.0 of twrp to update modem
Startlinger said:
in your case your efs may have gotton corrupt, next to a bad flash. Do if flashing old firmware doesnt fix it, restore the backup of efs if you made one to make more confusing you may need a special twrp version to have made the backup on in first place. to make more confusing.
Try this first,official twrp doesnt backup the firmware, so chance is highest you are running cm13firmware and cm12 rom. flash and reboot on recovery official 2.8.6.0, clean and repair system, data, cache. Flash old cm13 and let it boot. Note you should have no(maybe just 2) lines which state after "Writing radio image...")"already up to date
All functioning then score! Proceed with latest nightly
All not functioning efs restore should help. Never made one, follow above and flash back the cm12 rom you have. Same case with firmware updating and booting
Click to expand...
Click to collapse
I restored my twrp to 2.8.6.0 (after wiping the entire phone previously... urgh), and then flashed the latest nightly. Everything worked again!
I ended up going back to my CM12.1 backup as the TrueCaller CM app keeps crashing in CM13. I could just keep the stock dialer, but I have grown accustomed to knowing who's calling me!
Thanks for your help all!
I get this issue as well.
IVIatty said:
I get this issue as well.
Click to expand...
Click to collapse
ok, thanks for informing us.
bastard79 said:
ok, thanks for informing us.
Click to expand...
Click to collapse
Thank your for thanking him for informing us
Sent from my A0001 using Tapatalk
Hi, I'm stuck. I have tried flashing the twrp-2.8.6.0-bacon.img recovery image file I got from dl.twrp.me. The file matches the MD5 I got from the TWRP website (f69fa503419644851822d883c2388bb8), and I don't see any errors when I do a fastboot flash recovery twrp-2.8.6.0-bacon.img command.
However, when I have tried to boot back into Recovery Mode, my phone just ends up booting into Normal Mode (until my phone gets hung). Doing a fastboot boot twrp-2.8.6.0-bacon.img command didn't get me into Recovery Mode, either. If I go back and do a fastboot flash recovery twrp-2.8.7.0-bacon.img, I can boot back into the 2.8.7.0 TWRP Recovery Mode, but that won't let me get my modem back.
Can anybody help (maybe with a different copy of the twrp-2.8.6.0-bacon.img recovery image)?
Thanks.
¿GJ?
Startlinger said:
use twrp 2.8.7.6.0.
Click to expand...
Click to collapse
Hi, Startlinger - Do you mean 2.8.6.0? That's a little confusing ...
¿GotJazz? said:
Hi, I'm stuck. I have tried flashing the twrp-2.8.6.0-bacon.img recovery image file I got from dl.twrp.me. The file matches the MD5 I got from the TWRP website (f69fa503419644851822d883c2388bb8), and I don't see any errors when I do a fastboot flash recovery twrp-2.8.6.0-bacon.img command.
However, when I have tried to boot back into Recovery Mode, my phone just ends up booting into Normal Mode (until my phone gets hung). Doing a fastboot boot twrp-2.8.6.0-bacon.img command didn't get me into Recovery Mode, either. If I go back and do a fastboot flash recovery twrp-2.8.7.0-bacon.img, I can boot back into the 2.8.7.0 TWRP Recovery Mode, but that won't let me get my modem back.
Can anybody help (maybe with a different copy of the twrp-2.8.6.0-bacon.img recovery image)?
Thanks.
¿GJ?
Hi, Startlinger - Do you mean 2.8.6.0? That's a little confusing ...
Click to expand...
Click to collapse
Download again via different browser, double check filesize of what you downloaded. It was a bad download sir
You can download on your phone also, same check download size. From twrp where when flashing you can select img. Then select recovery, reboot recovery and your on the one that works
Sent from my A0001 using Tapatalk
Startlinger said:
Download again via different browser, double check filesize of what you downloaded. It was a bad download sir
You can download on your phone also, same check download size. From twrp where when flashing you can select img. Then select recovery, reboot recovery and your on the one that works
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Hi, @Startlinger - I've downloaded twrp-2.8.6.0-bacon.img with three different browsers (Chrome, MS IE, and Firefox). All three images acted the same way: They all matched the MD5 posted on TWRP, and they were all unbootable (either by flashing, or with a fastboot boot twrp-2.8.6.0-bacon.img command). I couldn't download the image to the phone via the internet, because I can't get an internet connection on my OPO anymore - probably because the modem is corrupted. I did copying one of the computer-downloaded 2.8.6.0 images to the phone, and tried flashing the image through TWRP 2.8.7.0, but the results were exactly the same ... it wouldn't boot into Recovery Mode after that.
Is the f69fa503419644851822d883c2388bb8 MD5 value correct? (I suspect it is)
One thing I've noticed is that I can't just power-off my phone anymore when 2.8.6.0 is loaded. If I try to power off, it comes back up in Normal Mode. This may be related to the corrupted 2.8.6.0 Recovery Mode.
Update: I've also noticed something else - I tried doing a fastboot boot twrp-image-file with other versions of TWRP (2.84.1 and 2.8.5.1). None of these boot into Recovery Mode - just the 2.8.7.0 image works.
Is there something else I need to recover on my phone (if it's even possible)? Is there any other way I can reinstall a workable Lollipop 5.0.2 Modem Image onto the phone?
well, thats a first gotjazz.
I would recommend 2.8.7.05 from here https://www.androidfilehost.com/?fid=24269982087010524
if same results, perhaps best to download latest fastboot rom from cyanogen. Then fastboot your way back to a complete stock situation. Before doing so wipe everything in 2.8.7.0, and repair all partitions that allow repairing.
when fastbooting everything take care in using the 64 if you got 64 gb
After let it boot, check if you can get reception. If that works, fastboot flash recovery of 2.8.6.0. or 2.8.7.05 and go back to whatever rom you want
Sent from my A0001 using Tapatalk
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.
Dear Apollo users,
I have seen threads like these for other phones, but would prefer a solution specific to the Apollo Lite. I just purchased my Apollo (second hand), I gave it a factory reset and now it is stuck in TWRP. The previous owner flashed a custom rom so TWRP has already been installed. It just will not boot any rom, I installed new roms and after reboot it will just boot straight to TWRP.
Any suggestions?
Mornioas
mornioas said:
Dear Apollo users,
I have seen threads like these for other phones, but would prefer a solution specific to the Apollo Lite. I just purchased my Apollo (second hand), I gave it a factory reset and now it is stuck in TWRP. The previous owner flashed a custom rom so TWRP has already been installed. It just will not boot any rom, I installed new roms and after reboot it will just boot straight to TWRP.
Any suggestions?
Mornioas
Click to expand...
Click to collapse
Just do a clean install ( stockrom ) with the SP flashtool and everything gonna bee alright
Thank you, I got it working. BTW some phones seem to have spyware or other types of nonesense on them. Once I install a custom rom, everything is clean?
For all who have the same problem: http://www.needrom.com/download/official-p10-rom-27-07-16/
marcolo76 said:
Just do a clean install ( stockrom ) with the SP flashtool and everything gonna bee alright
Click to expand...
Click to collapse
I have the same problem. How do I have to use SP Flash Tool to fix this problem?
Hahahaha at least i saw there was a link to fix this problem xD
save me
SagaTitan29 said:
I have the same problem. How do I have to use SP Flash Tool to fix this problem?
Hahahaha at least i saw there was a link to fix this problem xD
Click to expand...
Click to collapse
I have the same problem, but after returning to twrp because of the factory restore I deleted the cache, system, dalvik and data and now it does not work usb, when I connect it it goes directly to twrp and the flash tool does not can do the service. what do I do????
wipe cache
I just fixed that by entering bootloader, typed "fastboot -w" and "fastboot erase recovery" (for removing TWRP" and installed it again. When I tried to install the rom again it worked perfectly.
I recommend you to have the rom saved in your Sdcard 1 (removable SD CARD) for saving time.
Hi, I've got a XT1032, with the Lollipop bootloader and TWRP 3.0.0 installed, and I have a custom rom I want to flash (https://forum.xda-developers.com/moto-g/development/rom-aosp-4-4-4-gpe-screen-flickering-t3499889)
When I go to flash the ROM, TWRP says that the zip install went perfectly, but when I boot, it just loads into the stock Lollipop.
Even when I go to my computer and find fastboot devices, fastboot comes up with nothing, even though the Moto is in fastboot, and plugged into my computer.
It's awfully late, I have school tomorrow, and I kinda need my phone with the ROM I want. Please help!
...you have to change data to ext4, wipe everything, then install that rom.
ALSO UPGRADE TO 3.2.3
AaronVey22 said:
...you have to change data to ext4, wipe everything, then install that rom.
ALSO UPGRADE TO 3.2.3
Click to expand...
Click to collapse
I have exactly the same issue with my Moto G falcon.
As per your suggestion I have tried to format/change the data partition from f2fs to ext4 via TWRP, but everytime the format process completes successfully but does not change /data to ext4, it still stays stuck at f2fs
- I have tried multiple official twrps for falcon - 3.2.3, 3.2.1, 3.0.2.2 and son on ... nothing works
- I have also tried to format/wipe data with all TWRP version, nothing works
PS: My device was lying dead since a couple of years or so, but it was working fine back in 2017. Could this be a firmware issue?