http://forum.xda-developers.com/showthread.php?t=1522351&highlight=qhsusb
I found the thread to unbrick my phone. I am a little confuse on how the instruction on how to unrbrick the phone.
Under prerequisites, I need to
"a linux box/live cd with automount disabled and without unity"
What is unity?
I have Ubuntu installed on one of my computers but I don't want to continued until I know what I need to do before starting this unbricking process.
And what flavor of Linux can I use? Can I use Ubuntu?
I tried Using ubuntu,
Ubuntu will detect the device using this command
./brickdetect.sh
I unplugged it then plugged it back in, and then use the following command
sudo ./emmc_recover --backup b_hboot.img --device /dev/sdX12
It says waiting for device, then nothing.
F9zSlavik said:
I tried Using ubuntu,
Ubuntu will detect the device using this command
./brickdetect.sh
I unplugged it then plugged it back in, and then use the following command
sudo ./emmc_recover --backup b_hboot.img --device /dev/sdX12
It says waiting for device, then nothing.
Click to expand...
Click to collapse
That is because of automount.
There will, most likely, be a video tutorial that I'll be making soon.
And also, in the command, sdX needs to be replaced with the node that you got from brickdetect. That is, for example: sda, sdi, etc.
i am not an expert in this, but i do know what is Unity
here you go: http://unity.ubuntu.com/
kgs1992 said:
That is because of automount.
There will, most likely, be a video tutorial that I'll be making soon.
And also, in the command, sdX needs to be replaced with the node that you got from brickdetect. That is, for example: sda, sdi, etc.
Click to expand...
Click to collapse
I hate Linux so bad.... Great for certain things but god I just hate it ;/
So I downloaded Ubuntu 12.04 DVD version from Ubuntu website. I went and downloaded the necessary files for the unrbicking process.
I can detect my device, no issues with that.
BUT I had a hard time doing
sudo ./emmc_recover --backup b_hboot.img --device /dev/sdX12
nothing would happen even after I disable automount. I had to time it just right from when I plug the phone back in the USB and hitting enter in terminal to execute the command.
If I time it just RIGHT (took 20 tries), I can get it to back up of HBOOT. I have 1.27.
My isssue is the stupid *&^*%$% auto mounting crap. I have tried (thanks to google)
sudo apt-get install dconf-tools
after installing I then did this
dconf-editor then navigate to org -> gnome -> desktop -> media-handling: disable both automounts
Problem persisted. Nothing happens when I try to flash the hboot (because of automount)
so I tried using this command in Terminal,
gsettings set org.gnome.desktop.media-handling automount false
Same crap. I can't flash the stupid hboot. Nothing happens again when I execute the command.
sudo ./emmc_recover --flash pyrV.VV.nb0 --device /dev/sdX12 --backupafter hboot_f.nb0
I guess if I time it just right after plugging in the phone I might be able to do it.
And yes I am changing the V.VV to the corresponding file and yes I am changing X to whatever letter the phone is assign to.
I tried using the live cd provided by the OP but its even worse then te official one because I see NO WAY of disabling automount. I tried the above ways and nothing worked as far as disabling automount.
How do yo disable automount in the livecd provided by the thread?
This is the Unbricking Project thread
http://forum.xda-developers.com/showthread.php?t=1522351
I got the phone working again. I just had to time it just right.
The phone is completely back to stock with S-ON, reloaded ICS RUU, system still has the wifi issue. ;/
Related
I've searched the forums and the internet for a solution to my issue, but have thus far been unsuccessful in finding one that works. The problem itself has been covered online, but I can't seem to get the fix to work. I think I am missing a key step in all of this.
The problem: fastboot does not read my device, when the device is in fastboot mode.
$ ./fastboot devices
$
Click to expand...
Click to collapse
If I try to run a fastboot command, it sits eternally on <waiting for device>.
I am running a fresh install of Ubuntu 9.04 and have followed the instructions for getting the source build and all of that went great (after opening the git port in my firewall). So, I have the source build now and it compiled fine, after commenting a line (637) out of external/qemu/sockets.c. Also, I have the Java version of Eclipse 3.4 (Ganymede) and ImageMagick (current) installed.
Mainly, I want to get everything working correctly so that I can dev on the device and create custom builds, but I figured I would start small. Splash screen flashing. No joy. I got the image resized and converted correctly, but I cannot seem to get my G1 to show up in fastboot or adb. One site said I needed to tweak the UDEV, which I did, but I am not sure if I did so correctly. I think I need to reset the drivers, most likely, but I haven't a clue how to go about that. Most of the tutorials I find are for Windows/Cygwin.
Anyone have any suggestions? Thanks in advance.
My sig is outdated, so here is what I am working with:
G1 with JF's ADP1 cupcake build, rooted with HSPL, busybox & Debian, JF's cupcake radio.
Ubuntu 9.04 with sun-java5-jdk, eclipse 3.4, Android source build (master manifest) [compiled], ImageMagick
make sure that you do "adb remount" as root and all other commands too. Even if you load the adb deamon as non root and use root for following commands it will still not work. You will have to kill the adb server and start again.
"su adb kill-server"
(I think that will kill the server for you)
if fastboot says waiting for device then there's no device it can recognize...
can you use adb under normal system?
I found the problem. I forgot to run the following command:
Code:
chmod a+rx /etc/udev/rules.d/50-android.rules
That is all that was holding me back the last day and a half! Sorry if I wasted anyone's time and thanks pixel-painter, who reminded me of something else I was doing wrong.
Hey guys, I am a pretty new to ADB, I spent all day yesterday trying to figure it out and I think I have a fairly loose understanding of how it works. But, my question is what are the differences in the rooting guide if I'm trying to root on a Mac?
yea unfortunately for us mac users trying to root any device is very scarce, most if not all rooting methods require windows, even if they say works for mac, it usually doesn't for some reason.
I use VM ware, just torrent it for free, and torrent a windows 7 as well, if ussed this to root my older Droid model.
Rooting a phone using ADB on a Mac is no different than on Windows. IMO it's easier on osx/linux, as you don't have to worry about USB drivers.
Assuming you don't have a PATH variable setup for the platform-tools directory, just type "./adb whatever" instead of "adb whatever". That's about the only difference.
GrdLock said:
Rooting a phone using ADB on a Mac is no different than on Windows. IMO it's easier on osx/linux, as you don't have to worry about USB drivers.
Assuming you don't have a PATH variable setup for the platform-tools directory, just type "./adb whatever" instead of "adb whatever". That's about the only difference.
Click to expand...
Click to collapse
+1. It's SOOO much easier on a Mac, no driver issues, same basic command lines.
The only time it's easier on Windows is if there's some one-click method that requires a windows executable...but you still have to worry about getting Win to recognize the phone.
Edit: to answer the original post, there's no difference. Just put ALL the files into the same folder on your computer. Open the terminal app, type in cd then drag and drop the folder onto the terminal and hit enter. Type in ls and enter to make sure the files are actually there. After that, just follow the guide step by step. You can even drag and drop or copy/paste the commands. That's what I did (to make sure I made no typos).
Come to think of it, if OSX has curl installed on it (which I have no clue if it does or not), the linux easyroot script in the development forum should work just fine.
If not you could probably just change curl to wget and it would work fine. I'm assuming OSX comes with wget.
GrdLock said:
Come to think of it, if OSX has curl installed on it (which I have no clue if it does or not), the linux easyroot script in the development forum should work just fine.
If not you could probably just change curl to wget and it would work fine. I'm assuming OSX comes with wget.
Click to expand...
Click to collapse
OS X comes with curl.
Hi guys, I have been having major reboots problem with my Sensation after upgrading to the new ICS firmware. I have described my problem in this thread. The last attempt to fix my problem was flashing the firmware from this thread. I'm trying to flash other firmwares from the development section, but i keep getting the wrong model ID error. After some research, I believe I need to change my phone's CID to superCID using ADB.
And I have followed the instructions from this thread to do the superCID on my phone. Unfortunately, ADB is not detecting my phone. I installed ADB on two other Windows machines with the same result. Any help is greatly appreciated.
If you're running ADB from Linux (Ubuntu or something like it) by chance, you can run the commands as root. Put 'sudo' in front of the commands. That might fix it.
Also, try killing the server and restarting it. I don't know if this works in Windows.
Linux commands....
sudo ./adb kill-server
sudo ./adb start-server
./adb devices
Windows commands....if this even works in Windows (I've never tried using ADB in Windows so I have no idea)
Same, just take out sudo and "./"
Not sure if needed, but do you need to have HTC sync for adb to work properly?
Skipjacks said:
If you're running ADB from Linux (Ubuntu or something like it) by chance, you can run the commands as root. Put 'sudo' in front of the commands. That might fix it.
Also, try killing the server and restarting it. I don't know if this works in Windows.
Linux commands....
sudo ./adb kill-server
sudo ./adb start-server
./adb devices
Windows commands....if this even works in Windows (I've never tried using ADB in Windows so I have no idea)
Same, just take out sudo and "./"
Click to expand...
Click to collapse
Thanks for the reply buddy. I don't have any machine running Linux at the moment, but I will try killing the server in Windows.
In the mean time, can anyone help me find an older/stable firmware please? My phone have been rebooting every 2 minutes. Opens camera, reboots. Opens youtube app, reboots. Makes a call, reboots. It's driving me crazy!!
i had the same problem when i tried to flash the radio for my new ics...
so what i did was to to untick and retick the usb debugging mode and suddenly my windows 7 can automatically install some drivers in my computer... i also install htc sync too... then only my phone can be detected by my computer and i was able to flash the radio...
Thank you for the help guys. It turns out i didn't install HTC Sync. I just flashed a new firmware from the dev forum. Hopefully it will solve my nightmare.
I have come to the conclusion that the latest firmware broke all the gingerbread based rom , and so far only the 4.0.3 Sense ROM works, and not even the asop based 4.0.3 rom.
Sent from my HTC Sensation using Tapatalk
i ditched windows ages ago and i will never look back i am sick and tierd of waiting on moto uk to push ics. i use to have the dell streak and i rooted that but i was on windows then how do i root my xoom with linux mint is it possible and can any point me in the right direction please
Stand by, I will give you all the tools and options you need to do so, I could draft something tomorrow morning.
Sent from my PG86100 using Tapatalk
Thank you megabiteg Still learning linux but i Love it
megabiteg said:
Stand by, I will give you all the tools and options you need to do so, I could draft something tomorrow morning.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
well, it isn't that hard since everything you really need on your computer ist fastboot and a way to push a file to an sdcard (fat formatted)...
Just go here, download and install the android sdk from there. Make sure the commands adb and fastboot are in your path. (test by issuing adb devices, shold return a list of attached android devices with usb debugging turned on)
After that, just follow these instructions. I am not sure if you need to run fastboot as root, but you'll see
Cheers for the info just by any chance do you know the commands still learning Linux
llama-power said:
well, it isn't that hard since everything you really need on your computer ist fastboot and a way to push a file to an sdcard (fat formatted)...
Just go here, download and install the android sdk from there. Make sure the commands adb and fastboot are in your path. (test by issuing adb devices, shold return a list of attached android devices with usb debugging turned on)
After that, just follow these instructions. I am not sure if you need to run fastboot as root, but you'll see
Click to expand...
Click to collapse
elsworth1983 said:
Cheers for the info just by any chance do you know the commands still learning Linux
Click to expand...
Click to collapse
thought you ditched windows ages ago?
anyhow... don't have linux set up atm, so this will from memory and might contain some errors... Also, never tried mint, I always stuck to debian or debian-derivates...
anyhow, lets try this:
first, use your package management-system to install a jre (java runtime environment.
If that is set up, install the android sdk:
Code:
$ cd ~
$ wget http://dl.google.com/android/android-sdk_r17-linux.tgz
$ sudo su
[enter your su-password]
# cd /usr/local
# tar xfzv ~[yourusername]/android-sdk_r17-linux.tgz
# ./android-sdk-linux/tools/android
a window should open up and list some files available for download. Just select "Android SDK Platform-tools" and hit "Install 1 package...".
once that's finished (might take a while), close the Android SDK Manager and you should get back to your shell.
Code:
# ln -s /usr/local/android-sdk-linux/platform-tools/adb /usr/local/bin/adb
# ln -s /usr/local/android-sdk-linux/platform-tools/fastboot /usr/local/bin/fastboot
# exit
$ rm android-sdk_r17-linux.tgz
now, connect your xoom to your computer and enable usb debugging in the settings of your xoom. If you issue adb devices, you should get something like
Code:
List of devices attached
043c12343456476547 device
if you receive something like bash: adb: command not found, something went wrong somewhere. Try the same using sudo: sudo adb devices if that doesn't fix it please write another post.
Also, if you encounter an error after entering any of the comments above, please do not continue until you resolved that error. (For example ask for a solution here)
And, since you are still learning to use linux: whenever instructions contain a $ or # at the beginning of a line, DO NOT ENTER THESE. They are just there to tell you to issue that command as normal user ($) or superuser (#)
/EDIT: btw: there may be an easier way to do this if you just want to use adb/fastboot this once: you could try to simply download the adb and fastboot- binaries and put these into the folder with your recovery.img-file. Might work, not sure about that, though. Also, since I don't have linux installed on my machine atm, I can't provide you with a link to these binaries.
cheers for all your help will give this a go "Dont want to back to windows
Android SDK manger log
Error Stopping ADB server failed (code-1)
Connected the xoom and did adb devices and it listed the xoom with no errors in the terminal Thank you again ? Were do i go from here now
glad to read it's working
just follow the instructions in this thread That will help you to install a custom recovery and root your xoom. It will not, however, install a custom rom. To do that, you'd also need to download a custom rom (usually comes in a flashable .zip-file), place that on an acutal sd-card which you're gonna put into your xoom, and install that file from within the custom recovery. Just make sure you grab a rom that works with your xoom (for example, you shouldn't put a us-4g-rom onto a wifi-only-xoom and vice versa)
have i done something wrong
god-WE174AA-ABU-s5306uk god # adb reboot bootloader
god-WE174AA-ABU-s5306uk god # fastboot oem unlock
fastboot: command not found
The problem i seem to be having is when the xoom is on i type <adb reboot bootloader> The xoom reboots to the fastboot screen after that no commands work and when i do ADB devices in the terminal the device list is empty ?
elsworth1983 said:
have i done something wrong
god-WE174AA-ABU-s5306uk god # adb reboot bootloader
god-WE174AA-ABU-s5306uk god # fastboot oem unlock
fastboot: command not found
Click to expand...
Click to collapse
have you done the # ln -s /usr/local/android-sdk-linux/platform-tools/fastboot /usr/local/bin/fastboot? The error you're getting seems to suggest that it can't find the fastboot application? What happens if you type /usr/local/android-sdk-linux/platform-tools/fastboot oem unlock?
elsworth1983 said:
The problem i seem to be having is when the xoom is on i type <adb reboot bootloader> The xoom reboots to the fastboot screen after that no commands work and when i do ADB devices in the terminal the device list is empty ?
Click to expand...
Click to collapse
that is expected. adb is only available while android is booted up, fastboot is the protocol to use while in bootloader mode. As indicated before, I suspect that your computer can't find the fastboot application (on the computer).
Cheers for all the info i went back and started all from the top again only thing i am struggling with is Flashing the recovery now lol i get
god-WE174AA-ABU-s5306uk god # adb reboot bootloader
god-WE174AA-ABU-s5306uk god # fastboot flash recovery recovery-solarnz-100611-1150.img
error: cannot load 'recovery-solarnz-100611-1150.img'
I have it on a memory card which i checked which was working
elsworth1983 said:
Cheers for all the info i went back and started all from the top again only thing i am struggling with is Flashing the recovery now lol i get
god-WE174AA-ABU-s5306uk god # adb reboot bootloader
god-WE174AA-ABU-s5306uk god # fastboot flash recovery recovery-solarnz-100611-1150.img
error: cannot load 'recovery-solarnz-100611-1150.img'
I have it on a memory card which i checked which was working
Click to expand...
Click to collapse
The recovery image needs to be on your pc. It doesn't matter where on your pc as long as you can access it and know where it is.
Fastboot works by sending the image over the usb cable. Once you start flashing roms, those will need to be on your sd card within the xoom.
all i can say is thank you for all the information every 1 is giving me my head is mashed lol so if i put recovery-Tiamat-R4c-100611-1150-cwm.img on the desktop what would the terminal code be
kofrad said:
The recovery image needs to be on your pc. It doesn't matter where on your pc as long as you can access it and know where it is.
Fastboot works by sending the image over the usb cable. Once you start flashing roms, those will need to be on your sd card within the xoom.
Click to expand...
Click to collapse
depends on where your desktop is If it is in ~/Desktop/, then the correct command should be
Code:
fastboot flash recovery ~/Desktop/recovery-Tiamat-R4c-100611-1150-cwm.img
error: cannot load '/root/Desktop/recovery-Tiamat-R4c-100611-1150-cwm.img'
ARRRR i am really loosing the will to live ;-)
What am doing so wrong its lucky am not bold yet been trying this all day
elsworth1983 said:
error: cannot load '/root/Desktop/recovery-Tiamat-R4c-100611-1150-cwm.img'
ARRRR i am really loosing the will to live ;-)
Click to expand...
Click to collapse
if the graphical interface, where do you see the file located?
elsworth1983 said:
error: cannot load '/root/Desktop/recovery-Tiamat-R4c-100611-1150-cwm.img'
ARRRR i am really loosing the will to live ;-)
Click to expand...
Click to collapse
Sounds to me like you are running the commands as root. You likely have also downloaded the recovery image as a normal user. This means the '~' shortcut for the home directory is pointing you to someplace where the file is not.
Try using "fastboot flash /home/Your username/Desktop/recovery-Tiamat-R4c-100611-1150-cwm.img"
I have put the file on the desktop ? is that what u mean
Hi everyone, I've been doing a good bit of googling and found nothing yet, so if this has been asked before I'm very sorry but I haven't yet seen anyone on the forum with the exact same issue. I actually updated to JB OTA when I first got the device in Canada (US version), when I got back to the UK I decided to root, but then found out that you can't on JB, luckily I managed to downgrade to ICS V9.4.5.30 downloaded from the ASUS website! I was not able to downgrade to an earlier version however, stock recovery wouldn't allow it so NVFLASH root method is out the window... Now I would prefer not to unlock my bootloader for now.
When running debugfs.bin 1 click root method, on my desktop (not run as admin) it says:
Waiting for device to be detected...
* daemon not running. starting it now on port 5037 *
*daemon started successfully *
'find" is not a recognized as an internal or external command, operable program or batch file.
Less than half a second later it just closes down.
When run as admin, it does the same thing and instead of closing down it goes back to the first screen where you can select what method you want to use.
On my netbook it runs and just stops at daemon started successfully, the tablet has no response and debugfs just stays on that screen till I close it down.
Both my computers have all the correct drivers and the latest version of debugfs running, both are windows 7 Ultimate 64-bit.
Please help me as my Infinity is just sitting around doing nothing as when I downgraded to ICS all 190 apps I installed were wiped too, and obviously there's no point me reinstalling any apps till I get this bad boy rooted...
Many thanks in advance!
Make sure you're connecting to a USB 2.0 port, not 3.0, on your computer.
Try not to use any intervening USB hub.
Try to make sure that you're using the back ports on a desktop machine as sometimes the front ports and be a bit sketchy.
Reboot both tablet and computer before starting, and as always, make sure the tablet has USB debugging enabled.
only my netbook has usb 3.0 and I used the 2.0 port, I will now try the back ports of my desktop, I didn't use any extensions or usb hubs, I have debugging and unknown sources checked. I have tried the restarting already, which I'll do right now again... thanks though..
Code:
@adb kill-server
@adb wait-for-device
@adb shell mount | find " /system" | call RootDebugfs.bat x
That is where you're system is tripping up. For some odd reason when it runs that part of the script, it trips up.
It's not a device not found error, b/c it would 1) say that, and 2) never make it to that last line, just hang at the previous line. Yet when I connect my Infinity it works perfectly fine on mine. For some reason the command "find /system" is not working correctly on your system after performing the shell mount command.
Do you have the Android SDK installed on your system?
Android SDK and Java DK were not installed, just installed them still exactly the same issue, haven't rebooted since installing them though
Is there a way I could use Linux to root, as I do have Linux Mint running?
johnlgalt said:
Code:
@adb kill-server
@adb wait-for-device
@adb shell mount | find " /system" | call RootDebugfs.bat x
That is where you're system is tripping up. For some odd reason when it runs that part of the script, it trips up.
It's not a device not found error, b/c it would 1) say that, and 2) never make it to that last line, just hang at the previous line. Yet when I connect my Infinity it works perfectly fine on mine. For some reason the command "find /system" is not working correctly on your system after performing the shell mount command.
Do you have the Android SDK installed on your system?
Click to expand...
Click to collapse
I dunno why it is not working then. What you're doing is exactly what I did *successfully* to root my Infinity and then take the JB upgrade ans restore root.
I have another file called Infnity Root that you can try: check your PMs for the link
johnlgalt said:
I dunno why it is not working then. What you're doing is exactly what I did *successfully* to root my Infinity and then take the JB upgrade ans restore root.
I have another file called Infnity Root that you can try: check your PMs for the link
Click to expand...
Click to collapse
Thanks so much anyway! I've already tried that file, it's exactly the same
Yeah, it looked very similar, but it included more things in the actual Download like the drivers.
Not sure why it is not working - can you run those three commands in a command prompt window and see what you get?
well they say 3's a magic number, computer number 3 worked! For some reason something on my desktop and netbook was causing the root to fail, now I'm updating to jb ota... Thanks for the quick responses otherwise I would have assumed the problem was with the tablet and not my machines...
Glad you got it working. Quite possibly an antivirus program, firewall, or other such problem.