Hi, I decided to write here, I hope you can help me out.
So today I tried to root my phone with the instructions found at https://forum.xda-developers.com/showpost.php?p=68696079&postcount=114
I checked that my build no. is S288, so with rooting there would be no data loss for me (I still backed up everything important of course)
First problem I came across was that I had to found how to download QFIL, I downloaded and installed version 1.0.0.2 I think.
Second was that I couldn't get the Qualcomm Com port to show in QFIL neither in Device Manager. I figured out that as well, by doing loads of research (googling)
I also installed ADB to help me get into the state where I see the Qualcomm port, because normally if I just power it off, and connect it to my PC, it powers on in the "charging interface"
So everything was working, I downloaded the P1a42_S288_160721_ROW_RAW_QFIL file, extracted it, filled in everything in the QFIL program and hit Download while holding the + & - buttons to enter TWRP mode or whatever it is called. It returned with this:
Code:
PROGRAM: Send raw data fail
Failed to write I:\Telefon Ment�sek\Lenovo Vibe P1\Root (2017,03,11)\P1a42_S288_160721_ROW_RAW_QFIL\recovery_twrp.img to the device
Download Fail:System.Exception: Failed to upload the emmc images to the phone using Firehose
...
Download Fail: FireHose Fail FireHose Fail
Finish Download
Sorry, I can't write down everything bc I already closed the program, so I'm writing these off of screenshots
I already tried other USB cables, other USB ports, other drivers, even other ROMS, but everytime I try, I get this message:
Code:
Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol
at QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(String sFileName)
at QC.SwDownloadDLL.SwDownload.QPHONEMSSaharaDownloadArmPrg(UInt64& version, String armPrgPath)
Download Fail:Sahara FailSahara Fail
Finish Download
So currently I can't power on the device in any way, tried holding + and -, + and power, - and power, home and power, home power and +, home power and -, home power + -
Please help me, I would be really glad Cheers!
Also, sorry if my English is a bit poor, I'm a 15 year old boy who's native speaking lang is not English
P.S. I also don't know if I broke my warranty with this or not, because I technically have not rooted the phone, just did something else. And also, what if someone would've stolen it and I would've got it back and I wouldn't be able to turn it on because the thieves have broken it? (That is not the case right now, just asking).
PS 2: I have an alarm at 0:00 today, but I doubt that the phone is just gonna magically turn itself on for the alarm, we'll see. I may also try to leave the phone to completely discharge (I remember now why I didn't want to buy a phone with a built-in battery)
EDIT: I didn't mention, that the first time I tried to flash, I was using files from a Directory that's path contains both spaces and unknown (?) characters (é) (only unknown by the software) as seen above in the first box.
gabor6505 said:
Hi, I decided to write here, I hope you can help me out.
So today I tried to root my phone with the instructions found at https://forum.xda-developers.com/showpost.php?p=68696079&postcount=114
I checked that my build no. is S288, so with rooting there would be no data loss for me (I still backed up everything important of course)
First problem I came across was that I had to found how to download QFIL, I downloaded and installed version 1.0.0.2 I think.
Second was that I couldn't get the Qualcomm Com port to show in QFIL neither in Device Manager. I figured out that as well, by doing loads of research (googling)
I also installed ADB to help me get into the state where I see the Qualcomm port, because normally if I just power it off, and connect it to my PC, it powers on in the "charging interface"
So everything was working, I downloaded the P1a42_S288_160721_ROW_RAW_QFIL file, extracted it, filled in everything in the QFIL program and hit Download while holding the + & - buttons to enter TWRP mode or whatever it is called. It returned with this:
Code:
PROGRAM: Send raw data fail
Failed to write I:\Telefon Ment�sek\Lenovo Vibe P1\Root (2017,03,11)\P1a42_S288_160721_ROW_RAW_QFIL\recovery_twrp.img to the device
Download Fail:System.Exception: Failed to upload the emmc images to the phone using Firehose
...
Download Fail: FireHose Fail FireHose Fail
Finish Download
Sorry, I can't write down everything bc I already closed the program, so I'm writing these off of screenshots
I already tried other USB cables, other USB ports, other drivers, even other ROMS, but everytime I try, I get this message:
Code:
Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol
at QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(String sFileName)
at QC.SwDownloadDLL.SwDownload.QPHONEMSSaharaDownloadArmPrg(UInt64& version, String armPrgPath)
Download Fail:Sahara FailSahara Fail
Finish Download
So currently I can't power on the device in any way, tried holding + and -, + and power, - and power, home and power, home power and +, home power and -, home power + -
Please help me, I would be really glad Cheers!
Also, sorry if my English is a bit poor, I'm a 15 year old boy who's native speaking lang is not English
P.S. I also don't know if I broke my warranty with this or not, because I technically have not rooted the phone, just did something else. And also, what if someone would've stolen it and I would've got it back and I wouldn't be able to turn it on because the thieves have broken it? (That is not the case right now, just asking).
PS 2: I have an alarm at 0:00 today, but I doubt that the phone is just gonna magically turn itself on for the alarm, we'll see. I may also try to leave the phone to completely discharge (I remember now why I didn't want to buy a phone with a built-in battery)
EDIT: I didn't mention, that the first time I tried to flash, I was using files from a Directory that's path contains both spaces and unknown (?) characters (é) (only unknown by the software) as seen above in the first box.
Click to expand...
Click to collapse
Dear Pls follow this link
https://forum.xda-developers.com/vibe-p1/how-to/lenovo-vibe-p1-a42-c72-root-ready-t3533693
You can see the qualcomm driver only when you switch off phone and hold Volume+/- plus power button.
I can't bc my phone won't turn on currently,
So I probably shouldn't have used ADB to get into fastboot or whatever, my phone may be broken because I tried to do the flash while in that state.
Did you read my whole post though?
The next thing I'll try then is uninstalling all the drivers and programs related to my phone, and then following the guide you suggested, because I still see the Qualcomm port, I just can't do anything with my phone.
OMG, I have waited a few hours, and just randomly thought why not try again flashing the rom (I don't think this is the right word for the QFIL Download procedure), and it worked! So I'm actually really happy I don't need to send it in to repair or try other things. I got the system I started the procedure with, so I didn't actually lost any of my files neither did I root my phone. Now to decide if I want to try again rooting it with the detailed instructions you sent or just leave it like this so I avoid getting into all this again. I think I will try again to root it lol why not
Will report back here if it was successful
I have successfully rooted my phone, and installed the Xposed Framework on my phone, so I'm really happy.
I can't really seem to find where to lock this thread so please someone lock this thread (I am not familiar with this forum, so I don't know if it is needed or not)
Related
I did a rom upgrade on an hx2110 - installed successfully, but now the only thing I can get the pda to do is go into Pre bootloader mode (i.e. Pre-BL 1.00.02 blue screen). SO I tried the universal bootloader method - makes it all the way to the flashing portion but then does NOTHING - the terminal simply sits there saying "ready" and does not upload anything - the program sees the correct communication port (ie. usb01 or whatever). HOW do I force an upload???
Thanks!
Rusty
On another note - I had purchased a working 2110 with a good mobo to replace this one if the flash is not repairable - is that a difficult procedure? Unfortunately, the 2110 I purchased was not working, but this may still be in the books at a later time, so some info would help.
Thanks!
Rustmonkey said:
I did a rom upgrade on an hx2110 - installed successfully, but now the only thing I can get the pda to do is go into Pre bootloader mode (i.e. Pre-BL 1.00.02 blue screen). SO I tried the universal bootloader method - makes it all the way to the flashing portion but then does NOTHING - the terminal simply sits there saying "ready" and does not upload anything - the program sees the correct communication port (ie. usb01 or whatever). HOW do I force an upload???
Thanks!
Rusty
Click to expand...
Click to collapse
Rusty,
You are so lucky that I experienced this problem and solved it on my own. You did not specify what ROM you were loading, but here is the fix:
First you need to get another pocketpc, hx2000 series like yours that is working.
Put that device into white screen bootloader or pre-BL mode (depending on which device you got to borrow)
Ensure that the battery on that device is 100% charged.
Run the original ROM upgrade for the ROM you wish to install (use PDAViet if it's WM6 and use the HP SP32408 to Run it)
Hit all the Ok screens until it brings you to the one that has the "UPDATE" button.
Remove the working Ipaq from the cradle and place it's 100% battery in you own.
Put your Ipaq into pre-BL mode and put it on the cradle. Press the calendar button to activate the usb drivers.
Once it says "USB", Hit the "UPDATE" button and it will load the proper ROM to your IPaq.
When It is done, perform a hard reset by formatting the PS on the device.
Voila!! Your Ipaq is Un-Bricked!! Put in your original battery and charge it up!
Enjoy!!
Bless...
hi Rustmonkey,
i have the similar things - i made my hx2110 brick when i flashed it with a different language ROM, it went 100% when i flashed the ROM but didn't work at all after that.
the problem is i can get it in the bootloader mode after trying many ways, at the same time the pc can't find any USB device at all.
how to make it work again?
thanks.
reggaepoo said:
Rusty,
You are so lucky that I experienced this problem and solved it on my own. You did not specify what ROM you were loading, but here is the fix:
First you need to get another pocketpc, hx2000 series like yours that is working.
Put that device into white screen bootloader or pre-BL mode (depending on which device you got to borrow)
Ensure that the battery on that device is 100% charged.
Run the original ROM upgrade for the ROM you wish to install (use PDAViet if it's WM6 and use the HP SP32408 to Run it)
Hit all the Ok screens until it brings you to the one that has the "UPDATE" button.
Remove the working Ipaq from the cradle and place it's 100% battery in you own.
Put your Ipaq into pre-BL mode and put it on the cradle. Press the calendar button to activate the usb drivers.
Once it says "USB", Hit the "UPDATE" button and it will load the proper ROM to your IPaq.
When It is done, perform a hard reset by formatting the PS on the device.
Voila!! Your Ipaq is Un-Bricked!! Put in your original battery and charge it up!
Enjoy!!
Bless...
Click to expand...
Click to collapse
You, my good sir, are a genius - worked great! Fixed BOTH 2110s
tangwd898 said:
hi Rustmonkey,
i have the similar things - i made my hx2110 brick when i flashed it with a different language ROM, it went 100% when i flashed the ROM but didn't work at all after that.
the problem is i can get it in the bootloader mode after trying many ways, at the same time the pc can't find any USB device at all.
how to make it work again?
thanks.
Click to expand...
Click to collapse
You're going to need another hx2000 series to make sure the battery is fully charged - put the battery in and then use the bootloader keystrokes immediately (contacts+itask+reset) - you made need to tap reset a few times while holding the other two to get it to work. After it is in bootloader mode, push the calander button while it is connected to the cradle/usb to get the pc to recognize it
Rustmonkey said:
You're going to need another hx2000 series to make sure the battery is fully charged - put the battery in and then use the bootloader keystrokes immediately (contacts+itask+reset) - you made need to tap reset a few times while holding the other two to get it to work. After it is in bootloader mode, push the calander button while it is connected to the cradle/usb to get the pc to recognize it
Click to expand...
Click to collapse
really amazing !!!!!!
I just saved my hx2110 as per your step by step instruction now.
Thank you very much.
ok, well, I thought they were fixed... now one of them freezes at the bootup screen, even when I do a clean reset... I've tried reflashing multiple times to no avail... any ideas whats going on?
ok, got everything working - reflashed the non-working one back to an original 2003 rom - which made if freeze at boot - then upgraded it via pre-bl to 1.00.00.L - from here, it wouldn't do anything after filling the bar at the boot screen, but it didn't CRASH (as in lights out) - so I ran the pre-bl again and ran the flash program for 1.00.00.L again WITHOUT swapping between the 2495 and the 2110 - just put the 2110 in pre-bl and away we went - flashed, formatted, and booted - then proceed to upgrade to WM6 via 1.00.00.H --> 1.02.00.H --> WM6 - works GREAT!!!
Thanks for the help everyone!
Dear All,
I`ve got the same problem but i don`t have a second ipaq.. is there anyway to repair it with out the second device???
Thank you very much
Abs
Hello,
I have run into some problems with a bricked hx2110.
I was flashing the IPAQ to a new ROM WM5 (Battery was full and I read all the instructions 10 times prior to flashing). While flashing, the progress bar went to 100% then faded out immediately and it wouldn't reset (clean reset). I put the battery in my friends hx3000 series and the battery I used was completely dead. It did flash to 100% though, but not matter how many times I try 1 + 3 + reset, it doesn't reboot. If I can figure out how to get it to boot, that would be great, but I can't get anything to come up with any key combinations.
To this point all I can do is get into Pre-BL mode 1.00.04. I have tried the below scenarios on two machines, both running windows XP SP2 (USB 2.0) with the firewall and virus software disabled.
http://forum.xda-developers.com/showthread.php?t=330382&page=4
1) I have tried the above links directions and used the the Universal Bootloader (Bootloader.exe). It gets to the point where it says "The PDA should be updating now" or something similar but nothing happens. I don't get any errors regarding communications (it sees the device when I hold the "Calendar" button until it says USB; windows then recognizes the device as "HP USB ..." so I know it's communicating).
2) I tried to use the Bootloader_GUI.exe beta so that I can watch the progress indicator but it just sits at 0%. There are no error messages so it is communicating but for some reason, the device won't let it flash (and the flash utility thinks it's doing something).
3) I tried the original ROM flash from HP (SP29856.EXE) and it recognizes the device, but because the current ROM on the PDA is hosed, when it does it's "verifying" process, it comes up with "?" marks as the model number and when it goes to flash it starts at .1% then says "FINISHED" immediately. The ROM utility thinks it flashed it correctly but it didn't flash anything. I'm guessing that the verification of the PDA failed and forced the utility to not flash.
Does anyone have ANY ideas of what to try? I wish I had another HX2000 series PDA and try the "swap" thing prior to hitting the update button but I don't. All I have to work off of it my sad bricked PDA and a full battery (friend keeps charging it). His PDA is an HX3000 series.
Any ideas would be appreciated,
Thanks!
Are you using a the HP flash program that is specified for your device?
2nd - you might be able to use your buddies device in a swap as well - not sure but its worth a shot - use HPs upgrade program, let it verify, then swap your device onto the same cable - overwrite the firmware in the update program for HIS device with firmware compatible with yours and then hit update - let us know if this works...
I am using the "official" HP flash program specific for the HX2110 (from their website - SP29856), bootloader.exe, and bootloader_gui.exe
I wanted to try my friends, but he won't let me touch his because I bricked mine lol (I swore nothing would happen to his but he still won't let me try it).
Anyway, I just copied over the ROM image (from HP) and stripped out the header (now showing 64 bytes before the ECEC). The ROM is for WM2003. I copied the ROM in binary using psdwrite.exe to an 256 MB SD card. As soon as I can get the battery back, I'm going to try to flash it from the SD card. If this fails, I am going to try to play around with MTTY / USB and manually call the ROM flash and see what happens.
Having another HX2000 series would make this easy (maybe a little TO easy )!
Bootloader never worked for me - but if you can get it to manually call the flash, more power to you good luck!
Well it was worth a shot. After spending the better part of the day with the PDA, I have made no more progress (can't get Pre-Bl to update). The only option I have now is to find someone with another hx2000 series that is willing to resurrect it from the dead for me (PM me if you can help - I will pay two way fare). Until that happens, it's going in the "broken" drawer with all my old comp stuff .
Thanks to all the tips and tricks that is posted on these forums and brighthand! There is a wealth of information on this topic and without them, I would have gotten nowhere in trying to repair the device (granted, I wouldn't have been intrigued to upgrade the ROM in the first place and would still have a working PDA, but that's besides the point ).
Best of luck to you all.
1).download original ROM from HP (sp29799) -extract files
2) download http://upload.dvhk.pl/content.php?id=88892 - replace files
3) flesh device.
bay!
link crash http://upload.dvhk.pl/content.php?id=88892 - replace files
Please it can raise it again, thanks
Absolut3k said:
Dear All,
I`ve got the same problem but i don`t have a second ipaq.. is there anyway to repair it with out the second device???
Thank you very much
Abs
Click to expand...
Click to collapse
Same here.. is there another way to un-brick hx2110 on this problem ? thx ...
Solved, my hx2100 returns to be in this world
thank you i saved my ipaq
guys,my plus got trouble so many days help!
At first I update the kitkat,maybe its low electricity
after reboot it shows 'recovery mode'
but I dont konw what means
Then I start named the earliest fireware as
ko12_sd update and use the sd-card to save it.
As a result,my tablet often shows error and a fall android robot,always like this.
after a few repetitions,the next is bootloop.
Finally,(by some day)it only have
a white usb sign,in seconds charge red and in a constant cycleI have to seach the way.
but by time goes on ,my plus just show the red usb then turn on.unless contect pc it doesnt repeat.
I used to find some ways,but they all need the fastboot-doesnt have with my plus such as
video:'asus dead…solved'
short days before,I find a intel tool.
'xfstk downloader.exe' it likes very useful to fix my tablet ,but I didnt have the necessary files.
I also find a guy who has same problem
his article called 'a fluke…fe171cg'
lean from him,I try to do with myself.
seem that I have no luck like him.the xfstk appear many error .like
'Windriver Error: 0x20000015, Timeout expired'
'FW + OS download*did not complete'
Errors encounter during FW download. Aborting ...
XFSTK-STATUS--Error Code:*0*-Success
etc:crying:
only once it shows
success: FW download completed!os download skipped but my tablet doesnt reboot…
I try use it in another pc,but it is also the same.:silly:
I think a tablet running Intel processors is very special. unbricking it is a big challenge.
Anyone with the same experience?I want to know how flash it correctly.Or my method has wrongs?please give me some Inspired.thanks!!!
Hello Guys
My friend ask me for get a Lineage OS to his H815 with Nougat. I agreed as I made few successful changes from stock to Lineage OS with Samsungs and older LGs (like L3 E400). But G4 is really more complicated, more than I expected . Firstly I wanted to unlock this phone with FWUL, so I download a VirtualBox emulated image with FWUL and after it boots I opened SALT program and it detects the phone. I made a basic backup and then I choosed Unlock G4 (UsU). After that some windows pop up. Last window was a pre-checking, when the bar gets to the end window closed and nothing more was happening. So after almost hour of waiting I just turned off the phone - I thought its all. After that while phone is booting I have those messages in the left top corner:
[820]-----------------------
[870]
[920] Secure boot error!
[970] Error code : 1009
[1020[ OFFICIAL !!
[1070]
[1120]-----------------------
Its booting, but only sometimes its normal boot, most starts are with bootloop, sometimes its start after 10 restarts, sometimes after 2nd restart, sometimes after plug in/plug out USB cable it starts boot normally (connecting cable only to phone, not to PC), sometimes only thing that helps is to take out the battery. I made full wipe to be sure that its not a software problem, but only thing I achived with that is fact that phone has a Nougat and now it have a Marshmallow. It is (was?) H815, but now model name is LGLS991 (?), it gets very long until it shows software version (V20g), IMEI is unknow, even when I type *#06# I get the null response.
I can get into recovery, can put phone into download mode. But i'm not able to do anything to get LOS or a least Nougat.
I've read many, many tutorials how to get G4 working properly after unsuccessful unlock, but nothing helps. What I've tried:
1. Flashing stock Nougat for H815 with LGUP, installed USB drivers, proper DLL, set com to 41, but when I trying to flash, after a 4% i get error: KDZ file is invalid. Downloaded few KDZ firmwares, dont belive that every single one is invalid, there is something wrong with LGUP or with settings, but I cant find what
2. Flashing with LG Flash Tool 2014: tried both normal flash and cse flash and always stoping in the same moment, with "Connection to server failed. Try again in a moment". Read many tutorials about this error, none was helpful in my case.
3. Flashing with LG Flash Tool v1.8.1.1023 and a TOT file, but after select of dll and tot file and press the yellow arrow I get an error: "Failed PreviousLoad()"
Tried all this methods on second computer but without a luck.
What else can I try to get this G4 working properly? Maybe try to install some rom from stock recovery? But which rom will be ok and dont get things worst?
If you need more info dont hesitate to ask. Would be very greatful for any advices .
you definitely didn't read enough... go to read again the UsU thread and as you've read the whole tutorial, you can also read the whole FAQ and the OP, because 90% of what you pointed out in your publication (which incidentally is in the wrong section) is explained there.
A quick advice: Don't try to flash any KDZ/TOT again.
Hello everyone
i decided to write a new post because a bit lost on this one and need the help of a guru
First i've of course read and try to follow this complete guide but failing for me so i'll try to be the most concrete as i bet i'm near the solution
i bricked my moto G5 XT1676 stupidly trying to downgrade it (no error message ==> after boot screen is black and i have a flashing led when i connect)
since i downloaded the original rom and need to get back in fastboot mode
Using ADB tool my device is not seen but checking my com port it is still seen under a COM port (so still a bit of life)
as said i tried to burn to a sdcard the famous mmcblk0 using linux (or rufus under windows) it succeed , create a complete file system with around 48 partitions but inserting into my moto ==> no boot (tried to remove battery and add it again, tried VOL DOWN + POWER)
so i contacted a company called ARYKTECH and had 2 loader.img file dedicated in theory for my device , burn it on sdcard ==> no boot
i found on this forum a file called blankflash_CEDRIC and tried it ==> it failed each time with a sahara protocol error
then i tried QFIL tool with a programmer file comming from a file with a name called 8675_W00 ==> same, failed on sahara protocol error
I've read there is a tool called TOOLSTUDIO 4.6 that could help but a nice trojans is hidden in it
I also read SAHARA eerror come from the fact it would not be the good programmer file
As you understand i'm turning around and need just someone to highlight me a bit
neness2000 said:
Hello everyone
i decided to write a new post because a bit lost on this one and need the help of a guru
First i've of course read and try to follow this complete guide but failing for me so i'll try to be the most concrete as i bet i'm near the solution
i bricked my moto G5 XT1676 stupidly trying to downgrade it (no error message ==> after boot screen is black and i have a flashing led when i connect)
since i downloaded the original rom and need to get back in fastboot mode
Using ADB tool my device is not seen but checking my com port it is still seen under a COM port (so still a bit of life)
as said i tried to burn to a sdcard the famous mmcblk0 using linux (or rufus under windows) it succeed , create a complete file system with around 48 partitions but inserting into my moto ==> no boot (tried to remove battery and add it again, tried VOL DOWN + POWER)
so i contacted a company called ARYKTECH and had 2 loader.img file dedicated in theory for my device , burn it on sdcard ==> no boot
i found on this forum a file called blankflash_CEDRIC and tried it ==> it failed each time with a sahara protocol error
then i tried QFIL tool with a programmer file comming from a file with a name called 8675_W00 ==> same, failed on sahara protocol error
I've read there is a tool called TOOLSTUDIO 4.6 that could help but a nice trojans is hidden in it
I also read SAHARA eerror come from the fact it would not be the good programmer file
As you understand i'm turning around and need just someone to highlight me a bit
Click to expand...
Click to collapse
Same issue here, mainboard fault for sure. Hope you will find another one it in Amazon, eBay. etc. No other solution at this point.
Hi guys,
I've finally managed to get Windows 10 back to my Lumia 530.. from "bare metal" (really, it looked death at some try-and-fail steps
It will be done in two steps.
First, we need to push it to the 10586.107
The second update we will deploy the "final" version of v1511 - 10586.1176 (the fixed issues betwenn 107 and 1176 are a list of 8pages paper )
WHAT YOU NEED:
- Windows Device Recovery Tool (can ressurect dead phones, when nothing else can connect to it.... )
- The included thor2.exe cmdline tool (find it in the install path of the Recovery Tool).
- The Stock Windows 8.1 (can be downloaded by the tool or by yourself at lumiafirmware com
- IUTOOL.exe (included in the Windows Driver Kit (WDK) or from here, the big Windows 10 Mobile Offline Thread) as well as the perfect prepared first packages:
- the "win10_mobile_offline_updater_v41.wim" provided on this page. YOU need only the files in THIS SUBFOLDER: "3rd Generation\43X-532"
- If you want to prepare further updates or a different phone, you'll need also (comes with IUTOOL.exe) GetDuLogs.exe (I HIGHLY RECOMMEND to run it with your fresh updated device connected to USB), It will rip the update log wich are nice but it also includes a package list, that were updated on your Phone. THIS IS IMPORTANT because these package names are the packages you will need for every device upgrade rollup..
HOW TO:
1st: I believe i took the GUI Recovery tool the first time i succeeded but at my second try it didn't work.. The whole success depends on a few megabytes of free space. So whatever caused this, MY LAST and sucessful try worked after i flashed the Stock FFU with the command line tool thor2.exe using the whole bunch of options:
thor2 -mode uefiflash -ffufile "your_Phones_Stock_Build_imageFile.ffu" -do_full_nvi_update -do_factory_reset -reboot
After the reboot, and you will only succeed by following: Leave the phone at the first Screen (The Welcome, languange selection), connect to USB, let windows install the driver and once connected (when using Windows 10) Remove the device from Devices And Printers otherwise IUTOOL.exe will put out an error and won't work.
now start the update by launching: iutool -V -p e:\folderName (Where All The CABs Are Inside).. You won't get any message on your phone, but IF it fails, IUTOOL will put out an Error - in all my tries within 5 minutes.. YOU NEED TO WAIT for reboot. The Lumia 530 will take around 30minutes until it reboots itself. It boots in the known maintenance mode, takes some time and will come up with Windows 10.0.586.107. Because we didn't went through the OOBE before, either only the Start Screen will be empty or in addition the App list will not show every app - as expected - Easy Fix: If you have the settings app, go to SYSTEM-INFO and launch a factory reset.. If not take the hardware forced way: Hold Volume down AND the power button until it vibrates, release ONLY the button, hold volume down a bit longer to get the phone recognized what you want. When it shows the "!" launch the factory reset by pushing in this row: Vol Up - Vol Down - Power - Volume down..
the keyboard wont work so if you want your backup to be forced while OOBE, you need to make your Wifi Open without password... There is a fix for this issue on the Main Thread for the Offline Update, but i just removed my (in my case) German Keyboard and the englich keyboard worked fine immediately after removing..
The Swiss keyboard was also good for me - but i didn't care a lot - will be fixed with the final Update...
THE OOBE WAY doesn't work any more, seems like Microsoft wasn't amused by this and closed this nice door i just found as my very last idea with this phone. The genius idea.. i felt so cool after that really worked.... Now the last step: don't forget to call "getdulogs -o e:\outputfile.cab" in the cab are the logs as well as the important package list..
The second update is easier, because there is not much you can do... You can find it with normal Update search but - trust me - in the best case it fails with 50 MB too less space... really hard So the difficult part this time is to identify and get your packages. I've searched my 6 disks and finally i'found my phone updates but unfortunately i must have overwritten my get.cmd for 1176 which was a download batch for the files.. ****.. but it's also hard to identify the correct package at Microsoft, i'm tired but here's the little gift, definetely the correct package, you'll find here (i cannot post links, too new ) catalog-update-microsoft-com and seach for "14003.1176". The 2500 MB folder is yours, look for " Windows Mobile 10 Production Bundle - OS 10.0.14003.1176 update for all mobile phone devices", Click "Download to see all package links and download the ones in the log files package list...
I got 168 files, should be more - even if more are not a problem - we don't have any space for maybe resolution packages for other devices. NO
If you have some scripting or programming knowlegde, there are some hints for it below.. Or Contact me if you need help.
Update is easy:
- Factory Reset AND DON'T CONNECT your phone to the Wifi - at no point
- After OOBE - Uninstall absolutely every thing that is able to, delete temp files - these little two things worked fine for me, key point here is NO CONNECTION TO NOWHERE BEFORE.. again, we are fighting for 50 MB, so if it was connected -> do the factory reset before... but do it also if it never was on, because there are few files from the previous update, that will lock us these 50 MB...
Update itself like before, IUTOOL.exe -V -p u:\cabFolder
WHAT YOU NEED TO KNOW... If you like ****, this time you can watch the update progress - IUTOOL.exe forces the normal windows update so it will show progress..
reboot to maintenance mode - will all work fine BUT THE FIRST REBOOT - keep cool, and enjoy the blue flashing Disco Screen you will get - you can try to reboot, but it didn't help on all my 2 deployments. what it needs (was a surprise for me, and it helped twice) is a simple factory reset.. like i wrote in the previous update. This time you will have to use the hardware way i mentioned.. Thats all.. One little issue, i couldn't fix yet, but i don't care.. MSN News App, And the Weather App are only links to the store and for whatever reason the store thinks it is already installed, Take Foreca Weather... Everything else works fine.. Keyboard as well with native german on my side
Hopefully i mentioned it detailed enough... worked TWO times for me now.. 14393 update needs too much space, don't even think about it
I'm currently slowly reading into Deploying and developing customized windows mobile images, not that i wan't to run it on my 530 but maybe i'll find somehing...
Greetings, Stephan.. Below some hints for the downloads, if you want to script it...
THE SECOND UPDATE is based on the package list i've ripped. With this and the version number (this is tricky, because the internal Build will not stay at 10586, so you will find the update by searching for "Windows Mobile 1176" or sth near.. look for a Folder size of ~2500 and the update rollup .1176 - i'm not really sure - it was some near 14003.1176 (The Build number MUST BE LOWER than 14393. You'll either some creative knowledge like programming or a lot of patience and motivation to find all your 127 packages and download it manually.. i copied the the whole filename's list and the prefix to have a download link and then i wrote a little C# to compare my needed package List with the whole build list from microsoft.. i added also a "wget -c ". It's even more complicated... 2 different "base" links (i just took both links - only the correct one will work. And finally - the last complication is - there are downloads "tagged" with a "cbs" as well as with "cbsu" in the filename FOR MOST PACKAGES, i've not tried to find what it means - but however i decided to take the CBS because their filesize was realisic, cbsu are way too small, may be these are one fixes from last update, and not the whole rollup - what we need....
..the keyboard wont work so if you want your backup to be forced while OOBE, you need to make your Wifi Open without password...
Click to expand...
Click to collapse
Forget that... you cannot apply your backup at this time, even with internet connected... The hard point would be to login with Microsoft
can you post screenshots?
I followed that whole guide but I didn't succeed. It was then that I deleted the .cab files from languages that I'm not going to use and I remade the whole process, being transferred 31 files. I crossed my fingers and received the full storage message but the update followed and to my surprise the phone restarted and updated.
Someone to helpme with efiesp.bin partition?
Hello,
im trying to understand ur method but im not that into microsoft stuffs so, what do u mean with:
" now start the update by launching: iutool -V -p e:\folderName (Where All The CABs Are Inside) ? "
I get it done with more than 1Gb of free storage !
so I start with your steps u provided above and I got lost honestly.
-I have lumia 530 Dual SIM (1019) previous build was 8.1 I don't recall OS version but it was the latest, so yeah I searched for more information and I found this thread https://forum.xda-developers.com/windows-10-mobile/guide-win10-mobile-offline-update-t3527340/ of this glorious man @hikari_calyx
-I tired to intall W10 even the method says that not supported for 4gb devices, and it was really a fail because following his steps ended up with fail to update due to low storage, then I tried to delete anything I could, but again it fails for just 140mb or so... an idea pops up in my head which updating after a hard reset so the OEM apps won't get installed, and
here are the steps
1- go to the link provided for @hikari_calyx and follow the steps (make sure to download the .cab files) until it fails to update.
2- perform a hard reset to your phone (power off, press vol - and power button together after the vibrate release ur finger from power button and keep pressing vol - then in order : vol - vol + power button vol - )
and don't pass the language selection screen just keep it there.
3- Now go and update it like you just did before hard reset, it will take a lot of time just plug it to a power source and keep it cold, maybe more than 1 hour.
4-hurry it boot up you might face a problem in "Almost done.." screen, so the solution is : lock the screen and turn it on again, once u slide the lock screen up and before the app reloads keep pressing the "win" button it will open "one handed mode" then bring down the notification center and press anything (maybe win button I don't recall) until it goes to home screen (not 100% sure what I have done it was so random lol)
Congratulations u have W10 with a lot of storage.
STALKER18 said:
I get it done with more than 1Gb of free storage !
so I start with your steps u provided above and I got lost honestly.
-I have lumia 530 Dual SIM (1019) previous build was 8.1 I don't recall OS version but it was the latest, so yeah I searched for more information and I found this thread https://forum.xda-developers.com/windows-10-mobile/guide-win10-mobile-offline-update-t3527340/ of this glorious man @hikari_calyx
-I tired to intall W10 even the method says that not supported for 4gb devices, and it was really a fail because following his steps ended up with fail to update due to low storage, then I tried to delete anything I could, but again it fails for just 140mb or so... an idea pops up in my head which updating after a hard reset so the OEM apps won't get installed, and
here are the steps
1- go to the link provided for @hikari_calyx and follow the steps (make sure to download the .cab files) until it fails to update.
2- perform a hard reset to your phone (power off, press vol - and power button together after the vibrate release ur finger from power button and keep pressing vol - then in order : vol - vol + power button vol - )
and don't pass the language selection screen just keep it there.
3- Now go and update it like you just did before hard reset, it will take a lot of time just plug it to a power source and keep it cold, maybe more than 1 hour.
4-hurry it boot up you might face a problem in "Almost done.." screen, so the solution is : lock the screen and turn it on again, once u slide the lock screen up and before the app reloads keep pressing the "win" button it will open "one handed mode" then bring down the notification center and press anything (maybe win button I don't recall) until it goes to home screen (not 100% sure what I have done it was so random lol)
Congratulations u have W10 with a lot of storage.
Click to expand...
Click to collapse
@STALKER18 did you manage to get 1703 or 1709 on the Lumia 530?
Someone can help me with efiesp.bin file dumped with WPInternals?