Related
Hey guys,
I upgraded my G1/Dream from an older cyanogen version, to the newer one 4.2.15.1
and now for some reason my phone keeps restarting Any reason why ?
Can you please tell me how to fix it?
I've taken battery out & Also 'green+home+red' . Same keeps happening.
It restarts when it wants, can be 2 minutes, 10, 30.. but lately ever 1 minute or so..
What can I do?
Bump
bump
Anyone?? please
I'd recommend a full wipe and reinstall of your desired rom from scratch. Sounds like kernel panics to me.
my g1 was freezin up alot on cm4.15.1.... before it died and i had to get it replace....try unrootin and then root again and if it doesnt work it could be a hardware prob.
Tone-E said:
my g1 was freezin up alot on cm4.15.1.... before it died and i had to get it replace....try unrootin and then root again and if it doesnt work it could be a hardware prob.
Click to expand...
Click to collapse
Why would you completely unroot and reroot? That's just too much work.
Wipe, and reflash. Also, a few apps have a problem with custom ROMs, try disabling apps that run in the background one by one until you find that your phone no longer reboots.
However, if you didn't wipe, I highly recommend that as the person before me said.
First, thanks for the look.
Second, I have read the related threads to this, but none are like my special situation.
Twice I've had to get a warranty replacement for my Captivate after trying to restore from ODIN. Both times, the restore starts, then freezes mid-process. I've let it sit for an hour both times and nothing changes. Frozen. I have no choice but to unplug the USB cable, and remove the battery. The phone is then dead. I mean DEAD. Powered off & completely unresponsive. No power on. Screen doesn't light. "USB device is not recognized" when plugged into a PC w/ drivers. NODA. KAPUT.
I've successfully flashed w/ ODIN before, so I have no idea why certain times it decides to stop.
I'd like to use Clockworkmod to flash in between roms, but after re-flashing I always get the boot loop (AT&T screen is as far as it gets.) I try re-flashing to the original ROM, a backup of the stock ROM. Nothing works.
I REALLY don't want to try and get a 4th warranty phone if this happens again.
I know Clockworkmod requires a compatible ROM, but I've never seen one (Perception, Cognition etc.) that says it is. I know you need a backup of the nanroid, but isn't Clockworkmod supposed to do this?
Can someone straighten me out so I don't get yet another bricked phone?!
Thanks.
EDIT: Basically, I can flash a custom ROM just fine using Clockworkmod. Except when ODIN decides to be a *****, I can flash the stock ROM back, then another custom ROM. I want to flash from one custom ROM to another (or a backup of the stock ROM) without having to rely on a program that's bricked my phone twice!
Thanks again.
had this happen to me one night while trying to change roms. I used ROM Manager to flash back to a stock backup I made and stuck at ATT logo. got the phone into download mode and it would go a little then the screen would turn green or blue or orange, sometimes black and freeze running odin. I just kept at it, leaving the battery out for different intervals, holding volume keys with usb plugged in and then inserting battery. took about 30 tries but it finally took and odin flashed me back to stock. Just don't give up, try try again...you may get lucky
Development, I think not
Sent from my SGH-T959D using XDA App
bulletproof1013 said:
Development, I think not
Sent from my SGH-T959D using XDA App
Click to expand...
Click to collapse
Well, i figured since it was about ROMS it would belong here.
If there's a better place then move the thread.
bulletproof1013 said:
Development, I think not
Sent from my SGH-T959D using XDA App
Click to expand...
Click to collapse
NOTHING like throling auseless thread int he wrong section ... except we ve been politely asked by the admins to stop doing it so I will refrain from doing it ..
to answer you question , it seem like
the usb port/ card or even motherboard , ( might also be a bad usb cable) is at fault here , if you have a jig ( witch I advise you to build one asap if your into flashing roms ) I would never leave my phone plugged in to my pc when somethign is not responding . for example when flashing a kernel or even back to stock I know exatly how long thisi suppose to take and if its hanging I will unplug it and use the jig to go back in download mode and restart again , if your more cautious ten me then dotn , but nothing takes longer then 5 minuttes to flash on your phone so if by 10 minutes i dont work then your screwd so not worth letting your phone drain its battery ..
btw any questions belong in q&A no matther how relevant they are .
Without meaning to be rude, have you consider how reliable the computer you're flashing from is?
If you've seen the same behaviour twice, flashing two separate phones, then it seems likely that there's something specific either to the PC hardware (cables, ports), software (Odin, downloaded ROM, USB drivers) or method (human error of some kind) you're using.
Is there anything about your setup which might interrupt data on the USB line to the phone as it's being flashed?
Hope this helps,
AoN
i read on another forum somewhere that you cannot flash a stock backup from rom manager over a custom rom. that rom manager does not back up the kernel/modem etc...not sure how true it is, but I know the only time this ever happened to me was when I flashed a stock backup from ROM manager over a custom ROM.
DAGr8 said:
NOTHING like throling auseless thread int he wrong section ... except we ve been politely asked by the admins to stop doing it so I will refrain from doing it ...
Click to expand...
Click to collapse
For every non-development thread that is posted, one actual relevant thread gets bumped to page two. It hurts development, our at least slows it down.
Of course, that doesn't mean you should be rude or anything.
Sent from my GT-I9000 using XDA App
Also, if you're not doing it already, make sure you plug your USB cable into a USB port that is directly attached to your motherboard. Like the ones in the back. Many people have had issues using the front side USB ports or even going through a USB hub.
Also I guess it's worth it to reinstall drivers and do the normal windows type troubleshooting.
Now just had a little problem. I updated to Darky's 8.1 no wipe version. It updated fine but the first time it booted, it froze. Now it keeps doing a boot cycle over and over again. I see the i9000m screen but I do not get to the S logo screen or in this case the transformer screen because it reboots. Can you help me plz? Thanks.
Zink6 said:
Now just had a little problem. I updated to Darky's 8.1 no wipe version. It updated fine but the first time it booted, it froze. Now it keeps doing a boot cycle over and over again. I see the i9000m screen but I do not get to the S logo screen or in this case the transformer screen because it reboots. Can you help me plz? Thanks.
Click to expand...
Click to collapse
try a re flash of another ROM preferably a stock ROM then start all over again, similar thing happened to me earlier, i am quite new to all this but i dont know if its the kernel or lagfix i had what caused this...
i re flashed back to froyo and then installed darkys ROM then re installed my kernel last.. all is good (for now)
worked for me first time but when i went to sgs tools to upgrade your apps ie gallery, camera, it said no busybox installed but went ahead and done fine in v8.0 and i see that cwm changed from red to green too went to market for busybox to download it but when it goes to install phone just reboots all the time mmmm...
Easiest way out of cycling boot:
pull battery
place it in
bring phone in download mode (not recovery!)
prepare Odin with a stock ROM
connect the phone to your PC and give it a kick thru Odin
When done feel free to switch again to Darkys (8.0) with wipe (you will loose data) and afterwards upgrade to 8.1.
stepsch said:
Easiest way out of cycling boot:
pull battery
place it in
bring phone in download mode (not recovery!)
prepare Odin with a stock ROM
connect the phone to your PC and give it a kick thru Odin
When done feel free to switch again to Darkys (8.0) with wipe (you will loose data) and afterwards upgrade to 8.1.
Click to expand...
Click to collapse
YES !!! i agree, it is a pain.. but we love our phones and we would do anything for them its always best to flash back to standard FW if you ever get a problem...
I myself experienced this. Whenever I installed a new software, it would just boot. I got fed up because darky's forums are also down and there is no discussion. flashed doc's rom. Now everything is fine.
...mh... but it's not caused by Darkys ROM. This cycling boot feature may appear at all ROM, at all lag fix actions and so on. It depends how proper you interact with phone- and ROM-features while configuring. A lil disturbance during your session (by you or battery issue or whatelse) or a not so well prepared basic from where you start and your unlimited-feature-wishlist-and-paint-it-golden-one-click-action is enough to interrupt the whole thing and run into trouble.
It was and is all the same - since DOS or C64. And it will be the same, even when iPhone is on level 12.x or Android will be able to beam you elsewhere thru the barcode scanner.
It's a game. Nothing more. And game means lot of fun - and in the beginning a certain thrill when your phone stuck first time and you are thinking: "... f*ck... bricked..."
yup same for me
cycle boot thing
didnt enable download mode before that....
can get into debug screen thou but wiping it doesnt help
anyone with a suggestion on what i can try? warrenty = off so im screwed otherwise
anyone with a suggestion on what i can try? warrenty = off so im screwed otherwise
Just tell the warranty guy darky screwed it .
OR
http://forum.xda-developers.com/showthread.php?t=853950
jje
cant even boot the phone mate
so ehm i dont get it....how can odin help me ?
is there any way of getting it into download mode still when it doesnt boot up? i heard about that JIG thing they made themself...isnt that just like the microusb cable that comes with it to the pc? i dont get it sorry if im trippin but im maddd at myself for even trying this lockscreen thing
http://forum.xda-developers.com/showthread.php?t=819551
jje
Thanks guys for all the replies. Now I did try flashing a stock rom but with no results. Was still having the same thing happening to me. If you guys can give me the link to the files you used to solve this problem, that would be great. Also just for your information I have a Bell i9000m unlocked running on fido. And NO its not an sd card failure lol.
As for DarelSteilz85, I did make one of those JIG usb for myself. It easy, just get the micro usb and strip it bare to the point you can see the pins on the usb which usually are connected to the wires and get a resister to connect one pin to another. Now for which pins, I remember it was 4 and 5 that you had to connect through the resistor but double check as I am not sure. Also the resistor has to be a certain level which I forgot so double check that also. Good luck.
http://forum.xda-developers.com/showthread.php?t=853950
What i use for problems .
jje
hey guys i have a captivate that i tried flashing and was successful then i tried again and the screen went black. im not sure if my battery died during the process or what but idk what to do. I cant get into recovery mode, i can only get into downloading mode but none of the odin's ive downloaded have recognized my device today. they worked fine yesterday. then i tried "hemidall one click" to try and get it back to stock but no luck. also when i try to power on I get the "Cornkernel" loading screen since that was the kernel i had loaded when it was working, but it fills the bar then shuts off. so it seems like im going to be at the mercy of a computer program since i am unable to access anything on the phone, right? I recently upgraded to gingerbread before all of the flashing of the new roms. all i want is to get back to either froyo or gingerbread, i dont really care, heck ill even take 2.1 at this point. if anyone knows whats going on and can help me thatd be great.
Thanks
Remember to use a rear usb hub for destop and run as admin. Heimdall will mess up your odin drivers.
You may also want to check out the captivate connection issues thread.
Also, to clarify further on prbassplayer's point about Heimdall, it will write its drivers over the drivers assigned to the USB port you are plugged into when it detects your phone. So if you have 4 USB ports and you use port 3 for Heimdall, it would look like this:
1 - Odin port
2 - Odin port
3 - Heimdall port
4 - Odin port
All this means is that you'll need to be aware of the port you used with Heimdall, or just reinstall the odin drivers (they'll overwrite the Heimdall setup).
OK so i tried what you mentioned in that thread on the connection issue and unfortunately it didn't work. is there a way i could start fresh? like delete all the drivers from my computer and then try it again, or do u not think that would work? im open to any ideas/suggestions right now because i hate having an extra paperweight and the thought of buying a new phone.
Don't know if this'll help or even why it worked for me but, when I had problems with odin recognizing my phone, I reinstalled/repaired samsung kies and odin would work for at least one flash.
Note: used full odin (not oneclick)
Good luck
hey guys thanks a bunch i finally got it to work. i had to use a different computer like you said. What a great feeling to have a functional phone again..
Thanks Again!!
So i got the phone back up and running android 2.1 and I would like to get it back to the stock 2.3 I had before the whole mess of rooting and stuff. but when i try to upgrade with kies or straight on the phone it ends up failing and telling me to try it again. any ideas why this is happening? or how to fix it.
blackjack54 said:
So i got the phone back up and running android 2.1 and I would like to get it back to the stock 2.3 I had before the whole mess of rooting and stuff. but when i try to upgrade with kies or straight on the phone it ends up failing and telling me to try it again. any ideas why this is happening? or how to fix it.
Click to expand...
Click to collapse
Kies sucks lol
look at my sig the first "go to" has the One Click Odin file to get you to stock and rooted 2.3 ...should take no more then 5 mins to do it
the link on that page for the 1 click odin doesnt work.
Try looking >>HERE<<. There are more one clicks there than you will ever need (hopefully)
Thanks I think I might try one of those. But considering what happened earlier in the week i want to clarify/ask a few ?s about that page. How do I know which Gingerbread to use of the 3 listed? How do I know whether or not to click the one with or without the bootloader? I'm new at this with android but I used to flash roms on my old windows mobile htc TILT.
blackjack54 said:
Thanks I think I might try one of those. But considering what happened earlier in the week i want to clarify/ask a few ?s about that page. How do I know which Gingerbread to use of the 3 listed? How do I know whether or not to click the one with or without the bootloader? I'm new at this with android but I used to flash roms on my old windows mobile htc TILT.
Click to expand...
Click to collapse
if you have never flashed GB bootloaders, you need to. Just oonce will work from that time forward. After you flash bootloaders, it's best to avoid them. A bad bootloader flash is one of the few things that will turn a Captivate into a paperwight. About which GB to use, I would say KK4. Its the same as the Official KK4 that was released. So to recap, flash bootloaders only once, then use no bootloader packages after that.
Im not sure if I unlocked them or not honestly. I know i had the phone rooted at one point and was running Cerberus rom. is there any way for me to check?
If you don't know, flash them.
ok i apologize in advance if this is a stupid obvious question..i got the odin one click and i was looking at the page u referred to me to and im wondering what the kernel is for? you cant place it in the odin one click obviously so is that just to keep things together or do i actually need it?
The kernel links are just to use if you want to root the stock rom. You have to use full Odin for those. Stick with the one click until you feel more comfortable in flashing AND do a lot research before your next flash.
so i got the KK1 gingerbread working and everything seems to work fine but now my data doesnt work. So I cant get ATT 3g or edge or anything the only internet i recieve is wifi. anyone know why this is? or how to fix it. ive tried a reboot and nothing ive tried changing the settings under network settings.
OK folks, I know some of you are going to jump straight down my throat, but please, back off and stick to the friendly forums that this used to be where anyone would help anyone.
the story so far is that I once loved my Nexus One, I've had it since launch, I have ran Cynogen Mod 7 for a couple of years, I have had MUI roms running, I have played with various kernels, updated radio, upgraded hardware, all was going wonderfully.
the one thing I could never get was full SU!! Heck knows why!!
I then started getting random problems and downloaded the original google frf83 software and flashed the phone via update.zip using amon-ra recovery.
I thought all was well after this, as my phone received 3 OTA updates and now my phone is on...
Android 2.3.6
Baseband 32.41.00.32U_5.08.00.04
Kernel 2.6.35.7-59465-g42bad32 ([email protected] #1)
Build GRK394
I noticed that in the Status (settings) it was displaying my old sim card number, which is not the number for the sim in the phone now. his I thought was odd and that something had gone wrong.
So as most of us would do, I went to boot AmonRa recovery and it wasnt available, it had been overwritten with the default recovery; ok lets just ADB and reflash it, I hadnt used ADB for a couple of years because I did everything through AmonRa's awesome recovery!!
So off I go, install the SDK, all the appropriate packs including the USB driver, just like I did when I originally flashed the phone with the recovery image!
But an old problem came back that I hadnt even been bothered about because I always put stuff on SDcard via a card reader!!
I have had consistent problems with my nexus one for some time now in regards to the USB drivers, no matter what I do the phone will not install and I believe it could be some conflict in the device.
I am running Vista Ultimate (fully registered) and no matter what I do I cannot get the Nexus One to install. It will only display as unknown device, which is absolutely useless.
I have browsed every post and tried everything I have found, and yet nothing is working. I have used devmgmt, I have tried the roll backs, I have tried to install every driver available to get it working. I have uninstalled the device, updated drivers after fresh install attempts, I have even formatted my laptop thinking it may have had a corrupt OS and bought Vista Ultimate.
I am not a complete noob and I have been around these forums for some years, but I never thought I would have to cry out like a 4ucking Noob with such a seemingly simple problem, but it is not simple, I have done everything I can possibly find!!
I must get the USB working in order to get the recovery back, I can access my phones default recovery but it will not work when trying various roms as update.zip!!
I have tried the terminal commands on the phone to install the recovery.img but I do not have SU access and the phone point blank refuses.
I have attempted to change and remove the recovery files reffered that are causing the revert to default recovery, but shock.. I cannot delete because of insufficient permissions. I cannot ADB because the USB driver refuses to install.
So if I cannot change the files due to permissions, I cannot ADB because of USB, I cannot get to Ra's recovery because of bootfiles, I cannot use default recovery to update.zip... I am absolutely losing my mind and I'm going nuts browsing the forums for the second week running, yes I am now on day 12 of trying to fix this problem and at a complete loss...
Can someone please help??
I will even allow remote access to pc because I am that desperate to resurrect my beloved Nexus One.
I also have a Galaxy I9000 without 3 button download mode but that is an entirely different story!!
Please just someone, come to an oldskoolers rescue, and yes PAYMENT will be given to the knight in shiny armour!!
You could try on another computer which doesn't run Vista
tommert38 said:
You could try on another computer which doesn't run Vista
Click to expand...
Click to collapse
Or just use fastboot instead of adb...
His Nexus One isn't recognized by the computer, so that won't help unfortunately. Also, I've never heard of build GRK394..
tommert38 said:
His Nexus One isn't recognized by the computer, so that won't help unfortunately. Also, I've never heard of build GRK394..
Click to expand...
Click to collapse
Install the drivers for fastboot already Jeez and then read How to use android for dummies.