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
Related
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!
Good morning.
I was running 7.1.1 Dev 1 until yesterday afternoon.
The upgrade to Dev 2 popped up and I said no.
When I came back to my phone it was stuck in a boot loop.
I turned the device off and back on but it still was in a boot loop.
I decided to flash Stock NBD90X.
There was no issue with the flash.
The phone though is still in a boot loop and I am unsure where to go from here.
When I was running Dev 1 7.1.1 it was rooted and running Google assistant with the Pixel build prop. Could that be the issue?.
Any help gratefully received.
Matt
MATTHEWLONG said:
Good morning.
I was running 7.1.1 Dev 1 until yesterday afternoon.
The upgrade to Dev 2 popped up and I said no.
When I came back to my phone it was stuck in a boot loop.
I turned the device off and back on but it still was in a boot loop.
I decided to flash Stock NBD90X.
There was no issue with the flash.
The phone though is still in a boot loop and I am unsure where to go from here.
When I was running Dev 1 7.1.1 it was rooted and running Google assistant with the Pixel build prop. Could that be the issue?.
Any help gratefully received.
Matt
Click to expand...
Click to collapse
This has been an ongoing thing with the 6P and 5X, there are multiple threads on this bootlopop issue some recoverable, some not. Check this out see if it helps..
http://forum.xda-developers.com/android/help/guide-revive-angler-bootloop-t3454938/page5
Thanks for the support, I will take a look.
I've read too many threads about 7.1 and the beta program causing boot loops and bricks....this is ridiculous!
Do you have a nandroid on hand? If so, try restoring it and see if that works.
I have only boot looped twice with this phone. Each time I went into TWRP and did a full wipe (everything except internal storage). I completed the full wipe three times consecutively. After the third wipe I boot into fastboot and flash the latest stock images from Google. Reboot.
Let the phone sit for 10-15 minutes then boot back into fastboot to flash custom recovery (TWRP). Then boot into recovery to flash SuperSU. Reboot. Let phone sit for another fifteen before continuing with setup.
I know wiping the device three times probably doesn't do anything extra than wiping once before flashing but it's what I've always done and what's always worked for me.
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.
So tl;dr version - i was using my tablet, saw an update to magisk, installed it, now it boots to black screen while running sambones rom
[SM-P580] [BQK1] SaMBoNeS
TWRP 3.2.3.0 --> 3.3.1.0
longer story:
i was trying to get a game to run, it wasnt...and realized it has been a while for a restart, so i checked to see if anything needs to be updated and saw magisk needed an update. i didnt note what version it was before but it was a version or two earlier than what it was trying to install.
rebooted to blackscreen no samsung logo
have tried restarting a dozen times, booted to TWRP, tried to force normal system boot through the UI, nothing.
I tried installing a new kernal [SiriKernel], it made it to the samsung logo, waited 15 - 20 minutes and it never made it past. restored a backup using TWRP
updated TWRP to 3.3.1.0, still no luck.
i had this problem a long time ago, and cannot figure out how i fixed it....it may have fixed itself but it isnt this time. any advice would be appreciated. I am trying to avoid wiping and starting again if at all possible because the problem seems familiar. also trying to stick to a rom for use with adaptive storage. if i do have to wipe if that can be done on a newer stock OS that's fine as well but last time i messed with this tablet it wasnt