Related
My N10 with stock 5.1 previously had root with TWRP 2.8.6, but for some reason it recently lost root. In addition, it seems that TWRP has been corrupted because whenever I try to boot into recovery I get a dead bootloader with a red exclamation mart. After I flashed the most recent version of TWRP 3.0.0-1 using "fastboot flash recovery twrp-3.0.0-1-manta.img" (bootloader still unlocked), I still get a dead bootloader when booting into recovery.
Then I flashed back to TWRP 2.8.6, but the problem remains!
How to fix the problem? Thanks!
I hope you can go to bootloader mode... Revert to stock by flashing the factory images and then start over again
nitin.chobhe said:
I hope you can go to bootloader mode... Revert to stock by flashing the factory images and then start over again
Click to expand...
Click to collapse
Thanks!
Just flashed an even older version (2.8.5) of TWRP, and now suddenly it can boot into recovery without any problem. I have also gained root now after flashing SuperSU.
I was planning to flash the most recent version of TWRP (3.0.0-1), and then try out CM13, but for some reason my N10 with stock 5.1 does not like those newer versions of TWRP. Do you know why?
mj56gt said:
Thanks!
Just flashed an even older version (2.8.5) of TWRP, and now suddenly it can boot into recovery without any problem. I have also gained root now after flashing SuperSU.
I was planning to flash the most recent version of TWRP (3.0.0-1), and then try out CM13, but for some reason my N10 with stock 5.1 does not like those newer versions of TWRP. Do you know why?
Click to expand...
Click to collapse
No, I do not konw that. Are you flashing correct version of TWRP made for manta?
nitin.chobhe said:
No, I do not konw that. Are you flashing correct version of TWRP made for manta?
Click to expand...
Click to collapse
I downloaded all the three versions (2.8.5, 2.8.6, and 3.0.0-1) of TWRP I've flashed so far from here:
https://dl.twrp.me/manta/
This is weird. Is it because I didn't have root during the time I flashed 2.8.6 or 3.0.0-1? I thought that flashing TWRP would not require root.
Can I flash CM13 with TWRP 2.8.5? I'll definitely make a Nandroid backup before proceeding.
mj56gt said:
I downloaded all the three versions (2.8.5, 2.8.6, and 3.0.0-1) of TWRP I've flashed so far from here:
https://dl.twrp.me/manta/
This is weird. Is it because I didn't have root during the time I flashed 2.8.6 or 3.0.0-1? I thought that flashing TWRP would not require root.
Can I flash CM13 with TWRP 2.8.5? I'll definitely make a Nandroid backup before proceeding.
Click to expand...
Click to collapse
With nandroid, you are good to go.
Should be possible :fingers-crossed:
nitin.chobhe said:
With nandroid, you are good to go.
Should be possible :fingers-crossed:
Click to expand...
Click to collapse
I did factory reset in TWRP 3.0.0-1 and then flashed CM 13.0-20160309 on my N10 with the dynamic Gapps. Now I get this error Unfortunately Google Play Services Has Stopped. Is it because the default factory reset is not good enough or something else? If it needs a full wipe, what exactly should I wipe, system and data? And after a full wipe, do I need to reflash CM13 or just Gapps?
Thanks!
mj56gt said:
I did factory reset in TWRP 3.0.0-1 and then flashed CM 13.0-20160309 on my N10 with the dynamic Gapps. Now I get this error Unfortunately Google Play Services Has Stopped. Is it because the default factory reset is not good enough or something else? If it needs a full wipe, what exactly should I wipe, system and data? And after a full wipe, do I need to reflash CM13 or just Gapps?
Thanks!
Click to expand...
Click to collapse
Problem solved: Just flashed the pico Gapps, and now everything works fine. For some reason the dynamic Gapps didn't work for me.
mj56gt said:
Problem solved: Just flashed the pico Gapps, and now everything works fine. For some reason the dynamic Gapps didn't work for me.
Click to expand...
Click to collapse
May be there isn't enough space to flash them.
Happy that is working now
Sent from my Nexus 4 using XDA Free mobile app
I first rooted my Nexus 6p that was completely stock using the system less root method. After I flashed the modified boot and twrp and rooted, my camera wasn't working. It just shows the camera icon and a black screen. I looked up the problem and many people said flashing a vendor image would work, but after doing so, it just tells me there was an internal error, so I reflashed the factory images. After doing so, camera still wasn't working. I also saw one person flashed a different modified boot but this only gives me a bootloop. Does anyone know a fix to the camera problem? Thanks!
kwcty6888 said:
I first rooted my Nexus 6p that was completely stock using the system less root method. After I flashed the modified boot and twrp and rooted, my camera wasn't working. It just shows the camera icon and a black screen. I looked up the problem and many people said flashing a vendor image would work, but after doing so, it just tells me there was an internal error, so I reflashed the factory images. After doing so, camera still wasn't working. I also saw one person flashed a different modified boot but this only gives me a bootloop. Does anyone know a fix to the camera problem? Thanks!
Click to expand...
Click to collapse
It's most likely caused by flashing the wrong boot.img, when you flashed the factory images to go back to stock did you flash the boot.img too?
Heisenberg said:
It's most likely caused by flashing the wrong boot.img, when you flashed the factory images to go back to stock did you flash the boot.img too?
Click to expand...
Click to collapse
I think I did.. I can try reflashed the stock boot.img again though. But I'm not sure what I did wrong because I just flashed the modified boot necessary for twrp?
kwcty6888 said:
I think I did.. I can try reflashed the stock boot.img again though. But I'm not sure what I did wrong because I just flashed the modified boot necessary for twrp?
Click to expand...
Click to collapse
TWRP doesn't require a modified boot.img anymore, it hasn't for a long time, unless you're using the Android N dev preview. You also need to ensure that you flash the right boot.img to suit your ROM build. For example, if you flash the MHC19I boot.img on a ROM that's based on MTC19T you'll get problems, like the camera not working.
Heisenberg said:
TWRP doesn't require a modified boot.img anymore, it hasn't for a long time, unless you're using the Android N dev preview. You also need to ensure that you flash the right boot.img to suit your ROM build. For example, if you flash the MHC19I boot.img on a ROM that's based on MTC19T you'll get problems, like the camera not working.
Click to expand...
Click to collapse
Unfortunately I re-flashed the factory boot and recovery (using build MTC19T), and the camera is still not working. Do you have any other thoughts? Thanks for your help!
kwcty6888 said:
Unfortunately I re-flashed the factory boot and recovery (using build MTC19T), and the camera is still not working. Do you have any other thoughts? Thanks for your help!
Click to expand...
Click to collapse
Flash the full factory images (except userdata), then flash the latest TWRP, not boot into TWRP and enter the wipe menu, select advanced wipe, tick the data box and wipe it. Boot up and see if that helps.
Hey guys,
Today I tried to go from the Android N developer preview back to Cyanogen Mod 13 (which I had been running before). I tried installing through TWRP 3.0.0.0 but for some reason whenever I install CM I get stuck in a boot loop at the screen that just says Google but multiple times I've been able to flash back to the Android N Preview. I've flashed my phone many times before and I tried a bunch of different stuff (formatting the userdata partition before flashing to decrypt the phone, wiping and not wiping the davlik cache before and after flashing, multiple snapshots of cm13 etc.) but I can't seem to break that bootloop. I ended up going to Android N after I broke something on CM so I used the opportunity to try out Nougat before I flashed back to CM so I didn't have any back ups (I thought I did but i only backed up apps and app data, not a whole solid backup from TWRP or something). Right now I'm entirely stable on Android N but missing XPosed a little so any help would be appreciated.
Alex
touchmywillis said:
Hey guys,
Today I tried to go from the Android N developer preview back to Cyanogen Mod 13 (which I had been running before). I tried installing through TWRP 3.0.0.0 but for some reason whenever I install CM I get stuck in a boot loop at the screen that just says Google but multiple times I've been able to flash back to the Android N Preview. I've flashed my phone many times before and I tried a bunch of different stuff (formatting the userdata partition before flashing to decrypt the phone, wiping and not wiping the davlik cache before and after flashing, multiple snapshots of cm13 etc.) but I can't seem to break that bootloop. I ended up going to Android N after I broke something on CM so I used the opportunity to try out Nougat before I flashed back to CM so I didn't have any back ups (I thought I did but i only backed up apps and app data, not a whole solid backup from TWRP or something). Right now I'm entirely stable on Android N but missing XPosed a little so any help would be appreciated.
Alex
Click to expand...
Click to collapse
Are you flashing the corresponding vendor image? If you do not flash the correct vendor image you will boot loop. I have gone from N to Marshmallow and reverse without issue.
santque said:
Are you flashing the corresponding vendor image? If you do not flash the correct vendor image you will boot loop. I have gone from N to Marshmallow and reverse without issue.
Click to expand...
Click to collapse
No I wasn't, I couldn't very easily find much information on how to flash the vendor image so right now I'm reverting back to Marshmallow via the OTA opt out, that should do the trick right? If not, I know where to find the vendor image but how do I flash it? just fastboot flash vendor.img or what?
Thanks for your help!
touchmywillis said:
No I wasn't, I couldn't very easily find much information on how to flash the vendor image so right now I'm reverting back to Marshmallow via the OTA opt out, that should do the trick right? If not, I know where to find the vendor image but how do I flash it? just fastboot flash vendor.img or what?
Thanks for your help!
Click to expand...
Click to collapse
There are two ways you can flash a vendor image. Either through TWRP's 'Install' menu or using the 'fastboot flash vendor vendor.img' command.
You can grab hold of the vendor image corresponding to the build number from here: https://www.androidfilehost.com/?w=files&flid=49333
Thanks to BeansTown106 for the vendor uploads.
My phone is android 6.0 and I've been using "TruPureXMM 2.9" ever since it first came out. I have a February 1, 2016 android security patch level and my system version is 24.11.18 clark_retus.retus.en.US retus
I had an older version of twrp so I just updated it to the latest one before attempting this ofc...
I tried flashing the latest RR and AICP and both give me boot loops and I always get this one problem where it says
"mount: failed to mount /dev/block/bootdevice/by-name
/modem at /firmware: Device or resource busy"
I'm not sure if this has anything to do with the bootloop though...
Going to recovery after seeing the bootloop I always get the "keep system read only?" prompt where i swipe to allow modification but i usually just restore back to my backup from there... i dont think allowing it and trying to boot again will get rid of the bootloop...
I followed the process of first doing a full wipe with twrp > flash rom > flash gapps > restart system
no idea what i'm doing wrong..
OppaiHeroStar said:
My phone is android 6.0 and I've been using "TruPureXMM 2.9" ever since it first came out. I have a February 1, 2016 android security patch level and my system version is 24.11.18 clark_retus.retus.en.US retus
...
I followed the process of first doing a full wipe with twrp > flash rom > flash gapps > restart system
no idea what i'm doing wrong..
Click to expand...
Click to collapse
1st - you need twrp 3.x+,
2nd - full wipe - format data, adv.wipe - all without micro sd.
3rd - flash rom, flash gapps(opengapps.org, ≤mini, arm64, 7.1)
Last Rr is for Nougat modem - you are on MM modem.
Flash RR 21.11.2017.
https://forum.xda-developers.com/mo...ial-resurrection-remix-v5-8-3-t3637204/page36
dzidexx said:
1st - you need twrp 3.x+,
2nd - full wipe - format data, adv.wipe - all without micro sd.
3rd - flash rom, flash gapps(opengapps.org, ≤mini, arm64, 7.1)
Last Rr is for Nougat modem - you are on MM modem.
Flash RR 21.11.2017.
https://forum.xda-developers.com/mo...ial-resurrection-remix-v5-8-3-t3637204/page36
Click to expand...
Click to collapse
The first 3 steps I've already done that since the beginning
Where can i get the nougat modem/is it possible to update to it? I guess that's the reason every single 7.1 custom rom I tried in the android development section gave me boot loops...
And could you link the 21.11.2017 version of RR? I'm looking at the download links for RR and I dont see one with that exact date
edit-just saw your edit
Custom roms for MM modem works better.
I fully wiped using TWRP, checked everything I possibly could except my micro SD card and I flashed RR-N-v5.8.5-20171121-clark-Final.zip then gapps arm64, 7.1 nano and it's still giving me boot loops. I'm using TWRP 3.2.1-0
im gonna try using gapps arm64 7.1 mini really quick since you said I should use that one and see if it boot loops... - Edit guess I was too optimistic thinking this would fix it
Bugs probably after flashing december RR.
Change twrp to 3.1.x, reboot twrp, change all partitions to ext4 - adv wipes - One by one - cache, system, data, reboot twrp.
Change back to f2fs - only cache & data, wipe all, flash what I wrote.
dzidexx said:
Bugs probably after flashing december RR.
Change twrp to 3.1.x, reboot twrp, change all partitions to ext4 - adv wipes - One by one - cache, system, data, reboot twrp.
Change back to f2fs - only cache & data, wipe all, flash what I wrote.
Click to expand...
Click to collapse
changed to 3.1.1-0 and did everything you said, still have boot loop...
when flashing this RR i still get this, not sure if it's a problem but thought I would just let you know
"mount: failed to mount /dev/block/bootdevice/by-name
/modem at /firmware: Device or resource busy"
OppaiHeroStar said:
changed to 3.1.1-0 and did everything you said, still have boot loop...
"mount: failed to mount /dev/block/bootdevice/by-name
/modem at /firmware: Device or resource busy"
Click to expand...
Click to collapse
It doesn`t matter.
Try another custom - LOS f.e.
If bootloop still will be - you should flash full stock.
Last MM for RetUs
dzidexx said:
It doesn`t matter.
Try another custom - LOS f.e.
If bootloop still will be - you should flash full stock.
Last MM for RetUs
Click to expand...
Click to collapse
I tried crDroidAndroid-7.1.2-20171119-clark-v3.8.3.zip and it still boot loops :\ I also already tried LineageOS and AICP before we started talking
I went back to my backup and it put me in a bootloop which never happened before but changing cache back to ext4 instead of f2fs fixed it..
OppaiHeroStar said:
when flashing this RR i still get this, not sure if it's a problem but thought I would just let you know
"mount: failed to mount /dev/block/bootdevice/by-name
/modem at /firmware: Device or resource busy"
Click to expand...
Click to collapse
A little late to chime in and this does not help with your current situation, but here's a little advice. I flash a lot of ROMs (how else am I going to test builds right?). This error happens all the time, BUT if you flash a ROM twice it should not show on the 2nd flash.
So flash order goes:
Wipe/Factory reset
Format data x3 (yes I format my data 3 times for every ROM)
Reboot
Wipe/Factory reset
ROM
ROM again
GAPPS
Wipe caches
Reboot
Do the Initial setup
Reboot before use
OPTIONAL Kernel (if its not already build in)
OPTIONAL Magisk (I never flash Magisk on a clean build but heck I'm expecting a NON boot most of the time anyways)
At this point I would flash the stock Nougat image via fastboot to get the device operational again... Then look at TWRP, root, or custom ROM.
acejavelin said:
At this point I would flash the stock Nougat image via fastboot to get the device operational again... Then look at TWRP, root, or custom ROM.
Click to expand...
Click to collapse
so should I just straight up flash the nougat image via fastboot from your thread here? https://forum.xda-developers.com/moto-x-style/general/xt1575-moto-x-pure-edition-factory-t3704142
i dont need to go back to mm stock or something first? I don't really have much knowledge about this.
OppaiHeroStar said:
so should I just straight up flash the nougat image via fastboot from your thread here? https://forum.xda-developers.com/moto-x-style/general/xt1575-moto-x-pure-edition-factory-t3704142
i dont need to go back to mm stock or something first? I don't really have much knowledge about this.
Click to expand...
Click to collapse
Correct... And verify everything is working properly before you flash TWRP, root, or take any OTA update.
acejavelin said:
Correct... And verify everything is working properly before you flash TWRP, root, or take any OTA update.
Click to expand...
Click to collapse
so i finished flashing that nougat firmware and looks like everything is working ok, does that mean I can try flashing custom roms after twrp now?
OppaiHeroStar said:
so i finished flashing that nougat firmware and looks like everything is working ok, does that mean I can try flashing custom roms after twrp now?
Click to expand...
Click to collapse
Boot TWRP (don't flash it) and make a full back, and I would recommend not talking any OTAs either.
Then knock yourself out... You can always get back to this state if things go badly.
acejavelin said:
Boot TWRP (don't flash it) and make a full back, and I would recommend not talking any OTAs either.
Then knock yourself out... You can always get back to this state if things go badly.
Click to expand...
Click to collapse
was finally able to flash a custom rom without bootloops!
thank you and everyone else here for the help I honestly really appreciate it
OppaiHeroStar said:
was finally able to flash a custom rom without bootloops!
thank you and everyone else here for the help I honestly really appreciate it
Click to expand...
Click to collapse
What custom did you flashed?
dzidexx said:
What custom did you flashed?
Click to expand...
Click to collapse
I tried out AICP, AOKP, and RR. All latest versions and they worked but for some reason my data doesn't work on any of those customs.
guess my happiness was short lol. Considering just staying stock now
OppaiHeroStar said:
I tried out AICP, AOKP, and RR. All latest versions and they worked but for some reason my data doesn't work on any of those customs.
guess my happiness was short lol. Considering just staying stock now
Click to expand...
Click to collapse
I'm not sure for others but RR - only 5.8.5-04.12 works with N modem.
Did you check/set access points properly?
All customs for N modem(I think) have problems with notification sound, so you can stay at stock.
dzidexx said:
I'm not sure for others but RR - only 5.8.5-04.12 works with N modem.
Did you check/set access points properly?
All customs for N modem(I think) have problems with notification sound, so you can stay at stock.
Click to expand...
Click to collapse
I'm using t-mobile and I've checked the access points, clicking on the one im using and hitting save doesn't fix it. Always getting a notification telling me to sign in to network. Not sure what else I can do. I'll give it a day since I had this kind of problem before when I switched sim cards and data didn't work until the next day
Edit - just went back to stock and my data doesn't work now either... just going to stay at RR now and hope my data fixes itself because my access point settings for tmobile should be correct since I looked it up on the official website..
I flashed xXx based on OOS 5.0.2, and the phone doesn’t boot. It shows the boot logo for a few seconds, and then return to TWRP. How to fix it?
itaibarzilai said:
I flashed xXx based on OOS 5.0.2, and the phone doesn’t boot. It shows the boot logo for a few seconds, and then return to TWRP. How to fix it?
Click to expand...
Click to collapse
Why you're creating a new thread instead of looking here https://forum.xda-developers.com/on...xxx-nolimits-1-1-speed-ram-optimized-t3627121
Please give more details from which rom youre coming and if you are decrypted or encrypted and what selections you made in the xxx aroma installer(some mods are causing bootloops for example) and at last: what instructions did you follow?
strongst said:
what selections you made in the xxx aroma installer(some mods are causing bootloops for example
Click to expand...
Click to collapse
Which selections can case issues?
itaibarzilai said:
Which selections can case issues?
Click to expand...
Click to collapse
Google camera for example. You should tell what you selected. We can't look in your mind
itaibarzilai said:
I flashed xXx based on OOS 5.0.2, and the phone doesn’t boot. It shows the boot logo for a few seconds, and then return to TWRP. How to fix it?
Click to expand...
Click to collapse
Wipe data and cache and try reboot again. If it still doesn't work reflash the rom
Did you change the encrypted/decrypted option? If so, your sdcard needs to be wiped, otherwise it won't boot
itaibarzilai said:
I flashed xXx based on OOS 5.0.2, and the phone doesn’t boot. It shows the boot logo for a few seconds, and then return to TWRP. How to fix it?
Click to expand...
Click to collapse
Sounds like your encrypted, no problem. Using a pc, plug your phone in and use "fastboot - w" to wipe your device followed by "fastboot format system" - then flash an Oreo compatible twrp, and flash xxx. If you choose encrypted, flash xxx and nothing else, and then reboot to recovery, then press wipe, format data, type yes, then reboot. (reboot to twrp to flash anything else after). If you chose unencrypted, flash other stuff at will.
Source: I'm running xxx, it's what I do - I'm encrypted btw
@itaibarzilai
Here is the fix, i have experienced excatly same problem.
As i know from myself, you have installed substratum and some theme-overlays.
Flash prewious OOS version again (dirty flash) it will boot now.
Then go substartum and uninstall all themes.
Now flash 5.0.2 one more time it will boot now