I unlocked my Verizon Note II using Casual and following specific instructions from Adam Outler and other threads. Unlock succeeded and I was successfully rooted. Then a couple nights ago I plugged my phone in and it did not respond. I tried 6 different cables on different power usb sources as well as the pc with no luck. The phone would charge then stop and keep doing this sounding system notifications randomly. I tried flashing CWM 6.0.4.3 because someone in another thread said it may be TWRP causing issues. It flashed properly but the issue remains. Last night my phone drained completely while on the charger and I have been trying to charge it from all of my previous cable configurations. It will no longer accept any form of charge and I cannot boot. I tried booting into recovery and it will stay on while in recovery but not for normal boot. I am thinking this is a software issue. This is my main business phone and I do not have a backup to use in the meantime. I am also receiving a note 3 and have to send this one back so I have to flash back to stock. I would really appreciate a senior member's assistance. Thank You!
Related
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?
Hello guys, I have (I think) soft bricked my Galaxy S2.
(Details: UK Phone, Carrier was Orange but now I am running 3 on it, official phone model Galaxy I9100T (NFC support iirc) )
Right I am curious bunny hacking away at the phone from the day I bought it, reading pages after pages on different roms and kernel and everything. Finally I settled on CyanogenMod 9 and then went straight to the CM10.1 release. Today Morning I installed the 23/02/2013 CM10.1 realease and then started browsing the XDA forums on whats new. I came across the Siyah 6.0b kernel release and saw it was compatible with cm10.1, eager and foolish I downloaded the apk without doing any further reading or any instruction, overconfident from all the flashing I have been doing for the past year, flashed the kernel via CWM recovery. Now the phone is stuck in what I assume is a boot loop (again I am pretty noobish).
So What have I tried to fix the soft brick?
I tried to go "restore" an img I had taken a week ago of the system with CWM but the phone would no longer boot into recovery.
So I went ahead and got all the recovery package (I9100TDULP9_I9100THUTLP7_HUT) to reflash my phone with Odin 3.07.
This is where I hit a brick wall and now I am truly lost at what to do, my computer doesn't recognise the phone (Download Mode). I keep getting "there is a problem with this device" error and the Device manager shows an unknown device connected. So I installed the Samsung drivers from the samsung website with no luck. Still getting unknown device error. So I googled for a solution and the only solution that came up was reformat my PC since it could be a problem within the OS, so I went forward and used two other PC and still getting the error. Please Help SOS.
tl;dr: Getting Device not recognised error when I connect phone to the computer via USB cable.
Thanks in advance to all the knights to my rescue
DNoob92 said:
I came across the Siyah 6.0b kernel release and saw it was compatible with cm10.1, eager and foolish I downloaded the apk without doing any further reading or any instruction, overconfident from all the flashing I have been doing for the past year, flashed the kernel via CWM recovery. Now the phone is stuck in what I assume is a boot loop (again I am pretty noobish).
So What have I tried to fix the soft brick?
Click to expand...
Click to collapse
Just go to recovery menu (VOLUP+MENU+POWER) and wipe cache and wipe dalvik. That should fix it.
surplus mplieac
crocodilechris said:
Just go to recovery menu (VOLUP+MENU+POWER) and wipe cache and wipe dalvik. That should fix it.
Click to expand...
Click to collapse
I cannot enter Recovery Mode, the screen just goes blank
EDIT: So the only thing that works atm is
1) The battery charge animation (huge green battery in the middle of the screen) when plugged in.
2) Download/Odin mode (which 3 computer refuse to recognise when connected via a USB cable)
EDIT2: The other thing I forgot to mention was, that I have lost the original SII micro USB cable which was black and now I am using the white micro USB cable I received with my Galaxy Note 2.
You could try uninstalling all Samsung-related drivers/software (Ie: Kies), download the Android Naked Driver or the Android ADB Driver (I wish I could recall where I got it from, but it also came with the driver for the Galaxy SII... Sounds like it might be more of a driver issue than it would be a cable issue..
Borrow and S2 cable.
There are a lot of guys having issues with note's cable.
Try a laptop, and install kies on any other pc you try.
Flash siyah v5 instead of flashing v6.
You can relax, if the only thing you did is flash a kernel then there is nothing wrong with your phone.
Try different cables, try Odin 1.85 (that one always worked for me), try different pc's, reinstall drivers, make sure no kies process is running in the background.
First of all thanks for the replies
I couldn't get the drivers working still (after re-installing, installing kies). But while eating lunch I remembered reading about removing battery and pressing the Power button and it doing something I couldn't quite remember. So I thought to myself it wouldn't hurt trying. Did that and the phone Finally booted in recovery mode, I took a breather of relief and than located my previous backup img and restored the phone.
But now a new problem arose, the phone went into SIM lock as soon as it booted and now I guess I have to fix that
Well thanks guys
Quick question guys is SIM network unlock pin basically same unlocking phone form a carrier?
It's asking for a SIM pin or network code?
Get galaxysim unlock by searching xda (free here, paid at play store).
Sent from the little guy
So I rooted my s4 using towelroot and stupidly tried to install a custom recovery. First CWM then TWRP (not sure if this has anything to do with it, likely not?). Now it has no power, and wont charge...
Events leading up to the dead s4:
I "rebooted to recovery" and it brought me to the DOWNLOADING! screen instead of a recovery manager, I held down power and then it shut off and it turned back on again and brought me to another screen asking me to continue or boot normally.
I booted normally.
Then I deleted a few of the annoying apps that were preinstalled, nothing that was listed as essential to the Kernel/OS using Root App Delete. Finally I went to work with the battery dying, and it died on the way.
I tried to charge it the following morning and it would not charge. No LED light, no vibrate that usually happens. I left it alone with the battery out for 2 days, switching back to my s3. Tried again, still nothing.
Wont charge, computer wont recognize. Tried 3 different cables, a samsung charger and my asus tablet charger. Apparently it is a brick.
Thought it might be the USB port, and from a previous screen swap I performed, I still had the old USB assembly, so I swapped them, and it still will not respond. I even tried the older screen, nothing.
Anyone have the slightest clue what happened? I bought another battery to try, but doubt it will resolve the problem.
daveyp225 said:
So I rooted my s4 using towelroot and stupidly tried to install a custom recovery. First CWM then TWRP (not sure if this has anything to do with it, likely not?). Now it has no power, and wont charge...
Events leading up to the dead s4:
I "rebooted to recovery" and it brought me to the DOWNLOADING! screen instead of a recovery manager, I held down power and then it shut off and it turned back on again and brought me to another screen asking me to continue or boot normally.
I booted normally.
Then I deleted a few of the annoying apps that were preinstalled, nothing that was listed as essential to the Kernel/OS using Root App Delete. Finally I went to work with the battery dying, and it died on the way.
I tried to charge it the following morning and it would not charge. No LED light, no vibrate that usually happens. I left it alone with the battery out for 2 days, switching back to my s3. Tried again, still nothing.
Wont charge, computer wont recognize. Tried 3 different cables, a samsung charger and my asus tablet charger. Apparently it is a brick.
Thought it might be the USB port, and from a previous screen swap I performed, I still had the old USB assembly, so I swapped them, and it still will not respond. I even tried the older screen, nothing.
Anyone have the slightest clue what happened? I bought another battery to try, but doubt it will resolve the problem.
Click to expand...
Click to collapse
simple research you could have avoided all this....unless you have a MDK bootloader you CAN NOT install any custom recovery like TWRP of CWM without messing your phone up. Safestrap is your ONLY option. The link below is where you should have started your research. Most likely now you will have to try odin a clean image tar of your phone's firmware base
http://forum.xda-developers.com/showthread.php?t=2606501
decaturbob said:
simple research you could have avoided all this....unless you have a MDK bootloader you CAN NOT install any custom recovery like TWRP of CWM without messing your phone up. Safestrap is your ONLY option. The link below is where you should have started your research. Most likely now you will have to try odin a clean image tar of your phone's firmware base
http://forum.xda-developers.com/showthread.php?t=2606501
Click to expand...
Click to collapse
thank you. I know i messed up, have rooted/installed cfw on like 10 android phones but they always packaged root and unlocked the bootloader at once, which I never noticed.
Also, how can I connect the phone to odin if it wont connect to a PC? or charge for that matter
daveyp225 said:
thank you. I know i messed up, have rooted/installed cfw on like 10 android phones but they always packaged root and unlocked the bootloader at once, which I never noticed.
Also, how can I connect the phone to odin if it wont connect to a PC? or charge for that matter
Click to expand...
Click to collapse
I can't help you that
daveyp225 said:
thank you. I know i messed up, have rooted/installed cfw on like 10 android phones but they always packaged root and unlocked the bootloader at once, which I never noticed.
Also, how can I connect the phone to odin if it wont connect to a PC? or charge for that matter
Click to expand...
Click to collapse
Re install your drivers then try again
Sent from my SCH-I545 using XDA Free mobile app
Sounds like a total brick to me. There are jtag services. I bought the equipment myself to jtag for a hard brick but my warranty company decided the replace my phone after all so I didn't have to use the equipment. Mine did the same exact thing. Wouldn't even get warm when plugged into the charger.
Good morning guys
I've been having issues with my Galaxy S2 for about a month now so I'll try my best to explain what's happened.
I was playing on my PS4 and I had left my Galaxy S2 (non root) on charge. When I returned to check the charge levels, it had booted and was stuck on the black galaxy S2 logo screen. I was able to put it in download mode but not recovery and the phone would also charge. I removed the battery, tried to reboot but it just wouldn't boot past that screen. Upon reading on these forums about the potential issue, it sounded like the phone was softbricked so I tried to re-flash the stock rom that I downloaded from samware but Odin wasn't having any of it.
I tried multiple different PCs, Odin versions, USB cables and so on but it just kept failing. I eventually got fed up with trying to recover it and I just left it in storage. Today however, the wife has said she wants all the pictures off it so she can transfer them to her laptop so I got the Galaxy S2 out again and now it's dead. Won't turn on, won't charge, won't do anything. I've got a new battery but that won't charge either but I'm headed around a friend's later to charge it and see if that solves anything.
Any help or suggestions would be greatly appreciated :good:
MrChi 205 said:
Good morning guys
I've been having issues with my Galaxy S2 for about a month now so I'll try my best to explain what's happened.
I was playing on my PS4 and I had left my Galaxy S2 (non root) on charge. When I returned to check the charge levels, it had booted and was stuck on the black galaxy S2 logo screen. I was able to put it in download mode but not recovery and the phone would also charge. I removed the battery, tried to reboot but it just wouldn't boot past that screen. Upon reading on these forums about the potential issue, it sounded like the phone was softbricked so I tried to re-flash the stock rom that I downloaded from samware but Odin wasn't having any of it.
I tried multiple different PCs, Odin versions, USB cables and so on but it just kept failing. I eventually got fed up with trying to recover it and I just left it in storage. Today however, the wife has said she wants all the pictures off it so she can transfer them to her laptop so I got the Galaxy S2 out again and now it's dead. Won't turn on, won't charge, won't do anything. I've got a new battery but that won't charge either but I'm headed around a friend's later to charge it and see if that solves anything.
Any help or suggestions would be greatly appreciated :good:
Click to expand...
Click to collapse
Hi
Looks like your usb/charging Connector is broken.
Can be replaced if you are ready to spend money On an old device.
If your friend has a s2 try to connect it with your cable to your PC. If it works then it should be your usb Connector (having already a new battery)
But If you are able to enter (with loaded new battery) the recovery you can install philz cwm6 stock recovery with root and then flash a custom rom.
All files are zip files which you can copy on a micro SD card and can be installed from there without a PC.
So you have a working rom even with a broken Connector
Sent from my ME173X using XDA-Developers mobile app
---------- Post added at 04:47 PM ---------- Previous post was at 04:31 PM ----------
Just want to add:
In case you manage to install philz Kernel try first to reboot stock-rom. If it does'nt work, i would install custom rom.
Sent from my ME173X using XDA-Developers mobile app
Hi, it happened to me 2-3 yrs ago. Try this:
_phone off (check)
_take the battery out
_plug the phone in
_ wait a few seconds then put the battery back in
_ immediately, press and hold the power button.
Sometimes the USB charge chip get stuck and this somewhat "resets" it.
Also worth checking, remove the battery first, then with a small brush or a nail check for dust layer inside the USB plug.. it won't solve your problem, but might cause a bad connection (even if the connector click in).
So starting off, I'm having problems in terms of the bootloader of this phone. I kinda got bored with the stock so I unlocked Max M2's bootloader to install Evolution X ROM (which where recommended by Max M2 users) and yes I did installed it no problem but after a while when finally charging the phone it started to disconnect and reconnect until it finally wont charge. I tried to charge i through Laptop and yes it worked! but after awhile it started to not charge even on a laptop. So I'm starting to convince myself if it is a software problem or the phone itself. Though that's not the case, it connects to the computer when on fastboot mode so I started to think that it is a software problem. So what I find is that when I unlocked the bootloader it started to charge again and so I waited for 2 hours if the charging problem start to come again and yes it did! so what I did is, I relocked the bootloader and yes! IT STARTED TO CHARGE AGAIN!! (though I'm waiting if the problem starts to come again) so anyone also have this problem? or I did something wrong? I decrypted the device when I was rooting but I don't really know if that's the root of the problem?
Please kindly help me if you know, Thanks in advance!!
It seems like this isnt the case at all, so what I did is I tried to change the USB CONFIGURATION to charging and it started to charge again but the problem is the default is not "Charging Only" rather its MTP so how do I change it back to charging only?