Bear with me as I painfully type this out on my evo...
Earlier today, I tried to flash the new miui rom. It wouldnt go past the moto screen.
I try mounting each partition by hand, when I get a cannot mount error.
I try again and it mounts fine.
Try again.. and it fails.
The logs show it as unknown and sometimes as ext3 partition.
This all started from flashing cwm touch( which never showed up, it's the same cwm as before) via CWM(apk) as an attempt to get the amora installer working right.
i figure i need to fastboot and flash jokers custom cwm again. if that doesnt work, ill just get a replacememt until GS3.
Sent from my PC36100 using XDA
Update/Bump:
I'm trying to re-flash CMW, however...
When starting Fastboot protocol, it tells me that my battery is too low.
This would be all fine and dandy, but I'm unable to charge my phone.
Plugging it into an AC socket results in it being on the Moto screeen for hours (tested and proven). No battery screen comes up / battery is not charged.
Plugging it into a USB port starts the same thing.
going into CWM doesn't do anything either for the battery.
I don't have a spare battery either
I think I'm pretty screwed here.
My EVO won't charge with the case on, and the HTC Arrive was just a horrible phone in general lol...
Anything you can think of to try and get this fixed until I get my replacement or the Galaxy Nexus next week?
Related
I just flashed the Frankin Final rom on my vibrant and all was going well until I rebooted it and now the damn thing seems to be in a boot loop of some sort, but this is different than all others I have seen cause it goes to the samsung screen like normal and then it goes to a totally different screen that is only half size and is jumbled up and not a damn thing is readable. When I plug in my USB to the computer not only is it seen by the computer but it goes to the battery icon and then back to that screwed up - half sized screen. Please someone help.
Go back into recovery and reflash the rom you had installed previously. Or do a nand backup. You did back it all up before you flashed v4 as you should have, right?
I do have it backed up from v3 but it wont even get recognized by adb nor odin. Its the strangest friggin boot loop I have ever seen. When the vibrant screen goes blank then the strange unreadable screen comes on for about 2 seconds and then the vibrant screen comes on and thats over and over. I do have a hardware locked phone so I guess I will have to screw with it when I get home. I did have it in download mode but now I can't even get it to that. Is that USB that came with the phone the only usb that can be used when getting into download mode as I had no troubles at home but I am using my USB from my nexus one at work and its all screwed up.
Did you mean DON'T have a hardware locked vibrant?
I got it about a 2 months ago so I don't know if its locked or not.
Heres what happened in detail.
I rebooted via Rom Manager into the stock recovery.
I installed packages as I have the clockworkmod recovery as update.zip in my 14G sd
I backed up my current Frankin ver3 rom
I erased all userdata and such like I should when flashing a new rom.
I installed the Frankin Final Update
I rebooted the phone like normal and the BAM.
A never ending boot loop that wont even get recognized by my computer.
I cant even plug it into charge as it won't stop bootlooping. the
battery charging icon comes up but then it goes to that funky ass
screen and back to the charging icon. when I unplug the charger it
switches to the Vibrant screen and then the messed up screen. I
really think its bricked as its gotta be the boot image that is
screwed up.
I am very sorry if I am wasting your time on this as I do know how to
properly flash a rom on a phone but this phone is not like my G1 nor
my Nexus. Its about as flaky as a phone can get in my opinion and had
I known it was this flaky I never wouldve gotten the damn thing. I
guess I am going to Tmobile and tellin them the OTA update did this as
there is no way in hell to tell. Not even the splash screen comes up.
Its really bricked.
I just wanted to say that this website and you all developers are the BEST people I have ever followed. This is the very first post I have made and I really do think I f--ked big time. No matter, what you all have done for the G1 and Nexus blows my mind. I never owned a iphone and never will and I think I might say the same about this vibrant. Getting the Nexus bricked is nearly impossible but this Vibrant is to damn confusing and with the lag fixes and crap that I am leary about goin to the store and replacing mine with a new one. Wish me luck.
You may want to try loading Eugene's Froyo Rom that does not brick. Once that is done, try and install Frankin Twiz.
I tried and when the computer won't even read the connection all is bricked. good news though, I went to the tmobile store last night and showed the guy what happened after a OTA Update. he was totally understanding about it. He said it was the white screen of death and that I will have another shipped out the following day. Thanks again for all your help and especially the moderator for putting up with my crap. You all are the bomb-diggity.
I always just boot into recovery and flash say Vibrant7 that always seems to work for me. From there I flash whatever other rom I want.
Recovery meaning
Hold down your Vol + and -
Push Power.
Actually I get scared that I might screw things up by entering recovery through clockwork ( laugh at that now huh) so I always went to the stock recovery and updated my packages with the clockwork recovery file that was named update.zip. I think I had a issue with my phone from the get go as it never would enter download mode unless I was connected to only my samsung charger and no others. I tell ya it was a strange phone and to top it all of the tmobile dude showed me a g2 they had in stock. Nice phone I tell ya but it ain't no Nexus one. Thanks again for all your help guys. Keep the little green dude alive.
My friend is having some problems charging his Atrix. Basically, the phone will not charge or recognize a charger at all except for under certain circumstances.
Some background info: I helped him unlock his bootloader and install 4.5.91 way back when it came out. No problems there, it went well. All was fine until the 4.5.141 OTA update came around. He got the OTA notification and clicked update because he didn't know anything bad would happen. Luckily it didn't brick him like it did a lot of people, but he said it gave him an error message during the install and it would not boot after that, stuck at the Motorola dual core screen. I took a look at it and managed to get into recovery and flash back to 4.5.91. All was fine until it was time to charge the phone. It wouldn't recognize any charger. I tried flashing to tons of different roms, wiping everything, even restored a full nandroid recovery from my working Atrix on it. His phone will charge and will be recognized by a computer immediately after we flash a new rom, and will continue to charge for as long as we leave it plugged in, but if we unplug it then after a short time (like under 30 mins) it will not recognize a charger if we plug it in again. Wiping data alone will not make it start charging again, only actually installing a new rom will. Deleting battery stats does nothing. The closest we have gotten to fixing it was when I made a nandroid on my Atrix and then restored it on his (my backup was from Joker's CM9); after the restore, it would charge for a while, and we unplugged it and waited to see if it would do the same thing as it always did and stop recognizing a charger after a few minutes. About 30 minutes later it stopped recognizing the charger as usual. We played with the USB debugging setting (enable, plug in, see if it recognized the charger, disable, plug in, see if it recognized it, etc) and after messing with that setting a lot it recognized the charger once, but then when we unplugged it the phone wouldn't recognize the charger again. We could not reproduce this again.
To summarize what we have tried and found to work:
-flashing a rom will let the phone charge/let a computer recognize it for as long as we leave it plugged in after the first boot (we have tried every rom under the sun, they all do the same thing)
-restoring from a nandroid backup will have the same effect as flashing a rom
What we have tried that didn't work:
-different cords; have tried them all, both OEM cord and third party, this is not the problem
-wiping all data/factory reset doesn't do anything
-cache wipe doesn't do anything
-wiping battery stats doesn't do anything
I have also tried fastboot flashing back to 4.5.91, CWMing back to 4.5.91, using the unbrick scripts and stock restore scripts people have made, nothing will fix it.
If anyone has any suggestions or can refer me to anywhere with more info on this I would appreciate it, I have searched high and low and can't find anyone with a problem quite like this one. I don't even know if it's a hardware or software problem, if you guys know a way to determine this it would be helpful.
Have you tried a wall charger?
Yeah, both the stock one and a different one I have, neither work.
No one has any advice or ideas on this? Does anyone know if Moto does repairs in this type of situation with a voided warranty because of an unlocked bootloader, or does anyone know who may be able to fix this if I can't get any help from the forums or figure it out on my own?
Problem: Phone will not charge while powered off. Phone freezes on "Galaxy S III" screen. I can sometimes get my phone to boot up if i try installing the clockwork.tar or stock image file(boot-stock-sprint-sph-l710.tar) in Odin. When i can get into my phone and it boots up my battery is at 1% and a message pops up saying "charging paused: battery temp too high". When my phone is off and plugged into a wall a yellow triangle with a thermostat appears and doesnt seem to charge.
Background: My phone is the Sprint version of the GS3. My phone is rooted. I haven't touched any files pertaining to the system nor have I tried removing any bloatware. I haven't flashed any ROMs.The only posibile thing i have done that may have caused this is restoring apps in TB that were originally on my Droid X (only restored data on 2 games and amazon app store. didnt restore any system files or apps).I installed CWM using Odin(not adb). I rooted my phone by flashing the superuser.zip file in clockwork recovery. My phone was rooted for over 24 hours and functioning fine prior to bricking/battery problem. I currently can get into download mode but not CWM recovery.
My current plan moving forward is to try and get a new battery/find someone close to me with a gs3 so i can charge my battery before messing with my phone. I am afraid that if i try flashing anything in Odin now my phone may die in the process and mess my phone up any more than it is. One i get a charged battery i plan on trying to get back into CWM and restoring my non-rooted backup I made, or wait on a Full stock Odin package for my phone.
Also does anyone know if the Samsung Galaxy S III I9300 battery is compatible with the US Variants? I found this on Ebay -> http://www.ebay.com/itm/2-x-2100mAh...Accessories&hash=item3a753b6680#ht_2405wt_952 and figured it might be worth a shot. I had a similar charger as shown in the picture for my Droid X and it worked fine.
If anyone has any ideas as to why this happened to me or has any advice/suggestions i would greatly appreciate it.
So here is the deal, i went to flash a new ROM last night. I usually do everything on my phone as my computer does not normally recognize my USB for some reason, but anyways, i tried flashing last night and the flash failed. and i have no back ups nor can i plug in a USB and transfer anything to my "sd" portion of my phone because it does not work. Oh and when i go back to stock (Factory reset), when i try to boot into system. It just shoves me back into recovery mode, someone please help. I'm usually pretty good with this stuff and if i don't know a quick Google search is sufficient. But i have found nothing. This is my last resort.
FYI: I believe it failed because my recovery is an old version, I'm using team win recovery touch. not sure if that changes anything
Dylerium said:
So here is the deal, i went to flash a new ROM last night. I usually do everything on my phone as my computer does not normally recognize my USB for some reason, but anyways, i tried flashing last night and the flash failed. and i have no back ups nor can i plug in a USB and transfer anything to my "sd" portion of my phone because it does not work. Oh and when i go back to stock (Factory reset), when i try to boot into system. It just shoves me back into recovery mode, someone please help. I'm usually pretty good with this stuff and if i don't know a quick Google search is sufficient. But i have found nothing. This is my last resort.
FYI: I believe it failed because my recovery is an old version, I'm using team win recovery touch. not sure if that changes anything
Click to expand...
Click to collapse
Well u need to get something on the phone to flash. I suggest you work on the usb issue or get a micro sd reader.
Well the "sd" card is the integrated one i cant remove. And i have tried fixing the usb but nothings seems to remedy it. Very rarely i can get it to work but it will stop working the next time i try to plug it in. I have a ROM i can flash, but the recovery fails to flash it every single time, even after clean install. im fairly sure its my recovery that wont let me flash the rom but i also cant update that till i figure out how to at least get the phone to a homescreen. I honestly dont know much about odin but it looks like i may be able to try and flash it there, is this correct?
Okay, I want to start by saying I am truly sorry if this has already been looked at. I truly spent 20 minutes searching and could not find anything that address this problem.
Im going to give you the long story because, I am actually really in need of help.
My friends owns a droid x2, ?.?.5 (sorry I cant honestly remember but, its the gingerbread ending in .5)
Her husband decided to root her phone for her, and it was in Chinese and only had a partial root. Frustrated she brought it to me because, well I have a working knowledge of google, this forum, and have flashed and rooted many phones.
I managed to change the language, and root the phone (using DX2_batchroot), I installed a custom recovery (its an apk ), I also think I installed the Recovery BSR (that will make sense in a second)
I booted into custom recovery, I made a backup. Then I went about wiping caches so I could install a custom rom. I wiped all the caches, I formatted the internal memory, and then I accidentally hit "boot now".
The phone gets the the "M" and says "Failed to boot 1"
If I try holding the power and down button it just flips off completly.
I cant scroll thru the menu, I cant get the computer to acknowledge its on.
It has been plugged in the hole time.
So what do I do, and what DID I do, so I never do it again.
Thank yo
Update
Since this happened I have left it on the wall charger and checked it out occasionally.
Well it still won't boot into recovery but... It is now willing to play ball when I press volume down and then plug in to the computer. Sadly it then tells me that the battery is too low.
Now, I *guess* it could be, except after rooting and before rebooting into recovery to make my first backup I had the phone off andplugg ed into a wall charger for 2 hours.
Again, any help you can offer
Often if ROM won't boot, charging does not work either.
Will need a charged battery, or a TBH factory cable adaptor.
See my low battery options in my list.
sd_shadow's (themib) [Collection] of Links for Droid X2
Sent from my Amazon Kindle Fire using Tapatalk