edit---
solved. close please. had to allow su access on my phone when i typed su in the cmd prompt LOL i feel stupid. i watched the video on theunlockr website but it was blocked by my adblocker and i didnt know it was there until i read a comment saying something about a video ._.
edit--
sorry
Hi, so im new to this stuff. i followed theunlockr guide to rooting the g1 with androot and got that done fine.
Now I've moved to flashing a custom recovery and I placed the flash_image and the recovery.img on the root of my sdcard and went to terminal typed su and all that good stuff. and it just says flash_image not found or something. so i tried the adb method and all is good, i type su and when as im typing the "mount -o,exec...." all of a sudden it just says Permission denied when I haven't even pressed enter.
And now I'm stuck...what could I do to solve this problem? Do I not have su access in adb?
Related
I've followed the instructions to a T on the wiki but I'm having a few problems. I had to downgrade to RC29 and then put "recovery.img" and the HardSPL "update.zip" on the root of the memory card. I even finished with the telnet commands (which didn't seem to do anything) and flashed JesusFreke's 1.5 crb43. Now when I try to use the Terminal Emulator for abd commands I get a permissions error. In addition, nothing shows up in my Superuser Permission application leading me to believe that I may not have rooted properly.
Any help would be greatly appreciated.
I forgot to mention that I cheated and I don't know if that was a problem. I started with crb43 and used the old exploit to downgrade to rc29 (format sd card, copy rc29 update.zip to root of card, enter bootloader mode and flash).
SharpieMarker said:
I've followed the instructions to a T on the wiki but I'm having a few problems. I had to downgrade to RC29 and then put "recovery.img" and the HardSPL "update.zip" on the root of the memory card. I even finished with the telnet commands (which didn't seem to do anything) and flashed JesusFreke's 1.5 crb43. Now when I try to use the Terminal Emulator for abd commands I get a permissions error. In addition, nothing shows up in my Superuser Permission application leading me to believe that I may not have rooted properly.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
You should be using adb for terminal commands. If you type 'adb' in the terminal you will get nothing.
Go to terminal emulator and type 'su'
if it brings up the permission screen press 'allow'
if your command line changed from '$' to '#' then you have successfully rooted.
There shouldn't be anything in superuser permissions if you haven't given any apps permissions (every app is considered a different user)
Hope this helps, but this seems like a thread that would be better suited to the Q&A or Dream topics since this is the Development section not general questions...just thought I'd mention it.
Just AIM me: Breakthecycle2
Breakthecycle2 said:
Just AIM me: Breakthecycle2
Click to expand...
Click to collapse
I can't use AIM at work. I am better reached at [email protected]
I think that worked. su brought up permissions window and when I select allow I now have root. Brilliant. Thanks very much for the assistance.
EDIT:
Oops
Then what am I missing about this? I'm attempting to replace these files to increase my maximum volume and I'm unable to use any of the adb commands, even with root.
adb remount
- wait for the 'remount succeeded' message
adb push Desktop/AudioFilter.csv system/etc
adb push Desktop/AudioPara4.csv system/etc
adb push Desktop/AudioPara4_TMUS.csv system/etc - Optional
SharpieMarker said:
Then what am I missing about this? I'm attempting to replace these files to increase my maximum volume and I'm unable to use any of the adb commands, even with root.
adb remount
- wait for the 'remount succeeded' message
adb push Desktop/AudioFilter.csv system/etc
adb push Desktop/AudioPara4.csv system/etc
adb push Desktop/AudioPara4_TMUS.csv system/etc - Optional
Click to expand...
Click to collapse
adb is the Android Device Bridge that allows you to interface your G1/Magic with an x86 Windows system. It is included in the Android Developer Toolkit.
You need windows and to have your G1 connected to your computer. There are a few really good threads giving step by step walkthroughs on setting it up correctly, just use the search.
ADB for Dummies
ADB for Dummies
ADB can't be used from terminal emulator on the phone...you have to use it from your windows command prompt...read up on ADB first.
I've been trying to figure this out all day and I'm stumped.
My stock Droid recently failed to get past the bootloader.
I'm following the directions from the CM Wiki titled "Motorola Droid: Full Update Guide" (no direct link because of my new account, sorry) and others I've found and they all seem to be exactly the same.
I've got SPRecovery installed no problem and after I run the update.zip I get a successful install message, including "enjoy your root".
The problem is in the next step where I ADB it doesn't appear I actually have root access.
I think this may be because I'm connecting to my phone from the SPRecovery menu, but I'm not sure.
This is what my cmd screen looks like when I try to follow the steps under "Installing ClockworkMod Recovery" > "Second Method (manual method)".
Code:
C:\Users\XXXX>adb shell
/ # su
su
/system/bin/sh: su: not found
I noticed that in SPRecovery there are "mount options", so I tried mounting /system and trying again and I get basically the same thing, but without the "/" and without the directory
Code:
C:\Users\XXXX>adb shell
# su
su
su: not found
I'm not Linux savvy enough to know the difference unfortunately. I've tried 3 different update.zip from 3 different sources, but all appear to be the exact same thing.
Typing "busybox" in the ADB shell kicks back all the functions so it appears to be installed.
"adb devices" kicks back "040388990E0EDITED recovery"
Any ideas would be greatly appreciated, it's getting very frustrating.
Do you have the opportunity to root your phone from the Recovery-Menu?
I have OpenRecovery (OR) and when I boot in OR i can manually chose to root my phone.
----wrong----
Quinity said:
You can also simply download the SuperUser App from the market. This roots your phone.
Click to expand...
Click to collapse
I'm about 99% certain that is false. If it was that easy, I would have heard about it. Plus the only SU app on the market states " Grant and manage Superuser rights for your phone. This app requires that you already have root.."
Hey guys, im currently trying to unlock my bro's captivate. (the seller sent me a locked phone to be use in malaysia).
so here's my problem, i tried simple method using generate code.bat but it says "no nv_data.bin found". so it fails, then i search more on methods to unlock, i found this http://forum.xda-developers.com/showthread.php?t=831569
so when i get to step to fix permission denied .
If you receive a permission denied error, you can fix it by typing the following commands from an ADB shell (type "adb shell" at the DOS command prompt) or from within a terminal on the phone:
su
chmod 777 /efs/nv_data.bin
exit
exit
is says permission denied. please enlighten me on this. or recomend me any other methods out there. thanks.
sorry for my bad english.
Are you rooted?
Sent from my HTC Inspire 4G
First, you need to be rooted. Search the forum for how to do that if you dont have a custom ROM.
Second get Galaxy_S Unlock by Helroz from market. Works like a charm. Tried and tested by me! Worked in 3 different countries/carriers.
Okay so I have recently rooted my HTC Hero and would like to flash a custom ROM, but I am getting held up in ADB when trying to flash_image my custom recovery.
I have tried to put the Flash_Image file in the root of my SD Card, in my ADB folder, etc.... But nothing has worked so far.
Here is what I am doing, with the outcomes.
C:\Program Files\Android\Android-sdk\Platform-tools\>adb shell
$ su
# flash_image recovery /sdcard/CWRecovery.img
flash_image: not found
# ./flash_image recovery /sdcard/CWRecovery.img
flash_image: not found
Also I have adb pushed all the files required, and shortened the CWM Recovery image to 'CWRecovery.img' so I don't have to type as much lol.
My phone is rooted successfully, have installed BusyBox, SU, etc. So I don't know where the problem is coming from, but if anyone with any information could help, it would be greatly appreciated!
I couldn't tell you what is wrong with it, but have you tried using a terminal emulator on your phone to get it done? From there I'd just
$ su
#flash_image recovery /sdcard/CWRecovery.img
like you've done in adb.
I have tried doing it through Terminal Emulator.. But after trying for about 3 days, I have come up with something. Apparently in the 2.27.651.6 update there is no flash_image. So I had to downgrade to 2.27.651.5.
So I followed this guide http://forum.xda-developers.com/showthread.php?t=694572
Thanks to regaw_leinad for posting that!
Ah, now you've refreshed my memory. I actually had trouble with rooting my phone because mine was at 2.27.651.6 as well. I tried a bunch of the one-click methods and stuff, and they weren't compatible with it... Glad it worked out.
I think if you install busybox (via the Busybox installer app), that'll give you the flash_image executable on your phone. You shouldn't have to downgrade anything to get that functionality.
Not around my laptop atm but I believe Windows has two Android folders. One named "android-sdk-windows" and the other "AndroidSDK" . Have you checked to make sure you put the recovery.img into the "AndroidSDK" folder and not the
"android-sdk-windows" folder???
Also have you checked to make sure both img's are named exactly alike??
#Root-Hack_Mod*Always\
Thank you for the responses fellas, I tried to install BusyBox by downloading the App on the Market, and it said that BusyBox was already installed and asked if I would like to remove it or install over it, tried both options and still nothing. Tried re RUU-ing with .6 and doing z4Root, SuperOneClick, and tried RegrawMOD. Still could not access the flash_image.
Yeah, when I tried to root mine I also tried z4Root, SuperOneClick, andRegrawMOD, none of which worked for me either. I really didn't want to do the whole command line thing, but that's what I ended up having to do. This is the guide I used for root:
http://wiki.cyanogenmod.com/index.php?title=HTC_Hero_(CDMA):_Full_Update_Guide
I followed the directions in step one to install the SDK, then completed the rest of them. It actually wasn't as bad as I thought it would be, and after that I was able to flash a recovery.
Use Rom Manager from the market to flash a recovery
Sent from my HERO200 using XDA
Hi guys, I would really appreciate some help. I am able to root my gear and transfer the TWRP via odin. But when I reboot into recovery it just goes back to the stock launcher. I read this in the developer thread:
IF YOU FIND THE RECOVERY IS NOT STICKING & YOUR GEAR WIPES WHEN ATTEMPTING TO ACCESS RECOVERY AFTER FLASHING.
YOU MUST ROOT YOUR GEAR PRIOR TO INSTALLING TWRP AGIAN & RUN THE FOLLOWING COMMANDS IN ADB.
*NOTE* YOU WILL HAVE TO ACCEPT A SUPERUSER REQUEST POPUP WHEN EXECUTING "SU" COMMAND.
*NOTE 2* PROBABLY A GOOD IDEA TO RUN THIS PRIOR TO FIRST INSTALLATION, TO SAVE TIME.
Code:
$ adb shell
$ su
# mount -o rw,remount /dev/block/mmcblk0p20 /system
# rm /system/recovery-from-boot.p
IF YOU DELETE THE "RECOVERY-FROM-BOOT.P" FILE YOU MUST RELFASH TWRP RECOVERY.
I have rooted and installed roms on phone before but working in the developer tools is new to me. Can anyone explain exactly how and when to do this during the TWRP recovery install process? Or possibly just point me to a how to or youtube on basic adb commands? I have searched and it looks super complicated. Just need to know how to run these 3 commands.
THANKS!
i have the exact same issue, is there any answer for this??
Wettpassat said:
Hi guys, I would really appreciate some help. I am able to root my gear and transfer the TWRP via odin. But when I reboot into recovery it just goes back to the stock launcher. I read this in the developer thread:
IF YOU FIND THE RECOVERY IS NOT STICKING & YOUR GEAR WIPES WHEN ATTEMPTING TO ACCESS RECOVERY AFTER FLASHING.
YOU MUST ROOT YOUR GEAR PRIOR TO INSTALLING TWRP AGIAN & RUN THE FOLLOWING COMMANDS IN ADB.
*NOTE* YOU WILL HAVE TO ACCEPT A SUPERUSER REQUEST POPUP WHEN EXECUTING "SU" COMMAND.
*NOTE 2* PROBABLY A GOOD IDEA TO RUN THIS PRIOR TO FIRST INSTALLATION, TO SAVE TIME.
Code:
$ adb shell
$ su
# mount -o rw,remount /dev/block/mmcblk0p20 /system
# rm /system/recovery-from-boot.p
IF YOU DELETE THE "RECOVERY-FROM-BOOT.P" FILE YOU MUST RELFASH TWRP RECOVERY.
I have rooted and installed roms on phone before but working in the developer tools is new to me. Can anyone explain exactly how and when to do this during the TWRP recovery install process? Or possibly just point me to a how to or youtube on basic adb commands? I have searched and it looks super complicated. Just need to know how to run these 3 commands.
THANKS!
Click to expand...
Click to collapse
i have the exact same issue, is there any answer for this??
Well it's been well over a year since I did that but let's see if I can help..... Before I start I'm hoping you've already enabled adb debugging on the gear and downloaded adb onto your computer. I believe you run the commands after you've run cygnia but before you flash twrp. You run the task from a command prompt from your pc. I'm pretty sure you don't include the $ or #. Before you start try the adb command- adb devices from the command prompt on your pc. That'll let you know if the gear is connected. I remember being a bit intimidated by it all as it was different to any other flash I'd done. In reflection it's very easy, type the line in a command prompt, press enter, wait for the cursor to come up again, type the next line. As for guides..... I can't remember which one I used but there's plenty out there.