Database Users

Weird Issues with Haykuro's SPL?

Hey all, I hadnt visited xda for about 10 days until yesterday, to see how the different builds with Hero were going. Then I see the SuperHero post, and I remember that I have a partitioned 2gig MicroSD. So I go and re-root my phone(I unrooted due to rebooting issues) and install the HardSPL. After installing the Hard SPL, I try to Install Hay's Radio, then after a succesful Install, Install Hayk's SPL. Now, its kind of weird, but it doesnt want to boot. I got bricked and DREAIMG.nbh my way back to RC29. I read all about it, and saw that you need a PVT board and all that, which I do. I also remember he said there was a 99.99 Chance it will work with pvt, which, again, im guessing im that 0.01??? I am sure I have a PVT Board, it says PVT 32B or something like that..Its kind of awkward, so if anyone has any suggestions to tell me I would appreciate it. Also Mods if youre going to move this, please advice me first, I want to be able to track my Post.

I really could not track your steps but did you flash the radio update before you flashed the new spl?

Was it hung at the G1 screen? If so go back into the recovery and reflash the SPL. After it has completed, do not go into the console and type "reboot recovery". Instead reboot with the home and back buttons. It should then reboot twice and end back up in the recovery again. You should then be able to flash the ROM of your choice. That is what worked for me.
Vermithrax

Flashing the SPL will change the size of the system and data partitions of the internal memory, so you must flash your system again and wipe.

In general, find it there

Got the same problem, can't even get to recovery.
Hope there is a solution soon.

billc.cn said:
Flashing the SPL will change the size of the system and data partitions of the internal memory, so you must flash your system again and wipe.
Click to expand...
Click to collapse
And there it is.

Yes, I have been having the same problem as well, I believe a thread needs to be created in order to solve the current solution. There is no possible way for me to get into the phone what so ever at this time unfortunately. I am stuck at the G1 screen and I am unable to pass into recovery mode. Perhaps a brute force connection is necessary?

TylerKinkade said:
Yes, I have been having the same problem as well, I believe a thread needs to be created in order to solve the current solution. There is no possible way for me to get into the phone what so ever at this time unfortunately. I am stuck at the G1 screen and I am unable to pass into recovery mode. Perhaps a brute force connection is necessary?
Click to expand...
Click to collapse
This thread has been created. "Let's fix that SPL" by haykuro.

Bricked/Blind/Barely alive magic, no recovery screen (SPL ****up) any suggestions?

Hi
similar to an other thread here if tried to change my SPL
and never recovered.
I can still get the blue led going using TrackBall + EndCall buttons.
The orange led lights up when I connect the usb cable.
But I cannot see it from the pc in any way (adb/fastboot).
there is some life in it but not a lot, have not seen the screen light
up at all.
Would it be possible to get a new bootloader/spl on it? Perhaps using
some kind of automatic update mechanism that is build in using an
update.zip file on the sd card?
Any help is more than welcome.
abe

*bump*
hmm, post needs al least 10 chars... should be enough now...
Has everyone also drawn a blank on this?
abe

Try downloading the ruu from your phone's official reseller.

T-Mobile USA standard OS.
Assuming that you backed up using Nandroid or something to SAVE and STORE your originally packaged Android 1.5 (Cupcake) version from T-Mobile...you NEED to restore that properly using a recovery image. Amon_RA has a great one, so does Cyanogen, obviously by now I'm sure you're aware. But keep in mind, to get back to that state...you must be careful not to alter any necessary files on that standard OS.
Do some Google searching and try to track down a Cupcake 1.5 download from one of those sites that leaked it or something. That's your best bet. Right now you don't need to be worried about continuing on from where you are. You need to backtrack and begin anew.

Sorry to hear that. I was thinking of installing Haykuro Apps to SD ROM and it needs to change the SPL. But I think not worth taking a risk.
Can you tell a little bit more which ROM were you planning to install?
Which SPL did you update to?
Which ROM did you have at the time of SPL update?
Which thread or instructions did you follow if any?

Hi
@mrjunix
I have a google ion, and therefore cannot return it unfortunately to the
carrier, as there was none. I went to the Google IO conference but
I am back in Europe and there is not support here.
btw what do you mean by RRU??
@Reignzone
I do have a nandroid backup but I cannot get back into recovery mode,
or fastboot mode or anything... the pc does not recognize it either.
@technicolor
I installed the Cyanogen recovery image and was able to install
one of his rom's. It worked fine but then I wanted to install
a Hero rom and I wanted to update the SPL.
Used the cyanogen recovery to update the spl using an update.zip
file. the phone restarted the "android" update screen came on
briefly and it never came back on...
changing the recovery rom should not be an issue,
and normally I think you do not need to flash your spl at all any more.
you can do a lot with the fastboot mode and one of the recovery roms
mentioned by Reignzone
abe

Reignzone said:
Assuming that you backed up using Nandroid or something to SAVE and STORE your originally packaged Android 1.5 (Cupcake) version from T-Mobile...you NEED to restore that properly using a recovery image. Amon_RA has a great one, so does Cyanogen, obviously by now I'm sure you're aware. But keep in mind, to get back to that state...you must be careful not to alter any necessary files on that standard OS.
Do some Google searching and try to track down a Cupcake 1.5 download from one of those sites that leaked it or something. That's your best bet. Right now you don't need to be worried about continuing on from where you are. You need to backtrack and begin anew.
Click to expand...
Click to collapse
This is the same advise you gave me yesterday on my bricked MT3G, but if you can't enter recovery mode, a nandroid backup ain't gonna help much, is it?
Also, any cupcake downloads are not going to help either, if you can't fastboot or enter recovery.
I appreciate you trying to help, but if you pay attention to the OP (and my own post), you'll see that your advise isn't going to solve anything.

For starters:
My advice to have those of you who are in need to take an approach that allows you to backtrack you work. Perhaps you left out various details of your issue or process taken in order to end up where you're at.
Your bitterness isn't appreciated for my having misread the problem.
YOU are the one with the F***** device, not me.
Anyway, all that aside; you might try to read-up on various threads that could be of some help. Google search, HTC support, ADB, etc.
There's always something to be done.
Good luck.

abeman said:
Hi
@mrjunix
I have a google ion, and therefore cannot return it unfortunately to the
carrier, as there was none. I went to the Google IO conference but
I am back in Europe and there is not support here.
btw what do you mean by RRU??
Click to expand...
Click to collapse
forum puffering aside, RUU is ROM Upgrade Utility
Prepackaged programs that bypass the phone's software altogether to reflash the rom
My carrier is Rogers of Canada and I have their "HTC Magic" phone
Be warned that Rogers is intentionally altering their hboot to disable system changes, you may not be able to cook your os after using this rom update.
Their updates page
https://your.rogers.com/web_auth/techsupport.asp
has the update
http://downloads.rogers.com/wireless/products/htc/magic/RUU_Sapphire_Rogers_WWE_2.17.631.2_release_signed_NoDriver.exe

Rogers magic update freeze/brick

Hello all,
As many of you know Rogers issued an update for 911 issues and sense ui just recently, unfortunately as I attempted the update via SD card method, the first update seemed to have gone well but after once it wanted to reboot it keeps on splashing the ROGERS over and over.
I'm thinking this is most likely because I am rooted and the process just didn't agree.
I am currently running amon ra's 1.2.3 rec. img
with amon ra's 1.6 rom
32A motherboard
BTW I still get to boot when I hold end+vol down
and when I hold end+home I get amon ra's screen but is quickly taken away after a few seconds.
Any help would be much appreciated.
___________________
EDIT:
For the record I think I know the issue, just don't know how to fix it.
You see, instead of getting this:
fa rm5.static.flickr.com/4046/4298577978_f3366c55ae.jpg
(wouldn't let me post a link as I am new)
after "parsing...[SD ZIP]"
I only got
[1] BOOTLOADER
[2] RADIO_V2
help?

good news and bad news.
good news, im pretty damn sure thats not a brick as you can still get into fastboot (the vol down + power)((atleast thats what i think fastboot is))
bad news, i dunno how to fix it.
i know theres a way to revert to original stock ROM via fastboot, so im sure it is fixable. don't know about custom ROMs via fastboot.
bed time, though. good luck, man, and dont get bummed cause im 99% sure you aren't just plain ****ed.
edit: just noticed screenie, but can't see it because my girlfriends retarded wanna-be stepdad decides to look at pr0n all night and continues to install "mywebsearch" **** and i can't get to it. :/
Hopped on my mytouch, still think your good but let someone else who knows more vertify that.

another option
one other thing you can do,
go to a rogers store, and tell them you tried applying the so called essential upgrade 'b/c you care about your safety' and the '911 issue is a important fix'. tell them you recieved instructions to do w/e it is using the SD card method.
basically, you tried the update ---> phone got messed up.
i know someone else did it and it was grounds for them just giving you a new phone.
not saying 100% it'll work, but its worth it b/c you get a new device with the new ROM on it if it does.
goodluck.

cdstewart said:
I attempted the update via SD card method
Click to expand...
Click to collapse
Can you clarify which SD card method? Was it using the official DREAIMG.nbh from Rogers?
I thought that I had bricked my phone because I went for a hail mary attempt to root my phone. But unfortunately it wouldn't get past the Rogers screen.
However, after talking to a CSR, they sent me a link to the Windows 7 file and it rewrote everything back onto my phone and I was able to boot it normally again.

@r3s-rt
Ya, thanks. I figured I wasn't completely boned.
@mbk.2k3
I thought about that but when I go home+end you can see I'm using amon ra, which would mean they know I rooted and therefore void my warranty
@dotster
This is the method,
Upgrade Instructions for Rogers HTC Magic
Requirements:
Rogers Magic
Battery Level of 50% or more. Do not start upgrade if battery level less than 50%
MicroSD card formatted in FAT32, please note cards formatted in FAT will not work.
Installing the Update via MicroSD Card:
Part1
The first part will prepare the device for the actual update but will not upgrade the Operating System, the upgrade itself will be performed in Part2.
1) Download the HTC_Magic_Update_File1.zip and extract the file within, SAPPIMG.zip to the root of the memory card in this form, do not extract it’s contents and please do not change the file name.
2) Backup your personal data: All personal data (contacts, applications, photos, bookmarks, etc) stored on the device will be lost after the update process. There are also 3rd party applications on Android Market place to back up your applications and personal data.
3) Power off the device.
4) Remove the existing microSD card from your device (if there is one already installed), press in on the microSD Card to eject it and then remove it from the slot.
Insert the microSD card with the SAPPIMG.zip on it in the microSD slot, slide it into the slot until you feel a “clickâ€.
5) Press and hold the Volume Down Button and the Power buttons until the display turns white.
6) The update will begin installing, please follow any onscreen instructions, press the trackball when prompted to press “Actionâ€
7. Once the update is complete, “Press Action to Complete†will be displayed on the screen, press the TrackBall for the device to reboot and complete the first part of the upgrade process.
8. Power off the device to prepare for the step 2 below.
Part 2
Upgrading the device.
1) Delete the SAPPIMG.zip from the microSD card
2) Download the HTC_Magic_Update_File2.zip and extract the file within, SAPPIMG.zip to the root of the memory card in this form, do not extract it’s contents. Please do not change the file name.
3) Follow the same instructions as in Part 1 - step 3 TO 8.
4) Delete the SAPPIMG.zip file from the card.
Click to expand...
Click to collapse
Keep in mind this is magic and not dream
Thanks for the help guys.

cdstewart said:
Hello all,
As many of you know Rogers issued an update for 911 issues and sense ui just recently, unfortunately as I attempted the update via SD card method, the first update seemed to have gone well but after once it wanted to reboot it keeps on splashing the ROGERS over and over.
I'm thinking this is most likely because I am rooted and the process just didn't agree.
I am currently running amon ra's 1.2.3 rec. img
with amon ra's 1.6 rom
32A motherboard
BTW I still get to boot when I hold end+vol down
and when I hold end+home I get amon ra's screen but is quickly taken away after a few seconds.
Any help would be much appreciated.
___________________
EDIT:
For the record I think I know the issue, just don't know how to fix it.
You see, instead of getting this:
fa rm5.static.flickr.com/4046/4298577978_f3366c55ae.jpg
(wouldn't let me post a link as I am new)
after "parsing...[SD ZIP]"
I only got
[1] BOOTLOADER
[2] RADIO_V2
help?
Click to expand...
Click to collapse
I had the same problem while installing the new update yesterday. I had to call Rogers to guide me through it and even he couldn't figure it out. My phone just kept rebooting over and over after installing the first update. Even in recovery mode it didn't give me a chance to wipe, flash or restore anything because it would reboot in a matter of 2 seconds. The tech support guy on the phone had no idea what to do. I finally realised that I had a seperate Mini SDcard USB adapter that I could put my SDcard in and then plug into the USB. That allowed me to access my SDcard so I was able to delete the first SAPPIMG and then put the new SAPPIMG from the second update onto the SDcard. I repeated the same process from the first update (I was able to access fastboot without it rebooting), everything installed perfectly and now the phone is up and running great. If you don't have a Mini SDcard to USB adapter I'd suggest picking one up at your nearest Electronics store. I believe I picked mine up at BestBuy for $35 which came with a 4gb class 4 SDcard. The adapter is so small that it actually sits on my key-chain. Hope this helps.
Rogers Magic
Radio: 6.35.10.18
SPL: 1.76.0010
(unrooted)

cdstewart said:
@mbk.2k3
I thought about that but when I go home+end you can see I'm using amon ra, which would mean they know I rooted and therefore void my warranty
Click to expand...
Click to collapse
if you're desperate it's worth a try. maybe it's just my personal experience with them but i have a feeling most of the rogers reps/techs wouldn't know/care enough.

@FoTwoZero
Thanks that sounds just like mine.
I'll give it a shot.
Were you rooted before?

cdstewart said:
@FoTwoZero
Thanks that sounds just like mine.
I'll give it a shot.
Were you rooted before?
Click to expand...
Click to collapse
I was rooted before, this is why I'm sure I've had the same problem as many of you. It seems though that this issue doesn't just stop at us... This issue has been happening with many other carriers and I'm not sure why (as of yet). I've flashed dozens of other Sense ROM's and even ROM's without Sense for ei. Espresso and Eclair and they all worked fine before. This new Sense ROM from Rogers is fantastic. So try what I did and you should be on your way with no issues.
Now if only we can root this damn phone.
Rogers HTC Magic (32A)
HBoot - 1.76.0010
Radio - 6.35.10.18

Chynkinese said:
if you're desperate it's worth a try. maybe it's just my personal experience with them but i have a feeling most of the rogers reps/techs wouldn't know/care enough.
Click to expand...
Click to collapse
After the update your phone won't be rooted anymore, therefor your warranty will still be in effect. After flashing the first update it already changes your SPL and Radio therefor Rogers wouldn`t know if you were rooted prior to the update. If you stuck in the boot loop just follow my instructions and you will be home free.
Now if only we can root this damn phone.
Rogers HTC Magic (32a)
HBoot - 1.76.0010
Radio - 6.35.10.18

@FoTwoZero
Just did what you did and I'm up and running!
Thanks
I think they did misname the updates though.
Because in the instructions given, and picture above correspond to the 2nd zip file.

cdstewart said:
@FoTwoZero
Just did what you did and I'm up and running!
Thanks
I think they did misname the updates though.
Because in the instructions given, and picture above correspond to the 2nd zip file.
Click to expand...
Click to collapse
Happy to hear that I could help. They did misname the files but how could you blame someone who goes by the name of Rogers. I have several services with them and it's nothing but headaches with them.
I'm sure it was a rushed update as well. The devs at HTC were probably pressed for time to get this update up and out the door within a couple of days. Rogers will possibly be a major distributor for them in the next upcoming years.

Thanks a lot!
That solved it.

Anyone been able to root this ROM yet..?? I have tryed everything and I just keep semi bricking my phone.. but I can always recover it.

1.33.2005

Hi all,
I'm a complete newbie. Most of you will have little patience for me but I'm hoping to find at least a couple of you willing to help me out. Here's my story. I thought it would be cool to by a used HTC Magic from Ebay to use with AT&T. The guy that sold it to me put Froyo on it and I was excited to have the latest Android on the phone.
I got it yesterday and the trouble started quasi immediately. I will post the exact things that happened as well as I can.
1. First the phone was rebooting on its own. It would make it as far as the home screen with the icons but if I tried to press anything, like contacts, it would reboot.
2. Then it eventually took me to the recovery screen where, after reading several threads, I downloaded the newest (not ROM, but whatever the first thing is on that page that you can update it).
3. Then the phone stopped rebooting itself but I couldn't get to the market or email because the dumbass that sold me the phone hadn't wiped his user info. So I googled again and was told to factory reset.
4. I tried factory reset 3 times and it did nothing.
5. Went back to the recovery page to see if that had anything that would help and I clicked Fix Permissions and let it run that.
6. Still no change when it came to wiping his user info.
7. Got frustrated and googled again. This time I saw a thread that said you should reboot using the up/down key and power. Did that.
Since then, I've had a blinking HTC green screen. At some point during this process I made it to what looks like a basic OS window from which I copied the following information:
sapphire pvt 32b eng s-off h
1.33.2005
radio-2.22.19.261
apr 20 2009, 15:30:43
hboot
What do you suggest I do now? I emailed the guy who sold me the phone because I figure if he put it on there, he can put it back. Or at least send me the files. Not sure he will care or want to help me. Besides, doesn't seem like he got it right.
I am willing to try to fix this myself but I don't want to start downloading files and flashing the phone only to destroy it. Guidance is needed.
Thank you in advance.
Seelier.
Metuchen, NJ

If the device actually booting then you should be alright, just sounds as if the guy who sold it to you flashed it with something crappy.
1.33.2005 is your SPL version, and that particular SPL version is what's referred to as an "engineering SPL" which allows you to flash roms and custom recoveries via fastboot (basically). For more info you can read here , but it doesn't overly concern you now.
To flash any roms yourself (more easily) you will need a custom recovery such as Amon_RA's Recovery, which you can download in this thread. Follow his instructions. You may already have this but you didn't say so.
Once you have done so, I suggest you install a ROM such as CyanogenMod, which you can get from here. Again, instructions on how-to flash it are in his thread. Essentially though, it is as follows:
- Put cyanogenmod rom on your SD card.
- Boot in to recovery screen (press the ON button whilst holding HOME)
- Wipe data/dalvik-cache
- Flash .zip from SD card & choose the file you put there
- Reboot the phone and wait patiently
Edit: Just to reassure, the things that tend to "brick" phones are flashing SPL and Radio updates, which you don't appear to need to do. Flashing roms very rarely causes devices to break, it is usually just the rom at fault.

Not Development related. Moved to General.
OP, next time you post make sure you post in the correct section or I'll close the thread.

[Q] Bricked Wildfire after attempted Froyo Update, Please help!

First of all, sorry if this is posted in the wrong place. Im pretty new to all this and don't really know how things work here.
I think im pretty buggered, and im pretty far out of my depth now. Im just posting to see if anything can be done or if it's already too late. Sorry if im missing something obvious that can fix this, however after 3 days of messing with this stuff my brain is starting to blur lol. Ok so here it is:
Tried updating to froyo via the OTA update pushed out recently. That failed and ive tried various ways of getting froyo to install over the last few days using Clockworkmod recovery. I ended up pushing a load of system files onto my phone via adb just to let the updater-script get past assert's. The point is, this was obviously a bad idea as I now have some kind of messed up copy of froyo installed which will not boot up past the HTC splash screen. Problem: the half-cocked update replaced the Clockworkmod recovery with the stock recovery so I now cannot use nandroid to push a backup back onto the phone
To make things worse when I boot into the stock recovery I also can't get into adb/shell, it detects the device but just says offline. Tried a lot of things to get round this but nothing has worked. So as ive got stock recovery and can't seem to get into adb anymore it would appear ive pretty much run out of options unless something can be done with fastboot... I don't know what im doing with that though so any help would be appreciated.
HTC Wildfire T-Mobile UK
S-ON
HBoot - 1.01.0001
Radio - 3.35.20.10
Recovery - Stock
Im at the end of the road here. If anyone has any ideas to try I would be very very grateful, otherwise il have to go see how much T-Mobile wants to repair it
Thanks in advance !

Undeadllama said:
First of all, sorry if this is posted in the wrong place. Im pretty new to all this and don't really know how things work here.
I think im pretty buggered, and im pretty far out of my depth now. Im just posting to see if anything can be done or if it's already too late. Sorry if im missing something obvious that can fix this, however after 3 days of messing with this stuff my brain is starting to blur lol. Ok so here it is:
Tried updating to froyo via the OTA update pushed out recently. That failed and ive tried various ways of getting froyo to install over the last few days using Clockworkmod recovery. I ended up pushing a load of system files onto my phone via adb just to let the updater-script get past assert's. The point is, this was obviously a bad idea as I now have some kind of messed up copy of froyo installed which will not boot up past the HTC splash screen. Problem: the half-cocked update replaced the Clockworkmod recovery with the stock recovery so I now cannot use nandroid to push a backup back onto the phone
To make things worse when I boot into the stock recovery I also can't get into adb/shell, it detects the device but just says offline. Tried a lot of things to get round this but nothing has worked. So as ive got stock recovery and can't seem to get into adb anymore it would appear ive pretty much run out of options unless something can be done with fastboot... I don't know what im doing with that though so any help would be appreciated.
HTC Wildfire T-Mobile UK
S-ON
HBoot - 1.01.0001
Radio - 3.35.20.10
Recovery - Stock
Im at the end of the road here. If anyone has any ideas to try I would be very very grateful, otherwise il have to go see how much T-Mobile wants to repair it
Thanks in advance !
Click to expand...
Click to collapse
You'll need a goldcard and an RUU. Look up how to make a goldcard and let me know when you have one

Wow, thanks for the quick reply
I did try creating a goldcard yesterday (using android.modaco.com/content/software/308798/pc-application-goldcardtool/). So assume I DO have one for the time being...
however if it doesn't work and I need to create a new goldcard:
Since I can't get into adb or boot up android and therefore can't access my sd card through my phone I presume il have to go out and buy a cheap card reader tomorrow.
Also, I have to run this command again:
adb shell cat /sys/class/mmc_host/mmc1/mmc1:*/cid
But if I can't get into adb how would I go about doing this, can I get the CID of the sd card from a card reader?
As for the RUU, there's many to choose from on shipped-roms.com, does this sound about right?
RUU_Buzz_TMO_UK_1.14.110.1_Radio_13.45.55.24_3.35.15.19_release_130442_signed.exe
Thank you so much for your help.

This this a decent guide from Paul over at MoDaCo.

Ok disregard my last post about a card reader... I managed to borrow a friends android phone since it appears goldcard's are specific to the sd card, not the phone. So after following the instructions I now definitely have a goldcard.
Also have the RUU mentioned in the previous post.
RUU_Buzz_TMO_UK_1.14.110.1_Radio_13.45.55.24_3.35. 15.19_release_130442_signed.exe
Is this right, and what do I do with these now to get them on my phone? Ive tried running the RUU whilst in Hboot and in recovery but it wont recognise my phone, presumably because adb isn't working.
Thanks again for the help.

There is another way to do it when it can only get into hboot. I'll look today for the method and let you know.
Sent from my HTC Wildfire using XDA App

Ah I did manage to get round it in the end. Using the PC49IMG.zip hboot method. Tried pulling the rom.zip from the temporary files that are made when running the 1.14.110.1 RUU. But obviously as I had a newer hboot or bootloader or whatever it was and it wouldn't let me downgrade back to this version. So I went for the newest one, 2.22.405.1 I think it was. With that in the root of the sdcard everything was up and running again after it had finished installing over the top of the messed up system.
Only worked because T-Mobile's OTA was a slightly older version 2.21.110.2, thank god there was a newer version available on the interwebs.
Probably not the best way of doing it but im just glad ive got a working phone again.
Thanks for replying though.
Just on a side note... its bloody ridiculous that its so hard to downgrade android!!! It causes people like me, who don't really know what they're doing, large quantities of banging-head-against-wall sessions

Undeadllama said:
Ah I did manage to get round it in the end. Using the PC49IMG.zip hboot method. Tried pulling the rom.zip from the temporary files that are made when running the 1.14.110.1 RUU. But obviously as I had a newer hboot or bootloader or whatever it was and it wouldn't let me downgrade back to this version. So I went for the newest one, 2.22.405.1 I think it was. With that in the root of the sdcard everything was up and running again after it had finished installing over the top of the messed up system.
Only worked because T-Mobile's OTA was a slightly older version 2.21.110.2, thank god there was a newer version available on the interwebs.
Probably not the best way of doing it but im just glad ive got a working phone again.
Thanks for replying though.
Just on a side note... its bloody ridiculous that its so hard to downgrade android!!! It causes people like me, who don't really know what they're doing, large quantities of banging-head-against-wall sessions
Click to expand...
Click to collapse
Yeah that's the method I was going to suggest, glad you sorted it out.
It's the fact that they lock out fastboot and stuff. If we had S-OFF from the factory, fixing these things would be so much easier

Hi,
how were you able to do this?
"Ah I did manage to get round it in the end. Using the PC49IMG.zip hboot method. Tried pulling the rom.zip from the temporary files that are made when running the 1.14.110.1 RUU. But obviously as I had a newer hboot or bootloader or whatever it was and it wouldn't let me downgrade back to this version. So I went for the newest one, 2.22.405.1 I think it was. With that in the root of the sdcard everything was up and running again after it had finished installing over the top of the messed up system. "
Thanks