Related
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..
Title pretty much says it all. I tried to upgrade to the Oreo beta from LOS, it failed, tried to flash back to Lineage, it played the boot animation for about 5 seconds then powered off. Flashed Resurrection Remix, same thing, then the Oreo beta again, same thing. It just gets a few seconds into the boot animation and powers completely off. I can get it into TWRP, and my computer still recognizes it, so it isn't hard bricked at least. Any suggestions?
BoredIllinoisan said:
Title pretty much says it all. I tried to upgrade to the Oreo beta from LOS, it failed, tried to flash back to Lineage, it played the boot animation for about 5 seconds then powered off. Flashed Resurrection Remix, same thing, then the Oreo beta again, same thing. It just gets a few seconds into the boot animation and powers completely off. I can get it into TWRP, and my computer still recognizes it, so it isn't hard bricked at least. Any suggestions?
Click to expand...
Click to collapse
Have you tried formatting the internal storage/data? Also you might have to change the filesystem to what it was before, in my case I changed it to ext4. Also you might have to flash universal bootloader and modem again since your going back to nougat.
This might help you, read the first post.
https://forum.xda-developers.com/axon-7/development/rom-slm-t3752554/post75635304
Nicz14 said:
Have you tried formatting the internal storage/data? Also you might have to change the filesystem to what it was before, in my case I changed it to ext4. Also you might have to flash universal bootloader and modem again since your going back to nougat.
This might help you, read the first post.
https://forum.xda-developers.com/axon-7/development/rom-slm-t3752554/post75635304
Click to expand...
Click to collapse
I changed the format to ext4 like you suggested, and now the Oreo beta works. However, the device is shown in settings as an A2017G, even though I'm positive I selected A2017U during install. Obviously, mobile data doesn't work. LOS and RR still fail to boot on both ext4 and f2fs.
BoredIllinoisan said:
I changed the format to ext4 like you suggested, and now the Oreo beta works. However, the device is shown in settings as an A2017G, even though I'm positive I selected A2017U during install. Obviously, mobile data doesn't work. LOS and RR still fail to boot on both ext4 and f2fs.
Click to expand...
Click to collapse
That shouldn't affect the data, try flashing the right modem for a2017u from this thread. As for LOS and RR, are you restoring from a nandroid backup? If you are then you might have to flash the B15 universal bootloader and the U modem.
Hello all,
I have been having issues with upgrading from NoLimits 12.1 to 9.0.4. I know I have to go to 5.1.7 to jump to 9.0.4, but when I try to go back to stock 5.1.4, it keeps rebooting into recovery whenever the phone is booted up. It would get to the NoLimits splash screen and then reboot into recovery.
This is what I try:
https://forum.xda-developers.com/showpost.php?p=78687697&postcount=23
Any combination has the same result (It would get to the NoLimits splash screen and then reboot into recovery). I am at wit's end. No idea what to try anymore. Can anyone help please?
EDIT: I did try NoLimits to 5.1.5/5.1.6/5.1.7 but same as above.
azeem40 said:
Hello all,
I have been having issues with upgrading from NoLimits 12.1 to 9.0.4. I know I have to go to 5.1.7 to jump to 9.0.4, but when I try to go back to stock 5.1.4, it keeps rebooting into recovery whenever the phone is booted up. It would get to the NoLimits splash screen and then reboot into recovery.
This is what I try:
https://forum.xda-developers.com/showpost.php?p=78687697&postcount=23
Any combination has the same result (It would get to the NoLimits splash screen and then reboot into recovery). I am at wit's end. No idea what to try anymore. Can anyone help please?
EDIT: I did try NoLimits to 5.1.5/5.1.6/5.1.7 but same as above.
Click to expand...
Click to collapse
What is you current recovery (file name)?
Is your storage encryped or decrypted?
strongst said:
What is you current recovery (file name)?
Is your storage encryped or decrypted?
Click to expand...
Click to collapse
Storage is decrypted.
azeem40 said:
Storage is decrypted.
Click to expand...
Click to collapse
Maybe you did not wipe system, data, cache before flashing 5.1.4, as clean installation so you have the splash screen left?!
Maybe you can describe your personal steps and files you flashed as detailed as possible.
strongst said:
Maybe you did not wipe system, data, cache before flashing 5.1.4, as clean installation so you have the splash screen left?!
Maybe you can describe your personal steps and files you flashed as detailed as possible.
Click to expand...
Click to collapse
Sorry, I wiped everything and followed what it said in the thread I linked. However, wiping system before flashing the rom just gave an error that no os is installed even though I flashed the 5.1.4 rom afterwards.
Recovery is TWRP 3.2.3-x blu_spark V9.85.
Also, the issue isn't the splash screen but the fact it reboots into recovery after flashing any rom that is not xXx NoLimits.
Even jumping from xXx NoLimits to 9.0.0 after removing the compatibility.zip from the ROM file results in the phone getting to the splash screen and then rebooting into recovery. I don't understand what could be causing this issue. I can't think of anything that would cause such an issue.
EDIT: When I wipe vendor, I get stuck on a black screen after the splash screen.
I solved it. I had to flash blu_spark_r161-oos-pie_op5-op5t_2b876d534.zip after everything.
azeem40 said:
I solved it. I had to flash blu_spark_r161-oos-pie_op5-op5t_2b876d534.zip after everything.
Click to expand...
Click to collapse
Ok, never heard of it, but didn't make sense to flash a custom kernel
strongst said:
Ok, never heard of it, but didn't make sense to flash a custom kernel
Click to expand...
Click to collapse
It was either this or wiping internal storage, cuz those two are the only things that were different this time around.
azeem40 said:
It was either this or wiping internal storage, cuz those two are the only things that were different this time around.
Click to expand...
Click to collapse
More likely the last one
I installed TWRP 3.1.1 using the ODIN patched version and was successful. I had let the system boot into the samsung original stock from where you see "HI" then I rebooted it into TWRP to attempt flashing and I got the /data partition couldn't be wiped. So I ran some of the other repair functions in TWRP and that appear to have fixed it. I then flashed with the latest LineageOS, Gsap, and Magistk20. When it boots up the LineageOS I'm stuck on the Lineage Splash screen. I've let it run over night and it has't changed anything. Any advice?
I recommend trying to wipe the system and reinstall LineageOS with flashing Magisk. If the same problem occurs. Just wipe the system and flash LineageOS without installing Magisk.
secretwolf98 said:
I recommend trying to wipe the system and reinstall LineageOS with flashing Magisk. If the same problem occurs. Just wipe the system and flash LineageOS without installing Magisk.
Click to expand...
Click to collapse
Here's how I think I fixed it.
booted into TWRP
advanced wipe, Factory reset
booted it into TWRP
Flashed the LineageOS
boot into LineageOS
boot it into TWRP
flashed the Gapps.
I'm up and running now. I tried different iterations and It really bothered me because it worked fine on another one. I was also at time flashing it with SuperSU and other times with Magisk. It didn't matter which one I used it got stuck on the LineageOS splash screen.
dizzymon said:
Here's how I think I fixed it.
booted into TWRP
advanced wipe, Factory reset
booted it into TWRP
Flashed the LineageOS
boot into LineageOS
boot it into TWRP
flashed the Gapps.
I'm up and running now. I tried different iterations and It really bothered me because it worked fine on another one. I was also at time flashing it with SuperSU and other times with Magisk. It didn't matter which one I used it got stuck on the LineageOS splash screen.
Click to expand...
Click to collapse
By the way, it's called the boot animation. The splash screen is like the Samsung screen that says powered by Android.
Possible corrupted file
secretwolf98 said:
By the way, it's called the boot animation. The splash screen is like the Samsung screen that says powered by Android.
Click to expand...
Click to collapse
So far you're quite correct I personally have three SM-T580's and they all seem to work just a little bit different. Might I suggest doing an MD5 Sumcheck? The device shouldn't be getting into a bootloop unless there was something wrong with the files, or the device.
Hi all,
so I can't install any Nougat ROMs as they all make my device go to bootloop on the first reboot after flashing, and just keeps the device on the boot animation for hours
This includes LOS14.1, DotOS and ViperOS all versions.
When I flash the CM13 ROM (what I'm using now), everything works normally on the first try.
I can't be the only one experiencing this bootloop, anyone else having these issues?
Did anyone else get bootlooped? Did you manage to circumvent the issue?
Any help is appreciated
phayme said:
Hi all,
so I can't install any Nougat ROMs as they all make my device go to bootloop on the first reboot after flashing, and just keeps the device on the boot animation for hours
This includes LOS14.1, DotOS and ViperOS all versions.
When I flash the CM13 ROM (what I'm using now), everything works normally on the first try.
I can't be the only one experiencing this bootloop, anyone else having these issues?
Did anyone else get bootlooped? Did you manage to circumvent the issue?
Any help is appreciated
Click to expand...
Click to collapse
Did you flash magisk or supersu before fist boot?
I tried with and without rooting, of course before flashing the ROMs (and GApps) I would wipe everything except sd card.
Really don't know what's the issue as the majority of people that reported bootlooping on these ROMs managed to get it fixed later, but none of that works for me.
I tried restoring back to 4.4 then trying again, I tried leaving the boot animation until the tablet runs out of battery then trying again, still no luck.
When I flash the CM13 rom from xda, everything works fine on the first try and first boot takes only a new minutes. I also managed to install the CM12.1 and the latest LightROM for the t560. Weird
Anyway I can only hope this gets resolved, willing to try anything as I don't use this tablet for anything relevant. It's the UK version, if that matters.
phayme said:
I tried with and without rooting, of course before flashing the ROMs (and GApps) I would wipe everything except sd card.
Really don't know what's the issue as the majority of people that reported bootlooping on these ROMs managed to get it fixed later, but none of that works for me.
I tried restoring back to 4.4 then trying again, I tried leaving the boot animation until the tablet runs out of battery then trying again, still no luck.
When I flash the CM13 rom from xda, everything works fine on the first try and first boot takes only a new minutes. I also managed to install the CM12.1 and the latest LightROM for the t560. Weird
Anyway I can only hope this gets resolved, willing to try anything as I don't use this tablet for anything relevant. It's the UK version, if that matters.
Click to expand...
Click to collapse
Try to flash rom without gaaps or magisk only base rom
gitanillo87 said:
Try to flash rom without gaaps or magisk only base rom
Click to expand...
Click to collapse
Make sure the ROM is for your Device. T560NU has a different chip set that the LTE model and you can't interchange roms.
@gitanillo87
Try to flash rom without gaaps or magisk only base rom [\QUOTE]
I did, still not working unfortunately
@magicmckinney Make sure the ROM is for your Device. T560NU has a different chip set that the LTE model and you can't interchange roms. [\QUOTE]
yeah all these roms are for my device (T560)
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Flash my stock rom,with TPRW and later flash any nougat rom
First of all flash clean stock rom using Odin
-Install TWRP
-Factory reset
-Install CM13 and gapps (root optional)
-Wait to boot and pass all the steps in the initial setup
-When tablet completely booted reboot to TWRP
-Install any Android 7 rom ang gapps without factory reset
-Reboot
-Cross fingers and eventually it will boot!!!