Related
Guys,
I am lost. I thought I am not stupied, but it seems I am.
Here's the problem:
After flashing a couple of different ROMs somehow I wasn't able to access recovery any more - I always used a batch to load the recovery, I never flashed in permanently. Now I only see the white HTC screen.
So I unrevoked, a new RUU plus rerevoked but both scenarios give the same result: unrevoked it stopping when it should boot in recovery.
Also I used some batch scripts flying around. and the problem should be that it is not possible to write the recovery.
my phone:
BRAVO DVT1 SHIP S-OFF
HBOOT-0.75.0000
MICORP-031d
TOUCH PANEL SYNT0101
Radio 0-4.05.00.11
Any clue how I can restore recovery???
Thanks in advance.
M
Can you get into fastboot? If you can, go to shipped-roms.com and find your original stock RUU. Connect your phone and place it in Fastboot mode (select Fastboot and wait until it says FASTBOOT USB and run the RUU your phone came with originally). You may need to insert a Gold Card into your phone if you are running a generic one).
I;m just thinking... it could also be a USB brick, see this guide here for a possible fix:
http://forum.xda-developers.com/showthread.php?t=691187
If i were you, i would steer away from manually accessing recovery using batch scripts/pushfiles, especially when connected via USB, as this can always potentially brick your phone. As you were saying, use unrEVOked with a permanent custom recovery like Amon-Ra, or use ClockworkMod. This will make it virtually impossible to brick your phone.
Hope you get it fixed soon.
You could also try running unroked from a linux live cd. People have less problem running it true linux.
Thank you guys for trying to help.
I installed the RUU from fastboot and still... no recovery in sight. I looked into USB brick as well, but all solutions require a recovery mode - which I don't have. Also I don't this it is a bricked misch partition. But hell, what I know. I just bricked this *****.
After RUU I ran unrevoked again. all fine until booting the recovery: White screen and HTC logo. But at least I have root ;-)
Is it possible that there is something wrong with the rights? I tried:
r5-desire-root/fastboot-mac boot recovery-clockwork-2.5.0.7-bravo.img
downloading 'boot.img'... OKAY
booting... FAILED (remote: not allowed)
Any clue?
Cheers
M
tameike said:
Thank you guys for trying to help.
I installed the RUU from fastboot and still... no recovery in sight. I looked into USB brick as well, but all solutions require a recovery mode - which I don't have. Also I don't this it is a bricked misch partition. But hell, what I know. I just bricked this *****.
After RUU I ran unrevoked again. all fine until booting the recovery: White screen and HTC logo. But at least I have root ;-)
Is it possible that there is something wrong with the rights? I tried:
r5-desire-root/fastboot-mac boot recovery-clockwork-2.5.0.7-bravo.img
downloading 'boot.img'... OKAY
booting... FAILED (remote: not allowed)
Any clue?
Cheers
M
Click to expand...
Click to collapse
Try placing the 'recovery-clockwork-2.5.0.7-bravo.img' in the tools folder of the android sdk folder, and then drag the tools folder into terminal and type:
./fastboot-mac boot recovery recovery-clockwork-2.5.0.7-bravo.img (to boot the clockwork recovery through fastboot)
or this:
./fastboot-mac flash recovery recovery-clockwork-2.5.0.7-bravo.img (to flash the clockwork recovery through fastboot)
Hope this helps some.
Tried this just now:
./fastboot-mac flash recovery ../recovery-clockwork-2.5.0.7-bravo.img
sending 'recovery' (4216 KB)... OKAY
writing 'recovery'... FAILED (remote: not allowed)
./fastboot-mac boot recovery ../recovery-clockwork-2.5.0.7-bravo.img
cannot load 'recovery'
Does this mean anything to anyone?
Thanks guys...
You are S-on, maybe running alpharev so that you are S-off can help you. But I have no experience with that. If you are S-Off you can use the fastboot commands to push the recovery.
It's possible that the stock RUU you ran earlier may have had an HBOOT update in it forcing s-off to change to s-on, causing the HBOOT to be overwritten.
I s-off'ed not too long ago (i know... i know... it does sound dirty ) and it is a risky procedure as it could end up bricking your phonr entirely if not done correctly. I'm am not certain on what exact procedure to follow on Mac, running Windows 7 here...
If you want to give it a try yourself, you can follow what is suggested in the following guide:
http://forum.xda-developers.com/showthread.php?t=805811
This is what i did to security unlock my phone:
I ensured USB Debugging was enabled.
Downloaded this AlphaRev 1.5 HBOOT reflash utility (.iso file)
Important: Before starting this procedure, it is very important that you do not have your phone sync'd to your PC, as you should only connect the phone to the computer when prompted after the .iso is booted.
I burned the .iso to a bootable CD (you can also boot from a DVD disc or USB key).
Note: You may need to change the boot order in your computer BIOS to either boot from a CD/DVD or external device, like a USB key.
I rebooted my computer and booted from the CD I created, and pressed enter at the flashing cursor - you will know that you have successfully booted the .iso as the screen will display some Tiny Core Linux logos. While I waited, I powered on your phone but I made sure that I had not connected it to my PC via USB. After the initial loading, the screen will prompt you to press any key to continue. After this, I was prompted to connect the phone via USB.
Make sure you wait and only connect your phone via USB when prompted on your Mac. When you are ready, connect the phone via USB (while you are doing this, check the status of your phone as you may be prompted to allow super user permissions to continue). During this process, do not interact with your phone and just let it run it's course. Your phone will automatically reboot a few times during the 3 stages, so do not stop the procedure at any cost.
When it is done, go back into the Bootlader and at the top of the screen, it should show the AlphaRev text and s-off.
Next, you will need to flash the custom clockwork recovery here - http://koush.tandtgaming.com/recoveries/recovery-clockwork-2.5.0.7-bravo.img
Then, simply follow and enter the command I posted above (make sure you place the recovery image in the tools folder of the android sdk folder, and execute the fastboot command via the Terminal) to flash the custom clockwork recovery from fastboot, and it should then hopefully get you back on track.
Let us know how you get on with this. I will keep my fingers crossed for you
Regards,
Mas.
Another case of someone with a factory unlocked bootloader...where are they coming from or have HTC just sent them all out like it!?!?!
EddyOS said:
Another case of someone with a factory unlocked bootloader...where are they coming from or have HTC just sent them all out like it!?!?!
Click to expand...
Click to collapse
I think these s-off supplied devices are supplied specifically for developers as developer phones... i think
Hi.
I have a problem with my DHD, and have been browsing these forums for a solution. Im new to this so i need some confirmation, a url, and some explanation.
This happend:
I tried to root my desire HD with visionary+ r14. I did temproot, got back into the app just fine, checked for "set system r/w after root", and clicked attemt permroot. The phone booted, and got stuck in a bootloop. My Hboot menu sais S-ON on top. Tried reseting factory settings nothing helps. Since i didnt get the phone rooted, no clockword recovery installed...
Phone details:
The phone had the factory 1.32 build on it.
other info that might be valid:
Hboot: 0.85.0007
microp-0438
radio-26.03.02.26_M
eMMC-boot
oct 11. 2010
1. From searching and reading, it seems i need a RUU stock image build 1.32, can anyone provide me with an URL for the correct image?
2. Can i use the bootloader on the phone to do this? ..and how?
Hope u have some time to spare, and help this niblet :=)
Thnx for reading
PS:
Before i did this, the phone was rooted, with the same visionary pluss file. I tried to install clockword recovery mod, but it wouldnt "take". I then factory reset the phone in the android recovery menu, and the rest is listed above.
Download your RUU from here: http://xdafil.es/index.php?path=DesireHD/RUU/
How do i know i have the right drivers on the pc? Do i get those drivers from installing the HTC sync program?
sirreal1988 said:
How do i know i have the right drivers on the pc? Do i get those drivers from installing the HTC sync program?
Click to expand...
Click to collapse
If you install HTC sync (download it from their website or it is also in your sdcard unless you have not removed it ), you get all the necessary drivers...
Hm, i have installed HTC sync, but as my phone is stuck on the blackscreen and red triangle, HTC sync does not detect my phone.
When i try to run the exe file "RUU_Ace_HTC_WWE_1.32.405.6_Radio_12.28b.60.140e_26.03.02.26_M_release_155891_signed", it gives me an error [170], USB connection error.
Is there a way to run this file from the bootloader?
Try to push a PD98IMG.zip (this is stock HTC 1.32 rom from this thread unrooted, hboot s-on) to the sd card, boot into bootloader and flash "new" rom
with adb:
Code:
adb push directory/to/your/PD98IMG.zip /sdcard/
adb reboot bootloader
or if adb doesn't work, put the stock rom into the top of your sdcard, reboot the phone while holding the vol-down button.
follow the instructions on the device(normally it search for the PD98IMG.zip and ask you to install it)
How importanat is the last part of the filename of the RUU file "_2 6.03.02.26_M_release_155891_signed". As the phone is not bootable i cant check find that info on the phone anymore.
"Radio_12.28b.60.140e_2 6.03.02.26_M" it's the radio version.
At the bottom of this site is the USB Driver try it.
Thnx to both of u. Everything now working like a charm.
Good that you got it sorted. Can you edit the tag and put [solved]?
sirreal1988 said:
Thnx to both of u. Everything now working like a charm.
Click to expand...
Click to collapse
could you give me for detail how you solved this problem bro? because i have some problem like u (my dhd only black screen with red triangle warning since i was unsuccessfull root my dhd).
soni.setia said:
could you give me for detail how you solved this problem bro? because i have some problem like u (my dhd only black screen with red triangle warning since i was unsuccessfull root my dhd).
Click to expand...
Click to collapse
with an unbranded device it should be easy, download the driver and the image in the posts above, install the driver and run the exe.
On linux/unix you can download the sdk (intructions to install on the site) and then you are able to use the adb commands with the PD98IMG.img also in the posts above.
with a branded device it can be more complicated take a look at this but i don't know how far your system is online and if you are able to use adb.
As the guy above me mentioned, it's quite easy to recover your phone if it's unbranded.
Download a WWE RUU from the link someone postet before. Then boot into the bootloader and connect your DHD to your pc. If you have htc sync installed, it should recognise your phone. Then run the RUU on you pc and everything should be fine now.
I did root my evo 4g hboot 2.18 radio 2.15.0012.19 and i try to downgrade but i get stock... cant do anything and i have no backup... icant get into the recovery and i cant reboot onle the htc evo 4g logo plz help to solve this problem. How Ido to fixed plz help..
eddi2004 said:
I did root my evo 4g hboot 2.18 radio 2.15.0012.19 and i try to downgrade but i get stock... cant do anything and i have no backup... icant get into the recovery and i cant reboot onle the htc evo 4g logo plz help to solve this problem. How Ido to fixed plz help..
Click to expand...
Click to collapse
Try this:
1. power down
2. remove battery
3. press and hold power button for 10 sec.
4. reinstall battery
5. press and hold the volume down button
6. press the power button to turn the phone on but DO NOT release the volume button until you can see the boot screen.
when you are in the boot screen one of the options in the list should say recovery. use the volume button to navigate down to that option and press the power button to select it. your phone should then boot into recovery and you will get the recovery screen and choices.
thanks
i did it but when i get into recovery i see the phone with the sing and then i reboot get stock in htc evo 4g logo if u have any idea how to get into the phone to flash any rom would b perfect tnx
Sounds like it could be a USB brick. This has happened to me before. I remember when that happened to me and couldn't get into recovery. For some reason when I plugged in the micro usb to the phone it would let me boot into recovery. Give that a shot and try searching usb brick. Also my sd card could not be recognized once I booted into recovery.
How did you try to downgrade?
Sent from my PC36100 using xda premium
ok well i flash 2 programs 1 flash_image 2 mtd-eng then run the pc36img but nothing happen it says cant roll back hboot n i reboot the phone n i went to the bootloader n it was locked n i try to enter to the recovery n show me the phone w/ the sing...
any idea where can i get an usb brick??
I'm not familiar with a USB brick, but I believe that your computer can still read your phone through USB. I see that you were trying to S-OFF the phone. Looks like something went wrong when you flashed the misc partition, which locked your bootloader once again.
You should try running an RUU file from your computer with your phone connected which can be found here.
http://goo.im/stock/supersonic/ruu/...15.00.12.19_NV_2.33_release_234563_signed.exe
But first, you will need to install the Fastboot drivers to your computer which can be found here
http://unrevoked.com/rootwiki/doku.php/public/revolutionary
You need to run the RUU from your phone's bootloader from FASTBOOT USB (click on Fastboot then run the RUU from your computer).
If that works, that should at least get your phone back going again (unrooted of course).
i did but w/ the ruu doesnt work too appears error 155 unknow problem n stops i dont know what else to do
Just checking, did you run the RUU in FASTBOOT USB which should have been highlighted in red from your bootloader after clicking FASTBOOT? Also, with your phone connected to your computer while in FASTBOOT USB, check your computer's device manager from the control panel and see do you see anything under Android USB devices.
And too, which PC36IMG file did you try to run?
Sounds like you tryed to downgrade your hboot to the Eng hboot. If that is what you did, then congradulations! You have successfully bricked your device! Hboots are generally NOT downgradable...especially 2.18 to eng
{ParanoiA} said:
Sounds like you tryed to downgrade your hboot to the Eng hboot. If that is what you did, then congradulations! You have successfully bricked your device! Hboots are generally NOT downgradable...especially 2.18 to eng
Click to expand...
Click to collapse
Yea, I was afraid that the wrong PC36IMG file was indeed used. Generally on the newer phones, any downgrade of the Hboot below 2.02 is a guaranteed brick. That's why Captain Throwback only recommends PC36IMG files down to Hboot 2.10 (the 2.02 ones don't work with S-ON phones). On the older hardware however, the Hboot can be downgraded to anything, including 0.76 from 2.18. I've done it on mines. You just have to know which hardware version and partition erasesize your phone has.
the one that i get from evohacks pc36img i think i need one way to flash a rom
the one i get from a post in htcevohacks
is the pc36img
if i brick my phone is there any way to unbrick
eddi2004 said:
the one i get from a post in htcevohacks
is the pc36img
if i brick my phone is there any way to unbrick
Click to expand...
Click to collapse
The best advice that I can give you is to reboot the phone into FASTBOOT USB (connect it to your computer, then go to your bootloader and click on FASTBOOT), then go back to the HTCdev site, start over and try to re-unlock your bootloader. If you can do that, then I may have a workaround for you If not, there might not be much else that you can do.
ok i did everything that u tell me n now i rename the zip (ss_stock_4.67.651) in PC36IMG n then reflash recovery-RA-supersonic-v2.3 now i can get into the recovery menu n i flash the rename (ss_stock_4.67.651) PC36IMG n i have a rom from sprint but now i still cant use adb command so what else shuld i do to recovery to normal n there r many issues that cant load like mail that is forced to sptop unexpected n thank u for all ur help!!
in the command window type:
Code:
fastboot oem enableqxdm 0and then:
Code:
fastboot reboot
eddi2004 said:
in the command window type:
Code:
fastboot oem enableqxdm 0and then:
Code:
fastboot reboot
Click to expand...
Click to collapse
Oh no. I don't know which tutorial you got those instructions from.
I'm also lost with your description of what happened. I hope you unlocked your bootloader, and can now boot into the operating system. If so, you were not suppose to rename the ss_stock_4.67 file to PC36IMG. You were suppose to flash that through RECOVERY as is. If I were you, I would go back to RECOVERY, and wipe All Factory/Reset (or whatever it says) and Dalvik-cache, then reflash the ss_stock file or another ROM.
Second, the adb commands only work from the operating system, not FASTBOOT. You need to be inside the operating system with your phone connected to your computer and USB Debugging enabled under Settings/Applications.
ok here i am
i change the name cos the bootloader let me flash the recovery amon ra 2.3 then i can see the recovery menu n i flash the rom named pc36img n give me the sprint w/ errors now i download another rom that i flash n now my computer can read the sdcard but im still locked n i dont know if im still rooted so the what i think is i have a usb brick so i need to unbrick my usb to use the adb command so i apreciate ur help w/ this thanks all of u for ur help
Hello everybody,
This is my first post on XDA, although I've visited the site oftne
Anyways:
Yesterday I successfully rooted my One X and unlocked its bootloader. I also installed CWM recovery.
As the day came to a close I tried to install LC_MOD in an attempt to change the multitasking softkey to a menu button.
I did not make a backup, and the phone had no backups.
Needless to say the phone wouldnt boot. I panicked and in blind fear sortof erased everything off of my phone. everything. What I basically did was i went into advanced settings and formatted my /sdcard and all those other folders, hoping that would solve the issue (a simple data/cache wipe didnt work). So much data has been erased from the phone that I cannot even mount usb storage through CWM because im missing a file.
So, I come to you all, you gods of the tech world, with my head bowed, to ask for your help. I have literally tried everything in my power to fix the issue. I tried to install custom roms manually, that didnt work. I tried to install an RUU, and even that didnt work (the software could not detect my device). This was all made even more difficult because I myself have a mac, and much of the software I had to use was windows based, which led me on a journey to create a virtual machine.
I know i messed up, and what I'm really hoping someone out there cn do is upload one of their own backups of their One X's software, and show me how to use that to restore my phone.
Somebody out there please please help me :'(
Hi;
There is a reason all developers here shout out loud:
1- BACKUP YOUR PHONE BEFORE YOU F*** IT UP
2- DO NOT DO ANYTHING UNLESS YOU ABSOLUTELY KNOW HOW TO
But anyways, you ruined it, you should get it back, Hopefully you did not drain the battery below 30%, in that case keep on reading the next paragraph, but if you dropped the battery below 30, you should go to CWM Recovery, connect your phone to charger, and wait until it's charged properly...
After charging the phone, you need the correct RUU for your phone... As it seems, you don't know what you're doing, so go to fastboot, type this command:
Code:
fastboot oem readcid
Then post the code here in this topic, so someone can help you find the correct RUU for your phone...
After that go to THIS topic and follow the part where it says "If you DON'T have custom rom or Nandroid backup on internal SD card"
Thanks
Thanks a bunch bro!! And ye i get that it was completely my fault. I normally do backup before i do anything, but i guess i was just a bit too anxious. And I think you've told me everything i need to know, ill get that code out to you asap... And you're right, i seriously have no clue what im doing ^.^, I've never F***ed up this hard on any phone before
Xial649 said:
Thanks a bunch bro!! And ye i get that it was completely my fault. I normally do backup before i do anything, but i guess i was just a bit too anxious. And I think you've told me everything i need to know, ill get that code out to you asap... And you're right, i seriously have no clue what im doing ^.^, I've never F***ed up this hard on any phone before
Click to expand...
Click to collapse
Don't worry, with the correct version of RUU you can restore your phone...
Sent from my HTC One X using XDA
Next?
Alright I got the code:
<bootloader> DEBUG: cid: VODAP102
Whats next?
Xial649 said:
Alright I got the code:
<bootloader> DEBUG: cid: VODAP102
Whats next?
Click to expand...
Click to collapse
Your phone is from Voda Germany, and most probabely your correct RUU is this:
Code:
http://www.filefactory.com/file/t7qugfd3ey9/n/RUU_ENDEAVOR_U_ICS_40_Vodafone_CH-DE_1.26.166.2_Radio_1.1204.90.13_release_251279_signed.exe
Download it. Hopefully it would be the correct RUU for your phone.
1- Now open the exe file you just downloaded and make sure that it fully started.
2- Don't click anything, just open "Computer" (formerly known as my computer) in windows and enter %temp% in your address bar.
3- You will now see some folders, just search through these folders for the ROM.zip (using windows search function)
4- When you found it, copy it to your desktop.
5- Extract it with WinRar,7-zip or something like that and take the boot_signed.img and system.img.
6- Now copy the two files into the folder where the fastboot.exe is placed (if you have installed the Android SDK, it should be in platform-tools)
7- Go to your One X, go into the bootloader and go into fastboot mode. then connect your phone to computer.
8- Open CMD and navigate to the folder in which you have the two images and the fastboot file. (using cd command and after that the address you want to go to)
9- Now type in that
Code:
fastboot flash boot boot_signed.img
10- Now this one
Code:
fastboot flash system system.img
if all this is successful, you can just reboot your phone and everything is OK.
If you can't do any of these, let us now, we will help you through it...
Good lock
---------- Post added at 03:52 PM ---------- Previous post was at 03:41 PM ----------
In other note, RUUs are build to do an stand alone recovery of your phone. So you can first try, just running the RUU application and following the instruction given in the RUU. it may work correctly
This is good
Alright so i got everything going after downloading the RUU and it was in the process of restoring my phone, but then it said my battery went below 30% so i needed to recharge. At that point i had to leave, and so I noticed that if i left my phone in the booting animation (HTC logo) the LED light indicated that the phone was charging. Since I wasnt entirely convinced that my CWM recovery was actually charging the phone, i left it on booting while connected to my pc and hopefully itll be fully charged and ready to be restored tomorrow..... I really appreciate all the help you've given me man you've practically saved my life here , and I'd like to say that you've made my first cry for help a simple and smooth one.... Thank you very much my friend :victory: :highfive:
Problem
Ok so we have a new problem, the system.img file didnt flash. I tried and it said "FAILED"
What now??
& is the boot image supposed to only be around 4300 kb?
Could the sending of "system" failed because my phone had less than 30% batterylife???? & if its in Clockworkmod recovery5.8.4 while connected to an outlet will it be charging???
Edit: I've searched around and I saw this one guy who extracted the "boot_signed.img" and the "recovery_signed.img" (NOT the system.img), flashed them onto his phone, locked the bootloader with "fastboot oem lock", and then RAN the RUU..... He said he bricked his phone, and the situation he described is similar to mine. Any thoughts on which method of the two (yours and his) i should use?
Thanks again :3
Xial649 said:
Ok so we have a new problem, the system.img file didnt flash. I tried and it said "FAILED"
What now??
& is the boot image supposed to only be around 4300 kb?
Could the sending of "system" failed because my phone had less than 30% batterylife???? & if its in Clockworkmod recovery5.8.4 while connected to an outlet will it be charging???
Edit: I've searched around and I saw this one guy who extracted the "boot_signed.img" and the "recovery_signed.img" (NOT the system.img), flashed them onto his phone, locked the bootloader with "fastboot oem lock", and then RAN the RUU..... He said he bricked his phone, and the situation he described is similar to mine. Any thoughts on which method of the two (yours and his) i should use?
Thanks again :3
Click to expand...
Click to collapse
That's another method you can try, boot_signed is the stock kernel (and yes it's that small) and the recovery_signed is the stock recovery...
Since my previously mentioned method didn't work, do this:
1- flash the boot_signed.img into your device (fastboot flash boot boot_signed.img)
2- flash the recovery_signed.img in the device (fastboot flash recovery recovery_signed.img)
3- erase cache (fastboot erase cache)
4- lock your phone (fastboot oem lock)
5- now try again to flash the system image (fastboot flash system system.img)
And also, try having around 40% battery to do all this, don't let the battery drops under 30%
ALRIGHT!!!!
alright man!!!! that sounds like a plan... First thing tomorrow I'm going to try this method out.... and btw the RUU you linked me wasnt exactly working right (the software kept saying i had the wrong ruu), so i searched around and found someone with the same CID (VODAP102) and apperantly the uk RUU works fine on it, so i guess ill use that one ye? And btw does the bootloader have to be unlocked before i can flash these items? because i do believe its locked atm....
Xial649 said:
alright man!!!! that sounds like a plan... First thing tomorrow I'm going to try this method out.... and btw the RUU you linked me wasnt exactly working right (the software kept saying i had the wrong ruu), so i searched around and found someone with the same CID (VODAP102) and apperantly the uk RUU works fine on it, so i guess ill use that one ye? And btw does the bootloader have to be unlocked before i can flash these items? because i do believe its locked atm....
Click to expand...
Click to collapse
Your phone is "Vodafone Germany" version and the link I gave you is the "Voda DE" which seems right, but you can try that as well, doesn't heart...
No, for original ROM (RUU) you should have a locked boot-loader, unlocking is just for custom ROMs.
ok
ok so this is what ill do tomorrow:
1) make sure bootloader is unlocked
2) fastboot flash boot boot_service.img
3) fastboot flash recovery recovery_service.img
4) fastboot oem lock
5) fastboot flash system system.img
did i get everything?
Xial649 said:
ok so this is what ill do tomorrow:
1) make sure bootloader is unlocked
2) fastboot flash boot boot_service.img
3) fastboot flash recovery recovery_service.img
4) fastboot oem lock
5) fastboot flash system system.img
did i get everything?
Click to expand...
Click to collapse
The two first commands should work on a LOCKED boot-loader, so I think step 1 would not be necessary... If your phone is locked you should be able to do all steps 2, 3, 5 without problem (step 1 and 4 are the exact opposite of each other and if the phone is locked already I think can be skipped)
ok so its still not working.... I managed to flasht he boot_signed.img and the recovery_signed.img, clear cache and lock the bootloader after it, but i still cannot seem to flash the damn system.img... Any thoughts?
what happens is command prompt stays static for a second and then says sending 'system' (1000596 KB)
FAILED (remore: (00000006))
finished. total time: -0.000s
so? What now??
Xial649 said:
ok so its still not working.... I managed to flasht he boot_signed.img and the recovery_signed.img, clear cache and lock the bootloader after it, but i still cannot seem to flash the damn system.img... Any thoughts?
what happens is command prompt stays static for a second and then says sending 'system' (1000596 KB)
FAILED (remore: (00000006))
finished. total time: -0.000s
so? What now??
Click to expand...
Click to collapse
Any luck in running the RUU itself directly?
i gave up
alright so nothig worked. Not the manual flash, and not the RUU itself. So ive resolved to visit my local help center for HTC devices, and see what they can do, if they cant fix it the least they can do is send it to the german branch for repairs. Thanks for all your help mate, you've really proven to be a great guide, but I guess something just isnt clicking in this case :/.......... i love u man
I'm not sure if this would work.
If you are still htcdev unlocked:
1. Enter bootloader in fastboot usb
2. Fasboot flash recovery -your recovery .img here"
3. Boot into recovery
4. Go to "mounts and storage"
5. Mount SD(I think this is right) and your sd should show up in your pc
6. Copy your rom zips and other zips you need/want
7. Unmount SD
8. By this time you should be able to flash your rom
9. Make sure you flash boot.img again in bootloader.
Hope this helps
Sent from my HTC One X using xda app-developers app
Isn't it mount usb storage?
Sent from my HTC One X using XDA Premium App
You couldn't mount the USB storage / sdcard because you were running CWM from the bootloader. If you connect it to the pc you can put the recovery file you flashed into the fastboot folder and do:
fastboot boot *recoveryfilename*.img
Then you can mount the sdcard etc.
If you have photos and things you don't want an ruu to get ride of, you can fix the ROM. You broke it by trying to install an deodrexed mod for an odexed Rom. If you're interested I can tell you how to fix it.
You could also take this opportunity to install a custom Rom, with which I can also help.
Dear all,
I have been looking around the forums and downloaded a few things and looked at various solutions, but I am stuck at the first hurdle.
I have been given an htc Desire Bravo that just will not boot. I do not know how it failed originally but I can only get it into the boot screens, either the fastboot/hboot logon ot the 5 buzzes and the htc logo lock. Also it takes about 30 minutes with the battery out after every failed boot attempt to restart the boot screen.
I have run adb but it cannot tell me a cid number, I have a micro sd card in it but it does not have the pb99diag.zip on it. When I put such a file on the sd card it does not find it. Communication via adb and the phone has varied success. I suspect it is drivers and what I read is an old adb bug where server is out of date.
I have never done this before this weekend so please be gentle with me!
If I can get it to work, even to use it like a wifi tablet without phone I would be happy. I am in the UK and if we have real success I would get it on tesco PAYG
I get the "cannot find pb99diag.zip etc" dialogue when going into hboot.
The logon says
BRAVO PVT-1 SHIP S-ON
HBOOT-0.93.0001
MICROP-031d
TOUCH PANEL-SYNT0101
RADIO 5.11.05.27
AUG 10 2010, 17:52.18
Can someone suggest where to start? I have tried a number of guides on the forum but no success so far. Even just getting an os running would be success. I will be looking at this each evening so apologies if I seem slow to respond
Thanks
Adrian
First make S-Off. I forgot how but if i think right, you must it do via revolutionary, If it success, then download 4ext recovery.IMG and flash it via fastboot and reboot in bootloader in your recovery
Sent from my HTC Desire using XDA Free mobile app
battlekaier said:
First make S-Off. I forgot how but if i think right, you must it do via revolutionary, If it success, then download 4ext recovery.IMG and flash it via fastboot and reboot in bootloader in your recovery
Sent from my HTC Desire using XDA Free mobile app
Click to expand...
Click to collapse
Thank you battlekaier, I will try this out tonight when I get home and will report back.
A
ukubuntu said:
Thank you battlekaier, I will try this out tonight when I get home and will report back.
A
Click to expand...
Click to collapse
After you s off u can flash hboot the easy way but first s off.
Sent from my HTC Desire using XDA Free mobile app
If u phone does not boot then u can NOT s-off, ur phone needs to be booted.. also if ur s-on and not rooted then all u can do is flash a ruu.
Did u try factory reset from bootloader menu? Try that first, u never know but chances r ul prob need to ruu a ruu.
jmcclue said:
If u phone does not boot then u can NOT s-off, ur phone needs to be booted.. also if ur s-on and not rooted then all u can do is flash a ruu.
Did u try factory reset from bootloader menu? Try that first, u never know but chances r ul prob need to ruu a ruu.
Click to expand...
Click to collapse
Hi jmcclue,
Thanks for the comments. I can boot to the HBoot and Fastboot screens, thats how I could find the S-ON and version data. If I get it to reboot, I get either a white screen with just "htc" on it, or 5 buzzes and a screen with no life at all. I am hopeful to get it to S-OFF as I have had some communication through the usb to pc connection. I am not sure if I can do an RUU update as I don't seem to have a CID. I do not have a factory reset option on the HBOOT screen. I have tried clear storage but that has no effect. Perhaps I need the S-OFF first.
Cheers again,
A
Use the 2.3gb update ruu its wwe (world wide english) so dont worry bout cid. U can find it in bortaks troubleshooting guide in resources section and its naned 2.3.3 ruu. U will find it easy enough in google aswell. Search for "htc desire 2.3gb update" its a exe file so just boot ur phone into fastboot, plug in ur phone and run the ruu, hopefully it willvwork. Im a bit worried tho about the 5 vibrations u get, maybe a sign of hardware failure. But try that ruu anyway. And again u can not get s-off unless ur phone is fully working/booted.
jmcclue said:
Use the 2.3gb update ruu its wwe (world wide english) so dont worry bout cid. U can find it in bortaks troubleshooting guide in resources section and its naned 2.3.3 ruu. U will find it easy enough in google aswell. Search for "htc desire 2.3gb update" its a exe file so just boot ur phone into fastboot, plug in ur phone and run the ruu, hopefully it willvwork. Im a bit worried tho about the 5 vibrations u get, maybe a sign of hardware failure. But try that ruu anyway. And again u can not get s-off unless ur phone is fully working/booted.
Click to expand...
Click to collapse
Many thanks
Well that was a bit wierd
If anyone can see where I went wrong, feel free to say.
I could not seem to get the link between the phone and the pc so I removed the htc sync and restarted the pc. I could then connect to the phone in some way as abd gave a command error when I sent a fastboot oem readcid which it normally does. So leaving it in fastboot with usb I ran the wwe~.exe file and it all seemed to be doing installing. There were tens of installations going to the phone I guess each reaching 100%. Suddenly I had a web page popup in my browser s.rev2pub.com/ul_cb/player.html?a=19471543&context=c23573548&size=800x600&rt=popunder&ci=10&cb=[CACHEBUSTER] recommending I download latest drivers. The wwe ruu vanished and I have no continuing processes in Task manager that I can see.
So, should I have installed in hboot? Thankfully I can still get the phone to power on. What should happen after the exe file installs?
I am able to get some response from the phone as adb devices returns the phone device number. So I hope I can try again.
Any thoughts?
Many thanks
Revolutionary S-OFF and recovery
ukubuntu said:
Dear all,
I have been looking around the forums and downloaded a few things and looked at various solutions, but I am stuck at the first hurdle.
I have been given an htc Desire Bravo that just will not boot. I do not know how it failed originally but I can only get it into the boot screens, either the fastboot/hboot logon ot the 5 buzzes and the htc logo lock. Also it takes about 30 minutes with the battery out after every failed boot attempt to restart the boot screen.
I have run adb but it cannot tell me a cid number, I have a micro sd card in it but it does not have the pb99diag.zip on it. When I put such a file on the sd card it does not find it. Communication via adb and the phone has varied success. I suspect it is drivers and what I read is an old adb bug where server is out of date.
I have never done this before this weekend so please be gentle with me!
If I can get it to work, even to use it like a wifi tablet without phone I would be happy. I am in the UK and if we have real success I would get it on tesco PAYG
I get the "cannot find pb99diag.zip etc" dialogue when going into hboot.
The logon says
BRAVO PVT-1 SHIP S-ON
HBOOT-0.93.0001
MICROP-031d
TOUCH PANEL-SYNT0101
RADIO 5.11.05.27
AUG 10 2010, 17:52.18
Can someone suggest where to start? I have tried a number of guides on the forum but no success so far. Even just getting an os running would be success. I will be looking at this each evening so apologies if I seem slow to respond
Thanks
Adrian
Click to expand...
Click to collapse
Hey Adrian, I had the same problem as you did, hopefully I can be of help.
First, like everyone else is saying you will need S-OFF.
To do this head to this site on your PC revolutionary.io hit download for windows or Linux or whatever your pc is running, then you will need to fill out information about your device (see attached screenshot). Device, HBoot number, and serial number, (the serial number can be found behind the battery of your device). Once you have done that, click "Generate Key". it will give you a key, remember it or write it down.
Then, open the file that was downloaded, and extract the contents to your documents and Run the revolutionary( should look like the screenshot attached). Plug your device in (assuming you have the drivers) and it should ask you to enter the beta key we had before. Enter that and hit enter. it will then S-off your Desire and soon ask if you would like to install a custom recovery. hit Y and then enter, once that is finished, unplug your device and in HBoot go to "Recovery". Now you can flash a ROM of your choice.
Hopefully I made sense!
Best of luck
Neibaf97 said:
Hey Adrian, I had the same problem as you did, hopefully I can be of help.
First, like everyone else is saying you will need S-OFF.
To do this head to this site on your PC revolutionary.io hit download for windows or Linux or whatever your pc is running, then you will need to fill out information about your device (see attached screenshot). Device, HBoot number, and serial number, (the serial number can be found behind the battery of your device). Once you have done that, click "Generate Key". it will give you a key, remember it or write it down.
Then, open the file that was downloaded, and extract the contents to your documents and Run the revolutionary( should look like the screenshot attached). Plug your device in (assuming you have the drivers) and it should ask you to enter the beta key we had before. Enter that and hit enter. it will then S-off your Desire and soon ask if you would like to install a custom recovery. hit Y and then enter, once that is finished, unplug your device and in HBoot go to "Recovery". Now you can flash a ROM of your choice.
Hopefully I made sense!
Best of luck
Click to expand...
Click to collapse
Thank you Neibaf97
Can I confirm that I can do this from the HBOOT screen or the fastboot screen? Also where jmmclue said if I can't boot then I can't S-Off, does that mean boot to the HBOOT screen or into Android? Then if I want to load say WWE, do I put that on a microSD to get it to recover?
thanks again
A
ukubuntu said:
Thank you Neibaf97
Can I confirm that I can do this from the HBOOT screen or the fastboot screen? Also where jmmclue said if I can't boot then I can't S-Off, does that mean boot to the HBOOT screen or into Android? Then if I want to load say WWE, do I put that on a microSD to get it to recover?
thanks again
A
Click to expand...
Click to collapse
He means into android.
Sent from my HTC Desire using XDA Free mobile app
lilsafbig said:
He means into android.
Sent from my HTC Desire using XDA Free mobile app
Click to expand...
Click to collapse
Thanks lilsafbig, that was a little too ambiguous to understand, but I have a few developments.
I am able to communicate to some degree with adb between phone and pc. Before I was unable to get anything back but now with the right syntax I have got back the CID as HTC_001 and the device number. But when I run revolutionary from the fastboot USB screen the revolutionary continues to wait for the device to show. Is it likely that USB degugging was off prior to the failure, is there a way to get it on. I suggest this as when I connect it to my pc it recognizes the device and shows in the device manager as an htc unspecified device (this is progress). As I cannot boot android it does not show as an additional drive in file manger. when I try some of the fastboot oem commands I get bad command errors, whilst fastboot getvars is ok. Could this be why I cannot get revolutionary to S-OFF!
Thanks
additional info, when usb is in an in fastboot usb, the device manager sees it as android 1.0
ukubuntu said:
additional info, when usb is in an in fastboot usb, the device manager sees it as android 1.0
Click to expand...
Click to collapse
also tried "fastboot oem writecid 11111111" and got "FAILED(remoteartition is not existed).."
ukubuntu said:
also tried "fastboot oem writecid 11111111" and got "FAILED(remoteartition is not existed).."
Click to expand...
Click to collapse
So..... does this mean I am bricked?
BUMP!
ukubuntu said:
So..... does this mean I am bricked?
Click to expand...
Click to collapse
If you can still get to bootloader / fastboot screen, then you are rarely ever bricked.
1. Ignore anything and everything to do with revolutionary and fastboot for now. I'm afraid the first few posts while trying to be helpful have been misleading. Get your phone booting up into Android OS first, i.e. into a stock ROM using an RUU
2. Use the 2.3.3. GB RUU, nothing else, it doesn't need a goldcard or care about CID etc.
3. Download it from the bottom here, then use Bortak's troubleshooting guide stickied to the top of Q&A, Point [7] to run it as a PB99IMG.zip from the root of your sdcard. That way you don't need to run it through USB or care about what drivers are installed.
Thank you Eddie, I will try that. I did try flash a PB99IMG.zip before with no success but I will try again.
I found it here Official Stock Sense Gingerbread_v1.2 GB-2.3.3_A2SD – http://androidba.se/J7 for desire (neophyte)
I hope it can work out ok. I guess I format the sd card to fat32 not ext4
Will let you know how it goes.
Thanks,
A
ukubuntu said:
Thank you Eddie, I will try that. I did try flash a PB99IMG.zip before with no success but I will try again.
I found it here Official Stock Sense Gingerbread_v1.2 GB-2.3.3_A2SD – http://androidba.se/J7 for desire (neophyte)
I hope it can work out ok. I guess I format the sd card to fat32 not ext4
Will let you know how it goes.
Thanks,
A
Click to expand...
Click to collapse
That's a custom rom.
Here's the link for the 2.3.3 ruu.
http://www.theandroidsoul.com/downl...uu-now-to-update-to-to-the-latest-android-os/
Sent from my HTC Desire using XDA Free mobile app
ukubuntu said:
I did try flash a PB99IMG.zip before with no success but I will try again.
I found it here Official Stock Sense Gingerbread_v1.2 GB-2.3.3_A2SD – http://androidba.se/J7 for desire (neophyte)/
Click to expand...
Click to collapse
That did not work because the file is not an RUU...it is a stock rooted custom ROM with A2SD (the clue is in the name). It is designed to flashed in recovery like any other ROM. Renaming it to PB99IMG.zip won't do anything.
Use the actual shipped roms RUU link provided.
Reformat your sdcard to a single FAT32 partition if necessary, then follow Method [7] of the guide, place only the PB99IMG.zip on the root of the sdcard (not in any folder)