Slot A/B - Moto Z2 Force Questions & Answers

Hello Guys,
What is Slot A / B for?
is it possible to flash the rom in slot B?
Because,
I have a problem with my Z2 Force, the cell phone system is crashing out of nowhere, I have reinstalled the stock rom, I also installed LineageOS, but the problem persists.

danyfenton said:
Hello Guys,
What is Slot A / B for?
is it possible to flash the rom in slot B?
Because,
I have a problem with my Z2 Force, the cell phone system is crashing out of nowhere, I have reinstalled the stock rom, I also installed LineageOS, but the problem persists.
Click to expand...
Click to collapse
This is how a/b slots are supposed to work.
https://www.xda-developers.com/how-...ess-updates-affect-custom-development-on-xda/
But Moto isn't flashing a full system.img to slot b.
I'm not sure what that means for custom ROMs.
Sent from my ali using XDA Labs

sd_shadow said:
This is how a/b slots are supposed to work.
https://www.xda-developers.com/how-...ess-updates-affect-custom-development-on-xda/
But Moto isn't flashing a full system.img to slot b.
I'm not sure what that means for custom ROMs.
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
Thanks, I used the code to select Slot B, and flashed again, but I was unsuccessful, still crashing, and stopping applications.

danyfenton said:
Thanks, I used the code to select Slot B, and flashed again, but I was unsuccessful, still crashing, and stopping applications.
Click to expand...
Click to collapse
Did you get any errors when flashing?
Sent from my ali using XDA Labs

sd_shadow said:
Did you get any errors when flashing?
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
unfortunately not, I erased the entire system by TWRP, and flashed again, and without success, it keeps locking out of nowhere, the system stopping, and giving error in certain applications.
Ex: Interface, Config ...
or even the application I currently open.

Related

X crashes all processes upon startup

Hi Xda,
I was working on putting a custom ROM on my one x as a result of it being slow.
everything started out fine, bootloader was unlocked fairly easy, gaining perm root as well.
however after a couple of tries I haven't been able to get a custom rom working properly. it will start up the system, passed the startup, then as soon as the first start screen opens up, every possible process starts crashing. (the only really visible crash is com.android.phone, however as soon as I click "ok" it will pop-up again within a second)
I've done the following:
Remove lock,
gain root access,
install CWM
downloaded ROM and Gapps (put it on the SD card)
performed a full wipe (Dalvik Cache, factory Reset)
install ROM and Gapps.
after this the problems started occurring.
a few solutions i tried:
1. I've retried the above process and included the boot.img loading using fastboot, then clearing the cache again.
2. I've wiped all possible data using the "superwipescript"
3. tried a different ROM which gave me the exact same errors.
atm i'm getting desperate because I've run out of options.
Is there a workaround for this problem?
Thanks in Advance!
Have you flashed boot.img via fastboot?
Sent from my GT-N8000 using Tapatalk HD
this might be a silly question, but it's not an AT&T one x? there have been a few of those here who shouldn't be here.
if it isn't...then check your HBOOT version
csec said:
Have you flashed boot.img via fastboot?
Sent from my GT-N8000 using Tapatalk HD
Click to expand...
Click to collapse
yeah i've flashed the boot.img and then cleared the cache!
jeroen2303 said:
yeah i've flashed the boot.img and then cleared the cache!
Click to expand...
Click to collapse
Does your hboot meet the required version for the ROM You flashed ?
Sent from my GT-N8000 using Tapatalk HD
csec said:
Have you flashed boot.img via fastboot?
Sent from my GT-N8000 using Tapatalk HD
Click to expand...
Click to collapse
ace9988 said:
this might be a silly question, but it's not an AT&T one x? there have been a few of those here who shouldn't be here.
if it isn't...then check your HBOOT version
Click to expand...
Click to collapse
No i'm on the international one x (Dutch, T-Mobile)
my HBOOT Version is 1.39.0000
I've tried installing Paranoid Android 3.10 and 3.15 and ICJ422
Is that the correct version?
jeroen2303 said:
No i'm on the international one x (Dutch, T-Mobile)
my HBOOT Version is 1.39.0000
Is that the correct version?
Click to expand...
Click to collapse
Yes. You have the latest hboot.
You may wait for more expert replies.
Sent from my GT-N8000 using Tapatalk HD
csec said:
Yes. You have the latest hboot.
You may wait for more expert replies.
Sent from my GT-N8000 using Tapatalk HD
Click to expand...
Click to collapse
I've tried waiting with installing the Gapps till after the first boot but the same problem keeps occurring.
any other advice?
jeroen2303 said:
I've tried waiting with installing the Gapps till after the first boot but the same problem keeps occurring.
any other advice?
Click to expand...
Click to collapse
Reboot into recovery and under advanced, select fix permissions.
Sent from my GT-N8000 using Tapatalk HD
csec said:
Reboot into recovery and under advanced, select fix permissions.
Sent from my GT-N8000 using Tapatalk HD
Click to expand...
Click to collapse
tried but won't work!
Make a clean wipe manually twice
Factory reset
Wipe cache partition
Advanced - wipe dalvik cache
Mounts & storage - format cache, data, system
Then install the rom
Mr Hofs said:
Make a clean wipe manually twice
Factory reset
Wipe cache partition
Advanced - wipe dalvik cache
Mounts & storage - format cache, data, system
Then install the rom
Click to expand...
Click to collapse
I've tried the above but it gives the same exact error. as soon as the systems has started up it gives: "Unfortunately, the process com.android.phone has stopped" when i press ok there is a second error about messages but i'm not able to read this since the first message will pop up again.
should I start to get worried by now?
jeroen2303 said:
I've tried the above but it gives the same exact error. as soon as the systems has started up it gives: "Unfortunately, the process com.android.phone has stopped" when i press ok there is a second error about messages but i'm not able to read this since the first message will pop up again.
should I start to get worried by now?
Click to expand...
Click to collapse
Do you get this on all ROMs??
Try using a Sense ROM....
Sent from my HTC One X using xda app-developers app
Boot the phone without the simcard....
athulele said:
Do you get this on all ROMs??
Try using a Sense ROM....
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
I've tried using a Sense ROM without success. I Can't seem to get passed the HTC ONE logo.
as for the simcard, i've tried booting inserted and left out but none of the two work..
jeroen2303 said:
I've tried using a Sense ROM without success. I Can't seem to get passed the HTC ONE logo.
as for the simcard, i've tried booting inserted and left out but none of the two work..
Click to expand...
Click to collapse
Flash the boot.img from the sense ROM.zip.. and then fastboot erase cache...then it won't be stuck at HTC logo...
Which roms did your try??? :S
I was having the same problem on Paranoid Android... not all the time like you but 4-5 times a day... Changed to ICJ and everything is stable now! Also make sure you have flashed the proper gapps...
jeroen2303 said:
I've tried using a Sense ROM without success. I Can't seem to get passed the HTC ONE logo.
as for the simcard, i've tried booting inserted and left out but none of the two work..
Click to expand...
Click to collapse
I gave the phone a good hour and my phone seems to be working for now!
Thanks for all the help,
This is on a sense ROM!
Hmmm! Good to hear that m8!
vin4yak said:
Hmmm! Good to hear that m8!
Click to expand...
Click to collapse
felt only happy for a while, but back to problems now.
the ROM takes an hour to boot on average and won´t let me make any calls. besides the settings menu will crash as soon as I try to open anything.
I´m going to try another Sense based ROM now and will see what happens next!
jeroen2303 said:
felt only happy for a while, but back to problems now.
the ROM takes an hour to boot on average and won´t let me make any calls. besides the settings menu will crash as soon as I try to open anything.
I´m going to try another Sense based ROM now and will see what happens next!
Click to expand...
Click to collapse
Maybe this could help you: http://forum.xda-developers.com/showpost.php?p=40817031&postcount=42

[Q] N7 bootlooping on custom rom?

Okay, so I bought the n7 v2, went home, unlocked the boot loader, and rooted it. I've tried to flash versions of vanir I built my self, the betas that are posted here on the forums, and I also tried carbon ROM. Every time I flash a ROM, my device bootloops, so I just hold power + vol down to get to boot loader mode so I can boot into recovery. Any fix for this? I've tried flashing a stock IMG and re rooting to. No luck.
Bump
frap129 said:
Bump
Click to expand...
Click to collapse
Did you even wipe, and perform a factory reset before flashing a ROM?
Sent from my Nexus 7 using xda app-developers app
TheMrcool212 said:
Did you even wipe, and perform a factory reset before flashing a ROM?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yes, I wiped data, cache, and dalvik every single time.
Bump? Anyone?
try redownloading the rom and install, could of been a bad download
Sent from my Nexus 7 using xda app-developers app
shortyboy said:
try redownloading the rom and install, could of been a bad download
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
With four different ROMs, 2 transfered via adb and 2 from different download hosts, I doubt its a bad download.
frap129 said:
With four different ROMs, 2 transfered via adb and 2 from different download hosts, I doubt its a bad download.
Click to expand...
Click to collapse
you should've mentioned that in your original post. id try to reflash to complete stock and start all over. it seems like something you modified in the first rom you've flash isn't being removed from another flash,so going back to stock,you can be sure everything is working first.hope this helps
shortyboy said:
you should've mentioned that in your original post. id try to reflash to complete stock and start all over. it seems like something you modified in the first rom you've flash isn't being removed from another flash,so going back to stock,you can be sure everything is working first.hope this helps
Click to expand...
Click to collapse
I did mention that in the original post, as well as the fact that ive flashed stock a few times already.
Did you boot into the tablet after unlocking the bootloader but before rooting it? If not, try formatting data (not factory resetting) in recovery. I had the same experience and my sdcard never got populated with the default folders and files, remaining at 0MB. Apparently, symptoms of this problem include being unable to factory reset from recovery, being stuck on the splash screen, and having TWRP demand a password.
bananagranola said:
Did you boot into the tablet after unlocking the bootloader but before rooting it? If not, try formatting data (not factory resetting) in recovery. I had the same experience and my sdcard never got populated with the default folders and files, remaining at 0MB. Apparently, symptoms of this problem include being unable to factory reset from recovery, being stuck on the splash screen, and having TWRP demand a password.
Click to expand...
Click to collapse
I'll try that, maybe its because I restore my data after I wipe it that this happens. Another thing I've found is that after I flash and the restore my system partition that I backed up, su says that no subject binary was found, even though I've flashed it a million times. And some root apps don't work because it says no binary is found.

[Q] Please help, errors installing firmware

Hello,
I've tried to install new kitkat beta, however I have loads of issues running this, let me explain a little about what I did:
I had firmware b119, then I switched to B125, I've tried to Install ROM for Kitkatm But i wasnt able to achieved, then I downloaded the Beta kitkat firmware, but I had issues with google apps, then I've swichet to B125 again and when I've tried to add my google account this message pop up:
"couldnt sign in
Cant stablish a reliable connection to the server.
This could be a temporary problem or your Android device may not be provisioned for data services. If it continues call customer care"
THEN, I've swichet to B111 (official international firmware downloaded from Huawei web), however I still having this issue connecting to google accounts, so, I have no play store or google apps.
What could the issue be? How can I fix this? My data is working properly, I can use the browser, but not log into google account.
Im from Costa Rica and I also wasnt able to find the official firmware used here to return to the original state of the phone.
I've wanted to have ROM HYD52ROM V5] but seems I wasnt able to update it.
I´ve updated again to firmware b125 and I´m still having this same error.
I cannot log into Google accounts, all my back up information is there including my contacts.
Any idea how to fix this?
You could maybe try to flash latest gapps.
Sent from my HUAWEI P6-U06 using xda app-developers app
Sennincito said:
I´ve updated again to firmware b125 and I´m still having this same error.
I cannot log into Google accounts, all my back up information is there including my contacts.
Any idea how to fix this?
Click to expand...
Click to collapse
Flash hyd52ROM with full wipe data cust and system. Then wipe dalvik cache then flash gapps
Sent from my P6-U06 using xda app-developers app
husen4u said:
Flash hyd52ROM with full wipe data cust and system. Then wipe dalvik cache then flash gapps
Sent from my P6-U06 using xda app-developers app
Click to expand...
Click to collapse
I have installed kit kat, but i've tried to flash twrp, now phone turns on and now is not moving from Logo Huawei Ascend, I've tried to hard reset with Vol+ON but it goes into TWRP, when I reboot, it goes to logo screen again.
Now I cannot cdm because PC is not reading the phone and phone seems like have firmwares installed.
What I can I do? now im driving my self crazy
Sennincito said:
I have installed kit kat, but i've tried to flash twrp, now phone turns on and now is not moving from Logo Huawei Ascend, I've tried to hard reset with Vol+ON but it goes into TWRP, when I reboot, it goes to logo screen again.
Now I cannot cdm because PC is not reading the phone and phone seems like have firmwares installed.
What I can I do? now im driving my self crazy
Click to expand...
Click to collapse
So you can get into TWRP? Just wipe data, system and cust, and flash any stable rom from your sd
Sent from my P6-U06 using XDA Premium 4 mobile app
lootjelo said:
So you can get into TWRP? Just wipe data, system and cust, and flash any stable rom from your sd
Sent from my P6-U06 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
i did, i have tried installing LightningKat zip beta005.5 ROM and after rebooting it goes to Logo Ascend page and nothing happens...
Well seems like is not working at all.
How can I load an official firmware again? Please understand that phone from Logo is not moving, or just entering to TWRP but I cannot find where to load a new firmware.
Sennincito said:
i did, i have tried installing LightningKat zip beta005.5 ROM and after rebooting it goes to Logo Ascend page and nothing happens...
Click to expand...
Click to collapse
Try to install a ROM that's not KitKat?
Sent from my P6-U06 using XDA Premium 4 mobile app
lootjelo said:
Try to install a ROM that's not KitKat?
Sent from my P6-U06 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thank you for your replay..
Well... I was very upset doing this flashing, so, I was turning off my phone to take it into a store to repair it, but weird thing, phone rebooted and loaded a screen I have never seen before, google loading screen... then worked very well finally!!
I have been using the phone for 2 days and no complains!

how can I Update LineageOS via OTA?

help! when I try to update via OTA on the update menu of my phone, a message shows up saying that the phone can´t be rebooted in recovery mode, I am using TWRP 3.1.0 by shreps :crying:
behaapls said:
help! when I try to update via OTA on the update menu of my phone, a message shows up saying that the phone can´t be rebooted in recovery mode, I am using TWRP 3.1.0 by shreps :crying:
Click to expand...
Click to collapse
Same happens here. I recommend bro download from the official lineage and flash. Then just wipe cache and dalvik....
Sent from my Lenovo Vibe K5 Plus using XDA Labs
AmithNRG said:
Same happens here. I recommend bro download from the official lineage and flash. Then just wipe cache and dalvik....
Click to expand...
Click to collapse
doesn't this will erase data like app data?
gcmseb said:
doesn't this will erase data like app data?
Click to expand...
Click to collapse
No, app data will be there, after flashing you just need to wipe cache/dalvik (you will see an option after flashing it in twrp)
Sent from my Lenovo Vibe K5 Plus using XDA Labs

Question about : RemoveEncryptionOreo, RemoveVerity

Since i'm unlocked bootloader, rooted do I need to flash the above mentioned files??? reason I ask I logged into Zedge the other day just fine and then logged out, now when I try to log back in it tells me permission denied?? if I do have to flash is there anything special I need to do or can I just flash through TWRP or Flashify??c
blake .l said:
Since i'm unlocked bootloader, rooted do I need to flash the above mentioned files??? reason I ask I logged into Zedge the other day just fine and then logged out, now when I try to log back in it tells me permission denied?? if I do have to flash is there anything special I need to do or can I just flash through TWRP or Flashify??c
Click to expand...
Click to collapse
Neither of those have anything to do with any apps. If your using official TWRP then you can keep your /data partition encrypted. To remove encryption you will format which also erases everything in /data and internal SD. What your referring to changes the fstab to allow the choice to be encrypted, and was only necessary before TWRP was able to decrypt.
Sent from my Moto Z (2) using XDA Labs
skywalker-live said:
Neither of those have anything to do with any apps. If your using official TWRP then you can keep your /data partition encrypted. To remove encryption you will format which also erases everything in /data and internal SD. What your referring to changes the fstab to allow the choice to be encrypted, and was only necessary before TWRP was able to decrypt.
Sent from my Moto Z (2) using XDA Labs
Click to expand...
Click to collapse
Hello Skywalker! Can you tell me how I would go about disabling forced encryption for good?(at least until I choose to turn back on). I don't want my device to be encrypted whatsoever, so after I wipe data and flash lineage/stock, what else should I do to prevent the device from encrypting? Thanks!
itsttime206 said:
Hello Skywalker! Can you tell me how I would go about disabling forced encryption for good?(at least until I choose to turn back on). I don't want my device to be encrypted whatsoever, so after I wipe data and flash lineage/stock, what else should I do to prevent the device from encrypting? Thanks!
Click to expand...
Click to collapse
If you are dealing with lineage I would ask in that thread for help, or read through the twrp thread.
Sent from my Moto Z (2) using XDA Labs
skywalker-live said:
If you are dealing with lineage I would ask in that thread for help, or read through the twrp thread.
Sent from my Moto Z (2) using XDA Labs
Click to expand...
Click to collapse
Well, lineage OR stock. So for this case, stock. If I just flashed stock and have TWRP, how would I disable forced encryption?
itsttime206 said:
Well, lineage OR stock. So for this case, stock. If I just flashed stock and have TWRP, how would I disable forced encryption?
Click to expand...
Click to collapse
Again, read the twrp thread. It has the answer your looking for.
Sent from my Moto Z (2) using XDA Labs

Categories

Resources