First, Let's talk about how to flash a ROM into desired slot.
1. Reboot to another Slot (which you don't want to use) in TWRP.
2. Flash the ROM.
3. Reboot to system.
4. You are in the Slot which you want, and system works good.
--------------------------------------
I tried a couple times with fresh installing two different version of OOS ROM. I flashed them into slot A and slot B respectively and I found that Slot A takes 30 secs to boot, and slot B only takes less than 10 secs to boot.
How is this happened?
I don't think it matters which slot you boot into, you shouldn't need to manually pick one or the other. Just flash as usual and you should be fine.
As for faster boot times, have you tested this with multiple boots on each slot? Could have just been a coincidence that one slot booted quicker than the other.
Or, it could be that the faster booting slot had entered the OS once before and every boot following ends up being quicker in result. I say this because typically the first boot after a ROM flash takes longer than normal.
All-in-all, I don't think user intervention is needed for slots, you can almost forget they are there and be okay. Some users suggest flashing a ROM update to both slots but I've never done that and have had zero issues.
rickysidhu_ said:
I don't think it matters which slot you boot into, you shouldn't need to manually pick one or the other. Just flash as usual and you should be fine.
As for faster boot times, have you tested this with multiple boots on each slot? Could have just been a coincidence that one slot booted quicker than the other.
Or, it could be that the faster booting slot had entered the OS once before and every boot following ends up being quicker in result. I say this because typically the first boot after a ROM flash takes longer than normal.
All-in-all, I don't think user intervention is needed for slots, you can almost forget they are there and be okay. Some users suggest flashing a ROM update to both slots but I've never done that and have had zero issues.
Click to expand...
Click to collapse
Thanks for your help. I tested both slots based on their multiple boot time, also I skipped the first boot. Because the first boot is much slower than the later boots (I call them "Normal Boot"), due to the initial processes.
BTW, I observed a thing, I found that in slot B, the animation logo always spins 4 times and stop perfectly like they've done calc the timing before. And the slot A is not that lucky, always spins 20+ times and stop, which is super slow.
I planned to flash customs due to their stability. Unfortunately, their flash scripts had pinned the ROM to be flashed in slot A, which is not acceptable for geekers like us because we often install plugins that require many reboots.
Related
After I've been installing ROM's, the boot time on my fascinate has been very slow 1-2 mins just to boot before showing unlock screen. I recently installed adrynalyne's DL30 .8 Froyo which has made my boot even slower. I have tried installing boot animations before with little success. Is there a reason my initial boot is this slow? Is there a way to clean the boot files/settings to make it faster? The current boot animation in DL30 .8 is the galaxy S logo without Verizon and it works every time, just stuck on that screen for 2+ minutes before the unlock screen shows.
Edit:
So I took my SD card out and the phone shut down and booted up really fast. All my apps are stored on my phone haven't moved to SD. My phone also shuts down really slowly when the SD card is inserted. Anyone have reasoning for this?
Most likely a combination of the Media Scanner and the fact that Samsung's RFS file system is SLOW! Once we have Voodoo again things should get way better.
[Also, this belongs in General as it is NOT development]
Martian21
Anytime you flash a new ROM, theme, etc. the next boot up will always take longer
I have a Galaxy Note 3 and a Galaxy Note 4. I encrypted them and it seemed to go smoothly on both phones.
However after boot, the Note 4 started giving me headaches.
Turning it on I see the usual CyanogenMod's animation for a few seconds then it jumps and disappears. then I see a white box saying Android is finishing booting, and then I'm presented with a pattern screen different than the one I used to see. This one lets me change the amount of dots. It also lets me make emergency calls. So I slide my pattern, I see "Checking" then it's just the same initial CyanogenMod animation. For ever.
With the Note 3 I saw the exact same thing but the second animation lasted just a few seconds. Now it is working fine. The Note 3's storage had around 100MB in data. The Note 4 has several gigabytes of data in it. I presumed it was still doing some work, so I left it in the animation screen for a few hours. When I touched it was burning hot.
It won't enter Recovery Mode. I tried flashing recoveries with both Odin and Heimdall. With Odin it seems to work but it won't boot into Recovery Mode. Heimdall always gives me an error. I tried flashing cm-12.1-20160316-NIGHTLY-trltexx-recovery.img, twrp-2.8.7.0-trltexx.img and twrp-3.0.0-0-trltexx.img with Heimdall and twrp-2.8.7.0-treltexx.img.tar and twrp-3.0.0-0-treltexx-treltexx.img.tar with Odin.
Update: I've managed to install TWRP 3.0. The problem still persists though. TWRP doesn't ask for password or pattern, which doesn't allow me to do pretty much anything. The only MicroSD card I have is only 256MB - usable 240MB - latest CM 12.1 nightly is 255MB - so I can't even flash a new ROM! I'm surprised TWRP doesn't have a way to decrypt the storage. I very much hope I'm missing something.
Update 2: I've managed to flash a few different ROMs via ADB Sideload. I still can't get access to the data partition at all. I can't even format it! I'm getting quite desperate at this point.
Please, help!
I guess you could try a complete repartition using a pit file.
http://forum.xda-developers.com/showthread.php?t=3282641
I flashed a stock ROM. I genuinely thought it would completely erase the entire phone memory, but it didn't. as soon as it finished booting I saw the pattern decryption screen, but it just wouldn't accept my pattern.
I flashed another TWRP 3 again, went to that scary screen and wiped, and formatted, and erased, and did everything it allowed me to do, as I was sick and tired of that drama. flashed some CM to it and was done with it.
never trying to encrypt that thing again. Android's openness is too chaotic: too many OS variants, too many vendors, too many minor model variations, too many non-standard stuff going on. the result is it's unlikely someone else will have the exact same problem, with the same model, the same OS. I'm done.
I'm currently running the latest PureNexus (MM) with a pretty vanilla setup, I.e. no xposed, root, etc. All the sudden yesterday I had a hard crash while doing nothing in particular, a sudden reboot that sent me into a boot loop. It reboots right before the boot animation would appear. The only way I was able to fix it was to wipe the data partition. I was subsequently able to restore my backup and it booted successfully. The frustrating part is it's happened several times since then. In fact I can't keep it running more than a few hours without the same thing happening, even after doing a full wipe. Any ideas?
Thanks!
Arg, I tried flashing the new Android N system image (the official one) which basically flashes every partition and I'm still getting a boot loop. Is it possible that my SD card went bad?
ts_mpls said:
Arg, I tried flashing the new Android N system image (the official one) which basically flashes every partition and I'm still getting a boot loop. Is it possible that my SD card went bad?
Click to expand...
Click to collapse
Did you use flash-all.bat from google image or you flashed the images one by one?
I tried both. Both N and MM. Apparently I stumped Google too, they're sending me a new one.
that's weird... Glad you got a replacement though!
I haven't followed development of the 6T since November so please forgive me if this has been answered 100 times.
The steps to flashing custom non-OOS ROM's is to; flash ROM/flash TWRP installer/reboot recovery/flash gapps/flash magisk
The weird issue for me is when I reboot recovery after flashing the ROM and TWRP when I go to install gapps all my files are encrypted. My way around this was to sideload gapps and magisk and everything booted up fine. When I go back to recovery after the first boot all the files are normal again.
This has happened both times I've flashed a ROM.
I'm sure this has an easy answer and it's most likely due to a step I didn't execute properly -- or at all. I did a lot of reading and making sure I understood the process before rooting my device but as far as flashing ROM's I was noticing a lot of conflicting info which I've never seen before on any other device. Anyway, other than this I haven't had any issue.
Thanks for any feedback.
Security issue. Best way around it is to either format data before flashing and/or remove your lockscreen security pin before flashing.
Deleted
ogkillergreen said:
Security issue. Best way around it is to either format data before flashing and/or remove your lockscreen security pin before flashing.
Click to expand...
Click to collapse
I never use any lock. Always just use Swype to unlock. I'm aware of the issue with using a lock though. I read that people had problems. I just haven't seen where any one brought up my exact issue. It doesn't seem to effect anything so I'm not stressing it too bad. Eventually I'll get around to troubleshooting it.
I've flashed almost every ROM for 6T till now and every time I flash a ROM I'm having exactly the same issue as you. I've also tried formatting data several times, but the issue with unreadable data in TWRP after flashing a ROM returns every single time. I've tried multiple combinations of flashing, wiping etc. and it's always the same. However, what I'm doing in such case is flashing gapps + magisk from USB-C pendrive, no need to sideload, just mount USB and flash files from that as usual. After doing that I can boot to ROM and the data is readable again. I just need to remember to have this pendrive close to me when I'm flashing a new ROM.
BreathingWounds said:
I've flashed almost every ROM for 6T till now and every time I flash a ROM I'm having exactly the same issue as you. I've also tried formatting data several times, but the issue with unreadable data in TWRP after flashing a ROM returns every single time. I've tried multiple combinations of flashing, wiping etc. and it's always the same. However, what I'm doing in such case is flashing gapps + magisk from USB-C pendrive, no need to sideload, just mount USB and flash files from that as usual. After doing that I can boot to ROM and the data is readable again. I just need to remember to have this pendrive close to me when I'm flashing a new ROM.
Click to expand...
Click to collapse
Thanks for the tip and info. I don't mind sideloading because it's fast and anytime I mess with my phone it's when I'm at my PC. I've been using adb for so many years it's my go-to whenever my phone is acting stupid.
The second time I flashed a ROM I didn't even worry about flashing gapps, just magisk. And I stacked them. So ROM, TWRP, Magisk. Then rebooted system. I actually prefer this anyway because then you boot straight to the launcher with no setup process. Then I go back and flash GAPPS. I actually have used this flashing process for years because I hate the setup after a first time boot.
2 days ago my phone world was perfect. I had Android 10 just the way I wanted it on slot b and Droidian on slot a.
Today I can only boot on 1 slot and everything got wiped out.
I updated Droidian to bookworm and later installed snap. Ran sudo apt update again and the phone was bricked. I thought no problem, just switch slots and boot back to Android. Got into fastboot, switched slots, rebooted....bricked.
A user in the TG group sent me the Halium boot image and I accidentally flashed it to the A10 slot. No biggie, just get the right boot img and flash it...I thought. Flashed Halium to the correct slot...nothing.
Finally got into TWRP, where I should have had all the files I needed for a dirty flash of A10 and everything was gone from the phone. Everything was wiped. Not a huge problem I have a backup from April of the Android stuff and Droidian was 2 weeks old.
Sideloaded A9 to both slots and could only boot in 1 of the slots. A9 booted up, but no wifi. Went ahead and re installed Droidan and started setting it up (wifi worked fine). This morning I was installing flathub and an update. Has several unment dependencies and a large list of files that were no longer needed. Did not notice until after autoremove ran into problems the 1st file was "android-base-files" (see below). Not sure but guessing that cause the phone to brick again.
Latest update****I have A11 in slot B, but when I got to slot A it boots twice then goes to recovery. I have to delete everything to boot on that slot. No issues going back to B, but when I come back to A I have to do it all over again to get it to boot.
The guys in the Droidan TG group have been very helpful but have no idea what happened or how to get me back up and running on both slots.
Any ideas how to get both slots working??
Nothing on the phone right now so wiping and starting over is no problem. Done that 7 or 8 times in the last 48 hours.
can't delete