Related
i will try to be as detailed as possible. im coming from the kaiser community so go easy on me
when i had recieved the phone it would turn on go past the tmobile g1 screen and go into the recovery console. the console read. JF 1.41.
after reading around the best option i got was reverting everything back to factory settings.....and so i did. i installed the factory spl went back to rc29....then updated to rc 30 and installed the new cupcake.
everything was fine except for i couldnt get the phone activated given im an AT&T user.
this morning i finally recieved the unlock code from tmobile and when i turn the phone on with the att simcard, it gave me the triangle with the exclamation screen.
so i hit alt +l then alt w and after a reboot it would bring me back to the same screen. Also this recovery screen is diff from the jf 1.41 (im guessing this is the factory console).
now im out of ideas as to how to get this phone back in order. i would love flashing the DREAIMG.NBH but sadly my phone refuses to go in bootloader.
ive been trying to hold camera+ power and its jsut loads up the tmobile g1 screen.
any and all advice/helps are appreciated.
-thank you
so this is totally weird. i leave the phone unplugged with the battery out for about 3 hours. came back to work on it....turned it on and well it loaded and got me to the home screen ( no sim card ).
so i powered off the phone and inserted the AT&T simcard turn it on and it shows me the same screen again with the triangle and exclamation point.
how do u explain that ?!
pressed power for 3 seconds and then let go and held down the back key. it flashed the bootloader tricolor screen and then said ""everything will be reset to factory defaults .press send to reset"" and when i did that there was no change........nothing happened. ended up pulling the battery out..
Same problem..
I have very similar problem.. but mine takes much more than 3 hrs to come back.. and even then , the task manger keeps popping up from time to time in the home screen ,, so i guessed my home button was stuck or something...
After i found your "problem Sovled" post in another theread on 11th oct ..i thought i better take your suggestion before taking phone apart..
I was on 1.5 version and 2.22.19.26I radio. also i do not know whether i'm in RC29,30,33 ..
i'm really confused about all this radio,firmware ,recovery things....
Please Guide me ..
well first you need to get in your ph to find out if u have rc29. if you are able to get to home screen just hit menu - setting - about phone - all the way down it'll tell you what you are running.
i followed this guide to help me flash it to the cyanogenmod rom
http://forum.xda-developers.com/showthread.php?t=563679
hopefully it helps. but if you are able to get into bootloader unlike me then jsut flash the rc29 hopefully it will solve your problem.
my home key acted like it was stuck but now everything is working fine.
Thanks for Replying so quickly ..
I managed to go to the bootloader screen(tricolor) ..actually it went without even pressing the camera button(any idea why??) after leaving the phone without battery for about 5 hours.. and i flashed the Dreaimg-RC29 file .
Since then i'm Stuck in recovery mode again.. but this time the recovery utility is different (yellow letters)..i.e hopefully RC29 is succefully installed.
I wanted to complete doing your suggested guide before asking any more questions, but now i unable to so what shud i do now?
IS the task manger popping up involuntarily sometimes for you in the cM builds?
Can it be that you had a hardware button issue, which somehow rectified itself when going to Cyanogen..
I really appreciate your taking time to answer my questions ..
well sounds like jsut what had happened to me.
make sure you have tmobile simcard on you with a dataplan.
you're going to have to leave your phone off without the battery or just turned off for a while. from here on out it was trial and error. i kept trying to turn the phone on hoping it would go past the recovery screen once it did i activated the phone and finally completed the root process.
as for the cyanogen mod rom i think you are right. though on my initial flash i had a bunch of force closing apps but it all fixed itself upon a restart. ever since then i haven't seen the recovery mode every time i boot it.
PS: that reocvery mode that you see is the stock recovery meaning yes u have flashed RC29 sucessfully.
so i jsut flashed to CM 4.2.3.1. and well im back to square one. im booting into the recovery by default. obviously confirming my doubts about the hardware problem.
im going to try and leave the phone off for a while and see if i can get it to load up. usually that solves my problem.
Oh..
Thats depressing.. Anyways... Lets do it together then I have kept my phone unsed for about 16hrs now.. hope it works ..
Have you tried the HTC Diagonistic program for g1 (DREADIAG.nbh) ?.. I am yet to try it out as i cannot go to the bootloader..
http://www.megaupload.com/?d=7NRX7H40
which version of cyanogen were you using before this happened?
i have not tried diagnostic. iw as going to use ADB to push the recovery on there but it went into bootloader.
i was using cyanogenmod rom 4.1.9999. now i have updated to 4.2.3.1.
actually iw as working on it last night. i re did that whole guide except for downloaded the new rom and flashed it.
so as of now once again that hardware flaw is gone and the phone is working fine.
mtkhalid said:
i have not tried diagnostic. iw as going to use ADB to push the recovery on there but it went into bootloader.
i was using cyanogenmod rom 4.1.9999. now i have updated to 4.2.3.1.
actually iw as working on it last night. i re did that whole guide except for downloaded the new rom and flashed it.
so as of now once again that hardware flaw is gone and the phone is working fine.
Click to expand...
Click to collapse
Did you update from 4.1.9999 straight into 4.2.3.1? If so, that's the problem (maybe).. I suggest you install the HTC 1.6 ADP Rom (link in the cyanogen 4.2.3.1 post) then upgrade to 4.2.3.1. Make sure everything is updated.... rom, recovery & spl (before you upgrade SPL make sure you have the most recent radio version first! or you'll brick the phone). then give it a try and see what happens...
you are right. the first time i just flashed the new rom. the second time around i followed the guide except for i flashed the latest cyanogen rom.
I'm not able to make it go to the home screen even after so many attempts..
i could only manage to go to the bootloader screen once and flashed the RC29 and i'm stuck there
Can you elaborate on how you got to the Home screen , like how long you keep it off or press which buttons to start ?
I'm not in the US , and have bought this phone from Ebay (new, never used) from a seller with good feedback for G1 (wanted this phone very badly). I was using the phone for barely 3 days when i did a factory reset from the phone and this problem started occurring .
IS there anything else i can do..?
Thanks for Helping..
Still waiting for your answer
SaiSantoshD said:
I'm not able to make it go to the home screen even after so many attempts..
i could only manage to go to the bootloader screen once and flashed the RC29 and i'm stuck there
Can you elaborate on how you got to the Home screen , like how long you keep it off or press which buttons to start ?
I'm not in the US , and have bought this phone from Ebay (new, never used) from a seller with good feedback for G1 (wanted this phone very badly). I was using the phone for barely 3 days when i did a factory reset from the phone and this problem started occurring .
IS there anything else i can do..?
Thanks for Helping..
Click to expand...
Click to collapse
how did you flash the RC29? after pressing the power button
did it give you any errors? once its flashed, reboot by pressing home and back (or w/e the SPL tells you to)
it should boot into the rom
Home button problem (repaired/solved)
Firstly, thanks for responding ..
I had flashed RC29 when it had gone to the tricolor bootloader screen on its own
but after that it would not go anywhere other than recovery(exclamantion mark)
Now good news
4 hours back i opened the phone again(third time) , and took a safety pin and started scraping(gently) the non shiny parts of the connector ( daughter board to main board) .
I think it was previously shorted near that area , so by scraping removed the shorted metal joints .. and now the phone booted up to RC29 (just like that) and i even installed the cyanogen mod ..
Many thanks to u all .. hope this Comes UP in google search for people with similar problems(and there are many)...
KEYwords: Home button stuck on recovery no booting
Ah wow didnt think of that lol.. glad to see you got it to work
Hi guys,
UK G1 (Dream) phone recently updated to the 1.6 build, all working fine.
Yesterday I tried installing the free app Shop Savvy. the phone resetted itself after install and sat on the G1 boot screen permanently.
Now phone will pass this boot screen (Tmobile G1)
Tried:
Recovery mode - will not work at all
Quick boot - brings up the multicolour screen but does nothing after.
**PHONE IS NOT ROOTED**
looks like I have had the phone JUST over a year, not looking good...
Any ideas?
You can boot in to the SPL/bootloader so thankfully you haven't bricked
If you're on a contract with tmo you could take it back to the store and they should give you a replacement, but where's the fun in that?
If you want to fix the problem yourself, all you need to do is downgrade to firmware 1.1, then accept the OTA update to 1.6.
Here's the procedure:
1)Put the phones SD card in to a card reader and format as fat32
2) Extract this file and copy it to your SD card as 'DREAIMG.nbh'
3) Put the card back in the phone and hold down power and camera to boot in to the bootloader.
4) Flash it. (Action button is the trackball).
It's a good idea to leave the charger plugged in and have a decent amount of charge in the battery (eg 40%+).
Afterwards the phone will restart and you will need to re-enter your google account info. All your apps and data will be gone, but there's not much we can do about. You can set things up and install apps while you wait for the prompt to update.
Thanks alot AdrianK,
Really appreciate the steps and info, nice one
I have done some flashing on other phones etc so I have no problem with this. However, I am wondering how a normal app such as Shop Savvy could corrupt my ROM and am wondering if it might not be better to get a new phone as this one could have hardware fault?
What do you think?
Silver.
OK,
did exactly as you said Adrian. Phone went through all the flashing routine then, right at the end said press action button to continue (trackball) every time I press the trackball phone returns to the bootloader screen
What now?
SilverfoxUK said:
OK,
did exactly as you said Adrian. Phone went through all the flashing routine then, right at the end said press action button to continue (trackball) every time I press the trackball phone returns to the bootloader screen
What now?
Click to expand...
Click to collapse
I think you can take the battery out restart the phone
Thanks but unfortunately I have already tried that.
Phone just sits on the G1 boot screen as before...
Any other Ideas?
is that ROM you linked for me a UK ROM Adrian?
Once you get to RC7 use these to build back upto 1.6
http://code.google.com/p/official-android-firmware/downloads/list
SilverfoxUK said:
Thanks but unfortunately I have already tried that.
Phone just sits on the G1 boot screen as before...
Any other Ideas?
is that ROM you linked for me a UK ROM Adrian?
Click to expand...
Click to collapse
Yeah that's the RC7 ROM, the UK ROM for 1.1. RC29 is 1.1 for US phones.
This is all very odd, especially that it was an app that caused it, or as you suggested possible hardward failure. Oh well, I guess all you can do now is take it back to tmo.
So here's the deal.
it's a long story, but i happened in a short time.
I was unlocking my bootloader and stuff on my nexus one on my mac. using the boot loader.
I used the superboot to unlock it.
and so i succeed in that.
i didn't bother with the install-superboot-mac.sh thing.
i didn't know that by then.
so i went on to search about the cyanogenmod 7, and i can't get the radio refreshed. i read the article in the cm forum.
so, i saw this post somewhere,(...read hundreds of posts now)
that tells me to use the rom manager thing.
so i downloaded it, and i tells me that my phone is not rooted!
so i was wondering how this happened.
i searched online, and i found this post telling me to use that install.bat(which is for windows, mac is the one i mentioned above) thing after i unlock the bootloader.
i was a bit scared.
but i went on to the fast boot manu and i connect my computer,
i put the directory in, and then i threw the install-superboot-mac.sh thing in my phone, successful, so i rebooted my phone.
And after the first not-ANIMATED start up screen, which is the staying-X and the unlocked symbol at the bottom, the screen goes black.
i was not sure what happened. so i pullout the battery and booted it again.
same thing.
it was not until the third time i opened it and waited for it, i realized that it was my screen that's not working!
After the stable X, the system goes to the animated one, but my screen is blacked out, so i can't see.
The bottoms on the phone are still working , yet i can't see a thing!
I can still open the fastboot/bootloader screen, but after that, nothing!
the recovery don't work, it's just an android with the sign.
I'm very worried about this situation.
please reply to me!!
i really need help, since i know nothing about this.
I just thought that 2.3's cool and now i got this....
here's some info that might help,
i have the korean version of the phone, it was cheaper and stuff.
didn't notice a different except that there's no 3g?
i don't really know what's the deal with it.
but it seems to be special or something.
The phone is unlocked, but my computer fails to find it using the adb devices.
im not sure if my phone is usb debbuging.
probably yes.
Everytime i try to load the recovery, it tells me to wait for device.
I really need help!!
OK... so you might have messed up your firmware... no worries... get a custom recovery (like AmonRA recovery)... flash it using fastboot... pop in a custom ROM like CM... flash and reboot...
the thing is i can't load the recovery or the mods. so here's the problem
Do as Craig said.
Put phone into the bootloader screen. White screen with skateboarding androids.
Do your thing with fastboot.
Reboot directly into the freshly flashed recovery and install a ROM.
Read the wiki.
Sent from my Nexus One using XDA App
Read my signature, find a proper guide in Wiki ("Unroot / restore"), execute.
Next time, before you're trying anything, either find a good guide on the internet or try understanding what things actually do before you attempt them.
I've read the wiki, but is my phone compatible with the rom?
my phone's korean version..
im not sure if i can.
and i certainly can't afford another adversity.
reclusivenigma said:
I've read the wiki, but is my phone compatible with the rom?
my phone's korean version..
im not sure if i can.
and i certainly can't afford another adversity.
Click to expand...
Click to collapse
It will work just fine, your phone isn't bricked and will be working fine in no time if you follow the advice in the posts above.
Edit: Am I the only one who wants the word 'Bricked' explicitly defined for the xda forums?
and also, since my screen is out, im not sure of weather my back up data thing is on or not, and usb debugging also
i've tried the ROMs, but the three i tried don't work.
downloading more, but i doubt if there's difference.
the device doesn't tell me to install the update, instead it just goes back to the bootloader screen
i've tried the ROMs, but the three i tried don't work.
downloading more, but i doubt if there's difference.
the device doesn't tell me to install the update, instead it just goes back to the bootloader
...
K, they don't really work, after checking the rom, my phone just goes back to the screen that showed up when i pressed power and volumn down
Why do people insist on receiving their instructions on a golden spoon?
Do you think you're the first one ever that got his phone corrupted? Maybe the second?
Go to Wiki, download FRG33, proceed with instructions for PASSIMG method. PUT ATTENTION THAT YOU'RE NAMING THE FILE RIGHT!
These instructions have been given in 800000000 threads by now. Look for the thread about moving from Vodafone OS version to stock Google OS. Search the forum with the words "restore stock".
What exactly are you doing?
You have a few pieces of advice that will work, but you're not really giving any details about what you are actually trying...?
Here's the link to follow Jack's advice:
http://forum.xda-developers.com/wiki/index.php?title=Nexus_One/Guides_%26_Tutorials#Unroot_.2F_Restore_your_Nexus
Sent from my NookColor using Tapatalk
just if you want to know,
i've downloaded the frg33
and i HAVE NAMED it CORRECTLY!
YET, IT doesn'T WORK
im not a retard!
after the 2 min period of searching, which is step 7, my phone goes back to the same screen
CID incorrect!
Update Fail!
Do you want to reboot device?
<VOL UP> Yes
<VOL DOWN> No
this shows up a couple of times also
Why ask for help if you're not going to do what people tell you?
With a unlocked bootloadet flash a custom recovery.
Reboot DIRECTLY into that.
Wipe and flash any rom you want.
If you don't know how to do any of the above search or read the wiki.
Sent from my Nexus One using XDA App
As albundy2010 suggested - if you have the bootloader unlocked (I didn't notice that part in the OP), just follow the guide for unlocked bootloader - fastboot flash all the partitions on the device manually. The guide is in the same place, but a different one - this time use "for unlocked bootloader".
tHANKS man!
I was such a f-in idiot...
now i can finally boot into the recovery..
I got it.. thanks guys
It's a tough flashing world out there, hey rec
I am glad you got it working
Hey guys,
First off, I am a complete noob with all this tech stuff. But I felt a little adventurous and wanted to root my One V.
I managed to unlock the bootloader and also root my phone. Phone was working perfectly fine after this. So next I tried installing some custom ROM to change the GUI. I clearly must have done something wrong because my phone is now stuck at the boot screen. I did a google search and stumbled across a page which said I have to go into Recovery mode and Back up or something. I followed the instructions and I'm still facing the same problem. It just won't go past the boot screen. I have no clue what to do next. Now I'm wondering why I even tried to do all this.
What do I do next? Please keep in mind that I'm an utter noob.
Hi XDA community,
I'm scared out of my mind. Tried rooting for the first time ever, but don't actually know what I'm doing. Using various guides I found in these forums, I:
1. Used HTCdev to unlock the bootloader
2. Used ADB to install TWRP 3.0.2-0
3. Used TWRP to install UPDATE-SuperSU-v2.76.zip
Once that finished, my phone tried booting up (the white HTC logo) but now it has the red development build text at the bottom.... and then it gets into an infinite boot loop.
I don't know how to fix my phone. Please someone here with guidance, please help.
I've got the same identical issue.
I was able to get out of the boot loop by holding volume up and power, and I got back to download mode. From there, since the SU update I tried to install boot looped me (I was following this tutorial), I jumped ahead and just installed cm13 as I was planning to.
This install went fine, but then I ran into the issue of the rom not recognizing my sim card. I've been researching this problem and I guess I need to update my baseband? I tried for hours but I do not know how to accomplish this, and couldn't figure it out for the life of me. This thread on the cyanongenmod forum seemed to be the closest thing to help I could find, but still it didn't help very much.
So at this point now I'm trying to back out and unroot my phone and get everything back to factory settings; it doesn't feel worth it anymore to me since I've just had trouble every step of the way. I've been trying to follow this post to get back to at least a usable factory rom. But I can't even get this one to install because I cannot access my phone through adb while it's in download mode. Furthermore the instructions are just confusing me because I'm not so versed in the nomenclature of these procedures.
Is there anyone that can help me get back to complete stock t-mobile sense? Or if not, help me get my cm13 rom to recognize my sim card so I can at least have my phone working in some capacity? I'd be tremendously grateful of either. I'm really in over my head here and quite scared I won't be able to figure this out.