The following will VOID your warranty but will easily unlock the Xoom for fast software flashes using a custom recovery and will allow flashing root files or manipulated system files on to your current software installation.
This will ERASE your Xoom.
1) Get the Motorola USB drivers MOTODEV > Documentation & Tools > USB Drivers (you need to sign up on their but maybe you can google this and find it as well)
2) Get the Android SDK Android SDK | Android Developers (you only really need the fastboot executable file for your host OS)
2.5) - I will soon put together a windows pack for usb drivers & fastboot so you don't have to download all this stuff just to do one task.
3) Power off your Xoom
4) Press and hold the volume down button while pressing the power button
Even after the Xoom turns back on keep it pressed down and you'll see some starting fastboot protocol text on the top left of the screen.
5) Open a command window in your sdk\tools folder (not platform tools and depending on when you get the SDK you may need to copy over some DLL files)
6) type:
fastboot oem unlock
Click to expand...
Click to collapse
7) read the warning on your Xoom's screen, hit volume up if you wish.
You're now free to put whatever data you want on your tablet. Cheers.
-- To RE-LOCK your Xoom, boot in to fastboot, and on your computer (from the tools folder):
fastboot oem lock
Click to expand...
Click to collapse
Read this warning:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You actually have to read the warning and understand it - If you have modified your Xoom's software outside of the user space you won't be able to successfully re-lock your device. You'll have to restore it back to 100% factory, which you can do here: http://developer.motorola.com/produ...utm_source=supportforums&utm_term=unlockboard (The Verizon Wireless stock software).
This wouldn't negate the free LTE upgrade would it?
I'm not sure. I'd say you should re-lock the boot loader and restore any custom stuff to factory before you send it back in though.
I'm curious, what are the hardware ids in the usb driver when the xoom is in fastboot? Is the usb driver that is active while it's in fastboot called something like single adb device?
Thanks!
Sent from my MB860 using XDA App
How do you relock it?
Sent from my HTC Vision using Tapatalk
Wow, that has to be the easiest unlock I have ever seen. Does this mean we will not have to install something like Amon's RA Recovery to flash ROMs whenever people get a chance to make them?
Also, if we issue a fastbook oem lock (or whatever the proper command is), can we then send it in for repairs? in other words, is there some history on the device that says I unlocked it?
youareme7 said:
I'm curious, what are the hardware ids in the usb driver when the xoom is in fastboot? Is the usb driver that is active while it's in fastboot called something like single adb device?
Thanks!
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Windows first found it as fastboot, then I got the moto driver from their dev site and I didn't look what it was called after that. I think a Moto composite device or something, I'm pretty sure it installed 3 drivers. I will double check when I'm back home.
djunio said:
How do you relock it?
Sent from my HTC Vision using Tapatalk
Click to expand...
Click to collapse
I'm not sure but I would say "fastboot oem lock" should probably work. - What I am really curious about is if fastboot oem unlcok writes something to the tablet somewhere that lets Moto/VZW know it was unlocked.
padanfain said:
Wow, that has to be the easiest unlock I have ever seen. Does this mean we will not have to install something like Amon's RA Recovery to flash ROMs whenever people get a chance to make them?
Also, if we issue a fastbook oem lock (or whatever the proper command is), can we then send it in for repairs? in other words, is there some history on the device that says I unlocked it?
Click to expand...
Click to collapse
We'll still need a custom recovery to make life easier, but after you unlock it you can push any files/images to wherever you want.
The unlock screen makes you agree to the fact you're voiding your warranty. I'm not sure if re-locking it will be enough and I'd venture to speculate that there should be a difference between a hardware fail and software fail for warranty work. I guess we'll see.
thefredelement said:
This will ERASE your Xoom.
Click to expand...
Click to collapse
What does this mean? Does unlocking the device wipe everything, or just wipe data/cache? Is system effected just by executing this, or are you referring to the flash process?
mikejs78 said:
What does this mean? Does unlocking the device wipe everything, or just wipe data/cache? Is system effected just by executing this, or are you referring to the flash process?
Click to expand...
Click to collapse
It's a factory reset.
i know this was the same unlock for Nexus One, but will this give us root? has anyone attempted to install SuperUser.apk and su?
koush has just tried this and did not unlock bootloader. was this done on a consumer device or developer's device?
socomdark said:
koush has just tried this and did not unlock bootloader. was this done on a consumer device or developer's device?
Click to expand...
Click to collapse
A consumer device.
Is he using the right moto dev drivers and fastboot from the 3.0 sdk?
socomdark said:
koush has just tried this and did not unlock bootloader. was this done on a consumer device or developer's device?
Click to expand...
Click to collapse
I just saw his tweet, he was trying to boot a kernel from fastboot it looks like.
thefredelement said:
I just saw his tweet, he was trying to boot a kernel from fastboot it looks like.
Click to expand...
Click to collapse
yea but it looks like he has got clockwork mod on there.
If we void the warranty what happens to the return policy? store.motorola.com 's return policy to be specific
confused
Am i supposed to hold down the volume key the whole time while I'm clicking the fastboot command. I'm a little confused if anyone help understand
You just hold down the volume down key and power button until the white fastboot protocol text appears.
cant get it
thefredelement said:
You just hold down the volume down key and power button until the white fastboot protocol text appears.
Click to expand...
Click to collapse
ok done that but when it will not open in command prompt http://media.xda-developers.com/images/smilies/mad.gif. i think i will jus give up cause something not right.. The command prompt jus pops up and immediately goes away...but thanks for the help i jus wait for the thunderbolt and root it....lol big ups to all whom do and to KOUSH!!!! that brotha is awesome
No big deal here, you have to open the command prompt properly.
If you're on windows7, then browse to the folder in windows explorer, right click on the folder and select open command window here
In windowsXP go to start, run, type in cmd and then cd to the directory where the file is located.
I just purchased a Xoom, has anyone tried to issue the fastboot OEM lock command to see if it will indeed relock the device?
Related
Hi everyone, yes i have a DHD, and i tried to root it with AAHK tool. I know that many have success, but i failed.
Now i got stuck in CWM Recovery and can't get out. Although i tried all the options in the list, but it always returns the CWM screen.
I also tried to install a Rom cook, it said that Success, but then i return again in the CWM screen.
Here it's some pic
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here it's Hboot menu
This is when i try to run AAHK tool once more.
P/S: i've read the instruction of AAHK tool before action, my phone was pure, S-On, and run Android ver 2.3.5.
P/S 2: i think in the process, my usb cable wasn't properly connected (not my fault, DHD is a old device), cos i heard the sound of something plug in and out my pc many many times
You got obtained S-OFF so you're not stuck.
Muikkuman said:
You got obtained S-OFF so you're not stuck.
Click to expand...
Click to collapse
What does that mean?
Muikkuman said:
You got obtained S-OFF so you're not stuck.
Click to expand...
Click to collapse
What do you mean? I'm stucking there.
I can't get to home screen although i tried many way. Reboot it, flash it, wipe its data, ... It always return in this CWM screen, and i call it Stuck.
Please help
july3rd said:
What do you mean? I'm stucking there.
I can't get to home screen although i tried many way. Reboot it, flash it, wipe its data, ... It always return in this CWM screen, and i call it Stuck.
Please help
Click to expand...
Click to collapse
Is your volume rocker flaw? That seems to be a hardware issue and not software. Maybe it got stuck and that is why it boots to recovery..
glevitan said:
Is your volume rocker flaw? That seems to be a hardware issue and not software. Maybe it got stuck and that is why it boots to recovery..
Click to expand...
Click to collapse
Unfortunately my volume rocker works very well
july3rd said:
Unfortunately my volume rocker works very well
Click to expand...
Click to collapse
That is not unfortunate...have you tried flashing a ruu from fastboot to see what.happens?
Sent from my GT-N7000 using xda app-developers app
glevitan said:
That is not unfortunate...have you tried flashing a ruu from fastboot to see what.happens?
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
I don't rly know much of rooting a phone, but when i use AAHK tool, it asked me if i want to load some "RUU" file and install it, i said Yes.
If that is not what u're talking, please give some construction.
july3rd said:
I don't rly know much of rooting a phone, but when i use AAHK tool, it asked me if i want to load some "RUU" file and install it, i said Yes.
If that is not what u're talking, please give some construction.
Click to expand...
Click to collapse
Are you able to boot in hboot? You don't need recovery to flash a RUU..paste the information displayed in your hboot here...
Ok, first download the zip I've attached to this post. Extract the contents, run 'Start here.bat'. Now, on your phone, go back to the hboot screen, connect your phone to your computer, and press 'power'. Verify that the phone shows 'FASTBOOT USB' in red. Now go to the cmd window that opened with 'Start here.bat', and type (or copy-paste) from here -
Code:
fastboot flash recovery openrecovery-twrp-2.4.1.0-ace.img
When it finishes and displays a 'success' message, exit cmd, disconnect your phone, use 'volume down' to highlight 'recovery' and press power to select it. Your phone will boot into this new recovery which is called TWRP. TWRP and 4ext are the best recoveries for this device. CWM is outdated, especially the version you're using. Now using this recovery, wipe your device properly by running wiping 'system' and 'factory reset/data' in the wipe menu, and then flash whatever ROM you want. It should work fine.
Note: If it fails, then you've done something and you don't have an S-OFF bootloader anymore. As long as your bootloader has the same top line as in the picture you posted, you're good. If you have run an RUU either on your own or using AAHK, and you have an S-ON bootloader now, connect your phone back in hboot mode, enable 'FASTBOOT USB' and run AAHK again. You'll end up with an S-OFF bootloader, and you can follow the above step.
Also, the sound of your phone disconnecting and connecting repeatedly to your computer was not a problem with the USB cable. It happens everytime AAHK reboots the phone, because the phone disconnects while turning off and connects back when turning on. AAHK failed the second time you ran it because it you already got a fully unlocked S-OFF bootloader in the first try. It only works if the bootloader is locked.
sashank said:
Ok, first download the zip I've attached to this post. Extract the contents, run 'Start here.bat'. Now, on your phone, go back to the hboot screen, connect your phone to your computer, and press 'power'. Verify that the phone shows 'FASTBOOT USB' in red. Now go to the cmd window that opened with 'Start here.bat', and type (or copy-paste) from here -
Code:
fastboot flash recovery openrecovery-twrp-2.4.1.0-ace.img
When it finishes and displays a 'success' message
Click to expand...
Click to collapse
Thank you for your attention, Here it's the result
Btw, each time i load into Hboot, the screen flash into this
and then he goes to the normal Hboot.
Idk if it helps anything, i just give all i got to you.
july3rd said:
Thank you for your attention, Here it's the result
Btw, each time i load into Hboot, the screen flash into this
and then he goes to the normal Hboot.
Idk if it helps anything, i just give all i got to you.
Click to expand...
Click to collapse
you can not use flash commands in fasboot as you don't have ENG S-OFF (do not flash the tradicional but the modified one in the Hack Kit)
Or flash the zip file in fastboot this way:
Boot in fastboot usb (check that in the phone is display that)
Put this zip file somewhere you can find it: https://docs.google.com/file/d/0B2d8xxQzn5owMkpCQlBibkU2amM/edit?usp=sharing.
Open a cmd as admin in the PC
Go to where the recovery zip folder is located (in cmd)
And then type:
Code:
fastboot oem rebootRUU
fastboot flash zip cwm-5.0.2.7-ace.zip (when you get the OKAY in the cmd session you are done)
fastboot reboot-bootloader
When finished, you should have CWM recovery installed
glevitan said:
you can not use flash commands in fasboot as you don't have ENG S-OFF (do not flash the tradicional but the modified one in the Hack Kit)
Click to expand...
Click to collapse
Thank you, all steps has worked, but it seems that nothing has changed. The phone reboot and still stuck at the famous CWM screen.
Btw, i now can't use AAHK tool anymore, it always say that Phone not plugged in, or Driver not installed, or USB debugging not enabled.
glevitan said:
you can not use flash commands in fasboot as you don't have ENG S-OFF (do not flash the tradicional but the modified one in the Hack Kit)
Click to expand...
Click to collapse
Ah, my bad. I completely forgot about that. I've always had ENG S-OFF I'll remember your method. :good:
sashank said:
Ah, my bad. I completely forgot about that. I've always had ENG S-OFF I'll remember your method. :good:
Click to expand...
Click to collapse
Then maybe you have another solution ?
I'm still waiting for you guys :hopefully:
Yeah. If you still have S-OFF, connect your phone in fast boot and run AAHK. Choose the option to flash ENG hboot and flash the 0.85.2425 version. Once it's done, you'll see 'ACE PVT ENG S-OFF' at the top. Now you can do again what I said in the previous post.
Sent from my Desire HD using xda premium
sashank said:
Yeah. If you still have S-OFF, connect your phone in fast boot and run AAHK. Choose the option to flash ENG hboot and flash the 0.85.2425 version. Once it's done, you'll see 'ACE PVT ENG S-OFF' at the top. Now you can do again what I said in the previous post.
Sent from my Desire HD using xda premium
Click to expand...
Click to collapse
I can't, as i said, the AAHK tool don't recognize my device anymore. I did install the driver. I'll take a screen shot for you later
july3rd said:
I can't, as i said, the AAHK tool don't recognize my device anymore. I did install the driver. I'll take a screen shot for you later
Click to expand...
Click to collapse
Because you are trying to open he Hack Kit normally, but your phone does not boot so adb can't be used. Boot in fastboot usb and then open a cmd as admin and navigate to where the hack kit is located, then type:
Code:
hack-ace.cmd fastboot
That should bring the menu to flash ENG S-OFF...
glevitan said:
Because you are trying to open he Hack Kit normally, but your phone does not boot so adb can't be used. Boot in fastboot usb and then open a cmd as admin and navigate to where the hack kit is located, then type:
Code:
hack-ace.cmd fastboot
That should bring the menu to flash ENG S-OFF...
Click to expand...
Click to collapse
Still can't
I think my phone is missing something...
july3rd said:
Still can't
I think my phone is missing something...
Click to expand...
Click to collapse
ok, do you mind if I have a look to it over teamviewer?
So today I had a problem with an app not opening correctly so I rebooted the device. The device was stuck in the kit kat boot sequence. I turned it off and charged it. Tried booting to no avail. So I go into stock recovery mode and wiped cache and then proceeded to wipe/factory reset. It then got stuck on factory reset. I let it sit there on the charger for awhile and it was still stuck on factory reset. So i rebooted to attempt again. Now it won't even go into recovery mode. It'll boot to the fastboot screen but when trying to go into recovery it gets stuck on the white Google logo. Is there anything I can do or do I need to send it back? I bought it in July-ish so it should still be on warranty.
It should be easy to restore the stock ROM. Do you have the device drivers installed and a copy of fastboot?
http://developer.android.com/sdk/win-usb.html
http://www.xda-developers.com/andro...ng-fast-adb-fastboot-and-driver-installation/
Boot your Nexus 7 to the fastboot screen, then connect it to your PC. Open a command prompt window with administrator privileges, cd to the fastboot directory (let me know if you need help here), then type the following commands:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
This will wipe everything on your Nexus 7, preparing it for a full flash of the stock recovery and ROM. You can download the stock ROM from here, and there's a "flash-all.bat" file inside that will restore recovery and the ROM all by itself.
https://developers.google.com/android/nexus/images#razor
Pandae said:
It should be easy to restore the stock ROM. Do you have the device drivers installed and a copy of fastboot?
http://developer.android.com/sdk/win-usb.html
http://www.xda-developers.com/andro...ng-fast-adb-fastboot-and-driver-installation/
Boot your Nexus 7 to the fastboot screen, then connect it to your PC. Open a command prompt window with administrator privileges, cd to the fastboot directory (let me know if you need help here), then type the following commands:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
This will wipe everything on your Nexus 7, preparing it for a full flash of the stock recovery and ROM. You can download the stock ROM from here, and there's a "flash-all.bat" file inside that will restore recovery and the ROM all by itself.
https://developers.google.com/android/nexus/images#razor
Click to expand...
Click to collapse
when trying any commands in adb it says waiting for device and hangs on that.
Use adb if your tablet is booted into Android, and use fastboot if you're only at the bootloader.
Do you have the drivers installed? At a command prompt (again must be administrator permissions), type "fastboot devices" and see if it gives a response.
Pandae said:
Use adb if your tablet is booted into Android, and use fastboot if you're only at the bootloader.
Do you have the drivers installed? At a command prompt (again must be administrator permissions), type "fastboot devices" and see if it gives a response.
Click to expand...
Click to collapse
fastboot devices does nothing. I am in the fastboot directory. I thought I had the drivers installed, but in device manager it shows up as Android with an exclamation mark
OK, that explains it. Delete the driver by hitting Del, and just to be safe, click "View" at the top, then select to show hidden devices. Delete anything else that might be for any Android devices. Then install the drivers I linked to. They're generic drivers that work with either Nexus 7 generation, plus other Nexus devices.
Pandae said:
OK, that explains it. Delete the driver by hitting Del, and just to be safe, click "View" at the top, then select to show hidden devices. Delete anything else that might be for any Android devices. Then install the drivers I linked to. They're generic drivers that work with either Nexus 7 generation, plus other Nexus devices.
Click to expand...
Click to collapse
ok done now fastboot devices shows something, typed in fastboot erase boot and it says erasing boot...seems like it is stuck on this command
wildside84 said:
ok done now fastboot devices shows something, typed in fastboot erase boot and it says erasing boot...seems like it is stuck on this command
Click to expand...
Click to collapse
Couldn't you just try to boot a recovery IMG?
fastboot boot recovery path/to/recovery.img
That will let you run recovery without flashing it
Sent from my Nexus 7 using Tapatalk 4 Pro
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Erasing boot shouldn't take too long. Hopefully the partition isn't damaged.
SwoRNLeaDejZ, I believe he couldn't get into recovery. For problems like this, I like to erase recovery and everything else anyway, especially since flash-all.bat will restore stock recovery as part of the process.
Pandae said:
Erasing boot shouldn't take too long. Hopefully the partition isn't damaged.
SwoRNLeaDejZ, I believe he couldn't get into recovery. For problems like this, I like to erase recovery and everything else anyway, especially since flash-all.bat will restore stock recovery as part of the process.
Click to expand...
Click to collapse
no commands work. on erase recovery command it says failed command write failed invalid argument
edit: fastboot boot recovery fails also "command write failed unknown error"
edit: i get a lot of fastboot.exe has stopped working errors on windows. redownloaded platform tools and still happens. I'm at a loss I guess I have to get Google to replace it entirely
I may have taken something for granted. Did you unlock the bootloader?
fastboot oem unlock
Pandae said:
I may have taken something for granted. Did you unlock the bootloader?
fastboot oem unlock
Click to expand...
Click to collapse
no and whats funny is I just got done trying that before i read your message. i restarted the device and my computer and just decided to see if it would dirty flash the flash-all.bat and it was actually going through not giving the write errors but did say bootloader is locked. so i typed fastboot oem unlock and the screen popped up on the device to say yes or no. i selected yes and it, again, got stuck for 10-15 minutes on erasing data...rebooted the device, unlock appears to have failed. argh
If you power down and reboot back into the bootloader, it still says unlocked? What if you try unlocking again?
Pandae said:
If you power down and reboot back into the bootloader, it still says unlocked? What if you try unlocking again?
Click to expand...
Click to collapse
it says the bootloader is locked. i am trying again right now. i get to the yes no screen, select yes and on the command prompt it is stuck on erasing userdata
I've never seen it take very long. Let it sit for a while, maybe plug it in and just wait?
Pandae said:
I've never seen it take very long. Let it sit for a while, maybe plug it in and just wait?
Click to expand...
Click to collapse
ill let it sit, but i think there is something wrong with the device. i had a similar prob with a gs2 and it wouldnt erase or write anything to partition. would usb debugging have to have already been enabled? i cant remember if that was checked or not. or does that matter?
USB debugging is necessary for connecting once the tablet has booted into Android, but it isn't needed for fastboot and the bootloader level. At this point I fear there's more corruption than can be fixed, but let's wait a little while and see.
Pandae said:
USB debugging is necessary for connecting once the tablet has booted into Android, but it isn't needed for fastboot and the bootloader level. At this point I fear there's more corruption than can be fixed, but let's wait a little while and see.
Click to expand...
Click to collapse
Just received an email from Google support. They are unwilling to help because I purchased the device from Best Buy rather than Google Play...WTH? Best Buy won't help either I won't even bother. At this point I'll have to hope Asus will take it in for repair. That kind of bummed me out about Google. Not sure if I want to buy another nexus device again now.
wildside84 said:
no commands work. on erase recovery command it says failed command write failed invalid argument
edit: fastboot boot recovery fails also "command write failed unknown error"
edit: i get a lot of fastboot.exe has stopped working errors on windows. redownloaded platform tools and still happens. I'm at a loss I guess I have to get Google to replace it entirely
Click to expand...
Click to collapse
use usb jig and flash via odin nice work :good:
wildside84 said:
Just received an email from Google support. They are unwilling to help because I purchased the device from Best Buy rather than Google Play...WTH? Best Buy won't help either I won't even bother. At this point I'll have to hope Asus will take it in for repair. That kind of bummed me out about Google. Not sure if I want to buy another nexus device again now.
Click to expand...
Click to collapse
Is Google writing the book "How Not to Stand Behind Your Product"? Sheesh!
Sorry I couldn't be of more help. Good luck and speedy repairs to you. I must admit that with the touchscreen problems, and that it took someone who isn't a Google employee to fix it for a lot of people, all while Google is still silent, I myself don't care to buy another product by Google and/or Asus.
---------- Post added at 12:24 AM ---------- Previous post was at 12:18 AM ----------
VerlyAnanda said:
use usb jig and flash via odin nice work :good:
Click to expand...
Click to collapse
Odin is for Samsung devices, unless something's happened I didn't hear about.
For days now I have been trying to root this HTC Wildfire (NOT Wildfire S) that my dad gave to me (so I take it that this phone is very old), because I need to install Android 2.3 on it to be able to download Skype (the phone is stuck on Android 2.2). However after trying many guides, on this website AND others, I am simply unable to do it, so that is why I am writing this forum post.
This is the HBOOT screen:
(As a new user I can not post any images or links for some reason so I just typed this
*** LOCKED (OOW) ***
BUZZ PVT SHIP S-ON
HBOOT-1.02.0000
MICROP-0622
TOUCH PANEL-ATMEL224_20aa
RADIO-3.35.20.10
Dec 13 2011, 12:08:54
HBOOT
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
FASTBOOT
RECOVERY
CLEAR STORAGE
SIMLOCK
I have tried so many different things, especially posts on this website, and have so far been unsuccessful, but that may be mainly because I am new to this type of thing.
Any help is appreciated, it seems to me that there is almost no solution, half the links to files I need for this process has turned out to be so old that it is no longer even there.
NurusS said:
I have tried so many different things, especially posts on this website, and have so far been unsuccessful, but that may be mainly because I am new to this type of thing.
Any help is appreciated, it seems to me that there is almost no solution, half the links to files I need for this process has turned out to be so old that it is no longer even there.
Click to expand...
Click to collapse
Hi there, welcome to the forum
Have you tried using my guide to root hboot 1.02.0000? What have you tried already? (Links please ) also what are you getting stuck on/at?
lastly what version of windows are you on?
Sent from my Desire S using Tapatalk
heavy_metal_man said:
Hi there, welcome to the forum
Have you tried using my guide to root hboot 1.02.0000? What have you tried already? (Links please ) also what are you getting stuck on/at?
lastly what version of windows are you on?
Sent from my Desire S using Tapatalk
Click to expand...
Click to collapse
Yes, I have. I spent a lot of time trying to use your method but it simply didn't work
http://forum.xda-developers.com/showthread.php?t=2262345 I take it you mean this post?
I have problems at step 3. When I use the htcdev instructions, when I'm on the RUU it says ERROR[191]: ROM IS NOT SUPPORTED
And after that there is nothing that I can do to continue with your instructions. I am on Windows 8.
NurusS said:
Yes, I have. I spent a lot of time trying to use your method but it simply didn't work
http://forum.xda-developers.com/showthread.php?t=2262345 I take it you mean this post?
I have problems at step 3. When I use the htcdev instructions, when I'm on the RUU it says ERROR[191]: ROM IS NOT SUPPORTED
And after that there is nothing that I can do to continue with your instructions. I am on Windows 8.
Click to expand...
Click to collapse
Okay, windows 8 can have some issues with android development but we "should" ( ) be able to get around them.
to your main issue you do not need to flash the ruu, as you already have the upgraded hboot, so skip that part and move onto getting your unlock token via fastboot.( should it say that you need to download the ruu just to move the web page along then do so, but you dont need that file.) View here for a how to on getting fastboot set up with windows 8 and view here for commonly ran into issues with windows 8. Should you get stuck or need more advice just ask pal
heavy_metal_man said:
Okay, windows 8 can have some issues with android development but we "should" ( ) be able to get around them.
to your main issue you do not need to flash the ruu, as you already have the upgraded hboot, so skip that part and move onto getting your unlock token via fastboot.( should it say that you need to download the ruu just to move the web page along then do so, but you dont need that file.) View here for a how to on getting fastboot set up with windows 8 and view here for commonly ran into issues with windows 8. Should you get stuck or need more advice just ask pal
Click to expand...
Click to collapse
Are you sure? it says S-ON, LOCKED and I'm not sure what you mean by the adb folder (where we put the BUZZ-recovery file), but it seems to work where I put it and is stuck forever at < waiting for device >
What is the problem here?
NurusS said:
Are you sure? it says S-ON, LOCKED and I'm not sure what you mean by the adb folder (where we put the BUZZ-recovery file), but it seems to work where I put it and is stuck forever at < waiting for device >
What is the problem here?
Click to expand...
Click to collapse
Yeah im positive pal. the old hboot never used to say locked. if its sits at waiting for device it means that the device is not connected okay. can you run the command
Code:
adb devices
for me and see if it detects the phone.
Do you have usb debugging enabled?
Did you download the zip file from the forum page?
heavy_metal_man said:
Yeah im positive pal. the old hboot never used to say locked. if its sits at waiting for device it means that the device is not connected okay. can you run the command
Code:
adb devices
for me and see if it detects the phone.
Do you have usb debugging enabled?
Did you download the zip file from the forum page?
Click to expand...
Click to collapse
I ran the command an got this back:
C:\Users\Nurus>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
SH14RPY08821 device
I have USB debugging enabled on my phone.
What zip files are you referring to?
NurusS said:
I ran the command an got this back:
C:\Users\Nurus>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
SH14RPY08821 device
I have USB debugging enabled on my phone.
What zip files are you referring to?
Click to expand...
Click to collapse
Sorry for my delay pal, you seem to have download the correct zip file from the op. Try these commands
Adb reboot bootloader
(The device should reboot into fastboot, highlighted in red at the top, Followed by.)
fastboot oem get_identifier_token
Then highlight the code using right click/mark/ then select it all and right click it again. Post that into the htcdev website.
Sent from my nexus 7 using Tapatalk
heavy_metal_man said:
Sorry for my delay pal, you seem to have download the correct zip file from the op. Try these commands
Adb reboot bootloader
(The device should reboot into fastboot, highlighted in red at the top, Followed by.)
fastboot oem get_identifier_token
Then highlight the code using right click/mark/ then select it all and right click it again. Post that into the htcdev website.
Sent from my nexus 7 using Tapatalk
Click to expand...
Click to collapse
I did what you said, I got <waiting for device> again.
NurusS said:
I did what you said, I got again.
Click to expand...
Click to collapse
When the command prompt states waiting for the device,and you have booted into hboot using the command fastboot reboot boot loader, does the phone say fastboot in red at the top, with options like fastboot reboot and other options in red? Or is it the standard black/blue writing? If its not all red then with the fastboot option highlighted press power once. I will upload pictures of what o mean as soon as I get to my laptop.
heavy_metal_man said:
When the command prompt states waiting for the device,and you have booted into hboot using the command fastboot reboot boot loader, does the phone say fastboot in red at the top, with options like fastboot reboot and other options in red? Or is it the standard black/blue writing? If its not all red then with the fastboot option highlighted press power once. I will upload pictures of what o mean as soon as I get to my laptop.
Click to expand...
Click to collapse
Fastboot is highlighted in red.
NurusS said:
Fastboot is highlighted in red.
Click to expand...
Click to collapse
Sorry for my very delayed response pal, life got in the way.
ok so your hboot looks like this?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
yeah like this except yours will say locked and not unlocked at this stage.
So from here open your command prompt from within the adb folder
Then enter this command, copy and pastif prefered.
Code:
fastboot oem get_identifier_token
this should return a large code in the command prompt.
You will then need to Rght click, mark, and then highlight all the code like the htcdev website states.
post that info into the website and they will email you your unlock token.bin
post back on how you get on.
heavy_metal_man said:
Sorry for my very delayed response pal, life got in the way.
ok so your hboot looks like this?
yeah like this except yours will say locked and not unlocked at this stage.
So from here open your command prompt from within the adb folder
Then enter this command, copy and pastif prefered.
Code:
fastboot oem get_identifier_token
this should return a large code in the command prompt.
You will then need to Rght click, mark, and then highlight all the code like the htcdev website states.
post that info into the website and they will email you your unlock token.bin
post back on how you get on.
Click to expand...
Click to collapse
Once again, I just get <waiting for device>
NurusS said:
Once again, I just get <waiting for device>
Click to expand...
Click to collapse
Okay, then your issue is with your fastboot driver. Do you have another computer you can use?
Just install android SDK and jdk and then try to install your drivers as heavy metal man said. I hope this could work..or try to use this
http://forum.xda-developers.com/showthread.php?t=2317790
Sent from my Moto G using XDA Free mobile app
Hi,
I got a little bit of a problem on my head.... I planned to flash CM12.1 on my HOX but i flashed a different boot.img by mistake! Now i cant get the phone into debugging mode and while using hasoonss toolkit it wont see my device cause i cant get it into debugging mode . Any ideas on how to solve the problem? There are a lot of threads inhere about bricked hox but i cant find one talking about the same problem....
Hope i can get some help on this.
Ow and a bit more info, i can get into bootloader and recovery.
go_insane1981 said:
Ow and a bit more info, i can get into bootloader and recovery.
Click to expand...
Click to collapse
if you can get into bootloader then just get the good boot.img and flash it using fastboot flash boot boot.img
Tried that but it won't see my device.
It doesn't apear in my devices.
go_insane1981 said:
It doesn't apear in my devices.
Click to expand...
Click to collapse
When on bootloader/fastboot mode, type
fastboot devices
to check connection
if it returns your device serial no, then it is good for you to
fastboot flash boot boot.img
adb devices is working when in recovery or on running OS, not on bootloader/fastboot
ckpv5 said:
When on bootloader/fastboot mode, type
fastboot devices
to check connection
if it returns your device serial no, then it is good for you to
fastboot flash boot boot.img
adb devices is working when in recovery or on running OS, not on bootloader/fastboot
Click to expand...
Click to collapse
Tried both ways again but no reaction wth a list of devices. It's blank...
install htc drivers http://www.mediafire.com/?eqrqb44r3ot18g1
SÜPERUSER said:
install htc drivers http://www.mediafire.com/?eqrqb44r3ot18g1
Click to expand...
Click to collapse
Any options on how to install the drivers different from normally? Apparently the drivers won't install as it should install...
Have HTC sync on my system, can i use some of those exe's in there?
This is wat happens with HTC installer.
go_insane1981 said:
This is wat happens with HTC installer.
Click to expand...
Click to collapse
You have a newer sets of drivers installed and the installer exits instead of downgrade the version.
Are you sure you are in fastboot mode?
To enter this.
Power off your phone.
Hold Power and volume down button until phone enters a white screen with Hboot written on it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now press power button again. The screen should now change to this
Showing fastboot marked in red.
Go to device manager and look for the driver. It should look like this ( Android USB Devices, My HTC)
In cmd type fastboot devices.
My cmd returns this.
Cant seem to get the drivers in my device manager, they are installed but not showing in my device manager...
SÜPERUSER said:
You have a newer sets of drivers installed and the installer exits instead of downgrade the version.
Are you sure you are in fastboot mode?
To enter this.
Power off your phone.
Hold Power and volume down button until phone enters a white screen with Hboot written on it.
Now press power button again. The screen should now change to this
Showing fastboot marked in red.
Go to device manager and look for the driver. It should look like this ( Android USB Devices, My HTC)
In cmd type fastboot devices.
My cmd returns this.
Click to expand...
Click to collapse
Ok i used a old htc and now it sees my device again.
Device manager sees the HOX now too.
go_insane1981 said:
Device manager sees the HOX now too.
Click to expand...
Click to collapse
It was my thought at first. So now we know that htc apparently dropped the support for one x and older devices in their driver pack. Good to know
Now i need to take a look at how i can push a diff rom in there since the other rom apparently wont work..
go_insane1981 said:
Now i need to take a look at how i can push a diff rom in there since the other rom apparently wont work..
Click to expand...
Click to collapse
What rom are you trying to install?
SÜPERUSER said:
What rom are you trying to install?
Click to expand...
Click to collapse
http://forum.xda-developers.com/htc-one-x/development/rom-cyanogenmod-12-1-t3396521
go_insane1981 said:
http://forum.xda-developers.com/htc-one-x/development/rom-cyanogenmod-12-1-t3396521
Click to expand...
Click to collapse
Have you flashed this "new storage layout"?
http://forum.xda-developers.com/htc-one-x/orig-development/storage-layout-hox-endeavoru-t3022358
SÜPERUSER said:
Have you flashed this "new storage layout"?
http://forum.xda-developers.com/htc-one-x/orig-development/storage-layout-hox-endeavoru-t3022358
Click to expand...
Click to collapse
Making a new layout is something i missed, Mone said ;
Flashing instruction like usual: perform a full wipe with TWRP for new layout, flash the ROM, flash the suggested GApps, reboot into fastboot mode, flash the boot.img exctracted from the ROM.zip, reboot into system, enjoy cm-12.1.
So i wiped the damn thing( ) after making a backup offcourse(which btw doesn't help cuz its screwed...). But i completely missed that i had to make a new layout... But stil i am convinced it can be "unbricked" one way or another.
I basicly follwed all the steps mentioned in this thread; http://forum.xda-developers.com/showthread.php?t=2069904 and it al worked up to the point i flashed the wrong kernel. After that i searched the forum for hours and found some things which could be connected but with a total different view of what my problem is/was(partially solved with your help) and ended up with putting a SOS sign up for help.
/Users/sekhon/Desktop/Brick Phone.jpg
Hi,
My HTC M8 (which i have not used for a year) seems to have been cricked to what ever extent !
I put it on charge and the following shows up
________________________________________
*** Software status: Modified ***
*** Locked ***
M8_UL PVT Ship S-ON
(few other lines)
FastBOOT AC
<vol up. to previous item>
<vol down> to next item>
<power> to select item
HBOOT
RAMDUMP
REBOOT
REBOOT FASTBOOT
POWER DOWN
no matter what i do it just ends up here and doesn't really startup,
I had aSD Card in the phone and removed it and tried to restart but no luck!
Any help would be highly appreciated !
saint4mbuddapest said:
no matter what i do it just ends up here and doesn't really startup,
Click to expand...
Click to collapse
So what did you try to do? The above doesn't tell us anything you tried or didn't try (aside from removing the SD card).
Don't want to waste the time and effort, to advise you to do things you may have already tried.
Hello,
Thanks for the reply!
I tried to connect it to my mac via usb to flash a rom or twrp etc but my computer doesn't show the phone.
I tried selecting the recovery mode from the menus and nothing happens.
It just restarts and goes back to the same mode.
So honestly i havnt tried much as i do not know where to begin.. Apart from going into all of the menus on the screen and that's it.
I think i the phone is missing the recovery and the rom? Not sure.... Help!
saint4mbuddapest said:
I tried to connect it to my mac via usb to flash a rom or twrp etc but my computer doesn't show the phone.
Click to expand...
Click to collapse
The mac will only be able to connect via fastboot, in the current condition. Do you have fastboot/adb setup on your mac? I'm not a mac user, so I won't be able to advise much on that.
saint4mbuddapest said:
I think i the phone is missing the recovery and the rom? Not sure.... Help!
Click to expand...
Click to collapse
Since the phone will only boot to bootloader, you are correct in that it appears the ROM is damaged or corrupt. Since I don't think the Rogers version has RUU to recover, you are right in the approach of flashing TWRP and ROM to the phone.
However, you will also need to unlock the bootloader, in order to flash TWRP. And you will need working fastboot connection to mac/PC in order to unlock bootloader and flash TWRP. So you really need to troubleshoot the connection issue, first.
You might also read through the following thread for more recovery options or info: https://forum.xda-developers.com/showthread.php?t=2694297
redpoint73 said:
Since I don't think the Rogers version has RUU to recover
Click to expand...
Click to collapse
On post #1 OP wrote (few other lines) which is important to be highlighted. Without OS info no way to help.
Or as usual need fastboot getvar all result. If it is Lollipop RUU 4.20.631.3 is available for free.
Also I remember Marshmallow RUU is available too on AFH but can't confirm it now as I maybe wrong ..need to search for it
Edit : here is Marshmallow RUU - http://gsm-firmware.com/index.php?a=browse&b=file-info&id=14070
Leave it to you to guide OP.
Maybe need to flash 6.13.631.7 firmware first before RUU
Thanks!
I just tried the add fast boot connection went through all the steps ok, HOWEVER when i type in ./adb devices it does not show the phone. So far all posts and videos i have found explain about trouble shooting when the phone OS is still running but none for my situation.
There is a red highlights text which says "FASTBOOT"
and it turns to "FASTBOOT USB" when i plug in with my MAC
Also i have tried 2 different USB cables same result, tried clicking on the "REBOOT FASTBOOT" as well same result.
Anything else i can do to have a working connection ?
redpoint73 said:
The mac will only be able to connect via fastboot, in the current condition. Do you have fastboot/adb setup on your mac? I'm not a mac user, so I won't be able to advise much on that.
Since the phone will only boot to bootloader, you are correct in that it appears the ROM is damaged or corrupt. Since I don't think the Rogers version has RUU to recover, you are right in the approach of flashing TWRP and ROM to the phone.
However, you will also need to unlock the bootloader, in order to flash TWRP. And you will need working fastboot connection to mac/PC in order to unlock bootloader and flash TWRP. So you really need to troubleshoot the connection issue, first.
You might also read through the following thread for more recovery options or info: https://forum.xda-developers.com/showthread.php?t=2694297
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[/IMG]
http://i65.tinypic.com/254x8g0.jpg
<img src="http://i65.tinypic.com/254x8g0.jpg" border="0" alt="Image and video hosting by TinyPic">
saint4mbuddapest said:
Thanks!
I just tried the add fast boot connection went through all the steps ok, HOWEVER when i type in ./adb devices it does not show the phone. So far all posts and videos i have found explain about trouble shooting when the phone OS is still running but none for my situation.
There is a red highlights text which says "FASTBOOT"
and it turns to "FASTBOOT USB" when i plug in with my MAC
Also i have tried 2 different USB cables same result, tried clicking on the "REBOOT FASTBOOT" as well same result.
Anything else i can do to have a working connection ?
Click to expand...
Click to collapse
Have you installed the HTC drivers to your computer?
If not, install HTC Sync Manager (you can get the MAC version here). During the installation of Sync Manager the drivers will be installed. After they are, Uninstall Sync Manager (it doesn't play nice with ADB/fastboot) and the drivers will remain
xunholyx said:
Have you installed the HTC drivers to your computer?
If not, install HTC Sync Manager (you can get the MAC version here). During the installation of Sync Manager the drivers will be installed. After they are, Uninstall Sync Manager (it doesn't play nice with ADB/fastboot) and the drivers will remain
Click to expand...
Click to collapse
Just tried that as well, no improvement
saint4mbuddapest said:
I just tried the add fast boot connection went through all the steps ok, HOWEVER when i type in ./adb devices it does not show the phone.
Anything else i can do to have a working connection ?
Click to expand...
Click to collapse
When on fastboot, correct command is fastboot devices or ./fastboot devices
Based on your bootloader screenshot, you can try the above linked RUU to fix your phone
saint4mbuddapest said:
I just tried the add fast boot connection went through all the steps ok, HOWEVER when i type in ./adb devices it does not show the phone. So far all posts and videos i have found explain about trouble shooting when the phone OS is still running but none for my situation.
There is a red highlights text which says "FASTBOOT"
and it turns to "FASTBOOT USB" when i plug in with my MAC
Click to expand...
Click to collapse
This is working normally, and as intended.
adb and fastboot are related, but different conditions, usage and requirements.
adb: Only works in OS, or alternately TWRP. Needs debugging enabled in phone settings. Will not work in fastboot mode.
fastboot: Only works in fastboot mode. Does not require debugging enabled in phone settings.
Stuck in fastboot mode, you should get a response (phone's ID) to: fastboot devices
Otherwise, there may be a driver or USB connectivity issue.
However, since ckpv5 linked an RUU for you to use, the mac won't help you. RUU is probably the easiest way to get the phone back up and running. But you'll need access to a PC for the RUU to work. RUU won't work properly with mac, even emulating a PC.
redpoint73 said:
However, since ckpv5 linked an RUU for you to use, the mac won't help you. RUU is probably the easiest way to get the phone back up and running. But you'll need access to a PC for the RUU to work. RUU won't work properly with mac, even emulating a PC.
Click to expand...
Click to collapse
It's zip format, can use microsd method
ckpv5 said:
It's zip format, can use microsd method
Click to expand...
Click to collapse
Nice. :good: Obviously, I missed that detail. Should have figures, since most M8 versions without "official" released RUUs seem to get them leaked as zip format.