Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,769,298 Members 39,630 Now Online
XDA Developers Android and Mobile Development Forum

[Q] Rooted 4.4.2 with locked bootloader factory reset safe?

Tip us?
 
androiddoglover6969
Old
#1  
Member - OP
Thanks Meter 1
Posts: 57
Join Date: Oct 2013
Location [Q] Rooted 4.4.2 with locked bootloader factory reset safe?

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.
 
samwathegreat
Old
#2  
samwathegreat's Avatar
Senior Member
Thanks Meter 1134
Posts: 1,540
Join Date: Apr 2010

 
DONATE TO ME
Quote:
Originally Posted by androiddoglover6969 View Post
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.

You shouldn't have done it. You obviously didn't read or follow any of the guides here or you would have known better.

There was ONE (very tricky and convoluted) way of retaining root and it involves SafeStrap.

Sorry to say - there will likely be no root in your future.


A factory reset will most likely not help. You will have to download the 4.4.2 SBF and re-flash the entire stock rom.

There's a guide here: http://forum.xda-developers.com/moto...using-t2446515

^ This is the only way to get your phone back to being usable again. MAKE SURE you do NOT try to flash anything but 4.4.2. Flashing a prior version will likely permanently brick your phone.



After this process, the ONLY way you're going to obtain ROOT is to unlock your BL.


I hate to hear this happened to you, but its posted -all over- this forum that you cannot take the 4.4.2 OTA if you are rooted on a previous version. If you had followed the guide, and used Safestrap, you would be OK.....but now its too late. Once you've flashed the 4.4.2 OTA, it updates the bootloader, patching all of the exploits we used previously. Game Over.


Good Luck
The Following User Says Thank You to samwathegreat For This Useful Post: [ Click to Expand ]
 
androiddoglover6969
Old
#3  
Member - OP
Thanks Meter 1
Posts: 57
Join Date: Oct 2013
Quote:
Originally Posted by samwathegreat View Post
You shouldn't have done it. You obviously didn't read or follow any of the guides here or you would have known better.

There was ONE (very tricky and convoluted) way of retaining root and it involves SafeStrap.

Sorry to say - there will likely be no root in your future.


A factory reset will most likely not help. You will have to download the 4.4.2 SBF and re-flash the entire stock rom.

There's a guide here: http://forum.xda-developers.com/moto...using-t2446515

^ This is the only way to get your phone back to being usable again. MAKE SURE you do NOT try to flash anything but 4.4.2. Flashing a prior version will likely permanently brick your phone.



After this process, the ONLY way you're going to obtain ROOT is to unlock your BL.


I hate to hear this happened to you, but its posted -all over- this forum that you cannot take the 4.4.2 OTA if you are rooted on a previous version. If you had followed the guide, and used Safestrap, you would be OK.....but now its too late. Once you've flashed the 4.4.2 OTA, it updates the bootloader, patching all of the exploits we used previously. Game Over.


Good Luck
I did not have a root before 4.4.2. And I did not take the 4.4.2 OTA. I did follow the guide and have used Safestrap and still have it. What do you mean flash the 4.4.2 OTA? You mean installing it through the update notification? Well I didn't do that if that is what you meant. I flashed through the using the guide to get me no WP, root, and 4.4.2. So am I still doing it wrong?
 
samwathegreat
Old
(Last edited by samwathegreat; 30th May 2014 at 04:00 PM.)
#4  
samwathegreat's Avatar
Senior Member
Thanks Meter 1134
Posts: 1,540
Join Date: Apr 2010

 
DONATE TO ME
Quote:
Originally Posted by androiddoglover6969 View Post
I did not have a root before 4.4.2. And I did not take the 4.4.2 OTA. I did follow the guide and have used Safestrap and still have it. What do you mean flash the 4.4.2 OTA? You mean installing it through the update notification? Well I didn't do that if that is what you meant. I flashed through the using the guide to get me no WP, root, and 4.4.2. So am I still doing it wrong?
Sorry for the confusion...

Hmm...you didn't mention safestrap in OP - just that you "successfully rooted and updated to 4.4.2 from 4.2.2"

OK so if you followed the guide exactly your bootloader should still be on the JellyBean bootloader.

Assuming you followed the guide, you can start over. If you're ABSOLUTELY SURE you didn't update to the 4.4.2 bootloader, then I suggest starting from scratch.

Use RSD Lite to restore the 4.2.2 (JellyBean) rom (Again, you've been warned. If theres any possibility you flashed the 4.4.2 bootloader last time, this WILL brick your phone) Also, be careful to NOT flash the 4.4.2 ROM, or you will NOT be able to root as this patches the exploit.

Just follow the guide step-by-step: http://forum.xda-developers.com/moto...kat-4-t2738233

The first step is to restore back the 4.2.2 stock rom, so this is where you should start. Don't forget to re-install safestrap and MotoWpNoMo as described.



Please let us know how it works out.

samwathegreat
 
androiddoglover6969
Old
#5  
Member - OP
Thanks Meter 1
Posts: 57
Join Date: Oct 2013
Quote:
Originally Posted by samwathegreat View Post
Sorry for the confusion...

Hmm...you didn't mention safestrap in OP - just that you "successfully rooted and updated to 4.4.2 from 4.2.2"

OK so if you followed the guide exactly your bootloader should still be on the JellyBean bootloader.

Assuming you followed the guide, you can start over. If you're ABSOLUTELY SURE you didn't update to the 4.4.2 bootloader, then I suggest starting from scratch.

Use RSD Lite to restore the 4.2.2 (JellyBean) rom (Again, you've been warned. If theres any possibility you flashed the 4.4.2 bootloader last time, this WILL brick your phone) Also, be careful to NOT flash the 4.4.2 ROM, or you will NOT be able to root as this patches the exploit.

Just follow the guide step-by-step: http://forum.xda-developers.com/moto...kat-4-t2738233

The first step is to restore back the 4.2.2 stock rom, so this is where you should start. Don't forget to re-install safestrap and MotoWpNoMo as described.



Please let us know how it works out.

samwathegreat
Aslo, before I start to do the RSD Lite to restore the 4.2.2. Is there any other way how I can identify what is causing that error "com.motorola.process.system"? And isolate and get rid of that problem somehow or finding that stock app and preventing it from doing that?
 
samwathegreat
Old
(Last edited by samwathegreat; 30th May 2014 at 04:20 PM.)
#6  
samwathegreat's Avatar
Senior Member
Thanks Meter 1134
Posts: 1,540
Join Date: Apr 2010

 
DONATE TO ME
Quote:
Originally Posted by androiddoglover6969 View Post
Aslo, before I start to do the RSD Lite to restore the 4.2.2. Is there any other way how I can identify what is causing that error "com.motorola.process.system"? And isolate and get rid of that problem somehow or finding that stock app and preventing it from doing that?
Its extremely difficult to know why you are getting the error, but if you RSD Lite and start over, it will fix this issue.

Far too many people are running safestrap and not receiving the error. Likely there is a file on your device corrupted somewhere. RSD Lite will fix it as it completely restores the all of the partitions.

Just go -slow- step-by-step, and post here if you get confused or have questions. We will get your phone back to normal...


On another note....if you have $45 laying around, I highly suggest you email the gentleman from China. Once unlocked, you won't have to go through this long drawn-out process. You simply SBF back to stock, fastboot flash TWRP, and you're done. TWRP will install su-installer for you.

Your choice. The BL unlock method is best because you have permanent access and can never lose root.

Safestrap method will work as well, but you have to be very careful to not accept any new OTAs until the devs find a solution and post it here.


Good Luck.
The Following User Says Thank You to samwathegreat For This Useful Post: [ Click to Expand ]
 
androiddoglover6969
Old
#7  
Member - OP
Thanks Meter 1
Posts: 57
Join Date: Oct 2013
Quote:
Originally Posted by samwathegreat View Post
Its extremely difficult to know why you are getting the error, but if you RSD Lite and start over, it will fix this issue.

Far too many people are running safestrap and not receiving the error. Likely there is a file on your device corrupted somewhere. RSD Lite will fix it as it completely restores the all of the partitions.

Just go -slow- step-by-step, and post here if you get confused or have questions. We will get your phone back to normal...


On another note....if you have $45 laying around, I highly suggest you email the gentleman from China. Once unlocked, you won't have to go through this long drawn-out process. You simply SBF back to stock, fastboot flash TWRP, and you're done. TWRP will install su-installer for you.

Your choice. The BL unlock method is best because you have permanent access and can never lose root.

Safestrap method will work as well, but you have to be very careful to not accept any new OTAs until the devs find a solution and post it here.


Good Luck.
Woops I responded to another post but I am going to expect my bootloader code.

What is the first step from all of this that I should do?

1. SBF = what exactly? Hitting the factory reset button?
2. Fastboot Flash TWRP ? So after SBF. Fastboot Flash TWRP is done in AP Fastboot screen? Stock Recovery Screen? Or what screen exactly?
3. Did the guide I do didn't safestrap (twrp?) installed the su-installer for me as well right? Just wondering.
 
samwathegreat
Old
(Last edited by samwathegreat; 31st May 2014 at 10:01 PM.)
#8  
samwathegreat's Avatar
Senior Member
Thanks Meter 1134
Posts: 1,540
Join Date: Apr 2010

 
DONATE TO ME
Quote:
Originally Posted by androiddoglover6969 View Post
Woops I responded to another post but I am going to expect my bootloader code.

What is the first step from all of this that I should do?

1. SBF = what exactly? Hitting the factory reset button?
2. Fastboot Flash TWRP ? So after SBF. Fastboot Flash TWRP is done in AP Fastboot screen? Stock Recovery Screen? Or what screen exactly?
3. Did the guide I do didn't safestrap (twrp?) installed the su-installer for me as well right? Just wondering.
1.)

You can find the sbf files (stock rom) here: http://sbf.droid-developers.org/phone.php?device=0

Download the correct file for your carrier and try to flash with RSD lite.

You can find a great guide here: http://forum.xda-developers.com/moto...using-t2446515

PAY CLOSE ATTENTION TO STEP 4 - editing the xml file

If for some reason that doesn't work, let us know what carrier you are on and we can help you with manual flashing commands for your specific carrier.

Basically, an SBF is a complete STOCK image of the original filesystem (all partitions). By SBFing, you will be 100% back to factory stock. This method (SBFing) will actually fix a corrupted filesystem.

A "factory reset" does NOT do this. I highly suggest you do the SBF back to stock, and not try just reseting. If there is corruption, reset won't fix it.

Don't bother setting up any apps yet or setting up the phone. Wait until you complete the entire process.

2.
Yes! You'll flash TWRP from the "AP Fastboot" screen (bootloader).

UNLOCK YOUR BOOTLOADER FIRST. Otherwise you won't be able to flash TWRP custom recovery.

Now unplug the USB cord, and power off your device. Hold down the VOL DOWN button, and power back on. You will now be in bootloader (fastboot) mode. Plug the USB back into the phone now.

You must have "mfastboot" downloaded. You'll type:

mfastboot flash recovery twrp_file_you_downloaded.img (obviously replace with the actual filename)

You can find complete instructions here: http://forum.xda-developers.com/moto...droid-t2534850

P.S. If the download link for TWRP in the original post does not work, look near the end of the thread. Someone else re-uploaded it.

3.
Its entirely possible that something went afoul during your flashing process. I doubt the guide is to blame, because nearly everyone reported success. Sometimes things just go wrong...?



Good Luck.
The Following User Says Thank You to samwathegreat For This Useful Post: [ Click to Expand ]
 
androiddoglover6969
Old
#9  
Member - OP
Thanks Meter 1
Posts: 57
Join Date: Oct 2013
Quote:
Originally Posted by samwathegreat View Post
1.)

You can find the sbf files (stock rom) here: http://sbf.droid-developers.org/phone.php?device=0

Download the correct file for your carrier and try to flash with RSD lite.

You can find a great guide here: http://forum.xda-developers.com/moto...using-t2446515

PAY CLOSE ATTENTION TO STEP 4 - editing the xml file

If for some reason that doesn't work, let us know what carrier you are on and we can help you with manual flashing commands for your specific carrier.

Basically, an SBF is a complete STOCK image of the original filesystem (all partitions). By SBFing, you will be 100% back to factory stock. This method (SBFing) will actually fix a corrupted filesystem.

A "factory reset" does NOT do this. I highly suggest you do the SBF back to stock, and not try just reseting. If there is corruption, reset won't fix it.

2.
Yes! You'll flash TWRP from the "AP Fastboot" screen (bootloader). You must have "mfastboot" downloaded. You'll type:

mfastboot flash recovery twrp_file_you_downloaded.img (obviously replace with the actual filename)

You can find complete instructions here: http://forum.xda-developers.com/moto...droid-t2534850

P.S. If the download link for TWRP in the original post does not work, look near the end of the thread. Someone else re-uploaded it.

3.
Its entirely possible that something went afoul during your flashing process. I doubt the guide is to blame, because nearly everyone reported success. Sometimes things just go wrong...?



Good Luck.

On step 1. It is republic wireless 4.4.2 that I should download right. Correct me if I'm wrong.

Also is there RSDlite for mac or similar software? I tried to google it and xda'd it but I don't think there is. Or any other way to flash it into it.
 
samwathegreat
Old
(Last edited by samwathegreat; 31st May 2014 at 12:37 AM.)
#10  
samwathegreat's Avatar
Senior Member
Thanks Meter 1134
Posts: 1,540
Join Date: Apr 2010

 
DONATE TO ME
Quote:
Originally Posted by androiddoglover6969 View Post
On step 1. It is republic wireless 4.4.2 that I should download right. Correct me if I'm wrong.

Also is there RSDlite for mac or similar software? I tried to google it and xda'd it but I don't think there is. Or any other way to flash it into it.
If you have already received your code, yes, you should flash republic 4.4.2

If you haven't...just wait until you have it for sure. Once you flash 4.4.2 theres no going back. As long as you get unlock code, this is no problem....you'll be able to root regardless.

But, if for any reason he doesn't have your code (unlikely), you'll never be able to root once on 4.4.2....

As of right now (If I understand you completely), since you followed the safestrap guide, you SHOULD be on the jellybean bootloader, so the steps would be different if you didn't have an unlock code (and wanted to retain root).


Don't worry about any of this until we know for sure if you can get unlocked. In the unlikely event you don't get a code, post back here and I will step you through it.

Otherwise (if you get code), yes, start by using RSD Lite to flash the Republic Wireless 4.4.2 SFB per my previous instructions.


EDIT:

Just read the part about being on a MAC. AFAIK, there is no RSD Lite for Mac. We will have to go another route, unless you want to install windows inside a virtual machine....The dev that created the Mac Tooklit sold his X, and its no longer supported.

We will just do manual flashing...make sure you downloaded the "mfastboot" and followed all instructions on the RSD Lite thread I linked, EXCEPT follow the "Manual Flashing" instructions instead.

Extract the Republic Wireless SBF zip file Put the contents in to the same folder where fastboot and mfastboot are located. Here are the commands you will type after booting your X Into bootloader (Fastboot mode):

***Notice that mfastboot is used to flash the system.img. DONT try to use regular fastboot. Just type these commands one at a time.

fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem config carrier sprint ***be sure to type sprint. RW is a sprint MVNO, and I checked the xml file and this is the correct command for the Republic Wireless rom.
fastboot oem fb_mode_clear

Now reboot. Expect it to take a little longer than normal for the first boot-up. Congrats! You're now on 4.4.2 and your corruption issue will be a thing of the past.

Now Complete steps 2 & 3

The Following User Says Thank You to samwathegreat For This Useful Post: [ Click to Expand ]
Tags
com.motorola.process.system, moto x, republicwireless
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes