Develop Bugs

Windows RT 8.1 downgrade?

Hi there,
just a short question: Is it possible to downgrade a Surface using Windows RT 8.1 to Windows RT (without the 8.1)?
I read something about a recovery USB image but this solution wasn't working for me. (Yeah, I deleted the recovery partition before...) My surface arrived with RT 8.1 so I don't have a USB containing Windows RT. Can I use another USB stick from another tablet?
BR
Screeny

You would probably need a recovery image for the Surface and not from some other similar tablet.
Not sure on this though, so don't quote me on this.
I have been trying to downgrade my Lenovo Yoga 11, but I haven't had any luck with the RT 8.0 recovery image found here:
forums_lenovo_com/t5/Idea-Windows-based-Tablets-and/Yoga-11-Windows-RT-Recovery/td-p/1220234
(replace underlines with dots to follow the link, can't post links due to being a newcomer...)
Not surprising, but it seems that we are actively being locked out from going back to RT 8.0
Most annoying thing in my opinion is that the tilt sensor doesn't work, so I would have to manually choose to rotate the screen

Most of the time its user error, hence why it was so highly recommended to check that you know how to use a recovery drive before removing the partition on the device. Several users have downgraded to 8.0 via recovery, there is nothing locking you out from doing so.
But yes. If its a first generation surface, you can get a surface RT 8.0 recovery image to downgrade. Microsoft host the US one themselves and then Trig0r on these forums have Surface RT 8.0 recoveries for all languages on his own file server (PM him).
The recovery image you use should be specific to the device. A yoga recovery would not work properly on a surface and vice versa (it will boot but drivers will be wrong).
If its a Surface 2. There never was an 8.0 image for them. You cannot downgrade it.

Workaround
SixSixSevenSeven said:
Most of the time its user error, hence why it was so highly recommended to check that you know how to use a recovery drive before removing the partition on the device. Several users have downgraded to 8.0 via recovery, there is nothing locking you out from doing so.
But yes. If its a first generation surface, you can get a surface RT 8.0 recovery image to downgrade. Microsoft host the US one themselves and then Trig0r on these forums have Surface RT 8.0 recoveries for all languages on his own file server (PM him).
The recovery image you use should be specific to the device. A yoga recovery would not work properly on a surface and vice versa (it will boot but drivers will be wrong).
If its a Surface 2. There never was an 8.0 image for them. You cannot downgrade it.
Click to expand...
Click to collapse
Got it! Recovery wasn't working for me because the stick wasn't recognized as bootable.
Now I found a workaround (maybe this is working for the Surface 2 too? Would be very nice! Could some test it, please?)
At first create a bootable recovery stick with the current Windows RT version (maybe a downloaded image will work too). Download the recovery image for Windows RT 8.0 (search for Surface RT Recovery Image (Windows RT 8.0) ) and copy the "sources\Install.wim" file to your created bootable recovery stick.
Because my english isn't so good, here a short to-do list:
Use your surface to create a recovery USB stick with Windows 8.1
Download Windows RT 8.0 recovery image from Microsoft
Copy the file "install.wim" (located under "sources" from your downloaded 8.0 recovery image to your 8.1 recovery USB stick
Boot your surface with the 8.1 recovery USB
Start a cmd session (after choosing "Troubleshoot" -> "Advanced options" ...)
Use diskpart to delete both recovery partitions and the system partition
Create a new partition and format it with NTFS
Make it active and assign this partition a drive letter (for example G
Close diskpart
Use dism to install the Windows 8.0 image to your drive (if you saved the "install.wim" from the Windows RT 8.0 image to your USB sticks root dir, use this command: dism /apply-image /imagefile:\install.wim /index:1 /applydir:G:\
After applying the image use bootrec /fixboot
Close cmd and restart your Surface
This worked for me like a charm
Greetings
Screeny

Hmm, maybe my recovery files are messed up or something.
I haven't been able to get it to boot correctly from the usb-stick (if at all).
The led flashes on the stick, and i was able to wipe the hdd (not sure if that was from a ram-disk or the stick).
I assumed that the recovery process would be able to partion the ssd but apperently not.
Now the problem is that it does not want to boot from my usb-stick, I have tried 2 different sticks with the same result:
It skips them both even though they are bootable and should have the files necessary.

TheExileFox said:
Hmm, maybe my recovery files are messed up or something.
I haven't been able to get it to boot correctly from the usb-stick (if at all).
The led flashes on the stick, and i was able to wipe the hdd (not sure if that was from a ram-disk or the stick).
I assumed that the recovery process would be able to partion the ssd but apperently not.
Now the problem is that it does not want to boot from my usb-stick, I have tried 2 different sticks with the same result:
It skips them both even though they are bootable and should have the files necessary.
Click to expand...
Click to collapse
YOu know the tablet wont automatically boot from USB unless you tell it to?

SixSixSevenSeven said:
YOu know the tablet wont automatically boot from USB unless you tell it to?
Click to expand...
Click to collapse
Yes, I have tried holding down vol+/vol- while starting it and it doesn't seem to do anything.

You turn the tablet off. Then press and hold volume down, try to power it on while still holding the button. You dont release the volume down button until the surface splash screen appears.
If that still doesn't work then you haven't created the recovery USB properly.
The other way to boot from USB (but won't alter whether it will boot from an improper recovery image of course) for Surface RT's which do boot is to swipe the charms bar in, go to settings, Change PC Settings, Update or Recovery, Recovery, Advanced Startup, Restart Now, on the choose an option screen select Use A Device which should open a troubleshoot screen where you can select advanced options and finally the name of your USB device.

SixSixSevenSeven said:
You turn the tablet off. Then press and hold volume down, try to power it on while still holding the button. You dont release the volume down button until the surface splash screen appears.
If that still doesn't work then you haven't created the recovery USB properly.
The other way to boot from USB (but won't alter whether it will boot from an improper recovery image of course) for Surface RT's which do boot is to swipe the charms bar in, go to settings, Change PC Settings, Update or Recovery, Recovery, Advanced Startup, Restart Now, on the choose an option screen select Use A Device which should open a troubleshoot screen where you can select advanced options and finally the name of your USB device.
Click to expand...
Click to collapse
Solved that yesterday, the issue was not the procedure but the tool to make the usb-sticks bootable. Thanks anyway.

I was able to downgrade my Surface RT with Windows 8.1 (it came with 8.1 pre-installed) to Windows 8.0 using someone's else recovery image and using above procedure...
everything works fine! I'm happy - I jailbreaked it and can run unsigned apps...
the only problem is I cannot activate my surface anymore... it looks like MS blocked product key which was used in recovery image...
do you have any ideas how I can fix it?
Thanks
---------------------
If anyone is interested: I activated my Surface today using telephone activation system

Screeny said:
Use your surface to create a recovery USB stick with Windows 8.1
Download Windows RT 8.0 recovery image from Microsoft
Copy the file "install.wim" (located under "sources" from your downloaded 8.0 recovery image to your 8.1 recovery USB stick
Boot your surface with the 8.1 recovery USB
Start a cmd session (after choosing "Troubleshoot" -> "Advanced options" ...)
Use diskpart to delete both recovery partitions and the system partition
Create a new partition and format it with NTFS
Make it active and assign this partition a drive letter (for example G
Close diskpart
Use dism to install the Windows 8.0 image to your drive (if you saved the "install.wim" from the Windows RT 8.0 image to your USB sticks root dir, use this command: dism /apply-image /imagefile:\install.wim /index:1 /applydir:G:\
After applying the image use bootrec /fixboot
Close cmd and restart your Surface
This worked for me like a charm
Click to expand...
Click to collapse
I haven't followed your exact steps, but I managed to install windows 8 on my Surface that shipped with 8.1 but now it's telling me it's not activated. Did you have any problems with activation?
twister2000 said:
I was able to downgrade my Surface RT with Windows 8.1 (it came with 8.1 pre-installed) to Windows 8.0 using someone's else recovery image and using above procedure...
Click to expand...
Click to collapse
Did you use Screeny's procedure? How did you activate over the phone?
Thank you both

randoof said:
Did you use Screeny's procedure? How did you activate over the phone?
Click to expand...
Click to collapse
Just after Windows 8.0 installation don't connect to network and create a local account.
Then you can go to activation and there should be an option to activate over the phone - if so - just follow the steps (when the machine will ask you on how many PCs have you installed that Windows just press 1).
Cheers

twister2000 said:
Just after Windows 8.0 installation don't connect to network and create a local account.
Then you can go to activation and there should be an option to activate over the phone - if so - just follow the steps (when the machine will ask you on how many PCs have you installed that Windows just press 1).
Cheers
Click to expand...
Click to collapse
That did the trick. Thank you.

Screeny said:
Got it! Recovery wasn't working for me because the stick wasn't recognized as bootable.
Now I found a workaround (maybe this is working for the Surface 2 too? Would be very nice! Could some test it, please?)
At first create a bootable recovery stick with the current Windows RT version (maybe a downloaded image will work too). Download the recovery image for Windows RT 8.0 (search for Surface RT Recovery Image (Windows RT 8.0) ) and copy the "sources\Install.wim" file to your created bootable recovery stick.
Because my english isn't so good, here a short to-do list:
Use your surface to create a recovery USB stick with Windows 8.1
Download Windows RT 8.0 recovery image from Microsoft
Copy the file "install.wim" (located under "sources" from your downloaded 8.0 recovery image to your 8.1 recovery USB stick
Boot your surface with the 8.1 recovery USB
Start a cmd session (after choosing "Troubleshoot" -> "Advanced options" ...)
Use diskpart to delete both recovery partitions and the system partition
Create a new partition and format it with NTFS
Make it active and assign this partition a drive letter (for example G
Close diskpart
Use dism to install the Windows 8.0 image to your drive (if you saved the "install.wim" from the Windows RT 8.0 image to your USB sticks root dir, use this command: dism /apply-image /imagefile:\install.wim /index:1 /applydir:G:\
After applying the image use bootrec /fixboot
Close cmd and restart your Surface
This worked for me like a charm
Greetings
Screeny
Click to expand...
Click to collapse
Can you please clarify this step:
[*]Use diskpart to delete both recovery partitions and the system partition*
There are 2 recovery partitions, 1 System, and 1 Primary, and 1 Reserved. You say delete the 2 recovery and 1 system, but then since the primary is there there is not enough disk space...? Can you clarify what partitions to delete and what partitions to create?
Is System=Primary???
Thanks !!

chappatti said:
Can you please clarify this step:
[*]Use diskpart to delete both recovery partitions and the system partition*
There are 2 recovery partitions, 1 System, and 1 Primary, and 1 Reserved. You say delete the 2 recovery and 1 system, but then since the primary is there there is not enough disk space...? Can you clarify what partitions to delete and what partitions to create?
Is System=Primary???
Thanks !!
Click to expand...
Click to collapse
You can just use the "clean" command for deleting all partitions on this disk.
Just select your disk "select disk X" and then "clean"
Greetings
Screeny

Screeny said:
You can just use the "clean" command for deleting all partitions on this disk.
Just select your disk "select disk X" and then "clean"
Greetings
Screeny
Click to expand...
Click to collapse
Thanks for your reply !!
But if I use clean, I cannot boot the Surface at all. It shows the "Surface" screen and then just turns off. I end up with just one partition TOTAL - just one primary; no recover or anything else and my surface will not boot.
I am using the recovery from this post.
http://forum.xda-developers.com/showpost.php?p=43597775&postcount=32
Do I need a proper MS recovery image?
EDIT: In your method, you are just recopying the primary partition, right? Install.wim just recopies to primary. How do the recovery and system partitions get recreated..

chappatti said:
Thanks for your reply !!
But if I use clean, I cannot boot the Surface at all. It shows the "Surface" screen and then just turns off. I end up with just one partition TOTAL - just one primary; no recover or anything else and my surface will not boot.
I am using the recovery from this post.
http://forum.xda-developers.com/showpost.php?p=43597775&postcount=32
Do I need a proper MS recovery image?
Click to expand...
Click to collapse
Did you used the fixboot command?

Screeny said:
Did you used the fixboot command?
Click to expand...
Click to collapse
Yes, bootrec /fixboot...
The problem is I do not have any Reserved, System or Recovery part. Only one Primary part in the end..

chappatti said:
Yes, bootrec /fixboot...
The problem is I do not have any Reserved, System or Recovery part. Only one Primary part in the end..
Click to expand...
Click to collapse
Uhm. But this should be OK ...
But you can test this by creating a new 100 mb partition and try to use the /fixboot command to this new partition.

Screeny said:
Uhm. But this should be OK ...
But you can test this by creating a new 100 mb partition and try to use the /fixboot command to this new partition.
Click to expand...
Click to collapse
Well....the way I got Windows 8.0 downgrade was to follow this thread
http://forum.xda-developers.com/showthread.php?t=2350875
I had to completely create new partitions, which was no big deal when one knows the instructions (!), and then copy images along with restoring efi boot files.
It works !

[TUTORIAL]Howto backup whole phone and restore back in case hardbricked

Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this TUTORIAL
* before doing anything! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
In this tutorial i'll guide howto create full phone backup and restoring back in case got hardbricked. Tested and confirmed working myself (yes i've hardbricked my phone two days ago and managed to restore back to fully working state). My phone is nokia x, so this is confirmed to be working for the nokia x. For x+ and xl should be working too because basically theres not many different between the three. The backup created using this tutorial is low level whole disk backup, different from cwm or twrp backup because those recoveries will only backup certain partitions only, can be useful to restore back from the recoveries itself but became useless if got hardbricked. This backup can be used to restore back from hardbrick state. Attempting to do this backup alone is also dangerous on its own, i've warned u :angel:
Also special thanks to nikozzzzzz and AngSanley for chatting with me, giving idea and helping me in two days my phone got bricked :good:
Click to expand...
Click to collapse
PART 1 - TO BACKUP
THINGS THAT U NEED
Many spare times to read and follow this tutorial.
Your phone with battery not below 50%.
Busybox installed already.
Custom recovery installed already. I recommend cwm 6.0.2.8.
A reliable pc with adb installed.
A reliable usb cable.
Sdcard with more than 6GB free space. Later we will backup with custom recovery first and the backup could be 1GB, then came the whole disk backup that would be 4GB, and 1GB more for safe read/write io operation. So 1GB+4GB+1GB=6GB.
Click to expand...
Click to collapse
THE STEPS
Connect phone to pc via usb cable.
Mount usb storage and copy whole data from INTERNAL SD safely somewhere in the pc.
Boot into cwm recovery. At this time u should already have the requirement from above, the sdcard with at least 6GB free space inserted into the phone.
Do the usual whole rom backup using cwm. Backup to EXTERNAL SD not INTERNAL SD because we will format internal sd in next step.
Wipe internal sd, system, data, cache and dalvik cache from cwm.
Still in cwm and your usb cable should be connected between phone and pc, open windows cmd and do
Code:
adb shell
Still in cwm, and still connected between pc and phone using usb cable and still in windows cmd, do
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/mmcblk0.img
The backup process could take few minutes. The process is done when cmd showed something like
Code:
7634944+0 records in
7634944+0 records out
3909091328 bytes (3.9 GB) copied, 3367.93 s, 1.2 MB/s
The backup result is mmcblk0.img single file in root of your sdcard, around 3.9GB in size. U can transfer it to your pc and compress it if u want, after compress the size should be smaller, around 1.3GB. Make as many copy of it as u can and store it safely, in dropbox, in your sisters pc, in your grandma pc etc.
Now u can restore back your rom using previous cwm backup in step 4.
Backup process done.
Click to expand...
Click to collapse
Restore process continued to PART 2 below.

part 2 - to restore
things that u need
many spare times to read and follow this tutorial. The restore process can be long upto an hour.
obviously a hardbrick phone. The phone can be turn on by pressing power button but just vibrate, no nokia logo, no recovery mode, no fastboot mode, just blackscreen. Probably the bootloader is gone missing or corrupted. The phone is not hardbricked per se, its still alive if it vibrate after pressing power button. If the phone doesn't show any sign of life, doesn't even vibrate when pressing power button then probably battery depleted. Try to charge the battery using external charger, or find the same phone and charge the battery in it. If still doesn't work even after battery charge then probably thats total lost, only nokia aka microsoft mobile can repair, or until we find another way ourselves.
a reliable pc with a linux os installed. The pc need to have stable power source too because the restoring process could be long upto an hour or so. We dont want the pc to turn off or restart halfway of the process or risking totally messed up the phone disk. So what is linux? Where could u get it? Howto install it? Google for it yourself. I recommend linuxmint. The linux should also be installed, not in live mode because live mode usually unstable, again same as previous reason, we dont want unstable linux in live mode to make pc turn off or restart halfway of the restore process.
a reliable usb cable.
the backup file from previous part 1, the mmcblk0.img file. If u compress it earlier then decompress it.
Click to expand...
Click to collapse
the steps
remove from phone the back panel, battery, simcard and sdcard. Leave it for few seconds.
boot pc into linux.
copy backup file from previous part 1, the mmcblk0.img file into root of your home folder of your pc. Dont put it into any folder, just in root of your home folder.
reinsert phone battery and back panel but not the simcard and sdcard. Leave the simcard and sdcard out of the phone when doing restore process.
connect usb cable to pc and phone.
after connect pc and phone via usb cable, the phone should vibrate and linux probably would detect many new partitions mounted and it open many window in filemanager. Close all filemanager window that opens.
open linux terminal and do
Code:
sudo fdisk -l | grep 3909091328
and the terminal will ask for password
Code:
[sudo] password for user:
type your password (which will not be displayed for security reason) and press enter and it should give output like this
Code:
disk /dev/xxx: 3909 mb, 3909091328 bytes
thats what we want, especially the xxx. Remember the xxx, usually its only three letter long eg sdb, sdc, sde, sdf etc.. It may depends on your linux configuration so it may not be the same for everyone.
for this step we need internet connection for installing a package that not installed by default. Again still in linux terminal do
Code:
sudo apt-get update && sudo apt-get -y install pv
if the terminal ask for your password then just type it and press enter. The terminal will continue to give output and finally stop, the last line should be something like
Code:
setting up pv (1.2.0-1) ...
now close all filemanager window if u got any.
still in terminal do
Code:
sudo umount /dev/xxx
the xxx will be the one from step 7 above. If it asked again for password then type again your password and press enter. It'll give just one or two line of output after that, or nothing at all.
this is the crucial step here, to restore the disk. Still in terminal and phone still connected to pc via usb cable do
Code:
sudo pv -tpreb ~/mmcblk0.img | sudo dd of=/dev/xxx
again, the xxx will be the one from step 7 above. If the terminal asked for password again just type your password and press enter. It'll give output something like
Code:
859mb 0:12:50 [1.48mb/s] [======>....................................................................] 23% eta 0:42:30
and wait for it to finish. This will take long, probably an hour. In this time dont use the pc, don't watch movie, dont surf the net, dont do anything with it. Also dont touch the phone and the usb cable. Just leave it be, go out, take your girlfriend out, feed your cats or anything in the meantime. It'll finish when the percent goes 100% and give another output, something like
Code:
3.64GB 0:56:02 [1.11MB/s] [========================================>] 100%
7634944+0 records in
7634944+0 records out
3909091328 bytes (3.9 gb) copied, 3367.93 s, 1.2 mb/s
now just remove usb cable from pc and phone, remove the phone back panel and battery. Leave it for few seconds.
now reinsert the simcard, sdcard, battery and back panel.
turn on the phone by pressing power button and volume up to boot into recovery.
wipe internal sd, system, data, cache and dalvik cache from recovery.
i strongly suggest u got b-rom flashable zip file already in sdcard. Then just flash the b-rom zip. The b-rom i think doesn't provide kernel in it so u can flash my kernel. Why did i recommend b-rom? Because its pure stock based rom. We want to be on stock rom in first boot after the restore process.
restore process done. Now u just need to boot into rom, check all, ril, wifi, bt, wifi mac, bt mac, imei, serial etc if all in correct order.
Click to expand...
Click to collapse

Reserved #2

Sent from my Nokia_X using Tapatalk

Removed System Apps and cant reinstall them.
Can u please give me a twrp or cwm backed up file which i can use to restore my phone as i can easily boot into these recoveries.
:crying:

mdfzhi said:
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this TUTORIAL
* before doing anything! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
PART 1 - TO BACKUP
THINGS THAT U NEED
THE STEPS
Restore process continued to PART 2 below.
Click to expand...
Click to collapse
actually, I didn't understand many of your thread, in addition I'm tired reading by the way what I'm tryin to say is backing up doesn't need these whole steps. well, I backed up my stock Rom with few steps via CWM and the backup is only 1.73GB.please tell me the deference between mine and yours, I'm sure there's a different, but I can't notice it, and I appreciate your work.

Fikri adli supriatna
AngSanley said:
Sent from my Nokia_X using Tapatalk
Click to expand...
Click to collapse
:crying::crying::crying::crying::crying::crying::crying::crying:
how to cope with nokia x which hardbrick

hello
usuing cwm i formatted all partitions(boot,emmc..etc) and phone didn't boot or enter flash mod but vibrated with blank screen.
it detected as Qualcomm CDMA Technologies MSM but also as storage device,i cleaned partitions and created 1 partition with FAT file system.
now there is no any sign of life except Nokia emergency connectivity.
with or without battery only detects as below:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
in my case which all partitions are deleted and overwritten, how to restore?
any hope with repair boxes?

Hi
and thank you for your awesome Idea and everyone helped
10 sec after step 7 this command
dd if=/dev/block/mmcblk0 of=/sdcard/mmcblk0.img
Click to expand...
Click to collapse
Phone reboot to the System and no file on sd card
BTW Fresh system just repair it using atf box ...

never ever format partitions using windows(after phone bricked) because will cause the hard-brick and only can be fixed using atf box.
unbrick using atf box result in null imei,the only way is using another phones backup.
also using back up from another phone result in cloned imei.
if you format boot partition using CWM and reboot without installing kernel,your phone will brick.
best regard.

xsony.plus said:
never ever format partitions using windows(if bricked) because will cause hard-brick and can be fixed only using atf box.
unbrick using atf box result in null imei,the only way is using another phones backup.
also using back up from another phone result in cloned imei.
best regard.
Click to expand...
Click to collapse
Not Really i unbrick my phone using atf box and i have my original imei's :good:

murders10 said:
Not Really i unbrick my phone using atf box and i have my original imei's :good:
Click to expand...
Click to collapse
thanks but for me did:

Originally posted by mdfzhi
The backup created using this tutorial is low level whole disk backup, different from cwm or twrp backup because those recoveries will only backup certain partitions only, can be useful to restore back from the recoveries itself but became useless if got hardbricked.
Click to expand...
Click to collapse
But what is the difference between your type of backup and the CWM or TWRP type?
If your bootloader got stuck, why not reflash it (e.g. using Nokia X Flasher)?

no backup
guys what will i do if i didn't have backup as you suggested, i have a CWM backup and i have the RM-980 product images.
my ubuntu detects the partitions i just don't know which image belongs to which partition?
however all i need is the bootloader partition to be able to use fastboot which one is it and how can i write the bootloader .img to it
thank you very much

bootloader img
xWaLeEdOoOx said:
guys what will i do if i didn't have backup as you suggested, i have a CWM backup and i have the RM-980 product images.
my ubuntu detects the partitions i just don't know which image belongs to which partition?
however all i need is the bootloader partition to be able to use fastboot which one is it and how can i write the bootloader .img to it
thank you very much
Click to expand...
Click to collapse
I also do not have a backup, can anyone post an image of partitions NOKIA X derived from this statement?
Thanks in advance

kobzdik said:
I also do not have a backup, can anyone post an image of partitions NOKIA X derived from this statement?
Thanks in advance
Click to expand...
Click to collapse
You want to restore the phone to the original state?
Just flash it using this procedure: http://forum.xda-developers.com/showthread.php?t=2747262
Next, root the phone and install TWRP recovery.

Ano11 said:
You want to restore the phone to the original state?
Just flash it using this procedure: http://forum.xda-developers.com/showthread.php?t=2747262
Next, root the phone and install TWRP recovery.
Click to expand...
Click to collapse
Unfortunately the nokia x flasher does not detect the phone
The phone is defined as Qualcomm CDMA Technologies MSM

Maybe it helps to install "Nokia_Connectivity_Cable_Driver.msi" or the "nokia_x_usb_driver.zip"?
Otherwise, try the official Nokia software to do the flashing: NokiaCareSuite.

Ano11 said:
Maybe it helps to install "Nokia_Connectivity_Cable_Driver.msi" or the "nokia_x_usb_driver.zip"?
Otherwise, try the official Nokia software to do the flashing: NokiaCareSuite.
Click to expand...
Click to collapse
you still dont understand our issue my friend. nothing of that will work THERE IS NO FASTBOOT. NOKIA CARE flashes you device using FASTBOOT, if no FASTBOOT it cant detect your phone. Fastboot is located on partition mmcblk0p3 "/sys_boot" if you are willing to help and you own a NOKIA X RM-980 please head to my thread it has complete details about the issue
http://forum.xda-developers.com/nokia-x/general/fix-blank-screen-boot-format-sysboot-t3126617

xWaLeEdOoOx said:
you still dont understand our issue my friend. nothing of that will work THERE IS NO FASTBOOT. NOKIA CARE flashes you device using FASTBOOT, if no FASTBOOT it cant detect your phone. Fastboot is located on partition mmcblk0p3 "/sys_boot" if you are willing to help and you own a NOKIA X RM-980 please head to my thread it has complete details about the issue
http://forum.xda-developers.com/nokia-x/general/fix-blank-screen-boot-format-sysboot-t3126617
Click to expand...
Click to collapse
Ok, now I read the whole thread
I have two working Nokia X's here, so I gave this command:
dd if=/dev/block/mmcblk0 of=/sdcard/mmcblk0.img
But then I recieve this message: /dev/block/mmcblk0: cannot open for read: Permission denied
Enable USB debugging is enabled, phone is rooted...
EDIT:
Ok, I first gave the command in normal operation mode, now in recovery mode: that seems to work.
I guess I am backupping the whole phone now (mmcblk0) which will took about 15 minutes (4.1 MB/s). A backup of the boot partition only (mmcblk0p3) just a few seconds.
Please see the attachment for the boot partition. Product code of my phone: RM-980 NDT IMEA KE - 059T9F4.
Please let me know if it helps you guys!!

How to Root Nokia X after new update ( 1.2.4.1) without USB Drivers

Hello,
I've update my Nokia X in new update official (1.2.4.1 & plateforms 1.2) -> update is ok BUT, when i connected my phone on my PC, drivers are not recognized ... :/ .... so i found with web (fb group )
1- Download this How to root without drivers
2 - Copy UPDATE-SuperSU-v2.01.zip in your SD card or internal memory (folder Download for exemple)
3 - Boot into bootloader :
a) switch off your phone
b) then press power and volum down and when your device vibrates release the power button ONLY (no volum down)
c) after 15second release the volume down and connect your phone on USB (PC)
d) click on recovery.bat (folders download) : a command prompt will open,and after closed or whrite "done" -> disconnect your phone
e) remove battery and reinsert battery
f) boot into recovery (power + volum up) and flash UPDATE-SuperSU-v2.01.zip next reboot ...
.. and now, your device is root ... you can swap memory extern for exemple ... no need USB drivers
(NB : after this operation all OK, but USB drivers no found .. so wait for this ...)

i'll try this one

yoann44 said:
Hello,
I've update my Nokia X in new update official (1.2.4.1 & plateforms 1.2) -> update is ok BUT, when i connected my phone on my PC, drivers are not recognized ... :/ .... so i found with web (fb group )
1- Download this How to root without drivers
2 - Copy UPDATE-SuperSU-v2.01.zip in your SD card or internal memory (folder Download for exemple)
3 - Boot into bootloader :
a) switch off your phone
b) then press power and volum down and when your device vibrates release the power button ONLY (no volum down)
c) after 15second release the volume down and connect your phone on USB (PC)
d) click on recovery.bat (folders download) : a command prompt will open,and after closed or whrite "done" -> disconnect your phone
e) remove battery and reinsert battery
f) boot into recovery (power + volum up) and flash UPDATE-SuperSU-v2.01.zip next reboot ...
.. and now, your device is root ... you can swap memory extern for exemple ... no need USB drivers
(NB : after this operation all OK, but USB drivers no found .. so wait for this ...)
Click to expand...
Click to collapse
Fixed the adb drivers though: http://forum.xda-developers.com/nokia-x/general/fix-updated-adb-drivers-nokia-x-v1-2-4-1-t2835827
Still, nice job.

Dom3616 said:
Fixed the adb drivers though: http://forum.xda-developers.com/nokia-x/general/fix-updated-adb-drivers-nokia-x-v1-2-4-1-t2835827
Still, nice job.
Click to expand...
Click to collapse
when i try to install the .zip file .it say installation aborted?anyone?help please?578

Can't enter to Bootloader mode
yoann44 said:
Hello,
I've update my Nokia X in new update official (1.2.4.1 & plateforms 1.2) -> update is ok BUT, when i connected my phone on my PC, drivers are not recognized ... :/ .... so i found with web (fb group )
1- Download this [....]
2 - Copy UPDATE-SuperSU-v2.01.zip in your SD card or internal memory (folder Download for exemple)
3 - Boot into bootloader :
a) switch off your phone
b) then press power and volum down and when your device vibrates release the power button ONLY (no volum down)
c) after 15second release the volume down and connect your phone on USB (PC)
d) click on recovery.bat (folders download) : a command prompt will open,and after closed or whrite "done" -> disconnect your phone
e) remove battery and reinsert battery
f) boot into recovery (power + volum up) and flash UPDATE-SuperSU-v2.01.zip next reboot ...
.. and now, your device is root ... you can swap memory extern for exemple ... no need USB drivers
(NB : after this operation all OK, but USB drivers no found .. so wait for this ...)
Click to expand...
Click to collapse
I can't enter Bootloader mode.. it just nokia logo only for long time...

cheppimme said:
I can't enter Bootloader mode.. it just nokia logo only for long time...
Click to expand...
Click to collapse
Flash stock rom. You did something wrong.
Sent from my Nokia_X using XDA Free mobile app

I'm confused.
Dom3616 said:
Flash stock rom. You did something wrong.
Click to expand...
Click to collapse
Can you tell me more how to do for details?

cheppimme said:
Can you tell me more how to do for details?
Click to expand...
Click to collapse
Search Nokia X General section.

error

Mr.MadScientist said:
Hello.
Me too.
I can not install your update.
I allocated it into the sd card, I started the recovery, but it gave me out "installation aborted" .
I tried to install the cwm recovery with nokia x manager (with the right drivers and everything as you said), but the process hangs at nokia initial logo , and is necessary to remove the battery (after 60 min) for restart the phone. Nokia flash , however, if I try to install it on windows professional 32 bit ( the only windows I have, because I use linux) , tell "is not an application for 32-bit" .
Thanks for your work.
Click to expand...
Click to collapse
Then goto CWM Recovery Thread for Nokia X and learn how to manually flash it.
The update package won't work on Stock Recovery.

Dom3616 said:
Then goto CWM Recovery Thread for Nokia X and learn how to manually flash it.
The update package won't work on Stock Recovery.
Click to expand...
Click to collapse
I apologize for my error but I had write on the wrong thread.
I have not tried the solution proposed here , I tried the solution proposed in the other thread, with the update 1.2.4.1 .
Unfortunately they were open both and I responded to the wrong one.
I hope you will forgive me and especially yoann44 .
I can not download the package because i think that in my country is impossible to pay . I continue to put the code but says it is wrong.
Nor with safari or google chrome I can finish the procedure.
How can I do?

I don't understand about what are you saying, I think you phone is full brick if you are unable to enter in Bootloader Mod, so check your productcode and discribe you problem
Just Download and Follow the Guide from Below Links if you are able to enter in bootloader mode (Half Brick). Otherwise claim you warranty.
Nokia X Flasher are free by Devs.
Nokia X Offical Rom

selmopn said:
i'll try this one
Click to expand...
Click to collapse
and?
Ok now I tried it but without success.
I have done everything.
However :
1) "done" it never arrived even after half an hour
2 ) I repeated the operation
3 ) at the end everything is back (hopefully) normal without root
For me, this method does not work: installation aborted.

So you are removing some apps from system/app
Sent from my Nokia_X

adeebulrehman said:
So you are removing some apps from system/app
Sent from my Nokia_X
Click to expand...
Click to collapse
Yes, facebook , twitter and one drive .
It can be the cause?
If it is necessary I can do a factory reset ...
I do it?

Mr.MadScientist said:
Yes, facebook , twitter and one drive .
It can be the cause?
If it is necessary I can do a factory reset ...
I do it?
Click to expand...
Click to collapse
You can remove app the apps that you don't need.
[MOD][Flashable] Remove all Bloatware apps from system/app Partition within 2 Seconds
Attached is the flash able zip file read the instruction from above post and edit script file from attached as per you requirement.
I have removed Mix Radio, Music, Store, Launcher, Keyboard and replaced them with Google Ones

adeebulrehman said:
You can remove app the apps that you don't need.
[MOD][Flashable] Remove all Bloatware apps from system/app Partition within 2 Seconds
Attached is the flash able zip file read the instruction from above post and edit script file from attached as per you requirement.
I have removed Mix Radio, Music, Store, Launcher, Keyboard and replaced them with Google Ones
Click to expand...
Click to collapse
Thank you very much! But to be sure I 've done the factory reset and I will use after your precious advice , the apps have been restored , but the process does not work've done the factory reset, the apps have been restored, but the process does not work.

OK Try It, If you need help let me know

yoann44 said:
Hello,
I've update my Nokia X in new update official (1.2.4.1 & plateforms 1.2) -> update is ok BUT, when i connected my phone on my PC, drivers are not recognized ... :/ .... so i found with web (fb group )
1- Download this How to root without drivers
2 - Copy UPDATE-SuperSU-v2.01.zip in your SD card or internal memory (folder Download for exemple)
3 - Boot into bootloader :
a) switch off your phone
b) then press power and volum down and when your device vibrates release the power button ONLY (no volum down)
c) after 15second release the volume down and connect your phone on USB (PC)
d) click on recovery.bat (folders download) : a command prompt will open,and after closed or whrite "done" -> disconnect your phone
e) remove battery and reinsert battery
f) boot into recovery (power + volum up) and flash UPDATE-SuperSU-v2.01.zip next reboot ...
.. and now, your device is root ... you can swap memory extern for exemple ... no need USB drivers
(NB : after this operation all OK, but USB drivers no found .. so wait for this ...)
Click to expand...
Click to collapse
Why it's necessary to pay from software that is free form the autor's site?
The proposed solution isn't working on 1.2.4.1 is there another usefull solution to root?

joaofsantosj said:
Why it's necessary to pay from software that is free form the autor's site?
The proposed solution isn't working on 1.2.4.1 is there another usefull solution to root?
Click to expand...
Click to collapse
pay off? who said he had to pay ??? lol ... my tutorial is functional! anyway, there's no point really, because since then, the problem was corrected in USB drivers, so possibility via toolkit x or nokia manager ^^

Made a Huge Mistake: Formated and Cannot Restart the Phone! Help!!

I didn't know when I was formating my phone in CWS recovery mode. But when I tried to restart the phone, is showed me blank screen and even there is no vibration of starting.
I am really mad at this, how to get back to start my phone?

if you wanna fresh nokia x stock rom then download nokia care suite from here - http://www.seidea.com/2015/05/20/nokia-care-suite-pst-5-0-5-6-134-1513/
and stock nokia rom from here - http://cellomania.com/ffu/

pyumredkar said:
if you wanna fresh nokia x stock rom then download nokia care suite from here - http://www.seidea.com/2015/05/20/nokia-care-suite-pst-5-0-5-6-134-1513/
and stock nokia rom from here - http://cellomania.com/ffu/
Click to expand...
Click to collapse
I will try what you suggest me.
But there is NO VIBRATION, and NO DISPLAY. I should slap myself for formatting the phone without understanding the risk.

Love Psyche said:
I will try what you suggest me.
But there is NO VIBRATION, and NO DISPLAY. I should slap myself for formatting the phone without understanding the risk.
Click to expand...
Click to collapse
formatting system partition from custom recovery also formats bootloader partition. you need to follow this guide - http://forum.xda-developers.com/nokia-x/general/fix-blank-screen-boot-format-sysboot-t3126617

pyumredkar said:
formatting system partition from custom recovery also formats bootloader partition. you need to follow this guide - http://forum.xda-developers.com/nokia-x/general/fix-blank-screen-boot-format-sysboot-t3126617
Click to expand...
Click to collapse
Is it worked for when there is NO vibration along with blank screen?
And if so, please upload bootloader for RM-1053 model (X+).

I would suggest you that you must flash nokia x bootloader partition for right now until ur device starts. because when you flash nokia x+ rom with care suite your appropriate bootloader img will be flashed correctly from nokia care suite

In the guide you provided:http://forum.xda-developers.com/nokia-x/general/fix-blank-screen-boot-format-sysboot-t3126617, at 4th point of "How to fix", it said your phone should be vibrated.
But my phone cannot vibrate. Have you got my point? It has NO VIBRATION, not just only blank screen.

it is the last option for repairing ur device, anotherly it seems hardbricked and Microsoft stopped developing repairing spare parts of the device. so no any other hope.

Do you mean, I have no solution for this issue?

maybe

I still have hope and waiting for help about the issue.

I thought I would have a solution, but nobody showed me a solution. Maybe there is no solution!

At first check, if battery is properly inserted (maybe some pins are bent?), then recharge battery.
Next try again with this tutorial: http://forum.xda-developers.com/nokia-x/general/fix-blank-screen-boot-format-sysboot-t3126617
You can download latest Nokia X bootloader from http://cellomania.com/ffu/ (type your CODE from sticker inside device and download RM980_1.2.4.1_boot.img file)
If it won't work, run terminal (in Ubuntu), connect phone again, wait some seconds, type
Code:
dmesg >> ~/dmesg.log
and send dmesg.log file (use file manager to find it) to any pastebin-like service, so we'll be able to check, if Ubuntu can detect the phone.

[SOLVED] Help Flashing Lineage OS

EDIT:SOLVED -- READ BELOW:
I finally got it flashed by following a few guides here which I will link, and try to break it down easier for someone else to come across and follow. I thought I bricked my phone (flashed LineageOS then rebooted, phone did not show anything on screen, full black screen) but after following a few guides I got it solved.
If you get bricked, or just want to follow a clean perfect install, please start below (Skip to step 2 if you are starting fresh, if you have soft-bricked your device start from step 1)
1. Bricked it and had to execute QDLoader 9008 fix again.
Tutorial is easier than it looks, do not fear, if you have soft-bricked your device and see a black screen, go ahead and go through the qdloader brick solution.
2. From factory recovery updated to Version WW-16.1220.1909.193.
If you have started fresh, I would highly recommend updating to the more updated firmware first. For me this worked, and I suggest updating to get a more current kernel, which may play better with Lineage OS install. To install a newer stock firmware linked above, download the ~2GB Firmware above, and save it to your Minimal ADB / Fastboot folder. Power off your device, after it has been successfully restored (if you bricked it) or you want to start off fresh and get the install right the first time. With your device powered off, Hold Volume UP and then Hold Power Button until the Fastboot menu appears. Use your volume keys to select Recovery, then press Power button to enter the STOCK Recovery (we are still on stock firmware with stock recovery). When in stock recovery select install from ADB. We are going to push the install via ADB (I tried dragging the firmware to the internal and selecting install ZIP and that didnt work).
Go into your Minimal ADB / Fastboot folder on your computer and open command prompt by holding Shift+Control and Right clicking and then selecting open command prompt here.
Now, enter the following command in the command prompt and hit enter:
adb devices
This command will show if any fastboot device is connected. If it doesn’t show, then please check the drivers are installed properly and try again.
If your device is listed, then type the command given below and press enter:
adb sideload File_name.zip
^^This will be the ~2GB Firmware file downloaded above
Wait until the installation process completes.
Once the installation process is complete, restart your device.
Done. You have successfully upgraded the Asus ZenFone 6 to the newer firmware, please continue.
3. Downloaded OTA 16.1220.1909.193 to 16.1220.1909.194, renamed it to UL-ASUS_I01WD-ASUS-16.1220.1909.194-1.1.1-user.zip and placed into root of internal memory.
When I disconnected USB cable (or rebooted, not sure), I was prompted with update notification. I have updated it. Either way, reboot your device if you don't see the notification, and look in your notifications to see something saying: System Update Detected Proceed with Update - and select it and update.
4. Now that your phone is 100% Updated with the newest firmware, let's follow another guide I found here:
I assume you're on a fresh Android 9 stock ROM, or just finished restoring your phone with the Flashall_AFT.cmd from this tutorial.
You should at least boot once on the system, and disable any PIN or password to unlock your phone (hence putting a default password for the FBE).
Download the latest OFFICIAL TWRP.x.x.img (which we'll use to boot on it), and it's installer to install it later (TWRP.x.x.zip) if you want to use it.
LineageOS installation steps :
Reboot to bootloader (=fastboot mode), connect to your PC and boot on TWRP :
Command:
fastboot boot TWRP.x.x.img
Once on TWRP, you can see that we're on slot A (Menu > Reboot). Now go to wipe > factory reset and then wipe system (technically I suspect this only wipes slot A, but do it anyway, don't worry about the errors!)
Now go to Install > flash the newest official LOS_latest.zip. What happens here is that the LOS installer will flash LOS on the inactive slot (slot B in our case). And will also install the LOS recovery (on both slots it seems).
Reboot to recovery : your phone automatically switches slots and will boot the LineageOS recovery (Don't fear, we don't need TWRP right now, just go along with this step) on slot B.
On the LineageOS recovery, do factory reset (which seems to be a full /data format in fact, thus removing any previous encryption AND all your data on internal storage). If you want to use Magisk, go to the recovery's install menu and sideload it now
Use code:
adb sideload Magisk-v20.3.zip
Now reboot to system. It might take a while (one or 2 loops in my case), but your phone should boot, or in some cases will end up on LOS recovery asking for a 'factory data reset' (then do it and reboot again).
Once booted on your LOS rom, you can define a pin or password to lock your phone (that'll be the FBE decryption password).
Now if you want to use TWRP, reboot to bootloader and boot again on TWRP.img (step 1)
From TWRP > Install > flash TWRP.x.x.zip (that is, the TWRP installer). It installs on both slots by default. If you had installed Magisk, you have to flash it again (because anything modifying the boot.img - like the TWRP installer in our case - will erase it).
You can now reboot to system and enjoy LOS

Thanks for the nice documentation. I've recently also struggling with installing a custom ROM and this clears some things up.
Wanted to ask, if you also have the audio issue that 1) callers hear an echo of themselves, and 2) the bottom speaker is active when receiving a call?
Thanks.

abprie said:
Thanks for the nice documentation. I've recently also struggling with installing a custom ROM and this clears some things up.
Wanted to ask, if you also have the audio issue that 1) callers hear an echo of themselves, and 2) the bottom speaker is active when receiving a call?
Thanks.
Click to expand...
Click to collapse
Haven't actually put my sim in yet to make calls, will let you know later today, sorry about the delay!

I had previously attempted this a number of months ago, and managed to soft brick my Zenfone 6 several times, eventually kind of giving up and just using the stock firmware.
I tried again back on Memorial Day in the US. This time around, I bricked it hard. Could not get device to power on in any fashion. PC would not "see" USB connection at all.
I returned it to ASUS for service, and they've charged me a little over $200 to repair it. The only problem they noted was, "Device is rooted/unlock". So I have no way of knowing if their diagnosis is based on actual inspection of the device, or if they're just replacing the SOC on the basis that I used their official bootloader unlock tool, thus registering my phone's S/N.
Just a little caveat emptor for anyone attempting to use this guide. I was able to get TWRP to load, and succesfully updated the stock firmware, but any and all attempts to load the Lineage image failed.
Eventually one of them soft bricked my phone as before, and I think my mistake was interrupting the soft brick rewrite procedure by prematurely unplugging my phone from the PC.

I had a similar issue: Bricked and totally unresponsive phone (or so I thought until I realised the screen was flashing very faintly when I switched off the lights - I could only tell in the dark due to how dim the flashing on the display was) where de "Powered by Android" logo kept flashing for a millisecond and in a loop. None of the button combinations worked so I couldn't switch completely off, access recovery/fastboot, and my computer wouldn't recognise the phone when I connected it via USB. I ended up buying an EDL cable for deep flashing Qualcomm phones (€9) and within minutes I was back up and running. All solved.

~SilverLad~ said:
I had a similar issue: Bricked and totally unresponsive phone (or so I thought until I realized the screen was flashing very faintly when I switched off the lights - I could only tell in the dark due to how dim the flashing on the display was) where de "Powered by Android" logo kept flashing for a millisecond and in a loop. None of the button combinations worked so I could switch completely off, access recovery/fastboot, and my computer wouldn't recognize the phone when I connected it via USB. I ended up buying an EDL cable for deep flashing Qualcomm phones (€9) and within minutes I was back up and running. All solved.
Click to expand...
Click to collapse
Can you post a link to where you purchased the cable?

abprie said:
Can you post a link to where you purchased the cable?
Click to expand...
Click to collapse
I bought it from Amazon. The one I bought is out of stock now, but there are a lot of them available (from other brands/sellers). This one for example - is the one that most resembles the one I actually bought: https://www.amazon.es/ASHATA-tel%C3%A9fono-reparaci%C3%B3n-Adaptador-Engineering/dp/B086WZMFKW/ref=sr_1_18?__mk_es_ES=%C3%85M%C3%85%C5%BD%C3%95%C3%91&dchild=1&keywords=cable+edl&qid=1597417614&sr=8-18

Since the thread is already on topic, could I flash lineage os while being on a custom rom? I have Bliss ROM on partition A and stock on B. Is it possible to have both Bliss and Lineage in dual boot?
Also, maybe a little off topic, the partition A/B scheme was intended to be used as a dual OS boot like normal PCs? Because right now I can select A and boot Bliss, select B and boot stock, I don't get why the procedure for flashing Lineage OS is so convoluted(requires having stock both on B and A?!) since both partition seems to be standalone and separated from each other.

~SilverLad~ said:
I bought it from Amazon. The one I bought is out of stock now, but there are a lot of them available (from other brands/sellers). This one for example - is the one that most resembles the one I actually bought: https://www.amazon.es/ASHATA-tel%C3%A9fono-reparaci%C3%B3n-Adaptador-Engineering/dp/B086WZMFKW/ref=sr_1_18?__mk_es_ES=%C3%85M%C3%85%C5%BD%C3%95%C3%91&dchild=1&keywords=cable+edl&qid=1597417614&sr=8-18
Click to expand...
Click to collapse
Hey there, what's the process around using this cable?

vikashhero said:
Hey there, what's the process around using this cable?
Click to expand...
Click to collapse
The cable itself (on its own), doesn't seem to "do" anything, but is paramount in reaching the right area, in order to fix the problem by means of the appropriate instructions and files. I can't recall where I ended up getting the right instructions from - as I researched quite a bit, and did a lot of "trial an error" before getting it right - so I'm sorry but I can't refer you directly to them via link (so that whoever posted them originally gets the credit they deserve), but this is what I ended up doing (on a WINDOWS machine) based on said instructions:
DOWNLOADS:
- Qualcomm drivers: https://androidfilehost.com/?fid=11410963190603857508
- Firmware with scripts: https://androidfilehost.com/?fid=1395089523397969054
- Latest official ASUS firmware from the ASUS webpage (download and place it in a memory card)
- (If you don't already have it on your WINDOWS machine): download and install Microsoft Visual C++ 2010 Service Pack 1 Redistributable Package
PROCEDURE:
1- Install the Qualcomm drivers
2- Unpack the downloaded firmware containing the scripts
3- Place the memory card in the phone's slot (with the latest official ASUS firmware already in it)
4- Power off the phone by VolumeDown + Power buttons (keep them pressed for about <25 seconds)
5- Connect the phone to the computer via the EDL cable and press the button on the EDL cable (there was an extra bit on what to do with a archive from the drivers file if your computer doesn't recognise the port straight away, but it wasn't necessary in my case so I didn't keep that step/archive name in my notes... I'm afraid you will have to search for it like I did if you come across that issue).
6- Start update_image_EDL.bat script from the unpacked firmware
7- After the script in step 6 finishes, start script flashall_AFT.cmd
8- Start bootloader
9- Go to stock recovery mode and install the ASUS firmware from the memory card
X- (Instructions also suggested to repeat steps 8 & 9 again at this point - for a second time - but in my case it wasn't needed)
I hope this helps.

~SilverLad~ said:
The cable itself (on its own), doesn't seem to "do" anything, but is paramount in reaching the right area, in order to fix the problem by means of the appropriate instructions and files. I can't recall where I ended up getting the right instructions from - as I researched quite a bit, and did a lot of "trial an error" before getting it right - so I'm sorry but I can't refer you directly to them via link (so that whoever posted them originally gets the credit they deserve), but this is what I ended up doing (on a WINDOWS machine) based on said instructions:
DOWNLOADS:
- Qualcomm drivers: https://androidfilehost.com/?fid=11410963190603857508
- Firmware with scripts: https://androidfilehost.com/?fid=1395089523397969054
- Latest official ASUS firmware from the ASUS webpage (download and place it in a memory card)
- (If you don't already have it on your WINDOWS machine): download and install Microsoft Visual C++ 2010 Service Pack 1 Redistributable Package
PROCEDURE:
1- Install the Qualcomm drivers
2- Unpack the downloaded firmware containing the scripts
3- Place the memory card in the phone's slot (with the latest official ASUS firmware already in it)
4- Power off the phone by VolumeDown + Power buttons (keep them pressed for about <25 seconds)
5- Connect the phone to the computer via the EDL cable and press the button on the EDL cable (there was an extra bit on what to do with a archive from the drivers file if your computer doesn't recognise the port straight away, but it wasn't necessary in my case so I didn't keep that step/archive name in my notes... I'm afraid you will have to search for it like I did if you come across that issue).
6- Start update_image_EDL.bat script from the unpacked firmware
7- After the script in step 6 finishes, start script flashall_AFT.cmd
8- Start bootloader
9- Go to stock recovery mode and install the ASUS firmware from the memory card
X- (Instructions also suggested to repeat steps 8 & 9 again at this point - for a second time - but in my case it wasn't needed)
I hope this helps.
Click to expand...
Click to collapse
Hey buddy, I appreciate your reply. The cable is on its way but I got a bit fiesty and opened up the phone to short the two contacts. This did the trick for me, got me back into EDL mode, and I was able to flash the latest firmware. On that topic, I'm trying to find the most suitable firmware version to run LineageOS 17 on the phone. I grabbed Mauro's TWRP to temporarily boot into which allowed me to flash the latest Asus image from their site. I guell I'll just carry on from there.

vikashhero said:
Hey buddy, I appreciate your reply. The cable is on its way but I got a bit fiesty and opened up the phone to short the two contacts. This did the trick for me, got me back into EDL mode, and I was able to flash the latest firmware. On that topic, I'm trying to find the most suitable firmware version to run LineageOS 17 on the phone. I grabbed Mauro's TWRP to temporarily boot into which allowed me to flash the latest Asus image from their site. I guell I'll just carry on from there.
Click to expand...
Click to collapse
As far as I understand, that's pretty much what the cable does actually... I also came across that method along my research, but I didn't want to risk opening the phone up. Since you are in the "flashing state": be careful with some of the instructions out there - I flashed through TWRP as I have been doing all these years with other phones, following specific instructions for each ROM I've tried, and I had nothing but issues until I flashed through ADB. I still don't know why I was getting the "No OS" warning all the time despite flashing correctly from TWRP (contemplating the A/B partitions matter), but none worked...

~SilverLad~ said:
As far as I understand, that's pretty much what the cable does actually... I also came across that method along my research, but I didn't want to risk opening the phone up. Since you are in the "flashing state": be careful with some of the instructions out there - I flashed through TWRP as I have been doing all these years with other phones, following specific instructions for each ROM I've tried, and I had nothing but issues until I flashed through ADB. I still don't know why I was getting the "No OS" warning all the time despite flashing correctly from TWRP (contemplating the A/B partitions matter), but none worked...
Click to expand...
Click to collapse
Appreciated but I'm all sorted. I believe my pitfall was not using the copy-partitions .zip file detailed in the instructions. I had no idea that was a thing. Was extra careful this time and now I'm on the ROM I need.
I ****ing hate A/B partitioned phones, makes custom ROMs such a chore. Sort of getting fed up with phones in general but at least this is working well for now.

vikashhero said:
Appreciated but I'm all sorted. I believe my pitfall was not using the copy-partitions .zip file detailed in the instructions. I had no idea that was a thing. Was extra careful this time and now I'm on the ROM I need.
Click to expand...
Click to collapse
Happy to hear that Indeed be careful - this is a tricky phone...
vikashhero said:
I ****ing hate A/B partitioned phones, makes custom ROMs such a chore. Sort of getting fed up with phones in general but at least this is working well for now.
Click to expand...
Click to collapse
Same here. It was so easy to do the Samsungs "back in the day", and you always had ODIN as a fallback if things went south. But this "A/B" partition nonsense (as well as other useless changes they introduce every time they "upgrade" Android, or certain structure modifications every so often when a new phone comes out) are a pain in the butt! Changes clearly aimed at making things more annoying/difficult for us people who don't want standard/corporate/unnecessarily bloated phones... Actually (as a former Blackberry user) I was tempted to get one of these Android based Blackberrys (the KEY2), but I didn't in the end precisely due to the fact that the bootloader can't be touched, and it can be rooted...

vikashhero said:
Appreciated but I'm all sorted. I believe my pitfall was not using the copy-partitions .zip file detailed in the instructions. I had no idea that was a thing. Was extra careful this time and now I'm on the ROM I need.
I ****ing hate A/B partitioned phones, makes custom ROMs such a chore. Sort of getting fed up with phones in general but at least this is working well for now.
Click to expand...
Click to collapse
I want to switch to because the latest security update (August 2020) by Asus is soft bricking the phone for many users,
but I am seeing a few reports about some bugs (like the phone is stuck in the lineage boot symbol and cellular errors) in lineage os and also seeing few post with a lot of installation errors (like soft and total bricking) etc. and for me in developers options I'm not seeing the OEM and advanced boot options.(in my asus stock os) I just found out that I have to download the Unlock Boot loader apk separately from asus and install it using command prompt so I don't know how to proceed.
Can you please elaborate on how you actually did it with your Asus Zenfone 6(2019), I am a total noob in this and I also couldn't understand the partition a and b parts too.