[Q] HELP! Can't root after using MotoWPNoMo - Moto X Q&A

Okay all... I had 4.2.2 rooted, write protection off. I tried rooting up to 4.4, didn't go well so I flashed fresh 4.2.2, no root.
Well, I lost root and I'm not sure how to get it back. I've searched the forums for about 3 hours to no avail....
Any help or pointing me in the right direction would be greatly appreciated!

byrdmang2 said:
Okay all... I had 4.2.2 rooted, write protection off. I tried rooting up to 4.4, didn't go well so I flashed fresh 4.2.2, no root.
Well, I lost root and I'm not sure how to get it back. I've searched the forums for about 3 hours to no avail....
Any help or pointing me in the right direction would be greatly appreciated!
Click to expand...
Click to collapse
Start Rant
There is no way you searched the forums for 3 hours the 5th Thread in the Original Android Development is RockMyMoto which is the root for 4.2.2. Also a quick Google Search of Moto X 4.2.2 Root would of given you many guides..
End Rant
Here is the link hope it helps.
http://forum.xda-developers.com/showthread.php?t=2509590
and if you want to root 4.4 check out this guide.
http://forum.xda-developers.com/showthread.php?t=2603358

dray_jr said:
Start Rant
There is no way you searched the forums for 3 hours the 5th Thread in the Original Android Development is RockMyMoto which is the root for 4.2.2. Also a quick Google Search of Moto X 4.2.2 Root would of given you many guides..
End Rant
Here is the link hope it helps.
http://forum.xda-developers.com/showthread.php?t=2509590
and if you want to root 4.4 check out this guide.
http://forum.xda-developers.com/showthread.php?t=2603358
Click to expand...
Click to collapse
That's the thing though... I already HAD 4.2.2 root. I just wanted to root 4.4. I tried the OTA to it, then RSD'd to 4.2.2. But by that point, my write protection was gone, and trying slapmymoto wasn't working either... I'm sorry for being a nuisance and newb, I just want to figure it out and be done!

byrdmang2 said:
That's the thing though... I already HAD 4.2.2 root. I just wanted to root 4.4. I tried the OTA to it, then RSD'd to 4.2.2. But by that point, my write protection was gone, and trying slapmymoto wasn't working either... I'm sorry for being a nuisance and newb, I just want to figure it out and be done!
Click to expand...
Click to collapse
You should still have write protect off even if you flash the stock firmware
run this command and let me know what you get
Code:
adb shell getprop ro.boot.write_protect
If you see "0", that pesky write protection is gone
then we will go from there
but if you have tried rooting you need to give us the error's you got trying to do the 4.4 root so we can see what the issues is and help you find a fix.

Well I have 0.. I've checked that every time I've given this a go. I'm assuming since I've rooted 4.2.2 before AND ran (successfully) motowpnomo, I jump to slapmymoto right?
Well when I do that and run the dalvikvm -cp ... command line, it gives me the line that the system is not write protected (duh), proceed to step 3 attempt the 4.4 ota.. But it doesn't auto reboot like I've read it should. So I've manually done adb reboot, figuring no difference right?
After I'm on 4.4 I try adb reboot bootloader to flash the 4.2.2 recovery.. Does it's business, fastboot reboot.
It's now gotten to the LAST command line with the "echo" command where I get permission denied.. How does that work?

byrdmang2 said:
Well I have 0.. I've checked that every time I've given this a go. I'm assuming since I've rooted 4.2.2 before AND ran (successfully) motowpnomo, I jump to slapmymoto right?
Well when I do that and run the dalvikvm -cp ... command line, it gives me the line that the system is not write protected (duh), proceed to step 3 attempt the 4.4 ota.. But it doesn't auto reboot like I've read it should. So I've manually done adb reboot, figuring no difference right?
After I'm on 4.4 I try adb reboot bootloader to flash the 4.2.2 recovery.. Does it's business, fastboot reboot.
It's now gotten to the LAST command line with the "echo" command where I get permission denied.. How does that work?
Click to expand...
Click to collapse
idk what guide your following but i think it is old.
1. download the correct 4.2.2 CU firmware for your Carrier
2. open the .zip files and extract the files into your folder with ADB and MFastBoot.
3. Boot your phone into the bootloader
4. Run the below commands one by one
Code:
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 erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot reboot
i recommend wiping your device also but that is up to you
Code:
fastboot erase userdata
fastboot erase cache
Step1)
Unzip SlapMyMoto-1,0.zip and push the jar file to your internal storage
Code:
adb push SlapMyMoto.jar /sdcard/SlapMyMoto.jar
Step2)
Use http://www.cydiaimpactor.com/ to open up a telnet session as system user on port 2222. We covered how to use Impactor and telnet in the RockMyMoto root, I won't be covering it again since this post is going to be long enough already, see here -> http://forum.xda-developers.com/show....php?t=2509590 or http://rootzwiki.com/topic/107098-ro...the-first-ota/
Connecting over telnet, and run Stage1 with this command:
Code:
dalvikvm -cp /sdcard/SlapMyMoto.jar SlapMyMoto
When the device tells you to reboot, do this manually with "adb reboot" or your power button. It will not auto reboot on this step
Step3)
Once the device has rebooted, run Impactor again and connect over telnet just like in the previous step, then run the same command
Code:
dalvikvm -cp /sdcard/SlapMyMoto.jar SlapMyMoto
Once the device has rebooted, please take the 4.4 OTA.
Step4)
Now that we are on 4.4, we can finish the process with adb shell:
Code:
adb shell
cp /sdcard/install.sh /data/local/tmp/install.sh
chmod 755 /data/local/tmp/install.sh
echo "/data/local/tmp/install.sh" > /sys/kernel/uevent_helper
Then either wait, or toggle your bluetooth. Once the device reboots, you will have root.
Some times you have to manually reboot your device and also manually install SuperSU from the market place

Okay, I'm gonna try it again. What I'm seeing for myself as well as everyone else: fastboot camera update > rsd.
Should I root check before taking the ota to make sure everything's in working order? Especially when the times it's supposed to reboot on its own, don't.

byrdmang2 said:
Okay, I'm gonna try it again. What I'm seeing for myself as well as everyone else: fastboot camera update > rsd.
Should I root check before taking the ota to make sure everything's in working order? Especially when the times it's supposed to reboot on its own, don't.
Click to expand...
Click to collapse
nope just flash the 4.2.2 CU firmware and start the slapmymoto guide when u get to the end reboot after it boots up look for SU if not there install and open see if the binaries will install then check root.

Well sir, whatever method(s) I was/were using were obviously wrong or just bad, cause I got the 4.4 root!
I got kinda nervous when I had to manually reboot at the end and wait for supersu to install.
Thank you very much for your assistance! Thanks are in order :good:

byrdmang2 said:
Well sir, whatever method(s) I was/were using were obviously wrong or just bad, cause I got the 4.4 root!
I got kinda nervous when I had to manually reboot at the end and wait for supersu to install.
Thank you very much for your assistance! Thanks are in order :good:
Click to expand...
Click to collapse
glade your up and running

Related

How-to Root - newb question from newb

Yes, I'm a noob
so I got my Moto XOOM and rooted it with adb and flashed a new kernel and installed ROM Manager and got a new recovery in it and all that and it was smooth as butter. I'm not a fan of ROMs but the kernel does make a huge difference already. Now, I did that as soon as I took the XOOM outta the box so I had no data to lose when rooting...
I've had my N1 for about a year now, been using 1-click root exploits because I didn't feel like starting over and losing all data even though I can have backups I know... but just putting the settings back, losing high scores in games, etc... is annoying enough.
But I'm starting to think now's the time.
So:
1) Best backup solution to not lose anything? My last titanium backup is from about two month ago when I lost root after the Gingerbread OTA
2) does it still stay rooted now with gingerbread? basically adb --> fastboot oem unlock and that's it?
3) I've read the wiki and it's great but not "omg I'm such a noob" proof... so the steps:
- I backup my stuff
- Reboot in recovery
- from my PC, run the command in adb --> fastboot oem unlock
- yes
- my nexus one is now unlocked, rooted but is back to factory...
after that, get the 2.3.3 update zip file from XDA and flash that. flash a new kernel via kernel manager (which one you guys recommend for speed and stability without all the fuss?)
that's it, finito?
thanks if you respond!
A - there are exploits available for Gingerbread, so you don't need to unlock the bootloader (though don't let that stop you)...
http://forum.xda-developers.com/showpost.php?p=13090966&postcount=67
B - unlocking the bootloader doesn't give you root. You also have to install a custom recovery and flash the su zip to gain root...
C - flashing an update zip will probably cause you to lose root (unless it's a pre-rooted zip, in which case you would need a custom recovery to flash it)...
hmm so I skipped a step, after unlocking bootloader I need to do what exactly? (commands/links if possible!)
it seemed simpler on the xoom.... unless it's the same thing?
adb reboot bootloader
fastboot oem unlock (wait for reboot)
adb reboot bootloader
fastboot flash boot rootboot.img
fastboot reboot (wait for reboot)
adb remount
adb shell push su /system/bin
adb shell ln –s /system/bin/su /system/xbin/su
adb shell chmod 4755 /system/bin/su
adb push Superuser.apk /system/app
that's it? are the Nexus files different? (got a link?)
as for Gingerbreak, I kinda got sick of always waiting a long time for 1-click roots after each update. I will try to get it working (so far no go, gonna stick a blank sd in my phone and try that) just so I can do a full Titanium backup and maybe a recovery if possible
Gingerbreak worked - stuck a blank micro-sd, rooted, put my 16gb micro-sd back in - all is well
running full Titanium now...

[WIP] [REQUEST] Misc partition dumps

Hey all,
A few of us are attempting to put together a solution to unlock the bootloader of the N4 without wiping, and we need your help.
We need dumps of the misc partition of the N4 both in a bootloader locked and unlocked state. I've explained below what we need and how to do it.
Note, this will require you to re-lock and unlock your bootloader, (which will cause your data to be wiped) so do a nandroid and copy it off your device for a later restore.
Novice instructions:
1) You need to start off with an unlocked bootloader.
2) Boot into fastboot mode and plug into your PC.
3) If you don't have ADB and fastboot on your PC, download the attachment from this post and extract the contents to a directory.
4) If you don't have CWM or TWRP flashed, download CWM from here and save as cwm.img in the same directory as in step 3.
5) Open a command prompt in the same directory as in step 3 (i.e., hold the shift key and right click in a blank space in that folder).
6) Flash CWM: fastboot flash recovery cwm.img
7) On your phone, navigate with the volume buttons to "recovery mode" and select with the power button.
8) Once CWM is booted, type the following commands into the command prompt:
Code:
adb shell
dd if=/dev/block/mmcblk0p19 of=/sdcard/misc-unlocked.img
exit
adb pull /sdcard/misc-unlocked.img
adb reboot bootloader
fastboot oem lock
fastboot reboot-bootloader
9) On your phone, navigate with the volume buttons to "recovery mode" and select with the power button.
10) Once CWM is booted, type the following commands into the command prompt:
Code:
adb shell
dd if=/dev/block/mmcblk0p19 of=/sdcard/misc-locked.img
exit
adb pull /sdcard/misc-locked.img
11) Now you have two files (misc-unlocked.img and misc-lock.img) in the directory you created in step 3. Zip them up and upload them in this thread.
12) Your bootloader is now locked. If you want it unlocked, unlock it using the normal method of "fastboot oem unlock" which will wipe your data, but all you have to do is restore your nandroid, and you will be back to where you started.
Advanced user instructions:
1) Start with an unlocked bootloader
2) Dump the misc partition: dd if=/dev/block/mmcblk0p19 of=/sdcard/misc-unlocked.img
3) Lock your bootloader
4) Dump the misc partition again: dd if=/dev/block/mmcblk0p19 of=/sdcard/misc-locked.img
5) Upload the files to this thread.
For advanced users only (this has not yet been tested), if you want, you can try flashing the unlocked misc partition:
Code:
adb shell "dd if=/sdcard/misc-unlocked.img of=/dev/block/mmcblk0p19"
to see if it will unlock your device without wiping. But as I said, this has not been tested yet, so do the last step at your own risk.
Edit: nvm
Here is the dump. Thanks for your work.
KyraOfFire said:
Does it wipe sdcard? It need to know if I have to copy everything to the computer.
Thanks,
Click to expand...
Click to collapse
To be safe, you should copy everything to your computer.
Our theory is, once you lock your bootloader with "fastboot oem lock", you should be able to unlock it again without wiping anything just by flashing the misc partition that you dumped when your device was unlocked.
So, the steps themselves will not wipe anything. But, if you use "fastboot oem unlock" to unlock your bootloader (once you have completed all the steps), then it will wipe everything including /sdcard. If you use the command in the "advanced users instructions", the idea is that it won't wipe anything.
KyraOfFire said:
Edit: nvm
Here is the dump. Thanks for your work.
Click to expand...
Click to collapse
Great thanks!
Did you try re-flashing the unlocked misc.img (while you were locked) to see if it unlocked?
I can't flash the misc-unlocked.img
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell "dd if=/sdca
rd/misc-unlocked.img of=/dev/block/mmcblk0p19"
dd: can't open '/sdcard/misc-unlocked.img': No such file or directory
Click to expand...
Click to collapse
What is the command prompt code to flash it from my computer?
Edit: I did boot to Android and copy the file to SDcard, but I still got the error above.
KyraOfFire said:
I can't flash the misc-unlocked.img
What is the command prompt code to flash it from my computer?
Edit: I did boot to Android and copy the file to SDcard, but I still got the error above.
Click to expand...
Click to collapse
Try this:
1) Copy the file to /sdcard
2) Reboot into CWM
3) Type in the command
I still got the same error.
Also, the directories seem to be messed up again, the classic orphaned back up folders in that CWM/system doesn't seem to recognized anymore....
KyraOfFire said:
I still got the same error.
Also, the directories seem to be messed up again, the classic orphaned back up folders in that CWM/system doesn't seem to recognized anymore....
Click to expand...
Click to collapse
Not sure why your directories are messed up.
Find where the file is saved, and use that path for the "if" part of the command. For example, if it is saved in /storage/emulate/0, then use this command:
adb shell "dd if=/storage/emulate/0/misc-unlocked.img of=/dev/block/mmcblk0p19"
Confirmed!
Flashing misc-unlocked.img unlocked my bootloader.
Note: I copy the file to /system, mounted /system in CWM then
adb shell "dd if=/system/misc-unlocked.img of=/dev/block/mmcblk0p19"
Click to expand...
Click to collapse
I have no idea why /sdcard or /storage/emulate/0/ doesn't work. But I think you should take a look into this when you cook up the new root method
KyraOfFire said:
Confirmed!
Flashing misc-unlocked.img unlocked my bootloader.
Note: I copy the file to /system, mounted /system in CWM then
I have no idea why /sdcard or /storage/emulate/0/ doesn't work. But I think you should take a look into this when you cook up the new root method
Click to expand...
Click to collapse
Great, thanks for the confirmation.
Very strange that /sdcard did not work. It worked fine on mine, but we will certainly look into it.
Thanks again.
Glad I could help. Now folks have less things to worry about when they decide to root
KyraOfFire said:
Edit: nvm
Here is the dump. Thanks for your work.
Click to expand...
Click to collapse
After looking at your dumps, it seems like you are running an old version of Android. Is it possible that you are still on JVP15Q? If so, I don't think that will help us too much. I dumped mine when I was on JOP40C (and I will do so again with JOP40D). If you do upgrade, then new dumps would be appreciated.
By the way, could you list the following from your device:
ROM version:
Bootloader:
Radio:
Thanks.
EDIT: If you want to follow the progress, you can have a look at this thread.
efrant said:
After looking at your dumps, it seems like you are running an old version of Android. Is it possible that you are still on JVP15Q?
Click to expand...
Click to collapse
Well that is totally weird
Build Number:JOP40D
Baseband version:M92615A-CEFWMAZM-2.0.1700.33
Bootloader version:MAKOZ101
is there anything look wrong?
When I get some wifi later today, I'll return to stock and dump the misc partition for JOP40C, possibly redo JOP40D too.
KyraOfFire said:
Well that is totally weird
Build Number:JOP40D
Baseband version:M92615A-CEFWMAZM-2.0.1700.33
Bootloader version:MAKOZ101
is there anything look wrong?
When I get some wifi later today, I'll return to stock and dump the misc partition for JOP40C, possibly redo JOP40D too.
Click to expand...
Click to collapse
Hmm. Thanks for the offer, but don't bother going through the hassle. If you are already running JOP40D, then it should be ok. Weird that your dump had JVP15Q in it. I'll wait until a couple of the other guys have a look at it (in this thread).
For science
KyraOfFire said:
For science
Click to expand...
Click to collapse
Thanks! Still mentions JVP15Q for some reason but I don't think that's a big deal. Found some interesting stuff already so we might be on to something. You've been very helpful.
osm0sis said:
Thanks! Still mentions JVP15Q for some reason but I don't think that's a big deal. Found some interesting stuff already so we might be on to something. You've been very helpful.
Click to expand...
Click to collapse
I have a feeling that it has something to do with history/logging. My N4 came with JOP40C out of the box, and I would bet that KyraOfFire's came with JVP15Q out of the box.

ATT Root MotoX Failed to Update to 4.4

Hey guys, so I decided to root my ATT Moto X, I went through the process of reverting to 4.2.2 rooting(RockMyMoto) flashing factory img rooting (SlapMyMoto), did the wpnomore. And then started to update to 4.4, and it fails. Gets about half way and that says "error" and boots back up just fine. Tried a few times and it keeps happening, I tried booting into fastboot and erased the cache, still fails.
Any ideas?
dansskittles said:
Hey guys, so I decided to root my ATT Moto X, I went through the process of reverting to 4.2.2 rooting(RockMyMoto) flashing factory img rooting (SlapMyMoto), did the wpnomore. And then started to update to 4.4, and it fails. Gets about half way and that says "error" and boots back up just fine. Tried a few times and it keeps happening, I tried booting into fastboot and erased the cache, still fails.
Any ideas?
Click to expand...
Click to collapse
is this the order you did
flash to 4.2.2 CU
Root 4.2.2
disable WP
flash back to 4.2.2 CU
start SlapMyMoto guide
here is my step by step guide
http://forum.xda-developers.com/showthread.php?t=2603358
but if i am not mistaken you can unlock your bootloader and then just flash TWRP everything is in the guide i just linked you too
Followed the steps from this script http://forum.xda-developers.com/showthread.php?t=2591875
I can not unlock my bootloader.
Check if WP is off if so flash back to stock 4.2.2 camera update and then start the slap my Moto guide it should work
Sent from my XT1056 using XDA Premium 4 mobile app
Tried the step by step guide. 4.4. OTA still fails.
dansskittles said:
Tried the step by step guide. 4.4. OTA still fails.
Click to expand...
Click to collapse
no error msg or anything. when you try to install the 4.4 OTA did it redownload it or did it just install it without downloading.
The only thing i could think of is that it is trying to install a corrupted OTA file so if i can find out ware it downloads it and have you delete it and try installing the 4.4 OTA again it might work
No really error messages, besides the Software update failed. Everytime it goes to install the OTA it redownloads it. However I also tried copying it over to the device and updating from recovery. Same error as the OTA.
dansskittles said:
No really error messages, besides the Software update failed. Everytime it goes to install the OTA it redownloads it. However I also tried copying it over to the device and updating from recovery. Same error as the OTA.
Click to expand...
Click to collapse
ok i have a idea let me check it out and ill make a guide for you
That sounds awesome, thanks a lot.
Ok this is just a thought on how you might be able to get this to work but please Flash at your Own risk.
Download Required Files:
4.2.2 Camera update Firmware
http://sbf.droid-developers.org/download.php?device=0&file=22
4.4 firmware
http://sbf.droid-developers.org/download.php?device=0&file=4
ADB/Fastboot(Android SDK)
http://developer.android.com/sdk/index.html
Mfastboot
https://drive.google.com/file/d/0B0dUKGxGylgNTk43eU0xc3VLekE/edit?usp=sharing
SlapMyMoto
http://forum.xda-developers.com/attachment.php?attachmentid=2463879&d=1387477699
First thing we are going to do is flash your phone back to 4.2.2CU via fastboot,
To do this we need to extract the 4.2.2CU firmware into the same folder that your adb/fastboot/mfastboot is located in.
so open the .rar file and then open the ATT_XT1058_4.2.2-13.9.0Q2.X-116-X-17-54_CFC_1FF.xml folder and extract all the files inside.
now put your phone into Bootloader mode and plug in the USB cable
i see your on a Mac so open terminal and CD to the location of your adb/fastboot/mfastboot and firmware files.
once there we are going to run the commands below.
Code:
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 erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase userdata
fastboot erase cache
fastboot reboot
let you device boot up and then we are going to start the SlapMyMoto part
Step1)
Unzip SlapMyMoto-1,0.zip and push the jar file to your internal storage
Code:
adb push SlapMyMoto.jar /sdcard/SlapMyMoto.jar
Step2)
Use http://www.cydiaimpactor.com/ to open up a telnet session as system user on port 2222. We covered how to use Impactor and telnet in the RockMyMoto root, I won't be covering it again since this post is going to be long enough already, see here -> http://forum.xda-developers.com/show....php?t=2509590 or http://rootzwiki.com/topic/107098-ro...the-first-ota/
Connecting over telnet, and run Stage1 with this command:
Code:
dalvikvm -cp /sdcard/SlapMyMoto.jar SlapMyMoto
When the device tells you to reboot, do this manually with "adb reboot" or your power button. It will not auto reboot on this step
Step3)
Once the device has rebooted, run Impactor again and connect over telnet just like in the previous step, then run the same command
Code:
dalvikvm -cp /sdcard/SlapMyMoto.jar SlapMyMoto
OK this is ware i am going to change on how we install the 4.4 OTA we are going to manually install it but leave out some commands
Now we need to delete all the 4.2.2CU firmware files we extracted out of your adb/fastboot/mfastboot folder
once you do that then extract the 4.4 firmware the same way we did the 4.2.2Cu firmware.
now we are going to open Terminal again if you closed it and Cd to the same directory as last time ware you extracted the 4.4 firmware files.
Now we are going to run these commands
Code:
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 erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot reboot
after your phone boots up we are going to finish the last step in the slapmymoto guide
Code:
adb shell
cp /sdcard/install.sh /data/local/tmp/install.sh
chmod 755 /data/local/tmp/install.sh
echo "/data/local/tmp/install.sh" > /sys/kernel/uevent_helper
Then either wait, or toggle your bluetooth. Once the device reboots, you will have root.
if all goes well you should be rooted after the auto reboot or you might have to manually reboot your device.
sometimes you have to install SuperSU your self from the market.
To check and see if you have root install root checker from the market and see what it says.
again i am not sure if this will work but it is the only thing left i can think of to get the 4.4 OTA and Root on your device.
Credits
jcase - for the Lovely SlapMyMoto Root Exploit
Well this upgraded me to 4.4 just fine. But i get hung up here
Code:
[email protected]:/ $ echo "/data/local/tmp/install.sh" > /sys/kernel/uevent_helper
/system/bin/sh: can't create /sys/kernel/uevent_helper: Permission denied
dansskittles said:
Well this upgraded me to 4.4 just fine. But i get hung up here
Code:
[email protected]:/ $ echo "/data/local/tmp/install.sh" > /sys/kernel/uevent_helper
/system/bin/sh: can't create /sys/kernel/uevent_helper: Permission denied
Click to expand...
Click to collapse
SlapMyMoto didn't work then. Make sure you got rid of write protection using MotoWpNoMo...Use "adb shell getprop ro.boot.write_protect" to verify, it should say "0" if you no longer have write protection.
To be clear:
1. Revert to 4.2.2
2. RockMyMoto
3. Make sure you have root.
4. MotoWpNoMo
5. Make sure write protection is disabled.
6. Revert to 4.2.2
7. SlapMyMoto - First half on 4.2.2
8. SlapMyMoto - Second half on 4.4
It does indeed say 0
Install SuperSU from the market open it let it install the binary reboot and check root with root checker
Sent from my XT1056 using XDA Premium 4 mobile app
I installed SuperSU, "There us no SU binary installed, and SuperSU cannot install it"
dansskittles said:
I installed SuperSU, "There us no SU binary installed, and SuperSU cannot install it"
Click to expand...
Click to collapse
I would reflash back to 4.2.2 and retry SlapMyMoto.
dansskittles said:
I installed SuperSU, "There us no SU binary installed, and SuperSU cannot install it"
Click to expand...
Click to collapse
now that Su is installed try running the last commands again then if still nothing then i would do what j-hunnter said
Code:
adb shell
cp /sdcard/install.sh /data/local/tmp/install.sh
chmod 755 /data/local/tmp/install.sh
echo "/data/local/tmp/install.sh" > /sys/kernel/uevent_helper
when you do these make sure you run them one by one
adb shell
enter
and so forth
---------- Post added at 05:51 PM ---------- Previous post was at 05:50 PM ----------
JJHunterx said:
I would reflash back to 4.2.2 and retry SlapMyMoto.
Click to expand...
Click to collapse
J-Hunterx i know i am having him do some weird stuff but i had another user have this issue and im trying to find the post but he was able to get root without re-doing everything
dray_jr said:
now that Su is installed try running the last commands again then if still nothing then i would do what j-hunnter said
Code:
adb shell
cp /sdcard/install.sh /data/local/tmp/install.sh
chmod 755 /data/local/tmp/install.sh
echo "/data/local/tmp/install.sh" > /sys/kernel/uevent_helper
when you do these make sure you run them one by one
adb shell
enter
and so forth
---------- Post added at 05:51 PM ---------- Previous post was at 05:50 PM ----------
J-Hunterx i know i am having him do some weird stuff but i had another user have this issue and im trying to find the post but he was able to get root without re-doing everything
Click to expand...
Click to collapse
Fair enough. It sounded to me like he couldn't get Supersu to install the binary to gain root and he wouldn't be able to run the shell commands.
Im currently on 4.2.2 and cant get root working. Scripts/apps Slap/Rock MyMoto don't run. However read/write is still at 0.
Tried re flashing back to CMU, no luck.
i feel your pain, I had the same issues a few days ago.
Instead of using 604k's script (which is great, it helped me understand the process better), i just followed Jcase's steps manually and EVENTUALLY got it to work (20+ times of reflashing...) 3 days or so to figure this out
granted I am a novice... but its like 10 lines of commands you'd think it'd be simple!
What i did and what worked for me,
flash to 4.2.2 camera firmware w/ RSDlite
ROOT w/ rockmymoto (only should have to be done once)
remove write protection (permanent)
run slapmymoto UNTIL the 2nd step where it says 'accept 4.4 OTA')
WHILE STILL ON 4.2.2:
i ran the commands:
adb push su /data/local/tmp/su
adb push install.sh /data/local/tmp/install.sh
adb push install-recovery.sh /data/local/tmp/install-recovery.sh
adb reboot
then i was able to have root on 4.2.2
then accept 4.4 OTA (it will work now)
then:
adb shell
cp /sdcard/install.sh /data/local/tmp/install.sh
chmod 755 /data/local/tmp/install.sh
echo "/data/local/tmp/install.sh" > /sys/kernel/uevent_helper
then reboot and you will have root!

[Root] Root and TWRP for R

Disclaimer: If you are not comfortable with using Fastboot and ADB and editing system files than this guide might not be for you. At this point this is what I have to offer.
Click here for the unofficial twrp image - Latest version as of 12/27/14
So getting right into it.
1. Turn on ADB mode on the watch by going to about and tapping the build info 7 times.
2. Download ADB and Fastboot utilties
3. Plug the watch into the computer and your phone should vibrate and ask you to accept the computers fingerprint, tick the check box to always allow and hit ok
4. Open up a command prompt or terminal inside of where the ADB utilities are located and enter
Code:
adb reboot bootloader
This next step will wipe your data!
5. Now you should be in fastboot, go ahead and on the terminal use the next code and follow prompts to unlock
Code:
fastboot oem unlock
6. Now after you re-set up your watch again you will need to do step 1 and 3 again.
Please do not skip step 6!
7. Go ahead and issue
Code:
adb reboot bootloader
8. Flash unofficial twrp, make sure the recovery image file is in the same location as fastboot than issue
Code:
fastboot flash recovery YOURIMGNAMEHERE.img
9. Upon successfully doing that you should have twrp installed
10. Lots in one step here, download the latest supersu.zip flashable file and put it in the same folder as ADB use the proper name of what you downloaded. Issue
Code:
adb push SUPERSUNAMEHERE.zip /sdcard/
11. Issue
Code:
adb reboot recovery
12. than using the very tiny TWRP and somewhat messed up go ahead and use it to install the supersu.zip under the folder /sdcard
13. Enjoy root and twrp.
I will make this guide into a much easier Java program in the very near future to make it easier to use.
This was typed up pretty fast and it is kinda hacky, I will work on a bat script and a shell script if we have enough osx users here. I'm sure someone will come along and make this better if I don't get around to it.
Credits:
Dees-Troy for his TWRP support for dory our fish brother device which worked on our device
Chainfire for all his hard work these many years
Q: ADB complains there is no device listed.
A: Install universal ADB drivers and then go to device manager and under the device with a yellow warning icon go to update driver, Browse my computer, let me pick from list of device drivers, than Google ADB interface. If it still complains turn off debugging, than turn it back on, revoke authorization, then disable and re-enable again.
One more just in case.
Great work!!
Just got the watch today and couldn't be happier. Custom kernel, TWRP and root (well sort of) all within 6 hours of having this watch.
I say root (sort of) because SU is force closing when running su in adb shell. First time it crashed adb on PC and had to reboot watch. Now it just force closes on my watch and adb exits on PC. What is the most current version of SuperSU? I have 1.94 from Chainfire's site.
Thank you SO MUCH for this! Do you or your team have a paypal?
hatefuel19 said:
Just got the watch today and couldn't be happier. Custom kernel, TWRP and root (well sort of) all within 6 hours of having this watch.
I say root (sort of) because SU is force closing when running su in adb shell. First time it crashed adb on PC and had to reboot watch. Now it just force closes on my watch and adb exits on PC. What is the most current version of SuperSU? I have 1.94 from Chainfire's site.
Thank you SO MUCH for this! Do you or your team have a paypal?
Click to expand...
Click to collapse
The latest supersu is version 2.36 dated 11.27.2014. 1.94 is well over a year old, you need to update for sure that is why you are force closing.
I figured that's what it was. Feeel real dumb for not finding the newest version the first time. Also most current is now 2.37 XD
Edit: That got it! Thanks tonu!
hatefuel19 said:
I figured that's what it was. Feeel real dumb for not finding the newest version the first time. Also most current is now 2.37 XD
Edit: That got it! Thanks tonu!
Click to expand...
Click to collapse
I'm here to help! I'm working on adding other mods to my other thread right now I'm working on getting busybox working.
Thanks for doing all of this work.
I was hoping you could help me with a step I am stuck on.
10. Lots in one step here, download the latest supersu.zip flashable file and put it in the same folder as ADB. Issue "adb push SUPERSUNAMEHERE.zip /sdcard/
When I do this it is saying permission denied. Also, should the watch be in recovery or fully booted when I run this command?
Thanks
---------- Post added at 09:31 PM ---------- Previous post was at 09:28 PM ----------
jimmydigital00 said:
Thanks for doing all of this work.
I was hoping you could help me with a step I am stuck on.
10. Lots in one step here, download the latest supersu.zip flashable file and put it in the same folder as ADB. Issue "adb push SUPERSUNAMEHERE.zip /sdcard/
When I do this it is saying permission denied. Also, should the watch be in recovery or fully booted when I run this command?
Thanks
Click to expand...
Click to collapse
Disregard I did it again and for some reason it worked. Maybe I need to reboot first.
Recovery
I went through your command and everything worked until I ran:
fastboot flash recovery UNOFFICIAL-openrecovery-twrp-2.8.0.0-lenok.img
Now the device just boots into the recovery and not into the system. The system/data partitions keep saying:
E:Unable to mount /data
E:Unable to mount /system
I am very comfortable with fastboot and adb so I do not know what I did wrong here.
Any ideas?
adamrobles said:
I went through your command and everything worked until I ran:
fastboot flash recovery UNOFFICIAL-openrecovery-twrp-2.8.0.0-lenok.img
Now the device just boots into the recovery and not into the system. The system/data partitions keep saying:
E:Unable to mount /data
E:Unable to mount /system
I am very comfortable with fastboot and adb so I do not know what I did wrong here.
Any ideas?
Click to expand...
Click to collapse
Try reflashing the recovery IMG again. And check back here.
Sent from my A0001 using XDA Free mobile app
reflashed
tonu42 said:
Try reflashing the recovery IMG again. And check back here.
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
I reflashed the recovery you provided and I keep rebooting to system but it takes me to twrp.
I am in the process of downloading the system dump from another thread to hopefully flash those to get back into the system.
adamrobles said:
I reflashed the recovery you provided and I keep rebooting to system but it takes me to twrp.
I am in the process of downloading the system dump from another thread to hopefully flash those to get back into the system.
Click to expand...
Click to collapse
The dump is extracted from the system.img, you won't be able to flash it in any way. None of this guide touches system files besides the root stuff which shouldn't affect boot. Try flashing the stock recovery.img instead.
tonu42 said:
The dump is extracted from the system.img, you won't be able to flash it in any way. None of this guide touches system files besides the root stuff which shouldn't affect boot. Try flashing the stock recovery.img instead.
Click to expand...
Click to collapse
Thank you for that information, I stopped the download of the dump.
Downloading the stock recovery now.
---------- Post added at 02:24 PM ---------- Previous post was at 02:10 PM ----------
tonu42 said:
The dump is extracted from the system.img, you won't be able to flash it in any way. None of this guide touches system files besides the root stuff which shouldn't affect boot. Try flashing the stock recovery.img instead.
Click to expand...
Click to collapse
I must have skipped a step...
installed stock recovery
booted into the watch system
enabled adb debugging
reboot to bootloader
install your recovery image
rebooted
pushed supersu
rebooted to twrp
installed supersu
rebooted to system
adb shell - verified root!
You are awesome! Thank you for taking the time to help me!
HYPE for 5.0.1
'm Hype! can't wait to flash the first 5.0.1 system dump on this as stated by +Darek Ross we MAY be receiving update as early as today!
I did this yesterday, and run into the same problem - TWRP spitting out errors when flashing
It was caused by NOT rebooting after unlocking bootloader, but proceeding with the flash rightaway - this apparently leaves the watch in an empty state (no /sdcard or /system contents) and it needs to boot up at least once before you flash anything
So the correct procedure is like this
1) enable development options
2) enable usb debugging
3) adb reboot-bootloader
4) fastboot oem unlock
5) let the watch boot normally, pair with your phone, enable development options and usb debugging again
6) adb reboot-bootloader
7) fastboot flash recovery recovery.img
8) fastboot reboot
9) adb push supersu.zip /sdcard/
10) adb reboot recovery
11) flash supersu.zip
Apparently, there is a problem when the original kernel is not present after "fastboot oem unlock" - the watch will be left empty, while on the original kernel it "reinstalls"
I typed this from memory, but I think you should know how these things work anyway, as there's not much for a "normal" user to do anyway... yet...
zvieratko said:
I did this yesterday, and run into the same problem - TWRP spitting out errors when flashing
It was caused by NOT rebooting after unlocking bootloader, but proceeding with the flash rightaway - this apparently leaves the watch in an empty state (no /sdcard or /system contents) and it needs to boot up at least once before you flash anything
So the correct procedure is like this
1) enable development options
2) enable usb debugging
3) adb reboot-bootloader
4) fastboot oem unlock
5) let the watch boot normally, pair with your phone, enable development options and usb debugging again
6) adb reboot-bootloader
7) fastboot flash recovery recovery.img
8) fastboot reboot
9) adb push supersu.zip /sdcard/
10) adb reboot recovery
11) flash supersu.zip
Apparently, there is a problem when the original kernel is not present after "fastboot oem unlock" - the watch will be left empty, while on the original kernel it "reinstalls"
I typed this from memory, but I think you should know how these things work anyway, as there's not much for a "normal" user to do anyway... yet...
Click to expand...
Click to collapse
My guide is setup like the one you put there. In order to get adb working again you need to re setup the watch step 6. Read the instructions carefully. I'll post a batch script later to simplify this.
Sent from my A0001 using XDA Free mobile app
Step 6 doesn't really say "you need to do this, OR ELSE", it seems like you just rehash the factory reset thing
And you should put step 10 before step 6, it can't really be done in that order...
but again, I guess the people trying this should now how it works, so no biggie, but since a few of us got hit by that "no initial boot" issue, it would be better to put a note in there
zvieratko said:
Step 6 doesn't really say "you need to do this, OR ELSE", it seems like you just rehash the factory reset thing
And you should put step 10 before step 6, it can't really be done in that order...
but again, I guess the people trying this should now how it works, so no biggie, but since a few of us got hit by that "no initial boot" issue, it would be better to put a note in there
Click to expand...
Click to collapse
By default debugging is disabled, I'm not sure how you were able to issue an ADB command on step 7 with out first performing step 6.
Aaah, sorry, should have been "after step 6"
another option is to do adb push with recovery loaded
I guess that's why I got that error before, because I combined 5+8 and flashed the recovery, but TWRP was unable to revive the watch from factory reset state (which makes me think it should not be on the watch unless needed...)
zvieratko said:
Aaah, sorry, should have been "after step 6"
another option is to do adb push with recovery loaded
I guess that's why I got that error before, because I combined 5+8 and flashed the recovery, but TWRP was unable to revive the watch from factory reset state (which makes me think it should not be on the watch unless needed...)
Click to expand...
Click to collapse
Ah I see, yea the guide is written as the absolute minimum to work right now. Like I said later today I'll try to post a script that automates all of this, its much easier.

[TUTORIAL] Applying an OTA update with stock + root/custom recovery

Preamble
As the title suggests, I had a Nexus 5 running stock Android 5.0, with root and TWRP, and wanted to update to Android 5.0.1 (without losing all my data, of course). I couldn't find any guides for my particular circumstances, so after working out how to do it myself, I thought I'd share my method.
Note: This guide is not for the uninitiated. Be prepared to Google something for yourself if you don't understand it.
Prerequisites
Before starting this guide, you should have:
A Nexus 5 that running stock Android. The presence of root/Xposed/custom recovery (maybe custom kernels?) shouldn't be relevant, but I can't vouch for the efficacy of this guide if you've done something obscure to your install.
Android SDK tools, specifically the ADB and fastboot binaries. Additional USB drivers may be required on Windows.
The factory image for the Android version you are currently running.
1. Uninstall root and other /system modifications
If you have rooted your Android, and/or installed BusyBox, Xposed or other modifications to /system, you will need to uninstall these modifications. Failing to do so will cause the OTA to complain that there's something funky going on in your /system partition.
You may be able to manually uninstall each of these modifications, but this was not enough for my install – doing a ‘Full unroot’ in SuperSU still left behind files in /system. The easiest way to uninstall all /system modifications is to reflash the /system partition.
Extract the Nexus 5 factory image (e.g. hammerhead-lrx21o-factory-01315e08.tgz), yielding a directory with files such as flash-all.bat and image-hammerhead-XXXXXX.zip. Do not use the flash-all script, as this will unnecessarily wipe all data on the device.
Extract the image-hammerhead-XXXXXX.zip file, specifically the system.img file.
Open a command prompt/terminal window.
Connect the phone to the computer with a USB cable.
Boot the phone into the bootloader.
Method 1: Power down the phone, then hold VolUp + VolDn + Power until the phone boots into the bootloader.
Method 2: From the terminal, run adb reboot bootloader while the phone is still powered on.
From the terminal, run fastboot flash system /path/to/system.img.
2. Uninstall any custom recovery
Custom recoveries don't seem to support OTA updates, making it necessary to uninstall the custom recovery by reflashing the stock recovery.
Extract the recovery.img file from the factory image, as in Part 1.
Open a command prompt/terminal window, connect the phone to the computer, and boot into the bootloader, as in Part 1.
From the terminal, run fastboot flash recovery /path/to/recovery.img.
Optional: Reflash boot.img and/or cache.img
Some users have reported that reflashing system.img was not sufficient, and that reflashing boot.img and/or cache.img was also necessary. I did not have this problem, but if you do:
Extract the boot.img and/or cache.img files from the factory image, as in Part 1.
Open a command prompt/terminal window, connect the phone to the computer, and boot into the bootloader, as in Part 1.
From the terminal, run fastboot flash boot /path/to/boot.img.
From the terminal, run fastboot flash cache /path/to/cache.img.
3. Apply the OTA update
The simple part. In the bootloader, use the VolUp/VolDn buttons to select ‘Start’, then press the Power button, to reboot into Android. Follow the system update instructions to install the OTA update.
4. Reflash the custom recovery and re-root
Also self-explanatory.
Hey,
I just wanted to say thanks. This totally fixed the problem I was having. I also want to add that after I flashed the system.img, I was getting errors related to "EMMC:/dev/block/platform/msm_sdcc.1/by-name/boot" with a bunch of numbers after. I googled it and found I had to also flash boot.img, and after that, the OTA worked fine. I would assume if anyone else gets errors like this, they should flash whatever img it shows in the error (ie: mine said /by-name/boot so I flashed boot.img).
-BGM
It worked for me
I've always been using a toolkit for my rooting purposes, I have done Full Unroot on SuperSU, but still getting an error when trying to update to 5.0.1
Will flashing stock wipe everything(whatsapp image, camera's,messages, etc etc)on my phone?
azlan96 said:
I've always been using a toolkit for my rooting purposes, I have done Full Unroot on SuperSU, but still getting an error when trying to update to 5.0.1
Will flashing stock wipe everything(whatsapp image, camera's,messages, etc etc)on my phone?
Click to expand...
Click to collapse
I also had problems using ‘Full Unroot’ in SuperSU. It's not actually as ‘full’ as it sounds.
Flashing a full factory image would normally wipe everything, but carefully following this guide will only reset the /system partition, not any user data.
I'd like to say thank you very much! I was looking for this kind of tutorial... I encountered an error while following all the steps because I forgot I had a custom kernel. So I wanted to add that if you have a custom kernel remember to do the same steps as described above for the kernel (return to stock) and then follow the system and recovery steps afterwards.
If you don't like running commands in terminal you can use Nexus Root Toolkit, on advanced, you have all the commands you need available.
Thank you very much RunasSudo
Taiyo85 said:
I'd like to say thank you very much! I was looking for this kind of tutorial... I encountered an error while following all the steps because I forgot I had a custom kernel. So I wanted to add that if you have a custom kernel remember to do the same steps as described above for the kernel (return to stock) and then follow the system and recovery steps afterwards.
If you don't like running commands in terminal you can use Nexus Root Toolkit, on advanced, you have all the commands you need available.
Thank you very much RunasSudo
Click to expand...
Click to collapse
I have my ADB and Fastboot ok as confirmed by nexus root toolkit, but I am not sure on how to use terminal.. I launched command prompt but it doest recognise all the commands..
Tried Flash Stock + Unroot on Nexus Root Toolkit but the software will crash (fastboot.exe has stopped responding)
I am really clueless on what to do next..
azlan96 said:
I have my ADB and Fastboot ok as confirmed by nexus root toolkit, but I am not sure on how to use terminal.. I launched command prompt but it doest recognise all the commands..
Tried Flash Stock + Unroot on Nexus Root Toolkit but the software will crash (fastboot.exe has stopped responding)
I am really clueless on what to do next..
Click to expand...
Click to collapse
Flash Stock + Unroot wipes everything and defeats the purpose of the tutorial made by RunasSudo
First and foremost you should download Android SDK (Tools only) on http://developer.android.com/sdk/index.html and then ask to install the extra: Google USB Driver.
With Nexus Root Toolkit you don't need terminal, click on advanced and you should see options to flash through fastboot the system only, recovery and kernel. It is pretty straighforward and it asks where the .img are in your computer
Thanks! This guide worked.
For Ubuntu users, you need to install adb and fastboot with these commands :
sudo add-apt-repository ppahablet-team/tools && sudo apt-get update (optional)
sudo apt-get install android-tools-adb android-tools-fastboot
Thanks for the great step by step.
As with some of the other posters, re-flashing system.img was not enough for me, I had to also re-flash the boot.img. Once that was done, I had no problems side loading the update and am now running LRX22C.
I only seem to fiddle with adb once a year - when it OTA time comes - and can never seem to remember some of the steps that need to be taken. Reading through some of the other threads, I have a feeling a lot of people who rooted/custom recovery and cant do the OTA are going to be doing complete image re-flashes when this guide makes that completely unecessary.
thanks again,
.d
BananasGoMoo said:
I googled it and found I had to also flash boot.img, and after that, the OTA worked fine.
Click to expand...
Click to collapse
datcon said:
As with some of the other posters, re-flashing system.img was not enough for me, I had to also re-flash the boot.img.
Click to expand...
Click to collapse
Thanks for the feedback! I've added a note about boot.img to the OP.
+1 for flashing boot.img worked perfect after I did that.
I tried with this tutorial. I flashed system and recovery and then restart. Confirm OTA but I get ERROR.
Then I flashed boot as it was described. Now I don't get OTA In About phone, I'm still on 5.0.0, Check for updates now don't find update
Any idea?
UPDATE - UPDATE: After hour now it is here ... super, it works.
This walkthrough was most helpful! Ended up replacing the boot.img as well since I had ElementalX installed. My apps are optimizing as we speak. Thank you!
Worked for me. What a hassle!
Here is a summary of the process for those looking for a less wordy procedure, with a few added steps:
Download Nexus 5 5.0 (LRX21O) file (note: NOT 5.0.1 yet) https://developers.google.com/android/nexus/images
Unzip via 7-zip multiple times in order to get boot.img, recovery.img, system.img
Enable USB debugging: http://www.kingoapp.com/root-tutorials/how-to-enable-usb-debugging-mode-on-android-5-lollipop.htm
Plug phone into PC > cmd prompt where adb is installed > type "adb devices" to ensure connection is valid (will need to authorize via popup on phone > then "adb devices" should return your device id and "device"; if it says "unauthorized" then look for the popup on your phone)
adb reboot bootloader
Put system.img, recovery.img, and boot.img in same folder as fastboot.exe
Run commands:
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot erase cache (this is optional. I didn't have to do it, but you might)
Use Volume Up/Down to select Start > press Power Button to reboot
Update via Settings > About Phone > System Update
Re-flash TWRP recovery:
Get the file from here: http://forum.xda-developers.com/showpost.php?p=57580889&postcount=1
adb reboot bootloader
fastboot flash recovery openrecovery-twrp-2.8.1.0-hammerhead.img
Paul22000 said:
Worked for me. What a hassle!
Here is a summary of the process for those looking for a less wordy procedure, with a few added steps:
1. Download Nexus 5 5.0 (LRX21O) file (note: NOT 5.0.1 yet) https://developers.google.com/android/nexus/images
2. Unzip via 7-zip multiple times in order to get boot.img, recovery.img, system.img
3. Enable USB debugging: http://www.kingoapp.com/root-tutorials/how-to-enable-usb-debugging-mode-on-android-5-lollipop.htm
4. Plug phone into PC > cmd prompt where adb is installed > type "adb devices" to ensure connection is valid (will need to authorize via popup on phone > then "adb devices" should return your device id and "device"; if it says "unauthorized" then look for the popup on your phone)
5. adb reboot bootloader
6. Put system.img, recovery.img, and boot.img in same folder as fastboot.exe
7. Run commands:
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
8. Use Volume Up/Down to select Start > press Power Button to reboot
9. Update via Settings > About Phone > System Update
Click to expand...
Click to collapse
Maybe you could add `fastboot erase cache` as stepp 8.
gee2012 said:
Maybe you could add `fastboot erase cache` as stepp 8.
Click to expand...
Click to collapse
I added it to step 7, thanks. :good: I also cleaned up the formatting and added step 10 about re-flashing TWRP.
Loading problem
I flashed system, recovery & boot images strictly following the instructions, restarted the phone. It got stuck in loading where balls in four colors keep running for half an hour. Shall I keep waiting? I think there must be something wrong. Your advises are welcome.
guangy said:
I flashed system, recovery & boot images strictly following the instructions, restarted the phone. It got stuck in loading where balls in four colors keep running for half an hour. Shall I keep waiting? I think there must be something wrong. Your advises are welcome.
Click to expand...
Click to collapse
Try flash the partitions again. If it's still not working, you may need to reflash a factory image.
RunasSudo said:
Try flash the partitions again. If it's still not working, you may need to reflash a factory image.
Click to expand...
Click to collapse
I flashed the cache image as well, then the problem solved. Thanks

Categories

Resources