[UPDATED]Recover your dead X8/W8. - XPERIA X8 General

Hello there fellow X8/W8 users!
This post is intended to point your attention to the simple fact that there's a hardware imposed danger to hard brick your Xperia X8 and W8, applies to E15i/a and E16i/a, at the attempt to unlock the boot loader!
The phones affected by the problem are units being manufactured at, and after, 11W29!
To check if your device is affected by the problem follow this simple steps:
Turn off the phone and open it up
Take out the battery
Look at the sticker below
If the date code on the sticker reads 11W29, or any later date (11W30, 11W31, 11W32, 11W33, ...), DO NOT attempt to unlock the boot loader.
These phones ship with a revamped chipset configuration having the security hole the boot loader unlock uses effectively closed. This means that upon unlocking the boot loader your phone will end up as a hard brick - and you will have NO means to revive the phone yourselves. You either have to send it off to Sony for repair (recommended solution) or find a phone repair shop being able to resurrect shot devices!
The symptom you will experience when unlocking the boot loader on an affected device is like this:
The boot loader unlock will most likely go through fine
At restart the phone will show NO signs of life anymore.
NO LED, NO LCD output, NO vibration.
This is the point where you can not do anything anymore yourself to resurrect the device.
You have been warned, DO NOT TRY to unlock the boot loader on phones manufactured PAST 11W29!
But it has been seen that there are few devices with manufacturing code above 11W29 have also successfully unlocked their bootloader.
For example me,i have 11W34 and unlocked the bootloader just fine..
But let me remind you again that this was just a matter of luck.
You might not be so lucky...
Also if you have manufacturing code above 11W29 and are desperate to unlock your bootloader then there are paid methods for it as reported by few users who had successfully unlocked their bootloader with manufacturing date above 11W29.
Update (2012/02/23):
To clear up the "no means to resurrect the phone yourself": This is true unless you are a experienced electronics technician. If you own a JTAG box (RIFF Box, Medusa Box) you may attempt to resurrect the device through JTAG. It may also be possible to resurrect the device through UART flash by using a test pin connection. Google is your friend here to dig up the required informations.
As posted by baiclark: There's an option to unlock the boot loader on 11W29+ devices, though this involves some Software (setool2) where you need to buy credits to perform the unlock. This is an untested procedure. If you decide to jump the gun please report your experience.
Update: Home-Brew unbricking with Omnius
Forum member aze2learn posted a guide about how to unbrick your hard bricked W8/X8 by using a modified Nokia CA-42 cable and Omnius. Find his valuable contribution at this post.
/!\ Be warned that this requires basic electronics skills to make it happen. /!\

Unbrick your briked X8/W8 via flashtools
Hi all
I made this thread since some guys were having trouble unbricking their X8/W8 via FLASHTOOLS...
And let me make it clear that the following post wont help you if your phone has bricked in attempt to unlock your bootloader when your phones manufacturing code was above 11W29.
In such a case the only (period) solution is to send it off to SONY to have it repaired.
How to unbrick your Soft Bricked phone..
What do you need?
Flashtools.(thanks to androxyde and bin4ry)
X8 stock firmware.
Or from here.
Or here.
X8 drivers installed.
WinRar
Your X8/W8 phone
A USB cable
A PC
Relaxed mind..
Click to expand...
Click to collapse
Now lets begin.
1.First of all download and install Flashtools from the link provided above.
2.Download SE firmware in *.ftf file format and put it in Flashtool/firmwares folder.
3. Now, run the FlashTool and click the
{
"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"
}
Lighting bolt button to start flash.
4.Now click flashmode and choose Xperia X8 (E15i).
4.Now wait for a while till it says you to "remove your phone,press the back button and hold it and install the USB".
Do it and wait for the flashing proceedure to finish...
If everything works fine then CONGRATULATIONS!!!!!! you have successfully unbricked your phone and installed the 2.1.1.A.0.6 version with 015 baseband, fresh and stock!
If your phone doesnt boots up still, then you might have gone wrong somewhere in the flashing process..
So read the steps carefully and do it again..
[OPTIONAL STEP]
Guide for installing the required drivers for flashing, skip this if you have PC Companion installed and connected your phone in flash mode at least once!
If your phone is not recognized by Flashtool that means you don’t have the required drivers installed.
Open folder /Flashtool/drivers and install ggsetup-2.2.0.11
If after the above Flashtool still doesn’t recognize your phone, do the following:
From Flashtool/drivers folder extract the zip file XXX_ADB_driver which corresponds to your phone model
Open “Device manager” on the computer and find the device which is with an exclamation mark on it (do this with connected to the computer phone)
Right click on the device and choose Uptade driver
Choose to find the driver manually and browse to the folder where you’ve extracted the zip file.
That should install the required drivers on your computer.
Click to expand...
Click to collapse
Now as you have successfully unbricked your phone, the first thing you would possibly do is rooting your phone...
So here i show you how to Root your phone with flashtools..
1.Start Flashtool
2.Connect the device to the computer and wait until it's recognized
3.Click the icon with the "Padlock [the second in a row]
4.FT will start pushing files, wait till it finishes. Meanwhile the phone will reboot once.
5.When it's over Flashtool will notify "Root Access Allowed"
6.Open the application list on the phone and look for the app "Superuser".
7.If "Superuser" is there you have Rooted your device successfully.
Congrats!
That's it...........
If you found this thread useful don't forget to click the THANKS button for me...
Thanks to
Bin4ry and androxyde..(for flashtools)
crowds for the original guide..
Leajian for allowing me to use content from his guide.
BlackRabbit1703 for the mirror of firmware.
And all the people who liked my work...
See ya..

um, mine's an 11W29 and it unlocked just fine. it's only the one's AFTER it that have issues.

I have 11W33 and unlocked 2 times now without a problem ! and works fine

Realtbhuion said:
um, mine's an 11W29 and it unlocked just fine. it's only the one's AFTER it that have issues.
Click to expand...
Click to collapse
We also had a few phones in the 11W3x region that unlocked perfectly, but the hard bricks we observed so far all start at 11W29 - and newer.
The source from where we got the information about the hard brick danger is a post of the_laser on setool.net ...
seems most of lately produced msm7227-based phones have chipset with FIXED security hole, which used to altbypass unlock.
(that is not 100% confirmed, we only have few reports, however better be warned)
such phones will DIE after successful unlock procedure.
such dead phones CAN NOT be recovered. ( perhaps, jtag can fix that, perhaps, qualcomm fixed jtag security hole too )
there is NO WAY to determine if phone has fixed chipset or chipset with security hole.
the ONLY safe way is to use unlock by resurrection cables.
if phone can be connected and booted by resurrection cables, phone is safe to unlock.
if phone can not be booted by resurrection cables, phone has fixed chipset and could not be unlocked.
you have been warned.
get and use resurrection cables.
update:
e16 phone with manufacture date 11w38 affected, i think we should care about phones which produced after 11w26
Click to expand...
Click to collapse
As you can see the_laser referenced 11W26 as the "threshold" where our observation is that 11W29 is where the trouble really starts.
EDIT: See this thread for reference - post #62 and #63 where we summed up a few hard bricks. But that's just the tip of the iceberg, there have been way more.
You're of course free to dismiss the warning and do as you please, just don't come ranting about your hard brick - you've been warned.

My phone is 11W30 (I forgot to check this before unlock bootloader) but all works fine for me.

Mine was 11W37, and I said "was" 'cause I just bricked it.
So Im reading this thread too late lol
However, this situation only hurries things because I'm getting Xperia Ray soon. Now I have to get it sooner.
For now, I have a fa(i)lPhone, wich was a present from my dad. So no worries at all. But having my X8 completely bricked will be a good challenge, as I'll try to bring it back to life no matter if you say there is nothing I can do.
Of course, in case I achieve it, I'll share it! If not, then I'll have a nice modern piece of decoration for my living room: a smartphone XD

x8-11w37 new phone HARD BRICK!
I was lucky ennough they replaced my bricked x8. . No unlocked bootloader for me.

El Brillantinas said:
Mine was 11W37, and I said "was" 'cause I just bricked it.
But having my X8 completely bricked will be a good challenge, as I'll try to bring it back to life no matter if you say there is nothing I can do.
Of course, in case I achieve it, I'll share it!
Click to expand...
Click to collapse
To be precise - there is something that can be done, it's just not very easy.
On the one hand you can try to read up over at setool.net. The latest versions of SETool are able to resurrect shot W/X8's. However, you either need to know to which test-pins to you need to connect the cable from your computer or simply try to get one of the Qualcomm resurrection cables fitting the W/X8. Apart from that you need "credits" for SETool to actually perform the operation. This means you have to pry your W/X8 apart to gain access to the PCB - that's not exactly something everyone around here is able to do - and connect to the right pins to flash in UART mode.
On the other hand you can always try to find someone (private person / repair shop) having a RIFF Box to see if the phone can be resurrected by JTAG, though the way it sounds (the post I read on setool.net about UART resurrection) a JTAG restore seems to be impossible - but feel free to try.
If you can work out a working, and relatively simple to follow, solution to restore shot W/X8's be our guest to write up a post.

thks, for the info, My x8 manuf.code is 11W28, is it safe for unlock BL?

Can i unlock my bootloader?
My W8 code is 11W25 can i unlock my bootloader??

B.Jay said:
If the date code on the sticker reads 11W29, or any later date (11W30, 11W31, 11W32, 11W33, ...), DO NOT attempt to unlock the boot loader.
Click to expand...
Click to collapse
NarutoDroid said:
thks, for the info, My x8 manuf.code is 11W28, is it safe for unlock BL?
Click to expand...
Click to collapse
akhi24nick said:
My W8 code is 11W25 can i unlock my bootloader??
Click to expand...
Click to collapse
So ... 11W28 and 11W25 are below 11W29, right?
No guarantee given as there's always the chance that you may mess up, but it should be safe to try and unlock the boot loader.

Mine is 11W21 (uhm semms a old version or something like that...?), soon I'll try unlocking...
But it has a f..... sinaptic touchscreen, damn...

Hmmmm..... I got 11W34 and i can unlock my Droid

11W48
Hi there,
actually I was following guides in the manner google -> blogs -> direct links to oneclickroot/roms -> direct links to bootloader unlocker and...
Well, unfortunately 11W48 (pretty fresh, huh?) got hard bricked xD
I understand it's motherboard failure now and we can do NOTHING more than sending my new paperweight back to SE?
Also I'm looking forward to finding another way to unlock bootloader with new chips in case the one I get back won't be <11W29
Thanks in advance for your reply

Ahh i wish so much i had red this thread and didn't act too much excited about unlocking it.

10W48 ---> unlock with flashtool!

2010matej said:
10W48 ---> unlock with flashtool!
Click to expand...
Click to collapse
Man.... You are exceptional on EARTH.....
You unlocked bootloader with 11w48 making. You have battery backup beyond 6 days.
May be you can overclock your X8 upto 1Ghz and have Multitouch instead of dualtouch even its also possible that SE will make a firmware 4.0 only for you....
Really, you are an amazing guy...

that's very good to warn everyone here before attempting ^^

my is 11w06

Related

[REF] USB Jig FAQ (Frequently Asked Questions) [4/4/2012] ICS bootloader added

Please don't advertise or provide any external shopping link in my thread, as this thread is meant to provide information only. I want to prevent a amazon/ebay-link cycle which will initially divert the purpose for this thread. Thank you for your co-operation.
Greeting to all fellow android fans!!! i am starting this FAQ merely for USB jig for the Samsung Galaxy S2 as i have search long enough for a topic merely like this, however i couldn't find a topic that will exactly give a proper guide or explanation for this.
i am making this so it would be easier for a noob like me to have just the answers for USB jib.
i claim no credit for myself. all the answers here are compile after going through couple of threads/posts (not sure how many, but i know its many).
What is USB Jig?
- USB jig is actually a micro-USB device which consist of soldering a micro USB plug, and resistors/resistor (as long as you get value of 301k, however, some claim it will still work even between 300k - 400k, not exactly 301k).
The USB jig (not the home made one) should look like 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"
}
Where to get one?
There are actually 2 ways to obtain this tiny piece yet important device for most samsung android users. You can either purchase it from ebay or make it yourself!
- Actually it is selling very cheap at ebay (roughly around US$ 2.00) and worth to invest. However, in my opinion, it is a MUST for everyone (you are exclude if you are not into rooting and flashing your phone).
- I will not go into how to make a homemade USB jig. You can refer to the link below for reference.
Video:
http://www.youtube.com/watch?v=jKRrTZayRxU - thanks to zedomax
Step by step instructions:
http://forum.xda-developers.com/showthread.php?t=819551 - thanks to TheBeano
What does USB Jig do?
In short, USB Jig has 3 functions:
- Get into download mode (main function)
If you soft brick your phone, you can force into download mode using USB jig and reflash new kernel or ROM. As far as i concern, there are few ways to force into download mode, however this is the most simple way to get into it. If USB jig doesn't work, i don't think other method will work either.
If your phone is hard brick, i don't think this will work.
- Remove the yellow triangle
Once you flash your s2 with insecure kernel, a yellow triangle with exclamation mark will appear at boot splash. USB jig can do the trick to remove it for you. (i know flashing S2 with original will remove the triangle as well, but i just wanna point out USB jig function.)
- Reset Odin counter/Reset custom binary counter
If you flash custom ROM into your s2, the binary counter will record it, even after you unroot your phone and set everything to its original, Samsung can still keep track by referring to binary counter. No worry, USB jig will clear the counter. However, some manage to get away with it and still get a warranty, but better to be safe than sorry.
Quote from zedomax:
"And also works on these Samsung phones too:
Samsung Nexus S, Captivate Samsung i9000 Galaxy S, Samsung Vibrant , Samsung Fascinate, Epic 4G, Samsung Omnia 7, Samsung S 4G, Samsung Infuse SGH-i997, Samsung Galaxy S Ace"
There are question about I9100G version. It should work as well, since the different between G and non-G version is the processor only. However, the new G version come with GB 2.3.6, which means new bootloader (Newly G set sold in Malaysia come with it)! No worry, it is being solved! Scroll down and read on.
How do you use USB jig? (courtesy to mrsaccess for remind me this part )
actually this part is quite straight forward. however, i will still try to provide step by step guide (i prefer to do/read it this way, easier to read and understand).
a) how to unbrick your phone
- Turn off your phone and pull out the battery for 2 seconds.
- Put the battery back in the device and don't turn it on.
- Plug the jig into the micro USB port on the phone.
- After about few seconds, your phone should boot up automatically and bring you straight into download mode.
- Unplug the jig.
- Connect your phone with USB cable to computer and then flash your phone via the program "odin".
b) how to remove the yellow triangle
- Turn off you phone.
- Plug in the jig.
- After about few seconds, your phone should boot up automatically and bring you straight into the download mode.
- Unplug the jig.
- Turn off your phone by long pressing the power button.
- Turn it on again and the annoying sign should be gone.
c) how to reset custom binary counter
- Turn off you phone.
- Plug in the jig.
- After about few seconds, your phone should boot up automatically and bring you straight into the download mode(you should be able to see your custom binary counter here). The below message should appear below the counter in green.
ERASING DOWNLOAD INFORMATION SUCCEEDED.
- Unplug the jig.
- Turn off your phone by long pressing the power button.
- If you wanna check the counter, turn your phone on again using the 3 button combo or by using the jig.
HOWEVER...!!! YEAH, HOLD YOUR HORSES!!! I am not finish yet!!!
The nightmare is not finish, you will be sorry if you don't read on, this is where the problems start.
PROBLEM
Is there any problem you ask?
YES! Samsung does indeed keep track of every hack and trick out there. They eventually realize a lot of people is using this dirty USB jig method to reset the custom binary counter/remove the yellow triangle, in order to get a warranty, as they should have void your warranty and charge you for repairs!
Eventually they implement new bootloader into GB ver 2.3.4 onward to prevent USB jig from resetting the custom binary counter/removing the yellow triangle (confirmed by some owners in this forum).
However, this is random as i read that an owner with GB ver 2.3.6 manage to flash the custom binary counter. I assume it depends on which bootloader version they put into your phone then.
However, you can still get into download mode! Which is the most important purpose of all! Phew!!!
SOLUTION
Yes, you are lucky, this problem can be solve.
My many thanks and all credit goes to Intratech (don't forget to thank him for that )
Actually, you can refer to his thread:
http://forum.xda-developers.com/showthread.php?t=1075278
However, the solution is actually at the middle of the thread. To make it easy, i will quote it out.
Quote from Intratech:
"All packages below this point have the old bootloader so you can safely reset the binary counter with a Jig.
If you've already flashed a full package from elsewhere or updated using KIES and cannot reset your binary counter using the Jig just flash this package in the PDA or Bootloader section of Odin to replace the bootloaders and then you can reset the counter: http://www.multiupload.com/LQQBRQVJUD
Here are the new bootloader tarball if you want to flash them back after resetting your binary counter: http://www.multiupload.com/5LNOCL7KPV"
everything tested and worked fine! really a sign of relief for me and i guess its a good news to everyone too!
once again, this thread is meant for reference, and all credits will go back to respective person. I TAKE NO CREDIT FOR ANY INFORMATION HERE. just trying to put everything together as i don't want anyone to go through the hard time like i did.
lastly, all the credits go to:
Intratech
zedomax
TheBeano
if i made a mistake, do let me know, i will correct it. i will take any comment or suggestion so that this can be an easy reference regarding USB jig for everybody.
Android RULEZZZ!!!
EDIT(ADD ON INFO) - credit to rathian for the kind reminder:
New USB Jig V2
To be honest, i really not sure about the new usb jig. And i don't really have the chance to test it out. If someone of you tried it, maybe you can enlighten us here. Thank you.
Does USB Jig works for ICS ROM?
There is much debate for this topic. Some say yes, some say no. However, this is actually what happen in ICS. Samsung actually change a new bootloader for ICS. Basically, the USB Jig presumably will not work for ICS. That is bad news for all of us.
However, base on rathian, he did an experience of trying to flash old gingerbread bootloader into ICS, and you know what? It works! I don't actually recommend this as you might screw things up and end up bricking your phone.
If you want, you can try it out. Please bear in mind you are doing that at your own risk!
I also get some info, if you really wanna get ICS, get a custom ROM. Some developers actually use old bootloader for their custom ROM. That mean you can actually use USB Jig for custom ICS ROM. Please don't ask me which one as i don't really remember, and i might or might not be wrong. I will confirm it once i find out. Until then, better stick to gingerbread!
EDIT:
New ICS bootloader is added here for everyone to download it! FULL CREDIT TO INTRATECH!
Use it as per normal, flash with odin if you wanna use your USB jig. After that, flash back with ICS bootloader.
Please becareful before you do anything. Neither me nor intratech will be responsible for any damages. TAKE YOUR OWN RISK!
Great info buddy.
Can someone please make this a sticky?
Sent from my GT-I9100 using XDA App
Very good summary of how the jig works, definitely needs to be stickied so noobs have less chance of missing it.
Sent from my GT-I9100 using Tapatalk
Nicely written and I agree, we should get this stickied.
Absolutely fantastic summary even I the owner of this handy device and know how to use it.
Cheers
Sent from my GT-I9100 using xda premium
Thank you for putting the info together in one place.
Very helpful
cheers
Thanx for compiling this! *favorite on tapatalk*
thank you very much guys! actually you guys also did a very great job, especially intratech. i totally respect you .
whatever info i need, i can just use search function and i get the all the info i need. however, this (usb jig) is the only missing info here. its not totally missing, but you definitely need to search very hard and combine everything before it start make sense.
since everyone here is so helpful, i was thinking, why not i try to contribute a bit by compiling the info.
if there is any updates or whatsoever, just let me know, i will update it so other ppl can get every info in one place. let's continue with the helping culture here.
not to forget, HO HO HO, MERRY MERRY XMAS!!!
As I understand, the only way to brick your phone is when flashing bootloaders, so its a little scary. So basically, flash new firmware, then flash older bootloaders to remove triangle? Do we lose anything by going back to older bl? I would say only do this if taking phone back to shop, is this a reasonable statement
Sent using TCP/IP
Nice guide but you didn't write how we use the jig.
I mean, should we connect it to the device with the phone powered on? Should the phone be powered down? Do we have to go through a menu or something?
wondering is it work for i9100G model as well?
I tried to apply the old bootloader intratech had in his thread with Odin, flashed passed correctly and still nothing. When the phone is turned off and the jig is inserted, nothing happens (bought it on Ebay) , how can I check the bootloader version? Anything else I can do?
Sent from my GT-I9100
mrsaccess said:
Nice guide but you didn't write how we use the jig.
I mean, should we connect it to the device with the phone powered on? Should the phone be powered down? Do we have to go through a menu or something?
Click to expand...
Click to collapse
Simply power off the phone and when she's completely turned off just stick the Jig in her, all the way in, and simply wait for the it to turn her on and put her into download mode. It will auto reset the binary counter. From here just pull it out of her and hold down the power button and it will turn her off after a few seconds.
ahwai84 said:
wondering is it work for i9100G model as well?
Click to expand...
Click to collapse
I don't have access to a G model but don't try to flash the bootloader from the international model (the one in this thread) or you'll have a nice brick.
NXUS said:
I tried to apply the old bootloader intratech had in his thread with Odin, flashed passed correctly and still nothing. When the phone is turned off and the jig is inserted, nothing happens (bought it on Ebay) , how can I check the bootloader version? Anything else I can do?
Sent from my GT-I9100
Click to expand...
Click to collapse
If you stick the Jig in her when she's turned off and she doesn't get turned on into download mode then your Jig is faulty.
mrsaccess said:
Nice guide but you didn't write how we use the jig.
I mean, should we connect it to the device with the phone powered on? Should the phone be powered down? Do we have to go through a menu or something?
Click to expand...
Click to collapse
oh, yeah! thanks mrsaccess for pointing that out. how can i miss that!
i will re-edit and compile it.
edit: btw, forget to thanks intratech for helping me out ^^
credit to author of this post ;p
Thanks for the great write up, I was beginning to think I had a bad jig as it would go into download mode but not reset the counter!
gsw5700 said:
As I understand, the only way to brick your phone is when flashing bootloaders, so its a little scary. So basically, flash new firmware, then flash older bootloaders to remove triangle? Do we lose anything by going back to older bl? I would say only do this if taking phone back to shop, is this a reasonable statement
Sent using TCP/IP
Click to expand...
Click to collapse
I'm curious on this as well, is there any benefit to flashing the new bootloader after the counter is reset?
MagicMan3 said:
Thanks for the great write up, I was beginning to think I had a bad jig as it would go into download mode but not reset the counter!
I'm curious on this as well, is there any benefit to flashing the new bootloader after the counter is reset?
Click to expand...
Click to collapse
personally, i don't really bother with the triangle thing and the counter thing.
unless you wanna bring back your phone to Samsung for warranty, then it would be better to get everything back to its original. As they would have record all your version (kernel, bootloader, etc.) in their database, and they might void ur warranty if version is incorrect. (they might have different policies for different countries)
unless you have Samsung frens to confirm you that they don't really check on the bootloader version.
For me, possible future Samsung support is the reason I bought a jig. This guide is excellent!
Sent from my GT-I9100 using XDA App
quincy6688huang said:
credit to author of this post ;p
Click to expand...
Click to collapse
AllSeeyinEye said:
For me, possible future Samsung support is the reason I bought a jig. This guide is excellent!
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
thank you very much. i am glad to know that i am providing helpful info to all.
however, all 99.9% effort should remain credit back to the people who crack it. i am just doing 0.1% effort to compile all the info into one place, for reference.
Thank you for the explanation, very useful

Read through noob guides but still having problems with the auto BL unlock

I've been thinking about it for a while but decided to give it a try today . The step that tells me to hold up I get but then how so I power down to activate fastboot ?
Sent from my Atrix-4G, stock 2.3.4 (rooted)
DopeHack said:
I've been thinking about it for a while but decided to give it a try today . The step that tells me to hold up I get but then how so I power down to activate fastboot ?
Sent from my Atrix-4G, stock 2.3.4 (rooted)
Click to expand...
Click to collapse
hold volume down button while booting up, then hold volume up after fastboot is selected to activate it.
after that, you use fastboot commands on your computer.
But I was using the automatic unlocker . I still need to put in commands myself?
Sent from my Atrix-4G, stock 2.3.4 (rooted)
DopeHack said:
But I was using the automatic unlocker . I still need to put in commands myself?
Sent from my Atrix-4G, stock 2.3.4 (rooted)
Click to expand...
Click to collapse
Did you ask in that thread?
Sent from my MB860 using xda premium
DopeHack said:
But I was using the automatic unlocker . I still need to put in commands myself?
Click to expand...
Click to collapse
I believe the automatic unlocker will pause and should give clear instructions ask you to do specific things that have to be done by a human (power down and reboot into certain mode, etc), you just need to follow these instructions. After that, you just hit enter to continue.
If you are unable to follow these instructions, probably it's too much for you...
To reboot into fastboot, for example: press the power button, to turn off the phone; then hold the volume down button, press the power button again, you'll see "Fastboot", then release volume down, press volume up, you enter the "fastboot" mode
Too much for me lol I know how to get to all the menus that its telling me to go to but nothing else happens. the guide said nothing about typing in anything which is why I choose it. Especially since the automatic root worked easy as pie ...
Sent from my Atrix-4G, stock 2.3.4 (rooted)
You want help, laugh when people who are trying to help say it might be too much for you, yet you provide us close to absolute no information.
What guide are you following? We might know, but it still is your job to provide a link.
What is the step you are stuck at?
Why, what isn't going according to plan? What do you see happening in your sceen / phone?
If you can't explain properly, provide some screenshots.
You say you can get to all the menus it tells you to, yet in the first step you can't seem to get into fastboot. Your speech is unclear and what you want is hard to understand.
My opinion is you aren't ready to unlock your bootloader. You know very little about your phone or how it works. That's the community's fault really, with all these automatic scripts, which are really nice if you know what you're doing, but end up promoting easy ignorance in people like you.
I just hope in a month or two you are not one of those writing "OMG, please, I arrempted to downgrade by SBF and know my phone won't boot, what gives???"
Read up on some information a learn how these things work. It is the best you can do. Owning an android device and modding it can be great fun, but it does require some effort on your part. If I were you, I would learn how to unlock my bootloader with pudding, just to understand what is actuallly going on.
Either that, or you can learn how to ask for help properly and politely. Your choice.
Also, wrong section, This is not Q&A.
My girlfriend was rushing me so I tried to type up something quick but I used this
http://forum.xda-developers.com/showthread.php?t=1182871
As you can see like I can see it does not say I need to type anything in the cmd (which I have seen in YouTube videos and isn't that hard) but thought hey automatic sounds good so I gave it a try I don't have any problems getting the phone to fast boot or rsd as I've used the stock recovery to clear cache in an attempt to fix something. The part I'm stuck at is step 6
You are right I don't know alot about android which is why I didn't start messing with my phone the day I got it but I've been all over this site (well the atrix at least) and YouTube.
I appreciate any help and sorry for the misplaced thread
Sent from my Atrix-4G, stock 2.3.4 (rooted)
DopeHack said:
My girlfriend was rushing me so I tried to type up something quick but I used this
http://forum.xda-developers.com/showthread.php?t=1182871
Click to expand...
Click to collapse
this one is better
http://forum.xda-developers.com/showthread.php?t=1302423
doesnt give you the soft brick i think
So, let's see if I got this, you are having trouble at the part it says it should restart? Or before that? After you choose the number and press enter, what happens?
This could be a driver problem... If windows is not recognizing a device, it's common... Which windows are you using? I used to have some problems on XP and vista...
Newbleeto said:
So, let's see if I got this, you are having trouble at the part it says it should restart? Or before that? After you choose the number and press enter, what happens?
This could be a driver problem... If windows is not recognizing a device, it's common... Which windows are you using? I used to have some problems on XP and vista...
Click to expand...
Click to collapse
Right where it says it should restart and go into fastboot nothing happens I could hold that power button all day. I knew vista would bring an issue into the mix cause it never made the sound for connecting the phone but the SD cards show up
Sent from my Atrix-4G, stock 2.3.4 (rooted)
sanriver12 said:
this one is better
http://forum.xda-developers.com/showthread.php?t=1302423
doesnt give you the soft brick i think
Click to expand...
Click to collapse
This is the one I read before thanks hopefully my girlfriend will disappear for a hour or two (she doesn't want me to ruin my phone) so I can work on it .
so with this one I can use fauxs 1.3 or 1.45Ghz kernal with cm7 I've been craving that ice cream sandwich ..
Sent from my Atrix-4G, stock 2.3.4 (rooted)
Computer is down for a while seems like it wasn't meant to be but Im still going to get it done
Sent from my Atrix-4G, stock 2.3.4 (rooted)
I actually had to use a Vista system to get this to work.
Now, when the instructions say it should "Restart", at that point, have you been in "Fastboot" yet? Have you been to the part where you have to enter your "Unique ID"?
This is important to know because throughout the bootloader-unlocking process the phone should be restarted a couple of times. It sounds like you have at least gotten through the part where it flashes "Pudding" but it sounds like you haven't done the "fastboot" part yet.
Are you referring to "Step 6" in the actual post or within the script? If the power button does not work then just pull the battery. As long as it is not in the process of doing something you should be fine.
I also want to point out that the program you are using only requires that you type in your Unique ID, everything else is automated, not to mention the file contains everything you need including adb, fastboot, RSDlite, Superuser, Pudding, and a working recovery so it makes it very easy for the end user to not have to find everything on their own. The script unlocks the bootloader, roots your phone, and flashes CWM recovery.
Either way, please provide more details if you are still having issues. Good luck.
DopeHack said:
Right where it says it should restart and go into fastboot nothing happens I could hold that power button all day. I knew vista would bring an issue into the mix cause it never made the sound for connecting the phone but the SD cards show up
Sent from my Atrix-4G, stock 2.3.4 (rooted)
Click to expand...
Click to collapse
live4nyy said:
I actually had to use a Vista system to get this to work.
Now, when the instructions say it should "Restart", at that point, have you been in "Fastboot" yet? Have you been to the part where you have to enter your "Unique ID"?
This is important to know because throughout the bootloader-unlocking process the phone should be restarted a couple of times. It sounds like you have at least gotten through the part where it flashes "Pudding" but it sounds like you haven't done the "fastboot" part yet.
Are you referring to "Step 6" in the actual post or within the script? If the power button does not work then just pull the battery. As long as it is not in the process of doing something you should be fine.
I also want to point out that the program you are using only requires that you type in your Unique ID, everything else is automated, not to mention the file contains everything you need including adb, fastboot, RSDlite, Superuser, Pudding, and a working recovery so it makes it very easy for the end user to not have to find everything on their own. The script unlocks the bootloader, roots your phone, and flashes CWM recovery.
Either way, please provide more details if you are still having issues. Good luck.
Click to expand...
Click to collapse
I wasn't blaming vista I was just saying cause I've had problem with that is in the past.
I've basically done nothing haven't flashed or wiped my phone yet I was basically stuck at or around the first step cause it first asks for RSD protocol and then it says restart phone but the power button has no effect why in that mode nd when I pull the battery to manually put it in fast boot nothing happens nd I get some kind of batch error when it trays to get my unique id...
But got the computer back today so I'm gonna work on it again
Thanx for help ... will update you guys when I can
sanriver12 said:
this one is better
http://forum.xda-developers.com/showthread.php?t=1302423
doesnt give you the soft brick i think
Click to expand...
Click to collapse
Actually, I followed the method you linked (old netbook running XP) and got a softbrick on the automatic reboot after flashing pudding. I was so busy watching RSD Lite do its thing that I didn't catch that my phone had actually rebooted; it selected fastboot mode on its own so I was able to issue the unlock command. It took.
"7.Plug your device into your computer. RSD Lite should recognize your device and say “Model: NS Flash Olympus” and “Connected…” The acronym 'NS' may be different for your device people!!"
its not doing this(i have rsdlite 4.5.5 because i cant find 5.5)
edit: got on to next problem
Thanks everyone
{
"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"
}
Sent from Atrix 4G running CM7 ICS Final @ 1.2Ghz
If cpu not recognizing ur device in fastboot try restarting ur cpu. If u updated drivers u have to restart the cpu before it will see ur device.
Sent from my MB860 using xda premium

My LG G2 is COMPLETELY bricked.

So after 20 hours of fiddling... I can safely say that this LG G2 D803 is completely done.
Given by a friend, the phone started off by booting straight to fastboot, and had download mode available after he flashed a ROM designed for a tablet.
I attempted the .TOT method described here, where I used LGTools. I then only realized that this method was only suitable for an US device, such as AT&T, T-Mobile, or Verizon (couldn't find a Rogers .TOT). I didn't modify the phone in any way.
I then continued to download the Rogers KDZ file here. Using the method described in the same post above, I performed the upgrade, only to realize that this was method wasn't working either.
I then did some scouring to find a way to boot into TWRP (which was already installed). I found this trick: If you hold the power button down until the phone turns off, you can hold power and down until you see the LG symbol, and then depress and press them again immediately to get into TWRP!
In TWRP... I realized that the partitions were all messed up. It was showing 6GB internal, and countless errors were popping up. Another dead end. ADB was working, but I was unable to push anything.
I then realized I should attempt to flash updated partitions using fastboot. Using the cmd line in Windows, I erased and flashed partitions I downloaded here after putting the phone in fastboot mode.
This is where I did something stupid.
Instead of clicking and downloading on that site, I right-clicked "save-as" and downloaded 8kb corrupted partition files. I continued and flashed them unknowingly... and right after, the phone decided to not boot at all.
Using VMWARE and Ubuntu 14.04, I attempted to reflash the partitions using Linux commands described here. Unfortunately, the device would not show the /sd* partitions. Certainly, the bootloader that communicates with the PC does not allocate the partitions properly anymore.
Alright, the phone wont boot, because I flashed a bad bootloader. No biggie right? I would see the device as Qualcomm hs-usb qdloader 9008.
That's when I scoured for a new method to fix the partitions. I came across QPEST and eMMC Software App to get this device back alive.
I spent hours trying to find the right .hex and .mbn file on Chinese websites. I found 8974_msimage.mbn, MPRG8974.hex, flash.xml, rawprogram0.xml and patch0.xml. I had to create accounts of a bunch of sites to finally download the correct files.
Carefully using QPST, I was able to get the phone in Download Mode (Qualcomm download mode, not LG download mode), and pushed the instructions to the device.
... too bad. I thought I did everything right. The device times out in the process EVERYTIME.
{
"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 officially dead, there isn't a way I know of to get it started (at least to fastboot again). It really pays off to check what you're flashing before you do it. The internet is full of crap.
BuffMcBigHuge said:
So after 20 hours of fiddling... I can safely say that this LG G2 D803 is completely done.
Given by a friend, the phone started off by booting straight to fastboot, and had download mode available after he flashed a ROM designed for a tablet.
I attempted the .TOT method described here, where I used LGTools. I then only realized that this method was only suitable for an US device, such as AT&T, T-Mobile, or Verizon (couldn't find a Rogers .TOT). I didn't modify the phone in any way.
I then continued to download the Rogers KDZ file here. Using the method described in the same post above, I performed the upgrade, only to realize that this was method wasn't working either.
I then did some scouring to find a way to boot into TWRP (which was already installed). I found this trick: If you hold the power button down until the phone turns off, you can hold power and down until you see the LG symbol, and then depress and press them again immediately to get into TWRP!
In TWRP... I realized that the partitions were all messed up. It was showing 6GB internal, and countless errors were popping up. Another dead end. ADB was working, but I was unable to push anything.
I then realized I should attempt to flash updated partitions using fastboot. Using the cmd line in Windows, I erased and flashed partitions I downloaded here after putting the phone in fastboot mode.
This is where I did something stupid.
Instead of clicking and downloading on that site, I right-clicked "save-as" and downloaded 8kb corrupted partition files. I continued and flashed them unknowingly... and right after, the phone decided to not boot at all.
Using VMWARE and Ubuntu 14.04, I attempted to reflash the partitions using Linux commands described here. Unfortunately, the device would not show the /sd* partitions. Certainly, the bootloader that communicates with the PC does not allocate the partitions properly anymore.
Alright, the phone wont boot, because I flashed a bad bootloader. No biggie right? I would see the device as Qualcomm hs-usb qdloader 9008.
That's when I scoured for a new method to fix the partitions. I came across QPEST and eMMC Software App to get this device back alive.
I spent hours trying to find the right .hex and .mbn file on Chinese websites. I found 8974_msimage.mbn, MPRG8974.hex, flash.xml, rawprogram0.xml and patch0.xml. I had to create accounts of a bunch of sites to finally download the correct files.
Carefully using QPST, I was able to get the phone in Download Mode (Qualcomm download mode, not LG download mode), and pushed the instructions to the device.
... too bad. I thought I did everything right. The device times out in the process EVERYTIME.
The phone is officially dead, there isn't a way I know of to get it started (at least to fastboot again). It really pays off to check what you're flashing before you do it. The internet is full of crap.
Click to expand...
Click to collapse
there is a lot of crap on the internet but when you start fastbooting or dding partitions without verifying the integrity of the stuff you downloaded you will eventually brick something. Perhaps this experience will goad you into checking md5 or sha1 before you go about flashing things.
DeathmonkeyGTX said:
there is a lot of crap on the internet but when you start fastbooting or dding partitions without verifying the integrity of the stuff you downloaded you will eventually brick something. Perhaps this experience will goad you into checking md5 or sha1 before you go about flashing things.
Click to expand...
Click to collapse
It's very rare that I ensure the md5 is correct. In this case, the file sizes were completely off (8kb rather than 512kb), which is more noticeable than the hash. You're absolutely right. I sent the phone to MobileTechVideos for a JTag repair. I'll post the results when I get it returned.
You made a valiant effort, good luck man.
My hat goes off to you, man. Is it under a warranty that covers accidental damage? A good smashy-smashy would cover your tracks and relieve your stress all at once
I tell you though - fine attempt. Made my day reading this. Never stop at no. Hope you get your phone fixed.
Onward.
Sent from my LG-D802 using XDA Premium HD app
1 LG G2 down
20 million+ units still in combat working the daily grind!
Now phone is dead so go to the warranty method.
BigBoyPL said:
Now phone is dead so go to the warranty method.
Click to expand...
Click to collapse
he did the RIGHT thing and sent it to be repaired at his cost. to do what you are implying is to be a thief.
xlr8me said:
1 LG G2 down
20 million+ units still in combat working the daily grind!
Click to expand...
Click to collapse
make it 2 lg g2 mine is dead too...
mine is back to life finally
Can you not use a fastboot cable and re flash the correct partition images from there. I used that method to recover a completely bricked Kindle fire recently.
ClawOfDoom said:
Can you not use a fastboot cable and re flash the correct partition images from there. I used that method to recover a completely bricked Kindle fire recently.
Click to expand...
Click to collapse
I think this are the cases when the warranty should be used. The phone is not on it's best condition, so that should take care of this.
Any updates on the repair? I have a bricked D801 too...
zPacKRat said:
he did the RIGHT thing and sent it to be repaired at his cost. to do what you are implying is to be a thief.
Click to expand...
Click to collapse
I respectfully disagree. everything described is software related. The hardware is still fine. At least from what I was reading. Which means the phone could be sent back, under warranty and repaired in probably under 5 minutes. It might get a dollars worth of new plastic on it. Repackaged up and sent off to somebody else to replace their broken phone. The losses on the replacement phone would be recouped almost instantly.
Sent from my VS980 4G using Tapatalk
Can you help me.
Dear BuffMcBigHuge!
I have a situation same you, Now my LG G2 L-01F - NTT DOCOMO total Dead, it show Qualcomm HS-USB QDLoader only.
I searched many forum, but havent find out these file.
Can you give me these file for me to try unbrick My G2.
My email: [email protected]
Many thanks you.
dm6939 said:
Dear BuffMcBigHuge!
I have a situation same you, Now my LG G2 L-01F - NTT DOCOMO total Dead, it show Qualcomm HS-USB QDLoader only.
I searched many forum, but havent find out these file.
Can you give me these file for me to try unbrick My G2.
My email: [email protected]
Many thanks you.
Click to expand...
Click to collapse
+1 = I have the same here...
So after sending the device to MobileTechVideos, I was able to get it fully repaired and back into working order! They converted it to a D801, and its back in full working order!
Highly recommended!
BuffMcBigHuge said:
So after sending the device to MobileTechVideos, I was able to get it fully repaired and back into working order! They converted it to a D801, and its back in full working order!
Highly recommended!
Click to expand...
Click to collapse
Fantastic news glad there are still teams that are dedicated to there work and know what they are doing
Danzano's happy place
Danzano said:
Fantastic news glad there are still teams that are dedicated to there work and know what they are doing
Danzano's happy place
Click to expand...
Click to collapse
Any more updates here ? looks like we need 2 important files specific to the G2 . The .hex and the mnb file to enable writing to eMMC.
zathus said:
I respectfully disagree. everything described is software related. The hardware is still fine. At least from what I was reading. Which means the phone could be sent back, under warranty and repaired in probably under 5 minutes. It might get a dollars worth of new plastic on it. Repackaged up and sent off to somebody else to replace their broken phone. The losses on the replacement phone would be recouped almost instantly.
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
bc OP stated:
"Given by a friend, the phone started off by booting straight to fastboot, and had download mode available after he flashed a ROM designed for a tablet"
so when a device is broken, (whether it be hardware or software) by the user, that is not a manufacturer defect. That is misuse, nonwarranty. thats why the guy you responded to said "he did the RIGHT thing and sent it to be repaired at his cost. to do what you are implying is to be a thief." and i agree with him. I actually cringe when i see people on here brick their phones, then ask for ways to unroot so they can get it repaired under warranty. Manufacturers are going to continue to make it harder to gain root access bc im sure theyre tired of wasting time on people who broke their phones themselves, then want it repaired for free. sigh...

[UNBRICKING] Research on Unbricking Method for Zenfone 2

TESTERS NEEDED
The main intention of the threat was to find a way to restore a completely bricked zenfone 2. It is apparent that we are not having a spare bricked device to test upon.
Anyone with a Bricked Zenfone 2, A PC, and willingness to devote time, please participate.
Otherwise, this thread is going no where as we people who are searching for methods do not have bricked devices(And do not want to specially brick them for testing)(Obviously!!!) and all talks are in taking us nowhere.
Click to expand...
Click to collapse
"Bricked Devices" is a regularly heard phrase on XDA. Sadly, Asus devices dont come with a dedicated PC Companion or PC Suite software which can safely unbrick a Zenfone just in case someone is able to damage fastboot.
That Said, there have been Zenfone 2's that have been Hard Bricked in the past months. Fortunately, many of them may have got replaced as the device comes with a One Year Warranty. But what after that...???
So, i wanted to do some research upon this unexplored topic.
On successfully Hard Bricking your device, you will see something like this :highfive:
{
"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"
}
( credit to the one who bricked and clicked)
I do not have a bricked device, but if anyone can get one and test stuff, we may end up getting something concrete to restore in future.
So, i came across a page: http://www.asus-zenfone.com/2014/11/how-to-unbrick-zenfone-5-and-zenfone-6_8.html
But soon i understood that all these things are foreign to me ( So far ).
Also, The drivers for the SOC are for CloverView Plus Devices.
It would be seriously great if we can successfully recover from corrupt fastboot. As without fastboot we can do absolutely nothing.
I request senior members, Devs and all others to provide inputs and links and keep this thread productive.
Who knows, someday we may end up in a situation without warranty and with a corrupt fastboot.
I will keep on updating this thread with updates from your side
Lets Start.
So that method in the link is like the Odin for Samsung, or the NvFlash for nvidia. Except that it is for Cloverview (32 nm SOC) vs Moorfield (22nm SOC) which is what we have.
cmendonc2 said:
So that method in the link is like the Odin for Samsung, or the NvFlash for nvidia. Except that it is for Cloverview (32 nm SOC) vs Moorfield (22nm SOC) which is what we have.
Click to expand...
Click to collapse
Exactly!!. We need something that works on Moorefield
[email protected] said:
Exactly!!. We need something that works on Moorefield
Click to expand...
Click to collapse
I looked further into it and what we need is the DNX_FW, IFWI, DNX_OS, and OS files for this device. This guide has more details on the Intel Manufacturer Flasher, which seems to be a version of the xFSTK downloader? The downloader seems only to write files (or download files) to the device, not generate them or copy them from the device. Someone with more experience would have to do that.
cmendonc2 said:
I looked further into it and what we need is the DNX_FW, IFWI, DNX_OS, and OS files for this device. This guide has more details on the Intel Manufacturer Flasher, which seems to be a version of the xFSTK downloader? The downloader seems only to write files (or download files) to the device, not generate them or copy them from the device. Someone with more experience would have to do that.
Click to expand...
Click to collapse
I think we first need drivers for the moorefield SOC ( SOC Drivers) to access the partitions without fastboot support.
I havent read the PDF that you linked. Will read and revert back.
Great job guys
Better be prepared now than panic later haha
Hope i can help but im totally new in this kind of stuff
This makes me want to take a course related to this stuff cause its amazing how u brainstorm with each other
tactician10 said:
Great job guys
Better be prepared now than panic later haha
Hope i can help but im totally new in this kind of stuff
This makes me want to take a course related to this stuff cause its amazing how u brainstorm with each other
Click to expand...
Click to collapse
Well, thats what XDA is here for.
Learning is a never ending process. And i have learnt a lot from others in this place.
And regarding this thread being inactive.
I have got a few things, but they seem irrelevant to me. Searching for something really solid in this regard. No point in posting irrelevant findings from my side and bumping up the thread.
I am going to get a bricked Zenfone 5 (Sure) and Zenfone 2(Hopefully) from a local repair shop.
Will try doing serious software damage to the Zenny 2 and will then try to recover. Lets See!!
i have this problem, broke my fastboot
Does your phone bootup???? Does Android bootup?
If it doesnt, you are currently out of luck
As already said by @cmendonc2 , we need someone senior to extract some files
@edit@
I solved it.
I reflashed recovery via Adb in screen selection "recovery mode/bootloader/normal"
I'm very happy
test subject..
Phone is hard bricked.. cant fastboot and on reboot it bootloops. I went into stock recovery via adb n actually data wiped n now cant adb either.. so.. tell me what u want me to try n ill let u know. Btw i already requested RMA but asus says maybe 4 weeks till i get it back.. so im hoping u guys can help me fix it before i send it in. Thanks
Seoulja said:
Phone is hard bricked.. cant fastboot and on reboot it bootloops. I went into stock recovery via adb n actually data wiped n now cant adb either.. so.. tell me what u want me to try n ill let u know. Btw i already requested RMA but asus says maybe 4 weeks till i get it back.. so im hoping u guys can help me fix it before i send it in. Thanks
Click to expand...
Click to collapse
Can you boot into Android????
What is your device model?? ZE550ML or ZE551ML??
Seoulja said:
Phone is hard bricked.. cant fastboot and on reboot it bootloops. I went into stock recovery via adb n actually data wiped n now cant adb either.. so.. tell me what u want me to try n ill let u know. Btw i already requested RMA but asus says maybe 4 weeks till i get it back.. so im hoping u guys can help me fix it before i send it in. Thanks
Click to expand...
Click to collapse
[email protected] said:
Can you boot into Android????
What is your device model?? ZE550ML or ZE551ML??
Click to expand...
Click to collapse
ZE551ML / ZOOA
It bootloops when i try to boot it. I get the usb symbol when i try to fastboot. I wanna try using intel phone flash tool but require .xml flash file within a stock Rom .zip file. I looked everywhere but i can't find a zip with .xml flash file.
moorefield driver
[email protected] said:
I think we first need drivers for the moorefield SOC ( SOC Drivers) to access the partitions without fastboot support.
I havent read the PDF that you linked. Will read and revert back.
Click to expand...
Click to collapse
Hello, if you install the Intel phone flash tool lite, the tool install also the moorefield driver. When you open the xfstk downloader the tool looks the phone but in stock rom from asus i can not found the ifwi os dnx os image files. If anyone will find the files please tell to me.
Thans for your help.
We need some experienced dev to extract these files for us
Without that, there is no option
levi1232005 said:
Hello, if you install the Intel phone flash tool lite, the tool install also the moorefield driver. When you open the xfstk downloader the tool looks the phone but in stock rom from asus i can not found the ifwi os dnx os image files. If anyone will find the files please tell to me.
Thans for your help.
Click to expand...
Click to collapse
Hey there!!
Check out this page: http://forum.xda-developers.com/general/xda-assist/intel-phone-flash-tool-t3129091. Its for Zenfone 5
The Guy has stated that he found the Necessary files by unpaking the boot.img,which can be found in the firmware zip available on Asus Support website.
Alternatively, you can get it from Here. But these are older ones. I would recommend the Asus website though.
The Intel Phone falsh tool is available at https://01.org/android-ia/downloads/intel-phone-flash-tool-lite . Try it out.
I have wiped my Linux and windows partitions as i am installing Windows 10. So this is all i can help you with. If you need any information, Just Ask. I will do my best to help.
As for extracting the boot.img, do a quick google search. XDA has a thread for that. You need either Linux or cygwin.
All the best!!!!
Disclaimer: I have not tested these things. Try at your own risk
cmendonc2 said:
I looked further into it and what we need is the DNX_FW, IFWI, DNX_OS, and OS files for this device. This guide has more details on the Intel Manufacturer Flasher, which seems to be a version of the xFSTK downloader? The downloader seems only to write files (or download files) to the device, not generate them or copy them from the device. Someone with more experience would have to do that.
Click to expand...
Click to collapse
Hey,
I just stumbled upon something.
I downloaded the latest OTA zip package (20MB) of the ze551ml
I opened the ifwi folder
And i found the bin files. DNX FW etc of various zenfone variants.
Can you throw some light on this???
P.S.
Folder screenshot attached!!
Here's some more info I found on the IFWI images:
Two special IFWI images are used for booting in this mode: _dnx_fwr.bin and _dnx_osr.bin. These comprise a simple flash tool that writes a raw image to the eMMC boot partitions and another to the main eMMC space. xFSTK is provided with paths to the IFWI image and a eMMC image. The eMMC image contains an OSIP header (location/size of U-Boot in eMMC, load address, and entry point), a partition table, and partitions with U-Boot and the U-Boot environment.
Click to expand...
Click to collapse
So the dnx_fwr.bin is probably this file:
Code:
dnx_fwr_ann_a0-mofd_v1-ze551ml.bin
The ifwi.bin is probably this file:
Code:
ifwi_ann_a0-mofd_v1-ze551ml.bin
I checked the MD5sums of the different versions and they are different. I guess we need a bricked ZF2 to test and see. Although we still don't have the OSR files. Perhaps @shakalaca can help us.
Okay right
I just had one last week. I tried everything i could. Finally i gave it back.
And Today i stumbled upon this.
Ill see if the guy still has that bricked zen.
Thanks for your reply
Sent from my ASUS_Z00AD using XDA Free mobile app
Good day sir, i was just wondering if this reseach is still going. Still unable to find any solution to my hard bricked zenfone 2 ZE200ml. Im somehow counting on this. Goodluck!

[Flashtool] How to flash the Sony Xperia Z5 Compact with stock ROM [Flashtool]

Over the past couple of days, I have been experiencing various issues with flashtool. Using the internets help and many hours of my time I managed to fix most of these problems that occurred for me. Although there are hundreds of Flashtool step by step instructions, I thought it would be best for an updated and more in depth on what you should be aware of first before clicking "Flash".
Firstly, I do not take responsibility for any device broken or damaged since there is ALWAYS a minute chance of your device bricking.
Lets start, shall we?
Things Needed
Z5 Compact
Original Cable (or any cable actually that is working and can transfer files)
Flashtool 0.9.22.3
Sony Xperia Z5 Compact Stock Rom
Okay to start off.. Yes, this should work with other phones however I am not providing the stock roms for those, it takes a simple google search to find them ie. "Sony Xperia Z5 Stock Rom ftf"
You don't need the latest stock rom either since you can update once the phone is setup depending on if you have access to OTA updates (Over the Air).
Step 1.
Download flashtool if you haven't already. If you have an older version of flashtool, uninstall it and make sure all old files are gone for good and also be sure the new one is fully installed. I prefer to use the magnet link on the website (for torrents) since using uploaded.net takes forever.
Step 2a.
If you're on Windows 8/8.1/10 then please take note to this specific paragraph, any other OS skip to 2b Windows 8/8.1 like to have its security tight, so they block you from installing drivers with unsigned certificates to "keep your computer from harm" but just go ahead and follow the instructions to allow your computer install these drivers. If the drivers aren't installed correctly, then you won't be flashing anything today Okay, go to Settings>General and then click on 'Restart Now' under 'Advanced Startup'.
{
"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 will restart your PC. It will then take you to a screen that gives you various options. On Windows 8 you will see 'Troubleshoot' and on Windows 8.1 you will see 'Start-up Settings'. Select either that appears. This will take you to another page that will ask to restart windows in order to use some advanced startup features, just click 'Restart'. If it already takes you to the page without restart, or if your computer just restarted and you're getting the options of what to select, make sure you select 'Disable driver signature enforcement'.
Your computer should now restart with driver signature enforcement disabled. Now, go ahead and carry on with the instructions in 2b!
Step 2b.
Navigate to the 'drivers' folder where you installed Flashtool. If you cant remember where you installed it, the default directory should be in "C:\Flashtool". Open 'Flashtool-drivers.exe' and install:
Flashmode Drivers
Fastboot Drivers
Z5 Compact Device Driver (Or whatever your device is)
Now we have successfully installed the drivers for flashtool and our device!
Step 3.
Find the stock rom you downloaded, copy and paste it into your firmwares folder in flashtool. For me, this is in "C:\Users\Matty\.flashTool\firmwares". People have been saying to delete the folders inside the firmwares folder, do not do this as the flash might not work.
Step 4.
Note
If you're running 64bit, I recommend you to not use Flashtool64.exe at first, just use the standard 'Flashtool.exe'. If you dont get an icon on your desktop from the setup, just navigate to the folder in the directory you installed it in, then right click and click send to desktop so you can access it easy
Step 5.
Open Flashtool from your newly created shortcut on your desktop. Click the Flash icon, then click Flashmode, then hit Ok. Click your Firmware on the left to start off with. You might have to hit the firmware dropdown until it gets to the actual firmware like so:
If you want to remove all your data, where it says Wipe, hit all the boxes. (APPS_LOG, DIAG, SSD, USERDATA). Then click Flash. You will now see "Preparing files for flashing" on your screen. Be very patient, and in the meantime, turn your phone off ready to enter Flashmode. Make sure your phone is switched off and NOT plugged.
When you see this box come up on your computer, It's probably time to connect the USB to your computer, and enter flashmode on your phone.
Plug the USB into your computer
(TRY USB 2.0 FIRST, SOME REASON NO USB 3.0 PORT WORKED FOR ME+MANY OTHER PEOPLE HAD PROBLEMS WITH USB 3.0 I.E loader.sin errors)
Entering Flash Mode
Hold the Volume Down button and plug the USB cable from your computer into your phone. You should hear the Windows noise it makes to say the device is connected to the PC. If any extra drivers are needed to complete the flash it could take longer for the flash to start. You should then see a constant green light in the top right of your device, gently put it somewhere without unplugging the charger and let Flashtool do the hard work
Step 6.
Leave the device for no longer than 30 minutes. However, if you're unsure be safe and leave it for a full hour, go out have a nice brew, do a tap and dance and come back and it should be done. The only reason it would get stuck is because you unplugged the phone during the Flash, or if the cable somewhat died throughout the operation. If so, repeat the instructions in hope your device will be as good as new
Flashtool will now let you know when it is done. It will say "Flashing finished, please uplug and start your phone."
If it says that, hooray! You have successfully flashed your phone with stock rom!
If not and you get an error before it even wants to flash, or throughout the process you get an error, post it below and I'll take a look. I'm not very good but I know quite a few errors.
END OF TUTORIAL
I just thought I'd help the community out in a way that I can, since I'm bad at like everything else lol.
Peace folks :highfive: :cyclops:
Great write-up! I know it probably would have helped me months ago for something like this to exist. For anyone coming here for info, it also took me three PC's before I found one that played well with flash tool. Also if you ever get a failure, reboot PC, phone, and try again. Persistence pays off.
civicsr2cool said:
Great write-up! I know it probably would have helped me months ago for something like this to exist. For anyone coming here for info, it also took me three PC's before I found one that played well with flash tool. Also if you ever get a failure, reboot PC, phone, and try again. Persistence pays off.
Click to expand...
Click to collapse
Thanks buddy! I suppose the old saying does work.
"Have you tried turning it off and on again?" Works mostly for me lol
If you're on Windows 8/8.1
Click to expand...
Click to collapse
on Windows 10 to
Good work
ciopik said:
on Windows 10 to
Good work
Click to expand...
Click to collapse
I'll add that now, thanks man
The firmware folder is not detected by Flashtool although I have put it in the correct folder...
I have tried hundred of times, i just dont understand
you dont need unlock bootloader for stock kernel\rom right?
If you want to upgrade you better use Xperia companion.
If you want to downgrade and use FlashTool and if you have a problem you better have unlocked bootloader.
Guys,
This is a good tutorial. but I met a dead end, i got " processing partition.sin finished with errors" message, any suggestion?
Thanks for the help, this is my first time flashing
Regards
I am facing same issue i have xperia z5 dual unlocked bootloader i have installed flashtool and drivers correctly and i have placed the ftf firmware in given directory also but flashtool not showing any thing but for m4 aqua i am able to see the ftf firmware please help me
---------- Post added at 09:36 AM ---------- Previous post was at 09:32 AM ----------
EMJI79 said:
The firmware folder is not detected by Flashtool although I have put it in the correct folder...
I have tried hundred of times, i just dont understand
Click to expand...
Click to collapse
Same problem here:crying:
when i get to step 6 it starts flashing but then my phone just switch on on itself and the process stop
my IMEI become unknown,
please help
hi, can i do this on Z5C Docomo (SO-02H)?
also can i flash global rom on that...?
Hey guys.
I have a Z5 Compact (E5823) that's stuck on android version 5.1.1. It never shows any available updates in the Software Update screen. I'd like to get it on 6.0 in the least just for the better permissions system it contains.
In searching for a way to update it, naturally I found this page and all the helpful info it contains. I've never been steered wrong by XDA in the past. I've always found information on this site helpful, and it works.
I've downloaded Flashtool.
I've followed all of the instruction for installation, including the annoying driver installation process for Windows 8.1.
I've downloaded multiple firmwares from Xperifirm.
I can get everything happening, and it looks to work when looking at the Flashtool screen. It says it's complete (just like the little image at the bottom of the initial post).
Nothing seems to have happened to the phone. I boot it back up and it's still running the same old 5.1.1. Flashtool runs through it's process very fast, as in a few seconds, not the half an hour suggested.
The phone came from Hong Kong as far as I can tell. It may have been a refubished phone, I can't be sure. I'm trying to get the Customised AU version 6.0 software on it.
What am I doing wrong? I don't know what else to try, and it's annoying me. PLEASE HELP.
Thanks. Paul.
plazmafire said:
Hey guys.
I have a Z5 Compact (E5823) that's stuck on android version 5.1.1. It never shows any available updates in the Software Update screen. I'd like to get it on 6.0 in the least just for the better permissions system it contains.
In searching for a way to update it, naturally I found this page and all the helpful info it contains. I've never been steered wrong by XDA in the past. I've always found information on this site helpful, and it works.
I've downloaded Flashtool.
I've followed all of the instruction for installation, including the annoying driver installation process for Windows 8.1.
I've downloaded multiple firmwares from Xperifirm.
I can get everything happening, and it looks to work when looking at the Flashtool screen. It says it's complete (just like the little image at the bottom of the initial post).
Nothing seems to have happened to the phone. I boot it back up and it's still running the same old 5.1.1. Flashtool runs through it's process very fast, as in a few seconds, not the half an hour suggested.
The phone came from Hong Kong as far as I can tell. It may have been a refubished phone, I can't be sure. I'm trying to get the Customised AU version 6.0 software on it.
What am I doing wrong? I don't know what else to try, and it's annoying me. PLEASE HELP.
Thanks. Paul.
Click to expand...
Click to collapse
You better ask your question in the Z5 section, you're more likely to have answers and it's the same process (sorry I don't remember guq I did at the time I had the phone).
Sent from my HTC U12+ using XDA Labs
EMJI79 said:
You better ask your question in the Z5 section, you're more likely to have answers and it's the same process (sorry I don't remember guq I did at the time I had the phone).
Sent from my HTC U12+ using XDA Labs
Click to expand...
Click to collapse
Will do.
Thanks.
Hey, man, I used 9.18.5 and it worked
Mamada. said:
Hey, man, I used 9.18.5 and it worked
Click to expand...
Click to collapse
Any idea where I can find a good copy of version 9.18.5?
Hey,
I'm experiencing an issue with Flashtool.
Last weekend I successfully rooted my Z5C with the "How to root Z5C - the new, less painful way"-guide.
Finally the Z5C was flashed with Nougat (Customized DE) and rooted with Magisk (rooted with SuperSU first, but then switched to Magisk), even with working TA partition.
After reading that the Australian Stock ROM doesn't have battery drain issues, I tried flashing that one. Unluckily I'm always getting the following error:
17/059/2019 18:59:25 - ERROR - Processing of system.sin finished with errors.
17/059/2019 18:59:25 - INFO - Ending flash session
17/059/2019 18:59:25 - ERROR - ERR_SEVERITY="MINOR";ERR_CODE="0017";ERR_DYNAMIC="80090012";
Now I can't boot my phone and TWRP seems to be gone too, so I can't restore the backup I did beforehand.
Any idea how to fix this error?
EDIT:
If anyone wonders: I managed to make it work by downloading the firmware again and using a different USB-cable on a different USB-port. Can't say which of those things exactly helped.

Categories

Resources