Don't know if this is the correct thread category but as title I can't boot with slot A.
I'm using OOS 9.0.17 with unlocked bootloader and Magisk. After messing up with the partitions, I've restored the phone using MSMDownloadTool. Now I've noticed that slot A is not booting, but B is booting. I've tried copying the symlink of slot B to slot A without any chance.
Any advice?
Thanks
dreamwhite said:
Don't know if this is the correct thread category but as title I can't boot with slot A.
I'm using OOS 9.0.17 with unlocked bootloader and Magisk. After messing up with the partitions, I've restored the phone using MSMDownloadTool. Now I've noticed that slot A is not booting, but B is booting. I've tried copying the symlink of slot B to slot A without any chance.
Any advice?
Thanks
Click to expand...
Click to collapse
This is a question and should be in Question and Answer section
Fastboot the whole rom in slot a. Simlinks won't have a chance to work. And why do you need this slot booting? On next update OOS will be fleshed on slot a if you are running on slot b for now. That's the point of A/B phones.
Don't mess with partitions I don't see a single reason to do that.
Striatum_bdr said:
This is a question and should be in Question and Answer section
Fastboot the whole rom in slot a. Simlinks won't have a chance to work. And why do you need this slot booting? On next update OOS will be fleshed on slot a if you are running on slot b for now. That's the point of A/B phones.
Don't mess with partitions I don't see a single reason to do that.
Click to expand...
Click to collapse
Yeah I know but if I break the build.prop of slot A, I can't boot it and I need B
dreamwhite said:
Yeah I know but if I break the build.prop of slot A, I can't boot it and I need B
Click to expand...
Click to collapse
Don't mess with build.prop that's the second rule after don't mess with partitions. If you break both of them not surprising you have issues. A/B slots phones are very tricky and easily upset. Every time I saw people having issues in this forum it was because of unconventional use of recovery, slots etc ..
Well but the strange issue is that if I edit the build.prop in system_b and I choose slot_a it doesn't boot
dreamwhite said:
Well but the strange issue is that if I edit the build.prop in system_b and I choose slot_a it doesn't boot
Click to expand...
Click to collapse
Why would you do this?
Assuming the edited build.prop, hence the os, is on slot b, boot slot b. It should boot unless your tweaks to the build.prop broke something.
Well, I have modded Android until Cyanogenmod 14. And I remember that there were some tweaks in build.prop which I wanted to apply on Op6T :laugh:
Rules to remember for me:
- don't mess up with A/B
- don't edit build.prop
I have messed with both of that (boot slot partitions and build.prop), and I kind of agree, however I rarely have problems as the keyword is experience. I learned quickly what not to do on dual-boot setup, on the Google Pixel, as the Slot B was bricked for a while until I figured out how to fix it, now both boot slots are functional. (And yes, I still have the still-functioning Google Pixel, too bad development activities over there on XDA have actually died down.)
It's wise not to mess with it unless you really know what you are doing, like me. And always back up. Back up. Back up. I mean, everything can go wrong, even on the traditional Slot A only phones (apparently due to the UEFI bootloaders' touchy nature, even the personal computer owners would be familiar with the UEFI bootloader boot failure).
Sent from my ONEPLUS A6013 using Tapatalk
what system are you on 9 or 10 are you rooted some twrps dont work right on older systems get the ota flash in settings then do twrp a/b retention then install magisk directly then do ota it will boot to other system dont forget to turn off all magisk mods first
Related
Hi,
Why can I not successfully flash a zip kernel such as Elemental X or the Rey kernel? The .img file from the Neutrino kernel via fastboot works great. But with zips I get stuck on boot animation regardless of how long it sits. I've flashed in twrp or sideloaded in both twrp or stock recovery. In most cases I'm rooted and on custom ROM, and i especially liked B2 Android P (but no fling navigation and it didn't want to allow root for some reason?) Here's my understanding of the way it goes. As I'm just a novice, please correct my understanding of any concept or feel free to share any extra tips. I feel confident in getting from BTS to rooted custom rom and .img kernel. So my problems are probably in the way it works flashing zips in twrp. My questions are:
Say I'm on partition A running AICP rooted with Magisk and I want to install the ElementalX kernel. So I reboot to boatloader, fastboot flash boot twrp , staying on the same partition (side A) (switch sides here?).... i generally dont. Here is where the confusion comes. I know TWRP will flash a rom to the oppsite partition, so if I flash under this current scenario where i booted into TWRP on side A it will flash a ROM to side B. Additionally: Do I first need to flash the stock boot image here? It seems yes and no people include this as a step. Assuming i should, flashing an image file will stay on the same side, right?So I have flashed the stock boot image and now am installing the kernel zip. Do I flash the zip kernel to the same side (side A) it will be used on, or does it flash to the opposite side like a ROM will? Do all non-ROM zips flash in the same manner? If sideloading, does it have the same result as flashing within twrp?[/I]
To my knowledge I've never gotten past this and, "essentially" lol, have to use a kernel that is installed with fastboot, otherwise I get either bootlooped or stuck on the boot animation. I can get it booted by flashing a kernel via fastboot, but not a zip in twrp. thanks for the read. bonus question is below.
thanks
BONUS- it KILLS me not having a built in option on any ROM to reboot into the other partition to use twrp. Why is there not a mod for this? And i've seen with the Pixel phone and others they have gotten twrp to stick, but that involved using a flashable zip lol if feel ilike
KingBeefy said:
Hi,
Why can I not successfully flash a zip kernel such as Elemental X or the Rey kernel? The .img file from the Neutrino kernel via fastboot works great. But with zips I get stuck on boot animation regardless of how long it sits. I've flashed in twrp or sideloaded in both twrp or stock recovery. In most cases I'm rooted and on custom ROM, and i especially liked B2 Android P (but no fling navigation and it didn't want to allow root for some reason?) Here's my understanding of the way it goes. As I'm just a novice, please correct my understanding of any concept or feel free to share any extra tips. I feel confident in getting from BTS to rooted custom rom and .img kernel. So my problems are probably in the way it works flashing zips in twrp. My questions are:
Say I'm on partition A running AICP rooted with Magisk and I want to install the ElementalX kernel. So I reboot to boatloader, fastboot flash boot twrp , staying on the same partition (side A) (switch sides here?).... i generally dont. Here is where the confusion comes. I know TWRP will flash a rom to the oppsite partition, so if I flash under this current scenario where i booted into TWRP on side A it will flash a ROM to side B. Additionally: Do I first need to flash the stock boot image here? It seems yes and no people include this as a step. Assuming i should, flashing an image file will stay on the same side, right?So I have flashed the stock boot image and now am installing the kernel zip. Do I flash the zip kernel to the same side (side A) it will be used on, or does it flash to the opposite side like a ROM will? Do all non-ROM zips flash in the same manner? If sideloading, does it have the same result as flashing within twrp?[/I]
To my knowledge I've never gotten past this and, "essentially" lol, have to use a kernel that is installed with fastboot, otherwise I get either bootlooped or stuck on the boot animation. I can get it booted by flashing a kernel via fastboot, but not a zip in twrp. thanks for the read. bonus question is below.
thanks
BONUS- it KILLS me not having a built in option on any ROM to reboot into the other partition to use twrp. Why is there not a mod for this? And i've seen with the Pixel phone and others they have gotten twrp to stick, but that involved using a flashable zip lol if feel ilike
Click to expand...
Click to collapse
Sup guy:
A: sides won't switch, if you flash twrp on a, you will stay on A, just make sure you have disabled all locks, pins, swipes, and fingerprint s in room prior...which leads me to B
B: you must flash a stock boot.img (just ex doesn't help, due to system as root), then flash EX, then magisk, in that order, every time.
So.... Flash twrp-->get into twrp recovery-->FLASH STOCKBOOT.IMG VERY IMPORTANT-->flash custom kernel (this is obviously optional)--->magisk--->reboot
Additionally, I recall having issues getting kernels to flash if I didn't swipe all modifications in twrp. I would have the same issues as the OP when I didn't.
Milly7 said:
Additionally, I recall having issues getting kernels to flash if I didn't swipe all modifications in twrp. I would have the same issues as the OP when I didn't.
Click to expand...
Click to collapse
I promise the way above works
aer0zer0 said:
Sup guy:
A: sides won't switch, if you flash twrp on a, you will stay on A, just make sure you have disabled all locks, pins, swipes, and fingerprint s in room prior...which leads me to B
B: you must flash a stock boot.img (just ex doesn't help, due to system as root), then flash EX, then magisk, in that order, every time.
So.... Flash twrp-->get into twrp recovery-->FLASH STOCKBOOT.IMG VERY IMPORTANT-->flash custom kernel (this is obviously optional)--->magisk--->reboot
Click to expand...
Click to collapse
with roms that have built in updates, do i lose root and have to repeat this procedure every time a weekly update happens? the lack of a permanent twrp recovery is so inconvenient
envizion58 said:
with roms that have built in updates, do i lose root and have to repeat this procedure every time a weekly update happens? the lack of a permanent twrp recovery is so inconvenient
Click to expand...
Click to collapse
Like LOS and whatever, yeah, but it takes like 2 minutes. Stock won't flash, since magisk is there anyways
aer0zer0 said:
Sup guy:
A: sides won't switch, if you flash twrp on a, you will stay on A, just make sure you have disabled all locks, pins, swipes, and fingerprint s in room prior...which leads me to B
B: you must flash a stock boot.img (just ex doesn't help, due to system as root), then flash EX, then magisk, in that order, every time.
So.... Flash twrp-->get into twrp recovery-->FLASH STOCKBOOT.IMG VERY IMPORTANT-->flash custom kernel (this is obviously optional)--->magisk--->reboot
Click to expand...
Click to collapse
Thanks! the instruction you gave worked splendidly. I'm only a few months into modding and there are things that become so clear when someone tells you something that answers multiple questions. Thanks in specific for the "whatever side you boot into twrp with is the side you will flash on" . The rebooting sides in twrp doesnt function like an actual reboot.. no one has said that. so , one question down.
staying on topic with twrp, why can someone not write a script or something to reboot to the other side. I've been attempting to install it permanently to that partition like other a/b devices but the hangup for that is they all start with booting twrp using fastboot boot .file instead of flashboot flash boot command. is there an alternative way ti biit without flashing as the ph-1 bootloader doesnt recognize that command? the rest seems easy. but needing to have a computer any time something goes awry is really an inconvenience and if a patch exists I havent found it. you opened the door for this question by giving me the Thomas Edison moment in the first answer. Can't wait for a repeat cuz I'm dying to know this answer. Thanks again bud
Milly7 said:
Additionally, I recall having issues getting kernels to flash if I didn't swipe all modifications in twrp. I would have the same issues as the OP when I didn't.
Click to expand...
Click to collapse
Hopefully I'm reading this correctly, but if you are referring to swiping as opposed to sideloading I've noticed that too. i do still sideload the ROMs but I swipe all mods and kernels. commonly I would get an error regarding /system not remounting after some flashes but that stopped a while back. @topjohnwu commented in a magisk thread to mount system before flashing as a fix. Its worked great.
Thanks for the response and if i read your question wrong fire it back at me for a second attempt lol
KingBeefy said:
Thanks! the instruction you gave worked splendidly. I'm only a few months into modding and there are things that become so clear when someone tells you something that answers multiple questions. Thanks in specific for the "whatever side you boot into twrp with is the side you will flash on" . The rebooting sides in twrp doesnt function like an actual reboot.. no one has said that. so , one question down.
staying on topic with twrp, why can someone not write a script or something to reboot to the other side. I've been attempting to install it permanently to that partition like other a/b devices but the hangup for that is they all start with booting twrp using fastboot boot .file instead of flashboot flash boot command. is there an alternative way ti biit without flashing as the ph-1 bootloader doesnt recognize that command? the rest seems easy. but needing to have a computer any time something goes awry is really an inconvenience and if a patch exists I havent found it. you opened the door for this question by giving me the Thomas Edison moment in the first answer. Can't wait for a repeat cuz I'm dying to know this answer. Thanks again bud
Click to expand...
Click to collapse
with our TWRP being janky as it is, trust me, you dont want living in the other slot.
I am asking myself what these 2 options in TWRP are for,and when they should be executed?
The first option disables/enables dm-verity for the system partition, the 2nd option disables/enable EMMC write protection for the system partition. That's my understanding of it. You are using @Oki's TWRP, correct?
AnonVendetta said:
The first option disables/enables dm-verity for the system partition, the 2nd option disables/enable EMMC write protection for the system partition. That's my understanding of it. You are using @Oki's TWRP, correct?
Click to expand...
Click to collapse
Yes,correct,But i dont understand when we should execute these commands.
I followed oki s guide for flashing los15 with his EDL kit,and he mentioned these steps in his guide...but previous i never used these command
Don't use @Oki's guide, it is better to do everything by hand and get a learning experience/understanding of everything that is going on. Like for instance, view everything as a separate step unto itself (unlocking bootloader, flashing TWRP, flashing a ROM/modem, etc.). I tried both of his EDL packages and had various issues (ROM sometimes not booting, etc). You can still use his TWRP and vendor Party tool, just avoid his EDLs. I had posted in his thread once for help but never got an answer, so I moved on and started from scratch with a clean EDL flash.
Short answer: you can run them whenever you want
AnonVendetta said:
Don't use @Oki's guide, it is better to do everything by hand and get a learning experience/understanding of everything that is going on. Like for instance, view everything as a separate step unto itself (unlocking bootloader, flashing TWRP, flashing a ROM/modem, etc.). I tried both of his EDL packages and had various issues (ROM sometimes not booting, etc). You can still use his TWRP and vendor Party tool, just avoid his EDLs. I had posted in his thread once for help but never got an answer, so I moved on and started from scratch with a clean EDL flash.
Short answer: you can run them whenever you want
Click to expand...
Click to collapse
i always did.
I like to know what it does,not when i can run them whenever i want.
Because whent i have excetue this,my system partition is suddenly smaller,but my battery holds longer %
@Predatorhaze: I tried to explain to the best of my understanding. You are free to flash anything on your phone that you want. @Oki is a good dev and s/he tries to be helpful, but my experience with his/her ROM EDL zips hasn't been good, which is why I recommended to avoid them. The issues you mention seem quite weird, they should not be happening, are you certain?
I can only suggest that you post in the relevant thread for help.
Hi i got pixel experience installed on my Mi A1 and it comes with twrp. When i entered twrp to root i got a message saying encryption failed. Changed slot and discovered that i have android one installed on another slot. So i am confuse, i have two roms on the same device? its stuck on android one logo now!
Every time you upgrade the slot is changed, new OS is installed on the slot not in use and following installation the slot is changed, the old OS remains on the unused slot.
If I am on Android O on slot A and upgrade to Android P, the new Android P is installed on slot B and following a reboot I will be on slot B using Android P, even though I an on Android P, Android O remains on Slot A and is not used unless the upgrade fails in which case Android has a fall back working OS on slot A.
You will always have the old OS on the other slot, its an emergency fall back.
kudos1uk said:
Every time you upgrade the slot is changed, new OS is installed on the slot not in use and following installation the slot is changed, the old OS remains on the unused slot.
If I am on Android O on slot A and upgrade to Android P, the new Android P is installed on slot B and following a reboot I will be on slot B using Android P, even though I an on Android P, Android O remains on Slot A and is not used unless the upgrade fails in which case Android has a fall back working OS on slot A.
You will always have the old OS on the other slot, its an emergency fall back.
Click to expand...
Click to collapse
thx
Just for curiosity... What prevents from a dual boot system?
bodhi3 said:
Just for curiosity... What prevents from a dual boot system?
Click to expand...
Click to collapse
Shared data and other partitions. Only boot and system partitions are dual A/B. Two different systems can't share the same data partition (this is why it's needed to perform a factory reset when switching ROMs).
kudos1uk said:
Every time you upgrade the slot is changed, new OS is installed on the slot not in use and following installation the slot is changed, the old OS remains on the unused slot.
If I am on Android O on slot A and upgrade to Android P, the new Android P is installed on slot B and following a reboot I will be on slot B using Android P, even though I an on Android P, Android O remains on Slot A and is not used unless the upgrade fails in which case Android has a fall back working OS on slot A.
You will always have the old OS on the other slot, its an emergency fall back.
Click to expand...
Click to collapse
Thanks for the explanation!
A re-flash using Mi-Flash with original FW, does it it erase/overwrite the contents of both slots?
If not, how to delete the the contents of both slots?
Tiemichael said:
Thanks for the explanation!
A re-flash using Mi-Flash with original FW, does it it erase/overwrite the contents of both slots?
If not, how to delete the the contents of both slots?
Click to expand...
Click to collapse
No it won't, why do you want to erase the unused slot?
The unused slot is a failsafe should the update fail, as such it remains redundant and unused following a successful update, what is your reasoning for wanting to do this?
Although a failsafe the A/B setup is more about performing a seamless update, allowing you to use Android while the phone is updating to the unused slot, ie no more watch that "updating" message, just a simple reboot, once updated the old slot is unimportant and not worth worrying about.
Tiemichael said:
Thanks for the explanation!
A re-flash using Mi-Flash with original FW, does it it erase/overwrite the contents of both slots?
If not, how to delete the the contents of both slots?
Click to expand...
Click to collapse
Mi Flash script will overwrite both slots with the same FW version and set slot A as active. Check the content of flash_all_lock.bat file to see what is being flashed and how. You can remove lock command from the script to keep bootloader unlocked.
OTA update reflashes only the inactive slot.
@kudos1uk, @_mysiak_:
Thanks for your reply!
Background of my question is this: Somehow I might have screwed up the slot assignment ...
Before I installed Magisk, I used 'fastboot set_active a', and I see Magisk is using slot A. But maybe my OTA upgrade before went to slot B , which could explain why the OTA-upgrade became obsolete/invisible/...
Sorry, I was not aware the Mi Flash script overwrites both slots.
Either way it's certainly the right advice to start over.
fabiofloyd said:
Hi i got pixel experience installed on my Mi A1 and it comes with twrp. When i entered twrp to root i got a message saying encryption failed. Changed slot and discovered that i have android one installed on another slot. So i am confuse, i have two roms on the same device? its stuck on android one logo now!
Click to expand...
Click to collapse
can i get the script for repartition of Mi A1 ROM?? I'm unable to find it anywhere
For starters, there's no thread for this device and I wasn't sure where to put it.
Secondly, me and a friend have been tinkering around with the Cricket Dream 5G and have successfully unlocked the bootloader and obtained root access. Unlocking the bootloader was the easy part. Anyways we've made a full device backup before rooting. I have a magisk patched boot.img. Just unlock the bootloader, flash the patchedboot.img and install magisk. There you go, you have root
WARNING
DO NOT FLASH A MODIFIED SUPER.IMG IT WILL BRICK YOUR DEVICE You can, however modify your system, like removing or adding apps.
I bricked mine because I flashed a modified super img. It's stuck in preloader. Still learning this dynamic partition scheme, it's weird
Full backup on Google drive currently, gonna be moving to mega=>
https://mega.nz/folder/UARQCD6I#8CSNy43GWo6XjEKk_mlldw
Links below, all links are thru mega
Original boot=> https://mega.nz/file/JBAhHSTQ#Aw-GQQ6-StdNAhLsu0vdonNDXcBo4wXI8xEalQ99X2Y
Original boot is in bin format but magisk recognized it and patched it.
Patched boot.img=> https://mega.nz/file/hEJjlaxI#e2DdzvNkq1421uESaSQR4ZP_-CHvt6I_IDCEpyYDZqA
And an app for the magisk modules, not my work, only sharing=> https://mega.nz/file/VAQR0ARI#IUT42ycW5bbb8xVSDhDthREJzr1GEd5WHW0xZbkE8Ts
Also, relocking the bootloader after flashing the patched boot img, it will say there's no OS installed. It's still there. Just unlock it and it'll boot. Not sure why. I believe it's the secure boot being on
Just send a message on here if links are broken
If enough people are on this maybe we can get a working twrp
Update: twrp available here => https://forum.xda-developers.com/t/development-for-the-cricket-dream-5g.4414603/
If anyone uses gpay, unlocking the bootloader will break it. But I know a workaround if anyone wants it.
@Welkwo is behind the twrp process.
My post is just a guide, really.
Thank God! I have numerous phones but for some reason, I have my main number through a sim card thast's unfortunately tied into this phone.. I have been searching online for the stock firmware for this p;hone for a long time with no conclusive results, so upon my search for it this morning, I came acrfoss your post and I almost craped my pants. Thank God.. noot for the almost crapped pants, but for the efforts of you and your friend.. Thank you so much.
We are also working on a TWRP for the device. We can get it to boot but it doesn't recognize the partitions. I absolutely love the cricket dream 5g
Is it not completely slow as **** to you?! It's nowhere near what my OnePlus 5T , Redmi Note 8 nor Motorola Ace One can do nor did I expect it to be but God damn it's just super slow to me..
By the way should I flash boot_a and boot_b in fastboot because when I did the first time when I booted back up it kept making Google framework stop responding
Josephdbrewer25 said:
We are also working on a TWRP for the device. We can get it to boot but it doesn't recognize the partitions. I absolutely love the cricket dream 5g
Click to expand...
Click to collapse
Nevermind.. I retract m yprevious statement.. I just got root and I'm blown away at the sactual speed of this phone. It's such a night and day fgucking difference betweeen having root and not.
Sorry I've been absent. My work has me drained and I've bricked my dream 5g. I messed with my super partition and it is stuck in preloader.
Also I only flashed the boot for the current slot via fastboot
We need to create a scatter file, not quite sure how. Any help is appreciated
yooo... are you guys just needling the scatter to make a twrp recovery?
DrScrad said:
yooo... are you guys just needling the scatter to make a twrp recovery?
Click to expand...
Click to collapse
Honestly I'm not sure. My friend is behind the twrp process. We got one to boot but it don't recognize the partitions so it won't even boot to the os.
Do you have a scatter file? If so please share and I'll also attach it to the op if I have permission, lol
I've got me a new phone so I'll be experimenting again. Just don't flash a modified super img. I messed mine up when I did
Josephdbrewer25 said:
I've got me a new phone so I'll be experimenting again. Just don't flash a modified super img. I messed mine up when I did
Click to expand...
Click to collapse
Josephdbrewer25 said:
We are also working on a TWRP for the device. We can get it to boot but it doesn't recognize the partitions. I absolutely love the cricket dream 5g
Click to expand...
Click to collapse
TWRP for Cricket Dream 5G
Hi there, I have a Cricket Dream 5G and so far I have unlocked bootloader, root via magisk, full system image backup as well as GSI support with a TWRP device tree based on the boot.img. However, the system is A/B with dynamic super partition...
forum.xda-developers.com
lopestom said:
TWRP for Cricket Dream 5G
Hi there, I have a Cricket Dream 5G and so far I have unlocked bootloader, root via magisk, full system image backup as well as GSI support with a TWRP device tree based on the boot.img. However, the system is A/B with dynamic super partition...
forum.xda-developers.com
Click to expand...
Click to collapse
Yeah. Your point? That's the friend working on twrp
No TWRP file?
DragonPitbull said:
No TWRP file?
Click to expand...
Click to collapse
I'll get back with you. Currently at work. I think it's this file in the I've attached but I'm not sure
image-new.img
drive.google.com
Josephdbrewer25 said:
I'll get back with you. Currently at work. I think it's this file in the I've attached but I'm not sure
image-new.img
drive.google.com
Click to expand...
Click to collapse
I not need that. but anyone need permission access.
Josephdbrewer25 said:
Yeah. Your point? That's the friend working on twrp
Click to expand...
Click to collapse
Okay. But the DT in the github is your.
I need access of DT for help and if you or users need help about TWRP improvements. Looking my post about collaborator.....
UPD: I donwloaded your bot_a.bin (I need time for donwload super...img file) and I'm working with that to process informations & simple DT. I prefer collaborator than creating new DT in the github. But if I not receive any answer here so i go create new DT in the github and compiled TWRP file for anyone test.
The question now is: Who is the tester?
UPD1: super_backup_2022-03-10_02-34-47.img from MEGA is not good. 3 times trying donwloading file..... Can you put that as zip file in the GDrive?
UPD2: The super.img file was downloaded.
I need some informations from device. But at this point I'll write in the TWRP Cricket Dream 5G thread. .
If someone can put informations so answer in that thread.
Not sure if I should post here or at the TWRP thread but I think I've fixed the problem with being stuck at preloader after flashing modified super img. I got it to work by flashing the modified super img, locking bootloader and unlocking bootloader.
Can someone else also verify that this works?
Edit: Nvm I've been flashing the wrong super img
UPDATE: TWRP IS NOW AVAILABLE FOR THIS DEVICE.
See this post: https://forum.xda-developers.com/t/twrp-for-cricket-dream-5g.4418963/post-86858605
Kinda new to this, but I have a problem I am hoping someone knows about...I unlocked bootloader then i entered the fastboot flash command ...my phone died, as in shut off, power button does nothing, plugging it in to the computer does nothing, and charging does nothing. Thoughts? I'm assuming its dead? Thnx for listening lol
correction, i entered fastboot reboot fastboot
You know what? IT'S ALWAYS SOMETHIN'! I just got a Cricket Dream 5G for free (promo) and the bloody thing won't read a Micro SD card unless it's formatted to Fat32. Which means the largest card it'll use is a 32gb card. I mean WTH? I've never seen anything like this. If I put in a card formatted to exFat or NTFS it says it's corrupted. A Fat32 card is fine. Anyone else run across this? Just another X-File conspiracy against me.
so...no one knows anything??? anyway to fix this??? i noticed when plugged into computer it makes the connecting noise followed by disconnect noise a few minutes later, and button combos seem to change the timing of said noises but nothing shows up under adb or fastboot devices....help!!!!!
Hello guys.
I need some help and advice with a broken slot and verity mode issue. A/B partitions and AVB are somewhat new to me, so please excuse my ignorance.
I have previously unlocked and rooted my phone without problems, and have been using it for a month. Two days ago, I wanted to start over and flashed the 1.1.7 Global ROM from https://reindex-ot.github.io/ as I have used this package twice before with no errors.
First, I did a wipe but forgot to unroot Slot B (my big mistake) and since it was on the current 1.1.7 OS, I switched slots and flashed the files to Slot A and rebooted directly (fastboot boot) with a patched boot image. After this point, I am no longer sure which slot I was on, as I assumed I would be on Slot A. I don't know if Slot A was already damaged, and I was actually booted into Slot B.
After a successful boot, I installed Magisk, but the restart dialog came up and I accidentally clicked without patching the original boot image. I did another direct boot with a patched boot image, and then patched the supposedly untouched boot image directly and installed it, then rebooted to the OS successfully.
Next, I went to fastboot to check "getvar all" but here's where two errors came up. FIrst, I realized my verity mode was now set to "false", whereas it was always "true" during two other root attempts in the past month. Second, I realized I was in Slot B instead of the one I previously switched to.
I tried to switch back to Slot A, but it boots for a few seconds, fails, then falls back to Slot B. I then tried twice to flash all the usual partitions back to both slots and try them again, and Slot A consistently fails. It is my belief I may have patched a previously rooted boot image in Slot B, and somehow, verity was messed up during that step. At one point, Slot B also failed and I was dumped back to the bootloader. Now, I have one failed slot and verity mode off, so I need some help or advice.
Is there anyway I can re-enable verity, and are there any special partitions I need to flash to get Slot A working?
I previously made a backup of all smaller partitions (eg "modem" "persist" etc) except the "super" and "userdata" partitions with Wanam's partition backup tool. I believe this backup was made directly after I unlocked while on Slot A with 1.1.7 ROM after an OTA update, whereas Slot B at that time would be on 1.1.6 ROM. I think this is true because the sizes of some compressed images (the "abl" "align to 128k" and "boot") differs slightly for each slot's backup.
Will manually flashing the backups to both slots fix anything? Can I revert back to that point in time just after unlock? I am hesitant to do so because I no longer trust my backups in case flashing them qualifies as a "downgrade" (in the case of Slot B using 1.1.6 ROM). Or will manually flashing the backups for Slot A (the 1.1.7 ROM backup) to both slots ensure they are both considered "identical" to the current bootloader and not cause it to trip?
If this is not possible, will flashing a third party ROM to both slots before flashing NothingOS again help, especially if one slot has gone bad? I realize some third party ROMS first require both slots to have the current 1.1.7 ROM before flashing any third party software. I saw someone mention using RiceDroid to "downgrade" from his NothingOS 1.5 beta back to 1.1.7, but I am unsure if this works. I don't particularly mind not using NothingOS and can live with a third party ROM permanently, but I need to fix the damaged slot and maybe get verity back. I assume verity is useless in a systemless root setup with an unlocked bootloader (true or false?) but I wish to get everything back like it was before.
I apologize if my post is too lengthy, I have never posted to forums before, but I wish to be as accurate in describing my issue. Please advise if you can and thank you for any assistance.
Not an expert but I don't think you can make both slots work at the same time. One is for your rom, the other for OTA update. It doesn't matter on wich you are, when you flash, it flashes the other one on wich you are, if I was you, I would have flashed Rice (because of twrp recovery in case something is wrong) two times in a row to make sure your partitions are okay on both slots, then use your reindex link to flash 1.1.7 on one of them if you really want to go back on NOS