Database Users

Samsung Galaxy S4 Baseband: Unkown.IMEI:NULL

Greetings, So far I dug as far as I could in google. But still no luck. My 4.3 update on the GS4 gut buggy, So I thought I'd install back to 4.2.2 firmware using odin. Normally it succeeded. But when I inserted my Sim card, I couldn't make phone calls. Says not registered on Network. And my IMEI stated 0004...something. To save time I didn't thought of downloading the original firmware. So, I thought I could benefit from my mother's GS4 and use it's firmware unaware of the dangers. So I backed up system files from my mother's GS4 and restored it on my phone using TWRP. It booted and everything except there's completely no signal. Baseband is now UNKOWN and the IMEI is Null. I downloaded the stock firmware according to my mom's Baseband, but still no luck. I really need help. I'm beginning to lose faith in my phone and I'm afraid I'm gonna pay 40$ to fix it. I know nothing is impossible with you guys, so you are my last hope. PEACE!

You SHOULD NOT have downgraded your baseband like that, and when you did, and the trouble started, you should have searched first for solutions before trying to restore it from another device!
Anyway, now, you should flash the latest 4.3 modem or the 4.3 modem you had before, preferably flash the whole 4.3 rom again, the exact same version you had before, or the latest one, and your phone should live again properly!

jake_halawi said:
Greetings, So far I dug as far as I could in google. But still no luck. My 4.3 update on the GS4 gut buggy, So I thought I'd install back to 4.2.2 firmware using odin. Normally it succeeded. But when I inserted my Sim card, I couldn't make phone calls. Says not registered on Network. And my IMEI stated 0004...something. To save time I didn't thought of downloading the original firmware. So, I thought I could benefit from my mother's GS4 and use it's firmware unaware of the dangers. So I backed up system files from my mother's GS4 and restored it on my phone using TWRP. It booted and everything except there's completely no signal. Baseband is now UNKOWN and the IMEI is Null. I really need help. I'm beginning to lose faith in my phone and I'm afraid I'm gonna pay 40$ to fix it. I know nothing is impossible with you guys, so you are my last hope. PEACE!
Click to expand...
Click to collapse
You cannot downgrade it to 4.2.2, you must solve your issue over 4.3. Download your 4.3 rom o a newer rom from sammobile and flash it using odin 3.09 if you have i9505, or 3.07 of you have i9500.
Enviado desde mi GT-I9500 usando Tapatalk 2

jaswinky said:
You cannot downgrade it to 4.2.2, you must solve your issue over 4.3. Download your 4.3 rom o a newer rom from sammobile and flash it using odin 3.09 if you have i9505, or 3.07 of you have i9500.
Enviado desde mi GT-I9500 usando Tapatalk 2
Click to expand...
Click to collapse
I did Do That, still no luck. BTW I have the GT-I9500

Have similar issue
jake_halawi said:
I did Do That, still no luck. BTW I have the GT-I9500
Click to expand...
Click to collapse
I have a similar issue, it started when I put my S4 in flight mode, then when the plane landed I turn it off and since then I have no signal, IMEI NULL and when dialing *#1234# no CP information, only AP and CSC.
I have been digging and rooted the phone and tried with Galaxsim but nothing, then the IMEI null fix but nothing (once I applied this one the cell phone stuck in SAMSUNG icon at boot processs).
So I installed again stock firmware and it's back to the original status, no signal, no IMEI, etc... worrking only with wifi.
Please give me a hand on this. I also have GT-I9500

do you have a EFS copy? if u got a copy try restoring and then flash the latest modem, the 4.2 and 4.3 efs structure is diferent, i work phone repair area and the simlocks are diferent for me, if u can't do that, then go to a repair shop...

carlosm15 said:
do you have a EFS copy? if u got a copy try restoring and then flash the latest modem, the 4.2 and 4.3 efs structure is diferent, i work phone repair area and the simlocks are diferent for me, if u can't do that, then go to a repair shop...
Click to expand...
Click to collapse
I don't have efs Backup. And I'm trying to evade going to a repair shop because I'm sure there is a solution we just need to dig more. And thanks all for your suggestions. Helpful ^^

carlosm15 said:
do you have a EFS copy? if u got a copy try restoring and then flash the latest modem, the 4.2 and 4.3 efs structure is diferent, i work phone repair area and the simlocks are diferent for me, if u can't do that, then go to a repair shop...
Click to expand...
Click to collapse
I don't have efs backup, don't know how to do that. The thing is that I have sent to repair but they didn't solve the issue.

well try flashing a 4.3 modem only, when you try to downgrade you get imei 0047, then you flash the latest modem o 4.3 modem and everything its ok...
try with MG9 or MK1 modem...

Same thing happened to me 2 days before. I was using it on Airplane mode for almost 12 days and suddenly when I switched it to network it does not detect sim card. Later i found IMEI is null, Baseband unknown and serial number is messed up. I never rooted my phone. I tried to flash stock firmware 4.3 with odin still no luck.
Might go to repair shop..Just how my efs folder is damaged or anything else screwed up my imei and baseband..
Modders your help is appreciated..

carlosm15 said:
well try flashing a 4.3 modem only, when you try to downgrade you get imei 0047, then you flash the latest modem o 4.3 modem and everything its ok...
try with MG9 or MK1 modem...
Click to expand...
Click to collapse
I installed the latest modem of 4.3, Still no luck. I think this thing can't be fixed. I'm afraid I'm gonna pay 40$.

Guys who are having this problem try this:
What is needed
-A computer with ADB
-USB Cord for phone
-Your phone (of course lol)
What to do to possibly fix issue.
1. Make sure your phone's debugging is activated.
-If not go to Settings -> Developer Options -> Click "USB debugging"
2. Plug phone into computer (Make sure drivers are installed for adb to connect to your phone)
3. Open command promt and go to where adb is located
-(use "cd" (without quotations) to change directories i.e "cd c:\adb\" will take you to the directory needed)
4. Once you're in the same directory as the adb.exe file is type this
- adb reboot nvrestore
This will reboot your phone and you should see a quick flash on the screen stating in the top left in blue about restoring the nv
Kewl's suggestion. Link :http://teamuscellular.com/Forum/topic/2592-last-attempt-to-fix-stuck-in-roaming-mode-for-the-sgs3/
I didn't try it. I'll install ADB then test it. I bet your connection is faster than mine, so try it first and get back to this post if it worked.

jake_halawi said:
Guys who are having this problem try this:
What is needed
-A computer with ADB
-USB Cord for phone
-Your phone (of course lol)
What to do to possibly fix issue.
1. Make sure your phone's debugging is activated.
-If not go to Settings -> Developer Options -> Click "USB debugging"
2. Plug phone into computer (Make sure drivers are installed for adb to connect to your phone)
3. Open command promt and go to where adb is located
-(use "cd" (without quotations) to change directories i.e "cd c:\adb\" will take you to the directory needed)
4. Once you're in the same directory as the adb.exe file is type this
- adb reboot nvrestore
This will reboot your phone and you should see a quick flash on the screen stating in the top left in blue about restoring the nv
Kewl's suggestion.
I didn't try it. I'll install ADB then test it. I bet your connection is faster than mine, so try it first and get back to this post if it worked.
Click to expand...
Click to collapse
Sorry for the ignorance, what does ADB means?

santidavila said:
Sorry for the ignorance, what does ADB means?
Click to expand...
Click to collapse
usually this

I think I'm getting to the surface, I just need to know how to retrieve your original IMEI since your original efs is deleted. If you guys please help me and when everything is successful, I'll make a step by step guide on what I did.

My worst nightmare came true, I sent my S4 to Samsung, the price got high as 200$. I asked the reason why, they said that the EFS file is the most sensitive file in the phone, it what makes it a phone anyways. They also said that they will hook it on a box or something like that that costs about 7000$. That's a shocker. If you ask me what I'm going to do with my S4, I'll have to pay the price, and sell it for 400$ Until the s5 is announced, I'll close the price gap. Sorry for the bad news :/

My phone IMEI is correct i am only having the network not registered error can this command solve my device issue.
jake_halawi said:
Guys who are having this problem try this:
What is needed
-A computer with ADB
-USB Cord for phone
-Your phone (of course lol)
What to do to possibly fix issue.
1. Make sure your phone's debugging is activated.
-If not go to Settings -> Developer Options -> Click "USB debugging"
2. Plug phone into computer (Make sure drivers are installed for adb to connect to your phone)
3. Open command promt and go to where adb is located
-(use "cd" (without quotations) to change directories i.e "cd c:\adb\" will take you to the directory needed)
4. Once you're in the same directory as the adb.exe file is type this
- adb reboot nvrestore
This will reboot your phone and you should see a quick flash on the screen stating in the top left in blue about restoring the nv
Kewl's suggestion. Link :http://teamuscellular.com/Forum/topic/2592-last-attempt-to-fix-stuck-in-roaming-mode-for-the-sgs3/
I didn't try it. I'll install ADB then test it. I bet your connection is faster than mine, so try it first and get back to this post if it worked.
Click to expand...
Click to collapse

terminator1983 said:
My phone IMEI is correct i am only having the network not registered error can this command solve my device issue.
Click to expand...
Click to collapse
NO Don't try this. Go to settings > More > Mobile Networks > Network operators > wait for it to search and select your carrier.

jake_halawi said:
NO Don't try this. Go to settings > More > Mobile Networks > Network operators > wait for it to search and select your carrier.
Click to expand...
Click to collapse
No i have done that and even flashed stock firmwares and modem but still i am having this problem. I got this problem of weak signals and not registered to network after turning the airplane mode in airplane like stated by someone else in the above posts.

terminator1983 said:
No i have done that and even flashed stock firmwares and modem but still i am having this problem. I got this problem of weak signals and not registered to network after turning the airplane mode in airplane like stated by someone else in the above posts.
Click to expand...
Click to collapse
Then, problem is hardware not software.

[Q] Note 3 - tried CM rom .. No Service

Just got a note 3.
Wanted to install Cyanogemmod.
Seemed to go ok, everything went well but the s-pen wasnt responsive at all, so i rebooted phone.
S-pen became responsive but i lost connectivity and my phone can no longer make phone calls or send text messages.
It keeps saying "Searching for service", i have reinstalled Cyanogenmod again but still same problem.
I dont know what to do.

re: kernel
newFool said:
Just got a note 3.
Wanted to install Cyanogemmod.
Seemed to go ok, everything went well but the s-pen wasnt responsive at all, so i rebooted phone.
S-pen became responsive but i lost connectivity and my phone can no longer make phone calls or send text messages.
It keeps saying "Searching for service", i have reinstalled Cyanogenmod again but still same problem.
I dont know what to do.
Click to expand...
Click to collapse
I bet you have not tried to flash a compatible custom kernel.
If your phone is an N9005 then flash this kernel below:
http://whatever.host-base.de/kernel/hlte/custom-n3-clean-0.98-eur.zip
If all else fails, why not flash a non-experimental Kitkat 4.4.2
TW based full feature custom rom. (There are so many good ones)
Good luck!

Hello, thankyou for your reply
yes i have a n9005
i did try to flash that kernel, then rebooted. same problem.
really not sure what to do, im really lost :crying:
Misterjunky said:
I bet you have not tried to flash a compatible custom kernel.
If your phone is an N9005 then flash this kernel below:
If all else fails, why not flash a non-experimental Kitkat 4.4.2
TW based full feature custom rom. (There are so many good ones)
Good luck!
Click to expand...
Click to collapse

newFool said:
Just got a note 3.
Wanted to install Cyanogemmod.
Seemed to go ok, everything went well but the s-pen wasnt responsive at all, so i rebooted phone.
S-pen became responsive but i lost connectivity and my phone can no longer make phone calls or send text messages.
It keeps saying "Searching for service", i have reinstalled Cyanogenmod again but still same problem.
I dont know what to do.
Click to expand...
Click to collapse
HI, in dialer if you wite this code *#06# have you the same IMEI write behind your battery ?
have you make backup before ?

I experienced the exact same problem.
1. settings > about phone > status
Do you still have an IMEI listed? If yes, we must first backup your EFS, FSG, FSC partitions. Use EFSBackup tool from this thread and save backup somewhere securely.
2. Flash back to stock
If you were still on 4.3 flash 4.3 in order to keep the unlocked bootloader. Else flash 4.4 stock. Only flash the correct firmware from this list. You can figure out which device you have by using the Device Info feature of EFSBackup
This fixed the problem for me. Do not flash anything BEFORE making a backup of EFS, FSC, and FSC partitions. If you lose those you lose your IMEI, in that case it's pretty much finished.
Report back here with progress.

AO7 said:
I experienced the exact same problem.
1. settings > about phone > status
Do you still have an IMEI listed? If yes, we must first backup your EFS, FSG, FSC partitions. Use EFSBackup tool from this thread and save backup somewhere securely.
2. Flash back to stock
If you were still on 4.3 flash 4.3 in order to keep the unlocked bootloader. Else flash 4.4 stock. Only flash the correct firmware from this list. You can figure out which device you have by using the Device Info feature of EFSBackup
This fixed the problem for me. Do not flash anything BEFORE making a backup of EFS, FSC, and FSC partitions. If you lose those you lose your IMEI, in that case it's pretty much finished.
Report back here with progress.
Click to expand...
Click to collapse
I think he have 4.4 version, he would like test CM...
I think too, he have not backup...
I think he cry....

Hi
When i type that it says:
MEID
B0000000
NOT the same as IMEI behind battery.
But in settings > about phone > status i still have IMEI and it matches number behind battery
M3GATROLL said:
HI, in dialer if you wite this code *#06# have you the same IMEI write behind your battery ?
have you make backup before ?
Click to expand...
Click to collapse

1. Yes i have an IMEI
2. When i bought it, it had 4.3, then after i installed CM it was 4.4.2, which firmware do i flash ?
AO7 said:
I experienced the exact same problem.
1. settings > about phone > status
Do you still have an IMEI listed? If yes, we must first backup your EFS, FSG, FSC partitions. Use EFSBackup tool from this thread and save backup somewhere securely.
2. Flash back to stock
If you were still on 4.3 flash 4.3 in order to keep the unlocked bootloader. Else flash 4.4 stock. Only flash the correct firmware from this list. You can figure out which device you have by using the Device Info feature of EFSBackup
This fixed the problem for me. Do not flash anything BEFORE making a backup of EFS, FSC, and FSC partitions. If you lose those you lose your IMEI, in that case it's pretty much finished.
Report back here with progress.
Click to expand...
Click to collapse

newFool said:
Hi
When i type that it says:
MEID
B0000000
NOT the same as IMEI behind battery.
But in settings > about phone > status i still have IMEI and it matches number behind battery
Click to expand...
Click to collapse
If you have imei 0049.... or null/null it's EFS folder damaged (go to Samsung repair office)
With imei 0000, i have see guys fix this problem with flash .PIT File
(you restore your imei and your gsm connection, but after it 's possible have problem with wifi connection..)
Search in different thread, this problem is already mentioned.
I hope for you, you success.

AO7 said:
I experienced the exact same problem.
1. settings > about phone > status
Do you still have an IMEI listed? If yes, we must first backup your EFS, FSG, FSC partitions. Use EFSBackup tool from this thread and save backup somewhere securely.
.
Click to expand...
Click to collapse
Tried this but EFS doesnt seem to be able to detect when my phone is connected, i cant backup.
I used cwm to backup to sd card is this the same ?
is there another way to backup ?

newFool said:
Tried this but EFS doesnt seem to be able to detect when my phone is connected, i cant backup.
I used cwm to backup to sd card is this the same ?
is there another way to backup ?
Click to expand...
Click to collapse
OK I understand you still have IMEI?
Do not flash anything at the moment. We MUST first backup efs, fsc, and fsg blocks.
If the phone was only on 4.3 stock when you bought and and you have only flashed CM on it the bootloader is still 4.3
The bootloader is only upgraded when you flash 4.4 kitkat STOCK ROM. CM does not touch your bootloader.
What is the problem with EFSBackup? Did you enable root access for apps AND adb in the developer options menu?
I say again do not flash anything before we can get these backups. We can still fix the phone ATM.

Thankyou for trying to help me.
AO7 said:
OK I understand you still have IMEI?
Click to expand...
Click to collapse
Yes, When i go to: about phone > status > IMEI is still there.
AO7 said:
Do not flash anything at the moment. We MUST first backup efs, fsc, and fsg blocks.
Click to expand...
Click to collapse
Ok i wont flash anything until you guys say its ok.
AO7 said:
If the phone was only on 4.3 stock when you bought and and you have only flashed CM on it the bootloader is still 4.3
The bootloader is only upgraded when you flash 4.4 kitkat STOCK ROM. CM does not touch your bootloader.
Click to expand...
Click to collapse
I hope so
AO7 said:
What is the problem with EFSBackup? Did you enable root access for apps AND adb in the developer options menu?
Click to expand...
Click to collapse
When i connect my phone to the computer, computer detects it.
I then run EFSbackup and it says "Device not connected, plug in USB cable"... even though phone is plugged in and is detected by my computer.
I am not sure how to enable root access for apps AND adb, im sorry. how do i do that ?

newFool said:
I am not sure how to enable root access for apps AND adb, im sorry. how do i do that ?
Click to expand...
Click to collapse
Assuming you have CM running do this:
Settings > About Phone > Build Number.
Tap the Build Number section 7 times in a row. A small message will pop up that says "You are now a developer".
Return to the settings menu. You will now see there's a new menu at the bottom called "Developer options". Enter that menu and scroll down to the section "DEBUGGING". Tap on "USB debugging" to enable it. A small window will pop up that asks you again if you want to enable debugging. Tap "OK".
If the phone was not yet connected with a USB cable to your computer do that now. After a few seconds a window will appear that display your computers authentication ID. It will ask you to allow access for that computer ID. Check the box that says something like "Do not ask again for this computer" and then tap "Allow" or "OK" (can't remember what it says).
Now scroll up a little bit in the Developer options menu until you see "Root access". It should currently say only "Apps". Tap the menu and select "Apps and ADB" from the popup.
When all that is done start EFSBackup again. It auto-detects if you did everything correctly as written here. Report back here with your progress.

Thankyou for helping me, i got through it, but now in EFS Professional i get this error
AO7 said:
Assuming you have CM running do this:
Settings > About Phone > Build Number.
Tap the Build Number section 7 times in a row. A small message will pop up that says "You are now a developer".
Return to the settings menu. You will now see there's a new menu at the bottom called "Developer options". Enter that menu and scroll down to the section "DEBUGGING". Tap on "USB debugging" to enable it. A small window will pop up that asks you again if you want to enable debugging. Tap "OK".
If the phone was not yet connected with a USB cable to your computer do that now. After a few seconds a window will appear that display your computers authentication ID. It will ask you to allow access for that computer ID. Check the box that says something like "Do not ask again for this computer" and then tap "Allow" or "OK" (can't remember what it says).
Now scroll up a little bit in the Developer options menu until you see "Root access". It should currently say only "Apps". Tap the menu and select "Apps and ADB" from the popup.
When all that is done start EFSBackup again. It auto-detects if you did everything correctly as written here. Report back here with your progress.
Click to expand...
Click to collapse

I flashed this kernel as per advice. Could this be the reason EFS Pro says "your device is NOT perm rooted!" ?
Misterjunky said:
I bet you have not tried to flash a compatible custom kernel.
If your phone is an N9005 then flash this kernel below:
http://whatever.host-base.de/kernel/hlte/custom-n3-clean-0.98-eur.zip
If all else fails, why not flash a non-experimental Kitkat 4.4.2
TW based full feature custom rom. (There are so many good ones)
Good luck!
Click to expand...
Click to collapse

newFool said:
I flashed this kernel as per advice. Could this be the reason EFS Pro says "your device is NOT perm rooted!" ?
Click to expand...
Click to collapse
Are you certain you have selected APPS AND ADB in the root access menu of developer options?

Pretty sure i have.
AO7 said:
Are you certain you have selected APPS AND ADB in the root access menu of developer options?
Click to expand...
Click to collapse

newFool said:
Pretty sure i have.
Click to expand...
Click to collapse
Do you have SuperSU installed? Install it from the Play Store and come back here with the result.

SuperSU is installed.
AO7 said:
Do you have SuperSU installed? Install it from the Play Store and come back here with the result.
Click to expand...
Click to collapse

newFool said:
SuperSU is installed.
Click to expand...
Click to collapse
Ok can you run adb from the command prompt or shell as root?
Code:
$ adb devices
$ adb root
does that allow you to restart the adb daemon in root mode?

New Firmware 5.0.0-RU1.1.99

You can find it here: ftp://fw.ydevices.com/YotaPhone2/Firmwares/RU/
Install either via OTA update if you're already on the 1.87 RU ROM like I am. On my device it first wanted to install the update only, about 67MB, but it failed to install; then the next time I checked for updates after reboot through the settings update menu, it downloaded the full file, about 0,99 GB. Then the update went all the way through. SuperSU is lost on the way, I will try if it still works through the recovery installation.
You can also install through Yotaflasher like it's explained here: http://forum.xda-developers.com/showthread.php?t=3247356
Didn't have time to test things out, but it's still Lollipop 5.0, so only bugfixes and some new yotapanel features I guess.
Enjoy!

Thanks for that muchly dude, hadn't checked that for a while.
Update seems to be stability improvements, power efficiency improvements and some yotamirror and panel improvements and features.
Its not 5.1, but it's an update, I'll take it.
And yeah, super glad moved to the RU ROM. Backing up now, will OTA flash update once that's done. SuperSU has been flashable everytime after an update so far so fingers crossed.

All up and running .
I was rooted, running RU 1.87 with TWRP - phone handled it all just fine - downloaded OTA, pressed install - it went to TWRP > flashed stock recovery back over itself > rebooted and installed.
Phone booted up, all working fine. Lost root - simple reboot and flash the SU.zip had sitting there from the last update. Cache and Dalvik wiped for good measure.
Reboot and all is well and back to normal but with a few improvements, lovely.
About as easy as it's even been done really.
Hope everyone else gets to enjoy the update through similarly smooth procedures .

Yeah, I ended up doing a fresh installation plus rooting, everything smooth. I'm never too sure what an update leaves behind.
It's really a great device, hopefully they'll keep updating things for a while. Of course version 6.0 would be welcomed... Apparently, by the numbering they use, next step would be either 1.2.xx with Android 5.1 or 2.x.xx with 6.0. Let's see.

Fair play, I toyed with idea of it, but was fresh from last install and honestly don't have the time to set everything up again.
My hope is they take all their good ideas from this and can at least join someone else in making a great device.
Saw a working bendy phone the other day, lets you turn pages on reading app by bending corner as you would a book etc. I thought if that could be combined with yota tech, then you have damn near the perfect tablet.
Honestly I don't think we'll get 5.1, let alone 6.0. They're refining their ideas in prep for Yotaphone 3, that and the possible tablet are their main focus right now.
Interestingly, the update flashed it's stock recovery over twrp - someone prepared for the possibility of root owners this time around. So they are still paying attention .

So any idea what's the difference between the EU and the RU rom? I mean there has to be some reason they are two separate roms.

To answer my own question: there isn't too many differences between EU and RU roms. I did a diff between the RU1.1.59 and EU1.1.60, and out of 2092 files, roughly 1900 of the files inside system.img were identical. The APKs were slightly different, but only slightly. So probably the difference comes from some differently named resources.
The RU version also has some additional apps which the EU version does not have, such as Esquire, Questions, Strelka and Vector. These are probably the main reason why they have different ROMs. They might only work in Russia.

Jeopardy said:
To answer my own question: there isn't too many differences between EU and RU roms. I did a diff between the RU1.1.59 and EU1.1.60, and out of 2092 files, roughly 1900 of the files inside system.img were identical. The APKs were slightly different, but only slightly. So probably the difference comes from some differently named resources.
The RU version also has some additional apps which the EU version does not have, such as Esquire, Questions, Strelka and Vector. These are probably the main reason why they have different ROMs. They might only work in Russia.
Click to expand...
Click to collapse
FYI the difference is essentially the product package configuration (app bundles that are pre-loaded) but there are also some differences between the resources used for the stock apps. One in particular (my personal fav ) is the dialler - the RU variant includes cyrillic characters regardless of language/locale setting (feature). The EU will give you a regular english-only dialler if you're using english locale settings

Vuche said:
You can find it here: ftp://fw.ydevices.com/YotaPhone2/Firmwares/RU/
Install either via OTA update if you're already on the 1.87 RU ROM like I am. On my device it first wanted to install the update only, about 67MB, but it failed to install; then the next time I checked for updates after reboot through the settings update menu, it downloaded the full file, about 0,99 GB. Then the update went all the way through. SuperSU is lost on the way, I will try if it still works through the recovery installation.
You can also install through Yotaflasher like it's explained here: http://forum.xda-developers.com/showthread.php?t=3247356
Didn't have time to test things out, but it's still Lollipop 5.0, so only bugfixes and some new yotapanel features I guess.
Enjoy!
Click to expand...
Click to collapse
Ho to flash the update zip file? I m stuck on 4.4.3...

does nyone know how to flash the file zip into the phone?? i have no idea how it works and i dont find any infos

Does the new update solve the keyboard sensitivity issue??

zute333 said:
numerous guides and how to's in this forum and across XDA, as well as google.
download fastboot + adb > boot to download mode > flash twrp via fastboot commands > boot into twrp > flash zip.
There's obviously more to it than that, up to you to do the research.
Click to expand...
Click to collapse
i'm using this post as a minimalistic guide for myself (so i keep it up with my "discoveries" )
and ofc for been helped by everyone who wants to help me because i am completely new to android world cause this is my first android phone ever!
so.. let's get started!
i downloaded [TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3
version 1.4.3 doesnt works for me so i downloaded the 1.3 as suggested and worked.
then i enabled the download mode following the procedure:
Turn off the phone, then press and hold the volume down key + the power key at the same time. This should boot you into download mode.
Click to expand...
Click to collapse
note: phone MUST be disconnected form pc to be turned off.
now..
*does install twrp invalidate warranty?
EDIT: answer is YES cause of
TWRP 2.8.5.0 YotaPhone 2 recovery image said:
Warning: It is currently not known how to re-lock the bootloader. This means you cannot completely undo the next step as of yet. This might have consequences for sending the device in for repairs, if they check for this, and deem it a (warranty) problem
Click to expand...
Click to collapse
*is installing TWRP a mandatory step?
EDIT: the answer is NO. it seems that the mandatory part is to unlock the bootloader (the bad part for the warranty.. and that can erase ur data..) and this can be done following this guide How to Install TWRP Recovery on YotaPhone 2 untill point 6 included - which i am reporting here for easy of use.
How to Install TWRP Recovery on YotaPhone 2 said:
How to Flash TWRP Recovery on YotaPhone 2
1 - Setup ADB and Fastboot on your Windows PC.
2 - Enable USB debugging from developer options on your YotaPhone 2.
3 - Connect it to PC with a USB cable, if it asks for debugging authorization, permit it.
4 - Go to the folder where you downloaded the TWRP recovery image from the download link above on your PC and open a command window inside that folder by doing “Shift + Right click” on any empty white space inside the folder, then select “Open command window here”.
5 - (Skip this if your bootloader is already unlocked) Now to unlock the bootloader, type in the following command:
└ Beware that unlocking the bootloader may wipe your phone’s data. Make sure to backup first before proceeding.
adb reboot bootloader
Click to expand...
Click to collapse
└ This will reboot your phone to bootloader mode
fastboot oem unlock
Click to expand...
Click to collapse
└ This will unlock bootloader on your device.
6 - Now if your phone has rebooted and is no longer in the bootloader mode, then boot it back into bootloader mode with the “adb reboot bootloader” command.
Click to expand...
Click to collapse
i already downloaded yotaflasher and the last RU firmware 5.0.0-RU1.1.99.zip
NOTE: Russian firmware seems to contain English language. i dont know how to change it later to the favorite one.
NOTE: you need to move the firmware files to the same location as the Flasher tool. Default one is C:\Program Files (x86)\yotaphone_flasher
i tryed to use yotaflasher right now while phone is in download mode and it says:
error: cannot open 'firmware/emnc_appsboot.mbn'
error: cannot open 'firmware/boot.img'
error: cannot open 'firmware/system.img'
error: cannot open 'firmware/recovery.img'
error: cannot open 'firmware/cache.img'
error: cannot open 'firmware/radio/NON-HLOS.bin'
error: cannot open 'firmware/radio/sbli.mbn'
error: cannot open 'firmware/radio/rpm.mbn'
error: cannot open 'firmware/radio/tz.mbn'
error: cannot open 'firmware/enmc_appsboots.mbn'
Would you like to flash userdata[Y/N]:
Click to expand...
Click to collapse
EDIT: placing the firmware in the right folder and unzipping ip let me flash my phone without using any bootloader. now i dont know why but is stucked showing android logo.
i dont know if this happened cause i used the last RU firmware on my stock 4.4.3 android or what..
what do i have to do?:crying::crying::crying:
tnx

Hello guys, I downloaded Lollipop from the ftp but installation fails: no MD5 file found!
I downloaded all russian versions and also the 1.6 EU version... but no way I always get this error.
I'm using TWRP 2.8.5, I guess the last one, and in the tutorials I see this version...
Does anyone know how to solve? :crying:

giocorrado said:
does nyone know how to flash the file zip into the phone?? i have no idea how it works and i dont find any infos
Click to expand...
Click to collapse
The info is described in various posts across the yotaphone forum. Are you rooted? If not then there also many many guides across the internet for that.
Not walking you through the whole process, sorry. We all had to learn, once you do it's all much easier.

It happens also to me...don't panic! press Volume up and the power button and when you enter in the bootloader select the downloading options, it will restart the phone with the "downloading" status
in the meanwhile with the yotaflasher select the option to downloads a firmware and try a different one. When the download is finished try to flash once again.

Melting Blaze said:
i already downloaded yotaflasher and the last RU firmware 5.0.0-RU1.1.99.zip
NOTE: Russian firmware seems to contain English language. i dont know how to change it later to the favorite one.
NOTE: you need to move the firmware files to the same location as the Flasher tool. Default one is C:\Program Files (x86)\yotaphone_flasher
i tryed to use yotaflasher right now while phone is in download mode and it says:
EDIT: placing the firmware in the right folder and unzipping ip let me flash my phone without using any bootloader. now i dont know why but is stucked showing android logo.
i dont know if this happened cause i used the last RU firmware on my stock 4.4.3 android or what..
what do i have to do?:crying::crying::crying:
tnx
Click to expand...
Click to collapse
I placed like you the rom downloaded through website in the firmware folder and flash got wrong. I was blocked on "powered by android" logo like you.
After this almost-bricking experience, I flashed 4.4.3 downloaded all through Flasher and phone was working again.
Then I tried to substitute 5.0 system.img in the folder downloaded through Flasher but no way... after flashing phone didn't boot.
I reflashed 4.4.3 back again and now is working.
I think that we can't put files in folder for Yota Flasher...
I cannot download last 5.0 EU version, like described here: http://forum.xda-developers.com/yot...ially-dead-t3312382/post65839167#post65839167

TKPL said:
I placed like you the rom downloaded through website in the firmware folder and flash got wrong. I was blocked on "powered by android" logo like you.
After this almost-bricking experience, I flashed 4.4.3 downloaded all through Flasher and phone was working again.
Then I tried to substitute 5.0 system.img in the folder downloaded through Flasher but no way... after flashing phone didn't boot.
I reflashed 4.4.3 back again and now is working.
I think that we can't put files in folder for Yota Flasher...
I cannot download last 5.0 EU version, like described here: http://forum.xda-developers.com/yot...ially-dead-t3312382/post65839167#post65839167
Click to expand...
Click to collapse
yeah i've done the same.
i founded the trick i hope
after my big mistake i have done this:
*i downloaded the last 4.4.3-S01-003-EU1.0.3.61a.zip then i flashed it. reminding to unzip it and put it in the right folder of the flasher. remind that this will delete ur data too prob.
*i checked for update on the phone in setting--> about phone --> sistem update
*it downloaded lollipop (android 5.0 Lollipop - 1Gb to download) :laugh:
*i took the 5.0.0-RU1.1.99.zip and flashed it
*u can choose english when the phone boot so dont worry about firmware to be RU
*i checked the firmware version doing the combo "Volume up and the power button" (press it while restarting)
*i changed the language of the phone in setting --> language (there is plenty of languages to choose. i choose mine, italian, but sometimes it happens to find something in english )
i downladed some app etc etc but i never used it for calls cause of the requested nano sim that i'm going to take tomorrow probably cause today i get stucked with trouble about my contacts.
hope to solve the problem for pass my contacts form my nokia N8 to yotaphone 2 quickly!
please let me know if it works for u too
JAMMANDROID said:
It happens also to me...don't panic! press Volume up and the power button and when you enter in the bootloader select the downloading options, it will restart the phone with the "downloading" status in the meanwhile with the yotaflasher select the option to downloads a firmware and try a different one. When the download is finished try to flash once again.
Click to expand...
Click to collapse
yeah. is exactly what i did, but super panicing like a chicken without head

Melting Blaze said:
yeah i've done the same.
i founded the trick i hope
after my big mistake i have done this:
*i downloaded the last 4.4.3-S01-003-EU1.0.3.61a.zip then i flashed it. reminding to unzip it and put it in the right folder of the flasher. remind that this will delete ur data too prob.
*i checked for update on the phone in setting--> about phone --> sistem update
*it downloaded lollipop (android 5.0 Lollipop - 1Gb to download) :laugh:
*i took the 5.0.0-RU1.1.99.zip and flashed it
*u can choose english when the phone boot so dont worry about firmware to be RU
*i checked the firmware version doing the combo "Volume up and the power button" (press it while restarting)
*i changed the language of the phone in setting --> language (there is plenty of languages to choose. i choose mine, italian, but sometimes it happens to find something in english )
i downladed some app etc etc but i never used it for calls cause of the requested nano sim that i'm going to take tomorrow probably cause today i get stucked with trouble about my contacts.
hope to solve the problem for pass my contacts form my nokia N8 to yotaphone 2 quickly!
please let me know if it works for u too
yeah. is exactly what i did, but super panicing like a chicken without head
Click to expand...
Click to collapse
I saw also an update this morning at home on wifi (I wait for the SIM too) because yesterday I flashed the 4.4.3-S01-003-EU1.0.51a: is not the 61 like yours and I received an update alert to 4.4.3-S01-003-EU1.0.3.56. I'm at work, I'll try this evening.
I haven't updated this morning because I was downloading a previous 5.0, the EU 1.44, but when flashing I had error "cannot load firmware/system.img". So I reflashed 4.4.3... I'll try again this evening

giocorrado said:
does nyone know how to flash the file zip into the phone?? i have no idea how it works and i dont find any infos
Click to expand...
Click to collapse
Hi, download YotaFlasher, it permits you to download and flash firmwares in an easy way, and you don't need to know any shell command
---------- Post added at 09:37 AM ---------- Previous post was at 09:25 AM ----------
giocorrado said:
does nyone know how to flash the file zip into the phone?? i have no idea how it works and i dont find any infos
Click to expand...
Click to collapse
TKPL said:
I saw also an update this morning at home on wifi (I wait for the SIM too) because yesterday I flashed the 4.4.3-S01-003-EU1.0.51a: is not the 61 like yours and I received an update alert to 4.4.3-S01-003-EU1.0.3.56. I'm at work, I'll try this evening.
I haven't updated this morning because I was downloading a previous 5.0, the EU 1.44, but when flashing I had error "cannot load firmware/system.img". So I reflashed 4.4.3... I'll try again this evening
Click to expand...
Click to collapse
Hello! I have 5.0!
After flashing and old version of 4.4.3 (my phone went with a 4.4.something branded Vodafone Italy, and they evidently don't give a fork about updates). With the 4.4.3 rev 1.0.51a I immediately received he update to 1.0.56a: I downloaded the 114MB, rebooted, and then got the update to 1.0.61a, around 63MB. I rebooted and then got finally the update to 5.0, 1GB :laugh:
I have only one problem now: the device doesn't recognize when I'm looking at the ink screen, and power button powers on the amoled... Even unlocking through swiping from bottom to top doesn't work. Option is correctly set, I tried to uncheck, reboot, wipe cache and check the option again but it not working well yet.

I have only one problem now: the device doesn't recognize when I'm looking at the ink screen, and power button powers on the amoled... Even unlocking through swiping from bottom to top doesn't work. Option is correctly set, I tried to uncheck, reboot, wipe cache and check the option again but it not working well yet.
Click to expand...
Click to collapse
seems that is the same for a lot of people if not everyone..
cause of this problem i am using this app gravity screen on/off.
it halves the problem cause now i have no problem for the amoled. and for problem i mean use the pwer button instead of simply swipe.
for the e-ink panel i still have to use the power button, only way it works.

[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