Database Info

Help...Bricked

Hey all -
So I followed instructions very specifically for rooting my Xoom on my Mac, and successfully unlocked the Xoom. As soon as I flashed the rootboot.img I rebooted and cannot get past the Motorola logo. I can get into Android Recovery, Fastboot and RSD protocall support but my Mac does not recognize it when I type in ./adb devices....what shall I do? I already performed Factory Reset but this didn't help.
P.S. When I say I followed instructions carefully, that is not to say this is anyone's fault but my own. I obviously did something wrong, and am realizing now that I flashed a 3.0 img file on my 3.1 Honeycomb...this is probably where I went wrong.
Any help would be greatly, greatly appreciated.
Thanks

I had a similar situation using rootboot, don't worry....download the proper boot.img from tiamat's thread, and flash it via fastboot the same way you did the previous one and reboot. That should fix you right up.
And your Xoom is nowhere near bricked, just a little confused. It will be alright.
Sent from my GT-I9000 using XDA Premium App

ah so quick! thank you thank you thank you. how do i flash it if the device won't show up though?

I had to turn USB debugging on in order for my Mac to recognize the Xoom when i typed in ./adb devices...obviously I can't do that now, so it won't show up. Any way we could talk on AIM or something like that so it's easier to communicate?

bloodmut said:
I had to turn USB debugging on in order for my Mac to recognize the Xoom when i typed in ./adb devices...obviously I can't do that now, so it won't show up. Any way we could talk on AIM or something like that so it's easier to communicate?
Click to expand...
Click to collapse
You said you could get into fastboot, yes? Power the Xoom down with power + volume up, reboot into fastboot with power + volume down, plug in the USB, open a prompt in the same folder as you have the new boot image and use the same command that you did before....should have been something like fastboot flash boot boot.img.
That is what worked for me in much the same situation.
Sent from my GT-I9000 using XDA Premium App

It keeps saying unable to create a plugin over and over and over

Ah ok wait. I needed to shut down Parallels. The command ran, but it said failed in terminal. On the Xoom, it says "Boot command is not allowed on consumer devices, Failed to process command error (0x8)"

bloodmut said:
It keeps saying unable to create a plugin over and over and over
Click to expand...
Click to collapse
Unable to create a plugin....hmmm..that one is new to me.
Still don;t panic. If there is a way to get into Fastboot then there is a way to install a new boot image.
Did you type adb remount to start out?

Just unlocked it again using ./fastboot-mac oem unlock...but when i type ./fastboot-mac boot boot.img it says the boot command is not allowed on consumer devices even though I unlocked it...also could you link the .img i'm supposed to use just so I can be sure lol

and no ./adb devices doesn't show my xoom

Here is the boot image...
http://forum.xda-developers.com/showthread.php?t=978013
and shouldn't the command be:
./fastboot-mac flash boot boot.img

Okie Dokie I'm a damn idiot. Flashed it successfully and am at the welcome screen. Thank you so much for helping me, at least I got some practice in with adb and fastboot commands!

bloodmut said:
Okie Dokie I'm a damn idiot. Flashed it successfully and am at the welcome screen. Thank you so much for helping me, at least I got some practice in with adb and fastboot commands!
Click to expand...
Click to collapse
No worries...I viewed it the same way. Down the line the knowledge you have been getting with this process will serve you well. Anyone can one-click, but doing it this way we learn how and why things work in Android.

Absolutely. One last thing. I only flashed the boot.img and the Wifi says "error" under settings...should I have flashed anything else? I downloaded the stock image files and am considering flashing those and starting from scratch

Ended up flashing stock boot, system, and recovery images and am back to stock with no problems. Again, thank you for your patience and help.

bloodmut said:
Absolutely. One last thing. I only flashed the boot.img and the Wifi says "error" under settings...should I have flashed anything else? I downloaded the stock image files and am considering flashing those and starting from scratch
Click to expand...
Click to collapse
Actually I would go in and flash Tiamat's kernel via CWM. That worked for me in restoring my wifi.
Otherwise you can run the following commands to restore wifi (I think...)
adb push bcm4329.ko /system/lib/modules/bcm4329.ko
adb push cifs.ko /system/lib/modules/cifs.ko
adb push tun.ko /system/lib/modules/tun.ko
adb push scsi_wait_scan.ko /system/lib/modules/scsi_wait_scan.ko
EDIT....OR you can just go back to stock and start again. Good luck.

Phone Kinda Bricked

I have HTC Panache. I tried to install Ice Cream Sandwitch on my Phone
http://forum.xda-developers.com/showthread.php?t=1341847&page=17
The phone rebooted using ROM manager. it was extracting. I believe I pressed the power button. Anyways, the phone rebooted and now its just showing the MI logo and a sound that indicates that its a new rom but doesnot goes futher..
I tried to reboot using adb . But when I go into the Clockwork mod recovery, it just shows a hat with a yellow round arrow underneath it. My Clock work mod recovery version is 5.0.2.0

Just discovered
My version is as follows. Is it some thing to be worried ?
<6>[ 6.091674] mmcblk0: mmc0:0001 M4G2DE 2.10 GiB

Your recovery is corrupt. Assuming you have s-off, you can try flashing cwm recovery through bootloader via adb. Search the forum and you will find instructions on how to do that.

chem.manish said:
Your recovery is corrupt. Assuming you have s-off, you can try flashing cwm recovery through bootloader via adb. Search the forum and you will find instructions on how to do that.
Click to expand...
Click to collapse
find the recovery file, rename to "recovery.img" for easy typing, and put it in your adb tools folder.
reboot your phone into bootloader (volume down/power), and connect to computer. when connected to the computer, the phone should automatically switch into fastboot USB mode
type:
Code:
fastboot devices
to make sure device is seen. if it is, proceed. if not, get the drivers.
TYPE THIS EXACTLY!!!
Code:
fastboot flash recovery recovery.img
it should give you a # of bytes sent or something like that
then type
Code:
fastboot reboot recovery
and welcome back to clockworkmod recovery!
if this helped, hit the thanks button.

saranhai said:
find the recovery file, rename to "recovery.img" for easy typing, and put it in your adb tools folder.
reboot your phone into bootloader (volume down/power), and connect to computer. when connected to the computer, the phone should automatically switch into fastboot USB mode
type:
Code:
fastboot devces
to make sure device is seen. if it is, proceed. if not, get the drivers.
TYPE THIS EXACTLY!!!
Code:
fastboot flash recovery recovery.img
it should give you a # of bytes sent or something like that
then type
Code:
fastboot reboot recovery
and welcome back to clockworkmod recovery!
if this helped, hit the thanks button.
Click to expand...
Click to collapse
Correction, first command should be-
fastboot devices

Ok. I did flashboot the recovery. then it installed the rom automatically. Now I am on MyTouch4g T-Mobile ROM. I Installed ROM Manager but following are the errors now
Flash ClockWorkMod :- An Error occured while attempting to run privileged command !
Same happens when I click on Install ROM. In start, it says that No Super User found. Though, I am sure I rooted the phone. Thats why I have a new ROM on my phone
--
When I write Fastboot it says, it is not a recognizable command

ahaseeb said:
Ok. I did flashboot the recovery. then it installed the rom automatically. Now I am on MyTouch4g T-Mobile ROM. I Installed ROM Manager but following are the errors now
Flash ClockWorkMod :- An Error occured while attempting to run privileged command !
Same happens when I click on Install ROM. In start, it says that No Super User found. Though, I am sure I rooted the phone. Thats why I have a new ROM on my phone
--
When I write Fastboot it says, it is not a recognizable command
Click to expand...
Click to collapse
Do you have superuser installed on your phone?
Do you have adb installed on your computer?
Sent from my HTC Glacier Sense 3.5 using xda premium

saranhai said:
Do you have superuser installed on your phone?
Do you have adb installed on your computer?
Sent from my HTC Glacier Sense 3.5 using xda premium
Click to expand...
Click to collapse
He sure has adb if he sees that privileged command error.
I would suggest now you find full pd15img.zip which has rom, recovery and flash thru bootloader. Once you are up and running stock, re-root the device.

He has S-OFF, but he doesn't have engineering bootloader. Which makes him unable to run fastboot commands. That's the standard bad news for those who root and don't flash engineering bootloaders.
But, his phone boots to adb, which is good enough - so the engineering bootloader could be flashed by adb, or at least the recovery could be flashed by adb. The last one can be done using flash_image executable while in adb root shell.

Off topic but what the engineer bootloader what the differences between are regular boot loader ?
Sent from my Tweaked out RCmix3D myTouch 4G via xda premium !

Tez MyTouch said:
Off topic but what the engineer bootloader what the differences between are regular boot loader ?
Sent from my Tweaked out RCmix3D myTouch 4G via xda premium !
Click to expand...
Click to collapse
eng bootloader you can use fastboot with, and you can change more stuff.
correct me if i'm wrong...

chem.manish said:
He sure has adb if he sees that privileged command error.
I would suggest now you find full pd15img.zip which has rom, recovery and flash thru bootloader. Once you are up and running stock, re-root the device.
Click to expand...
Click to collapse
You mean I should follow all the steps of rooting once again ?
Jack_R1 said:
He has S-OFF, but he doesn't have engineering bootloader. Which makes him unable to run fastboot commands. That's the standard bad news for those who root and don't flash engineering bootloaders.
But, his phone boots to adb, which is good enough - so the engineering bootloader could be flashed by adb, or at least the recovery could be flashed by adb. The last one can be done using flash_image executable while in adb root shell.
Click to expand...
Click to collapse
So you mean, I should install bootloader using adb again ?
What was the command flash ... ?
When I type reboot recovery, it goes into the bootloader and a phone appears.. Thats all

When your phone is booting, run "adb shell" and watch. The "#" sign should appear.
If the shell stays and doesn't drop out when the phone is bootlooping (the sign is still there after 2-3 minutes) - you're good to go.
WARNING: YOU'LL BE FLASHING BOOTLOADER. WRONG MOVE - AND YOUR PHONE IS A BRICK.
Since you're already running a rooted OS, "adb shell" should present you with "#" sign.
The thread below has steps to flash engineering bootloader. Don't use those steps, but download the bootloader and check the md5sum (do me a favor and don't ask how to do it, simple googling will spill you 200000000 answers). Put the bootloader into your ADB directory.
http://forum.xda-developers.com/showthread.php?t=858996
Direct link to the file: http://www.megaupload.com/?d=NN5726Z8
md5sum: df4fd77f44993eb05a4732210d2eddc6
Now, to flash engineering bootloader while you're in the ADB root shell, use these steps:
Open Windows' Command prompt in the ADB directory (DO NOT enter ADB shell yet!).
Type (EXACTLY as below):
adb push hboot_dhd.nb0 /data/local/
adb shell
("#" should appear)
cd /data/local/
dd if=hboot_dhd.nb0 of=/dev/block/mmcblk0p18
You should see something like: 2048 bytes in 2048 bytes out 1048576 bytes copied blah blah blah
Now reboot into bootloader, see that you have 0.85.2007 version, enter FASTBOOT mode (select FASTBOOT with volume keys and press power button), and from there you can follow the suggestion above to fastboot flash the recovery, or anything you want.
And on the side note: you won't see any ICS in MIUI that you've attempted flashing. You should have read the thread - it clearly says "all the ICS changes are under the hood, visually it's just a regular MIUI".

I do not see # sign when i type adb shell..
Means I have to root again ?

What do you see? "$"?
In that case, try typing "su" and see if it brings you root.
If it doesn't - you can try to achieve temp root like when downgrading, using fr3vo.
For instructions - section "gain temp root" from the following thread:
http://forum.xda-developers.com/showthread.php?t=1178912
In case it doesn't help you - you'll need to apply PD15IMG in bootloader as suggested to bring you back to stock, and then re-root.

this link returns me error
an error occured while running the exploit <-1> errno 25..
Probbaly because its already exploited may be ?
I am stuck and confused..
Dont know what to do :S

Jack_R1 said:
In case it doesn't help you - you'll need to apply PD15IMG in bootloader as suggested to bring you back to stock, and then re-root.
Click to expand...
Click to collapse
This.
Please google up "mt4g return to stock" or "mt4g apply pd15img", I'm sure there are enough guides to find.

Though applying pd15img.zip is pretty simple, there is even a simpler way for you to return to stock - just find the panache ruu executable in dev section, connect your phone to pc and run that exe.

Is this the file you are referring to ?
http://dl.dropbox.com/u/25823285/RUU...466_signed.exe
I have heard about phones being bricked. So do I need to be extra careful ?

It worked. Great. Now I am on HTC Sense. 2.1 !
Sounds great
Now should i start from zero again ?

Fastboot cant find device in linux? Try this...

I wanted to post this as a reply to some peoples problems in this thread but the posting rules dont allow me access to development forums.......
I was trying to use fastboot but it kept hanging saying it was waiting for the device.
> ./fastboot flash recover recovery-Tiamat-R4c-100611-1150-cwm.img
< waiting for device >
Click to expand...
Click to collapse
using "fastboot devices" gave me the clue
> ./fastboot devices
no permissions fastboot
Click to expand...
Click to collapse
TO FIX IT: I ran the command as root.
> su
> ./fastboot devices
028841444160c3d7 fastboot
Click to expand...
Click to collapse
and then my device showed up and as root I could continue flashing my Xoom.
Hope this helps someone else.
And completely as a side note, does it take anyone else 20 tries to pass every damn captcha on this site?

had same problem, used same fix.
thak you for posting an update, most of the user put just solved, without thinking that other people may need the same solution

thx,
but how can use i fastboot without root ?

rabiny said:
thx,
but how can use i fastboot without root ?
Click to expand...
Click to collapse
You can use udev rules to make fastboot accessible for normal users.

dreamcwli said:
You can use udev rules to make fastboot accessible for normal users.
Click to expand...
Click to collapse
Could you please post a link of this "udev" software? My friend's Xoom updated to 4.0.3 via OTA and he can't get any USB connection recognised by the computer. We've tried everything. It's not rooted and fastboot doesn't work because his bootloader is still locked.

Could you please post a link of this "udev" software? My friend's Xoom updated to 4.0.3 via OTA and he can't get any USB connection recognised by the computer. We've tried everything. It's not rooted and fastboot doesn't work because his bootloader is still locked.
Click to expand...
Click to collapse
udev is not a software (it is but not like you think)
in this context is just bunch of lines you need to add to file (under linux OS)
see: http://developer.android.com/tools/device.html
and here: http://wiki.cyanogenmod.org/wiki/udev

I love you
I have spent 4 hours trying to fix this whole lack of rom on my device thing. You rock.

You are a legend! This solved my problem straight away!

????????
when i use root (sudo) it just sends me back a reply with like a ton of ?
I type in sudo fastboot devices and i get
????????????????? fastboot
what do i do

You're great guys ever in the milkyway. Kiss kiss
fastboot flash recovery /usr/bin/twrp.img
< waiting for any device >
fastboot waiting error arch linux manjaro
twrp installation error
How to flash TWRP Recovery with Linux

This command "028841444160c3d7 fastboot" simply doesn't work anyway. I did it as root. Of course, I did this command with my device number but catching it from adb command

Rooted Phone, But Have To Issue SU To See In ADB?

Boy, this is frustrating! So after fixing Windows broken drivers, HTC's inability to support Windows 8, and about a dozen other things that have gone wrong, I am now trying to understand why, after rooting my phone, SU permissions is not granted automatically from the bootloader.
I'm just trying to update to a newer version of CM. When I issue "adb devices", nothing. Finally, I figured something out. If the phone is booted into CM, I got into the emulator, and issue "su" - and the prompt changes from $ to #, bingo, device shows up in ADB devices. I wouldn't be able to switch to SU if the phone weren't rooted right? I mean, I'm already running CM, so phone must be rooted?
I can't really issue "SU" from bootloader.
Not sure what to do. Can someone assist?
Thanks so much!

You don't use adb in bootloader, you use fastboot
fastboot flash recovery nameofrecovery.img
Sent from my Nexus 4 using Tapatalk 2

demkantor said:
You don't use adb in bootloader, you use fastboot
fastboot flash recovery nameofrecovery.img
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Thanks. Yes, sorry, that is what I meant. I was in fastboot. It says fastboot usb. I see "My HTC" in the device manager. But adb devices is empty. If I boot it up, start term mon, and issue "su", then adb devices shows the phone.

demkantor said:
You don't use adb in bootloader, you use fastboot
fastboot flash recovery nameofrecovery.img
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Or, are you saying I wouldn't even need to see it as a device in ADB devices in order to issue the fastboot command you specified above?

Correct, you should not be using adb when in bootloader, use fastboot, adb is only for in recovery and os
Sent from my Nexus 4 using Tapatalk 2

[Q] MAC Nexus Unlock + Root Guide?

Are there any mac detailed step by step guides of how to unlock and root the Nexus 5??
I've seen the 2 main threads here but they are step by step for windows and some of the coding has already been pointed out as wrong for the mac so I'm having a very hard time just unlocking and rooting my nexus 5 which is sitting here.
If anyone could please link me to a detailed MAC guide, I would very much appreciate it.
Thanks.

Willz said:
Are there any mac detailed step by step guides of how to unlock and root the Nexus 5??
I've seen the 2 main threads here but they are step by step for windows and some of the coding has already been pointed out as wrong for the mac so I'm having a very hard time just unlocking and rooting my nexus 5 which is sitting here.
If anyone could please link me to a detailed MAC guide, I would very much appreciate it.
Thanks.
Click to expand...
Click to collapse
I can help you out.
Download and install Android File Transfer, which will install the necessary drivers for your phone to connect to your computer. http://www.android.com/filetransfer/
Enable developer options on your phone by going to Settings > about phone and tapping the build number 7 or so times. Then go to the developer settings and enable USB debugging.
Once this is done, in your folder entitled your "username" in your Mac (the same folder that has Desktop, Documents, Downloads, etc.), create a folder titled Android.
Inside that Android folder, put these two files: http://cl.ly/SMwW and http://cl.ly/SMiC These are adb and fastboot.
Once that's done, open Terminal, type:
Code:
cd /Users/yourusername/Android
and hit enter.
Then type:
Code:
./adb devices
hit enter, and you should see your phone's serial number so long as you enabled USB debugging as described above.
Then type:
Code:
./adb reboot bootloader
hit enter, your phone will reboot to the bootloader
Download this file and place it inside the Android folder we created earlier: http://cl.ly/SMw9 This is the latest TWRP for our phones.
Into the same Terminal window, type:
Code:
./fastboot oem unlock
hit enter, WARNING: your phone will be returned to stock and your storage erased, once that's done, type
Code:
./fastboot reboot-bootloader
and hit enter to reboot back into the bootloader that is now unlocked.
Then to install TWRP, type:
Code:
./fastboot flash recovery openrecovery-twrp-2.6.3.2-hammerhead.img
and then reboot the bootloader again. I would then suggest hitting your down arrow a couple of times and booting into recovery, where TWRP will prompt you to root your device with SuperSU. Alternatively, here is the SuperSU zip that you can put onto your phone's storage and flash in TWRP. http://cl.ly/SMlk

Not sure if you missed it, but alternatively there's a Mac toolkit that's recently been posted.
http://forum.xda-developers.com/showthread.php?t=2515640

I do not want to root using a toolkit on my mac and I am trying to root on my macbook using this thread.
I keep on getting:
-bash: ./fastboot: Permission denied
after I type localhost: ./fastboot oem unlock in terminal
What's going on?

stelv said:
I do not want to root using a toolkit on my mac and I am trying to root on my macbook using this thread.
I keep on getting:
-bash: ./fastboot: Permission denied
after I type localhost: ./fastboot oem unlock in terminal
What's going on?
Click to expand...
Click to collapse
Are you cd'd into the directory where the fastboot binary is?
Also, here is a really good tutorial, Google ftw...
http://forum.xda-developers.com/showthread.php?t=1917237

0dBu said:
Are you cd'd into the directory where the fastboot binary is?
Also, here is a really good tutorial, Google ftw...
http://forum.xda-developers.com/showthread.php?t=1917237
Click to expand...
Click to collapse
Yes I am cd'd into directory and it recognizes my device until a reboot to bootloader. Then while in bootloader mode on my phone, terminal on my computer will no longer recognize my device.
I will take a look at the link though. Thank you. I dont have sdk setup on my computer, maybe thats it.

stelv said:
Yes I am cd'd into directory and it recognizes my device until a reboot to bootloader. Then while in bootloader mode on my phone, terminal on my computer will no longer recognize my device.
I will take a look at the link though. Thank you. I dont have sdk setup on my computer, maybe thats it.
Click to expand...
Click to collapse
When you're in bootloader and you type: fastboot devices what does it return?

0dBu said:
When you're in bootloader and you type: fastboot devices what does it return?
Click to expand...
Click to collapse
Its just blank after I type devices. Before I boot into bootloader though ./adb devices shows me my phones serial number

stelv said:
Its just blank after I type devices. Before I boot into bootloader though ./adb devices shows me my phones serial number
Click to expand...
Click to collapse
If adb devices shows your device you're in recovery, not bootloader

It doesn't show my device in boot loader though. Terminal says permission denied though. Maybe I'll try a different directory when I get back to my computer.
Sent from my Nexus 5

stelv said:
It doesn't show my device in boot loader though. Terminal says permission denied though. Maybe I'll try a different directory when I get back to my computer.
Sent from my Nexus 5
Click to expand...
Click to collapse
Use fastboot devices if you're in bootloader

Anyhow, the link I posted is a good tutorial, it should get you sorted. Although, even though I have ADB and Fastboot in my Path (ADB works fine), I still have to cd into the platform-tools directory to get fastboot to work. If anyone has some insight into that's I'd be all ears, but I still make it work.
Sent from my Nexus 5 using Tapatalk

Thanks guys. I got fastboot working, boot loader unlocked and twrp installed but I had to use the fastboot file from the other thread. The fastboot file in the second post this thread doesn't work correctly.
Now my next problem is I have twrp installed but it is asking me for a password and it will not backup my system. When I try to reboot I get bootloops. I can get back into fast boot though. Do I need to push a ROM file or superuser via fast boot? What is the command for that?
Sent from my Nexus 7

stelv said:
Thanks guys. I got fastboot working, boot loader unlocked and twrp installed but I had to use the fastboot file from the other thread. The fastboot file in the second post this thread doesn't work correctly.
Now my next problem is I have twrp installed but it is asking me for a password and it will not backup my system. When I try to reboot I get bootloops. I can get back into fast boot though. Do I need to push a ROM file or superuser via fast boot? What is the command for that?
Sent from my Nexus 7
Click to expand...
Click to collapse
That has happened to me also. I went ahead and flashed the factory image, and then re-flashed recovery after that and it worked fine.
Sent from my Nexus 5 using Tapatalk

0dBu said:
That has happened to me also. I went ahead and flashed the factory image, and then re-flashed recovery after that and it worked fine.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks. I saw a fix in the twrp thread as follows, so i did this. Twrp is working as normal now and no bootloops. I have the factory image downloaded too just in case. Thanks again! Everything seems to be working now.
Dees_Troy said:
If you have just used fastboot oem unlock, you should let the device boot up normally first before trying to install TWRP. If you boot TWRP first before booting normally, you will be prompted for a password. Hit cancel and got to Wipe -> Format Data. Type yes at the prompt and hit the "enter" key. Hit the home button at the bottom and Reboot -> Recovery. Unlocking the device will cause you to lose all userdata, apps, pictures, downloads, etc.
To root, when you select to reboot from the GUI in TWRP, you will be asked if you want to install SuperSU. Swiping to confirm will root your device.
Click to expand...
Click to collapse