I originally had Windows 8 on my laptop. Now I triple booted windows 7 and XP on it but the bootloader was replaced by windows 7 one. Now My question is how do I get back the metro style bootloader of Windows 8?
karan128 said:
I originally had Windows 8 on my laptop. Now I triple booted windows 7 and XP on it but the bootloader was replaced by windows 7 one. Now My question is how do I get back the metro style bootloader of Windows 8?
Click to expand...
Click to collapse
as a general rule of thumb always start from the oldest OS, XP>7>8 that way the bootloaders don't get all messed up
Pop a Win 8 Disk in and boot to it
Hit SHIFT+F10 to enter the command prompt
Type - bootrec /fixmbr to update the main boot record just in case its messed up (shouldn't be!)
Then type - bootrec /fixboot to update the boot sector on the system partition.
Finally type - bootrec /scanos to add your OSs
that should sort it out, cant remember if that scans for XP, if it doesn't that's fixable too but you should really consider hyper-v and run XP in a VM, if you absolutely have to that is.
dazza9075 said:
as a general rule of thumb always start from the oldest OS, XP>7>8 that way the bootloaders don't get all messed up
Pop a Win 8 Disk in and boot to it
Hit SHIFT+F10 to enter the command prompt
Type - bootrec /fixmbr to update the main boot record just in case its messed up (shouldn't be!)
Then type - bootrec /fixboot to update the boot sector on the system partition.
Finally type - bootrec /scanos to add your OSs
that should sort it out, cant remember if that scans for XP, if it doesn't that's fixable too but you should really consider hyper-v and run XP in a VM, if you absolutely have to that is.
Click to expand...
Click to collapse
Thanks, but it didn't work...
dazza9075 said:
as a general rule of thumb always start from the oldest OS, XP>7>8 that way the bootloaders don't get all messed up
Pop a Win 8 Disk in and boot to it
Hit SHIFT+F10 to enter the command prompt
Type - bootrec /fixmbr to update the main boot record just in case its messed up (shouldn't be!)
Then type - bootrec /fixboot to update the boot sector on the system partition.
Finally type - bootrec /scanos to add your OSs
that should sort it out, cant remember if that scans for XP, if it doesn't that's fixable too but you should really consider hyper-v and run XP in a VM, if you absolutely have to that is.
Click to expand...
Click to collapse
Worked for me.
Sent from my One V using xda app-developers app
try these steps, remember you need to have windows 8 or some other OS that's compatible with the Windows 8 bootloader (like server 2012) set as the first boot OS because at the point that the windows 8 loader shows the menu options the system kernel and drivers are already loaded.
http://www.intowindows.com/restore-boot-options-menu-in-windows-8/
the command:
"bcdedit /set {current} bootmenupolicy standard"
and variations of it did the job for me when I was working with a multiboot of server 2012 and win7 + other OS's.
nbates66 said:
try these steps, remember you need to have windows 8 or some other OS that's compatible with the Windows 8 bootloader (like server 2012) set as the first boot OS because at the point that the windows 8 loader shows the menu options the system kernel and drivers are already loaded.
http://www.intowindows.com/restore-boot-options-menu-in-windows-8/
the command:
"bcdedit /set {current} bootmenupolicy standard"
and variations of it did the job for me when I was working with a multiboot of server 2012 and win7 + other OS's.
Click to expand...
Click to collapse
Thank You. The second method for power users on that link you provided worked for me.
Hello all lumia owners ,with the release of windows phone internals there is a great rush to unlock bootloader and install custom rim.
In previous post I have posted about unlocking bootloader and enabling root access but what if you have bricked your lumia?
In That case Please read this thread and fix your lumia.
Lumia can be bricked by bad updating phone or disconnection in update or something else it might also be bricked by flashing custom Rom.
REQUIREMENTS
1.Windows Device Recovery Tool (WDRT)- Get it here
2.FFU image for your phone.(Larger than 1gb)(If you have custom rom then skip ffu image and jump to method 2) - check here
3.Drivers (Installed with WDRT)
Instruction
Method 1
1.Install WDRT and run it.
2.Dont Connect your phone, just click on I can''t find my device button.
3.Let it to Search for a Device.
4.Connect your device via USB cable.
4.Start Up your lumia by pressing power button.
5.If it is not starting,Struck on logo,or just a boot loop it can be read by WDRT.
6.WDRT will show device with unknown manufacturer, o's version etc.
7.Dont Flash software with it Just close it.
8.Go to http://www.lumiafirmware.com/info and read all instruction and follow it to manual flash flu file.
9.Wait Until all is done and reply if this fixed your lumia.
Method 2 (Easy)
If you didn bricked your device in flashing or unlocking bootloader then Its better to jump out method 1 as it is more easy for you.
Or if you have custom rom for your phone and not want to download full original ffu then stay here.
1. Install Windows device recovery tool.
2. Go to :
For 32bit window.
C:\Program Files (x86)\Microsoft Care Suite\Windows Device Recovery Tool
For 64bit window.
C:\Program Files\Microsoft Care Suite\Windows Device Recovery Tool
Or whatever install folder you selected.
3. Hold shift and right click on your mouse and click open command windows here.
4. Paste thor2 -mode uefiflash -ffufile " " in cmd and click enter.(This will start searching your phone)
4. Press And Hold Poweroff + Lower Volume Button (Dont release it if your phone turn on automatically)(Especially in Bootloop).
5. Connect your phone to PC ( of course using USB cable).
6. if it detect Your device it will take you to Flash Screen (Ignore errors as it appear becuase in ffu location we take " " and its completely normal.)
7. Run Windowsphone internals and now it will detect your phone in flash mode.
8. Now you can Flash Custom rom (if bootloader unlocked) or just flash stock ffu image (dont need unlocked bootloader.)
Done
I will try to find more and more method to fix brick lumia until then this method is best or just send device to service center if this didn't fixed.
Greetings;
the *.ffu file won't be found at: http://www.lumiafirmware.com/info (for most devices).
That's some misleading website info; copied to several tutorials.
Reference: "Tutorial: Unbrick Lumia Devices"
Considering your System drive is " C: "
Open: C:\Program Data\Microsoft\Packages\Products\RM-<Number>
* Where <Number> will be your device release model number.
Note: You can check Code & Release Model Number on the back of your phone by removing your battery.
Inside that folder you can see that you have some required files to recover your device from Bricked states.
i.e: the *.ffu file.
Hi,
My phone crashed during the bootloader unlock process. I think My hex codes were not in sync with the ffu.
Now my PC does not detect the phone enither does it vibrates or shows any activity on the screen.
When I tried the above methods, I get the following error message.
C:\Program Files (x86)\Microsoft Care Suite\Windows Device Recovery Tool>thor2 -mode uefiflash -ffufile " "
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
Process started Sat Jun 17 05:30:45 2017
Logging to file C:\Users\siddh\AppData\Local\Temp\thor2_win_20170617053045_ThreadId-10580.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)
Is there any way I can create a temporary bus between the phone and that thor utility to send a bootloader handshake?
Hi,
My phone crashed during the bootloader unlock process. I think My hex codes were not in sync with the ffu.
Now my PC does not detect the phone enither does it vibrates or shows any activity on the screen.
When I tried the above methods, I get the following error message.
C:\Program Files (x86)\Microsoft Care Suite\Windows Device Recovery Tool>thor2 -mode uefiflash -ffufile " "
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
Process started Sat Jun 17 05:30:45 2017
Logging to file C:\Users\siddh\AppData\Local\Temp\thor2_win_201706 17053045_ThreadId-10580.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)
what i do now? is that any way to recreat my lumia phone?
swapnilnaikwadi said:
Hi,
My phone crashed during the bootloader unlock process. I think My hex codes were not in sync with the ffu.
Now my PC does not detect the phone enither does it vibrates or shows any activity on the screen.
When I tried the above methods, I get the following error message.
C:\Program Files (x86)\Microsoft Care Suite\Windows Device Recovery Tool>thor2 -mode uefiflash -ffufile " "
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
Process started Sat Jun 17 05:30:45 2017
Logging to file C:\Users\siddh\AppData\Local\Temp\thor2_win_201706 17053045_ThreadId-10580.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)
what i do now? is that any way to recreat my lumia phone?
Click to expand...
Click to collapse
Same problem? did you find a solution?
YOU ARE THE MAN.
my 930 was bricked by wpinternals misuse and this simple guide fixed it!!
my nokia was completely dead, and you sir, saved my 930 with this recommended guide!!
rgxHost said:
Greetings;
the *.ffu file won't be found at: http://www.lumiafirmware.com/info (for most devices).
That's some misleading website info; copied to several tutorials.
Reference: "Tutorial: Unbrick Lumia Devices"
Considering your System drive is " C: "
Open: C:\Program Data\Microsoft\Packages\Products\RM-<Number>
* Where <Number> will be your device release model number.
Note: You can check Code & Release Model Number on the back of your phone by removing your battery.
Inside that folder you can see that you have some required files to recover your device from Bricked states.
i.e: the *.ffu file.
Click to expand...
Click to collapse
if it is possible to recover data from a damaged lumia, I do not want to lose data
Greetings; using Nokia firmware tool will reset your device to factory settings (on mine, reverts back to windows 8).
Best regards;
Hi all, i have a bricked lumia 1320 with samsung emmc. When i power it on, it says: unable to find boot options
This problem started when i downgraded from windows 10 mobile to lumia denim using WDRT. The flashing procedure went well and, at reboot, the error message appeared on screen.
i've tried with thor2, windows phone internals, WDRT to unbrick the device but i failed. Do you have other suggestions? I read that exists a way to restore the device using jtag or atf box but i don't want to buy a 100$ peripheral for a one-time procedure
I made a program that unbricks your device, recovers from QHSUSB_DLOAD, QHUSB_DLOAD.
It's called...
Windows Phone Unbrick Tool (WPUT)
It comes with an installer.
NOTE:
1. You should enter the license key that is provided in the License Agreement section (for checking that you are not a bot, so don't use autoinstaller!
2. You must download your emergency HEX and MBN files from lumiafirmware.com
3. You must specify the correct path to the HEX/MBN files otherwise the program will fail!
4. If the unbricking succeeds remove your battery from your device for 1 minute and put it back on
5. Charge the device for at least 30 minutes before turning it on!
6. Reflash your device with Windows Device Recovery Tool.
Download it here
b i t . l y / 2 O Y Q Z V R
(REMOVE THE SPACES)
gmirz2005 said:
I made a program that unbricks your device, recovers from QHSUSB_DLOAD, QHUSB_DLOAD.
It's called...
Windows Phone Unbrick Tool (WPUT)
It comes with an installer.
NOTE:
1. You should enter the license key that is provided in the License Agreement section (for checking that you are not a bot, so don't use autoinstaller!
2. You must download your emergency HEX and MBN files from lumiafirmware.com
3. You must specify the correct path to the HEX/MBN files otherwise the program will fail!
4. If the unbricking succeeds remove your battery from your device for 1 minute and put it back on
5. Charge the device for at least 30 minutes before turning it on!
6. Reflash your device with Windows Device Recovery Tool.
Download it here
b i t . l y / 2 O Y Q Z V R
Click to expand...
Click to collapse
Hi!
My lumia 635 has no .mbn and .hex extension files at lumiafirmwaredotcom, but .edp and .ede files.
I tried both but not working, runs 20seconds and "err connection not found"
My lumia when connected at usb is recognized as unkown device, dont know what do anymore
nhtmd2 said:
Hi!
My lumia 635 has no .mbn and .hex extension files at lumiafirmwaredotcom, but .edp and .ede files.
I tried both but not working, runs 20seconds and "err connection not found"
My lumia when connected at usb is recognized as unkown device, dont know what do anymore
Click to expand...
Click to collapse
OK, so what you need to do now is, to remove the battery of your phone and connect it to the computer.
As I am seeing the log of the program, it says that the device is not detected.
So try removing your battery, connect it to your computer, wait until the computer successfully installs the QH-USB Dloader driver.
Firstly, try repairing your phone by doing the following steps:
1. start CMD as administrator
2.type cd C:\Program Files (x86)\Microsoft Care Suite\Windows Device Recovery Tool
or if your pc is 32 bit OS, then type C:\Program Files\Microsoft Care Suite\Windows Device Recovery Tool
3.now type the following thor2 -mode emergency -protocol sahara -hexfile edefile.ede -edfile edpfile.edp
4. do it for 5 times
5. disconnect the device
6. insert the battery
7. connect it to wall charger
8. wait 10 minutes, for it to charge
9. connect the device to PC
10. if the device shows the red flash screen, then you are good to go
11. if not, then remove the device from computer, disconnect the battery, reconnect the device to computer, launch WDRT
12. click My Device Is Not Detected
13. click LUMIA
14. if your device has been detected, it will be shown in WDRT (if not then retry the steps from 1 to 7 for several times)
15. click your device
16. wait until the device recovers from Emergency State
17. wait until your device reflashes
18. enjoy!
NOTE: All data is already lost and cannot be recovered as Windows Phones use secure erase, and no data recovery tool will be able to get the files back
SO FINGERS CROSSED TO ONEDRIVE BACKUP YOUR PHOTOS/VIDEOS and ELSE!
gmirz2005 said:
OK, so what you need to do now is, to remove the battery of your phone and connect it to the computer.
As I am seeing the log of the program, it says that the device is not detected.
So try removing your battery, connect it to your computer, wait until the computer successfully installs the QH-USB Dloader driver.
Firstly, try repairing your phone by doing the following steps:
1. start CMD as administrator
2.type cd C:\Program Files (x86)\Microsoft Care Suite\Windows Device Recovery Tool
or if your pc is 32 bit OS, then type C:\Program Files\Microsoft Care Suite\Windows Device Recovery Tool
3.now type the following thor2 -mode emergency -protocol sahara -hexfile edefile.ede -edfile edpfile.edp
4. do it for 5 times
5. disconnect the device
6. insert the battery
7. connect it to wall charger
8. wait 10 minutes, for it to charge
9. connect the device to PC
10. if the device shows the red flash screen, then you are good to go
11. if not, then remove the device from computer, disconnect the battery, reconnect the device to computer, launch WDRT
12. click My Device Is Not Detected
13. click LUMIA
14. if your device has been detected, it will be shown in WDRT (if not then retry the steps from 1 to 7 for several times)
15. click your device
16. wait until the device recovers from Emergency State
17. wait until your device reflashes
18. enjoy!
NOTE: All data is already lost and cannot be recovered as Windows Phones use secure erase, and no data recovery tool will be able to get the files back
SO FINGERS CROSSED TO ONEDRIVE BACKUP YOUR PHOTOS/VIDEOS and ELSE!
Click to expand...
Click to collapse
Oh man ty very much for your answer, im gonna try it out tomorrow night and come back here to give u feedback!
Sorry for the double quote here and in the other post.
Fingers crossed, thanks!
nhtmd2 said:
Oh man ty very much for your answer, im gonna try it out tomorrow night and come back here to give u feedback!
Sorry for the double quote here and in the other post.
Fingers crossed, thanks!
Click to expand...
Click to collapse
got it!
Waiting!...
Hope it works
I have a Nokia Lumia 1020 completely unresponsive buttons and screen, except for the Windows LED logo that lights up briefly when I plug it in. It is running wp8.1 and it doesn't have a removable battery
Any help would be greatly appreciated. I honestly don't mind if it needs to be completely wiped. I mostly just use it for the camera.
ChrisWilke said:
Any help would be greatly appreciated. I honestly don't mind if it needs to be completely wiped. I mostly just use it for the camera.
Click to expand...
Click to collapse
Try leaving your phone charging for 1 day.
After that connect it to WDRT (Windows Device Recovery Tool)
And start reflashing the software.
NOTE: If the WDRT doesn't detect it, try holdin POWER and VOLUME DOWN buttons for 15 secs, it will trigger a power-cycle.
https://forum.xda-developers.com/windows-phone-8/development/unbrick-dead-boot-lumia-jtag-t3872885
Does anybody know how to use this thor2 command?
Device authentication:
thor2 -mode rnd -do_authentication -sdauthenticationtype production -skip_com_scan -skip_gpt_check [-server saisec001.europe.nokia.com] [-securesessionfile mysession.sessionid]"
Click to expand...
Click to collapse
gmirz2005 said:
I made a program that unbricks your device, recovers from QHSUSB_DLOAD, QHUSB_DLOAD.
It's called...
Windows Phone Unbrick Tool (WPUT)
It comes with an installer.
NOTE:
1. You should enter the license key that is provided in the License Agreement section (for checking that you are not a bot, so don't use autoinstaller!
2. You must download your emergency HEX and MBN files from lumiafirmware.com
3. You must specify the correct path to the HEX/MBN files otherwise the program will fail!
4. If the unbricking succeeds remove your battery from your device for 1 minute and put it back on
5. Charge the device for at least 30 minutes before turning it on!
6. Reflash your device with Windows Device Recovery Tool.
Download it here
b i t . l y / 2 O Y Q Z V R
(REMOVE THE SPACES)
Click to expand...
Click to collapse
Thanks for your gr8 efforts - However How to find Hex and MBN files - how to identify and from where to download - can make life easy - please help i have - i have Lumia 532 - Product 059w980 - RM-1031
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!
Hello forumers,
I finally succeed in installing TWRP :victory: and I spent many time to search my mistake to conclude it was a simple path error when I write it
But I could't go on the next steps (root final) because of sdcard's problem.
After installing TWRP img and launching root batch my phone don't appear on device on win 7 (but I heards It connects).I reinstall Moto driver 2.5.4 but nothing.On one of XDA' s thread I tested a version for 32bits win (my Linux is 64 but win want only 32 ).It doesn't work too.
So I change for Linux (Manjaro).My phone is connect and it appears in my files manager (thunar).
Code:
mtp://motorola_Moto_G__4__ZY223HS8TX/
After many research on the web I notice that it's very hard to copy a file in a sdcard on Linux with mtp and I don't understand currently how it works.Debug mode is activated on the phone.I verify I have all mtp packages installed to work normally.And my sdcard was formated as mobile storage not internal phone storage (I use ROM phone for install applications).But mtp want I initialize it.
Code:
[cracotte ~]# mtp-detect
libmtp version: 1.1.16
Listing raw device(s)
Device 0 (VID=22b8 and PID=2e76) is a Motorola Moto G (ID1).
Found 1 device(s):
Motorola: Moto G (ID1) (22b8:2e76) @ bus 3, dev 6
Attempting to connect device(s)
error returned by libusb_claim_interface() = -6LIBMTP PANIC: Unable to initialize device
Unable to open raw device 0
Do you have infos and advises to configure it please?
An another solution is to use ftp mode beetween Linux and phone but I can't install ES Explorer on the phone because I can't activated Wifi more just after loading TWRP
I'm not at the end of my difficulties :crying:
One simple question: as I had to start phone normally to access sdcard after loading TWRP would I have problems to install supersu after this or must i had begin root process completely by the first?If it is the case my phone is new and I will use it after I succeed it so it wasn't a problem to do it again.
Sorry for my english too
Use adb push
Code:
adb push <whatever-name>.zip /sdcard[CODE]
P.S: I wouldn't recommend SuperSu. Use magisk instead
Hello I would like to do it but I can't access to my sdcard.It's my problem.When I types fdisk -l on a terminal no sdcard (sdb or sdc should display not?)
Code:
[cracotte ~]# fdisk -l
Disque /dev/sda*: 465,8 GiB, 500107862016*octets, 976773168*secteurs
Unités*: secteur de 1 × 512 = 512*octets
Taille de secteur (logique / physique)*: 512*octets / 512*octets
taille d'E/S (minimale / optimale)*: 512*octets / 512*octets
Type d'étiquette de disque*: dos
Identifiant de disque*: 0x3a7bbd0b
Périphérique Amorçage Début Fin Secteurs Taille Id Type
/dev/sda1 * 2048 206847 204800 100M 7 HPFS/NTFS/exFAT
/dev/sda2 206848 133122047 132915200 63,4G 7 HPFS/NTFS/exFAT
/dev/sda3 133122048 362366975 229244928 109,3G 83 Linux
sda2 is win7 and sda3 is manjaro
But it doesn't work
Code:
[cracotte ~]# adb push Magisk-v17.1.zip /sdcard
* daemon not running; starting now at tcp:5037
* daemon started successfully
adb: error: failed to get feature set: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
Maybe a pb of permission about /dev?
I precise I have configurated my /usr/lib/udev/rules.d/51-android.rules to indicate ID VENDOR and ID PRODUCT.
And root and biscotte are both in adbusers group.My sdcard seems not recognize by Linux.I'm going to look for.
Magisk seems to be a better solution thanks for info.
Hello after spending many days to search what the problem was I finally progressed.I have installed a Win10 rather than my seven because I thought my version was too old.But not.By curiosity I connect my phone in recovery mode (under TWRP so) and my phone appears.:victory:
I could copy magisk.zip on sdcard and install it by TWRP.As I still hadn't wifi to install Magisk Manager I downloaded it under my pc and create a flashable zip to install by TWRP.It seems it didn't work well because I can't verify if root access was unlocked (screen displays only installed but nothing about root fonctions).
Therefore I wanted modify build.prop to restore wifi access but TWRP didn't want to install ES Explorer or Mixplorer.And I don't find the file about system so that I suppose rooting was unsuccessfull.
And adb don't always recognize my device (unauthorised) and all xda's forums solutions didn't work more.
Finally I restore my stock ROM with your tuto and It works.While I 'm searching on the web I notice I hadn't "Revoke USB DEBUGGING Authorization" as many other users.But after restore my ROM this option was activate :victory::victory::victory:
Even if I don't understand why it is the case I 'm enjoy to progress one steps by steps.Maybe adb will soon connect my device .And I 'm going to begin procedure again
Thanks to people who helped me!!!!!
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.