Title says it all. Fastboot works, flashing works. Even if I try to charge the phone on power off condition, it loops infinitely to splash screen. Tried flashing both custom and official ROMs via fastboot. I don't think this is an emmc problem since I can still format and erase all partitions.
Before all of this, I used the official RR Nougat ROM. Everything works fine until it suddenly bootloops out of thin air.
bakanui said:
Title says it all. Fastboot works, flashing works. Even if I try to charge the phone on power off condition, it loops infinitely to splash screen. Tried flashing both custom and official ROMs via fastboot. I don't think this is an emmc problem since I can still format and erase all partitions.
Before all of this, I used the official RR Nougat ROM. Everything works fine until it suddenly bootloops out of thin air.
Click to expand...
Click to collapse
Flash stock firmware with QFIL
mshoaib7 said:
Flash stock firmware with QFIL
Click to expand...
Click to collapse
I have tried to flash via QFIL, but it stopped midway flashing the system and device won't turn on now
I guess it's just me messing up somehow with the cables or something
Thank you anyway mshoaib7!
https://boycracked.com/2016/02/12/e...rmware-any-android-devices-via-fastboot-mode/
Try this one. May help u. Extract from official ROM. And flash those things. System IMG is not needed if u have any old backup means. Flash use this. Go to recovery and restore old one.
Bcz system image is large, so sumtyms it fails to flash. That's y I said lrave the system data image flashing and restore the backup.
mshoaib7 said:
Flash stock firmware with QFIL
Click to expand...
Click to collapse
@mshoaib7 bro you like idli or dosa??
Give it to service centre
bakanui said:
I have tried to flash via QFIL, but it stopped midway flashing the system and device won't turn on now
I guess it's just me messing up somehow with the cables or something
Thank you anyway mshoaib7!
Click to expand...
Click to collapse
bro use downloader the flash tool which is already given in the stock firmware if still it get stuck in the middle then it is driver problem then format u r pc or use friend pc
how to properly revert back from mm or nougat roms to stock kitkat rom?
I was on cm13 by ed300, then I tried to restore nandroid backup of stock kk via twrp
then my phone stuck on boot logo, only fastboot mode works, then flashed twrp and stock kk rom after some attempts.
So what are the steps to successfully revert back to kk? (in case this problem happens again in future)
Related
Regardless of what recovery I used, (yash28, regalstreak, official twrp) or even starting from the scratch( flashing stock OxygenOS using the Oneplus tools) and then reflashing the recovery, my attempts to succesfully load into a ROM has been futile. As of now, I am pretty much unable to boot into any recovery, and I am stuck using the stock OxygenOS. I tried flashing modem, first attempt was clean flashing the new modem, then flashing it dirty after flashing my rom, I tried doing the same thing with the old modem, my attempts have been futile. If anyone could shed light in this situation, it would be great, I would hate to be stuck using the stock OxygenOS rom, and not try out the great roms that are developed. I can however flash oxygenOS stock rom.
i have the same problem and i cant find any solution i thought of starting fromt he scratch as it didnt help u it might not help me too
Have the same, I've done everything. I've made the phone full stock again and still won't boot.
I have finally found the solution to my own problem
Apparently what made this impossible was due to sensors, as I noticed some of my sensors werent working. That could have made me unable to flash anything but OOS. Anyway, the solution is to fastboot erase persist, and reflash persist.img (Instructions are here: http://forum.xda-developers.com/showpost.php?p=65340562&postcount=591). I hope this fixes your guys problem.
abhisek1994 said:
Apparently what made this impossible was due to sensors, as I noticed some of my sensors werent working. That could have made me unable to flash anything but OOS. Anyway, the solution is to fastboot erase persist, and reflash persist.img (Instructions are here: http://forum.xda-developers.com/showpost.php?p=65340562&postcount=591). I hope this fixes your guys problem.
Click to expand...
Click to collapse
So now youre able to flash CM13 without bootloops?
yousuf.shareef said:
So now youre able to flash CM13 without bootloops?
Click to expand...
Click to collapse
Yep! Also make sure you are using official TWRP (https://dl.twrp.me/oneplus2/) Good luck.
abhisek1994 said:
Apparently what made this impossible was due to sensors, as I noticed some of my sensors werent working. That could have made me unable to flash anything but OOS. Anyway, the solution is to fastboot erase persist, and reflash persist.img (Instructions are here: http://forum.xda-developers.com/showpost.php?p=65340562&postcount=591). I hope this fixes your guys problem.
Click to expand...
Click to collapse
FINALLY! Thank you!! Ive been stuck all day without getting ANY MM ROM to boot,. and this ...thing...fixed it! Thanks again
Finally someone found the answer! Unfortunately I wiped whole internal memory and forgot to take backup of whatsapp backup so i lost that. Oh well, all works good now, thank you!
JudderArts said:
Finally someone found the answer! Unfortunately I wiped whole internal memory and forgot to take backup of whatsapp backup so i lost that. Oh well, all works good now, thank you!
Click to expand...
Click to collapse
Dont forget to thank people.
abhisek1994 said:
Dont forget to thank people.
Click to expand...
Click to collapse
JudderArts said:
thank you!
Click to expand...
Click to collapse
That's exactly what I did.
I think i faced the same problem, im using h2os 6.0.1 close beta, with twrp 3.0, but without rooting. I can restore my rom tru twrp without problem. But my try to flash grarak cm13 and new mokee os 6.0 ended up with bootloops, both stuck at oneplus logo
abhisek1994 said:
Apparently what made this impossible was due to sensors, as I noticed some of my sensors werent working. That could have made me unable to flash anything but OOS. Anyway, the solution is to fastboot erase persist, and reflash persist.img (Instructions are here: http://forum.xda-developers.com/showpost.php?p=65340562&postcount=591). I hope this fixes your guys problem.
Click to expand...
Click to collapse
Do you have to go back to the stock rom before flashing persist and then install cm13? or can i do it while i am on the boot logo screen...i tried going into fastboot while stuck on the boot logo (which i was able to) and flashed persist and rebooted but it is still stuck on the boot logo screen
muthukumarc said:
Do you have to go back to the stock rom before flashing persist and then install cm13? or can i do it while i am on the boot logo screen...i tried going into fastboot while stuck on the boot logo (which i was able to) and flashed persist and rebooted but it is still stuck on the boot logo screen
Click to expand...
Click to collapse
You have to downgrade fastboot/bootloader to the Lollipop one (just flash the usual revert_to_lollipop.zip found in these forums as usual).
i flashed nuclear 7.1 but i encurred in a bootloop that i could resolve only with qfil tool, so i putted cos 12.1 stock, unclocked bootloader and flashed twrp, now: when i flash ANY rom via twrp i go in a bootloop that i can only solve with qfil tool going back to cos and do everything from beginning.
i tried:
change recovery (i tried CWM but i have same problem)
wipe storage (anything changed)
i tried several roms but everyone gave me the same result: very fast bootloop in zuk logo and phone vibration
the only thing i can do is to restore a backup, but since im note able to flash mm firmware (bootloop) i cant use touch id and g-sensor
what can be the problem?
any solution?
thanks
Boot and recovery partitions
Sounds like you messed up boot and recovery sections. Since you can boot up successfully, you may try to flash back to ZUI which changes these two sections completely. If it's not a solution for you, I think the only way to repair is completely format including kernel, system and partitions. You can find the tutorial on Website.
...
you can fix it just use TOOL_ZUK_Z1_ENG_0.0.6
Try flashing COS 12.1 via fastboot.
crazyox said:
i flashed nuclear 7.1 but i encurred in a bootloop that i could resolve only with qfil tool, so i putted cos 12.1 stock, unclocked bootloader and flashed twrp, now: when i flash ANY rom via twrp i go in a bootloop that i can only solve with qfil tool going back to cos and do everything from beginning.
i tried:
change recovery (i tried CWM but i have same problem)
wipe storage (anything changed)
i tried several roms but everyone gave me the same result: very fast bootloop in zuk logo and phone vibration
the only thing i can do is to restore a backup, but since im note able to flash mm firmware (bootloop) i cant use touch id and g-sensor
what can be the problem?
any solution?
thanks
Click to expand...
Click to collapse
Hi!! I've flashed the NucleaRom too and for a couple of weeks it worked just fine. However one day, out of nowhere, the phone, while still on and working, restarted itself and entered a bootloop. After a few days it restarted normally and lasted a couple of hours but then it all started again. The BIG issue here is that when the phone enters in this bootloop where it remains on for about 15 seconds, it does it either in the system or the recovery/fastboot. I've managed to install two other ROMs via TWRP, when it miraculously remained turned on, but the problem persisted.
Is there a chance your problem was similar? How did you manage to flash via QFIL? I can't enter into that "emergency" or "download mode" in order to flash.
Many thanks in advance
i think that the problem is in the bootloader itself you should try flashing the latest os u have used and instal ordinary unofical lineage nightly (you can find everywhere) by this way your bootloader will be updated to 7.1 after that you can install any software i was having same problem when trying to migrate to lineage os
unable to install Custom ROM's
hi ,,
even i had the same problem like recovery was not accepting any ROMS... if we flash it ll go to recovery again and again,
and later i have flashed CM 13 with image file,, it worked and gone to recovery and updated the update to lineage OS 14.1 with Gapps..
hope it might help u...
crazyox said:
i flashed nuclear 7.1 but i encurred in a bootloop that i could resolve only with qfil tool, so i putted cos 12.1 stock, unclocked bootloader and flashed twrp, now: when i flash ANY rom via twrp i go in a bootloop that i can only solve with qfil tool going back to cos and do everything from beginning.
i tried:
change recovery (i tried CWM but i have same problem)
wipe storage (anything changed)
i tried several roms but everyone gave me the same result: very fast bootloop in zuk logo and phone vibration
the only thing i can do is to restore a backup, but since im note able to flash mm firmware (bootloop) i cant use touch id and g-sensor
what can be the problem?
any solution?
thanks
Click to expand...
Click to collapse
crazyox said:
i flashed nuclear 7.1 but i encurred in a bootloop that i could resolve only with qfil tool, so i putted cos 12.1 stock, unclocked bootloader and flashed twrp, now: when i flash ANY rom via twrp i go in a bootloop that i can only solve with qfil tool going back to cos and do everything from beginning.
i tried:
change recovery (i tried CWM but i have same problem)
wipe storage (anything changed)
i tried several roms but everyone gave me the same result: very fast bootloop in zuk logo and phone vibration
the only thing i can do is to restore a backup, but since im note able to flash mm firmware (bootloop) i cant use touch id and g-sensor
what can be the problem?
any solution?
thanks
Click to expand...
Click to collapse
i am continuously on the boot loop! how to get rid of it?
plz help its been 4 hrs, i think i am in trouble! any possible solutions!!!!
U can try one thing.... Install cm13 with flash file and then restart - - & go to recovery select install update and select lineage 14 and G apps... I did like this . And it worked....
2-3 days ago I successfully rooted my Moto E3 power by unlocking bootloader and installing twrp recovery. Yesterday I installed Lineage 14.1 custom Rom (7.1.2) for Moto E3 power from here
https://forum.xda-developers.com/moto-e3/development/rom-lineage-14-1-moto-e3-power-t3610435
The Rom installation was successful. Phone was working fine. But there was some minor lag and screen was appearing to be yellowish. Hence I decided to Factory reset the phone. I tried to reset it from phone settings. The phone switched off and turned on into twrp recovery mode. Then I tried to factory reset through twrp mode. But it is always booting into twrp recovery. I wiped all cache and data including system data and flashed the above Rom again. But whenever I try to system reboot, it is not booting normally, but always going into twrp mode.
Please provide solution for the issue with appropriate information and links.
Thanks.
Beauause u delete the all ROM
For Reset phone -: not need to wipe system and boot.. Only do a factory reset
Rupi Singh said:
Beauause u delete the all ROM
For Reset phone -: not need to wipe system and boot.. Only do a factory reset
Click to expand...
Click to collapse
Yes, I know that
I had done just factory reset earlier, but after that it kept on booting into recovery mode everytime I reboot the phone. Then I cleared system data to flash the ROM again. I should have done factory reset through recovery mode rather than from phone settings.
Flash a sp flash ROM without format... And again try twrp and custom ROM
Rupi Singh said:
Flash a sp flash ROM without format... And again try twrp and custom ROM
Click to expand...
Click to collapse
yes, already did same thing today. it worked fine and i successfully installed stock rom again.
sid100 said:
yes, already did same thing today. it worked fine and i successfully installed stock rom again.
Click to expand...
Click to collapse
Hi,
Would be great if you can share step by step process on how you recovered. Am also facing the same issue. Have factory reseted my phone and now its booting only to TWRP recovery mode. Am on Mac. Can try to get a Windows Laptop if required.
Awaiting you response.
Thanks in advance!
question?
Rupi Singh said:
Flash a sp flash ROM without format... And again try twrp and custom ROM
Click to expand...
Click to collapse
can you elaborate this ?
What do you mean by Sp flash ROM.?
Do it mean stock rom?
or i have to install sp flash tool in my computer then install stock rom?
if i have twrp install if than i can use it to install stock rom?
Please reply fast.
my phone is as good as dead now.
Ansh Vijay said:
can you elaborate this ?
What do you mean by Sp flash ROM.?
Do it mean stock rom?
or i have to install sp flash tool in my computer then install stock rom?
if i have twrp install if than i can use it to install stock rom?
Please reply fast.
my phone is as good as dead now.
Click to expand...
Click to collapse
I have got the same problem bro. If I can recover from the situation somehow, I'll update it here.
Have an update!
Ben_android enthusiast said:
I have got the same problem bro. If I can recover from the situation somehow, I'll update it here.
Click to expand...
Click to collapse
Update: Don't know if you still need the solution, but I am gonna share my info. Although as the phone you were talking about must be Moto E3, my phone is Lenovo K3 Note, but the processor should basically be the same, as both runs on Mediatek processors. And for the same reason, they both would use the SP Flash Tool to flash a ROM. You'll need to download the Stock ROM file for your moto E3, and flash it through SP flash tool installed on your computer. You'll get the tutorials on youtube. When the stock ROM is flashed, the phone will start with your stock ROM. I have had my phone do the same and it is fine now.
Ben_android enthusiast said:
I have got the same problem bro. If I can recover from the situation somehow, I'll update it here.
Click to expand...
Click to collapse
Yes i recovered from the situation.
You just had to download the sp flash tool and the stock ROM for your respective phone, and flash it . Remember for the above problem you just have to use the "download only" option in your sp flash tool and it will work. if you use "format all+download"
you will left by losing imei number of your phone and then you have to follow other procedure to fix that. but according to me your phone will start by choosing download only.
I have a Moto X Style XT1572 Indian version. I updated it to stock Nougat 7.0 via OTA when it was rolled out in India. Later in January I unlocked the bootloader and installed unofficial TWRP recovery for flashing custom ROMs. I did take a full backup of stock ROM immediately when I installed the recovery. Since then I'm using custom ROMs built for Nougat modem.
At present, how can I go back to stock Nougat? I did do a full wipe (except internal memory) and tried to restore the stock Nougat backup which I took in January. The backup always gets successfully restored. However, when the phone boots up completely and reaches the language selection screen(the first screen when the phone boots up), the phone reboots and goes into a bootloop just displaying the bootloader unlocked screen. The only option I have then is to flash any custom ROM again and they do work perfectly. So what must be restricting the stock backup to boot? Also, is there any other way to go back to stock Nougat?
anyone, please?
AsquareX said:
anyone, please?
Click to expand...
Click to collapse
This thread looks like it has the nougat full firmware package for your phone. Try fastboot flashing all of it: https://forum.xda-developers.com/moto-x-style/general/xt1572firmwareclarkretasiaindiads7-t3735257
If that doesn't work out, here's another trick I've seen work on occasion. Restore your TWRP backup, but do not reboot into it. After restoring the backup, use TWRP to flash stock recovery, then reboot to recovery and do a factory reset with the stock recovery. Then reboot into the stock rom. That can clear up some internal storage problems that hang things up. There are other ways to do it, but this is easiest.
jason2678 said:
This thread looks like it has the nougat full firmware package for your phone. Try fastboot flashing all of it: https://forum.xda-developers.com/moto-x-style/general/xt1572firmwareclarkretasiaindiads7-t3735257
If that doesn't work out, here's another trick I've seen work on occasion. Restore your TWRP backup, but do not reboot into it. After restoring the backup, use TWRP to flash stock recovery, then reboot to recovery and do a factory reset with the stock recovery. Then reboot into the stock rom. That can clear up some internal storage problems that hang things up. There are other ways to do it, but this is easiest.
Click to expand...
Click to collapse
I'll give a try to the fastboot version.
I flash ram kernel then flash magisk, then my N9100 hongkong version bricked, I can only go to download mode
I have tried to flash stock firmware, it seem to be succeeded then reboot in to recovery to flash something but crashed in the middle then turned off. and can not turn on again just only download mode worked
I tried to flash boot.img and recovery.img and catche.ext4 to get stock recovery but not succeded
I tried to flash root method by CF, this time my n9100 can boot into stock recovery. I try to flash firmware again but the problem stay the same.
Please help me. I am very confused now because this is my first time the flashing firmware doesnt work.
bangdt said:
I flash ram kernel then flash magisk, then my N9100 hongkong version bricked, I can only go to download mode
I have tried to flash stock firmware, it seem to be succeeded then reboot in to recovery to flash something but crashed in the middle then turned off. and can not turn on again just only download mode worked
I tried to flash boot.img and recovery.img and catche.ext4 to get stock recovery but not succeded
I tried to flash root method by CF, this time my n9100 can boot into stock recovery. I try to flash firmware again but the problem stay the same.
Please help me. I am very confused now because this is my first time the flashing firmware doesnt work.
Click to expand...
Click to collapse
Does it give mmc error in download mode?
If yes emmc is physically damaged
kpwnApps said:
Does it give mmc error in download mode?
If yes emmc is physically damaged
Click to expand...
Click to collapse
Thanks for suggestion. I am trying to format it. Hope it could be ok.
I flashed firmware with pit option to reformat all nand partitions to correct errors if it were there, but still not successes. The processes stay the same, flash then the phone restart to stock recovery then flashing something then crashed in the middle and finally went off.
I tried flash twrp and try to restore the phone by my stock rom backed up but the problem still there, the restoring breaked in the middle then turn off.
I guest i have some errors in the middle of the emmc so if the rom could be smaller then i can pass the problem.
Finally I unbricked the phone by flashing a smaller rom (an unoffical pie for trltedous) which only around 1gb zip. This time everything was passed then The phone boot in to the pie os.
After boot success, I tried to fullfil my phone by some data and magically pie full os can write full of my storage. I turn it of then use odin to flash stock firmware. This time everything ok.
From this case, I thing we should have a tiny flashable os to correct problem in emmc. As tiny as posible.
bangdt said:
I flashed firmware with pit option to reformat all nand partitions to correct errors if it were there, but still not successes. The processes stay the same, flash then the phone restart to stock recovery then flashing something then crashed in the middle and finally went off.
I tried flash twrp and try to restore the phone by my stock rom backed up but the problem still there, the restoring breaked in the middle then turn off.
I guest i have some errors in the middle of the emmc so if the rom could be smaller then i can pass the problem.
Finally I unbricked the phone by flashing a smaller rom (an unoffical pie for trltedous) which only around 1gb zip. This time everything was passed then The phone boot in to the pie os.
After boot success, I tried to fullfil my phone by some data and magically pie full os can write full of my storage. I turn it of then use odin to flash stock firmware. This time everything ok.
From this case, I thing we should have a tiny flashable os to correct problem in emmc. As tiny as posible.
Click to expand...
Click to collapse
Its emmc fault then