Related
i followed the instructions to the letter and after it was done
i was presented with a picture of an IC microchip and an arrow pointing down.
i restarted the phone and now it wont start.
i cant get into bootloader mode or recovery mode...
Please help me get my phone back!!!!
did you let it finish? the ic microchip and arrow pointing thing? or did you yank out the battery?
i panicked and yanked out the battery...i killed it, didnt i?
I think he didn't let the phone finish and restarted the phone cause it wasa taking too long if that's the case 99.0% the phone is bricked. It happend to somebody else here already. Jy
He just call tmobile and told them the wasn't turning on and they send him a replacement.
I think this is something that needs to be added to the flashing roominstructions.
slyfury said:
i panicked and yanked out the battery...i killed it, didnt i?
Click to expand...
Click to collapse
Im sorry man, you did the one thing you shouldnt have while flashing
Perrosky said:
I think he didn't let the phone finish and restarted the phone cause it wasa taking too long if that's the case 99.0% the phone is bricked. It happend to somebody else here already. Jy
He just call tmobile and told them the wasn't turning on and they send him a replacement.
I think this is something that needs to be added to the flashing roominstructions.
Click to expand...
Click to collapse
i agree 100% please add that to the instruction for noobs like me
oh well, i just hope i get a replacement quickly
that happened to me so i called t-mo and told them that my g1 wont turned on at all and tried the other battery so they send me a replacement. of course i was a noob back then. i learned my lesson in a hard way so i suffer a week without my precious g1 lol.
slyfury said:
i followed the instructions to the letter and after it was done
i was presented with a picture of an IC microchip and an arrow pointing down.
i restarted the phone and now it wont start.
i cant get into bootloader mode or recovery mode...
Please help me get my phone back!!!!
Click to expand...
Click to collapse
also once you called t-mo do not let them know that youre modifying your phone otherwise they will not send you another handset.
slyfury said:
i followed the instructions to the letter and after it was done
i was presented with a picture of an IC microchip and an arrow pointing down.
i restarted the phone and now it wont start.
i cant get into bootloader mode or recovery mode...
Please help me get my phone back!!!!
Click to expand...
Click to collapse
how about take out the sdcard and connect it to the computer, put the jfr33 in it, and flash your phone again. It works
also he could try getting into recovery mode using adb or sumthin...i am not too sure about it...but i think it can be done..!!!
tannyfiles said:
also he could try getting into recovery mode using adb or sumthin...i am not too sure about it...but i think it can be done..!!!
Click to expand...
Click to collapse
If the phone can't reach the bootloader or recovery console I don't think ADB is going to work but I could be wrong.
patience is a virtue
your topic title is misleading and could lead users who haven't tried yet to be too wary about flashing over to Haykuro's builds...
Ultimately...your phone didn't mess up after flashing 4.X..YOU messed up.
if you cant turn on youre g1 then it is dead, even if you connect it to pc or what if it cant be turned be on, it is dead cuz thats what happened to me so just call t-mo and tell them youre phone wont turn on and you tried another battery still wont turn and DO NOT tell them you modify or even saying you attemped to modify your g1's rom.
the best thing for him to do would be flash rc29 nbh and start from scratch...the phone is more than likely not bricked.
korndub said:
the best thing for him to do would be flash rc29 nbh and start from scratch...the phone is more than likely not bricked.
Click to expand...
Click to collapse
To my opinion, i do not think the phone is bricked since there is no hardware issue is involving, it's the software itself, if he can access to the root of the sd card, problem is solved.
but oh well, i would call Tmobile and request a new shinny phone . wait... they will send a refurbished one won't they? oh noo...
I have a similar problem, i was attempting to move apps to the sd card, partitioned it, installed the lucidrem rom and then started using his code and the flashing android loop started, turned it off and back on and still the flashing android, i used the fastboot method to restore my nandroid backup, and the phone is back to working, my problem is that i cant access recovery mode.
everything else is fine, just when i try to load the recovery mode it just stays on the boot screen, can anybody help a newbie out?
the bootloader works, and the phone can load normally, but the recovery mode wont start.
cueballv2 said:
I have a similar problem, i was attempting to move apps to the sd card, partitioned it, installed the lucidrem rom and then started using his code and the flashing android loop started, turned it off and back on and still the flashing android, i used the fastboot method to restore my nandroid backup, and the phone is back to working, my problem is that i cant access recovery mode.
everything else is fine, just when i try to load the recovery mode it just stays on the boot screen, can anybody help a newbie out?
the bootloader works, and the phone can load normally, but the recovery mode wont start.
Click to expand...
Click to collapse
That happened to me also. When I installed lucidrem's rom the recovery would work. What it actually was that when you first rooted your g1 do you rmr installing the recovery img? Well its pretty much the same thing lucidrems rom didn't have a recovery img command line attatched to it. I just installed recovery again from the terminal emulator just like it said in the root your g1 thread.
Atleast that is my side of the story. I don't anything about coding. So I could be wrong but that was just my experience.
bigballa said:
That happened to me also. When I installed lucidrem's rom the recovery would work. What it actually was that when you first rooted your g1 do you rmr installing the recovery img? Well its pretty much the same thing lucidrems rom didn't have a recovery img command line attatched to it. I just installed recovery again from the terminal emulator just like it said in the root your g1 thread.
Atleast that is my side of the story. I don't anything about coding. So I could be wrong but that was just my experience.
Click to expand...
Click to collapse
wow, thanks alot for your help, reflashed the recovery.img and it worked a treat, thought id bricked it good and proper, but your advice worked, thanks again.
Hi all,
I have a Magic 32b and recently put the Modaco_custom_1_51 rom on, with the Amon Ra's recovery image (as recommended on unlockr)
It was working ok, not great, a bit slow and mms wouldnt work, so...
I decided to change the rom, unfortunately I was in a bit of a rush and I kind of forgot what I was doing...
I went straight to the Recovery mode and clicked 'part sd: fat32+ext2+swap'
Then I put the new rom on using usb storage mode, I clicked on applied update.zip and of course it wouldnt work (all without applying any recovery image when the phone was working and wiping first), I rebooted the phone and now after the vodafone image I just get a blank black screen...
I then woke up and realised what i'd done.
I have tried searching what to do when this happens but I couldnt find anything... I've never used abd or commands and dont really know how the commands work... I just flashed and applied the rom using the 'one click' method on unlockr.
I dont think its bricked... I can boot in Recovery and fastboot...
I would appreciate any help you can give, theres propably a simple way to do it (well simple for you guys) but I just cant work it out, if anyone can give me some instructions it would be really grateful.
Im new here so take it easy on me
I got no reply when I asked before so I'd really like someone to help
Regards
Gino
this happend to me
okay the process is to,
1. put something else on ur sdcard
2. Right click on ur computer Icon. once inside click on ur SdCard rout. which is or i can be j,k,l,m,p what ever yours is then
3. right click put saftly remove. once done that click on Storage off on ur Ra' Recovery
4. Then Click reboot, and press home button once ur screen goes black. u'll go back to ur recovery Images and u should have the things there, and if u dont then u know what that means ur SD card is fried.
Thanks for the reply...
This is what I done..
(Remember I cant get into the phone to do anything)
-Booted phone into recovery
-Wiped data
-Part sd card fat32+ext2+swap
-Took sd card out, put new rom on
-Put sd card back in
-Wiped again for safety
-Applied update.zip
-Rebooted phone and then...
Went past vodafone screen and stuck on Black screen again....
What am I doing wrong?
Someone must know
Thanks
What rom are you trying to flash? Have you tried any other roms? Are you sure it's actually flashing your new rom?
Thanks again for the reply... I think the problem was the rom. I tried the new Evil Hero rom -3s final... but it seems pretty slow for me.
Do I have to increase swappiness or anything... I dont know how to do that or even check it?
Thanks
Anyone have any idea why its so slow?
Gino_x said:
Anyone have any idea why its so slow?
Click to expand...
Click to collapse
How big is your swap partition? Most hero roms seem to require a lot of swap (96Mb+) and that will need to be configured either in swapper (app from market) of by editing user.conf if the rom has one.
long story short. i bought a locked g1. did the factory reset. dont have data but have a sim card. i was trying to do the activation over wifi.
when i press enter type reboot and press enter nothing happens.
every time i downgrade to rc29 everything goes smoothly, until its time to reset it after its complete. I restart it and it always get stuck at the screen with the andriod and it says andriod beside it flashing from time to time.
the only way around this is to next install cupcake which brings me back to the activations screen. but i still cant reboot by typing in reboot
its not taking any commands so i cant never get adb to work.
from my searches I'm the only that has this problem right after downgrading to rc29
any info/ help would be greatly appreciated
Do you mean the screen that says "touch the android to continue"? You might want to do what it says.
Oh, and you might want to also do what this FORUM says... post your questions in the QUESTIONS section.
It appears to me that there is nothing wrong except that you aren't willing to follow the instructions.
prelude91sit said:
long story short. i bought a locked g1. did the factory reset. dont have data but have a sim card. i was trying to do the activation over wifi.
when i press enter type reboot and press enter nothing happens.
every time i downgrade to rc29 everything goes smoothly, until its time to reset it after its complete. I restart it and it always get stuck at the screen with the andriod and it says andriod beside it.
the only way around this is to next install cupcake which brings me back to the activations screen. but i still cant reboot by typing in reboot
its not taking any commands so i cant never get adb to work.
from my searches I'm the only that has this problem right after downgrading to rc29
any info/ help would be greatly appreciated
Click to expand...
Click to collapse
If thats what i meant thats what I would have typed.
lbcoder said:
Do you mean the screen that says "touch the android to continue"? You might want to do what it says.
Oh, and you might want to also do what this FORUM says... post your questions in the QUESTIONS section.
It appears to me that there is nothing wrong except that you aren't willing to follow the instructions blah blah blah.
Click to expand...
Click to collapse
I only found one other person that was having this problem after loading dreaing.nbh and no solution was posted other than he might need to upgrade to rc33
prelude91sit said:
I only found one other person that was having this problem after loading dreaing.nbh and no solution was posted other than he might need to upgrade to rc33
Click to expand...
Click to collapse
You mean you found one other person who couldn't follow directions. You won't get anywhere by sassing lbcoder.
Start by posting the question in the right subforum, then follow the directions on the CM wiki.
Ive tried everything. I followed the directions to the T. Its not rocket science. I done everything over 10 times and still hangs at the flashing andriod boot screen. Never goes to the activation screen. I can do the <enter>reboot<enter> and that works. also was able to sucessfully connect to adb for the first. when i tried it at this screen. i get an error when trying to pull up the wifi settings cause my phone itsnt functioning properly.
anybody???
Maybe try something else like RC7. When I was rooting my G1 I followed a tutorial which was recommending RC7 and RC29 to do telnet stuff. RC7 wasn't working for me so I tried RC29 and everything was OK. Maybe it's the same for you, but in reversed order .
i well try it asap. the only reason i havent tried it yet cause im in the u.s. i didnt think i could use it.
got a not allowed. its funny cause when i first tried it i think the image was messed up. it said not found or something. try it a couple times didnt work stopped and let it power up normal and it worked. i was excited. i was able to register it over wifi and everything.. turned it off swiped sim cards ect. then it just got stuck back on the flashing andriod screen. wtf? so im starting all over again it hangs again at that screen as usual
i would try flashing RC33 first...
I would try posting this in the proper forum. It seems to me you asked a question, however you posted in the Android Development forum, see where I'm going with this?
Hey guys,
ok, so I flashed an incorrect radio onto my phone (i think) I was running CM7 and flashed a new radio to try and fix the GPS and now it's stuck on the white HTC screen. I cannot boot into recovery because all I get is Hboot and no option to run a restore.
I put the SD card into another phone and downloaded the correct radio, rebooted to recovery and ran the update, but it still gets stuck on the white HTC screen.
Im in a bit of a panic here please can someone help me.
Sorry I know im not the first guy whos done this and im sure you gusy get sick of people asking for help but im really desperate here.
Many thanks,
Adam
We have all had that feeling ^^
Do this:
1. - Open the back cover
2. - Remove the SD Card
3. - Pull the battery out for 5 secs and put it back in
4. - Put the cover back on
5. - Press Vol Down and Power at the same time. Keep holding on Vol Down till you get in bootloader
6. - Select Recovery
7. - Wipe Cache
8. - Put your SD Card back in
9. - Reboot phone and its all working again. Yey.
It was in the thread
Thanks for the quick reply, I'll give that a shot and see how I get on, really appreciate the support.
Adam
flashing radio
I wouldn't have flashed a radio unless I absolutely had to if you can boot into recovery and you have a backup of your original radio and do a full wipe and do a clean install if you still have all your zip files in recovery see this why the dev's tell you don't mess with the radio your going to have this pushed from a pc good luck
There's nothing wrong with flashing a radio. It's a very simple procedure and shouldn't cause any problems if done properly.
Hey guys,
Just to let you know popping the SD card let me get into recovery and fix the problem.
As you can see from my sig it's been a loooong time since I played around with Android and I probably mis-read (didn't read) something.
You have my very humble thanks.
Thanks TheStigx! Really helped, I was freaking for a minute there
nichos said:
Thanks TheStigx! Really helped, I was freaking for a minute there
Click to expand...
Click to collapse
does anyone know exactly why sometimes flashing a radio does this? is it cause they didnt clear cache? im jus wondering so i can avoid this issue alll togetherrr
i tried the instructions in post#2 and it worked, thanks so much i was freaking out too lol. just goes to show how little i know. just an edit though, i had to pull my sd car out, boot into the bootloader, then install the sd card back in and reboot into recovery, then i got a bunch of errors about mounting so i ignored that and then just did the wipe cash and rebooted. then it came back to life! i thank you guys
Whenever I try to boot into recovery (vol up and power), I get a blue screen with no text or options. It's supposed to give me an option so that I can mod my phone. I have CWM recovery, and I followed the instructions right. I'm not sure why I continue to see a screen with no options. Any help would be appreciated.
Can anyone help me with this? I know the Impulse isn't a very popular phone, but someone has to know something that relates to this (it's pretty much the same as the Ideos X5, I believe). I could really use some help.
I changed the OP to hopefully narrow the problem down for anyone reading. Maybe it'll be easier to read and help with that way.
Are you sure that you flashed the right recovery for your phone?
MissionImprobable said:
Are you sure that you flashed the right recovery for your phone?
Click to expand...
Click to collapse
Yeah, that was the problem. I was able to load the rom, which led to another problem: can't get pass the at&t screen. Doing a factory reset doesn't do anything either. I had my apps and my system data backed up on titanium, so will that help me at all to restore my phone (I can only boot recovery)? Is there anything I can do, or did I brick my phone trying to load this rom?
jlm990 said:
Yeah, that was the problem. I was able to load the rom, which led to another problem: can't get pass the at&t screen. Doing a factory reset doesn't do anything either. I had my apps and my system data backed up on titanium, so will that help me at all to restore my phone (I can only boot recovery)? Is there anything I can do, or did I brick my phone trying to load this rom?
Click to expand...
Click to collapse
In your case i would go back to stock firmware and you will be good to go
And then do it all again and maybe some went wrong during installation on your phone
Cheers