Database Develop

Xperia Z unresponsive - possible bricked

ok so I got my phone (xperia z)
rooted with easy rooting toolkit
Installed cwm recovery
Stupidly tried to flash a gnexus rom
did nothing still on stock
So i found the yuga cyanogen 10.1
tried to flash that
Wiped Data, Cache
Loaded
But it did nothing, and then when I tried to turn it on it vibrated but was otherwise unresponsive
When plugged into mains, flashing orange LED
When USBed, orange light, quickly changes to green light then off
ABSOLUTELY ZERO RESPONSE
tried everything suggested on here, I really have, wouldnt be wasting your time otherwise, but i'm really scared
On PC companion it just connects, disconnects, connects, disconnects continually with no device type recognition just 'phone connected'
PLEASE HELP
and also my mother is going to absolutely destroy me if i dont fix this. I was bugging her for ages for this phone, and now ive broken it :'(

If you keep the volume UP button pressed and connect the USB. (Do not press power)
Does it enter fastboot mode?
Kind regards, Stefan.

Thaevil0ne said:
If you keep the volume UP button pressed and connect the USB. (Do not press power)
Does it enter fastboot mode?
Kind regards, Stefan.
Click to expand...
Click to collapse
yes i love you
but um now what
thanks

Download and flash a generic FTF file from your region, using flashtool.
Check the topic: [NOOBS GUIDE] Create your own stock firmware FTF & Flashtool flashing guide[+ pics]
http://forum.xda-developers.com/showthread.php?t=2188129
Check the part: Stage 4 = Flashing FTF.
That is after downloading a generic FTF file from your region, and installing the correct fastboot drivers.
This post belongs in Xperia Z General instead of Xperia Z Android Development, and should be stickied.
Very useful information by xl VipeR lx.
Kind regards, Stefan.

AW: Xperia Z unresponsive - possible bricked
Overkill. Either run a "repair" operation on PC Companion or reflash your phone with SUS, Sony Update Service. No point in flashing a FTF which doesn't originally belong to the phone.

@OP I'm guessing you haven't unlocked the bootloader which is probably why flashing CM bricked your phone. Relax... Xperias are very hard to brick, as schaggo said just repair with SUS and you should be fine. In future if you have any doubts just drop me a PM

Sounds to me like the reason you couldn't get CM to work is because you didn't actually flash the kernel like you are supposed to the first time. I assume this because all you say is you got cm10 and flashed it and it didn't work.
You are supposed to (for the first time flashing CM10):
1) download the .zip
2) extract boot.img from the zip
3) flash that boot.img in fastboot (put it in your fastboot folder, open cmd and use the command "fastboot flash boot boot.img" then "fastboot reboot"
4) boot into recovery
5) now flash the .zip of cm10 as per normal.
6) enjoy the cyan goodness
My issue I am facing now is returning to my original stock firmware. Restoring the backup doesn't work, nor does getting the boot.img out of the backup folder and fastboot flash that. Well it all flashes and restore, but it won't boot. It's easy enough to get back to cm from there though:silly:

myxperiazisbricked said:
ok so I tried to flash a gnexus rom :'(
Click to expand...
Click to collapse
{
"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"
}

Unable to flash stock ROMs

The problem I am having is that my phone is bricked. It won't boot to any ROM and it's not cooperating with RSD 5.6 Lite.
I was running CM11, the 12/20 nightly with PA-GApps (Full Modular pa_gapps-modular-full-4.4.2-20131215-signed.zip), and last night I decided to download the 12/21 nightly and update. I was using the CM Updater in the phone settings and I downloaded it fine (I assume), went to flash, and it only gets past the red M and nothing else.
I have been trying numerous sites/methods to reset it to factory settings and none of it is working. I've tried all the zips at the sbf.droid-developers and I keep getting the same error:
{
"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"
}
When I go into AP Fastboot, I see the following:
AP Flashboot Flash Mode (S)
0A.77
eMMC Info: Size 16G
To return to normal mode - first press power key to power down
Device is LOCKED. Status Code: 0
Battery OK
OK to Program
Transfer Mode:
USB Connected
I originally rooted it with the CM guides and used SafeStrap Recovery as the recovery software.
Like I said, its stuck and I cannot get it to work with my RSD Lite.
Guides used:
http://forums.androidcentral.com/motorola-droid-4/170460-how-restore-your-motorola-droid-4-stock-windows-only.html
http://www.droidforums.net/forum/android-news/211167-video-how-unbrick-droid-4-via-fastboot.html

PJroast said:
The problem I am having is that my phone is bricked. It won't boot to any ROM and it's not cooperating with RSD 5.6 Lite.
I was running CM11, the 12/20 nightly with PA-GApps (Full Modular pa_gapps-modular-full-4.4.2-20131215-signed.zip), and last night I decided to download the 12/21 nightly and update. I was using the CM Updater in the phone settings and I downloaded it fine (I assume), went to flash, and it only gets past the red M and nothing else.
I have been trying numerous sites/methods to reset it to factory settings and none of it is working. I've tried all the zips at the sbf.droid-developers and I keep getting the same error:
When I go into AP Fastboot, I see the following:
AP Flashboot Flash Mode (S)
0A.77
eMMC Info: Size 16G
To return to normal mode - first press power key to power down
Device is LOCKED. Status Code: 0
Battery OK
OK to Program
Transfer Mode:
USB Connected
I originally rooted it with the CM guides and used SafeStrap Recovery as the recovery software.
Like I said, its stuck and I cannot get it to work with my RSD Lite.
Guides used:
http://forums.androidcentral.com/motorola-droid-4/170460-how-restore-your-motorola-droid-4-stock-windows-only.html
http://www.droidforums.net/forum/android-news/211167-video-how-unbrick-droid-4-via-fastboot.html
Click to expand...
Click to collapse
If you can get into AP fastboot, you should be able to use the droid 4 utility in the development section to flash everything back to original.
http://forum.xda-developers.com/showthread.php?t=2207384

RoninRyan said:
If you can get into AP fastboot, you should be able to use the droid 4 utility in the development section to flash everything back to original.
http://forum.xda-developers.com/showthread.php?t=2207384
Click to expand...
Click to collapse
Thank you, will try once the download is all done!

PJroast said:
Thank you, will try once the download is all done!
Click to expand...
Click to collapse
Also, the guide you were using was for android 2.3. I don't think you can downgrade to eclair from jelly bean or kitkat. the utility will install 4.1. i'd recommend selecting the full wipe option.

Need urgent help! Didn't OEM unlock in Dev and now stuck!!

Ok, so got my brand new shiny Oneplus 3T yesterday after waiting aged for it to come in.
Using it for a bit, noticed an OTA update to nougat came out (about 900mb) which downloaded in the background.
Triggered the upgrade, now the phone won't boot. I'm also having trouble installing any recovery roms on to it, because I was never intending to root the phone in the first place, and as a result didn't unlock the bootloader using the phone interface when it was on.
So now, it appears I'm stuck! My phone won't accept any side-load roms, (fails), full roms don't read (cannot open file) and fastboot won't unlock the bootloader (Not allowed)
....um.. not having a clue what I'm doing here....help???
{
"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"
}

try going to stock oxygen recovery. wipe data and cache there. see if it boots.
try the unbricking thread too.
if all else fail, call OP customer service.
let us know what happens.

To fix it - see "[UNBRICK] Unbrick Tutorial For The OnePlus 3T!!!!!!!! by Harris K". You have to download his two files onto a laptop or desktop computer and install a qualcomm driver (one of the files). The qualcomm driver will open a serial port into the phone's chipset. The other file will download a stock system, recovery, and fastboot to your phone through the qualcomm serial port. Harris is a genius, buy him a beer. This will fix the following problems.
1) It sounds like the OTA patch screwed up your /system where it doesn't even try to boot. You can still boot into /recovery and /fastboot but just not into /system. Since the phone is still "locked" (flashing prohibited) you cannot flash anything to fix it.
2) dm-verity does not allow any changes to /system. dm-verity checks a hash of hashes of /system. If the hash check fails when you boot /system, dm-verity will "brick" your phone (by design) leaving you with a black screen.
The OTA updates the system and downloads a hash key corresponding to that version. After the OTA, everyone has to end up with exactly the same system in order to pass the dm-verity check.
When you enable flashing (called "unlocking the bootloader") dm-verity will wipe /data to prevent someone from flashing a non-stock recovery to access your data.

infamousvincci said:
try going to stock oxygen recovery. wipe data and cache there. see if it boots.
try the unbricking thread too.
if all else fail, call OP customer service.
let us know what happens.
Click to expand...
Click to collapse
Ok, so went to the unbricking thread. The tool worked! I'm back up and running

bunburyist said:
Ok, so went to the unbricking thread. The tool worked! I'm back up and running
Click to expand...
Click to collapse
I deserve a thank you button haha

Bricked ME375CL Please Help

I managed to brick my ME375CL in my attempt to root it, it only shows the "Intel Inside" logo when I boot it up.
After much driver install/reinstall and cursing at my computer, I managed to get it to be recognized in Intel Phone Flash Tool.
I've read the instructions on doing custom flashes in blank phone mode for other tablets, but for the life of me, I can't figure out which file is supposed to go in which field.
I would greatly appreciate any insight into this that anyone can provide.
I already have the firmware downloaded.
This is where I am at:
{
"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"
}
This is the list of files I have to work with from the firmware download:
Thanks in advance!!!

The link below may be your best bet to reload the system and root it. I would recommend reading the entire thread first.
https://forum.xda-developers.com/memo-pad-7/help/official-rom-att-asus-memo-pad-7-lte-t3554127

johnkirchner said:
The link below may be your best bet to reload the system and root it. I would recommend reading the entire thread first.
https://forum.xda-developers.com/memo-pad-7/help/official-rom-att-asus-memo-pad-7-lte-t3554127
Click to expand...
Click to collapse
Thanks for the reply. I've already read through that post and attempted the steps within. The problem is that I followed those steps and they failed, now it can only be recognized as an Intel SoC by my computer, so ADB, fastboot commands and Asus Flash Tool will not work.
The only programs I've gotten to recognize the tablet is Intel's Phone Flash Tool and Flash Tool Lite.

If you haven't yet, try using the boot, system and recovery images from the firmware you downloaded in the android section of the flash tool and see what happens.

johnkirchner said:
If you haven't yet, try using the boot, system and recovery images from the firmware you downloaded in the android section of the flash tool and see what happens.
Click to expand...
Click to collapse
I've tried all kinds of combinations in this software, but it always fails at either the IFWI step or gives me this error:
10/08/17 14:03:09.468 INFO : Port 5/1/1: Rebooting in Provisonning OS (current state = UNKNOWN_STATUS)
10/08/17 14:03:09.468 INFO : Port 5/1/1: Cannot Reboot android device, status is UNKNOWN_STATUS
Based on the reading I've done in other threads, the only way to correct this is through a firmware flash in blankphone mode, but it won't accept any of the IFWI files that I have found for this tablet.
I appreciate you trying to help, but I can't do what you are suggesting when it's not even being detected as an Android device. Fastboot commands will not work because there's nothing on the tablet for ADB to make a connection to.
Here's what happens when I try:
Here is what my tablet is doing:
When it's detected by Intel Phone Flash Tool, it usually has a blank screen. Otherwise, it just shows that Intel logo for about 15 seconds, reboots and then does it again, endlessly.

Oh, I forgot to mention that Asus support was kind enough to offer a repair or replacement for $155, since it's out of warranty. I'm hoping for a much cheaper option.

I have never seen the intel logo on mine? Have you tried booting the tablet in to fastboot mode by shutting it down and then turn it on by holding the volume up button and the power button? If you can get to fastboot mode, you should be able to use adb commands. Unfortunately, i am not familiar with the flash software you are using.

[HARD Hard Brick] Literally nothing's working... Please help.

I need help. ​
The problem?​My phone is bricked AF.
Where it started:​So, a few days ago I was flashing custom ROMS on my Redmi 9C, at this point everything was good, although I did brick the phone twice, I was able to get it back up and running again using MTK Bypass and SP Flash tool.
You see, 2 days ago I stupidly it was a good idea to flash a custom ROM (Arrow OS) on top of another one (DotOS) ~I'm not a noob, I KNEW this probably wasn't going to work~. I thought it would work since it's still using the same base but shortly after flashing when I restarted my phone there was nothing, no boot logo, no sound, no vibration, nothing.
I couldn't boot to fastboot or anything, it wouldn't respond to ANY input.
At this point I already knew well how to fix the issue but this time it didn't work at all.
The first attempt kinda worked, I was able to bypass auth and flash but after like 2 seconds the flash tool stopped, and I got a STATUS_EXT_RAM_EXCEPTION error and after that I tried to reflash. It did get detected by the bypass tool a few times but after that every time I plug my phone into my pc, I get this:
{
"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"
}
and I see this in device manager:
Libusb won't even detect it.
I tried driver after driver, I switched the cable, I tried a different computer, I waited a day, I read thread after thread, installed python, tried tool after tool, but to no avail.
I tried all sorts of button combinations but the only one that does anything is vol+ and pwr but that just makes it disconnect and reconnect to my pc with the same results.
I watched a bunch of videos about it and tried every method but still, no luck. I am confused where they say remove the battery because some do and some don't, but I can't really do that in my current position anyway...
I know there are MANY similar threads on this, but I haven't been able to find anything to help me in this situation.
I've tried all sorts of solutions but now I just don't know any more.
Please. Help. Would really appreciate it.

I had a similar brick yesterday, when I tried to use mtkclient but it only got halfway. As far as I understand, the system was actually on, but it got stuck in a state where it wouldn't respond to anything.
What fixed it was power cycling the device by disassembling it, and disconnecting and reconnecting the battery (search for battery replacement videos). The idea is from this comment by bkerler, the author of mtkclient. I guess my warranty really is void now.
(Another thing I considered was power cycling it by waiting for the battery to run out, and then recharging it. But I've no idea if this might have got it into a state where it wouldn't even charge, so I didn't do it.) I'll avoid mtkclient from now on when possible, and prefer to use fastboot or a recovery for flashing.
I am a noob; no guarantee that I'm right about anything (other than that my phone works now), nor that your situation is identical to mine.

Here is solution if you are not noob,
Post in thread 'HARDBRICKED REDMI 9C ANGELICA NO BOOT NO RECOVERY NO FASTBOOT ONLY VIBRATES' https://forum.xda-developers.com/t/...-fastboot-only-vibrates.4494095/post-88308869