Database Users

Device stuck on "Sony" screen FIX

There has been a lot of cases of this happening lately, so to save time here is the answer
So...
You have successfully soft-bricked your phone, and now are worried / wondering how to get out?
Easy
You will need a functioning computer with ADB drivers installed (flashtool has a driver installer you can use), and an internet connection
~~On Computer~~
First things first, you will need to Download FLASHTOOL - and you will also need to download the FIRMWARE for your phone (they are all the same - D5833/D5803)
Now upon opening flashtool it will say you need to move files from *flashtool/folder* to *.flashtool/folder* -- move the files and also move the .ftf (firmware file) to this new folder
Once completed that click the lightning bolt in flashtool and click the firmware you downloaded and click flash
~~On Device~~
Hold POWER + VOLUME buttons down until the device vibrates 3 times (It is now turned off)
While turned off hold the VOLUME DOWN button while plugging phone into the computer (should see the LED turn red - green/blue then off)
Flashtool will now say device is connected in flashmode and will flash the firmware
DONE
note for windows 8 + users
adb drivers do not always work with win8 and above, please follow these steps to get adb to work
arsradu said:
Or, you can do this:
run cmd.exe as Administrator (right click -> Run as administrator)
type this command:
Code:
bcdedit /set testsigning on
reboot
install drivers. Agree to installing unsigned drivers when you see the pop-up. Drivers should be correctly installed now.
run cmd.exe as Administrator (right click -> Run as administrator)
type this command:
Code:
bcdedit /set testsigning off
reboot
That's all.
Click to expand...
Click to collapse

I learnt pretty early to have a backup file, saved in multiple locations with all the tools needed to recover from the soft brick. Shat myself first time it happened, phone was only a few weeks old.

mrrflagg said:
I learnt pretty early to have a backup file, saved in multiple locations with all the tools needed to recover from the soft brick. Shat myself first time it happened, phone was only a few weeks old.
Click to expand...
Click to collapse
haha same
Only put this tutorial up because some people might not have flashtool / know how to use it
or do not know how to get the firmware files

nzzane said:
haha same
Only put this tutorial up because some people might not have flashtool / know how to use it
or do not know how to get the firmware files
Click to expand...
Click to collapse
Thank you!
For Windows, maybe it would be nice to mention that it's not gonna work (by default) in Windows 8, 8.1 and 10, so Windows 7 is recommended for this.
There is, however, a way (actually, there are 2, but I found one of them to be easier than the other) to get those drivers installed on Windows 8 and above.
You can find it here.

nzzane said:
There has been a lot of cases of this happening lately, so to save time here is the answer
So...
You have successfully soft-bricked your phone, and now are worried / wondering how to get out?
Easy
You will need a function computer with ADB drivers installed (flashtool has a driver installer you can use) and an internet connection
~~On Computer~~
First things first, you will need to Download FLASHTOOL - and you will also need to download the FIRMWARE for your phone (they are all the same - D5833/D5803)
Now upon opening flashtool it will say you need to move files from *flashtool/folder* to *.flashtool/folder* -- move the files and also move the .ftf (firmware file) to this new folder
Once completed that click the lightning bolt in flashtool and click the firmware you downloaded and click flash
~~On Device~~
Hold POWER + VOLUME buttons down until the device vibrates 3 times (It is now turned off)
While turned off hold the VOLUME DOWN button while plugging phone into the computer (should see the LED turn red - green/blue then off)
Flashtool will now say device is connected in flashmode and will flash the firmware
DONE
note for windows 8 + users
adb drivers do not always work with win8 and above, please follow these steps to get adb to work
Click to expand...
Click to collapse
Thank you thank you thank you!!! I almost cried
Stupid me... After installing locked dual recorver, i wiped the system and switched the phone off... It game me a warning sign saying there was no OS, and I said yup, no worries (thought it was like PCs where boot OS has nothing to do with Android).
Phone got stuck on the Sony logo and the only way to do anything was to use the hard reset button!! YOU SAVED ME!

Bump
Many people still get themselves stuck in this issue :3

yep stuck on Sony screen
here what flash tool says;
12/048/2017 21:48:23 - INFO - Selected Bundle for Sony Xperia Z3 Compact(D5803). FW release : 23.0.A.2.93. Customization : Customized CE1
12/048/2017 21:48:23 - INFO - Preparing files for flashing
12/048/2017 21:48:24 - INFO - Please connect your device into flashmode.
12/048/2017 21:48:32 - INFO - Device connected in flash mode
12/048/2017 21:48:32 - INFO - Opening device for R/W
12/048/2017 21:48:32 - INFO - Reading device information
12/048/2017 21:48:32 - INFO - Phone ready for flashmode operations.
12/048/2017 21:48:32 - INFO - Opening TA partition 2
12/048/2017 21:48:32 - INFO - Current device : D5803 - YT9115XKA6 - 1288-7915_R2D - 1285-6521_23.5.A.1.291 - GLOBAL-LTE_23.5.A.1.291
12/048/2017 21:48:32 - INFO - Closing TA partition
12/048/2017 21:48:32 - INFO - Start Flashing
12/048/2017 21:48:32 - INFO - Ending flash session
12/048/2017 21:48:32 - ERROR - Can't read a byte value
12/048/2017 21:48:32 - ERROR - Error flashing. Aborted

I was able to successfully apply erased firmware by following your instructions.....Thanks a ton

[guide] repair hard bricked devices with deleted bootloader (sboot)

I'm writing this in android development section because this is only section for both models, i hope this is not a problem.
Also i want to say thanks to sataccount from gsmhosting, he found working map at the end.
This guide is for hard bricked phones, where bootloader is destroyed and there is no any tools which recognize phone.
When you connect phones without bootloader Windows detects them as exynos7420 in other devices in device manager.
All this is achieved using trial/error method and I still don't know real sboot map and where is what in sboot.bin.
What i found till now is that sboot consist from this parts:
1. fwbl1 bl1
2. bl2 bl2
3. el3_mon el3
4. bootloader bootloader
5. tzsw tzsw
I repaired my g925a and have files only for this model, but i will try to explain how to prepair files for any other model.
We have to use same version of bootloader which was previosly in phone, or if you are unsure use latest sboot.bin.
Download tools: http://www.mediafire.com/file/sg5m2ti3k6a63z5/USB_Down_Load_32bit.zip
In folder USB_DownLoad_Tool there is a folder Disk1
Connect phone and hold power button.
Windows will detect exynos7420 device, install Driver:
click manually,
com and lpt ports,
have disk,
point to data1 folder.
Don't run setup from Data1 folder!!!
Now we have to copy
WinDNWApi.dll
WinDNWApi.lib
in:
c:\Program Files\SAMSUNG\Exynos USB Driver\Drivers\
Probably there is no this folder, just create it and copy 2 files.
Don't copy WinDNWApi.dat as it is written in original manual, this file is for older exynos chip and procedure will not work, everything works without this file (it only has maps for 5250 and some other cpu)
Now we have to create boot files.
Download sboot.bin for your device, as i wrote best to find same bootloader which was in device before brick.
In some hex editor create 4 files (i'm using frhed, just click copy, enter offset, new file, paste, save and over again for all four files) with this map (again thanks to sataccount):
Novi1.bin 0..0x1FFF (size 0x2000 or 8192 )
Novi_2.bin 0x2000..0x31FFF (size 0x30000 or 196608)
Novi_3.bin 0x32000..0x3dfff (size 0xC000 or 49152)
Novi4.bin 0x3E000..10EFFF (size 0xD1000 or 856064)
This is all without tzsw. If phone still does not enter to odin mod, make last file from 0x3E000 to the end of the file (18F10F) and try again.
Start multiuploader.exe
Connect phone and hold power button.
Browse and find SH-usb-booting.cfg (in attached file proba folder, that is where you will probably prepare all boot files)
click start and phone will enter odin mode.
Start odin and flash sboot and everything else.

First of all thanx this is a real sharing is caring thing.I'm seeing a way to downgrade bootloader here as tzsw gets separated well this can be done by daring dev who can take risks.

I'm not sure about downgrading.
When i tried to repair my phone, first i tried with 5.1 sboot (eng and normal). It hangs on second file. It checks somethings before start to load real bootloader. Maybe to fill whole device with zeros with dd command (deleting pit can be enough, but also maybe it ignores PIT and read some specific bytes on sda) and then restoring phone as it is just builded in factory. Of course first to make backup of EFS etc...
Even with downgraded sboot, i'm not sure can we use 6.0 and 7.0 roms?
Best way is someone with IDA knowledge to find bytes for unlocking and we can write them to sboot with dd if="something" of =/dev/sdb bs=xx count=xy
At least it is now repairable if it is bricked after that

Good find, thanks.
How did you break the bootloader (sboot) anyway?

Dd if=sboot_from_925f of=/dev/block/sdb
I had engineering boot (kernel) with adb root access. And after that phone is dead.
On 925a sboot is on sdb (just sdb without numbers), cm.bin on sdc. Probably same on all variants.

Hi
I'm not sure I understood the hex files creation step.
Start byte : 0
End byte : 0x1FFF
Size : 8192 for Novi1.bin for example
Right ?

Yes, that's it
Just compare with my files if unsure.

OK Thanks
Congrats for this amazing guide

G928c dont know version inside.
I tried 7.0 but tool hang after novi1 transfer.
with android 6 sboot all 4 files transfer succeed but no download mode
if I do 0x3E000 to the end of the file, tool hang after 1st file.
according to customer 7.0 was inside before brick.

ok I tried different 7.0 which take me to on display usb recovery mode.
but phone not detected by pc after reset by keys now phone completely dead.
no exynos mode, no download mode nothing.
PC not sensing phone anymore.

Did you restore exynos mode?
Try to add tzsw ( novi4 should be from 0x3E000 to the end of sboot.bin).

yes I open phone and re-insert battery. Now exynos mode.
(novi4 should be from 0x3E000 to the end of sboot.bin) give me USB Recovery Mode. but as previous post no detection.
do sboot contain tzsw ?
if so what is address for tzsw ?

tzsw is from 10F000 to the end of file. But you added it and phone loaded when you made novi4 from 0x3E000 to the end of sboot.bin.
I think it is still problem with different sboot version, it must be same as version previously in phone. Try few more sboot bin.
You don't have to pull out battery, just press volume down and power for more then 20 seconds, it is same like you reinsert battery.

I reconfirmed version form client and he said he is sure about 7.0 version.
this variant have only 3 files of 7.0 and I tried all sboot from 3 available versions.
zogu said:
You don't have to pull out battery, just press volume down and power for more then 20 seconds, it is same like you reinsert battery.
Click to expand...
Click to collapse
yes this is the way but in my condition not reset after 30sec and I feel phone heat too. thats why I decide to open phone.

Phone enter download mode and pc does not detect it, it is really strange, like it hangs after entering mode. Maybe is phone (flash memory) broken?
try with jig cable, maybe this can help, it is only idea i have...

zogu said:
Phone enter download mode and pc does not detect it, it is really strange, like it hangs after entering mode. Maybe is phone (flash memory) broken?
try with jig cable, maybe this can help, it is only idea i have...
Click to expand...
Click to collapse
I also think this can be memory issue.
tried all possible ways but no success.
device returned to customer.
anyways thanks for this guide and your quick response.
:good:

I dd over sdb, BOTA0 BOTA1 RECOVERY CACHE and SYSTEM, am i sol on this one? Phone doesnt get detected by pc. Even tried unplugging the battery. For those curious why...I found out theres a partiton flag set on all of those partitions. Its SYSMAGIC X , X being a number. Lowering that number on the system by dd' ing sda18 and rebooting, results in a fw error, binary 3 device 4. Aka phone thinks system installed is lower then what it really is. I know u cant downgrade the bootloader using your method, but if u dump sdb, and edit the sysmagic line in a hex editor, dd it back. It will now be corrupt, I wonder if you can now downgrade to the version we faked. Anyone care to give it a trytry?

how i open multidownloder it giving massage mfc110u.dll missing when i try to install it said opreating sysytem not supported i have window 7 32 bit sp1 but its not working

jhony352 said:
how i open multidownloder it giving massage mfc110u.dll missing when i try to install it said opreating sysytem not supported i have window 7 32 bit sp1 but its not working
Click to expand...
Click to collapse
It worked for me on win 7 32 bit...
Try to reinstall Visual C++ redistributable 2012
https://www.microsoft.com/en-us/download/details.aspx?id=30679

cfg file for s6 sm-g920p
thx its working
Please can you help me from where i can download cfg file for S6 sm-g920p i have sboot.bin file it is in bin format and this file is not open and work in mfc multidownloader

Nokia Lumia 520 Rm-915 QHSUSB_DLOAD stuck

Please Help me
My nokia lumia 520 is dead in QHSUSB_DLOAD?
Pc/ device manager/other devices show me ?QHSUSB_DLOAD
Help meeee

fix the QHSUSB_DLOAD brick
I had this the other day but I got it fixed that is if you can still access flash mode (red screen with giant nokia logo)
1. press VOL - and POWER for 10 seconds
2. go to the cellomania website just type in on google "cellomania ffu downloader", click on the first link witch has a pixelated C as its icon next to the website name put in your product code it should be 059XXXX
3. download all required files such as XXXX.pcx or XXXX.XXXX.XXXXX.ffu
4. download nokia care suite its easy to find just type it in on google and it should appear
5. once nokia care suite has installed go to C:\ProgramData\Nokia\Packages\Products\RM-915 and put all files in there
6. then open product support tool for store then click work offline because as it saved locally you don't need a wifi connection
7. then click open product
8. type in RM-915 my code is RM-935 so mine is a nokia Lumia 625
9. go into programming --> recovery
10. then click your firmware files that you saved into that folder
11. it will say that it lost connection press VOL - while you plug the usb in
12. it will say it is just flashing the VPL file but in actual fact its flashing all the files
12. and finally it will say recovery completed
13. and your phone should come up with the language selection after 5 or 10 minutes

my cell phone is dead
It does not turn on, is dead
I want to umbrick with the method without tjag but i have error
-- GPT ENDs --
Can help me fix the error?
Sending OPEN_MULTI_REQ
Received valid response to OPEN_MULTI_REQ
Checking eMMC read / write test results...
Failed to read number of eMMC sectors. eMMC is not working!!
ALPHA EMERGENCY FLASH END
Emergency messaging closed successfully
Operation took about 12.00 seconds.
Unknown error code.
THOR2 1.8.2.18 exited with error code 85035 (0x14C2B)

@ feherneoh thanks...
This problem is strange
Because my phone never dropped and used the method in two lumias 520 but show me the same Error
Was running the OS the build windows 10 mobile 10586 insider
The battery was discharged and never turned on

feherneoh:
When I connect the phone to the computer
I quickly see a green color icons connected
QHSUSB DLOAD toolkit conectivity emergency
I use windows 10 But i don't know if the are the corrects drivers to windows 10
I'm at work now
I do not remember very well but my phone is recognized immediately when connecting to the pc

feherneoh said:
In this case the reason for immediately going into emergency mode is probably that the bootrom of the SoC cannot read the eMMC. You cannot do anything without some professional tools and luck.
Click to expand...
Click to collapse
Thank you so much..
Fight for a week with this phone
And with your answer I will not fight any more
The strange thing is that I try with
2 lumias 520 and none returned to life
Please close this topic...

Ive bricked my nokia lumia 520 while trying to unlock the bootloader:
the way i did it was
Going into C:/Program Files/Microsoft Care Suite/Windows Phone Recovery Tool
and generating GPT0.bin (this file is very important)
You can generate your GPT0.bin file by inserting
Thor2 -mode ffureader C:/example directory/myfile.ffu -dump_gpt C:/example directory
and getting the right .hex file corresponding to the RKH (root key hash) you can get your RKH by booting into flash mode, opening windows phone internals,going to the info tab and finding the really long string of letters and numbers because thats your RKH
Then going into the MPRG_HEX.zip (you can find it with a quick google search)
Rename the correct hex file with your RKH to hex.hex
Then going back into command prompt and inserting
thor2 -mode emergency -hexfile C:/example/hex.hex -mbnfile C:/example/GPT0.bin -orig_gpt
Then it should take a few seconds
DO NOT REMOVE PHONE UNTIL TOLD TO!!!!!!
Then remove phone, take out the battery, insert battery and turn on the phone, you should hear a vibration and it should boot into nokia flash mode and you can go ahead and flash the ffu by:
Thor2 -mode uefiflash -ffu C:/example/flashy.ffu
Replace the example directory with your real directory
Wait 20 minutes and your phone should be fully operational
You just revived your lumia from death!

Bricked 950XL

Hi,
It seem my 950 is dead brick, when I plug it vibrate, then nothing. No light on sceen, no logo. At least windows seem to recognize an unknow device.
To get it back, I tried to follow the tutorial on lumiafirmware website.
Code:
thor2 -mode uefiflash -ffufile "C:\Users\sylva\Downloads\RM1116_1078.0053.10586.13169.12732.034E13_retail_prod_signed.ffu" -do_full_nvi_update -do_factory_reset
THOR2 1.8.2.18
Built for Windows @ 13:36:46 Jun 16 2015
Thor2 is running on Windows of version 6.2
thor2 -mode uefiflash -ffufile C:\Users\sylva\Downloads\RM1116_1078.0053.10586.13169.12732.034E13_retail_prod_signed.ffu -do_full_nvi_update -do_factory_reset
Process started Thu Oct 24 16:58:36 2019
Logging to file C:\Users\sylva\AppData\Local\Temp\thor2_win_20191024165836_ThreadId-16276.log
Debugging enabled for uefiflash
Initiating FFU flash operation
WinUSB in use.
Operation took about 1 minute, 0 seconds.
THOR2_ERROR_NO_DEVICE_WITHIN_TIMEOUT
THOR2 1.8.2.18 exited with error code 84003 (0x14823)
I tried this too: xdabloger.blogspot.com/2016/04/finally-unbrick-your-lumia-device_28.html
The app told me it was downloading the urgency files, then «Operation failure» message, I guess it doesn't manage to connect to the phone.
I had a look here too forum.xda-developers.com/windows-10-mobile/tutorial-how-to-rescue-lumia-emergency-t3434825 , but I didn't find the hex file I need…
Any magic solution ?

First you should have a look at your device manager: is there an USB Device as Nokia Emergency or Qualcomm USB or Comm Port? Assign to this device the Nokia Emergency driver which came with WDRT.
Download the Emergency files from LumiaFirmware, if not already done.
Modify this command line according to your needs:
thor2 -mode emergency -hexfile "MPRG8992_fh.ede" -edfile "RM1104_fh.edp" -ffufile "RM1104_1078.0053.10586.13169.13756.034EE9_retail_prod_signed.ffu"
For me, it worked as charm on my Lumia 950 XL.

Thanks for your answer, sadly in the device panel I only have an unknow one regarding the phone … :crying:

I suggest to change USB cable and USB port. I think as there is an unknown USB device it can't be recognized properly. Also you might append a screenshot of your device manager, especially the Details tab of the properties window. Normally. a Lumia 950 XL is "unkaputtbar", but I've also a device, which is not even recognized as an unknown device. You may also PM me, if you have a different preferred language... For me. FR, IT, HU also work... ES not really, I can read it.

I noticed that the post is on 2019 I thought it's new, sorry about that... any way the steps might be helpful for others.
I faced this problem exactly, I accidentally disconnect the cable while it was flashing and the mobile got dead as your situation.
The possible solution which saved me is this:
Create folder name it "Products"
Create folder name it "RM-1116"
Copy all your flash files into "RM-1116" if you don't have everything go to lumiafirmware.com and download all the files related to your device
Move the folder "Products" Into somewhere you can access it later
Now open Windows Devices Recovery Tool
In the dots at right-bottom click and choose "Settings"
Go to "Packages"
Active "Use Custom Package path"
Click "Browser" then choose the root folder that you copied "Products" folder into... (select the root folder not the "Products" folder)
i.e. Choose "D:\Custom Packages" -> "Custom Packages contains "Products"
Now Connect you mobile to the computer
wait a little after turn on
Choose "My Device was not detected"
Choose "Lumia"
Once you mobile connected probably you will see it listed
Click on it and recover the system
This should work hopefully.

Lumia 520 RM-914 Can`t flash LK Bootloader

Hi,
my rm-914 won`t flash LK Bootloader. Bootloader was unlocked succesfully with WP Internals but i got errors when i try to install lk using uefi2lk.cmd.
Any help???
This flasher is for x86_64 (64bit) Windows, Installer for Lumia 520 (fame)
If you don't have a full backup of your phone yet, stop right here and use Win32 Disk Imager
Press any key to continue . . .
Are you REALLY sure you backed it up?
Press any key to continue . . .
Okay, don't blame me if something goes wrong, it will be your fault...
Press any key to continue . . .
Make sure there are no other phones connected to the PC
Disconnect every Android and Windows based device
Turn your phone off
Remove and re-insert the battery
Connect it to the PC after pressing ENTER
Press any key to continue . . .
THOR2 1.8.2.18
Built for Windows @ 13:36:46 Jun 16 2015
Thor2 is running on Windows of version 6.2
C:\Program Files (x86)\Microsoft Care Suite\Windows Device Recovery Tool\thor2.exe -mode rnd -asciimsgreq NOKD -asciimsgresp NOKD -skip_com_scan
Process started Sun Apr 10 00:15:06 2022
Logging to file C:\Users\sasza\AppData\Local\Temp\thor2_win_20220410001506_ThreadId-7640.log
Initiating do RnD operations
WinUSB in use.
Debugging enabled for rnd
Starting to handle ASCII message
Sending ASCII message request : NOKD
THOR2_ERROR_TO_COMMUNICATE_WITH_UEFI_IN_DEVICE
THOR2 1.8.2.18 exited with error code 84103 (0x14887)
THOR2 1.8.2.18
Built for Windows @ 13:36:46 Jun 16 2015
Thor2 is running on Windows of version 6.2
C:\Program Files (x86)\Microsoft Care Suite\Windows Device Recovery Tool\thor2.exe -mode thor2 -mode uefiflash -partitionname UEFI -partitionimagefile DATA\EMMCBOOT.mbn
Process started Sun Apr 10 00:15:18 2022
Logging to file C:\Users\sasza\AppData\Local\Temp\thor2_win_20220410001518_ThreadId-12580.log
Debugging enabled for partitionimageflash
Initiating flash of partition image operations
WinUSB in use.
Using programming of partition image method
isDeviceInNcsdMode
isDeviceInNcsdMode is false
Detecting UEFI responder
Lumia UEFI Application did not respond to version info query
Device is not in Lumia UEFI mode
Device mode get failed, mode is 6
Unknown UEFI responder
Cannot flash partition image. Write the RDC into the device or use open/RnD HW & SW
Operation took about 3.00 seconds.
THOR2_ERROR_UEFI_RDC_OR_AUTHENTICATION_REQUIRED
THOR2 1.8.2.18 exited with error code 84214 (0x148F6)
THOR2 1.8.2.18
Built for Windows @ 13:36:46 Jun 16 2015
Thor2 is running on Windows of version 6.2
C:\Program Files (x86)\Microsoft Care Suite\Windows Device Recovery Tool\thor2.exe -mode rnd -reboot
Process started Sun Apr 10 00:15:21 2022
Logging to file C:\Users\sasza\AppData\Local\Temp\thor2_win_20220410001521_ThreadId-12832.log
Initiating do RnD operations
WinUSB in use.
Debugging enabled for rnd
Detecting UEFI responder
Send HELLO
Send HELLO
Send HELLO
Send HELLO
Send HELLO
Lumia UEFI Application did not respond to version info query
Device is not in Lumia UEFI mode
Reading device mode failed
Exited with success
< waiting for device >

Done. Lumia must be in fastboot mode to do this (tap power and volume down for 10 sec and release to run fastboot mode till phone vibrate).
But after LK flashing only Android Kernel Works, TWRP wont install with adb commands, no android partitions on internal memory, can`t create partitions from adb commands.
I can boot twrp but can`t wipe partition too. TWRP says that internal memory have 0 MB. What to do? Any suggestions? Recovery to WIndows Phone from WIn32Imager don`t work. Only MinOS and Data partitions are accesible.

Done.
I did restore WP8 from WIn32Image backup once again with success using those instruction:
Restore Windows Phone 8 if you have Android installed (Windows instructions)
Thanks to @feherneoh who posted the content of this thread originally here:Post #1 Post #2 NOTE: DO NOT ask for a backup. If you do not have one, you have to accept to be permanently on Android like me. Create a folder somewhere that we can...
forum.xda-developers.com
Something went wrong as in this manual - linux partitions are not set up!!! ->

Second try... ALL OK. Instructio is ok.

wlodar2wwa said:
Done. Lumia must be in fastboot mode to do this (tap power and volume down for 10 sec and release to run fastboot mode till phone vibrate).
But after LK flashing only Android Kernel Works, TWRP wont install with adb commands, no android partitions on internal memory, can`t create partitions from adb commands.
I can boot twrp but can`t wipe partition too. TWRP says that internal memory have 0 MB. What to do? Any suggestions? Recovery to WIndows Phone from WIn32Imager don`t work. Only MinOS and Data partitions are accesible.
Click to expand...
Click to collapse
Second time, no fastboot mode is needed.

Did you manage to fix the 0 mb issue?

TabbyBeni said:
Did you manage to fix the 0 mb issue?
Click to expand...
Click to collapse
the second time everything loaded correctly.