Many people complain that they have "bricked" their phones when they really haven't. This thread will hopefully help reduce the questions on all of our useful threads.
How to tell if your phone is bricked:
1.) When you try to turn it on, nothing happens?
2.) Camera+Power does nothing.
3.) Home+Power does nothing.
4.) You flashed the SPL BEFORE the radio
If you answered yes to any of the above 4, you are bricked. You probably need a new board in the phone. Read more here: http://forum.xda-developers.com/showthread.php?t=516440 It has been confirmed that you WILL brick your phone if you attempt to downgrade your radio after flashing the new SPL. Not sure why you would want to anyways...
How to tell if you just need to re-flash:
1.) Your phone is stuck on the g1 logo
2.) Your phone is stuck in a boot loop
3.) Home+Power boots into recovery
If you answered yes to the above then you are NOT bricked. You have the G1 Night Light. This is (usually) a very easy fix.
The usual scenario is: You just upgraded your radio and/or the SPL on your phone and now you are trying to turn it on with no luck.
How to fix: After you upgrade your radio and/or SPL, you need to wipe a rom on the phone. For a plain almost stock feeling rom, checkout http://jf.andblogs.net/2009/05/24/jfv151-images-are-out/ if you are looking for hero, checkout the tutorial at g1upgrade.com.
I have also noticed when you flash hero, it will stay on the g1 logo for 5 or 6 minutes and then it'll finally start loading. Make sure your not being impatient and give it several minutes if you have just flashed a rom.
Last step:
If you have installed a new radio, then spl, then a new rom and you STILL get the g1 screen. Try it all over again. You probably didn't do something right. You don't need to ask questions in 30 different threads, your issue is not unique. You just need to search for some answers.
*Saved for future posts*
Edit:
Thanks! Updated.
I flashed the SPL before the radio whenever Haykuro released the Hero ROM and I didn't brick my device. Guess that I just got lucky. Thank goodness I know better now. haha
it's possible you flashed the radio prior to the SPL, only a loooong ways back.
Another thing to try if you are having issues is:
su
rm -r /system/sd/*
I was stuck in a boot loop and a quick ext3 wipe did the trick. The command should be able to be ran from console or terminal. You may need to mount /system with:
mount -t -rw,remount -o yaffs2 /dev/block/mtdblock3 /system
You would need to type that in between the commands above . I ran across this in another post but i think this is a good spot for it too .
Duplicate post...
thanx
At least I know now how to tell if I bricked my phone or just flashed it badly thanks for this.
youneek said:
How to tell if you just need to re-flash:
1.) Your phone is stuck on the g1 logo
Click to expand...
Click to collapse
many people who flashed the new SPL before the radio are stuck at the G1 splash logo, but cannot get to recovery or spl bootloader / fastboot mode regardless of what they do, so this bit might be misleading...
they aren't technically "bricked" b/c it's loading the radio rom, but it never hands off to the SPL, so there is currently no way of reloading either of those to make the device do anything useful -- essentially a brick
alapapa said:
many people who flashed the new SPL before the radio are stuck at the G1 splash logo, but cannot get to recovery or spl bootloader / fastboot mode regardless of what they do, so this bit might be misleading...
they aren't technically "bricked" b/c it's loading the radio rom, but it never hands off to the SPL, so there is currently no way of reloading either of those to make the device do anything useful -- essentially a brick
Click to expand...
Click to collapse
This is exactly what happened to me, it was a brick, sent for repair and they replaced the mainboard.
I have fixed 2 phones that had no recovery and stuck at the g1 screen. If someone has this problem message me and I'll help you fix.
Good Job
Sorry this is off topic. But...
Thank you for this thread!
Ok,
By the way, has anyone figured out what The difference in the baseband is?? I have a U in mine...
youneek said:
I have fixed 2 phones that had no recovery and stuck at the g1 screen. If someone has this problem message me and I'll help you fix.
Click to expand...
Click to collapse
really? if it can't get to recovery / fastboot mode nobody has published a fix w/o a hardware swap.
what's your method?
I will buy a bricked one off ebay and post the steps I do to get it back. I can only fix the "Night Light", I can't fix a truly bricked phone (yet).
digital006 said:
This is exactly what happened to me, it was a brick, sent for repair and they replaced the mainboard.
Click to expand...
Click to collapse
How and where did you sent for repair and how much does it cost? I have a bricked MyTouch3G at this moment. Did HTC took it?
not bricked just weird!
ok been reading on here ,not sure if i need to just reflash everything or sd issuse?i put the new raidio,then spl on !then put jacxrom on my phone worked great!then ran for a day.then tryed cyanogenmod 4.0 and loaded fine but got force closed issues at the google sign in so i wipe and went to jachero 1.2 loaded fine went to logo android and then htc ,but then the screen went to blank .like the as said g1 night light .so i went back to jacxrom 1.3 it loaded fine got stuck in t mobile g1 screen .ok i flashed again same thing. but this is the part if i take my memory card out it will boot up just fine!then put memory card back in but lol all apps are missing have reinstall them. i wipe every time.i have the latest raidio 22.19.26I).,spl 1.33.2005 .also the jacxrom is running fine when phones on .so any help please thanks .also when i put the spl on it loaded then said reboot so i did. after went back to recovery at the bottom it said formatting cach... but was setting there for a while so took battery out then booted phone .was it suposse to say done or not ! hope dont make any mad thanks for the info
bump
hey help me plz i have big problem
i forget hit alt+w when i install SPL then i press alt+s when SPL install i out battery then i put it my mobile don’t want open and when i holding down the Home and Power button don’t open recovery mode and i holding the End key and the Camera button don’t open boot loader plz help me plz
You aren't going to get any help with sentences that atrocious. Can you be more clear?
Related
I am a little confused. I have been trying to get WM6 on my T-mobile Wizard and actually got TNT 1.1 loaded and was working fine. I found that I could no longer view my contacts. The page would appear and then as quickly as it appeared it disappeared.
So I figured, I at least got it this far. I will just reload this rom and see if perhaps something did load right. Well after the reload. The phone boots up to the splash screen with IPL\SPL numbers and just sits. NOTHING.
I left it there for like 2 hours and still nothing. But I can still get into the BootLoader.
My questions to you gurus is:
Is the phone fubared?
Can I do some kind of master reset?
Why would it tell me "Invalid Vendor ID" when trying to flash the orginal T-mobile rom?
Are there any tools that can help me out? Paid\free?
Please help!!! Seriously! Please HELP!!!
Very much appreciated.
Thanks
Drunknasty said:
I am a little confused. I have been trying to get WM6 on my T-mobile Wizard and actually got TNT 1.1 loaded and was working fine. I found that I could no longer view my contacts. The page would appear and then as quickly as it appeared it disappeared.
So I figured, I at least got it this far. I will just reload this rom and see if perhaps something did load right. Well after the reload. The phone boots up to the splash screen with IPL\SPL numbers and just sits. NOTHING.
I left it there for like 2 hours and still nothing. But I can still get into the BootLoader.
My questions to you gurus is:
Is the phone fubared?
Can I do some kind of master reset?
Why would it tell me "Invalid Vendor ID" when trying to flash the orginal T-mobile rom?
Are there any tools that can help me out? Paid\free?
Please help!!! Seriously! Please HELP!!!
Very much appreciated.
Thanks
Click to expand...
Click to collapse
if your device is G3, unlocking is required to flash any rom, before upgrade your device, it is recommended to flash an official WM5.0 rom (in your case T-Mobile rom) with IPL and SPL 2.xx then flash again.
in general there are many probabilities for your issue.
((Where is TNT1.1?? did you mean 1.0?? ))
My Bad meant 1.0
So to get it straight.... I will need to unlock my phone each time?
Oh and to correct myself again, when flashing with the T-mobile ROM it says UPGRADE ONLY. And the read me file says its the wrong RUU. But it is the same file from Tmobile I used when I first got the phone. But I will try again.
Are there any other suggestions?
You need to read the "how to flash" sticky.
I did. I am not any expert or anything but I believe the phone is unlocked already since I once had WM6 on my phone. The real issue I am having is that it wont boot past the splash screen after flashing.
And that is true when re following the steps in guide. After flashing to the button rom it will not boot past the splash screen.
Try another ROM.
Sounds like you need the "Wizard Love" rom. I dont have the link handy but I am sure someone else does.
Drunknasty said:
I did. I am not any expert or anything but I believe the phone is unlocked already since I once had WM6 on my phone. The real issue I am having is that it wont boot past the splash screen after flashing.
And that is true when re following the steps in guide. After flashing to the button rom it will not boot past the splash screen.
Click to expand...
Click to collapse
Already got it. Thanks I am trying to load it now. But the only thing is that the last time it failed and I can understand what the error says. I know the number is 300 but can read the language.
But I will let you guys know when this load completes.
Thanks again for all the assistance.
No worky worky. The load completed and then boots the splash screen shows and then stays there.
Any ideas?
Try to remove the battery and let it out for at least half an hour. Then put it back in and see what it does then.
I thought the same thing too. So when it got done last night, out of frustration, I removed the battery and left it there to wait on when I get off work today. I will report back on what happens.
Again I would like to thank you guys for helping me. I really do appreciate it!
STEP 1 install the original manufacturer ROM
T-mobile UK
http://www.tm-phonedownloads.com/download_manager_mda_vario.html
T-mobile US
http://www.t-mobile.com/wmupgrade/
Search for the original rom for any other
instructions on how to use the original rom can be found here
http://support.t-mobile.com/knowbase/root/public/tm23294.htm?&A2L.SERVICE=AboutUpgrading
Put it in the bootloader mode.. ( three color screens )
hope this helps..
cheers
Praneet
Ok I did that and it gave me ERROR 296: UPGRADE ONLY
Then it tells me that the NBF file cannot be used for my PDA Phone. Please get newer NBF file.
Is there any way I can get the Tmobile splash and IPL\SPL number back to original, it doesnt need to boot all the way into WCE but atleast show the same numbers and splash during boot up?
Or any other way to get this thing to work?
Thanks guys
BTW it is a HTC Wizard from T-mobile.
If you are getting an error 300 you need a newer rom update utility, and regardless if your phone is a G3 or G4 it needs to be unlocked before you flash any rom.. LOAD a OFFICIAL cingular ROM onto your device before going any further, then unlock your phone either via www.imei-check.com or through some of the tools offered here...
Which one should I down load from Cingular? Even though I have a Tmobile phone?
what ipl and spl are you using and what radio are you using. Just post all the numbers from the bootloader
As soon as I get home, I will post them.
Thanks
Ipl 1.01
Spl 3.08
Thanks
Drunknasty said:
Ipl 1.01
Spl 3.08
Thanks
Click to expand...
Click to collapse
uh oh. someone tell me if I'm wrong, but I think this is bad. it's the result of flashing a g4 with g3 or the other way around... keep searching, and good luck.
flash the original t-mobile rom. your phone doesn't appear to be unlocked. good luck
I did a search, and dont see anything to answer this specific question.
Ive got my new Dev 1, and have the latest JF update. I want to install some cool themes, however, I know its a possibility to brick my phone.
Exactly how easy is it to brick your phone while installing a theme? I plan on following the directions step by step, but I will be very upset if something happens.
Any advice would be much appreciated. I suppose I just need some reassurance...
Thanks in advance.
Not too easy but if you Flash a corrupted SPL your toast
not very easy, just remember, if it boots to the SPL or recovery mode you are fine, it's not a true brick. if it doesn't boot at all then you may have an issue. i have had many times where the phone decided it didn't want to boot past the boot screen, or the flashing android and yet i am able to post this now using my phone as a tether. if you get stuck on one of those screens then you need to either flash the dreaimg.nbh or a new update.zip including the full JF build
Dredge said:
I did a search, and dont see anything to answer this specific question.
Ive got my new Dev 1, and have the latest JF update. I want to install some cool themes, however, I know its a possibility to brick my phone.
Exactly how easy is it to brick your phone while installing a theme? I plan on following the directions step by step, but I will be very upset if something happens.
Any advice would be much appreciated. I suppose I just need some reassurance...
Thanks in advance.
Click to expand...
Click to collapse
Why are you so worry about brink your phone? If you want to brink your phone pour some concrete on the phone and make a customize brink G1.
tubaking182 said:
not very easy, just remember, if it boots to the SPL or recovery mode you are fine, it's not a true brick. if it doesn't boot at all then you may have an issue. i have had many times where the phone decided it didn't want to boot past the boot screen, or the flashing android and yet i am able to post this now using my phone as a tether. if you get stuck on one of those screens then you need to either flash the dreaimg.nbh or a new update.zip including the full JF build
Click to expand...
Click to collapse
whatever he said....^^
I've flashed themes that were designed for RC3xx on my ADP1.1 and managed to "bricked" it. All i did was go to bootstrap and reload the SPL with RC29 and re-flash ADP1.1 to the phone.
As long the hard-SPL on the bootstrap remain untouched, there's always a way to recover your phone...it may be long, boring, and redundant...but it will safe your G1 from truly becoming a brick...or paper weight...or both
This makes me feel a bit better. I will just back up the latest JF update and keep it in case something happens. I will probably just hold off at tleast for a little while before I try doing much. I need to get a feel for the phone before I try to mod it. I found some cool wallpapers that should tide me over for at least a little while. But the clock is u-g-l-y. Im use to having TouchFlo, with HHC, and all the neat custom clocks.
Well, thats why I am probably not going to update my SPL...
I own an ADP1 and so already got the engineering SPL... and as the SPL update seems for me to be the only way to brick my phone... well, I am a coward...
It may be a little offtopic, but i am planning to update to JF1.43, or perhaps even messing around with Ubuntu MID (if ever possible).
Is there a really good reason I should update to HardSPL?
HELP I CAN'T GET DREAIMG.NBH Installed!
I just tried to downgrade my G1 from RC33 v1.42 + Radio Update 1.22.14.11!!!
I think I made the mistake and downgraded my bootloader from SPL_Hard to Original RC29_ SPL, because I was having trouble getting the file Dreaimg.nbh, recognized after booting holding camera + power buttons.
After downgrading from SPL_Hard to Orig RC29, I was able to boot holding the camera + power buttons, and the process started, but just before completing I got an error, FAILED TO UPDATE TERMINATING, and now my phone only reboots to the SPL screen with this showing:
DREA100 PVT 32B RUUNBH
HBOOT-0.95.0000
CPLD-4
RADIO-1.22.14.11
SEP 2 2008
I believe it's has to due with the Radio Update 1.22.14.11...
I'm going to try using QMAT and follow the Inst from that same thread. If that doesn't help can some offer some help???
Follow UP!
QMAT WORKED:
http://forum.xda-developers.com/showthread.php?t=490960
Sorry about the double posts!
So i think i know what i did wrong, but is there anyway to fix it? I have a 32b which i rooted with the "recovery-RA-sapphirev1.5.2H", then i tried to update the radio with the "update-radio-32A-6.35.08.29-signed" (i didnt read the "32A"). Then i tried to reboot the phone and it got stuck on the "Mytouch 3g" green start up screen, i cant get to the recovery image by holding home+end.
My understanding (please correct me if im wrong) to get the new Nexus ROM was that i had to;
1) Go the the 1.5.2 recovery image & wipe
2) Partition the card (and convert Ext2 to Ext3 or Ext4 depending on the ROM), reboot
3) Flash the new Radio, then reboot
4) Wipe, Flash the new SPL, then reboot
5) Wipe, flash the new ROM, and reboot
Im sure what i did was noobish...
Previously i had been using the 1.3.2 immage and had loaded Hero ROM's and tweeked Cupcake ROM's just fine, it was only when i had to update the radio and SPL was it that i found difficulty, mostly because i found too many and didnt know which one to use.
PLEASE HELP!!!
I'm willing to try anything. I hope i can get this fixed by this afternoon =,(
My first guess is that you are f**ked!
Only 2 "Nexus" roms I know that require new radio are for the 32A. And only new radio I know is for the 32A Magic!
Don't know where you got the instructions to upgrade your radio, but the ones I read stated that you have to flash radio, hboot, recovery in this sequence, and THEN reboot. Also, your recovery should be for 32B, dunno how you missed that one.
Try this: find your old radio image, your old hboot and recovery, boot in fastboot mode (back+power) and type in the following commands from the Android SDK tool directory:
Code:
fastboot flash radio your_radio.img <enter>
fastboot flash hboot your_hboot.img <enter>
fastboot flash recovery your_recovery.img <enter>
fastboot erase system -w <enter>
fastboot reboot-bootloader <enter>
You should now have rebooted back in fastboot mode. If that worked, try to reboot into recovery and see that works.
Once in recovery you can restore or flash another 32B rom.
See here for Engineering hboot images.
Download recovery for 32B
I found the link on theunlockr.com
developers.com/showthread.php?t=598973
And found instructions on youtube "ECLAIR 2.1 ROM REVIEW AND TUTORIAL !!!" and tweaked it slightly because i found a recovery image for my sapphire which didn't support either the spl or the radio, i forget... I've been up since 3am on Wednesday because of work and school, and now its 9am Thursday.
I was reading that 32b ROMs were working for the 32a, so i thought i might try a 32a since none of the links on Amon_RA's page developers.com/showthread.php?t=529019 were working for me.
I cant get to the fast boot menu... so that way doesnt work
Some_Biker_Guy said:
I'm willing to try anything. I hope i can get this fixed by this afternoon =,(
Click to expand...
Click to collapse
I think you are rather screwed. I believe the phone boots up the radio image before the bootloader and therefore you can't even get to flash a new recovery or radio image as the boot process is halted because of the defective radio image.
The only salvation I know if is a JTAG connection. This involves open up and soldering stuff to the mainboard of your phone. Since you're asking you probably not familiar with it I wouldn't recommend it to you.
you have a mytouch 3g right? if so, you flashed the wrong radio image. you flashed the ra(blahblahblah)H! not the ra(blah)G! "H" IS FOR HTC BRANDED "G" IS FOR GOOGLE BRANDED (THE MT3G). so that is your first issue. try to boot into fastboot and flash the RIGHT RECOVERY IMAGE.
wow as soon as I looked at this thread, you made so many mistakes on the first sentence lol. I hope you learn to read and not rush things next time ^^ Recovery H = 32A, Radio says 32A, and you have a 32B and now you can't get into fastboot? I'm 99.9999% sure it's bricked, but correct me if I'm wrong! 32B roms work for 32A when you port them over. Seems like you did almost no research at all.
You're understanding of what to do is right, but you didnt pick ANY of the right files
KAwAtA said:
wow as soon as I looked at this thread, you made so many mistakes on the first sentence lol. I hope you learn to read and not rush things next time ^^ Recovery H = 32A, Radio says 32A, and you have a 32B and now you can't get into fastboot? I'm 99.9999% sure it's bricked, but correct me if I'm wrong! 32B roms work for 32A when you port them over. Seems like you did almost no research at all.
You're understanding of what to do is right, but you didnt pick ANY of the right files
Click to expand...
Click to collapse
I agree with KAwAtA. You pretty much did the right steps (kinda) but you got the wrong files and now you got a nice brick. You should do research and know how to tell if your phone is 32A or 32B, why you should never flash the wrong radio/spl for your type of phone, and what ROMs are compatible with your hardware and why you should never flash the ROMs for another piece of hardware.
Well look on the bright side, since you bricked your magic, instead of trying out the "Nexus" ROMs, you can now buy a Nexus One for real but do not ROOt it because you might flash a 32B radio on it and make that a fancy brick.
damn sorry bro. does sound like everything that could have gone wrong went wrong for you. i also went to theunlockr to root my phone and add roms to it but i read those instructions like 3 times and watched the videos a few times when i first did it. oh well, you'll learn from this at any rate.
AndroidNoobie said:
Well look on the bright side, since you bricked your magic, instead of trying out the "Nexus" ROMs, you can now buy a Nexus One for real
Click to expand...
Click to collapse
that lucky SOB!
you can't get into recovery, that's fine, but can you boot into hboot and fastboot mode? if so, your phone will be fine, just have to fastboot flash the right junk on
Some_Biker_Guy said:
So i think i know what i did wrong, but is there anyway to fix it? I have a 32b which i rooted with the "recovery-RA-sapphirev1.5.2H", then i tried to update the radio with the "update-radio-32A-6.35.08.29-signed" (i didnt read the "32A"). Then i tried to reboot the phone and it got stuck on the "Mytouch 3g" green start up screen, i cant get to the recovery image by holding home+end.
My understanding (please correct me if im wrong) to get the new Nexus ROM was that i had to;
1) Go the the 1.5.2 recovery image & wipe
2) Partition the card (and convert Ext2 to Ext3 or Ext4 depending on the ROM), reboot
3) Flash the new Radio, then reboot
4) Wipe, Flash the new SPL, then reboot
5) Wipe, flash the new ROM, and reboot
Im sure what i did was noobish...
Previously i had been using the 1.3.2 immage and had loaded Hero ROM's and tweeked Cupcake ROM's just fine, it was only when i had to update the radio and SPL was it that i found difficulty, mostly because i found too many and didnt know which one to use.
PLEASE HELP!!!
I'm willing to try anything. I hope i can get this fixed by this afternoon =,(
Click to expand...
Click to collapse
Well, I BRICKED BRICKED BRICKED my other mytouch. Im talking where the computer wouldn't recognize it, wouldn't charge, turn on, splash screen, NOTHING. Wasn't the battery. If you can get to the screen (where you hold down volume and power) you can probably recover it. DON'T know if this would work but it may be worth a try read this link to get it un-rooted and then retry. http://theunlockr.com/2009/08/22/how-to-unroot-your-mytouch-3g/
iluvmymytouch said:
Well, I BRICKED BRICKED BRICKED my other mytouch. Im talking where the computer wouldn't recognize it, wouldn't charge, turn on, splash screen, NOTHING. Wasn't the battery. If you can get to the screen (where you hold down volume and power) you can probably recover it. DON'T know if this would work but it may be worth a try read this link to get it un-rooted and then retry. http://theunlockr.com/2009/08/22/how-to-unroot-your-mytouch-3g/
Click to expand...
Click to collapse
maybe u already tried.
dan-htc-touch said:
you can't get into recovery, that's fine, but can you boot into hboot and fastboot mode? if so, your phone will be fine, just have to fastboot flash the right junk on
Click to expand...
Click to collapse
he already said that he couldnt get into fastboot mode. most likely its a brick..
oshizzle1991 said:
you have a mytouch 3g right? if so, you flashed the wrong radio image. you flashed the ra(blahblahblah)H! not the ra(blah)G! "H" IS FOR HTC BRANDED "G" IS FOR GOOGLE BRANDED (THE MT3G). so that is your first issue. try to boot into fastboot and flash the RIGHT RECOVERY IMAGE.
Click to expand...
Click to collapse
I tried the "G" and it didn't work, so i tried the "H" and it worked. Fastboot didn't work...
Thanks everyone for you input... this is my reply to everyone since i cant reply to one/ a few at a time.
1) I knew how to root my phone, and did it multiple times. I also unrooted it a few times as well (just to get a fresh start and make sure i knew how to). I also loaded many different ROM's onto it including Hero and tweaked cupcake ROM's
2) Fast boot did not work, and the computer would not recognize the phone at any point.
3) The unlockr did a good job with instructions on how to root and unroot then loading the hero and cupcake rom's onto it but it had no explanation for loading the nexus rom onto it, although it did feature a link on where to get it. therefore i tried to piece together ways to update the radio and spl (this is where it all went to hell). i figured out that that is what i needed to do to run the nexus rom.
ok, ok now i know, wait for a full set of instructions for my specific phone to try to put the newest and coolest rom onto my phone... :/
4) i got it all taken care of, got "new" phone for free! so glad it worked out.
G1 DREAM (really is a dream, right now, a little bad one a little embarrassing)
been 5 mos since I took root via Cyanogenmod's latest G1 stable and last theme was PHRASh Then I thought about checking out
some other themes and clockwork orange caught my eye... Orange is my favorite color, so wehen I saw there was some Orange theme I must've had a dare encounter with myself-- i recall actually installing the Orange theme..... when i asked the phone to flash the theme, it went into permanent G1. Gave it about 12 minutes. Rebooted into recovery (home menu power) and then did what I think got me in deep droid doo doo -- I attempted to restore to my last backup whch was the day before (and ironically the BEST backup i ever made I had it all humming so nice and fast) Guys -- instead of hitting restore to last backup... I actually hit nandroid backup. I know. That was a really bad day and its been a worse 50 hours. I know -- and Ive learned -- OK?
Since that time.... 50ish hours Ive lost track of what Ive done, but its a potpourri
bootloader is dev spl skateboarding, recovery is Cyanogenmod JesusFreke 1.4 recovery.
DREAM DREA100 PVT 320
HSPL10.95.3000
CPLD-4
RADIO 2,22.19.361
OCT 29 2008
SERIAL0 -- (fastboot i have fastboot as well)
at first flash of bootloader it says "NO IMAGE FOUND!"
If I press Home when it restarts in perpetual cyclical hell I get into CMJF recovery. I have executed every single option numerous times -- and have not been able to successfully flash anything else -- and now I dont know WHAT to flash. I even tried to go back to root!
If I dont press Home or Camera, I get this....
the awful permanent G1 screen. Forever and ever.
I have Wiped backed up, tried to get update.zip and just about ANYTHING into my sdcard but I dont think they have been successful installations to flash. I am not ADB enabled yet. Surely someone knows what this is all about and I am willing to take a flame for posting in the wrong forum if I can get something out of this, I will pitch in later and help y'all keep these forums in workin' order!
every optioon on the recovery screen which is recovery CM and JF 4.2
When I try to load files according to the instructions in xda and cm i cannot get it in fast enough on the g1 running on the frozen G1 screen because I dont known the time of mount the SDCARD has and when it begins (I know it opens for a while and then closes)
So i got droidexplorer and its almost impossible to get the file in there. I can get it in, and see it, and reboot the phone (and computer)( restore usb connection and I see the update.zip on the sdcard. Then I unmount the phone and reflash and it says something about not being able to find the file.
Whats next? Please dont assume I know what I am doing, I am sure you can tell -- but I am really good at following instructions!
Hello anyone?
I have been up all night trying to fix this phone and i am still not able to do so. I
I cannot get into recovery anymore ------
i am stuck on the hardspl and I have found fastboot again. But I cannot use frastboot if I cannot get any commands into it. Anyone?
ok i get it -
thanks for the help guys! I now have my phone working at a blitzing pace and i am leaving it alone for now. I dare myself to leave it unchanged for a week. Thanks mostly to one of the Dudes on Cyanogenmod.com -- who helped me piece together the missing parts.
Actually -- let me summarize even if only I am reading this
Androids levels of defenses are 1. HardSPL 2. Recovery and 3. normalcy. Lose normalcy (Ok, a beauty of a ROM) you have recovery to get the ROM back -- but the trick is -- can you get the necessary IMG file on your SDcard to update.zip with? Can you figure out ADB and push the update.zip? Can you figure out Fastboot and what it REALLY does and what you can and cannot do with FB? If you can do any of these or FB with ADB, then you have a good chance. Just dont lose the HardSPL. If you give up after frustration and while grinding your teeth waving a white flag, flash the DREAIMG.img file, then you have given up root and FB. But at least you are at RC29, the level where the froot can be found. It is weird hanging out in Android 1.0 lemme tell ya. Feels so 1980'ish with bellbottoms in late decline.
But now its android time at CM with Phrash.
Later
heres the deal, I'll try to make this short and sweet:
Screwed my other g1 up in VA at Busch Gardens
Did a handset exchange got a brand new g1 (or refurbished) delivered to my door today
downgraded to RC29, and obtained root, installed RA recovery
flashed danger spl
but heres where I went wrong, before flashing spl I wiped (stupid me)
So since I wiped, recovery no longer exists and G1 boot screen is all I can access
Because after flashing danger, the only thing to do is boot a rom
but how can I do that if I no longer have a /system/recovery and I also cant boot into bootloader?
I am currently in a Soft brick stage...someone help!!
there is a soft brick thread, you are a senior member... should know this
I was told this once.. haha
I was just been lazy to use the search botton
yeah I know, Im just freaked out right now so I panicked and posted anywhere
mind linking me to that thread?
never mind I found it, and to confirm...I don't have a softy
yup....she's definitely a hard brick....****!
So what? you can't access the bootloader screen either?
1. This is not development related. Thread closed.
2. The issue was that you didn't upgrade your radio before you flashed the DangerSPL. That's an insta-brick move.