Related
I don't know what I did wrong. After downloading a moddet statusbar vor Oxygen 0.2 I wanted to reboot into recovery and it took me very long. It freezed. After pulling the battery and setting it back in and pushing the power button my desire vibrated in 3 short intervals.
Since that I can't boot into the os or into recovery. Only thing that is working is the bootloader and the fastboot.
First thing I tryed is to flash (with fastboot) a new recovery but nothing changed. still it freezes at the splash screen.
I also downloaded official o2 rom from their homepage. But I think they want me to run the .exe while in android. A error comes up and tells me that it can't find a phone.
official htc roms don't work too. one told me that I'm not allowed to install this particular rom and an other official rom keeps exiting with error code: 170 telling me that the usb connection couldn't be established or something like this.
is there something else I can try?
I googled and searched the board. Tryed to boot into recovery without microSD card too but still no success.
help
Unpack the Rom and get the image out of the file...
Rename it to pb99img.zip dump only that on the root of your sdcard and boot into hboot .
T i d y .
Or just look on shiped roms for an 02 pb99img.zip and download then rename
T i d y .
Thank you so much. I already tryed this with 3 different pb99img images and had always the same error (CID). One of them was a o2 uk rom. So I gave up on trying it this way. But I didn't know that it could be extracted from every rom.
Now I think every thing is working again. Thank you.
Oh well ... I destroyed it again. Like I said I was able to install official o2 rom and everything was working again. After that I wanted to root it with unrevoked 3.21 but it freezed at "waiting for reboot". So I had to pull the battery once again.
But now I can't even enter bootloader. Only a screen pops up with htc in the middle and with four ! in every corner of the display.
Tryed to install official o2 rom again. It can find it and starts installing but at the end of the installation it stops with an error:
error [110]: error while opening data. Tryed it 3 times but always the same.
This might work for you
WAIT, BEFORE YOU START, CREATE A GOLDCARD. IT IS VERY NECESSARY. THINGS WILL GO WRONG IF YOU DONT.
EDIT: YOU MUST BE ABLE TO BOOT GO TO THE BOOTLOADER MENU.
Firstly, download this file. http://dl.dropbox.com/u/13240777/Desire Downgrade.ZIP
Extract the files.
Run the win-down.bat file.
Follow on screen instructions.
After the process is completed, Head to the root of your SD card and check if there is a file named P99***IMG (FORGOT THE EXACT NAME BUT IT SHOULD BE SOMETHING LIKE THIS) there should be one.
Secondly, disconnect your phone and turn it off.
After that boot up your phone while pressing the volume down button and the power button.
The bootloader should be checking for files after awhile and once it found the file that is supposed to be in the root of your sd card, press the volume up button (NOT EXACTLY SURE, SHOULD BE THE ONE THAT SAYS YES AND CONTINUE)
It should be writing files to your phone. and replaces everything. E.G: HBOOT, RECOVERY,RADIO and such.
It should be writing files successfully and then it would ask you to reboot. Continue with the reboot and you should be having your Desire back to stock. Perfect.
PLEASE KEEP IN MIND THAT THERE ARE RISKS INVOLVED LIKE FAILURE OF WRITING TO THE HBOOT. PLEASE REMEMBER TO FOLLOW INSTRUCTIONS. MAINLY, DO NOT BLAME ME FOR ANYTHING THAT GOES WRONG.
FINALLY, YOU SHOULD BE READING EVERYTHING UP TO HERE AND THAT YOU MUST HAVE A GOLDCARD (A GOLD SD CARD)
Hope this helps you and please ask if you have further questions. PM me if the questions cannot be answered here. Good Luck
You have to have a working Goldcard and be able to access HBOOT to do the above
Nevermind.
I send it to o2. Since I was able to install the official RUU once I think they will take care of it.
What happend is:
For some reason I wasn't able to boot my phone. Recovery wasn't working too. Only thing that was working was Bootloader and Fastboot.
Just to sum up what I tryed:
Installing new recovery didn't help. I was able to install official o2 RUU and everything was working. But I lost my root. I think it had HBoot 0.930001
So I wanted to root it again with unrevoked 3.21
It started well and rebootet one or two times. But at the thirt reboot attempt it juft freezed and nothing was happening. I don't know what I did wrong?
is unrevoked 3.21 really able to root a phone with hboot 0.930001?
As I said ... if faild and after that I couldn't even enter Bootloader or Fastboot.
So I send it to o2 and hope they fix it.
But now I am really scared to root it again. If it fails again ... what will they think if I send it after 3 days again to them.
Peikko said:
Nevermind.
I send it to o2. Since I was able to install the official RUU once I think they will take care of it.
What happend is:
For some reason I wasn't able to boot my phone. Recovery wasn't working too. Only thing that was working was Bootloader and Fastboot.
Just to sum up what I tryed:
Installing new recovery didn't help. I was able to install official o2 RUU and everything was working. But I lost my root. I think it had HBoot 0.930001
So I wanted to root it again with unrevoked 3.21
It started well and rebootet one or two times. But at the thirt reboot attempt it juft freezed and nothing was happening. I don't know what I did wrong?
is unrevoked 3.21 really able to root a phone with hboot 0.930001?
As I said ... if faild and after that I couldn't even enter Bootloader or Fastboot.
So I send it to o2 and hope they fix it.
But now I am really scared to root it again. If it fails again ... what will they think if I send it after 3 days again to them.
Click to expand...
Click to collapse
Well lad you had USB brick, easy to fix.There is a thread on this thing.
I am having similar problem described.
Currently I can get into Fastboot, and have tried reflashing recovery but still boot loop.
What should I do now?
please help my desire break
my desire wont work into recovery and os only work in fastboot and hboot.
i am root desire and install custom rom arabic after flash not boot up,usb work into only charge, but not work lcd
i am install recovery clock work mod slcd on recovery clockwork mod 2.5.0.7 and break recovery.
now not work os and recovery.
please help me please.
BRAVO PVT3 SHIP S-ON
Hboot-0.93.0001
TOUCH PANEL-SYNT0101
RADIO-5.09.05.30-2
Aug 10 2010,17:52:52
please help me.
Hi,
I have the same problem and getting pretty desperate now.
Only FASTBOOT and BOOTLOADER works.
I have clockwork recovery installed but it wont boot into recovery. It just gets stuck on the white boot screen.
I can't copy PB99IMG.zip or any other zip file because I can't access the phone through usb. I tried:
adb push PBIMG99.zip /
error: device not found
Is my phone useless now? As good as a brick?
try pack it in some tolietpaper put it in to the freezer fore 5 min an try again
jalal.arkat said:
my desire wont work into recovery and os only work in fastboot and hboot.
i am root desire and install custom rom arabic after flash not boot up,usb work into only charge, but not work lcd
i am install recovery clock work mod slcd on recovery clockwork mod 2.5.0.7 and break recovery.
now not work os and recovery.
please help me please.
BRAVO PVT3 SHIP S-ON
Hboot-0.93.0001
TOUCH PANEL-SYNT0101
RADIO-5.09.05.30-2
Aug 10 2010,17:52:52
please help me.
Click to expand...
Click to collapse
janielsen's idea seems crazy but give it a try..
put it in the freezer for few minutes then take it out
and then try to get into recovery mode..
you'll be able to do that
if you see a triangle with ! mark at the center that means it's a serious hardware issue and we can't do anything about that you have to send it to htc service center
Ha, funnily enough I did try the freezer thing but that didn't work either. What did work was booting into fast boot, connecting the usb and flashing with an official RUU in windows.
The phone is still stuffed!!!
It now has an official htc rom, no root, no mods, nothing... just stock!
But whenever it has to do a bit more processing like viewing a complex web page with flash, playing a game, downloading from the market it resets itself. Why?
I am starting to think it's a hardware problem but I need confirmation. I tried different roms but I get the same result. Has anyone has the same experience???
well i have sent my phone in fore repare the trick whit the freezer is only so u can unroot it so they cant see that it has bien rooted
the problem is that the cpu is getting to hot
Hey janielsen,
I had a feeling it was a hardware problem, because it only resets when it's doing a lot of processing.
But what can they do? Replace the CPU? Did they say how much it costs?
I bought my phone second hand so I don't have warranty.
yes u have warrenty because htc can see by the imei when the garanty is running out
they will replace the mainboard
FreshNClean said:
Hey janielsen,
I had a feeling it was a hardware problem, because it only resets when it's doing a lot of processing.
But what can they do? Replace the CPU? Did they say how much it costs?
I bought my phone second hand so I don't have warranty.
Click to expand...
Click to collapse
i thit also buy my second hand an didtn have the warrantypapper
but they said that i still have the 2 year warrenty so my is in fore repair
i shut get it back this week
Hello everybody..
As the title says, I'm stuck on this screen.
I am S-OFF, I was using CM7 with CM7 r2 partition table, and I used the latest official RUU to come back to Sense properly.
Unfortunately, everytime I used the RUU, it wasn't working. Then, I tried to plug out my phone and try again, as advised in some topics, and the RUU went well until the end. A triangle appeared next to the progress bar. After this, my phone was not working.
I turned it off by removing the battery and turned it on just after, and when I reboot, I arrive on the black screen with 4 triangles in each corner. I can't do anything. When I try to relaunch the RUU, everything goes well, except one thing.
At the end, when I unplug the phone, I can see that the 9 lines are green, except the line 6 "SYSTEM" where it is written "Fail-PU" instead of "OK"...
What can I do to save my phone ?
I'm not used tu using adb or the SDK, so I'm not familiar with all of this stuff..
Thank you by advance everybody...
this happened because you were using the cm7 hboot which has a system partition that is too small for the RUU.
when you plug in via USB it should be in RUU mode but still receives fastboot commands.
Go to the alpharev website and flash the "bravo_stock" hboot and try the RUU again.
***EDIT: NEVER MIND, JUST FOLLOW WHAT I WROTE BELOW***
Your hboot is too small for sense ROM's which is why it's failing.
My advice is to get learning fastboot commands!
The screen with the red triangles is basically the phone in fastboot mode with an HTC warning (some say your phone is bricked at this but it is not)
If you ran the official HTC gingerbread update (like I mistakenly did) you will now have an updated hboot with s-on.
The new revolutionary.ie website will help you s-off it again.
Then replace hboot with one suitable for sense roms.
I've only done the above once two weeks so do your research in case I've got bits wrong!
actually I just realised... since you're S-OFF you can just flash recovery..
Follow these instructions:
1. Download recovery, rename it to "recovery.img" and place it in c:\ (MD5: 6CBF5C129739F3DE0948EA6F3D274CEA)
2. unzip the attached file (fastboot.exe) into c:\
3. open command prompt (start menu, accessories)
4. type:
Code:
cd\
fastboot flash recovery recovery.img
fastboot oem gencheckpt
5. By typing the commands above, you will have flashed recovery and booted into recovery. Now just flash a ROM.
Hello,
I have the same problem as Mayaku in the 1st post and I followed bortak's instructions and... I was able to flash recovery, boot into recovery, flash rom, but after reboot black screen with triangles appeared.
What else can I do to make it work?
cielik said:
Hello,
I have the same problem as Mayaku in the 1st post and I followed bortak's instructions and... I was able to flash recovery, boot into recovery, flash rom, but after reboot black screen with triangles appeared.
What else can I do to make it work?
Click to expand...
Click to collapse
What rom did you flash? What Hboot table have you got? Were you using an RUU that got you to sthis screen?
Please provide details.
CM7 Nighgtly #183
Alpharev CM7 r2 table
I used RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed.exe
I even tried to restore nand backup that appeared OK but after reboot the same black screen with htc logo and triangles.
other details:
PVT1
HBOOT-6.93.1002
RADIO-5.11.05.27
cielik said:
CM7 Nighgtly #183
Alpharev CM7 r2 table
I used RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed.exe
I even tried to restore nand backup that appeared OK but after reboot the same black screen with htc logo and triangles.
other details:
PVT1
HBOOT-6.93.1002
RADIO-5.11.05.27
Click to expand...
Click to collapse
this is the millionth time is say it: read aplharev.nl
u need to flash the downgrader hboot, after u can flash the ruu
please tell me why u dont read that? u downloaded the cmr2 without read the rest of the alpharev site? can u explain?
I guess maybe I didn't fully understood that/bad english... I think...
cielik said:
I guess maybe I didn't fully understood that/bad english... I think...
Click to expand...
Click to collapse
u need to flash the downgrader hboot, after u can flash the ruu
try to read it again
good luck
doin' it right now. Many thanks, silly me ;p
First of all, hello to all forum members!
I had not been particularly active here in the forum,
but I read a lot here and build some knowledge.
so far I have solved all my problems due to browse and read.
But now I am facing a problem, where I need help.
I got a desire from a friend with wrong nexus one blackrose hboot.
I managed to install alpharev hboot on it, but its not booting the rom, neither the recovery.
I decided to get a ruu on it, to reflash boot, system, recovery, etc.
After i did:
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip <rom.zip>
the phone is stuck in fastboot RUU mode. No matter if I pull the battery and power on with vol-, vol+ or back, the fastboot RUU mode starts (Black screen with htc logo in the middle and 4 exclamation marks in the corners).
What Ive done so far:
Tried different RUUs(Europe, WWE) via fastboot. Most of them fail while writing radio image.
Tried to flash the radio image via fastboot. Most of them stuck while writing.
Asked a friend with exactly matching hardware to send me his working nand backup, his hboot is CM7 r2, so I flashed it
to match his nand backup.
I flashed his boot/recovery/system/cache and the latest radio, matching the nand backup.
The latest radio was flashed successfully.
The recovery in his nand backup was 4EXT Touch 1.0.0.3
So, after flashing boot, recovery, system, cache and even misc and userdata (AND erasing them prior on second try), the behaviour stays the same, the phone wont boot the rom or recovery and no matter what buttons I press on power on, it boots at fastboot RUU mode.
I tried
Code:
fastboot oem boot
, but that keeps stucking in the white htc splash1
If I plug in the usb cable and pull it out again, I see the hboot infos:
AlphaRev CM7 r2
BRAVO PVT1 SHIP S-OFF
HBOOT-6.92.1002
MICROP-031d
TOUCH PANEL-SYNT0101
RADIO-5.17.05.23
<date>
RUU
After a lot of research, Ive found several opinions:
-its a brick (sure it is ;D)
-its a radio brick (ive sucessfully flashed the newest radio, so I doubt it)
Almost all users wo tried it hardly, and havent given up after the second try,
recovered their phone from this fastboot RUU mode.
I can run all fastboot extended commands, and flash RUUs over it.
So: what have I done wrong? Is there anything missing?
Can someone who knows what he says please take a look over it?
Thank you really much
criestr
After "a lot" of research you still haven't looked at my guide, well done.
Sure Ive looked at your guide,
I work with linux, and I hate flashing tools.
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
Click to expand...
Click to collapse
Is it any difference to use
Code:
fastboot flash hboot bravo_alphaspl.img
instead of using Android Flasher?
I dont think so, and Ive already done the steps in your guide, except using Android Flasher to flash the AlphaRev stock version.
Or is there another point in your guide that Im missing?
If so, then I am sorry for wasting your time.
I know, I am "new" here, so thats the standard answer for all newbs from you.
Thats ok. But Ive fixed a lot of phones without open even one thread, just with hours of research. But after google search for about 8 hours, several tries and following several guides and tips I didnt find an answer yet.
New update: Ive managed to push and boot the 4EXT Recovery image.
Fair enough, but the guide was meant to be made as easy to use as possible.
All you had to do was flash the stock hboot, or the downgrader, and then try a RUU.
The reason for it being stuck, is because alpharev hboots have write protection (meaning they won't be overwritten until you use the downgrader), and since you had the cm7r2 partition flashed, there was not enough space in /system for the stock ROM.
Hi again,
thanks for your answer.
I had the right stock hboot whilst flashing the RUU, so that wasnt the problem.
The RUU always failed to write the radio. A few hours ago i figured out that
the problem was because of a faulty battery. I changed the battery, loaded it
half an hour, and voila! the RUU was running quite fine.
The stock rom wasnt booting yet, but from then it was possible to go into the HBOOT/Fastboot, so it was making progress ;D
After another research I found out that my misc partition was screwed, maybe because the blackrose hboot, maybe because of the pre-owner.
Fixed the misc partition with cid, kernel commandlines & rom version.
After that I wiped cache and data, and did fastboot oem boot.
The rom was booting, but did random reboots/crashes after about 3-5 mins.
After 3 or 4 reboots the phone is now stuck at htc splash1, and isnt booting anymore.
For now I will try to flash the nand backup again, see if that works out.
Anyone has an better idea?
Thanks alot
criestr
New update:
The phone switched randomly between bootable and non-bootable bootloop/stuck in splash1.
I tried different radios, different boot & system.img from RUUs.
I can flash a new recovery, tried 4 different ones, none of them is booting,
not over hboot->recovery and also not over
Code:
fastboot oem gencheckpt
.
The only thing that worked was to erase cache and immediatly do
Code:
fastboot boot recovery.img
,
so after the stock rom randomly reboots, I decided to install a custom rom for CM7 r2 hboot. So I flashed the CM7 r2 hboot again, erased cache, booted the recovery and flashed rom.
The rom was booting! But again, after fiddling with flashing a new recovery with 4EXT Updater, the rom rebooted into splash1 and stuck there.
After this first time, it has yet never rebooted again. So I twist my fingers that it was a custom rom bug on first boot.
Flashing the recovery via 4EXT Updater worked for me, despite of none of the recoverys flashed via fastboot had booted before.
Anyway, thanks for the help.
Hopefully it helps someone with the same problem,
but I doubt there are many people dumb enough to flash blackrose hboot on a desire
Cheers
criestr
I had a similar problem with my old Magic. I have Desire now but never had that problem. I hope not.
Anyways, the way I solved it was to flash the right radio.img. I supposed you can try to fastboot flash radio radio.img. Make sure you use the right radio.img. That is what I did if I recall correctly and it worked for me on Magic. I don't know if it is will work on Desire that way.
The other thing is when Ruu failed at radio, I think it is because the lower version of radio.
I hope this helps.
Try it and let me know.
bortak said:
After "a lot" of research you still haven't looked at my guide, well done.
Click to expand...
Click to collapse
link please
I hope someone in this community is able to help. I've already been scouring Google this morning for people with a similar issue and haven't been successful in getting my phone to come back so I suspect there may be a hardware issue.
Here's a summary of the problem:
My phone shutdown this morning while I was listening to a podcast. It got stuck in a boot loop at the splash screen, constantly rebooting itself. A battery pull would not solve the problem. I was able to get it into HBOOT (version 0.92) but when I tried going into recovery from there, It got stuck on the splash screen (no looping). Before all this I had been running Nils Business Gingersense for quite a while and things were working fine, in case anyone needs that detail.
After failing to boot to recovery, here are some of the things I have tried to fix this issue:
1. Factory reset in HBOOT
2. Flashed RUU 2.2 and then tried RUU 2.3.4 through HBOOT. Though neither of these would get the phone to come up, the splash screen reboots stopped and the phone just freezes in splash screen now (over 30 minutes with no change).
3. Tried to reflash CWM 5.0.2.0 through Fastboot. Although the phone is recognized by 'fastboot device', it says 'remote: not allowed' when try to flash the .IMG file.
4. Tried to flash an older CWM recovery from when I originally rooted my phone --same 'not allowed' error
5. Ran the official RUU for Froyo on my PC and it looked promising but I never got past the splash screen afterward a reboot.
6. I don't know a ton about ADB but ADB does not recognize my device even though Fastboot does.
At this point I'm not sure what else to try. It seems promising that I can get into HBOOT and that Fastboot will recognize my phone but what can I do with that now?
Thanks for any ideas you might have.
Have you tried flashing cwm thru hboot as a PB31IMG.zip? http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip. If that dosent work you could try to update hboot to 1.02 and htcdev unlock it. This will allow extended fastboot commands. You can do this on the htcdev website. Or you could downgrade hboot to the 0.77 engineering bootloader http://dinc.does-it.net/Hboots/ENG_Hboot_0.77/PB31IMG.zip which basicly does the same thing, and might be a better option than upgrading. You are s-off right?
Yes, I still have S-OFF. I did try flashing several recoveries through hboot and they all acted like they updated fine but I wasn't able to boot into any of them because I kept getting frozen at the white screen after choosing recovery from hboot. I will try another hboot and see if that makes any difference. Thanks.
Cmlusco, I tried the CWM version you posted with hboot .92 and .77 but had no luck. I also tried walking through the hboot upgrade steps on the htcdev site but I couldn't get the RUU exe to find my phone. This is odd because an older RUU found the phone just fine earlier today.
SOLVED. THE PHONE IS BROKEN AKA HARDWARE FAILURE
Hi,
My old Desire had been sitting in my desk for about a year since i bought myself a Galaxy S2. Today, I decided to try it out. Charged the battery first and then tried to boot it. Well, I got stuck in the splash screen. The phone had been working normally the last time i used it (maybe 6 months ago?) so i thought it was weird. Then I tried to boot it into recovery, and got again stuck in the splash screen. HBOOT came up normally but after pressing the recovery button the phone just made the boot vibration multiple times and then was stuck in the splash screen.
What I have:
- Alpharev S-OFF HBOOT: bravo_alphaspl-oxygenr2.img
- Oxygen rom (don't remember the version but i have the zip on my computer): update-oxygen-2.1.6-signed.zip
- My current HBOOT screen shows the following:
--- AlphaRev ---
BRAVO PVT1 SHIP S-OFF
HBOOT-0.93.0001
MICROP-031d
TOUCH PANEL-SYNT0101
RADIO-5.11.05.27
Aug 10 2010, 17:52:18
- AFAIK the phone is the older AMOLED version (if that matters)
- I have a working ADB
- I dont have a goldcard
What I did after noticing the problem:
1. Read the sticky which told me to reflash my recovery.
2. Flashed the CWM 2.5.0.7 recovery via Android flasher. The program said it was successful but my phone was in a bootloop again without access to recovery.
3. Flashed the Amon Ra recovery via Android flasher. The program again said it was successful but the bootloop persisted.
4. Flashed both of the recoveries (one at time of course) via the adb fastboot command. Again, it was supposed to be successful, but the phone STILL was in the bootloop.
I thought the sticky explained my situation perfectly but apparently this is not the case
I have also a RUU lying around:
RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00. 32U_5.11.05.27_release
But I was hesitant to use it as I have the custom Alpharev HBOOT which might cause problems.
So what should I do now? I appreciate all advice.
Re: Bootloop with no access to recovery (S-OFF)
In my sig you'll find a thread with how to install 4ext recovery through pb99img. Check it out.
I DL'd the PB99IMG.zip file for the recovery and put it on my SD by moving the SD to my other phone and connecting it to my PC.
However, when the HBOOT searches for the PB99IMG.zip, it only says "No Image!".
Re: Bootloop with no access to recovery (S-OFF)
Are you sure you didn't put it in any folder?
Then, again in my sig, you'll find a partitioning guide. The first part of the guide will help you install a recovery. Try it.
Yes, I put it right in the root of the sd card.
The partitioning thread in your sig has a few methods of installing the recovery. But i have already tried them and for some reason they fail. I have now tried the Android flasher method, the ADB + Fastboot method and the PB99IMG.zip method. I have no clue why these should fail like i have described.
EDIT: Looks like I cannot run the RUU either. It says it failed to detect the device. What on earth could be going on when EVERY possible way of reinstalling the recovery fails? I was starting to think that maybe there was something wrong with my USB connection/drivers or ADB so I made a test and flashed another alpharev HBOOT (their bravo stock one: bravo_alphaspl.img) and the flashing procedure worked. So at least my ADB is working. Still no idea why the PB99IMG.zip just won't work... looks like my phone defies all these guides available here.
Update:
I downloaded the 2.3 GB RUU from the sticky topic. Suprisingly enough I could run it, it detected my device and went throught the whole RUU process without a single error. I booted the phone - and was again stuck in a bootloop. Went to HBOOT, chose recovery (the RUU should have flashed the stock recovery) but no, I could not get into the recovery. Instead the phone was again stuck in a bootloop. So I still cannot get into the recovery. The only thing that changed was the splash screen I was stuck on... (I had a custom splash, now it's the stock one)
I then formatted my SD, put the 4ext recovery PB99IMG.zip there and booted into HBOOT. This time It found the PB99IMG.zip. It asked if I wanted to update, I pressed yes and it went through it without any error. When it asked if i wanted to reboot, i pressed no, navigated into recovery and pressed the power button. This should have taken me to the 4ext recovery i just flashed successfully. And guess what? Bootloop again...
So after all this, I still do not have access to the recovery. I just get the bootloop every time. I've whacked around with android phones (mostly Galaxy S2 though) quite a lot but this far have never seen such a persistent problem which just evades all (for other people) working attempts to fix it. The procedures work exactly as described and give me no errors, but in the end the issue still persists: I cannot access the recovery because of the bootloop.
I was starting to wonder if it could be hardware failure causing this? Just a wild guess but the phone has been sitting in my desk for almost a year... I didn't change anything in the software. The only thing that comes to my mind is that the memory where the recovery and rom are stored is somehow corrupt. This would explain why I cannot get into the recovery even though i have reflashed it successfully multiple times. I also can change my HBOOT and splash screen.
Does anyone have any ideas left?
Re: Bootloop with no access to recovery (S-OFF)
Are you s-on now?
Yep,
At the moment i'm S-ON with the 2.3 RUU from your sig. Bootloader is 1.02.0001. I flashed the RUU from the PB99IMG. No errors. Still cannot get to recovery.
I then opened the phone and removed the mainboard but i could not see any damage at all. No burns, marks of water damage etc.
Re: Bootloop with no access to recovery (S-OFF)
As weird as it sounds, try putting the phone in the freezer without the battery for 10 minutes, then try to boot.
You are pretty good, man.
CASE CLOSED
Explanation: after putting the phone into the freezer for some time, I tried to boot. It booted normally to the ROM. Wifi worked, I could use internet, setup my settings etc. After 10 minutes the phone rebooted into a bootloop. This proves that the problem always was a hardware one, and this is why any software fixes couldn't solve the issue. Because i don't have a freezer in my pocket I can safely say the phone is broken and I can throw it away.
Thank you!