Database Develop

Soft Brick or Hard Brick?

{
"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"
}
I believe that my device might be 'hard bricked' not 'soft bricked'
Recap: Had to go back to 2.1 via Odin, tried to install 2.3.3 via Odin 1.8 and it failed and now my screen looks like the attached image. Since I can't find a way to get into download mode and the Heimdall One-Click Unbrick failed, I think it might be a 'hard brick.' I have a dongle jib on the way, that might do the trick.
Here's the long story: I tried moving from Serendipity 7 to Cognition 5 last night. I followed the directions here; since both ROMS are 2.3.3, I skipped Step 1, which was to get the phone to Gingerbread. I copied the kernel and cognition zip files to the phone and then rebooted into CWM Recovery Mode. After installing the kernel, I used ADB to get back into CWM Recovery Mode, but unfortunately, the enter key (ie the power button) did not work, so I couldn't install the full ROM.
I then thought that it must have been because I didn't flash to gingerbread the way that was described in Step 1, so I followed those directions [URL="http://forum.xda-developers.com/showthread.php?t=1127249]here[/URL], flashed ZImage-root.tar through Odin, got the fugu fish, somehow couldn't get past this point (I cannot remember why ). I ended up using I897UCJF6-final-OCD-REV0.exe and reinstalling Eclair via Odin.
This worked great, but I had the stock phone. So I rooted the phone via the One-Click Root program and tried to install the zImage-root.tar, which FAILED. Since the screen when black on my phone, I pulled the battery and when I plugged it back in, this is the image that came up.
I have a Dongle Jig on the way to get the phone into Download mode, but the Heimdall One-Click Unbrick failed, so I'm worried that this might be a hard brick.
My phone is under "warranty" until November, but I doubt that AT&T will take the phone back with the attached image showing (it kind of voids the warranty, right?).
I want to thank everyone on xda-developers for so much help...even the people who chew me out.

It is not a hard brick if you are seeing the screen as you posted above

oops double post.. sorry

Thanks for the quick "double post." That's somewhat of a relief, as I read on the UnBrick Tool forum the following:
Soft bricks:
Flash improper firmware which the system recognizes as improper
Prematurely terminate transfer
Flash with a bad cable
Hard Bricks:
Flash improper bootloaders
Flash mismatched versions of proper bootloaders
Flash bootloaders with a bad cable
I don't know if what I flashed via Odin was a bootloader, it was this "Fugu" Kernel.

herschen said:
Thanks for the quick "double post." That's somewhat of a relief, as I read on the UnBrick Tool forum the following:
Soft bricks:
Flash improper firmware which the system recognizes as improper
Prematurely terminate transfer
Flash with a bad cable
Hard Bricks:
Flash improper bootloaders
Flash mismatched versions of proper bootloaders
Flash bootloaders with a bad cable
I don't know if what I flashed via Odin was a bootloader, it was this "Fugu" Kernel.
Click to expand...
Click to collapse
Its a kernel. Not bootloader. You are not hard bricked, and I have presonally used the phone--!--pc screen as download screen

[Q] Atrix HD Corrupted Data partition

I'm a newb..
Atrix HD with unlocked bootloader and rooted. Installed cwm recovery, flashed to the latest nightly cm 11 for atrix hd, rebooted and stuck at cyanogenmod loading screen (head with the spinning circle around it). left it that way over night with no change still stuck on bott.
I've spent several hours following several guides with no success
I think the problem started whn I did a factory reset and clear cache in cwm before I flashed cm 11. it gave an error on data or something.
fastforward several hours later I now have philz touch 6 recovery which I read on this guide http://forum.xda-developers.com/showthread.php?t=2577447 you could use to fix the corrupted data partition. problem is when booted to philz recovery the driver for phone is not installed correctly.
{
"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 phone is recognized fine in fastboot mode however.
Is there a way to fix the corrupted data partition using fastboot?
I've already tried fastboot -w and reflashing but that did not work.
I have the latest motorola drivers and latest sdk with google usb installed etc.
Unfortunately I was stupid and didn't make a nandroid backup so I hope there is another way to get this phone working.
thanks

Solved
After 2 days of monkeying around I finally got it fixed.
I never could get the phone recognized in recovery mode (philz mod) and using ADB as suggested by the guide I linked.
Finally what worked is I downloaded the stock rom zip, extracted it, edited the xml file in MS word deleting the 2 lines with "getvar" in them, booted the phone into fastboot mode, connected the phone to my PC and made sure it was recognized in device manager, loaded the xml from the stock rom into RSD Lite and flashed back to stock, rebooted, and all was working fine.
I know there's a million and 1 guides that say to do what I just described and believe me I tried the exact things I posted above for the better part of 2 days and rsd lite would always fail with some kind of error. Finally I rebooted my PC, downloaded the stock rom again, edited the xml, and tried one last time and it finally worked...I don't know what made the difference.
Now if I could just find a trick around this darn subsidy (hard) lock this Atrix HD would be back in business.

Sony Xperia Z3C without /system, /boot partition, doesn't boot even in recovery mod!!

Please help, I Need your help!!!!!!!
I made a sh*t thing, I went to recovery mod (phil'z touch), I deleted /system, /boot and then I clicked on reboot recovery and guess what, the phone doesn't let go either in recovery nor bootloader mode!!! I don't know what to do, the phone is not either recognized by the pc!!!!!!!
Please I really don't know how to proceed further!!!

put it in flash mode and flash a new ftf with flashtool...

daha2002 said:
put it in flash mode and flash a new ftf with flashtool...
Click to expand...
Click to collapse
how do I put it in flash mode!? sorry but I'm really confused because it boots, but it stays stuck on "sony" screen!!!

With phone off, press volume down and connect usb cable connected to pc (drivers should be previously installed), when the led change color, release volume button. Done, you're in flash mode, now just flash tft (do it fast before your battery runs out)

daha2002 said:
With phone off, press volume down and connect usb cable connected to pc (drivers should be previously installed), when the led change color, release volume button. Done, you're in flash mode, now just flash tft (do it fast before your battery runs out)
Click to expand...
Click to collapse
Hi, I succedeed in connecting the device in fastboot mode but flashtool has opened a popup that never dismiss... I attach a screenshot, and in the meanwhile I'm downloading latest version of flashtool program..
Spoiler
{
"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"
}

Your phone has fastboot and FLASH modes.
Put it in FLASH mode (volume down) and the hit the lighting icon and flash a new firmware.
Don't worry, Sony phones are (almost) unbrickeable, just don't run out of battery.

daha2002 said:
Your phone has fastboot and FLASH modes.
Put it in FLASH mode (volume down) and the hit the lighting icon and flash a new firmware.
Don't worry, Sony phones are (almost) unbrickeable, just don't run out of battery.
Click to expand...
Click to collapse
So, first attempt was unsuccessfully because I tried to NOT wipe the user's /data and I got a bootloop in the end.. I'm newly trying to flash the firmware with all the wipes ticked... I'll let you know, thanks in advance for your support
edit: the phone booted up this time, and now it works!!

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.