I mixed up my update files trying to update my radio and spl and installed the spl before the radio. And now it is stuck on the "t-mobile G1" screen. recovery won't work, fastboot won't work. Is there anything that I can do or is it gone for good?
Babyche43 said:
I mixed up my update files trying to update my radio and spl and installed the spl before the radio. And now it is stuck on the "t-mobile G1" screen. recovery won't work, fastboot won't work. Is there anything that I can do or is it gone for good?
Click to expand...
Click to collapse
lol......its gone....call tmobile and tell them your phone said it had an update and you said to update it and that you left it there for a while and when you came back it wouldn't get past that.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Just another brick in the wall.
How did you mix up the ordering of the files? Sounds like you know which should come first...
Oh well. Thanks for the advice. I just call T-mobile and they are going to send me a new phone and give me a loaner phone until the new one arrives. Great.
I did know but I'm new to this rooting thing I just started Monday. I had my phone rooted but I messed up when i was switching roms. I didn't know I had to wipe everything when you switch to a hero rom. So I started over and picked the wrong spl from all the different files that I downloaded on my computer to do the root. Then combine that with all the different guides that I have been reading I was doomed. The funny thing is that as soon as I hit update I knew I messed up.
Babyche43 said:
I did know but I'm new to this rooting thing I just started Monday. I had my phone rooted but I messed up when i was switching roms. I didn't know I had to wipe everything when you switch to a hero rom. So I started over and picked the wrong spl from all the different files that I downloaded on my computer to do the root. Then combine that with all the different guides that I have been reading I was doomed. The funny thing is that as soon as I hit update I knew I messed up.
Click to expand...
Click to collapse
You don't need to reroot the phone to go to a hero ROM from another modded rom. You only need to flash the newest radio and then the special SPL (in that order)
Babyche43 said:
I did know but I'm new to this rooting thing I just started Monday. I had my phone rooted but I messed up when i was switching roms. I didn't know I had to wipe everything when you switch to a hero rom. So I started over and picked the wrong spl from all the different files that I downloaded on my computer to do the root. Then combine that with all the different guides that I have been reading I was doomed. The funny thing is that as soon as I hit update I knew I messed up.
Click to expand...
Click to collapse
Yessir the ol gut feeling.
that's the worst when you ****ed up and there is nothing that you can do to stop it. well unless you are like me and don't care and just do it anyway
Diceman4 said:
You don't need to reroot the phone to go to a hero ROM from another modded rom. You only need to flash the newest radio and then the special SPL (in that order)
Click to expand...
Click to collapse
I know but something happen when I went from a Cyanogen mod too a Drizzy hero rom to were it would work and kept boot looping (if that is a word) so since I don't know that much about flashing roms and all that I figured I would just start over and just install the hero rom from the beginning and that's were I installed the wrong update.
Babyche43 said:
I mixed up my update files trying to update my radio and spl and installed the spl before the radio. And now it is stuck on the "t-mobile G1" screen. recovery won't work, fastboot won't work. Is there anything that I can do or is it gone for good?
Click to expand...
Click to collapse
How would you know if you bricked your G1?will it be stuck in a certain logo it'll be stuck at?
will it be stuck in a certain logo it'll be stuck at?
hahahahahahaha yes. The very first one.
you will know your phone is bricked by the fact that it no longer wants to cuddle with you when your press power, or when it no longer gets in the mood when you press home and power, and you know all hope is lost and you will never get to the g-spot on your g1 when camera and power no longer does anything.
yes all the answers are in there lol
Related
I was tryin to update the radio rom on my MDA and i i was usin the RUU and i guess i did somethin wrong cause now thers a X where the active sync is and a exclamation point where my reception bar is, also wen i go to about device i dont see the radio rom where the others ones are listed. So i downloaded the universal radio gsm exe but it doesnt recogize my device even thought it pluged in my microsoft active sync does recognize it either. and now its runs extremly slow, could someone give me some insite to wat i have done wrong and how i can fix it,
Thanks klawdlan
PS i am runin the orginal firm that came wit my mda US-Tmobile
The radio for the Universal will not work in the Wizard.
so what should i do to fix my prob
Download a Radio Rom (as an example you could try the Cingular 2.25 Radio Rom) for the Wizard on the XDA FTP
my pc is nto recognize it after i deleted the radio firm, even wen i plug in the wall charger thers no indication thats its chargin.
Can you get in bootloader mode by pressing the camera button (and hold it) and then doing a soft-reset?
If you get the tri-color screen, THEN try to update the Radio Rom, if that doesn't work, then you are in deep **** I guess!
yea i can get to that screen
Then go into that screen and flash the Radio Rom!
The Radio Rom is located here: ftp://xda:[email protected]/Wizard/Radio_Roms/wizard_radio version-2.25.zip
Good luck.
how will i get the rom to the pda if it wont even recognize it in microsoft synce, i cant even browse the device wen i go to my computer?
Listen carefully!!
- Connect your device via the cable to your PC.
- Get your device in the bootloader (tricolor-screen) mode.
- Unzip the zip file with the Radio Rom
- Go into to folder you unzipped it in
- Doubleclick the .exe file and follow instructions on your screen!
Good luck!
p.s. You flash Roms from your PC to your device, you dont flash Roms "on the device itself".
p.s.2 Maybe it will be smart to do a hard-reset afterwards (because your device is very very slow, look at my post in this topic on how to do a hard-reset http://forum.xda-developers.com/viewtopic.php?t=56145&highlight= ).
i did everythin u said word for word wen ruu was runin this came up
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and i continued and in about device it doesnt show a radio rom
Just continue!!
Just press Next or Continue until it starts flashing or gives an error!
i did and i still get no radio rom in the end
Dont pay attention whats on your screen.
You can end up with 2 things:
1) You get an error and the update failed.
2) The flashing begins and you will get a message when it's done!
Molski
i get the message that its done and that i flashed, but in im in wm5 and i go to systems about device i still dont see a radio rom
Then grab a Full Rom from here: ftp://xda:[email protected]/Wizard/Roms
And flash the Full Rom the same way I decribed for flashing only your Radio Rom.
Good luck pal !
p.s. When you turn on your device, don't you see a Radio Rom (GSM version number in your top-left corner?
alright ima try it now, thanks
PRAISE BE UNTO molski FOR HE HAS HELPED ME FIX MY FONE, thanks man i got a hang of this update thing now, learned mucho mucho i would make a new thread in ur honor if it were proper forum edicate
It's never wrong to thank someone (especially me in a new thread haha)
I'm glad your phone is working again that and you learned how to do things like flashing your Wizard!
And now you can play around with it....you know what to do if something goes wrong
Regards,
Molski.
Something screwed up today after installing that ApptoSD application from the market and I had to downgrade to RC29 again. That was all fine.
Now I was in the process of upgrading to CM 4.0.4. I already installed the old HardSPL, and realized I needed to install the 'new' one. I did this, and upon reboot my phone is stuck at the G1 screen.
Home+Power and Camera+Power do absolutely nothing.
Am I ****ed? This sucks.
jackaz said:
Something screwed up today after installing that ApptoSD application from the market and I had to downgrade to RC29 again. That was all fine.
Now I was in the process of upgrading to CM 4.0.4. I already installed the old HardSPL, and realized I needed to install the 'new' one. I did this, and upon reboot my phone is stuck at the G1 screen.
Home+Power and Camera+Power do absolutely nothing.
Am I ****ed? This sucks.
Click to expand...
Click to collapse
Yes, its gone. You need to install the radio update before the SPL update. Don't know why you would install the update that kills so many phones without reading up on it...
for the record: cm4.0.4 and all cyanogen mods do not require the DangerSPL, hardspl works fine.
Wow you get a big ol' F for not doing your homework and thinking that you needed the newest thing, good job screwing yourself
Just like everyone else said your toast. I was first thinking why would you need to go back to rc29 because of an apps2sd issue or really any issue, you should have just reflashed a rom. Second (like the others said) you didn't need the new spl.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
WTB - spare batt and batt cover!
Whoa, didn't need to jump down my throat - I already flashed the new radio after HardSPL, but I suppose it doesn't matter anyway.
The phone bricked after installing that app, and upon restart it was stuck at the G1 screen, I had to leave the office so I reflashed to RC29 (as it was the only ROM I had on my laptop) while I was on the road (so no internet access) because I desperately needed my phone for a job I was attending. When I got back to the office I must have mixed up my update.zip files somewhere in the process.
Thanks for the help from the people that weren't dicks about it, at the end of the day it's only a phone. Time for a shiny new one.
It is pretty common knowledge that the DangerSPL will not work with older radio versions BUT I believe flashing RC29 downgrades your radio to an earlier version, therefore bricking your phone. If you decide to use DangerSPL or Haykuro's SPL (the same I think) in the future, make sure you flash HardSPL BEFORE restoring to RC29.
I would play the stupid card with TMO and see if they will send you a new one.
And if you don't already, use Cyanogen's 1.4 Recovery. You can backup and restore via Nandroid from the recovery image so you can have a working version on your SD card at all times and not need a computer to access it.
Just for my own knowledge,
A phone with the hard spl can be safely downgraded back to rc29 (if you needed to send it back to tmo for instance) correct?
It's the danger spl that can brick your system if you downgrade to earlier radio right?
dcorrea said:
Just for my own knowledge,
A phone with the hard spl can be safely downgraded back to rc29 (if you needed to send it back to tmo for instance) correct?
It's the danger spl that can brick your system if you downgrade to earlier radio right?
Click to expand...
Click to collapse
Correct......
downgrading by using rc also downgrades the radio and spl, does not matter what spl you are using. it takes it back. you will not brick by using the rc dreaimg.nbh
r4d14n7 said:
It is pretty common knowledge that the DangerSPL will not work with older radio versions BUT I believe flashing RC29 downgrades your radio to an earlier version, therefore bricking your phone. If you decide to use DangerSPL or Haykuro's SPL (the same I think) in the future, make sure you flash HardSPL BEFORE restoring to RC29.
I would play the stupid card with TMO and see if they will send you a new one.
And if you don't already, use Cyanogen's 1.4 Recovery. You can backup and restore via Nandroid from the recovery image so you can have a working version on your SD card at all times and not need a computer to access it.
Click to expand...
Click to collapse
Thanks for that information.
I'd play the stupid card but I'm guessing that being in Australia makes that pretty difficult eh?
hey you guys have an awesome prime minister
He gave use all $900 just for the fun of it. Great guy.
I guess I can try contacting HTC and see if they'll repair it, I'm expecting to pay for it but i guess it's better than paying for a new phone.
i was talking about his policies, like telling everyone that this is our country and that we will not bend over backwards to appese you and if you don't like it then get the **** out. we need someone like that guy here instead of ass kissing obama
sorry small rant
yeah you could call htc
Haha I know you were
I've got in contact with the repair center in my area and they're going to 'get back to me'.
Y does my phone brick everytime i try to flash SPL? i know to do radio 1st, the SPL 2nd, then reboot, but when i reboot, it brick, this happened 5 times in a row, just today alone
It's not a brick if you can flash the radio and spl again. After flashing the spl you have to flash a new ROM because the spl removes the ROM.
make sure you flash the right spl for the right device, i flashed hard-spl to my 2nd gen dream and had a brick, 2005 spl worked on the replacement device
Fingerlickin said:
It's not a brick if you can flash the radio and spl again. After flashing the spl you have to flash a new ROM because the spl removes the ROM.
Click to expand...
Click to collapse
no believe me it was bricked, i couldnt do anythin, i just know how to fixed a bricked G1 thats all, but thanx 4 the info, i will try it now
djet229 said:
no believe me it was bricked, i couldnt do anythin, i just know how to fixed a bricked G1 thats all, but thanx 4 the info, i will try it now
Click to expand...
Click to collapse
Would you like to share how to fix a brick, there are many that would love this information.
Fix bricked g1
david1171 said:
Would you like to share how to fix a brick, there are many that would love this information.
Click to expand...
Click to collapse
all u have to do is unroot, have a spare SD card, format it 2 FAT32 just like in the beginning, then place the dream.nbh file on the root of the SD, the start the phone inn bootloader(u guys know this stuff) then when its done, u will have lost root access, but will still have a working G1 and can always reroot
djet229 said:
all u have to do is unroot, have a spare SD card, format it 2 FAT32 just like in the beginning, then place the dream.nbh file on the root of the SD, the start the phone inn bootloader(u guys know this stuff) then when its done, u will have lost root access, but will still have a working G1 and can always reroot
Click to expand...
Click to collapse
If you can get into the bootloader the phone is not bricked. Your terminology is incorrect. What you have is known as a soft brick.
rdfry said:
If you can get into the bootloader the phone is not bricked. Your terminology is incorrect. What you have is known as a soft brick.
Click to expand...
Click to collapse
Is that also known as a whiskey brick? HAHA
djet229 said:
all u have to do is unroot, have a spare SD card, format it 2 FAT32 just like in the beginning, then place the dream.nbh file on the root of the SD, the start the phone inn bootloader(u guys know this stuff) then when its done, u will have lost root access, but will still have a working G1 and can always reroot
Click to expand...
Click to collapse
The brick we are referencing is where the phone will not get into bootloader or recovery.
ummm... aren't you supposed to install a ROM after you upgrade your SPL? BTW, don't tell us you know what a brick is and then show that your phone is not bricked... I'm pretty sure if there was a fix for the brick it would be big news.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I had a brick, I held down the power button and the phone turned off and I could not get it to turn back on by holding the camera or home buttons. I finally found that the way to unbrick the phone was to hold down the power button and voila' it worked great
By the way I killed another G1, damn screen died out
***** and complained to t-mobile and got no where's with them, then I found the execitive custumer's relations # within 10 minutes they had me able to go get a brand new one at a store
gridlock32404 said:
I had a brick, I held down the power button and the phone turned off and I could not get it to turn back on by holding the camera or home buttons. I finally found that the way to unbrick the phone was to hold down the power button and voila' it worked great
By the way I killed another G1, damn screen died out
***** and complained to t-mobile and got no where's with them, then I found the execitive custumer's relations # within 10 minutes they had me able to go get a brand new one at a store
Click to expand...
Click to collapse
whoa i need that number
hjlow said:
make sure you flash the right spl for the right device, i flashed hard-spl to my 2nd gen dream and had a brick, 2005 spl worked on the replacement device
Click to expand...
Click to collapse
somebody can explain what is that ?? which device can I install hard SPL ?
I would like some clarification too... Last night I tried rooting my Rogers HTC Dream with the step-by-step guide using CyanoGen Mod, but on the very last step (Where it should have booted back into normalcy), it just stayed at the Rogers logo forever.
I don't think it's entirely bricked as I can get into the SPL thing (That's where you can do 'Fastboot USB', right?). I'm not sure how to get it back to normal though, I tried doing 'fastboot boot recovery.img' while the phone is in the Fastboot usb screen, and it reboots but it just sits at the Rogers logo again.
Is this thing bricked, or do I have options?
Okay, I did some more reading and now i understand a bit better...
What I have access to is the Bootloader, but I can't seem to get into the SPL. What steps do I need to take to get it back to working condition? I have a Rogers HTC Dream and I must have messed up when trying to apply the Cyanogen ROM
Holy Crap! A way to fix a Brick????!!!!!!!WOW!!!!!!!!
Hey if there's a way to fix a brick let me know cuz WOW! I would have gotten further with the last G1 I sent back to T-Mobile if I could have fixed it myself! Check your statements as you pertain it to being "BRICKED." BRICKED is not going past the T-Mobile G1 screen or not starting up at all! These newbies need to get it right! WOW! This one did give me a GREAT laugh today! This just made my day better now that I've had a good laugh!
can you get into recovery after the spl? home+power
jonzina said:
somebody can explain what is that ?? which device can I install hard SPL ?
Click to expand...
Click to collapse
Only the t-mobile g1/ADP1
rogers from canada will brick
use 1.33.2005 for rogers. its safe on that phone
the spl is the bootloader (well just think of it as the same)
in command prompt, when you type
Code:
fastboot devices
can you see your phone?
Also, if you booted off of the HTC recovery rom, your actual recovery is being replaced on each boot.
Search for the
"flash_image not found" thread in this section and look at sleepy_sanchez's method to remove the script that replaces the recovery.
EDIT
fastboot erase recovery
fastboot flash recovery *name of recovery*
fastboot flash system system.img
fastboot flash userdata data.img
fastboot flash boot boot.img
fastboot reboot
Click to expand...
Click to collapse
try that
making sure the images are in the same folder as the fastboot
if that doesnt work, try
http://forum.xda-developers.com/showthread.php?p=4677631#post4677631
Hi, all,
my radio refuses to upgrade on my G1 so im desperately trying to get adb and fastboot working to i can use hard spl to flash the newest radio (since im on the oldest one right now).
Im on a Windows 7 64-Bit HP Laptop and after using the usb drivers that came with the latest SDK, I managed to get adb working for literally 1 minute before it automatically shut off and the system stopped recognizing it and throwing out a Code 10: Device cannot start error. I downloaded USBDeview and uninstalled the usb drivers then I went through the registry and deleted all 'vid_0bb4&pid_0c02' keys values and folders...except one that keeps throwing this error for me:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Even when i set permissions to delete it, i still get that error.
Even though i deleted all the values but that one, i managed to install it successfully once i used DroidExplorer, and i managed to get it working for literally 1 minute before the driver stops sensing the phone. Any suggestions?
Uninstalling the driver in device manager and installing it from device manager always worked for me. But I havn't used Windows for the past month+ so there could have been an update or something that breaks ADB.
ive tried that a thousand times =/
no i dont think they made an update that prevents it.. ive been trying off and on to install adb for a few months now but now that i flashed hard spl in hopes of fixing my stupid radio, ive been aggressively trying for the past 2 weeks lol
Anyone have any suggestions? I was thinking of formatting the whole hard drive on the computer but that's extremely painstaking and a little extreme...anyone have any ideas?
speedysilwady said:
Anyone have any suggestions? I was thinking of formatting the whole hard drive on the computer but that's extremely painstaking and a little extreme...anyone have any ideas?
Click to expand...
Click to collapse
You shouldn't format for something as small as installing a single driver, the headache that comes with setting up countless progs or accs and what not isn't worth it, at least for me. i had dual-booted vista instead since it worked with the DL'd driver. I haven't tried in 7 though haven't looked for the driver yet.
Yeah you're right formatting would be a huge pain, that's why I'm wondering if anyone can help me remove that registry key cuz I think that's what's been screwing up my install.. I can't dual boot an earlier OS because I don't have the disc for vista or xp. =/
You get this error when you plug in your phone?
And how are you trying to flash your radio? When you're in recovery, you can't flash the require update.zip? Maybe give some other information, like what ROM are you on, what recovery?
tehseano said:
You get this error when you plug in your phone?
And how are you trying to flash your radio? When you're in recovery, you can't flash the require update.zip? Maybe give some other information, like what ROM are you on, what recovery?
Click to expand...
Click to collapse
I am currently on Super D 1.9.2 (modified to fit on Any SPL)
Amon_RA Recovery 1.6.2
Yes Ive had this problem forever, i used to be stuck on the .11 radio, it refused to update to 26i or the latest radio whenever I used amon_RA or cyanogen's recovery image, whether i used button shortcuts to flash or if i manually selected the radio update with the trackball. It would flash with no error message but everytime i held power and camera itd be the .11 radio, and the baseband displayed the same thing...then I was advised to make a goldcard and use DREAIMG.nbh to downgrade to .29 and reroot...which i did, and after trying again to upgrade the radio it wont even go up to .11 and above now.. even after flashing Hard SPL. So now Im trying to get ADB set up so I can fastboot a radio update. I have no idea why it wont work through recovery.
bump anyone?
Try a system restore? I can't really help you, all I have is vista
Can anyone give me the link to a guide to get fastboot drivers and fastboot.exe working on 64-bit windows 7? XDA search is down at the moment and I'm searching like crazy on google and not finding the results. I want to flash a new recovery on my Tab 10.1, thanks!
OneStepAhead said:
Can anyone give me the link to a guide to get fastboot drivers and fastboot.exe working on 64-bit windows 7? XDA search is down at the moment and I'm searching like crazy on google and not finding the results. I want to flash a new recovery on my Tab 10.1, thanks!
Click to expand...
Click to collapse
Here you go sir:http://www.youtube.com/watch?v=Bg-cGTZE2XI&feature=related
Story, in key point format:
-Just moved, no internet at home yet (in fact I've been using tether since I only check e-mail and use FB anyway)
-At cafe... Already closed, but they agreed to let me stay about 5 minutes past closing time, no time to search. NO N00B/"SEARCH FIRST" COMMENTS PLEASE.
-Don't have any old phones
-Just got a new girlfriend and didn't think much about emergency expenses and spent most of my $ on wine n' dine with her (but at least I got some worthy "dessert", but that's another story).
-Just lost my job a week after meeting her (I stayed up all night, eventually gave into a "food coma" [see above] and came into work late) LOLOL... Woulda had a new phone budget if I was around for another 2 weeks, but noooo....
Anyway:
-Tried to install CM5 onto G1
-Installed it with the CM bootloader (or something like that, it had an orange font)
-Downgraded to RC29, successfully loaded AMON_RA
-Installed DangerSPL, rebooted per the instructions
-Stuck on the boot screen for almost exactly half an hour (5 mins after 8PM until 8:30PM), said "WTF" and pulled battery out
-According to the first few search results, my phone is "fully bricked", as in end+back/home/camera/whatever doesn't work (although when you push end+trackball the blue light turns on, whatever that means)
With that in mind, what should I do? Any hope?
Hmm well Im not an expert like most of these other guys by ANY means, but in my experience I've learned that removing the battery during a percieved "hangup" is a sure fire way to brick a G1. Trust me Ive done it, not fun.
If you can make it to the recovery screen somehow, theres still hope. On the Cyanogen Wiki, I believe theres a type of method for reflashing a rom, by booting while holding the camera button. I would recommend researching that.
Pulling the battery had nothing to do with it. The combination of 1.33.2005 SPL + 1.x radio is incapable of booting any known kernel. The misc partition was configured to boot-recovery, which overrides any key presses. So when it starts up, it figures it should launch recovery, which boots far enough for the SPL to think that its booted (otherwise it would force you into fastboot).
Your only hope right now is to jtag the thing and either wipe your misc partition or load a compatible SPL that allows fastboot.
You forgot to flash a compatible radio!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
BoomBoomPOW said:
You forgot to flash a compatible radio!
Click to expand...
Click to collapse
The funny thing is that if he had done the first sensible steps of installing an engineering bootloader (one with fastboot) and wiping the recovery partition (to force it into fastboot when recovery failed due to being wiped), he'd be fine.
DAMNITS!! I only read the "steps" portion of the instructions on the Cyanogen Wiki, which didn't even include the "radio" portion of the equation (I edited it just to avoid other people having the same problems).
lbcoder said:
Pulling the battery had nothing to do with it. The combination of 1.33.2005 SPL + 1.x radio is incapable of booting any known kernel. The misc partition was configured to boot-recovery, which overrides any key presses. So when it starts up, it figures it should launch recovery, which boots far enough for the SPL to think that its booted (otherwise it would force you into fastboot).
Your only hope right now is to jtag the thing and either wipe your misc partition or load a compatible SPL that allows fastboot.
Click to expand...
Click to collapse
Jtag? Sounds horribly hard; baking it and taking out a ROM chip? Wow.
Acecalibur said:
...by booting while holding the camera button. I would recommend researching that.
Click to expand...
Click to collapse
"-According to the first few search results, my phone is "fully bricked", as in end+back/home/camera/whatever doesn't work"
lbcoder said:
The funny thing is that if he had done the first sensible steps of installing an engineering bootloader (one with fastboot) and wiping the recovery partition (to force it into fastboot when recovery failed due to being wiped), he'd be fine.
Click to expand...
Click to collapse
Well, I was (somewhat) following the steps of the Cyanogen wiki.
EdWaRdW818 said:
Jtag? Sounds horribly hard; baking it and taking out a ROM chip? Wow.
Click to expand...
Click to collapse
Your information is wrong. There's no baking, there's no removing chips. There is just interfacing with the board. If you're handy with a soldering iron, its a cakewalk.
Well, I was (somewhat) following the steps of the Cyanogen wiki.
Click to expand...
Click to collapse
Finding all your information in one location? What makes you think that your SINGLE SOURCE of information was accurate or correct? For all you know, it was written with the INTENTION of screwing you up.