I went to flash a clean copy of MK2 onto my girlfriend's phone for her last night, when we first got our S4's back in 2013 or so I froze all updates and hers has basically sat there ever since. Well anyways, I went to flash it and odin failed right before it was to finish system.img.ext4 EVERY.SINGLE.TIME. I tried both of my pc's, I reformatted one, I used 7 different cords, different usb ports and NOTHING was working. At around 10 a.m. I decided I needed to try someone else's pc altogether so I went to my grandparents. Mind you I had been working on this phone since 8pm the night before since I have no work today and my girl needed her phone back in time for work. I get there and load the drivers and all the necessary files and then start the flash,First try it passes. I guess I'm trying to say for anyone searching, if your pcs keep failing try someone else's. The weird part is my pops has the exact same phone as her and I flashed his phone less than two weeks ago using my machines so that was very odd.
Related
I have read and read and read. I have "bricked" my phone in the past and fixed it. I have used, tested, and flashed many roms from this site (Thanks to all cooks for their work!) but I still consider myself somewhat 'new' to troubleshooting.
I woke up this morning to make some important phone calls today and as luck would have it, my phone was stalled again. It's been doing that for a few weeks now. My last flash was Open Touch 5.0 UL I believe (either that or 5.2 biggy) and it has been working great except for the occasional freeze.
The problem is now it won't boot up after it froze this morning. Just sits at the boot screen
So I've tried my other methods of fixing it...
Except this morning nothing is working. I have tried flashing with Orig. T-mobile ruu, tried SD flashing with the RUU_signed.nbh, tried restarting the computer, phone, removing battery and sim... NOTHING! When trying the sd flash (which I've never done before today, it reads and tells me to push the down button but then goes to bootloader screen and just sits there. With the RUU I'm getting err 300 but I'm using the SAME RUU (4.10...) that I've used in the past to reflash my phone AND tried the new one (4.26...)
Possible problem: Does it matter what kind of usb cable you use? I don't have the normal one I use as I am not home but I figured usb is usb...
I've read about it being a motherboard issue, how common is this?
I've read somethings about MTTY, would this apply to me??
Please help, anyone who has any suggestion, I'll try it!!
Stats:
IPL 4.10.0002
SPL 4.10.0000
NOT hard-spl'd
Wing w/ Open Touch Project 5.0 or 5.2
By The Way...
I decided to post this in this section as well because it pertains to a problem with Open Touch 5.0 or 5.2 as it is directly related to my problem.
Since you are not hardspl, did you try to go to the bootloader and then flash the original Tmo stock rom from there?
Yes I did, all I am getting is an error 300... I wonder if it my usb cable though cause I'm using one that is meant for a TV to CPU device. (it's a little thicker than my other cable which is at home unfortunatly)
To be honest, I've tried two different Tmo stock rom's and I can't even get it past 0% before getting the 300 error. Even though one of the two I've used before for this situation, the 4.10
epicphotoeye said:
Yes I did, all I am getting is an error 300... I wonder if it my usb cable though cause I'm using one that is meant for a TV to CPU device. (it's a little thicker than my other cable which is at home unfortunatly)
To be honest, I've tried two different Tmo stock rom's and I can't even get it past 0% before getting the 300 error. Even though one of the two I've used before for this situation, the 4.10
Click to expand...
Click to collapse
Have you tried your regular wing USB?
Sometimes the metal inside the USB varies in number even if they have the same size..
Hi I had the same problem after flashing the phone of a collegue of mine.
After reading forum after forum I found the goldcard method.
It is found here: http://forum.xda-developers.com/showthread.php?t=417930
It is a bit tricky to get it working but eventually it did work. And the phone is up and running again.
good luck..
PM me if you are having problems.
this happened to me.im new at this so i was jus lookin around in the phone and i found that when you install opt 7.5 biggy it changes me from tmobile to at&t and i changed it back and my phone worked with no problems.
I was slow around flashing to the latest baseband but finally took the dive today and the program locked up at 5% for like 2 hours before I yanked it. Now it just gets to the "S/W Updater" screen regardless of what I do (NVFlash recoveries, roms, kernels, format, hard reset, etc). When I try to update it again, it just immediately says it's already the latest version. Why won't it just flash over it like most flashing programs.
Tmobile is pinging me $20 for a replacement but I have a really good G2x. Is there anything I can do to revive mine or is it toast? ADB commands or something? I have clockworkmod on there now, but I'm not really getting anywhere.
[Update]
Use this NVFlash method to completely format your phone, re-setup your partition tables, and flash the stock GB rom:
http://forum.xda-developers.com/showthread.php?p=17258229
Dead
It's dead. Same thing happened to me and to many many others. Turn it back to TMo and take the hit--it's not worth the time playing around with it any more.
Call TMo and ask to be forgiven the $20. If you've been a long and loyal customer they might even do it.
Your new phone should come with 2.3.3 installed. Mine did and I've had no trouble with it--it's finally settled down into a very usable and fast phone. Stock ROM. But I won't buy another LG phone again for a very long time--not until they hire a few software engineers who know what they're doing.
No my friend. I got revived!
http://forum.xda-developers.com/showthread.php?p=17258229
It totally erased everything, formatted everything, reset all the partitions, and flashed the GB Stock rom.
Booted up, NVFlashed CWM, Restored my Nandroid backup, viola!
Thought it would be a good thing to make more available. It was in the Android development thread but the title is tricky as its listed as a rom (which I guess it kinda is).
Sent from my LG-P999 using xda premium
i dont understand why people get stuck on this. ok
when i did it. the LG Tool stop responding on half the period % and my phone had the S/W updater screen so what i did i click on closed unpluged my device then open the LG Tool again plug my device and the LG TOOL said that there was a problem if i wish to continue with my update i click yes and it kept doing till it was done and my phone was fine with 2.3.3
The mistake you made was just stopping the update. Mine did the same thing. Instead of listening to the stupid message about removing the battery, etc. I just removed the usb cable, waited for the beep, put the cable back in, waited for the beep and then pressed "restart" on the update. It completed perfectly after that.
Well I've gone through all of those scenerios and it would attempt to reflash it, but the last time it got stuck on 5% for about 2 hours... no error message or anything. After 2 hours at 5% I pulled the plug. When it is in the middle of "flashing" and gets locked up, there is no Cancel button or Restart button like when it errors out.
I had no errors, just a locked up program. Regardless the posted link really fixed me up and got it working again.
I changed the title and updated the OP with the solution.
Well... Tried to plug my Blaze in tonight and got the above error. I've tried a few different suggestions I've found on the web, but none seem to work. I just got the phone on sat and rooted it. I did a data wipe and still get the same error. Any one know how to fix this? If not hopefully the Tmobile store will replace it since it's just 5 days old.
After leaving it plugged in and turned off all night it appears to be fine now.
I woke up today noticing that my Samsung device kept rebooting. I thought that was pretty odd so I tried to enter factory reset. However, instead of going to Samsung's factory reset screen I got to Kingroot's recovery screen (This happens every time). Everything is in Chinese so I can't figure it out. I rooted my phone a couple weeks ago and this has never happened to me before. I don't know what to do and much help is appreciated... I use my phone for a lot of things.
I already tried using Odin but it kept failing, it would always fail at "Nand write start". Tried the image I was supposed to flash at ( http://stockroms.net/file/GalaxyS6/SM-G920F/Netherlands/T-Mobile/G920FXXU1AOCV_G920FDNX1AOCV_TNL.zip ) but that didn't seem to work, so I tried pretty much any of these; http://forum.xda-developers.com/tmo...irmware-sm-g920t-firmware-odin-guide-t3077706 tried different usb ports too and both my laptop and computer.
My Nexus 6P was recently broken but my GF (on accident lol but still she's lucky I love her. If it had been anyone else, like one of my guy friends, I prolly woulda had to hit em haha j/k)
Anyways, borrowed a friend Acatel 4060a IDEAL. He dropped it off last night. I then factory reset it and all that, hooked up my google accounts, downloaded WoW - Hearthstone and my Drastic DS emulator, and everything was fine. Then this morning I was bored and figured I would see about if this cheap POS is rootable. Which it is, and I proceeded to do so. Everything worked fine the whole morning, til bout 45min ago, I was leaving to run up to the AT&T store to get a SIM card so I could hook it up to my account, and on the way out the door I reset it cause I just had finished updating some apps in the play store. It then became stuck at the Bootlogo. So I then did what you always do in this case, try taking the battery out and the SD Card, then putting just the battery back in, see if that works. Didn't. Tried just resetting it a few more times, and let it sit for like 20min hoping maybe it was just taking extra long. Nope. So I then booted into the stock recovery wiped the cache and did a wipe/factory reset. Still nothing, still stuck. Tried a couple more times. Still nothing. And this phone apparently doesn't have a download mode, so I can even plug it into my laptop cause it can't make a connection obviously without being in download mode, or fully booted into the OS. I am at my wits end.
I'm hoping one of you fine peeps might have a suggestion of something I could try that I perhaps have overlooked or didn't know about. Learn something new every day right So please HELP ! lol its gonna be at almost 2 more weeks til I get paid and will be able to afford the Insurance Deposit for them to send me a replacement Nexus 6P, and I got way too much going on right now and I can't go two weeks without a phone.
I'm All Ears !
Silicon Knight said:
My Nexus 6P was recently broken but my GF (on accident lol but still she's lucky I love her. If it had been anyone else, like one of my guy friends, I prolly woulda had to hit em haha j/k)
Anyways, borrowed a friend Acatel 4060a IDEAL. He dropped it off last night. I then factory reset it and all that, hooked up my google accounts, downloaded WoW - Hearthstone and my Drastic DS emulator, and everything was fine. Then this morning I was bored and figured I would see about if this cheap POS is rootable. Which it is, and I proceeded to do so. Everything worked fine the whole morning, til bout 45min ago, I was leaving to run up to the AT&T store to get a SIM card so I could hook it up to my account, and on the way out the door I reset it cause I just had finished updating some apps in the play store. It then became stuck at the Bootlogo. So I then did what you always do in this case, try taking the battery out and the SD Card, then putting just the battery back in, see if that works. Didn't. Tried just resetting it a few more times, and let it sit for like 20min hoping maybe it was just taking extra long. Nope. So I then booted into the stock recovery wiped the cache and did a wipe/factory reset. Still nothing, still stuck. Tried a couple more times. Still nothing. And this phone apparently doesn't have a download mode, so I can even plug it into my laptop cause it can't make a connection obviously without being in download mode, or fully booted into the OS. I am at my wits end.
I'm hoping one of you fine peeps might have a suggestion of something I could try that I perhaps have overlooked or didn't know about. Learn something new every day right So please HELP ! lol its gonna be at almost 2 more weeks til I get paid and will be able to afford the Insurance Deposit for them to send me a replacement Nexus 6P, and I got way too much going on right now and I can't go two weeks without a phone.
I'm All Ears !
Click to expand...
Click to collapse
I'm assuming you used Kingroot to root it? It's a common issue for Kingroot to cause a bootloop.
Typically, this is fixed by re-flashing the stock firmware but you have to get it to connect to PC to do it, and that's only if the stock firmware is even available.
Sent from my SM-S903VL using Tapatalk