OK.. I have NMJ32-F in Slot B and all is working fine when it's the active slot.
When I boot to Slot A It shows NMJ20D and attempts to update to NMJ32F. Download works fine and the update fails.
I also have No WiFi when booted from Slot A.
Everything is working on Slot B. Is there a method to clone Slot B TO Slot A??
I'd hate to lose anything as the phone is working perfectly at the moment!
TWRP installed and working. (That's how I choose Slots to boot from.) Phone is Rooted as well. (D'uh.)
Thanks!
Rick
Related
Hi all,
So - I followed this post - http://forum.xda-developers.com/ver...-to-downgrade-lollipop-5-0-to-kitkat-t3088571
I downgraded from Android 5.0
Now it shows Android 4.4.4
Build ANI2
Kernal 3.4.0
Everything went to plan. Towelroot worked, installed and ran supersu, busybox and safestrap 3.75.
I booted into safestrap - backed up my stock slot, created slot1 and tried to restore my backup to slot1. - after a fair amount of time and normal looking prompts it looks like it is finishing and then says - failed.
Boot it to slot1 just to confirm... it times out and boots to android recovery.
Well - deleted slot, created slot, downloaded Eclipse Rom http://forum.xda-developers.com/ver.../rom-eclipse-s5-tw-v1-0-12-8-14-real-t2967151
Flashed to slot 1
boot fails
Backedup sdcard to my pc
formated sdcard
Uninstalled/reinstalled busybox and safestrap
created backup and tried to restore to slot1...
Still fails.
Not sure what I am doing wrong. Seems like I am missing something easy... Any help would be appreciated.
Regards,
wantpizza said:
Hi all,
So - I followed this post - http://forum.xda-developers.com/ver...-to-downgrade-lollipop-5-0-to-kitkat-t3088571
I downgraded from Android 5.0
Now it shows Android 4.4.4
Build ANI2
Kernal 3.4.0
Everything went to plan. Towelroot worked, installed and ran supersu, busybox and safestrap 3.75.
I booted into safestrap - backed up my stock slot, created slot1 and tried to restore my backup to slot1. - after a fair amount of time and normal looking prompts it looks like it is finishing and then says - failed.
Boot it to slot1 just to confirm... it times out and boots to android recovery.
Well - deleted slot, created slot, downloaded Eclipse Rom http://forum.xda-developers.com/ver.../rom-eclipse-s5-tw-v1-0-12-8-14-real-t2967151
Flashed to slot 1
boot fails
Backedup sdcard to my pc
formated sdcard
Uninstalled/reinstalled busybox and safestrap
created backup and tried to restore to slot1...
Still fails.
Not sure what I am doing wrong. Seems like I am missing something easy... Any help would be appreciated.
Regards,
Click to expand...
Click to collapse
No need to restore your stock slot to one of your slots,the slot is safe. Just flash away.
It has been a while since I used a slot (Roms seem to work better on stock slot) but make sure you are creating a large enough slot to accomadate your ROM. Also, make sure you are using the slot compatible safestrap. If you aren't you will need to go into safestrap, uninstall recovery, go into settings, uninstall safestrap. Go into SuperSU, tell it to forget safestrap. Then install the correct safestrap.
Thanks Tulsadiver.
That is the same safestrap that I used but I will double check it.
I know I don't have to restore stock to slot1 but it would sure give me a warm and fuzzy feeling that things were working if that worked. I guess I am a little scared that something isn't right and flashing a rom to my stock slot could leave me without a phone for a bit if things don't go right.
Do I need to be on a newer firmware? Is the standard slot too small to even fit my stock backup? When I flash a rom to the slot - it completes without errors. But backing up my stock to slot1 trips an error just before completing...
I Can't Flash Any Rom In Slot B.Its Automatically Flashed Slot A.Then my device doesn't boot.:crying:
So, I am confused about the whole a/b partition for first time ROM flashing.....can someone hlep. Do we need to flash OOS on both slots first?
jamescable said:
So, I am confused about the whole a/b partition for first time ROM flashing.....can someone hlep. Do we need to flash OOS on both slots first?
Click to expand...
Click to collapse
No, if you are flashing OOS there is no reason to flash both slots. Just flash one slot and you are fine. When you flash a ROM it automatically flashes the opposite slot.
- So if you were running 907, in Slot A and wanted to update to 911. You would flash 911.
- Flash TWRP installer next. As the 911 file would replace everything including your recovery. Remember you are still on Slot A right now. 911 was just installed to Slot B.
- After installing TWRP, reboot to recovery. This time it will boot up to Slot B.
- Now install Magisk.
- Now Reboot to the OS.
Hopefully that clarifies things. The only reason people were flashing both slots, were for AOSP roms. Sometimes funny things happen when OOS was in one slot and AOSP was in another. Who knows if this will always be an issue or not. At the moment though, it's easier to just flash AOSP twice and not deal with any problems.
OhioYJ said:
No, if you are flashing OOS there is no reason to flash both slots. Just flash one slot and you are fine. When you flash a ROM it automatically flashes the opposite slot.
- So if you were running 907, in Slot A and wanted to update to 911. You would flash 911.
- Flash TWRP installer next. As the 911 file would replace everything including your recovery. Remember you are still on Slot A right now. 911 was just installed to Slot B.
- After installing TWRP, reboot to recovery. This time it will boot up to Slot B.
- Now install Magisk.
- Now Reboot to the OS.
Hopefully that clarifies things. The only reason people were flashing both slots, were for AOSP roms. Sometimes funny things happen when OOS was in one slot and AOSP was in another. Who knows if this will always be an issue or not. At the moment though, it's easier to just flash AOSP twice and not deal with any problems.
Click to expand...
Click to collapse
So, what you are saying is, one I run the conversion on the T-Mobile version to international, unlock the bootlaoder and install twrp, I can just wipe system, data, cache like normall and install havoc OS or RR?
So, I installed havoc, kernel, magisk to slot a...even magisk said current slot a, even twrp set I was on slot a....but, when I rebooted, booted back to twrp...but when I rebooted to slot b, havoc booted up.....I don't understand this
How are you installing this stuff? If TWRP says you are in Slot A, and you install a ROM, the ROM will be installed to the opposite slot. Kernels and such will be installed to the current slot. So if you were in Slot A and installed Havoc it would be installed to Slot B.
You should, install ROM, install TWRP, reboot to recovery so you will be on the correct slot with the new ROM, then install your kernel, GAPPs and so on.
So I flashed back to stock using the awesome helper script found on here. Fixed the serious battery problems I was having. So I decided to proceed with flashing the magisk root boot image to both slots, bypassing twrp. All well there, couldn't be happier. Slot B was active. I poked around with Macrodroid (hurray for root options available!) and enabled the root helper, it told me to reboot and I obliged. I was greeted with a 2 minute long boot, then a reboot into a yellow and blue recovery screen stating that my data was corrupt and had only two options, try to boot again, or wipe everything.
I knew better. So back to my PC I went, switched active slots, and voila! Slot A boots fine. First thing I did was disable the MacroDroid root helper, rebooted with baited breath and all was fine. I tried booting into Slot B and was greeted with the same issue from before. I'm up and running with Slot A no problems.
I'm wondering what the heck happened with MacroDroid that caused Slot B to bork over like that. I tried reflashing the magisk boot image to slot B again but no luck.
I'm down to be using slot A for the remainder of my PH1s life. Just wondering if there's anything I can do to fix slot B just in case I need it?
You could probably flash the stock system image via fastboot to system_b since you're on stock, that should fix things nicely.
As to what macrodroid did, it probably wrote to the system partition in some way, which is a huge issue on stock as it trips verity and causes, at best, the device to throw up a warning, kinda why magisk is systemless, as anything writing to system will change the dm_verity hashes, and that in turn generally causes what you saw, only fixable by flashing the image or rom you're using
JonTheConquerer said:
So I flashed back to stock using the awesome helper script found on here. Fixed the serious battery problems I was having. So I decided to proceed with flashing the magisk root boot image to both slots, bypassing twrp. All well there, couldn't be happier. Slot B was active. I poked around with Macrodroid (hurray for root options available!) and enabled the root helper, it told me to reboot and I obliged. I was greeted with a 2 minute long boot, then a reboot into a yellow and blue recovery screen stating that my data was corrupt and had only two options, try to boot again, or wipe everything.
I knew better. So back to my PC I went, switched active slots, and voila! Slot A boots fine. First thing I did was disable the MacroDroid root helper, rebooted with baited breath and all was fine. I tried booting into Slot B and was greeted with the same issue from before. I'm up and running with Slot A no problems.
I'm wondering what the heck happened with MacroDroid that caused Slot B to bork over like that. I tried reflashing the magisk boot image to slot B again but no luck.
I'm down to be using slot A for the remainder of my PH1s life. Just wondering if there's anything I can do to fix slot B just in case I need it?
Click to expand...
Click to collapse
I would download the current firmware
And use the flashall.bat that is with the firmware
https://www.essential.com/developer/current-builds
Sent from my mata using XDA Labs