i dont know exactly whats happened here, but i've tried to get my WFS sorted with a different rom than the carriers bloated version.
what i've done is updated hboot to 1.08.0099 and unlocked the boot loader sucessfully (hboot has *** UNLOCKED *** across the top; i used the HTCDEV.com process).
i believe i've got permanent root too.
when i attempt to flash CWM (via PG76IMG.zip), it appears to flash ok, but if i reboot the phone and try to access recovery, it just gets stuck on a white HTC screen.
i've redownloaded the CWM file to see if it's a corrupt download, but still the same problem.
CWM isnt a big issue, although it is nice to have.
however i also am unable to flash another rom either via the PG76IMG.zip SD method, or RUU.
i beleive i've done everything right, and i'm not entirely new to unlocking/rooting devices; only did my HTC Desire last week so the general process is still new in my head.
If your rooted install rom manager and flash recovery from there.
I had problems installing cwm from sd, so used the tool from here http://forum.xda-developers.com/showthread.php?t=1431969
previously was this one mediafire.com/?b0bsb4ms4lo714b
just plug the usb in sync and folow the instructions
Related
Hey, I updated my phone last night to CM 6.1.1 from Oxygen by AdamG using ROM Manager. I chose the options to wipe the data/cache and to install google apps. When that finished and my phone rebooted it now doesn't start anymore and just stays on the cyanogenmod loading screen and that loops around every minute or so. I've looked at the output of adb logcat and that shows some dalvik vm errors about not enough free space but I don't know what its refering to.
I tried going into recovery by holding power + back and then going to bootloader=>recovery but that just brings up a red triangle with an exclamation mark in.
I've also tried flashing the HTC Desire RUU (RUU_Bravo_Vodafone_UK_1.19.161.5_Radio_32.36.00.28 U_4.06.00.02_2_release_126338_signed.exe) to try get it working again, but that detects the phone (I started the RUU program while the phone was in fastboot.) and starts to flash the rom but fails.
I can't flash the recovery back with fastboot due to my device being S-ON (i assume thats the cause because i get signature verification fail)
How can I get this working again?
Thanks,
Jack.
Edit:
Bootloader Info
BRAVO PVT1 SHIP S-ON
HBOOT-0.80.0000
MICROP-031d
TOUCH PANEL-SYNT0101
RADIO-5.10.05.23
how was this device rooted?
flashing a rom cannot replace the recovery unless its an RUU but you said you had the exclamation mark which means unrevoked didnt replace the recovery
please tell me how this was rooted, did you use unrevoked?
Umm, it was with some goldcard method I think. It was ages ago when I first rooted it so I can't really remember what I did and i've done loads of ROM flashes since then and they've all been fine.
Heres some output from adb logcat while the phone is booting - pastebin.com/yfGJdRwe (can't post links yet
did you try and go into recovery before or after you ran the RUU?
us a gold card and try and do the pb99img.zip method
the RUU didn't install. it detected the version but wouldn't install.
Which pb99img.zip do I flash?
jacknetgb said:
the RUU didn't install. it detected the version but wouldn't install.
Which pb99img.zip do I flash?
Click to expand...
Click to collapse
Depends on the version of baserom you have now.
Safe bet is to go for an equal or higher version. If one isnt available, youd have to use goldcard and go for the latest WWE
How would I find the baserom version?
you would have hopefully made a note of it before rooting
if not, as Droidzone said, you would be best making a goldcard and flashing the latest WWE RUU from shipped roms.
well, acording to my experience .
your may got some problems in your ext portion of your SD card.
try to repair the ext portion with the recovery.
hope this would be helpful to you.
Umm, well no I didn't
Right so if i make a goldcard and use this RUU (http://forum.xda-developers.com/showthread.php?t=869048) and take the .zip from it.
That should work with no major complications?
yep, make a goldcard.
this is a direct link to the latest PB99IMG.zip you should use:
http://shipped-roms.com/download.ph...9.00.32U_5.11.05.27_release_159811_signed.zip
should work ok
Right its back to stock and im trying to root it again using unrevoked and everything is going fine but at the end it says "Internal Error: failed to unlock NAND flash?"
what version of unrevoked are you using?
make sure you do not have any form of adb tools running on the machine like droidexplorer etc etc
ok so i wanted to get a custom rom my desire hd 2.3.5
at start i have tryed the old way thats in the sticky but that was for 2.3.4 so that didnt work.
what did work was unlocking the bootloader via htc dev site. after that i was clueless.
I've found AAK to root my phone and downgrade so i had used that, but i forgot that the phone was unlocked and it said it had to be locked.
and now the phone is bricked i've tried all possible ways with wiping data and cache but it doesnt work.
i wanted to relock the bootloader with fastboot.
i had entered this command:
fastboot oem lock
but that gave this error
FAILED (status malformed (1 bytes))
so my phone hangs on the boot screen and i cant do anything?
can you guys please help me?
The fact you can get to the bootloader is a great sign, so don't worry! The only time you need to properly panic is when you can't get anything on the screen or even a charge light.
---Double check with someone else that this is correct, but I think this is what you need to do ---
Do you have a custom recovery (i.e clockworkmod)? Can you boot into recovery? Use the volume keys to select recovery, then press the power button. If you get options like "reboot now" and "install zip from sd card" then flash a rom like Android Revolution HD.
If you get a red triangle, find a zip you want to flash and name it "PD98IMG.zip" then put it on the root of the SD card. Reboot to bootloader and it should flash.
If you truly want to relock the bootloader, flash an RUU and it will restore you to stock.
Tamen said:
If you get a red triangle, find a zip you want to flash and name it "PD98IMG.zip" then put it on the root of the SD card. Reboot to bootloader and it should flash.
If you truly want to relock the bootloader, flash an RUU and it will restore you to stock.
Click to expand...
Click to collapse
Simply renaming a ROM PD98IMG.zip wont work it needs to be formatted in a certain way, but if the phone is S-OFF, which wasn't mentioned there are certainly PD98IMG's about for a variety of ROMs. But I suspect Tamens suggestion of flashing the appropriate RUU and starting from scratch is going to be quickest way to get sorted
I had this same problem with mine it got stuck trying to boot up but I had no boot loader or I couldn't get into recovery.so download a took called ANDROID FLASHER and reflash the radio ect.my desire hd is now fine.
Sent from my HTC Sensation XL with Beats Audio X315e using XDA App
well i have tried to flash the ruu but without succes.
ive loaded the PD98IMG.zip on the sd and let the bootloader use it. nothing happened.
also my phone is s-on and could not find a way to go to s-off in recovery mode or boatloader.
Down load the tool above Android flasher.from the tool u can enable fast boot ect from your PC and loads of other stuff.it is a very simple to use and it has loads of folders for recovery, boot loader ect let it do every thing for u.that was the only thing that worked for me
Sent from my HTC Sensation XL
I've tried it but it doesn't work because my phone is s-on...
the description of that utility said that s-off is essential
i am really running out of options..
in short my phone has a unlocked bootloader and after that i've used AAK.
the result is bricked phone with s-on and unlocked bootloader
Let me start by saying this forum has provided me with a ton of support in the past. There is so much information available here that I rarely have to start my own thread. Unfortunately, I have spent the past 18 hours looking for a solution to my current problem and have come up empty handed. I'm hoping some of you are savvy enough to help me out. I will try to provide as much information as possible to help diagnose the issue.
Device
HTC One M8
Carrier: AT&T
CID: CWS_001
Unlocked HTC Bootloader
S-On
I was previously running the stock ROM rooted (based on the above) simply to disable the AT&T bloatware. As of last week, AT&T began pushing the 4.4.4 update and I made the mistake of trying to install it not realizing my custom recovery (TWRP 2.7.1.0) would prevent it. Ever since this occurred, my phone has been doing strange things, i.e. random reboots and the "AT&T" logo in the upper left corner of the task bar would flash and disappear. It eventually got to the point where my phone was stuck in a constant boot loop and the only thing that would fix it was a factory reset from TWRP recovery. The phone would then act normal for about 24 hours and then the boot loop would start again.
I decided to try solving the issue by installing the GPE 4.4.3 ROM. I performed a complete wipe in TWRP (including system) and installed the GPE ROM via ADB/Fastboot. Everything was fine from this point and all apps/data synced after I logged into my Google account. Shortly after the phone booted, I was asked to install the GPE 4.4.4 update. It was at this point that I decided to load the stock recovery image so I could simply install the OTA update. Once again, no problems. Stock recovery flashed fine and I downloaded the 4.4.4 OTA update and rebooted the phone. The phone appeared to finish the install, but failed to boot. Now I cannot get past the HTC splash screen and I do not have a custom recovery.
The factory reset option from stock recovery does not help (still gets stuck at the splash screen) and for some reason my device is no longer recognized in Fastboot which prevents me from flashing a custom recovery. I thought it may have been a driver issue so I uninstalled and reinstalled HTC Sync Manager. I also tried manually uninstalling the drivers from the USB Root Hub, pulled the battery on my laptop, and allowed Windows 7 to auto update the drivers automatically. In each case, the drivers were successfully installed, but the phone is still not recognized in Fastboot (no devices listed). I even did a system restore on my laptop to a few days before the issue and the phone still isn't recognized by HTC Sync Manager or Fastboot.
The stock recovery bootloader displays the following information:
*** TAMPERED ***
*** UNLOCKED ***
M8_UL_CA PVT SHIP S-ON
HBOOT-3.18.0.0000
RADIO-INVALID_VER_INFO
OpenDSP-INVALID_VER_INFO
OS- (2.12..1700.1)
eMMC-boot 2048MB
Based on all of this, do I have any options or is my phone bricked?
1. Is there anything I can do so my device is recognized by ADB/Fastboot so I can flash a custom recovery?
2. Can I install a ROM from the SD card with the stock recovery? I currently have the GPE 4.4.3 ROM on my SD card, but the zip is not recognized by the stock recovery. Can I rename it to something else so it can be recognized and installed?
3. Because the phone is not recognized by Windows, I cannot use the RUU method. Are there any other ways to return my phone to stock without RUU?
Any help is greatly appreciated.
Swazi Samurai said:
Let me start by saying this forum has provided me with a ton of support in the past. There is so much information available here that I rarely have to start my own thread. Unfortunately, I have spent the past 18 hours looking for a solution to my current problem and have come up empty handed. I'm hoping some of you are savvy enough to help me out. I will try to provide as much information as possible to help diagnose the issue.
Device
HTC One M8
Carrier: AT&T
CID: CWS_001
Unlocked HTC Bootloader
S-On
I was previously running the stock ROM rooted (based on the above) simply to disable the AT&T bloatware. As of last week, AT&T began pushing the 4.4.4 update and I made the mistake of trying to install it not realizing my custom recovery (TWRP 2.7.1.0) would prevent it. Ever since this occurred, my phone has been doing strange things, i.e. random reboots and the "AT&T" logo in the upper left corner of the task bar would flash and disappear. It eventually got to the point where my phone was stuck in a constant boot loop and the only thing that would fix it was a factory reset from TWRP recovery. The phone would then act normal for about 24 hours and then the boot loop would start again.
I decided to try solving the issue by installing the GPE 4.4.3 ROM. I performed a complete wipe in TWRP (including system) and installed the GPE ROM via ADB/Fastboot. Everything was fine from this point and all apps/data synced after I logged into my Google account. Shortly after the phone booted, I was asked to install the GPE 4.4.4 update. It was at this point that I decided to load the stock recovery image so I could simply install the OTA update. Once again, no problems. Stock recovery flashed fine and I downloaded the 4.4.4 OTA update and rebooted the phone. The phone appeared to finish the install, but failed to boot. Now I cannot get past the HTC splash screen and I do not have a custom recovery.
The factory reset option from stock recovery does not help (still gets stuck at the splash screen) and for some reason my device is no longer recognized in Fastboot which prevents me from flashing a custom recovery. I thought it may have been a driver issue so I uninstalled and reinstalled HTC Sync Manager. I also tried manually uninstalling the drivers from the USB Root Hub, pulled the battery on my laptop, and allowed Windows 7 to auto update the drivers automatically. In each case, the drivers were successfully installed, but the phone is still not recognized in Fastboot (no devices listed). I even did a system restore on my laptop to a few days before the issue and the phone still isn't recognized by HTC Sync Manager or Fastboot.
The stock recovery bootloader displays the following information:
*** TAMPERED ***
*** UNLOCKED ***
M8_UL_CA PVT SHIP S-ON
HBOOT-3.18.0.0000
RADIO-INVALID_VER_INFO
OpenDSP-INVALID_VER_INFO
OS- (2.12..1700.1)
eMMC-boot 2048MB
Based on all of this, do I have any options or is my phone bricked?
1. Is there anything I can do so my device is recognized by ADB/Fastboot so I can flash a custom recovery?
2. Can I install a ROM from the SD card with the stock recovery? I currently have the GPE 4.4.3 ROM on my SD card, but the zip is not recognized by the stock recovery. Can I rename it to something else so it can be recognized and installed?
3. Because the phone is not recognized by Windows, I cannot use the RUU method. Are there any other ways to return my phone to stock without RUU?
Any help is greatly appreciated.
Click to expand...
Click to collapse
There is 2 methods to do an RUU. one is by putting the RUU on your sdcard and booting into the bootloader and waiting a few minutes then accepting the prompt to do it and 2 is the fastboot method. Since you have an SD card you could attempt the first one I listed. Make sure you don't change the name of the RUU and make sure you get the proper one for your phone.
S1L3nTShaDoWz said:
There is 2 methods to do an RUU. one is by putting the RUU on your sdcard and booting into the bootloader and waiting a few minutes then accepting the prompt to do it and 2 is the fastboot method. Since you have an SD card you could attempt the first one I listed. Make sure you don't change the name of the RUU and make sure you get the proper one for your phone.
Click to expand...
Click to collapse
Don't you have to be S-OFF or have a locked bootloader to run a RUU? I am unable to achieve either of those since my phone is not recognized by by ADB/Fastboot.
Also, because my most recent functioning ROM was GPE 4.4.3, would I still be able to run the stock AT&T RUU? I thought the partitions were different? I have the GPE RUU as well, but I don't think I can run that either without changing my CID and locking my bootloader.
Swazi Samurai said:
Don't you have to be S-OFF or have a locked bootloader to run a RUU? I am unable to achieve either of those since my phone is not recognized by by ADB/Fastboot.
Also, because my most recent functioning ROM was GPE 4.4.3, would I still be able to run the stock AT&T RUU? I thought the partitions were different? I have the GPE RUU as well, but I don't think I can run that either without changing my CID and locking my bootloader.
Click to expand...
Click to collapse
S-OFF not so sure about, locked bootloader, no you can have it unlocked. But you can try it anyways, the SD card method.
Yes you would be able to run it, I'm quite sure all you did was flash a GPE ROM. I believe all flashing the ROM does is give you a GPE ROM where as the GPE RUU would change all that and give you GPE phones firmware too.
On the off hand you did do a GPE RUU then I'm not sure.
S1L3nTShaDoWz said:
S-OFF not so sure about, locked bootloader, no you can have it unlocked. But you can try it anyways, the SD card method.
Yes you would be able to run it, I'm quite sure all you did was flash a GPE ROM. I believe all flashing the ROM does is give you a GPE ROM where as the GPE RUU would change all that and give you GPE phones firmware too.
On the off hand you did do a GPE RUU then I'm not sure.
Click to expand...
Click to collapse
I have heard it has to be one or the other. If S-OFF, the bootloader can be unlocked. If S-ON, the bootloader has to be locked.
I did not run the GPE RUU originally; I installed the ROM through custom recovery. I'm assuming that is a good thing based on your feedback.
Regardless, I haven't been able to try the SD method because the zip file I extracted from the RUU exe will not transfer to my SD card. I also tried downloading another user's bootable version and it won't transfer either. I have copied many other files to and from my SD card (even larger file sizes) without any issues. I have no clue what is going on now...
Swazi Samurai said:
I have heard it has to be one or the other. If S-OFF, the bootloader can be unlocked. If S-ON, the bootloader has to be locked.
I did not run the GPE RUU originally; I installed the ROM through custom recovery. I'm assuming that is a good thing based on your feedback.
Regardless, I haven't been able to try the SD method because the zip file I extracted from the RUU exe will not transfer to my SD card. I also tried downloading another user's bootable version and it won't transfer either. I have copied many other files to and from my SD card (even larger file sizes) without any issues. I have no clue what is going on now...
Click to expand...
Click to collapse
I formatted my SD card and was finally able to transfer the RUU. The bootloader begins to run the 0P6BIMG file, but it fails right after it starts parsing. I tried running it several times and the results were the same.
I really wish I could get ADB to recognize my phone so I can flash a custom recovery... When I plug my phone into a USB port, my computer makes a noise, the phone says "USB" next to Fastboot, and HTC Sync Manager begins to load. When HTC Sync Manager comes up, it says "HTC Sync Manager couldn't connect to your phone." Windows Device Manager also does not have anything listed for an Android device.
I've noticed when the phone is not powered on and simply charging from the USB port, an "HTC MTP Device" driver tries to install, but fails. Could this be the problem? I've tried plugging the phone into 3 different computers and they all get the MTP failure.
If you are coming from a GSM variant things get a little bit more complicated to install a GPE RUU, as the GPE HBoot is different from the GSM one and partition sizes are as well.
You have to be S-Off to install the proper firmware and prior to doing this, change the CID as well as the MID to a GPE one.
There is a full guide on this forum to convert your M8 from GSM to GPE, bit as I'm on the train at the moment I can't provide you the link right away.
Sent from my HTC One_M8 using XDA Free mobile app
HTCNerdYoda said:
If you are coming from a GSM variant things get a little bit more complicated to install a GPE RUU, as the GPE HBoot is different from the GSM one and partition sizes are as well.
You have to be S-Off to install the proper firmware and prior to doing this, change the CID as well as the MID to a GPE one.
There is a full guide on this forum to convert your M8 from GSM to GPE, bit as I'm on the train at the moment I can't provide you the link right away.
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
I'm not specifically trying to install the GPE RUU at the moment. I had the stock GSM recovery installed based on my original CID and I'm trying to load the associated RUU.
I originally loaded GPE 4.4.3 with TWRP and downloaded the 4.4.4 update OTA from Google. Before restarting my phone and installing the update, I flashed the stock GSM recovery for CID CWS_001. This may have been what caused the issue initially when the phone tried to apply the update if it was looking for a GPE recovery.
I know I cannot install the GPE RUU because I'm S-ON and ADB does not recognize my device so I cannot change the MID or CID. At this point, I'm really just trying to get back to stock so I can start fresh.
Is it possible that when the 4.4.4 update tried to run, it associated my recovery with GPE and now that's why it will not install the stock RUU due to a mismatch? I'm really just guessing at this point.
Look here at post #28 and #30. http://forum.xda-developers.com/showthread.php?t=2717928&page=3 . Download that .zip template
I think you can put the TWRP recovery.img (it has to be renamed to recovery.img) inside the zip as directed, put it on the SD card and let the bootloader automatically detaect and flash it. Once its completed you would have to power down and remove it from the SD card otherwise it would try to update again next time you go into the bootloader. That should load a recovery from which you can flash a ROM.
3484jacks said:
Look here at post #28 and #30. http://forum.xda-developers.com/showthread.php?t=2717928&page=3 . Download that .zip template
I think you can put the TWRP recovery.img (it has to be renamed to recovery.img) inside the zip as directed, put it on the SD card and let the bootloader automatically detaect and flash it. Once its completed you would have to power down and remove it from the SD card otherwise it would try to update again next time you go into the bootloader. That should load a recovery from which you can flash a ROM.
Click to expand...
Click to collapse
I'll give that a try and report back. Thanks for the input.
3484jacks said:
Look here at post #28 and #30. http://forum.xda-developers.com/showthread.php?t=2717928&page=3 . Download that .zip template
I think you can put the TWRP recovery.img (it has to be renamed to recovery.img) inside the zip as directed, put it on the SD card and let the bootloader automatically detaect and flash it. Once its completed you would have to power down and remove it from the SD card otherwise it would try to update again next time you go into the bootloader. That should load a recovery from which you can flash a ROM.
Click to expand...
Click to collapse
You are the freakin man!!! I edited the template from the post you suggested, added my MID/CID, and packaged it with the TWRP image. Booted right from the SD and I now have custom recovery! I wish I could buy you a beer!
No problem mate. Glad I could help. :thumbup::thumbup::beer:
Sent from my HTC One_M8 using XDA Free mobile app
Hello, I need some serious help with my friends HTC m8.
We unlocked the phone of my friend and wanted to install a custom recovery. After installing TWRP latest version everything still worked fine, the device still booted normally. After that we tried to install the GPE ROM of the M8 through TWRP without realizing the phone isn't s-off. By itself the installation failed and we just rebooted the device and saw that it wouldn't boot anymore, it was stuck on the boot screen, even though it aborted the installation because the MD5 numbers weren't matching.
Now we don't know what to do, the M8 won't boot and is s-on. We tried downloading: http://forum.xda-developers.com/htc-one-m8/general/htc-one-m8-european-signed-ruu-0p6bimg-t2911563 the stock file and pushing the update by renaming the zip file to 0P6BIMG.zip but gave us the error "halted due to large image update fail". So this didn't help us either
CiD of the device = HTC_E11
After all we're just idiots by not researching enough before doing anything. Hopefully some experienced people can help us out!
Thanks in advance,
Pepie.
Pepie said:
Hello, I need some serious help with my friends HTC m8.
We unlocked the phone of my friend and wanted to install a custom recovery. After installing TWRP latest version everything still worked fine, the device still booted normally. After that we tried to install the GPE ROM of the M8 through TWRP without realizing the phone isn't s-off. By itself the installation failed and we just rebooted the device and saw that it wouldn't boot anymore, it was stuck on the boot screen, even though it aborted the installation because the MD5 numbers weren't matching.
Now we don't know what to do, the M8 won't boot and is s-on. We tried downloading: http://forum.xda-developers.com/htc-one-m8/general/htc-one-m8-european-signed-ruu-0p6bimg-t2911563 the stock file and pushing the update by renaming the zip file to 0P6BIMG.zip but gave us the error "halted due to large image update fail". So this didn't help us either
CiD of the device = HTC_E11
After all we're just idiots by not researching enough before doing anything. Hopefully some experienced people can help us out!
Thanks in advance,
Pepie.
Click to expand...
Click to collapse
Firstly, I don't think it has anything to do with "not researching" enough but more to do with NOT reading what you "researched" already. You post a link to the RUU .zip that you wanted to use and obviously haven't picked up on the fact that the OP in that thread specifically stated: S-Off is Required with Eurpean CID right after admitting that you are NOT S-OFF.
Secondly: You don't need S-OFF to flash a custom ROM. You just need an unlocked bootloader and a custom recovery, that's it. You'll need S-OFF to fully convert the device to GPE though, as it makes changes to partition sizes.
Try to get back into bootloader again. Hold Volume UP + Power for 10 seconds the moment the feel a vibration and/or screen goes dark immediately hold Power + Volume Down to enter bootloader. You should still have TWRP on the device you didn't mention anything about taking it off. Head over to the RUUs, OTAs, Stock TWRP Backups, Firmware & More Collection grab a nandroid backup for your device. Unpack it and place it inside the TWRP backup folder on your device. If you don't have one, make a backup of just "Boot" it'll then create the path for you.
Once done, restore the nandroid. That'll take you back to "stock" then.
Else, just place a custom ROM on the SDcard enter TWRP again and try to flash a custom ROM again.
What ROM did you try to flash? Perhaps give the link...
Oh and remove the 0P6BIMG.zip from the SDCard else it'll just keep on trying to flash it through HBoot.
Hai,
long time lurker here...
I've managed to get my hands on a Wildfire S, yet there are so many anomalies with it that now I'm turning to the collective...
Problem
Phone's seem only to be soft-bricked/non bricked, there is hboot, htc logo, but no OS and seemingly no bootloader either. Managed to charge its battery to the minimal level (around 3.86+) and can now freely enter into hboot.
I wanted to just install a quick recovery, some stable custom rom...now get very interesting
MARVEL PVT SHIP S-OFF RL
HBOOT-0.90.0000 (!)
RADIO.7.46.35.08
Apr 8 2011 etc
-When trying to install recovery through fastboot, it gives the error "NOT ALLOWED". Tried cwmod and twrp and a custom zip, no luck
-This made me think that loaders locked too, so I tried HTCDEV, but was unable to get the indentifier token and the hboot update was unsuccessful (written in several ways, just to be sure). ERROR: Command error!!!
-Also tried searching for custom firmware and bootloader unlock methods, but nearly all the links are offline by now...
...the phone seem to be unlocked and rooted, yet the hboot is ancient, there is no bootloader (it just shows the htc screen upon restart) and there is seemingly no way for me alone to find a solution to install anything
Any leads for the bootloader to work would be very much appreciated!!!! ty
UPDATE: solved possibly by trial and error:
1) try out
https://drive.google.c om/folderview?id=0B5cR4v1TTgVVOVRad0dNTERkcFU&usp= sharing these bootloaders through hboot as SD-card auto-install (fat32). Each time you update check whether the hboot FW and/or the logo screen is updated. Thats the one to stick with
2) Install
https://drive.google.co m/file/d/0B5cR4v1TTgVVOUppMVc4eTk1X0E/view?usp=sharing this all-in-one rom package through hboot/SDcard. Every time the filename must be "PG76IMG.ZIP" (its possible that this is all what you need as its installs the stock recovery along with the stock 2.3 rom
3) from there you can just install CWmod or TWRP via apk/market -> flash preferred custom