Database Develop

[Q] BootLoop Infinity!!!!!

Recently, I had saved on my HDD before PirateGhost pulled it, his ICS rom, So I followed the diretions to flash the boot.img before flashing thr rom, so it installed and such, and when it went back to the recovery menu it said installed failed, but the actual program that launched o install the stuff said it was ok..Ok lets fast forward I reboot the device and it starts booting up, and shows the boot animation, then it will freeze and of course bootloop, but me being smart I did a backup before I installed anything and it still bootloops, it doesn't even get to the bootanimation... So this is where I start worrying. So I looked and try to revert back to stock just to see if it will work, I can't even lock my bootloader because it says something about error too many links.>.< I need help and any help is most appreciative!

Did you let the PH39IMG.zip install 2 times? Or did you try to update to the newest H-Boot before you re-locked your bootloader? I saw the same error about too many links when I tried to update H-Boot before I locked the bootloader. When you go into the bootloader what version of H-boot does it show?

I have Hboot 1.83.0014, and after i installed the PH39IMG, I installed a new kernel and a new rom too see if it would work and it booted up and everything it was working, so I tried to restart the phone to restore a backup I had and now my recovery won't even boot up, I can still access bootloader and such

Riomaru said:
I have Hboot 1.83.0014, and after i installed the PH39IMG, I installed a new kernel and a new rom too see if it would work and it booted up and everything it was working, so I tried to restart the phone to restore a backup I had and now my recovery won't even boot up, I can still access bootloader and such
Click to expand...
Click to collapse
Read the instructions again. You have the wrong hboot
Sent from my HTC PH39100 using xda premium

Riomaru said:
I have Hboot 1.83.0014, and after i installed the PH39IMG, I installed a new kernel and a new rom too see if it would work and it booted up and everything it was working, so I tried to restart the phone to restore a backup I had and now my recovery won't even boot up, I can still access bootloader and such
Click to expand...
Click to collapse
That's the old H-Boot. That's why the ICS ROM doesn't flash correctly. You need to lock your bootloader and use the PH39IMG.zip to install the new H-Boot. Ignore the error you get on the command line when relocking. You should get into the bootloader and it should say relocked and have a security warning of some kind. Just let it run the PH39IMG.zip and update. It will run once and turn your phone off. Boot back into the bootloader and let it update again. When it's done you will have to flash recovery again, then the boot.img, and then boot to recovery and flash the ROM.

pside15 said:
Just let it run the PH39IMG.zip and update. It will run once and turn your phone off. Boot back into the bootloader and let it update again. When it's done you will have to flash recovery again, then the boot.img, and then boot to recovery and flash the ROM.
Click to expand...
Click to collapse
The step I bolded isn't necessary. If you wait long enough (30-45 seconds?), the phone powers back on and boots into bootloader on it's own and completes the install without any action required on your part.

anthromatt said:
The step I bolded isn't necessary. If you wait long enough (30-45 seconds?), the phone powers back on and boots into bootloader on it's own and completes the install without any action required on your part.
Click to expand...
Click to collapse
Thanks for the info. I wasn't aware of that. I just booted back to the bootloader manually and everything worked well.

pside15 said:
Thanks for the info. I wasn't aware of that. I just booted back to the bootloader manually and everything worked well.
Click to expand...
Click to collapse
Yeah, I discovered that by accident after about 4 failed attempts to successfully flash. The last time I "forgot" to pull the battery after the phone powered off because I had gone into the kitchen to get coffee. When I returned, it had rebooted itself and was finishing the update.

I couldn't flash the recovery while it was locked so I had to unlock it, but currently I am flashing the rom and I will see what happens

I had success by flashing the RUU first then flashing the new recovery, then finally the Rum Float zip file.

Riomaru said:
I couldn't flash the recovery while it was locked so I had to unlock it, but currently I am flashing the rom and I will see what happens
Click to expand...
Click to collapse
Yes, that is true but you didn't complete the H-Boot update. ICS ROMs won't flash properly on the old H-boot. You need to lock the bootloader to use the PH39IMG.zip to update H-Boot then unlock and flash recovery and then ROM.

pside15 said:
That's the old H-Boot. That's why the ICS ROM doesn't flash correctly. You need to lock your bootloader and use the PH39IMG.zip to install the new H-Boot. Ignore the error you get on the command line when relocking. You should get into the bootloader and it should say relocked and have a security warning of some kind. Just let it run the PH39IMG.zip and update. It will run once and turn your phone off. Boot back into the bootloader and let it update again. When it's done you will have to flash recovery again, then the boot.img, and then boot to recovery and flash the ROM.
Click to expand...
Click to collapse
Ok that did it !!!! Thank so much

Riomaru said:
Ok that did it !!!! Thank so much
Click to expand...
Click to collapse
No problem. Glad you got everything worked out.

I have a soft-bricked Raider and looks like I am having the same problem, I have hboot 1.83.0014 and unlocked. a getver all shows the version-main to be 1.65.666.3 so I google that up and found this ICS image...
OTA_HOLIDAY_ICS_35_S_BM_3.38.666.2-1.65.666.3_release_255932wpop8vtj8tts3ou3.zip
http://forum.xda-developers.com/showthread.php?t=1498003
So it appear I need to lock my bootloader and update the hboot.
When I run oem lock this is what I get.
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot oem lock
...
(bootloader) Lock successfully...
FAILED (status read failed (Unknown error))
finished. total time: 0.022s
I let it sit for 15 minutes but no change.
what do I need to do to get my bootloader relocked?

Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Thanks ✟
Moving to Q&A

HELP! Stuck on HTC quietly brillant boot screen

Hi Guys,
My heads sorta spinning from information overload so I'm hoping one of you guys can help me. I have a Incredible S and I used this guide to downgrade my HBOOT and get my S-OFF using revolutionary and flash clockwork, which I did successfully. I then decided to install this ROM which requires Blackrose. So I installed blackrose beta sucessfully overwriting the revolutionary HBOOT. This is where it all starts to go wrong. I then set about doing a full wipe and tried to install the ROM using Clockwork and the installation completed sucessfully. But when I try to boot up my phone I get stuck at the HTC quietly brilliant screen. I also restored a backup I took with Clockwork with the same results; stuck at the boot screen. I tried following the steps in the thread of the ROM (listed below) with no avail.
Here are some steps you can try if the ROM hangs on the HTC splash screen
1. Download the file lib.zip from here: http://bit.ly/PwK4BH (MD5 SUM: 83dd68b32d39c994b3069d8813b3c3ea)
2. Unzip the lib.img and place it on your PC where you have fastboot.exe installed.
3. Boot into FASTBOOT USB mode and then enter the following command:
fastboot flash lib lib.img
4. Wipe Data/System Reset.
5. Wipe Dalvik Cache.
6. Then reinstall vivo_signed_WWE_4.10.405.1_ICS_SENSE36_8.zip
Do any of you guys have any suggestions or know whats wrong? Even if I can get back to the latest stock ROM while preserving my root I would be happy.
Thanks Guys!!!
BTW i would have posted in the rom thread on I dont have enough posts :crying:

No need blackrose on this rom. Just flash and install rom if you S-On flash boot.img manual via adb flash.
Before, i ve used that rom & back to my prev rom like Stock and Nik Rom.
++no need blackrose++
Sent from my HTC Incredible S using xda app-developers app

wesly.btm said:
No need blackrose on this rom. Just flash and install rom if you S-On flash boot.img manual via adb flash.
Before, i ve used that rom & back to my prev rom like Stock and Nik Rom.
++no need blackrose++
Sent from my HTC Incredible S using xda app-developers app
Click to expand...
Click to collapse
It says in the ROM thread "This ROM requires that you upgrade Revolutionary HBOOT 6.13.to BlackRose 2.02.0002 because of space issues with the ICS /system partition."

4.
prodlad said:
It says in the ROM thread "This ROM requires that you upgrade Revolutionary HBOOT 6.13.to BlackRose 2.02.0002 because of space issues with the ICS /system partition."
Click to expand...
Click to collapse
What version of HBOOT does your phone now show?
Did the flashing of thr lib.img in FASTBOOT USB mode show any errors?
What is the exact file name of the vivo_signed_WWE_4.10.405.1_ICS_SENSE36 rom?
Which version of ClockworkMod are you using?

Things have went from bad to worse. I uninstalled blackrose now I'm back to revolutionary hboot 1.13.0000. But now I cannot boot at all or even get to the white htc screen. I am stuck in bootloader and have lost recovery. Thereby my phone will not charge enough to accept a RRU. I tried to reflash recovery by fastboot but I keep getting a Remote:signature verify fail error Have I bricked my phone? :crying::crying::crying:

prodlad said:
Things have went from bad to worse. I uninstalled blackrose now I'm back to revolutionary hboot 1.13.0000. But now I cannot boot at all or even get to the white htc screen. I am stuck in bootloader and have lost recovery. Thereby my phone will not charge enough to accept a RRU. I tried to reflash recovery by fastboot but I keep getting a Remote:signature verify fail error Have I bricked my phone? :crying::crying::crying:
Click to expand...
Click to collapse
The only option you have at this point is to flash an official PG32IMG.zip file extracted from a RUU and copy it to your SD card. Then when you boot into bootloader it will find the file, flash it and that should get you going.
It sound like you need to use the 2.30.405.1 RUU from here:
http://www.filefactory.com/file/c0a...5AU_3805.06.03.03_M_release_199308_signed.exe

DUDE! This is no lie. You are a legend!!! That worked. I had myself prepared for buying a new phone!!!!!!!!!!! THANKS SO MUCH

[Q] Error: Unable to load "recovery_for_1.28"

hello guys, i really need help with this last few steps of rooting my phone.
from here,http://forum.xda-developers.com/showthread.php?t=1625841
in step 4. flash recovery downloaded aboved by using this command: fastboot flash recovery recovery_for_1.28
i get the error message as per the title
now before i tried to flash the recovery 1.28, i flashed another recovery from o' brian's. would this cause any problems that would lead to the error message above? i assumed that flashing a new recovery would just overwrite the old one.
when i flashed the recovery from o'brian's, it says waiting for device or something similar to that. then i proceeded to go into recovery as instructed. however, my phone simply turns off. when i have to turn it back on manually, nothing changed.
can any kind soul please enlighten me?

niekehecv said:
hello guys, i really need help with this last few steps of rooting my phone.
from here,http://forum.xda-developers.com/showthread.php?t=1625841
in step 4. flash recovery downloaded aboved by using this command: fastboot flash recovery recovery_for_1.28
i get the error message as per the title
now before i tried to flash the recovery 1.28, i flashed another recovery from o' brian's. would this cause any problems that would lead to the error message above? i assumed that flashing a new recovery would just overwrite the old one.
when i flashed the recovery from o'brian's, it says waiting for device or something similar to that. then i proceeded to go into recovery as instructed. however, my phone simply turns off. when i have to turn it back on manually, nothing changed.
can any kind soul please enlighten me?
Click to expand...
Click to collapse
Note what kind of hboot do you have, check your bootloader, if you have Hboot 1.25 then the functional and recommended Recovery for you is by Paul O'Brien, if you are on Hboot 1.28 then the recommended one is bue unlimited.io, if you are lazy to search for them, you have them included in this tool, i really can't understand why people doesn't use this, as it is free and keeps you away from lots of searching, many threads are old, many procedures are old so the guide recommended by me for everything is the guide by stona15, this one
Hope this helps

[Q] Assistance required with altered N1

I recently came across a modified Google Nexus One (N1) that has been experimented on. Upon boot up, I get a black screen with the HTC logo and four exclamation marks inside triangles in each of the four corners of the screen. As I attempted to enter hboot, I saw it has been replaced with Blackrose which leads me to believe it has been unlocked/rooted at some point in time. ( I am fairly new at this, but I lurk around the forum ). I tried hooking the N1 up to RUU to flash it back to a stock ROM, however that proved unsuccessful - the phone boots up to the above mentioned logo and stays that way. When I try to go to recovery/hboot, instead of the usual menu choices, there's only RUU as an option... Is the phone bricked, and if not, how can I revert it to a working state ?
I have attached pictures of what the boot screen looks like, as well as the recovery menu.
Thank you in advance.

It's in the middle of RUU mode, entered by executing "fastboot oem rebootRUU" (I might not remember it 100% correct, so check it with Google).
This should be enough for you to check with Google how you exit RUU mode.

The only way I see to exit this mode is if I flash it with something via fastboot ( since no recovery works, custom or stock ). What image file or zip do I flash it with, in order to revert it back to complete stock ( stock hboot, stock recovery, stock ROM ) - I want the phone like it was out of the box, so I can reroot it and unlock it myself.
I tried flashing it with PASSIMG_Passion_Google_WWE_3.13.1700.1_GRK39F_release_signed.zip through fastboot, for a moment it seemed to be going ok, then at the very end, while it was unpacking the [user data] image I get a partition update fail message 51, and after reboot - still the gray HTC letters and Blackrose instead of HBOOT.
Any suggestions ?

Short googling with the error would have revealed you the bad news.
Partition update fail means bad stuff - your NAND is malfunctioning, which equals a dead phone.

Have you tried to uninstall Blackrose?

tommert38 said:
Have you tried to uninstall Blackrose?
Click to expand...
Click to collapse
doesn't the phone need to be working in order for me to hook it up to Blackrose ? As of now, with this screen, the PC doesn't seem to detect it as a working phone, only fastboot. And Blackrose just says waiting for device... how do I uninstall it then?
I also tried this RUU: RUU_Passion_Vodafone_Generic_3.11.151.3_GRJ22_release, flashing the ROM to an image version 3.11.151.3, but at the end I get a message saying ERROR [110]: FILE OPEN ERROR. The RUU cannot open the requested files or the files are damaged. The RUU cannot continue with the update. Please get a complete RUU package and try again. Can someone please refer me to a working RUU package for the Nexus One, I am really scared of experimenting trying to find one by myself, seeing how the phone is already hanging in the balance, I would be thankful

You could try to flash this stock HBOOT, and if you have resized partitions I guess you could always use blackrose_manual_120421.zip to change to stock partition layout (145/95/196).
Edit: I've never flashed a HBOOT this way, and I never resized my partitions the manual way, so I would check the Blackrose for details. And I'm not responsible if you brick your phone
Edit2: I see you haven't got working recovery, so you should find a way to flash the HBOOT via fastboot. Maybe the Blackrose developer dla5244 can help you out (or Google).
Edit3: You could also try to flash this engineering HBOOT

tommert38 said:
You could try to flash this stock HBOOT, and if you have resized partitions I guess you could always use blackrose_manual_120421.zip to change to stock partition layout (145/95/196).
Edit: I've never flashed a HBOOT this way, and I never resized my partitions the manual way, so I would check the Blackrose for details. And I'm not responsible if you brick your phone
Edit2: I see you haven't got working recovery, so you should find a way to flash the HBOOT via fastboot. Maybe the Blackrose developer dla5244 can help you out (or Google).
Edit3: You could also try to flash this engineering HBOOT
Click to expand...
Click to collapse
Thanks for your time friend, I tried the above mentioned steps, it says OK all across the board in fastboot while I flash, but after I reboot it just goes back to the same screen, stuck in RUU. I did some digging around and found this which seems to be exactly my problem:
RUU PROBLEMS
"I tried using a RUU, but it failed, and now my phone is stuck on a black HTC Screen with /!\ In every corner!"
Possible Causes:
- You were S-OFF and you flashed a custom bootloader from alpharev
- You didn't check the MD5 Sums before proceeding, and the download may have been corrupted.
- You tried using the wrong RUU
Fixing your problem
Your phone is stuck in RUU mode. RUU mode is like fastboot mode, and can still receive fastboot commands, therefore it can be easily "fixed".
It helps to have a goldcard for this problem, so that you can use any RUU you want.
S-OFF
[STEP1]- download "Bravo Stock" from Alpharev
[STEP2]- download Android Flasher
[STEP3]- use android flasher to flash "Bravo Stock"
[STEP4]- run the RUU again and wait for it to finish
S-ON
If you're S-ON it eliminates the possibility of you having a custom bootloader, and the only possibility now is that the RUU was corrupted or you
used the wrong RUU for your device. Therefore, for this process you need a goldcard.
[STEP1]- Create the goldcard from the tutorial
[STEP1]- Use the WWE RUU
However, this is from a thread for the HTC Bravo. Anything similar for the N1 ?
Edit1: Could it be that the hboot partition was resized with Blackrose and therefore the RUU I tried to flash it with needs stock partition layout ?

Your partitions ARE resized. 2nd picture 2nd line JB-220/10/206. If it's b*tching about the resized partitions, then that would be about your cache partition (which is 85MB smaller than its stock size).
Edit: you should also try to wipe your partitions with fastboot, then flash the img's that are inside the passimg

what's the command line to wipe the partition ? fastboot format hboot/recovery/system ?

Dude, your Nexus One is dead, the internal NAND is damaged and therefore unrecoverable.
Sent from my Nexus S using Tapatalk 2

fastboot erase system/cache/userdata/boot

[Q] need some serious help with return to stock

hi all,
sorry to sound like a complete idiot in advance !
I have been trying for over a month now to find some way to return my phone to stock so I can get the new ota update but im just having no luck !
I have tried everything to unroot , relock boot loader, and return to stock, I can successfully unroot, successfully relock the boot loader but cannot update OTA everytime I download the ota and allow the phone to start update process the phone boots into bootlaoder and a new line appears in the normal messages **** security warning*** when this happens I loose recovery and the phone hasn't updated. I then have to re-unlock the bootloader to then flash a recovery.
I cant flash RUU as there isn't an RUU available for me, H3G_001 , I have tried the suggested CWM nandroid backup, but this fails half way through something to do with android_secure
I cant seem to get the phone to successfully grant s-off to try the change cid method, I have tried to do this using HTC one kit by hasoon but no luck,
if anyone could please help it would me much appreciated
regards
okz19

Probably you don't have the stock rom or the recovery, because the secure warning come out when you aren't fully stock..

Look on this site: http://www.htc1guru.com/downloads/stock-rom-downloads/
Mine One works now fine and i have update to the latest OTA.

Justin2003 said:
Look on this site: http://www.htc1guru.com/downloads/stock-rom-downloads/
Mine One works now fine and i have update to the latest OTA.
Click to expand...
Click to collapse
Is better link to XDA

still stuck!
hi all as you can probably tell form the age of this topic, I have been stuck for a while !!! (11 October ! )
I am still having problems trying to get the new update 2.24.771.3
my phone is carrier locked to three uk
it is unrooted
custom recovery cwm touch
bootloader unlocked / tampered
I understand I need stock recovery and to lock bootloader
I don't have stock rom
my problem is as follows, my phone has been telling me for atleast 4 months now that I have a software update, when I click it it restarts takes me to cwm recovery verifys install then gets stuck on cannot mount data ....
I understand I need to flash stock recovery, I have tried to do this using the "all in one kit" however when I click flash my own recovery, (phone reboots into bootloader) I then proceed to select the stock recovery.img the cmd box then hangs "waiting for device" I am then alerted by my computer that the usb device has malfunctioned. ( I am on windows 8 and have turned of signature verification)
I cannot use the supposed simple method of RUU as there isn't one available for my stupid network!!
I have tried to use a cwm recovery image, this usually starts then spits out android_secure is missing.
yes I do have a hammer ready to hit the phone with, but just before I do this is there ANYONE with any last tips to help me, because ive just about had enough with this stupid phone !
the phone has 24 hours left to live, can you save its life ?
thanks in advance for any help.

1. You cannot install an OTA with a custom recovery.
2. I've encountered a CWM bug having to do with .android_secure. There's a hidden folder in /sdcard that caused it, I don't remember whether this file is ".android_secure" or another. You can probably wipe the sdcard before restoring the backup. If that fails, you can probably manually restore the backup with ADB (this will be hard).
3. If you want to install the custom recovery, boot to the fastboot and use USB to install the recovery. Don't use a toolkit because they're useless when anything goes wrong.