[Q] RockMyMoto - need a bit of help - Moto X Q&A

I made a few judgement errors while playing with my phone one day (vzn android 4.4 rooted) and ended up getting stuck in a situation where I had to RSD back to stock. I started over, but now I am getting hung up on attempting to root. I am hoping it is just something totally stupid I am missing so I can get it solved and be on my way.
I am currently sitting on a fresh install of 4.2.2 (post camera). I have re-downloaded RockMyMoto and unzipped it. Completely fresh file. Everything is a clean install. On the first time of running it, I get this message:
System is not write protected...
Executing step 3...
Click to expand...
Click to collapse
I am not sure what is happening or why it is happening, but I am hoping someone else knows.
I've tried wiping data and cache, tried RSDing a couple of times.
This happens both when I am following the tutorial JCase posted and when I am using the moto toolbox.
Thank you in advance.

http://forum.xda-developers.com/moto-x/development/tool-moto-x-toolkit-v1-4-0-t2477132
So easy a caveman
I used 1.3.4 and was piece of cake.. just follow instructions. I was on 4.4 and clicked root with slap, maybe some peeps here can help you as to where you need to start now since you already began a process
edit, when you get to the download page the real download button is in the red circle... don't know why stillthisguy stillusesthissitetohosthisfile.. you get spammed like crazy but the toolkit works well

le Fix
http://forum.xda-developers.com/showpost.php?p=53896831&postcount=5
Fadelight said:
I made a few judgement errors while playing with my phone one day (vzn android 4.4 rooted) and ended up getting stuck in a situation where I had to RSD back to stock. I started over, but now I am getting hung up on attempting to root. I am hoping it is just something totally stupid I am missing so I can get it solved and be on my way.
I am currently sitting on a fresh install of 4.2.2 (post camera). I have re-downloaded RockMyMoto and unzipped it. Completely fresh file. Everything is a clean install. On the first time of running it, I get this message:
I am not sure what is happening or why it is happening, but I am hoping someone else knows.
I've tried wiping data and cache, tried RSDing a couple of times.
This happens both when I am following the tutorial JCase posted and when I am using the moto toolbox.
Thank you in advance.
Click to expand...
Click to collapse

doitinthedirt said:
http://forum.xda-developers.com/moto-x/development/tool-moto-x-toolkit-v1-4-0-t2477132
So easy a caveman
I used 1.3.4 and was piece of cake.. just follow instructions. I was on 4.4 and clicked root with slap, maybe some peeps here can help you as to where you need to start now since you already began a process
edit, when you get to the download page the real download button is in the red circle... don't know why stillthisguy stillusesthissitetohosthisfile.. you get spammed like crazy but the toolkit works well
Click to expand...
Click to collapse
I tried the toolbox. I got the same error. Otherwise, yeah, that toolbox is awesome.
When I rooted my phone the first time, that toolbox hadn't yet been updated, so I did it all manually, but Ive rooted a couple of other phones using his tool. He is an awesome guy for releasing that tool, for sure.
erecker1 said:
http://forum.xda-developers.com/showpost.php?p=53896831&postcount=5
Click to expand...
Click to collapse
This looks like exactly what I need. Thank you very much! Ill give it a go later. In the meantime, it appears your search was far better than mine, so I'll just let this thread die. lol.
Thanks again, guys.
EDIT: worked awesomely. I cant thank you enough, erecker1.

Perfect, glad to hear that got you going! Yes, it's a shame that JCASE has closed his rockmymoto thread so this cannot be posted there, AND xda-developers says I don't have enough 'points' or 'cred' or whatever to post this fix directly to the Developers forum. So here I am, randomly replying to people with this fix I made. Looks like this time, xda-developers got the hero they need, not the hero they want. lol
Anyways, cheers mate, enjoy!
Fadelight said:
I tried the toolbox. I got the same error. Otherwise, yeah, that toolbox is awesome.
When I rooted my phone the first time, that toolbox hadn't yet been updated, so I did it all manually, but Ive rooted a couple of other phones using his tool. He is an awesome guy for releasing that tool, for sure.
This looks like exactly what I need. Thank you very much! Ill give it a go later. In the meantime, it appears your search was far better than mine, so I'll just let this thread die. lol.
Thanks again, guys.
EDIT: worked awesomely. I cant thank you enough, erecker1.
Click to expand...
Click to collapse

Related

[Q] How to start over?

I'm not sure whats going on with my D3. However, I have RSD and I have .890 and .959 downloaded as well as Fastboot.
What I want to do is just wipe the phone completely and just flash it like its a brand new phone.
Anyone know how to do so? Please post a link or instructions, I would greatly appreciate it.
atquick said:
I'm not sure whats going on with my D3. However, I have RSD and I have .890 and .959 downloaded as well as Fastboot.
What I want to do is just wipe the phone completely and just flash it like its a brand new phone.
Anyone know how to do so? Please post a link or instructions, I would greatly appreciate it.
Click to expand...
Click to collapse
http://goo.gl/7NoAv
Androidsims said:
http://goo.gl/7NoAv
Click to expand...
Click to collapse
Tried that. It keeps failing saying something about size was not as expected or something like that.
Redownload?
Avelnan said:
Redownload?
Click to expand...
Click to collapse
I have. MD5 sums match up each time. Should I try removing the ext sd card?
I would redownload everything and try agian
littleneutrino said:
I would redownload everything and try agian
Click to expand...
Click to collapse
Alright, attempt will be made again. Should I redownload RSD again or just the sbf's?
atquick said:
Alright, attempt will be made again. Should I redownload RSD again or just the sbf's?
Click to expand...
Click to collapse
Downloading the sbf's again. Went over to check and see if the phone was still on, The charging led is on, however the screen is off..
Held power, nothing. Held M + Power. Still nothing... Any thoughts on whats going on now?
I didn't see if you have pulled the SD card but yeah it can't hurt.
Sent from my DROID3 using XDA App
http://forum.xda-developers.com/showthread.php?t=1278056
Follow the first portion of the instructions on how to flash back to original 5.6.890. Note the making of a folder and it's name for the 890 flash.
Ignore the part about flashing the new ROM. These are the best instructions I've found so far for flashing back to stock via RSD lite.
Good luck, keep us posted.
Download and follow exactly and you'll be good to go.
Hope that helps.
Sent from my DROID3 using xda premium
wattnxt said:
http://forum.xda-developers.com/showthread.php?t=1278056
Follow the first portion of the instructions on how to flash back to original 5.6.890. Note the making of a folder and it's name for the 890 flash.
Ignore the part about flashing the new ROM. These are the best instructions I've found so far for flashing back to stock via RSD lite.
Good luck, keep us posted.
Download and follow exactly and you'll be good to go.
Hope that helps.
Sent from my DROID3 using xda premium
Click to expand...
Click to collapse
It keeps failing.
Step 3 mbmloader.bin
Step 4 mbm.bin
Step 8 logo.bin
Step 9 'lbl'
I'm stuck.
Let me do some looking when I get home tonight. I remember there being a file for certain versions of XP that helped some people and they couldn't flash without it.
I never had it happen personally, but I know those that did were terribly frustrated.
I also hear the 959 version is easier to flash for some reason. Never flashed that version, so this is only hear-say. But I know it did flash easier according to posts.
I will try to dig up a link for you.
i am getting the same thing also getting the bad CG boot.. now this may be a fix but idk how this guy got it it.. i have been asking eveywhere maybe you guys could help me... here is the thread http://forum.xda-developers.com/showthread.php?t=1248721
I found this by Psouza. He is likely the foremost expert on making things easy as far as unbricking your D3. Rumor has it he has a set of unbrick tools floating around this forum somewhere, though I haven't found it yet. Try in the Development thread, for sure it has to be there somewhere.
Post number 84
psouza4 said:
For those of you having problems flashing this and/or are suspicious of flashing ebr, mbr, and parts of the bootloader, you can selectively just flash the rest of it.
See attachment.
Click to expand...
Click to collapse
http://forum.xda-developers.com/attachment.php?attachmentid=715510&d=1315657647
Hope this helps.
I also saw that flashing the pre-installs file alone first helped someone. That file borked on me once, but I was able to adb it over and then execute it via adb to get my phone unbricked.
Please let us know what works for you, as all of this is a work in progress right now.
Good luck!
i don't know to much about adb and are looking for help on pre-installed files. I don't understand what that means or how to go about it? i also cant get past the bootloader screen, "invalid CG version". i can not boot up at all.
How bricked are you? can you boot into CWM? Are you able to boot into tools, or how far can you get?
What version were you running? 5.959 (stock) or 6.890 OTA or Leaked OTA or Soak test (all the same as far as 6.890 goes).
i can get into boot tools and just tryed another flash got to step 6 till it failed instead of 3.. I'm running stock. Cannot get passed boot tools... scratch all that just tried to flash again just on the off chance it mnight work and i got it. Going to try and re-root and CWN recovery with sdteel froids rom... will keep you in the loop
Awesome!!
Here is the link about the adb commands for preinstall.sh
http://forum.xda-developers.com/showpost.php?p=17196391&postcount=88
It helped me when I borked my leaked update. I ran into the same problem as limaxray did with too many files in /system. So make sure you clean out any apps you made into system apps before trying the update via the standard update route, and that all stock system apps are in place and properly named.
I had to remove some that updated partially with the leaked update when mine borked. I used the posted system dump to push them to the phone and then the update ran properly and updated them anyhow.
If for some reason re-rooting doesn't work for you. Go to /system/bin and remove su, busybox. Do the same in /system/xbin. For some reason if you already have them in there when you run the process, it will say success but no root after reboot. My 2c as it happened to me. You do not need to remove superuser.apk, but you will have to update it in the market after you re-root.
Congrats!!
I see now too there is a fastboot and moto-fastboot. moto-fastboot has worked for some who had issues from what I've found.
Keep us posted, and smile knowing you've recovered from a bork; none of us got where we are without doing it at least once, so you're in good company.
re-rooted and installed bootstrap, just got steel droid all loaded up and all is good.... thanks for your speedy responses and detailed instructions and links. I realy think all that happened was i took everything aet it sone last time tried to flash and it went threw. All i used was RSD lite and flashed the 8.6.590 fast boot file and after a several retries it went threw. If anyone needs help on this i will post the file links if you need the ones i used

HTC VIVID Super User Problems....

So I am a new person and therefor can not post this in the development thread under the forum where I feel it would belong with the other root related questions.... So i followed the SUPER GUIDE to root my phone (Thank you so much Slapshot and PirateGhost, I was beginning to regret not getting a skyrocket until I found your thread). My super user is running into an issue I can not seem to fix.....
Maybe this is simple or maybe I really messed something up....
Basically none of my apps have root anymore (they did at one point and to my knowledge I change nothing...)
When I go to the Super User app to update my binaries and hopefully get any issues resolved I am greeted by the following error message in the update log: "Failed to find currently installed SU binary. Update cannot continue"
Is there a resolution for this? I have not found anyone even running into the same issue on the Vivid.....
A little nervous.... I didnt have near this many issues rooting my ATRIX and modding the living daylights out of that.
Have you checked with Root Checker Basic to see if you even have Root? If you didn't follow the Super Guide step by step your phone could have relocked after you turned your phone off/on.
If it still fails to update you could try SuperUser Update Fixer.
Yes I have check with root checker.
This may be a dumb question but how do I uninstall Superuser? When I go to the typical application management it does not give me the option. I have done an install again to overwrite the files and nothing changed there.
I followed the instructions step by step (though obviously I messed up somewhere...)
Sent from my HTC PH39100 using XDA App
Kraizk said:
So I am a new person and therefor can not post this in the development thread under the forum where I feel it would belong with the other root related questions.... So i followed the SUPER GUIDE to root my phone (Thank you so much Slapshot and PirateGhost, I was beginning to regret not getting a skyrocket until I found your thread). My super user is running into an issue I can not seem to fix.....
Maybe this is simple or maybe I really messed something up....
Basically none of my apps have root anymore (they did at one point and to my knowledge I change nothing...)
When I go to the Super User app to update my binaries and hopefully get any issues resolved I am greeted by the following error message in the update log: "Failed to find currently installed SU binary. Update cannot continue"
Is there a resolution for this? I have not found anyone even running into the same issue on the Vivid.....
A little nervous.... I didnt have near this many issues rooting my ATRIX and modding the living daylights out of that.
Click to expand...
Click to collapse
Interesting... maybe your root didn't stick. We had a little trouble with that before but pirateghost fixed the CWM ROOT zip. You have a working CWM Recovery, correct?
In the superguide, I have a second option for root in case the first doesn't work. In your case, go ahead and try the second option. The one involving the supertool. That should get you perm root. If that doesn't even work, then we might have to put you back to stock and go at it again.
EDIT: BEFORE TRYING THE SUPERTOOL, try flashing the new CWM ROOT VER2 zip from CWM recovery and see if root sticks.
Slapshot, thank you for checking the General Thread, I really do appreciate that. I have tried both methods multiple times since the root failure seeing as so many people said they had to run the methods multiple times to make them stick (this admittedly may be part of the issue). The most recent one has been the CWM ROOT VER2. Still no dice. Is there a method to remove and re install super user? Or am I reading into the error too literally and instead I just basically do not have root.
Kraizk said:
Slapshot, thank you for checking the General Thread, I really do appreciate that. I have tried both methods multiple times since the root failure seeing as so many people said they had to run the methods multiple times to make them stick (this admittedly may be part of the issue). The most recent one has been the CWM ROOT VER2. Still no dice. Is there a method to remove and re install super user? Or am I reading into the error too literally and instead I just basically do not have root.
Click to expand...
Click to collapse
No problem. At this point I think you may just not have root... but first, go ahead and go into bootloader (power off, then power on while holding power and vol down). Does your device say unlocked?
*Just a clarification*
You have to unroot your phone to get rid of it Idk why I put uninstall/reinstall earlier...still out there from last night I guess.
slapshot30 said:
No problem. At this point I think you may just not have root... but first, go ahead and go into bootloader (power off, then power on while holding power and vol down). Does your device say unlocked?
Click to expand...
Click to collapse
Yes the device still says unlocked. That was one of the first things I checked... Haha....
As I said ive flashed the rooted CWM and it says it went over successfully.
If i use the Zerg exploit it still seems to go over successfully (I realize this has a tenancy to mess with internal storage and only provide a temp root but i do not even get that temp root).
How would I unroot my device? Do you mean flash to stock and relock my boot loader?
As I said I have flashed several devices in the past (Atrix, eee pad transformer, HTC Inspire, HTC DINC, SAMSUNG GALAXY S T-Mobile) but I am not completely up to date on all of the technical terms...
Kraizk said:
Yes the device still says unlocked. That was one of the first things I checked... Haha....
As I said ive flashed the rooted CWM and it says it went over successfully.
If i use the Zerg exploit it still seems to go over successfully (I realize this has a tenancy to mess with internal storage and only provide a temp root but i do not even get that temp root).
How would I unroot my device? Do you mean flash to stock and relock my boot loader?
As I said I have flashed several devices in the past (Atrix, eee pad transformer, HTC Inspire, HTC DINC, SAMSUNG GALAXY S T-Mobile) but I am not completely up to date on all of the technical terms...
Click to expand...
Click to collapse
Yes, I mean relock the bootloader and back to stock rom, then try again. Do you know how to get back to stock?
slapshot30 said:
Yes, I mean relock the bootloader and back to stock rom, then try again. Do you know how to get back to stock?
Click to expand...
Click to collapse
actually that one I do not know how to do... I realize this is probably somewhat annoying because I am sure you have said how to do it before.... Some help would be greatly appreciated
Kraizk said:
actually that one I do not know how to do... I realize this is probably somewhat annoying because I am sure you have said how to do it before.... Some help would be greatly appreciated
Click to expand...
Click to collapse
I haven't told anyone how to do it surprisingly, and I'm more than happy to help . I was honestly thinking about adding reverting back to stock to the superguide, and I think I just may do that. Here is the link. Pirateghost is the man.
http://forum.xda-developers.com/showpost.php?p=20821226&postcount=4
Thank you for this and all of your help, people like you and ghostpirate are why i still feel like I can turn to the XDA community. I will try this firs thing in the morning and give an update on how things went. I would try it tonight but lets be honest, its the 1st of the year and the last thing I need to be doing is messing with technology.....
Kraizk said:
Thank you for this and all of your help, people like you and ghostpirate are why i still feel like I can turn to the XDA community. I will try this firs thing in the morning and give an update on how things went. I would try it tonight but lets be honest, its the 1st of the year and the last thing I need to be doing is messing with technology.....
Click to expand...
Click to collapse
It's no problem, this isn't a dumb question or easy issue by any means. If the method I directed to you doesn't work, let me know. There is another way to do it without all the code.
slapshot30 said:
I haven't told anyone how to do it surprisingly, and I'm more than happy to help . I was honestly thinking about adding reverting back to stock to the superguide, and I think I just may do that. Here is the link. Pirateghost is the man.
http://forum.xda-developers.com/showpost.php?p=20821226&postcount=4
Click to expand...
Click to collapse
Worked perfectly. I flashed it back to stock using the thread you linked me to. Then I did the CWM Root method and so far so good. I appreciate all of your help
Nice, I'm glad you were able to get everything working.
Sent from my HTC PH39100 using xda premium

***Easiest Method for Keeping Root Thru the ZV8 Update***

Please Read Full Post Before Posting Any Questions!!! If You Ask A Question That Is Answered In This Post, It Will Not Get Answered!!!
Alrighty Boys and Girls!!! I have tried to make this as easy as possible for what we have!!! First and foremost, this will NOT root if you are already on ZV8!!!
Prerequisites
Pretty easy, you need ANY form of ZV7 (By any that includes stock, GingerVolt, Blitzkrieg, self modified, whatever) and CWM. Also, if you have frozen the software update app, make sure you unfreeze before anything!!!
1) Download this file: http://d-h.st/MeH
2) Flash that file in cwm
3) Reboot into the OS
4) Update to ZV8
That is it!!! You are now rooted stock ZV8!!!!
After gaining root on ZV8 you can get CWM recovery by running this ZV8CWMRecovery.bat: http://dl.dropbox.com/u/54501789/Revo/ZV8CWMRecovery.zip
There you have it!!! That was easy now wasn't it!
You are AMAZING! Very nice mtmichelson.
I'll give it a shot. What do we do if the OTA fails??
Edit:
OTA failed. Lol
Edit: fixed my market, broke my swype.
Edit: broke all sound and vibration. At work, can't take time to troubleshoot. Later, hopefully.
EDIT!
Holy effing facepalm, batman! I just realized what was killing the OTA.. And while I certainly feel like an idiot, I can assure you I am truly not one. Also, I refuse to disclose where I screwed the pooch.
Updating to zv8 now..
Edit:
Yup. It works. Ha!
Still not sound/vibration though. No worries, Im going to flash a clean zv7 and do this again in a bit.
I really should have waited until I was home to mess with this. Thanks MT!
Cal8192 said:
I'll give it a shot. What do we do if the OTA fails??
Edit:
OTA failed. Lol
Edit: fixed my market, broke my swype.
Edit: broke all sound and vibration. At work, can't take time to troubleshoot. Later, hopefully.
EDIT!
Holy effing facepalm, batman! I just realized what was killing the OTA.. And while I certainly feel like an idiot, I can assure you I am truly not one. Also, I refuse to disclose where I screwed the pooch.
Updating to zv8 now..
Edit:
Yup. It works. Ha!
Still not sound/vibration though. No worries, Im going to flash a clean zv7 and do this again in a bit.
I really should have waited until I was home to mess with this. Thanks MT!
Click to expand...
Click to collapse
This method does still take advantage of the local.prop file. Delete it from /data and reboot and you will have sound back. If you run the .bat it will remove it for you though.
Sent from my VS920 4G using Tapatalk
Awesome job MT! This was a life saver for me since my USB connection doesn't work! I was hoping the ZV8 upgrade might fix it, but it didn't. Oh well, at least now I'm on ZV8 with Break Out 1.1!!!
I had to enter the commands in Terminal Emulator by hand, which sucked. But hey, I got there...
sweet will try this later. i take it this means you dont want that update file anymore?
ejammer said:
sweet will try this later. i take it this means you dont want that update file anymore?
Click to expand...
Click to collapse
Nope, got it lol. Thanks!
Sent from my VS920 4G using Tapatalk
mtmichaelson said:
This method does still take advantage of the local.prop file. Delete it from /data and reboot and you will have sound back. If you run the .bat it will remove it for you though.
Click to expand...
Click to collapse
Yeah, that's what I figured. And since I was going to go fresh install after work I wasn't concerned. Thanks for helping a guy out, even if you did laugh at my previous post. It's cool, you can admit it. ; )
Cal8192 said:
Yeah, that's what I figured. And since I was going to go fresh install after work I wasn't concerned. Thanks for helping a guy out, even if you did laugh at my previous post. It's cool, you can admit it. ; )
Click to expand...
Click to collapse
No, I would never laugh at you lol
I know I am a complete noob for asking this, but what is the best way to execute the .bat file (.zip file, since we cannot install it with CWM)? I know I can adb, though I am foggy on the details since it has been a while. What are the steps that need to be taken to make sure that i direct terminal correctly towards my phone. I just want to make sure I do it right the first time. Thanks in advance!
Another dumb question again here. sorry, but....
To run the CWM Recovery bat file, I need to be hooked up to the computer, right?
I have done the update to ZV8, but I am at work and have no cable to connect to the computer. Did the first part through WIFI to get the files.
There is no way to run the bat file off the phone itself is there?
mtmichaelson said:
Please Read Full Post Before Posting Any Questions!!! If You Ask A Question That Is Answered In This Post, It Will Not Get Answered!!!
Alrighty Boys and Girls!!! I have tried to make this as easy as possible for what we have!!! First and foremost, this will NOT root if you are already on ZV8!!!
Prerequisites
Pretty easy, you need ANY form of ZV7 (By any that includes stock, GingerVolt, Blitzkrieg, self modified, whatever) and CWM.
1) Download this file: http://d-h.st/MeH
2) Flash that file in cwm
3) Reboot into the OS
4) Update to ZV8
That is it!!! You are now rooted stock ZV8!!!!
After gaining root on ZV8 you can get CWM recovery by running this ZV8CWMRecovery.bat: http://dl.dropbox.com/u/54501789/Revo/ZV8CWMRecovery.zip
There you have it!!! That was easy now wasn't it!
Click to expand...
Click to collapse
Dang that does sound easy, I guess that's what I get for being an early adopter.
Big Cam said:
Dang that does sound easy, I guess that's what I get for being an early adopter.
Click to expand...
Click to collapse
EXACTLY! Lol!
PS, worked like a charm. Awesome work mt!
Big Cam said:
Dang that does sound easy, I guess that's what I get for being an early adopter.
Click to expand...
Click to collapse
Nothing to see here anymore!!!
Sent from my VS920 4G using Tapatalk
Cal8192 said:
EXACTLY! Lol!
PS, worked like a charm. Awesome work mt!
Click to expand...
Click to collapse
Awesome! Thanks!
Sent from my VS920 4G using Tapatalk
eghill1125 said:
Another dumb question again here. sorry, but....
To run the CWM Recovery bat file, I need to be hooked up to the computer, right?
I have done the update to ZV8, but I am at work and have no cable to connect to the computer. Did the first part through WIFI to get the files.
There is no way to run the bat file off the phone itself is there?
Click to expand...
Click to collapse
Yes you need to be hooked to a computer and I assume you need to be in USB debugging mode and internet connection only. I felt bad because no one else answered.
As to pushing the file through ADB I have no idea I usually just use the simple connect and run by the means of MT's programz since they do it all for you anyways. Still denating to update though because I love my blitzkrieg...
Sent from my VS910 4G using xda premium
Thanks.
I figured as much. Will have to wait til after work then. It's been so long since I have done any updating on this phone, that I am forgetting how to do things.
I spend most of my time putting new Roms and stuff on my Nook Color and this stuff is new again to me.
Thanx a million
Will the phone info still say v7 after this. I flashed, all went fine, rebooted, all still good. Checked root, got it, but then checked phone info and it still says v7. I don't really care if it says v7 or what ever as long as I know it's v8. Thanks for all your time and effort dedicated to all of us Revo users MT.
buffettman03 said:
Will the phone info still say v7 after this. I flashed, all went fine, rebooted, all still good. Checked root, got it, but then checked phone info and it still says v7. I don't really care if it says v7 or what ever as long as I know it's v8. Thanks for all your time and effort dedicated to all of us Revo users MT.
Click to expand...
Click to collapse
You have to go into your settings and update now. The file doesn't upgrade for you.

[Q] Need Help! Tried rooting my Note 3 for the first time and now very inoperable

To start this off im going to say that i am very new to Android devices, ive owned my Note 3 (The AT&T SM-N900A one) for nearly three weeks now spending time researching on rooting and the methods, etc. Well i just tried to and didnt quite have much success.
I followed this guide and its steps very thoroughly. http://forum.xda-developers.com/showthread.php?t=2559715
Yet it all ended with it booting up looking like new but nearly every 3 seconds errors appear about processes crashing and trying to stop, for example "Unfortunately, Direct pen input has stopped."
After that failure i went ahead and tried to undo it which probably wasnt a good idea, i followed this tutorial: http://www.droidviews.com/how-to-unbrick-att-galaxy-note-3-sm-n900a/.
I ended up at the exact same place, same error over and over. Does anyone know how to fix this?
Thank you.
(I apologize if this had been brought up before i went searching but found nothing that was a solution to my problem.)
baileynapier said:
To start this off im going to say that i am very new to Android devices, ive owned my Note 3 (The AT&T SM-N900A one) for nearly three weeks now spending time researching on rooting and the methods, etc. Well i just tried to and didnt quite have much success.
I followed this guide and its steps very thoroughly. http://forum.xda-developers.com/showthread.php?t=2559715
Yet it all ended with it booting up looking like new but nearly every 3 seconds errors appear about processes crashing and trying to stop, for example "Unfortunately, Direct pen input has stopped."
After that failure i went ahead and tried to undo it which probably wasnt a good idea, i followed this tutorial: http://www.droidviews.com/how-to-unbrick-att-galaxy-note-3-sm-n900a/.
I ended up at the exact same place, same error over and over. Does anyone know how to fix this?
Thank you.
(I apologize if this had been brought up before i went searching but found nothing that was a solution to my problem.)
Click to expand...
Click to collapse
Have you performed a factory data reset since the last attempt?
440bro said:
Have you performed a factory data reset since the last attempt?
Click to expand...
Click to collapse
Yes i have,a few times, it just then reboots with the setup and that error still occurring.
baileynapier said:
Yes i have,a few times, it just then reboots with the setup and that error still occurring.
Click to expand...
Click to collapse
That error is a bugger to get rid of, if you even can. i had this happen and had to return my device to the store. BUT that was before we had a working back to stock MJ5 solution.
http://forum.xda-developers.com/showthread.php?t=2559715
If you were on MJ5 this will get you back to out of the box stock with or without Root, its up to you.
i have used this twice and has worked smoothly both times, just make sure you download the files needed and follow the steps.
the2rrell said:
That error is a bugger to get rid of, if you even can. i had this happen and had to return my device to the store. BUT that was before we had a working back to stock MJ5 solution.
http://forum.xda-developers.com/showthread.php?t=2559715
If you were on MJ5 this will get you back to out of the box stock with or without Root, its up to you.
i have used this twice and has worked smoothly both times, just make sure you download the files needed and follow the steps.
Click to expand...
Click to collapse
That is the method OP used to get root....
OP, you should have used Kingo... Now you will have to redo that whole process just to restore back to stock. You had a bad flash or a bad download.
Sent from my SM-N9005A using XDA Premium 4 mobile app
28248965 286a
the2rrell said:
That error is a bugger to get rid of, if you even can. i had this happen and had to return my device to the store. BUT that was before we had a working back to stock MJ5 solution.
http://forum.xda-developers.com/showthread.php?t=2559715
If you were on MJ5 this will get you back to out of the box stock with or without Root, its up to you.
i have used this twice and has worked smoothly both times, just make sure you download the files needed and follow the steps.
Click to expand...
Click to collapse
That was the method that originally got me into this situation and i just tried it again step by step and i am still having the issue.
One thing that has caught my eye is that this was my devices information before ever trying any rooting process or anything:
MODEL NUMBER: SAMSUNG-SN-N900A
ANDROID VERSION: 4.3 (Jelly Bean)
BASEBAND VERSION: N900AUCUBNB4
KERNEL INFO -
3.4.0-1625098
se.i[email protected] #1
Mon Feb 10 21:13:28 KST 2014
BUILD NUMBER: JSS15J.N900AUCUBNB4
SELINUX STATUS: Enforcing
Is there any possible way to get it back to being a BNB4 device like the information above?
graydiggy said:
That is the method OP used to get root....
OP, you should have used Kingo... Now you will have to redo that whole process just to restore back to stock. You had a bad flash or a bad download.
Sent from my SM-N9005A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
tis the reason i directed him back to that thread. i know they are working on a easier odin flash to return to stock in another thread. dont know why he was using that to get root, but he will now need to use it to get booting back to normal again.
anyway, apologies for not being more clear.
so to sum it all up, redownload the files in case you got a bad one and repeat the process my good sir.
the2rrell said:
tis the reason i directed him back to that thread. i know they are working on a easier odin flash to return to stock in another thread. dont know why he was using that to get root, but he will now need to use it to get booting back to normal again.
anyway, apologies for not being more clear.
so to sum it all up, redownload the files in case you got a bad one and repeat the process my good sir.
Click to expand...
Click to collapse
Okay, thank you guys very much but its back to functioning properly! :victory:
Now am i just trying to accomplish a root, but that doesnt seem to be working, after i put the root de la vega files onto the sdcard SuperSU never installs upon restart, why is it not auto-installing like it seems to be expressed as in the tutorial?
EDIT: Okay guys, nevermind about the root, i just used Kingo.
baileynapier said:
Okay, thank you guys very much but its back to functioning properly! :victory:
Now am i just trying to accomplish a root, but that doesnt seem to be working, after i put the root de la vega files onto the sdcard SuperSU never installs upon restart, why is it not auto-installing like it seems to be expressed as in the tutorial?
Click to expand...
Click to collapse
use kingo 1.1.8 it is a lot easier
baileynapier said:
ive owned my Note 3 (The AT&T SM-N900A one) for nearly three weeks now spending time researching on rooting and the methods, etc.
Click to expand...
Click to collapse
How did you NOT find Kingo right away?
What kind of research did you do for 3 weeks? lol
Well, I'm glad you're good to go now. The devs on this site are exceptional and you are lucky to have them. (me too).
baileynapier said:
Okay, thank you guys very much but its back to functioning properly! :victory:
Now am i just trying to accomplish a root, but that doesnt seem to be working, after i put the root de la vega files onto the sdcard SuperSU never installs upon restart, why is it not auto-installing like it seems to be expressed as in the tutorial?
EDIT: Okay guys, nevermind about the root, i just used Kingo.
Click to expand...
Click to collapse
So how did you get it back functioning properly? I am at the same point. I bricked my N3 screwing around with getting Face Unlock to work. So I followed the steps of Restore for MJ5 post, and immediately upon the final boot into setup, the Direct Pen Input error started, and makes the device useless. What fixed yours?
Re-download all the files and retry. Also, verify the size. I think you may have a corrupt file somewhere.
And factory reset after installing a ROM, even if it's the same ROM you had. Any ROM, on any phone, not just this one. Different ROMs store data in different locations, and if a ROM picks up the data from a previous ROM, that may bot be the data it wants, so it causes things to crash.
Ok thanks for the replies. I actually tried a factory reset after seeing the error, but it didn't help at all. And I did run a checksum on the only file that displayed a number, when I originally downloaded the files. But as would be expected, after all simple efforts to fix the issue failed, I started fresh on a whole different PC, downloaded all of the files again, used a different USB cable, and installed everything all over again. And low and behold, the second time was a total success. I can't explain what made the difference, and the checksum result showed an accurate download both times. But this is the nature of the beast isn't it?
Thanks,

[Q] Newly Rooted LG G2, Tried Installing TWRP, Recovery not Working

Hi all,
I searched the forums and I'm not finding any information pertaining to my situation (or I'm getting bogged down and skipping over things that would pertain to my situation). I do apologize, but I've been searching for a few hours now and I can't figure this out.
I just rooted my phone this evening. I was following the directions on the cyanogenmod website and things got confusing when it started talking about Clockworkmod and TWRP. Installed clockwork and rebooted into recovery and couldn't figure out how to flash. So I started looking at youtube vids and I saw people using TWRP. So I downloaded it from the play store and that's when things took a turn for the worse.
I opened up the app, I went to Install TWRP, picked my g2vzw and started Install Recovery. The app started downloading the open recovery file and then I got a popup saying "WARNING Ensure the partition listed below is the correct one for your device...etc. and at the bottom it had "/dev/block/platform/msm_sdcc.1/by-name/recovery". I didn't know how to verify and I figured it was right (my idiot mistake), so I hit yes.
After I did that, I looked at clockwork again and saw an option to Install ROM from SD Card. When I hit that, I saw all the directories on my phone, so I figured I could dump the cyanogenmod zip file onto my phone via Android File Transfer and go back into Clockwork and flash the file.
So when I did that the phone rebooted and I got the white text at the top of my screen with Secure Booting Error and then the phone shuts off and I have to press and hold the power button a good while until the phone boots back up.
So is happening as a result of what I did using TWRP? Is there anything I can do to fix this? I would really like to experience different ROMs. I hope all is not lost.
Like I said, I'm using a Mac and I haven't used Terminal in a while. The only reason I was able to root was because the root folder I downloaded had an executable for Terminal that did everything for me.
Thanks in advance for your help!
i did the same i attempted to use ez unlock to unlock bootloader and just twrp manager to flash twrp. after trying to reboot i get no text no logo just a black screen and when holding the buttons it vibrates with an occasional red light can turn on and off just a black screen though shows in pc as bulk drive....on windows.....please help i only had the thing for a couple hrs.
Have either of you tried returning to stock using the kdz or tot method? It might save you...
I'm taking about this:
http://forum.xda-developers.com/showthread.php?t=2448960
---------- Post added at 11:21 PM ---------- Previous post was at 11:18 PM ----------
Me personally, if it's not on xda, I don't use it (concerning root/recovery). Using ioroot25 for root and freedom tool for recovery (or autorec)...
njstein said:
Have either of you tried returning to stock using the kdz or tot method? It might save you...
I'm taking about this:
http://forum.xda-developers.com/showthread.php?t=2448960
---------- Post added at 11:21 PM ---------- Previous post was at 11:18 PM ----------
Me personally, if it's not on xda, I don't use it (concerning root/recovery). Using ioroot25 for root and freedom tool for recovery (or autorec)...
Click to expand...
Click to collapse
Thanks! I tried the KDZ method last night and it didn't work. I'm performing the TOT method as I type (waiting for the ROM to finish downloading). I'll let you know what happens.
shaka411 said:
Thanks! I tried the KDZ method last night and it didn't work. I'm performing the TOT method as I type (waiting for the ROM to finish downloading). I'll let you know what happens.
Click to expand...
Click to collapse
I could never get kdz to work either, aggravates me but the tot method did! Hopefully it works out for you...
njstein said:
I could never get kdz to work either, aggravates me but the tot method did! Hopefully it works out for you...
Click to expand...
Click to collapse
So I was using VMware and it stalled out during step 3 of the thread you linked. So frustrationg, I've been at this all day to end up getting no where. Now I have to get bootcamp installed and retry this whole thing. So much time to do something so little. Ugh.
shaka411 said:
So I was using VMware and it stalled out during step 3 of the thread you linked. So frustrationg, I've been at this all day to end up getting no where. Now I have to get bootcamp installed and retry this whole thing. So much time to do something so little. Ugh.
Click to expand...
Click to collapse
VMware?
njstein said:
VMware?
Click to expand...
Click to collapse
Yes, it's a virtual machine that allows me to use Windows on my Mac's desktop without having to partition my hard drive and use Boot Camp.
shaka411 said:
Yes, it's a virtual machine that allows me to use Windows on my Mac's desktop without having to partition my hard drive and use Boot Camp.
Click to expand...
Click to collapse
Ahhh, yes. Interesting. I'm assuming it'll work. Why not? But if you keep getting that same problem, try a Windows desktop.
njstein said:
Ahhh, yes. Interesting. I'm assuming it'll work. Why not? But if you keep getting that same problem, try a Windows desktop.
Click to expand...
Click to collapse
It worked!!! You are the man!!! Now that I have the phone back to normal and Windows up and running, I would very much like to root and install cyanogenmod the Right way, especially the boot loader part, having to do with the loki master (that I didn't do the first time around), would happen to know a good thread that will help me?
Again, thank you so much. I was nervous that I wouldn't be able to fix this. The TOT method was awesome.
shaka411 said:
It worked!!! You are the man!!! Now that I have the phone back to normal and Windows up and running, I would very much like to root and install cyanogenmod the Right way, especially the boot loader part, having to do with the loki master (that I didn't do the first time around), would happen to know a good thread that will help me?
Again, thank you so much. I was nervous that I wouldn't be able to fix this. The TOT method was awesome.
Click to expand...
Click to collapse
Ya, bro, this thread:
http://forum.xda-developers.com/showthread.php?p=51826092
The OP has a link for ioroot25 (which is the best way to root) and the freedom tool installs twrp. The steps are fairly straightforward but if you have questions, let me know! These are both for kitkat (so if you haven't, update) and you don't even have to worry about the bootloader. Updating to kk also erases some steps if you go the cm route. Also, do not use the "official" cm. It uses 4.2.2 base (crappy builds). Use JackpotCalvin's CM11, from what I've read it's top-notch.
Make sure you have ALL drivers for the phone installed before you start (including the adb drivers and debugging).
Glad you got it fixed, like I said, don't hesitate to ask if you have any doubts (easier to solve of you haven't done anything)!
As far as drivers, since I had to install them so that I could go back to stock, I should be good right?
ioroot25 is great, because it comes with "ioroot.tool" which is one click root for Macs.
njstein said:
Ya, bro, this thread:
http://forum.xda-developers.com/showthread.php?p=51826092
The OP has a link for ioroot25 (which is the best way to root) and the freedom tool installs twrp. The steps are fairly straightforward but if you have questions, let me know! These are both for kitkat (so if you haven't, update) and you don't even have to worry about the bootloader. Updating to kk also erases some steps if you go the cm route. Also, do not use the "official" cm. It uses 4.2.2 base (crappy builds). Use JackpotCalvin's CM11, from what I've read it's top-notch.
Make sure you have ALL drivers for the phone installed before you start (including the adb drivers and debugging).
Glad you got it fixed, like I said, don't hesitate to ask if you have any doubts (easier to solve of you haven't done anything)!
Click to expand...
Click to collapse
I guess I am already confused by the post. I know how to do the root. I can just run ioroot25, but then do I do the Recovery steps? And which link am I clicking the "One Click custom recovery TWRP for 12b ota. If your on 11a, do OTA first. Must have root also." or the "Then flash this in recovery if you wants TWRP 2.7: Thanks MindRocket"?
UPDATE
shaka411 said:
I guess I am already confused by the post. I know how to do the root. I can just run ioroot25, but then do I do the Recovery steps? And which link am I clicking the "One Click custom recovery TWRP for 12b ota. If your on 11a, do OTA first. Must have root also." or the "Then flash this in recovery if you wants TWRP 2.7: Thanks MindRocket"?
Click to expand...
Click to collapse
So I ran ioroot25 on Windows. Do I skip the "Recovery Section" and go straight to the "KITKAT 24A OTA FREEDOM" section? Sorry, I just want to be Really sure of what I'm doing this time, last time I went into this on my own thinking I knew what I was doing and we all know how that ended up.
Thanks!
shaka411 said:
So I ran ioroot25 on Windows. Do I skip the "Recovery Section" and go straight to the "KITKAT 24A OTA FREEDOM" section? Sorry, I just want to be Really sure of what I'm doing this time, last time I went into this on my own thinking I knew what I was doing and we all know how that ended up.
Thanks!
Click to expand...
Click to collapse
Root it with ioroot25, find the proper Autorec for vs980, install the app on your phone and run it to install recovery.
shaka411 said:
I guess I am already confused by the post. I know how to do the root. I can just run ioroot25, but then do I do the Recovery steps? And which link am I clicking the "One Click custom recovery TWRP for 12b ota. If your on 11a, do OTA first. Must have root also." or the "Then flash this in recovery if you wants TWRP 2.7: Thanks MindRocket"?
Click to expand...
Click to collapse
shaka411 said:
So I ran ioroot25 on Windows. Do I skip the "Recovery Section" and go straight to the "KITKAT 24A OTA FREEDOM" section? Sorry, I just want to be Really sure of what I'm doing this time, last time I went into this on my own thinking I knew what I was doing and we all know how that ended up.
Thanks!
Click to expand...
Click to collapse
Correct! Go to 24a ota freedom section. I've used it multiple times and never had an issue. It has the bat extension like ioroot25, just click and follow directions.
Autorec is another option (as mentioned) but I know nothing about it. As always, your choice!
njstein said:
Correct! Go to 24a ota freedom section. I've used it multiple times and never had an issue. It has the bat extension like ioroot25, just click and follow directions.
Autorec is another option (as mentioned) but I know nothing about it. As always, your choice!
Click to expand...
Click to collapse
So I hope I did this right. I started up the KitKat Freedom and pressed enter. And this what the command line said:
* server not running *
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Then my phone was automatically disconnected and then reconnected. Is that it? I figured the process would be longer.
shaka411 said:
So I hope I did this right. I started up the KitKat Freedom and pressed enter. And this what the command line said:
* server not running *
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Then my phone was automatically disconnected and then reconnected. Is that it? I figured the process would be longer.
Click to expand...
Click to collapse
Nevermind, it worked! I don't know what happened, maybe my USB Cable was loose or I didn't wait long enough, but I ran the program and waited and everything worked. I booted into recovery and Teamwin popped up (man we're really making progress!). So now I gotta get cyanogenmod. Should I just do a search for JackpotCalvin's, and once I find it how do I flash it?
shaka411 said:
Nevermind, it worked! I don't know what happened, maybe my USB Cable was loose or I didn't wait long enough, but I ran the program and waited and everything worked. I booted into recovery and Teamwin popped up (man we're really making progress!). So now I gotta get cyanogenmod. Should I just do a search for JackpotCalvin's, and once I find it how do I flash it?
Click to expand...
Click to collapse
So I did some searching and I found this post: http://forum.xda-developers.com/showthread.php?t=2702958
Step 5 makes me nervous (seems like we've come so far, I hate to screw up now), and he saying this is off of Jelly Bean. I thought CM11 was based off of KitKat.
Once again, never mind I already did step 5 by doing KitKat Freedom. Looks like all I really have to do is download Jackpot's build, transfer it to my phone and install using TWRP.
Just backed up everything. I'll let you know how it works out!
shaka411 said:
So I did some searching and I found this post: http://forum.xda-developers.com/showthread.php?t=2702958
Step 5 makes me nervous (seems like we've come so far, I hate to screw up now), and he saying this is off of Jelly Bean. I thought CM11 was based off of KitKat.
Once again, never mind I already did step 5 by doing KitKat Freedom. Looks like all I really have to do is download Jackpot's build, transfer it to my phone and install using TWRP.
Just backed up everything. I'll let you know how it works out!
Click to expand...
Click to collapse
My friend. Everything worked perfectly. I have Jackpot's build running and I got the Google Apps installed and running. Thank you so much for your help. That was quite an experience, I'm glad I had you leading every step of the way.

Categories

Resources