Related
I dunno what went wrong here...
1) I have GT-I9505 (SSN: -I9505GSMH). I installed Galaxy S4 toolkit
2) Reboot into download mode. Used toolkit/Odin to root phone. Boots up. See SU.
3) Reboot into download mode. Used toolkit/Odin. Flashed TWRP Recovery
4) Phone boots up normal. Reboot into TWRP recovery. Did a factory Reset. Format.
5) Installed Zip (Latest Omega 9.0 ROM), unchecked the things I didn't want to install. Completed install, no errors reported. Rebooted.
6) Phone stuck on Samsung boot screen. I left it overnight thinking sometimes it may take 15 mins to boot system after new install.
7) Woke up, battery dead. Tried to charge phone. No charging indicators when plugged in. With whatever juice I had left I booted into TWRP recovery, it starts to charge again as I see the % batter increase after 5 mins.
-=-=-=-=- Did the Following to try to repair
a) Reinstalled Omega, this time leaving alll options on. Rebooted, stuck in Samsung boot
b) Flashed Phil CWM touch recovery, did complete wipe to install new ROM. Rebooted into Phil recovery. Flashed OMEGA. Reboot, stuck in Samsung boot.
c) Rebooted into Phil recovery, installed echo ROM, rebooted. Black screen. Rebooted into Phil. This time cannot get into recovery.
d) Started panicking, used Odin flashed TWRP. Would not flash. Something displayed about PIT error. Flashed Phil again. Reboot into recovery, WORKS! (recovery only). Went back into Download mode flashed TWRP. Rebooted, also WORKS!. Did a factory wipe. During wipe there was an error. Format, factory reset, error during wipe. Flashed OMEGA. Reboot. Stuck on samsung boot loop.
e) Downloaded official Samsung kernal for i9505 thinking it was the full flash rom. Flashed with ODIN (hoping to put everything back to factory). Completed flash, phone boots. I get OMEGA ANIMATION!!! Waited for 15 mins. Stuck on Animation. Reflashed TWRP. Rebooted, installed OMEGA...again. Stuck on samsung boot screen.
-=-=-= Kinda frustrated. What did I do wrong in the beginning?
There are so many official roms for the S4 based on region. What can I do to put it back to factory again? I purchased phone in Australia @ Samsung store. I figured download the Australia ROM but there are like 5 of them 4 being network branded roms I think. THe other one XSA is unbranded?
I tried searching for help but so far nothing works.
omega ROM or any other custom ROM uses single CSC so before booting into system you must boot into stock recovery to apply CSC of that ROM, download stock recovery of that firmware the ROM was built from
after applying CSC it will work if not flash Omega 9.0 again , it will work :good::good:
arnob_xperia said:
omega ROM or any other custom ROM uses single CSC so before booting into system you must boot into stock recovery to apply CSC of that ROM, download stock recovery of that firmware the ROM was built from
after applying CSC it will work if not flash Omega 9.0 again , it will work :good::good:
Click to expand...
Click to collapse
Thanks for responding
So I take it when I did the full factory wipe and FORMAT the formatting part erased the CSC?
The steps are:
1) Find stock recovery of the original ROM OMEGA was built on. Use odin, flash that specific recovery. ( I might as well do a complete flash of the original stock firmware)
2) Use odin, replace recovery with TWRP, flash Omega this time no formatting
Reboot should be ok?
kabloomz said:
Thanks for responding
So I take it when I did the full factory wipe and FORMAT the formatting part erased the CSC?
The steps are:
1) Find stock recovery of the original ROM OMEGA was built on. Use odin, flash that specific recovery. ( I might as well do a complete flash of the original stock firmware)
2) Use odin, replace recovery with TWRP, flash Omega this time no formatting
Reboot should be ok?
Click to expand...
Click to collapse
first use CWM or TWRP or whatever you want and format everthing
flash a fresh firmware(latest i prefer)
then flash stock recovery via odin of the built version what v9 was used, simply reboot to recovery and it will say MULTI CSC APPLIED from fresh frimware you used
then flash TWRP/CWM and flash v9
again simply reboot to recovery and it will say MULTI CSC APPLIED from V9
it will reboot, you must need to apply CSC to boot your phone
I can confirm this!
I was trying to flash Omega 9 on top of jamal's 4.3 and my phone always booted to recovery. So I restored my stock touchwiz (no custom recovery or even root) nandroid backup and applied Omega 9: it worked!
douglascamata said:
I was trying to flash Omega 9 on top of jamal's 4.3 and my phone always booted to recovery. So I restored my stock touchwiz (no custom recovery or even root) nandroid backup and applied Omega 9: it worked!
Click to expand...
Click to collapse
thats right stock recovery boot is needed to apply CSC
problem
I need help. I am on stock build i9505XXUBMG5. then I rooted it using CF-autoroot. and i used the 1.85 version of ODIN. (Does the version of ODIN affect how the phone is rooted?) Anyways, After that, it is rooted. then after some time, my Wifi is not working or not turning on. I checked google and found the *#0011# method and turned off the Wifi power saving. Then, at first, it worked. After a while, the problem insists. but randomly turns on. I observed that in the *#0011# -> wifi window, the state is power off. but when it is completely not turning on, the state is now disconnected. How can I fix this?
I tried flashing Omega ROM, because there was a wifi fix on that ROM. But when I finished flashing it and continue to reboot, it's stuck on the boot animation. It is not even the Omega robot animation, just the original animation. (Another problem) i tried wiping cache, delvik cache and data but nothing happens.
macoy_412 said:
I need help. I am on stock build i9505XXUBMG5. then I rooted it using CF-autoroot. and i used the 1.85 version of ODIN. (Does the version of ODIN affect how the phone is rooted?) Anyways, After that, it is rooted. then after some time, my Wifi is not working or not turning on. I checked google and found the *#0011# method and turned off the Wifi power saving. Then, at first, it worked. After a while, the problem insists. but randomly turns on. I observed that in the *#0011# -> wifi window, the state is power off. but when it is completely not turning on, the state is now disconnected. How can I fix this?
I tried flashing Omega ROM, because there was a wifi fix on that ROM. But when I finished flashing it and continue to reboot, it's stuck on the boot animation. It is not even the Omega robot animation, just the original animation. (Another problem) i tried wiping cache, delvik cache and data but nothing happens.
Click to expand...
Click to collapse
Do you have an IMEI showing on your phone? What recovery did you use to flash Omega?
It matters, because some recoveries will screw it up.
Do you try to install with Philz recovery?
Sent from my GT-I9505 using xda premium
macoy_412 said:
I need help. I am on stock build i9505XXUBMG5. then I rooted it using CF-autoroot. and i used the 1.85 version of ODIN. (Does the version of ODIN affect how the phone is rooted?) Anyways, After that, it is rooted. then after some time, my Wifi is not working or not turning on. I checked google and found the *#0011# method and turned off the Wifi power saving. Then, at first, it worked. After a while, the problem insists. but randomly turns on. I observed that in the *#0011# -> wifi window, the state is power off. but when it is completely not turning on, the state is now disconnected. How can I fix this?
I tried flashing Omega ROM, because there was a wifi fix on that ROM. But when I finished flashing it and continue to reboot, it's stuck on the boot animation. It is not even the Omega robot animation, just the original animation. (Another problem) i tried wiping cache, delvik cache and data but nothing happens.
Click to expand...
Click to collapse
At this point I think it is the CSC issue arnob-xperia mentioned.
This is how I corrected my issue.
1) Omega v10 uses newer base FW. In their description it tells u. (ex: ver 9 uses XUBMG5). Search on the i9505 forums here. I can't link for some reason I can't see any of the stickied threads, especially the one listing all avail stock firmwares.
Flash into Philz or TWRP do a complete wipe of everything including data. etc.
You MUST download the full firmware, Not just the smaller kernel and recovery or csc. The full stock fw is usually over 1.6 GB. Anything around that range and u got the right one for Odin flash with the md5. Use Odin to flash. I used 1.85 and it was fine.
2) Once done it will reboot and in theory you are stock everything. At this point, for me somehow the phone got stuck in fricken boot loop. I pulled out battery, reboot into stock recovery and made sure I saw the multicsc. Rebooted. Still boot loop.
After hours of doing all sorts of things and putting the phone aside for a day. Came back, flashed the stock fw again using Odin. Reboot into recovery. Check the multi csc. Reboot. Stuck in boot loop. Reboot to download mode. Then I decided to ROOT the phone for ****s and giggles. This worked!
Phone booted.
3) Now you have stock (for that specific OMEGA fw) w/ the matching CSC. From here on follow OMEGA flash instructions for the specific things it tells u to wipe. DO NOT DO A FULL WIPE/FORMAT like I did (what got me in the mess to begin with).
** For Galaxy S3s, S4s, for some reason I've always had problems with TWRP. I had better luck using Philz. Everyone's personal experience varies on this one.
** I think the problem has to do with the CSC which handles specific region phone and carrier modes. This doesn't mean that it won't work if you use a diff region CSC. Just that it has to match the FW base you are using otherwise you have all sorts of problems. After that you can go in android and setup your APNs etc if you have probs with data. I didn't have this problem and was testing using the UK fw base on AU network sim.
*** Why does Samsung make things so damn complicated. I remember way back in 2k3 using fricken ODIN (samsung flashing utitility) to flash **** and it was the same setup as now. This whole crap about CSC pairing is a bit annoying. It is bad enough there are 6+ variations of S4s lol...
Hope this helps.
wifi problem
kabloomz said:
At this point I think it is the CSC issue arnob-xperia mentioned.
This is how I corrected my issue.
1) Omega v10 uses newer base FW. In their description it tells u. (ex: ver 9 uses XUBMG5). Search on the i9505 forums here. I can't link for some reason I can't see any of the stickied threads, especially the one listing all avail stock firmwares.
Flash into Philz or TWRP do a complete wipe of everything including data. etc.
You MUST download the full firmware, Not just the smaller kernel and recovery or csc. The full stock fw is usually over 1.6 GB. Anything around that range and u got the right one for Odin flash with the md5. Use Odin to flash. I used 1.85 and it was fine.
2) Once done it will reboot and in theory you are stock everything. At this point, for me somehow the phone got stuck in fricken boot loop. I pulled out battery, reboot into stock recovery and made sure I saw the multicsc. Rebooted. Still boot loop.
After hours of doing all sorts of things and putting the phone aside for a day. Came back, flashed the stock fw again using Odin. Reboot into recovery. Check the multi csc. Reboot. Stuck in boot loop. Reboot to download mode. Then I decided to ROOT the phone for ****s and giggles. This worked!
Phone booted.
3) Now you have stock (for that specific OMEGA fw) w/ the matching CSC. From here on follow OMEGA flash instructions for the specific things it tells u to wipe. DO NOT DO A FULL WIPE/FORMAT like I did (what got me in the mess to begin with).
** For Galaxy S3s, S4s, for some reason I've always had problems with TWRP. I had better luck using Philz. Everyone's personal experience varies on this one.
** I think the problem has to do with the CSC which handles specific region phone and carrier modes. This doesn't mean that it won't work if you use a diff region CSC. Just that it has to match the FW base you are using otherwise you have all sorts of problems. After that you can go in android and setup your APNs etc if you have probs with data. I didn't have this problem and was testing using the UK fw base on AU network sim.
*** Why does Samsung make things so damn complicated. I remember way back in 2k3 using fricken ODIN (samsung flashing utitility) to flash **** and it was the same setup as now. This whole crap about CSC pairing is a bit annoying. It is bad enough there are 6+ variations of S4s lol...
Hope this helps.
Click to expand...
Click to collapse
I did flash the Omega v9.1 and applied the wifi fix but the wifi is still broken. I tried unrooting it by flashing the original rom and formatting the data but the wifi is still broken. I can't turn it on. Thanks for the instructions anyways. ))
no pit partition
also, when i tried to root it again, it fails and says there is no PIT partition..
Where is the csc in TWRP so I can so what ones on the phone..??
What stock firmware can I use for a Orange Network in the UK.
GT-i9505 stuck on boot when upgraded from omega v16 to v21
Hello guys,
Well, I followed all the instructions and flashed new bootloader and new modem and after that I installed omega v21 with Full swipe. After that I ended up stuck in boot animation. :s What to do? I already tried to re-flash modem and bootloader, updated CWM and tried to re-install that v21 and after that I flashed twrp over cwm and tried to re-install v21 but always I ended up stuck in that boot animation. :S All installs were successful, but it just wont boot.
What to do?
Hopefully you understand my problem.
Cheers from Finland!
Nico
EDIT:
Ok, I flashed omega rom v19 with full wipe and tried to boot. Didnt work, but then I installed Kies to my computer, opened Kies, Plugged USB in and started my phone and then Kaboom! It booted. What exactly happened there?
BizK1d said:
Hello guys,
Well, I followed all the instructions and flashed new bootloader and new modem and after that I installed omega v21 with Full swipe. After that I ended up stuck in boot animation. :s What to do? I already tried to re-flash modem and bootloader, updated CWM and tried to re-install that v21 and after that I flashed twrp over cwm and tried to re-install v21 but always I ended up stuck in that boot animation. :S All installs were successful, but it just wont boot.
What to do?
Hopefully you understand my problem.
Cheers from Finland!
Nico
EDIT:
Ok, I flashed omega rom v19 with full wipe and tried to boot. Didnt work, but then I installed Kies to my computer, opened Kies, Plugged USB in and started my phone and then Kaboom! It booted. What exactly happened there?
Click to expand...
Click to collapse
Hi, I am having the same problem. First I installed the new firmware (NA5) and modem, tested it with the Omega ROM v21 and boot caught on so now tested the rom Fox Hound 4.1 and am having the same problem.
Kies tested this option but have not had the same luck as you. = /
Anyone know the reason? The rom Google Edition Jamal runs on my phone.
i9505
Hi all,
I was running the official Google 5.1.1 version until this morning. I now did an oem unlock using fastboot and installed the latest twrp recovery 3.0.0, and finally copied overy CM-13 nightly (and Chroma-2016-02 for testing purposes) using adb.
Flashing itself work flawless, there is no warning or error message, but when hitting "Reboot" within twrp the Google logo shows up for a few seconds and it directly boots into twrp again. This is with both, CM-13 and the latest Chroma.
So I basically cannot get my Nexus-4 bootet regulary any more.
Any ideas what the problem might be?
Any help is welcome,
regards, mistersixt.
Mmmh, strange, I did a factory installation (latest 5.1.1 from Google) and started the same thing from scratch ... and guess what... the system is booting fine now.
No idea why it did not work on my first attempt .
Regards, mistersixt.
mistersixt said:
Hi all,
I was running the official Google 5.1.1 version until this morning. I now did an oem unlock using fastboot and installed the latest twrp recovery 3.0.0, and finally copied overy CM-13 nightly (and Chroma-2016-02 for testing purposes) using adb.
Flashing itself work flawless, there is no warning or error message, but when hitting "Reboot" within twrp the Google logo shows up for a few seconds and it directly boots into twrp again. This is with both, CM-13 and the latest Chroma.
So I basically cannot get my Nexus-4 bootet regulary any more.
Any ideas what the problem might be?
Any help is welcome,
regards, mistersixt.
Click to expand...
Click to collapse
Same here. Running stock until today, wanted to see a different ROM, flashed TWRP 3.0.0, it refused to boot anything else. Tried to flash DU, then tried Chroma. Did a full wipe, then an advanced wipe selecting everything, then a full format, same thing. Installed TWRP 2.8.7, same thing. Finally installed latest stock, it is now booting, optimizing apps. I don't know if installing a custom rom will work or not yet.
Edit: Yeap, after flashing stock 5.1.1 and installing TWRP 3 again, the phone is now booting into DU.
First time I did a wipe with TWRP, it complained that it couldn't mount /data. Since this is the first time doing it, I assumed it was normal. After going through a full format, it didn't complain about data anymore, but it did complain about something to do with /dev/zero and another file under /dev/. I assume it was trying to dd /dev/zero to a file under /dev/ that didn't exist.
+1
Done the whole process from scratch again and worked like a charm
Hello, same story here.
First I:
- unlocked bootloader
- flashed TWRP (last version)
- flashed Chroma and Gapps
- reboot
=> I consistently rebooted on TWRP. No way to properly install the ROM. No error message at all.
Then I found this thread, and did as described:
- flashed the latest stock ROM
- flashed TWRP again (took me ages to manage to do this: TWRP would not install. I don't know how I finally did it, but at some point it suddenly worked. Probably a driver problem)
- flashed Chroma and Gapps again
Bingo, this time it worked! I don't know why it didn't work the first time. Could it be linked to the bootloader unlock thing?
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....
Hi everyone
I flashed the stock 6.01 firmware and everything flashed fine.I didn't flash the recovery because I had TWRP but ended up flashing it again anyways.My issue is now when I restart my phone or turn it on it boots into fastboot and I have to manually select "start" to get into android.I'm using LOS 14.1 now but this issue is still manifesting so its not the ROM.
Any ideas guys?Appreciate the help
Okay I solved it.I did something wrong during flashing as I was using an old guide.Everything is fine now since I used the guide on github
I flashed AOSP Extended yesterday everything went well, but me not thinking about it ended up flashing the Clark Simple Kernel and it flashed successfully and I rebooted it showed the Motorola logo it vibrated the screen went black and it did the same thing again it wasn't going to reboot. I was able to go into TWRP recovery by pressing the power and volume down I went to into the wipe section did the swipe to factory reset but it just froze and ended up continuously vibrating for a few seconds and it rebooted again. I then went to into my backups and restored AICP ROM but almost at the middle it just rebooted and did the same thing I went back into TWRP restored the AOSP ROM and it did the same thing. I then went into advanced wipe I wiped Dalvik/Art Cache, system, and cache successfully I then tried to wipe the data but that's when I phone just vibrated for a few seconds and it rebooted. I then repaired Dalvik/Art Cache, system, and cache and Mirco SDCard that didn't work as I went into my backups to restore and at the middle it just rebooted and it went to the Motorola logo screen it vibrated the screen went black and I went back into TWRP again. I then flashed a clean AICP ROM from the install section it flashed successfully I ended up rebooting thinking that it finally worked but I just ended up in the moto logo screen again. So I went into the install section flashed the clean version of the AOSP Extended ROM it was successful I rebooted and it worked. But know I went to the Wipe Section Swipe to factory reset and it just vibrates for a few seconds as it did before what should I do?
I have TWRP Version 3.1.1-0
Which firmware/modem are you on?
It sounds like you're on the N firmware/modem. There is a different version of TWRP for this setup.
It also seems like you tried to flash a kernel that is not for that firmware/modem combo (as far as I know Simple hasn't been updated to work with the newer N firmware/modem), which is why it didn't boot.
I have android 7.1.2 Nougat but how can I fix my problem?
Sent from my XT1575 using XDA Free mobile app
R77 said:
I have android 7.1.2 Nougat but how can I fix my problem?
Sent from my XT1575 using XDA Free mobile app
Click to expand...
Click to collapse
What android version was before custom?
Before I flashed a custom ROM I had Marshmallow 6.0.1 pure stock when it came in the box.
Sent from my XT1575 using XDA Free mobile app
Last version of Motorola Original Android on MXS/P.
I'm not asking about custom roms.
I think it can be Lolipop or Marschmallow. So you have LL or MM baseband.
AICP works on ≤MM baseband, AOSP - two versions - ≤MM & =N, clark simple kernel is only for MM.
Problems with twrp - try this solution:
https://forum.xda-developers.com/mo...ial-resurrection-remix-v5-8-3-t3637204/page44 from #433
---------- Post added at 09:58 AM ---------- Previous post was at 09:56 AM ----------
N - Nougat, you haven't N baseband - u can't flash it.
So I clicked on the link and it took me to the TWRP downloads which version of it should I flash?
Sent from my XT1575 using XDA Free mobile app
R77 said:
So I clicked on the link and it took me to the TWRP downloads which version of it should I flash?
Sent from my XT1575 using XDA Free mobile app
Click to expand...
Click to collapse
Sorry #434, link to:
https://forum.xda-developers.com/showpost.php?p=74713790&postcount=54 and there to AFH.
dzidexx said:
Sorry #434, link to:
https://forum.xda-developers.com/showpost.php?p=74713790&postcount=54 and there to AFH.
Click to expand...
Click to collapse
It works I flashed the recovery.img on TWRP and was able to swipe to factory reset without any problems but when I went into my old backups like AICP it restored normally I rebooted my phone at the Moto Logo screen, it vibrated and turned off and did the same thing again. So I wiped and flashed a clean version of AICP it flashed successfully rebooted without any problems installed my apps realized it wasn't rooted so I went into recovery flashed Magisk-v14.0.zip and simple kernel again rebooted but it wouldn't go the Moto logo it just rebooted again. I ended up doing a factory reset and flashed AICP by itself had no problems then decided to flash Magisk-v14.0.zip that I had saved but booted fine but at the AICP logo it froze and went to back to the Moto logo screen. So I decided to download a clean version of Magisk-v14.0.zip but that didnt work so I then flashed AICP by itself and no problems. What should I do?
Aicp hasn't magisk inbuilt? 14.5? @R77
I should flash Magisk v14.5 beta instead?
Edit: I ended up flashing the beta version it flashed successfully booted up and at the lockscreen it just rebooted by itself back to the lockscreen again it was unresponsive, and no magisk is not build in the ROM. Going back to another AICP backup so what happens.
Edit again: Well my backups don't work it restores successfully but it goes in a bootloop it goes to the Moto logo boots up again. It only boots successfully when I flash clean version of AICP ROM and has no problems. What should I do?
Sent from my XT1575 using XDA Free mobile app
dzidexx said:
Aicp hasn't magisk inbuilt? 14.5? @R77
Click to expand...
Click to collapse
I should flash Magisk v14.5 beta instead?
Edit: I ended up flashing the beta version it flashed successfully booted up and at the lockscreen it just rebooted by itself back to the lockscreen again it was unresponsive, and no magisk is not build in the ROM. Going back to another AICP backup so what happens.
Edit again: Well my backups don't work it restores successfully but it goes in a bootloop it goes to the Moto logo boots up again. It only boots successfully when I flash clean version of AICP ROM and has no problems. The only backup that worked was AOSP. What should I do?
Sent from my XT1575 using XDA Free mobile app
obsolete1 said:
Which firmware/modem are you on?
It sounds like you're on the N firmware/modem. There is a different version of TWRP for this setup.
It also seems like you tried to flash a kernel that is not for that firmware/modem combo (as far as I know Simple hasn't been updated to work with the newer N firmware/modem), which is why it didn't boot.
Click to expand...
Click to collapse
It works I flashed the recovery.img on TWRP and was able to swipe to factory reset without any problems but when I went into my old backups like AICP it restored normally I rebooted my phone at the Moto Logo screen, it vibrated and turned off and did the same thing again. So I wiped and flashed a clean version of AICP it flashed successfully rebooted without any problems installed my apps realized it wasn't rooted so I went into recovery flashed Magisk-v14.0.zip and simple kernel again rebooted but it wouldn't go the Moto logo it just rebooted again. I ended up doing a factory reset and flashed AICP by itself had no problems then decided to flash Magisk-v14.0.zip that I had saved but booted fine but at the AICP logo it froze and went to back to the Moto logo screen. So I decided to download a clean version of Magisk-v14.0.zip but that didnt work so I then flashed AICP by itself and no problems. What should I do?
Edit: I ended up flashing the beta version of Magisk it flashed successfully booted up and at the lockscreen it just rebooted by itself back to the lockscreen again it was unresponsive, and no magisk is not build in the ROM. Going back to another AICP backup so what happens.
Edit again: Well my backups don't work it restores successfully but it goes in a bootloop it goes to the Moto logo boots up again. It only boots successfully when I flash clean version of AICP ROM and has no problems. The only backup that worked was AOSP. What should I do?
Sent from my XT1575 using XDA Free mobile app
Flash Resurrection Remix.
If you have MM modem - 21.nov., for N - 04.dec.
https://forum.xda-developers.com/mo...ial-resurrection-remix-v5-8-3-t3637204/page36
https://forum.xda-developers.com/showpost.php?p=74737565&postcount=397
If you don't know modem version - flash stock first.
dzidexx said:
Flash Resurrection Remix.
If you have MM modem - 21.nov., for N - 04.dec.
https://forum.xda-developers.com/mo...ial-resurrection-remix-v5-8-3-t3637204/page36
https://forum.xda-developers.com/showpost.php?p=74737565&postcount=397
If you don't know modem version - flash stock first.
Click to expand...
Click to collapse
I didn't see MM modem - 21.nov., for N - 04.dec
I just saw Resurrection Remix version from July 14 to August 13?
Sent from my XT1575 using XDA Free mobile app
R77 said:
I didn't see MM modem - 21.nov., for N - 04.dec
I just saw Resurrection Remix version from July 14 to August 13?
Sent from my XT1575 using XDA Free mobile app
Click to expand...
Click to collapse
Very funny, Resurrection Remix 5.8.5:
21 XI 2017
https://forum.xda-developers.com/showpost.php?p=74626773&postcount=351
04 XII 2017
https://forum.xda-developers.com/showpost.php?p=74737565&postcount=397
Modem - you should know what you have onboard.
dzidexx said:
Very funny, Resurrection Remix 5.8.5:
21 XI 2017
https://forum.xda-developers.com/showpost.php?p=74626773&postcount=351
04 XII 2017
https://forum.xda-developers.com/showpost.php?p=74737565&postcount=397
Modem - you should know what you have onboard.
Click to expand...
Click to collapse
So I ended up flashing the unofficial Resurrection Remix flashed successful but got stuck at the moto logo, did a clean wipe and flashed the official nougat Resurrection Remix and it worked. I then decided to flash the simple kernel but got stuck at bootloop did a clean wipe restored my backup of Remix ended up flashing handbag kernel and booted up with no problems. What should I do for that?
What can't you understand?
You had stock Nougat - you have Nougat modem/baseband.
The same for stock MM.
RR 4 XII works only with N modem.
Simple kernel works only with MM modem.
@R77
i went through something like this recently, and my story is posted here: https://forum.xda-developers.com/showpost.php?p=74779723&postcount=417 . I couldn't get anywhere in Recovery, including dirty flashing another rom, because the process wouldn't complete. I ended up running the nougat firmware update "Moto X Pure Factory Firmware Nougat NPH25.200-22" via bootloader. Then unlocked, flashed TWRP, then put RR 12/4 rom on, but im still dealing with glitches (gps lock is horrible/lte signal is worse) (unsure if rom based or firmware from nougat). hope this info helps
The_Bizzel said:
i went through something like this recently, and my story is posted here: https://forum.xda-developers.com/showpost.php?p=74779723&postcount=417 . I couldn't get anywhere in Recovery, including dirty flashing another rom, because the process wouldn't complete. I ended up running the nougat firmware update "Moto X Pure Factory Firmware Nougat NPH25.200-22" via bootloader. Then unlocked, flashed TWRP, then put RR 12/4 rom on, but im still dealing with glitches (gps lock is horrible/lte signal is worse) (unsure if rom based or firmware from nougat). hope this info helps
Click to expand...
Click to collapse
I'm wondering will going back to Marshmallow fix my problem?
I have RR N final and have no problems but flashing AICP ROM with magisk and it won't boot, it will only boot with just the ROM alone?