Hello! I am so sorry beforehand for my noob question but I still can't understand how it's exactly work. I have read a lot information about slot A/B and now I've faced with one question which I can't understand by my self. Firstly I flashed recovery by lineage os both A and B . Then I flash ROM by lineage OS when I was in recovery slot B. After it recovery changed to A by itself and ROM load normal but when I try from ADB to change slot to B and load to ROM from slot B I do get bootloop. I have to change slot B to A again for booting in ROM . Is it OK or I should have opportunity to load in ROM both from slot A and slot B?
BigBan123 said:
Hello! I am so sorry beforehand for my noob question but I still can't understand how it's exactly work. I have read a lot information about slot A/B and now I've faced with one question which I can't understand by my self. Firstly I flashed recovery by lineage os both A and B . Then I flash ROM by lineage OS when I was in recovery slot B. After it recovery changed to A by itself and ROM load normal but when I try from ADB to change slot to B and load to ROM from slot B I do get bootloop. I have to change slot B to A again for booting in ROM . Is it OK or I should have opportunity to load in ROM both from slot A and slot B?
Click to expand...
Click to collapse
First thing is to be able to boot either you have to completely wipe data first or neither will boot. So in essence you could have lineage on b and run till your tired then you could fastboot--set-active =a and have stock rom. But won't boot unless you wipe data between trying. Op8 here and it's basically the same thing
mattie_49 said:
First thing is to be able to boot either you have to completely wipe data first or neither will boot. So in essence you could have lineage on b and run till your tired then you could fastboot--set-active =a and have stock rom. But won't boot unless you wipe data between trying. Op8 here and it's basically the same thing
Click to expand...
Click to collapse
Without success unfortunately. What I have recovery: lineage-17.1-20201229-recovery-hotdog.img . What I did:
1) loaded in recovery slot A and wiped data and factory reset
2) loaded in recovery slot B and wiped data and factory reset
3) flashed ineage-17.1-20201229-nightly-hotdog-signed.zip
4) rebooted to recovery and it's showed slot A but I haven't changed it
5) made wipe data and factory reset in slot A again
6) loaded in recovery slot B and wiped data and factory reset and tried to load in system (unfortunately without any success)
What did I wrong or it works correct and it should be so?
BigBan123 said:
Without success unfortunately. What I have recovery: lineage-17.1-20201229-recovery-hotdog.img . What I did:
1) loaded in recovery slot A and wiped data and factory reset
2) loaded in recovery slot B and wiped data and factory reset
3) flashed ineage-17.1-20201229-nightly-hotdog-signed.zip
4) rebooted to recovery and it's showed slot A but I haven't changed it
5) made wipe data and factory reset in slot A again
6) loaded in recovery slot B and wiped data and factory reset and tried to load in system (unfortunately without any success)
What did I wrong or it works correct and it should be so?
Click to expand...
Click to collapse
You wipe one flash one reboot to other repeat
toolhas4degrees said:
You wipe one flash one reboot to other repeat
Click to expand...
Click to collapse
I'm not sure what you mean exactly but I tried to update my ROM on new version from standard point in the system and it's install in slot B automatic and then system load from slot B without any problem. Ths for your response!
BigBan123 said:
I'm not sure what you mean exactly but I tried to update my ROM on new version from standard point in the system and it's install in slot B automatic and then system load from slot B without any problem. Ths for your response!
Click to expand...
Click to collapse
I meant you wipe current slot data then flash rom then reboot to recovery which should take you to other slot then you wipe data again and flash rom again. Then reboot.
toolhas4degrees said:
I meant you wipe current slot data then flash rom then reboot to recovery which should take you to other slot then you wipe data again and flash rom again. Then reboot.
Click to expand...
Click to collapse
Why would you do it twice? Data is shared across both slots, it's redundant.
Lossyx said:
Why would you do it twice? Data is shared across both slots, it's redundant.
Click to expand...
Click to collapse
Benn doing it for 2 years wipe all the flash reboot to recovery and repeat works everytime
Related
Hello
I have issu with many ROM, after i flash them i get black screen boot and nothing happend
The only rom i manger to get working are
http://forum.xda-developers.com/showthread.php?t=2222535
http://forum.xda-developers.com/showthread.php?t=2260951
http://forum.xda-developers.com/showthread.php?t=2396234
http://forum.xda-developers.com/showthread.php?t=1756659
Any idea why ? I try many different rom but there are the only one working!
I use SAFESTRAP and have tried different ROM slot
Thx for your help
Which version of Safestrap? Create slot, wipe data/cache, flash Rom, flash appropriate gapps, wipe dalvik, reboot.
I've never used LS 2.2 or ArtMod, but I had to install LS 2.9 on slot 3. AOKP on slot 2.
LuckiestNut419 said:
Which version of Safestrap? Create slot, wipe data/cache, flash Rom, flash appropriate gapps, wipe dalvik, reboot.
I've never used LS 2.2 or ArtMod, but I had to install LS 2.9 on slot 3. AOKP on slot 2.
Click to expand...
Click to collapse
I think i have used the wrong version of Safestrap : Safestrap-RAZR-D4-BIO-3.11.apk do you think it can be the problem here ?
Motorola Razr XT910 from Europe
Also i never wipe dalvik after flashing rom, i will try it
Thx for your help, any other suggestions ?
No, I believe that's the correct version. It's what I use, and have been recommended to use (as 3.5 seems to have some issues with some roms). Once you've created the proper romslot, run (under wipe menu) "factory reset". Then, install rom, install gapps (whatever apps are recommended by dev; then wipe cache/ dalvik cache, and reboot. You shouldn't have any problems. The proper gapps are imperative to not getting the death-by-forced-close experience, though it's easily correctable. Good luck.
EDIT
Also ensure that whatever the recommended slot is the slot you use; PA- slot 1, AOKP- slot 2, LS- slot 3. Any other roms should have listed, either in the original thread, or replies, the correct slot to install to.
Been using twrp since rooting note II. I wanted to try out 4.4 PA but they said to only use cwm. It was late so I decided to be lazy and since I used to use rom manager all the time I installed it to flash cwm recovery then booted into recovery to install touch version. It wasn't showing the touch version so selected to restart to check to see where I saved it to it would not boot past the first "note II" splash screen. Battery pull then back into recovery and went ahead and flashed PA 4.4 and now it will get past the splash screen then shows boot animation but then starts all over.
Is this a rom manager issue?
can I flash twrp from within cwm recovery?
will I have to basically reroot it?
Any suggestions on how to get back to twrp and to a usable phone?
thanks
If you download a .zip of twrp and flash it you will have twrp for your recovery.
As long as you flash a rooted rom, you will be rooted.
Not sure what happened with the boot loop, did you by chance wipe the system without flashing another before booting?
Sent from my SCH-I605 using Tapatalk
cadavjo said:
If you download a .zip of twrp and flash it you will have twrp for your recovery.
As long as you flash a rooted rom, you will be rooted.
Not sure what happened with the boot loop, did you by chance wipe the system without flashing another before booting?
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
Nope did my standard wipe cache, wipe dalvik, and factory reset then flashed rom then gapps. Going to go back to twrp and wait for 4.4 to be more stable before I try it out again and maybe then I can use twrp to flash it.
thanks for the help
cadavjo said:
If you download a .zip of twrp and flash it you will have twrp for your recovery.
As long as you flash a rooted rom, you will be rooted.
Not sure what happened with the boot loop, did you by chance wipe the system without flashing another before booting?
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
that didn't work. flashed newest twrp then rebooted into it and tried to flash tweaked and sticks at the splash screen again
jdpeck said:
that didn't work. flashed newest twrp then rebooted into it and tried to flash tweaked and sticks at the splash screen again
Click to expand...
Click to collapse
Have you wiped data at all? You need to wipe data / factory reset when switching roms, and it sounds like you havent.
fallingup said:
Have you wiped data at all? You need to wipe data / factory reset when switching roms, and it sounds like you havent.
Click to expand...
Click to collapse
As stated above, on both cwm and twrp I wiped caches and did factory reset and still having the issues. Once back on twrp I even formatted internal memory thinking maybe rom manager messed something up on it and still can't get passed the splash screen.
jdpeck said:
As stated above, on both cwm and twrp I wiped caches and did factory reset and still having the issues. Once back on twrp I even formatted internal memory thinking maybe rom manager messed something up on it and still can't get passed the splash screen.
Click to expand...
Click to collapse
Copy a ROM to your SD card (external not internal)
Install cwm and format data (actually full format, where /data/media gets wiped) and system
Install rom
Reboot
TWRP has some issues randomly with corrupting /data, that's why I no longer use it.
fallingup said:
Copy a ROM to your SD card (external not internal)
Install cwm and format data (actually full format, where /data/media gets wiped) and system
Install rom
Reboot
TWRP has some issues randomly with corrupting /data, that's why I no longer use it.
Click to expand...
Click to collapse
Finally got it. Thought using odin to flash back to root 66 and start fresh would work but after that it was still going to the splash screen then black and a battery pull had to be done. TWRP back ups would fail when trying to restore, so I reverted back to an older version of twrp and it finally let a back up be installed and it booted up just fine!!
thanks for all the suggestions
Im having a similar problem to yours, I am using twrp and flashed PA 3.99 the phone works great, but if my battery dies or i restart the phone or shut it down it automatically wont get passed the samsung logo, or sometimes the PA logo, the only work arounds ive seen to it is to wipe the cache and dalvik to boot, but when that fails i have to install the whole rom over again. any ideas?
I really want to use SafeStrap instead of BMM because with BMM, my SD card and internal storage get messed up on every reboot. However, I'm just not ok with partitioning in order to install a ROM; I want it installed over my Stock partition. Can I do that with SafeStrap? Whenever I try, it just boots to a black screen after the recovery.
Redjax said:
I really want to use SafeStrap instead of BMM because with BMM, my SD card and internal storage get messed up on every reboot. However, I'm just not ok with partitioning in order to install a ROM; I want it installed over my Stock partition. Can I do that with SafeStrap? Whenever I try, it just boots to a black screen after the recovery.
Click to expand...
Click to collapse
yeah you can. clear you cache and dalvik in the recovery, should start up find after that.
@Redjax Have you had any luck in doing this? I tried flashing to the stock partition (after making backups of everything, thank goodness!) and got the same black screen. Is there anything extra to do if you want to flash the Stock partition?
I flashed to the newest cm11 to stock slot on SS3.65. Here's what I did with no problems.
Activate Stock Slot
Wipe: Cache, Dalvik Cache, Android_secure, System, Data (Repeat; I always wipe everything twice, probably unnecessary, but i like to be sure)
Flash CM11 Nightly
Flash PA Gapps
Flash JBX Kernal
Flash WiFi Patch
Wipe Cache, Dalvik Cache again
Reboot
Everything worked fine first try. I realize what you flash will probably be different depending on which Rom you choose.
Sent from my Nexus 10 using xda app-developers app
coreywallen said:
I flashed to the newest cm11 to stock slot on SS3.65. Here's what I did with no problems.
Activate Stock Slot
Wipe: Cache, Dalvik Cache, Android_secure, System, Data (Repeat; I always wipe everything twice, probably unnecessary, but i like to be sure)
Flash CM11 Nightly
Flash PA Gapps
Flash JBX Kernal
Flash WiFi Patch
Wipe Cache, Dalvik Cache again
Reboot
Everything worked fine first try. I realize what you flash will probably be different depending on which Rom you choose.
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
Hmm.. I wiped everything except for the Android_secure... Wonder if that's what did it? I was just trying to flash the latest/first official CM11 nightly, along with DHackers no_set_metadata GAPPS.
After I flashed the phone wouldn't boot -- just red Moto symbol then black screen. I managed to get it into APX Fastboot mode, used DROID_RAZR_Utility to flash the stock rom back on to the phone (without data wipe). Lo and behold, the phone came back to life! RE-rooted and reinstalled Safestrap 3.65, and all the slots were still there -- no harm, no foul, but I thought for a good while I bricked the phone. Whew!
Ok, Off to research what the Android_secure partition is for...
I think, BMM is better than SS, don't have any problem with my device
I've been out of the loop for awhile. Back in the days of og droid we just used recovery. SS came in later allowing you to have dual boot.
If you don't want that option can you just use a recovery like CW and not use SS or BMM?
Sent from my XT912 using Tapatalk
On SS 3.65 i always wipe in my stock rom everything exept the SD card and the internal Storage and it works, i do it like that nearly a year without any problems.
Yes, I've not had a problem. I'm using Jelly Bean's ROM, and all I did was backup my Stock ROM, wipe it, and install through SafeStrap. I don't know why it wouldn't work for you...what ROM are you attempting it with?
I installed some roms like "ArchiDroid_V2.5.1_2 - Resurrection_Remix_KK_v5.1.5"
but after install any rom my phone doesn't boot ,, keeps restarting showing ”Samsung Galaxy S3 GT-1930 :crying: :crying:
any solutions????
t4r3k said:
I installed some roms like "ArchiDroid_V2.5.1_2 - Resurrection_Remix_KK_v5.1.5"
but after install any rom my phone doesn't boot ,, keeps restarting showing ”Samsung Galaxy S3 GT-1930 :crying: :crying:
any solutions????
Click to expand...
Click to collapse
More information is needed for people to be able to help you
(1) What recovery are you using
(2) Are you wiping before flashing (If so explain how you may have missed a step)
(3) Are you doing a factory reset after flashing
Many things cause a bootloop details please more details will stop alot of people suggesting things you may have already tried.
tallman43 said:
More information is needed for people to be able to help you
(1) What recovery are you using
(2) Are you wiping before flashing (If so explain how you may have missed a step)
(3) Are you doing a factory reset after flashing
Many things cause a bootloop details please more details will stop alot of people suggesting things you may have already tried.
Click to expand...
Click to collapse
(1) What recovery are you using?? i'm using recovery clockwork touch-6.0.4.4 s3 GT-i9300
(2) Are you wiping before flashing (If so explain how you may have missed a step)?? yes
(3) Are you doing a factory reset after flashing?? yes
t4r3k said:
(1) What recovery are you using?? i'm using recovery clockwork touch-6.0.4.4 s3 GT-i9300
(2) Are you wiping before flashing (If so explain how you may have missed a step)?? yes
(3) Are you doing a factory reset after flashing?? yes
Click to expand...
Click to collapse
Thankyou for your reply unfortunately you did not answer question (2) fully...The reason I asked for in detail is that you may need to do a full wipe not a standard wipe ie: format system, format data,format cache delvik etc.This will get rid of any residue files left over ready for a clean install (sorry if you do this already) I would suggest trying the above but be careful it leaves you without any rom in system so have one ready to flash from ext sd card.
If that fails I would flash stock with odin and if that boots try again but with a different recovery.
tallman43 said:
Thankyou for your reply unfortunately you did not answer question (2) fully...The reason I asked for in detail is that you may need to do a full wipe not a standard wipe ie: format system, format data,format cache delvik etc.This will get rid of any residue files left over ready for a clean install (sorry if you do this already) I would suggest trying the above but be careful it leaves you without any rom in system so have one ready to flash from ext sd card.
If that fails I would flash stock with odin and if that boots try again but with a different recovery.
Click to expand...
Click to collapse
I did it all
i need link for stock rom
t4r3k said:
I did it all
i need link for stock rom
Click to expand...
Click to collapse
Sammobile.com
Check that the problem isn't the power button, somethimes it stucks and the device keeps rebooting like crazy
Plz anybody help this out...
I unlocked bootloader, then immediately flashed Pitchblack recovery, then booted into recovery.
Initially console shows decrypted FBE device with default password. But Encryption status : Encryped
So I went into wipe & Formatted Data inorder to get rid of encryption. Then I rebooted recovery & it shows Unable to decrypt FBE device.
[UPDATE] (24/12/20) : The console output Unable to decrypt FBE device was nothing but to tell us that incompatible operating system flashed.
I flashed global version roms which are the main cause for bootloops. I flashed stock rom, then immediately worked out of the box.
1. Format data after going into twrp *It will wipe you device*
2. If you don't want to install a custom rom just mod MIUI, remove your lock screen password or flash orange fox and if it asks for password just put your lock screen password.
3. Else if you want to install a custom rom
Open recovery
Wipe data cache davilk
Flash rom
Format data
Reboot.
LoadOP2 said:
1. Format data after going into twrp *It will wipe you device*
2. If you don't want to install a custom rom just mod MIUI, remove your lock screen password or flash orange fox and if it asks for password just put your lock screen password.
3. Else if you want to install a custom rom
Open recovery
Wipe data cache davilk
Flash rom
Format data
Reboot.
Click to expand...
Click to collapse
Thnx for reply. I've tried Orange fox too. When I format data, internal storage doesn't decrypt. Also when I flash custom roms, they flash, but I'm gonna stuck in bootloop.
My main problem is that I can't decrypt storage. Phone boots only when I'm on MIUI stock. Am I missing something ?
That is odd but still flash fastboot rom and then flash twrp , flash a rom of your choice then format data . Maybe it will help . Btw which rom are you installing.
LoadOP2 said:
That is odd but still flash fastboot rom and then flash twrp , flash a rom of your choice then format data . Maybe it will help . Btw which rom are you installing.
Click to expand...
Click to collapse
Thnx for the reply. I'm trying to have lineage 17.1 & resurrection remix official build. I think rom's not the issue here. I need to know one thing.
To exactly say my issue, I can do flashing. But when I do & then reboot, Internal storage doesn't show the size & mtp doesn't work too, with bootloop issues along together.
There is no official LineageOS for the device.
kalehrl said:
There is no official LineageOS for the device.
Click to expand...
Click to collapse
Oh, I've mistaken, I was about to say resurrection remix official build & lineage unofficial one. Btw what do you think my device is going up to ? How can I decrypt & use internal storage successfully? I can't use internal storage when I flash a rom. Bcaz internal storage renders useless because of encryption.
Which recovery are you using?
Try flashing magisk 20 or 21.
Flash twrp by marounfurio( I am sorry if I slaughtered the name) which is available on xda.
And format data.
It's midnight here and I am going to sleep I will help to tommorow morning.
LoadOP2 said:
Which recovery are you using?
Try flashing magisk 20 or 21.
Click to expand...
Click to collapse
Right now I'm on Pitchblack beta latest build.
I tried magisk on MIUI stock through patched boot method, it worked, but no apps able to access root. I checked all magisk settings...
I think encrypted data partition is the whole culprit here. How can I decrypt it ?
MPK99 said:
Right now I'm on Pitchblack beta latest build.
I tried magisk on MIUI stock through patched boot method, it worked, but no apps able to access root. I checked all magisk settings...
Click to expand...
Click to collapse
And what about flashing magisk in twrp.
MPK99 said:
Right now I'm on Pitchblack beta latest build.
I tried magisk on MIUI stock through patched boot method, it worked, but no apps able to access root. I checked all magisk settings...
I think encrypted data partition is the whole culprit here. How can I decrypt it ?
Click to expand...
Click to collapse
Formatting data normally decrypts it . I don't know why something like this is happening here.
Follow my guide again maybe? Give it a shot step by step.
LoadOP2 said:
Formatting data normally decrypts it . I don't know why something like this is happening here.
Follow my guide again maybe? Give it a shot step by step.
Click to expand...
Click to collapse
Yah, I'm feeling weird too. Normally there are 3 ways to remove decryption...I tried all those.
1. Formatting Data by typing "yes"
2. Formatting data partition from f2fs to ext4
3. Installing Decrypt script v2 zip immediately after flashing stock rom.
I tried everything I could. I know all sorts of common flashing things. I caz I always used to try so many roms on my previous redmi's, but this one is special case.
I'd suggest you use LineageOS recovery. That's how I removed decryption.
kalehrl said:
I'd suggest you use LineageOS recovery. That's how I removed decryption.
Click to expand...
Click to collapse
Sure. Encryption is the whole culprit for me to say exactly. I'm trying to decrypt & flash builds. I'll notify if it works. Nice to get help from you guys.
Try this.
How to decrypt rom/storage so you can easily switch roms without format
First I would thankx to @sakhatlonda for koutiliy.zip
Steps to download file
1. Download koutility.zip from below.
2. Documentation related to koutility
Read from below link (recommended)
Just a utility zip which can be flashed on every rom flash, to do some pre-defined tasks.
Can be used either to copy everything you place in sdcard/sudeep/system_root to respective dirs or to set config and use that to do predefined tasks
This is how it works:
Flash in recovery, every option has Note with it
Available Configs:
brbootdtbo - auto backup/restore boot & dtbo, will do backup if no backup present and will do restore if backup is there
bbootonly - always backup boot
bdtboonly - always backup dtbo
resbootdtbo - always restore boot & dtbo (brbootdtbo won't work if this is enabled)
enalways - encrypt always (edauto won't work if this is enabled)
dealways - decrypt always (enalways & edauto won't work if this is enabled)
edauto - auto change encryption state on each flash
avb - removes avb flags (if decrypted)
quota - removes quota flag (if decrypted)
keep - doesn't over-writes boot/dtbo backups
debloat - removes bloats
rebloat - restore removed bloats
patchD - same as flash but set in config
productsize - makes a product image from your currently flashed rom to sdcard/sudeep and adds 600mb to it. So you can flash gapps etc. without error. (PC needed to flash product.img)
Steps to decrypt rom/storage
1. Flash roms
2. Flash koutility.zip tested on aosp only
3. Format data (required only first time after flashing koutility)
4. Reboot to recovery
5. Flash gapps (optional)
6. Boot into system
Congratulations your storage/rom is decrypted , you can switch roms without format
Next time when you want to switch roms
Steps
1. Wipe data,caches and dalvik caches
2. Flash rom
3. Flash koutility.zip
4. Reboot to recovery
5. Flash gapps (optional)
6. Boot into system
Notes
Remember you need to config koutility.zip in recovery
How to config koutility for decryption
Volume down (set config) > yes
After that "No" till 5th option
Then "yes" for 6th option
Rest "No" till 15th option
Last "yes" to flash
@LoadOP2 Thanx for providing KoUtil & its read me.
But I think we shouldn't reboot to recovery immediately after formatting the data. Because the stock rom will start it's initial encryption process by then & I won't get decrypted storage. Isn't it ?
I think this is the case that's happening to me. I always reboot recovery after formatting data, my storage will encrypt again because of stock rom's existence.
Yes you have to reboot to recovery. Otherwise you won't be able to use data partition.
LoadOP2 said:
Yes you have to reboot to recovery. Otherwise you won't be able to use data partition.
Click to expand...
Click to collapse
Yes, you're correct, we should do that. But can you read my 1st post in this thread. This is about that specific problem. I'm rebooting recovery after formatting data, then recovery shows Unable to decrypt FBE device
Send your recovery logs after formatting data.
LoadOP2 said:
Send your recovery logs after formatting data.
Click to expand...
Click to collapse
That would help. I'll attach screenshots too. Currently I'm on stock & being busy. I'll do this by today night & post logs & screenshots.