Hey, I was trying to root my photon Q and installed CWM + Cyanogen mod 10.1 but I got stuck in the bootanimation.
I was trying the usual stuff like wiping cache but it told me it was unable to mount /data.
After searching a web I found out that CWM may not read the file system so i tried to change the partions of the internal flash rom using this tutorial: (sorry i am not allowed to post the link so search google: "SOLVED: messed up partitions on internal storage - CyanogenMod page 1 #11"
and look at post #7.)
After altering the partition tables on /dev/block/mmcblk0 the phone does absolutely nothing anymore when pressing the powerbutton. Did I brick the phone? Is there a way getting it back to live using an external sd card?
have you tried to boot into recovery ?
(hold power button + volume up). if this works you can maybe copy i.a. cyanogenmod 10 or so to your sd card and install it).
if this wont work, try to reinstall the stock photon q firmware fxz files. this is what i would try to do if my phone is "bricked".
here is a small tutorial which i wrote (sorry for my bad english).
i have uploaded the fxz files and the tools which are needed to wuala (like dropbox) as a personal backup for myself.
Please read this tutorial first one time complete and start then!
With this you will lose all your data which is stored on your phone (internal storage, an external sd card shouldnt be affected), but its better to put it out.
1. install RSD Lite 6.1.5 + MTK Patch (install first rsd lite and then the mtk patch)
2. boot into bootloader (hold power + volume down)
3. plug your photon q into your computer with the usb cable. (you must use a usb port on the "backside" of your pc. on all computer which i have testet RSD Lite didn't noticed the photon q if it was plugged with one of the front usb ports. on a laptop it is doesnt matter)
4. Run RSD Lite as Administrator.
5. Select the downloaded firmware unter "Filmename:"
6. click on "Decompress and start flashing".
7. if you get an error message on step 6, open the .zip file with 7zip or winrar and edit the .xml file
filename: asanti_c_sprint-user-4.1.2-9.8.2Q-122_XT897_FFW-5-6-release-keys-cid9.xml
in the .xml you have to delete the 2 lines
<step operation="getvar" var="max-download-size" />
after you deleted the 2 lines save the xml file in the zip archive.
8. select on under "Filmename:" the new .zip file.
9. now it should work, wait until it finishes.
10. now your photon q should be back on stock.
here are all files:
firmware:
(you have to select your carrier, in my example my photon q is from sprint, as you can see in the beginning of the file name (asanti_c_sprint-user.... for sprint model or asanti_c_cspire-user... for CSpire))
i prefer you to install the newest (last in the list, which is jelly bean 4.1.2, you can see the android version after the asanti_c_sprint-user-4.1.2
THE RIGHT FIRMWARE IS REALLY IMPORTANT !
http://forum.xda-developers.com/showthread.php?t=2095536
RSD Lite + MTK Patch.
https://www.wuala.com/gangster123/Android/?key=XQYzh52Wj4yn
Hi,
thanks for your affords but the problem is, the phone doesen't do anything when pressing the power button. The screen just remains black. Therefore it's not possible to get into recovery mode. What I did was doing the parted /dev/block/mmcblk0 mkfs ext2 command on adb shell. The /dev/block/mmcblk0 (internal sd card) had alot of partitions (about 39) and I guess also the recovery mode files are stored there. (I assumed it is stored somewhere else on a dedicated memory) The phone just can't read it anymore, since the partition table is damaged.
Maybe I could restore it by using the dd command and rewrite the original partition table. But I have to get access to the internal sd card chip for that.
If nothing helps, I have to desolder it and flashing it manually. But I realy wan't to do that as the realy last step.
Maybe there is a possible mod for getting a 32GB or more as internal flash lol.
I also read something about the possibility of using the JTAG debugging port. Will I get access using that? If yes, where are the pins on the mainboard?
Anyway I downloaded RSD Lite + Stock rom and did everything you mentioned (except getting in recovery mode) but RSD lite doesen't show anything when clicking on Show Device and there is nothing happening when clicking on start. But it can't be bad having the stock rom so thanks for that.
can you boot into the bootmanager ?
and try other usb ports (dont use usb hubs or, only direct connection from phone to pc)
The phone is absolutely doing nothing when pressing the power button. I tried connecting it on the usb 3.0 port an my laptop. I will try another one as soon as I am home but I doubt it will make any difference, since the boot manager is stored on the internal flash i guess.
coon42 said:
The phone is absolutely doing nothing when pressing the power button. I tried connecting it on the usb 3.0 port an my laptop. I will try another one as soon as I am home but I doubt it will make any difference, since the boot manager is stored on the internal flash i guess.
Click to expand...
Click to collapse
Well, I'm not quite sure why you decided to repartition... sounds dangerous ! Especially using ext2, that is not appropriate for this device at all.
I guess you know that now... At any rate, have you tried pressing & holding power+camera? Hold it, you should get a menu.
If that doesn't work, does the device actually charge? Do you get any indication that it's charging from AC or USB?
RSD Lite won't show anything unless you are in fastboot mode, and the phone is plugged in/recognized by your PC - and of course, you have the proper drivers installed.
arrrghhh said:
Well, I'm not quite sure why you decided to repartition... sounds dangerous ! Especially using ext2, that is not appropriate for this device at all.
Click to expand...
Click to collapse
Because clockwork mod was not able to mount it so I i wasn't able to wipe data and cache. I assumed that was the reason cyanogenmod was hanging on boot.
I guess you know that now... At any rate, have you tried pressing & holding power+camera? Hold it, you should get a menu.
If that doesn't work, does the device actually charge? Do you get any indication that it's charging from AC or USB?
Click to expand...
Click to collapse
The screen just remains black whatever I do but in background the phone seems to run and crash immediately, because there is no readable bootloader. After I let the phone laying around and plugged it in again, the upper led was lighing green for a short time (indicating that the battery is empty and that the phone can't be turned until it reached 5%)
RSD Lite won't show anything unless you are in fastboot mode, and the phone is plugged in/recognized by your PC - and of course, you have the proper drivers installed.
Click to expand...
Click to collapse
I am pretty sure it is not possible getting it run just by an using USB cable since the processor cant mount the system filesystem and immediately crashes.
Only solution should be JTAG but for that I need to find the JTAG pins first...
coon42 said:
Because clockwork mod was not able to mount it so I i wasn't able to wipe data and cache. I assumed that was the reason cyanogenmod was hanging on boot.
Click to expand...
Click to collapse
So you changed the partition table!?! Seems like a drastic solution.
coon42 said:
The screen just remains black whatever I do but in background the phone seems to run and crash immediately, because there is no readable bootloader. After I let the phone laying around and plugged it in again, the upper led was lighing green for a short time (indicating that the battery is empty and that the phone can't be turned until it reached 5%)
I am pretty sure it is not possible getting it run just by an using USB cable since the processor cant mount the system filesystem and immediately crashes.
Only solution should be JTAG but for that I need to find the JTAG pins first...
Click to expand...
Click to collapse
Battery does sound dead, if you can't get to fastboot mode... JTAG is probably the only option. I would keep trying to get the phone into fastboot mode if I was you. JTAG isn't exactly easy to use.
arrrghhh said:
So you changed the partition table!?! Seems like a drastic solution.
Battery does sound dead, if you can't get to fastboot mode... JTAG is probably the only option. I would keep trying to get the phone into fastboot mode if I was you. JTAG isn't exactly easy to use.
Click to expand...
Click to collapse
Fastboot is also just a tool which is on the internal flash and can't therefore booted.
It seems the phone is still charging but I cant realy test it. The only thing I could do is measuring the voltage with a multimeter...
It says 2.891V now. I will plug it in for two or three hours and try again... If the voltage get higher we know that the phone still charges and that the problem can't be the battery.
Meanwhile i did some photos of the mainboard:
Front:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Front upper:
Front bottom:
Back side:
There are already two consumptions where the JTAG port could be located:
On 1 there are a few connectors. When these connectors aren't closed by the backcover the phone won't start. Maybe some connectors are JTAG. I also spotted an unused connector on 2. I asume that this is some kind of debugging port because it is just covered by the battery and not connected on normal use.
What are 3, 4, 5, 6 and 7 for? Looks like connectors for antennas...
Okay, battery doesen't get warm and voltage didn't change so charging doesen't seem to work.
Is there a way powering the phone without battery? I heard something about a factory cable... may I just connect 3,3V on the battery pins or will i screw up the charging electronics by doing that?
coon42 said:
Fastboot is also just a tool which is on the internal flash and can't therefore booted.
It seems the phone is still charging but I cant realy test it. The only thing I could do is measuring the voltage with a multimeter...
It says 2.891V now. I will plug it in for two or three hours and try again... If the voltage get higher we know that the phone still charges and that the problem can't be the battery.
Click to expand...
Click to collapse
Connector #1 is the set of contact point for the antennas (one for 3G, one for LTE, one for wifi, etc.), and presumably the battery also, since the phone refuses to boot up without it being connected (and because I didn't make out any battery contacts in the photos provided). #2 is most likely the JTAG, since as you say, it's completely unconnected during normal phone operation. 3-7 are usually antenna connections, but they could also be used as diagnostic test points to make sure the local circuitry (or the phone as a whole) works as it's supposed to while the phone is going through the manufacturing process.
As for connecting voltage straight to the phone, it shouldn't be a problem as long as the polarity is correct, and you use no more voltage AND current as is supplied by the charger that came with the phone (5.1V and 850mA).
Ok, I also asume to 90% that 2 is the jtag port. So, any idea how to find out the pinout? Is it some standardized port by motorola? I didn't find anything on google yet but I'm still searching...
I'd like to measure directly on the CPU but since the pins are unreachable when soldered (since all pins are UNDER the cpu) I can't.
xaelith said:
Connector #1 is the set of contact point for the antennas (one for 3G, one for LTE, one for wifi, etc.), and presumably the battery also, since the phone refuses to boot up without it being connected (and because I didn't make out any battery contacts in the photos provided). #2 is most likely the JTAG, since as you say, it's completely unconnected during normal phone operation. 3-7 are usually antenna connections, but they could also be used as diagnostic test points to make sure the local circuitry (or the phone as a whole) works as it's supposed to while the phone is going through the manufacturing process.
As for connecting voltage straight to the phone, it shouldn't be a problem as long as the polarity is correct, and you use no more voltage AND current as is supplied by the charger that came with the phone (5.1V and 850mA).
Click to expand...
Click to collapse
#1 is the audio headphone jack. Check the chassis where it mates.
The battery terminals (screw posts) are below the hdmi & usb ports, next to #4 on your pic.
The antennas have different connection points around the mobo, eg, the gps antenna connects and is located around the volume rocker location.
I wouldn't recommend a higher voltage than the battery is rated at if you are going to power the phone directly. Chargers are generally all USB spec now days (5vDC), so that most (any) phone can be charged from a usb port/power adapter. This is then regulated by the internal charging circuit to charge the Lithium battery, typically a 3.7vDC (nominal) cell.
Your battery is too discharged to start the phone. Research lithium battery cell voltages to understand. Get a lithium cell charger, or if you understand the risks & how to do it, you could revive the battery another way.
Maybe I'm wrong, but it seems you are getting in too far without understanding your phone & the terminals/components. This may lead to more trouble than you first had.
Good luck with it.
Sent from my XT897 using xda app-developers app
schmandroid said:
Maybe I'm wrong, but it seems you are getting in too far without understanding your phone & the terminals/components. This may lead to more trouble than you first had.
Click to expand...
Click to collapse
Well, the phone is bricked anyway. I can't make it any more worse yet.
Sending it to a repair service wouldn't also make any sense. For about 50$ - 80$ I could just buy a "new" cracked screen bad ESN photon q and replace the mainboard with my mint chassis, that's not the point.
I'm also interested in electronics so why not trying to rescue it? If I screw it up, so what, I just buy a "new" one then. But if I will be successfull I maybe help other people with a tutorial who also softbricked their phones.
so it seems that the battery is the "problem". maybe the bootloader would work if the battery has some more power (more as 5% or so)
pujdo1 said:
so it seems that the battery is the "problem". maybe the bootloader would work if the battery has some more power (more as 5% or so)
Click to expand...
Click to collapse
Exactly - Shows you are thinking.
Sent from my XT897 using xda app-developers app
---------- Post added at 11:39 AM ---------- Previous post was at 11:20 AM ----------
coon42 said:
Well, the phone is bricked anyway. I can't make it any more worse yet.
Sending it to a repair service wouldn't also make any sense. For about 50$ - 80$ I could just buy a "new" cracked screen bad ESN photon q and replace the mainboard with my mint chassis, that's not the point.
I'm also interested in electronics so why not trying to rescue it? If I screw it up, so what, I just buy a "new" one then. But if I will be successfull I maybe help other people with a tutorial who also softbricked their phones.
Click to expand...
Click to collapse
I'm giving you feedback. I am guessing you are posting in order to get assistance?
If it is bricked, then a charged battery won't help, however, if it just has a flat battery, problem solved. (Unbricked by voltage mod)
Would you pull an engine out of a car that won't start because of a flat battery?
Sent from my XT897 using xda app-developers app
schmandroid said:
I am guessing you are posting in order to get assistance?
Click to expand...
Click to collapse
Yep. As I already mentioned I see two possibilities here:
1. Finding the JTAG port and reflashing the internal sd card using a JTAG Programmer (RIFF Box for example)
2. Finding the sd card chip, desolder it, reprogramm it, resolder it.
I already repaired a harddrive by replacing the circuit board and desoldering / resoldering the flash rom chip from the broken one to the new one.
Doing this on the phone shouldn't be any big difference.
The question is, if the internal sd rom chip of the photon q does - similiar to the CDMA chip - does only have about 10 pins and is therefore pin compatible to a real sd card and behaves like a real one so it can be read and written using SPI or SDIO. In that case rewriting the bootloader will be very easy using an arduino or if only SDIO works, a STMF4 microcontroller for example. If there are hundreds of pins on the chip it meight be too hard till impossible.
The Problem is, I just don't know where the flash chip and the JTAG pads / pins are exactly placed nor the pinout of the JTAG. That's where I need your help. If nobody knows, I will post another picture with all metal covers removed.
If it is bricked, then a charged battery won't help, however, if it just has a flat battery, problem solved. (Unbricked by voltage mod)
Click to expand...
Click to collapse
It is definitely softbricked since I screwed the partition table of the rootfs so I don't think a working battery will help here. Anyway I will try making a factory cable and look what happens then.
OK,
Some earlier phone chargers (Sony Ericsson etc) were 3.5-3.9vdc, if you use one of these, you may get it to power up - the phone 'may' require more power on startup than the adapter can supply though, so a bench supply may be the better option if this is the case. Try it & see.
If you are gung-ho on electronics, then you'll probably have something lying around.
Swapping SMD bios chips etc is a quick way around bad flashes & locked bios. Been there, done that. Sounds like you are familiar with TSOP etc, seeing as you are discussing JTAG etc???
I have acquired a few phones that won't power on (including these), & poor (dead) battery volts is usually the culprit. The batteries won't charge from the phone charger due to the battery internal protection ccts exceeding the lower limit, but if you have a multi-chemistry charger they can be revived by directly connecting to the power terminals & then they often work well.
This is also a good reason to not let the phone self discharge as a way of rebooting when things go wrong. People are doing this, & it is not ideal for this reason.
Try the power adapter & report how it goes.
By the way, there is already an image of the mobo showing what is under the shields. Look at cornholio's thread on the sim mod to find it.
Sent from my XT897 using xda app-developers app
schmandroid said:
OK,
Some earlier phone chargers (Sony Ericsson etc) were 3.5-3.9vdc, if you use one of these, you may get it to power up - the phone 'may' require more power on startup than the adapter can supply though, so a bench supply may be the better option if this is the case. Try it & see.
If you are gung-ho on electronics, then you'll probably have something lying around.
Click to expand...
Click to collapse
I am doing all of my electronics works on a hackerspace so I have more than enough of equipment i need. (bench suppy, oscilloscope, rework station) I also may get a bus pirate if I ask someone there.
I will try powering it up using a bench suppy but I assume the screen will just remain black. But I will let you know as soon as I tried that.
Swapping SMD bios chips etc is a quick way around bad flashes & locked bios. Been there, done that. Sounds like you are familiar with TSOP etc, seeing as you are discussing JTAG etc???
Click to expand...
Click to collapse
I wouldn't call me an expert but I already did some simple TSOP works.
I have acquired a few phones that won't power on (including these), & poor (dead) battery volts is usually the culprit. The batteries won't charge from the phone charger due to the battery internal protection ccts exceeding the lower limit, but if you have a multi-chemistry charger they can be revived by directly connecting to the power terminals & then they often work well.
Click to expand...
Click to collapse
May I use any Li-ion charger? I have a HTC Desire Z / (HTC Vision or G2 in the USA) which has a 3.7V battery but photon Q has only 3.6V so I am afraid killing the battery when charging it using the HTC.
This is also a good reason to not let the phone self discharge as a way of rebooting when things go wrong. People are doing this, & it is not ideal for this reason.
Click to expand...
Click to collapse
I had no choice. I bricked the software when I was at home. Since I have no T5 screwdriver there I wasn't able to remove the battery so the battery just got discharged on the bootloop.
Try the power adapter & report how it goes.
By the way, there is already an image of the mobo showing what is under the shields. Look at cornholio's thread on the sim mod to find it.
Click to expand...
Click to collapse
I will do. Thanks for that info, I found a tomographic scan of the whole phone made by ikv:
I already PMed him for sending me a higher resolution version of that picture so I may find the sd card IC.
When reading cornholio's thread I also found out the reason why my sd card actually wasn't got detected in recovery mode:
http://forum.xda-developers.com/showpost.php?p=35151506&postcount=194
I indeed removed some SMD resistors while removing the CDMA IC so that seems to be the real reason while the SD card wasn't detected.
I just wonder why it still got detected by adb then
Whatever, knowing that the resistors are connected to the sd card IC will make it very easy to find it by a multimeter.
Related
Last night I changed the SIM of my Nexus S, put back the battery but did not close the phone with its battery cover since I was going to change the SIM again soon after. I turned the phone on, but the battery fell down and obviously the phone turned off. However, when I tried to put the battery back and turned on the phone, it did not. The phone seems dead and I'm pretty sure the problem is not the battery as it has always been working fine. Any help?
mimimouchi said:
Last night I changed the SIM of my Nexus S, put back the battery but did not close the phone with its battery cover since I was going to change the SIM again soon after. I turned the phone on, but the battery fell down and obviously the phone turned off. However, when I tried to put the battery back and turned on the phone, it did not. The phone seems dead and I'm pretty sure the problem is not the battery as it has always been working fine. Any help?
Click to expand...
Click to collapse
No charging animation right? Same here. it seems we have bricked our phones beyond repair.
Cache?
I am not too sure if this would work but try these steps however this will only work if you phone is rooted (ONLY UP TILL STEP 5, AFTER STEP 5 ROOT WILL BE NEEDED):
1) Pull of the back cover of the phone and then plug it into the computer via a usb cable
2) Hold down the power button for 15 seconds, in some lucky chances the phone may turn on if not continue to step 3
3) Pull out the battery but keep the usb plugged in DO NOT UNPLUG
4) Now hold down the power button for a further 15 seconds, in some lucky chances the phone may turn on if not continue to step 5
5) After this unplug the phone from the usb, reinsert the battery IF YOUR PHONE IS ROOTED attempt to turn it on but holding the volume UP button and the power button then navigate to the recovery section from here clear your cache then attempt to turn your phone on. IF YOU PHONE IS NOT ROOTED you can only try and turn it on the normal way (by holding down the power button).
Hope this works for you.
mine too, pulled off battery after it hang, and now it can't be turn on.
---------- Post added at 10:55 AM ---------- Previous post was at 10:49 AM ----------
purebasshavoc said:
I am not too sure if this would work but try these steps however this will only work if you phone is rooted (ONLY UP TILL STEP 5, AFTER STEP 5 ROOT WILL BE NEEDED):
1) Pull of the back cover of the phone and then plug it into the computer via a usb cable
2) Hold down the power button for 15 seconds, in some lucky chances the phone may turn on if not continue to step 3
3) Pull out the battery but keep the usb plugged in DO NOT UNPLUG
4) Now hold down the power button for a further 15 seconds, in some lucky chances the phone may turn on if not continue to step 5
5) After this unplug the phone from the usb, reinsert the battery IF YOUR PHONE IS ROOTED attempt to turn it on but holding the volume UP button and the power button then navigate to the recovery section from here clear your cache then attempt to turn your phone on. IF YOU PHONE IS NOT ROOTED you can only try and turn it on the normal way (by holding down the power button).
Hope this works for you.
Click to expand...
Click to collapse
nope, didn't work for me.
JUST STOP !!!
My phone is getting scared.. :laugh:
Do you know how many times i've just pulled the battery when it hangs, or I was stupid and didn't have on the back cover, or it Was wednesday and I was bored?.. Here my phone is, all in a panic, and I'm afraid to pull it's battery to ease the pain of it being frozen, or pull it's battery when it gets sick with a bootlooping bug.. How am I supposed to pull the battery when my hands are shaking and my mind is telling me NO, but my heart just wants to help?? How am I supposed to look my phone in the camera and say, "I can't help you"??
I just can't do it,..
I just can't..
:crying:
:silly:
This sh1t happen to me last night, from my research the emmc is bricked the phone needs a new emmc or a repair using a tool like riff box or an external programmer of a kind.
The cost for this operation is really high i will try to do it with a simple smd work station and see how it goes
@mimimouchi if u don't have warranty, u will have to pay a huge amount to fix the phone which doesn't worth it if u take into consideration the current price and age of the phone
Why this happen on samsung mobiles ? is this company going down ? ffs
Bump
ross231 said:
Bump
Click to expand...
Click to collapse
From my research, people which pull the battery during boot have a dead/bricked or whatever, emmc. Your first bet is the unbrickable mod if u have the soldering skills and the proper tools, after u apply the mod and u can't flash the phone ur emmc crapped and u need to replace it with a new one, u will need an smd station to remove the chip and solder the new one.
The cost of the operation is around 100$, another option is to try and find a new motherboard from a user / broken whatever nexus still at the price range of 100$++
My opinion ? ur phone is dead blame samsung for this **** and go buy a new one without samsung parts ....
Magusxd said:
From my research, people which pull the battery during boot have a dead/bricked or whatever, emmc. Your first bet is the unbrickable mod if u have the soldering skills and the proper tools, after u apply the mod and u can't flash the phone ur emmc crapped and u need to replace it with a new one, u will need an smd station to remove the chip and solder the new one.
The cost of the operation is around 100$, another option is to try and find a new motherboard from a user / broken whatever nexus still at the price range of 100$++
My opinion ? ur phone is dead blame samsung for this **** and go buy a new one without samsung parts ....
Click to expand...
Click to collapse
Same situation, my battery fell out in my nexus-s phone the other day, and in my son nexus-s phone a few weeks ago. Now I have two dead nexus-s phone. WTF. Has anyone solved this issue or is the emmc mod the only option ? I've read about jtag etc. Has anyone tried that ?
jay55555 said:
Same situation, my battery fell out in my nexus-s phone the other day, and in my son nexus-s phone a few weeks ago. Now I have two dead nexus-s phone. WTF. Has anyone solved this issue or is the emmc mod the only option ? I've read about jtag etc. Has anyone tried that ?
Click to expand...
Click to collapse
If ur battery fell during the boot sequence then ur emmc is bricked, and u need to replace it ther is no mod to fix this nor jtag can fix it, if u have experience with smd soldering desoldering reballing reflowing etc etc then u can fix it urself
The cost for this will run around 100euros depends on the shop and the method that they will use to solder the new chip
You can ask local technicians how much they charge for something like this, my opinion is that if they want more than 50euros ur better off buying a newer phone
Magusxd said:
If ur battery fell during the boot sequence then ur emmc is bricked, and u need to replace it ther is no mod to fix this nor jtag can fix it, if u have experience with smd soldering desoldering reballing reflowing etc etc then u can fix it urself
The cost for this will run around 100euros depends on the shop and the method that they will use to solder the new chip
You can ask local technicians how much they charge for something like this, my opinion is that if they want more than 50euros ur better off buying a newer phone
Click to expand...
Click to collapse
actually the battery fell out during the shutdown. Does that change the diagnosis ?
jay55555 said:
actually the battery fell out during the shutdown. Does that change the diagnosis ?
Click to expand...
Click to collapse
no cause ur phone acts completely dead 99% when a nexus s can't give a signal of life (despite battery heating when u plug the charger) it's an emmc brick which can be resolved only if u replace the actual chip all the emmc bricks happen when the battery is removed during boot / shutdown and rarely when the phone is already running android
But if u want to be 100% sure the only cheap solution IF U HAVE THE EXPERIENCE is to perform the unbrickable mod, which requires to remove a resistor on the motherboard and bridge 2 pads, then ur phone will be detected and if u can't flash a rom in this stage then u need to replace the emmc
As for me i'm sure that ur phone has an emmc brick, a nexus s that acts dead, no vibration, no lights, no nothing, except heating when u plug the charger indicates a hardware failure
You have 2 solutions bring it to a shop or fix it urself if u can ... nothing can be done with software at this point that's my opinion
Hey, I had cyangonenmod 10.1 by the whisp for quite a time now. I decided to try swapper and my phone was stuck in bootloop (power on shows samsung logo then off, trying to go download mode shows little light and off, recovery didn't work either, connecting USB shows the same light and off (and odin recognized then 2 seconds after it disconnected), connecting wall charge with the same little ligth and off).
I didn't try adb(maybe if it was possible I could run shell swapoff or something) but now my battery seems to be drained, none of the mentioned above shows any respone.
I have a nandroid backup, but without recovery mode is no use. Is there a way to do something without battery? or even if I get a battery is there something to do?
I had soft brick motorolla defy with battery drained out last week and forums said try Macgyver method (cut any usb cable and connect the red cable to the + where you put the battery) and it worked, should I try it here?
Thanks
mumsy said:
Hey, I had cyangonenmod 10.1 by the whisp for quite a time now. I decided to try swapper and my phone was stuck in bootloop (power on shows samsung logo then off, trying to go download mode shows little light and off, recovery didn't work either, connecting USB shows the same light and off (and odin recognized then 2 seconds after it disconnected), connecting wall charge with the same little ligth and off).
I didn't try adb(maybe if it was possible I could run shell swapoff or something) but now my battery seems to be drained, none of the mentioned above shows any respone.
I have a nandroid backup, but without recovery mode is no use. Is there a way to do something without battery? or even if I get a battery is there something to do?
I had soft brick motorolla defy with battery drained out last week and forums said try Macgyver method (cut any usb cable and connect the red cable to the + where you put the battery) and it worked, should I try it here?
Thanks
Click to expand...
Click to collapse
we have some posts here talking about swapper, it hard bricks the phone
you cant use any method, usb jig or better go to a service
so I found this http://linux-sunxi.org/Boot_Android_from_SdCard,
if someone could help me with the needed files i'd be grateful
can I use a nandroid backup to boot from sdcard?
mumsy said:
so I found this http://linux-sunxi.org/Boot_Android_from_SdCard,
if someone could help me with the needed files i'd be grateful
can I use a nandroid backup to boot from sdcard?
Click to expand...
Click to collapse
7227A doesn't support boot-from-SD.
ShadowsDie said:
7227A doesn't support boot-from-SD.
Click to expand...
Click to collapse
And then my hopes went down the drain .
There's no reason for jtag not to work right? but it's very costly! I don't understand why.. with this riff box you just plug it to the motherboard and push a button.
mumsy said:
And then my hopes went down the drain .
There's no reason for jtag not to work right? but it's very costly! I don't understand why.. with this riff box you just plug it to the motherboard and push a button.
Click to expand...
Click to collapse
every usb jig is special in his way to work with certain devices
i strongly recommend you to replace the motherboard, its the best and the most accurate way of repairng, or go to a service maybe they have jtag
ShadowsDie said:
every usb jig is special in his way to work with certain devices
i strongly recommend you to replace the motherboard, its the best and the most accurate way of repairng, or go to a service maybe they have jtag
Click to expand...
Click to collapse
No, I tried a jig it didn't work, I was asking if jtag has a chance of not working?
Replacing the motherboard is overkill, it's just a galaxy ace plus, probably the motherboard's worth almost like a new phone
mumsy said:
No, I tried a jig it didn't work, I was asking if jtag has a chance of not working?
Replacing the motherboard is overkill, it's just a galaxy ace plus, probably the motherboard's worth almost like a new phone
Click to expand...
Click to collapse
yes..there are chances to a jtag to not work but it worth a try
basically if the problem is the broken emmc yes it will work like would do boot-from-sdcard
but if the bootloader is totally broken i guess no
Hi Guys!
First post here.
Long story short, I put my Moto G to recharge with his own charger, the damn thing started to loop in boot. It powers on, shows the boot logo, vibrates, then stays in black screen but powered for a couple seconds, then reboot again.
I never installed any custom ROM, unlocked bootloader or anything else, in fact, before this I never bothered learning about flashing Android devices. I'm an IT Manager, so the tech terms are no problem, also working with scripts and codding.
Now, because I'm in Brazil and our local Motorola Tech Support is a total disaster, I decided to try solve this on my own, little I knew about the hell I would go trough.
First I tried the Hard Reset, the thing is, my Moto G rebooted when I tried to enter the Recovery Menu.
I tried a Stock 4.4.2 Firmware, no good at all.
I have all the procedures I tried in this thread: ww w.firmware-team.com/showthread.php?p=2564
(remove the space, because I'm a new user, they block me from posting an external link, even if it would help to understand the problem)
If anyone could help me with this, I bought this Moto G less than 4 months, will be a shame If it is lost.
Seems I can't even edit my post until wait 5 minutes. I'm sure you have good reasons, but edit the post should be available, new post should be blocked.
LFCavalcanti said:
Hi Guys!
First post here.
Long story short, I put my Moto G to recharge with his own charger, the damn thing started to loop in boot. It powers on, shows the boot logo, vibrates, then stays in black screen but powered for a couple seconds, then reboot again.
I never installed any custom ROM, unlocked bootloader or anything else, in fact, before this I never bothered learning about flashing Android devices. I'm an IT Manager, so the tech terms are no problem, also working with scripts and codding.
Now, because I'm in Brazil and our local Motorola Tech Support is a total disaster, I decided to try solve this on my own, little I knew about the hell I would go trough.
First I tried the Hard Reset, the thing is, my Moto G rebooted when I tried to enter the Recovery Menu.
I tried a Stock 4.4.2 Firmware, no good at all.
I have all the procedures I tried in this thread: ww w.firmware-team.com/showthread.php?p=2564
(remove the space, because I'm a new user, they block me from posting an external link, even if it would help to understand the problem)
If anyone could help me with this, I bought this Moto G less than 4 months, will be a shame If it is lost.
Seems I can't even edit my post until wait 5 minutes. I'm sure you have good reasons, but edit the post should be available, new post should be blocked.
Click to expand...
Click to collapse
After everything you've done i can't suggest you anything.
But have you considered that maybe something in the hardware broke when you charged it?
As far as i know motorola never made a charger for this phone but many carriers bundle a charger with the phone, hopefully a motorola branded one.
see if you can claim the warranty.
Also, can you post the input/output of the charger you used?
Z-WolF said:
After everything you've done i can't suggest you anything.
But have you considered that maybe something in the hardware broke when you charged it?
As far as i know motorola never made a charger for this phone but many carriers bundle a charger with the phone, hopefully a motorola branded one.
Click to expand...
Click to collapse
In some regions (mostly in Asia) you do get 500mAh charger instead of OTG cable.
Actually, this is probably a battery problem guys. Luckily you have the Moto G and not the X so you can easily remove the battery. Order a new one, make *absolute* sure it's original. Try Amazon or eBay, but make sure it's not used.
Sent from my HTCONE using xda app-developers app
---------- Post added at 10:44 AM ---------- Previous post was at 10:41 AM ----------
Also, try a different outlet source, 1amp or 2amp charger, and different cable.
Personally, what I would do to work around your problem, is order a aftermarket battery set where you can charge the batteries outside the phone (directly w/ adapter), and swap em out when your phone dies. Back when I had a Galaxy this was a life-saver, never tied to an outlet during the day and also helped me in emergency situations.
Sent from my HTCONE using xda app-developers app
Hi!
My charger is branded by Motorola, 850mAh, 5.1V.
I could agree that some hardware may broke during the charge, but which part? Because the battery still charges, the device still connects through Fast Boot menu.
aarongillion63 said:
Actually, this is probably a battery problem guys. Luckily you have the Moto G and not the X so you can easily remove the battery. Order a new one, make *absolute* sure it's original. Try Amazon or eBay, but make sure it's not used.
Sent from my HTCONE using xda app-developers app
---------- Post added at 10:44 AM ---------- Previous post was at 10:41 AM ----------
Also, try a different outlet source, 1amp or 2amp charger, and different cable.
Personally, what I would do to work around your problem, is order a aftermarket battery set where you can charge the batteries outside the phone (directly w/ adapter), and swap em out when your phone dies. Back when I had a Galaxy this was a life-saver, never tied to an outlet during the day and also helped me in emergency situations.
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
The battery on Moto G is not removable without removing the screws and back plate of the phone. Also, the battery stills charges, and the phone can go all day long rebooting, until the battery discharge.
LFCavalcanti said:
Hi!
My charger is branded by Motorola, 850mAh, 5.1V.
I could agree that some hardware may broke during the charge, but which part? Because the battery still charges, the device still connects through Fast Boot menu.
Click to expand...
Click to collapse
I'm not familiarized with phone hardware, but seeing that i'm talking with an IT colleague i can make an analogy
Based on the symptoms you describe, it looks like your HDD, or the HDD chipset is fried.
Now, as in phones almost everything are SoCs (System on a Chip) it does not do any good to know which part is broken because the repair involves changing or replacing almost the entire phone internals.
Z-WolF said:
I'm not familiarized with phone hardware, but seeing that i'm talking with an IT colleague i can make an analogy
Based on the symptoms you describe, it looks like your HDD, or the HDD chipset is fried.
Now, as in phones almost everything are SoCs (System on a Chip) it does not do any good to know which part is broken because the repair involves changing or replacing almost the entire phone internals.
Click to expand...
Click to collapse
I see. What I find most weird is that when writing(flashing) the firmware, I get no errors, seems all the files were written fine.
Maybe is the Partition table. Is there anyway to completely format these Android Devices, like wiping the disk entirely? Because I tried the Blank Flash procedure, but seems the MBR on the disk is not erased in the process.
LFCavalcanti said:
I see. What I find most weird is that when writing(flashing) the firmware, I get no errors, seems all the files were written fine.
Maybe is the Partition table. Is there anyway to completely format these Android Devices, like wiping the disk entirely? Because I tried the Blank Flash procedure, but seems the MBR on the disk is not erased in the process.
Click to expand...
Click to collapse
As far as i know, there aren't ways to play with the partitions in the Moto G.
(I hope it's a) proof: http://forum.xda-developers.com/showthread.php?t=2719931
if i were you, i'd try my chances claiming the warranty if there is one and they don't mind you unlocking the bootloader.
Please help me! :crying:I have already went to different forms and read several threads, but I cant find any solution. I have a Samsung Galaxy tab 2-P3110 that is completely restored to factory settings except that it is still rooted. I tried to update its OS to 4.4 manually by using CWM 6.0.2.7(which is specifically for my device), flashed it using heimdall. At first it worked out fine, booted into CWM recovery mode. But i think i have downloaded a broken OS upgrade, because when i tried to install the package it said it was aborted. After that i never tried to install it again but started to wipe every data that i can wipe, I wiped the cache, the dalvik cache, even restored it to factory settings again. Then i selected boot system now,then it goes into a boot loop in CWM recovery mode, after trying some things like booting it into download mode and pressing the power button down for minutes but it doesn't turn off still the boot loop. Then I emptied the battery, didn't touched it for a couple of days, then charged it for hours, but when i tried to press the power button it didn't boot looped into recovery mode, and it didn't boot at all, all i can see is the empty battery logo when plugged. Even tried pressing all three buttons, and pressing power+down/power+up buttons still nothing. Is my device hard bricked? Help me please!!!
Update: Tried using oneclick unbrick tool (how noobish). It occurred to me that i can't even boot my droid into download mode or even simply boot it for cryn out loud, how can my PC read it. Maybe i should try making an improvised JIG for desperate measures hahaha.
Nirdla01 said:
Please help me! :crying:I have already went to different forms and read several threads, but I cant find any solution. I have a Samsung Galaxy tab 2-P3110 that is completely restored to factory settings except that it is still rooted. I tried to update its OS to 4.4 manually by using CWM 6.0.2.7(which is specifically for my device), flashed it using heimdall. At first it worked out fine, booted into CWM recovery mode. But i think i have downloaded a broken OS upgrade, because when i tried to install the package it said it was aborted. After that i never tried to install it again but started to wipe every data that i can wipe, I wiped the cache, the dalvik cache, even restored it to factory settings again. Then i selected boot system now,then it goes into a boot loop in CWM recovery mode, after trying some things like booting it into download mode and pressing the power button down for minutes but it doesn't turn off still the boot loop. Then I emptied the battery, didn't touched it for a couple of days, then charged it for hours, but when i tried to press the power button it didn't boot looped into recovery mode, and it didn't boot at all, all i can see is the empty battery logo when plugged. Even tried pressing all three buttons, and pressing power+down/power+up buttons still nothing. Is my device hard bricked? Help me please!!!
Click to expand...
Click to collapse
i had a similar problem.. but did you try and go into recovery mode (using cwm)... press volume up and then hold power down until it switches off and then let go of power. you should see the tab 2 logo and after about 5 seconds should go to recovery mode.
volume up is the one next to the power button btw. not sure if that will let you fix it in your case (depending on you having a working recovery) but it fixed my softbrick (did a full wipe in preparation for new rom but rebooted instead of installing a new rom).
Thank you for the advice, but...
50chickens said:
i had a similar problem.. but did you try and go into recovery mode (using cwm)... press volume up and then hold power down until it switches off and then let go of power. you should see the tab 2 logo and after about 5 seconds should go to recovery mode.
volume up is the one next to the power button btw. not sure if that will let you fix it in your case (depending on you having a working recovery) but it fixed my softbrick (did a full wipe in preparation for new rom but rebooted instead of installing a new rom).
Click to expand...
Click to collapse
Thank you for the advice, but i have already tried that, given the title: Wont Boot, enter Recovery or Download mode. For the past few days I've been trying to accept that my device is officially bricked. Because I have read a forum about the difference between hard bricked and soft bricked, and when my device didn't enter both download or recovery mode I already knew that is a sign that it is hard bricked and that it would be hard to fix it because i cant connect it to my computer and try to force boot it manually. Now I'm feeling hopeless But once again thank you, because u tried to help me :good:
I think your recovery is out of date flash the latest recovery then try again.
Sent from my XT907 using xda app-developers app
mrkhigh said:
I think your recovery is out of date flash the latest recovery then try again.
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
But how can i flash if i cant enter the download mode. I think i may use the jig method. Btw thank you for the suggestion.
Edited
Sent from my XT907 using xda app-developers app
Nirdla01 said:
I tried to update its OS to 4.4 manually by using CWM 6.0.2.7(which is specifically for my device)
Click to expand...
Click to collapse
To get to the most critical point first: You obviously didn't read the OP of the ROM thread as "everything P311x Android 4.4.x" needs to flashed through TWRP (recommended recovery for OMNI) or PhilZ Touch or CWM Swipe Edition (later two are recommended for CM11). That being said and out of the way...
- "Bootlooped when attempting to get into CWM"
Well... if your tablet is plugged in to the charger the key combo to either enter recovery or download mode doesn't work. Your tablet needs to be turned off (looooooong pressing power will turn it off in case it hangs) and disconnected from the charger/USB port. Of course, needless to say that you best have 50%+ charge at least.
- "Drained battery, doesn't charge"
No idea what really went wrong in your various attempts to breathe life back into the tablet, but if you drained the battery and now it won't turn on / charge but only show you the "empty battery" sign ... the only way to resurrect the tablet would be to open it up, take out the empty battery and replace it with a charged one to flash back Stock or the correct recovery to go from there again.
I don't know from the top of my head how many cables leads the battery uses to connect to the motherboard, but I assume there are at least three of them (+5V, GND, Charge monitoring). If you can't get hold of a charged replacement battery then you may try to use the trick AdamOutler posted on his YouTube channel? XDA TV channel? some time ago. This involves the use of a resistor across the +5V/GND pins (right there where the battery connects to the motherboard) to trick the charging circuit into actually charging the battery.
However, be warned that taking apart the tablet and tinkering around with the electronics requires SOLID knowledge, otherwise it's just a recipe for disaster (seeing how you already failed reading comprehension prior to flashing a ROM).
As a last resort you may try to post a question in the General forums to try and maybe get a reply on how to get the tablet to charge back up by giving it a shot with Adam's little trick. Alternatively there might also be a way to "hot charge" the battery by connecting it to a suitable power supply for a short amount of time (restoring just a basic charge as you can't possibly fully charge the battery this way - would be way too dangerous without proper charge monitoring).
If you manage to get it back to life you well better make sure you read "everything flashing" the next time you try to flash a ROM... using the totally wrong recovery can have nasty side-effects.
Don't recall if it is a li-poly or lithium ion battery if it is lipo I don't suggest attempting to charge it indoors I set a fire once in a tin pan attempting to charge an rc car lipo pack. It started off normal then about 80% charge it must have finished quickly and exploded yielding a surprisingly large flame.
But if he is right and a charge on the battery will cure it watch it very very closely.
Sent from my XT907 using xda app-developers app
It should be a Li-Ion battery pack.
However, "hot charging" the battery from a power supply is a dangerous task even with "just" a Li-Ion one. It shouldn't be charged for any longer than one hour tops, and depending on the amp rating of the power supply the +5V line should also be choked with a suitable current-limiting resistor to prevent too much current rushing into the cells; that could heat up the battery pack and lead to very unlovely effects like the battery going up in flames.
Like I said ... tinkering around inside the tablet, or with its battery, requires some SOLID, and SERIOUS, knowledge about electronics (i.e. Ohms law to calculate a suitable current limiting resistor value).
Anyhow, attempting Adam's trick (applying a "dummy load" resistor across +5V/GND to get the charging circuit to charge the battery) or pre-charging the battery might be the only way left to get the tablet back to operation - unless he wants to fork out some cash to obtain a replacement battery. Though, with a somewhat charged up replacement battery the "life saving" attempt should well better play out at the first attempt to at least get a recovery up and running (the tablet actually charges in TWRP, can't say for PhilZ/CWM Swipe) or have the tablet get into download mode (once connected to the PC it should draw power from the USB and leave the battery alone).
Though... on a second thought... shouldn't the tablet charge the battery with a lot less than 5V? Looking at the image of a replacement battery on Amazon it would seem the max. charge voltage is 4.2V (this may even involve a voltage divider to bring a 5V supply down a bit).
Typically you can charge a battery with a slightly hotter voltage.
.8 volts isn't that bad a car can charge at 14.4 volts for a fast charge (normally 13.8 tho)
I would charge it from a 100 ma USB charger till it hit 3.7 volts but then again I'm the guy who burned up his rc car....
Sent from my XT907 using xda app-developers app
BoneWithABeagle said:
If you manage to get it back to life you well better make sure you read "everything flashing" the next time you try to flash a ROM... using the totally wrong recovery can have nasty side-effects.
Click to expand...
Click to collapse
First of all I'm very grateful for the concern and more grateful for the knowledge that u shared. i tried to remove the battery and putting it back again, guess what it did'nt work. :silly: I know I'm such a klutz for not reading all about this new OS, because i have done flashing a couple of times before with older versions that's why i felt confident in flashing this new one. I truly feel like an idiot now hahaha... Hope that it would turn on again even if only in the download mode. (Wishful thinking...)
Thank you again for the info, idea, suggestion, etc. etc.. :good:
I have a question. Do you think i accidentally destroyed my battery in my attempt to bring my tab back to life? I just drained it after reading a thread that says "drain the battery and charge it again". Is it the battery or did i just hard bricked my tab by being a complete idiot
btw isn't "Adam's trick" similar to the so called JIG method where you solder resistors/resistor to a micro USB plug? (I'm very sorry for my lack of knowledge, I'm just a medical student with a knack of tinkering with devices
@Nirdla01: To answer your posts from above...
About "was flashing ROMs before":
There's the trap. Each device requires a different strategy to prepare it for flashing a custom ROM; it's not as straightforward across devices - even within the same vendor - as you may think. The other trap, which isn't obviously clear from "just reading through the <insert name of ROM here> OP post" is that the more recent ROMs require an updated recovery for successful flashing.
To wrap it up:
CWM 6.0.2.7 is to be used with CyanogenMod 10.1.2 ONLY
CWM Swipe Edition, Philz Touch Advanced CWM Recovery and TWRP are to be used with CyanogenMod 11 or OMNI
TWRP is to be used with OMNI (with the official Nightlies it's even required so you can flash the nightly delta updates, to my knowledge CWM does not support the "OpenRecovery" scripting).
CWM Swipe Edition, PhilZ Touch and TWRP are all provided by AndroidAndi through his file repository on AndroidFileHost.
As for "destroyed battery":
No, I don't think you "destroyed" the battery. That's not easily doable. However, if the battery is deeply depleted the charging circuit may not want to start charging because it has to pull a whole lot of current (current = Amps). Normally a properly designed charging curcuit shut down in case it goes over-amp to prevent damage.
What I don't fully understand is that you can't get into download mode, though you said the tablet will at least show you the red "Battery Empty" screen for a brief moment.
Anyway, disconnecting and re-connecting the battery doesn't help you in any way. I would try to get some juice into the battery by using a silicon diode (that are the tiny diodes with that copper/brown glass body and the black stripe on one side denotig the cathode) in series with the +5V line coming from the power supply to drop the voltage to ~4.3/4.4V and let it try to charge for... let's say 30 minutes for a start while also keeping an eye at the temperature of the battery (just touch it every one or two minutes, and if it gets too hot to the touch (~ 122°F/50°C) disconnect the power supply and let it cool down if the 30 minutes aren't up already). BUT... Do NOT use any power supply outputting more than 500/750mA for safety reasons! Once you charged for some time connect the battery to the tablet's motherboard and see if it shows a change in charge (i.e. slightly green instead of red). If that works just charge it up a bit more until you're at ~50/60% charge.
Then prepare ODIN + Stock image or ODIN + custom recovery and see if you can get into download mode to flash (avoid having the tablet turned on for too long to save battery - once it's connected to the PC and flashing it draws power from the USB anyway).
If that does not work out no matter what you try, because you managed to screw things up really good, using a JIG to flash through JTAG is then your last resort of recovery (if you can get hold of a readily-assembled one or are able to build one yourself).
As for the confusion about the resistor. I wasn't referring to a JIG. I was talking about putting a resistor (possibly 10 Ohms I would assume) across the positive and negative pins of the pins where the battery connects with the motherboard (and while it's connected). That acts as a "current limiter". In this case the battery can't attempt to pull too much current, therefore avoiding the charging circuit from shutting down.
If you have any questions feel free to ask.
@BoneWithABeagle: Thank you for entertaining my questions you've been a really good help in my journey to revive this piece of brick :laugh: I'm sorry for asking these silly questions, as you know I'm not that knowledgeable about electrical stuff, and I find your advice and suggestions very helpful. So here's another question Can I use the usb cable maybe cut the part where the plug goes into the tablet and maybe connect the wires of that cable to the wires battery directly, then plug the cable into the adapter then try to charge it?
to give you an idea I uploaded some pics :fingers-crossed: btw please view the photos in another tab to see them fully because I've put red arrows as guides.
Nirdla01 said:
So here's another question Can I use the usb cable maybe cut the part where the plug goes into the tablet and maybe connect the wires of that cable to the wires battery directly, then plug the cable into the adapter then try to charge it?
to give you an idea I uploaded some pics :fingers-crossed: btw please view the photos in another tab to see them fully because I've put red arrows as guides.
Click to expand...
Click to collapse
Not a terribly great idea for two reasons: The charger you got with the tablet will happily output up to 2.1 Amps... that's a whole lot of current and far beyond any safe attempt of trying to "hot charge" the battery to reinstate a basic charge. The other reason being the leads inside the USB cable. You cut them rather easily while stripping the outer insulation, but if you got a replacement cable in case the repair attempt works out have a crack at it.
So, while you can sacrifice the cable if you don't have anything better at hand, I highly recommend you to either use a power supply being limited to a much lower output amperage (5V @ 500<->750mA - you don't have any old phones?) or to torture Google to work out a suitable resistor to limit current from the Samsung charger (again, should be large enough to choke current down to 500<->750mA). Also be aware that a limiting resistor needs to turn quite a few Watts into heat. Layman's Estimation Formula: Volts * Amps ~= Watts. Burning away 1.35 Amps to bring it down to ~750mA ... the resistor has to turn ~6.5W into heat, and that's a lot even if it doesn't sound like much! So you need a ceramic power resistor which will get very hot to the touch (keep that away from things that easily melt). Every well-equipped electronics store should have such a such for some exchange money.
Hi i tried to root my phone and got it bricked. I already tried lots of methods to unbrick but only got it worse, at first it was on a soft brick boot loop i used a tool to unbrick and when it was about to finish the app crashed and closed, my phone went dark and died right there. Now when i plug it my pc sees it as "QHSUSB_BULK" and i cant enter to the download mode or anything else (i did some research and find out that my phone doesn't have recoverty mode). I don't know what to do, if anyone can help me i'll be very greatfull.
To try to root my phone i followed this steps: http://forum.xda-developers.com/showpost.php?p=62119694)
To try to Unbrick my phone for the first time i followed this steps: http://forum.xda-developers.com/g-flex2/general/p-restore-recovery-to-stock-tool-h950-t3171550 (Total failure)
Then i followed this: http://www.modifyandroid.com/stock-roms/lg/how-to-flash-stock-rom-for-lg-g-flex-2/ (Used normal flash mode and app crashed so i got HARDBRICKED)
Sorry for my english it's a bit rusty
only solution for this....
http://forum.gsmhosting.com/vbb/f672/worlds-first-lg-ls996-dead-boot-repair-done-2087401/
Maybe somebody will be need that.
Lats time i get to repair Lg G Flex 2 (H955) it was one time working one time not (singing of deth-no reaction).
By disconnecting of battery pluging the charging cable and making shortage on one pin (round one) neared abowe batery socket with - (the plate securing emmc and other stuffs) the phone become alive (sometimes still didnt give the sign of life or was totaly no detection of the phone by pc).
My Laptop sometimes detect him like normal device sometimes like quallcom 9008 device (the most time quallcom) i was in mining that is software problem (from one side will but someting for me was not right).
Also my motherboard was kind of damage from down side of mainboard are 2 capiticors wicht some kind of chip with 4 legs (i dont know the name of it) but is placen on downstairs from left side (i replaced it with other one). After that phone give more singing of life.
I was looking still (because of strange behaviour of phone and switching off).
I get idea to look for emmc of the phone i clean the black stuff aroud that and i give some flux so i make rehot of that chip in temperature of 320 degrees of C with hot air station.
After that i make the phone in one peace and gess what the phone become alive (no porblems with and the client didnt loos the data from the phone) also was some problems to get the phone alive because of not charged battery (so before that all solution please make sure that your battery is 100% ok beacuse sometimes the battery looks ok and is charging but happen that is still damaged).
Also before please check the usb charging socket (and replace it if its damaged) beacuse also the system of phone also switch off the data ways of the usb because of shortages in socket (when the phone is ok and you make it alive and still usb data connection didnt work with your pc use repair app from the store for your android system version) after that everything must work ok.
So in my situation all the phone is working correctly and caused problem of the phone was wrong connection of emmc memory to the board.
Greetz for all.