hi there
i already flashed a few phones over the last years so im not new to flashing but i never made it behind casual using custom roms.
so today i decided to flash my moto g (3g, 2012, single sim, european version) with the resurrection remix rom and gapps. before, i unlocked the bootloader via motorolas homepage (i now have the warning sign when booting up)
i followed the install instruction in resurrection remix thread and wiped my devies, flashed the rom, flashed gapps.
so somehow i ended up with a bootloop (resurrection remix logo) after flashing the zips via CWM and couldnt do anything about it.
i couldnt reboot into CWM recovery so i tried to use trwp falcon recovery and wiped everything.
i tried to install the custom rom again but it wont work. also i downloaded a stock firmware from the developers section but it didnt work either.
fastboot commands work for me, but adb doesnt (device not found) i already reinstalled motorola and adb universal drivers..
so basically im stuck at the bootloader menu. via fastboot boot recovery.img i can boot up to twrp recovery. i can't mount my devices system. i tried to install zips to my sd but it didnt work out (adb sideload doesnt work because device not found). i tried to mfastboot flash the stock in every single step (.xml.zip style) but im stuck at mfastboot flash boot boot.img (bootloader denies permission) (http://forum.xda-developers.com/showthread.php?t=2542219)
im now searching for a solution for about 6 hours (its 0600 am now) and im really frustrated.
please help me, i was never stuck in such a situation ever before
how can i fix it?
I'm with virtually the same issue.
Difference I can ADB the device. I even sideloaded others ROM but couldn't pass the boot.
Any help would be thanked.
today i managed to flash a brazil stockrom via "how to unbrick..." so i fixed my problem
but then
i tried flashing resurrection remix again (and crdroid)
i keep getting a boot loop
i dont know what im doing wrong
Hey Guys,
Someday with no reason, my phone just got a bootloop after restart. At this time i was using Paranoid AOSP-L.
There was no way to get into recovery (2.8.6.0), cause i was always getting bootloops. Only thing was available to me - fastboot mode.
I installed CM11S via fastboot, and it worked just fine. But trying to install any TWRP version newer than 2.8.3.0 caused bootloops (2.8.4.0 & 2.8.5.0 reboot immediately after getting into recovery, "fastboot erase cache" doesnt help, newer versions - just a bootloop). With TWRP 2.8.3.0 i managed to install CM13 by SultanXDA (wiped everything, flashed CM13 nightly, Sultan's ROM & GAPPS) and it worked. Everything was just fine (but any recovery newer, than 2.8.3.0 still caused a bootloop). I was updating it for a few months until 20160111 came (20160106 worked fine). Now bootloop is here again.
I was wiping everything, installing pretty much every unofficial TWRP version - no luck. Anything's newer than 2.8.3.0 = bootloop.
I was unable to find anything similair on any forums around, so if anyone had such problem - please help.
nklnv said:
Hey Guys,
Someday with no reason, my phone just got a bootloop after restart. At this time i was using Paranoid AOSP-L.
There was no way to get into recovery (2.8.6.0), cause i was always getting bootloops. Only thing was available to me - fastboot mode.
I installed CM11S via fastboot, and it worked just fine. But trying to install any TWRP version newer than 2.8.3.0 caused bootloops (2.8.4.0 & 2.8.5.0 reboot immediately after getting into recovery, "fastboot erase cache" doesnt help, newer versions - just a bootloop). With TWRP 2.8.3.0 i managed to install CM13 by SultanXDA (wiped everything, flashed CM13 nightly, Sultan's ROM & GAPPS) and it worked. Everything was just fine (but any recovery newer, than 2.8.3.0 still caused a bootloop). I was updating it for a few months until 20160111 came (20160106 worked fine). Now bootloop is here again.
I was wiping everything, installing pretty much every unofficial TWRP version - no luck. Anything's newer than 2.8.3.0 = bootloop.
I was unable to find anything similair on any forums around, so if anyone had such problem - please help.
Click to expand...
Click to collapse
I have not seen such issue, per my understanding, everything should be fixed after reinstalling entire COS using fastboot except EFS partition, however, I have a feeling that you should try flashing a recovery using phone itself, like Flashify or TWRP Mananger app.
Rajneeshgadge17 said:
I have not seen such issue, per my understanding, everything should be fixed after reinstalling entire COS using fastboot except EFS partition, however, I have a feeling that you should try flashing a recovery using phone itself, like Flashify or TWRP Mananger app.
Click to expand...
Click to collapse
Well, latest CM12 via TWRP - bootloop. Same with fastboot CM12.1 image. Flashify doent help.
I hope you mentioned Cyanogen OS 12.1 not CyanogenMod.
Rajneeshgadge17 said:
I hope you mentioned Cyanogen OS 12.1 not CyanogenMod.
Click to expand...
Click to collapse
Is where any difference? All the files are still named cm. And i've mentioned that one: cm-12.1-YOG4PAS3JL-bacon-signed-fastboot.zip
Just tried to erase every flashable partition (includion system, data, modem, efs, etc.) and got a brick. Unbricked to Color OS, unlocked bootloader and flashed CM12.1 via fastboot (file mentioned in my previous post); result: bootloop.
Maybe something inside is broken? But then, why CM11S works fine. And CM13 worked fine, up to 20160106. Or am i missing something?
Noticed, that not every CM11S version works.
If i flash cm-11.0-XNPH33R-bacon-signed-fastboot it works.
If i flash cm-11.0-XNPH05Q-bacon-signed-fastboot it doesnt.
Anyone knows, what's the global differences, which can cause such behavior?
As of now i tried:
Flashing CM12.1 YOG4PAS3JL via fastboot/recovery = boot to Android logo > reboot > loop
Flashing CM11S XNPH05Q via recovery = boot to Android logo > reboot > loop
Flashing CM13 builds CM/SultanXDA = boot to Android logo > reboot > loop
Flashing any TWRP newer than 2.8.3.0 = boot to Android logo > reboot > loop
Erasing & flashing/creating persist via fastboot/adb etc. - doesnt help. Same with erasing cache.
At this point OPO feels fine with CM11S XNPH44S & TWRP 2.8.1.0 or OxygenOS 1.0.0
Everything works, but why i cant upgrade it?
nklnv said:
As of now i tried:
Flashing CM12.1 YOG4PAS3JL via fastboot/recovery = boot to Android logo > reboot > loop
Flashing CM11S XNPH05Q via recovery = boot to Android logo > reboot > loop
Flashing CM13 builds CM/SultanXDA = boot to Android logo > reboot > loop
Flashing any TWRP newer than 2.8.3.0 = boot to Android logo > reboot > loop
Erasing & flashing/creating persist via fastboot/adb etc. - doesnt help. Same with erasing cache.
At this point OPO feels fine with CM11S XNPH44S & TWRP 2.8.1.0 or OxygenOS 1.0.0
Everything works, but why i cant upgrade it?
Click to expand...
Click to collapse
@nklnv did you solve the problem?
I m in the same situation and i dind't understand what's the problem.
dontyou_68 said:
@nklnv did you solve the problem?
I m in the same situation and i dind't understand what's the problem.
Click to expand...
Click to collapse
You can try flashing the newest stock ROM COS13.1 instead of that since this topic is 1yo.
I try to install cm13 but didn't work for me.
help me solve boolop
nklnv said:
Hey Guys,
Someday with no reason, my phone just got a bootloop after restart. At this time i was using Paranoid AOSP-L.
There was no way to get into recovery (2.8.6.0), cause i was always getting bootloops. Only thing was available to me - fastboot mode.
I installed CM11S via fastboot, and it worked just fine. But trying to install any TWRP version newer than 2.8.3.0 caused bootloops (2.8.4.0 & 2.8.5.0 reboot immediately after getting into recovery, "fastboot erase cache" doesnt help, newer versions - just a bootloop). With TWRP 2.8.3.0 i managed to install CM13 by SultanXDA (wiped everything, flashed CM13 nightly, Sultan's ROM & GAPPS) and it worked. Everything was just fine (but any recovery newer, than 2.8.3.0 still caused a bootloop). I was updating it for a few months until 20160111 came (20160106 worked fine). Now bootloop is here again.
I was wiping everything, installing pretty much every unofficial TWRP version - no luck. Anything's newer than 2.8.3.0 = bootloop.
I was unable to find anything similair on any forums around, so if anyone had such problem - please help.
Click to expand...
Click to collapse
hey i m stuck in bootloop only able to go to fastboot help me with the problem please.
Anurag352 said:
hey i m stuck in bootloop only able to go to fastboot help me with the problem please.
Click to expand...
Click to collapse
I solve installeed rom: cm-11.0-XNPH25R-bacon-signed-fastboot with this command in fastboot mode:
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot update -w cm-11.0-XNPH25R-bacon-signed-fastboot.zip
Try an let me know.
Now i work only with this ROM but i have problem with Whatsupp and didn't able to listen audio inside the chat.
Hi all,
Recently I updated my Nexus 5 from Lollipop to Marshmallow 6.0.1 (MMB29Q) - latest build.
everything stock works fine but, once I flash a customer recovery, in my case TWRP it stops working...I get either a startup loop or TWRP gets erased by stock recovery.
I tried various steps ...
flashed TWRP 2.8.7.1 - rebooted to boot loader was able to get into TWRP but, once I reboot system, everything works but TWRP is gone/erased and replaced by stock recovery?
Flash TWRP 2.8.7.1, then flash latest TWRP 3.0, reboot to boot loader and can get into TWRP but once i reboot into system, I am stuck on the initial boot loop.
I have to start from scratch of flashing system and boot etc to get past the loop and it still replaces TWRP with stock recovery.
I can always get into Fastboot but when I go to recovery it seems its being replaced by stock recovery.
anyone experiencing this issue? thanks for your help.
I guess I am doing something stupid but, not sure what...and thanks for your help
If you give more detail on the steps you are taking it will be easier for someone to help. Also, have you tried doing a factory reset when it bootloops?
thanks for the response..here are the details..
I had Lollipop with TWRP 2.8.7.1
yesterday, I downloaded latest build from android site...extracted all files....booted into bootloader and flashed all files..
rebooted - Marshmallow works perfectly...offcourse it not rooted yet or its locedback due to this flash
Scenario:1
So downloaded TWRP 2.8.7.1 and flashed it as recovery, no errors nothing...i rebooted to bootloader and went to recovery to confirm TWRP is there
I rebooted the system - TWRP gives option to root which I said yes so its rooted. I reboot system, this goes into bootloop - I wait for say 5-10 min in this loop mode and I see that adb can recognize the device but nothing else....its stuck in loop
when I force shut down by holding power button for few sec - and go back bootloader/recovery - TWRP is still there
***note*** I did factory wipe in TWRP but that did not fix above condition.
Scenario2:
exact same steps but after I flashed twrp2.8.7.1, I rebooted bootloader and flashed twrp 3.0 as well confirmed twrp 3.0 is flashed and rebooted system - phone start normally no issues - when I restart to bootloader - no TWRP exists, its replaced by stock recovery
Scenario 2, I tried couple of other ways and still the same thing happens - twrp 3.0 get erased.
not sure what I am doing wrong but TWRP doesn't stick
since this is my active device - i flash system.img and boot.img to get the phone to working condition
thanks for your help
Try flashing the latest supersu to get root.
audit13 said:
Try flashing the latest supersu to get root.
Click to expand...
Click to collapse
That did the trick.....thank you very much. I was using older version of supersu thinking it was latest.....I downloaded V2.65 and installed it and that fixed all my troubles..
muchas gracias
I attempted to switch custom rom and end up in a brick situation.
What actually happened:
I rooted my device and installed twrp successfully.
Then I found this thread: https://forum.xda-developers.com/mi-4i/development/rom-lineageos-15-0-t3671815
I was really interested in switching to custom rom and downloaded all necessary stuff.
(Here comes my mistake) I boot to twrp and flashed the latest firmware (8.1.5.0), wipe cache, latest rom build (LOS 15.1),wipe cahe,gapps,wipe cache and reboot to system. (all process altogether)
Now device stucked at MI logo and never booted to system again. And unable to boot to twrp mode too.
What i tried to resolve(but failed):
Device was showing lineage battery icon but nothing else was happening. So i decided to return back. I flashed my device with latest stock flashboot rom "ferrari_global_images_V9.2.3.0.LXIMIEK_20180414.0000.00_5.0_global_680c582f20" and successfully flashed it as while charging i got led light back and stock battery icon but issue remain the same. Stucked at boot loop.
I also tried Fastboot Flash Through CMD-Prompt https://in.c.mi.com/thread-334-1-0.html
But still not working. I think it must be due to firmware upgrade to oreo and if downgrade is possible, issue can be resolved but not sure and don't really know how to execute that.
Please help me in solving this issue and whatever suggestion you give please provide proper guidance or link to guidance as I'm still new to all this.
Video showing bootloop on mi4i device : https://drive.google.com/open?id=1ufwk8TNIUmycJUdjTmDBXj38-1cPCrBu
Hi guys,
so since a few days I have a really strange problem. No matter what I do, everytime I flash the TWRP installer after the rom I get stuck in a recovery loop.
I found out that if I do not install TWRP it will boot into the ROMs recovery. If I do a factory reset (erase everything) in there it will boot again just fine into the system.
If I install TWRP afterwards, for example through Magisk it will stay and work without any problem.
I've also tried a restore with the MSMDownloadTool multiple times (which worked without any problem) however after that, again, everytime I want to install a ROM and flash the TWRP installer afterwards
I'm stuck in the recovery.
I've never had this problem before and am at my wits end, because I just can't figure out what is causing this problem.
Did anyone of you also had this problem and found a way to resolve it? Any help would be much appreciated!
Note: I'm using this TWRP (3.3.1-71) -> https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
Observed same behavior.
ROM: 10.0.1 GM21AA
TWRP: 3.3.1-71 q
Magisk: v20.1
EDIT: seems the problem is related to F2FS, after formatting data back to ext4 my phone booted.
aqua_hopps said:
Observed same behavior.
ROM: 10.0.1 GM21AA
TWRP: 3.3.1-70 q
Magisk: v20.1
EDIT: seems the problem is related to F2FS, after formatting data back to ext4 my phone booted.
Click to expand...
Click to collapse
Good to know, however in that case it seems that my problem is unrelated to this, as I have never used F2FS.
TheExoduser said:
Hi guys,
so since a few days I have a really strange problem. No matter what I do, everytime I flash the TWRP installer after the rom I get stuck in a recovery loop.
I found out that if I do not install TWRP it will boot into the ROMs recovery. If I do a factory reset (erase everything) in there it will boot again just fine into the system.
If I install TWRP afterwards, for example through Magisk it will stay and work without any problem.
I've also tried a restore with the MSMDownloadTool multiple times (which worked without any problem) however after that, again, everytime I want to install a ROM and flash the TWRP installer afterwards
I'm stuck in the recovery.
I've never had this problem before and am at my wits end, because I just can't figure out what is causing this problem.
Did anyone of you also had this problem and found a way to resolve it? Any help would be much appreciated!
Note: I'm using this TWRP (3.3.1-71) -> https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
Click to expand...
Click to collapse
Sounds like your using bad command. fastboot boot whatever.img, it's better if after the word boot, drag and drop TWRP.img into command line. Oh, try 3.3.1-70, then upgrade TWRP to 71, I was having the same issue.