Develop Bugs

Question about ROM Manager

Ok so when i try to use rom manager, it says i need flash clockworkmod recovery. So i click on it n it says confirm model n i do, then it says "an error occurred while attempting to run privileged commands." Wat am i doing wrong?? Thanks.

Are you rooted? That's usually a good sign that you aren't.
Sent from my EVO from the Apple Store.

yea i went thro all the steps to root n in titanium backup it says root access is OK. so im confused now.

Make sure you have the latest version of Super User Permissions (2.2.2): http://forum.xda-developers.com/showthread.php?t=682828
When I got that error, it was because I hadn't told SUP to allow ROM Manager quick enough, and RM had timed out on the permission request.

ok so how do i get this onto my phone, i apologize, this is my first android phone.

tarheelsmj12001 said:
ok so how do i get this onto my phone, i apologize, this is my first android phone.
Click to expand...
Click to collapse
Just go ahead and download the zip file su-2.2.2-ef-signed.zip from that thread I linked to. Plug your USB cable into your phone and computer, and either go to Notifications, tap on Chareg Only, and then change it to Disk Drive and press done, then open My Computer (or if on Mac/Linux, double-click the drive on your desktop) and copy the ZIP file directly to SD card, or use ADB to push the file by first turning on USB debugging if it isn't already (Settings>Applications>Development>USB debugging) then open Command Prompt (Terminal on Mac/Linux), go to wherever you have ADB located (usually the Tools folder of the Android SDK) and use this command:
Code:
WINDOWS: adb push *path to ZIP*\su-2.2.2-ef-signed.zip /sdcard/
MAC/LINUX: ./adb puh *path to ZIP*/su-2.2.2-ef-signed.zip /sdcard/
If you used the ADB method: Go ahead and just use the command "adb reboot recovery" (or "./adb reboot recovery" if on Mac/Linux) to reboot into your Recovery. If you used USB Mass Storage, power off your phone, then hold down the Volume Down button, then continue holding Volume Down while holding the Power button. You will then see the bootloader screen (white screen with three skateboarding Androids at the bottom) and can let go of the buttons as soon as you do. Press Volume-Down to highlight "RECOVERY", and then the Power button to select it. Next you'll see the words "HTC EVO 4G" on a white screen (like a normal boot-up) followed shortly after your Recovery image.
Next, use Volume Up/Down to move your selection up/down and use the Power button to select "Install ZIP from SD Card" (or something along those lines). You should have one option for "install update.zip" and one for "Choose ZIP from SD card" (again, or something similar). Choose the latter of the two, and then use Volume Up/Down to select su-2.2.2-ef-signed.zip, and Power to select. Wait a few moments until you're told that the installation was successful, and then select to reboot the phone.
You should then be able to boot into Android, and have the Super User Permissions app installed! Whenever you try to run something which needs root, you'll get a pop-up asking for permission. Go ahead and launch ROM Manager, and you'll get the pop-up, make sure "Remember" is checked, and then press allow. If ROM Manager still complains that it didn't get permissions, re-launch it, and it should work fine.

drmacinyasha said:
Just go ahead and download the zip file su-2.2.2-ef-signed.zip from that thread I linked to. Plug your USB cable into your phone and computer, and either go to Notifications, tap on Chareg Only, and then change it to Disk Drive and press done, then open My Computer (or if on Mac/Linux, double-click the drive on your desktop) and copy the ZIP file directly to SD card, or use ADB to push the file by first turning on USB debugging if it isn't already (Settings>Applications>Development>USB debugging) then open Command Prompt (Terminal on Mac/Linux), go to wherever you have ADB located (usually the Tools folder of the Android SDK) and use this command:
Code:
WINDOWS: adb push *path to ZIP*\su-2.2.2-ef-signed.zip /sdcard/
MAC/LINUX: ./adb puh *path to ZIP*/su-2.2.2-ef-signed.zip /sdcard/
If you used the ADB method: Go ahead and just use the command "adb reboot recovery" (or "./adb reboot recovery" if on Mac/Linux) to reboot into your Recovery. If you used USB Mass Storage, power off your phone, then hold down the Volume Down button, then continue holding Volume Down while holding the Power button. You will then see the bootloader screen (white screen with three skateboarding Androids at the bottom) and can let go of the buttons as soon as you do. Press Volume-Down to highlight "RECOVERY", and then the Power button to select it. Next you'll see the words "HTC EVO 4G" on a white screen (like a normal boot-up) followed shortly after your Recovery image.
Next, use Volume Up/Down to move your selection up/down and use the Power button to select "Install ZIP from SD Card" (or something along those lines). You should have one option for "install update.zip" and one for "Choose ZIP from SD card" (again, or something similar). Choose the latter of the two, and then use Volume Up/Down to select su-2.2.2-ef-signed.zip, and Power to select. Wait a few moments until you're told that the installation was successful, and then select to reboot the phone.
You should then be able to boot into Android, and have the Super User Permissions app installed! Whenever you try to run something which needs root, you'll get a pop-up asking for permission. Go ahead and launch ROM Manager, and you'll get the pop-up, make sure "Remember" is checked, and then press allow. If ROM Manager still complains that it didn't get permissions, re-launch it, and it should work fine.
Click to expand...
Click to collapse
Damn i appreciate ur help n giving me the steps. Just one question, how do i get my command prompt to go to where my ADB is located, its stuck on C:\documents and settings. Thanks again for ur help n sorry for my stupidity.

When i go into my recovery n click on apply sdcard:update.zip, it says failed to open /sdcard/update.zip ( no such file or directory). Wat am i doin wrong??

tarheelsmj12001 said:
When i go into my recovery n click on apply sdcard:update.zip, it says failed to open /sdcard/update.zip ( no such file or directory). Wat am i doin wrong??
Click to expand...
Click to collapse
dont click that one, click the one that says install zip file or something, not update .zip

skittlesV1 said:
dont click that one, click the one that says install zip file or something, not update .zip
Click to expand...
Click to collapse
hmmm i dont have that option

skittlesV1 said:
dont click that one, click the one that says install zip file or something, not update .zip
Click to expand...
Click to collapse
Correct. There's usually two options, one of them being to choose to look for a ZIP file, and the other is sdcard:update.zip. You want to have it look for the ZIP file, and select it off of your card's root directory.
Oh, and to change what directory your command prompt is in, use "cd *path*" which is both for Windows, Mac, and Linux.

yea i dont have that option, only have the one to update.

What Recovery are you using? Perhaps your first step should be to get a better recovery image.

If u don't mind telling me how to do that then ill try n get a better one. N i have no idea which one i have.
Sent from my PC36100 using XDA App

Alright, at the top or bottom of your recovery mode's screen, it will usually tell you what recovery you have (ClockworkMod, Amon Ra, etc.).
To flash a new one, connect your computer and phone, and open up command prompt. Change to wherever you have ADB, and get ready for some fun.
First up, download recovery-RA-evo-v1.7.0.1.img (Amon_Ra's Recovery). Boot your phone into Fastboot by either using "adb reboot bootloader" or turn off you're phone, and turn it back on by holding Volume Down and Power. You'll get the white screen with the skating Androids again. Go ahead and select FASTBOOT. Now, in your command prompt/terminal, use this command:
Code:
fastboot devices
It should acknowledge that fastboot can see your phone. If not, try rebooting again. Once it sees your phone, use this command to flash the recovery:
Code:
fastboot flash recovery *path to file*\recovery-RA-evo-v1.7.0.1.img
Give it some time, and it should succeed. Then go on your phone, select bootloader, and then recovery. You should then boot into RA Recovery 1.7.0.1. Select "Flash zip from sdcard" and select the su-2.2.2-ef-signed.zip file. Give it a bit to do its thing, and then when it's all done, select "Reboot system now"

drmacinyasha said:
Alright, at the top or bottom of your recovery mode's screen, it will usually tell you what recovery you have (ClockworkMod, Amon Ra, etc.).
To flash a new one, connect your computer and phone, and open up command prompt. Change to wherever you have ADB, and get ready for some fun.
First up, download recovery-RA-evo-v1.7.0.1.img (Amon_Ra's Recovery). Boot your phone into Fastboot by either using "adb reboot bootloader" or turn off you're phone, and turn it back on by holding Volume Down and Power. You'll get the white screen with the skating Androids again. Go ahead and select FASTBOOT. Now, in your command prompt/terminal, use this command:
Code:
fastboot devices
It should acknowledge that fastboot can see your phone. If not, try rebooting again. Once it sees your phone, use this command to flash the recovery:
Code:
fastboot flash recovery *path to file*\recovery-RA-evo-v1.7.0.1.img
Give it some time, and it should succeed. Then go on your phone, select bootloader, and then recovery. You should then boot into RA Recovery 1.7.0.1. Select "Flash zip from sdcard" and select the su-2.2.2-ef-signed.zip file. Give it a bit to do its thing, and then when it's all done, select "Reboot system now"
Click to expand...
Click to collapse
Ok so i downloaded the recovery image. Where i get confused is when u say open the the command prompt and change to where i have ADB. So i go to start, run, n then type command?? N i dont understand when u said how to change what directory the command prompt is in, idk wat "cd *path*" means.

Where do you have ADB or the Android SDK?
To open command prompt, go to Start>Run and type cmd then hit enter. Then use the command cd (path to Android SDK)\tools\, so for example, I have my Android SDK in "C:\Program Files (x86)\Android SDK" so I would use cd C:\Program Files (x86)\Android SDK\tools\.

tarheelsmj12001 said:
Damn i appreciate ur help n giving me the steps. Just one question, how do i get my command prompt to go to where my ADB is located, its stuck on C:\documents and settings. Thanks again for ur help n sorry for my stupidity.
Click to expand...
Click to collapse
Dude it's not stupidity. This is the steepest part of the learning curve and there is actually not an easy answer. This drove me nuts when I first started to learn. But it's really fun once you figure it out.
First, follow the steps here: http://htcevohacks.com/htc-evo-hacks/how-to-install-android-sdk-and-adb-drivers-for-htc-evo-4g/
That will give you the SDK folder on your computer. I recommend that you extract the files directly onto the C: drive. That will give you the following path: C:\android-sdk-windows\tools (that will make more sense once you actually follow those steps.
Then, open a Command Prompt on your computer. If you use windows, it's under the Accessories folder on the Start menu. You obviously know this from your earlier post.
Then type the following:
Code:
cd C:\android-sdk-windows\tools
That should bring you to that folder. Everything you ever do that is "ADB" is done from this folder. That means that you actually need to put pertinent files into the "tools" folder there.
Once you are there type the following:
Code:
adb devices
If a long number shows up, then it sees your phone. There you go. If the above doesn't work, it might mean that you have to do another really annoying b.s. maneuver to your computer. Not worth mentioning if you don't have to do it. So just reply if this doesn't work and you can take it from there as far as troubleshooting.
Having said all that, the easiest way to install the new su zip file is to just put it on the your SD card, reboot into recovery, and choose install from SD card, and just choose it.

I would just like to thank u guys so much for ur help n def ur patience. I followed the steps u guys gave me n it worked flawlessly. Im so damn happy now lol, ive been trying to do this for sometime now. Now its time to get some ROMs on this bad boy. Once again, thank u very much guys for ur help, its nice to see ppl helping each other out on here so much.

tarheelsmj12001 said:
I would just like to thank u guys so much for ur help n def ur patience. I followed the steps u guys gave me n it worked flawlessly. Im so damn happy now lol, ive been trying to do this for sometime now. Now its time to get some ROMs on this bad boy. Once again, thank u very much guys for ur help, its nice to see ppl helping each other out on here so much.
Click to expand...
Click to collapse
You're more than welcome, just make sure to hang onto ADB and the Android SDK folders, and where they're are, as they'll be necessary for almost any ROM, upgrade, unlock, etc.!

[Q] Need Assistance, I brick my Galaxy Nexus

Hi, I am afraid I brick my Galaxy Nexus (Rooted)
Cause:
I think I wrongly delete some system files in Clockworkmod.
Symptoms:
1. When the mobile is turn on, only shows 'Google' logo and the 'Unlock' logo, no responds then.
2. Press Volume + and - key, I can successfully enter recovery mode.
3.Press Volume - key, I can successfully enter Download mode.
4. I do not have any Stock Rom file (or other Rom file) in the mobile memory.
Urgently need your expertise and help.
Many Thanks
(I am not an expert, so would you mind teach me step by step if you got the solution)
Thanks!!!!

So you cannot boot the phone at all past the Google splash screen? LTE or GSM?
Or does the phone boot fine, but you just can't get into ClockworkMod Recovery?

cbs2002 said:
Hi, I am afraid I brick my Galaxy Nexus (Rooted)
Cause:
I think I wrongly delete some system files in Clockworkmod.
Symptoms:
1. When the mobile is turn on, only shows 'Google' logo and the 'Unlock' logo, no responds then.
2. Press Volume + and - key, I can successfully enter recovery mode.
3.Press Volume - key, I can successfully enter Download mode.
4. I do not have any Stock Rom file (or other Rom file) in the mobile memory.
Urgently need your expertise and help.
Many Thanks
(I am not an expert, so would you mind teach me step by step if you got the solution)
Thanks!!!!
Click to expand...
Click to collapse
The key piece of information for your symptom is in this line:
1. When the mobile is turn on, only shows 'Google' logo and the 'Unlock' logo, no responds then.
The other lines do help provide background as to the other modes such as recovery and download working properly, which indicates the issue is not *serious*.
The symptom you state, where the device does not boot past the boot logo, usually means the device is not able to boot the kernel or boot past the kernel. The boot logo appears while the kernel is being loaded on the device. Generally, after the boot logo and kernel finish loading a boot animation appears which indicates the kernel has usually handed off to the Android OS to continue booting.
My approach would be to load a completely stock ROM in order to restore a working kernel and ROM to the device. I generally perform this step as a baseline to get everything back in working order.
In many instances the ROM is dependent on the kernel. Your situation requires at least a kernel to be loaded and in order to prevent any further issues, it would be best to load a ROM dependent on the kernel being loaded.
A simple way would be to grab the stock factory images from Google's site and load those back onto the device.
Another simple way would be to grab a stock ROM and flash the .zip through CWM in recovery mode.
Hope that helps!

Since you're rooted I'm going to assume you have ADB and the necessary drivers installed.
1.) Download a ROM. It doesn't have to be stock, you can choose any of the ROMs from the development section for your device. Most of the ROMs are packaged with a kernel already.
2.) Save this ROM file to the same folder where you have ADB installed.
3.) Boot your phone into CWM recovery and plug it into your computer.
4.) Use ADB to push the ROM zip file to your phone (/data/media). For example:
Code:
c:\gnex\>adb push rom.zip /data/media/rom.zip
5.) Use CWM to wipe data, cache, and davlik-cache
6.) Install zip from sdcard and flash the rom.zip.

RMarkwald said:
So you cannot boot the phone at all past the Google splash screen? LTE or GSM?
Or does the phone boot fine, but you just can't get into ClockworkMod Recovery?
Click to expand...
Click to collapse
1. I am using GSM
2. Whenever I turn on my mobile, the 'Google' and 'Unlock' logo appears and then freeze, with no more respond at all
* I definitely mess up some system files, but don't know how to restore it because my PC do not recognize my mobile.
Thanks

I am seeing more and more of these threads about "bricked" nexus's is this an issue with how new the phone is or people not following instructions properly as they are too eager to root their phones?
All else fails flash back to stock and count yourself lucky.

To silow,
Thanks for your advice, but fail
1. I put adb.exe, adbwinapi.dll and fastboot.exe (3 files) under my PC C drive (i.e. C
2. I also put a stock Rom (rename as rom.zip) under C drive (i.e. C
3. Boot phone into CWM recovery and plug it into computer.
4. Use cmd command and type c:\gnex\>adb push rom.zip /data/media/rom.zip
5. It fails , It say "Access Denied" (in Chinese, but I translate it into English here)
6. How do I use ADB (it is a ADB.exe file, When I double click it, it only flash up a few page very fast and nothing happen)
Please assist!

To Joeykrim,
I agree that
"Another simple way would be to grab a stock ROM and flash the .zip through CWM in recovery mode."
But how? (according to my symptoms)

The command I gave you was just an example. I didn't spell out the exact details because I thought that you would know how to do it considering you rooted the phone.
If you put the adb.exe and AdbWinApi.dll file in your C: drive, make sure you copy the ROM file to your C: drive too. In the follow example I'm going to use "ROM.zip" but use the name of the ROM file that you downloaded. Also I am assuming you are on Windows XP.
1.) Boot your phone into CWM recovery and then plug it in.
2.) Go to your Start Menu and choose Run. Then type in "cmd" without quotes and hit enter to open a command prompt.
3.) Enter:
Code:
cd c:\
4.) Enter the following to make sure ADB can see your phone:
Code:
adb devices
You should see something similiar to this to confirm ADB can see your device:
List of devices attached
019B756F0C018012 device
5.) Enter the following command to copy the ROM file to your phone. Remember to replace ROM.zip with whatever the name of the ROM file is:
Code:
adb push ROM.zip /data/media/ROM.zip
6.) Use CWM to wipe data, cache, and davlik-cache
7.) Install zip from sdcard and flash the rom.zip.

To Silow,
You have been very helpful, but I fail.
"You should see something similiar to this to confirm ADB can see your device:
List of devices attached"
There is NO device number shown after the phrase 'List of devices attached'
To recap:
a) Phone is already plugged in my PC, under the Clockworkmod Recovery 5.5.0.2
b) adb.exe and AdbWinApi.dll file are under C: drive directly
c) Also type cmd in 'Run', a black Dos window shown C:\windows\system32\cmd.exe
d) c:\>adb devices
List of devices attached
(But no device number show up, it cannot recognize my mobile)
Pls don't give up on me!
: )

you can't use adb from CWM, you need to enter the bootloader, then try adb or fastboot (edit: wrong!)

Sounds like your ADB USB drivers are not correctly installed. While the phone is under CWM, when you plug it in is your computer attempting to install drivers for a new device?
Download these bare ADB Interface drivers.ADB USB Drivers
Go into Device Manager on your computer and check the device list for any unknown devices or "?" devices. If you need to update those drivers by pointing them to the drivers you downloaded and extracted from that link above.
When the ADB Interface drivers are correctly installed you should see Android Phone listed under under your Device Manager when it's plugged in with CWM recovery loaded.
---------- Post added at 02:36 PM ---------- Previous post was at 02:35 PM ----------
cancerouspete said:
you can't use adb from CWM, you need to enter the bootloader, then try adb or fastboot
Click to expand...
Click to collapse
You CAN use ADB with CWM. That's one of the reasons why CWM is so awesome.

silow said:
You CAN use ADB with CWM. That's one of the reasons why CWM is so awesome.
Click to expand...
Click to collapse
edit: i did appear to have one missing driver, my mistake. it was listed in device manager as "unknown - full"
its funny cause i never had to use adb from cwm before, never noticed

cbs2002 said:
d) c:\>adb devices
List of devices attached
(But no device number show up, it cannot recognize my mobile)
Click to expand...
Click to collapse
This symptom generally occurs from not having loaded the drivers for the hardware. As with the majority of hardware devices when being connected to a Windows machine, the drivers need to be loaded. Sometimes these are automatically loaded and other times they have to be manual loaded.
As an alternative and for future reference, the android-sdk package contains general USB drives which usually work for Google Nexus devices.
Generally, as this providers a *cleaner* install, best practice as recommended by Google is to download the whole android-sdk .zip and then from the installer download/install the pieces needed, such as platform-tools (containing adb) and USB drivers as opposed to extracting out the adb.exe and .dll file and installing manually.
cancerouspete said:
you can't use adb from CWM, you need to enter the bootloader, then try adb or fastboot
Click to expand...
Click to collapse
silow said:
You CAN use ADB with CWM. That's one of the reasons why CWM is so awesome.
Click to expand...
Click to collapse
Agreed. To add greater clarification so there is no confusion: adb can't be used from the bootloader.
The /sbin/adbd daemon on the device is only loaded while in normal android boot mode or in recovery mode as called by the init.rc (or on some older devices, recovery.rc) file in the boot process.
Bootloader mode will only work with fastboot while it is in fastboot usb mode.
On some devices, the bootloader has a separate menu for fastboot and on other devices, the fastboot mode is directly entered when entering the bootloader.
Hope that helps clarify!

To silow (and all other helpers)
1. I fail
2. The ADB USB drivers in my PC should be fine as in Device Manager , I can see Android Phone with Android Composite ADB Interface. (No exclamation mark)
3. On the other hand, whenever I plug my mobile into PC, I can see "Unknown-Full"
4. In DOS, when I first type "adb devices" it shows
* daemon not running. starting it now on port 5037*
*daemon started successfully *
List of devices attached
(but NO device number shown!)
5. When I enter adb devices second time, it shows
List of devices attached (No device number shown)
Thank you so much , but it is Hong Kong time (my place) at 0511 am , I didn't sleep all night and I am very tired.
If you don't mind (especially big helper Silow), please give me email so that I capture screen picture and show you in detail (hope it may help)
my email is
[email protected]
I need to sleep now, I will check my email and see you guys or come back this Forum later (several hours later, as I really need some sleep right now)
Pls don't give up on me as this is an expensive mobile. I think the hardware is fine, just need to figure out a way to unbrick it.
Thanks, and see you!

What you need to do is right click on "Unknown-Full" and click on "Update Driver...". Then choose "Install from a list or specific location". Make sure "Search for the best driver in these locations." is checked and "Include this location in the search:" is check. Click on the Browse button and browse to where you extracted the driver files from the link I posted above. Click Next and this should install the correct drivers for you. Afterwards try "adb devices" again to see if ADB now reconizes your device.

To Silow,
Fail.
1. Already installed the drivers you gave me (and there is no 'Exclamation' Mark) in Device manager
2. Situation is the same , Cannot recognize my mobile (i.e. no Device No. after entering adb devices)
3. "List of devices attached" shown in DOS video but without any number.
No other method?
My mobile is really 'bricked' to death?

To Silow and all,
Something important
1. When choose 'install zip from sd card' under CWM, a list of old folder names remains
(e..g gameloft, DCIM, Pictures, etc). That means almost all old files, folders are STILL in my mobile!
2. I have already use the funcion 'Wipe data/factory reset', 'wipe cache partition', ' Wipe Dalvik Cache'
Perhaps my CWM has problem?

What happens when you update drivers for Unknown-Full?
Boot into fastboot and see if your computer recognizes the phone by checking device manager. The key here is to get your computer to see the phone either in fastboot or CWM.
Perhaps try another cable, USB port, or new computer.
The goal is to get Android Phone ADB Composite Interface to show up in device manager either in Fastboot or CWM. Without that done you cannot use Fastboot to flash nor ADB to push a zip file to the phone.
Sent from my Galaxy Nexus using XDA App

[HOWTO]Unlock, Root, and install CWR Galaxy Nexus with Ubuntu Linux or Linux Mint 12

warnning: any damage you do to your phone following these directions is your responsibility. Assume you warranty is void if your are rooted.
I used the information koush provided here and info birdman provided here and adopted it in Ubutnu Linux 11.10. I hit some bumps along the way using my Linux box so I decided to write this for those of us not using OS's made by the darkside This should also work with Ubuntu 12.04 LTS just fine.
All this should work with Linux Mint 12 also.
1- Set up Android SDK, adb, and fastboot in Ubuntu Linux using the links in my signature. I can't stress how useful and easy it is to set adb and fastboot in your "path" so you can easily use it from any prompt. The links explain it. Take your time with that and it will payoff for all your devices. Here is the guide I wrote http://forum.xda-developers.com/showpost.php?p=19446284&postcount=62
STOP NOW! EVERYTHING INCLUDING YOUR PERSONAL FILES, PICTURES, AND VIDEOS WILL BE ERASED WHEN YOU UNLOCK/ROOT THIS DEVICE. It does not have a physical SD card. Very annoying. Use Dropbox or Google+ to backup everything.
2- on your phone, go to settings/Developer Options and check the box for USB Debugging
3-connect your phone, fire up a terminal, and type:
Code:
adb devices
You should get the serial number of your device appear. If not, unplug, reboot phone, re-attach the phone to your computer and try again. If you still do not get your device's serial number, go back to step 1 and make sure everything is setup correctly.
4- Now download Clockwork Recovery from here
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.5.0.4-toro.img
(make sure it's the CDMA one (toro). The GSM one is called maguro and steps should be the same)
and su.zip from here
http://download.clockworkmod.com/test/su.zip
5-Turn the phone off, hold both Volume up and Volume Down and press the power button. You should come to a screen that has a big arrow and some writings at the bottom (fastboot). Last line should say Locked state.
6- Connect your phone to your computer, fire up a terminal and type:
Code:
fastboot devices
your phone and its serial number should appear just as it did using adb above. adb will not work here of course. If you don't see your device, go to step one. I guess you can download the fastboot for linux and cd to that directory and do it but I like to have it setup on my computer.
STOP NOW! EVERYTHING INCLUDING YOUR PERSONAL FILES, PICTURES, AND VIDEOS WILL BE ERASED WHEN YOU UNLOCK/ROOT THIS DEVICE. It does not have a physical SD card. Very annoying. Use Dropbox or Google+ to backup everything.
7- Now for the stuff that voids your warranty: Type
Code:
fastboot oem unlock
and enter. Look at your phone now, use the Volume up to choose YES and press the power button to accept. It should say that you are unlocked and fastboot is in good state.
9-use the volume up to change the value appearing in the arrow to recovery and press the power button to accept. You are taken to laying down android with a red triangle. This is the stock recovery. Now carefully press the volume up, volume down, and the power button to get to a menu. Choose wipe data and factory reset. 2 things: I had a hard time getting to the menu. Do it a few times and try pressing the power button JUST a fraction of a second earlier than the 2 volume buttons. Also wiping and resetting takes a few minutes, be patient.
10-you are now unlocked. Turn the phone off ( I pulled battery), go to fastboot screen by holding volume up, down and power button. Connect your phone to your computer and make sure it is recognized by typing:
Code:
fastboot devices
If it is, change directory to where you downloaded clockwork recovery. If you didn't change it, it should be the Download directory (remember it's case sensitive):
Code:
cd Downloads
11- Time to re-write your recovery:
Code:
fastboot flash recovery recovery-clockwork-5.5.0.4-toro.img
Please make sure you use common sense here when it comes to file names. If the file you downloaded has a different name or version, change it in the code above. I guess you can put the fastboot file in that location also to be used if you do not have it setup as in step 1. I'm not positive how and if that would work. Downloading and installing the wrong file is a mistake that may cause harm to your phone.
12- Use the vol up/down to point the big arrow toward recovery, push the power button to get to Cloclwork Recovery. Once you confirm you have CWR, reboot the phone normally and let Android OS create all the folders it needs. Once at start up screen, pull the battery to turn phone off, and then get to bootloader by holding vol up/down and power button in. Use the vol up/down to point the big arrow on sceen toward recovery. While in recovery, make sure your terminal prompt still shows the Downloads directory (or where the su and recovery files were downloaded to). Now type: (note the space between zip and /data)
Code:
adb push su.zip /data/media
this will put the su.zip file in the root of your virtual sd card.
You are still in recovery, reboot into recovery to refresh the file list by typing this
Code:
adb reboot recovery
Now go ahead and install su.zip through clockwork recovery's menus. Pretty self explanatory (choose zip from sd card). The su.zip should be now in the root of your virtual sd card.
That's all. You are now unlocked and rooted. Reboot. Make sure you install the paid versions of rom manager, titanium backup, and update superuser app.
13- Download Rom Manager and flash the recovery again (top choice). This will erase the install-recovery.sh file and keeps your CWR at each boot. You do not have to do step 14 if you do this. I will leave step 14 here just in case someone needs it.
14-When you are back in the fastboot screen. DO NOT reboot the phone here. There maybe a file that re-writes the recovery to stock if the phone is rebooted. Your phone may or may not have this file. of the two GN I have, one did and one did not at this step(may have been erased). The file is reovery.sh and is located in /system/etc/ . You need to either rename it or delete it.
While in fastboot and after you flashed CWR, use the Volume up and Down to change the arrow's value to recovery and press the power button. You should now see the familiar Clockwork recovery. In recovery, you can use adb (you can't in fastboot of course). You need to rename that file, use these steps in terminal: (If you see no file/folder found message, you know you do not have this file)
Code:
adb shell
Code:
mount -o rw,remount /system
Code:
mv /system/etc/install-recovery.sh /system/etc/install-recovery.bak
step 1 fires up adb, step 2 allows you to change permissions and read and write, and step 3 renames it. You can now unplug the phone.
Again, you can also get rid of this file by flashing the clcokwork recovery in Rom Manager or using the paid app root explorer to rename the file.
Once again referrence links:
http://rootzwiki.com/topic/12013-welcome-to-rootzwiki-editionstep-by-step-oem-unlock-and-root/
https://plus.google.com/103583939320326217147/posts/1Jsh9xPwnQP

thank you so much this is exactly what i was looking for. cant believe im the only one to comment on this. it is very detailed even some one new to Ubuntu could figure this out.

I've been using it too for a while but never posted so THANK YOU! Very easy to follow. Great work.

you're welcome. I find it ironic that a Linux based OS such as Android has so many HOWTOs for Windows but not enough for Linux. #powerofmonoply

I find I need to run fastboot commands with sudo or su into root before it will work. Same for you, or misconfig on my side?
Sent from my Galaxy Nexus using XDA

ual4720 said:
I find I need to run fastboot commands with sudo or su into root before it will work. Same for you, or misconfig on my side?
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
I'm not sure. How did you setup your adb and fastboot? I did not have to sudo for fastboot commands. What OS are you running?

Hey loveubuntu, I have a question.
I'm at Step 12, and I'm in recovery and when I run adb push su.zip /data/media, it isn't finding any devices. When I run adb devices, the device isn't listed.
Any advice?

AndroidSparty said:
Hey loveubuntu, I have a question.
I'm at Step 12, and I'm in recovery and when I run adb push su.zip /data/media, it isn't finding any devices. When I run adb devices, the device isn't listed.
Any advice?
Click to expand...
Click to collapse
were you able to see the device in the previous steps 3, 6 and 10 and now you don't?
Things that come to mind is:
1- Do you have the usb debugging checked?
2- unplug and replug the device and see if it works.
3- don't forget the samsung recovery file install-recovery.sh. If the phone is rebooted you may have re-written your recovery and have to start over. Then reboot the phone and go to rom manager and reflash the recovery (first option). This will take care of the install-recovery.sh file.

loveubuntu said:
were you able to see the device in the previous steps 3, 6 and 10 and now you don't?
Things that come to mind is:
1- Do you have the usb debugging checked?
2- unplug and replug the device and see if it works.
3- don't forget the samsung recovery file install-recovery.sh. If the phone is rebooted you may have re-written your recovery and have to start over. Then reboot the phone and go to rom manager and reflash the recovery (first option). This will take care of the install-recovery.sh file.
Click to expand...
Click to collapse
3, 6, & 9...check.
I rebooted my phone by pulling the battery and I still can't get adb to see the device. The install-recovery.sh? I don't remember reading anything about that.
In step 12 it says to let the phone reboot into the Android OS, but it's now back at factory reset, as that's what we did earlier in the instructions. As soon as it boots into the Android OS, adb lists the device.
At that point, since I'm in the AOS, I downloaded Astro File Manager and tried to put su.zip in the /cache folder, I think that's the folder that the clockwork recovery mod folder sees, and I don't have permission. I was hoping I could cheat and just drag & drop instead of pushing it. BUT...I did try the command adb push su.zip /media/play and I get permission denied. I'm guessing I don't have permission, even as sudo, to move the file to /data/media.

Okay I finally got it!
I didn't wait long enough for the Android OS to boot up. I finally was able to move the .zip file, but I couldn't find where /data/media was. So I let the OS boot up, removed the battery, went back into recovery, moved the zip file, and it was finally listed.

Ordered a Galaxy Nexus too, will definitely be using this guide. Windows guides are confusing.

Forceflow said:
Ordered a Galaxy Nexus too, will definitely be using this guide. Windows guides are confusing.
Click to expand...
Click to collapse
>Windows guides are confusing
>Windows guides
>Windows
Root of the issue
But agreed, this was a good supplement to follow for Ubuntu.
Sent from my Galaxy Nexus using xda app-developers app

Thank you for this guide. Some how I like the Linux method better than the Windows ones.
12- Use the vol up/down to point the big arrow toward recovery, push the power button to get to Cloclwork Recovery. Once you confirm you have CWR, reboot the phone normally and let Android OS create all the folders it needs. Once at start up screen, pull the battery to turn phone off, and then get to bootloader by holding vol up/down and power button in. Use the vol up/down to point the big arrow on sceen toward recovery. While in recovery, make sure your terminal prompt still shows the Downloads directory (or where the su and recovery files were downloaded to). Now type: (note the space between zip and /data)
Click to expand...
Click to collapse
This step is confusing. While in recovery should be replaced by "Hit Power button to enter ClockworkMod Recovery"
Otherwise people may mis-interpret by "Stay in fastboot and position the big arrow on top to Recovery Mode"
In my case (GNex GSM stock JB 4.11):
adb push su.zip /data/media
or
adb push su.zip /sdcard
did copy su.zip successfully but could not be listed by ClockworkMod Recovery menu when selecting "choose zip from sd card". I had to do this:
Code:
adb push su.zip /sdcard/Alarms
And, within the ClockWorkMod Recevery menu, select "choose zip from sd card"
Land on another screen where I could navigate to Alarms folder and see the su.zip there.
Now go ahead and install su.zip through clockwork recovery's menus. Pretty self explanatory (choose zip from sd card). The su.zip should be now in the root of your virtual sd card.
Click to expand...
Click to collapse
Sorry for being picky but personally, it is NOT self explanatory for me. I was expecting a menu item in CWM Recovery menu to say "Install su.zip". Actually you must navigate in the file system and select the su.zip yourself. Ok, may be that seems obvious now that I know what to do. But on the moment, I was worried I screwed up something because I needed to do some extra manipulations while you said that should be "self explanatory".
4- Now download Clockwork Recovery from here
Click to expand...
Click to collapse
You may want to up date the link, ClockWorkMod now has a Recovery program which is touch sensitive:
GSM: http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.1.0-maguro.img
Sprint: http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.1.0-toroplus.img
VRZ: http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.1.0-toro.img

Step 12 finishes with
That's all. You are now unlocked and rooted. Reboot. Make sure you install the paid versions of rom manager, titanium backup, and update superuser app.
Click to expand...
Click to collapse
Therefore what is the need of doing #13 and 14?
Furthermore, Step 13 starts by
13- Download Rom Manager and flash the recovery again (top choice)
Click to expand...
Click to collapse
What is that top choice? Do you mean restart from the top at step #1? If you need to reflash again CWN, would it be simpler to restart from Step 10 instead of going back to the top?
And BTW, what is the reason to reflash the CWM Recovery again just after you have successfully flashed it at Step 12? Could that be #13 and #14 are some steps of an older guide which no longer apply now but you forgot to remove?
Sorry for the silly question but I am rather lost. After all that hardwork, when I attempt to Update SuperUser, it failed on the line "Gaining root access ..." What is the reason and how to fix that? FOUND ANSWER: the su.zip given in the post is Superuser 3.07 which is outdated, It is probably buggy. Replaced it by SuperSU 0.94 and it works perfect: http://download.chainfire.eu/204/SuperSU/
Thanks

worked like a charm.. if you have problem using fastboot, just cd to the folder with fastboot and run it like this:
Code:
sudo ./fastboot "command"
it will require your password and then work normally, seems like it need super user permissions.
Also for new user: to avoid writing a command or a folder name manually just push the TAB button, it will autocomplete the word if it's unique in that folder

[Q] Q Please help stupid noob. Tried 2 install new rom and failed.

Hey all. Tried to install new rom and now all I have got is the white HTC screen. Problem is I cant access recovery to fix it, tried pressing power and volume down button but all it does is reboots. Please help and i promise not to touch my phone again.

Did you flash the boot.img file with fastboot commands ?
Try this : connect the phone to the pc and open a commandprompt inside the fastboot folder then type
Fastboot reboot bootloader
or
Adb reboot bootloader
This should boot you to the bootloader and from there you can acces the recovery !

ah no, oops. I shouldnt be messing with my phone coz I aint got a clue what Im doing. How do I do what you just told me

How did you install the recovery then ?
But try this then
Download these files
http://db.tt/ldx3qOOU
And put them on the pc looking like this
C\fastboot\files i gave you
Then install the HTC drivers (google) if you didn't do that already
Open a dosprompt inside the fastboot folder and type
Fastboot reboot bootloader
or Adb reboot bootloader
If that doesn't work hold down the power button and the volume - button together as long as it takes to see the bootloader !

First off thanks for your help. Tried that but still nothing. I got a htc all in one toolkit but it aint reconnising my phone.

Thank you, thank you, thank you and a million times thank you. Im in recovery, yay. Thank you again.

Then you have to install the java sdk platform tools too ....
http://forum.xda-developers.com/showthread.php?t=1605720
Read this too carefully...
But did you get in by holding the buttons or the commands, and what recovery do have at the moment
Please answer the questions carefully and right, so i can help you the right way

Will read that thread now. Got into recovery by holding the buttons down for what seemed like10 mins. Got clockworkmod recovery.

Oke wich one ? Is it 5.8.4.0 if yes leave the phone sitting in the recovery because it will charge the battery ! Leave it connected to the pc or wallcharger. You should see a red light of charging !
And try to get the fastboot stuff working its necessary to flash the kernel and maybe a different recovery if the one you are using is to old.
But how did you flash the recovery ?

I don't know which ROM you were flashing but here is what you can do:
Things I expect you have done already, according to your posts:
- Unlocked bootloader
- Installed recovery (Clockworkmod Recovery)
Things to do before you start:
- Install HTC drivers (and reboot the computer afterwards to make sure everything's working)
- setting up the fastboot files like Mr Hofs told. (so put adb.exe, AdbWinApi.dll and fastboot.exe in C:\fastboot\)
- Get the ROM (.zip) you wanted to flash, because eventually you still want this ROM .
- Have the ROM (.zip) on your phone, so you can select it in the recovery for direct installing. I will tell you how you can put it on your phone anyways so it's not a big problem if you haven't done this yet.
Now let's get started:
- Open the .zip and extract the boot.img inside this file to C:\fastboot\.
- Start up your phone in bootloader (hold volume-down, press power button)
- Select "FASTBOOT" with the volume keys to go up and down, then press power to activate it.
- Plug in the USB cable into your computer and phone, this will make your phone say "FASTBOOT USB".
- Open up the directory C:\fastboot\. Hold shift and right-click in this folder (not on a file!). Select "Open command window here".
- Now type "fastboot flash boot boot.img". Now you should see "SUCCESS". Now type "fastboot erase cache".
- Go back to your phone, and select "HBOOT", after that select "RECOVERY".
- Once loaded in recovery, select the following things:
- "wipe data/factory reset";
- "advanced" -> "wipe dalvik cache";
- "mounts and storage" -> "format /system"
- Additional tip for placing ROM on your phone! Select "mounts and storage" -> "mount USB storage". Now you see that you can put files on your phone by your computer. So place the ROM you want to install somewhere you like to.
- Press "unmount" on your phone.
- Press "install zip from sdcard" -> "choose zip from sdcard" -> "directorytoyourrom/YOURROM.zip"
- Now reboot your phone, and see the magic happen!

Dude ... did you bother to read back the few posts ???

I did actually, and read carefully. But I guess not careful enough, please explain what I missed.
He said he could get into recovery. So my assumption is also that this is CWM 5.8.4.0, because the most recent toolkits got this versuib,
So that's where I started off from.
The only mistake I could have made is not thinking of his "i promise not to touch my phone again."
But he wanted to try, it 'failed' and got a little scared. This is no reason to reset everything to stock and never try again.
Plus the fact that he now knows how to get into recovery is already a big plus, so you won't actually have to start all over.
And
Correct me if I'm wrong, but wasn't I clear enough to make it understandable for a 'noob'?

No its all about the amount of info ! Its one big post with to much info ! Let it go step by step as he stated he does not have a clue what he is doing, let him easy understand a small piece of text and get it working !

Part of your problem could be is that you have fastboot ticked you need to untick fastboot on your device and then you when you press volume down press power and hold both keys and you should boot right into boot loader with no problem
Sent from my HTC One X using XDA Premium HD app

jslim38 said:
Part of your problem could be is that you have fastboot ticked you need to untick fastboot on your device and then you when you press volume down press power and hold both keys and you should boot right into boot loader with no problem
Sent from my HTC One X using XDA Premium HD app
Click to expand...
Click to collapse
He can't ....he's in a bootloop

I understand, sorry for that.
I was also looking at the big picture: Maybe another 'noob' would pass by with the same problem, and wants to know how to do it too and might find it helpful.
But let's not go too far off topic.
I'll leave the specific help to you.

appiehappie94 said:
I understand, sorry for that.
I was also looking at the big picture: Maybe another 'noob' would pass by with the same problem, and wants to know how to do it too and might find it helpful.
But let's not go too far off topic.
I'll leave the specific help to you.
Click to expand...
Click to collapse
No problem, but that is the point, your explanation is good but for a lot of people to much to handle. They see 1 block of text with things to do and go on and start confusing things for themselves ....
Its all good with the right intentions :thumbup:

Total Nub's guide to rooting Qmobile Q Infinity & Micromax Canvas Inifinity

After failing some 1-click rooting methods, for the first time I tried to do it the hard way.
That turned out to be a pretty easy way thanks to some handy links to drivers and other files I found.
Infinity thanks to the thread I found platform-tools from and the website called "getdroidtips" for the Custom TWRP for the HS2.
NOTE: THIS GUIDE WILL WIPE YOUR DEVICE SO BE PREPARED
Standard warning: FOLLOW THIS GUIDE AT YOUR OWN RISK. REMEMBER, AS PER MY NAME I AM A TOTAL NUB. I DO NOT TAKE RESPONSIBILITY FOR YOUR PHONE MALFUNCTIONING, BRICKING, BLOWING UP OR DROWNING IN COOKING OIL (rip my Elephone S7)
Pastebin code for missing links: F2RGqM1A
1) Preparation
Download the latest Flashable.Zip from [ ]
Place SuperSu.zip in your sd card or internal storage
Enable Developer Options by going to Settings -> "About Phone" -> Click "Software Version" 7-8 times
Go to developer Options in Settings
Enable OEM Unlocking
Enable USB Debugging
Shutdown your phone by holding the power button
Boot into fastboot by holding the Volume Up key + Power Button
Press Volume Down key to get into fastboot
2) On your Windows PC:
Download the file from [ ] and extract the platform-tools folder (I extract to "D:\Downloads" in this example)
Download the Custom TWRP from [ ] and place it inside the platform-tools folder
Connect your device to your computer
press Win+R, type cmd and press enter
2.1) (not always needed)
If your device won't connect or the steps below don't work, try updating drivers:
Connect your phone while it's in fastboot
open start menu, search and open Device Manager
check inside Portable Devices or Android Devices for your phone's name
or look for Android Bootloader Interface
if it's not there, it might be named something else, with an icon that has a yellow triangle inside it.
Right click it, Update Driver
> Browse my computer for driver software
> Let me pick from a list of available drivers on my computer
> select Android Bootloader Interface
to check if you are connected, type "fastboot devices" in cmd and you'll see a device code
3) Unlocking Bootloader
In cmd, enter the following commands:
Code:
D:
cd D:\Downloads\platform-tools
fastboot oem unlock-go
THIS STEP WILL WIPE YOUR DEVICE DATA
wait for restart
4) Booting into TWRP
Go to device Settings again and ensure OEM Unlocking and USB Debugging are still Enabled. Reboot into fastboot.
In cmd:
Code:
fastboot boot twrp-3.1.1-0-20171128-UNOFFICIAL-HS2.img
(In case above cmd line doesn't work, type "fastboot boot twrp" and press Tab)
5) Backing up your rom and data (Optional but recommended)
Inside TWRP, Click Backup, tick everything, select desired directory and swipe to backup.
Reboot and follow step 5 again if needed
6) Installing SuperSU with root privileges
Inside TWRP, Click Install and select SuperSU.zip
Swipe to install and reboot
Enjoy

Please port miui 9 or lineage os 15 for micromax canvas infinity hs2

NubbyMcNubNub said:
After failing some 1-click rooting methods, for the first time I tried to do it the hard way.
That turned out to be a pretty easy way thanks to some handy links to drivers and other files I found.
Infinity thanks to the thread I found platform-tools from and the website called "getdroidtips" for the Custom TWRP for the HS2.
NOTE: THIS GUIDE WILL WIPE YOUR DEVICE SO BE PREPARED
Standard warning: FOLLOW THIS GUIDE AT YOUR OWN RISK. REMEMBER, AS PER MY NAME I AM A TOTAL NUB. I DO NOT TAKE RESPONSIBILITY FOR YOUR PHONE MALFUNCTIONING, BRICKING, BLOWING UP OR DROWNING IN COOKING OIL (rip my Elephone S7)
Pastebin code for missing links: F2RGqM1A
1) Preparation
Download the latest Flashable.Zip from [ ]
Place SuperSu.zip in your sd card or internal storage
Enable Developer Options by going to Settings -> "About Phone" -> Click "Software Version" 7-8 times
Go to developer Options in Settings
Enable OEM Unlocking
Enable USB Debugging
Shutdown your phone by holding the power button
Boot into fastboot by holding the Volume Up key + Power Button
Press Volume Down key to get into fastboot
2) On your Windows PC:
Download the file from [ ] and extract the platform-tools folder (I extract to "D:\Downloads" in this example)
Download the Custom TWRP from [ ] and place it inside the platform-tools folder
Connect your device to your computer
press Win+R, type cmd and press enter
2.1) (not always needed)
If your device won't connect or the steps below don't work, try updating drivers:
Connect your phone while it's in fastboot
open start menu, search and open Device Manager
check inside Portable Devices or Android Devices for your phone's name
or look for Android Bootloader Interface
if it's not there, it might be named something else, with an icon that has a yellow triangle inside it.
Right click it, Update Driver
> Browse my computer for driver software
> Let me pick from a list of available drivers on my computer
> select Android Bootloader Interface
to check if you are connected, type "fastboot devices" in cmd and you'll see a device code
3) Unlocking Bootloader
In cmd, enter the following commands:
THIS STEP WILL WIPE YOUR DEVICE DATA
wait for restart
4) Booting into TWRP
Go to device Settings again and ensure OEM Unlocking and USB Debugging are still Enabled. Reboot into fastboot.
In cmd:
(In case above cmd line doesn't work, type "fastboot boot twrp" and press Tab)
5) Backing up your rom and data (Optional but recommended)
Inside TWRP, Click Backup, tick everything, select desired directory and swipe to backup.
Reboot and follow step 5 again if needed
6) Installing SuperSU with root privileges
Inside TWRP, Click Install and select SuperSU.zip
Swipe to install and reboot
Enjoy
Click to expand...
Click to collapse
Hi please help me, after flashing recovery my phone is on bootloop now, what do i do

Hem97 said:
Please port miui 9 or lineage os 15 for micromax canvas infinity hs2
Click to expand...
Click to collapse
I wish I could.
Sudhangshu said:
Hi please help me, after flashing recovery my phone is on bootloop now, what do i do
Click to expand...
Click to collapse
Did you try "flashboot boot twrp..." like in my guide or "flashboot flash twrp..."?
And which twrp image did you use?
In any case, if you can still get to the fastboot screen, try booting with the twrp image in Step 4 above (download links in the pastebin link)

NubbyMcNubNub said:
I wish I could.
Did you try "flashboot boot twrp..." like in my guide or "flashboot flash twrp..."?
And which twrp image did you use?
In any case, if you can still get to the fastboot screen, try booting with the twrp image in Step 4 above (download links in the pastebin link)
Click to expand...
Click to collapse
Hi, "flashboot boot twrp" wasnt working at all, so i tried "flashboot flash twrp" and all i have is a bootloop. So after flashing recoveru i booted my phone to fastboot and run the command, " flashboot boot recovery recovery.img" where recovery is the custom recovery image and it booted into recovery. Then there is one more step to do that allowed me to finally boot into my os. Its working fine and i still have twrp installed on my phone
---------- Post added at 06:53 PM ---------- Previous post was at 06:49 PM ----------
NubbyMcNubNub said:
I wish I could.
Did you try "flashboot boot twrp..." like in my guide or "flashboot flash twrp..."?
And which twrp image did you use?
In any case, if you can still get to the fastboot screen, try booting with the twrp image in Step 4 above (download links in the pastebin link)
Click to expand...
Click to collapse
Btw i dont find any pastebin links, im sorry im just a noob too..... Lol

Want custom rom for Qmobile Qinfinity
I want a custom rom for Qmobile Qinfinity.
Because its own rom lags and does not have full features. Please give the rom like lineage os,RR,Or Stock
Please Help?:good:

hi bro,recently i just buy a new phone which is micromax canvas infinity.i have rooted my phone successfully,but there are no custom roms available for this phone.can you develop any custom rom for this phone?that will be very helpful...