We’re excited to announce that we’ve released Remix OS 2.0 ROMs for Nexus 9 and Nexus 10. The Nexus 9 and Nexus 10 ROMs are now available for download here:
Nexus 9 ROM
http://www.jide.com/remixos/devices/nexus9
Nexus 10 ROM
http://www.jide.com/remixos/devices/nexus10
Flash Tutorial
http://support.jide.com/hc/en-us/articles/218081838
We’ve also been conscious of all the interest that Nexus 9 and 10 users have expressed in being able to experience Remix OS 2.0 on your tablets. And, although we’re still a relatively small team, we definitely heard your comments and are excited to finally have Remix OS 2.0 ready for you.
You can submit your bug report here:
http://bit.ly/1qh2jQq
Cheers
does this work on the lte variant?
Based on Android 5.11? No thanks.
I am not sure if I want to downgrade my nexus 9 to 5.11.
But Android 6.x and N are not good enough for me at least.
I am thinking if any other customize rom can be used.
Also Ubuntu for tablet might be a choice.
Any hopes of being able to load this via TWRP recovery? Or being able to load this via ADB while still keeping TWRP recovery?
Is there a possibility now to use google account and google services or still no?
Woofly said:
Any hopes of being able to load this via TWRP recovery? Or being able to load this via ADB while still keeping TWRP recovery?
Click to expand...
Click to collapse
You can fastboot flash while keeping twrp
maelfilk said:
Is there a possibility now to use google account and google services or still no?
Click to expand...
Click to collapse
It now comes with play store. Overall it's world's better than 1.5.
dictionary said:
You can fastboot flash while keeping twrp
It now comes with play store. Overall it's world's better than 1.5.
Click to expand...
Click to collapse
Sweet. Does it have Google Play Services as well? Are we able to run apps like Gmail and Play Music?
Woofly said:
Sweet. Does it have Google Play Services as well? Are we able to run apps like Gmail and Play Music?
Click to expand...
Click to collapse
Yes sir. Haven't tried play music, but running gmail and hangouts fine. When you fastboot flash things, just don't flash recovery. Also, I had to flash the old 5.1.1 bootloader and vendor first.
Anyone here NOT getting a bootloop after installing? what am i doing wrong here....
th3fallen said:
Anyone here NOT getting a bootloop after installing? what am i doing wrong here....
Click to expand...
Click to collapse
Working fine for me here. Was getting constant reboots and bootlooping before I flashed back to 5.1.1 first though. Bootloader and vendor especially. Then wiped everything but internal in TWRP, then fastboot flashed Remix except for twrp. Booted into TWRP before booting into the system. Worked great after that.
So does it work for LTE variant? Also anyone running custom kernel with it? (afaik FIRE-ICE has special kernel)
Bootloopers
To all those getting bootloop:
* Download latest 5.11 image LMY48T (not 6.x) https://developers.google.com/android/nexus/images#volantis
* In theory you only need to flash bootloader-flounder-3.44.1.0123.img however to be on the safe side I ran the whole ./flash-all.sh
* Now reboot the bootloader (even if you are already there, since we just flashed a different one), then run the following:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash cache cache.img
# flashing vendor.img will solve the problem of annoying messages on boot/unstable play services
fastboot flash vendor vendor.img
# there is no userdata.img , so we can wipe userdata like so:
fastboot -w
* Now reboot and it should work great. With my experience so far it seems very stable
dictionary said:
Working fine for me here. Was getting constant reboots and bootlooping before I flashed back to 5.1.1 first though. Bootloader and vendor especially. Then wiped everything but internal in TWRP, then fastboot flashed Remix except for twrp. Booted into TWRP before booting into the system. Worked great after that.
Click to expand...
Click to collapse
Working fine for me here. Was getting constant reboots and bootlooping before I flashed back to 5.1.1 first though. Bootloader and vendor especially. Then wiped everything but internal in TWRP, then fastboot flashed Remix except for twrp. Booted into TWRP before booting into the system. Worked great after that.
Click to expand...
Click to collapse
That was my issue. Thanks
Bootloop on second boot
So after the tablet seemingly working perfectly and no boot loops on install, it is now only bootlooping after rebooting (even after wiping cache) And this is after installing 5.11 factory image before remix os.
Will try factory reset etc.
i am really interrested in this OS
but before i am doing anything i want to ask some questions
1) how far is google play and google play store integrated? can i open every app?
2) can i type without a manual keyboard?
3) is LTE supported in this version?
I will try this as soon as I get home. Can't wait to test it.
Fallon9111 said:
To all those getting bootloop:
* Download latest 5.11 image LMY48T (not 6.x) https://developers.google.com/android/nexus/images#volantis
* In theory you only need to flash bootloader-flounder-3.44.1.0123.img however to be on the safe side I ran the whole ./flash-all.sh
* Now reboot the bootloader (even if you are already there, since we just flashed a different one), then run the following:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash cache cache.img
# flashing vendor.img will solve the problem of annoying messages on boot/unstable play services
fastboot flash vendor vendor.img
# there is no userdata.img , so we can wipe userdata like so:
fastboot -w
* Now reboot and it should work great. With my experience so far it seems very stable
Click to expand...
Click to collapse
What I find even easier, is to go into twrp. Do all the usual wipes (data, cache, dalvik, system), then reboot into bootloader. It'll say no OS installed in twrp, but that's fine. Then I fastboot flashed the 5.1.1 image manually, skipping recovery.img . Once done, I reboot recovery. It'll boot into twrp. (Doing this ensures that twrp won't be overwritten upon first boot). Then rebooted into 5.1.1. Just making sure it worked fine. Now reboot into twrp. Wipe the same things again, and this time install RemixOS. Again, reboot into twrp. Now reboot. Should be okay. I just don't like having to constantly reflash twrp. Either way works great though.
th3fallen said:
Working fine for me here. Was getting constant reboots and bootlooping before I flashed back to 5.1.1 first though. Bootloader and vendor especially. Then wiped everything but internal in TWRP, then fastboot flashed Remix except for twrp. Booted into TWRP before booting into the system. Worked great after that.
That was my issue. Thanks
Click to expand...
Click to collapse
No problem.
Fallon9111 said:
So after the tablet seemingly working perfectly and no boot loops on install, it is now only bootlooping after rebooting (even after wiping cache) And this is after installing 5.11 factory image before remix os.
Will try factory reset etc.
Click to expand...
Click to collapse
I've rebooted several times, including changing DPI, and no issues. I know you said you installed 5.1.1 prior, but did you do a complete wipe before flashing RemixOS?
oediv said:
i am really interrested in this OS
but before i am doing anything i want to ask some questions
1) how far is google play and google play store integrated? can i open every app?
2) can i type without a manual keyboard?
3) is LTE supported in this version?
Click to expand...
Click to collapse
1. I haven't tried every single app, nor will I, but gmail, hangouts, drive, Google+, all work fine.
2. You mean, is there an onscreen keyboard? If so, then yes. I haven't connected a hardware keyboard.
3. Not sure. Give it a try and let us know! It won't break LTE, so worst case scenario is you just flash back to whatever you had before.
---------- Post added at 10:11 PM ---------- Previous post was at 10:10 PM ----------
maelfilk said:
So does it work for LTE variant? Also anyone running custom kernel with it? (afaik FIRE-ICE has special kernel)
Click to expand...
Click to collapse
The current 10.2.1 Fire and Ice will cause boot loops and break Wi-Fi. Elemental X for 5.1.1 works fine though. Running it now.
dictionary said:
I've rebooted several times, including changing DPI, and no issues. I know you said you installed 5.1.1 prior, but did you do a complete wipe before flashing RemixOS?
Click to expand...
Click to collapse
Yeah, I did a full factory image thing, and even let it boot once into 5.1.1 before rebooting back to fastboot and installing remix. I'm not sure what caused the boot loop problem, (wiping the caches and even a factory reset from twrp didn't fix this), but after flashing factory images then installing everything a 2nd time, the tablet seems to be working fine. So I'm not really sure why it went wrong (looking back in my terminal history I don't spot any obvious errors)...
Fallon9111 said:
Yeah, I did a full factory image thing, and even let it boot once into 5.1.1 before rebooting back to fastboot and installing remix. I'm not sure what caused the boot loop problem, (wiping the caches and even a factory reset from twrp didn't fix this), but after flashing factory images then installing everything a 2nd time, the tablet seems to be working fine. So I'm not really sure why it went wrong (looking back in my terminal history I don't spot any obvious errors)...
Click to expand...
Click to collapse
Yeah that's odd. After I flashed 5.1.1 and let it boot, I rebooted to TWRP, and wiped data, cache, system, and dalvik. Then rebooted to bootloader, then fastboot, and flashed boot.IMG, system.IMG, cache.IMG and vendor.IMG. Didn't have an issue. Glad it's working now for you though.
Related
Hello everyone,
i just flashed the newest Pure Nexus Rom and everything went fine.
I forgot to flash the SuperSU Zip so i tried to got back into TWRP, but now it stuck.
The System boots normally, only TWRP wont boot.
Anyone had that problem too?
if anyone else has the same issue, here is the answer:
I forgot to erase the userdata or cache.
If you have the same problem use fastboot!
fastboot format cache
fastboot format userdata
Then it should work again.
(Everything on your own risk)
If you dont flah SuperSU asap, TWRP will not stick on reboot (w nougat). That was the issue.
No SuperSU was not the problem.
It happened before i flashed the SuperSU zip.
As far as i know, there is a problem if you upgrade to Nougat and dont format the userdata and cache because of the encryption or sth like that.
kaufikauf said:
No SuperSU was not the problem.
It happened before i flashed the SuperSU zip.
As far as i know, there is a problem if you upgrade to Nougat and dont format the userdata and cache because of the encryption or sth like that.
Click to expand...
Click to collapse
Exactly. It happened before you flashed SuperSU zip. Not flashing SuperSU caused your problem. It needs to be flashed the first time you go into TWRP or you won't be able to boot back into TWRP. The previous poster is correct.
Maybe we talk about different problems
Ive formatted cache and userdata yesterday,
now i can go back into twrp.
(SuperSU is not flashed now).
Just tried it, works perfectly!
kaufikauf said:
No SuperSU was not the problem.
It happened before i flashed the SuperSU zip.
As far as i know, there is a problem if you upgrade to Nougat and dont format the userdata and cache because of the encryption or sth like that.
Click to expand...
Click to collapse
I never, ever flash userdata, and never had an issue.
We can agree to disagree. Either the other poster and I arent understanding your question, or you arent understanding our reply. It's cool, it happens.
But TWRP not sticking is due to not running SuperSU at the end of the install process. It wont stick.
And now i know the misunderstanding!
My sentence was a little bit silly formulated:
It didnt stuck by flashing SuperSU. I just forgot to do that and when i recognized this, i want to boot into recovery. Then i recognized the bootloop.
So SuperSU as itself was not involved. By the way BeansTown wrote in the Thread for PureNexus Rom that you have to format your userdata (normally over TWRP).
Shame on me that i didnt read before start flashing
kaufikauf said:
And now i know the misunderstanding!
My sentence was a little bit silly formulated:
It didnt stuck by flashing SuperSU. I just forgot to do that and when i recognized this, i want to boot into recovery. Then i recognized the bootloop.
So SuperSU as itself was not involved. By the way BeansTown wrote in the Thread for PureNexus Rom that you have to format your userdata (normally over TWRP).
Shame on me that i didnt read before start flashing
Click to expand...
Click to collapse
You should take a look at this post in the official TWRP thread for a clearer reason why.
SlimSnoopOS said:
You should take a look at this post in the official TWRP thread for a clearer reason why.
Click to expand...
Click to collapse
So I followed the guide and updated to 7.1.1 and did the normal "fastboot flash recovery xxx" then "fastboot reboot bootlader" then rebooted it via phone I go to "Recovery" from my phone and I get a screen saying "No Command" I tried to flash twrp-3.0.3-0-angler.img
Did I miss something?
USFguy said:
So I followed the guide and updated to 7.1.1 and did the normal "fastboot flash recovery xxx" then "fastboot reboot bootlader" then rebooted it via phone I go to "Recovery" from my phone and I get a screen saying "No Command" I tried to flash twrp-3.0.3-0-angler.img
Did I miss something?
Click to expand...
Click to collapse
After flashing TWRP from the bootloader, go directly into recovery and flash SuperSU 2.78 or newer to make it stick permanently.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
After flashing TWRP from the bootloader, go directly into recovery and flash SuperSU 2.78 or newer to make it stick permanently.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
It won't boot into recovery, I flash recovery, unplug device hit recovery boot and it boot loops once then boots normally....
USFguy said:
It won't boot into recovery, I flash recovery, unplug device hit recovery boot and it boot loops once then boots normally....
Click to expand...
Click to collapse
Hmm. If you are on stock, reflash the boot, system, recovery, and vendor from the factory image that matches your stock, security update. Restart the phone and boot into Android. Restart into the bootloader then fastboot flash recovery TWRP-angler.img. See if it lets you boot into TWRP then. If not, try an older version of TWRP and see if that will flash and allow you to boot into it.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Hmm. If you are on stock, reflash the boot, system, recovery, and vendor from the factory image that matches your stock, security update. Restart the phone and boot into Android. Restart into the bootloader then fastboot flash recovery TWRP-angler.img. See if it lets you boot into TWRP then. If not, try an older version of TWRP and see if that will flash and allow you to boot into it.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Tried that, ended up going down an update in TWRP and it worked, weird....
I had a similar issue and I had to go back in and reflash Recovery image to recovery partition and all was well
I bought this phone used and the person who had it before me it rooted and installed some of different ROMs on it. After getting my used moto x pure 2015 running android 6.0. I booted it up and tested all the functions (including downloading a few apps) Wi-Fi, camera, audio/charging jacks ext. Everything worked fine. So did normal factory reset (not using TWRP) just to make sure everything was clean before using it as my daily. Then, (BUM BUM BUM!) when I tried to start downloading all my apps. None of them would download even though the Wi-Fi was working. Error 492 I think.
I started trying custom ROMs because I was having two big issues (apps not downloading and incoming call not bringing up accept/decline screen) with my stock rom. and wanted to fix those issues with a fresh stock image.
This is all new to me and has not been as easy as anticipated. If anyone knows a clean factory image I could flash or a fail proof fix to error 492 that would be helpful. I really just want to return to fully working Motorola stock android, but the files I have used haven’t fixed the issue. I have searched for a factory image without finding one…
Is there a way to flash the Motorola image through TRWP?
Otherwise, maybe you can help me with my flashing method, and maybe tell me what I am doing wrong. I tried to flash multiple stock images all with the same issue. I have also tried to flash Resurrection Remix, and Brocken OS, both having resulted in a bootloop. I am starting to think I have done something wrong. The steps I have taken so far have been these:
My bootloader is unlocked status code 3.
My phone is not rooted. Do I need root?
First I downloaded adb and fastboot.
Then I flashed TWRP (3.0.2).
I never installed the official Motorola stock image because flashing it from fast boot wouldn’t work and it couldn’t be flashed with TWRP because it is a .gz not a .zip. (I knew a .gz needs to be flashed with fastboot but I knew TWRP was easer so I didn’t fuss with it)
After flashing TWRP to my phone, I downloaded (yes, I checked the md5) the various ROMs to my computer then transfered them to my phone via micro SD card.
Here are the file’s names if that matters:
moto_x_pure_edition_stock_x1575_mphs24.49-18-3_v1-odexed
(booted and Wi-Fi but play store won’t download apps)
moto_x_pure_edition_stock_x1575_mph24.49-18_v1-odexed
(booted but no Wi-Fi)
Broken-v4.9.1-clark-6.0.1-OFFICIAL-20160824 (with Broken_gapps_lp5.1.x_09172015)
(Brocken was the only non-stock that got past boot, but I still couldn’t get past set up without an error and never made it to the system.)
ResurrectionRemix-N-v5.8.0-20161220-clark (7.1 gapps failed to flash but I booted it anyway.)
(boot loop after both of my tries)
I got Wi-Fi working on one of the above stock ROMs (so I KNOW it works) but couldn’t even turn Wi-Fi on in all the others.
The method I used to flash all of the above files in TWRP was:
Wipe
Full wipe (davlik cache, data, system, cache)
(used for RR and Brocken)
Factory reset (using TWRP) (davlik cache, data , cache)
Used for the stock ROMs or even after flashing .zip file I got the error: no OS installed.
Install
Select file of ROM flash (gapps if needed) and flash
I can’t remember which ones but on some of them after flashing I again did a factory reset.
Then I rebooted
Thanks for reading. Sorry it was so long. I tried to add as much useful information as possible. Hopefully someone smarter than me will see my error(s) and help me get my phone into fully working order.
cont.
I really just want to return to fully working Motorola stock android, but the files I have used haven’t fixed the issue. I have searched for a factory image without finding one…
Is there a way to flash the Motorola image through TRWP?
Otherwise maybe you can help me out with my flashing method and maybe tell me what I am doing wrong. I tried to flash multiple stock images all with the same issue. I have also tried to flash Resurrection Remix, and Brocken OS, both having resulted in a bootloop. I am starting to think I have done something wrong. The steps I have taken so far have been these:
My bootloader is unlocked status code 3.
My phone is not rooted. Do I need root?
First I downloaded adb and fastboot.
Then I flashed TWRP (3.0.2).
I never installed the official Motorola stock image because flashing it from fast boot wouldn’t work and it couldn’t be flashed with TWRP because it is a .gz not a .zip. (I knew a .gz needs to be flashed with fastboot but I knew TWRP was easer so I didn’t fuss with it)
After flashing TWRP to my phone, I downloaded (yes, I checked the md5) the various ROMs to my computer then transfered them to my phone via micro SD card.
Here are the file’s names if that matters:
moto_x_pure_edition_stock_x1575_mphs24.49-18-3_v1-odexed
(booted and Wi-Fi but play store won’t download apps)
moto_x_pure_edition_stock_x1575_mph24.49-18_v1-odexed
(booted but no Wi-Fi)
Broken-v4.9.1-clark-6.0.1-OFFICIAL-20160824 (with Broken_gapps_lp5.1.x_09172015)
(Brocken was the only non-stock that got past boot, but I still couldn’t get past set up without an error and never made it to the system.)
ResurrectionRemix-N-v5.8.0-20161220-clark (7.1 gapps failed to flash but I booted it anyway.)
(boot loop after both of my tries)
I got Wi-Fi working on one of the above stock ROMs (so I KNOW it works) but couldn’t even turn Wi-Fi on in all the others.
The method I used to flash all of the above files in TWRP was:
Wipe
Full wipe (davlik cache, data, system, cache)
(used for RR and Brocken)
Factory reset (using TWRP) (davlik cache, data , cache)
Used for the stock ROMs or even after flashing .zip file I got the error: no OS installed.
Install
Select file of ROM flash (gapps if needed) and flash
I can’t remember which ones but on some of them after flashing I again did a factory reset.
Then I rebooted
Thanks for reading. Sorry it was so long. I tried to add as much useful information as possible. Hopefully someone smarter than me will see my error(s) and help me get my phone into fully working order.
I think this thread will help you: https://forum.xda-developers.com/showthread.php?t=3489110
Sent from my XT1572 using Tapatalk
Install stock firmware via fastboot... if that dont fix the issue, install TWRP make a full wipe, FULL, and install the stock firmware again, eventualy that sould fix the issue.
RK2116 said:
Install stock firmware via fastboot... if that dont fix the issue, install TWRP make a full wipe, FULL, and install the stock firmware again, eventualy that sould fix the issue.
Click to expand...
Click to collapse
I'm having a similar issue. Tried the TruPure rom but I want to switch back to stock. If I do a full wipe, would I be able to use the files that Motorola provides on their website and flash those throught fastboot? Or through TWRP? Any chance you have a link to a guide on how to do the latter option (installing through TWRP)? I'm just trying to get my device back to 100% stock so that I can receive OTA.
cdiaz8 said:
I'm having a similar issue. Tried the TruPure rom but I want to switch back to stock. If I do a full wipe, would I be able to use the files that Motorola provides on their website and flash those throught fastboot? Or through TWRP? Any chance you have a link to a guide on how to do the latter option (installing through TWRP)? I'm just trying to get my device back to 100% stock so that I can receive OTA.
Click to expand...
Click to collapse
Odexed one, install with TWRP, full wipe before doing that, no GApps, just ROM, them, install stock recovery vía fastboot. After that you Will be stock with OTAs.
https://forum.xda-developers.com/mo...t/rom-marshmallow-6-0-september-2016-t3536120
RK2116 said:
Odexed one, install with TWRP, full wipe before doing that, no GApps, just ROM, them, install stock recovery vía fastboot. After that you Will be stock with OTAs.
https://forum.xda-developers.com/mo...t/rom-marshmallow-6-0-september-2016-t3536120
Click to expand...
Click to collapse
Thank you for sharing that link. I think I get it but it seems too easy considering what I've tried so far. Just to make sure I get it:
I should download the odexed rom, go to twrp and wipe data, cache and dalvik then flash the odexed rom through the install function? And thats it? I've literally tried a ton of stuff so if this takes care of it, this is great!
cdiaz8 said:
Thank you for sharing that link. I think I get it but it seems too easy considering what I've tried so far. Just to make sure I get it:
I should download the odexed rom, go to twrp and wipe data, cache and dalvik then flash the odexed rom through the install function? And thats it? I've literally tried a ton of stuff so if this takes care of it, this is great!
Click to expand...
Click to collapse
Yes, also wipe system, make a backup before If you want, but remember, for the OTAs support you need yo flash the stock recovery via fastboot. Good luck.
RK2116 said:
Yes, also wipe system, make a backup before If you want, but remember, for the OTAs support you need yo flash the stock recovery via fastboot. Good luck.
Click to expand...
Click to collapse
This got me back to stock! You are the real MVP.
So I remember seeing a recovery.img file in the factory image that motorola posted on its site. Does it have to be a specific stock recovery or do I need a specific one to match with the file I just installed?
thanks again
cdiaz8 said:
This got me back to stock! You are the real MVP.
So I remember seeing a recovery.img file in the factory image that motorola posted on its site. Does it have to be a specific stock recovery or do I need a specific one to match with the file I just installed?
thanks again
Click to expand...
Click to collapse
Just a stock one, if Motorola have one use that.
RK2116 said:
Just a stock one, if Motorola have one use that.
Click to expand...
Click to collapse
So I'm on stock build 49-18-8 and flashed the recovery from 49-18-3. I went into fastboot and selected recovery. I got the android character with an !
I then did the power button and volume up and got into stock android recovery. Am I supposed to see the android character with ! each time I try to reach the recovery menu? Just wondering if I did this correctly.
Thanks again for pointing me to these resources!
cdiaz8 said:
So I'm on stock build 49-18-8 and flashed the recovery from 49-18-3. I went into fastboot and selected recovery. I got the android character with an !
I then did the power button and volume up and got into stock android recovery. Am I supposed to see the android character with ! each time I try to reach the recovery menu? Just wondering if I did this correctly.
Thanks again for pointing me to these resources!
Click to expand...
Click to collapse
Yes.
Hi! Guys I have a problem, which doesn't resemble the BLOD, so here is what has happened. I was running stock android June build on 6p, rooted. And my phone started random reboots. I thought it could be fixed with either stock or custom rom. So I decided to flash AOSPA. I went into twrp but could not flash it, phone rebooted each time. I tried stock images via flash all command as well as manual. No rom worked although I could flash kernel etc. I used The Flash's custom twrp and fixed data and was able to flash rom easily, but it bootlooped on google logo, and rebooted. Now I can flash roms etc but it bootloops. Although Tesla rom did go into bootanimation before bootlooping.
So what can I do? Is it software related? What do you guys say!
PS. I did look into other threads, nothing was similar, although I did try a few mentioned fixes.
osamaasif786 said:
So what can I do? Is it software related? What do you guys say!
Click to expand...
Click to collapse
Use fastboot to FORMAT system, userdata and cache. Note any errors during the FORMAT process.... and then try flashing a full image from Google using flash-all.bat
v12xke said:
Use fastboot to FORMAT system, userdata and cache. Note any errors during the FORMAT process.... and then try flashing a full image from Google using flash-all.bat
Click to expand...
Click to collapse
It gives no error and did try the flash-all.bat method no luck.
osamaasif786 said:
It gives no error and did try the flash-all.bat method no luck.
Click to expand...
Click to collapse
I'd say you were squarely in a small group of people who are able to access and fully use Recovery but still boot loop after formatting and installing a clean image. If you've already tried a factory reset from the stock recovery I think you are done. Hardware issue. Replacing the motherboard is a fix, but not economically viable.
I had the same issue formatting data and cache to Ext4 and flashing modified stock ROM fixed. It would boot to Google logo freeze reboot and sometimes get to boot animation freeze and reboot.
Exodusche said:
I had the same issue formatting data and cache to Ext4 and flashing modified stock ROM fixed. It would boot to Google logo freeze reboot and sometimes get to boot animation freeze and reboot.
Click to expand...
Click to collapse
Which modified one, can you share the link?
osamaasif786 said:
Which modified one, can you share the link?
Click to expand...
Click to collapse
Cortex ROM it's flashable stock firmware with extras . Though my symptoms where the same I hope I'm not giving you false hope. Worth a shot though.
The only was I recover my phone without replacing is using https://forum.xda-developers.com/nexus-6p/general/boot-images-bootloop-t3633723 < method from here... but the phone is lag af as it is only running 1 core on stock july build. Good luck for that.
I have the same issue going on. i was trying to flash magisx and suddenly it is stuck in bootloop. i tried flashing stock images and everything. i can access twrp and flash eveything and they are getting flashed fine but still it is stuck on the bootloop.
TheTickReborn said:
I have the same issue going on. i was trying to flash magisx and suddenly it is stuck in bootloop. i tried flashing stock images and everything. i can access twrp and flash eveything and they are getting flashed fine but still it is stuck on the bootloop.
Click to expand...
Click to collapse
So have you used fastboot to FORMAT system, userdata and cache? Did each format command complete with no errors?
I'm having a very difficult time getting this phone setup. I can get very, very close... but then it starts boot looping into recovery.
So starting at the beginning, here is what I did:
- Booted up phone, make sure it works and connects to wifi (I find out later that it got encrypted, even though I didn't set a PIN).
- Inside the OS on first boot, I install and use the official bootloader unlock APK from Asus.
- Rebooted into the bootloader and fastboot flashed TWRP.
- Rebooted into TWRP and flashed the Oreo modem, current unofficial Carbon OS 6.1, nano gapps, and magisk 16.6.
- Rebooted and the Carbon ROM logo comes up. It works for about 2-3 minutes, then reboots.
- After many attempts to decrypt (and a lot of help from the forum), I successfully restore the phone to "WW_ZE552KL_14.2020.1712.85_M3.10.47.15_Phone-user.raw.zip" with the Asus tool.
- Phone is fixed and booting again to the OS, but I'm back to square one.
Second attempt:
- Thinking I need to flash the raw Oreo ROM (instead of just the Oreo modem), I use the Asus tool to flash "WW_ZE552KL_15.0410.1803.55_M3.10.47.19_Phone-user.raw.zip"
- The phone works fine and is now an Oreo ROM with an Oreo modem
- It's still unlocked, so I rebooted into the bootloader and fastboot flashed TWRP.
- Rebooted into TWRP and flashed the current unofficial Carbon OS 6.1, nano gapps, and magisk 16.6.
- Rebooted and the Carbon ROM logo comes up. It works for about 2-3 minutes, then reboots.
- After the reboot, it goes to TWRP... whether I just let it boot on its own, or press power when it says: Start - Continue to boot >
What am I doing wrong?
You're having a rough go at this one eh.
I know we talked about this before, but did you try a factory reset and wiping cache/dalvik before rebooting?
Yes. As we discussed before, you can't wipe cache from TWRP. So I'd wipe dalvik from TWRP, then reboot to the bootloader to do a "fastboot format cache".
I'm going to try a different ROM later this afternoon. Maybe that will make a difference.
Flapjack said:
I'm going to try a different ROM later this afternoon. Maybe that will make a difference.
Click to expand...
Click to collapse
Hello! I've been able to boot any ROM by:
1. flashing TWRP
2. rebooting to recovery
3. installing the ROM zip
4. rebooting to bootloader
5. fastboot continue
But when I restart the phone, it always boots to recovery(TWRP), so I have to repeat steps 4 and 5 to boot the ROM, which is
Could you try and tell me if it works for you too?
I'm gonna take a moment to read about the boot process in depth, as it seems there is no straightforward solution to this out there.
junglesnake said:
Hello! I've been able to boot any ROM by:
1. flashing TWRP
2. rebooting to recovery
3. installing the ROM zip
4. rebooting to bootloader
5. fastboot continue
But when I restart the phone, it always boots to recovery(TWRP), so I have to repeat steps 4 and 5 to boot the ROM, which is
Could you try and tell me if it works for you too?
I'm gonna take a moment to read about the boot process in depth, as it seems there is no straightforward solution to this out there.
Click to expand...
Click to collapse
1) Flash Oreo RAW (can be downloaded from @Saktis_STi' s unlocking thread.
2) Boot till system
3) Flash TWRP
4) Flash ROM, Magisk, GApps
5) Reboot
The reason why it reboots to TWRP is because of 'encryption' thingy.
BootloaderBoi said:
1) Flash Oreo RAW (can be downloaded from @Saktis_STi' s unlocking thread.
2) Boot till system
3) Flash TWRP
4) Flash ROM, Magisk, GApps
5) Reboot
The reason why it reboots to TWRP is because of 'encryption' thingy.
Click to expand...
Click to collapse
many many thanks! I was able to get Ressurection Remix working by now
your steps were right, and I will detail them better to tell how I made it work for others reading this thread:
1) Flash Oreo RAW
1.1 - @Saktis_STi's thread is a bit outdated. I downloaded the newest firmware from Asus website.
1.2 - I also had to find a recent recovery.img, which I think I got it from here https://forum.xda-developers.com/zenfone-3/how-to/original-recovery-img-boot-img-zenfone-t3572188
1.3 - I used the stock recovery's adb sideload to flash the stock ROM
2) Flash TWRP - all good here
3) Flash ROM, Magisk, GApps
3.1 - I wiped system, data, cache and dalvik.
3.2 - I flashed RR ROM, GApps and Magisk (EDIT 2: install all three before the first custom ROM boot, or GApps won't work)
3.3 - Performed a Factory Reset
4) REBOOTED TO GLORY!
For what it seems, the stock ROM encryption that is performed on the stock's first boot was the enemy.
Now one last thing... In Security -> Encription, my device is NOT encrypted.
Do I run the risk of ruining everything if I encrypt it?
EDIT: No, it didn't break, working fine
junglesnake said:
1) Flash Oreo RAW
1.1 - @Saktis_STi's thread is a bit outdated. I downloaded the newest firmware from Asus website
Click to expand...
Click to collapse
lmao. His RAW firmware version is the latest version though
https://forum.xda-developers.com/zenfone-3/development/updated-unlock-relock-bootloader-t3749456
Anyways, enjoy your phone running on custom ROM :good:
Hi there folks!
Sorry if i open a thread, probably you've discussed somewhere before about this problem that i'm experiencing.
My OnePlus 5 basically works only with omniROM, it doesn't boot at all when i try to install another one.
I tried with this:
https://forum.xda-developers.com/oneplus-6/development/rom-aospextended-rom-v5-7-t3825642
and this one:
https://forum.xda-developers.com/oneplus-5/development/rom-crdroid-android-5-0-t3836886
I followed every step (About CRAndroid), radio firmware 5.1.5 + TWRP 3.2.3 + Gapps + Magisk 17.1 and No Verity v3 (First try without noverity, second using it)
and i followed also every step neeeded in AOSPExtended rom.
When i try to boot the phone, after the OnePlus logo, nothing happens. The phone reboots in recovery mode, that's it.
If i repeat the same steps with OmniROM it works all fine, except Magisk. If i flash Magisk on the Omni it doesn't boot, if i flash SU it works.
Could it be something related to the encryption/Decription of the device?
When i go into TWRP it doesn't ask me for a pattern or a code. It should be decrypted, right? (i'm a bit confused about that).
I purchased the phone on Gearbest, could it be a particular version of the phone that doesn't allow me to work properly with roms?
Help
did you tried old stock ROMs, 4.* versions ? then 5.0.0 and then the others
Sometimes the partitions need to be wiped. Try a fastboot format userdata; fastboot format system.
azretier said:
did you tried old stock ROMs, 4.* versions ? then 5.0.0 and then the others
Click to expand...
Click to collapse
Actually when the phone arrived i've just unlocked the bootloader and installed a custom rom....what's the purpose of this?
moffa~ said:
Sometimes the partitions need to be wiped. Try a fastboot format userdata; fastboot format system.
Click to expand...
Click to collapse
You....you're a good guy.
I did the command you said, then i booted into TWRP, flashed AospExtended, Gapps Pico and Magisk 17.1 - after reboot it has been stuck @ 1+ logo, then it rebooted again (as always when it doesn't work) and i said "ok here we go again in the TWRP-loop" and INSTEAD it booted rom! Yes!