Related
I finally got my droid x about 2 weeks ago after waiting almost a month on backorder.. Since i ordered it ive gotten an pneumonia lung infection as of saturday tonsilitis and fevers.. Plus two weeks in i got laid off so this hasent been the greateast of time. Ive been pretty out of it and yea.. anywho. I got this and first thing i did was Root via the "DroidX Root" with the Root Me and UnRoot Me " buttons. Ive owned a G1 and a Droid Eris prior to all this and loved em both. Rooted them gotten the recovery image's custom roms ect. With this im getting confused. I think its partially because ive been so ill and disoriented half the time. Also because of this efuse crap and what not. Yes ive googled and searched but again ive been fairly out of it so im still not certian what i should do here. I downloaded some apk file Recovery Bootstrap v1.0.0.3 that i was told i needed to get but again...
I want or at least i think i want to get to 2.2 im currently still on the 2.1 build it shiped with. i have *228'd it or changed the firmware in any way all ive done is rooted it.
Im having issued with the data connection. My browser seems to hang a good 50-60% of the time wether im on my wireless g connection at home or on 3g. Ill listen to slacker radio and often it stops for sometime and either wont resume playback until ive closed and re-opend it or just does it on its own.
Ive heard of people getting roms on it but others tell me there not "real".
Also its "fluid'ness speed" seems to be jotty at times. I havent hardly installed much on this and its slows down really bad at times.
Basicly i like modding my phone and really enjoy all the work people put out to fully give us the full capability's of these pieces of hardware we buy. But i dont feel like im getting that.
What other suggestions can you all give me to do to my phone, to speed it up back it up remove this crapware like dlna ect. I have seen some threads about doing this but then people telling me they get stuck at the boot logo cause they messed something up and i dont really wanna do that.
What have you done with your phones? How well do they run?
Thanks for taking the time to read my post and i look forward to everyone's reply
-Mort
.....
Sent from my DROIDX using Tapatalk
Sorry to hear about your problems. I just went through a week of hell before being diagnosed with pneumonia this June. So I know how it felt.
Basically, even though 2.2 OTA is available, if you mess up your phone while modding, there is no stock image to fall back to, so you'll be stuck with a bricked phone.
The best solution right now is to upgrade to original 2.2 leak. Then you can install leaked 2.3.15 which is the same as OTA (with a difference of being deodexed and rooted). In this case even if you have problems, you can always flash original 2.1 back and start from scratch.
rootzwiki has a good amount of info on how to do all of this. But of course feel free to ask questions.
http://rootzwiki.com/index.php/Smartphones/Motorola/Droid-X/Droid-X.html
I have a early version of the Vibrant that I have rooted and installed Roms over.. T-Mo sent me a refurb because I was complaining about the poor GPS locks.. we wanted to see if another Vibrant would do better... unfortunately it doesnt...
Today I started adding a ROM to the new phone and it went haywire on me... wouldnt go into Recovery, hard time going into Download mode... literally 2 hours later after a scary Orange explanation mark on the screen did it finally cooperate and I ODIN'd the stock rom back on... turns out the stock rom wouldnt get passed the Galaxy S screen... so then I was about to get into recovery and reinstalled Obsidian since the zip was still on the card... now I can go in and erase everything off the internal memory... should I just return it and keep my early version... my original phone never acted up like this
if you wanna sell it... PM me
JD76 said:
I have a early version of the Vibrant that I have rooted and installed Roms over.. T-Mo sent me a refurb because I was complaining about the poor GPS locks.. we wanted to see if another Vibrant would do better... unfortunately it doesnt...
Today I started adding a ROM to the new phone and it went haywire on me... wouldnt go into Recovery, hard time going into Download mode... literally 2 hours later after a scary Orange explanation mark on the screen did it finally cooperate and I ODIN'd the stock rom back on... turns out the stock rom wouldnt get passed the Galaxy S screen... so then I was about to get into recovery and reinstalled Obsidian since the zip was still on the card... now I can go in and erase everything off the internal memory... should I just return it and keep my early version... my original phone never acted up like this
Click to expand...
Click to collapse
Tell them to send you a new one. I'd be fine with a refurb phone if everything worked. but if it doesn't then what's the point of the exchange?
JD76 said:
I have a early version of the Vibrant that I have rooted and installed Roms over.. T-Mo sent me a refurb because I was complaining about the poor GPS locks.. we wanted to see if another Vibrant would do better... unfortunately it doesnt...
Today I started adding a ROM to the new phone and it went haywire on me... wouldnt go into Recovery, hard time going into Download mode... literally 2 hours later after a scary Orange explanation mark on the screen did it finally cooperate and I ODIN'd the stock rom back on... turns out the stock rom wouldnt get passed the Galaxy S screen... so then I was about to get into recovery and reinstalled Obsidian since the zip was still on the card... now I can go in and erase everything off the internal memory... should I just return it and keep my early version... my original phone never acted up like this
Click to expand...
Click to collapse
Change it, it could be defective
Since the replacement didn't show improvement on gps, If you still have your original phone, keep it and send the refurb back...
Sent from my SGH-T959 using XDA App
They sent me refurb unit too. I sent it back. xP
Thanks everyone.. Im back to my old one... I went back to stock J16 with a lag fix and a MobileAP mod on it...
If you didn't flash JFD you're doing it wrong. All you will get is a refurbished phone. They're not giving out new ones.
I have 7 days to return it so im testing out every froyo ROM out before I give it back squeeky clean...lol
Blame people who get replacements for issues that exist in every phone at the software level for the refurbs.
I got two brand new exchanges in a row, though.
Hello,
My HTC EVO 4g keeps randomly restarting and when the phone is under heavy usage is reboots. I'm going to go into a Spring store today and try and get a new phone as I have the TEP plan.
I currently have CM7 installed on my device. When I bring it in to the Sprint store, should I have the stock ROM installed on there? Or does it not matter?
Thanks for your time and answers!
Regards, th3gh05t
th3gh05t said:
Hello,
My HTC EVO 4g keeps randomly restarting and when the phone is under heavy usage is reboots. I'm going to go into a Spring store today and try and get a new phone as I have the TEP plan.
I currently have CM7 installed on my device. When I bring it in to the Sprint store, should I have the stock ROM installed on there? Or does it not matter?
Thanks for your time and answers!
Regards, th3gh05t
Click to expand...
Click to collapse
Well that would suck... you're going to end up getting a phone that cannot be rooted (for now) and won't be installing CM7. What you really should do is instal the rooted OTA and see if you can hack that for a couple of days first... If not, debate how long you can put up with the reboots.
Thanks for the reply, but at this point, I really just need a phone that works.
Playing games, surfing the web, or using Maps will restart the phone.
I just need to know if they won't take the phone cause it's been "rooted".
Just in root leave s off for someone in the future
Sent from my PC36100 using XDA App
Is anyone at the Sprint store going to freak out and not take the phone back if I don't have stock ROM?
It's ALWAYS recommended to unroot and return to stock before going into a sprint store. Yes, SOME people have gotten lucky and not got caught. But if you do get caught being rooted, they will flag your phone and you will NEVER get it fixed. It literally takes 5 minutes to unroot, just do it just to be safe.
On a side note, are you sure your problems aren't related to the CM7 rom you have? ANY custom rom will have problems. You should try flashing back to stock rom, or at least a Sense rom and see if you still have the same problem.
Okay, thanks for the advice!
Yes, I have tried other ROMs, and I still experience the issue. I've tried Fresh and will be flashing stock ROM to see if that helps.
I've gotten 3 replacements, I leave them s-off and they never check that. I do however flash a stock rom first just so they don't give me any sh*t. And I got lucky last week, my replacement phone came with 2.3 on it but it was s-off. You may get lucky too
We're comin from a pure power source.
Since you're going to be stuck on the stock ROM anyway if you replace it, you might want to first try installing the stock rooted ROM from here and run it for a few days.
http://forum.xda-developers.com/showthread.php?t=1133379
It's quite possible that something in your setup on CM7 is causing the phone to overheat. Or it could be any number of things that might have nothing to do with hardware. Before you give up a rootable phone for one that can't be, you might as well try the stock ROM first. If that clears things up, you can experiment to find the culprit.
bkrodgers said:
Since you're going to be stuck on the stock ROM anyway if you replace it, you might want to first try installing the stock rooted ROM from here and run it for a few days.
http://forum.xda-developers.com/showthread.php?t=1133379
It's quite possible that something in your setup on CM7 is causing the phone to overheat. Or it could be any number of things that might have nothing to do with hardware. Before you give up a rootable phone for one that can't be, you might as well try the stock ROM first. If that clears things up, you can experiment to find the culprit.
Click to expand...
Click to collapse
EXACTLY! If you're having software issues and you're running a custom ROM, before even considering exchanging the phone you should revert to stock to see if the problem truly lies within the hardware itself or the ROM you are using. As far as unrooting, I would not unroot before taking it to Sprint should you have to resort to that. Just flash a stock rooted ROM and you should be fine.
th3gh05t said:
Hello,
My HTC EVO 4g keeps randomly restarting and when the phone is under heavy usage is reboots. I'm going to go into a Spring store today and try and get a new phone as I have the TEP plan.
I currently have CM7 installed on my device. When I bring it in to the Sprint store, should I have the stock ROM installed on there? Or does it not matter?
Thanks for your time and answers!
Regards, th3gh05t
Click to expand...
Click to collapse
i am having the same problem when i went into the sprint store they looked at me like i was lien then took it to the back did a hard reset and told me it was fixed after i told them i did a hard reset over the phone with the teck and when i got home started up my google beta and started playing cut the rope it restarted on me so i called like 3 days later and thet gave me a hard time trying to get a new phone told me that they dint do replacement that i had to call HTC wow my wife had i epic and got 4 replacements no problem so i snaped and thery are now sending me a new phone they said that it will take a week or two cuz they are on back order and yes i unrooted the phone b4 i went in but i had to let you know the BS you might havr to go through
dino1342 said:
i am having the same problem when i went into the sprint store they looked at me like i was lien then took it to the back did a hard reset and told me it was fixed after i told them i did a hard reset over the phone with the teck and when i got home started up my google beta and started playing cut the rope it restarted on me so i called like 3 days later and thet gave me a hard time trying to get a new phone told me that they dint do replacement that i had to call HTC wow my wife had i epic and got 4 replacements no problem so i snaped and thery are now sending me a new phone they said that it will take a week or two cuz they are on back order and yes i unrooted the phone b4 i went in but i had to let you know the BS you might havr to go through
Click to expand...
Click to collapse
Is your period key broken?
mlin said:
EXACTLY! If you're having software issues and you're running a custom ROM, before even considering exchanging the phone you should revert to stock to see if the problem truly lies within the hardware itself or the ROM you are using. As far as unrooting, I would not unroot before taking it to Sprint should you have to resort to that. Just flash a stock rooted ROM and you should be fine.
Click to expand...
Click to collapse
Thanks for the advice! I will let you know how the stock ROM is working!
th3gh05t said:
Hello,
My HTC EVO 4g keeps randomly restarting and when the phone is under heavy usage is reboots. I'm going to go into a Spring store today and try and get a new phone as I have the TEP plan.
I currently have CM7 installed on my device. When I bring it in to the Sprint store, should I have the stock ROM installed on there? Or does it not matter?
Thanks for your time and answers!
Regards, th3gh05t
Click to expand...
Click to collapse
Are you running a CM7 nightly? After build 132 everyone has been having reboot problems.......
Sent from my PC36100 using XDA Premium App
No, I am (was) running the latest RC.
Just unroot and take it back. Shouldn't be a problem.
Sent from my PC36100 using XDA Premium App
Long lurker, posted a few times.
I had a my myTouch since February, and I went ahead and rooted it the first day I got it. Then, when I discovered Virtuous Unity 2.35, I went ahead and flashed it, along with the Panache radio and theme (Revolution). After about 2 days, the phone started acting up. It would freeze about 1 minute into boot and would require a battery pullout to turn back on. On it's fourth time of freezing, I pulled the battery out as usual, and put it back in. The phone never came back on again. I tried everything, from using another battery; waiting ten minutes before putting it back in; putting in the charger didn't help, as there was no charging light.
I sent it back to T-Mobile and got a new one. Again, I did the same for the new one, and heard about the bad emmc chips. I went ahead and looked at mine, and with dimay, I found out I had a bad one. After 3 days, the same thing that happened to the old one happened to the new one.
Seriously, what is going on here? TWO bricks within a couple of days apart? Also, why is T-Mobile still releasing these dead chips?
My question is, "Is there any way to fix this full brick, if at all boot into recovery?" Thanks!
nzube14 said:
Long lurker, posted a few times.
I had a my myTouch since February, and I went ahead and rooted it the first day I got it. Then, when I discovered Virtuous Unity 2.35, I went ahead and flashed it, along with the Panache radio and theme (Revolution). After about 2 days, the phone started acting up. It would freeze about 1 minute into boot and would require a battery pullout to turn back on. On it's fourth time of freezing, I pulled the battery out as usual, and put it back in. The phone never came back on again. I tried everything, from using another battery; waiting ten minutes before putting it back in; putting in the charger didn't help, as there was no charging light.
I sent it back to T-Mobile and got a new one. Again, I did the same for the new one, and heard about the bad emmc chips. I went ahead and looked at mine, and with dimay, I found out I had a bad one. After 3 days, the same thing that happened to the old one happened to the new one.
Seriously, what is going on here? TWO bricks within a couple of days apart? Also, why is T-Mobile still releasing these dead chips?
My question is, "Is there any way to fix this full brick, if at all boot into recovery?" Thanks!
Click to expand...
Click to collapse
I'm just trying to learn from experience after all the flashing when you started to get freezing and acting up did you flash that one file on Virtuous Unity 2.35 page that states if you get phone freeze to flash the file
nzube14 said:
Long lurker, posted a few times.
I had a my myTouch since February, and I went ahead and rooted it the first day I got it. Then, when I discovered Virtuous Unity 2.35, I went ahead and flashed it, along with the Panache radio and theme (Revolution). After about 2 days, the phone started acting up. It would freeze about 1 minute into boot and would require a battery pullout to turn back on. On it's fourth time of freezing, I pulled the battery out as usual, and put it back in. The phone never came back on again. I tried everything, from using another battery; waiting ten minutes before putting it back in; putting in the charger didn't help, as there was no charging light.
I sent it back to T-Mobile and got a new one. Again, I did the same for the new one, and heard about the bad emmc chips. I went ahead and looked at mine, and with dimay, I found out I had a bad one. After 3 days, the same thing that happened to the old one happened to the new one.
Seriously, what is going on here? TWO bricks within a couple of days apart? Also, why is T-Mobile still releasing these dead chips?
My question is, "Is there any way to fix this full brick, if at all boot into recovery?" Thanks!
Click to expand...
Click to collapse
As of now, there is no way to fix it. Strange though, my old one had a dead eMMC as well but I.could still go in CWM
Sent from my HTC Glacier using xda premium
Always remember, after rooting you should Check your eMMC
If the eMMC is good, try flashing otherwise report it to T-Mobile
SEMO4G is the "good" one & M4G2DE is the name of the "bad" one.
__________________
If this replay helped, please hit the "Thanks" button.
Flashing that one file? I don't know which one you are talking about. If you saw it, could you point me to it, please?
Also, if your eMMC is bad, you could report it to T-Mobile? How? I was asking them about the eMMC, and they (the tech department) knew nothing about it. -__- Yeah, I had the M4G2DE. Although looking at this thread (http://forum.xda-developers.com/showthread.php?t=1081243) it seems that the SEM04G is still bad, or am I just confused?
Don't get confused. If you get just SEMO4G it is "good"
Try for yourself
Download terminal emulater
Type in:
su
(to gain root permission)
Than type in
cat /sys/class/block/mmcblk0/device/name
__________________
If this replay helped, please hit the "Thanks" button.
If your eMMC is bad, don't try to flash any custom Rom.
If you try to modify the system, the phone will get damaged.
febycv said:
Always remember, after rooting you should Check your eMMC
If the eMMC is good, try flashing otherwise report it to T-Mobile
SEMO4G is the "good" one & M4G2DE is the name of the "bad" one.
__________________
If this replay helped, please hit the "Thanks" button.
Click to expand...
Click to collapse
No. Check eMMC before rooting. That way, you will not have warranty problems.
Sent from my HTC Glacier using xda premium
Just to throw it out there though, it's not definitive that your phone will brick when you have the bad eMMC.
I used to have the bad eMMC before I exchanged it out for an unrelated problem. I flashed a ROM on that phone about couple times a week for 3-4 months with no issues. I've even seen some that have had the bad chip since day one and flash almost every CM7 nightly and still haven't had a problem. So my guess is that if your bad eMMC doesn't fail fairly soon and quick then you should be in the clear.
Ive had the bad eMMC since day one and have flashed many roms of all kinds. Knock on wood, i have had no problems
cowboy2844 said:
Ive had the bad eMMC since day one and have flashed many roms of all kinds. Knock on wood, i have had no problems
Click to expand...
Click to collapse
Yeah my point exactly. All of the failed ones are highly documented so every one thinks every "bad" eMMC is going to fail but who knows how many people with that eMMC has actually not failed?
I'm another one with the "bad" eMMC, so far no problems flashing roms.
I have the good eMMC chip and this is my 3rd failure. -.- after rooting using visionary+ it seems like data partition gets borked either while formatting or flashing rom.
CWM outputs unable to mount /data
lmao
anyway downloading pd15img.zip lets see what happens (I know I will lose root and my eng bootloader but oh well atleast i might get my phone back xD)
_ice_ said:
I have the good eMMC chip and this is my 3rd failure. -.- after rooting using visionary+ it seems like data partition gets borked either while formatting or flashing rom.
CWM outputs unable to mount /data
lmao
anyway downloading pd15img.zip lets see what happens (I know I will lose root and my eng bootloader but oh well atleast i might get my phone back xD)
Click to expand...
Click to collapse
Have you tried format the SD card with sdformatter v.2.0 or any other program to fat32 then try gain full root and put CWM on it to see if it stops that unable to mount problem
Sent from my HTC Glacier using XDA App
Just got another replacement, and looked up eMMC chip. SEMO4G!
With good screen as well! Hopefully, no more bricks.
Yeah I have the bad eMMC on a Mobilicity Panache. But so far nobody with a Panache (as opposed to MT4G) has reported failure, even though at least half of them have the "bad" eMMC. And seeing as a thread I started here is the only guide that speaks directly to rooting the Panache, I would expect any bricks to be reported on that thread.
Hello guys I'm def a noob at all this and bricked my continuum about three months ago and got the galaxy nexus. im with verizon and i kinda gave up on it and now my nexus is acting up and after 6 replacements its still power cycling so im trying to go back to my continuum til i feel comfortable enough to root and run a new rom on my nexus. ok story goes i have a samsung continuum its rooted with super one click and i wanted to try new roms. well i stayed up all night reading for hours on how to do it and was really tired and got the pit file and tar file mixed up in odin i believe. dumb i know. well all i had was gray screen after that it would turn on and off but none of the hard keys work and wouldnt charge i can feel it getting warm now when i start charging it but thats it the screen wont even come on. i tried making a jig today with resisters and nothing happened. i just want to bring this phone back to life. it is a true bricked phone it does nothing. ive been reading the forums here for about 6 months i know u all hate when noobs post but i have exhausted all options. ill figure out my pos nexus soon enough its the biggest dissapointment i ever invested in. so anyways plz help if u can thanks. i love this site its hepled me through everything ive done so far
samsung continuum/verizon/rooted superone click
stock kernal
stock rom