Database Users

[GUIDE] Recover 2012 and newer XPERIAs from SOFT-brick

Please read all of the first post above and then all the instructions FIRST, before trying anything. If you are unsure about anything PLEASE ASK QUESTIONS. No one wants you to damage your phone. So make sure you understand what your doing. If your not sure what your doing you could do more damage to the phone And remember with an unlocked bootloader you can do severe damage.​ATTENTION:​ If your phone is not working but you see a led or have bootloops DO NOT USE HARD-RESET. This can make your phone lock/freeze up until the battery dies. It took 51 hours for mine to die.
However if you get stuck on a boot screen or get bootloops a SOFT-RESET may work to reboot.​​​
If you have unlocked your bootloader this guide may or may not work for you. If you have trouble recovering then see the "TRICKS that require FASTBOOT-mode" below.​
YOU NEED TO RESET YOUR PHONE!
​
If your phone is soft-brick and does nothing when, -the buttons are pressed, -a charger is plugged in, -or if the screen is still ON then....
The memory chips need lose power to clear the bad data and reset the phone. Either by the battery going dead or by unplugging the battery.
You can to leave the phone on a charger to see when the battery dies. Usually the battery will not charge in a soft-brick state and will die while still plugged in. After the reset you should then get the red led. However if you get a red led immediately when first plugged in and no response but red led for a long time, then you may need to leave the phone unplugged and let the battery die.
Only after the chips reset will you get the red led. The RED LED should mean the phone is charging in 'low battery level charge mode'.
Once you get the red led, after the reset, do NOT try to turn on the phone. If you try to start the phone now without fixing the problem you will have to start all over.
​​
UNPLUGGING THE BATTERY
If you feel like taking your phone apart you can unplug the battery. Most 2012 XPERIA's have a built in battery that is not designed to be easily removed. However next to the battery there should be a ribbon cable with a plug to the mother board. Unplugging this cable for 2-3 minutes should reset your phone without letting the battery die. Read here for the original idea post
CAUTION: this may effect your warranty
CLICK This for a Picture
{
"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"
}
​
The Rubber Band Trick
Here are some links to help describe the rubber band trick.
http://forum.xda-developers.com/showpost.php?p=37562298&postcount=301
http://forum.xda-developers.com/showpost.php?p=37844592&postcount=317
http://forum.xda-developers.com/showpost.php?p=39835850&postcount=527
​
Now after the phone has reset and you have the red led.​​~ keep charging with wall charger. A charger has a higher current rate and should charge faster than a PC.
~ Make flashtool ready to flash your stock.ftf file. If you are experiencing errors while flashing the entire ROM try to flash just the kernel, check off all in the exclude box except kernel. At this point your battery is very low and doing this will make the flash process much faster than trying to flash the entire ROM.
~ Try to connect phone in flash-mode. If your phone has enough battery you will get green led. If the flash fails on the first try, just put it back on the charger and wait about 10-30 minutes and repeat. It may take a while to charge enough to flash.
~ If you see the red led go out, then try for flash-mode.
~ If you get bootloops, try to flash between loops. As soon as you notice loop, hold volume down and plug the phone into PC with FlashTool ready. Once the loop starts you have very little time to flash, before the loops drain the battery. If you can not flash, the battery will have to die and phone reset. Then start over with red led.
~ After you complete the flash, unplug the phone and see what happens. Sometimes it will boot to Sony screen and then shut off by itself, if so plug in to a charger. You should get the red led then the battery charging screen then. After about 20 minutes of red led.
~ If you get a green led (for flash mode) then press the power button until 1 vibration. The green led should flash 1 time. This will end flashmode and start the phone. If you don't end flashmode the phone will still give a green led whenever plugged in, but it will not charge, until the battery dies and the phone resets again.
~ If you were able to flash the entire stock.ftf file and your phone has gone from red led to the charging screen, then your phone should now be recovered and turn on normally.
~ If you could only flash the kernel then you will get bootloops. Again you can unplug and try a hard-reset to turn off the phone. If hard-reset works plug in charger and wait for red led and then charging screen.
~ If you don't do a hard-reset, the phone boot looping should kill the battery and then plug in charger (this is what I did). Then wait for red led and then charging screen.
~ Now you should have a good kernel and the phone plugged in. You should have the charging screen with the battery icon and led for 'off-line charge mode'. Charge until over 50%. A quick press of the power button will bring up the charging screen.
~ Once over 50% then flash the full stock.ftf with a full wipe.
~ If you got this far but still cannot flash a full stock.ftf file then try to use PC Companion software to REPAIR your phone. Make sure battery is more than 50%.
~ If all fails then post a copy of the FlashTool log in this thread.
To save space please use the BB code for HIDE. Example
[HIDE]The text from your log here[/HIDE]
The text from your log here
​
If the above steps do not work you can also try the tricks below.​
Due to the amount and length of TRICKS, I have provided links to their post​
TRICK: FOR PHONE THAT WONT RESPOND; {VIEW THIS POST FOR TRICK}; Confirmed working on ION
TRICK: FOR PHONE THAT WONT RESPOND; {VIEW THIS POST FOR TRICK}; Confirmed ION
TRICK: TRY CONNECTING TO PC; {VIEW THIS POST FOR TRICK}
TRICK: IF BOOTLOOPS WHEN PULGGED INTO PC; {VIEW THIS POST FOR TRICK} This should also work for FLASH mode; Confirmed ION
TRICK: FOR PHONE THAT WONT RESPOND; {VIEW THIS POST FOR TRICK}; Confirmed working on Xperia J
​These TRICKS require FASTBOOT access on the phone​
TRICK: FOR KERNEL WITHOUT OFFLINE CHARGING; {VIEW THIS POST FOR TRICK }
TRICK: IF YOU GET INTO FASTBOOT MODE, BLUE LED; {VIEW THIS POST FOR TRICK}; Confirmed ION
TRICK: FOR UNLOCKED BOOTLOADERS; {VIEW THIS POST FOR TRICK}; Confirmed ION
TRICK: IF YOU TRIED A HARD RESET (3 vibrations); {VIEW THIS POST FOR TRICK}
TRICK: TO USE FASTBOOT TO ACCESS FLASHMODE; { VIEW THIS POST FOR TRICK}; Comfirmed S
TRICK: USE FASTBOOT TO FLASH KERNEL; {VIEW THIS POST FOR TRICK}; Confirmed ION
TRICK: FOR UNLOCKED BOOTLOADERS; {VIEW THIS POST FOR TRICK}; Confirmed SOLA​
Please give feedback if any of these work and on what devices, I will update. 272​​
If you think I should add something new, either post it or PM me the content to add. Thanks to all those who help.
Please vote in my POLL. If this thread helped you please guide others here for the same help ​
LINK FOR FLASHTOOL HELP POST
List of those that have recovered
RaWrGs said:
thank you! Worked perfect!! as hard as it was to let the battery die I did it and she worked!!!
Click to expand...
Click to collapse
305nole said:
My phone is working again, you just have to be patient, as it took >16 hrs for my phone to turn on. Once my phone turn on automatically, I had let sit for 4hrs, then pressed the power and volume up buttons at the same time and held it for exactly 5 seconds, it then turned off and I was able to flash as normal. Just be patient. Thanks everybody.
Click to expand...
Click to collapse
accts said:
Here are the steps I took successfully revise my phone from soft brick.
[*]That is all ... Back and running.
[/LIST]
GOOD Luck.
Timing = could be different from phone to phone - depends on battery of the phone before it dead.
Sent from my HTC PH39100 using Tapatalk 2
Click to expand...
Click to collapse
accts said:
Unbelievable - SOFT brick again :crying: ... trying to deodex the new fw 6.1.E.2.68. Now my device is unresponsive neither to soft or hard reset. Waiting for the phone battery to die and see if I can do anything after that
Edit: whewww...So glad just had to wait for battery die - recharge ! was able to reflash - back in business again :victory:
Click to expand...
Click to collapse
faiisfaizal said:
i charge it then got bootloop...but i did not manage to go to flashmode but fastboot....so i just flash cm9 kernel and it boot..then it go back off....i charge it again and its turning on so i just manage to go flashmode so i flash stock ...and now its revive...im glad i made it
dont just w8 it to green....when it bootloop just do the button to go to flashmode...dont do hard reset..it make ur phone longer charging to make the red led coming
Click to expand...
Click to collapse
soudara said:
ok flashtool flash complete very hard to get greenled but its ok but no boot , i replug in wall charger for 10mn and auto boot and all is ok
my ion working perfect
thank you all
i use generic honkong tft firmware LT28i_6.1.E.1.19_Hong Kong.zip
Click to expand...
Click to collapse
ching11 said:
yeah, finally, Successful to flash the rom in my ION and running normal now~~~:victory::laugh:
Click to expand...
Click to collapse
ghekua said:
I just get my phone back to life )
My phone back to life now.
Click to expand...
Click to collapse
markelON said:
I Flashed Custom kernel and got Briked (Boot Loops) at 9th Dec Morning 10:30AM
Did Hard Reset and phewwww Phone is Completely Dead Unresponsive.
BUT DON'T GIVE UP....
Many Thanks To People Who Have Shared Their Experiences Here.. Keep It Up Guyz.:good:
Click to expand...
Click to collapse
aimakun said:
In last Thursday I decide to get back my bricked ION and then follow the instruction as markelON suggested.
And when I tried 2 hours later, I've finally get the Xperia logo again, and everything become working!
In my case I found later that the speaker in back of the phone has broken. I don't sure this was already broken since the phone bricked or between the repair service tries for recover my phone. But other functions are working and my dad had car accident recently. So I keep my phone and still not send back to repair service yet.
Now it has hardware issue, not brick, so I could call the repair service to fix it now. :silly:
I thank everyone who lend the help, especially markeION.
Thank you very much.
P.S. I has also written the fix instruction summary in my language and publish to local community too, based on markeION suggustion. So I think this would help others who aren't skill the English language too.
Click to expand...
Click to collapse
Zirdark said:
Thanks!
I was able to get it in fastboot mode, i will now try to fla****
this is what i did for the people having the same issue.
once you get the boot loop press power+vol up until you get first vibration, after that very quickly you need to plug usb to the pc while holding only the vol up key.
this worked in a xperia ion bootloader unlocked
Thanks everyone for your help. i got more experience now, i hope this helps to everyone else that have or get the same issue.
Remember when you get bootloop press power+vol up until you get first vibration, then very quickly connect the phone pressing vol up or vol down to get fastboot or flashmode, then you can fix the phone with flashtool. this worked for my Xperia Ion bootloader unlocked
Click to expand...
Click to collapse
warfist said:
Look, right now i am in Fastboot Mode! This time it worked again. But when i try to flash a kernel.sin it says that there is no device! What to do man??
EDIT: WAIT, NOW I AM IN FLASH MODE AND TRYING TO FLASH KERNEL! But after a few seconds i get this:
EDIT 3: I made it! I had to flash the whole Rom. Not just the system.sin and kernel.sin. THANKS FOR ALL YOUR HELP!
Click to expand...
Click to collapse
JaneKimC said:
So I don't do anything about the purple led and just redo the steps?
Okay o_o
-edit-
whathe
I GOT IT TO FLASHMODE
After charging and having constant red led to no led (?) I unplugged from the wall charger and and then plugged to laptop to wait for bootloop. So there was red led, then after a while no led again. I just pressed down (didn't expect anything to happen lol) and then I got GREEN LED!!!! Luckily, I already set up flash tool
I installed ALL the drivers in flash tool
But there was no Ion,
right now i'm installing pc suite cause my sister said there are drivers there.
Am I doing the right move? O_O
-edit2-
MY SISTER WAS RIGHT
IT FLASHED ALL THE WAY THROUGH!!!
btw, checked Exclude TA, is that correct?
phone still won't boot (assuming no battery)
I'M CHARGING RIGHT NOW!!
will report back when it boots
sorry for page stretching!
-edit3-
HOMYGOSH I LOVE YOU ALL
THANKS SO MUCH GUYS!
HAPPY NEW YEAR!
EVERYTHING PAID OFF!!
THANKS TO EVERYONE WHO HELPED ME!!!!
SAVED ME A LOT OF $$$ ^_^
Click to expand...
Click to collapse
tempest2112 said:
Many thanks for this post as I was stuck in a ram dump boot loop and following the instructions allowed me to flash a ftf file and now the phone (Sony Miro) is up and running :victory:
Click to expand...
Click to collapse
albuah said:
i manage to get bootloop after 5-10 minutes.
got my kernel on back. tapping the sony logo and enter cwm , restore my backup , and reboot...but the phone not reboot.
screen are black and red led still there. usb still attach to pc.
need to recharge batteries to full/green led ?
update : i remove the usb cable , and use fastboot mode to flash kernel and on the phone. it boot up nicely in my miui backup with 1% battery haha...
thx to all that help me and of course to this thread
Click to expand...
Click to collapse
ganeshbiyer said:
The phone is back.
Sent from my LT28i using xda premium
Click to expand...
Click to collapse
txingu said:
Thanks ToledoJab!!
I can repair one xperia s with a format memory problem.
The phone stay in SONY logo everytime, but I can flash it again.
Thanks!!
Click to expand...
Click to collapse
Damjan94 said:
Thanks you rly helped me get my phone working again
I got it bricked by installing cwm and it didn't let me boot in os, than I formatted /system and lost cwm, all my system
I wonted to install newest cynogen mod so my question is: "can I use flasher to flash cynogen mod?"
Click to expand...
Click to collapse
dansdepeter said:
After all, I read about unbricking phone I am now in the situation of blinking red light and the phone turn on with a black screen.. then after 20min the phone fully turn-off and i charge the phone and i get solid red light.. hoping that it will be fix. Thanks to all
My Xperia ion now back to normal.. I get red light but cannot detect on laptop and all the button of xperia not working. I first run the flashtool ready to install firmware and then together with pc companion and finally the xperia green led comes up........ w/out pc companion my xperia still on red light and all button of xperia not working.. The Flashtool detect the phone and install the firmware...
Thanks to this blog..
Click to expand...
Click to collapse
gegode said:
:victory: :good: well thanks to all xda developer for this thread.. :good: :victory:
my 1 week old Sony Xperia J (rooted , v6 supercharger , stock firmware) that appears BOOTLOOP :crying:
it happens when i try to use some method "how to connect stock firmware ICS to ad-hoc" by changing wifi supplicant script..
OK ,
:silly:ENJOY UR BRAND NEW/OLD ware:silly:
:victory: WELL THATS IT ,, THATS WHAT I'VE DONE ,, you guys can follow it if you like .. i can do it , so u can. ryt? :silly:
THANKS TO THIS THREAD , AND ALL CREDIT TO ALL XDA Developer Who already tested all trick and method and provide all TOOLS :highfive:
IM NOT GOOD ENOUGH IN ENGLISH . PERIOD
Click to expand...
Click to collapse
crevatsch said:
Thanks for the answer and the miracle has happened, my phone is back from the dead. This is how i did it:
I got frustrated with the phone after it wouldn't respond to the soft reset it was trying (power + volume up). Then i pressed the volume up button while playing a game with the other while in the corner of my eye i see the light changing color and yes, it had gone into fastboot. After that i flashed the kernel only, but the phone wouldn't boot. I was angry that i let this good chance slip, but i managed to do the trick again: just keep pressing volume up, until it went into fastboot. I flashed the stock rom and my phone worked again.
Moral of the story (and something to put in the startpost): Even if the screen doesn't show anything and even if the phone doesn't vibrate or give a signal to indicate the battery is full it can still go into fastboot if you press the button repeatedly and keep trying.
Thanks for the help!
Click to expand...
Click to collapse
CoB_Mike said:
Worked like a charm for me brother. Installed something to my L28at and it was showing incorrect battery and couldnt re install original OS. Now I am good!
Click to expand...
Click to collapse
snaky47 said:
Anyone can help me please, i have strong red light and i can't flash again.
EDIT: Now, after unplugged and waiting 5 mn, i plugged again I see the logo of the battery:laugh: and it appears that it is empty after 20 hours of charging lol. I wait a bit and I'll let you know if I can flash:fingers-crossed:
EDIT2: I installed cm9 and restored my backup. everything is ok now.
Click to expand...
Click to collapse
gnahanut said:
Mine is the same problem, the kernel does not support offline charging, and the issue is that: the phone runs out of battery - It gets booted up after 5 minutes charging and then turn off. The cycle continues.
I solve the problem by:
- Let it charge till the screen boots up.
- Power + volume up for 1 vibration, and then hold volume up for fastboot mode.
- Flash adv kernel 17 and then connect to charger. Let it charge for 30 mins.
- Reflash the Rom kernel.
Everything works perfectly after that.
Click to expand...
Click to collapse
Flowa said:
Thanks it worked!
But is there a way that you can use the phone with pc companion after flashing it?
Because pc companion told me i have a wrong firmware...
Click to expand...
Click to collapse
anzsensei said:
Alhamdulillah ~ SUCCESS :good:
SUPER Thanks To Everyone Here~!!
:victory:
Click to expand...
Click to collapse
ardalaan said:
ok i after about 9 hours of charging i didn't get any response from my Phone (ion)
so i decided to open my phone and disconnect the battery cable !
after i disconnect my battery cable and plug it again i connect my phone to wall charger and get a red light LED.. after about 20 minutes red led become orange then i connect my phone to pc and start flashtool and flashed new TFT file
all i am saying is that if u don't get red light after couple of hour you have 2 options !
let the battery drain then start charging or unplug battery cable then plug it back
here is the picture of my ion's battery flat
Click to expand...
Click to collapse
Levopron said:
Yess!! I Repair.. Thank Youu!!
Click to expand...
Click to collapse
ToledoJab said:
Well I recovered my Ion.
Now for some reason I cannot flash any baseband when using win xp. I can flash basebands from ubuntu though. It took me a few hours to figure this out. Tried reboot, older version and every stock ftf I have, ics & gb. I can flash all other parts of the stock ftf. Baseband freezes flashtool up at processing the data and I have to close flashtool.
Not sure why win xp wont work, but since linux worked I dont care
I got some good tips to add to OP.
Flashing just the kernel requires less battery charge to flash and fixes offline charging.
Also unplugging the battery after back pieces are removed should eliminate the waiting for battery to die, if you can handle taking phone apart. Battery unplug should save a lot of time in both discharge and charging. If battery is full if will take days to discharge. But if you unplug it should reset and keep the charge for flashing.
Well now on to my wifes captivate glide. It keeps shutting down when data is turned on. Time to learn about odin and Samsung
Click to expand...
Click to collapse

[SOFT-BRICK RECOVERY] Recover most XPERIAs from SOFT-BRICK
If you are not sure what your doing or just want to confirm something, PLEASE ASK QUESTIONS FIRST. You always want to do the easiest things first.There many of us that have had success using different methods. And there are many of us who are willing to help.
The Wikipedia definition for {Brick (electronics)}
When used in reference to consumer electronics, a "brick" describes an electronic device such as a smart phone, game console, router, or tablet computer that owing to a serious misconfiguration, corrupted firmware or a hardware problem, can no longer function. The term derives from the vaguely cuboid shape of many electronic devices (and their detachable power supplies) and the suggestion that the device can only function as a large, heavy object.
The term can also be used as a verb. For example, "I bricked my MP3 player when I tried to modify its firmware."[1]
In one common sense of the term, "bricking" suggests that the damage, often a misconfiguration of essential on-board software, is so serious as to have rendered the device permanently unusable.
However, another use of the term "bricked" is understood to describe a situation where a device is unable to function even when the device does have potential to be recovered later to a working state. In this sense, the damage may be reversible; it is only during the period that it's unable to function that the device is deemed "bricked". This is often referred to as a "soft brick" whereas an unrecoverable device is a "hard brick".​
DON'T WORRY, BE PATIENT, YOU CAN FIX YOUR PHONE.
This common 'cents' is worth more than a million dollars the price of your phone
accts said:
My two cents, always install CWM - Backup your ROM, before doing any modding to your phone.
Click to expand...
Click to collapse
​
For this guide I will define types of RESETS that happen when pressing both the POWER and VOLUME UP buttons.​SOFT RESET = 1 vibration then let go of buttons (hold about 3 seconds); Like hitting REBOOT.
HARD RESET = 3 vibrations then let go (about 10 seconds); Like taking out the battery.*
*USE HARD RESET ONLY IF ALL OTHER TRICKS HAVE FAILED. RECOVERY FROM THIS DEEP LEVEL OF SOFT-BRICK WILL TAKE A LONG TIME​Both can be used at anytime on a working phone. Most bootloops will also allow resets​
XPERIA phones have 2 different modes that are used in recovering from SOFT-brick. FLASH mode & FASTBOOT mode.​FLASH mode, is used by FLASHTOOL and can be used on every model of XPERIA phone with a locked or unlocked bootloader. FLASH mode will give a soild GREEN notification led when connected. To connect in FLASH mode:
Start with the phone turned off (or in between loops for some tricks)
Press and HOLD the volume DOWN button. (don't let go )
Now connect to a PC using USB
If all went correctly you will get GREEN led, then let go of button
​FASTBOOT mode is used by Android Debug Bridge (ADB), and is found on every Android device. FLASHTOOL also uses FASTBOOT mode, however to flash this way you need an UNLOCKED bootloader. NOT EVERY PHONE CAN USE FASTBOOT. To find out if you can use FASTBOOT and how to set it up read {Spectre51's} thread on {unlocking & relocking bootloaders}. FASTBOOT mode will give a soild BLUE notification led when connected. To connect in FASTBOOT mode:
Start with the phone turned off (or in between loops for some tricks)
Press and HOLD volume UP button. (don't let go )
Now connect to a PC using USB
If all went correctly you will get BLUE led, then let go of button
​​
To recover your phone you need to have FLASHTOOL ready and waiting at a specific spot.​
If you need help with setting up & using FLASHTOOL {>>CLICK HERE<<}
DO NOT CONNTECT YOUR PHONE
First you need to have FLASHTOOL installed from {HERE}
Now run FLASHTOOL.
From FLASHTOOL home, select the flash/lightning bolt button
Select FLASH MODE
Select your stock firmware file
WIPE: everything
If available EXCLUDE: TA. (this option is not available for all stock.ftf files, if it's there just exclude it)
Now click START button
After FLASHTOOL prepares files, you should get this screen (or similar depending on version of FLASHTOOL)
>>>>>STOP<<<<< FLASHTOOL is now ready for TRICKS
​​​
For help with finding your phones STOCK.ftf file click here​
You can use the file for your XPERIA model below to recover from SOFT-brick.
To make your models specific .ftf file after you recover, you will find instructions {IN THIS POST}
MAKE SURE YOU USE A STOCK FIRMWARE FOR YOUR MODEL XPERIA. Each phone model has a different file. Using the wrong file will give you the very SOFT-brick your trying to fix. If your not sure then ask for help.
Links to STOCK FIRMWARES
XPERIA P{LT22}
XPERIA V{LT25}
XPERIA S{LT26}
XPERIA SL{LT26ii}
XPERIA Acro S{LT26W}
XPERIA ION{LT28}
XPERIA TX{LT29}
XPERIA T{LT30}
XPERIA TL{LT30at}
XPERIA TIPO{ST21}
XPERIA TIPO DUAL{ST21_2}
XPERIA MIRO{ST23}
XPERIA U{ST25}
XPERIA J{ST26}
XPERIA GO{ST27}
XPERIA Sola{MT27}
Special THANKS go to the following XDA members for providing and maintaining links for the STOCK.ftf files above. Please click their THANKS button in the post you download from.
{dimon2242} {championswimmer} {Yakandu} {NomNomM} {zhuhang} {Spectre51} {hhlong89} {gregbradley} {Jozinek} {TeamMex} {Deadmask} {irontech}
PC Companion can interfere with FLASHTOOL. Make sure it is NOT running when using FLASHTOOL.​
BATTERY CHARGING CYCLES​
On a working phone there are different stages of a battery's charging cycle. The stages are listed in order they happen. The cycle goes from a completely dead battery through a phone running on battery and back to a completely dead battery.
Dead battery. No response from the power button, no screen and no led.
Connect to charger
low battery level charging mode. This is when just the RED led is on and no screen. At this stage the battery's charge is to low to turn the phone on, but it is charging.
Kernel controlled off-line charging mode. This is when the battery has charged enough from step (3) and boots the kernel to charge the battery. The phone is off, but could be turned on using the power button. A quick press of the power button will show this battery icon. Icon will fill with charge.
The kernel also controls charging when the phone is on.
Battery is fully charged.
Unplug the phone and turn on.
Battery is dead from normal use.
Repeat stages starting at (1)
​
Now, that is for a working phone. But if your reading this you don't care about a working cycle right? WRONG, this gives a baseline of charging check points to help in recovering your phone, so it is fairly important to understand.
A soft-brick charging cycle can restart at different points along the baseline while attempting to boot.
The kernel is the first thing to run at start-up.
If the kernel is broken the phone may.....
Lock-up before the kernel boot screen with just the back-light on.
Lock-up at the kernel boot screen.
get stuck in boot loops.
The SONY screen is displayed during kernel start-up, for a stock kernel.
A charging cycle for a phone with a broken kernel can go as far as stage (4) and then lock up or boot loop. Then the battery will have to die for the phone to reset and start over at step (1).
Thus ending a broken kernel cycle from dead battery to dead battery.
The system or ROM/firmware runs after the kernel starts successfully.
If the ROM is broken the phone may.....
Lock-up after the kernel screen with just the back-light on
Lock-up at the ROM boot screen
Get stuck in boot loops.
The XPERIA screen is displayed during ROM start-up, for a stock ROM.
A charging cycle for a phone with a broken ROM can go as far as stage (6) and then lock up or boot loop. Then the battery will have to die for the phone to reset and start over at step (1).
Thus ending a broken system cycle from dead battery to dead battery.
​​
​{SONY's PC Companion}
AN UNLOCKED BOOTLOADER WILL NEED TO BE RE-LOCKED FOR PC COMPANION TO WORK.​​

Thanks this is very helpful

thank you! Worked perfect!! as hard as it was to let the battery die I did it and she worked!!!

Before you wait all that time, try this. Hold the volume up button and the power button at the same time. The phone will vibrate once, keep holding until it vibrates 3 more times. Now you should be able to try flashing again. Worked for me.

44Blackhawk said:
Before you wait all that time, try this. Hold the volume up button and the power button at the same time. The phone will vibrate once, keep holding until it vibrates 3 more times. Now you should be able to try flashing again. Worked for me.
Click to expand...
Click to collapse
+1

In my case, trying to reset didn't work at all.

Yea same here as I could not get mine to do anything. I saw in another thread on this someone said once you get the Sony loop to do a force reset (1 buzz) and as soon as it buzz's hold volume down. You should see the green light flash and should then be able to connect it in flash mode again. Adds up with what I did and its very strange there is so much difference from device to device on a shared issue.
Edit: Pop why did you bale on the Ion???

The AHD is more responsive and the screen seems to be brighter and more clear and the glass was already scraching and the gorilla glass on the AHD will not.

Well was nice to have your help for as long as we did. Enjoy your new device.

popfan said:
The AHD is more responsive and the screen seems to be brighter and more clear and the glass was already scraching and the gorilla glass on the AHD will not.
Click to expand...
Click to collapse
The glass or the clear cover over it was?
Sent from my Sony Xperia S

popfan said:
The AHD is more responsive and the screen seems to be brighter and more clear and the glass was already scraching and the gorilla glass on the AHD will not.
Click to expand...
Click to collapse
Also known as Xperia ion lt28h.
General 2G Network GSM 850 / 900 / 1800 / 1900 3G Network HSDPA 850 / 900 / 1700 / 1900 / 2100 Announced 2012, April Status Available. Released 2012, June Body Dimensions 133 x 68 x 10.8 mm Weight 144 g - Touch-sensitive controls Display Type LED-backlit LCD, capacitive touchscreen, 16M colors Size 720 x 1280 pixels, 4.55 inches (~323 ppi pixel density) Multitouch Yes, up to 4 fingers Protection Scratch-resistant glass - Sony Mobile BRAVIA Engine
- Timescape UI Sound Alert types Vibration; MP3 ringtones Loudspeaker Yes 3.5mm jack Yes

Spectre51 said:
The glass or the clear cover over it was?
Sent from my Sony Xperia S
Click to expand...
Click to collapse
The glass itself. It has several small scratches into before I turned it in, just 28 days later. That is rather poor scratch-protection.

Does the Ion have the film over the glass like the Play did?? My Play scratched one day when I dropped it but figure I will just find me a high quality screen protector and replace it. Maybe some 3m product. I looked on the Ion and could not tell if it has it or not.

zackspeed said:
Does the Ion have the film over the glass like the Play did?? My Play scratched one day when I dropped it but figure I will just find me a high quality screen protector and replace it. Maybe some 3m product. I looked on the Ion and could not tell if it has it or not.
Click to expand...
Click to collapse
Yes it does.
Sent from my Sony Xperia S

popfan said:
The glass itself. It has several small scratches into before I turned it in, just 28 days later. That is rather poor scratch-protection.
Click to expand...
Click to collapse
The only way you could scratch the glass itself is if you removed the oem screen protector. You can't really tell its there until you know it's there. The X10 was the same way.
The included screen protector does scratch fairly easily and looks like scratched glass when it happens.
Sent from my Xperia ION using xda premium

if my screen is stuck on xperia logo. NOT BOOT LOOP. just stuck there. (unable to hard reset) cannot turn phone.
is this soft brick?

I performed these steps and it worked one time but when I did it a second time, it bricked my phone. It won't respond to any thing. Can somebody please help?!?
EDIT: Sorry guys, I freaked out last night and posted this before I did my reSEARCH. This is my problem now, I've been charging for phone for >9 hrs and it still hasn't turned on. It took about 6 hrs to get the red led light. When it came on, it was solid and not blinking. Should I just be patient?

You did not hard brick your phone. You will just have to do the steps all over again. Wait until the battery dies, then recharge and reflash. Make sure you battery is over 50%.

Just be patient and persistent. It can be very frustrating but you will get back in.

[Q] Help! Nexus 7 not working, may be bricked

Hello all,
Recently I have had a major issue with my nexus 7. About a week ago, it died (ran out of battery) while I was using it. When I attempted to turn it on after charging it, I would get the screen that says google, with unlocked lock icon. The tablet would be frozen at this screen. I left it running until it died again. I was running the latest stable release of cyanogenmod 10 with no problems before when this happened.
By now I had realized that the nexus may have been bricked. I did some googling and found that this is an issue other users have been having when their battery died on android 4.2.2. I attempted to restore the nexus. At this time I was able to access bootloader on the device by holding down all of the buttons at the same time. However, I decided not to restore the nexus, and wait until a time where I would be able to turn all of my attention to the problem. But when I tried to restore the device yesterday, I was not able to access bootloader! I connected the device to my PC (running win8) and it is not recognized. Similarly, trying fastboot restart-bootloader gives me "waiting for device". I am afraid that the bootloader may have been corrupted somehow.
My question is, how can I fix this? Is there a way to reflash the bootloader, or is there something that I am missing? Is there a hardware operation that needs to be performed on the device (battery pull, etc)?
Thanks.

AW: [Q] Help! Nexus 7 not working, may be bricked
I doubt your nexus is bricked. Most likely you entered the APX mode. Hold down the power button for about 6-10 seconds, then it should exit from there.
http://forum.xda-developers.com/wiki/APX_mode
Sent from my Nexus 7 using xda app-developers app

Not working
AndDiSa said:
I doubt your nexus is bricked. Most likely you entered the APX mode. Hold down the power button for about 6-10 seconds, then it should exit from there.
http://forum.xda-developers.com/wiki/APX_mode
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
When I hold down the power button, the device just turns off and comes back on again. The google boot logo shows for a few seconds, then I get a black screen.

patil215 said:
When I hold down the power button, the device just turns off and comes back on again. The google boot logo shows for a few seconds, then I get a black screen.
Click to expand...
Click to collapse
If you get a Google logo, that is a good sign - it means the bootloader is at least partially intact, possibly even in perfect shape.
I would proceed assuming that your battery is completely discharged.
Put the device on the charger overnight and then try starting it up while it is still plugged in to the charger. Hold the vol-down button and the power button continuously until at least one second after the Google logo flashes - this should put the device into fastboot mode if the bootloader is intact.
Something to remember is that Li-Ion batteries have a safety feature that prevents them from charging if the battery voltage gets too low. This is part of the reason why they are shipped with a 50% charge - they can sit that way for months and months only self-discharging at a very very slow rate.
OTOH, if you discharge the battery deeply and then let it sit for a long time afterward - especially if there is something like APX mode draining current - the battery voltage can fall below this "safety threshold voltage" and (even though it is still a "good battery" it can no longer be charged).
I'm not sure it the N7 can be started up while plugged in to only the charger; if it can, disconnecting the battery and trying to power up the device might be a way to discriminate "dead device" from "unchargeable battery".
good luck

I've tried this before
bftb0 said:
If you get a Google logo, that is a good sign - it means the bootloader is at least partially intact, possibly even in perfect shape.
I would proceed assuming that your battery is completely discharged.
Put the device on the charger overnight and then try starting it up while it is still plugged in to the charger. Hold the vol-down button and the power button continuously until at least one second after the Google logo flashes - this should put the device into fastboot mode if the bootloader is intact.
Something to remember is that Li-Ion batteries have a safety feature that prevents them from charging if the battery voltage gets too low. This is part of the reason why they are shipped with a 50% charge - they can sit that way for months and months only self-discharging at a very very slow rate.
OTOH, if you discharge the battery deeply and then let it sit for a long time afterward - especially if there is something like APX mode draining current - the battery voltage can fall below this "safety threshold voltage" and (even though it is still a "good battery" it can no longer be charged).
I'm not sure it the N7 can be started up while plugged in to only the charger; if it can, disconnecting the battery and trying to power up the device might be a way to discriminate "dead device" from "unchargeable battery".
good luck
Click to expand...
Click to collapse
I've tried this before. I still get a google screen, even after fully charging it. Does this mean that the battery has become unusable? How can I fix this?

Then try it again. It takes less time than typing a post into XDA.
There are two ways to try it.
1) Hold both Power & Vol-Down simultaneously, and keep holding them down until at least 4 seconds after the B&W "Google" text appears on the screen
2) Hold only the Power button down continuously, but be ready! Press the Vol-Down button as soon as the Google logo appears! - you only get less than a second to do this. (If you are late, the bootloader tries to boot the boot partition). Also, you need to keep holding the Power button down (3 or 4 seconds) after this - wait long enough that you are convinced that the fastboot screen is not going to occur.
As for the battery, you can pop off the back case and use a voltmeter to CAREFULLY measure the open-circuit voltage. The normal 0%-to-100% voltage range is about 3.6v - 4.15v. Obviously if it won't take a charge then there is a battery issue. BE CAREFUL - avoid doing anything which could short the terminals even momentarily.

bftb0 said:
Then try it again. It takes less time than typing a post into XDA.
There are two ways to try it.
1) Hold both Power & Vol-Down simultaneously, and keep holding them down until at least 4 seconds after the B&W "Google" text appears on the screen
2) Hold only the Power button down continuously, but be ready! Press the Vol-Down button as soon as the Google logo appears! - you only get less than a second to do this. (If you are late, the bootloader tries to boot the boot partition). Also, you need to keep holding the Power button down (3 or 4 seconds) after this - wait long enough that you are convinced that the fastboot screen is not going to occur.
As for the battery, you can pop off the back case and use a voltmeter to CAREFULLY measure the open-circuit voltage. The normal 0%-to-100% voltage range is about 3.6v - 4.15v. Obviously if it won't take a charge then there is a battery issue. BE CAREFUL - avoid doing anything which could short the terminals even momentarily.
Click to expand...
Click to collapse
I've tried holding down the buttons in various configurations at least 50 times already. As for the battery, there is current flowing, so I don't think this is a battery issue. Also worth noting is that if the device completely dies and I plug it in again, the charging battery sign appears (an empty battery slowly filling with white bars). Sometimes the device will give a black screen with little white sparks flickering randomly on it.

Well there have been several posts on here with identical symptoms, where the affected owner later reported that their tablet mysteriously started operating normally.
Unfortunately nothing consistent seems to have emerged from those reports.
You could try disconnecting the battery for a few minutes and reconnecting it to see if that makes any difference.
But whatever you do, you're gonna eventually have to press some buttons & the procedure I suggested is diagnostic for the bootloader, even if the boot or /system partition are borked.
BTW In my experience that battery charging graphic shows the charge state of the battery - does yours show closer to empty or full?

bftb0 said:
Well there have been several posts on here with identical symptoms, where the affected owner later reported that their tablet mysteriously started operating normally.
Unfortunately nothing consistent seems to have emerged from those reports.
You could try disconnecting the battery for a few minutes and reconnecting it to see if that makes any difference.
But whatever you do, you're gonna eventually have to press some buttons & the procedure I suggested is diagnostic for the bootloader, even if the boot or /system partition are borked.
BTW In my experience that battery charging graphic shows the charge state of the battery - does yours show closer to empty or full?
Click to expand...
Click to collapse
Mine shows the battery going from empty to full, like an animation. Also, I'm considering sending in the device for repair but I know that since the bootloader is unlocked it probably wouldn't be free.

Also can you link me to any posts related to this? They might be useful in solving my problem.
Thanks

Were you able to get your computer to recognized your Nexus when you connected it? I had to jump through a bunch of hoops with my Win8 machine to get the driver installed, because it didn't pass Microsoft's signature check. Maybe you can use Wug's toolkit to try to fix it, or at least re-lock the bootloader before sending it in for repair?

codehunter2000 said:
Were you able to get your computer to recognized your Nexus when you connected it? I had to jump through a bunch of hoops with my Win8 machine to get the driver installed, because it didn't pass Microsoft's signature check. Maybe you can use Wug's toolkit to try to fix it, or at least re-lock the bootloader before sending it in for repair?
Click to expand...
Click to collapse
After spending a few hours, I was able to get an adb driver installed onto my computer, I also had to jump through a lot of hoops (I run win8 too). Running adb devices shows the nexus in recovery mode. However, I can't access the bootloader whatsoever. Typing fastboot reboot-bootloader just hangs, and I've tried several toolkits but they just hang. I'm not sure if I can do anything unless I can access bootloader. If you know anything I can do please tell.

patil215 said:
Mine shows the battery going from empty to full, like an animation. Also, I'm considering sending in the device for repair but I know that since the bootloader is unlocked it probably wouldn't be free.
Click to expand...
Click to collapse
By coincidence I was charging mine right now (82%), so I shut it down and looked at that battery animation. (I have the v4.18 bootloader & Dec '12 hardware) First the "lightning bolt" symbol shows up in the battery icon, and the a little later, it performs a "filling the battery up" animation. But here's the important part: when that animation runs on mine, it starts from nearly, but not quite full (mostly white, not all black)- about 82%.
Can't tell exactly from the way you described your situation, but this (again) sounds like your battery is either not charging, or the bq27541 charge controller is reporting the wrong battery state.
Unplug the battery and let it sit for a while before reconnecting. If you have a safe way to measure the battery voltage, do so. You'll know right away if the battery is charged and the charge controller chip is lying.
---------- Post added at 08:14 PM ---------- Previous post was at 07:37 PM ----------
patil215 said:
After spending a few hours, I was able to get an adb driver installed onto my computer, I also had to jump through a lot of hoops (I run win8 too). Running adb devices shows the nexus in recovery mode. However, I can't access the bootloader whatsoever. Typing fastboot reboot-bootloader just hangs, and I've tried several toolkits but they just hang. I'm not sure if I can do anything unless I can access bootloader. If you know anything I can do please tell.
Click to expand...
Click to collapse
That is completely bizzare. The only way that a recovery can be started is via the bootloader. If the bootloader doesn't run, nothing can run. (The recovery is a booted kernel just as with the regular OS). Moreover, you saw the battery screen light up - if a recovery was (still) running, you would think something would show on the screen (although I guess recent versions of TWRP does screen blanking now). Very weird.

bftb0 said:
By coincidence I was charging mine right now (82%), so I shut it down and looked at that battery animation. (I have the v4.18 bootloader & Dec '12 hardware) First the "lightning bolt" symbol shows up in the battery icon, and the a little later, it performs a "filling the battery up" animation. But here's the important part: when that animation runs on mine, it starts from nearly, but not quite full (mostly white, not all black)- about 82%.
Can't tell exactly from the way you described your situation, but this (again) sounds like your battery is either not charging, or the bq27451 charge controller is reporting the wrong battery state.
Unplug the battery and let it sit for a while before reconnecting. If you have a safe way to measure the battery voltage, do so. You'll know right away if the battery is charged and the charge controller chip is lying.
---------- Post added at 08:14 PM ---------- Previous post was at 07:37 PM ----------
That is completely bizzare. The only way that a recovery can be started is via the bootloader. If the bootloader doesn't run, nothing can run. (The recovery is a booted kernel just as with the regular OS). Moreover, you saw the battery screen light up - if a recovery was (still) running, you would think something would show on the screen (although I guess recent versions of TWRP does screen blanking now). Very weird.
Click to expand...
Click to collapse
Can I have the links that you mentioned about users having identical symptoms that "fixed themselves"?
I really don't want to send it in for repairs if it's going to cost me. I'm a student with not much money to spare . One of the reasons I bought the nexus 7 in the first place.

bftb0 said:
By coincidence I was charging mine right now (82%), so I shut it down and looked at that battery animation. (I have the v4.18 bootloader & Dec '12 hardware) First the "lightning bolt" symbol shows up in the battery icon, and the a little later, it performs a "filling the battery up" animation. But here's the important part: when that animation runs on mine, it starts from nearly, but not quite full (mostly white, not all black)- about 82%.
Can't tell exactly from the way you described your situation, but this (again) sounds like your battery is either not charging, or the bq27451 charge controller is reporting the wrong battery state.
Unplug the battery and let it sit for a while before reconnecting. If you have a safe way to measure the battery voltage, do so. You'll know right away if the battery is charged and the charge controller chip is lying.
---------- Post added at 08:14 PM ---------- Previous post was at 07:37 PM ----------
That is completely bizzare. The only way that a recovery can be started is via the bootloader. If the bootloader doesn't run, nothing can run. (The recovery is a booted kernel just as with the regular OS). Moreover, you saw the battery screen light up - if a recovery was (still) running, you would think something would show on the screen (although I guess recent versions of TWRP does screen blanking now). Very weird.
Click to expand...
Click to collapse
I also fully charged the nexus 7 overnight. The battery icon now showed no animation because the battery was full (it first showed a picture of the lighting bolt battery, then a picture of a full battery) so I believe that the battery is working correctly.

patil215 said:
Can I have the links that you mentioned about users having identical symptoms that "fixed themselves"?
I really don't want to send it in for repairs if it's going to cost me. I'm a student with not much money to spare . One of the reasons I bought the nexus 7 in the first place.
Click to expand...
Click to collapse
I didn't make a record of them - you will need to search. What sounded very familiar was when you had said
patil215 said:
...black screen with little white sparks flickering...
Click to expand...
Click to collapse
What I recall - probably imperfectly - was that most of those cases seemed to spontaneously resolve when the owner charged their battery. And since your story started out with "black screen and little white sparks flickering", and "low battery" it sounded quite similar.
The various folks who mentioned this said things like "white lines flashing", "like sparks", or "like snow on an old-fashioned TV screen". Don't know if that will help you search, but they are in this forum (Q&A).
I also don't know if their tablets were in one particular mode or another (judging from a PC connected to the tablet - a black screen on the tab doesn't tell you anything) - I don't think any of them reported this.
As I said previously, that Black and White Google logo is produced by the bootloader. I just started my tablet in APX mode right now, and while the "charging battery" icon shows up when using the APX cold-start sequence (Vol-Up+Power), that B&W Google (text) Logo does not show up on the screen - the tablet goes directly from battery charging to APX mode (detected by looking at the PC - device shows up under "Other devices -> APX" in the device manager; VID/PID pair USB\VID_0955&PID_7330&REV_0103
)
So, my point is that it sure seems like your bootloader is there and capable of at least starting up at least part way.
What if your Vol-Down button was not working and you had a borked "boot" partition? If you had that combination, the bootloader wouldn't go into fastboot mode, as it would never see the Vol-Down keypress... and if your boot partition was borked, then you would never get any boot accompanied by a black screen.
At this point I think you should try observing the behavior of the USB port from the PC while trying to start it up... and even though you've tried it before, see if you can get the fastboot screen to appear. Perhaps there is something funky going on with your Vol-down button.
good luck

bftb0 said:
I didn't make a record of them - you will need to search. What sounded very familiar was when you had said
What I recall - probably imperfectly - was that most of those cases seemed to spontaneously resolve when the owner charged their battery. And since your story started out with "black screen and little white sparks flickering", and "low battery" it sounded quite similar.
The various folks who mentioned this said things like "white lines flashing", "like sparks", or "like snow on an old-fashioned TV screen". Don't know if that will help you search, but they are in this forum (Q&A).
I also don't know if their tablets were in one particular mode or another (judging from a PC connected to the tablet - a black screen on the tab doesn't tell you anything) - I don't think any of them reported this.
As I said previously, that Black and White Google logo is produced by the bootloader. I just started my tablet in APX mode right now, and while the "charging battery" icon shows up when using the APX cold-start sequence (Vol-Up+Power), that B&W Google (text) Logo does not show up on the screen - the tablet goes directly from battery charging to APX mode (detected by looking at the PC - device shows up under "Other devices -> APX" in the device manager; VID/PID pair USB\VID_0955&PID_7330&REV_0103
)
So, my point is that it sure seems like your bootloader is there and capable of at least starting up at least part way.
What if your Vol-Down button was not working and you had a borked "boot" partition? If you had that combination, the bootloader wouldn't go into fastboot mode, as it would never see the Vol-Down keypress... and if your boot partition was borked, then you would never get any boot accompanied by a black screen.
At this point I think you should try observing the behavior of the USB port from the PC while trying to start it up... and even though you've tried it before, see if you can get the fastboot screen to appear. Perhaps there is something funky going on with your Vol-down button.
good luck
Click to expand...
Click to collapse
UPDATE!:
Not sure if this will help at all. But I ran adb -d reboot bootloader, and the device just turned off. Completely. I turned it on again by holding power for 15 seconds but I got the exact same thing as before (google with black screen following). Once the device was on and I connected it to Windows, windows said "Windows detected malfunctioning device". But I couldn't duplicate the results again. Running adb -d reboot bootloader just hangs.

patil215 said:
UPDATE!:
Not sure if this will help at all. But I ran adb -d reboot bootloader, and the device just turned off. Completely. I turned it on again by holding power for 15 seconds but I got the exact same thing as before (google with black screen following). Once the device was on and I connected it to Windows, windows said "Windows detected malfunctioning device". But I couldn't duplicate the results again. Running adb -d reboot bootloader just hangs.
Click to expand...
Click to collapse
Incredibly, extra-ordinarily bizzare. ADB on the tablet side is a daemon process that runs in userspace. You would need a completely functional kernel to be running on the tablet, and a functioning ramdisk too in order to communicate with the tablet. ADB does not talk to fastboot mode, nor any other mode of the bootloader.
IF YOU ARE REALLY SHUTTING YOUR DEVICE OFF AND THEN SOMETIME LATER YOU ARE ABLE TO TALK TO THE TABLET BY USING THE adb COMMAND (not fastboot), THAT MEANS THAT THE BOOTLOADER IS SUCCESSFULLY BOOTING SOME (unknown) LINUX KERNEL.
That truly beggars the question of why you are seeing anything on the screen after the google logo. Did the previous ROM not have a splash-screen?
Well, if you can communicate with ADB it might be appropriate to try:
adb reboot recovery
and see what this does.
If you can find the device in the Windows device manager, what would be really, really helpful would be the device VID/PID pair.
The way you do this is like this:
1) Identify the device in device manager; right-click on it and select "Properties"
2) Select the "Details" tab
3) In the "Property" Combo-box pulldown, select the Property Name"
Hardware Ids
If you can get those values we can identify exactly which mode the device is in. There is a decoder ring at the end of the first post in this thread
OK, I'm starting to get fatigued, as I offer up both things to attempt as well as avenues of exploration, and you seem to simply ignore all of it.
I know you have tried it several times, maybe even a million times. Please try both methods of starting the tablet to try and intercept the initial phase of the bootloader startup and see if you can get the tablet to go into fastboot mode.
It's OK to try it and fail. But in all this back-and-forth, not once have you said, "yes I tried it again and it still failed". Try it and report the result, even if it fails.
Please try it again - both methods. In the second method where you click the Vol-Down button only after you see the B&W "Google" text, you need to do it really quickly - and not let your finger off the Power button either for several seconds.
---------- Post added at 06:08 PM ---------- Previous post was at 06:02 PM ----------
PS
The "-d" option to the adb command should only be needed if you were running an emulator via the Google SDK on the same PC.
If that were the case, when you ran the command
Code:
adb devices[/url]
you would see multiple lines of output indicating multiple devices on the machine - one for each running emulator, and one for the actual hardware device (so long as it is actually booted into a recovery or OS and you have the right drivers installed).

bftb0 said:
Incredibly, extra-ordinarily bizzare. ADB on the tablet side is a daemon process that runs in userspace. You would need a completely functional kernel to be running on the tablet, and a functioning ramdisk too in order to communicate with the tablet. ADB does not talk to fastboot mode, nor any other mode of the bootloader.
IF YOU ARE REALLY SHUTTING YOUR DEVICE OFF AND THEN SOMETIME LATER YOU ARE ABLE TO TALK TO THE TABLET BY USING THE adb COMMAND (not fastboot), THAT MEANS THAT THE BOOTLOADER IS SUCCESSFULLY BOOTING SOME (unknown) LINUX KERNEL.
That truly beggars the question of why you are seeing anything on the screen after the google logo. Did the previous ROM not have a splash-screen?
Well, if you can communicate with ADB it might be appropriate to try:
adb reboot recovery
and see what this does.
If you can find the device in the Windows device manager, what would be really, really helpful would be the device VID/PID pair.
The way you do this is like this:
1) Identify the device in device manager; right-click on it and select "Properties"
2) Select the "Details" tab
3) In the "Property" Combo-box pulldown, select the Property Name"
Hardware Ids
If you can get those values we can identify exactly which mode the device is in. There is a decoder ring at the end of the first post in this thread
OK, I'm starting to get fatigued, as I offer up both things to attempt as well as avenues of exploration, and you seem to simply ignore all of it.
I know you have tried it several times, maybe even a million times. Please try both methods of starting the tablet to try and intercept the initial phase of the bootloader startup and see if you can get the tablet to go into fastboot mode.
It's OK to try it and fail. But in all this back-and-forth, not once have you said, "yes I tried it again and it still failed". Try it and report the result, even if it fails.
Please try it again - both methods. In the second method where you click the Vol-Down button only after you see the B&W "Google" text, you need to do it really quickly - and not let your finger off the Power button either for several seconds.
---------- Post added at 06:08 PM ---------- Previous post was at 06:02 PM ----------
PS
The "-d" option to the adb command should only be needed if you were running an emulator via the Google SDK on the same PC.
If that were the case, when you ran the command
Code:
adb devices[/url]
you would see multiple lines of output indicating multiple devices on the machine - one for each running emulator, and one for the actual hardware device (so long as it is actually booted into a recovery or OS and you have the right drivers installed).[/QUOTE]
Sorry for not indicating the results of all of your suggestions.
Believe me, I have probably tried both of your button combinations at least two dozen times already. And I have gone down every avenue of exploration that you've suggested.
I've even tried every single one of the button combinations in the thread of nexus 7 button combinations. When I do anything from when the device is on, after 5 seconds or so the device turns off. Then the tablet shows the Google screen for about 5 seconds, no matter what I do. After the google screen comes a blank black screen (I can tell the device is still on because it's illuminated black, different from if the device was dead or powered off). There's not even a way I can get the tablet to power off - it just automatically restarts even if it's not connected to power, so I have to let it die or do a battery pull if I want to fix it. The black screen remains there indefinitely (until the battery runs out of course).
I've tried disconnecting the battery, leaving it disconnected for 30 minutes, connecting the device to power with the battery disconnected, having the buttons held down and connecting the tablet to wall power and USB pc, and different chargers. Nothing gives me a different result. The battery is alive and working, and the voltimeter did give me a current, sorry for not posting that earlier. About the random sparks/snow, there is really no pattern to when these appear, although they might be more frequent (but it might just be me) after a battery pull or full battery discharge.
Remember, I used to be able to access the bootloader but that stopped working for some reason. I'm kicking myself right now for not restoring the tablet when I was able to access bootloader, but I was busy at the time.
I've had some experience with rooting, locking, and unlocking other android devices, but this is something extremely weird.
Also, I should have posted the hardware ID's of the device before. I had done the exact same thing as you suggested when I was trying to install an adb driver for the nexus 7 (had to jump through a lot of hoops to get it working on win8, goddamn win8). The hardware ID's are USB\VID_18D1&PID_D001&REV_9999 and USB\Vid_18D1&PID_D001. According to the guide this means the device is in custom recovery, which makes sense because I was running Cyanogenmod 10 with clockworkmod recovery. If normally booting into the OS, the tablet should be giving me the default animated Cyanogenmod splash screen. Perhaps this issue is a bug with clockworkmod recovery?
I know that -d is to target a specific device, however I pulled up adb and went through each command methodically (really tedious) to see which ones would work. For some reason adb -d reboot-bootloader was the only thing that gave me a response, and even that won't do anything anymore (it just hangs, same with any other adb command). adb reboot recovery hangs also, and any fastboot command gives me waiting for device. Since I've installed a driver for it, in device manager the device shows up as Android phone and Android Composite ADB Interface. Windows tells me it's working properly (really? I'm not so sure windows).
I'd like to apologize for not indicating the results of trying your suggestions. Believe me, I have been trying them! I've spent probably a total of 12 hours trying to get this damn tablet fixed.
I'd also like to thank you. Without people like you this forum would not be any good. I am really grateful for any advice even if it does not work.
I know this is a hell of a problem. No goddamn clue how this happened. I love android but I sincerely hope that this is a clockworkmod recovery problem because otherwise that would make it a mistake on Google's (and therefore android's part). I know that the battery issues are quite frequent on android 4.2.2, but I have yet to find another user with my symptoms.
Lastly, do you know of some way to lock the device or destroy evidence of having the bootloader unlocked without being able to access the bootloader, in case this can't be fixed and I have to send it in for repair?
Click to expand...
Click to collapse

patil215,
Whew. That took you some time to write - thanks for all the details.
The USB\VID_18D1&PID_D001 USB Device Id sure does look like the custom recovery. I will assume - unless you say differently - that you would see this VID/PID pair any time you had the "black screen but with the backlight on".
Android uses this thing called the "BCB" (Boot Communications Block) to write instructions for the bootloader about what it should do when it starts up the next time. In the absence of seeing this, no doubt the bootloader has a default behavior. But basically, the way this works is that a "reboot" command eventually causes the kernel to write into this non-volatile memory area, and then a soft hardware reset occurs. The bootloader is aware of the BCB, and under normal circumstances, it will read it and attempt to follow the indicated boot mode - and then either erase the BCB or fill it with the "default booting instructions" just prior to booting a kernel or special-purpose mode previously indicated. In this way it will return to it's default behavior the next time it is booted.
The reason I mention it is that I have seen on other devices that got borked (HTC Droid Eris) in a way that sometimes those phones would always jump into a particular booting mode - and ignore any hard-button presses that would normally cause the bootloader to follow a different path. The Eris had/has "bootloader", "fastboot", and "OEM" modes and sometimes borked devices would not boot into anything other than the OEM mode.
So, since you apparently are seeing some evidence that a partially-functioning recovery is running, that sounds like a very similar scenario - the Asus bootloader is always booting to your (damaged?) recovery.
So, that's materially different (I think) than what other folks might have experienced it. The first time I've seen it here, although TBH I've only been looking in here for a little less than 3 months.
I don't know what else to suggest - it sounds like maybe you've tried things like "adb shell" commands?
If the bootloader can't be forced into fastboot mode, that (possibly damaged) recovery mode is the only privileged thing you have left. It seems to me that if you can't get into that somehow - adb being the most obvious route - then there is little left to do.
No, I don't know how to relock the bootloader without using the bootloader. That's probably something that can only be done with factory methods (possibly in APX mode).
Sorry.

[Q] Nexus 4 Damage Help

So first some back-story, I'll get right into it. I recently dropped my phone in some water. As soon as possible I dried off the outside, and let it sit. That was the only thing I could do at the time, I had no rice, no tools to open up the phone, anything. I ended up with a solid red light, and everything unresponsive.
The next day I got some tools to open her up. There was pretty extensive corrosion to the motherboard, so using some alcohol I cleaned it all off, rinsed it, and let it dry. I also took apart everything else and cleaned any corrosion. The inside looks brand new. However, this isn't the point of the thread.
It appeared my cleaning helped quite a bit. Upon re-assembling and plugging in, I immediately got a charging sign on the phone. However, after trying to power on, I got no response. Additionally, The charging signal went out after about 20 seconds, and the whole phone became unresponsive again. I can do this process as many times as I want, but the same thing happens every time.
So I tried a different approach. First I hold down both volume rockers plus the power button, and plug it in while holding them down. This puts the phone into "download mode" However, once in download mode the phone is, again, unresponsive. After plugging into my laptop, my computer recognizes the phone, but not as "Nexus 4," but as "Full JellyBean on Mako."
Is there anything I can do about this? I've heard about drivers being able to be installed when in download mode, but I would not know what these are, where to get them, or how to install them. I really don't mind if my phone never works 100% again, I doubt it would. I just want to be able to get into the storage so I can recover some of the files I lost.
It's also probably worth mentioning I have not gotten a solid red light after the clean. Once in a while I will get a blinking red light after plugging it in, but after less than a minute it stops and goes through the charging/stop charging phase I'm so familiar with. Any help at all would be appreciated, and thanks in advance.

The charging block and/or battery could be wrecked, for safety reasons and because it will probably become faulty soon you should change the battery anyway. If the charging block is broken flashing your phone could fail. It's also possible the board was irreparably damaged, but it's probably worth a try as the parts aren't too expensive.

DrFredPhD said:
The charging block and/or battery could be wrecked, for safety reasons and because it will probably become faulty soon you should change the battery anyway. If the charging block is broken flashing your phone could fail. It's also possible the board was irreparably damaged, but it's probably worth a try as the parts aren't too expensive.
Click to expand...
Click to collapse
After trying to figure more things out, I kept it plugged in for a while. It appears my battery actually holds at least a pretty good charge, as the indicator is full when I plug it in now. However, I don't know what you mean when you say charging block.
Also, I seemed to determine my power button isn't working either. I always thought no response to pushing it meant there was something else going on, but I am able to put it into "download mode" by just holding down the volume rockers and plugging it in. Is there a way to turn on the phone another way besides the power button? Also if not, will buying another power button fix the problem? I don't want to buy one then later figure out the reason it wasn't turning on was just a board problem, and not a problem with the button itself.

You can short the power button with a screwdriver or something should turn the phone on., By charging block I mean the secondary board that the micro usb port is a part of, it can be replaced fairly easily if necessary.

26694484 100
DrFredPhD said:
You can short the power button with a screwdriver or something should turn the phone on., By charging block I mean the secondary board that the micro usb port is a part of, it can be replaced fairly easily if necessary.
Click to expand...
Click to collapse
With a screwdriver? Enlighten me, I'd have no idea how to do that. If I had a faulty charging block, then my phone wouldn't be able to charge correct? My phone was plugged in for a while in download mode, and it gained a full charge from a relatively low charge. I also took the block apart and cleaned any corrosion, so I think that's still functional.
Some more progress, upon further attempting to turn the phone on, I was able to get it into fastboot mode. When plugging into the computer it is recognized, but as just "Android." I will type out what information is displayed here, minus serial number, as a new member cannot submit links in posts apparently.
FASTBOOT MODE
PRODUCT_NAME - mako
VARIENT - mako 8GB
HW VERSION - rev_11
BOOTLOADER VERSION - MAK0230d
BASEBAND VERSION - M9615A-CEFWMAZM-2.0.1700.98
CARRIER INFO - None
SERIAL NUMBER -
SIGNING - production
SECURE BOOT - enabled
LOCK STATE - locked
Also, fastboot at the top (as far as I know) usually says "Start" or "Recovery Mode," but mine says "Restart bootloader." When I try switching with my volume buttons, nothing happens.

Another update, just in case anyone is still listening..
Str1ngcheese said:
Also, fastboot at the top (as far as I know) usually says "Start" or "Recovery Mode," but mine says "Restart bootloader." When I try switching with my volume buttons, nothing happens.
Click to expand...
Click to collapse
This no longer applies, for some reason I am able to switch through all modes, incliding "Start, Power Off, Recovery Mode, and Restart bootloader."

Str1ngcheese said:
Another update, just in case anyone is still listening..
This no longer applies, for some reason I am able to switch through all modes, incliding "Start, Power Off, Recovery Mode, and Restart bootloader."
Click to expand...
Click to collapse
Now that you're at this point, have you attempted to flash the phone with a stock image? I'd be weary of what the other poster said though and ensure your USB connection is holding steady because you don't want it dying half way through a flash because then you'll have a brick.

Monotoko said:
Now that you're at this point, have you attempted to flash the phone with a stock image? I'd be weary of what the other poster said though and ensure your USB connection is holding steady because you don't want it dying half way through a flash because then you'll have a brick.
Click to expand...
Click to collapse
I have tried actually. I used the Nexus Root Toolkit v1.8.0 to try and flash it. At first it wouldn't find the device, but through device manager I manually installed the usb_driver onto the phone. After this, the toolkit was able to find the phone. I attempted to flash the image, but it ended up staying in fastboot mode. The program then suggested I try to enable "force flash," which I did, and this time it was never able to finish because the phone tried to restart, but went through that "charging to unresponsive" state I described in my first post.
Upon trying to flash it normally again, it looks like maybe the phone has to be unlocked to do this properly? I then tried to unlock with the same program, but in order to do that, I need the power button to confirm I actually want to unlock the phone. So yet again, I need that power button working.
Any ideas/suggestions/solutions would be amazing.

Jellybean on mako means that your phone is in lgnpst/qcpnst mode. Looks like something failed to start and made the bootloader trogger that mode
Sent from my Nexus 4 using xda app-developers app

opssemnik said:
Jellybean on mako means that your phone is in lgnpst/qcpnst mode. Looks like something failed to start and made the bootloader trogger that mode
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Soo, any suggestions?

Str1ngcheese said:
Soo, any suggestions?
Click to expand...
Click to collapse
clean all the contacts with alcohol (not the normal one, the other that i dont remember the name).clean all the corrusion that you can find,let your phone charge for some hours and try again

opssemnik said:
clean all the contacts with alcohol (not the normal one, the other that i dont remember the name).clean all the corrusion that you can find,let your phone charge for some hours and try again
Click to expand...
Click to collapse
I've already done that.
Str1ngcheese said:
The next day I got some tools to open her up. There was pretty extensive corrosion to the motherboard, so using some alcohol I cleaned it all off, rinsed it, and let it dry. I also took apart everything else and cleaned any corrosion. The inside looks brand new.
Click to expand...
Click to collapse
Problem is the power button doesn't work, and the flashing fails. It looks like the flashing fails because the phone isn't unlocked. To unlock, I need the power button. Kinda stuck.

Str1ngcheese said:
I've already done that.
Problem is the power button doesn't work, and the flashing fails. It looks like the flashing fails because the phone isn't unlocked. To unlock, I need the power button. Kinda stuck.
Click to expand...
Click to collapse
the golden contacts on the power button / mobo could be damaged, do a little short till phone turns on

opssemnik said:
the golden contacts on the power button / mobo could be damaged, do a little short till phone turns on
Click to expand...
Click to collapse
How would I go about doing a short?

Str1ngcheese said:
How would I go about doing a short?
Click to expand...
Click to collapse
touch in both pins, something that passes electric current(like a yarn,wires, copper wire, something that passes electrical current).its basicly what the power button does.

Locked out of EDL, ROM, and recovery

I have an A2017U. Earlier I EDL flashed @jcadduono's B19. But now, when I use VolUp+Power, it goes to stock recovery and reboots. So I can't factory reset the phone. And I don't have TWRP either. I also can't boot into the stock ROM by just holding power, stock recovery appears for a second and then the phone turns off. When I hold VolUp+VolDown+Power I get a black screen and a solid red light, which is supposed to be EDL. But MiFlash doesn't detect the phone.
What the hell am I supposed to do to recover, when I'm locked out of all the modes I can use to get out of this mess?!
Thanks!

Always replace recovery with twrp when flashing. If you can get to test mode - vol down + power - you can adb reboot edl.

@lafester: Do you mean the FTM screen? Is that test mode? I've seen it before but I've always thought it was 100% useless. I've never heard of anyone flashing from that screen. What about DFU? When I press VolDown+Power the stock recovery screen just flashes for a second and the phone shuts off. Same thing when I press VolUp+Power. I simply don't see how flashing a stock EDL can brick the phone, MiFlash reported it was successful. No errors at all. But now, I can't get back into EDL. Just a solid red light and a black screen. MiFlash wont read it, neither will Axon7Tool. I think the issue is that my data and cache partitions are F2FS, stock recovery can't read them, so it just shuts down. I had this issue before, but eventually the ROM booted and told me to factory reset. So I did and all was dandy. No luck this time around.

Another thing I've noticed, is that when I reboot to EDL, I get a black screen and a solid red light. I was previously running AEX Oreo, I have heard that the Oreo bootstacks can screw with EDL. Before Oreo I got a black screen and a red light that blinked once and turned off, then I was able to EDL flash. I have read that if I let the phone fully discharge (by allowing the red light to drain the battery completely), then maybe I can try something else in a few hours once that is done. But what? really need some help here.
Thanks!

AnonVendetta said:
Another thing I've noticed, is that when I reboot to EDL, I get a black screen and a solid red light. I was previously running AEX Oreo, I have heard that the Oreo bootstacks can screw with EDL. Before Oreo I got a black screen and a red light that blinked once and turned off, then I was able to EDL flash. I have read that if I let the phone fully discharge (by allowing the red light to drain the battery completely), then maybe I can try something else in a few hours once that is done. But what? really need some help here.
Thanks!
Click to expand...
Click to collapse
I run Oreo bootstacks and EDL works fine.
If you cant enter recovery or EDL mode, you will have to try with a deep flash cable (very low chances of it working) or follow this guide https://forum.xda-developers.com/axon-7/how-to/guide-dfu-unbrick-guide-disassembly-t3731152

So did you try it? Yes, ftm screen is test mode. You also need to tell us what device manager is saying when you are in edl mode.

lafester said:
So did you try it? Yes, ftm screen is test mode. You also need to tell us what device manager is saying when you are in edl mode.
Click to expand...
Click to collapse
he has a black screen with a red light, that's DFU
EDL only blinks a red light once
thats a 4th category brick

AnonVendetta said:
Another thing I've noticed, is that when I reboot to EDL, I get a black screen and a solid red light. I was previously running AEX Oreo, I have heard that the Oreo bootstacks can screw with EDL. Before Oreo I got a black screen and a red light that blinked once and turned off, then I was able to EDL flash. I have read that if I let the phone fully discharge (by allowing the red light to drain the battery completely), then maybe I can try something else in a few hours once that is done. But what? really need some help here.
Thanks!
Click to expand...
Click to collapse
Have fun using my guide! ?

He has a u version. Most likely not bricked.

lafester said:
He has a u version. Most likely not bricked.
Click to expand...
Click to collapse
crap, i overlooked that. Maybe @kitcostantino knows more? Honestly I never understood what was his problem or what he did to fix it, but it was on an U and it looked exactly like DFU...

Only time I ever had a dfu issue was with the very first Chinese beta. I was able to get into test mode and then boot into edl.

So, no access to FTM, otherwise my issue would be solved and I wouldn't be posting. I let the battery drain all day by letting the red light burn through it, I had figured that letting the battery drain would be the equivalent of short circuiting the pin that @Choose an username... speaks of. No power in the circuits=reset. I got it to where the red light either does blink, or stays on for a moment and turns off. But EDL and other tools doesnt recognize the phone either way. I read some of the 4th category brick guide, it says you need to disassemble the phone. But I am no good with hardware, if I take it apart then it will very likely not go back together in one piece. So I would like to avoid that. I also don't have the money to pay a technician, I prefer to fix my own problems. I bought my A7 new from NewEgg, it came with SquareTrade insurance. Maybe I should call ZTE and try to get a warranty repair? I can just tell them I was repairing via EDL from a bootloop, when it all went bad. Don't need (and probably shouldn't) mention TWRP, etc.
I have 3 QUSB__BULK entries under "Universal Serial Bus Devices" in Device Management. Normally, it would show up in "Ports" category, if EDL was working properly.

Just dropped a private message to @kitcostantino to see if here can post in the thread.....

Volume + and - plug USB cable at the same time may work......

@stinka318: Already tried that before you posted. Same as before.

If you still have your warranty, then I'd send it back to ZTE if you can't get it to come back to life.

@try5890: I still have the standard warranty, as well as SquareTrade insurance. But if there is a way out of this that doesnt involve hardware disassembly (which might make things worse), then I'd rather go that route instead. It's Sunday anyway, so I'll have to wait til tomorrow to call either ZTE or SquareTrade. If there is a chance of resolving it before then.....

AnonVendetta said:
So, no access to FTM, otherwise my issue would be solved and I wouldn't be posting. I let the battery drain all day by letting the red light burn through it, I had figured that letting the battery drain would be the equivalent of short circuiting the pin that @Choose an username... speaks of. No power in the circuits=reset. I got it to where the red light either does blink, or stays on for a moment and turns off. But EDL and other tools doesnt recognize the phone either way. I read some of the 4th category brick guide, it says you need to disassemble the phone. But I am no good with hardware, if I take it apart then it will very likely not go back together in one piece. So I would like to avoid that. I also don't have the money to pay a technician, I prefer to fix my own problems. I bought my A7 new from NewEgg, it came with SquareTrade insurance. Maybe I should call ZTE and try to get a warranty repair? I can just tell them I was repairing via EDL from a bootloop, when it all went bad. Don't need (and probably shouldn't) mention TWRP, etc.
I have 3 QUSB__BULK entries under "Universal Serial Bus Devices" in Device Management. Normally, it would show up in "Ports" category, if EDL was working properly.
Click to expand...
Click to collapse
You have another problem there. Right click on the QUSB_BULK and Uninstall device. If you were on DFU it would show up as ZTE Handset Diagnostic Interface.
If you ever used Zadig then that's your problem. If not, it's worth trying anyways

Choose an username... said:
crap, i overlooked that. Maybe @kitcostantino knows more? Honestly I never understood what was his problem or what he did to fix it, but it was on an U and it looked exactly like DFU...
Click to expand...
Click to collapse
just to clarify, what i have had success with,is letting the phone completely die, then charging with my laptop (which is lower power than a QC or standard plug) until i get the 'connect charger' message. at that point i charge using my Quick Charge oem brick and cable. after that, for whatever reason, EDL works for me again. Prior to that, point, DFU mode was all i could get. no recovery, no fastboot, no EDL. Just solid red light after holding the EDL mode key combo (vol +, vol -, power). but no Qualcomm 9008 whatever it is, ive done this a couple of times. its always trying to go stock, but something had failed.
while it makes no sense to me, id say its worth a shot. boot into what you have at that point, which is only DFU mode, and simply let the phone die. if it powers off, power back on, and let it die completely. then plug up to a computer usb port, let it charge until you get that message, and after you charge above 30-40% min, EDL to something else. i must also say somewhere in my mis-adventures, i killed the imei on not one but two a2017u boards, so something does not like going back to MM. at that point, i had a bad download of b15 that was breaking touch functionality, so i flashed back to MM. The board flashed fine, but serial and imei went bye bye.
[posted for the greater good...this was a pm. ]
AnonVendetta said:
@try5890: I still have the standard warranty, as well as SquareTrade insurance. But if there is a way out of this that doesnt involve hardware disassembly (which might make things worse), then I'd rather go that route instead. It's Sunday anyway, so I'll have to wait til tomorrow to call either ZTE or SquareTrade. If there is a chance of resolving it before then.....
Click to expand...
Click to collapse
Dude, it may seem daunting, but this is one of the easiest phones to disassemble i have owned. grab some guitar pics, a magnet (for screws), and something like the top to the axon 7 box, and a relatively high quality phillips precision screw driver. the trickiest parts are the speaker grills, the fingerprint cable, and separating the back. the screws beneath the tape/speaker screen material i just didnt put back in my axon phone that has been taken apart. if ya have warranty, ya may as well send it in. i presently have not one but two boards that are without an IMEI. i keep my second axon in an easy to disassemble state as i didnt put the screws that are under the adhesive and speaker grills. i can board swap it in about two minutes now as ive done it like 20 times. it really isnt bad man. watch jerryrigeverything's video and its a piece of cake.
however, if you want to use warranty and not have to pay ($79) to ZTE to use Passport warranty, dont take it apart. if ya take it apart and fail, worst case scenario, ZTE will charge ya $80.
Square Warranty i know nothing about.
critical step on drain/trickle charge/edl is to just let it charge by itself on the oem usb cable to the computer until you get the 'plug in....' screen. just going over it in my mind trying to be certain i mentioned everything i did. in both instances, i was on stock.

AnonVendetta said:
@try5890: I still have the standard warranty, as well as SquareTrade insurance. But if there is a way out of this that doesnt involve hardware disassembly (which might make things worse), then I'd rather go that route instead. It's Sunday anyway, so I'll have to wait til tomorrow to call either ZTE or SquareTrade. If there is a chance of resolving it before then.....
Click to expand...
Click to collapse
No need to open your device, just follow this guide.

Anyway to retrieve data from a *dead* LeEco Le Pro3 (x727)

I am unable to boot up the device. I tried all (power + Vol Up) key combos, not working. Is there anyway to pull data out from the device?

easyxpress said:
I am unable to boot up the device. I tried all (power + Vol Up) key combos, not working. Is there anyway to pull data out from the device?
Click to expand...
Click to collapse
No fastboot or custom recovery ?
Then no theirs nothing really to do
Maybe a battery replacement would boot it up
Sent from my ONEPLUS A6010 using Tapatalk

No fastboot or custom recovery. I'm wondering if the *storage* can be pulled out like a hard drive?

easyxpress said:
No fastboot or custom recovery. I'm wondering if the *storage* can be pulled out like a hard drive?
Click to expand...
Click to collapse
Nope it's just a chip on a circuit board
Sent from my ONEPLUS A6010 using Tapatalk

easyxpress said:
I am unable to boot up the device. I tried all (power + Vol Up) key combos, not working. Is there anyway to pull data out from the device?
Click to expand...
Click to collapse
Not enough information. What did you do prior to your phone failing to boot? Was there a software mod you installed? What were the symptoms the phone showed the last time it was on? Any problems before it failed to boot like an old battery, misbehaving ROM, poor charging?
Basically, you need to identify (help us identify) the cause of your phone not booting. We cannot find the solution to a problem we don't know the cause of. The problem must first be defined and then we work from there.
All the best.

twistyplain said:
Not enough information. What did you do prior to your phone failing to boot? Was there a software mod you installed? What were the symptoms the phone showed the last time it was on? Any problems before it failed to boot like an old battery, misbehaving ROM, poor charging?
Basically, you need to identify (help us identify) the cause of your phone not booting. We cannot find the solution to a problem we don't know the cause of. The problem must first be defined and then we work from there.
All the best.
Click to expand...
Click to collapse
Prior to the phone failing to boot, the phone kept crashing. I saw the screen turning into *mess* and then the phone shut off by itself. Initially, I was able to boot up the phone after the crash, however the screen would get mess up and shut off again after a few minutes. Eventually, It got harder and harder to turn on the phone until it finally failed to boot (die). At this point, the phone seems dead. When I plug in the charger, there is no response of any kind, just black screen.
At one time, when the phone was on its last legs, I was able to boot into the Recovery mode, the phone seems to stay in that mode without the crash. Unfortunately, I didn't stay long enough in the Recovery mode to confirm this.
The phone was running on Lineage of Android 8. I have been using the phone for two years, the battery is surely weakened but can still last an hour or two for continual Youtube watching. I didn't do any software update after the Lineage Android 8's last nightly build.
Hope you can help and give some pointers. Thanks.
-- Joseph

easyxpress said:
Prior to the phone failing to boot, the phone kept crashing. I saw the screen turning into *mess* and then the phone shut off by itself. Initially, I was able to boot up the phone after the crash, however the screen would get mess up and shut off again after a few minutes. Eventually, It got harder and harder to turn on the phone until it finally failed to boot (die). At this point, the phone seems dead. When I plug in the charger, there is no response of any kind, just black screen.
At one time, when the phone was on its last legs, I was able to boot into the Recovery mode, the phone seems to stay in that mode without the crash. Unfortunately, I didn't stay long enough in the Recovery mode to confirm this.
The phone was running on Lineage of Android 8. I have been using the phone for two years, the battery is surely weakened but can still last an hour or two for continual Youtube watching. I didn't do any software update after the Lineage Android 8's last nightly build.
Hope you can help and give some pointers. Thanks.
-- Joseph
Click to expand...
Click to collapse
This appears to be hardware failure. The SoC is most probably dead. You should have recovered your data when it was still able to boot. Right now I think it's too late.

twistyplain said:
This appears to be hardware failure. The SoC is most probably dead. You should have recovered your data when it was still able to boot. Right now I think it's too late.
Click to expand...
Click to collapse
I just plugged in the phone. Miraculously, after few minutes, it did come up with the boot screen (with some messy lines), see the attached picture. However, It didn't go beyond the boot screen and recycle again for 2 or 3 times and then no more. I was able to duplicate this recycling situation several times after plugging it to the charger. Also, I was able to push it into the Recovery mode, but it only stay at the boot screen (with lines) and shut off again after few seconds.
What do the messy lines on the boot screen suggest? Is it the battery totally dead? Or, is the charging system faulty that somehow it doesn't have any enough juice to push thru beyond the boot screen and hence shut off?
-- Joseph

easyxpress said:
I just plugged in the phone. Miraculously, after few minutes, it did come up with the boot screen (with some messy lines), see the attached picture. However, It didn't go beyond the boot screen and recycle again for 2 or 3 times and then no more. I was able to duplicate this recycling situation several times after plugging it to the charger. Also, I was able to push it into the Recovery mode, but it only stay at the boot screen (with lines) and shut off again after few seconds.
What do the messy lines on the boot screen suggest? Is it the battery totally dead? Or, is the charging system faulty that somehow it doesn't have any enough juice to push thru beyond the boot screen and hence shut off?
-- Joseph
Click to expand...
Click to collapse
what happened to TWRP ? thats stock recovery
will it enter fastboot mode ? if you can get into TWRP their is a chance of off loading your userdata to a PC

easyxpress said:
I just plugged in the phone. Miraculously, after few minutes, it did come up with the boot screen (with some messy lines), see the attached picture. However, It didn't go beyond the boot screen and recycle again for 2 or 3 times and then no more. I was able to duplicate this recycling situation several times after plugging it to the charger. Also, I was able to push it into the Recovery mode, but it only stay at the boot screen (with lines) and shut off again after few seconds.
What do the messy lines on the boot screen suggest? Is it the battery totally dead? Or, is the charging system faulty that somehow it doesn't have any enough juice to push thru beyond the boot screen and hence shut off?
-- Joseph
Click to expand...
Click to collapse
Yup...This phone is dead. I have seen a similar le pro 3 posted here on XDA with the same streaks along the display. It's definitely a hard brick. No way to get around it that I know of. I'd like to rope @tsongming in on this. He has seen a few dead pro 3's so this is within his expertise.
Sent from my LeMobile Le X526 using XDA Labs

twistyplain said:
Yup...This phone is dead. I have seen a similar le pro 3 posted here on XDA with the same streaks along the display. It's definitely a hard brick. No way to get around it that I know of. I'd like to rope @tsongming in on this. He has seen a few dead pro 3's so this is within his expertise.
Click to expand...
Click to collapse
Sorry bad news.
As twistyplain said, your phone is absolutely fried, and there is no solution.
It's definitely no brick, that is a hardware issue... Most likely shorted solder connections. The same thing happened to two of our X727s, we have one left that still works.
I highly recommend buying a seemingly unbrickable Xiaomi phone. Their budget models are awesome and of course their flagships are awesome. Everyone in my family has Migrated to Xiaomi . I currently have Android 10 working flawlessly.

Thanks for the info. I made a mistake of not backing up the photos from the phone. I'm still hoping for a slim chance and searching that some of the repair shops (in China?) are somehow able to boot up the phone and retrieve the photos for me. Meanwhile, I'll check into Xiaomi.
-- Joseph

easyxpress said:
Thanks for the info. I made a mistake of not backing up the photos from the phone. I'm still hoping for a slim chance and searching that some of the repair shops (in China?) are somehow able to boot up the phone and retrieve the photos for me. Meanwhile, I'll check into Xiaomi.
-- Joseph
Click to expand...
Click to collapse
If you are in China and located in a large city or tech industrial area you should have plenty of shops that repair at the component level.
Your phone could very likely be repaired by a shop that has a hot air rework soldering station with an electron microscope.
We used to have these types of places in the US but they have all gone out business, replaced by board swappers, who charge a lot. I would suspect that you could get it repaired in China for 100 yuan or less.
I worked in Beijing for 3 months, about 18 years ago and these types of places were everywhere.