so I got a new (new to me was used) g1 today from a friend at work and everytime I turn the phone off with the power button it only starts in boot loader without pushing the camera button it does it on its own if I take the battery out and wait a minute or two then it will boot and run normally
history of the phone
not sure if this was a problem with previous owner he said that for the 3 months he owned it he never turned it off and so never saw the problem (thats crazy that he kept it charged all the time for 3 months)
phone was off when I got it running the latest ota firmware
I turned it on into bootloader and downgraded to rc29
downloaded telnet never got it to connect
while playing with telnet noticed the problem of booting into bootloader
downloaded flashrec.apk and put 1.4 cyanogen recovery on
made nandroid back up
did hard spl from the g1 faq
put on ota-tmobile cupcake with root
put expansion on for ota-tmobile cupcake with root
bump I will be back tomorrow afternoon to see if any one knows thanks everyone
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.
I have a G1 that was replaced under warranty earlier in the year. I rooted it as I had my preordered G1 that it replaced and it has always acted weird. I'll get freezes during use, it will randomly reboot, it will lock up when sleeping.
It seems as though i can do a fix_permissions or mess with some setting and it will be fine for a while, then crash. This usually happens when my wife is trying to call me and she's furious that my phone is dead - again. The weird thing is that I would update the software, the phone would act like **** for a few days, then calm down and work as it should - but still screw up once every two or three days.
It has been really pissing me off lately, I tried to completely blow it out and go totally back to square one with the DREAIMG.nbh. It never once crashed during the 12 hours I was running RC29. I rooted it and as soon as I installed the Cyanogen recovery image, it started acting weird.
I did the usual steps of run telnetd, reflash recovery, then reboot. That was fine. When I went to flash DRC83 and flash CM 4.2.8.1, it started hanging at weird times inside of the recovery console.
Once was when I chose "Flash from update.zip" by mistake, it hung.
Another time I went to flash DRC83 and it hung before it started writing.
Then it would finish DRC83 and hang at the main menu.
Random reboots.
Finally I got DRC83 and 4.2.8.1 installed and it rebooted to Cyanogen's ROM like it should. I was high-fiveing myself and everything (no, I wasn't) but it was short lived; it hung after the 3rd app installed from the Market.
WTF? Do I have a phone that just doesn't want to flash? It seems whatever it is that doesn't like my phone lives inside the recovery partition as well.
My phone says this at the tricolor screen:
DREA100 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-1.22.12.29
Sep 2 2008
This phone came with RC31 on it if I remember, I think it was a month or two in to when they all came with RC31.
I would like to re-root the phone since I like getting all the cool updates being pulled from the newer builds. If it can't happen, I'm just going to OTA the damn thing and use it unrooted but reliable and get less crap from the wife.
when flashing the cyan rom you use the 1.6 image from HTC,which can no longer be found there.You should be doing this:
1.Wipe
2.Install 1.6 APD...Blah devphone..blah
3.install cyan right after without rebooting
4.now reboot
5.should goto rec mode
6.reboot once more
That's pretty much what I had done except using the 1.6 image with the radio and recovery partitions removed, from the cyanogen wiki. The problems seem to start with the new Recovery partition.
I just received the 1.6 OTA overnight and I'm going to let it run for a few days to make sure that the phone itself isn't defective in some way.
It may be that there is some component in the phone that is of borderline quality and just can't handle something in the Cyanogen ROM but works with OTA software otherwise.
Ok, I received the 1.6 OTA and after that, the phone started acting ****ty. Not nearly as bad as what it was doing when Rooted but for sure acting the same way. I had about 12 hours before the phone locked up in the Market, then froze while asleep, then rebooted when I hung up on a call. Apparently the 1.6 ROM just hits the phone harder than 1.5 did.
I have put in a request for a warranty exchange and should hopefully have a new phone this coming week. I'll let it run unrooted for a few days to make sure it's OK, then I'll root it.
Your radio version is out of date from what I see.
That was the RC29 radio, it is now at 2.22.19.26I with the 1.6 OTA.
It is pretty remarkable that a phone that had NO problem with the 1.5 OTA and occasional screwup with the 1.6 OTA would totally crap itself when running Cyanogen's 1.6. I guess he's right when he says that it can cause problems. It certainly made a phone with marginal HW problems go over the edge.
starting a couple days ago, my g1 would restart on boot for no reason. It gets into the phone OS and says preparing SD card and then it vibrates and restarts. I've even unrooted my g1 and rerooted just to make sure everything is perfect and nothing is wrong using the cyanogenmod wiki. I have the latest radio/dangerSPL yet this keeps happening. my phone only boots when its not rooted in 1.5 or 1.6. I'd give more info, but I need some help doing that. I even made a useless video for you to watch my problems. http://www.youtube.com/watch?v=kyAOAPAhq2U
(While I was in a rooted DOK2 FW - Tmobile SM-910T3)
So heres the deal, trying to walk around I wanted to mock my location but was interrupted and placed my phone in my pocket which "locked" the bootload.
I managed to flash the stock image and unlocked the bootloader loaded TWRP and restored from my backup
Now this is where hell starts. It looked fine until I rebooted my phone.
Symptoms:
On a reboot the phone will not turn back on after I opt to reboot my phone
At this time the phone will not turn back on (i noticed this when i rebooted while plugged in the charging light was not on) I pull the battery for a few minutes to turn it back on
When I power the device back on sometimes it is stuck in the Bootloader Screen (unable to get into recovery and download) so I need to pull battery wait and turn back on
When the device does boot I can get into recovery and download mode on when it boots properly
Sometimes its stuck on the tmobile screen and I need to reboot it.
When the phone is operational it will occasionally lock up and I will need to wait a few minutes before the device is able to respond.
Any ideas what I can do? I had thought flashing a stock rom (from sammobile) would fix the boot issues
As of now:
I've recently flashed to the new Tmobile marshmallow stock via odin. I am still seeing these symptons. I'm currently installing the Maximum Overdrive Rom hoping it will fix some issues
Still seeing some of the same issues. Stock romantic and a deflated romantic did nothing. Is there a way to reflash a bootloader?
I'm having the same issues....I have odined back to stock dok2 twice....I think the pe3 bootloader files are floating around the forums somewhere...http://forum.xda-developers.com/showpost.php?p=67514260&postcount=4
When my N4 boots up I occasionally get the emmc boot error...I brought it to tmobile and explained the issue to the rep. She brushed it off as being my battery. I know its not my battery as its a 3 month old 10000mah zerolemon. So I'm going to just limp this phone along until its time to jump to the Note 7. I've been flashing roms since the golden era of windows mobile/palm os days and on android since my G1...And some rookie rep who doesn't even know how to put a phone in recovery or download mode tries to brush it off as the battery.... My girl has the sprint note 4 and hers did the same thing, she took it to a store the rep ended up giving her a fully functional refurb... (which is the right thing to do if the phone has emmc failures) Anyways I hope you have better luck than I've had
i had the exact same issue as you guys started 2 months ago got worse overtime now my emmc is dead it wont write anything or even go into recovery or download i had tried all types of roms stock firmwares even took the phone apart swapped the power button and bought a new battery now my memory is dead and i can actually say its the emmc chip, seems to me these note 4s are starting to die i bought mine when it first came out in 2014 kind of feel ripped off but best phone i ever had imo