Database Users

SM-G900V unknown baseband and restart

Hi,
Phone restarts automatically with no imei and unknown baseband, I download stock firmware 4.4.2 and install on it but same situation,
any suggestion or help pls,
thanks
br

Isn't IMEI used for phone identification along with MEID? If thats blank, would it be an issue on Verizons side?

Elite49 said:
Isn't IMEI used for phone identification along with MEID? If thats blank, would it be an issue on Verizons side?
Click to expand...
Click to collapse
imei is unknow

2 Choices
nsnobel2 said:
imei is unknow
Click to expand...
Click to collapse
Hi
I don't know if you've fixed your issue with your g900v or not, but i have the same problem and the same phone and obviously the same symptoms ...
As far as I've tried, nothing worked not ODIN flashing ROMs, or QPST to write IMEI or EFS professtiona ADB .... etc.
What I've come to know is this :
1- keep the phone in a safe place till next months reveal a solution through developers here or elsewhere.
2- Flash the Original Samsung Verizon Rom ( Full Package with efs and bootloader mounts and all partitions " Clean Flash" ) which costs about 100$ .
3- Change the board for a (200$) new one .
So, I would try to pay the 100$ and flash the original ROM, and comeback to tell if it solved the Problem.
I wish if you share any different approach or feedback . I would love to hear it .
Bye

It could possibly be that your EFS folder is damaged. This is where your IMEI and Baseband info is stored. If that's the case for your device, these steps should work. I've done this on two phones (one being an S5) and it fixed this problem.
I'm assuming that you're rooted. If not then you'll need to root your device first. And you need to have debugging enabled. What this does is backups the files from the EFS folder, repairs the partition tables, then restores the files to the repaired folder.
1. Connect the phone to your computer. (Windows)
2. Download this: https://www.dropbox.com/s/v2h5dzisjd0rgj5/EFS_Professional_2.1.73_Release.zip?dl=0
3. Extract and run the program
4. Click EFS Professional... It will open a window showing that it found your phone
5. Click on the Backup Tab and make sure all of the partitions are checked, and your Device Filter is recognized
6. Hit the Backup button to backup the EFS folder
7. After that's done, click the Restore button and it will restore your files to the EFS folder.
I hope this helps you.

There used to be a tool for the Note 2 I believe, maybe S4, that would let you re-write your EFS if it accidentally got erased. Not a backup/restore deal, but a tool to key in your IMEI and it would write it to the phone. Maybe research that tool for a fix?

joshw0000 said:
There used to be a tool for the Note 2 I believe, maybe S4, that would let you re-write your EFS if it accidentally got erased. Not a backup/restore deal, but a tool to key in your IMEI and it would write it to the phone. Maybe research that tool for a fix?
Click to expand...
Click to collapse
Was it a tool specifically for the Note 2, or multiple Samsung devices, or maybe a universal program like CDMA Workshop? I love that program. It's what I use when it comes to actually entirely rewriting files like this. Most of the time a full rewrite isn't needed though if the EFS folder has just been damaged. Which "damaged" is totally the wrong word here, but that's what it's called for some reason. I really don't even know how it happens, but I do know when it does, it usually just jumbles and/or fragments the info in the folder and needs to be put back in it's correct order. Kind of like defragging in Windows. Just a tool like you're talking about would definitely be cool for me to have though. I shall start my quest to find it. Lol

Please some help
Any luck yet ???
Got the same issue here, and none of the threads here worked .

Same problem
Hello,
I have the exact same problem. I bought the phone here in Mexico, and the phone came with erased EFS folder. Phone restarts automatically when screen turns off. When I'm using the phone, it works just fine, but some seconds after screen goes off, phone restarts automatically. EFS folder is messed up, I've tried out a lot EFS restoring tools with no luck.
I tried QPST but it does not detect the phone, only appears "?" and "No phone" blinking. The same happens with DFS Tool.
I will try to look for that tool joshw0000 talks about.
I hope we can find out a solution for this excellent phone.
Bye.

Hey ...
I did a factory reset and cache wipe, and now the phone stopped restarting when the screen goes off, but still got the "Unknown" issues.
But at least I got rid of the annoying restarts.
570 ppl read this and still no answer, I got to admit ... it's tough.
Sent from my SM-G900V using XDA Free mobile app

Samsung Galaxy Note 3 (SM-N900) - Rooting failed (Odin stuck), need to recover

Hi all,
So I've decided to root my Exynos International Galaxy Note 3 (SM-N900) using Chainfire's CF-Auto-Root. All went well until Odin got stuck at cache.img, then fails after a couple of minutes. I unplug the phone and restart it, it then displays "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again" whenever I try to boot. I can access download mode again, but not recovery. My phone is stock 4.2.2.
It's the first time I have such a problem, I flashed a couple of phones before without any trouble. I searched XDA for a solution and tried other Odin versions, different cable/ports, even tried on another computer: Same issue. Stuck at cache.img. I can't get my phone to work again. Some people suggested it might have something to do with USB debugging, but I can't remember if I left it enabled or disabled.
I didn't back any of my data (I didn't expect the root to fail...) and retrieving my phone, rooted or not, is of the utmost importance. Please avoid posting solutions that involve data loss.
Feel free to ask about anything I might have left out.
Thanks!

GST_Diandre said:
Hi all,
So I've decided to root my Exynos International Galaxy Note 3 (SM-N900) using Chainfire's CF-Auto-Root. All went well until Odin got stuck at cache.img, then fails after a couple of minutes. I unplug the phone and restart it, it then displays "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again" whenever I try to boot. I can access download mode again, but not recovery. My phone is stock 4.2.2.
It's the first time I have such a problem, I flashed a couple of phones before without any trouble. I searched XDA for a solution and tried other Odin versions, different cable/ports, even tried on another computer: Same issue. Stuck at cache.img. I can't get my phone to work again. Some people suggested it might have something to do with USB debugging, but I can't remember if I left it enabled or disabled.
I didn't back any of my data (I didn't expect the root to fail...) and retrieving my phone, rooted or not, is of the utmost importance. Please avoid posting solutions that involve data loss.
Feel free to ask about anything I might have left out.
Thanks!
Click to expand...
Click to collapse
I think you'll have to flash an official Sammy Firmware to get past the error, although if you look in the Note 3 Android Development, I recall seeing some deodexed, rooted firmware that is supposed to work from Odin. Not sure if any of them are for exynos version though.
Data? I keep everything I can on the extSD for exactly this reason. You should be able to remove the card and put it in a card caddy and read it in a PC and copy out your media etc. The root process shouldn't have overwritten anything you need.
For rooting, maybe DL the SuperSU zip file Chainfire's website and flash it in Recovery once you're up and running? I use TWRP but Philz or CWM recoveries will do it.

Journyman16 said:
I think you'll have to flash an official Sammy Firmware to get past the error, although if you look in the Note 3 Android Development, I recall seeing some deodexed, rooted firmware that is supposed to work from Odin. Not sure if any of them are for exynos version though.
Data? I keep everything I can on the extSD for exactly this reason. You should be able to remove the card and put it in a card caddy and read it in a PC and copy out your media etc. The root process shouldn't have overwritten anything you need.
For rooting, maybe DL the SuperSU zip file Chainfire's website and flash it in Recovery once you're up and running? I use TWRP but Philz or CWM recoveries will do it.
Click to expand...
Click to collapse
I see. So in newbie terms, if I flash the official firmware I have from SamMobile, I should have my phone back running with all my apps & data? Also, any hint about why rooting didn't work in the first place?
After this tragic experience with Odin, I'm gonna forget root for now, maybe update to Lollipop then think about rooting again.
Thanks for replying !

GST_Diandre said:
I see. So in newbie terms, if I flash the official firmware I have from SamMobile, I should have my phone back running with all my apps & data? Also, any hint about why rooting didn't work in the first place?
After this tragic experience with Odin, I'm gonna forget root for now, maybe update to Lollipop then think about rooting again.
Thanks for replying !
Click to expand...
Click to collapse
Did the official firmware work when you did it? If so, download Phone INFO Samsung from Play and use it to check what hardware you actually have.
I have had issues with CF-Auto root recently so I flash Stock, then the TWRP md5 file (in Odin 3.09) then I boot into Recovery and flash SuperSU. That gives me Recovery and root. You normally have to run SuperSU when you start so it can update.
U[pdating to LP is a good idea - most of the things going on in Dev are now LP versions.

Journyman16 said:
Did the official firmware work when you did it? If so, download Phone INFO Samsung from Play and use it to check what hardware you actually have.
I have had issues with CF-Auto root recently so I flash Stock, then the TWRP md5 file (in Odin 3.09) then I boot into Recovery and flash SuperSU. That gives me Recovery and root. You normally have to run SuperSU when you start so it can update.
U[pdating to LP is a good idea - most of the things going on in Dev are now LP versions.
Click to expand...
Click to collapse
I didn't flash the official firmware ever. Before trying to root with Odin and getting it stuck, I never flashed or modified anything internally on this phone.
Obviously, I can't use Phone INFO because my phone is stuck at BSOD.
I will upgrade to Lollipop, once I can get my phone working as it was. For now I'm still hesitating to flash the official firmware. I don't know if that would wipe the apps or just get back the phone as it was.

GST_Diandre said:
I didn't flash the official firmware ever. Before trying to root with Odin and getting it stuck, I never flashed or modified anything internally on this phone.
Obviously, I can't use Phone INFO because my phone is stuck at BSOD.
I will upgrade to Lollipop, once I can get my phone working as it was. For now I'm still hesitating to flash the official firmware. I don't know if that would wipe the apps or just get back the phone as it was.
Click to expand...
Click to collapse
It will wipe Apps and Data - it makes your phone like you just bought it.
I didn't realise it was stuck in that mode - just thought that happened whenever you tried to flash something.
First thing. Turn phone off. Take back off and remove battery for 10 secs or so. Turn it on holding down Vol Down + Home + Power - release when DL screen shows and press Vol Down. If that gets you into the phone, spend some time saving your data to extSD.
I use Call Logs Backup & Restore, SMS Backup & Restore, I export my Contacts to ext storage. I use TiBu to backup all my apps to a folder on extSDCard. If you are on Stock ROM, you should be able to set your camera to save to extSDCard but you need a file explorer (I use ES File Explorer) to copy your current DCIM folder across - other than that, look for music, documents and video folders on internal memory)
If it doesn't open the phone for you, & your data is important, take card out and use adapter to save data onto a computer.
Go to Sammobile and download the proper official firmware for your phone - note you need to set up a free account before you can DL.
Download Odin 3.09 Run Odin
Then repeat the phone process but this time press Vol Up when at the DL screen. It is important to have the phone Off and electrically flat before attempting a firmware update.
Connect phone to PC - Odin should recognise it. If it doesn't you probably need the Samsung USB Drivers so get them and install them.
Then connect phone again. Click AP and find your DL from Sammobile. Wait for it to load then press Start. Wait... it will reboot and usually sits on the logo for quite some time.
Set up your phone, and restore or reinstall your apps.
Rotsa Ruck!

Journyman16 said:
It will wipe Apps and Data - it makes your phone like you just bought it.
I didn't realise it was stuck in that mode - just thought that happened whenever you tried to flash something.
First thing. Turn phone off. Take back off and remove battery for 10 secs or so. Turn it on holding down Vol Down + Home + Power - release when DL screen shows and press Vol Down. If that gets you into the phone, spend some time saving your data to extSD.
I use Call Logs Backup & Restore, SMS Backup & Restore, I export my Contacts to ext storage. I use TiBu to backup all my apps to a folder on extSDCard. If you are on Stock ROM, you should be able to set your camera to save to extSDCard but you need a file explorer (I use ES File Explorer) to copy your current DCIM folder across - other than that, look for music, documents and video folders on internal memory)
If it doesn't open the phone for you, & your data is important, take card out and use adapter to save data onto a computer.
Go to Sammobile and download the proper official firmware for your phone - note you need to set up a free account before you can DL.
Download Odin 3.09 Run Odin
Then repeat the phone process but this time press Vol Up when at the DL screen. It is important to have the phone Off and electrically flat before attempting a firmware update.
Connect phone to PC - Odin should recognise it. If it doesn't you probably need the Samsung USB Drivers so get them and install them.
Then connect phone again. Click AP and find your DL from Sammobile. Wait for it to load then press Start. Wait... it will reboot and usually sits on the logo for quite some time.
Set up your phone, and restore or reinstall your apps.
Rotsa Ruck!
Click to expand...
Click to collapse
Thank you, I just tried going into download mode and pressing vol down, still get the same BSOD. I guess that means phone cannot be recovered as it is...
I'm backing up my stuff now. I have no problem backing up contacts/SMS/etc.., but can you tell me whether I can still back up applications and restore them as they were using Titanium Backup on PC ? I know this should have been done before even soft-bricking my phone, but since it inaccessible to run the app on it...
I already have the official firmware waiting to be installed, just need to be sure about TiBU and that I backed up everything correctly Thanks for answering !

GST_Diandre said:
Thank you, I just tried going into download mode and pressing vol down, still get the same BSOD. I guess that means phone cannot be recovered as it is...
I'm backing up my stuff now. I have no problem backing up contacts/SMS/etc.., but can you tell me whether I can still back up applications and restore them as they were using Titanium Backup on PC ? I know this should have been done before even soft-bricking my phone, but since it inaccessible to run the app on it...
I already have the official firmware waiting to be installed, just need to be sure about TiBU and that I backed up everything correctly Thanks for answering !
Click to expand...
Click to collapse
That depends... TiBu can only recover what you've saved (obvious I know...) and only if it didn't get wiped in the new firmware flash. (which it will if you didn't choose extSDCard for the backups)
Other than that, once your phone is set up and your Google account active, Play Store will DL all your apps.

Journyman16 said:
That depends... TiBu can only recover what you've saved (obvious I know...) and only if it didn't get wiped in the new firmware flash. (which it will if you didn't choose extSDCard for the backups)
Other than that, once your phone is set up and your Google account active, Play Store will DL all your apps.
Click to expand...
Click to collapse
Okay great So where exactly do I get TiBu for pc?

GST_Diandre said:
Okay great So where exactly do I get TiBu for pc?
Click to expand...
Click to collapse
Unfortunately it's a Play Store app, so first you have to get your phone working.
You could try the attached from Recovery but I have no idea if it would work as it's from my rooted CM12.1 system.

Journyman16 said:
Unfortunately it's a Play Store app, so first you have to get your phone working.
You could try the attached from Recovery but I have no idea if it would work as it's from my rooted CM12.1 system.
Click to expand...
Click to collapse
Recovery isn't working for me... The only thing I can access on the phone is Download mode.
I guess it's lost? :/

GST_Diandre said:
Recovery isn't working for me... The only thing I can access on the phone is Download mode.
I guess it's lost? :/
Click to expand...
Click to collapse
The only other thing I can think of would be using ADB over USB but I don't know if that would work with DL mode or if it is only for Recovery. You'd have to search and learn how to use it.
So maybe time to just get the phone working and make sure for future you have backups?

Journyman16 said:
The only other thing I can think of would be using ADB over USB but I don't know if that would work with DL mode or if it is only for Recovery. You'd have to search and learn how to use it.
So maybe time to just get the phone working and make sure for future you have backups?
Click to expand...
Click to collapse
SOLVED. I can't believe how easy it was. I was about to flash it over from scratch but then it struck me.
Chainfire ships Odin with all its root bundles, a version where you cannot untick "Auto Reboot". Because of Auto Reboot being ticked, Odin freezes at "cache.img". It might not freeze for some people but for me, having Auto Reboot activated causes the freeze
Downloading a different version of Odin (any version, I used 3.09) that allows changing parameters and LEAVING EVERYTHING UNTICKED BUT F. RESET TIME works like a charm.
Don't forget to reboot your phone after Odin displays PASS or RESET (Long press power).
I'm going to PM Chainfire about this, and tell a max of people about it.
Thank you for your support
EDIT: Also going to NANDroid my phone. I'm tired of panicking over failed roots

just a helpful little tip

so samsung has reps at most best buys that will help you free of charge ( i had to go there when i first started rooting because i softbricked my phone and had no idea what to do and needed it the next day so if you dont feel like waiting or need something done that second or just dont wanna post on here you can always head up there and just tellem your question and theyll try and help you with what you need

Veid71 said:
so samsung has reps at most best buys that will help you free of charge ( i had to go there when i first started rooting because i softbricked my phone and had no idea what to do and needed it the next day so if you dont feel like waiting or need something done that second or just dont wanna post on here you can always head up there and just tellem your question and theyll try and help you with what you need
Click to expand...
Click to collapse
Thank you for your post. I soft bricked my S5 (bootloop) and will keep this in mind. For now I am at home and want to see if I can figure it myself. I need help to push a working ROM to my device SD card. I found a toolkit on root page http://forum.xda-developers.com/showpost.php?p=64744448&postcount=2
***Is there a tutorial that can help me know how to use the toolkit?

cyberfem said:
Thank you for your post. I soft bricked my S5 (bootloop) and will keep this in mind. For now I am at home and want to see if I can figure it myself. I need help to push a working ROM to my device SD card. I found a toolkit on root page http://forum.xda-developers.com/showpost.php?p=64744448&postcount=2
***Is there a tutorial that can help me know how to use the toolkit?
Click to expand...
Click to collapse
http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370
check that out if you werent previously rooted if you were previously rooted then try this
Use Odin to flash the lollipop kernel you were using. Then go into the stock recovery (hold Home + Vol UP and Power) and clear the cache and reboot. If that doesn't work, go back into the stock recovery, clear cache and select factory reset, then reboot. That should allow MOAR (whatever rom you want i stole this post from one of my other topics about when i softbricked mine) to boot, then you can reinstall SafeStrap Lollipop.

If you're getting any kind of logo screen showing up on boot, you are only "soft" bricked (not "hard" or permanently bricked) and you can fix it easily.
If you're only getting a logo, try what Veid71 said in the post above mine. If that doesn't work, then worst case you just need to flash a factory restore image with Odin and start over.
A word of caution, though: if your firmware version was updated to BOE1, BOG5, BOK3, do NOT flash an earlier factory image or you will brick because after BOD the bootloader was locked and you can't downgrade it.

painiac said:
If you're getting any kind of logo screen showing up on boot, you are only "soft" bricked (not "hard" or permanently bricked) and you can fix it easily.
If you're only getting a logo, try what Veid71 said in the post above mine. If that doesn't work, then worst case you just need to flash a factory restore image with Odin and start over.
A word of caution, though: if your firmware version was updated to BOE1, BOG5, BOK3, do NOT flash an earlier factory image or you will brick because after BOD the bootloader was locked and you can't downgrade it.
Click to expand...
Click to collapse
I get the logo screen like it is turning on then it goes to recovery mode options. I can get to Download mode and Odin has a blue port connection but my Win8 and Win7 PCs do not see the device at all, so I cant' flash in Odin. Background - I attempted to root using jrkruse method and got stuck and never rooted. Anyone know a way around this maybe using the external SD card?

cyberfem said:
I get the logo screen like it is turning on then it goes to recovery mode options. I can get to Download mode and Odin has a blue port connection but my Win8 and Win7 PCs do not see the device at all, so I cant' flash in Odin. Background - I attempted to root using jrkruse method and got stuck and never rooted. Anyone know a way around this maybe using the external SD card?
Click to expand...
Click to collapse
When it boots into the recovery mode options, try clearing cache and then reboot. If that doesn't work, do it again, clearing cache and also factory reset. That may allow your phone to boot back up normally.
The SDcard Unbrick method is only needed if your phone cannot boot into Download mode. In this case, it wouldn't help you because your phone is functioning in that regard.
When you have the phone in Download mode, your computer won't show it as a device in "My Computer" because it's not connected as a media device., but software that knows how to look for it can see it. If Odin is lighting up blue in the first ID:COM box, it IS seeing the phone and you will be able to flash to it.
If you're to a point where you need to flash a factory restore image, click the "AP" button in Odin to select it. The image needs to be one that ends with a file extension "tar.md5", or Odin can't see it. If what you've downloaded is a zip archive, the image is inside that and you need to extract it first. Use the image in "step 2" of the root thread

I figured out what went wrong from your response thanks! I had saved the .tar.md5 on the external SD card rather than pc. Now attempting to re-root, .bat sees device but doesn't root.

cyberfem said:
I figured out what went wrong from your response thanks! I had saved the .tar.md5 on the external SD card rather than pc. Now attempting to re-root, .bat sees device but doesn't root.
Click to expand...
Click to collapse
yeah its really annoying youll have to unplug and plug it back in and x out of the thing like 20 times before it acutually does it

Did I Brick my new Verizon Galaxy S7 edge? SM-G935VV??

Recently I had tried rooting my phone and was certainly successful at it until I wanted to get Superman rom. Since then I downloaded it on my computer ran it on twrp on my phone but then after going through the configuration screen it booted into installation mode but then failed after a minute, resulting my phone to go into not being able to start up. The screen flashed something along the lines of "not able to load with secure boot". Secure boot must've turned on or something like that because it was totally off when I started the process, and I couldn't go into my phone besides download mode/recovery. Since I booted it up in download mode, erased partition all the options in recovery mode, and loaded it up original firmware based on my phone in odin3. Then I loaded the original firmware file being called "VZW_G935VVRU1APB1_G935VVZW1APB1_CL7042442_QB8595625_REV02_user_low_ship_MULTI_CERT.tar.zip" unzipped and put all the necessary parts in their places, AP, BL ,CP, CSC. After trying it multiple times I was dumb and clicked re partition because odin3 would fail to flash until I re partitioned it. Ever since then my phone is blank and no commands work. My phone is a Samsung S7 Edge that was rooted, I have an micro SD if there is a way of unbricking my phone...

Go to the service center
I think "Box" will fix it
Sent from my SM-G7102 using Tapatalk

why did you try to flash superman rom? It is for exynos chipset.

nolanshaye said:
Recently I had tried rooting my phone and was certainly successful at it until I wanted to get Superman rom. Since then I downloaded it on my computer ran it on twrp on my phone but then after going through the configuration screen it booted into installation mode but then failed after a minute, resulting my phone to go into not being able to start up. The screen flashed something along the lines of "not able to load with secure boot". Secure boot must've turned on or something like that because it was totally off when I started the process, and I couldn't go into my phone besides download mode/recovery. Since I booted it up in download mode, erased partition all the options in recovery mode, and loaded it up original firmware based on my phone in odin3. Then I loaded the original firmware file being called "VZW_G935VVRU1APB1_G935VVZW1APB1_CL7042442_QB8595625_REV02_user_low_ship_MULTI_CERT.tar.zip" unzipped and put all the necessary parts in their places, AP, BL ,CP, CSC. After trying it multiple times I was dumb and clicked re partition because odin3 would fail to flash until I re partitioned it. Ever since then my phone is blank and no commands work. My phone is a Samsung S7 Edge that was rooted, I have an micro SD if there is a way of unbricking my phone...
Click to expand...
Click to collapse
I don't know it is work for you or not but if you can enter download mode you can try this full firmware with pit file..
http://us.samfirm.net/threads/g935v...35vvru1apb1-vzw-android-6-0-1-marshmallow.73/

ecg803 said:
why did you try to flash superman rom? It is for exynos chipset.
Click to expand...
Click to collapse
Because im a noob, I didn't realize...

I understand. I used to be anoob back in the day messing with s3 and hard bricked it. I had to send it off to get jtag. I wonder if you had a jig could it force it into download mode. I have one somewhere and just can not seem to find it.
Sent from my SM-G935F using XDA-Developers mobile app

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