edit: It finally worked. I cleaned the microsd with diskpart and made a new goldcard, then I flashed a HTC WWE 2.29 Image, with the PB99IMG method. Now Im on bootloader 0.93.00. Back to business (I don't know exactly why the goldcard worked this time, or maybe the goldcard wasnt the problem)
Hello,
I tried to go back to the original state (TMobile germany branded). The phone was S-Off and rooted and I had a cm7 partition table.
At first I just tried to flash over an original T Mobile Rom (RUU_Bravo_TMO_UK_1.21.110.4_Radio_32.36.00.28U_4.06.00.02_2_release_127570a_signed.exe).
Everything worked, and after that I did put the newest OTA Update on the phone. Checking to see what bootloader I have I saw that I was still Security Off. So I flashed a downgrade HBoot from the alpharev page. After that I flashed the same T Mobile Rom again to have an original HBoot.
Somewhere in the middle of the procedure though it stopped and I was stuck in that screen with four triangles on the sides and HTC written in the middle. At first I thought now its totally bricked without hboot, but I was able to reboot into HBoot. Also i can get to fastboot and the standard recovery mode. The current Hboot is 0.80 and S-ON.
Now from there on I tried many things:
- Downgrader from xdadevelopers does not work because one has to be in a working system
- Unrevoked does need a working system
- Tried same TMobile Rom numerous times with the installer on PC (gives bootloader version wrong 140) and as update.zip in recovery mode (signature verification failed)
- Tried RUU_Bravo_HTC_WWE_1.21.405.2_Radio_32.36.00.28U_4.06.00.02_2_release_126984_signed.exe and RUU_Bravo_HTC_Europe_1.15.405.3_Radio_32.30.00.28U_4.05.00.11_release_121865.exe
- I made a goldcard and tried to flash these roms from the goldcard in recovery mode
- Tried to flash the ota update I installed through recovery mode
- Also I tried all of these things with the rom.zip named as PB99IMG.zip in Bootloader
- Fastboot commands do not work, So I should have a locked Bootloader now
- The old root method with goldcard which did not work
- I tried to get into an adb shell in recovery mode with various drivers to get the cid of the sd card to make a new goldcard but the device is listed as offline
I am not really sure why the goldcard does not work, maybe my saved goldcard image got messed up for some reason. Unfortunately I can't get the cid of the phone, because I can't use adb meaning the phone is recognized with "adb devices" but shown as offline.
If there is some other way to get the cid that I have not found as of yet, that might help.
Otherwise I am out of ideas... I hope its not bricked, help is greatly appreciated
edit: official update utility tmobile rom shows that I'm coming from 2.12.110.2 and going to 1.21.110.4 so it seems like the room still exists somehow but cannot boot, bootloader starts and deletes user data, sends data, updates signature=> bootloader version error 140
Related
Hi,
I tried to flash the standard HTC RUU so that i could send it in for repair.
It said that it couldn't flash and gave me error code 140.
Now whenever i turn on my phone it goes straight to fastboot mode which i think means there is no rom on the phone.
However the RUU overwrote my recovery and i dont have an sd reader to put a recovery update.zip on the sd card.
I want to do this so i can try and flash a rom to allow me to boot and try the RUU again.
Is there any way i can either copy files to the sd card or flash a recovery img from hboot, fastboot or recovery?
i tried using "fastboot flash recovery c:\recovery.img" but it just hangs the terminal, any idea why?
Thanks
this looks like it could help
http://forum.xda-developers.com/showthread.php?t=531310
can anyone clarify where exactly i enter the commands.
Im in recovery (black screen with red triangle).
thanks
Not sure if that will help but you enter those commands through ABD in the CMD terminal on your PC.
I'm not sure on this but your fastboot flash might be hanging because your file might need to be in your tools folder within your Android SDK folder.
no that didnt help. I think im gonna have to wait until tomorrow and buy a card reader
thanks
With flashing an ruu you are s-on and you cannot use fastboot any more.
Make a goldcard with linux (as far as i understand you cannot boot into your phone's os any more):
http://www.nazriawang.com/2010/04/how-to-create-goldcard-with-ubuntu.html
Then put this in your desire and try to flash ruu again. It should work now.
I know that i can use the RUU because i've used it before. I think it failed because i was S off (im not sure how i was meant to S on first). I think i need to:
1. copy update.zip to sd card with a recovery in it, and a rooted rom
2. boot to recovery via update.zip
3. flash a rooted rom
4. boot into rom and then flash RUU using the exe
Is this correct? as far as i know i have to be in android to use the RUU, is this correct? If i could flash it from recovery it would save me doing step 3.
thanks
Sorry, but i do not understand you...
Please answer these questions first:
Can you boot into clockworkmod or amonra recovery?
Can you start your rom?
Which hboot do you use?
And flashing failed because of cid error i think? So why don't you create goldcard and try to flash ruu again? The programm will tell exactly what to do.
no, i can only get into the blue basic recovery. This is why i need to put update zip onto the sd card so i can access amonra.
I cant start my rom. when i turn it on normally it goes straight to the fastboot screen with 3 androids at the bottom.
HBOOT is 0.80.0000
Flashing didnt fail because of CID error because i brought my phone unlocked and i have used this exact same RUU before (its the standard HTC signed one). i dont understand how a goldcard would help as i need to be booted into a rom before i can flash the RUU. I dont think i can do it from recovery?
Thanks
"I know that i can use the RUU because i've used it before. I think it failed because i was S off (im not sure how i was meant to S on first). I think i need to:"
You don't have to be S-ON to be able to flash a RUU. The actual RUU will override anything you have done to "jailbreak" your phone: ROOT, S-OFF, Custom HBOOT, Custom Recovery (Amon RA or CWM) and restore you to basic (you'll have none of the above). This is why it is used.
If you have tried to flash the RUU and get the error, you are more than probably not ROOT-ed and S-OFF anymore so you can't install a CUSTOM ROM. This is what makes the problems even harder.
The error you got: Error 140 is Bootloader version error.
Read the second post from http://forum.xda-developers.com/showthread.php?t=880268 and try to extract the PB99IMG.zip from your RUU and try to flash it from card in boot.
EDIT: Also be sure (I don't know how ) if the RUU you got has the same bootloader version as your phone. I read that this is a kind of incompatibility if it is lower than your version.
You should get the latest WWE 2.29.405.5 RUU. I think this should be compatible. Extract the PB99 and put it on root of SD.
LEDIT: if you want to mount your SD card try this http://forum.xda-developers.com/showthread.php?t=531310. Maybe it helps you.
Ive tried it with RUU RUU_Bravo_HTC_WWE_1.21.405.2_Radio_32.36.00.28U_4. 06.00.02_2_release_126984_signed.exe
It gives me an error "Main version is older!"
do you think this means i should try the newer version you recommended or the older version (RUU_Bravo_HTC_WWE_1.15.405.4_Radio_32.30.00.28U_4. 05.00.11_release_122704.exe)
Thanks for your help
That has worked perfectly with the RUU you recommended. I will be keeping that image on my SD card to avoid this happening again.
Thanks
jbaldwinroberts said:
That has worked perfectly with the RUU you recommended. I will be keeping that image on my SD card to avoid this happening again.
Thanks
Click to expand...
Click to collapse
I'm glad I was able to help you and that you resolved your problem.
Hello together
i really need your help, i think i just bricked my phone.
like the title says i got a german vodafone branded DHD which is now stuck on the white background with the green htc logo.
Original rom version: 3.13.161.5
Android 2.3.5
radio 26.14.52.27
bootloader 2.00.0027
the story:
after updating hboot to version 2.00.0029 i was able to unlock the bootloader via htc dev and the easy ace root tool.
i created a goldcard
then i started the now installed cwm and tried to install cynaogen 7.xx (dont know the version exactly)
after this the device dindt want to boot anymore or let me even enter the bootloader
i mangaged to get into the bootloader again via "adb reboot bootloader" command
then i have done the recommended "full wipe" of all caches and installed cyanogen 7.2.0 + the boot.img file and the other zip file that belongs to non-sense roms.
AND now it wont start anymore or let me acces the bootloader again, even the adb or fastboot commands don't work
i downloaded an original stock htc ruu, it doesnt recognize my phone, none of the tools does
as you can see from my post im a noob, i got the phone now for 2 days and hope i didnt brick it.
can anybody help me?
How did you flash the boot.img? What other zip are you referring to?
bananagranola said:
How did you flash the boot.img? What other zip are you referring to?
Click to expand...
Click to collapse
boot.img via cmd window, this file was named gapps-gb-20110828-signed and i understood to install this one additionally to the system image
current state of affairs:
le me idiota, didnt recognise i can pull out the battery....
now i finally figured out how to get into the bootloader again, i am even able to start clockword mod recovery and install zip files from there and also the acces via cmd window works again.
but even if i install the zip from the sd card and flash the boot image via console into the phone, the system doesnt start
my problem now is (i just think this is the problem) that i wiped all caches and therefore there is no more usb debuging enabled and the system wont start. also my hboot says it is unlocked but s-on.
http://forum.xda-developers.com/showpost.php?p=31211732&postcount=396
this was the solution to my question, thank you forum!
Well after about 20+ hours spent looking online and tinkering with my phone I have arrived at this point. I have been trying to install a custom rom with no success. I have rooted and S-OFF my phone with revolutionary. I have installed 4ext recovery. I have been trying to install the cm 10.1 rom and/or the paranoidandroid rom. No success on either one, I always got the status 7 error. After looking online I found that status 7 relates to the wrong HBOOT, so I flashed the the stock HBOOT from alpharev.nl and now my phone's screen won't turn on for any mode(normal boot, hboot, fastboot) it's just a black screen. The phone does "turn on" because my pc can see that it's there and it vibrates. I can also send fastboot commands to the phone.
Does anyone know of this problem and how to fix it? I've tried to flash different HBOOTS and ROMS and Recovery but with no success, it always says "out of memory" or a different error. Also I tired doing SUU but it always says I have the wrong model phone.
I just tried fastboot flash hboot bravo_downgrade.img(from alpharev.nl)
fastboot reboot-bootloader
fastboot erase cache
then I ran RUU from shipped-roms.com it was the HTC_Desire_Android_2.3_Upgrade.exe
gives me "error 130 model id error"
Anyone?
cree125 said:
I just tried fastboot flash hboot bravo_downgrade.img(from alpharev.nl)
fastboot reboot-bootloader
fastboot erase cache
then I ran RUU from shipped-roms.com it was the HTC_Desire_Android_2.3_Upgrade.exe
gives me "error 130 model id error"
Click to expand...
Click to collapse
the downgrader isn't actually an hboot, it's just a way of 'unlocking' an hboot like cm7r2 which can't be overwritten by RUU.
flash the stock hboot again, then run the 2.3.3 RUU.
I repeated the same process as in the previous post except replacing the downgrader with the stock boot and received the error. The RUU starts to work and the progress bar at the top says "sending" but then just stops and gives the error. I am not very knowledgeable about android OS so basically I am out of ideas at this point.
cree125 said:
I repeated the same process as in the previous post except replacing the downgrader with the stock boot and received the error. The RUU starts to work and the progress bar at the top says "sending" but then just stops and gives the error. I am not very knowledgeable about android OS so basically I am out of ideas at this point.
Click to expand...
Click to collapse
Can you boot into bootloader and confirm what it says on the top line please?
Have you tried the 2.3.3 RUU by PB99IMG.zip method?
Try bortak's troubleshooting guide, step 7, ignore the bit about goldcard for now. You basically need to extract the rom from your RUU, rename it to PB99IMG.zip, and put it on the root of your sd card to run from bootloader.
eddiehk6 said:
Can you boot into bootloader and confirm what it says on the top line please?
Have you tried the 2.3.3 RUU by PB99IMG.zip method?
Try bortak's troubleshooting guide, step 7, ignore the bit about goldcard for now. You basically need to extract the rom from your RUU, rename it to PB99IMG.zip, and put it on the root of your sd card to run from bootloader.
Click to expand...
Click to collapse
Sorry I have been really busy with work! Hopefully I can try this with in the next couple days, thanks a lot for the advice!
Hey guys,
So I've spent the last 48 hours raking my head on this one. I'm an intermediate user (Samsung whiz - Ace, i9100, T989, I747, S4 Canada, knowledgeable in HTC's - S-OFF HTC Evo 3D GSM / S-OFF HTC EVO 4G, experience in Experia devices), so I'd say I've done some things, but this one has totally stumped me.
I've successfully:
- Managed to upgrade the HBOOT before unlocking the bootloader (required an RUU update > "PG7611000_Marvel_Hboot_1.08.0099_1.36.666.5.exe"
- Flashed TWRP/CWM (currently running TWRP) using "fastboot oem flash recovery"
- Created a backup of the stock ROM
- Flashed latest version of SuperSU
Now, I restarted the WFS to finalize all my work and hand it back to my friend, but it just bootloops. I do have access to the bootloader still, and always have. I try to load recovery through the bootloader and it bootloops.
Here's the real kicker:
- If I keep the USB cable plugged in, it runs beautifully. Both booting normally into any ROM I've flashed, and to the recovery.
- If I unplug the USB cable when booted into the ROM, it'll run fine until I restart/shut down.
- If I pull the battery and start it up normally, it bootloops. Vibrate, HTC logo, sits for about 5 seconds, goes black, repeat.
Attempts:
- I've tried to create a Gold Card, but the website making the *.img file is down. Tried the other site that just asks for your CID and spits out the *.img file, but neither forward/backward works.
- I've downloaded the only full Bell RUU > "RUU_Marvel_BM_1.36.666.5_Radio_47.10a.35.3030_7.46.36.14M_release_189856_signed.exe", then tried pulling the ROM.zip from the temp folder. It's the only one where the archive appears to be broken. I've tried different download locations and confirmed the md5 matches.
- I've tried just running the Bell RUU thinking that it might work, but it doesn't when it's an older release or equal to the existing one.
- I've tried the latest European RUU > "RUU_Marvel_S_HTC_Europe_2.26.401.3_Radio_47.23e.35.3038H_7.57.39.10M_release_261695_signed.exe" and I can pull the ROM.zip, but because the phone is BM___001, it won't allow the flash. I would need a Gold Card, which as I've mentioned is unavailable.
The only thing I haven't done (scared to do so)
- I haven't tried flashing it directly using "Method 3" in This Link because I'm afraid to really brick the device.
Because I can't unzip the Bell RUU (corrupted), I'm afraid to try using even the generic European RUU. Would this even work? There's also this Link which I've checked, but again, I don't think I can even do this one without the Gold Card working.
Leave it to Bell for only having one RUU.
Any thoughts on this very peculiar issue? I've seen a few threads that talk about other HTC devices with this issue, but only an RUU can be performed. And back to the "only-one-Bell-RUU" and "Gold-Card-website-down" issue.
Any help would be greatly appreciated!
Stats:
- Bell HTC Wildfire S (Bell Branded, BM___001)
- Unlocked Bootloader from HTC Dev
- TWRP 2.2.2.0
- Marvellous-Sense-3.5_07.10.13_FIXED
*** UNLOCKED ****
MARVEL PVT SHIP S-ON RL
HBOOT - 1.08.0099
MICROP - 0451
RADIO - 7.46.36.14M
Nov 28 2011, 19:09:21
I'm working from memory, and I'm only going by what you typed, but I'll suggest 2 things for your consideration/research:
I'm unsure how you used, "fastboot oem flash recovery". In my wildfireS (Marvel) the command, "fastboot oem..." doesn't have a flash command option. I'm wondering if this has got you stuck in a bootloader bootloop. You can see the available fastboot [bootloader] commands by hooking up to your PC and in fastboot, type, "fastboot oem ?" without the quotations of course, and it will list the commands. I wonder if you flashed your recovery without that oem in the command line if that might help??? I've always just done straight, "fastboot flash recovery [recovery].img"
The second thing is I've read that either ChainsDD superuser or the superuserSU by Chainfire doesn't play well with TWRP. I don't remember which. Although that's less likely to cause a bootloop, I'm just throwing it out there for consideration.
I'm sorry I can't say anything definitive, but those 2 things came to mind reading your post. Good luck.
Boot Loader Loop, Unlocked, S-Off, Rooted HTC M8 Tmobile
A year ago I believe I used HBoot and or Firewater to root my M8. I recently removed some applications that seemed to make my phone act funny, and now the phone is stuck in a boot loop, or rather just a boot and stop at the second HTC "One" screen. Not exactly a loop.
I've download ADB tool and tried the fastboot method to install TWRP but have no success because the computer does not recognize the phone while running ADB or Fastboot, therefore I cant install TWRP and am stuck in the bootloader menu. I have tried various different cables and restarted the pc several times, and installed htc sync and other drivers necessary for that process. Also uninstalled and installed different drivers later as well. Now im not sure what i have installed but I have access to the phones internal drive via explorer.
Using Hboot.
Stats:
***UNLOCKED***
M8_UL PVT SHIP S-OFF
CID-HTC__32
RADIO- 1.15.2133156
OpenDSP-v38.2.2-00542-M8974.0311
OS-1.54.401.5
eMMc-boot 2048MB
Mar 22 2014, 00:53:32.0
Options:
HBOOT (when scanning says that all images are not found)
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
CHECK SMART SD
IMAGE CRC
SHOW BARCODE
Recovery leads to nothing and eventually returns to the HTC One menu stop.
Reset does nothing, acts like fast boot actually.
Ramdump under fastboot seems to works, and does produce log files.
While the phone was still active, I managed to create a full "manual" backup of the device by plugging it in and backing up/copying the entire internal memory. After screwing with the phone and every option for several hours I managed to access the files of the internal memory by switching to recovery mode via the boot menu and then plugging in the phone via usb to comp while deleting the drivers at the same time. I tried a full restoration of the internal backup i made, by copy and replace if the same method, but still nothing.
Ive attached an image of the Hboot menu with the details and options of that Hboot for those of you familiar with hboot.
The ideal situation, or what i'd like to do is restore the phone without flashing the rom and loosing the information, then id like to upgrade to lollipop or a new custom rom I found here actually, but the first step is getting back into the phone which i would be very grateful for in general.
also, not great with cmd and all that stuff, I do have sdk tools downloaded and installed but not great with that either. If there was a more simple way to replace existing files in the phone via the file manager (because im able to access the internal drive via the file manager, that would be the most ideal and easiest situation. But knowing the path and the boot files and which files are necessary for boot is what im looking for as well.
Also i know how to flash a sd and htc has a sdcard slot as well. Also i should mention that prior to the phone being screwed up I did want to delete some internal certificates because i believe someone installed a spy application on the phone, hence the reason for all of this checkup and removal anyway. In the process of trying to do that, i followed a tutorial on this forum which suggested I create a security lock pin, which I did. This could also be the cause of the problem not being recognized by the adb or fastboot script.
Who ever helps me do that gets a tip.
Please help.
It's not easy to find a nandroid backup with such old version no.
You already backup your internal memory data/files.
Why don't just run RUU to start fresh at lollipop level.
Run this RUU - RUU_M8_UL_L50_SENSE60_MR_HTC_Europe_4.16.401.10_Radio_1.25.214500021.06G_20.68.4196t.01_F_release_417003_signed.exe
Download here : http://androidruu.com/?developer=M8
What you need :
Put the device in bootloader/fastboot mode
A windows PC with USB2.0
Right click the exe and select run as administrator and follow the instructions ..
Won't that delete all my current contacts/logs/texts, etc?
ckpv5 said:
It's not easy to find a nandroid backup with such old version no.
You already backup your internal memory data/files.
Why don't just run RUU to start fresh at lollipop level.
Run this RUU - RUU_M8_UL_L50_SENSE60_MR_HTC_Europe_4.16.401.10_Radio_1.25.214500021.06G_20.68.4196t.01_F_release_417003_signed.exe
Download here :
What you need :
Put the device in bootloader/fastboot mode
A windows PC with USB2.0
Right click the exe and select run as administrator and follow the instructions ..
Click to expand...
Click to collapse
ckpv5 said:
It's not easy to find a nandroid backup with such old version no.
You already backup your internal memory data/files.
Why don't just run RUU to start fresh at lollipop level.
Run this RUU - RUU_M8_UL_L50_SENSE60_MR_HTC_Europe_4.16.401.10_Radio_1.25.214500021.06G_20.68.4196t.01_F_release_417003_signed.exe
Download here :
What you need :
Put the device in bootloader/fastboot mode
A windows PC with USB2.0
Right click the exe and select run as administrator and follow the instructions ..
Click to expand...
Click to collapse
By the way, Your rom was the was one i already downloaded and wanted to install for M8. The skydragon for M8. SO it's cool that you're helping.
Yeah .. the RUU will wipes everything .. that's why I said start fresh.
SD ROM/any lollipop based ROM won't work on your current hboot, too old/outdated version.
Good luck .. it's 4 am here, good night