Related
i have tried the fresh roms, and the TTG CDMA rom, regardless of the rom i get force close errors on settings in the phone and i dont have data or voice service. everything else works perfectly EXCEPT for settings and service.
help?
ae you performing a wipe before you flash? I know a lot of these roms say that they are no wipe but I have found that that it is always better to wipe then flash that way you know you are getting a clean install. also do you have a ton of apps? it is a known problem that the phone will freak if you have more than like 60 apps
yeah, i have wiped also. but one thing i only wipe data/factory reset
should
i wipe
dalvik cache also? alsong with anything else?
when I install a new rom I wipe both the factory/data reset and delvik cache. I also do this when I am going from say TTG 1.6 back to my backup of fresh 1.1. It just assures me that anything that one dev did in their rom will be wiped out and replaced by what the other did with no problems. the only FC I get is google voice ( which FC's on EVERYTHING for no particular reason)
ok wiping data, and dalvik because jusr assuming battery status, rotate settings and partition doesnt matter.
from my personal use I dont use all the options in recovery. the partition SD is going to be usefull once you get the ROMs running if you want to run apps2sd
nope...
ive unrooted used kitchen numerous times to auto root aswell then just apply update and I can get everything to work except FC on settings and no service, im trying to figure out how to use ruu 1.2.3 instead of the 1.5 one idk just gonna try.
samrozzi said:
nope...
ive unrooted used kitchen numerous times to auto root aswell then just apply update and I can get everything to work except FC on settings and no service, im trying to figure out how to use ruu 1.2.3 instead of the 1.5 one idk just gonna try.
Click to expand...
Click to collapse
RUU 1.29 will not work for you if you have used 1.56. Are you sure you're running a Sprint CDMA Hero? Can you step by step explain the process you go through when RUU'ing and when flashing, and when the problems start?
ok if i wanted to start from scratch, i will unroot my phone with htc sync and reload the stock rom.
then i use kitchen and run the tests and everything checks out good.
i auto root and its successful and working.
then say I download fresh 1.1, load it onto the root of the sd card.
Power off the phone then power on while holding home.
apply .zip on sdcard. it applies the fresh 1.1 update says successful
i click reboot, phone goes through startup process everything seems fine, rom loads up i can navigate through menues. except i get force close errors anytime i goto settings, and i have no service, no data or voice signal.
I have tried renaming fresh and other roms to update aswell, i have tried numerous roms, one of the most recent was the TTG cdma hero rom. and i get the same errors.
One interesting thing is the first rom i tried on the cdma hero was eclair 2.1 beta and that worked flawlessly like all the roms i tried on my g1. but i decided to go to fresh and nothing works.
samrozzi said:
ok if i wanted to start from scratch, i will unroot my phone with htc sync and reload the stock rom.
Click to expand...
Click to collapse
I'm not sure what you mean by unrooting it with htc sync and reloading stock rom? You need to be using the RUU to flash back to stock.
Also if you are using apps2sd then I would recommend temporarily formatting your sdcard back to 100% fat32 (you will lose all data) and then try RUU and flash. Or just grab another sd card and put it in there. If you are using apps2sd and there is an app on your sdcard that is breaking things then it will persist even after a wipe.
1. Partition sdcard to 100% fat32 or replace it with another temporarily
2. Run 1.56 RUU to return to bone stock. Confirm everything works.
3. Run auto-rooter in kitchen. Confirm everything works.
4. Flash a rom, confirm everything works.
If you follow those steps exactly then everything will work out for you.
ok gonna try it again when wiping sd card and foratting to fat32.
any way or know how to get htc sync to recognize my phone?
it picks it up on my vista laptop but on my windows 7 64 bit it doesnt, but atm all i have is my windows 7 one.
samrozzi said:
ok gonna try it again when wiping sd card and foratting to fat32.
any way or know how to get htc sync to recognize my phone?
it picks it up on my vista laptop but on my windows 7 64 bit it doesnt, but atm all i have is my windows 7 one.
Click to expand...
Click to collapse
http://www.mydigitallife.info/2009/08/24/workaround-for-htc-hero-sync-problem-in-windows-7/
ok about to return to stock, when i apply the fresh 1.1 rom after i use kitchen auto rooter i jsut stick it on root of sdcard and DO NOT change file name?
just used to most roms from g1 have to be renamed update.zip
samrozzi said:
ok about to return to stock, when i apply the fresh 1.1 rom after i use kitchen auto rooter i jsut stick it on root of sdcard and DO NOT change file name?
just used to most roms from g1 have to be renamed update.zip
Click to expand...
Click to collapse
You can do it either way. But you don't have to rename it.
WOW IT WORKS, their had to be something wrong with my sd card, because it wouldnt let me format it.
I had to delete all the files, then install some 3rd party software that would let me format it. idk what was wrong, but working great !!!
so excited finalllly lol
thanks everyone and especially flipz
i am running fresh 1.1 defreshed atm, love it but curious about what AOSP i think its called. what exactly is that, looking at it and seems interesting,
im hoping we get a rom similar to nexus, love the app drawer etc..
It may have worked because when you wiped your Sd, you deleted your apps, if you install too many, you'll have the same issue. I went round and round with mine before I figured it out, then found a thread on it.
AOSP stand for "Android Open Source Project" they are ROMs that are crated and developed from scratch by various developers.
I have played with AOSP builds and I have found that out of them all I like AOSP 1.6 best. The thing you have to rememeber about AOSP builds right now is that A. we still dont have the Kernel source so not everything is working correctly and they can be kinda buggy and B. all the AOSP builds are vanilla android, meaning they dont use sense UI which in my opinion defetes the purpose of having a hero. If I didnt care about sense then I would have gotten a moment.
that being said I will say that the AOSP builds are REALLY fast.
if you want to try a ROM that is close to an AOSP build but still has sense try TTG1.6 its really fast and has a really small memory footprint due to it being almost completely gutted and optimized.
Ok so I've done a bit of searching and asking on androidforums but nobody can figure out my an answer to my problem. Alright, first off originally the phone had android 1.5 but when sprint released the 2.1 update I did it. From there, I used regaws tutorial on rooting the official 2.1 release which worked great. Basically I was on a mission at this point, a mission to try out all the 2.1 based custom rims. I had been using the rom manager app for its ability to wipe and flash new roms without even rebooting to recovery. As you are probably aware, to do anything with rom manager, you have to have their clockwork mod recovery flashed, which is simple to do with this app. So one day I wiped and flashed a new rom, aloysius I think, and after it was trying to boot the new rom it gave me some error message and the installation failed. I think at this point I tried to restore my nandroid, which also didn't work, I'm guessing that you have to be using the same recovery you were using when you created the nandroid? No matter what I did from recovery I could not restore my nandroid, as a last ditch effort I did a factory wipe and then rebooted. I didn't think it would reboot at all, honestly I was way scared and thought that I had bricked the phone but after about 5 minutes it finished booting up. Now I don't understand why or how, but when it came to it was quite obvious, I was back at stock 2.1. I immediately look in the app tray for the superuser app and obviously it isn't there, I've been dealing with the phone as is for about a month. A couple of weeks ago I decided to get back to work, sat down at the computer and tried to root it again using the same exact method. After like 5 attempts I get the same problem, I get to the step where command prompt spells out "UNREVOKED" really big but I notice that instead of having a "$" like it shows in the picture I have a "#". At this point the guide instructs you to open the Superuser app on the app tray on the phone, sure enough, I don't have one. I have tried this probably like 7 times all with the same result. I've even tried to install that .6 update to patch whatever remnant of root access I have and go from there as I'm sure the fact I was rooted once and lost it has something to do with my failure. I've tried running RUU's many times as well and always wind up getting an error 171 USB connection error. I havent heard of anyone else having an issue like this. I'm not sure whether I posted this thread in the right place to really get help either so if this needs to be moved to development or whatever don't hesitate. I'd really appreciate anyone trying to figure this out as I am tired of running the slow stock rom but have exhausted virtually every option that I am aware of, PLEASE HELP ME!
I know everyone is probably still reading that book I posted, but once you get to the end lol please gimme some advice, i've tried everything and don't wanna live with the phone as is for the next year....
It's a little hard to read your original post, but I'll do my best to help. From the sound of it you may still have root.
I haven't had to root on stock 2.1 install, so I'm not familiar with the new method. If you get to a bash shell or terminal prompt that is a '#' rather than a '$', you still have root.
You said that you did a factory wipe on the phone. Did you RUU or did you simply wipe through recovery? Are you still able to get to the clockwork recovery?
If you can get back to your modded recovery, you're golden. I would STRONGLY recommend you flash the newest Amon_RA. http://forum.xda-developers.com/showpost.php?p=4898505&postcount=1
If you can get that far, you should just be able to wipe and flash a new ROM.
have you tried to update your sync/drivers on your computer lately?
Sent from my Hero CDMA using XDA App
Oh well I finally got it all figured out, had to rum the ruu twice back to back whole the phone was still frozen at the bootloader. From there I finally was able to re root it.
Hey folks, I've read through all the JI6 OTA threads here and on the TMo forums and while I've seen a few people guess as to the cause of soft bricks, dosen't seem like anyone has nailed down the actual cause. I'm going to assume I'm not the only person out there with no access to a windows box to run ODIN so knowing what if anything can be done to prep my phone before accepting the OTA (that is sitting in my notification bar as we speak) would be immensely helpful.
So far the two best guesses I've seen are the existence of other update.zip files on SD and removal of bloatware, specifically Media Hub and possibly edited startup/shutdown screens.
Since I've got all these going on, I guess I'm staring down the barrel of a brick. But obviously one of these is easily rectified while the others, not so much.
Aside from those claiming bricks on vigin phones. Can we hear from those who have made mods to their rooted devices and either did or did not experience an OTA brick? I think this info will be helpful to many in sorting out what exactly is going on here.
I have black bar mod, I have naked swype, removed most t-mob app except media hub no change to start up or shut downtried to update. 50 % through it said update failed. Then rebooted fine. But I had an extra update.zip on my sd so maybe that's why. But no firmware now? Maybe I'm sol.
Sent from my SGH-T959 using XDA App
Mine wouldn't complete the update Rooted, most of the bloat removed, had an update on the sd. Was able to get into clockwork after the failed update and am performing a nandroid restore now.
this is great, thank you. beginning to look more like an issue with extra update.zip files than media hub. any successful OTA's with media hub removed prior to accepting the update?
Sent from my SGH-T959 using XDA App
I never uninstalled Media Hub. I have seen a correlation of about 5 people who had ROM manager installed and used that to install Recovery. Whether it be the installation of Recovery or a possible permissions issue with how it generates the update.zip that may have caused my issue.
just a question, why do people remove media hub? Does the application make the phone slow?
iynfynity said:
just a question, why do people remove media hub? Does the application make the phone slow?
Click to expand...
Click to collapse
Because up until now, it was a non-functional app. I didn't remove it, I use LauncherPro so I just removed it from my drawer. I'm still not touching this update. I got my Vibrant used so I would be out of luck if it jacked my phone up and I hate using ODIN. Too much hassle when my phone runs great on Bionix 1.4 as it is.
Wife's phone was toasted by OTA. Stuck at Vibrant screen. Rooted, unlocked, she did have an update.zip, if that turns out to be the culprit. Also had some apps removed, replacement startup animations, and removed shutdown junk.
She was set for always-on WiFi, too.
My rooted Vibrant soft bricked yesterday and I had to flash stock with Odin. I had the (what seems to be infamous) update.zip, removed Kindle, Mobi TV, Avatar Icon, Gogo. I had RyanZAOneClickLagFixV1+ installed but removed it. I also had the EXT2 Tools installed. @ the time of the update I was @ work and had a full charge on the phone. I flashed back to stock last night after work, and I haven't recieved the update notificaiton again...maybe TMo crossed me off some type of "update list"?
There are also different possible symptoms.
In my case the update appeared to have completed its cycle, except the tail end of the download of the new update wnt really fast then the system rebooted. System came back up into the Black Vibrant screen. I could start 'adb logcat' and the system had SurfaceFlinger repeatedly crashing.
Attempts in Recovery Mode after this to reinstall files didn't resolve the issue, reboots would still lead to a crashing SurfaceFlinger.
2 separate users in a thread, 1 had removed Boot Animations + Sounds, I only had removed Sounds.
Quite a few people had Stock Roms + Root, but some with Root didn't have any issues. Only correlation was with Titanium + Rom Manager, which a lot of people would have installed since it's listed in the Tips and Tricks thread. Titanium shouldn't do anything to the system unless you generate a backup Update.zip or install LZO support busybox.
One guess is that ROM Manager and Titanium can create a update.zip file that doesn't have the proper permissions. An OTA update that attempts to overwrite this file may get confused. Simply removing the file in advance may alleviate this issue. Another issue is ROM Manager installs ROM Recovery, which may change how the OTA perceives the phone.
Bionix 1.4...
I was running Bionix 1.4 KK OC/UV yesterday morning... Was a little dumbfounded when I received the update message from Tmo. Figured it wouldn't show w/ modded handset. Delayed install until I could read everything on here about it. Tried installing over Bionix last night just to see, and had no joy. I had removed all crapware, mediahub included. Hit 50%, said flash failed, rebooted and was back to my homescreen in no time. No ill effects to phone except being denied upgrade.
So I Odined back to Stock JFD FW (and wiped device for S&G), rooted, and updated from JI6 tar posted. Flashed perfectly, no ill effects as I've noticed. Reception is improved (for me anyway), and GPS functions similar to Bionix... No real incentive for update, but was curious.
I see Bionix 1.7 updated so it was all for nothing.
Now to play with other stuff...
Cheers
My girl friends phone bricked the other night from the OTA, it's rooted(update.zip) and has the bloatware uninstalled, nothing else like lagfix/roms on it etc.
T-Moible is sending her a replacement phone, which im pretty surprised about. Now since we have to send the old phone back so they can check for damage or anything that would void the warrenty.
We get to keep the external SD card(Avatar), now im sure there is a pretty good chance they will find that its been rooted. So we would have to pay $400 they said if its voided.
Now I can't get this phone to boot into download mode or even mount it, so what should I do? I know about ODIN but have never used it, can it mount the phone?
I got the soft brick and had to flash back to stock via Odin and then I flashed the JI6 tar file from the forum. All is working fine now.
I had root but no update.zip file on the sdcard root, had removed startup an shutdown sounds, had used both ROM Manager and Titanium (with LZO compression turned on), and had removed bloatware including the non-functioning Media Hub.
Next time I'll flash back to stock before doing an OTA update.
I am rooted have Titanium backup, ROM Manager, and clockwork mod. I also had an update.zip but I think it was from OCLF not from another source. My update went fine and I'm running without any problems on the new update.
PepeLasNoches said:
My girl friends phone bricked the other night from the OTA, it's rooted(update.zip) and has the bloatware uninstalled, nothing else like lagfix/roms on it etc.
T-Moible is sending her a replacement phone, which im pretty surprised about. Now since we have to send the old phone back so they can check for damage or anything that would void the warrenty.
We get to keep the external SD card(Avatar), now im sure there is a pretty good chance they will find that its been rooted. So we would have to pay $400 they said if its voided.
Now I can't get this phone to boot into download mode or even mount it, so what should I do? I know about ODIN but have never used it, can it mount the phone?
Click to expand...
Click to collapse
Woo, got it unbricked! finally got into download mode and ODIN saved the day.
this video was helpful for me: http://www.youtube.com/watch?v=AnY7P14JSWQ
^ODIN walkthrough
paxton said:
I'm going to assume I'm not the only person out there with no access to a windows box to run ODIN
Click to expand...
Click to collapse
there is a cross platform tool being developed called 'Heimdall'. It is currently a command line tool and is in beta. however people are successfully flashing their phones using it. It is obviously not a 'one click' solution, so you will have to go find the proper files and type out the command.
It can be found here http://forum.xda-developers.com/showthread.php?t=755265#
If you are the type of person with access to both a windows machine and a linux machine, I suggest you check this out. Testers are needed. Of course you can test if you don't have windows, but it's nice to have Odin as a back up. ;-) just incase....
-p
I had a failed update twice using Odin. It wasn't until I went back to stock T959JFD for the second time and deleted update.zip and all clockwork back ups that it finally worked. Runs perfect with no issues.
Sent from my SGH-T959 using XDA App
Was rooted with OCLF, Captive camera, gps fix, rom manager, titanium backup and add removal. Removed the OCLF and unrooted, ran the update, looked like it got to 100% (not sure cause I looked away and then back at it right before reboot) but said update failed. Got stuck at the vibrant screen blah blah. I'm pretty sure I had an update.zip on the sd, but not 100% on that. After pushing the update with ODIN I have noticed my phone lagging quite a bit.... Thoughts?
Sent from my Rooted Samsung Vibrant using XDA App
Alright, this issue has seriously driven me insane over the last few days, and today it's gotten to the point where I'm going to do something I'll regret if somebody can't help me out. As you can tell, I'm pretty desperate.
Using Fresh 3.5.0.1, I've encountered more reboots than I can count. Whether it's checking an email or playing Asphalt, the phone frequently decides it doesn't want to cooperate and restarts itself. I decided to try to get rid of the reboots for good today with a complete wipe and new rom.
First, I made a nandroid backup, followed by a data/system wipe and cache/dalvik cache wipe. Afterward, I flashed the ZenDroid 1.1.0 kernel in case that was the issue. I then proceeded to flash CyanogenMod 7 RC1 with gapps.
That worked for all of three minutes, and then it got even worse. The phone started restarted itself when I wasn't even doing anything, up to the point where it would restart on the CM7 boot animation. I took my rage out on a nearby pillow and decided to try something else.
I downloaded the final release MIUI rom and used Calkulin's format all to wipe my phone as instructed. This time around I flashed Savage-Kernel 1.6 along with MIUI. Lo and behold, after rebooting I was finally able to swipe through the home screens again.
And then I wasn't. It started rebooting on the boot animation again. At the moment it's even worse, rebooting three seconds into the damned splash screen. I've tried keeping the battery pulled for half an hour with the HTC battery and two after market batteries. I wiped the ext partition on the micro sd card. I even physically removed the card itself. This effing phone is still rebooting on the splash screen.
I'm at the end of my wits. All I want is for my Evo to WORK, without any constant reboots or force closes that make it utterly unusable outside. If anyone could help me out with this issue, I'd be extraordinarily grateful.
Mecha2142 said:
Alright, this issue has seriously driven me insane over the last few days, and today it's gotten to the point where I'm going to do something I'll regret if somebody can't help me out. As you can tell, I'm pretty desperate.
Using Fresh 3.5.0.1, I've encountered more reboots than I can count. Whether it's checking an email or playing Asphalt, the phone frequently decides it doesn't want to cooperate and restarts itself. I decided to try to get rid of the reboots for good today with a complete wipe and new rom.
First, I made a nandroid backup, followed by a data/system wipe and cache/dalvik cache wipe. Afterward, I flashed the ZenDroid 1.1.0 kernel in case that was the issue. I then proceeded to flash CyanogenMod 7 RC1 with gapps.
That worked for all of three minutes, and then it got even worse. The phone started restarted itself when I wasn't even doing anything, up to the point where it would restart on the CM7 boot animation. I took my rage out on a nearby pillow and decided to try something else.
I downloaded the final release MIUI rom and used Calkulin's format all to wipe my phone as instructed. This time around I flashed Savage-Kernel 1.6 along with MIUI. Lo and behold, after rebooting I was finally able to swipe through the home screens again.
And then I wasn't. It started rebooting on the boot animation again. At the moment it's even worse, rebooting three seconds into the damned splash screen. I've tried keeping the battery pulled for half an hour with the HTC battery and two after market batteries. I wiped the ext partition on the micro sd card. I even physically removed the card itself. This effing phone is still rebooting on the splash screen.
I'm at the end of my wits. All I want is for my Evo to WORK, without any constant reboots or force closes that make it utterly unusable outside. If anyone could help me out with this issue, I'd be extraordinarily grateful.
Click to expand...
Click to collapse
hmm...
i don't know what kernel fresh comes with, but both of the other kernels are more aggressive ones, and i would guess your phone doesn't like them. i would try this:
Wipe twice using calk, wipe again using recovery, flash mikfroyo or stock rooted (stock kernel). If you still get reboots... unroot and take your phone back in because its a hardware problem.
I had this problem. Drove me insane. Ultimately just unrooted and got a new one from sprint. Not one reboot since I got the new one.
Sent from my PC36100 using XDA App
Well I'm still super new to the whole flashing of the ROM's. But from what you have explained the only thing I can think of is that you missed a step when you rooted your phone. Because of this that is why your phone keeps brick. You should go and check out HTC EVO Hacks (go Google it) and the guy who runs the site made a sweet video & write-up on how to root your phone. Just re-do everything and follow directions, then when your done just flash Kings Unleashed. And when you check out the HTC EVO hacks root page look for the link to the XDA root forum which has more info on how to root your HTC the proper way.
Sent from my PC36100 using XDA App
aimbdd said:
hmm...
Wipe twice using calk, wipe again using recovery, flash mikfroyo or stock rooted (stock kernel). If you still get reboots... unroot and take your phone back in because its a hardware problem.
Click to expand...
Click to collapse
Yeah, I guess I should try the stock rooted rom. If I'm only able to use that instead of any other custom rom, though, I'm going to lose it. There's something inherently frustrating about a device refusing to work for no apparent reason.
chickut123 said:
I had this problem. Drove me insane. Ultimately just unrooted and got a new one from sprint. Not one reboot since I got the new one.
Click to expand...
Click to collapse
I'm sort of hoping I won't have to do that, considering I'll likely get a refurbished unit.
Fredrow425 said:
But from what you have explained the only thing I can think of is that you missed a step when you rooted your phone. Because of this that is why your phone keeps brick. You should go and check out HTC EVO Hacks (go Google it) and the guy who runs the site made a sweet video & write-up on how to root your phone. Just re-do everything and follow directions, then when your done just flash Kings Unleashed. And when you check out the HTC EVO hacks root page look for the link to the XDA root forum which has more info on how to root your HTC the proper way.
Click to expand...
Click to collapse
I'm pretty sure that isn't the case at all. If there was an issue with the way I rooted my phone, it would have been present eight months ago when I bought it. This rebooting issue is relatively new, and it isn't bricked. I appreciate the advice, though.
It could be just a defective phone - memory isn't immortal or impervious to defects.
I'd downgrade to a Sprint ROM, and keep it stock and see how that works. You have to rule out bad hardware first, and that's the only way to do it.
I agree on all of your guys suggestions but one thing i noticed was that he said he wiped data then dalvic cache then he said he flashed the kernel then the rom. Maybe he should try and rewipe everything with calk format all then flash the rom and reboot. Then go back into recovery and flash your new kernel then reboot again and see whats up from there.
Have you tried repartitioning your SD card and formatting? I was getting random reboots on every single rom I tried, and every single kernel. Turns out my partitions somehow got messed up on my SD card and that was causing it randomly. Now I have no reboots.
akrod2as said:
Have you tried repartitioning your SD card and formatting? I was getting random reboots on every single rom I tried, and every single kernel. Turns out my partitions somehow got messed up on my SD card and that was causing it randomly. Now I have no reboots.
Click to expand...
Click to collapse
Yes, I first formatted the sd card in Windows and then partitioning it on the phone's recovery. Still no luck.
Yeah... Sprint rom or if you go through with the unrooting process (I forgot how...) then you can figure out if it is hardware.
But yeah, endless reboots are frustrating.
If Sprint rom is giving you troubles, then just return it and get a new one. It's gotta be hardware then.
Also you could try running stock rooted without any downloaded market apps. Just run what came with the phone.
You can also try stock rooted eclair 2.1
Mine started the reboot bs after the december update. Mine seems to reboot when I use it heavily even though I'm not overclocked (heats up). Before the 2.2 update, it was very fussy being outside during the summer. I would like to exchange mine for another, even though I don't use it anymore. It would be nice to have a fully functioning backup. My gf's daughter wants the evo very much. Even if I would do that, which I wouldn't, I wouldn't let someone use a possibly unstable phone. If an emergency happened, and the phone started it's rebooting bs, it would be very bad to not be able to use the phone when you need it the most.
I am guessing I would have to reactivate the evo, run it for a month or so, unroot and lock it, then take it to a service center and see if I can make it start rebooting like crazy. Maybe I will get lucky and they would give me another one. I don't care too much if it is a refurb as long as it is in good shape and works good.
Try removing the SD card and booting.
Sent from my PC36100 using XDA App
rebooting
I had this same problem with my evo. Sometimes it would be ok, but then others it wouldnt stop doing it, didnt matter what I did. It could be sitting by itself and I would hear it rebooting. Drove me mad!!!
My first evo was awesome, it was a hardware ver 3. My camera lens cracked and the gave me a refurb, hardware version 2. This is when my reboots started happening.
After 3 batteries from Sprint and two more refurbs I finally blew in front of a store full of customers telling them that either give me a NEW evo, hardware version 3 like I originally had with no problems or it was going against their wall.
I havent had one problem since.
I wasnt rooted yet so cant comment along those lines but if you take it back to stock and it still does it I recommend throwing it at one of Sprints walls. No need to do any drywall patching at your place LOL.
I hope you get it resolved as I can feel your pain!
It may not be hardware. Did you restore any apps using any back up app (Titanium Backup) after flashing the AOSP roms? If so, make sure you did NOT restore any system apps or data. This is especially important when you go from Sense to AOSP.
The test is what everyone is suggesting. Flash back to Sprint rom and see what happens.
Also, you need to flash the kernel after flashing the rom, otherwise you'll just get the kernel packaged with the rom. I usually reboot and art least try the default kernel unless I know that my phone hates it.
bigmoogle said:
It may not be hardware. Did you restore any apps using any back up app (Titanium Backup) after flashing the AOSP roms? If so, make sure you did NOT restore any system apps or data. This is especially important when you go from Sense to AOSP.
The test is what everyone is suggesting. Flash back to Sprint rom and see what happens.
Also, you need to flash the kernel after flashing the rom, otherwise you'll just get the kernel packaged with the rom. I usually reboot and art least try the default kernel unless I know that my phone hates it.
Click to expand...
Click to collapse
No, I haven't even been able to get to the stage of installing any apps before the rebooting cycle starts again. I tried installing the stock Sprint rom this morning with the stock radios and kernel and it was stable for about five minutes. It's back to rebooting again, though.
Do you guys think it's time to unroot and go to the Sprint store for an exchange?
Mecha2142 said:
No, I haven't even been able to get to the stage of installing any apps before the rebooting cycle starts again. I tried installing the stock Sprint rom this morning with the stock radios and kernel and it was stable for about five minutes. It's back to rebooting again, though.
Do you guys think it's time to unroot and go to the Sprint store for an exchange?
Click to expand...
Click to collapse
If it was me, I would take it back. I just downloaded the newest ruu and will flash it later tonight. The only thing I'm worrying about is they won't be able to reproduce the problem. I really have to be multitasking a lot and pushing the phone hard. Actually the last time it had rebooting fits was with wireless tether running. The back of the phone was warm. I put it in front of the ac vent in the car for a minute or two and that seemed to help it stop rebooting.
herbthehammer said:
If it was me, I would take it back. I just downloaded the newest ruu and will flash it later tonight. The only thing I'm worrying about is they won't be able to reproduce the problem. I really have to be multitasking a lot and pushing the phone hard. Actually the last time it had rebooting fits was with wireless tether running. The back of the phone was warm. I put it in front of the ac vent in the car for a minute or two and that seemed to help it stop rebooting.
Click to expand...
Click to collapse
Well, it looks like I'll be taking it to the store after all. I just finished unrooting my phone with the RUU, so it's as if I had never touched the software. Lo and behold, the damned thing still rebooted a minute into using the phone.
I guess that in some sick way, I can consider myself more 'fortunate' than you, seeing as how my phone doesn't even need to be used in order to begin rebooting. It's ridiculous that I have to part with my Evo because of this bs.
Mecha2142 said:
Well, it looks like I'll be taking it to the store after all. I just finished unrooting my phone with the RUU, so it's as if I had never touched the software. Lo and behold, the damned thing still rebooted a minute into using the phone.
I guess that in some sick way, I can consider myself more 'fortunate' than you, seeing as how my phone doesn't even need to be used in order to begin rebooting. It's ridiculous that I have to part with my Evo because of this bs.
Click to expand...
Click to collapse
Did you even try removing the sd card and booting the phone?
Same thing happend with my old evo it started after i install one of the first cm safe roms not nightlies not saying tyat was the cause, i tried evverything wiping unrooting botting without sd, ive been on android sice g1 and i tried everything nothing worked, ended up going to sprint and getting another refurnished it was prolly hardware issue maybe cpu overheating or something, anyways not sure why ppl are so scared of refurnished phones i believe they do a lot more tests on those phone than retail ones lol
akrod2as said:
Did you even try removing the sd card and booting the phone?
Click to expand...
Click to collapse
Yes. I've already said I tried booting the phone without the sd card several times now without success.
Ok, so I updated from stock, using official update phone rebooted and stayed at samsung screen forever it kept blinking and vibrating. Pulled battery, tried restarting it goes samsung loading bar -> VM welcome -> flashing/vibrating samsung screen.....I can get into recovery AND download mode. Tried clearing cache, factory reset, and updating again, but still gets stuck at samsung screen. I am desperate guys I really need help, I am going on a LONG road trip this weekend and need my phone so ANY help would really be appreciated. THANKS!
When u say update do u mean u went from ex. 2.1 to 2.2.... android that is? U should elaborate a hit more, if what I mentioned is the case then revert back to the ROM prior to the update. If u give more info I may be able to help from my personal experiences
Sent from my HTC HD2 using XDA App
Yes used official update went from 2.1 (stock) to 2.2 as the update finished, it got stuck in a sort of boot cycle, stuck at a samsung screen keeps flashing samsung logo, and vibrating. wont fully boot
OK, I saw on my facebook page samsung intercept page. Mediafire link to download update.zip file,has anyone tried this. Will this work,if it bricks my phone i will be pissed...
There's always the chance that a phone can get bricked, no mater what ...even from an 'official' update from your service provider. With that said, however, I've downloaded the Virgin Mobile 2.2 Froyo update file that's floating around and it installed no problem on my phone.
For the first poster ....I believe that the stock recovery is necessary for the VM 2.2 update to work. I won't swear on that though.
Here's what I did. Downloaded the 2.2 VM Froyo update to my laptop. Renamed it 'update.zip'. Copied it to the root of my sdcard on my Intercept via bluetooth. Booted into recovery mode and applied the update. Twiddled my thumbs while it updated itself from recovery and then rebooted....and the reboot takes a while, maybe 5 minutes. Presto ...2.2 Froyo.
creativenate88 said:
Ok, so I updated from stock, using official update phone rebooted and stayed at samsung screen forever it kept blinking and vibrating. Pulled battery, tried restarting it goes samsung loading bar -> VM welcome -> flashing/vibrating samsung screen.....I can get into recovery AND download mode. Tried clearing cache, factory reset, and updating again, but still gets stuck at samsung screen. I am desperate guys I really need help, I am going on a LONG road trip this weekend and need my phone so ANY help would really be appreciated. THANKS!
Click to expand...
Click to collapse
I think that you didn't wait long enough...as the reboot takes a looooong time, maybe 5 minutes or more at least. Patience is a virtue.
Okay guys,im new here. I installed VM Froyo 2.2 update.zip,it seems to work fine. A bit slow but its still booting up. I installed stock rom,stock kernal, and update.zip,in that order. And backup works too,wiped dalvik cashe to. I like this forum its more informative,will let yall know more later. Thanks.
ajones23 said:
Okay guys,im new here. I installed VM Froyo 2.2 update.zip,it seems to work fine. A bit slow but its still booting up. I installed stock rom,stock kernal, and update.zip,in that order. And backup works too,wiped dalvik cashe to. I like this forum its more informative,will let yall know more later. Thanks.
Click to expand...
Click to collapse
You're making this way to convoluted. All that one needs to do when updating from stock 2.1 on the VM Intercept is to download the (official unofficial) update file, rename it to 'update.zip' on the root of the sdcard, boot into recovery, and apply the update. That's it. It installs Froyo and the new radio, etc, itself...all from the update.zip. No need to mess with kernels and recovery or wipe anything ....except one's own azz if they go take a chit while waiting for it to reboot. In fact, when I updated it even kept all of my 2.1 widgets and icons and imported them into Froyo ...I didn't need to do a thing.
Oh, I see ....you had to convert your Intercept back to 'stock' first. Nevermind...
Yes, i did i downloaded stock rom,stock kernal and stock recovery all .zip. Put stock.zips in sdx/zip folder and update.zip 2.2 in root on sdcard. Installed all three wiped dalvik cashe rebooted each time in custom recvery. When i got to stk rec. rebooted to stock rec. Ran update.zip 2.2 may take a while but it booted no problems.
Can u get the phone into download more with any button sequences, YouTube it if u don't know what i mean(mobiletechvideos) then y will need to use odin to use tp download an official Samsung Rom.... PM if u need help
Sent from my SGH-T959 using XDA App
hey people first post longtime reader any way i got my samsung intercept update
just fine saved all adw stuff and everything but i cant root anymore {big up to z4root} anyone can help?
sorry trying to delete my posts.
Love XDA but but for interecpt help Go to SDX forums