[Q] How to fix USB block - S-OFF Problem Resolved - Desire Q&A, Help & Troubleshooting

Hi I have a gsm desire which is usb bricked. I have tried to use the procedure described here:
http://forum.xda-developers.com/showthread.php?t=691639&highlight=usb+brick
but it doesnt provide a solution. I get a message from windows 7 stating usb device not recognised. The desire is rooted, s-off, and has modaco non sense kitchen rom on it.
fastboot oem boot data is as attached.

It seems from above log.. your CID is O2__001 .. try to edit the mtd0.img file attached there and push that to your device

Use another card reader to copy the new mtd0.img with your CID at the root of the sd card. Then plug it to your desire, boot, and launch terminal emulator. Enter this :
Code:
su
cp /sdcard/mtd0.img /data/mtd0.img
reboot

Hi,
I have alreeady tried this, as per the procedure, and it doesnt work for me.

kev94 said:
Use another card reader to copy the new mtd0.img with your CID at the root of the sd card. Then plug it to your desire, boot, and launch terminal emulator. Enter this :
Code:
su
cp /sdcard/mtd0.img /data/mtd0.img
reboot
Click to expand...
Click to collapse
Hi I tried this but nothing changes.

if you are S-OFF
simply go into fastboot mode and do:
fastboot oem enableqxdm 0
fastboot oem eraseconfig
and that is is, of course you must have ADB set up on your PC

USB BRICK RESOLVED - Thanks DZUMAGOS
Hi,
This has WORKED!! Thank you. I cant tell you how many hours I have spent trying to fix this. I want to be a little wary because I tried the USB fix detailed in the original thread and it seemed to work temporarily, but this has been working for a couple of hours now and I have tried rebooting the desire, laptop, using usb in recovery, all scenarios, and it seems to have fixed the problem. Thank you. My wife and kids will be happy to see me again!!
One plus point is that I have learnt much in trying to solve this problem, but I wish I had found this solution quicker.
I hope you dont mind but I have a couple of extra questions. I am keen to learn and you never know I may know enough to help someone else on the forum one day.
Can I ask how it works? I understand the first fastboot line, but what does the fastboot oem eraseconfig bit do?.
Do you know why this problem was caused in the first place?
Will this solution work for all USB Bricked S-OFF desires? If so I think it may be worth mentioning in the main USB Brick thread before others spend hours on it.
Also, where I have been performing the fastboot oem enableqxdm 0 via adb previously to try to fix this I have numerous files that have been written onto the sd card like "qxdm_20110607_125733_1.dm". Is it safe to remove these, or do I need to keep them on the sdcard?
Thank you so much again. The will to live has returned, and I can now find other ways of messing my desire up.

you can delete the files from SD, these are just some log files (qxdm logs)
how this works ? well i THINK that this formats the misc partition with mtd0 which makes it re-do itself with default settings (however this is just me guessing, i can be faaar away from truth right now)
also this method is not mention in the USB-Brick 1st post, it is somwhere later on mentioned a few times.
this should work for all S-OFF USB-Bricked desires
why does it happen?
something to do with recovery obviously, they didnt figure that out exactly, it just happens randomly, you can have it after flashing 10 roms or 10.000... or never. i got it after switichng to AmonRa 2.0.1 and restoring a GB nandroid. fixed it and everything is OK ever since.
also i dont mind you hitting 'thanks' button
i dont know if it is possible to do S-OFF while usb-bricked (for S-ON users), this was sometimes adviced to the S-ON users who experienced usb-brick. however i dont know if it was possible to do S-OFF.
anyway this is another good reason to S-OFF, it makes usb-brick totally fixable whereas the other method with mtd0 etc doesnt often work and is seriously more complicated

Hi,
thank you very much for this info. I understand a little better. Hit the thanks button, so thanks should be official now..
I'll try to re-title my original thread to add S-OFF. It may help others to find your answer quicker.

dzumagos said:
if you are S-OFF
simply go into fastboot mode and do:
fastboot oem enableqxdm 0
fastboot oem eraseconfig
and that is is, of course you must have ADB set up on your PC
Click to expand...
Click to collapse
Thanks a million !!! I thought my phone will never be useful , but this post saved my phone.

Related

[Guide] How to recover your semi-brick

YES YOU NEED TO READ THIS WHOLE POST, PROB MORE THEN ONCE TO MAKE SURE YOU GOT IT. YES I KNOW HOW LONG IT IS, I TYPED IT!
*Also note that not all sections will apply to you. I have tried to seperate different senerios using * at each one. Also more then one section here may be needed by you.
the reason i call it a semi-brick is because a true brick can bot be recovered with out opening the case.
first go here and read this for info: http://forum.xda-developers.com/showthread.php?t=838484
now since your here im going to assume that its too late.
*things you will need.
copy of cwm recovery. get it here (the manual install link): http://forum.xda-developers.com/showpost.php?p=9145724&postcount=28
adb installed and working.
a known good rom, or nandroid backup. here is one: http://forum.xda-developers.com/showthread.php?t=836042 (use odex one)
a wpthis.ko for YOUR specfic kernel (run (adb shell cat /proc/version) that will tell you what kernel you have)
*first thing we need to know is, are you s-off or s-on now?
if your s-off just boot into clockwork mod recovery, wipe the phone and flash a known good rom and be done with it. if you dont have cwm recovery installed. boot into fastboot (vol down+power) you must have the sdk/adb installed and working, and type fastboot flash recovery LocationOfRecovery.img (where LocationOfRecovery.img= where you have the recovery, ie c:\android\recovery.img). once thats installed follow instructions above.
*if you are s-on:
will the phone boot into android? if so your not bad off.
if you want to unroot to return the phone, follow the unroot thread here: http://forum.xda-developers.com/showthread.php?t=835971
if you dont want to unroot then you have a couple of different options. if you have cwm recovery still installed, just follow instructions above and flash a known good rom. ive been told that boot.img (kernel) wont flash if you are s-on. the way to fix this (temporarily) is boot into recovery, but before you flash run these commands:
(put wpthis.ko in sdk folder)
adb remount
adb push wpthis.ko /data/local/wpthis.ko (specific for your kernel)
adb shell
# insmod /data/local/wpthis.ko (should get same function not implemented error as when u rooted first time)
then proceed to flash the rom. once booted into android skip down to, "now to get back to s-off"
*if you have stock or eng-recovery installed.
will the phone attempt to boot android at all? where is it stuck at?
a good min after it starts to try to boot, type these commands:
adb remount
adb shell
if you can get in shell then theres still hope. back out shell for a second and start here:
put the cwm recovery.img and wpthis.ko in your sdk folder
adb remount
adb push wpthis.ko /data/local/wpthis.ko (specific for your kernel)
adb push recovery.img /data/local/recovery.img
adb shell
# insmod /data/local/wpthis.ko (should get same function not implemented error as when u rooted first time)
# dd if=/data/local/recovery.img of=/dev/block/mmcblk0p21 (now wait a min or 2 to give it time to finish)
#sync (give it another min or to just to be safe)
#reboot recovery
at this point you should be in cwm recovery. follow instructions above for flashing with s-on.
*if you cannot get into shell while booting, but have eng-recovery installed, there might be some options.(however this is all theory)
boot into recovery-
if you are on linux using adb, you can try taking sh from /system/bin folder of any custom rom, chmod 0755 it, then push it to /system/bin and adb shell might work.
windows-
boot into recovery.
a system.img compatible with your installed kernel pushed may work. put the system.img into the sdk folder.
adb push system.img /data/block/mmcblk0p25
then reboot and see where you are. if that dont work, grab the modified miscnew.img here: http://www.4shared.com/file/pUPfrGi-/mmcblk0p17.html
rename it misc.img put it in sdk folder and
adb push misc.img /dev/block/mmcblk0p17
then reboot into bootloader with PC10IMG.zip on root of sdcard and it should run though. if it does your fully stock and get to start all over again.
*if you cannot get into shell, and you have stock recovery, s-on, and post OTA, im sorry your pretty screwed. as of right now the only thing thats gonna bring it back is a full img/update signed from htc thats equal to or higher then the version currently on the phone. (well and jtag of course)
*well now you've done one of the steps above. your booted into android, you have perm root, and cwm recovery installed, just still s-on. dont worry your almost there!
first take that wpthis.ko for you kernel and push it, and the eng hboot.
adb push wpthis.ko /data/local/
adb push hboot-eng.img /data/local
then from adb shell, or terminal root prompt:
# insmod /data/local/wpthis.ko (again you should get the function not implemented error)
NOW REMEMBER THIS NEXT STEP COULD MEAN DEATH FOR YOU G2 IF TYPED WRONG, AND AFTER ALL THIS HARD WORK!
# dd if=/data/local/hboot-eng.img of=/dev/block/mmcblk0p18
wait a few mins to be sure its done.
# sync
wait a few more just cause.
reboot, you should now be s-off, cwm recovery installed, and free to do whatever you want. just dont go screwing it up again
* as new methods are discovered, or ones here are proven wrong, i will update as necessary. as of the writing post, 2 devices that i know of have been saved!
good luck!
wpthis.ko for bacon bits.03 kernel: http://www.4shared.com/file/OAcd1bix/wpthis-263221-cyanogenmod.html
before you post with problems make sure you have read this at least 2 times. have this info in you post:
what was the last running rom/kernel combo you had?
list EVERYTHING you have done since that point
which recovery is installed?
what happens in recovery when you type
adb devices?
adb remount?
adb shell?
does it try to boot? is it stuck on splash screen, or does it make it to boot animation? 1 min after you turn it on, what happens when you type:
adb devices?
adb remount?
adb shell?
Thank you, really, for taking the time to write this guide. I shared that dreadful feeling of a brick a little while ago, but made it out alive. I know this will help a lot of people.
I'm not bricked, semi bricked or none of that. Rootrd and running BB 0.3
This is the best guide to everything you would need. Too bad you can't post this at the beginning of every thread or some kind of link on every page. This would answer a lot of question if some people would look hard enough. I'm not some smart phone guy by no means. I just read a lot before I ask. In my further reading I can direct people.with further problems here.
Thanks for all your work and giving me another fun hobby
Peace
Sent from my T-Mobile G2 using XDA App
Question why is it that you have "dd if....../mmcblk0p21" in one area and towards the bottom you have "May brick phone ...dd if...../mmcblk0p18." Thought it should always be .../mmcblk0p18?
Phone: T-Mobile G2/Vision Rooted
Rom: Latest Cyanogen
Recovery: CWM waiting for Amon_RA
Good point . Not sure on that one
Sent from my T-Mobile G2 using XDA App
renn9420 said:
Question why is it that you have "dd if....../mmcblk0p21" in one area and towards the bottom you have "May brick phone ...dd if...../mmcblk0p18." Thought it should always be .../mmcblk0p18?
Phone: T-Mobile G2/Vision Rooted
Rom: Latest Cyanogen
Recovery: CWM waiting for Amon_RA
Click to expand...
Click to collapse
if you look where im saying /mmcblk0p21 we are replacing RECOVERY with CWM. i do that because i just dont like the idea of trying to replace hboot from a looping system. worst case something goes wrong, you still have hboot and you can try again. screw up hboot, game over! then once android is back up and running we worry about hboot on mmcblk0p18.
you should not state that steps can be changed if people are brave, someone is going to sip parts and cry that their hboot is boned and now they have a BRICK, this is the best post i have seen in the G2 section thus far and i have been through almost every thread(with any kind of importance) in the dev section and 90% of them in general and Q&A. thank you for this post and let's hope people READ at least 5 times before even starting on this.
Gotcha
Phone: T-Mobile G2/Vision Rooted
Rom: Latest Cyanogen
Recovery: CWM waiting for Amon_RA
Amazing guide, thanks a lot.
fastludeh22 said:
the reason i call it a semi-brick is because a true brick can bot be recovered with out opening the case.
Click to expand...
Click to collapse
I have a full, honest-to-god brick in my drawer (executed dd if=/sdcard/hbooteng.img of=/dev/block/mmcblk0p18 with a wrong "hbooteng.img file).
I'm really, really interested in some guide or info about how to try and recover the brick. I don't mind if I have to open the case, there's not going down from where I am right now.
By the way, my second DZ just arrived, tomorrow I'll try to S-OFF it again... I will have nightmares tonight.
reycat said:
Amazing guide, thanks a lot.
I have a full, honest-to-god brick in my drawer (executed dd if=/sdcard/hbooteng.img of=/dev/block/mmcblk0p18 with a wrong "hbooteng.img file).
I'm really, really interested in some guide or info about how to try and recover the brick. I don't mind if I have to open the case, there's not going down from where I am right now.
By the way, my second DZ just arrived, tomorrow I'll try to S-OFF it again... I will have nightmares tonight.
Click to expand...
Click to collapse
Well it will take a jtag and a lot of research, since it hasn't been done to a g2 yet. Search g1 development forum dor debricking if u want an idea of what's involved.
I remember talking to gtrab a little about your problem. So did you use the wrong file, or did you type an address wrong? What file or typo was it exactly?
What happens when u try to boot into fastboot, or anything else?
{golf clap} on the post.
you sir, have incredible patience... and it's truly appreciated.
fastludeh22 said:
Well it will take a jtag and a lot of research, since it hasn't been done to a g2 yet. Search g1 development forum dor debricking if u want an idea of what's involved.
Click to expand...
Click to collapse
Mmm... It seems all of it is quite a bit over my head.
I remember talking to gtrab a little about your problem. So did you use the wrong file, or did you type an address wrong? What file or typo was it exactly?
What happens when u try to boot into fastboot, or anything else?
Click to expand...
Click to collapse
Don't ask me how I did it, but I actually downloaded a web page instead of the actual hboot file I should have used . I did it from the phone and didn't notice. Since I was supposed to rename it to make the typing easier, I didn't notice it was the wrong file.
Anyway, right now the phone is a complete brick. It doesn't respond to any button presses, the LED doesn't do anything when you plug in the charger... A complete brick.
Device offline?
fastludeh22 said:
before you post with problems make sure you have read this at least 2 times. have this info in you post:
what was the last running rom/kernel combo you had?
list EVERYTHING you have done since that point
which recovery is installed?
what happens in recovery when you type
adb devices?
adb remount?
adb shell?
does it try to boot? is it stuck on splash screen, or does it make it to boot animation? 1 min after you turn it on, what happens when you type:
adb devices?
adb remount?
adb shell?
Click to expand...
Click to collapse
Never used ADB before, followed [forum wont let me post outside links] to set it up. when typing adb devices while in recovery mode, get "list of devices attached
HT09PR204734
offline."
here is a screen shot : [forum wont let me post)
running windows 7 64bit...device not recognized by ADB at alll when stuck on splash screen....did some research couldnt find a real solution...soooo what do you recommend trying?
im stuck on the splash screen.. and i cant get adb to work either.. is missing a driver but i cant for the life of me find one ...
-FuRBz- said:
im stuck on the splash screen.. and i cant get adb to work either.. is missing a driver but i cant for the life of me find one ...
Click to expand...
Click to collapse
Download and instal PDANet, that gave me the drivers i needed for adb, now if only i could figure out how to get my device to register online through the ADB command interface.....
^^ you my friend are awesome! dl pdanet, was able to get the drivers.. was able to go into bootloader and did a recovery from there.. im up and running again!!
marley097 said:
Never used ADB before, followed [forum wont let me post outside links] to set it up. when typing adb devices while in recovery mode, get "list of devices attached
HT09PR204734
offline."
here is a screen shot : [forum wont let me post)
running windows 7 64bit...device not recognized by ADB at alll when stuck on splash screen....did some research couldnt find a real solution...soooo what do you recommend trying?
Click to expand...
Click to collapse
Sounds like you have stock recovery installed, with s-on and no adb/shell access, I'm sorry your pretty screwed. You can try factory reset and see if that helps boot, or to get adb access while trying to boot. Other then that, at the moment the only way to recover is a offical signed pc10img of version equal to or higher then what you have. I'm working hard to come up with something, ill keep you guys informed. I think u said in pm, you have already done the OTA, which makes you version number 1.22.something.
-FuRBz- said:
^^ you my friend are awesome! dl pdanet, was able to get the drivers.. was able to go into bootloader and did a recovery from there.. im up and running again!!
Click to expand...
Click to collapse
Glad you got it! After drivers installed, did you fix it per a section of the op?
it all happened because i had tried flashing cm 6.1- it got stuck on the splash screen but i had done a recovery prior to trying to flash... once i got the drivers installed i was able to get in to adb and do a reboot-bootloader and was able to get into the recovery file
fastludeh22 said:
Sounds like you have stock recovery installed, with s-on and no adb/shell access, I'm sorry your pretty screwed. You can try factory reset and see if that helps boot, or to get adb access while trying to boot. Other then that, at the moment the only way to recover is a offical signed pc10img of version equal to or higher then what you have. I'm working hard to come up with something, ill keep you guys informed. I think u said in pm, you have already done the OTA, which makes you version number 1.22.something.
Click to expand...
Click to collapse
Lame....so how often do they release official pic10img's....? are we talkin a month....or a year?

[Q] HTC Desire Z Rooting Problems

Hello together
First of all i searched to solve my problem already. But after spending several hours by searching and trying I thought i better ask the community.
Well my problem is, that I can't root my phone. I tried diffrent ways and there was always the same result. If I use Visionary+ r14 and press temp root now (usb debugging activatet) it loads for a while and then it hangs on a black screen. Seems to freez always.
If I try it with the terminal emulator and the manual found http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD here, it hangs in the terminal emulator. I don't know the reason but i couldn't find another possibility to root my device.
sorry for my bad english and thank you
Which version of the stock rom are you on? 1.34 or 1.72 or 1.85?? If its 1.72 you need to downgrade your version number to 1.34 in order to root using the Psneuter Method found Here. If its the new 1.85 update, im not sure if that version is rootable or if the psneuter method works on it also.
I've got the 1.72 version of the rom. Well this exactly is my next problem. I tried to downgrade using your method some time before. When i enter the bootloader and it checks the sdcard it just prints CID incorrect.
I know that I have to create a goldcard to make the downgrade possible. To create a goldcard I fallowed also different manuals.
here are two i've tried:
http://android.modaco.com/content/general-discussion/305672/creating-a-goldcard/
http://forum.xda-developers.com/showthread.php?t=572683
there are always the same steps. I tried different manuals and tools. But in the end i got always the same cid which looks something similar to this: 1501004d344732444503ad020c67ade0 then i need the reverse string and the hexeditor and overwrite the first sector of the sdcard. but no matter which method i try, in the end I get always CID incorrect.
anybody already had a similar problem?
nobody had a similar problem?
well solution found... in all the manuals there was written about the "adb shell cat /sys/class/mmc_host/mmc1/mmc1:*/cid" command.
because this method didnt work for me i searched and found the solution to change the command to "adb shell cat /sys/class/mmc_host/mmc0/mmc0:*/cid". With this command i got a CID.
The problem was that I didnt search further in this direction because I had a CID. with the command "adb shell cat /sys/class/mmc_host/mmc2/mmc2:*/cid" everything worked and i got another CID.
im hving th same problem....im on 1.72 rom and get stuck at wrong cid part like u.. ive tried everything...no joy
You tried all the mmc methods?
with mmc1 i got no cid, with mmc0 i got the wrong cid and with mmc2 it worked.
I will try again tomoz ..actually im gona try everything again...and then wait foor my hair to grow back so i can pull it out again
Sent from my HTC Vision using XDA App

Fix USB Brick No Root

Hi Guys, sorry if this has been posted before but i have just spent 14 hours trying to un usb-brick my desire. Each method seemed to need root which i had lost.
Eventually i found these instructions, they are not mine, i only found them so total kudos to the author. to keep it simple (and remember this is for unrooted desires:
Requirements:
Fastboot (part of Android SDK) installed. For instructions on setting up fastboot, search guide on how to install ADB & Android SDK.
HTC Desire USB Unbrick Files .
Android Terminal Emulator app (Install from Android Market)
Procedure:
Reboot your device into its bootloader (fastboot) mode and connect it to your computer via USB.
Launch a Command Prompt window on your computer and enter this command:
fastboot oem enableqxdm 0
On your phone, Go to Menu > Settings > About phone > Software information and note down the Kernel version that you see there. If you see more than just numbers, only note down the numbers e.g. 2.6.32.15.
In the Command Prompt window on your computer, enter this command:
fastboot getvar cid
Note down the CID that you get. It should be something similar to ‘HTC__022’.
Visit this site, enter the CID from step 4 and the kernel version from step 3 as the ROM version, and click ‘OK’. This will generate an mtd0.img file and prompt you to download it. Save it somewhere you will remember.
Now connect your SD card to your computer using a card reader device or another phone, and transfer the extracted HTC Desire USB Unbrick files as well as this mtd0.img to it. Make sure the files are in the root of the SD card and not in any folder.
Insert the SD card back into your phone.
Launch Terminal Emulator on your phone and enter these commands:
cat /sdcard/rageagainstthecage-arm5.bin > /data/data/jackpal.androidterm/rageagainstthecage-arm5.bin
cat /sdcard/flash_image > /data/data/jackpal.androidterm/flash_image
cat /sdcard/mtd0.img > /data/data/jackpal.androidterm/mtd0.img
cd /data/data/jackpal.androidterm/
chmod 755 rageagainstthecage-arm5.bin flash_image
/data/data/jackpal.androidterm/rageagainstthecage-arm5.bin
In case your phone seems to crash or shows erratic behavior, ignore it for now.
Completely quit Terminal Emulator: First press the ‘Home’ button and then go to Menu > Settings > Applications > Manage Applications > All, find ‘Terminal Emulator’ there and tap ‘Force Stop’.
Launch Terminal Emulator again. This time, you should see a # prompt instead of $, indicating you have achieved temporary root access necessary for the next step.
Enter these commands in Terminal Emulator:
cd /data/data/jackpal.androidterm/
./flash_image misc mtd0.img
Finally, reboot your phone and you’re done.
That’s all there is to it – your USB brick issue should now be fixed.
If Mods believe this is easily accessible elsewhere on XDA, please delete the post but it took me 14 hours of trawling the net to get my desire un-bricked
regards
Whilst the info is good it's quite useless without the actual links. I'm sure I've seen similar info within these forums before though. Fortunately I've not managed to brick mine (yet).
Parva4 said:
Whilst the info is good it's quite useless without the actual links. I'm sure I've seen similar info within these forums before though. Fortunately I've not managed to brick mine (yet).
Click to expand...
Click to collapse
Sorry about that, files now added to first post
Regards
Jamadant
Try to get visionary+ I don't think you can get it from the market but there are other places, this will give you temporary root as I couldn't get root using the rageagainstthecage, then extract the flash image and paste it with the mtd file in data, then carry on with the commands in as above after the root (so dnt enter commands for rageagainstthecage as that is a process for getting root)
If you need more details let me know as I know how it feels to almost have a very expensive paperweight
Sent from my HTC Desire using XDA Premium App
thanks for you to share this method
USB Brick HELP!
Hi, last night I got my htc desire bricked. Pc can't detect my phone and sd card.
As a requirement on your posted guide, i need to install ADB and Android SDK. But when I plugged my phone into my pc to install software drivers its showing "Qualcomm CDMA Technologies MSM Driver not found". Where can I get this drivers?
I tried also to enable SD card by "fastboot oem enableqxdm 0' in command prompt but "'fastboot' is not recognized as an internal or external command"
My phone details for reference:
Android 2.2
Hboot 0.93
Software 2.14.207.1
PVT3 Ship S-On
RAdio 5.09.05.30_2
Unrooted, O2 branded
How can I continue to unbrick my phone with these initial problems?? Can you suggest newer guide for my case?
PLEASE HELP!
USB Brick help...
after i force stop the terminal emulator when i try to lounch it again doesn't run.
i get a white screen and nothing more
have you guys any ideea why is this happening?
rugarai_3x said:
Hi, last night I got my htc desire bricked. Pc can't detect my phone and sd card.
As a requirement on your posted guide, i need to install ADB and Android SDK. But when I plugged my phone into my pc to install software drivers its showing "Qualcomm CDMA Technologies MSM Driver not found". Where can I get this drivers?
I tried also to enable SD card by "fastboot oem enableqxdm 0' in command prompt but "'fastboot' is not recognized as an internal or external command"
How can I continue to unbrick my phone with these initial problems?? Can you suggest newer guide for my case?
PLEASE HELP!
Click to expand...
Click to collapse
Follow my instructions here for fastboot :- http://forum.xda-developers.com/showthread.php?t=1176663
HBoot 1.02 S-On No Root
Hi!
I USB-Bricked my Desire PVT4. Now it is with HBoot 1.02 and official unrooted Gingerbread.
I tried common methods, but I cant get access to write misc partition.
I got my SD card working with fastboot oem enableqxdm 0. I made a valid mtd0 Image etc... but after copy the flash_image, rageagainstthecage and mtd0 the terminal emulator wont run after stopping the task.
Cant downgrade HBoot without root. Alpharev (revolutionary4-4) needs USB running in ROM.
Please !!!! I need help!!!!!
Thanx guys
Search for guide for usb brick.
TouchPaled from Oxygen with Transparent XDA App
MatDrOiD said:
Search for guide for usb brick.
TouchPaled from Oxygen with Transparent XDA App
Click to expand...
Click to collapse
I did (with help of Leinad):
http://forum.xda-developers.com/showthread.php?t=955845
Cant pass step 5! Relaunching the Terminal Emulator fails! Doesnt open anymore. I read, that writing Misc partition in HBoot 1.02 is not possible using this method.
Need working method for HBoot 1.02 with official gingerbread 2.3.3 in order to USB-unbrick my Desire!
Any ideas?
dexterm1 said:
I did (with help of Leinad):
http://forum.xda-developers.com/showthread.php?t=955845
Relaunching the Terminal Emulator fails!
Click to expand...
Click to collapse
Try to re-do all the steps..if it fails to open, before u can flash the misc partition, maybe u did something wrong..at least it should open and u should be able to run the commands to flash the misc

[Q] Problem downgrading my Desire Z

Guys,I got a problem when I was downgrading my Desire Z using this guide(http://forum.xda-developers.com/showthread.php?t=1178912). Since I'm a new member,I cannot post in that post.
The problem is:
When I enter this code:
# ./flashgc
I got this code:
./flashgc
./flashgc: permission denied
So,can anyone PLEASE help me?I will be very thankful!
there could be a whole bunch of reasons why thats happening. You didn't push it properly, you aren't in the right dir, you didn't chmod it, etc.
So it would be helpful if you pasted everything in your cmd/terminal
-Nipqer
waiting for device
Hello XDA,
i post my question in here, because it refers to the same guide. Everything worked fine, untill the last step of the fastboot part. After entering "> fastboot-mac flash zip StockRom.zip" the terminal says "waiting for device" for an hour now, and the phone still shows the grey htc logo.
I use mac osx, and my phone was up to date.
What went wrong? Most important, how do i interrupt this process, without damaging the device?
thank you
next morning
UPDATE:
I left everything as it was. This morning nothing happend in Terminal, phone was turned off. After starting it, still android 2.3.3, no changes as far as i see.
Still: What went wrong, and if i try again, how can i interrupt "waiting for device" if i try again, and don't have time to wait for hours.
UPDATE II:
Tried "Manual Downgrade"-Method. I am froyo now. Thanks for letting me post this little monologue
No idea what went wrong, could be a permission issue. Try running fastboot as root?
As for interrupting it, so long as its just on 'waiting for device' its not actually doing much, so you can hit ctrl + c in terminal to halt it.
-Nipqer
not sure but when i type <fastboot - windows .....> or whatever that wont work for me. anything i have ever done in fastboot has started like <fastboot -w> or <fastboot flash> never <fastboot-windows oem flash or whatever>
maybe next time (if there is) drop the "-mac" ?
just a thought
Setherio made a guide which used fastboot, but made it universal so renamed the fastboot binaries according to which OS they are made for.
The fact he has 'fastboot-mac' instead of just 'fastboot' makes no difference at all.
-Nipqer

[GUIDE] Comprehensive S-OFF/Root Methods

Please do not PM me with questions about this guide! I don't have time to help everyone through it, create a thread in Q&A if you don't have 10 posts or post here, there are other people who have done this and can help you, and I will get to it if I can. PMs asking questions about this guide will be ignored. Thank you.
Fully stable root methods for all firmware versions (no bootloops on 6.01.605.05 firmware!)
Table of Contents
To quickly find a section, hit CTRL+F and type the letters in parentheses, then click "Next"
(IRO) Intro: Read first!
(HDV) HTCDEV Unlock
(TCR) Tacoroot
(DWG) Downgrade tool
(RVL) Revolutionary
(HSO) S-OFF with HTCDev unlock (second post)
(ASO) After S-OFF (second post)​
INTRO(IRO)​DISCLAIMER: I am not responsible for anything that happens to your device while following these instructions. I will try to help you through problems as much as I can, but I can't guarantee success, especially if you do not carefully read the instructions.
This is a comprehensive guide of all known and fully stable root/s-off methods, at this time, it covers just about all firmware versions out there. Most of these methods will require the Android SDK, so download that (Google it. A link for this really isn't necessary, and I'm sure many people could use practice googling things. ) and set it up (again, just google "android sdk," the download page even has tutorials). The downgrade methods no longer require the sdk, but it is still reccomended that you download it as it is a very useful tool. Don't forget to download the device drivers here (only neccessary on Windows) and set the PATH variable.
So, which downgrade method should you use? Most likely you will either have firmware version 5.x or 6.x, you can find out under Settings>About phone. If you are using 5.x, go to the Downgrade Tool section; if you have 6.x, go to the Tacoroot section. Both methods eventually lead to the Revolutionary section, HTCDev unlock is not reccomended and, honestly, completely pointless (read more below).
HTCDEV UNLOCK(HDV)​Versions: All
HTCDev is HTC's "official" unlock, it will unlock the bootloader but leave S-ON. Don't do it. Seriously. It's a guaranteed voided warranty and pretty much a huge PITA (you can't flash radios and need to extract and separately flash ROM kernels), and s-off methods are completely stable and even relockable. That said, if for whatever reason you do wish to do this, just go to http://htcdev.com/bootloader/. If you want to obtain S-OFF at any time after using HTCDev unlock, see the second post.
Note: to flash ROMs when HTCDev unlocked, flash the ROM normally, then extract the boot.img from the rom.zip and boot into fastboot, then use the command "fastboot flash boot boot.img."
TACOROOT(TCR)​Versions: 6.01.605.05 firmware
Tacoroot is a temp root method discovered by Justin Case that will allow those on the newer firmware to flash an older version and root with Revolutionary. Before you begin, download this zip containing all the files you'll need:
EDIT: Looking for the files? See this post.
Extract this zip to C:/Android. You can extract it somewhere else, just replace C:/Android with the path to the wherever you extracted it wherever it comes up. Now, connect your device to your computer with a USB cable, turn on USB Debugging under Settings>Apps>Development, and disable fastboot under Settings>Power. Make sure your phone is fully charged. Open a command prompt by opening the start menu, typing "cmd" and hitting enter. Type in everything that is in black text. Notes and extra instructions will be written in blue. It is reccomended that you copy/paste the code to avoid typos, to do this, copy by highlighting the line and hitting Ctrl+C as usual; to paste, go to your command prompt and click the small black icon in the upper left corner. A menu will pop up, go to Edit>Paste. Make sure you have not highlighted any spaces before or after the line or any of the blue text. Now, begin copying the code:
cd C:/Android
md5sums RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Radio_1.09.01.0622_NV_VZW1.92_release_199487_si.zip Remove the space in the middle of the word radio before hitting enter, I don't know why it won't let me remove it. Result should be cea499f51b40055ffd118960e1e73255, if it isn't, redownload the miniadb zip.
md5sums 1.09.01.0312_vivow_Radio_PG32IMG.zip Result should be ea6b98be48210d7797e62362f49ff751
md5sums tacoroot.sh Result should be 6ec06d776feb212d8b2a55817eddf76d
md5sums misc_version Result should be 050f55d34ddbcc860efa5982491437de
adb devices Result should be your phone's serial number. If it isn't make sure drivers are properly installed and USB Debugging is enabled.
adb push tacoroot.sh /data/local/
adb shell chmod 755 /data/local/tacoroot.sh
adb shell /data/local/tacoroot.sh --setup This will reboot your phone. When you get to a screen with a red exclamation mark, press VolUp+Power until you get to a menu, then press VolUp+VolDown+Power until the phone turns off. Once it is rebooted, continue.
adb shell /data/local/tacoroot.sh --root
adb wait-for-device Running the step before this will reboot your phone again, this time it will be bootlooping, meaning it will not boot fully and get stuck on the boot animation. Once your prompt comes back after this step, you're good to continue even though the phone isn't fully booted.
adb push misc_version /data/local/tmp/misc_version
adb shell chmod 777 /data/local/tmp/misc_version
adb shell /data/local/tmp/misc_version -s 2.18.605.3
adb shell /data/local/tacoroot.sh --undo This will reboot your phone one more time, this time fully stable and will boot completely. Continue once fully booted.
adb reboot bootloader This will reboot your phone to a white screen with a few options. Once you are at this screen, continue with the instructions.
fastboot devices Result should be your phone's serial number, again.
fastboot getvar mainver The result should be 2.18.605.3. If it is not, something was not done correctly, you'll need to restart from the beginning.
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Radio_1.09.01.0622_NV_VZW1.92_release_199487_si.zip This will take a bit of time without giving any indication as to when it will be done, be patient and do not interrupt it.
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip 1.09.01.0312_vivow_Radio_PG32IMG.zip Same as the above, do not interrupt under any circumstances (unless you really wanted a phone-shaped paperweight )
fastboot reboot
That's the end of the codes, you should be fully booted into the now downgraded version. Re-enable USB debugging, then continue to the Revolutionary section and follow instructions there.
DOWNGRADE TOOL
Versions: HBOOT .98, firmware below 6.01.605.05
This will not work with firmware version 6.01.605.05! Use the tacoroot method!
This tool will downgrade you to 2.3.3, which will allow you to use Revolutionary to gain S-OFF.
Download the tool here, and extract it to a folder where you can easily get to it in a command prompt/terminal.
Now, connect your device to your computer with a USB cable, and turn on USB Debugging in settings. To ensure you are connected, open a command prompt/terminal and type "adb devices". If you see a bunch of letters and numbers followed by "device," you're good to go.
Navigate to the files you extracted in a command prompt/terminal ("cd /path/to/folder," replacing /path/to/folder with the actual filepath), type "hack-vivow.cmd" and let it run. It may take a while and seem to get stuck on some commands, just leave it alone. After it's done, continue to the Revolutionary section. Yep, it really is that easy.
REVOLUTIONARY
Versions: GB 2.3.3, any others after downgrade methods
This is the final step that will actually get you S-OFF.
Go to the revolutionary website, click on the download link for your OS, you'll get a download right away. While it's downloading, fill out the form that pops up (if you don't know your serial number and have the sdk installed, open up a command prompt/terminal and type "adb devices," the letters/numbers before "device" is your serial. Extract the files and run either revolutionary or revolutionary.exe depending on your OS, enter your beta key and say yes when it asks to install CWM recovery. Let it run, and you'll be S-OFF and ready to go!
If you have any questions/comments or found something that isn't right, go ahead and post, I would greatly appreciate any positive or negative feedback, as long as it's constructive.
Credits:
attn1 for Downgrade tool
Revolutionary team
Guhl for misc_version
jcase for Tacoroot
PalmerCurling for Tacoroot downgrade guide
MIVLives for bootloop fix
scotty85 for better Tacoroot downgrade and HTCDev S-OFF method
If you find anything I didn't give credits for and should have, let me know and I'll add it.
Get S-OFF after using HTCDev Unlock
(HSO)​If you used HTCDev unlock and want to get S-OFF, follow this guide. What you get from going from HTCDev unlocked to full S-OFF is a full unlock instead of HTC's restricted unlock. This way, you can flash custom radios and flash ROMs without needing to extract and separately flash the boot.img. (Note: If you already installed a custom recovery and a custom ROM, flash this ROM and start at "adb push misc_version /data/local/tmp/misc_version" in the code.) To do this, first download this zip and extract it to C:/Android. You can extract it somewhere else, just replace C:/Android with the path to where you extracted it wherever it comes up. Next, download this zip and extract it to C:/Android. Download this zip as well and put it in your C:/Android folder, but do not extract it. Now, connect your device to your computer with a USB cable, turn on USB Debugging under Settings>Apps>Development, and disable fastboot under Settings>Power. Make sure your phone is fully charged. Open a command prompt by opening the start menu, typing "cmd" and hitting enter. Type in everything that is in black text. Notes and extra instructions will be written in blue. It is recommended that you copy/paste the code to avoid typos, to do this, copy by highlighting the line and hitting Ctrl+C as usual; to paste, go to your command prompt and click the small black icon in the upper left corner. A menu will pop up, go to Edit>Paste. Make sure you have not highlighted any spaces before or after the line or any of the blue text. Now, begin copying the code:
cd C:/Android
md5sums RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Ra dio_1.09.01.0622_NV_VZW1.92_release_199487_si.zip Result should be cea499f51b40055ffd118960e1e73255, if it isn't, redownload the miniadb zip.
md5sums 1.09.01.0312_vivow_Radio_PG32IMG.zip Result should be ea6b98be48210d7797e62362f49ff751
md5sums misc_version Result should be 050f55d34ddbcc860efa5982491437de
adb devicesResult should be your phone's serial number.
adb push CWM-SuperSU-v0.94.zip /sdcard This might take a minute or so. If it gives an error, try "adb push CWM-SuperSU-v0.94.zip /mnt/sdcard"
adb reboot bootloader This should reboot your phone to a white menu, once it is there, continue.
fastboot devices This should return your phone's serial number.
fastboot flash recovery recovery.img This might take a while, be patient and do not interrupt it. Once it is done, use the volume buttons on your phone to navigate through the menu until RECOVERY is highlighted, then press Power to select it. Your phone will reboot into another menu, once it shows up, select "install from sdcard" then "choose zip from sdcard," then scroll down and select CWM-SuperSU-v0.94.zip, and accept it. Once it is finished, press power then select reboot. Once you are fully booted, continue with the instructions.
adb push misc_version /data/local/tmp/misc_version
adb shell chmod 777 /data/local/tmp/misc_version
adb shell /data/local/tmp/misc_version -s 2.18.605.3
adb reboot bootloader This will reboot you to the white menu again.
fastboot devices Result should be your phone's serial number.
fastboot getvar mainver Result should be 2.18.605.3. If it isn't, make sure you didn't get any errors in the above code and everything was copied correctly.
fastboot oem lock
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Ra dio_1.09.01.0622_NV_VZW1.92_release_199487_si.zip This will take a while, be patient and do not under any circumstances interrupt it.
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip 1.09.01.0312_vivow_Radio_PG32IMG.zip This will also take a bit, again, do not interrupt it.
fastboot reboot
That's the end of the code, you should be downgraded and can now get S-OFF by following the Revolutionary guide in the first post.
After S-OFF(ASO)​So, now you have S-OFF. Congratulations! The next step would be to flash a custom recovery, then either an su zip or a custom, rooted ROM. For recoveries, the choices are ClockworkMod, 4EXT or TWRP. I personally prefer 4EXT, but TWRP is also great and has many great features. ClockworkMod is a little slower, but still stable. All ROMs and recoveries for the Dinc2 can be found in the development forums (where you found this guide), and there are many different ROMs to choose from, so check them out! If you want something rock solid and completely stable, try out CondemnedSoul's CM7 or one of the Gingerbread Sense ROMs, or if you want something newer, a bit faster, but maybe has a few minor bugs, check out one of the many ICS ROMs. If you want the latest and greatest, with a few slight bugs, go Jelly Bean with aeroevan's CM10. If you were looking to just root, download and flash the zip found here: http://forum.xda-developers.com/showthread.php?t=1538053, however, I would recommend that you try one of the Gingerbread Sense ROMs such as Skyraider Zeus if you wanted something a bit different with extra features, or andybonestock for a faster, debloated ROM that looks and feels exactly like what you're used to, but rooted.
Nice guide. I have to use the tacoroot method for a buddy of mine.
Awesome post!
This should be stickied...
sk842018 said:
This should be stickied...
Click to expand...
Click to collapse
+1 ^^
Sent from my Kang Banged Dinc2
Consider it done, excellent resource :good:
Also added to roll-up.
Bad links for Tacoroot.sh and .0312 radio. Great wright up though and cant wait to get my replacement unlocked.
Edit: Ok so I am almost there but have run into some issues. I cant get the 2.3.3 RUU to flash. It will get so far and stop saying bad signature verification. The one thing I noticed is that at the end of the file name it has si and not signed. I tried to change it but kinda knew that would not work and it didn't. Hope this can be fixed soon.
Edit of the edit. Ok so I followed dets34's wright up as I could not get the commands posted here to work. I put the files in the proper SDK folders and went through the commands and when I got to the RUU I hit tab after starting the name to make sure the end was si.zip. Flashed went into boot loop, boot recovery, flash newest radio, and bam no more loop with S off. Thanks to everyone who keeps us sorted out and flashing strong.
zackspeed said:
Bad links for Tacoroot.sh and .0312 radio. Great wright up though and cant wait to get my replacement unlocked.
Edit: Ok so I am almost there but have run into some issues. I cant get the 2.3.3 RUU to flash. It will get so far and stop saying bad signature verification. The one thing I noticed is that at the end of the file name it has si and not signed. I tried to change it but kinda knew that would not work and it didn't. Hope this can be fixed soon.
Edit of the edit. Ok so I followed dets34's wright up as I could not get the commands posted here to work. I put the files in the proper SDK folders and went through the commands and when I got to the RUU I hit tab after starting the name to make sure the end was si.zip. Flashed went into boot loop, boot recovery, flash newest radio, and bam no more loop with S off. Thanks to everyone who keeps us sorted out and flashing strong.
Click to expand...
Click to collapse
Links work fine for me. What did you do differently with dets34's tutorial?
The only thing that was different was I put misc and taco files in AndroidSDK\platforms. Then I put the RUU in the tools folder. Ran the commands and it went through first try. For the first part I cd c:\ to my platforms folder and ran the first part then cd c:\ to my tools folder and installed the RUU. Once it booted as soon as I messed with it boot loop. So flashed the radio and all seems to be fine.
zackspeed said:
The only thing that was different was I put misc and taco files in AndroidSDK\platforms. Then I put the RUU in the tools folder. Ran the commands and it went through first try. For the first part I cd c:\ to my platforms folder and ran the first part then cd c:\ to my tools folder and installed the RUU. Once it booted as soon as I messed with it boot loop. So flashed the radio and all seems to be fine.
Click to expand...
Click to collapse
Shouldn't make a difference if you added those folders to your PATH variable, that way you can use adb/fastboot commands without having to cd in.
Yea that's kinda what I thought but some how I messed it up or something because it never would flash the RUU. I am no expert at this by any means. Either way you helped out and its nice to see we don't have to worry about loops any more. :good:
Great guide, thanks! My couple of things I had to add in to make everything work:
Code:
fastboot flash zip RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Radio_1.09.01.0622_NV_VZW1.92_release_199487_si.zip
I had to add the path to this file for it to work and then afterward do a
Code:
adb reboot
to get ready for the Revolutionary process. At first Revolutionary wouldn't recognize the device when it booted. I quickly realized I needed to re-enable USB Debug.
Then I used adb to do the rebooting necessary to flash the .0312 radio.
Thanks again! Great stuff.
techspecs said:
Great guide, thanks! My couple of things I had to add in to make everything work:
Code:
fastboot flash zip RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Radio_1.09.01.0622_NV_VZW1.92_release_199487_si.zip
I had to add the path to this file for it to work and then afterward do a
Code:
adb reboot
to get ready for the Revolutionary process. At first Revolutionary wouldn't recognize the device when it booted. I quickly realized I needed to re-enable USB Debug.
Then I used adb to do the rebooting necessary to flash the .0312 radio.
Thanks again! Great stuff.
Click to expand...
Click to collapse
Updated, thanks.
Thanks for your guide. Will this guide work with the newest firmware 5.10.605.9? Just use TACOROOT?
leshan said:
Thanks for your guide. Will this guide work with the newest firmware 5.10.605.9? Just use TACOROOT?
Click to expand...
Click to collapse
Use the downgrade tool.
Sent from my vivow using Tapatalk 2 Beta-5
leshan said:
Thanks for your guide. Will this guide work with the newest firmware 5.10.605.9? Just use TACOROOT?
Click to expand...
Click to collapse
The latest firmware is 6.01.605.05. You don't have to use tacoroot.
Thanks. worked perfectly.
prototype7 said:
Use the downgrade tool.
Sent from my vivow using Tapatalk 2 Beta-5
Click to expand...
Click to collapse
unroot to re-root correctly
Does anyone know a method to go back to stock on one of refurbed phones in order to re root correctly and not get the Sense bootloop? I found a few methods but they are all four hboot .97 and I have a feeling won't fix the problem.
mccarrel said:
Does anyone know a method to go back to stock on one of refurbed phones in order to re root correctly and not get the Sense bootloop? I found a few methods but they are all four hboot .97 and I have a feeling won't fix the problem.
Click to expand...
Click to collapse
Flash the latest firmware, or just flash whatever RUU then the .0312 radio, then follow the guide to go back to s-on.
Sent from my Incredible 2 using Tapatalk 2 Beta-5

Categories

Resources