Related
This is a thread where people can discuss what is working and not working for them for the boot manager app. I will begin by asking if anyone else is having problems using bootmanager with the magnolia ROM. My next question would be is anyone else having a problem not being able to turn on wifi for miui if its put as an sdROM? The only roms that really seem to be fully functional are CM7 and OMFG. What ROM are most people using for the phone ROM, and what roms do you have working fully as sd card roms?
I haven't had much luck with the Boot Manager so far... I can make the backup of my current rom (Miui) and try and install the zips of other downloaded roms and get almost all the way finished and then I will get an error message.. So I have given up and thought I'd wait for an update and see if that may help.
Got Miui Working fine.
After some work and reinstallation I was able to get miui working on the sdcard ROM, for boot manager. I will keep this updated if I notice any more fixes.
A quixk suggestion would be to clear them and reinstall boot manager and restart your phone, after doing that and reinstalling the ROMS on ext2 I noticed they worked/ installed, when they wouldn't before.
After getting the hang of it I have been able to flash any ROM, kernel, nightly or whatever. It's awesome, I think.
I do everything to the phone rom slot through regular clockwork recovery, as if the app didn't exist. Then from the phone rom I flash everything else to the other slots. I always go back and boot into the phone rom before I flash anything to the other slots. Not sure if that's right but it has worked for me.
It would be cool if you could restore an existing nandroid you had into one of the slots but I don't think they are formatted the same. Not sure.
Can someone explain the method of how to perform the setup?
To setup, run the "setup phone rom", which only takes a few seconds. What this does is make a copy of your boot file in case you screw something up. Once this is done, you can install up to 4 different ROM's on your SD card and then boot into them from this same program.
If something gets screwed up along the way and you cannot boot your phone, boot into CWR, install a zip from a file, and find the update.zip in the bootmanager/phonerom(or whatever ROM folder you want to boot) folder.
Currently I am running MIUI, TSM pool party, TSM gangbang, Skyraider Zues, and newt's 3.0 port.
I was hoping to get some discussion started about Boot Manager. One thing I would like to know is what roms have others successfully installed to a slot. I would also like to hear any tips or tricks. I have found this app to be frustrating, love the idea of it though. So lets get this going and help each other out, sure I'm not the only one that likes the idea of this app but have been frustrated with it at times. Thanks
Boot Manager always asks if I want to install a slot as ext2 or ext4 but it seems I'm currently running ext3. Now what?
I use ext2 usually works better also select use large boot image almost all aosp roms work fine sense roms seem more picky with bm but most work fine.
Sent from my Incredible 2 using Tapatalk
Which sense roms have you had work in a slot. I have tried Mikrunny, Skyraider Zeus and TSM Vanilla. They all work as a phone rom, have gotten them all to successfully install to a slot but none will boot.
I used to use skyraider in a slot but had it as phone rom an made a backup of it an restored the backup to a rom slot an it worked fine.I run magnolia from a slot without any problems.
Sent from my Incredible 2 using Tapatalk
Thanks RRF12, using ext 2 as you suggested I was finally able to get Skyraider Zeus and MikRunny to install and boot from a slot. Starting to like this app now. I never gave the custom sense roms much of a chance, that is why I wanted to use this app, thought I would keep them on the phone longer and play with them more.
I have tried several times to flash Areoevans new ICS kernel using boot manager and it is not working, any ideas.
Edit: Figured it out, must be you can't flash a new kernel to the slot you are currently using. I booted into a different slot and then successfully flashed the new kernel to the slot with ICS rom.
Woot! I finally got a ROM to boot in a slot. Checking large boot image did it.
Something else I have noticed that seems to work is to flash roms, kernels and other zip files to the slot roms when you're booted into the phone rom not another slot rom.
anyone using SD booster? What settings do you use?
How about MIUI roms? I can't get them to get DATA working if they are in a slot, but if I flash them in the phone rom, I get data working?
bberryhill0 said:
Woot! I finally got a ROM to boot in a slot. Checking large boot image did it.
Click to expand...
Click to collapse
Where do you go to check large boot image?
barinaman said:
Where do you go to check large boot image?
Click to expand...
Click to collapse
Menu> Settings
Thanks! 10char
This app will let you dual boot your phone, correct? Was thinking of installing it so I can test different ROM's and not always have to re-install is I don't like a new ROM.
It gives you four ROM slots in addition to your main (phone) ROM. Pretty slick when it works. I couldn't get MikRunny to work in a slot. Each loaded slot takes 2GB of space on the SDCard.
This works great for almost all AOSP ROMs but haven't had any luck with sense ROMS at all.... which sucks because flashing a phone rom isn't really using boot manager its using your phone. Being able to boot a sense from from one of the slots is what matters and nothing appears to boot that has sense. I am able to use Aeroevans ICS roms flawlessly though.
I have yet to get a rom to work with this app... When I try to install a zip(rom) all I get is a message that there is an error building the boot.image.
I get this on all the roms I have tried. I have large boot image checked...
If I could sell this app to someone, I would ... Waste of money if you asked me.
PacerguyDon said:
I have yet to get a rom to work with this app... When I try to install a zip(rom) all I get is a message that there is an error building the boot.image.
I get this on all the roms I have tried. I have large boot image checked...
If I could sell this app to someone, I would ... Waste of money if you asked me.
Click to expand...
Click to collapse
I was having lots of issues, but finally found success.
Make sure large boot image is checked, which looks like you have
disable logging in super-user app under preferences
Check keep screen on during install
use ext 2 for sense roms.
I have succeded when flashing a rom to the phone rom, making a nandroid and then restoring said nandroid to a slot.
If you can get the logs emailed to init2winit, they have always been pretty quick with help.
I have sucessfully booted Coredroid, Condemned sense, condemned cm 7.2, MIUI 4.0 (old miui works without data in a slot), couple ICS roms, Vivow milestone 3 & TSM Bullet.
420fan said:
I was having lots of issues, but finally found success.
Make sure large boot image is checked, which looks like you have
disable logging in super-user app under preferences
Check keep screen on during install
use ext 2 for sense roms.
I have succeded when flashing a rom to the phone rom, making a nandroid and then restoring said nandroid to a slot.
If you can get the logs emailed to init2winit, they have always been pretty quick with help.
I have sucessfully booted Coredroid, Condemned sense, condemned cm 7.2, MIUI 4.0 (old miui works without data in a slot), couple ICS roms, Vivow milestone 3 & TSM Bullet.
Click to expand...
Click to collapse
Thanks for the input.
I did finally get CM7 to install into slot one... So I booted into it. Then when I tried to download Boot Manager to CM7 from the market, I kept getting error messages from the market and was unable to download Boot Manager (or any other app) so I ended up going to recovery and flashed back to my Backup of CM9... I think I'm going to give up on this app for a while again
You don't have to flash back with boot manager if you have your phone rom setup just boot into recovery an install your zip of phone rom will be under boot manager.I use bm all the time most everything works except a lot of sense rooms which I don't use anyway.
Sent from my Incredible 2 using Tapatalk
Safetrap 3.05 is awesome and hashcode will release a new version 3.1 with flashing to Stock ROM soon for Razr M, this is a very important update since the complicity of Additional slot and Image files would eat up space for apps, most the apps will be installed into Image drive, but some of them, ( like games, heavy apps which requires additional data ) are not able to be installed since doesn't have enough space in Image as well as outside. So this is my trick to Flash Custom ROM directly to Stock slot. even CM10, BHD, and so on...
Step 1: Use stock ROM to install Safetrap as normal.
Step 2: Go to safestrap, create 1Gb drive and install your favourite ROM, and flash all additional package you like (Beat, Dolby, GAPP etc... )
Step 3: Boot into that ROM and make changes as you want
Step 4: Make a backup of that ROM
Step 5: Change Boot option to Stock
Step 6: RESTORE ( not Install since Install function was not invented yet on Safetrap 3.05) and restore your backup directly to stock ROM
Step 7: Install Safetrap again
Step 8: PROFIT
I haven't neither tested with all ROM nor running through a day, but it's works for now with BHD ROM. This can be awesome method before new Safetrap released.
Hope u enjoy it.
Dave
Thanks much !! Confirmed on BDH v2
Sent from my XT907 using xda premium
Help please
So I've installed Safestrap 3.0, have downloaded simplex rom. I created a ROM slot 2GB slot. When I go to install the ROM it merely opens the folder rather than prompting the install. Any idea as to what is going wrong?
cfitz0812 said:
So I've installed Safestrap 3.0, have downloaded simplex rom. I created a ROM slot 2GB slot. When I go to install the ROM it merely opens the folder rather than prompting the install. Any idea as to what is going wrong?
Click to expand...
Click to collapse
Did you choose the zip file?
Sent from my XT907 using Tapatalk 2
I would use the exact version as OP.
Did you use 3.0.5 ?
yes. 3.05 ... Running so good with outstanding battery life now..
So u flashed Slot 2 with Custom rom, made a back up of it.
Then Restored Slot 1 with back up of Slot 2.
Making the phone run Custom Rom in Slot 1
The question is Is slot 2 still there ?
And how do you get it back to stock if messing up ? Do you just RSD it back to Stock ?
Germanese said:
So u flashed Slot 2 with Custom rom, made a back up of it.
Then Restored Slot 1 with back up of Slot 2.
Making the phone run Custom Rom in Slot 1
The question is Is slot 2 still there ?
And how do you get it back to stock if messing up ? Do you just RSD it back to Stock ?
Click to expand...
Click to collapse
No you delete slot 2 before restore ( u already have the backup in the sd card ) .. if you messing up, you can always use fastboot RSD to reinstall stock rom. Easy.
Sent from my XT907 using Tapatalk 2
Could anyone post a mirror of 3.05.20?
Proxy at work has me blocked.
EDIT: NM, Got it.
Thanks for the info =)
cybrnook
I was going uhhhhh wth is that girl doing LMAO ? It just caught me off guard LMAO made me laugh confused.
For some reason when I try to install any version of Safestrap the app FCs upon opening and I am unable to fully get it installed
Sent from my XT907 using xda premium
UN5EEN said:
For some reason when I try to install any version of Safestrap the app FCs upon opening and I am unable to fully get it installed
Sent from my XT907 using xda premium
Click to expand...
Click to collapse
You should wipe and reinstall from beginning then.. Best solution..
nevermind.
jtommyj said:
Thanks much !! Confirmed on BDH v2
Sent from my XT907 using xda premium
Click to expand...
Click to collapse
i did all of the instructions except when I boot up it stays on the glowing red eye screen...not sure if I'm boot looping or what but I redid the process and it sill continues
this is really helpful for people that install a lot of apps.
cpupeli1 said:
i did all of the instructions except when I boot up it stays on the glowing red eye screen...not sure if I'm boot looping or what but I redid the process and it sill continues
Click to expand...
Click to collapse
I used RSD Lite to flash the stock ROM (Jellybean); however, after the phone rebooted, it has been stuck at the glowing red eye screen. I will try fastbooting and flashing the ICS stock ROM instead, and then updating the OS, but does anyone know why this occurs? I did try to fastboot and re-flash the JB 2x with the same result.
JOLiu said:
I used RSD Lite to flash the stock ROM (Jellybean); however, after the phone rebooted, it has been stuck at the glowing red eye screen. I will try fastbooting and flashing the ICS stock ROM instead, and then updating the OS, but does anyone know why this occurs? I did try to fastboot and re-flash the JB 2x with the same result.
Click to expand...
Click to collapse
I know I'm 2 1/2 months late to this party, but I've had the same issue. Trying to restore CM10 to my stock slot from slot 1, and I get to the red eye and it hangs.
To restore to working order, had to go into quick boot and flash ICS stock and then JB stock (going straight to JB stock left it hanging at red eye again). Then restored my backup to slot 1 to get back to where I started.
Anybody know how to get around this? Thanks.
colbyman said:
I know I'm 2 1/2 months late to this party, but I've had the same issue. Trying to restore CM10 to my stock slot from slot 1, and I get to the red eye and it hangs.
To restore to working order, had to go into quick boot and flash ICS stock and then JB stock (going straight to JB stock left it hanging at red eye again). Then restored my backup to slot 1 to get back to where I started.
Anybody know how to get around this? Thanks.
Click to expand...
Click to collapse
If I restore CM10 on stock slot, then activate stock slot, it loops on the safe strap screen.
Also note that you cannot get into recovery (or boot into any other slot) until you RSD back to stock.
Sent from my XT907 using xda premium
So I have a ~week old Tab which I havn't used, I played around with it last night and flashed CWM using Odin and that worked fine. I went and flashed the rooted stock firmware, and it seemed to have flashed fine, except now the tablet is in a reboot loop, it restarts about 3 times and then automatically boots into recovery. I've flashed all the ROMs I can find for the 10.1" and it happens with all of them, last resort is flashing stock recovery then taking it back to the place I bought it from and to play dumb, but I'd rather not. Anyone got any suggestions?
TL;DR Tablet stuck in reboot loop, won't boot ROM, recovery & download mode work fine.
You might have done it, but have you tried flashing back the stock firmware ?
try it and post back please
Agree, I had the same issues with a few of the custom roms. I went back to stock rom and have had no issues. My issue was flashing from a SD card. For some reason it would not work. I put the rom on the device in the download folder and flashed from there. Most roms did flash correctly but I found them to be of little use. Did you by chance do a backup before you started playing around with other roms? Hope so. Then at least you can recover back to factory condition.
Nitro_123 said:
You might have done it, but have you tried flashing back the stock firmware ?
try it and post back please
Click to expand...
Click to collapse
I have, I tried reinstalling my backup, as well as both of the stock roms here, although both times I didn't have a microsd card available, so I sideloaded both of the ROMs (which apparently worked fine, verified etc). I've just gone and bought one, so when I get home tonight I'm going to have another play around and see if I can get something working.
Brian D said:
Agree, I had the same issues with a few of the custom roms. I went back to stock rom and have had no issues. My issue was flashing from a SD card. For some reason it would not work. I put the rom on the device in the download folder and flashed from there. Most roms did flash correctly but I found them to be of little use. Did you by chance do a backup before you started playing around with other roms? Hope so. Then at least you can recover back to factory condition.
Click to expand...
Click to collapse
Interesting, I haven't tried that, I shall, thanks
I might also try flashing the ROM through Odin instead of a recovery.
I do believe that stock roms MUST be uploaded via ODIN. They cannot reside on the device. The stock rom is around 1.9gb (XAR-P5210UEUAMK1). So you will use that file (or whatever stock rom you wish to use). If you are loading one of the other roms developed here then you can put it on the device and load from there (via the recovery app CWM or TWRP)
Brian D said:
I do believe that stock roms MUST be uploaded via ODIN. They cannot reside on the device. The stock rom is around 1.9gb (XAR-P5210UEUAMK1). So you will use that file (or whatever stock rom you wish to use). If you are loading one of the other roms developed here then you can put it on the device and load from there (via the recovery app CWM or TWRP)
Click to expand...
Click to collapse
Oh, damn, really? That would explain quite a lot then, thanks, hopefully I'll be home in a couple hours and can report back
My bad I didn't make myself clear. Yes I meant flashing back a stock ROM via ODIN as that is the best way to restore it to stock. Thanks to @Brian D for pointing that out
Nitro_123 said:
My bad I didn't make myself clear. Yes I meant flashing back a stock ROM via ODIN as that is the best way to restore it to stock. Thanks to @Brian D for pointing that out
Click to expand...
Click to collapse
Haha thanks, I'm downloading a stock rom now, hopefully I'll be able to report back in about 30
Holy ****, thanks guys! Managed to get the stock ROM flashed with Odin, silly me for the not realising. Anyone know what would have caused the boot loop? I really don't want to run the stock rom with all the samsung crap (I guess I can root and remove everything)
I think what you did was called a dirty flash. You had bits and pieces of the original rom on the device when you tried to load another rom. The two mixed like vinegar and oil. You have to wipe your system clean before you can load a new flash. Before proceeding please do a backup of what you have right now. Load either CWM or TWRP and do the backup. My preference is TWRP. I like the look and feel of how it works.
I found the best instruction set to be http://forum.xda-developers.com/showpost.php?p=49715684&postcount=172. I had the same boot loop as you but when I followed these instructions I finally loaded the rom. But like I said, to me I gained nothing by using it. But this is me. After much reading I found that if I just delete bloatware then I should be ok. I used an app called bloatfree from the play store. Worked just great but one has to be careful about what one removes. That is why I always backup before doing anything. I must have had 20 backup files at one time. LOL
Good luck!
In the AOKP thread someone brought up switching slots and flashing to a different slot, and in my search for answers I found out that you can easily brick this phone by switching to an empty slot.
pcriz said:
Did you swap slots before you dirty flashed?
If you are in slot A and want to dirty flash to fix something I would recommend switching to slot B, flashing the ROM because it flashes back over slot A.. Then rebooting.
Click to expand...
Click to collapse
Can you explain the slot A & B stuff? If I want to dirty flash, I need to flash in slot B, rather than just flashing on top of the current ROM?
Like today, there's a new build out. I don't simply follow the instructions from post #1?
If updating a new AOKP build:
Flash ROM (GAPPS are included for now)
Flash TWRP Installer ZIP (Every time)
Reboot
Click to expand...
Click to collapse
Or has something changed, and the OP needs to be updated? I know gapps have to be flashed now as well, right?
Edit: Holy cow. I searched "TWRP slot a slot b" and first few results are about bricking the phone:
https://forum.xda-developers.com/pixel-xl/how-to/pixel-xl-bricked-switching-to-slot-b-t3520675
I keep forgetting that this isn't like normal a Nexus device. You had to absolutely be trying to hard brick one of those.
I also found this reddit thread: https://www.reddit.com/r/GooglePixel/comments/647k52/twrp_slot_a_b/
I rebooted to recovery and saw that it was in slot B currently. I don't remember switching slots. I went straight from stock to unlock bootloader, install TWRP, and flashed this ROM. So, should I switch to slot A to dirty flash? What would happen if I switched to slot A right now and rebooted?
Click to expand...
Click to collapse
I didn't want to clog up that thread with my questions, so I'm asking here.
There's a new build out for that ROM today. I'm currently on slot B. So if I want to flash the new build, I should boot into recovery, go to the Restart menu, select slot A, and then go through with flashing the ROM. Is that correct?
I spent the entirety of yesterday playing with my new Pixel XL and honestly, it's not nearly as easy to brick as people seem to claim. There are two bootloaders, one for each slot and you can just flip between slots. The only confusing thing is that when you flash a ROM, it flashes to the other slot and then tells your phone to switch to that slot next boot. Also, the recovery is now part of the boot image, so you have to flash TWRP every time you install a ROM or it will be overwritten (which is not a big deal since you can still just boot it through the bootloader and flash it if you forgot).
As a side note, because nobody I talked to seem to understand it yesterday, I figured it out myself: Every guide suggests wiping system before flashing the ROM, however this is wrong in the sense that it wipes the currently active slot, not the one the ROM will be flashed to, so what you need to do is using fastboot or TWRP, set the active slot to the one you plan on flashing the ROM to, do your wipe system (data is shared so it doesn't matter when you wipe it), then switch back to the other slot, reboot TWRP and then flash your ROM.
So, just so I'm straight, it should be:
If updating a new AOKP build:
Boot into recovery
Wipe system - which will wipe System on the current slot
Boot into other slot
Flash ROM & GAPPS - which will install ROM on the slot you are not currently in
Flash TWRP Installer ZIP (Every time)
Reboot
admiralspeedy said:
I spent the entirety of yesterday playing with my new Pixel XL and honestly, it's not nearly as easy to brick as people seem to claim. There are two bootloaders, one for each slot and you can just flip between slots. The only confusing thing is that when you flash a ROM, it flashes to the other slot and then tells your phone to switch to that slot next boot. Also, the recovery is now part of the boot image, so you have to flash TWRP every time you install a ROM or it will be overwritten (which is not a big deal since you can still just boot it through the bootloader and flash it if you forgot).
As a side note, because nobody I talked to seem to understand it yesterday, I figured it out myself: Every guide suggests wiping system before flashing the ROM, however this is wrong in the sense that it wipes the currently active slot, not the one the ROM will be flashed to, so what you need to do is using fastboot or TWRP, set the active slot to the one you plan on flashing the ROM to, do your wipe system (data is shared so it doesn't matter when you wipe it), then switch back to the other slot, reboot TWRP and then flash your ROM.
Click to expand...
Click to collapse
Custom roms wipe the system in the slot that it switches too. So you really don't need to wipe system. That being said, the new inactive slot will have your previous image left in it if you don't wipe system.
---------- Post added at 11:54 PM ---------- Previous post was at 11:52 PM ----------
jova33 said:
So, just so I'm straight, it should be:
If updating a new AOKP build:
Boot into recovery
Wipe system - which will wipe System on the current slot
Boot into other slot
Flash ROM & GAPPS - which will install ROM on the slot you are not currently in
Flash TWRP Installer ZIP (Every time)
Reboot
Click to expand...
Click to collapse
You never flash gapps and rom in the same TWRP session. Roms switch slots gapps don't. You flash rom and TWRP. Reboot into recovery, which puts you into the new slot, then flash gapps and boot system
admiralspeedy said:
I spent the entirety of yesterday playing with my new Pixel XL and honestly, it's not nearly as easy to brick as people seem to claim. There are two bootloaders, one for each slot and you can just flip between slots. The only confusing thing is that when you flash a ROM, it flashes to the other slot and then tells your phone to switch to that slot next boot. Also, the recovery is now part of the boot image, so you have to flash TWRP every time you install a ROM or it will be overwritten (which is not a big deal since you can still just boot it through the bootloader and flash it if you forgot).
As a side note, because nobody I talked to seem to understand it yesterday, I figured it out myself: Every guide suggests wiping system before flashing the ROM, however this is wrong in the sense that it wipes the currently active slot, not the one the ROM will be flashed to, so what you need to do is using fastboot or TWRP, set the active slot to the one you plan on flashing the ROM to, do your wipe system (data is shared so it doesn't matter when you wipe it), then switch back to the other slot, reboot TWRP and then flash your ROM.
Click to expand...
Click to collapse
We told you yesterday , you don't need to wipe system. And you can change slots with TWRP, don't have to use fastboot , just have to reboot to recovery or bootloader to make it official
Golf c said:
You never flash gapps and rom in the same TWRP session. Roms switch slots gapps don't. You flash rom and TWRP. Reboot into recovery, which puts you into the new slot, then flash gapps and boot system
Click to expand...
Click to collapse
Ok, thanks. Yeah, I was drunk last night and couldn't figure out why when I attempted to dirty flash it would boot, but none of the Google services would work.
And someone gave me a pretty good rundown in the AOKP thread:
pcriz said:
You don't have to wipe system unless you want to., not a requirement since most rom scripts (if not all for the pixel) wipe system anyway.
Boot in TWRP
Reboot TWRP to Inactive Slot
Flash ROM (for a clean flash simply factory reset before flashing rom)
Flash TWRP
Reboot to Recovery (makes inactive slot active)
Flash Gapps (They flash to active slot slot)
Click to expand...
Click to collapse
So if I rebooted TWRP to slot A right now, currently on slot B, it won't brick the phone?
Also, can you use slot A & slot B for dualboot? That's what I initially thought it was for, so I wasn't messing around with switching slots. Thought I could just dive right in and it'd be the same as my Nexus 6P.
jova33 said:
Ok, thanks. Yeah, I was drunk last night and couldn't figure out why when I attempted to dirty flash it would boot, but none of the Google services would work.
And someone gave me a pretty good rundown in the AOKP thread:
So if I rebooted TWRP to slot A right now, currently on slot B, it won't brick the phone?
Also, can you use slot A & slot B for dualboot? That's what I initially thought it was for, so I wasn't messing around with switching slots. Thought I could just dive right in and it'd be the same as my Nexus 6P.
Click to expand...
Click to collapse
Dual slots are for seamless updates. Nothing like previous devices. Once you understand the slots, it's easy. You can dual boot the same rom. But with one shared data partition it won't work very good with two different roms. As far as bricking, who knows. You always take a risk. As long as you pay attention to what your flashing I don't see a problem.
mac796 said:
We told you yesterday , you don't need to wipe system. And you can change slots with TWRP, don't have to use fastboot , just have to reboot to recovery or bootloader to make it official
Click to expand...
Click to collapse
Except I want to wipe system before I flash a ROM... Also, if you actually read my post that you quoted, I quite clearly said that you can change the slot with fastboot or TWRP.
---------- Post added at 08:20 PM ---------- Previous post was at 08:18 PM ----------
Golf c said:
Custom roms wipe the system in the slot that it switches too. So you really don't need to wipe system. That being said, the new inactive slot will have your previous image left in it if you don't
Click to expand...
Click to collapse
I was unaware of that. Is there any way to actually confirm that a ROM wipes systems first (it makes sense obviously, but I'm just curious)?
admiralspeedy said:
Except I want to wipe system before I flash a ROM... Also, if you actually read my post that you quoted, I quite clearly said that you can change the slot with fastboot or TWRP.
---------- Post added at 08:20 PM ---------- Previous post was at 08:18 PM ----------
I was unaware of that. Is there any way to actually confirm that a ROM wipes systems first (it makes sense obviously, but I'm just curious)?
Click to expand...
Click to collapse
Not really, if it didn't wipe the old image, I doubt if it would work very well.
Edit: I believe the TWRP log will tell you it wiped the system.
What happen if I want to flash the stock image (return to stock) If I am in a custom ROM..?? . DO I need to take any precautions (Slot A or B) before running flashall.bat ???.
Glsoto said:
What happen if I want to flash the stock image (return to stock) If I am in a custom ROM..?? . DO I need to take any precautions (Slot A or B) before running flashall.bat ???.
Click to expand...
Click to collapse
I do a factory reset on TWRP then go back to stock
Glsoto said:
What happen if I want to flash the stock image (return to stock) If I am in a custom ROM..?? . DO I need to take any precautions (Slot A or B) before running flashall.bat ???.
Click to expand...
Click to collapse
mac796 said:
I do a factory reset on TWRP then go back to stock
Click to expand...
Click to collapse
Hello,
I think you don't necessarily need to factory reset. Since system will be overwritten and userdata partition will be wiped anyway.
Also, just as a precaution... If you installed custom ROMs on both slots (intentionally or by mistake), i would flash stock firmware on slots a and b.
Cheers...
5.1 said:
Hello,
I think you don't necessarily need to factory reset. Since system will be overwritten and userdata partition will be wiped anyway.
Also, just as a precaution... If you installed custom ROMs on both slots (intentionally or by mistake), i would flash stock firmware on slots a and b.
Cheers...
Click to expand...
Click to collapse
Yes you do you will get system FC errors if you don't. That's been my experience so far. That's with the - w removed. If your doing it with the-w you probably don't have to factory reset
5.1 said:
Hello,
I think you don't necessarily need to factory reset. Since system will be overwritten and userdata partition will be wiped anyway.
Also, just as a precaution... If you installed custom ROMs on both slots (intentionally or by mistake), i would flash stock firmware on slots a and b.
Cheers...
Click to expand...
Click to collapse
Ok, thank you... I have a custom ROM only in one of my slots (SLOT B), so do you recommend me to install the stock firmaware in both slots. or just install the stock firmaware only in SLOT A.
If I have to installed in both slots, I order to do so , do I need to use the fastboot command to swtich slots after I installed in slot A, to installed in slot B.. ???
Thank you for your help
Glsoto said:
Ok, thank you... I have a custom ROM only in one of my slots (SLOT B), so do you recommend me to install the stock firmaware in both slots. or just install the stock firmaware only in SLOT A.
If I have to installed in both slots, I order to do so , do I need to use the fastboot command to swtich slots after I installed in slot A, to installed in slot B.. ???
Thank you for your help
Click to expand...
Click to collapse
Hello,
If you are sure only the slot b is modified, then flash on slot b. This way, both will be stock afterward.
Good luck...
5.1 said:
Hello,
If you are sure only the slot b is modified, then flash on slot b. This way, both will be stock afterward.
Good luck...
Click to expand...
Click to collapse
Is there any way to know what files do I have in each slot..??? or do i need to switch slots and boot from each one to see ..
Glsoto said:
Is there any way to know what files do I have in each slot..??? or do i need to switch slots and boot from each one to see ..
Click to expand...
Click to collapse
Hey,
I don't know a safe way to know what is on a or b except booting to system. I have stock NHG47K on a and PN on b (or the inverse). I use PN. Just for testing i booted on a. After this I had permissions issues on PN. So be careful...
Good luck...
From within TWRP _without_ rebooting of any kind can I flash the ROM first to A, and then switch some setting to flash ROM to B? so all my bases are covered?
New Slot a and slot b are confusing
Hi, I have nearly spent 10 hours of my time trying to figure out the slot a and slot b stuff.
I haven't flashed a custom ROM for past few years, I tried to flash custom rom but figured it out there's this new thing slot a and slot b which is really hard to understand. I have read the whole thread and understood a bit. can someone please educate me on this.. Thank you so much in advance..
Can i install TWRP recovery on both A and B slot permanently??
Is there a way to use only Slot A and ditch slot B?
Slot A and Slot B can have to different custom recoveries?
If i mess up slot A rom how can i switch back to slot B?
erica butson said:
Hi, I have nearly spent 10 hours of my time trying to figure out the slot a and slot b stuff.
I haven't flashed a custom ROM for past few years, I tried to flash custom rom but figured it out there's this new thing slot a and slot b which is really hard to understand. I have read the whole thread and understood a bit. can someone please educate me on this.. Thank you so much in advance..
Can i install TWRP recovery on both A and B slot permanently??
Is there a way to use only Slot A and ditch slot B?
Slot A and Slot B can have to different custom recoveries?
If i mess up slot A rom how can i switch back to slot B?
Click to expand...
Click to collapse
Here are several more guides and explanations on the A/B slots that might help you understand :
https://www.xda-developers.com/how-a-b-partitions-and-seamless-updates-affect-custom-development-on-xda/
https://www.droidwin.com/flash-roms-magisk-twrp-kernels-a-b-partition-devices/
https://www.droidwin.com/flash-files-a-b-partition-devices/