Database Users

[Q] I have a semi-bricked Vibrant and CANNOT FIX!!! HELP!!

I have been on this forum for 3 days going through many fixes for this problem.
NONE of them have worked.
I have been able to get into download mode, and the phone is recognized via com3 in odin.
I have re-flashed it with Eugenes no-brick version, then re-flashed it with tons of different stock and non-stock roms. It gets to various stages but does NOT work.
Any ideas or fixes will be a lifesaver!! Thanks in advance!

If you can still get into download mode and Odin recognizes your phone, flash it with these two files, they work:
http://androidspin.com/2010/08/09/how-to-restore-or-recover-your-samsung-vibrant/
DO NOT check the re-partition checkbox in odin.

why not repartition as long as you put pit file in pit field repartitoin like crazy if you like .
and repartition would be required if you coming from vodoo based kernel or if you ran anyother partiton than rfs .

Thanks for the quick response.
I tried these files again (I have tried them before) both with and without checking the re-partition box.
It boots then says Vibrant Samsung, then crashes. When I turn it back on it again crashes and turns itself off after the initial splash screen.
Any other ideas? It says that I passed in Odin

charge your phone ?

bartek25 said:
charge your phone ?
Click to expand...
Click to collapse
Hahaha ya I wish it was something so simple (maybe it is!) but it isn't that!

download this ! http://forum.xda-developers.com/showthread.php?t=734475
put JFD in to PDA
also downlaod PIT from the same lik i gave you and seriously charge your phone , and when you odin with the files i gave you from the link check rapartition . check phone efs clear and f.reset time and auto reboot .

come back report resoults if not we help more .

also by any chance u didnt play with ROM MANAGER when your wibrant was working and didnt play with repartiton while there right ?

The same crashing loop has happened with the latest advice. I checked Phone efs clear, re-partition, auto-reboot, and f.reset.time.
I used tVhe T959UJFD PDA, and the 512 Pit.
This phone has been plugged in for days I really doubt the battery is dead.
It just is a constant loop of crashing,h whether at te "off battery" logo or the vibrant splash screen.
The ONLY flash that has given me any different results is the "eugene no brick froyo" which takes me to the Android Recovery screen but does not allow me actually select any of the options.
I am starting to think there may be a hardware issue.

To be completely honest, I got this phone from a friend who had bricked it. If I can get it working then I have a galaxy on the cheap.
On the downside I have no idea what he did to brick it, and he is not tech-savvy enough to know himself.
I come from an original G1 and Cliq, so this is a tad different then I am used to.

from my point of view your phone is fried (it happends) or you are not doing something right or someone is more tech savy to help more , did you pull battery out for at least a min and let it sit and try again to boot ...

Ohhh i know whats wrong with the phone ........if your friends gave it to you broken i think good advice is ,download a program that can repartition hard drive from windows like any program that can do format of anydrive from windows i recomend PARAGON PARTITION MANAGER , find your phone while in the program and u need some skills lol for it but find the phone and click delete partiton after you do that click apply 2. after deletion and applaying the actions click on the phones formated drive in the program i recomended you and click submenu wher you will see create partiton click FAT32 apply 3. click again on the disk you created and click format . 4 done , its easy just get to hang of it

Good advice, I will work on this and get back to you later tonight.
Thanks again!

sounds like your friend bricked his phone from ROM MANAGER by creating EXT4 partion in phones memmory not on SD thats why phone cant find a drive to install the system , happend to me by my own mistake but i got it to work so if that help you You have free vibrant so try hard if not u have paper weight toy

if u dont want the phone i buy back from you for 20 bucks so i cant smash it against the wall , always want it to do that

Intim said:
The ONLY flash that has given me any different results is the "eugene no brick froyo" which takes me to the Android Recovery screen but does not allow me actually select any of the options.
Click to expand...
Click to collapse
Just so you know when you get to this point you need to make sure you had ADB set up on your pc and then plug in the phone and do adb reboot and that will boot the phone up, then you can shut it down and go into DL and flash back to stock. if you read the directions from Eugene's no brick it stated you need to do a adb reboot to get it to work, so you can fix it if your getting to the recovery of that flash.

Ok so for the paragon partition manager it does not recognize my phone's harddrive. Unsure how to fix that as it is just a wizard type program.
I have been able to recognize the phone in ADB, although I cannot push any files to the phone (access denied) and have not been able to get SU access either as I am assuming he did not have root when he bricked it.
Any ideas?

you dont need to push any files to the phone with the adb, after you flash the eugene rom and it boots into recovery you just need to load up your adb and type this
adb reboot
thats it, and it should reboot your phone and if it does boot up fine then you can flash back to stock with odin from there.

Did you perchance happen to have installed the Team Whiskey DOW kernel on this phone?
Your symptoms match the symptoms of quite a few others.
http://forum.xda-developers.com/showthread.php?p=11704550&posted=1#post11704550
http://forum.xda-developers.com/showthread.php?p=11680374#post11680374

[FIX] Cannot make calls or receive them and no sound on I9505

Hi all,
If you change ROM quite often and baseband too, most of the time everything goes smoothly, however, if you choose the wrong combination, you might encounter a very annoying issue: lost of the system sound, no ability of calling nor receiving phone calls.
I finally found a way to make my mobile sound working again (as it should) and I am able to call and receive phone calls as well. No reboots either.
When I started my investigation I had the following on my mobile:
ROM: [AOSP] Official 4.4.2 - S4 Google Edition - Final-R1.1 by jamal2367
Baseband: baseband XXUFNA1
Recovery: TWRP
Let me make the point. It is not because of the above settings that I had problems, but because of a combination of changing ROMs and baseband, probably only baseband.
When I was receiving a phone call only the vibration was working, no sounds, I couldn't slide the screen to answer properly, which means that I was able to slide, but the round icon of the slide could not catch the phone green icon. I could play no sound at all on videos, spotify, alarm, etc.; at the beginning I thought it was the current ROM, then
- I add to install Kies to try to restore the original firmware
- I changed it to another one
- I changed to CyanogenMod (and changed recovery to the default that comes with it: CWM)
- I rolled back to Samsung Stock edition (thank God I made a backup with TWRP months ago, before rooting)
Same damn issue and since I was there, I kept changing baseband with what I thought was the best for that particular (current) ROM. It is easy, you ask Mr. Google and he will tell you or you can try with http://www.sammobile.com/firmwares/2/
How can you fix it?
a. Download I9505XXUEMKF_I9505OXXEMK3_I9505XXUEMKF_HOME.tar.md5 and I9505XXUEMK8_I9505OXAEMK8_I9505XXUEMK8_HOME.tar.md5
b. Untar them in different directories
c. Use Heimdall - http://glassechidna.com.au/heimdall/ to flash all files in I9505XXUEMKF_I9505OXXEMK3_I9505XXUEMKF_HOME
c1. On Heimdal, click on the second tab _flash_, then browse your pit file, click on the button _add_ and choose the right partition. Do this for all the files inside the directory. Inside the _partitions (files)_ window you will have as many items as you have in the directory, in the example I put only 3, but you should have 12 of them in total (see image below)
- Under the partition ID, there is also a label/text that suggest you what file to choose.
- A note, MDM is for the modem, do not use MODEMST1 or MODEMST2
- If you do not have a pit, you can google it or as I did, use the forth tab _Utilities_, detect your device, and save as...under Download PIT.
c2. Then click on start to flash.
d. reboot in recovery and let CWM install unrecognized packages if asked. You might also find some red lines on the top left of the screen, but do not worry too much.
You might also find other red text _unable to unmount this or that_, after pressing start, but do not worry.
I tried to restart my mobile, but I was not able to restart it; in case you can, your stock Samsung ROM still has no sound. So
e. reboot in download and flash NON-HLOS.bin from the other folder I9505XXUEMK8_I9505OXAEMK8_I9505XXUEMK8_HOME. Use Partition Name _APNHLOS_ from partition Details in Heimdall.
f. the sounds is back
g. re-install your favourite recovery back
h. re-install your favourite ROM
I put back TWRP and [AOSP] Official 4.4.2 - S4 Google Edition - Final-R1.1 by jamal2367
Current baseband XXUEMKF. I will leave it as it is for a while, without changing it.
You can use Heimdall on windows too, but in case of driver problems use this to resolve the issue http://zadig.akeo.ie/
LTE and WiFi will work too.
You can get the two folders from this zip file: https://mega.co.nz/#!GARWHLDY!d2hrbCaVMKMLOXdNG6VfgkFMcjZclXJHTxe6amz0TNM
Note:
- When you flashed NON-HLOS.bin it might get the message stuck on _Rebooting device..._ and it does not give the impression that it finished. If you manual reboot and sometimes it means _remove the battery_, it will work.
- At the reboots note how the text on the top left changes during and after flashing.
At the booting now I get a warning text on the top-left (small text), it is something I can cope with or fix it later.
You can read in some posts that if _my phone number_ in unknown, under _status_ then you have problems with phone calls. I always had that one and still have it and it is working, so I wouldn't pay too much attention.
- if you have problems with heimdall, remove Kies (actually you can just remove it directly) and on mac, to remove some dependencies, run
sudo sh -
kextunload -b com.devguru.driver.SamsungComposite
kextunload -b com.devguru.driver.SamsungACMData
kextunload -b com.devguru.driver.SamsungACMControl
the uninstaller seems like it is working ok, so you might not need the above lines.

Or just flash the right non-hlos/wifi fix and that should fix your problem ...if you have a newbootloader just flash any latest non-hlos, but if you are still in oldbootloader feel free to flash a BMH1 non-hlos/wifi fix.. have a nice day.
Sent feom Hell ?

haven't really understood Step c1 Please @racoonlab

I cant find The pit File

Hi m_beek,
m_beek said:
I cant find The pit File
Click to expand...
Click to collapse
Have you tried the 4th tab of heimdall, utilities?
a. detect
b. save as
c. download
If you do not detect it, use the Zadig drivers first.
You can also try to have a look at http://forum.xda-developers.com/showthread.php?t=999097

What about getting "ERROR: Claiming interface failed!" after Clicking Start ?

m_beek said:
What about getting "ERROR: Claiming interface failed!" after Clicking Start ?
Click to expand...
Click to collapse
Do you have the Kies software installed? If yes, uninstall it and see also the last few lines of my post, to remove potential dependencies.
EDIT
Restart your machine too after the uninstall
R

Since I'm on W8 , I have never Installed Kies

m_beek said:
Since I'm on W8 , I have never Installed Kies
Click to expand...
Click to collapse
i. did you manage to get the pit?
ii when did you get that message, when flashing?
R

I couldn't get my Pit from _Utilities_ because of that, So I Googled "GT I9505 Pit" and download a Pit file, The After Managing Pit and Start flashing That What it's sayed
"This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
ERROR: Claiming interface failed!"

m_beek said:
I couldn't get my Pit from _Utilities_ because of that, So I Googled "GT I9505 Pit" and download a Pit file, The After Managing Pit and Start flashing That What it's sayed
"This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
ERROR: Claiming interface failed!"
Click to expand...
Click to collapse
Have you tried the Zadig drivers? To me it helped to:
- start the program
- see the list of the usb in used
- while the program was showing me the list, I unplugged the cable from one usb and attached to another one.
- run the program.
R

racoonlab said:
i. did you manage to get the pit?
ii when did you get that message, when flashing?
R
Click to expand...
Click to collapse
Ps. Odin Works, Can I Flash it with Odin ?

m_beek said:
Ps. Odin Works, Can I Flash it with Odin ?
Click to expand...
Click to collapse
probably with the latest yes.
http://www.xda-developers.com/android/mobile-odin-updated-to-version-4-new-features-and-devices/

racoonlab said:
probably with the latest yes.
http://www.xda-developers.com/android/mobile-odin-updated-to-version-4-new-features-and-devices/
Click to expand...
Click to collapse
Finally works
Ps. Its normal to get "Invalid Percent of Drawing progress Bar1"

Repulsa said:
Or just flash the right non-hlos/wifi fix and that should fix your problem ...if you have a newbootloader just flash any latest non-hlos, but if you are still in oldbootloader feel free to flash a BMH1 non-hlos/wifi fix.. have a nice day.
Sent feom Hell
Click to expand...
Click to collapse
Currently I have this one instaled I9505VJUHOK1. It was working fine with the stock ROM from SamMobile (http://www.sammobile.com/firmwares/download/61139/I9505VJUHOK1_I9505ZTOHOK1_ZTO/).
There is no sound at all on calls when using CM13.
What would you recommend?

[FACTORY FIRMWARE] [FLASH STOCK ROM] Nokia X2DS RM-1013 059V782 v2.1.0.13

NOTE-1:
I'm not a developer or something even near to that. All information provided here is copied from different internet sources like this & this & this and many others.
It's according to best of my knowledge and I'll not be responsible for any harm to you or your device. It works perfectly for me. You may try it on your own risk.
Save / backup your data before continuing. Whole device will be wiped.
NOTE-2:
If you have a custom recovery, install Stock ROM (v2.1.0.13 or v2.1.0.12) instead.
If you don't have a custom recovery, you may get one here or here.
If your device is bricked and can't boot into recovery or bootloader mode (read here what it is), proceed.
NOTE-3:
Given firmware link is v2.1.0.13 for device 059V782. There are some variants of Nokia X2DS (other product codes) which were officially updated from 2.1.0.11 to 2.1.0.12, so they dont support version 2.1.0.13.
Make sure your device supports 2.1.0.13 by googling your product code (written on back of device, see by removing back cover) or you may get in trouble. In case if you need 2.1.0.12, download it from some other link and follow the instructions given here.
NOTE-4:
Hard-bricked devices (with no buttons working, no Download Mode) may also be recovered by this method but with a slightly different procedure.
QFIL can also be used instead of NCS, but NCS feels a kinda little bit official way
REQUIREMENTS:
A PC with Windows and uninterrupted power supply. (I used Dell Inspiron 15R with Windows 8.1 and 10).
A USB data cable.
Fully charged phone, soft-bricked at maximum i.e. no recovery, no boot accessible
STEPS:
Download and Install NCS to your PC.
Copy UserGroupsConfiguration.cfg to "C:\Program Files (x86)\Nokia\Nokia Care Suite\Product Support Tool For Store 5".
Download Firmware and extract to "C:\ProgramData\Nokia\Packages\Products\RM-1013".
Launch NCS > Product Support Tool for Store 5.
At Sign-In screen, click Work Offline.
Disable Automatic Product Selection.
Go to File > Open Product and select RM-1013.
Click Programming > Recovery. Downloaded Firmware must be listed there.
Click Start and follow instructions. DO NOT INTERRUPT FLASHING PROCESS OR IT MAY HARD BRICK YOUR PHONE LEAVING IT USELESS.
Wait a few minutes and done. You have a newly purchased phone in your hands if all goes well.

Thanks for making a proper post for this.:good:

Devnikolus said:
Thanks for making a proper post for this.:good:
Click to expand...
Click to collapse
There are many others​ but mine is simple and solid

mirfatif said:
NOTE:
I'm not a developer or something even near to that. All information provided here is copied from different internet sources and according to best of my knowledge.
I'll not be responsible for any harm to you or your device. It works perfectly for me. You may try it on your own risk.
Save / backup your data before continuing. Whole device will be wiped.
REQUIREMENTS:
A PC with Windows and uninterrupted power supply. (I used Dell Inspiron 15R with Windows 8.1 and 10).
A USB data cable.
Fully charged phone, soft-bricked at maximum i.e. no recovery, no boot accessible
STEPS:
Download and Install NCS to your PC.
Copy UserGroupsConfiguration.cfg to "C:\Program Files (x86)\Nokia\Nokia Care Suite\Product Support Tool For Store 5".
Download Firmware and extract to "C:\ProgramData\Nokia\Packages\Products\RM-1013".
Launch NCS > Product Support Tool for Store 5.
At Sign-In screen, click Work Offline.
Disable Automatic Product Selection.
Go to File > Open Product and select RM-1013.
Click Programming > Recovery. Downloaded Firmware must be listed there.
Click Start and follow instructions. DO NOT INTERRUPT FLASHING PROCESS OR IT MAY HARD BRICK YOUR PHONE LEAVING IT USELESS.
Wait a few minutes and done. You have a newly purchased phone in your hands if all goes well.
Click to expand...
Click to collapse
Bro, i got an error with
Initializing WinUSB with device handle. The parameter is incorrect
Exception:
System.ComponentModel.Win32Exception (0x80004005): Initializing WinUSB with device handle. The parameter is incorrect
at Nokia.Merak.UsbDeviceIo.WinUsbIo.CheckError(Boolean expression, String message)
at Nokia.Merak.UsbDeviceIo.WinUsbIpen()
at Nokia.Merak.UsbDeviceIo.UsbDeviceIo..ctor(String devicePath)
at Nokia.Delta.Messaging..ctor(ConnectionDetails details)
at Nokia.CareSuite.PlugIns.DeltaRecovery.RecoveryDialog.RecoveryDialogModel.ChangeDeviceMode()
at Nokia.CareSuite.PlugIns.DeltaRecovery.RecoveryDialog.RecoveryDialogModel.Flash()
at Nokia.CareSuite.PlugIns.DeltaRecovery.RecoveryDialog.RecoveryDialogModel.<HandleDownloadVariantPackageCompleted>b__15(Object state)
please help phone not booting

himanagendra said:
Bro, i got an error with
Initializing WinUSB with device handle. The parameter is incorrect
Exception:
System.ComponentModel.Win32Exception (0x80004005): Initializing WinUSB with device handle. The parameter is incorrect
at Nokia.Merak.UsbDeviceIo.WinUsbIo.CheckError(Boolean expression, String message)
at Nokia.Merak.UsbDeviceIo.WinUsbIpen()
at Nokia.Merak.UsbDeviceIo.UsbDeviceIo..ctor(String devicePath)
at Nokia.Delta.Messaging..ctor(ConnectionDetails details)
at Nokia.CareSuite.PlugIns.DeltaRecovery.RecoveryDialog.RecoveryDialogModel.ChangeDeviceMode()
at Nokia.CareSuite.PlugIns.DeltaRecovery.RecoveryDialog.RecoveryDialogModel.Flash()
at Nokia.CareSuite.PlugIns.DeltaRecovery.RecoveryDialog.RecoveryDialogModel.<HandleDownloadVariantPackageCompleted>b__15(Object state)
please help phone not booting
Click to expand...
Click to collapse
You followed instructions 100%? Install NCS from my given link. It contains all necessary drivers including Emergency Driver. Use some other USB port on your PC. Try reinstalling NCS or try on different PC / different OS. You may also try QFIL if NCS doesn't work.

mirfatif said:
You followed instructions 100%? Install NCS from my given link. It contains all necessary drivers including Emergency Driver. Use some other USB port on your PC. Try reinstalling NCS or try on different PC / different OS. You may also try QFIL if NCS doesn't work.
Click to expand...
Click to collapse
thank god you are still there. okay here is the result.
Phone is not responding.
charging - > no indication, no screen
Volume down/up + power -> nothing. no response.
Do you know any softwares which can flash my phone without using volume up/down + power .
tnzzz for help

himanagendra said:
thank god you are still there. okay here is the result.
Phone is not responding.
charging - > no indication, no screen
Volume down/up + power -> nothing. no response.
Do you know any softwares which can flash my phone without using volume up/down + power .
tnzzz for help
Click to expand...
Click to collapse
Hmm it's hard bricked. No problem. Follow this thread. Things are explained more clearly there.

mirfatif said:
Hmm it's hard bricked. No problem. Follow this thread. Things are explained more clearly there.
Click to expand...
Click to collapse
thank you very much for your help but unfortunately it didn't work bcz as i told, nothing will comeup and even the buttons don't work.
In that case, please follow this thread

himanagendra said:
thank you very much for your help but unfortunately it didn't work bcz as i told, nothing will comeup and even the buttons don't work.
In that case, please follow this thread
Click to expand...
Click to collapse
Good. I suggested you to use QFIL already For me, both NCS and QFIL work but I didn't try any other product code firmware except 059V782 which is my device code.
What's your product code? 059V787 or 059V782? I'm gonna add a warning to my thread about this.
There are some devices which were officially updated from 2.1.0.11 to 2.1.0.12, so they don't support 2.1.0.13 as per my understanding.

mirfatif said:
Good. I suggested you to use QFIL already For me, both NCS and QFIL work but I didn't try any other product code firmware except 059V782 which is my device code.
What's your product code? 059V787 or 059V782?
Click to expand...
Click to collapse
Yeah...i thought you would give me a direct link. Anyways thanks for u help.
But bro, please mention that v2.1.0.13 don't suit for every Nokia x2 device. It doesn't suit the Indian version.

himanagendra said:
Yeah...i thought you would give me a direct link. Anyways thanks for u help.
But bro, please mention that v2.1.0.13 don't suit for every Nokia x2 device. It doesn't suit the Indian version.
Click to expand...
Click to collapse
Yes.
mirfatif said:
Good. I suggested you to use QFIL already For me, both NCS and QFIL work but I didn't try any other product code firmware except 059V782 which is my device code.
What's your product code? 059V787 or 059V782? I'm gonna add a warning to my thread about this.
There are some devices which were officially updated from 2.1.0.11 to 2.1.0.12, so they don't support 2.1.0.13 as per my understanding.
Click to expand...
Click to collapse

mirfatif said:
Yes.
Click to expand...
Click to collapse
Bro, do you know how to solve the sim 1 issue? i mean, my sim network is being recognized by the nokia x2 but, there is no signal for that.

himanagendra said:
Bro, do you know how to solve the sim 1 issue? i mean, my sim network is being recognized by the nokia x2 but, there is no signal for that.
Click to expand...
Click to collapse
Well, personally I never faced this issue. But you can try flashing @yoAeroA00 Custom Firmware. It flashes radio as well as other related partitions.

Quote:
Originally Posted by mirfatif
i cant find "C:\ProgramData\Nokia\Packages\Products\RM-1013".plz help me...

shuvo.khan97 said:
Quote:
Originally Posted by mirfatif
i cant find "C:\ProgramData\Nokia\Packages\Products\RM-1013".plz help me...
Click to expand...
Click to collapse
Create it if not found

Thx a lot, its helped me
Sent from my MI 5 using XDA-Developers Legacy app

For me please rm-1013:
2.0.0.11
059WOWO
thank you

how to connect mobile with pc in recovery mod or fast mod or normal mode i have custom rom and my sims are not working i want to stock rom again but when i select progmramming then recovery then there is no file shown in box for your information i attached img plz check and tell me the solution

lovegrw said:
how to connect mobile with pc in recovery mod or fast mod or normal mode i have custom rom and my sims are not working i want to stock rom again but when i select progmramming then recovery then there is no file shown in box for your information i attached img plz check and tell me the solution
Click to expand...
Click to collapse
Just flash stock rom zip before installing whole firmware

not able to get .xml file while flashing nokia x2
when i click on load xml in QFILL then i get new window but it shows no raw program file.
In reality it exist in extracted folder 'rm-1013 ' . When i type .xml in window it shows no file match.
please tell how to get this to proceed further.

Le pro 3 x720 brick?

Hi, since yesterday I have a big problem with my le pro 3, while charging the phone suddenly turned off. The system did not want to turn on, so I went into recovery (TWRP) and tried to format and upload a new rom, unfortunately during the flashing, a blue screen appeared. When changing the kernel, the flashing of the rom was done, but with the installation of the gapps it hung. I tried to install another rom, but it also spilled, with this addition, that I can not enter recovery, because artifacts appear or reboots.. Only fastboot works. With it, I tried to flash the kernel, recovery, but it did not do anything. I also used (TOOL ALL in ONE) and uploaded the stock rom, but the phone still does not work. Do you know what else could help, or is buying a new phone? Thanks for help

If you can use fast boot, your phone is not hard bricked. A brick is when you can not do anything , you will have a black screen and a red blinking light if a usb cable is connected.
Try pushing Twrp ( newest version) to the phone. If that is successful boot to recovery, fully wipe your phone, reboot to recovery and install you Rom> Gapps, and Magisk. I would suggest initially flashing Lineage 15.1. Once your phone is restored, flash whatever you would like.
If it doesn't work try another cable, or another port, or another computer. Computer needs to be up to date and you may need to temporarily disable antivirus, if the All in One tool isn't working its likely that your computer is blocking the install. especially if you are using Windows 10. All the program to be open within your firewall settings. Make sure its up to date and use AIO to update android drivers and adb.

I'm not giving anything, I still can't get into recovery

miichus said:
I'm not giving anything, I still can't get into recovery
Click to expand...
Click to collapse
Click reply to the person you are talking to otherwise, they will not receive a notification of your response.
Next, if you expect some help, be courteous, to people spending their own limited free time to help with your self created issue by clicking the thank you button.
Finally read this link: https://forum.xda-developers.com/showpost.php?p=76947769&postcount=4

tsongming said:
Click reply to the person you are talking to otherwise, they will not receive a notification of your response.
Next, if you expect some help, be courteous, to people spending their own limited free time to help with your self created issue by clicking the thank you button.
Finally read this link: https://forum.xda-developers.com/showpost.php?p=76947769&postcount=4
Click to expand...
Click to collapse
The operation in flashone goes well, but it still does not help. System and recovery does not boot, only fastboot

miichus said:
The operation in flashone goes well, but it still does not help. System and recovery does not boot, only fastboot
Click to expand...
Click to collapse
What does the log say?
if you are getting no errors at at and can only boot to fastboot try the All in One tool or use the QPST method to unbrick. Also, some posted versions of Qfil are corrupted. Did you use the version that I provided a link for?

tsongming said:
What does the log say?
if you are getting no errors at at and can only boot to fastboot try the All in One tool or use the QPST method to unbrick. Also, some posted versions of Qfil are corrupted. Did you use the version that I provided a link for?
Click to expand...
Click to collapse
For the second time I tried to use flashOne and the phone started up. When entering the pin code, the phone was stuck again. When I wanted to reboot, I could only enter fastboot again.

miichus said:
For the second time I tried to use flashOne and the phone started up. When entering the pin code, the phone was stuck again. When I wanted to reboot, I could only enter fastboot again.
Click to expand...
Click to collapse
For the second time I tried to use flashOne
Click to expand...
Click to collapse
Okay sure, I provided you with a link to the correct files to use. I.E Flash 2.0 and le_zl1_qfil_ufs_fix.zip
Twice you have mentioned that you are using flash One, when you should be using flash 2.0
What Pin code?
Your pin error sounds like you are either using the old Qfil ( its corrupted, and never worked for anyone. ) Or the technician repair rom did not complete. There will be a log file on the PC from Flash 2, not the phone, is port 9008 open in device manager?
There should be no pin code, if qfil was installed, all of your data would be wiped, did you encrypt the phone with 3rd party software?
Are also using the wrong version of Qfil?
Review these additional steps
https://forum.xda-developers.com/showpost.php?p=76100899&postcount=121

tsongming said:
Okay sure, I provided you with a link to the correct files to use. I.E Flash 2.0 and le_zl1_qfil_ufs_fix.zip
Twice you have mentioned that you are using flash One, when you should be using flash 2.0
What Pin code?
Your pin error sounds like you are either using the old Qfil ( its corrupted, and never worked for anyone. ) Or the technician repair rom did not complete. There will be a log file on the PC from Flash 2, not the phone, is port 9008 open in device manager?
There should be no pin code, if qfil was installed, all of your data would be wiped, did you encrypt the phone with 3rd party software?
Are also using the wrong version of Qfil?
Review these additional steps
https://forum.xda-developers.com/showpost.php?p=76100899&postcount=121
Click to expand...
Click to collapse
I am using flashone 2.0 and flashing from your link, the file "le_zl1_qfil_ufs_fix.zip". Port 9008 is open. After three flash in 2.0 flash, I could enter recovery, but when flashing custom rom, a blue screen appeared.

Not enough information, did you follow all of the steps? You can't just flash a Rom after unbricking.
To be clear
You restored the phone, booted into the system, turned on developer options, checked oem unlocking, booted into recovery, and did a factory reset to repair the storage as outlined in my instructions link?
Then booted into the system again, turned on developer options, checked oem unlocking, checked that storage is accurate?
From this point you start over, if your storage issue isn't fixed you will get a blue screen.
After you have perform those steps you should be able to use the all in one tool to check that the bootloader is unlocked, install the latest TWRP, compatible Rom, Gapps and latest magisk.
If you still have issues after all of that. No doubt, its hardware related. It could be one part or several parts. Time to buy a new phone.
Sent from my Pixel XL using XDA Labs

tsongming said:
Not enough information, did you follow all of the steps? You can't just flash a Rom after unbricking.
To be clear
You restored the phone, booted into the system, turned on developer options, checked oem unlocking, booted into recovery, and did a factory reset to repair the storage as outlined in my instructions link?
Then booted into the system again, turned on developer options, checked oem unlocking, checked that storage is accurate?
From this point you start over, if your storage issue isn't fixed you will get a blue screen.
After you have perform those steps you should be able to use the all in one tool to check that the bootloader is unlocked, install the latest TWRP, compatible Rom, Gapps and latest magisk.
If you still have issues after all of that. No doubt, its hardware related. It could be one part or several parts. Time to buy a new phone.
Sent from my Pixel XL using XDA Labs
Click to expand...
Click to collapse
Once we managed to load the system, which hung up after 3 seconds and the whole situation started again. Failed to reload the system or enter recovery. I did all the steps in turn. After the system startup I did not even manage to enter the settings, because it has already hung up and restarted.

miichus said:
Once we managed to load the system, which hung up after 3 seconds and the whole situation started again. Failed to reload the system or enter recovery. I did all the steps in turn. After the system startup I did not even manage to enter the settings, because it has already hung up and restarted.
Click to expand...
Click to collapse
That sucks!
Its either that the partitions are inaccurate or you have hardware problems.
If its partitions, its not something that I have experience with. However, I did find this link; which has instructions for resolving partition issues using the MiniTool Partition Wizard and HDD Raw Copy Tool. https://www.leakite.com/2016/06/revised-how-to-unbrick-qualcomm-android.html

tsongming said:
That sucks!
Its either that the partitions are inaccurate or you have hardware problems.
If its partitions, its not something that I have experience with. However, I did find this link; which has instructions for resolving partition issues using the MiniTool Partition Wizard and HDD Raw Copy Tool. https://www.leakite.com/2016/06/revised-how-to-unbrick-qualcomm-android.html
Click to expand...
Click to collapse
Hi tsongming Where do I get this files ???
* prog_emmc_firehose_8936.mbn (I think for our x720 has to be prog_emmc_firehose_8916.mbn)
* rawprogram0.xml
* patch0.xml
I have seen this procedure on different sites but none of them provide this files
I hope you can help me
Thanks in advance

mavelino said:
Hi tsongming Where do I get this files ???
* prog_emmc_firehose_8936.mbn (I think for our x720 has to be prog_emmc_firehose_8916.mbn)
* rawprogram0.xml
* patch0.xml
I have seen this procedure on different sites but none of them provide this files
I hope you can help me
Thanks in advance
Click to expand...
Click to collapse
They should download automatically, if you follow the instructions on those previous Links . The instructions should show which folders the files are located in.
Luckily, I saved these files the last time I de-bricked someones phone.
Here is the link to my Google Drive: https://drive.google.com/open?id=1mjvi_FR4Xh9QfSg6imMLduQ6p3zP2e_u
See the Thanks button: Click it, send cash or both.

tsongming said:
They should download automatically, if you follow the instructions on those previous Links . The instructions should show which folders the files are located in.
Luckily, I saved these files the last time I de-bricked someones phone.
Here is the link to my Google Drive: https://drive.google.com/open?id=1mjvi_FR4Xh9QfSg6imMLduQ6p3zP2e_u
See the Thanks button: Click it, send cash or both.
Click to expand...
Click to collapse
Noup they do not download automatically (I followed the instructions), I tried flashone tool procedure in a windows 7 computer and did not work (I already tried this a lot of times on to differente laptops with windows 10), I have not tried the qfil procedure because I do not have the files I mentioned before. Please if you have them upload them (* prog_emmc_firehose_8996.mbn* rawprogram0.xml* patch0.xml)
Thanks in advance

mavelino said:
Noup they do not download automatically (I followed the instructions), I tried flashone tool procedure in a windows 7 computer and did not work (I already tried this a lot of times on to differente laptops with windows 10), I have not tried the qfil procedure because I do not have the files I mentioned before. Please if you have them upload them (* prog_emmc_firehose_8996.mbn* rawprogram0.xml* patch0.xml)
Thanks in advance
Click to expand...
Click to collapse
All I have is in the link you just responded to.
if that doesn't work try unpacking the Qfil and and see if you can just extract them.
I will look further when I get back home.

i also have an bricked LEX 3 Pro . i bought it as an X722 but of cause iam not shure . could also be an X720. i can not find the difference.
so Phone has only fastboot.
when i plug in usb cable it just reboot every 10 sec . no charging sreen appears
i flash Qfil, but not helped it stay the same

Device not detecting in Adb devices but gets detect in fastboot devices

Hi, everyone I tried to flash a new recovery on X00T but before I did this I Wiped all the data except internal storage. I Flashed the new recovery (completely forget about there being no OS) I rebooted to recovery and ignored the no OS message as the device rebooted I came on a black screen even the fast boot mode screen was black. I had no idea what to do so I tried to install the old TWRP from power shell/Adl so I could have a recovery and then install Custom rom again from recovery.
But there when I try to flash a file with command
-> Fastboot flash Recovery ....(..= file name)
It is shown completed on pc but on android even after rebooting I can't get anything except the black screen. This is what I get when I enter the following commands
-> fastboot devices
My devices number is shown
but if I type.
-> adl devices
My device is not shown.
But when I press the recovery buttons on device adl devices Is able to recognise device as a recovery screen device.
And the extra bonus on this is when I try to flash rom or fimware from adl. It says unable to read zip file.
So can anyone tell me if there is a way to fix this unable to read zip file problem. (I have tried uninstalling and reinstalling drivers from device manager & tried installing 64 bit files also)
Is there a command to flash rom from recovery. Or any way to fix this black screen
Thanks to everyone for reading any advice would be really helpful at this time.

Try using Asus Flash Tool to flash stock ROM

Tianhe said:
Try using Asus Flash Tool to flash stock ROM
Click to expand...
Click to collapse
Thanks for helping, Will surely try it. Can you please provide the link from where i can download flash tool?

Xda user 101 said:
Thanks for helping, Will surely try it. Can you please provide the link from where i can download flash tool?
Click to expand...
Click to collapse
I am not sure if posting external links (except hosting sites) is permitted. A simple google search or search within XDA will give you the results. In case you face difficulty, PM me.

Try to use this adb
If it still doesn't get detected, maybe use usb hub.
I wrote a thread guiding people on how to install stuff and my experience (issues) that is similar to yours. Not sure if my thread will help ya though

Vysair said:
Try to use this adb
If it still doesn't get detected, maybe use usb hub.
I wrote a thread guiding people on how to install stuff and my experience (issues) that is similar to yours. Not sure if my thread will help ya though
Click to expand...
Click to collapse
Bro tried as you said but didn't worked but finally found a solution. Now device is on and working again.

If anyone else face this issue I followed this thread https://forum.xda-developers.com/as...uide-revert-to-stock-rom-lock-t3798420/page46
It worked on my phone it is on again. Will have to root again but learned my lesson will never try new twrp when there is no os installed. :laugh:

thanks you Tianhe and Vysair for your advice for solving the issue.