Hi,
I'm fooling around with my z3c trying to get it to an acceptable rooted state. The route I've taken is I've followed the steps in bilboa1's how-to post, up to step 25. After that i figured I could just as well flash one of the existing pre-rooted images instead of doing the dance with two images (as suggested by someone in post #159 of that thread), and this worked for me, partially. I'm using wajk's SLiM ROM at the moment.
EDIT: Reading through this, I realized I should have tried
What I don't understand is why boot loops occur randomly (-or not) when I'm doing this. I've had varying success with different ROMS:
- Wajk's ROM: Success twice, boot loop once
- My own PRFCreated Rom, based on Nordic Stock from this thread: No success at all, boot loop twice
- My recovery (created with TWRP) of the Wajk installation: Success once, boot loop once.
- @evildog1's image ("23.4.A.1.264 - Unbranded - NORDIC (1288-5411) [...]" from the pre-rooted ROMs thread: boot loop once (perhaps I should have tried more)
Every time I encounter a boot loop I go back into recovery (TWRP), wipe dalvik and cache, power off, wait for a while, flash the rom again, wipe again, power off again, etc, and varying combinations thereof. Sooner or later I will get out of the loop. Not with my home-grown ROM though, which is a pity, because I wanted to have a rooted stock ROM to be able to use Xposed. Wajk's ROM works great but there appears to be a lot of conflict with variuos Xposed modules (which I guess is expected), so I haven't been able to come up with a combination that allows me to choose a dark UI for instance.
I should add that when I say boot loop, I mean the scenario where the phone get's stuck on the boot animation and never finishes. It's not really a 'loop', I guess.
However, it should be obvious from all this that I'm just poking around with no clear understanding of what I'm doing. Why do I get different results from what I believe to be the same procedure? It seems likely that I'm not doing the PRFCReate thing right and that my ROM is corrupt. Or, perhaps I'm not doing the right steps to prepare the phone when flashing a different ROM. Or, perhaps my interpretation of bilboa1's method is dumb. Or perhaps I'm committing a lot of different errors that all result in similar boot loops. Is there perhaps a way to diagnose different boot loop causes?
I'd be grateful for any insight into this that you care to share. Thank you.
EDIT: I decided to give evildog's ROM another go. I finally got it to boot and managed to install Xposed, paying closer attention to what I was actually doing. This is the entire sequence:
Factory reset -> flash ROM -> Wipe Dalvik -> Power off/on -> Boot loop -> wipe Dalvik -> Power off/on -> Booted OK -> flash Xposed zip -> Wipe Dalvik -> Boot loop -> Power off/on -> Wipe Dalvik -> Boot loop -> Power off/on -> Wipe Dalvik -> Booted OK
This is my MO, more or less. In the end things work out but I don't know how or why. Still interested in learning about this.
Hello
I'm using 23.4.A.1.264 - Unbranded - NORDIC on my D5803 and i never got any bootloops. If you flashed D5803 ROMs on D5833, then the problem will occur.
My steps
1. Wipe everything except internal and external Sdcard
2. Flash the ROM on TWRP
3. Boot the phone and it took 10 min to boot for the first time
Thank you. Perhaps I'm not waiting long enough before I get impatient and shut the phone off. And, perhaps, cause problems that weren't there from the start. Your ROM works well once I got through my shutting-of-the-phone-too-early process. I'm using wajk's ROM again now, since I discovered it's actually possible to do some theming after all, using LPthemer.
Next time I flash something I'll wait longer. Mystery solved (I hope)...
Related
Hello. After i read/followed more than one tutorial on this matter, i rooted my milestone 1 and tried to install a custom rom to it. From the several attempts that i made, only miui installation was successful, even if after installation the recovery yellow triangle appeared, and had to make another "wipe data" and wipe cache", after which the phone started as normal. The problem is that i immediately figured that i don`t like miui, so, after following the same procedure, i tried over and over again to install cronos or cm7.2 kang, again with wiping data/cache, then wiping the last 3 options in the following menu. Everything seems to work fine, until i reboot the phone, and either enters recovery mode again, either stays with the motorola logo- i waited for about 7 minutes, but nothing happened. Can anyone tell me what am i doing wrong, because i did this over and over again.
I have a video with the whole process, but i can`t post any links here(it appears on my edydear21 account on flickr)
Any sugestions will be appreciated !
post scriptum: i eventually managed to get HO!NO! ics edition rom in the same way i did with the miui. Since i`m fed up with process of changing roms, i`l just settle fo the one i managed to get going.
Try out THIS guide. This one tells you what you need to do and how to do it.
Very noobish issue. Rooted, unlocked bootloader on Atrix HD. Set up SafeStrap as recovery. Everything checked and working. After letting SafeStrap install Cyan 10.3 and rebooting, phone entered CyanogenMod boot screen and become stuck for an hour. Realized that I forgot to reset and wipe all stock settings and cache (yes, I know that should have been obvious step). Figured I could just go into SafeStrap and make the quick fix.
Seems that I'm unable to enter my custom recovery, instead I'm lead to the familiar bricked android stock recovery. No options to access stock rom (assuming it was deleted during install or lost, etc). Tried installing a different recovery, but fastboot on PC is unable to find device. Help at this point is very much appreciated, either to do any of the following:
1. Somehow access SafeStrap again (assuming that it wasn't wiped aswell) so I can clear stock settings and cache, get Cyan 10.3 going properly.
2. Instructions/links to another method to otherwise forcibly delete stock settings and cache (please keep in mind, fastboot is currently unable to find device).
3. Otherwise completely clear phone of EVERYTHING, then reinstal stock recovery and or/stock ROM so I can give up on flashing custom and stick with stock.
*Update:
Was finally able to get phone into AP Fastboot Flahsh Mode. My computer itself can't see the phone, but device manager shows it as "Fastboot QINARA S" and I'm able get a response through my PC's end of flashboot.
Tried using RSD lite to install a stock ROM, but no success since the phone isn't off and can't be turned off without trying to go into another Boot Loop. Also tried installing a new recovery through fastboot, but I keep getting the response, "(Bootloader) variable not supported."
At this point, I'd be really happy if I could get the proper commands to wipe and factory reset my phone while in fastboot. At least then I'd have Cyan. I could try installing stock if it continued to glitch.
Update Motorola drivers on your computer and check threads for fastboot files from skeevydude.
Sent from my MB886 using XDA Premium 4 mobile app
Well safestrap is for use with locked bootloaders so there lies your problem. Maybe you can make a factory cable or buy one to put your phone into fastboot so you can flash stock through rsd.
Sent from my PACMAN MATRIX HD MAXX
http://forum.xda-developers.com/showthread.php?t=2226527
Sent from my MB886 using XDA Premium 4 mobile app
SkunkID said:
*Update:
Was finally able to get phone into AP Fastboot Flahsh Mode. My computer itself can't see the phone, but device manager shows it as "Fastboot QINARA S" and I'm able get a response through my PC's end of flashboot.
Tried using RSD lite to install a stock ROM, but no success since the phone isn't off and can't be turned off without trying to go into another Boot Loop. Also tried installing a new recovery through fastboot, but I keep getting the response, "(Bootloader) variable not supported."
At this point, I'd be really happy if I could get the proper commands to wipe and factory reset my phone while in fastboot. At least then I'd have Cyan. I could try installing stock if it continued to glitch.
Click to expand...
Click to collapse
The error is from using the wrong fastboot executable. Look at post 5. If you get a stickybit error, search our general forums for "stickybit" and you'll find that fix.
deeje00 said:
Well safestrap is for use with locked bootloaders so there lies your problem. Maybe you can make a factory cable or buy one to put your phone into fastboot so you can flash stock through rsd.
Sent from my PACMAN MATRIX HD MAXX
Click to expand...
Click to collapse
With a bit of creativitity one could use SSR to dual boot Holo Blur and Batakang....or two custom 4.3's that use the same kernel....PAC + Carbon both with arrrghhh's kernel.....Only problem is ya can't be a noob at all if ya do it.
Solved issue...somehow.
Used method shown in link below to install stock recovery image since Safety Strap was apparently deleted/wiped/banished?
(can't link, still noob poster. Just search, "[Guide] How to flash back to Stock Rom - chacha. Please Sticky This !", should be the first result.)
After installing stock recovery, was able to go to the standard dead android screen, but after punching the volume buttons randomly, the option menu for stock recovery opened. Was able to factory reset and wipe cache, then properly reboot. Cyanogenmod finally got out of it's BootLoop, and everything seems to be running fine. Flashed a non-official CWM (no offical CWM or Twrp avaliable for Atric HD) and got Gapps. Phone is finally running fine.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Lingering issues worth mentioning incase there are obvious fixes.
.Cyan likes to crash whenever running programs for the first time or doing do much activity in a short amount of time (I suspect the cache has something to do with the cleared cache since revisiting apps doesn't cause crashes as often). If it persists, I'll probably just back up and look for a more stable rom.
.All notification lights are white, except the battery notification lights, despite me changing the colors and/or allowing apps to use their own light settings.
When you're at the "dead Android" screen pressing Vol Down + Power pushes it into recovery, iirc - might seem random but there's a purpose behind it.
SkunkID said:
Solved issue...somehow.
Used method shown in link below to install stock recovery image since Safety Strap was apparently deleted/wiped/banished?
(can't link, still noob poster. Just search, "[Guide] How to flash back to Stock Rom - chacha. Please Sticky This !", should be the first result.)
After installing stock recovery, was able to go to the standard dead android screen, but after punching the volume buttons randomly, the option menu for stock recovery opened. Was able to factory reset and wipe cache, then properly reboot. Cyanogenmod finally got out of it's BootLoop, and everything seems to be running fine. Flashed a non-official CWM (no offical CWM or Twrp avaliable for Atric HD) and got Gapps. Phone is finally running fine.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Lingering issues worth mentioning incase there are obvious fixes.
.Cyan likes to crash whenever running programs for the first time or doing do much activity in a short amount of time (I suspect the cache has something to do with the cleared cache since revisiting apps doesn't cause crashes as often). If it persists, I'll probably just back up and look for a more stable rom.
.All notification lights are white, except the battery notification lights, despite me changing the colors and/or allowing apps to use their own light settings.
Click to expand...
Click to collapse
Hi, I am having the same issue you had... how the heck were you able to get back into stock recovery? Every time I try my phone just reboots and gets stuck again. I cant even turn off my phone with out it rebooting. I have read your posts and followed that other forum you mentioned but if I cannot boot into recovery and if my computer cant see my phone it wont work. Please help when you get a chance.
When I tried reinstalling Stable OxygenOS 4.1.6, the phone locks up upon install and setup screen. This goes for previous OS versions, as well. It takes force quits, restarts, and numerous install attempts and the phone still locks up. I tried stock recovery, old and new TWRP versions, all of which are clean installs, Nothing. LineageOS and other Hydrogen based roms still lock up, either at the setup screen, or when I try and activate developer options. Every Rom I tried after activating developer options, it doesn't leave the gear icon in the menu, either. It takes a restart (force quit) for it to show up. Also, WiFi doesn't work. Sometimes when I try and install OxygenOS either by sideloading, or through TWRP, the phone locks up at the wifi setup screen. This goes for every version of OxygenOS I tried. Your advice is appreciated. Thanks.
I had some problems last night while switching back and forth between Beta and stable. I could try to help but I'm not a guru at this, so wait for confirmation if you are not sure.
First I think you need the right TWRP version. 3.1.1-2 is the latest one, but I'm using 3.0.4-1 (flashed stableOOS with it) and everything is back to normal for me.
Try a clean flash of stableOOS. TWRP > Advanced wipe, select dalvik,cache,data,system and swipe.
Then install the OS. Don't reboot yet, and instead boot into recovery after going back. I read that this ensures you keep TWRP.
It may say No OS installed, but go ahead. Then boot into system again. This worked for me and I restored my backups
I just went from beta 10 to 4.1.6 and have no issues at all.
I followed the basic procedure, in TWRP (recommend to use the latest bluesparks one from his kernel thread - just TWRP no need for his kernel), I did a factory reset, (in TWRP just swipe to Factory reset from the WIPE screen where it says 'Most of the time this is all you need'), its correct nothing else needed, then flashed the full v416 file, then flashed Magisk 13.2, rebooted to system, that was all. TWRP was not lost with this method.
System booted to stable v4.1.6 and no issues.
Check what format are your partitions fornatted in. Make sure they are f2fs. Otherwise try the debrick tutorial. It helped me fix a lot of bugs on my 3T.
I tried all of the above, and I'm certain under the right circumstances, your advice would work. In the end, I used the unbrick tool which brought it back to it's original locked state, and I'm still running into issues. I wonder if there's a hardware issue somewhere that was the result of using Beta. The OS boots up and I'm finally able to access developer options, but no WiFi and the phone still refuses to restart or power off unless I do a hard shutdown. I've never seen anything like it. Numerous ROMS, recoveries, and sideload installs using the One Plus Recovery, and it still doesn't work.
Thanks for everyone's input, but I feel like this phone is done.
Hello everyone, how do you do?
I've got this phone that was running perfectly the stock rom, but I have that addiction to customize every phone I land my hands into (I guess some of you either haha).
But
This time something horrible happened, and I just can't back this phone to work. I'll tell what did I've done and I'm hopping you to help me (just paid a lot to fix the broken screen, don't want to buy a new board...)
Here we go: yesterday, several times I've tried to unlock the phone, and figure out that the fastboot command to do that have changed to fastboot oem unlock (at least in this phone), and had no need to copy that code into Motorola's page. After unlock, tried to install TWRP Recovery, several times, and finnaly got one that worked here. Okay. Ready to go. Also had difficulty to find a ROM that is compatible with this phone (I wanted some with Android 9, or 8.1, at least). I was capable to install the Lineage OS 15 Unnoficial for Nicklaus, but got stuck in Lineage OS Logo Screen. Fine. Downloaded the Lineage OS 14 Unnoficial (Android 7.1), flashed, and everything went fine! The ROM was installed, configured, but... My phone has the OnScreen Buttons for Navigation... And this ROM doesn't appear to get this to work... Every time I went to settings page and tried to enable this feature, the Settings Application stucks and phone restarts. So, at this point, I thought that the ROM was with some code problem, whatever, decided to download another. And (that was a HUGE MISTAKE). Downloaded the DotOS ROM here.
After flash, the ROM loaded up fine. Settings, ok, system, ok. But, the same problem with the Navigation Buttons. What? Again? Yes. Tried to enable via settings, but I realized that some configurations of Lineage OS installation is still there - forgot to wipe data before flashing ROM... But at this time (I guess it was 2AM) I had no patience to reboot, wipe, boot, configure, and decided to factory reset using the option in Settings menu. The DotOS shows me a logo saying "Wiping data". The phone reboots. And reboots. And reboots. But, the TWRP stills working, and tried many, many times to flash all sort of ROMs with no success at all.
I was going insane, you know, WHY I CAN'T FLASH THE ROM I'VE JUST FLASHED MINUTES AGO?? Got a clue: somehow when wiping data, DotOS bugged my /data partition (in TWRP, when wiping data, got an error in this partition, and cant fix it using TWRP fix menu). Tried a lot of tutorials over the internet to fix that partition, with no success. And, unfortunately, at that point my /system and /cache partition got broken too.
But, I had my secret weapon: THE STOCK ROM. Yes. Everytime all went wrong, is quite simple: just install the factory's ROM, and you will be fine. Right? Wrong. Really don't know why, I was not able to flash some images of the ROM (boot, recovery, system also). Thought I've downloaded the wrong Stock ROM. Tried another. And another. No success. What the hell? At this point my mind was not lucid enough, and decided to STUPIDLY FORMAT PARTITIONS BY MY SELF. Reboot Bootloader. Connect Cable. Fastboot.
fastboot devices -> OK
fastboot erase boot -> OK
fastboot erase userdata -> OK
fastboot erase system -> OK
That's it! Fixed! Now is just reboot, and... Reboot. Reboot. Reboot. Reboot.
Ok, Vol Down + Power. Nothing. Ok, Vol Up + Power. Nothing. Ok, Vol Up + Vol Down + Power, Vol Power + Dow Up, Fingerprint + Screen + Two Punches + Power. Nothing.
Stuck in boot loop. My worse nightmare. Thinked: okay, lets remove the battery, and... Remember I've just fixed the broken screen? Yeah. Out of lucky, the assistance tried THREE TIMES to change my screen, because the screen's provider at first provided a screen with ghost touches, at second a screen that had light glitches. At third, a correct screen. Don't want to loose my warranty, you know. If this third screen has some problem either? The assistance put that tag over the screw, you know. Can't take my battery off. But I really don't know if removing the battery will really help, because I've erased my boot partition. I hate me. My wife too (but she hated before). Now, got this tutorial: Ultimate Guide for [Bootloop Recovery] Noob Friendly, that is a little outdated, and can't help me. But gave me some hope: So, my phone isn't bricked yet! I can fix it!
But I really don't know how.
I hope someone helps me, and that this topic can be useful for any one who got stuck in Boot Loop from here to eternity.
Regards,
Fernando Garcia (sorry for my bad english, I only speak JavaScript)
fernandocg30 said:
Hello everyone, how do you do?
I've got this phone that was running perfectly the stock rom, but I have that addiction to customize every phone I land my hands into (I guess some of you either haha).
But
This time something horrible happened, and I just can't back this phone to work. I'll tell what did I've done and I'm hopping you to help me (just paid a lot to fix the broken screen, don't want to buy a new board...)
Here we go: yesterday, several times I've tried to unlock the phone, and figure out that the fastboot command to do that have changed to fastboot oem unlock (at least in this phone), and had no need to copy that code into Motorola's page. After unlock, tried to install TWRP Recovery, several times, and finnaly got one that worked here. Okay. Ready to go. Also had difficulty to find a ROM that is compatible with this phone (I wanted some with Android 9, or 8.1, at least). I was capable to install the Lineage OS 15 Unnoficial for Nicklaus, but got stuck in Lineage OS Logo Screen. Fine. Downloaded the Lineage OS 14 Unnoficial (Android 7.1), flashed, and everything went fine! The ROM was installed, configured, but... My phone has the OnScreen Buttons for Navigation... And this ROM doesn't appear to get this to work... Every time I went to settings page and tried to enable this feature, the Settings Application stucks and phone restarts. So, at this point, I thought that the ROM was with some code problem, whatever, decided to download another. And (that was a HUGE MISTAKE). Downloaded the DotOS ROM here.
After flash, the ROM loaded up fine. Settings, ok, system, ok. But, the same problem with the Navigation Buttons. What? Again? Yes. Tried to enable via settings, but I realized that some configurations of Lineage OS installation is still there - forgot to wipe data before flashing ROM... But at this time (I guess it was 2AM) I had no patience to reboot, wipe, boot, configure, and decided to factory reset using the option in Settings menu. The DotOS shows me a logo saying "Wiping data". The phone reboots. And reboots. And reboots. But, the TWRP stills working, and tried many, many times to flash all sort of ROMs with no success at all.
I was going insane, you know, WHY I CAN'T FLASH THE ROM I'VE JUST FLASHED MINUTES AGO?? Got a clue: somehow when wiping data, DotOS bugged my /data partition (in TWRP, when wiping data, got an error in this partition, and cant fix it using TWRP fix menu). Tried a lot of tutorials over the internet to fix that partition, with no success. And, unfortunately, at that point my /system and /cache partition got broken too.
But, I had my secret weapon: THE STOCK ROM. Yes. Everytime all went wrong, is quite simple: just install the factory's ROM, and you will be fine. Right? Wrong. Really don't know why, I was not able to flash some images of the ROM (boot, recovery, system also). Thought I've downloaded the wrong Stock ROM. Tried another. And another. No success. What the hell? At this point my mind was not lucid enough, and decided to STUPIDLY FORMAT PARTITIONS BY MY SELF. Reboot Bootloader. Connect Cable. Fastboot.
fastboot devices -> OK
fastboot erase boot -> OK
fastboot erase userdata -> OK
fastboot erase system -> OK
That's it! Fixed! Now is just reboot, and... Reboot. Reboot. Reboot. Reboot.
Ok, Vol Down + Power. Nothing. Ok, Vol Up + Power. Nothing. Ok, Vol Up + Vol Down + Power, Vol Power + Dow Up, Fingerprint + Screen + Two Punches + Power. Nothing.
Stuck in boot loop. My worse nightmare. Thinked: okay, lets remove the battery, and... Remember I've just fixed the broken screen? Yeah. Out of lucky, the assistance tried THREE TIMES to change my screen, because the screen's provider at first provided a screen with ghost touches, at second a screen that had light glitches. At third, a correct screen. Don't want to loose my warranty, you know. If this third screen has some problem either? The assistance put that tag over the screw, you know. Can't take my battery off. But I really don't know if removing the battery will really help, because I've erased my boot partition. I hate me. My wife too (but she hated before). Now, got this tutorial: Ultimate Guide for [Bootloop Recovery] Noob Friendly, that is a little outdated, and can't help me. But gave me some hope: So, my phone isn't bricked yet! I can fix it!
But I really don't know how.
I hope someone helps me, and that this topic can be useful for any one who got stuck in Boot Loop from here to eternity.
Regards,
Fernando Garcia (sorry for my bad english, I only speak JavaScript)
Click to expand...
Click to collapse
Hey, download the stock rom for your from here:
https://motostockrom.com/motorola-moto-e4-plus-xt1773
And follow this process to flash the rom on to your phone:https://androidmtk.com/flash-stock-rom-using-smart-phone-flash-tool
Warning for this phone flashing process:
In SP flash tool, "do not" select 'format all+ download'(the phone will be bricked). Only select 'Download only'.
Secondly deselect preloader after adding scatter file(flashing it will also brick the device).
This all warnings are already given in the flash guide, i just want you to give proper attention while doing it.
Hi everyone! I have been suffering with this problem for 2 full days on my S10 (SM-G973F/DS) and now i just have absolutely no idea how to fix it, so I thought it was worth writing about it here.
On stock, I used one old and outdated application that made user certificates system certificates, but which worked. Having tried it on EvolutionX 5.9.1 (Android 11), it brought the phone into a bootloop. I didn’t have a backup and because in order not to go through the installation process on a new one again, I decided that I would try to delete the folders from the data partition ONLY, but after half a day of attempts, nothing happened and I started to install the rom from scratch, but then weird things began to happen: after reinstallation/factory reset, boot animation randomly started (check attached video), which either went into an endless boot, or loaded the system back, but then if boot animation started on loading then this loading become endless, and the buttons (in the system) "Reboot to recovery", "Reboot to bootloader" and etc simply turning off the phone without booting into the recovery or bootloader, and if this happened, then somewhere in 2 minutes after turning it off.
I think i tried almost everything: re-installation according to the instructions, re-installation according to the way I did it before, I even tried to install the stock, and after the recovery again and then rom, but absolutely nothing changes, I cannot use custom rom if it is up to this worked fine and everything started on the same version as I was trying to install like before, I even tried to download the rom installation file again, not installing magisk-patch in boot, installing multidisabler, even find my old backup for TWRP that has every partition, but absolutely nothing changes, maybe someone knows how to fix it?
Thanks in advance!
P.S Stock rom works perfectly (android 11), but i want to use custom anyway (also android 11)