So my tablet got unplugged during the NVFLASH process shortly after formatting the partitions. It is now stuck in NVFLASH. Is there anyway I can reboot it or do I need to wait for the battery to drain and for it to die.
I have been having problems with my power button not responding when pressed so I filed for an RMA. They said to send it back but I wanted to flash back to stock before sending it. Could I send it to them like this ans say that it just stopped working or do I need to reflash to stock. Its a B50 so I know it can be fixed I just dont want to waste time waiting.
If you still have service on your tf they will repair your power button , i don't know if they flash new software files because of your button. What i do know they have to test your button and then they will see that it won't boot.
So with a bit of luck they will flash new files bcause of the whole startup problem with the power button.
Good luck
Let the battery drain, and NVFlash to stock. It will seriously help if you don't want to deal with any crap if they see you were rooted.
You don't have to let the battery drain.
When I bricked mine, my battery was low when I started the nvflash process, then the process failed b/c I forgot to put the files where they were needed, so I unplugged my transformer, let it charge for a little bit more so the battery wouldn't die while I found the files needed, then I plugged it back into my laptop and did a reboot into nvflash and let it do it's thing.
So I am having a weird issue with nvflash; it randomly quits mid-process. Sometimes nvflash stops when initializing the boot loader while other times it starts formatting the partitions and then stops. A few times it has even kicked my tablet out of apx mode.
Has this ever happened to anyone?
Is your cable bad? That's all I could think of, try several different USB ports as well.
Thing O Doom said:
Is your cable bad? That's all I could think of, try several different USB ports as well.
Click to expand...
Click to collapse
I tried multiple usb ports on two different computers. My macbook running ubuntu and a windows pc both have the same issue. I will try using another cable but dont know if that will help.
If I send the tablet back in this condition (no OS and NVFLASH not working), will they say its user error?
So I was never able to get the tablet to boot up. I am not sure what the issue was but I believe that the battery was almost dead but not quite. This left the tablet in nvflash mode, unable to charge. When I tried to transmit data however, it created too much of a load on the tablet and it would fail. I sent the tablet to asus as is and I just got a notification that they fixed everything and are sending it back to me. In case somebody is in the same situation as me it seems they did not care that all the partitions were formatted blank, just that there was no custom rom installed.
Good that it was resolve, and that they didn't give you any trouble.
Related
I'm running Darky's 6.0 Rom with xcaliburinhand's kernel. I began to realize my phone wouldn't charge when I plugged it into the charger. I tried flashing to stock using odin but once I'd get into download mode via the long-press menu when pressing the power button (because other methods that involve plugging in the cord and pushing buttons doesn't work since it's not recognizing the cable). I don't think it's a faulty cable or port since everything was working before I flashed the ROM. Anyone have any ideas on how to get the computer to recognize the phone so I can flash stock??
edit: When I do plug in the phone to the computer, I'll sometimes get a message saying the device isn't recognized.
(And yes I do have drivers installed.)
Also, I tried flashing other ROMs via CWM but I get error messages on all that I try. Such as can't mount .dev/block/st19 and can't mount SYSTEM
Edit: After a while I've noticed that it in fact is charging but the battery icon doesn't show it's charging. And in settings it shows it's not charging. But battery level is increasing
Have you tried a different computer to see if the usb port is bad?
Sent from my SAMSUNG-SGH-I897 using XDA App
Does it charge when you plug it into an ac adapter? You can also try reinstalling the drivers and see if that helps and/or try a different usb port. I've had issues with the drivers before.
Also try a different cable. My cable became defective somehow where xp no longer recognized it, yet would still show charging on the phone. All was back to normal after I got another "data/sync" cable.
Sent from my SAMSUNG-SGH-I897 using XDA App
I don't have a different computer to try it on but I've tried different ports. It's not the computer because it still won't show it's charging when I plug into the wall. And yes I think it does charge when it's plugged into a wall but it doesn't show it or turn on when I plug the cord into the phone. I don't think it's hardware. It has to be software since it just happened when I flashed the ROM. Also whenever I open contacts I get a force close of acore (a little off-topic, but still another issue). I also have tried reinstalling drivers. But also, it doesn't work when plugged into a wall charger. So it's definitely nothing with the computer
I just need to know if anyone knows how to force the computer to recognize the phone so I can flash to stock and hopefully that'll resolve the issue
update: I also tried v7 via CWM and no luck still.
Well I update xcaliburinhand's kernel by transferring it over bluetooth and that installed fine over CWM. Then I tried updating Darky's rom to v7 and that worked too. I booted up and got a million FC's. Tried to get into recovery and it just sits at AT&T screen. It's very tricky to even boot up the phone, and even when I do I can't do anything because of all the Force closes. I can't get back into recovery mode with any button combinations and when i try via the power long press I can get into download mode fine, but I still have the issue with the computer not recognizing it, so it's useless. Anyone have any ideas????? I'm getting sick at staring at this AT&T boot screen for so long. I have no idea of what to do next. Someone please help!!
Sorry to say it, but it sounds like your phone has serious hardware problems.
opcow said:
Sorry to say it, but it sounds like your phone has serious hardware problems.
Click to expand...
Click to collapse
Is there nothing I can do? Because I'm pretty sure I'm way past return date, and I didn't have a warranty.
well it sounds that you have messed it up. your installation is probably wrong somewhere, in fact i am even sure, but i dont want to hurt anybody.
do a clean install from scratch starting everything with ODIN (ie download mode)
first off all load a ancien but correct kernel, because in fact you don't even know what you lagfix is. load one of the zenkins kernels (ya-ok) no matter one of the recent ones.
start and go back into recovery, and adjust lagfix to ext4 only. not ext4/ext2
don't use not either the integrated voodoo.
it will format everything.
the again into recovery and disable lagfix
that will then reformat everything into rfs, that what it's needed.
then you go again into reboot and flash one of the ancien .tar files like xwjpa.
and then it shoudl startup.
and you can take it from there.
zoubidou said:
well it sounds that you have messed it up. your installation is probably wrong somewhere, in fact i am even sure, but i dont want to hurt anybody.
do a clean install from scratch starting everything with ODIN (ie download mode)
first off all load a ancien but correct kernel, because in fact you don't even know what you lagfix is. load one of the zenkins kernels (ya-ok) no matter one of the recent ones.
start and go back into recovery, and adjust lagfix to ext4 only. not ext4/ext2
don't use not either the integrated voodoo.
it will format everything.
the again into recovery and disable lagfix
that will then reformat everything into rfs, that what it's needed.
then you go again into reboot and flash one of the ancien .tar files like xwjpa.
and then it shoudl startup.
and you can take it from there.
Click to expand...
Click to collapse
Please read earlier posts... I cannot get into recovery mode and the computer won't recognize download mode.
mikel.canovas said:
Is there nothing I can do? Because I'm pretty sure I'm way past return date, and I didn't have a warranty.
Click to expand...
Click to collapse
Unless you have a bad USB cable causing all the weirdness with both charging and the PC connection, but that wouldn't explain all the other strange errors. It sounds to me like the phone is terminally ill.
opcow said:
Unless you have a bad USB cable causing all the weirdness with both charging and the PC connection, but that wouldn't explain all the other strange errors. It sounds to me like the phone is terminally ill.
Click to expand...
Click to collapse
Doesn't there have to be a way to revert to stock if it's all because of the ROM? I really don't want to just give up and throw away a semi-new Captivate and have to break contract to buy another one.
mikel.canovas said:
Doesn't there have to be a way to revert to stock if it's all because of the ROM? I really don't want to just give up and throw away a semi-new Captivate and have to break contract to buy another one.
Click to expand...
Click to collapse
I've seen no accounts of bad flashes causing problems like you described. Particularly the phone not being detected in download mode and the AC charging funkiness. Besides, you already tried reflashing it and not only did that not help, it revealed all sorts of other symptoms.
opcow said:
I've seen no accounts of bad flashes causing problems like you described. Particularly the phone not being detected in download mode and the AC charging funkiness. Besides, you already tried reflashing it and not only did that not help, it revealed all sorts of other symptoms.
Click to expand...
Click to collapse
Ok. Thanks. If anyone else has any other ideas. Please post
I've had the Captivate for around 4 months. Does anyone know if I short out the phone and say it got really hot then shut off, they will exchange it?
mikel.canovas said:
I've had the Captivate for around 4 months. Does anyone know if I short out the phone and say it got really hot then shut off, they will exchange it?
Click to expand...
Click to collapse
Or you could just rob a liquor store and use the proceeds to buy a new one.
So last week my B70 TF101 suddenly started to gave up on me... Rooted and running ARHD 3.4.0 for about a week, in the morning all was ok, played with it a little bit and put it away (not sure if I turned it off or locked screen only) and in the afternoon it didnt wake up anymore. Black screen, I could still here e-mail notifications and docking sound when plugged in the dock.
Repeatedly tried to hard reset, get into CWM recovery, and finally tried to hook it up to my desktop to get into APX mode. Got sure it was charged until dock LED was lit green, also had it hooked to charger directly for a few hours (without dock).
At this point when blindly tried to reset/power off/power on I did not hear any notification anymore except for the occasional camera shutter click but as I have no feedback if its on or off or whatever mode it was in I dont know if its running anymore or not.
Strangely not even my desktop recognizes it when plugged in with USB, trying to get into APX (vol up + power >6sec), no USB notification sound in Windows, new hardware found, refresh of the Device Manager tree, nothing.
I feel at least the backlight is defect but that doesnt explain the no response on USB so looks like there is more to it than just the backlight. I also tried to use a flashlight but cannot detect any screen activity.
So I decided as I still have 2 months warranty I would RMA it. It is beeing picked up tomorrow but have not been able to unroot and install stock recovery/rom...
Now my question is, what chances do you think I have if, lets asume, also the Asus repair centre cannot get access over USB so they wont notice it was rooted, will repair/replace it and send it back?
Did any of you guys manage to get your rooted TF101 repaired and returned under warranty? Or did you get charged? If so how much?
Thanks for any replies!
NVFlash is out for SBK2 devices, use that and repartition your device.
http://forum.xda-developers.com/showthread.php?t=1676845
whitekidney said:
NVFlash is out for SBK2 devices, use that and repartition your device.
http://forum.xda-developers.com/showthread.php?t=1676845
Click to expand...
Click to collapse
Yes thanks, and so I noticed, but that brings me to 2 questions:
1. I am not familiar with Linux.. Does that mean I have to wait until the tool is released for windows?
2. It clearly says "All usage requires booting your tablet into APX mode by connecting it to USB, turning it off and turn it back on while holding Volume Up!".
There is absolutely no response when I connect my TF101 by USB and try to enter APX mode. Would that be different on Linux?
FYI, I used APX a few times about a year ago to gain root, so I am not unfamiliar with this method. I know the USB hardware detected sound in Windows should sound when APX mode is entered and besides it should show up in the deivce manager. Neither is the case.
APX mode is power-volup, just to be totally clarified. Try reinstalling the apx drivers on windows manually, and you don't have to install linux totally, you can use a LiveCD or virtualbox to run NvFlash
You're right, typo edited.. I will try your suggestion, thanks.
Sent from my HTC One X using xda premium
wait, don't bother with windows drivers, you need linux if you're Sbkv2. They'll most likely notice if you're on a ROM, definitely if you have recovery, and may or may not charge you for repairs.
Thing O Doom said:
wait, don't bother with windows drivers, you need linux if you're Sbkv2. They'll most likely notice if you're on a ROM, definitely if you have recovery, and may or may not charge you for repairs.
Click to expand...
Click to collapse
Update: some progress... guess what.. tried my friends USB cable and presto.. APX mode, was able to flash stock rom (http://www.xdafileserver.nl/index.php?dir=Asus/Asus+Transformer+(TF101)/ROMS/NVflash+STOCK/ICS+.21). Following succesful flash, tried powering off and on + voldown to get in recovery but does not give ANY visual feedback.
So still zero screen activity, during flashing, booting, whatever. At least I got it back to stock and can now turn it in for repairs...
Good, rma that and it should be fixed without complaint from asus.
Thing O Doom said:
Good, rma that and it should be fixed without complaint from asus.
Click to expand...
Click to collapse
Thanks, will do... might as well toss in the cable too
Ok, stop me if you've heard this one before (I've searched and searched to find a solution to this issue, so I appreciate any help I can get)
I recently rooted my TF101 and have been flashing different ROM's to see which one I like the best. I'm not a complete NOOB, but I've never done flashing on a tablet before. I flashed Megatron 1.6.1 and when I went to reboot I couldn't get out of recovery and it kept looping back to recovery despite my doing a complete re-wipe/flash. When I finally powered down I wasn't able to power back on.
Now the unit will not turn on, either regularly or in recovery. It's completely dead. I've been letting it sit plugged in for a while to see if that helped and still nothing. I've held the power button down in every conceivable way and for different lengths of time and still nothing.
I'm at my wits end... any help would be AMAZING!!! Thank you in advance.
Can you get into APX mode? You may want to nvflash back to stock and try again.
Sometimes the tf not really shutdown, it just freeze in black screen when we thought it already shutdown. Undock it and plug in charger to see if it charging as it might be given up totally battery drained.
Sent from my awesome rooted Defy: 2.3.6 XDA premium
I have been unable to get the unit into APX mode... when I plug it into the PC it recognizes it as a generic device but I can't do anything with it other than eject it.
I've heard about the "deep sleep" issue and I was really hoping it was something simple like that. I've left it plugged in over night and it still won't respond to anything.
Is this thing bricked? I'm used to troubleshooting issues with devices but typically if it can't even turn on there's not much that can be done. I'm fearing the WORST!!!
Rogueharvest said:
I have been unable to get the unit into APX mode... when I plug it into the PC it recognizes it as a generic device but I can't do anything with it other than eject it.
I've heard about the "deep sleep" issue and I was really hoping it was something simple like that. I've left it plugged in over night and it still won't respond to anything.
Is this thing bricked? I'm used to troubleshooting issues with devices but typically if it can't even turn on there's not much that can be done. I'm fearing the WORST!!!
Click to expand...
Click to collapse
it happened to my wife's tf101 too we went out of town for a 2 day vacation then we forgot to shut it down..when we got back we noticed that it connected to our wireless tether...when we tried to open it the device simply wont open...but the thing is you could hear it starting up and plays music when hitting the play button on the dock..but the screen is all dead...i dont know what to do
redninja007 said:
it happened to my wife's tf101 too we went out of town for a 2 day vacation then we forgot to shut it down..when we got back we noticed that it connected to our wireless tether...when we tried to open it the device simply wont open...but the thing is you could hear it starting up and plays music when hitting the play button on the dock..but the screen is all dead...i dont know what to do
Click to expand...
Click to collapse
The battery might be drained after 2 days away. Try charge it individually first.
As the OP issue.. I fear it might be the display problem but you must be certain before judging it to hardware issue. Still best way is flashing it to stock via NVflash method when all the screen give is black. You can do it by just listening the connection sound on your PC and install the right driver for the APX to work.
new damages
farsight73 said:
The battery might be drained after 2 days away. Try charge it individually first.
As the OP issue.. I fear it might be the display problem but you must be certain before judging it to hardware issue. Still best way is flashing it to stock via NVflash method when all the screen give is black. You can do it by just listening the connection sound on your PC and install the right driver for the APX to work.
Click to expand...
Click to collapse
i already tried nvflashing back to stock it went back to stock but the screen still wont turn on...i charged it for 12 hours still nothing.but it plays music still ...after getting pissed off,,,my wife hits the tf101 screen and then it turns on finally but the screen was orange and red... then she hit it again then i think she damaged it once more hahhaha....im pissed off too but when thinkin bout her face while hitting the tf101 EPIC hahahha...any help wanted i wanna buy new screen... attatched is the picture she sent me hahaha
So I'm stumped... I've flashed my Charge many times, no problems until now.
I wanted to flash back to stock ROM and had my Samsung drivers installed and Odin recognizing the phone and everything was good, but then Odin was taking WAAAAAAY too long. In the past this usually took about 20 mins. This time, after 45 mins and the progress bar hanging in the same place for 30+ mins on factory.rfs I disconnected the phone (I know this is where I screwed up). Now Odin won't recognize the phone at all. It does get into download mode, but Odin won't pick it up.
Same computer, same cable, and same USB ports as I've had when flashing this phone many times before. I don't know what my options are now. I don't think I can flash either the ROM or PIT without Odin at least recognizing the phone. What can I do now?
So I've done some more tinkering - trying different cords, multiple computers, uninstall/reinstall different drivers... What I've noticed on more than one computer is that Odin doesn't recognize the phone when it's in download mode ONLY.
If I power on the phone Odin is able to detect it and windows detects it as a Samsung USB device (even though the phone hangs on the Samsung logo). When I put it into download mode both the computer and Odin don't recognize it.
dragonlady726 said:
So I've done some more tinkering - trying different cords, multiple computers, uninstall/reinstall different drivers... What I've noticed on more than one computer is that Odin doesn't recognize the phone when it's in download mode ONLY.
If I power on the phone Odin is able to detect it and windows detects it as a Samsung USB device (even though the phone hangs on the Samsung logo). When I put it into download mode both the computer and Odin don't recognize it.
Click to expand...
Click to collapse
FWIW, I've also noticed a simple computer reboot fixes it....
jco23 said:
FWIW, I've also noticed a simple computer reboot fixes it....
Click to expand...
Click to collapse
I neglected to mention in my OP that I was going through the right protocol with driver uninstall/reinstall and rebooting each time. I rebooted again for good measure after seeing your post but I still get the same.
It's the same result from two different computers, one with Win7 and the other XP (I read in another thread that XP had worked better for some). If the phone is powered on, even though it doesn't successfully boot, Odin and Windows recognize it properly. If it's in download mode neither one recognize it, windows says the device failed to start and shows either unrecognized device or "Gadget Serial" (which would be a great name for a band, but google searches for it aren't much help).
I don't think it's a driver problem because it's recognized when the phone is powered on. But could there be a specific driver out there for the phone when in download mode only? I've flashed this phone dozens of times and never had a problem until now. I'm on the verge of forking over the $50 and sending it to JTAG if no one can suggest something else to try. Please help
did you make sure your phone is in debugging mode?... i forget who flashed what... or where I read something about flashing and it turned off their debugging mode...so check that first...and try reinstalling Odin on your computer... i don't think jtag is necessary on a Droid charge... if your phone is being recognized then it seems your missing a step...like maybe pulling your battery before hooking up the usb... or reinstalling the battery after going in download mode... and last of all check and make sure your not accidentally making mistakes when setting up your Odin before flashing... and last efforts to get a working phone would be going into cwm... volume up... home... and power button... hold while powering up and releasing on the second Samsung logo...and install your last back up...or reflash your rom with cache and dalvik wipes
Sent from my SCH-I510 using xda premium
curious, when you are/were performing the Odin process, were you still using the computer (web-surfing, e-mail, etc.)? in my experience, whenever I tried to multi-task on my computer while running Odin on my phone, Odin freezes. this has happened on more than one occasion. also, my toddler daughter even pressed the power button while Odin was running - so on three separate occasions, I've had a reflash interrupted. however, I've clearly been able to recover.
the key was using the right cord in the right port. I had one cord working fine for awhile, but then when I switched cords, it worked again.
also, some folks have had better success when removing the battery during the process.
finally, what are your steps exactly when flashing - and which guide are you using?
lukegman said:
did you make sure your phone is in debugging mode?... i forget who flashed what... or where I read something about flashing and it turned off their debugging mode...so check that first...and try reinstalling Odin on your computer... i don't think jtag is necessary on a Droid charge... if your phone is being recognized then it seems your missing a step...like maybe pulling your battery before hooking up the usb... or reinstalling the battery after going in download mode... and last of all check and make sure your not accidentally making mistakes when setting up your Odin before flashing... and last efforts to get a working phone would be going into cwm... volume up... home... and power button... hold while powering up and releasing on the second Samsung logo...and install your last back up...or reflash your rom with cache and dalvik wipes
Sent from my SCH-I510 using xda premium
Click to expand...
Click to collapse
I can't actually get the phone to boot (doesn't get past Samsung logo) so I don't know how I can tell if it's in debugging mode or how to change it if it's not.
Going in to download mode I've tried both battery in and out, using multiple USB ports and cables and can't get any version of Odin to detect it. I've tried v1.82 and 1.85 of Odin. I get the same result for both - Odin does not detect the phone when in download mode, but will detect it if it's powered on or just connected to the computer with battery in to "charge." But afaik I can't flash it when it's NOT in download mode
It won't boot into into recovery either... It never gets past Samsung logo no matter how long I hold the buttons... I've used recovery before, so I'm sure I'm giving the android 3-finger salute correctly.
I'm thinking maybe I got unlucky because the whole key to flashing is having Odin recognize the phone in download mode and that's the only time that Odin won't recognize it.
jco23 said:
curious, when you are/were performing the Odin process, were you still using the computer (web-surfing, e-mail, etc.)? in my experience, whenever I tried to multi-task on my computer while running Odin on my phone, Odin freezes. this has happened on more than one occasion. also, my toddler daughter even pressed the power button while Odin was running - so on three separate occasions, I've had a reflash interrupted. however, I've clearly been able to recover.
the key was using the right cord in the right port. I had one cord working fine for awhile, but then when I switched cords, it worked again.
also, some folks have had better success when removing the battery during the process.
finally, what are your steps exactly when flashing - and which guide are you using?
Click to expand...
Click to collapse
I wasn't actively multitasking during the bad flash, although I may have had email running in the background. Since then I've been rebooting and only had Odin running in the foreground when trying. I did use multiple usb ports/cables and try going into download with battery in/out.
As far as guides go, I had been using trparky's awesome guide for years until he took it down and lately went to the one in the dev forum here on xda: http://forum.xda-developers.com/showthread.php?t=1160580
Like I said, I'm thinking maybe I got unlucky because Odin recognizes the phone when plugged into the computer EXCEPT when it's in download mode and without that I don't know what else to do.
dragonlady726 said:
I can't actually get the phone to boot (doesn't get past Samsung logo) so I don't know how I can tell if it's in debugging mode or how to change it if it's not.
Going in to download mode I've tried both battery in and out, using multiple USB ports and cables and can't get any version of Odin to detect it. I've tried v1.82 and 1.85 of Odin. I get the same result for both - Odin does not detect the phone when in download mode, but will detect it if it's powered on or just connected to the computer with battery in to "charge." But afaik I can't flash it when it's NOT in download mode
It won't boot into into recovery either... It never gets past Samsung logo no matter how long I hold the buttons... I've used recovery before, so I'm sure I'm giving the android 3-finger salute correctly.
I'm thinking maybe I got unlucky because the whole key to flashing is having Odin recognize the phone in download mode and that's the only time that Odin won't recognize it.
I wasn't actively multitasking during the bad flash, although I may have had email running in the background. Since then I've been rebooting and only had Odin running in the foreground when trying. I did use multiple usb ports/cables and try going into download with battery in/out.
As far as guides go, I had been using trparky's awesome guide for years until he took it down and lately went to the one in the dev forum here on xda: http://forum.xda-developers.com/showthread.php?t=1160580
Like I said, I'm thinking maybe I got unlucky because Odin recognizes the phone when plugged into the computer EXCEPT when it's in download mode and without that I don't know what else to do.
Click to expand...
Click to collapse
Also, are you sure you have enough battery juice? To make sure, leave it plugged in to a wall outlet for about 30 min to an hour.
tappin' that....
Finally fixed - Bad USB port
Just to close out the thread, I did finally get my phone fixed. The issue was a bad USB port that decided to fail during flash. This is according to Josh from MobileTechVideos, who is a great guy with amazing customer service.
Longer version: I sent it off to MobileTechVideos/JTAG and after a week I got a call back saying the JTAG process didn't work and as a last resort they could try replacing the USB port itself. Josh told me that it was either the port or the controller, that the port was a known failure point on the Charge, and if replacing the port didn't work it meant the USB controller had failed and I'd be out of luck. He also said that if the port replacement didn't fix the issue he wouldn't charge me and refund my original payment (which impressed the hell out of me given the time he had already put into it and there was no guarantee that the extra work would fix it). This was late afternoon on Valentine's Day... he said that he'd get to swapping out the port the next day but an hour later called back to tell me that he replaced the port and flash was successful. I wish everyone was as straightforward in communication and dedicated to their job.
So yeah, MobileTechVideos is legit, Josh is a rock star, and send those guys your phone if something really screwy happens. They will take the time and go above and beyond if necessary to fix it, and you will absolutely get your money's worth.
Hoping that no one else is "lucky" enough to have their USB port fail mid-flash, but if your symptoms look like mine a bad port might be your problem.
I've heard nothing but good things about them. I've never used them myself, but I have directed a couple of people to them and heard nothing but glowing reviews.
Cool I managed to finally back up my sd card after a few attempts with a bad port (went out after a month of having the phone). I've been on a rotating batteries off a wall charger system, but need to odin because everytime I get down to 110-120 ish mb of internal memory my charge says low memory blah blah, I clear cache, play store , etc.
Needless to say people have said resorting back to stock ep4 etc with Odin should work, but I'm afraid mid flash something will happen. I have to jam the cord in, wrap extremenly tight while holding the phone at a perfect angle and sometimes it still will beep like being disconnected.
I have no idea if this would be possible for you, but I wonder if Mobile Odin could help you?
Hello,
I am quite familar with samsung devices and flashing etc. but my friends phone died today I suppose. At some point it got stuck and got into a bootloop. After some reboots it tried to find a ota update.zip, but there was none. After some tries I got into download mode, but flashing a stock image (was stock before as well, never seen root or something) did help at first (it booted, we backupped some stuff) but at some point it got stuck into bootloop again.
This time, when going into recovery, it tried flashing a firmware again, however this ended badly (freeze while flashing). Now it's not even charging anymore. Not a single button combination is working (force reboot, recovery, download mode, ...) and when plugging into a power bank, it doesn't even charge anymore (power bank shows if a device is charging). So it's completely back and unnoticed by odin, adb or fastboot. Does anyone know this problem or have an idea, what we could try? My last idea would be to test a wireless charger, which i sadly do not have at hand.
Thanks!
Cloud2F said:
Hello,
I am quite familar with samsung devices and flashing etc. but my friends phone died today I suppose. At some point it got stuck and got into a bootloop. After some reboots it tried to find a ota update.zip, but there was none. After some tries I got into download mode, but flashing a stock image (was stock before as well, never seen root or something) did help at first (it booted, we backupped some stuff) but at some point it got stuck into bootloop again.
This time, when going into recovery, it tried flashing a firmware again, however this ended badly (freeze while flashing). Now it's not even charging anymore. Not a single button combination is working (force reboot, recovery, download mode, ...) and when plugging into a power bank, it doesn't even charge anymore (power bank shows if a device is charging). So it's completely back and unnoticed by odin, adb or fastboot. Does anyone know this problem or have an idea, what we could try? My last idea would be to test a wireless charger, which i sadly do not have at hand.
Thanks!
Click to expand...
Click to collapse
If it's not showing any signs of life and will not charge then it's a hardware problem, you should start with the obvious like the usb connector. You are going to have to open the phone and check usb connection, battery connection etc. but it may be easier to take to repair shop.
cooltt said:
If it's not showing any signs of life and will not charge then it's a hardware problem, you should start with the obvious like the usb connector. You are going to have to open the phone and check usb connection, battery connection etc. but it may be easier to take to repair shop.
Click to expand...
Click to collapse
but when it died the first time, i was able to flash the stock image; after it rebooted, it was charging perfectly fine until it died again. from that point on, i was not able to get any sign of life anymore... maybe something crashed that badly and it's still running and i have to wait for the battery to completely drain, so it can do something again? or is the charging process completely hardware dependent, so a crash shouldnt do anything?
Cloud2F said:
but when it died the first time, i was able to flash the stock image; after it rebooted, it was charging perfectly fine until it died again. from that point on, i was not able to get any sign of life anymore... maybe something crashed that badly and it's still running and i have to wait for the battery to completely drain, so it can do something again? or is the charging process completely hardware dependent, so a crash shouldnt do anything?
Click to expand...
Click to collapse
the way to test if it has power but blank screen is to hold power+volume down+home. If it has power it will turn off and boot into download mode
After the Forst Crash all such combinations didnt Seen to work either. Once odin recognized is while having a black screen. At that point I flashed stock :/ but still, not even the led was showing something