Hey guys,
So I properly powered down my phone and went to go into the bootloader by holding vol down + power button. As soon as it opened up the bootloader the phone turned off. I went to turn it on and it flashes the white sprint screen for less than 1 sec and turns off. When I plug it into a charger the light turns on for a few secs then goes away.
I have s-off + cwm.
I have read that if your battery dies in the bootloader after installing cwm your battery won't charge and the phone won't boot. I am not sure if this is the case but was hoping to get some input.
I am not sure what percentage my battery was at when this happened.
Thanks!
Go to bootloader (cwm) and reinstall your back up rom that outta do it. And after download the rom you currently have but replace your old one and flash it over usin cwm
Supa Dupa Troopah
My phone only stays on for 1 second tops. I cannot go to my bootloader. My computer sees the phone even when it won't turn on witch is weird. I also cannot communicate with the phone with adb / fastboot etc. The only thing I have not tried is hacking a usb cable to communicate. Any advice would be great. I will try a battery tomorrow.
ADB
Wow hey ok so I can see the phone in ADB after all... List of devices attached
HT167HX05101 recovery
Is there a way to flash the old recovery?
Or can someone point me to the RUU.exe? Not the ZIP
Thanks!
EDIT:
Well never mind... I had adb and booted into bootloader and flashed team win recovery from fastboot and it failed - sending 'recovery' (5016 KB)... OKAY
writing 'recovery'... FAILED (status read failed (Cannot send after transport endpoint shutdown))
Now the light stays on when I plug in but no longer flashes when I power button and no more adb. I'm screwed
Idk what your problem is since i do not have your phone in front of me, either you deleted an import file and are now screwed no offense and cant boot your phone my suggestion is to either call or take it to the store by gettin a new one. I would tell them your phone got hot all the sudden and just crashed that way its under warentee
Supa Dupa Troopah
can you use fastboot? Also, leave the phone alone and charge it, while off, for a bit. If you come back to a full charge phone and hold vol down and then power, it should boot into fastboot, try running a fastboot command from the PC. Also, you could download twrp 1.0.2 zip and put it on your SD card as PG86IMG.zip, same vol down/power and it *might* install the recovery from hboot. Don't give up yet. In theory if your charging light turns on, you're not bricked.
hopefully this works for me !!
Thanks
il Duce said:
can you use fastboot? Also, leave the phone alone and charge it, while off, for a bit. If you come back to a full charge phone and hold vol down and then power, it should boot into fastboot, try running a fastboot command from the PC. Also, you could download twrp 1.0.2 zip and put it on your SD card as PG86IMG.zip, same vol down/power and it *might* install the recovery from hboot. Don't give up yet. In theory if your charging light turns on, you're not bricked.
Click to expand...
Click to collapse
Thanks for the help.
I last time I had adb I got into the bootloader by using an adb command once in there I flashed teamwin rec. It failed during install and ever since I am locked out. I can't get any commands. I wonder if it damaged my boot loader. Ill keep trying otherwise I should be able to get it swapped since it does not boot at all
SpyFi said:
Thanks for the help.
I last time I had adb I got into the bootloader by using an adb command once in there I flashed teamwin rec. It failed during install and ever since I am locked out. I can't get any commands. I wonder if it damaged my boot loader. Ill keep trying otherwise I should be able to get it swapped since it does not boot at all
Click to expand...
Click to collapse
yeah if you can't get into the bootloader/adb/recovery/rom then sprint can't either
Sorry to be a bother.. but can someone check out my problem? I really need help. I know, i am such a troll coming to another post to look for help.
-Mike
Check out this threath i hope it helps..
http://androidforums.com/evo-3d-all-things-root/385959-error-16-sprint.html
Supa Dupa Troopah
I was switching from sinister's v6 rom to decks. I booted into twrp recovery and wiped cache, dalvik, factory reset, and system. Then I flashed decks zip and then gapps. I then used adb reboot-bootloader to get back to the bootloader. From there I used "fastboot flash boot deckboot.img" (I changed the boot.img name to deckboot.img).
this is the message I recieved:
c:\Android>fastboot flash boot deckboot.img
sending 'boot' (1976 KB)...
OKAY [ 0.370s]
writing 'boot'...
OKAY [ 0.690s]
finished. total time: 1.070s
then I tried to reboot through adb but got this
c:\Android>adb reboot
error: device not found
so used the phone keys to reboot the phone. Now my phone will not show anything but the very first splash screen, which I think means my phone is bricked (****). I had h-boot 1.19, firmware 2.13, htc unlocked, and had s-on. I plugged the device into my computer but when using the command "adb devices" nothing shows up. It was weird because my computer recognized the device as something and was looking for drivers or something like QHUSB-DLOAD but did so to no avail. Any advice?
Can you get to the bootloader by holding volume down + power (I think that's the right sequence, anyhow)?
Sent using my HTC EVO LTE and a magic wand
FinZ28 said:
Can you get to the bootloader by holding volume down + power (I think that's the right sequence, anyhow)?
Sent using my HTC EVO LTE and a magic wand
Click to expand...
Click to collapse
I would try that and if you are able to get to bootloader I would reflashed the bootimg without changing the name. Just leave it bootimg.
Sent from my EVO using Tapatalk 2
Okay so I tried doing that but no luck. The only screen I'm seeing is the white HTC screen that says the phone has been dev unlocked. It's weird that a few seconds after I let go of power and down I see the HTC splash screen and then it's back to black. At first I thought it was because I wasn't holding it long enough but after multiple tries it seems like the phone is waiting for me to let go of the buttons.
I got the advice to "Hold power and volume down for like 15 seconds. Take your finger off the power button for 2 or 3 seconds and repress it while holding volume down all the time" and I was able to get back to the bootloader. From there I went to recovery and redid wiped and flashed everything. It turned out I extracted the boot.img from deck's Evo 4G rom (dope!). Anyway everything is working fine for me now. Thanks for the help guys.
StrummingLevi said:
I got the advice to "Hold power and volume down for like 15 seconds. Take your finger off the power button for 2 or 3 seconds and repress it while holding volume down all the time" and I was able to get back to the bootloader. From there I went to recovery and redid wiped and flashed everything. It turned out I extracted the boot.img from deck's Evo 4G rom (dope!). Anyway everything is working fine for me now. Thanks for the help guys.
Click to expand...
Click to collapse
Good to hear.
Sent from my EVO using Tapatalk 2
Hi all,
after successfully unlocking the bootloader and flashing CyanogenMod 10.1.0 RC2 boot.img via fastboot from Linux, I couldn't manage to boot the tablet again.
I tried several things (Emma, Flashtool, etc.) in order to relock the bootloader and/or flash a stock ROM, but I only could put the device into fastboot mode.
Things are getting possibly worse now: the red notification light is still, I can't neither reboot (pressing Power+VolumeUp for 5 seconds) nor halt (Power+VolumeUp for 10 seconds)...
What a mess! Anyone can suggest me how to fix this situation, please?
Alberto
This is why u shouldn't mess with your tablet.just use it as it came, not worth the hassle
bibe74 said:
Hi all,
after successfully unlocking the bootloader and flashing CyanogenMod 10.1.0 RC2 boot.img via fastboot from Linux, I couldn't manage to boot the tablet again.
I tried several things (Emma, Flashtool, etc.) in order to relock the bootloader and/or flash a stock ROM, but I only could put the device into fastboot mode.
Things are getting possibly worse now: the red notification light is still, I can't neither reboot (pressing Power+VolumeUp for 5 seconds) nor halt (Power+VolumeUp for 10 seconds)...
What a mess! Anyone can suggest me how to fix this situation, please?
Alberto
Click to expand...
Click to collapse
ash6783 said:
This is why u shouldn't mess with your tablet.just use it as it came, not worth the hassle
Click to expand...
Click to collapse
This answer is about as helpful as a heart attack lol
I can assure you that even us dev's run into issues like this, I soft bricked my new tab 5 times today (still trying to figure out this recovery/no recovery thing sony is doing lol).
Aberto, I had/did the exact thing today, first off I'm guessing you have a wifi only like I do right? Those roms/boot imgs won;t work it seems, Im learning as fast as I can so I can get a port for Baked for this tab, I own the wifi only so its my first priority.
Here's what I did, took allot of patience, so be prepared to try a bunch of times!
1. Unplug the usb cable
2. hold both vol + and - (I know this is not documented but stick with me here), then press and hold the power button until the led flashed "white" "3 times" (u will see one white flash, then after about another 20 seconds a second set of white flashes will begin, it will blink 3 times)
3. Plug in the usb cable
4. Make sure you have emma/drivers setup, since this is a windows only (boo!) tool you should here the usb device plug notifiction that it detected the "S1 Service Sony Mobile Communications AB"
This only lasts about 1 minute before it will go back to red led, launch emma and restore a stock image from sony, after its done, unplug the device, and hold power, it should come back to life!
Thanks nycbjr, I tried this morning before getting to work and I could "unlock" the red notification light.
This evening I'll try to get further in the process of resuscitating my tablet.
Thanks for the tips!
Alberto
nycbjr said:
Alberto, I had/did the exact thing today, first off I'm guessing you have a wifi only like I do right? Those roms/boot imgs won;t work it seems, Im learning as fast as I can so I can get a port for Baked for this tab, I own the wifi only so its my first priority.
Click to expand...
Click to collapse
Yep, I have a SGP312 (wifi only, 32 GB)
nycbjr said:
This answer is about as helpful as a heart attack lol
I can assure you that even us dev's run into issues like this, I soft bricked my new tab 5 times today (still trying to figure out this recovery/no recovery thing sony is doing lol).
Aberto, I had/did the exact thing today, first off I'm guessing you have a wifi only like I do right? Those roms/boot imgs won;t work it seems, Im learning as fast as I can so I can get a port for Baked for this tab, I own the wifi only so its my first priority.
Here's what I did, took allot of patience, so be prepared to try a bunch of times!
1. Unplug the usb cable
2. hold both vol + and - (I know this is not documented but stick with me here), then press and hold the power button until the led flashed "white" "3 times" (u will see one white flash, then after about another 20 seconds a second set of white flashes will begin, it will blink 3 times)
3. Plug in the usb cable
4. Make sure you have emma/drivers setup, since this is a windows only (boo!) tool you should here the usb device plug notifiction that it detected the "S1 Service Sony Mobile Communications AB"
This only lasts about 1 minute before it will go back to red led, launch emma and restore a stock image from sony, after its done, unplug the device, and hold power, it should come back to life!
Click to expand...
Click to collapse
Thanks! I just saved my Tablet Z's life by your method!
It seems like no kernel I can flash now (SGP312 32GB WiFi) I flashed CWM-Based Recovery 6.0.3.2 twice, and m SGP312 died twice
yt92 said:
Thanks! I just saved my Tablet Z's life by your method!
It seems like no kernel I can flash now (SGP312 32GB WiFi) I flashed CWM-Based Recovery 6.0.3.2 twice, and m SGP312 died twice
Click to expand...
Click to collapse
you are welcome! Im working with doomlord on getting recovery working foir the sgp311/12..
btw baked blackbean 9 is booting on the z tab.. few days I'll release it
nycbjr said:
... after its done, unplug the device, and hold power, it should come back to life!
Click to expand...
Click to collapse
You saved my tablet's life too! I could manage to restore Sony's factory ROM, and finally I can use it!
Thanks again nycbjr!
hmz
Glad I found this topic, but so far I can't get it to work.
Situation is the same I guess, red light, tried to flash the wrong img to my wifi only modell.
When I press all 3 buttons at the same time, the first white blink shows up after about 5secs, then there is a 3 blink sequence also in white after another 3-5secs. If I plugin the usb cable still holding down the buttons, no usb device is recognized, nothing happens..
If I keep holding down the buttons a 3 white blink sequence shows up again, followed by a white/red quick blink, then after 5 secs another 3 white blink sequence starts again, followed by a white7red combo et cetera. As soon as I release the buttons it turns to a constant red again.
Any more ideas or should I just keep trying?
defy0815 said:
Glad I found this topic, but so far I can't get it to work.
Situation is the same I guess, red light, tried to flash the wrong img to my wifi only modell.
When I press all 3 buttons at the same time, the first white blink shows up after about 5secs, then there is a 3 blink sequence also in white after another 3-5secs. If I plugin the usb cable still holding down the buttons, no usb device is recognized, nothing happens..
If I keep holding down the buttons a 3 white blink sequence shows up again, followed by a white/red quick blink, then after 5 secs another 3 white blink sequence starts again, followed by a white7red combo et cetera. As soon as I release the buttons it turns to a constant red again.
Any more ideas or should I just keep trying?
Click to expand...
Click to collapse
Normally it is the follows:
Hold Vol+ and Power.
1x blink = Reboot (doesn't help you in this case)
after holding it longer
3x blink = Shut down (device is switched off and in a defined state)
Drink a beer
open flash-tool and prepare the firmware to flash
Hold Vol- and plug the device to the computer
If the led turns green the firmware will flash
If not check what the flash-tool says in which state the device is
If the led turns red maybe the battery is to empty?!?
I don't know about the red led, but thanks for the hint.
Pressing only vol down when pluggin in the usb seems to have changed something. I tried power+vol down before but that didn't help.
Now flashtool seems to be working, it says it's flashing, but it seems to take ages. I'll let it keep on working for now (running since 10mins, but after "checking header" and "flashing data" there is no progress anymore...yet). I'll report back
I canceled it after 2h with no progress...damnit.
Does anyone have another suggestion?
defy0815 said:
I canceled it after 2h with no progress...damnit.
Does anyone have another suggestion?
Click to expand...
Click to collapse
With Flashtool it didn't work, but with EMMA it works! YES!
Thanks!
This also saved my tablet's life.
defy0815 said:
I canceled it after 2h with no progress...damnit.
Does anyone have another suggestion?
Click to expand...
Click to collapse
Hi, try flashing again with Emma but use a different USB cable i had a similar issue where the flash started then seemed to freeze so tried a different cable and it worked.
Edit: lol seems i missed your post where you tried again with Emma -_- glad you got it sorted though
UserX10 said:
Normally it is the follows:
Hold Vol+ and Power.
1x blink = Reboot (doesn't help you in this case)
after holding it longer
3x blink = Shut down (device is switched off and in a defined state)
Drink a beer
open flash-tool and prepare the firmware to flash
Hold Vol- and plug the device to the computer
If the led turns green the firmware will flash
If not check what the flash-tool says in which state the device is
If the led turns red maybe the battery is to empty?!?
Click to expand...
Click to collapse
you need a big kiss from someone thanks a million :good::good::good::good::good::good::good:
This worked for me, albeit after trying the first part (holding VOL+, VOL- & POWER) intermittently for 2 days.
What seemed to get the table/battery to reset was I connected the USB cable to the charger on a wall outlet on the second day. When I plugged in the cable the Red LED came on and stayed there. After an hour it was still red so I removed the cable and tried 1) pressing VOL+ & POWER (about 3 seconds), then 2) VOL- & POWER (about 3 seconds) and after a while the red LED went off.
Then I tried the VOL+, VOL- & POWER and it started blinking white once, then white again after a while, and I was able to continue with the instructions.
Thanks!
Hi there,
I just started to hassle with my Z2, apparently it won the first round...
It's not possible to switch on. When a charger (or PC) is connected, its status LED starts flashing red.
This does not stop until unplugged. I am using the official charger with my ASUS usb cable.
I already left it in that state for an hour. It does not blink when connected via magnetic charger.
When holding power, the phone vibrates weakly, repeating when holding power for longer.
The HW reset button seems to have no effect.
When holding VolUp+Power (with USB connected) it lights blue and vibrates thrice.
VolDown+Power makes the LED stay on red a bit longer.
No ADB/Fastboot, but Sony PCC recognizes it, but tells me it's no a SE phone.
When last booted TWRP showed a battery percentage of ~60%.
At that boot I switched from stock FW to CarbonROM, but did not wipe system.
EDIT: fastboot seems almost fully working, but i can't flash:
sending 'boot' (11932 KB)...
OKAY [ 0.384s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.394s
Click to expand...
Click to collapse
Any ideas how to revive it? Does magnetic charging work when the phone is switched off?
Yes,if fastboot is working then definitely flashmode would also be working volume down+usb connect to pc.If green light is there ,just flash stock ftf
Sent from my D6502 using XDA Premium 4 mobile app
The OP now solved his problem by following the instructions
Thread closed
little backstory/info: Had my DNA rooted for years now. S-off, unlocked...all that good stuff.
This morning I wake up and go to turn on the screen (it was asleep, not powered off). well the screen didnt light up but my notification light was blinking.
Tried a few taps of the power button as this has happened before (the phone is getting pretty old now). No avail, so i hold the power button until the touch keys start to blink and reboot the phone.
Upon turning back on it shows the screen that normally shows the htc logo (mine is modded) and then it should go to the boot image (in my case, a custom .gif that i flashed over long ago). well, before it gets to the boot image it simply blacks out and reboots.
At one point in time i could boot to the hboot screen and select 'recovery'... it would say 'entering recovery...' in pink at the top of the screen ... and then reboot. So, no getting into the recovery
Now, hitting 'recovery' in hboot sends me directly to the fastboot menu
So, here's what I'm able to do. I can boot to fastboot and issue fastboot commands using minimal_adb.
I've tried
Code:
fastboot flash recovery recovery.img
which returns
Code:
writing 'recovery'
FAILED (Remote: image update error)
Yes, the recovery .img is in the same folder with adb.
Yes, the name of the .img was typed in correctly.
Yes, I tried other recovery .img.
At this point I don't mind having to wipe everything, the thing is, I only have fastboot to work with.
kind of same here
mine is just stuck in the bootloader and nothing works like holding the power and volume buttons and if i plug in the charger it keep restarting over and over again on the htc logo part.
zaarwxd said:
mine is just stuck in the bootloader and nothing works like holding the power and volume buttons and if i plug in the charger it keep restarting over and over again on the htc logo part.
Click to expand...
Click to collapse
Mine has gotten to the point now where it doesn't boot loop sometimes, but it still doesn't load past the initial boot up screen (normally white screen with HTC logo)
I've since gone and gotten a new phone (I was due to upgrade anyway) but still wouldn't mind being able to recover the DNA and the media on it if i can.
were you using a custom recovery?
this was addressed to pshock ^
---------- Post added at 10:46 PM ---------- Previous post was at 10:45 PM ----------
zaarwxd said:
mine is just stuck in the bootloader and nothing works like holding the power and volume buttons and if i plug in the charger it keep restarting over and over again on the htc logo part.
Click to expand...
Click to collapse
if you go into bootloader, does it still keep rebooting?
Mine was all stock.....same issue.
I brought the phone back to life but theres no recovery