Related
Having a problem here. Today I got a refurbished dinc, and tried to root w/ unrev. 3.2 and it went all the way through the process up to the point where it says waiting on reboot (could take 5 mins.) After that U.R said it lost its connection with the phone and rebooted. since then its been stuck in boot loops. S-off was never achieved and clockwork wasn't installed. I've tried resets and a 2.2 pb13img and nothing can stop the loops. Once in a while of random resets and fumbling around in the stock recovery it will boot to the phone program screen to call *228. It reboots and loops right after it goes to mount storage. I've tried taking out the card thinking it might be that.
It's a amoled screen.
I've rooted before and have no issues on my other dinc.
Plz help.
Sent from my ADR6300 using XDA App
riley614 said:
Having a problem here. Today I got a refurbished dinc, and tried to root w/ unrev. 3.2 and it went all the way through the process up to the point where it says waiting on reboot (could take 5 mins.) After that U.R said it lost its connection with the phone and rebooted. since then its been stuck in boot loops. S-off was never achieved and clockwork wasn't installed. I've tried resets and a 2.2 pb13img and nothing can stop the loops. Once in a while of random resets and fumbling around in the stock recovery it will boot to the phone program screen to call *228. It reboots and loops right after it goes to mount storage. I've tried taking out the card thinking it might be that.
It's a amoled screen.
I've rooted before and have no issues on my other dinc.
Plz help.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
What is your HBOOT version?
Hboot 0.92
Radio 2.15.00.07.28
Clockwork 2.5.1.2
Un.Rev. 3
Un.Rev. Forever
Incredibly re-engineered 2.2
Update -
Managed to get Un.Rev. to install with cw. And installed a Rom. Now I still get random reboots. Everything will be fine...ill update and install a bunch of apps. and I can use the phone for a while. Then all of a sudden it reboots over and over. To get it to stop, I have to re-do everything. Wipe cache, wipe dalvik, wipe battery stats, data/factory reset. I get an error after dalvik clear though "can't mount /dev/block/mmeblk12 (file exists)"
That puts me to square one.
Everything will be ok and then.....reboots...randomly at different points. sometimes right away and some times after an hour or two. No real pattern. I have a gut feeling it has to do with onboard memory?
Are you overclocking? What kernel are you using?
Try installing a different kernel, make sure it is a sense based kernel as you are using a sense based rom.
You can pick one from here - http://forum.xda-developers.com/showthread.php?t=866736
No I'm not over clocking. And I'm using the kernel that came with the Rom.
I do, however, seem to remember reading something about dincs overheating and rebooting until they cool. Maybe this is the case with mine.
I had the exact same issue when i received my refurbished phone. It is not uncommon that these issues - and others, will occur. Even before rooting i was having the issue.
I did notice that it will happen when i pushed the phone a bit, like talking and trying to download something from the market at the same time.
My suggestion is to unroot, everything stock, test the phone and see if it happens again. The Verizon representative tried to reset the phone and it started boot looping right in front him! And then they order another refurbished phone, which also had issues. Long story short, they gave me a new phone after i begged. (thank u VZ local store, which btw i sent a few customers your way )
According to some inside people i talked to, the 3rd party companies (or individuals) that fix these phones do a terrible job at it and the Verizon stores see quite a few people everyday with similar issues. I have no way of verifying this, just what i was told.
riley614 said:
No I'm not over clocking. And I'm using the kernel that came with the Rom.
I do, however, seem to remember reading something about dincs overheating and rebooting until they cool. Maybe this is the case with mine.
Click to expand...
Click to collapse
I would still try another kernel first, HeyItsLou or Ziggy IMO. If you still have the problems then, flash back to complete stock and take it to Verizon.
Yea, ill give that a try. If I have no luck, ill send it back. After unrooting of course.
Sent from my ADR6300 using XDA App
Riley, were you able to fix it? I'm really interested in some analysis of the problem and investigating issues with refurbished phones boot looping. Someone else just posted a similar problem.
Nah. No luck here. Still randomly looping. Nothing seems to have an effect in when it why it loops. It'll loop even w/o any apps installed.Even after a "fresh" install of a rom and system wipe.
Gonna send it back.
riley614 said:
Nah. No luck here. Still randomly looping. Nothing seems to have an effect in when it why it loops. It'll loop even w/o any apps installed.Even after a "fresh" install of a rom and system wipe.
Gonna send it back.
Click to expand...
Click to collapse
Sorry to hear that, as i said i had the same issue and i had to get another one. if you get a second "lemon" refurb go to Verizon and talk to a manager. They might do an out of the box replacement and put it in the system as defective under warranty. Good luck.
Hey Guys-
Couldnt find a thread similar so I'll start my own.
6 days ago i updated my rom to CM 7.0.3 and the newest version of Savaged Zen Kernel (dont remember version). Everything was fine until leaving work last night and it began to boot loop in my pocket while driving home. Phone had worked as normal all day (web, text, talk), no changes made to phone either. The only thing i can do is get into the bootloader (by holding power and volume up). Although when i try to enter recovery from there to flash a backup, it just puts me back into the boot sequence again. Any help guys?
http://api.viglink.com/api/click?fo...ersonic-v2.3 - xda-developers&txt=PC36IMG.zip
download that rename PC36IMG and put on root of sd card now go into bootloader go into fastboot and it should stay start update press volume up for yes and then when its done put yes it gonna reboot now take out battery put it in evo again and go into bootloader againthen from bootloader go into recovery from there and you should see amon-ra and from there try to do a nandroid or flash a new rom
I got the update to go through, but now when it prompts me for a reboot it just keeps looping. Even when i select no i dont want to reboot and then try and go into recovery, it loops.
try taking out battery for 2 hours and try again
cool will let it rest and let you know the results when I try again.
ar4senal said:
cool will let it rest and let you know the results when I try again.
Click to expand...
Click to collapse
Do you have insurance on your Evo? Is it still within it's 1 year warranty? It sounds like you got the eternal bootloop of death. Is your bootloader S-on or S-off? The condition you're experiencing is unexplained and usually not fixable. running an RUU is your only hope, and if that failed...your pretty much out of luck.
See this thread: http://forum.xda-developers.com/showthread.php?t=1009672&highlight=boot+looping+no+recovery+access
Yea I'm pretty sure it is still under warranty. I got the phone last August. My bootloader is S-Off. Ill check that thread out.
All you should need to do is wipe and re flash cm7... Our write and re store a back up
Sent by Supersonic!
could be the battery is bad and it is just not getting a constant connection, thus boot looping. i had this issue with a bad battery, swapped it out, no problems
For the record, I mis-spoke...
Sent by Supersonic!
Yea Its not taking anything I flash onto it. No way to get the S On back either. After reading that thread its looking like I am gonna have to somehow fully brick it and take it back to Sprint for a new one......UGH!
First, there are a lot of instances of this happening. Well, not a LOT, but there are several threads about it.
Anyhow, give me a few minutes to upload a file to my mediafire. It's a walk through someone on here wrote that is very detailed and it takes some work, but if everything else fails, it has been known to work.
I'll post the link in a few.
http://www.mediafire.com/download.php?9zc41jsfs7sm1qf
That's it.
You said that you installed the new recovery and still getting loops. That's because you didn't do anything in recovery. Go into recovery and try wiping cache/dalvik cache. See if it boots. If it doesn't go back into recovery go to the wipe menu and wipe everything except SD card and rotate settings. Reflash cm7 and it should work. Loops are a common thing and easy fix
P.s. I don't know if you did this but ill throw it in there anyway. You have to wipe cache and dalvik cache when flashing new kernels.
Sent from my PC36100 using XDA Premium App
ar4senal said:
Yea Its not taking anything I flash onto it. No way to get the S On back either. After reading that thread its looking like I am gonna have to somehow fully brick it and take it back to Sprint for a new one......UGH!
Click to expand...
Click to collapse
You can get s-on with 2 files one you flash in recovery the other in the bootloader (the same way you updated to amon recovery). I would post a link but can't cuz I'm on my evo. Just go into the evo development section and there is a thread like 2nd or 3rd page maybe farther back that is called "how to unroot in 2 steps" or something like that. Just did it for a friend 2 days ago so I know it works.
Sent from my PC36100 using XDA Premium App
The issue is that I cannot get into recovery AT ALL. Have tried numerous things. It just wont go into recovery. I bit the bullet and took it into the Sprint Store, they pulled up bootloader and never noticed the S Off at the top. Unfortunately my phone had undergone some sort of water damage. (?) So they were unable to do anything for me, looks like ill be paying the $100 deductible for the refurb.
On a side note the tech at the store told me he has been harvesting parts from evos and epics, and has amassed quite a collection of odds and ends, and that if I ever needed a screen replaced, etc. He would do it under the table for a small charge instead of going through the insurance company. Since i still have the phone ill try all these things again just to see if I can get it working again.
@HipCat- Posted before i read your post....Ill try those steps here in a minute. Thats something I have not tried.
PhxkinMassacre said:
You can get s-on with 2 files one you flash in recovery the other in the bootloader (the same way you updated to amon recovery). I would post a link but can't cuz I'm on my evo. Just go into the evo development section and there is a thread like 2nd or 3rd page maybe farther back that is called "how to unroot in 2 steps" or something like that. Just did it for a friend 2 days ago so I know it works.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
I cant get into recovery.....
Hi,
I need some help please. Running CM7 7.0.0, using RomManager and ClockworkMod 3.0.0.5. I've been very busy with work and school so have not had much time to play with the phone, so two days ago I wanted to checkout one of the nightlies and installed nightly#101. Then I thought I haven't updated the PRL in a while and dowloaded the stock odexed version 4.20 from RomManager. I updated and then went back to the nightly#101.
This time though everytime I tried to make a phone call I would get a "Call has been lost" message. I figured must be a bug in this nightly or something. So using clockworkmod went back to CM7 7.0.0 backup. That's where my problems started. When the phone came on it was not reading the SD card (I tested it in my girlfriend's phone and it is good, I borrowed hers and the evo didn't read it), I could not turn on the bluetooth and when I rebooted it vibrated 5X and then the green light would blink. I though maybe the battery is dead, so I let it charge for 30 mins and the phone came on. I tried to reboot into recovery so I could reinstall the backup, but it would vibrate and blink, and sometimes it would come on and others not, almost randomly it seems.
Today, I found this fix for the SD card http://forum.xda-developers.com/showthread.php?t=1017387 and it worked.
However, the bluetooth is still not working and can't go into recovery. It seems that the only time I can get the phone to turn on and vibrate and blink is if I 1)put the battery in, 2)Press the power button and 3)plug the power in. Don't know why that works.
Any help would be greatly appreciated!
Recovery works now!
So I turned the phone on, went to RomManager and reflashed clockworkmod and tried to go into recovery from there, but it vibrated and blinked. I took the battery out, put it back in pressed power and vol down together and selected recovery and it didn't work (by the way, hboot.97 and it says s-on even though I had rooted with unrevoked and it was s-off).
I turned the phone back on figured let me try amon-ra since I have an amon-ra created backup in my computer. I turned the phone off, turned on with power+vol down, went to recovery and clockworkmod 3.0.0.5 loaded up.
I tried the reflash my backup and then once it completed, i hit reboot and it vibrated and blinked. Took battery out and put back in procedure again. went back to clockworkmod wiped cache and dalvik (not sure if needed, but figure it can't hurt). Rebooted from Cwm, but vibrated and blinked, and I did my boot up procedure again.
Bluetooth still not working, wifi works, wimax works.
I think maybe I should unroot go back to stock and see if that works. If it doesn't at least I can bring it to sprint and get a replacement.
I love CM7 and don't like Sense or Sprint bloatware.
I see 2 of your problems right off hand; Rom Manager and Clockwork Mod.
Get rid of RM and switch to Amon Ra.
HipKat said:
I see 2 of your problems right off hand; Rom Manager and Clockwork Mod.
Get rid of RM and switch to Amon Ra.
Click to expand...
Click to collapse
i second that!!!
to the OP....what I would try (as a last resort) is factory reset your phone and unroot (run the 2.2 RUU or any other method that unroots), then try to reroot your phone....and flash Amon_RA as opposed to RM and CWM. then reflash the rooted 4.22 ROM, do your updates of radios, prls, etc. and then CM7....that might do the trick. I'm suggesting this cause you said:
topollillo said:
by the way, hboot.97 and it says s-on
Click to expand...
Click to collapse
and question for ya....you had used Amon_RA but then went to RM and CWM?? why???
I rooted with unrevoked and then installed rommanager. i had then installed amonra, because of what i had read about CWM and the rsa keys backups. but went back because of the convenience when flashing roms.
So now i have discovered that the Usb is not working. I tried the fix in the same thread as the sd card fix, but it did not work.
I'm going to go back to 2.2 see if that fixes it and then follow your steps.
If it doesn't fix then will go to sprint for a new phone
Will report back on what happens. Thanks.
do u have an sd card reader
and yeah amon ra is way better than clockwordmod
back to 2.2 bluetooth not working, usb not working, vibration + light still happening.
If I call sprint to get a replacement phone, they will prob ask me to make sure I have the latest software. should I just accept the OTA and see what happens, or am I risking losing root? Does it not matter?
I don't have an sd card reader, downloaded to phone over wifi.
how can s-on happen automatically. I had rooted and had s-off with unrevoked forever?
Apparently you messed something up, because with s-on, you aren't rooted. I would boot into the bootloader, do a clear storage [factory reset], then try unrevoked again. Make sure you have the hboot drivers, installed then uninstalled htc sync.
Went to the Sprint store after an unpleasant phone chat with sprint support. They tried to force the phone to update, that didn't work. So they gave me a new phone.
So I don't mess up this one, could someone give me a recommendation as to how I should go about rooting and installing CM7. Use unrevoked, install amon-ra, flash to my heart's content. Avoid Rom manager. Please fill in some blanks for me, if you have a link to a good guide it would be great. I know there are a lot of great guides here, unfortunately with work, school and the wife I don't have the time I used to have to enjoy my day reading up on the forums.
All your help was greatly appreciated.
Sent from my PC36100 using XDA App
topollillo said:
Went to the Sprint store after an unpleasant phone chat with sprint support. They tried to force the phone to update, that didn't work. So they gave me a new phone.
So I don't mess up this one, could someone give me a recommendation as to how I should go about rooting and installing CM7. Use unrevoked, install amon-ra, flash to my heart's content. Avoid Rom manager. Please fill in some blanks for me, if you have a link to a good guide it would be great. I know there are a lot of great guides here, unfortunately with work, school and the wife I don't have the time I used to have to enjoy my day reading up on the forums.
All your help was greatly appreciated.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Yup, that is fine. Though if the new phone has 2.3 on it, you can't root it yet; if still on 2.2, use unrevoked and good to go.
I had the same blinking light and vibrating probelms on my evo. Mine was overheating really bad. It would run at a constant 102 degrees and when it hit 104 it would shutdown. I called sprint and told them what was happeningand without any questions or problems they sent me a brand new one in the box(non refurbished)
Sent from my PC36100 using XDA App
yesterday a dialog popped up on my phone to update my phone. I clicked on postpone, thinking it would simply just ask me later. I am running RMK's ROM, and now every time I turn on my phone it turns off and tries to update, but fails. How do I stop my phone from doing this? I don't want the update.
Try either doing a data wipe or flashing another ROM then going back if you want to stay on RMK.
I have also heard wiping the cache from recovery works too.
I'm running RMK's Rom and just caught the update notice just now. PITA it limited deferment to 5 days. Earlier today I didn't catch it in time and had to batt pull after it hung. When I went to recover from a recent nandroid backup it hung trying to boot into CWM. I did get into recovery on the second attempt. Just be sure you have a current nandroid of your stuff.
Shouldv'e dug a little more before posting.
http://forum.xda-developers.com/showpost.php?p=16093933&postcount=383
Sent from my ADR6350 using XDA Premium App
Hi, can anyone help?
I am running the most recent inc-deck ROM, with incredikernel. Yesterday I updated google maps from the market, and today, for the first time in months of using inc-deck, for the first time ever since having rooted my phone months ago, I am having force closes of most apps I try to open.
ROM manager force closes also, so I can't restore the nandroid I have on my SD card from there. I try to boot into Clockworkmod recovery, but all I can get into is the stock "white screen" recovery, not the black and orange clockwork recovery screen.
Is there a way I can flash a nandroid manually, without having to go through clockworkmod? Or does anyone have any other idea of how I can get my phone functional again?
Thank you in advance-
Try getting 4Ext recovery from the market if it is available for your phone. Flash it to recovery and restore your nandroid.
Sent from my T-mobile G2 using xda premium
ahadzi said:
Hi, can anyone help?
I am running the most recent inc-deck ROM, with incredikernel. Yesterday I updated google maps from the market, and today, for the first time in months of using inc-deck, for the first time ever since having rooted my phone months ago, I am having force closes of most apps I try to open.
ROM manager force closes also, so I can't restore the nandroid I have on my SD card from there. I try to boot into Clockworkmod recovery, but all I can get into is the stock "white screen" recovery, not the black and orange clockwork recovery screen.
Is there a way I can flash a nandroid manually, without having to go through clockworkmod? Or does anyone have any other idea of how I can get my phone functional again?
Thank you in advance-
Click to expand...
Click to collapse
Reflash cw recovery thru hboot and then see if it works. My only other thought would be messed up or bad sdcard. Try reformating it fat32, or try a different sd.
so it's fixed now, and in case this helps anyone:
i was trying to install cwm recovery directly on the root of my sdcard by attaching the phone via usb to my computer, and while i was looking around my folders i noticed that "whatsapp" was suddenly working on my phone, whereas when it was malfunctioning i kept getting notifications that whatsapp could not access old messages. so this made me wonder whether rom manager was working. i opened it, and indeed it was working. from there i fixed permissions, and this seems to have fixed the problem.
i don't know why attaching the phone to the computer would have let things work enough for me to get into rom manager, but i'm just grateful to have my phone back.