Related
Hey guys,
So last night I accidentally wiped internal storage in TWRP. I guess that messed up my partitions or something, I don't know. Anyway, I can still access recovery, and I've tried to do a restore (one that I made back when I was on stock 4.4.2 I think) but after that it tries to boot, gets to "Android is upgrading... Optimizing app Y of X." and once that operation completes it shows the lockscreen for about a tenth of a second, and the phone reboots.
I'm stumped. Anyone know what can I do?
Sorry if this has been asked a hundred times. For some reason the search function in the forums isn't working for me. And I've been looking for a solution all morning.
EDIT: FYI when I tried the restore I did only System and Data and not Boot, because I was afraid that'd cause more problems.
Did you try restoring and performing a factory wipe before booting the newly-restored ROM?
It seems that Marshmallow based roms aren't working, but Lollipop ones will boot. Not sure why as I didn't have any problem with the same MM roms in the past.
More info:
MM roms wont flash in TWRP; after the failed attempt, TWRP says system cannot be mounted until I either wipe or install a 12.1 rom.
Tried to install a stock rom (4.4.2) and it failed in TWRP. Just says "Error Flashing"
Are you performing a full wipe (system, Dalvik, cache, data) before installing or restoring a ROM? Is the phone running the latest version of TWRP?
audit13 said:
Are you performing a full wipe (system, Dalvik, cache, data) before installing or restoring a ROM? Is the phone running the latest version of TWRP?
Click to expand...
Click to collapse
Yes to full wipe. TWRP is 2.8.7.0, so yeah I think it's the newest? Not 100% sure.
Wiping internal storage should not affect the partitions. I'm not sure that TWRP even has the ability to change partitions.
Yes, 2.8.7.0 is the latester version of TWRP.
If you are on the nj2 bootloader, try flashing this in TWRP: http://forum.xda-developers.com/galaxy-s3-att/general/rooted-ucufnj1-stock-rom-t2985006
Welp, seems to be all good now. Not sure if I really did anything to fix it or not. I tried to install a stock ROM but it wouldn't boot (stuck on Samsung logo) but after that my CM13 ROM installed properly again. The one CM13 ROM I have still wont install at all - maybe that file became corrupt or something? Not sure if that's even possible.
Either way I'm all fixed up. Thanks for all your help.
Cheers
Glad you got it sorted out. If you do figure out what you did to get it working, post your answer as it may help others that are in a similar situation.
After flashing TWRP with Odin, I boot into recovery and wipe the dalvik cache. I then go to install the CM13 zip file, and it works. I wipe Dalvik again and reboot in the os. This is where it just shows the CM boot screen infinitely. Nothing else. What is up. I am using the latest TWRP and CM13 release.
Try this:
1. Wipe cache, dalvic cache, data, system
2. Install CM13 again, along with your gapps(google apps if you didn't know, custom ROMs never come with them, optional)
3. Boot it, it should work
You cannot switch ROMs without wiping data. Bad things happen.
You must clean flash when:
1. Switching between a stock ROM to a custom ROM
2. Downgrading Android versions (5.1 to 5.0)
3. Switching custom ROMs (I.E. CM13 to AICP)
4. When the ROM's thread warns to (switching keys)
5. Switching between nightly builds and stable.
When you're updating nightlies, you shouldn't have to though.
RDChase said:
Try this:
1. Wipe cache, dalvic cache, data, system
2. Install CM13 again, along with your gapps(google apps if you didn't know, custom ROMs never come with them, optional)
3. Boot it, it should work
You cannot switch ROMs without wiping data. Bad things happen.
You must clean flash when:
1. Switching between a stock ROM to a custom ROM
2. Downgrading Android versions (5.1 to 5.0)
3. Switching custom ROMs (I.E. CM13 to AICP)
4. When the ROM's thread warns to (switching keys)
5. Switching between nightly builds and stable.
When you're updating nightlies, you shouldn't have to though.
Click to expand...
Click to collapse
Just did it, it still seems to be booting like it previously was. Wiped cache, dalvic, data, and system and then installed CM13 and gapps. Still booting as I write this.
Since that failed, check your download, make sure nothings bad. If its bad, redownload, if not, idk.
If you post your recovery logs, or what the console says, that will help me figure out what's going on.
Also, is your phone the triband model (l710t)?
Are you flashing anything else at the same time?
The more info you give, the better.
RDChase said:
Since that failed, check your download, make sure nothings bad. If its bad, redownload, if not, idk.
If you post your recovery logs, or what the console says, that will help me figure out what's going on.
Also, is your phone the triband model (l710t)?
Are you flashing anything else at the same time?
The more info you give, the better.
Click to expand...
Click to collapse
I've kind of given up at this point. Even CM12 doesn't work. The only thing that seems to work is the stock rom. My phone is the regular SPH-L710 model. I didn't even know the L710t was a thing.
I have the same problem, and sometimes it boot in the system setup mode, but the sensor is not working, i can turn on airplane mode, reboot or power off, and sensor works, what happend i dont know((
ovil101 said:
After flashing TWRP with Odin, I boot into recovery and wipe the dalvik cache. I then go to install the CM13 zip file, and it works. I wipe Dalvik again and reboot in the os. This is where it just shows the CM boot screen infinitely. Nothing else. What is up. I am using the latest TWRP and CM13 release.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2755793
helped)))
1vankill1 said:
http://forum.xda-developers.com/showthread.php?t=2755793
helped)))
Click to expand...
Click to collapse
That just seems to be a stock rom.
yes it stock rom, after it was installed, I was able to install 13 cm
Hello!
Recently I unlocked the bootloader and flashed twrp on my phone...
I decided to try Sultan's CM13 because it's very popular... I downloaded it, flashed it, along with Gapps, and everything was good...
Then, I decided... I want to try a new ROM.
So, I went in, wiped everything besides internal storage then went to flash the ROM and Gapps...
Everything was good (optimizing and booting wise) then I got in to the system setup....
5-10 seconds after I got into system setup (Language selection and such), my whole phone froze, then rebooted... It did this on a continuous cycle, so I decided to wipe dalvik + cache, and to no avail, it still froze my phone and restarted it...
I decided to restore to the back up I made (OOS 3.2.4) and it works fine there, but any custom ROM breaks my phone, I've tried Resurrection Remix with Mini Gapps, and Sultan's CM13 with Full Gapps, and vise versa...
Help? Thanks!
got the same problem after flashing CM 13....
SynaTech said:
Hello!
Recently I unlocked the bootloader and flashed twrp on my phone...
I decided to try Sultan's CM13 because it's very popular... I downloaded it, flashed it, along with Gapps, and everything was good...
Then, I decided... I want to try a new ROM.
So, I went in, wiped everything besides internal storage then went to flash the ROM and Gapps...
Everything was good (optimizing and booting wise) then I got in to the system setup....
5-10 seconds after I got into system setup (Language selection and such), my whole phone froze, then rebooted... It did this on a continuous cycle, so I decided to wipe dalvik + cache, and to no avail, it still froze my phone and restarted it...
I decided to restore to the back up I made (OOS 3.2.4) and it works fine there, but any custom ROM breaks my phone, I've tried Resurrection Remix with Mini Gapps, and Sultan's CM13 with Full Gapps, and vise versa...
Help? Thanks!
Click to expand...
Click to collapse
I'll tell you what, this is the only situation where saying "try something different" is valid. So, there you have it.
To flash between different roms you have to wipe everything so do a titanium backup of all your apps them full wipe flash the new ROM and then restore your apps with titanium
daleski75 said:
To flash between different roms you have to wipe everything so do a titanium backup of all your apps them full wipe flash the new ROM and then restore your apps with titanium
Click to expand...
Click to collapse
I don't care about apps, however, If I wiped internal, wouldn't it get rid of all my Roms, and my backups?
SynaTech said:
I don't care about apps, however, If I wiped internal, wouldn't it get rid of all my Roms, and my backups?
Click to expand...
Click to collapse
If you just do a standard wipe without going into advanced on twrp you will be fine.
Hello!
For some reason the custom ROMs Sultans CM13 and Resurrection Remix crash every 5-15 minutes, it freezes then reboots, and does it faster after that. I've tries reinstalling TWRP to no avail...
Stock works fine with Root and Xposed... But Custom ROMs don't want to work... So my guess is it's not a hardware issue...
I really want to get this solved since HOS is being merged with OOS...
help? Thanks!
SynaTech said:
Hello!
For some reason the custom ROMs Sultans CM13 and Resurrection Remix crash every 5-15 minutes, it freezes then reboots, and does it faster after that. I've tries reinstalling TWRP to no avail...
Stock works fine with Root and Xposed... But Custom ROMs don't want to work... So my guess is it's not a hardware issue...
I really want to get this solved since HOS is being merged with OOS...
help? Thanks!
Click to expand...
Click to collapse
This is not a hardware issue..
Back to stock..
Did you wipe all?
Twrp latest better 3.2.0
madsponge26 said:
This is not a hardware issue..
Back to stock..
Did you wipe all?
Twrp latest better 3.2.0
Click to expand...
Click to collapse
_________________________________________________
Back to stock as in... No root, stock bootloader?
Wipe all being Dalvik + Cache + System or Dalvik + Cache + System + Internal?
Also, I'm on the latest version of twrp possible
SynaTech said:
__________________________________________________
Back to stock as in... No root, stock bootloader?
Wipe all being Dalvik + Cache + System or Dalvik + Cache + System + Internal?
Also, I'm on the latest version of twrp possible
Click to expand...
Click to collapse
No that's both dirty flashing. You need to wipe Dalvik + Cache + System + data.
Do not wipe internal because then there's nothing left to flash.
You will lose all your apps wiping data but I suppose you know right?
J_Dutch said:
No that's both dirty flashing. You need to wipe Dalvik + Cache + System + data.
Do not wipe internal because then there's nothing left to flash.
You will lose all your apps wiping data but I suppose you know right?
Click to expand...
Click to collapse
Yes I know, I've flashed before...
Now, when I wipe all but internal (for obvious reasons) I will loose root + xposed correct? I've never flashed any Roms while having root and xposed installed...
Or before I flash do I have to delete/remove both?
SynaTech said:
Yes I know, I've flashed before...
Now, when I wipe all but internal (for obvious reasons) I will loose root + xposed correct? I've never flashed any Roms while having root and xposed installed...
Or before I flash do I have to delete/remove both?
Click to expand...
Click to collapse
When you wipe all but internal you are starting clean and don't need to do anything other then flash ROM+gapps
And optional flash xposed. Root is already included in most roms.
J_Dutch said:
When you wipe all but internal you are starting clean and don't need to do anything other then flash ROM+gapps
And optional flash xposed. Root is already included in most roms.
Click to expand...
Click to collapse
Since I want to flash Sultans CM13, root isn't included... So, my flash order is...
Wipe Dalvik + Cache, System, Data (Everything but system), Flash ROM, GApps, and Root, then Xposed all in one flash?
SynaTech said:
Since I want to flash Sultans CM13, root isn't included... So, my flash order is...
Wipe Dalvik + Cache, System, Data (Everything but system), Flash ROM, GApps, and Root, then Xposed all in one flash?
Click to expand...
Click to collapse
Your doing it correctly.but still facing issues so i will suggest you to do real clean flash that means first flash full rom zip (about 1.3 gb in size) of stock oos via twrp then let device to boot.
Then enter into recovery ( use Official latest one) and wipe cache, data and system partition.
Now flash ROM.zip - supersu -kernel(optional) and now boot the Device and let it optimize all apps.
If you want Xposed now you can flash it ( be careful while selecting xposed zip . flash appropriate zip - sdk23 arm64)
JumboMan said:
Your doing it correctly.but still facing issues so i will suggest you to do real clean flash that means first flash full rom zip (about 1.3 gb in size) of stock oos via twrp then let device to boot.
Then enter into recovery ( use Official latest one) and wipe cache, data and system partition.
Now flash ROM.zip - supersu -kernel(optional) and now boot the Device and let it optimize all apps.
If you want Xposed now you can flash it ( be careful while selecting xposed zip . flash appropriate zip - sdk23 arm64)
Click to expand...
Click to collapse
So, I've flashed CM13 Sultans with root, which I haven't done before... It seems stable, I'll know in an hour or so...
JumboMan said:
Your doing it correctly.but still facing issues so i will suggest you to do real clean flash that means first flash full rom zip (about 1.3 gb in size) of stock oos via twrp then let device to boot.
Then enter into recovery ( use Official latest one) and wipe cache, data and system partition.
Now flash ROM.zip - supersu -kernel(optional) and now boot the Device and let it optimize all apps.
If you want Xposed now you can flash it ( be careful while selecting xposed zip . flash appropriate zip - sdk23 arm64)
Click to expand...
Click to collapse
He didn't mention he wiped data, since I told him to wipe data it will be fine now, there is totally no use in going through all you describe, people just need to read a little and know how to wipe and flash.
SynaTech said:
Yes I know, I've flashed before...
Now, when I wipe all but internal (for obvious reasons) I will loose root + xposed correct? I've never flashed any Roms while having root and xposed installed...
Or before I flash do I have to delete/remove both?
Click to expand...
Click to collapse
Haven't had cause to use xposed for a while, but am assuming it still uses it's own framework? This used to preclude flashing a new rom whilst xposed was activated.
ghostofcain said:
Haven't had cause to use xposed for a while, but am assuming it still uses it's own framework? This used to preclude flashing a new rom whilst xposed was activated.
Click to expand...
Click to collapse
Annnnnd...
IT WORKS!
I'm so happy, I decided to wipe the dalvik and cache after every action... And wipe each party all together, then individually... It works!
And yes, Xposed uses its own framework still, its super easy to install, I would recommend checking it out again!
SynaTech said:
Annnnnd...
IT WORKS!
I'm so happy, I decided to wipe the dalvik and cache after every action... And wipe each party all together, then individually... It works!
And yes, Xposed uses its own framework still, its super easy to install, I would recommend checking it out again!
Click to expand...
Click to collapse
But it does mean you have to do full wipe and or deactivate it before flashing new rom. I probably will get around to using xposed again one day just nothing I need from it at present.
J_Dutch said:
He didn't mention he wiped data, since I told him to wipe data it will be fine now, there is totally no use in going through all you describe, people just need to read a little and know how to wipe and flash.
Click to expand...
Click to collapse
The ROM still crashed, ugh.. I'm worried that I won't be able to get an OTA working, since I can't get them normally because of root, xposed, etc...
I did everything you said, and it still crashed...
To be fair, it took waaaaay longer than normal to crash, so I think we are getting there... Hmmm
Suggestions?
Thanks!
Also, it crashes the same way every time, freeze for 5-10 seconds, then boop, black screen, then reboot...
SElinux is enforcing, and I'm encrypted... Could those have anything to do with it? Thanks!
ghostofcain said:
But it does mean you have to do full wipe and or deactivate it before flashing new rom. I probably will get around to using xposed again one day just nothing I need from it at present.
Click to expand...
Click to collapse
The ROM ended up crashing, ugh.. I'm worried that I won't be able to get an OTA working, since I can't get them normally because of root, xposed, etc...
I did everything you said, and it still crashed...
To be fair, it took waaaaay longer than normal to crash, so I think we are getting there... Hmmm
Suggestions?
Thanks!
Also, it crashes the same way every time, freeze for 5-10 seconds, then boop, black screen, then reboot...
SElinux is enforcing, and I'm encrypted... Could those have anything to do with it? Thanks!
Debugging instability with custom roms, and adding xposed modules into the mix, is a bit of a black art but here goes.
First install your custom ROM, with a clean flash i.e wipe everything. Do Not restore any data, except the stuff Google restores itself. Run the rom in this state for a good while (as a rule of thumb try running it for twice your expected stable period before considering it at stable i.e if it crashes once a day run it for two days) if stable proceed to next stage.
If your chosen custom ROM does not have xposed framework install it and activate now, Do not install any modules run for a while to access stability before proceeding to next step.
One by one install your chosen modules, again running each for a while to access stability.
At any one of these steps stability should degrade if so you have identified your culprit.
I know this process is laborious and likely to take a while to complete but sometimes otherwise rock solid roms can be affected by a combination of things and without carrying out the above steps identifying the culprit is nigh on impossible, do bear in mind that some custom roms are just less stable than stock.
ghostofcain said:
Debugging instability with custom roms, and adding xposed modules into the mix, is a bit of a black art but here goes.
First install your custom ROM, with a clean flash i.e wipe everything. Do Not restore any data, except the stuff Google restores itself. Run the rom in this state for a good while (as a rule of thumb try running it for twice your expected stable period before considering it at stable i.e if it crashes once a day run it for two days) if stable proceed to next stage.
If your chosen custom ROM does not have xposed framework install it and activate now, Do not install any modules run for a while to access stability before proceeding to next step.
One by one install your chosen modules, again running each for a while to access stability.
At any one of these steps stability should degrade if so you have identified your culprit.
I know this process is laborious and likely to take a while to complete but sometimes otherwise rock solid roms can be affected by a combination of things and without carrying out the above steps identifying the culprit is nigh on impossible, do bear in mind that some custom roms are just less stable than stock.
Click to expand...
Click to collapse
Wipe everything but internal correct? And also should I install gapps right away or wait a bit, then install gapps?
Thanks for all the help!
Yes wipe everything bar internal, personally I'd run it without gapps, even, to start with.
ghostofcain said:
Yes wipe everything bar internal, personally I'd run it without gapps, even, to start with.
Click to expand...
Click to collapse
Even without Gapps, it crashed in around 2-3 minutes
Wow, that is poor. You aren't having this problem with stock OS?
Hi everyone,
I recently made a fresh install of the latest OOS ROM on my Onplus 5T (OOS 9.0.8). After reinstalling all the apps and data I tried to root the phone. My bootloader was already unlocked, so I just went on to flash TWRP (first tried the official TWRP 3.3.1 dumpling, and then the 3.3.1 blu_spark version). Then I tried to flash Magisk via TWRP (tried versions 19.2, 19.3, 19.4), and every time I try to reboot I get stuck on a black screen with the cyan led on, and I have to uninstall Magisk in order to reboot on the phone. Also the phone is encrypted, and I have a the Microsoft Intune Portal app installed to use some work apps, but I don't know if that can be the source of the problem.
If you have any idea on how to successfully flash Magisk, that would be amazing.
Thanks in advance :good:
I use the same version of ROM and magisk I use is canary build . Working fine. (even its not canary build I also can boot successfully)
you might need to check if some apps you install might cause this.
my recommendation is clear /data and starts fresh then root it before installing any apps. to see if it working fine or not.
also after you flash magisk do you try to wipe cache, dalvik-cache?
and how long are you waiting for its to boot? normally it would take more time than normal boot (without magisk)
Just connect to to ADB and delete vendor.. recovery.. rom.. radio.. antennaa.. ect everything. Get yourself a stock full rom and flash that through ADB. Then flash custom recovery, custom rom, gapps, custom kernel, magisk. thats it. find stock rom on manufacturers data server. I did this to a different phone I had but this is the way to 100% fix everything... by purging the phone to nothing. You can however do a twrp backup before doing so.
Thanks for the input, I will try first to reflash the ROM and root before installing any apps, and see if it works in order to avoid the long process of restoring all my data. I do wipe cache/dalvik cache before and after every flash. If that doesn't work I will try another time a clean flash and tell you if it worked.
I just reflashed the ROM and right after I flashed Magisk 19.3, then rebooted and it worked. Not sure what the issue was but the problem is now resolved. Thanks guys for the advice.