[Q] K910 Bricked Flashed Charging - Lenovo Vibe Z Questions & Answers

i have bricked my k910 with installing the TWRP.
i have now managed to flash it with MiPhone2.11.6 to K910_1_S_3_2144.1_0040_140219_qpst
and after that sdfuse update to K910_SS_S_2_040_0109_131226 i was able to install all other ROMS.
now my problem is the phone wont charge anymore. i have tried different chargers and i have used the following ROMS
VIBEUI_V2.0_1433_4_ST_K910_baralajbi_V5
VIBEUI_V2.0_1503_7.254.1_ST_K910_NK_W_855A_baralajbi_V12.3
and original roms though OTA update with update assistant and i have restored the ROM before the phone was bricked.
when i plug in the cable i see popup "charging protection enable" and the battery indicator shows that is charging/pluged in but the phone won't charge.

solved
karuna1979 said:
i have bricked my k910 with installing the TWRP.
i have now managed to flash it with MiPhone2.11.6 to K910_1_S_3_2144.1_0040_140219_qpst
and after that sdfuse update to K910_SS_S_2_040_0109_131226 i was able to install all other ROMS.
now my problem is the phone wont charge anymore. i have tried different chargers and i have used the following ROMS
VIBEUI_V2.0_1433_4_ST_K910_baralajbi_V5
VIBEUI_V2.0_1503_7.254.1_ST_K910_NK_W_855A_baralajbi_V12.3
and original roms though OTA update with update assistant and i have restored the ROM before the phone was bricked.
when i plug in the cable i see popup "charging protection enable" and the battery indicator shows that is charging/pluged in but the phone won't charge.
Click to expand...
Click to collapse
re installing the rom VIBEUI_V2.0_1503_7.254.1_ST_K910_NK_W_855A_baralaj bi_V12.3 for the third time solved the problem. this time i renamed VIBEUI_V2.0_1503_7.254.1_ST_K910_NK_W_855A_baralaj bi_V12.3 to update.zip and installed with slideload.

Related

[Q] Weird charging problem

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?

[Q] Rooted, deleted a few things, then dead galaxy s4? What happened?

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.

KNOX or Flashing gone wrong?

Hello Everyone,
So recently I got a new S4 and I decided to root and mess around with it a little bit... Didn't go so well.
First KNOX was pissed that I tried that because I had given SU power to SuperSU (I didnt want to use KingUser) so when that happened, SuperSU failed to set itself as the primary SuperUser app. So I decided to install recovery (TWRP) to do it the recover way, scripts and all that. After that, I went ahead and removed KNOX, via the settings menu on the app.
Now I fail to boot into RECOVERY, and I also fail to boot into normal Android mode. When I attempt to boot normally, the SAMSUNG logo comes up then verizon, Okay fine its booting. 5 miutes later, the phone gets hot, and still wont boot.
I cannot charge the normal way, or even use the charging port. I have to take the battery out and put it in a dock. So ODIN is out of the choice.
My Phone Specs:
Samsung Galaxy S4 i545 (Verizon)
1GB SD Card
No recovery or ODIN.
Please help...
If you can't get into download mode then you have a problem.
Without it there isn't much you can do. You also need the pc to recognize your phone.
I'd say flash a custom ROM because new update which I received on stock firmware of I9500 added some security and an app called smart manager which is causing instability. Connect your dead phone to charger and then flash TWRP 2-3 times and don't forget to untick F.rest time and auto reboot. Normally it is ticked, and manually boot to download mode each time I hope you know how to do that. Then try your luck. That's how I did it. And use latest recovery available on the web.
Hit thanks
I believe the Verizon s4 has a locked bootloader (http://forum.xda-developers.com/showthread.php?t=2681316); therefore, you cannot flash a custom ROM or custom recovery.
You may get more replies if you post your question here: http://forum.xda-developers.com/galaxy-s4-verizon/help
Read before posting!
THe thing is though, If I could use Download mode, i would. But because of damage in the port, it fails to work So this is why I am confused on what to do...
---Edit will go here if needed.
thedarkness523 said:
THe thing is though, If I could use Download mode, i would. But because of damage in the port, it fails to work So this is why I am confused on what to do...
---Edit will go here if needed.
Click to expand...
Click to collapse
if the port is physically damaged then you need to
get the port replaced
there is absolutely nothing you can do until you have the usb port repaired
. secondly hold power down while inserting the battery if that doesn't get it into download mode then congratulations you now have a 200.00 dollar brick
the i545 does not support custom recoveries or custom roms outside of modded stock roms attempting to flash one will result in a permabrick as you just found out
Once the usb is repaired if you are still unable to access download mode then you have a big problem. When the port is repaired see if the comouter recognizes the phone as QHUSB_dload, if so, you need jtag, if the computer doesnt recognize the phone then it is most likely damaged beyond repair.

Elephone p9000 brick - Screen lights up after flashing stock ROM but no boot

I tried flashing the stock rom onto my Elephone P9000 with sp tools. I followed all the steps correctly as I have done in the past. Sp flash tools downloads the rom and says it is a success but yet when attempting to boot the phone, the screen turns on and remains blank. No logo or recovery. Recently I tried flashing TWRP onto the device and that also did not work, when attempting to open recovery mode, the device just rebooted a couple of times, so I left it and forgot about it. I have managed to successfully flash the stock rom in the past but since I sent off my phone to have it's screen replaced, flashing no longer seems to work. I have tried flashing with battery in and out. And i've unplugged cables and replugged them inside the phone, checking for loose connections. If it also makes a difference, since the screen repair, the wireless charging does not seem to work.
If anyone can offer any advice it would be greatly appreciated.
edit: potentially relevant info, flash tool memory test states nand flash is not detected, found a relevant thread but the answer provided did not work for me: http://forum.xda-developers.com/showthread.php?t=1866962
-William
Flash the stock firmware 15072016

LG LS660P soft bricked (Please Help)

H Hi all,
My friend has (I think) soft bricked his LG tribute from sprint. It doesn't charge correctly when plugged into a laptop or the original charger that came with the phone. It just shows the loading battery symbol. However, if you leave it on the charger for about 5-10mins, it will show something up in the top left hand corner of the screen like
[101160] fastboot_init ()
[101260] USB init ept @ 0xffe5000
[101280] udc_start ()
Oh, something that I also forgot to mention is that the phone thinks the battery is at 0% every time I plug it back into the charger, even though I have sufficiently charged it using an external charger. Even when I try to get into recovery mode, the phone won't let me sometimes, because of the supposedly "low" battery percentage. I want to get this phone back up and running, so if ANY of you guys have the same device as me, I need the stock Rom for this device. I have been googling for hours with no luck (the roms that I found weren't in the correct format I needed) A .kdz format is required in order to flash through LG flash tool. Also, take note that this device has NEVER had a custom recovery installed on it, or flashed in any way. If any of you guys have or have found a link to the stock rom file, PLEASE link it in the thread. Thanks!!
Edit: I have found the rom file and have flashed it, and i was able to restore it to factory settings. Consider this thread closed!!!!

Categories

Resources