[Completed] [Q] Moto X 4.4.2 rooted w/ locked bootloader, factory reset safe? - XDA Assist

Hi, I have a republic wireless moto x I just successfully rooted and updated to 4.4.2 from 4.2.2 with a locked bootloader with no write protection (wp)
Since I updated it to 4.4.2 I have this error that pops up that I can not resolve
"Unfortunately, the process com.motorola.process.system has stopped"
I googled several pages of several website results and several pages of google but can not find the solution.
Solutions found was to:
Safe Mode (I tried this first with no apps installed on non safemode and non system apps updated, didn't work and popped up even on safe mode)
Change date & time method (didn't work)
Wipe Cache (didn't work)
Wipe Cache & dalvik cache (didn't work)
I am debating about factory reset but unsure if it will make me lose my root because I have a locked bootloader (if that matters in anyway I am still new to this, and that my moto x is from republic wireless not like other carriers with unlocked bootloaders).
Please help me and discuss with me how I can get rid of that error. Or point me to the right path.

Do you have a Custom Recovery Installed ? If not, then that would be your first Step. There's a Moto X Link in my signature that will help you install one. Once that is done, you can do factory reset from inside the Recovery. But before you boot, make sure to flash SuperUser Zip File from the Recovery.

Perseus71 said:
Do you have a Custom Recovery Installed ? If not, then that would be your first Step. There's a Moto X Link in my signature that will help you install one. Once that is done, you can do factory reset from inside the Recovery. But before you boot, make sure to flash SuperUser Zip File from the Recovery.
Click to expand...
Click to collapse
Hello. Not sure how to answer this because I am still new to it.
I have the SafeStrap App, it says "State: Installed" above Install Recovery / Uninstall Recovery & "Safe System: Not Active" over Reboot to Recovery" version 3.65.
I do have a SafeStrap (TWRP) and have a backup but not sure if it is on 4.2.2 or 4.4.2.
If I did a recovery, which parts will it back up or all of it? Because I don't want that error to show up. It is driving me nuts.
Can you further assist me with what I replied before I do that recovery?

I see that you have already Opened another Thread on the Moto X forum.
Kindly Understand that the purpose of XDA Assist is to
svetius said:
The mission of XDA Assist is to provide basic help to those who have tried searching but can't find what they are looking for and need assistance. This is not a "helpdesk" providing technical assistance but more to point you in the correct direction with your problem. Perhaps you can't find posts on how to root your phone, install custom recovery or maybe you have questions about how to navigate and use features on the site.
Our XDA Assist team will give you links to threads/forums that are relevant to your problem. You may be pointed towards guides and instructions that can be quite complex, so you will still need to read carefully and be cautious before attempting to make software changes to your device. It is essential you are in the correct forum for your device model; what works for one can ruin another.
Click to expand...
Click to collapse
As you can see this is not the case for your question. You clearly do know where to post the question. That forum is the right place for your query and someone will help you if it can be salvaged.

Related

[Q] Xoom Installing Custom Recovery through Stock

Hello all! I have locked myself out of my Motorola Xoom. MZ604, US Wi-Fi Only. I am on a stock ROM. I am not rooted, or unlocked. I don't have Wi-Fi enabled currently, and Android Debugging Bridge is not enabled. I am trying to install CWM or some other custom recovery through the stock recovery so that I can access my files through AROMA. Currently, I have been unable to install any zip whatsoever though the Attached USB host drive.
The Xoom is recognizing the file contents of the USB drive, but when I go to install any zip it keeps ending at "Installation Aborted"
I have searched and searched for a way back into my Xoom. The only answer I found thus far is to do a factory reset through the Stock Recovery. I would at all costs like to avoid doing that. I never made a backup, and really don't want to lose what's on there.
Any help whatsoever is appreciated.
Hi,
Unfortunately a factory reset it definitely something good to try. As is possibly reflashing your stock firmware.
And you can't flash a custom recovery from the stock recovery, it won't work. And can you clarify what you mean by you looked yourself out? If you mean you forgot your pin for your security.... Usually a factory reset or fresh stock install are the only wants to get back up and running. That's the point of the security pin. So no one can access your data. So you must wipe to get around it.
I will have your thread moved to your device section, so the experts who own your device can assist, here...
> Motorola Xoom > Xoom Q&A, Help & Troubleshooting
Good luck!
Darth said:
Hi,
Unfortunately a factory reset it definitely something good to try. As is possibly reflashing your stock firmware.
And you can't flash a custom recovery from the stock recovery, it won't work. And can you clarify what you mean by you looked yourself out? If you mean you forgot your pin for your security.... Usually a factory reset or fresh stock install are the only wants to get back up and running. That's the point of the security pin. So no one can access your data. So you must wipe to get around it.
I will have your thread moved to your device section, so the experts who own your device can assist, here...
> Motorola Xoom > Xoom Q&A, Help & Troubleshooting
Good luck!
Click to expand...
Click to collapse
Thank you so much for your very quick reply. I did forget my pin, which is how I locked myself out. Although, it is very unlikely that I got my pin wrong, and I suspect there is a bug or something going on here.
I definitely don't want to lose my data which is why I'm not doing a factory reset at the moment. However, I was curious what is flashable through stock recovery? I got what I believed to be an OEM stock ROM but that wouldn't install either. Is there anything specific you or anyone here could recommend which I would be able to flash in stock recovery to get me a stock reinstall without losing my data?
Any and all help and replies are great appreciated!
Your thread will be moved to your device section for other opinions.... And no, any option I know of wipes data. Again, that's the point of the added security.
Xda Assist is here to help navigate the site, not for support. ?
Thanks for understanding.
Darth said:
Your thread will be moved to your device section for other opinions.... And no, any option I know of wipes data. Again, that's the point of the added security.
Xda Assist is here to help navigate the site, not for support. ?
Thanks for understanding.
Click to expand...
Click to collapse
OK, thanks. I thought I was replying in the device section. If not, how do I move this thread there?
Thanks again!
You should be able to use android device manager to create a new password/pin for any android device
Just google android device manager, sign in with your google account. Waut until the device is located, the click the lock icon, this will replace your current loclscreen with a new password of your choice
Sent from my HTC6525LVW using Tapatalk 2

[Completed] [Q] How to remove twrp and fully unroot LG G3 d-855?

I have rooted my LG G3 and tried flashing twrp (no idea if it worked, when booting to recovery the notification led just flashes red and blue...). I decided that I want my phone to be completely stock again (If thats possible..) and couldn't find info on this for G3 devices. I'm quite sure that my twrp flash attempt failed but I would like to remove any files that the installer might have placed on my phone when attempting to install it. I also need help in unrooting my device, I have heard that you can do so from SuperSU, but does that FULLY unroot my device? I am running Lollipop 5.0
Hello and thank you for using XDA Assist.
This thread here http://forum.xda-developers.com/showthread.php?t=2785089 should provide the information required to completely flash your device back to stock.
This is the only way to actually reset the device and completely remove any files you may have uploaded to the device while rooting and attempting to flash custom recovery.
This method will also wipe all internal storage. So please back up anything like picture, videos and files you would like to save.
Also make sure you select the appropriate firmware for your device.
If things are unclear I suggest you ask the individuals in that thread as those are the users who are experts in your device.
Good Luck!
No reply in 2 days Thread Closed.

[Completed] Galaxy S5 Active (SM-G870A) stuck in bootloop!

I don't really know why my phone is stuck in a bootloop to begin with. I've tried EVERYTHING I could possibly think of!
Here's What I've tried :
WipeData/Factory Reset and I also wiped Cache.
I tried to use ODIN to flash the original stock ROM to the device but the bootloader is locked so its impossible to flash any ROM to the devices (Even if it's official).
I tried to apply the Lollipop 5.0 update in recovery using a external SD card.
I tried using ADB sideload.
(Bonus points if you can give me away to unlock the bootloader! because i'll know what to do if it's unlocked.)
So...If anyone has suggestions, I'll happily take any!
Also Please! Leave links so I have quick access!
Hi,
I can't find a relevant thread on your device and issue, but you can ask for help here,
http://forum.xda-developers.com/android/help
Good luck!

Rooted and bricked without a custom recovery.

rooted bricked boost mobile moto G. 4.4.4. i messed up my phone while editing "build.prob" with es root file i believe and when i was done editing i clicked on the folder looking icon on the top right corner which i thought was enter/save but itwas something else that rearranged the letters after it booted i only got bootloader unlocked warning screen and a plain black screen after and thats it however i can also get to the the fastboot menu. so any way can i get my phone back with maybe just using adb and fastboot. i just rooted my phone like a week ago so never got to play around with it so i have alot to catch up with on terms and research dont worry i'll look up what you tell me to do rather than keep on asking how how and how. well guys hope you can help me thank you.
XDA Visitor said:
rooted bricked boost mobile moto G. 4.4.4. i messed up my phone while editing "build.prob" with es root file i believe and when i was done editing i clicked on the folder looking icon on the top right corner which i thought was enter/save but itwas something else that rearranged the letters after it booted i only got bootloader unlocked warning screen and a plain black screen after and thats it however i can also get to the the fastboot menu. so any way can i get my phone back with maybe just using adb and fastboot. i just rooted my phone like a week ago so never got to play around with it so i have alot to catch up with on terms and research dont worry i'll look up what you tell me to do rather than keep on asking how how and how. well guys hope you can help me thank you.
Click to expand...
Click to collapse
Hello, and thank you for using XDA Assist!
Quite possibly my easiest problem of the night.
Your bootloader is unlocked. So....flash custom recovery. One that can do adb as well (unless you Moto G also has an SD card slot, but if we are talking about the original 2013 model, then one won't be there).
Then, reboot into recovery. Make a backup. Pull the backup files to your PC (either by adb or MicroSD, if available). Extract the system backup file (is a tarball) in a Linux filesystem. Fix up your build.prop mistakes. Tar system back up, and bundle the backup as a second set to push back to your device. Restore that backup (need only be system partition). Profit.
Any further questions, can ask in the following thread (assuming you have the 2013/1st gen non-LTE version - otherwise reply here with variant details for further instructions):
> Moto G > Moto G Q&A, Help & Troubleshooting > [RC-FAQ] >> Frequently Asked Questions for Motorola Moto G [Updated : 2015/09/23]
Please note, you will need to register for an account in order to post there.
Hope this helps, and good luck!
joel.maxuel said:
Hello, and thank you for using XDA Assist!
Quite possibly my easiest problem of the night.
Your bootloader is unlocked. So....flash custom recovery. One that can do adb as well (unless you Moto G also has an SD card slot, but if we are talking about the original 2013 model, then one won't be there).
Then, reboot into recovery. Make a backup. Pull the backup files to your PC (either by adb or MicroSD, if available). Extract the system backup file (is a tarball) in a Linux filesystem. Fix up your build.prop mistakes. Tar system back up, and bundle the backup as a second set to push back to your device. Restore that backup (need only be system partition). Profit.
Any further questions, can ask in the following thread (assuming you have the 2013/1st gen non-LTE version - otherwise reply here with variant details for further instructions):
> Moto G > Moto G Q&A, Help & Troubleshooting > [RC-FAQ] >> Frequently Asked Questions for Motorola Moto G [Updated : 2015/09/23]
Please note, you will need to register for an account in order to post there.
Hope this helps, and good luck!
Click to expand...
Click to collapse
im sorry man i shouldve updated and listed that i have usb debugging off -_- i was trying a stock fastboot method but ended up putting 4.3 or 4.4 instead without realizing so now its in a bootlooop still access to stock recovery tho. and so i was going to fastboot the 4.4.4 download from file factory but its down due to maintenance. so on to motorolla website i go and what ya know "cant unarchive". any ideas man? its a 45 dollar phone couldve easily replace it but something about leaving it as paper weight that will bug me forever haha plus lets not forget the satisfaction of solving the problem haha. and i have yet to read up on custom recovery which i will do if you believe it'll work. thanks for your reply man
jasj0410 said:
im sorry man i shouldve updated and listed that i have usb debugging off -_- i was trying a stock fastboot method but ended up putting 4.3 or 4.4 instead without realizing so now its in a bootlooop still access to stock recovery tho. and so i was going to fastboot the 4.4.4 download from file factory but its down due to maintenance. so on to motorolla website i go and what ya know "cant unarchive". any ideas man? its a 45 dollar phone couldve easily replace it but something about leaving it as paper weight that will bug me forever haha plus lets not forget the satisfaction of solving the problem haha. and i have yet to read up on custom recovery which i will do if you believe it'll work. thanks for your reply man
Click to expand...
Click to collapse
No problem.
USB debugging being off is only a consequence if planning to ADB in from system. Recovery has it's own rules.
Not sure about the "cannot unarchive" message, but if you can get the stock ROM, that's a viable option as well.
joel.maxuel said:
No problem.
USB debugging being off is only a consequence if planning to ADB in from system. Recovery has it's own rules.
Not sure about the "cannot unarchive" message, but if you can get the stock ROM, that's a viable option as well.
Click to expand...
Click to collapse
no luck with installing Stock Rom thru Custom Recovery im using twrp. suddenly my terminal wont let me fastboot the zip file because of
"unknown partition 'Rom.zip'
error: cannont determine image filename for 'Rom.zip'
and if it helps i tried using stock recovery with this method (installed. 4.4):
androidforumsDOTcom/threads/cdma-boostmobile-only-guide-on-returning-to-stocDOT.826108/
and adb works when im on custom recovery if that helps out
and i never got to do the back up build.prop method because i had already done the first stock recovery method which i feel mightve messed things up. thanks for your replies man it really means alot
jasj0410 said:
no luck with installing Stock Rom thru Custom Recovery im using twrp. suddenly my terminal wont let me fastboot the zip file because of
"unknown partition 'Rom.zip'
error: cannont determine image filename for 'Rom.zip'
and if it helps i tried using stock recovery with this method (installed. 4.4):
androidforumsDOTcom/threads/cdma-boostmobile-only-guide-on-returning-to-stocDOT.826108/
and adb works when im on custom recovery if that helps out
and i never got to do the back up build.prop method because i had already done the first stock recovery method which i feel mightve messed things up. thanks for your replies man it really means alot
Click to expand...
Click to collapse
Hello,
Fastboot is unable to flash zips unfortunately. That's the recoveries job.
If you can find fastboot images of stock, you can flash back that way.
Especially at this point, I would urge you to take advantage of the help thread I mentioned earlier. They know more about your device (particularly what's available and what not) they I would.
Hope this helps!

Stuck in TWRP (Recovery)

Hello everyone, I hope I'm writing in the right section.
I'll go straight to the issue: after finally deciding to install a custom rom on my device (HUAWEI GX8), i decided to opt for this one: https://forum.xda-developers.com/moto-g4-plus/development/rom-aospextended-rom-v3-0-t3537792
The first problem i had to face was the "ERROR:7" (so the rom seemed to be made for a different phone than mine) that occured while installing the rom in the twrp, but being that the rom was specifically made for my phone I followed this guide: https://www.youtube.com/watch?v=wed03948gcg and fixed the issue, resulting in a perfect installation... or so I thought.
After rebooting, the phone didn't start the os but was stuck in the twrp (I tried rebooting multiple times and in different ways of course).
Being that I had made a backup before installing the new rom, I decided to restore that backup from the twrp... but still the phone is stuck in the twrp and I don't know what to do :crying:
I hope somebody can help me because I'm starting to panicking.
Cheers in advance.
PS: I'm a complete newb so this was the first time I installed a custom rom, I tried searching for this problem online but couldn't find a solution that fitted me. I hope I won't ask too many stupid questions.
SlimeAndroid said:
Hello everyone, I hope I'm writing in the right section.
I'll go straight to the issue: after finally deciding to install a custom rom on my device (HUAWEI GX8), i decided to opt for this one: https://forum.xda-developers.com/moto-g4-plus/development/rom-aospextended-rom-v3-0-t3537792
The first problem i had to face was the "ERROR:7" (so the rom seemed to be made for a different phone than mine) that occured while installing the rom in the twrp, but being that the rom was specifically made for my phone I followed this guide: https://www.youtube.com/watch?v=wed03948gcg and fixed the issue, resulting in a perfect installation... or so I thought.
After rebooting, the phone didn't start the os but was stuck in the twrp (I tried rebooting multiple times and in different ways of course).
Being that I had made a backup before installing the new rom, I decided to restore that backup from the twrp... but still the phone is stuck in the twrp and I don't know what to do :crying:
I hope somebody can help me because I'm starting to panicking.
Cheers in advance.
PS: I'm a complete newb so this was the first time I installed a custom rom, I tried searching for this problem online but couldn't find a solution that fitted me. I hope I won't ask too many stupid questions.
Click to expand...
Click to collapse
The ROM that you flashed was NOT made specifically for your device, you have HUAWEI GX8, the ROM was made for Moto G4 Plus. You would have know this if you had looked at the forum it was posted in. It was posted in in the Moto G4 forum, not in a Huawei forum.
The "fix" that you used didn't help.it successfully flash, it only help you "force" the ROM to flash. You bypassed a safety measure that was designed to keep you from flashing the wrong thing, now you're dealing with the results of forcing it to flash on a device it wasn't meant for.
Learn to pay attention to what you are reading.
You need to flash your stock firmware to fix this.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
The ROM that you flashed was NOT made specifically for your device, you have HUAWEI GX8, the ROM was made for Moto G4 Plus. You would have know this if you had looked at the forum it was posted in. It was posted in in the Moto G4 forum, not in a Huawei forum.
Learn to pay attention to what you are reading.
You need to flash your stock firmware to fix this.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
I'm sorry I may have linked the wrong page, either way on the website of the rom I downloaded the right thing, I'm sure about it because I checked it multiple times (the error I made in writing the post may be cause by me panicking, sorry :crying: ).
While waiting for answers I installed a different twrp and it WORKS! I'm so happy I could cry. Thank you nonetheless for your help (Still dunno what the problem was though xD)
@SlimeAndroid as you installed ROM of different phone, it might not get installed as ROM zip contains script for Mobile verification.
I assume you had wiped /system and after installation of wrong ROM you rebooted your phone without reading if TWRP said you don't have any OS installed or what. (That means you have ran without any OS, that may be reason why you stuck with TWRP.)
But after Restoring Backup of Working ROM, it should boot your device, but it doesn't.
We (on G4 plus) have faced issue: when phone start, it always goes to TWRP/recovery instead of booting to system.
Are you facing similar ?
Solution for this problem was to clear bootloader data, by using fastboot commands (i assume you know how to do, otherwise ask for better explanation )
Run this two commands from Comand Prompt
-> fastboot oem fb_mode_set
-> fastboot oem fb_mode_clear
This worked for us. You can try, if doesn't work then flash Stock ROM.
____Mdd said:
@SlimeAndroid as you installed ROM of different phone, it might not get installed as ROM zip contains script for Mobile verification.
I assume you had wiped /system and after installation of wrong ROM you rebooted your phone without reading if TWRP said you don't have any OS installed or what. (That means you have ran without any OS, that may be reason why you stuck with TWRP.)
But after Restoring Backup of Working ROM, it should boot your device, but it doesn't.
We (on G4 plus) have faced issue: when phone start, it always goes to TWRP/recovery instead of booting to system.
Are you facing similar ?
Solution for this problem was to clear bootloader data, by using fastboot commands (i assume you know how to do, otherwise ask for better explanation )
Run this two commands from Comand Prompt
-> fastboot oem fb_mode_set
-> fastboot oem fb_mode_clear
This worked for us. You can try, if doesn't work then flash Stock ROM.
Click to expand...
Click to collapse
If you read the post above yours, you'll see they solved the issue.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
You always have to make sure the download is for your model of phone(settings -about) and always make sure the download has properly downloaded and I use md5 checksum as this verifies the download is not courupt.
Sent from my iPhone using Tapatalk

Categories

Resources