Related
im having some serious issues with my SU.
i tried temporizer's fix with no help.
it started a while ago when i flashed a theme and i could never get it back.
Ive tried EVERYTHING (to my knowledge which is definitely not vast lol) to no avail. and from what temp and a couple others have told me its a problem with cyan recovery 1.3, but now i cant flash to 1.4. im stuck with no SU, no way to flash a new recovery and pretty much half ass phone. ive never had this type of problem since i rooted back in januaryish. any help would be much appreciated.
anon1ski said:
im having some serious issues with my SU.
i tried temporizer's fix with no help.
it started a while ago when i flashed a theme and i could never get it back.
Ive tried EVERYTHING (to my knowledge which is definitely not vast lol) to no avail. and from what temp and a couple others have told me its a problem with cyan recovery 1.3, but now i cant flash to 1.4. im stuck with no SU, no way to flash a new recovery and pretty much half ass phone. ive never had this type of problem since i rooted back in januaryish. any help would be much appreciated.
Click to expand...
Click to collapse
Download cyan's recovery 1.4 to your sdk tools folder, start the phone in fastboot mode [back+power] folder and run:
Code:
fastboot boot cm-recovery-1.4.img
That should boot the recovery image and you can work from there to reflash whatever you want.
sdk tools folder? and that would beeeeeeee?
apparently im not as savvy as i once thought..... lol
anon1ski said:
sdk tools folder? and that would beeeeeeee?
apparently im not as savvy as i once thought..... lol
Click to expand...
Click to collapse
Errr... you don't have the sdk?
You don't use adb...?!
That's like trying to play football with no limbs..
Get yourself rigged up with this:
http://developer.android.com/sdk/1.5_r3/installing.html
btw.. you won't need to set up eclipse or the adt plugin for this, just make sure your environment variables and java paths are set up as per the guide.
well while football WITH limbs does sound much less entertaining, i am normally no where near a computer, and do almost everything right from my phone.... and i mean everything..... i download all my roms, themes, etc. right to my download folder, find em', rename em' flash em' and im good to go. i went on a computer to get the recovery simply because it downloads wrong on my phone and saves as a text file, seems like it does the same on mozilla for some people but i got it in .img form and its on the root of my card, and nothing.
anon1ski said:
well while football WITH limbs does sound much less entertaining, i am normally no where near a computer, and do almost everything right from my phone.... and i mean everything..... i download all my roms, themes, etc. right to my download folder, find em', rename em' flash em' and im good to go. i went on a computer to get the recovery simply because it downloads wrong on my phone and saves as a text file, seems like it does the same on mozilla for some people but i got it in .img form and its on the root of my card, and nothing.
Click to expand...
Click to collapse
I do a lot of stuff from my phone too tbh, Somehow it satisfies my geek cravings more fully.. But adb is massively useful when you're on the pc.. saves a lot of cramped typing on the device keyboard.
Fastboot will be your saviour in this case though, and you're gonna need a proper box to run that on.
i have NO idea what im doing with adb, i just downloaded it and im just starign at my screen like it tried to feed me a cheeseburger.....
anon1ski said:
i have NO idea what im doing with adb, i just downloaded it and im just starign at my screen like it tried to feed me a cheeseburger.....
Click to expand...
Click to collapse
lol.. adb is pretty simple.. a few examples:
Code:
adb push localpath devicepath # push files to your phone eg: adb push c:\update.zip /sdcard
adb pull devicepath localpath # pull files from device
adb shell # basically a terminal running on your device that you control from your pc.. im sure you can figure this out if you do everything from your phone.
adb shell reboot # guess?
adb shell reboot recovery # go straight to recovery without holding any buttons
fastboot should be in the same folder as adb.. you can use it to flash .img files from the pc or just boot the images without flashing them.
how do i run fastboot, adb, etc. in relation to them running processes on my phone.
i downloaded everything. i just dont know how to run it or if i have to run a couple things, have my phone in recovery or fastboot(im guessing).
god. i feel like a moron.
anon1ski said:
how do i run fastboot, adb, etc. in relation to them running processes on my phone.
i downloaded everything. i just dont know how to run it or if i have to run a couple things, have my phone in recovery or fastboot(im guessing).
god. i feel like a moron.
Click to expand...
Click to collapse
Assuming you're on windows, you'll have to install the adb driver first (not the standard android that windows installs automatically, theres a seperate driver in the usb_driver folder of the sdk). You also need to enable usb debugging on your phone.
Follow this guide if you need to:
http://forum.xda-developers.com/showthread.php?t=532719
You can use adb whatever mode your phone is in.. even when its stuck in a bootloop usually. You don't need to be running anything on the phone, the drivers are switched on by init.rc.
Fastboot can only be run with the phone in fastboot mode (surpisingly).
thanka alot man. im gonna give this all a try.
Good luck
ok. got adb running. ran the command you gave me. it brings up 1.4 but doesnt push it to my phone...... can i actually INSTALL 1.4 from fastboot/adb?
nevermind. figured it out. used common sense and just ran fastboot flash recovery recovery.img and it worked. thanks for everything
my super user still wont work.; so apparently it had nothing to do with the recovery..... im going to wipe, reflash cyan 3.9.1. and see if that works.
Would really appreciate some help here guys...
basically i have a new SLCD nexus one with Ramons 1.8.01 recover image.
I tried uploading a few roms but none of them worked..
so I'm trying to restore one of two nandroid backups i made before i started messing..
on the phone if i go into recovery and select nandroid restore then i get an error telling me to run nandroid-mobile.sh via ADB.
So, i set up adb, follow a guide (here) and end up with an error saying
error: unyaffs not found in path
does anyone know how i can get that backup working???
I've attached a copy of my cmd window..
Any help would be gratefully appreciated
Quick update, I have Cyanogen 6.0.0 working on the phone now..
But i'd still like to be able to restore!
jamin100 said:
Would really appreciate some help here guys...
basically i have a new SLCD nexus one with Ramons 1.8.01 recover image.
I tried uploading a few roms but none of them worked..
so I'm trying to restore one of two nandroid backups i made before i started messing..
on the phone if i go into recovery and select nandroid restore then i get an error telling me to run nandroid-mobile.sh via ADB.
So, i set up adb, follow a guide (here) and end up with an error saying
error: unyaffs not found in path
does anyone know how i can get that backup working???
I've attached a copy of my cmd window..
Any help would be gratefully appreciated
Click to expand...
Click to collapse
I would suggest trying to type the directory instead of using default. When the restore prompts you to either type the directory or hit enter... instead of hitting enter type:
/sdcard/nandroid/HT08BP800418/BCDS-20100911-2252
See if it gives you the same error.
NOTE: That IS case sensitive.
Thanks for your reply, unfortunately it does give the same error, I have 3 nandroid backups but cant restore any of them which is worrying incase anything happens to the phone!
Please help
Try this... while in the shell... type the following:
Code:
ls -l /sdcard/nandroid/HT08BP800418/BCDS-20100911-2252
It should bring up a list of 5 files. Go ahead and attach a screen if you can if you are getting a list of files. If not let me know what error you get.
Thanks for your help,
here's the screen shot
Nobody encountered this problem?
Ok... sorry had you look in the wrong place. I thought it was looking in the directory with the image in it for what it needed. I just looked at the nandroid code. Turns out... it looks for some executables that are required for the script to run. It doesn't have to do with your image and I think your images are probably fine.
I need you to run 2 more commands so I can see where the problem is. First run:
Code:
env
Next run:
Code:
which unyaffs
The "env" command should show your enviroment variables. What we are looking for is for /system/bin to be in your "PATH" variable. It should be because it checks for another executable first "flash_image" and it is not coming up with an error. The second file it is checking for is "unyaffs". Next you need to check and make sure unyaffs is actually in your /system/bin folder. It is probably not... and would explain the error you are getting.
I guess my first question is... is this happening on all ROMs you have tried (or have you only gotten one up and running)? If it is there may have been a problem when you flashed it. Even though it is possible that you could copy it to the /system/bin I would suggest not doing this. The reason is because if that one file is missing... there may be other files missing that should be there from when you flashed your ROM. These missing files... if there are any... could cause problems later. It might be best just to reflash whatever ROM you are using. I would suggest CM6 (not nighties) and then moving to some other ROM once you get a "known good" to work with.
Hey GoblinLord,
Thanks for your help on this, really appreciate it..
OK, well i've ran the two commands that you said and have attached the screenshot with the output. I've tried going to /system/bin but get permission denied errors through adb.
Although it looks like the PATH is actually /sbin rather than /system/bin ???
As for the roms..
I'm currently using CM6 (the stable version) as this was the only one that I could manage to get to work. As this is a SLCD nexus i dont think there are many roms that have the right drivers for the screen. Its does work fine though.. The nandroid restore is the only part of the phone that i cannot get working....
Again thanks for the help...
jamin100 said:
Hey GoblinLord,
Thanks for your help on this, really appreciate it..
OK, well i've ran the two commands that you said and have attached the screenshot with the output. I've tried going to /system/bin but get permission denied errors through adb.
Although it looks like the PATH is actually /sbin rather than /system/bin ???
As for the roms..
I'm currently using CM6 (the stable version) as this was the only one that I could manage to get to work. As this is a SLCD nexus i dont think there are many roms that have the right drivers for the screen. Its does work fine though.. The nandroid restore is the only part of the phone that i cannot get working....
Again thanks for the help...
Click to expand...
Click to collapse
Hmmm... the permission denied is normal. That is because it is a folder and not an executable. You should be able to do:
Code:
ls -l /system/bin
This will list what is in your /system/bin directory. As for your path being different... that seems a bit strange. I am doing the commands from a terminal on my device... once I get back home today I will do it through the ADB shell and see what I get. The "which" command will only look in the folders in your "PATH" variable for the executable. If /system/bin is not in there I am not sure how it is passing the part where it looks for "flash_image". In my sbin folder I only have the ADB daemon (adbd) executable. What you could do is manually add the /system/bin to your PATH variable while in the shell... that may work. You can try the following:
Code:
PATH=$PATH:/system/bin
Run that before running your restore command. That should manually place the directory you need into your PATH environment variable. I will do a little testing with ADB once I get home and update this if I get to before you try it.
Thanks for the reply....
I won't be able to try this until Wednesday as I have left the USB cable at work ....
I will try it Wednesday and let you know...
Thanks
Sent from my Nexus One using XDA App
jamin100 said:
Thanks for the reply....
I won't be able to try this until Wednesday as I have left the USB cable at work ....
I will try it Wednesday and let you know...
Thanks
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
I checked my environment variables via ADB. Mine did show the /system/bin in my PATH variable. Seeing as this is a shell being run on your device... I would still venture to say that something may have went wrong when you flashed your ROM originally. That or something you installed changed it for some crazy reason (and shouldn't have). Either way, I still think it would be best to flash again... possibly to a different version. I know you would have had to get a modified version of CM6 so... if you don't mind me asking where did you get your copy?
EDIT: Correction... I am getting the same path variable as you when in recovery mode. I am not quite sure why this is... the guide I found for using nandroid restore through ADB doesn't seem to run into this issue. It might be some kind of issue related to just Amon_Ra recovery. This would mean that Amon_Ra Recovery just didn't add it to the PATH variable... which I guess is rather odd... but whatever. Just try manually adding it to the PATH variable as mentioned above and then run the restore. It should work then.
EDIT 2: I did a bit of researching on that error you are getting when you try and restore in recovery. Reference:
http://forum.xda-developers.com/showthread.php?t=621940
Various people point to things that may cause this error. Is your phone charged? Do you have plenty of space on your SD card?
I'm rooted and am trying to mount the system to remove bloatware apps... However everytime Titanium Backup removes it and I reboot it's still there...
Anyone have any ideas?
System is protected: you can't modify it while the phone is booted. You'll have to make a zip or whatever to delete it in recovery.
You have to be kidding me...
I've spent all day long trying to root this bastard phone and that didn't work then I managed it and now I can't disable, remove any apps ?
So much for HTC being dev friendly
fkofilee said:
You have to be kidding me...
I've spent all day long trying to root this bastard phone and that didn't work then I managed it and now I can't disable, remove any apps ?
So much for HTC being dev friendly
Click to expand...
Click to collapse
It seriously took you all day to root? What went wrong?
Did you try just freezing the app instead?
Brand new trick from HTC?Didn't have it in hox+
Sent from my Nexus 4 using Tapatalk 2
afilopou said:
Brand new trick from HTC?Didn't have it in hox+
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
So you can no longer go into ES explorer, mount root/system go to system > apps and delete whatever you want ?
Sent from my HTC Incredible S using Tapatalk 2
The recovery flashed but wouldnt boot , managed to get round it when i discovered POB with his superboot Thank god for the desire C
Then i realised that i couldnt flash anything because I manged to install 6.0.2.8 as a boot img, and 6.0.3.0 as a proper recovery.
Then i didnt have any files on the device to flash boohoo so i managed to get ADB sideload working through the AIO One Toolkit... And managed to flash AHRD finally getting a working device,
As you see Im a seasoned vet at these things but the HTC One has been the first device that has stumped me....
----------------------
The apps issue is not unkwown for HTC however they havent done this for a while.... Back with the G2 they did exactly the same thing and yes ive frozen them but there should be away to remove system apps for us through root.... But i cant remember how, Throwing it into ADB Shell and requesting SU along with a Remount works fine but still would like to remove the apps.
Im also looking for someone with a locked phone... (Sim Locked) i have a theory and it worked on the Desire C Anyone wanna help?
fkofilee said:
I'm rooted and am trying to mount the system to remove bloatware apps... However everytime Titanium Backup removes it and I reboot it's still there...
Anyone have any ideas?
Click to expand...
Click to collapse
Delete the apps with titanium and power off the phone. Don't do a restart.
Already tried that ^_^
You need to flash a custom kernel with a modified ramdisk to disable system protection Without doing that you're like deleting an app on windows with deepfreeze on it
Is that the only solution?
There are so many bloated useless and intrusive (cr)apps on this phone it's unbelievable.
Other solution is boot in recovery and delete it there. Either thru adb while in recovery mode, flashable zip or through file manager(if you're using TWRP). Other than that nope
Hmmm I'm thinking adb through recovery here but how do I got about doing this?
fkofilee said:
Hmmm I'm thinking adb through recovery here but how do I got about doing this?
Click to expand...
Click to collapse
the joys of a s-on devices
read up on adb commands...
or use the zip I attached and edit line 18 in this format with the apps you want to get rid of, use a file explorer to get the proper names.
make a backup first in case you mess up something
Code:
delete("/system/app/xxxxx.apk", "/system/app/xxxx.odex", "/data/app/xxxxx.apk");
The best way to remove apps in recovery is through adb:
Code:
adb shell
sysrw
rm /system/app/abc.apk
the simple way is ROM CLEANER, but isn't available yet for the One.
cheers
fkofilee said:
Hmmm I'm thinking adb through recovery here but how do I got about doing this?
Click to expand...
Click to collapse
type the following commands.
Code:
adb shell
su
cd /system/app/
ls
rm <insert the name of the apk you want to delete here which can be found in the list shown by the ls command>
Riyal said:
type the following commands.
Code:
adb shell
su
cd /system/app/
ls
rm <insert the name of the apk you want to delete here which can be found in the list shown by the ls command>
Click to expand...
Click to collapse
I dont have a One, and dont plan on having one (ever, thanks to this thread! I think I'll stick to Sony, they have instructions to unlocking bootloader on their official website)
BUT, if the system is locked, it should be locked trough ADB too, so I guess what I'd try is install busybox, custom recovery, go into recovery, connected it to the PC (or a mac, but since we're on no-apple forum, I'll assume PC), mounting system there and doing your thing.
You can install busybox and custom recovery right?
Edit: never mind, I should really learn to read. Sometimes I think I'm dyslexic a little, just for words, not letters.
I did not see the 'recovery' part mentioned.
Anywho, mounting system is what you forgot, so at least I said something helpful
ogdobber said:
the joys of a s-on devices
read up on adb commands...
or use the zip I attached and edit line 18 in this format with the apps you want to get rid of, use a file explorer to get the proper names.
make a backup first in case you mess up something
Code:
delete("/system/app/xxxxx.apk", "/system/app/xxxx.odex", "/data/app/xxxxx.apk");
Click to expand...
Click to collapse
MacHackz said:
The best way to remove apps in recovery is through adb:
Code:
adb shell
sysrw
rm /system/app/abc.apk
Click to expand...
Click to collapse
limx said:
the simple way is ROM CLEANER, but isn't available yet for the One.
cheers
Click to expand...
Click to collapse
Riyal said:
type the following commands.
Code:
adb shell
su
cd /system/app/
ls
rm <insert the name of the apk you want to delete here which can be found in the list shown by the ls command>
Click to expand...
Click to collapse
issak42 said:
I dont have a One, and dont plan on having one (ever, thanks to this thread! I think I'll stick to Sony, they have instructions to unlocking bootloader on their official website)
BUT, if the system is locked, it should be locked trough ADB too, so I guess what I'd try is install busybox, custom recovery, go into recovery, connected it to the PC (or a mac, but since we're on no-apple forum, I'll assume PC), mounting system there and doing your thing.
You can install busybox and custom recovery right?
Edit: never mind, I should really learn to read. Sometimes I think I'm dyslexic a little, just for words, not letters.
I did not see the 'recovery' part mentioned.
Anywho, mounting system is what you forgot, so at least I said something helpful
Click to expand...
Click to collapse
All Wonderful Ideas folks, however i had a go at this last night, it was a fricking nightmare even mounting ADB through recovery
Hey, all. So, I just got a Moto X through AT&T, and I'm looking to root it. It came with the 4.4 update already on it, so I've been trying to follow the appropriate guides from jcase, but I'm running into an error very early on. After I download the ADT bundle and get adb installed and have it up and running, I was at first finding that my device wasn't showing up when I did the command "adb devices". I fixed this by getting the drivers from motorola with their device manager download, but...
Now I'm getting it showing up as an unauthorized device. I have USB debugging enabled, to start. I never received an authorization option when plugging my phone into my computer. I have it set to PTP, not MTP. I've tried toggling the USB debugging off and on multiple times, I've tried the revoke usb debugging authorization multiple times, and I've gone through and deleted the .android folder in C->Users->me. Since I don't have root, I can't go through and delete any sort of folder in my phone involving adb, because I saw that a lot as I've been doing google searches on how to try and fix this before posting here. One of my attempts when deleting .android involved me unplugging my Moto X, deleting the .android folder, running adb kill-server and then adb start-server commands, and rebooting my Moto X before plugging it back in. I still have never received an option to authorize my device.
I am running on Windows 8.1, if that makes any difference. I checked my adb version using the command, and it shows me running adb version 1.0.31. I am rather new to playing around with phones and whatnot, and all of the things I have tried were things that I found through google searches that pointed me to threads here at XDA. I'm willing to try pretty much anything, and I will report back and give further information if needed.
Thanks in advance, all
Xenther said:
Hey, all. So, I just got a Moto X through AT&T, and I'm looking to root it. It came with the 4.4 update already on it, so I've been trying to follow the appropriate guides from jcase, but I'm running into an error very early on. After I download the ADT bundle and get adb installed and have it up and running, I was at first finding that my device wasn't showing up when I did the command "adb devices". I fixed this by getting the drivers from motorola with their device manager download, but...
Now I'm getting it showing up as an unauthorized device. I have USB debugging enabled, to start. I never received an authorization option when plugging my phone into my computer. I have it set to PTP, not MTP. I've tried toggling the USB debugging off and on multiple times, I've tried the revoke usb debugging authorization multiple times, and I've gone through and deleted the .android folder in C->Users->me. Since I don't have root, I can't go through and delete any sort of folder in my phone involving adb, because I saw that a lot as I've been doing google searches on how to try and fix this before posting here. One of my attempts when deleting .android involved me unplugging my Moto X, deleting the .android folder, running adb kill-server and then adb start-server commands, and rebooting my Moto X before plugging it back in. I still have never received an option to authorize my device.
I am running on Windows 8.1, if that makes any difference. I checked my adb version using the command, and it shows me running adb version 1.0.31. I am rather new to playing around with phones and whatnot, and all of the things I have tried were things that I found through google searches that pointed me to threads here at XDA. I'm willing to try pretty much anything, and I will report back and give further information if needed.
Thanks in advance, all
Click to expand...
Click to collapse
i also use mine on MTP but im running win7
issue def sounds like you did not allow the connection. have you tried uninstalling the drivers in device manager for the phone restarting and letting windows reinstall them and see if you can get the toast on your phone and accept it.
if that fails i would try competley reinstalling everything or trying another computer, another cable, another port.
dray_jr said:
i also use mine on MTP but im running win7
issue def sounds like you did not allow the connection. have you tried uninstalling the drivers in device manager for the phone restarting and letting windows reinstall them and see if you can get the toast on your phone and accept it.
if that fails i would try competley reinstalling everything or trying another computer, another cable, another port.
Click to expand...
Click to collapse
I tried PTP because people were saying that they were having better luck with phones in PTP, not MTP. I haven't tried uninstalling the drivers yet, which might be the issue. I tried initially just plugging my phone in before I downloaded the Motorola Device Manager program, so I'll try going through and uninstalling the drivers, and the MDM program, and then reinstalling (when I get home from work).
I'll try another port, and I can also try another computer, so I'll also do that when I get home. Thanks for your response, and I'm really hoping this works :good:
Xenther said:
I tried PTP because people were saying that they were having better luck with phones in PTP, not MTP. I haven't tried uninstalling the drivers yet, which might be the issue. I tried initially just plugging my phone in before I downloaded the Motorola Device Manager program, so I'll try going through and uninstalling the drivers, and the MDM program, and then reinstalling (when I get home from work).
I'll try another port, and I can also try another computer, so I'll also do that when I get home. Thanks for your response, and I'm really hoping this works :good:
Click to expand...
Click to collapse
i looked threw a couple threads of people having this issue. this is the order i would troubleshoot myself one other thing i have read is something about unsigned drivers which i dont think you should be having any issues with it but if you ever see a window that states about unsigned drivers reboot your PC while tapping F8 and tap the down arrow till you highlight Disable driver signature required i think is what it says and see if that helps
1. drivers only(make sure you restart after you remove the drivers and make sure you check the box for delete drivers)
2. different port
3. different cable
4. complete reinstall of adb and everything.( also restart after you uninstall everything.)
5. different computer (or use virtual PC if you don't have another PC)
6. re post here lol
Hope this all helps man
dray_jr said:
i looked threw a couple threads of people having this issue. this is the order i would troubleshoot myself one other thing i have read is something about unsigned drivers which i dont think you should be having any issues with it but if you ever see a window that states about unsigned drivers reboot your PC while tapping F8 and tap the down arrow till you highlight Disable driver signature required i think is what it says and see if that helps
1. drivers only(make sure you restart after you remove the drivers and make sure you check the box for delete drivers)
2. different port
3. different cable
4. complete reinstall of adb and everything.( also restart after you uninstall everything.)
5. different computer (or use virtual PC if you don't have another PC)
6. re post here lol
Hope this all helps man
Click to expand...
Click to collapse
Thanks again, so much, for all this! I'll go through all of these in about... two hours or so. I'll report back regardless of the outcome. You're awesome for this! :highfive:
No problem man hope it fixes your problem
Sent from my XT1056 using xda app-developers app
dray_jr said:
i looked threw a couple threads of people having this issue. this is the order i would troubleshoot myself one other thing i have read is something about unsigned drivers which i dont think you should be having any issues with it but if you ever see a window that states about unsigned drivers reboot your PC while tapping F8 and tap the down arrow till you highlight Disable driver signature required i think is what it says and see if that helps
1. drivers only(make sure you restart after you remove the drivers and make sure you check the box for delete drivers)
2. different port
3. different cable
4. complete reinstall of adb and everything.( also restart after you uninstall everything.)
5. different computer (or use virtual PC if you don't have another PC)
6. re post here lol
Hope this all helps man
Click to expand...
Click to collapse
So, I've done everything in this list, and also added trying forums.motorola.com/posts/caa12135bd?commentId=725256#725256 out. I'm pretty much out of ideas, because everything I've searched showed pretty much everything you've suggested (and that I tried!) as suggestions
I appreciate the help, but so far (at this rate), I think I might just not have to root. This is super frustrating to me!
EDIT: Actually, I think I finally have something here! After hooking it up to another computer, installing the adk and everything, making sure all the drivers showed up as installed correctly and getting nothing I pretty much resided to giving up. I, for whatever reason, decided to try and run adb. After I did, and ran the start-server command, it gave me the window to accept my laptop's fingerprint! Finally on to follow the rest of the guides!
Thanks!!!
Second edit: So, proceeding to step 3 or so in RockMyMoto, I'm encountering another issue. When running Impactor and trying to run telnet on port 2222 or whatever that is, I get an error that says Signature Bugs unavailable. If I'm understanding correctly, I have to do everything in this guide to downgrade to 4.2.2 or whatever the version with the camera update is, because there isn't a root available for 4.4 without downgrading. But now I'm seeing that I somehow need to downgrade from 4.4 to the previous version in order to get Impactor/telnet working correctly?
I'm super lost now :C
well in order to root 4.4 you have to downgrade to 4.2.2 camera update. if your not sure on how to do it here is a link to a video on how to do it
http://forum.xda-developers.com/showthread.php?t=2446515
and if you are having issues with telnet here is a guide that might help
http://forum.xda-developers.com/showthread.php?t=2509676
if after reading that if you are still lost i can setup remote access via Teamviewer and show you how to do it. but only if you are comfortable with it.
dray_jr said:
well in order to root 4.4 you have to downgrade to 4.2.2 camera update. if your not sure on how to do it here is a link to a video on how to do it
http://forum.xda-developers.com/showthread.php?t=2446515
and if you are having issues with telnet here is a guide that might help
http://forum.xda-developers.com/showthread.php?t=2509676
if after reading that if you are still lost i can setup remote access via Teamviewer and show you how to do it. but only if you are comfortable with it.
Click to expand...
Click to collapse
So I'm going to work on downgrading to 4.2.2 camera update right now. Thanks for all these links and offers for help :good:. I'll report back, hopefully with a successful root
EDIT: A question for you. Am I able to run my phone in ART runtime after I root it, should I stay in dalvik or w/e it is, or does it not matter?
Xenther said:
So I'm going to work on downgrading to 4.2.2 camera update right now. Thanks for all these links and offers for help :good:. I'll report back, hopefully with a successful root
EDIT: A question for you. Am I able to run my phone in ART runtime after I root it, should I stay in dalvik or w/e it is, or does it not matter?
Click to expand...
Click to collapse
i wouldn't see why not but i am not sure
26344422579
dray_jr said:
i wouldn't see why not but i am not sure
Click to expand...
Click to collapse
Alright, cool. I'll make a backup after I'm done with everything and try it out. Maybe do some poking around here first, see if it came up at all.
I've hit a few snags, but so far I've figured everything out. I'm working on doing SlapMyMoto right now, which is the last step for root and to be on 4.4, yeah?
Xenther said:
Alright, cool. I'll make a backup after I'm done with everything and try it out. Maybe do some poking around here first, see if it came up at all.
I've hit a few snags, but so far I've figured everything out. I'm working on doing SlapMyMoto right now, which is the last step for root and to be on 4.4, yeah?
Click to expand...
Click to collapse
correct
dray_jr said:
correct
Click to expand...
Click to collapse
I didn't want to bug you with this, so I had made a post over in the SlapMyMoto thread, but I'll put it up here. If you don't wanna bother, I'll hang around in the SMM thread and wait for a response.
"I've done everything from 1-3, including accepting and installing the OTA update to 4.4. I'm trying to run the last command in step 4, the adb shell stuff, but literally nothing is happening. I still have access from motowpnomo, I checked using the write_protect command, and it is still showing a "0" I don't know what to do at this point, though.
USB Debugging is on, adb devices shows my phone as being connected correctly
This is a screen cap of what my command prompt shows after I input that command from step 4
http://i.imgur.com/WeekMAf.png
Any suggestions?"
Xenther said:
I didn't want to bug you with this, so I had made a post over in the SlapMyMoto thread, but I'll put it up here. If you don't wanna bother, I'll hang around in the SMM thread and wait for a response.
"I've done everything from 1-3, including accepting and installing the OTA update to 4.4. I'm trying to run the last command in step 4, the adb shell stuff, but literally nothing is happening. I still have access from motowpnomo, I checked using the write_protect command, and it is still showing a "0" I don't know what to do at this point, though.
USB Debugging is on, adb devices shows my phone as being connected correctly
This is a screen cap of what my command prompt shows after I input that command from step 4
http://i.imgur.com/WeekMAf.png
Any suggestions?"
Click to expand...
Click to collapse
everything looks fine bro just finish the last command and then run root checker you should be fine.
i know when i ran mine nothing happened also, after the last command wait a few mins if nothing happens toggle Bluetooth like is says and if it does not restart then restart the phone and you should be good if not we will figure it out
i might downgrade just to run back threw it to see if i can figure it out and maybe put together a package for you that i know works. but i am on the sprint X
dray_jr said:
everything looks fine bro just finish the last command and then run root checker you should be fine. i know when i ran mine nothing happened also, after the last command wait a few mins if nothing happens toggle Bluetooth like is says and if it does not restart then restart the phone and you should be good if not we will figure it out
Click to expand...
Click to collapse
I'm confused again; when I run the last command (I literally just copypasted the entire fourth step command into my command promt), I get an error.
http://i.imgur.com/yr11VjL.png
Screenshot of after I type in the last command
I'm about to head out to work, so I'll be able to work on this later tonight, but if you have any suggestions I would be super appreciative (not to say that I already am not!)
Xenther said:
I'm confused again; when I run the last command (I literally just copypasted the entire fourth step command into my command promt), I get an error.
http://i.imgur.com/yr11VjL.png
Screenshot of after I type in the last command
I'm about to head out to work, so I'll be able to work on this later tonight, but if you have any suggestions I would be super appreciative (not to say that I already am not!)
Click to expand...
Click to collapse
no no do them one by one
adb shell
enter
cp /sdcard/install.sh /data/local/tmp/install.sh
enter
chmod 755 /data/local/tmp/install.sh
enter
echo "/data/local/tmp/install.sh" > /sys/kernel/uevent_helper
enter
and the device should restart
im running a nandroid backup as we speak and im going to revert back to the 4.2.2 camera update and run threw it again see if i can't figure out what is hanging u up.
dray_jr said:
no no do them one by one
adb shell
enter
cp /sdcard/install.sh /data/local/tmp/install.sh
enter
chmod 755 /data/local/tmp/install.sh
enter
echo "/data/local/tmp/install.sh" > /sys/kernel/uevent_helper
enter
and the device should restart
im running a nandroid backup as we speak and im going to revert back to the 4.2.2 camera update and run threw it again see if i can't figure out what is hanging u up.
Click to expand...
Click to collapse
Alright, I tossed the adb stuff on my flash drive, and I'm going to see if I can try this at work. I'll report back. You are going above and beyond to help me out, and it's just amazing. After my last community being the League of Legends community, I'm not used to this! :highfive:
dray_jr said:
no no do them one by one
adb shell
enter
cp /sdcard/install.sh /data/local/tmp/install.sh
enter
chmod 755 /data/local/tmp/install.sh
enter
echo "/data/local/tmp/install.sh" > /sys/kernel/uevent_helper
enter
and the device should restart
im running a nandroid backup as we speak and im going to revert back to the 4.2.2 camera update and run threw it again see if i can't figure out what is hanging u up.
Click to expand...
Click to collapse
Running each of the commands works, until the last one. I get "can't create /sys/kernel/uevent_helper: Permission denied" error message
EDIT: I got it! Yeah!! :highfive: I found someone suggesting to take the phone back to 4.2.2 with this error message and redo SMM, and it stuck! Downloaded root checker, and I got a congrats result! Thanks so much, mate! You've been such a huge help; I was going to give up the first night before I even decided to post here!
I'm glad to hear you got it rooted finally if you have any other questions or need any ideas on what to do please feel free to pm me anytime
Sent from my XT1056 using xda app-developers app
i've got one for you... running windows 7, 32 bit. Eset AV-disabled.. have 4.2.2 rooted, but can't get moto-wp-nomo to successfully run...any ideas?
Hi,
I am in a bit of trouble I have a Motorola Edge 20 (2022) and I was playing with De-Bloater under Magisk. It worked really fine until I pushed the limit of how many Motorola apps i can remove. The last one was the wrong one, I think it was Motorola settings storage (provider) or so. Now the phone won't boot anymore and I was stupid enough not to back up the photos I made in the last three days.
I don't have TWRP on the phone (it's not available yet), so the Android recovery has to do. I saw that I can mount /system, but I don't know how to modify or even read it after mounting it. The internet is full of instructions of how to mount it and always mentions that you can then modify anything on it, but nowhere does it explain exactly HOW to do that
adb shell/push/pull just says "unable to... : closed"
The second option seems to adb sideload some zip. But what zip would I have to flash to disable the De-Bloater without factory resetting everything?
thanks
whoohoo! I jst discovered Safe Mode. Immediate problem thereby solved However, I am still interested in the first part of my question: how to use the mounted /system in Recovery Mode?
michael-brade said:
whoohoo! I jst discovered Safe Mode. Immediate problem thereby solved However, I am still interested in the first part of my question: how to use the mounted /system in Recovery Mode?
Click to expand...
Click to collapse
with stock recovery, youre unlikely to win as /data is decrypted (usually) and /system is largely unmountable and writeable (at least easily)
the usual prescription if you cant get into safe mode is:
Code:
adb wait-for-device shell magisk --remove-modules
from the bible (read on for TWRP ways which are 100% easier):
Magisk - Installation and troubleshooting:Magisk and MagiskHide Installation and Troubleshooting guide
didgeridoohan.com
which obviously removes all modules, even us experienced folks fond ourselves using the magical key combo to get into safe mode on occasion because we flew too close to the sun doping something in magisk
ironically debloating wasnt one of those times for me, i gave a log of what i debloated to the author of one debloater modules recently when he released a new version of his module and he was like "and it still boots?"...the list of debloated packages was at 135, and i could remove even more...
Thanks, good to know. But even adb wasn't able to connect anymore, Android got stuck even earlier.
However, I don't really mind if /system is read-only, I am more interested in how to (even theoretically) use the stock recovery. There is no manual and nobody said anything so far. So once you clicked "mount /system", what to do?
Lenovo (owner of Moto) has a online 'rescue' site that u can go to with your phone connected to the PC and it'll flash your Moto back to stock...prolly won't retain ur data, but it saved my a$$ a few times with my old twrp-less A/B slotted Moto G7. Can't recall the exact url but am sure u can dig it up with google.
Zaxx32 said:
Lenovo (owner of Moto) has a online 'rescue' site that u can go to with your phone connected to the PC and it'll flash your Moto back to stock...prolly won't retain ur data, but it saved my a$$ a few times with my old twrp-less A/B slotted Moto G7. Can't recall the exact url but am sure u can dig it up with google.
Click to expand...
Click to collapse
Hmm... but I can already do that without their help using fastboot. No need for the Android recovery.
Isn't it strange that there is a function we don't know how to use or how it works?