I don't understand how to use it :\
I've been browsing the forums and reading posts all day long, but I can't seem to get this.
I am sure my lumia has an unlocked bootloader since windows asks me to format it when I test it.
Here are some info about my thing if it helps.
location of the rom I am trying to flash: C:\Users\David\Desktop\os-new.nb
location of dd.exe: C:\Users\David\Desktop\os-new.nb
drive letter of the phone : E:
When ever I command dd to do "dd if=./os-new.nb of=/dev/sdE9", replaced "x" with the drive letter of the phone which is E.
It doesn't seem to do anything, or it doesn't do anything at all...
Can someone do a detailed tut for this; in windows? I'm not a noob by any sort but this is just frustrating with such limited instructions.
looks like no one is kind enough to clarify. Ok.
Sent from my Lumia 710 using Board Express
You cannot use dd on windows; it's an internal Linux command that doesn't exist in Windows.
Hmm, why did it say we can use the windows version of dd?
Sent from my Lumia 710 using Board Express
If so then is it possible to flash the .nb with Qualcomm qpst? I don't have enough diskspace to install linux
Sent from my Lumia 710 using Board Express
wndows version of dd may no use, and i don't konw why
dd is used to copy the nb file to disk?
maybe another software to do like this, such as winhex?
dewe said:
wndows version of dd may no use, and i don't konw why
dd is used to copy the nb file to disk?
maybe another software to do like this, such as winhex?
Click to expand...
Click to collapse
I'm trying it again with DD in linux this time. Took a hard drive out of a broken ps3 and installing ubuntu on that
If you don't want to install Linux on a separate hard drive or partition, Cygwin is your friend. Be sure not to accidentally dd erase your Windows hard drive though...
Refrain from use of Windows to unlock bootloader, most likely to brick your device, use Linux, if you don't have it, don't try it. You have been warned.
sHaHiN786 said:
Refrain from use of Windows to unlock bootloader, most likely to brick your device, use Linux, if you don't have it, don't try it. You have been warned.
Click to expand...
Click to collapse
Hmm, can you give me a step by step instruction to do this?
I went from the Nokia DLOAD to Qualcomm loader already. Thats how far I am. I've also played around with the DD commands with my uncles mac.
dd if=./os-new.nb of=/dev/sdX9
if the phone shows up as /dev/sdb3 on ubuntu, do I do
dd if=<path to the .nb>/os-new.nb of=/dev/sdb3?
wardoc22 said:
dd if=./os-new.nb of=/dev/sdX9
if the phone shows up as /dev/sdb3 on ubuntu, do I do
dd if=<path to the .nb>/os-new.nb of=/dev/sdb3?
Click to expand...
Click to collapse
dd if=./os-new.nb of=/dev/sdX9
Where X is the disk detected by your linux distribution.
After that, you'll need to hard reset the phone. Hold Power button for 10 seconds to exit Qualcomm's disk mode, and press and hold POWER+VOLUMEDOWN+CAMERA until you feel the phone vibrate. After that, RELEASE power button but KEEP HOLDING volume down + camera for five or more seconds. This will trigger the hard reset.
sHaHiN786 said:
dd if=./os-new.nb of=/dev/sdX9
Where X is the disk detected by your linux distribution.
After that, you'll need to hard reset the phone. Hold Power button for 10 seconds to exit Qualcomm's disk mode, and press and hold POWER+VOLUMEDOWN+CAMERA until you feel the phone vibrate. After that, RELEASE power button but KEEP HOLDING volume down + camera for five or more seconds. This will trigger the hard reset.
Click to expand...
Click to collapse
dd if=/home/david/os-new.nb of=/dev/sdb9
I already did dd if=/home/david/os-new.nb of=/dev/sdb3
Well, I screwed up =\
Now it gets recognized in windows as qualcomm device, but it won't show up in ubuntu.
I made a full backup of it though.. You got any ideas?
Anyways in the end, I phoned tmobile up, they said they will send me a new one. I will be retrying this when I get that new lumia
sHaHiN786 said:
Refrain from use of Windows to unlock bootloader, most likely to brick your device, use Linux, if you don't have it, don't try it. You have been warned.
Click to expand...
Click to collapse
^ I tried it the other day, and it bricked. LOOOL. I recommend listening to this guy. I ended up having to get a replacement device, luckily came the next day. attempted again except used Wubi for ubuntu, and it worked fine. i got the interop unlocked tango for the lumia 710
sHaHiN786 said:
dd if=./os-new.nb of=/dev/sdX9
Where X is the disk detected by your linux distribution.
After that, you'll need to hard reset the phone. Hold Power button for 10 seconds to exit Qualcomm's disk mode, and press and hold POWER+VOLUMEDOWN+CAMERA until you feel the phone vibrate. After that, RELEASE power button but KEEP HOLDING volume down + camera for five or more seconds. This will trigger the hard reset.
Click to expand...
Click to collapse
Lumia 710 does not support SW by pressing POWER button!
wardoc22 said:
dd if=/home/david/os-new.nb of=/dev/sdb9
I already did dd if=/home/david/os-new.nb of=/dev/sdb3
Well, I screwed up =\
Now it gets recognized in windows as qualcomm device, but it won't show up in ubuntu.
I made a full backup of it though.. You got any ideas?
Anyways in the end, I phoned tmobile up, they said they will send me a new one. I will be retrying this when I get that new lumia
Click to expand...
Click to collapse
Yeah, I guess you're pretty much screwed now. I don't get why people without a understanding of the DD command use it. Either way this procedure is still far away from being stable. You could try to reflash the third Partition if you have a backup somewhere. But if you don't you can only get a replacment device.
ChrisKringel said:
Yeah, I guess you're pretty much screwed now. I don't get why people without a understanding of the DD command use it. Either way this procedure is still far away from being stable. You could try to reflash the third Partition if you have a backup somewhere. But if you don't you can only get a replacment device.
Click to expand...
Click to collapse
Well I do have an understanding of what the command is and what every part of it means now... We learn from experience lol. I never had a huge experience with linux haha.
I will try to explain this as best as I can, to make sure I am correct, and to try to clarify the command for other people confused.
dd if=./os-new.nb of=/dev/sdX9
"if=./os-new.nb"
This specifies the file path of where your os-new.nb file is. So for example, the location of my .nb file is:
"/home/david/os-new.nb" so I would do "if=/home/david/os-new.nb"
of=/dev/sdX9
This specify the location of where you are copying the .nb file to.
For this, you would just have to replace the "X", and only the X, which is in terms of the letter your device turns up in linux as. This was the part I got confused on. It showed up as sdb3 on my machine, which I thought that I would have to replace the entire sdx9 with it.
To find out the letter, in terminal, type in
"df"
It will lists all your active drives. Mine shows up as the latter B, under the name windows device. So I would do
"of=/dev/sdb9"
So to put it all together, the command I would type in is:
"dd if=/home/david/os-new.nb of=/dev/sdb9"
Am I correct?
And also, if there a way to flash your lumia from within windows? Cause it still shows up as a USB drive in windows like usual but it refuses to show up in ubuntu.
And also, I gave up trying to make it show up on ubuntu and tried it on my uncle's mac.
Heres what I got.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I flashed the wrong partition, which was partition 3. So I am wondering if anyone can make an IMG file for partition 3 for me(lumia 710, unlocked qualcomm bootloader) then might be able recover it.
Worth a shot I guess as I will be getting a new lumia anyways.. And I might not have to be stuck with no phone for 10 days lol.
Related
Method outdated and risky.
Improved method: http://forum.xda-developers.com/show...5#post17148825
Hi Everybody, Im Jcmaster and im Kind of new in this forum, i have been following this forum for some time ind i think its time to give something to this comunity, i have been searched for a while and found nothing like this, i'dont know if this is ilegal (i dont think so) or if it is in the wrong section but i will continue any ways.
Ok this is to all the people who had they phones bricked while doing this, First of all, i succesfully Bricked my phone and bring it back to life by doing the following.
I was reading all the messages from people who bricked their phones by doing this tutorial and i did not understand how they did it so i tried to brick my phone to see how to fix it, but the only way i could do this was by skiping the last step, umount /efs, when i did not make this and restarted my phone, the phone get bricked, it onli lighted up the screen and do nothing.
Once i managed to brick my phone i just downloaded the KPN gingerbread rom, and the brazilian rom, y followed this tutorial to unbrick my phone: This is The Tutorial
I Installed the KPN with the OPS and the Modem files of the brazilian rom, once i got the rom running my phone was kinda messy, some random error messages and many more, so i did a wipe of the chache and dalvik and restarted the phone an it was ok, and the i installed the Fla.sh rom via odin and thats the rom im runing now and i dont have any problem, well thats how i bricked/unbricked my phone on purpose, and dont forget the last step, umount/efs. i hope it works for somebody because i worked with me.
Firts Things First, I'm not responsible for a, Brick or semibrick that may come with this tutorial i have succesfully unlocked 15 Phones and by the thime they dont have any problem, so i suggest to read the entire post as many times is needed to understand the entire procedure & clarify all the doubts that you may have.
If you have a cuestion, please ask it, its better to wait some time until you have an answer that brick your phone, and also your cuestions are usefull for other people.
Once this is understood lets proceed.
Ok ill start with the Requirements.
You Will Need:
Your Samsung Galaxy Ace (obviously)
The original Usb Cable that comes with the phone.
Your Computer (I will use Windows XP for the demonstration, because i dont know how to do it with other O.S)
Your Phone has to be Rooted
Samsung Kies Installed Wich can be found HERE
ADB wich comes with Android SDK and can be found HERE
Ok Once you have all that stuff we can continue.
I will not teach how to Root your device because custom roms are already rooted and if you have a stock rom there are plenty tutorialn on hou to root it, and also i will not teach you how to install Kies because its realle easy and anyone can do it, i will only teach you how to install Andoid SDK and the specific ADB Package OK lets start.
Once you have downloaded the Android SDK Run the Installer trough all the steps to install it, I recomend to Install it in "C:" disk so it makes easier to make al the further steps, if it ask for the Java SDK just download and install, restart the Android SDK Installer and continue, Once its Fully Installed open it and do this next steps:
1-Go to the "Available Packages" Option on your left Menu
2-Click on the "Refresh" Button ond the bottom Right and wait until it finish
3-From Items select the "Andoid SDK platform-tools, revision 6" Item
4-Click the "Install Selected" button on the botton right and wait until it finish
5-Now you can either close the SDK or leave it open.
Image:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now that you installed the SDK and the ADB its time to set the Path so the cmd.exe recognizes the ADB, there are two methods, One With cmd.exe (console) and one with the My PC Properties, i will explain bot of them.
Cmd.exe (console) Method.
Click on your start button and select "Run" from the Start Menu, type cmd.exe on the box and press enter.
Once the CMD its open write the next Text: set PATH=%PATH%;C:\android\android-sdk-windows\platform-tools
The text Write in Bold means your SDK Installation Directory, thats why i told you to Installa the sdk In C: Disk, just check that your Installation Directory is the same as mine or modify the line according to your needs.
My PC Properties Method.
Open My PC, and Right click on a blank space,
Select "Properties" from the just opened contextual menu,
On My PC Properties select the "Advanced Options" Tab
On the "Advanced Options" tab click on the "Environment Variables" button.
Now Mark the "Path" Variable and click the "Edit" Button.
At the end of the line add this text:
;C:\android\android-sdk-windows\platform-tools
Remember that The text Write in Bold means your SDK Installation Directory, thats why i told you to Install the SDK In C: Disk, just check that your Installation Directory is the same as mine or modify the line according to your needs.
Ok now you have completly installed the android SDK and the ADB (Android Debugging Bridge) and you can now do the final steps to Unlock or Get the Unlock Code for Your Samsung Galaxy Ace.
Ok now that you have Installed all the necessary programs:
Connect your SGA to your Computer via the included USB Cable. (the drivers should be installed by now, Kies installs them automaticaly)
Click on you start button and open the "Run" option, on Run type cmd.exe and press enter.
Now on Cmd.exe type the next text to acces the ADB Shell:
cd C:\android\android-sdk-windows\platform-tools
Remember that this means your Android SDK Installation directory, so if you get an error, check that the route is well writed and if you installed it in a diferent directory just modify the line so it fits to your needs, just remeber to pur - instead of spaces and \ (not / ) to indicate folders.
Image:
Now that you are in "C:\android\android-sdk-windows\platform-tools" type: adb shell
Image:
Now That you are in adb shell type the next command: su
At this point you have to give root premission to adb shell on you Phone
Image:
Ok now that adb shell has root premission and its inside you phone, type the next line:
cd /
Now be carefull and notice that there are spaces in the line and that we are using / instead of \
Image:
Ok now that you typed cd / type the next line: mount -o remount rw /
Image:
Ok Now type: mkdir /efs
Image:
And now type: mount -o nosuid,ro,nodev -t vfat /dev/block/stl5 /efs
Image:
And now type: cat /efs/mits/perso.txt
And you will get some strange characters on the screen and a 8 digit number, thats your unlock code, copy it in paper or in a Notepad file, but check it twice so you get the correct number, also the number provided is unique so dont try to use your number with other phones or use my number with yours.
Image:
Ok Now that you Have your Code just type: umount /efs
And disconnect your phone from your computer, turn off your Phone and insert a SIM from another company, it will ask for the Unlock Code, just type the code that you just get and you are done, your phone is now unlocked and without brick risk.
Image:
Now you can check that your cellphone is unlocked by typing the next code on your numeric keyboard, like if you where doing a call: *#7465625#
Image:
And thats it, its really easy, and its really safe if you read everything, and clear your doubts.
All the images are mine and i learned this from a friend of my, but its tested in 15 Samsung Galaxy Ace Phones an none get hurt XD,
Well thats it, remember to comment and ask as many times you need, im glad to answer all of your questions, se you later
great tutorial. very detailed and easy to understand.lucky for me my phone is already unlocked out of the box
Sent from my GT-S5830 using XDA Premium App
Thank you Im gonna try it
This works with every android? or every samsung android?
Or its just ACE?
once again GREAT TUTORIAL
Gh0s7_Hun73r said:
Thank you Im gonna try it
This works with every android? or every samsung android?
Or its just ACE?
once again GREAT TUTORIAL
Click to expand...
Click to collapse
I havent tried, but maybe it can work i just tried with galaxy ace because one friend of my bought several of them to sell and i unlocked them all, well its just matter of trying
Just tried on mine. Works perfect!!!!!!!! Thank youuuuu
Sent from my GT-S5830 using XDA App
Thanks for ur contribution......... Luckily we dont have network lock in our country
Now thanks to you, I dont have it either
hehehehehe .... This may encourage other to buy ACE..... More Aces Strong community
ThanKS! i got the code.
I was denied access trying to go to into SU because I made a mistake in Cmd.exe (console) Method.
I then tried My PC Properties and it worked.
umount /efs did not do anything so i just used exit.
Deserves to be in development thread.
Did you follow the steps with the SIM installed and registered, or without SIM?
Even i use preunlocked ace, i have to admit that this tutorial is well writen. Straighforward and easy to understand. Good one will click that thanks button once i get on my pc later
Sent from your phone
I did it with my SIM on the phone lol. Then when i got the code, i switched the sim for another provider and after i put the pin it asked for the code. Put it and "phone not restricted" message apear
Sent from my GT-S5830 using XDA App
Very nice and easy to understand tutorial...thanks
rjtd said:
Did you follow the steps with the SIM installed and registered, or without SIM?
Click to expand...
Click to collapse
The first time i tried this i had the original telcel sim on the phone, then when i finished i restarted the phone with other company (movistar) sim, and for the tutorial my phone was already unlocked and the original telcel sim on
Sent from my GT-S5830 using XDA App
wow, just tryed it 5 min ago, and it WORKED
Thank you so muhc, you save me some euros
terminal
could i do this from terminal on my phone instead of thru ADB?
wow! it really worked
hats off to you my friend
dg1598 said:
could i do this from terminal on my phone instead of thru ADB?
Click to expand...
Click to collapse
I havent tried but you can give it a try, butt i dont thin it will work.
I have done the proces but after I type SU I receive a message permision dennied, I have updated my phone with the new Telcel Ginger version and rooted with the acegingeroot file, wht can I do??
thanks
Hello,
New to this forum as is shows it is my first post, and i have a problem with my Blackphone that i hope you guys could help me with it.
I have a Blackphone first generation with PrivatOS with some files on it and locked screen ( forgot the password / pin actually ),i didnt use the phone for a while since i had some problem downloading and purchasing some apps considering the lack of options compatible with the phone when it was first released and prior to opening the Silent Store.
I've tried several methods i found online such as :
Disable your lock screen using custom recovery and “Pattern Password Disable” (SD card needed)
but no success i get the error ( invalid arg ) when i try to flash the zip file on the SD card.
also i wanted to try this method : http://forum.xda-developers.com/showthread.php?t=2244741
but i am using a Macbook Pro OSX El Capitan 10.11.2
So i ma not sure how to go from here ?
Issue with file manager
Saw i've been trying several method to tackle this problem since i didnt get any reply from the 56 views so far, but i hope someone could explain how to get over this issue i am having trying to apply Method 4 or Method 5 at this post http://forum.xda-developers.com/showthread.php?t=2620456
I was able to download and install all the required applications, from Android SDK and JDK also adb not to forget Android file manager. But i have a problem with the file manager, since i forgot the pin and i am trying to recover some files from the phone it is frustrating to not be able to apply any of these methods because the file manager wont connect the device while it is locked.
Every time i try to type in the command ad devices in Terminal or adb shell i get a return error of device not found, and i guess its because the file manager is not allowing me to do that since the phone is locked.
Any idea how to get over this problem ?
The whole point of that phone is to prevent just what you are trying to do.
Indeed
zelendel said:
The whole point of that phone is to prevent just what you are trying to do.
Click to expand...
Click to collapse
Yes indeed i understand which is the dilemma am in, but that is the point of all phonee pin locks and there are methods to bypass them for most of the phones as i could see all over the internet, this one should not be any different i guess.
I even tried to use the password pattern disable file, but i guess when i flash the file from an SD card i guess some kind of error in the header, am assuming the header in the code of the file should be modified to the OS of this particular phone .
From what i could see the only issue here is the different OS on this phone.
Any suggestions ?
janusjanus said:
Yes indeed i understand which is the dilemma am in, but that is the point of all phonee pin locks and there are methods to bypass them for most of the phones as i could see all over the internet, this one should not be any different i guess.
I even tried to use the password pattern disable file, but i guess when i flash the file from an SD card i guess some kind of error in the header, am assuming the header in the code of the file should be modified to the OS of this particular phone .
From what i could see the only issue here is the different OS on this phone.
Any suggestions ?
Click to expand...
Click to collapse
You would be amazed. This one and the black berry device. Both are meant to be uncrackable by default. I know one secure phone even prevents anything but charging over usb
zelendel said:
You would be amazed. This one and the black berry device. Both are meant to be uncrackable by default. I know one secure phone even prevents anything but charging over usb
Click to expand...
Click to collapse
I am so far, i really assumed that it is possible to so without the factory reset, but i guess that is the only option.
I still have couple of options that i could think of and maybe try,
1- Modify the Pattern Password Disable .zip in order for it to be compatible with Privat OS, easy to say hard to do, since i have no idea how to start tampering with these files and rewrite the coeds in it.
2- Trying to update the firmware on the phone with an SD card which will bypass the pinlock i guess, as i read in one of the posts on the blackphone support website, as a solution for faulty upgrade through the phone.
BTW i didnt try it, but i could see alot of posts for Blackberry to bypass this sort of problem, non for Black phone specifically
I appreciate your sweft reply and attention, hope you could come up with better ideas !?
Another attempt
zelendel said:
You would be amazed. This one and the black berry device. Both are meant to be uncrackable by default. I know one secure phone even prevents anything but charging over usb
Click to expand...
Click to collapse
So, i had to try using the pattern_password_disable.zip in order to see if it is good, and applying the same instruction here i was not able to unlock my Samsung Trend lite 2.
First i downloaded the file into an sdcard, the zip file and tried to flash the .zip from the recovery mood, but the phone did not find anyfiles on the SDcard, so i tried to apply updates from ADB, and when i wrote the comand as instructed on the phone
PHP:
" ad sideload +filename+ "
i got an error
E: footer is wrong
E: signature verification failed
then the phone tried to open it again and i got the same erorr
after that the phone rebooted into the home screen with the pattern lock, i've tried several random guesses but it didnt unlock. ( i know the right one for this phone ).
And since i realized that my mac got connected to the devices while it was in the recovery mood, and i confirmed that by typing adb devices in terminal and the device showed up, i thought of trying the same with the BlackPhone
but i also got the same error
as shown in the picture.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I wanted to apply the same commands mentioned in the post i've mentioned
PHP:
adb devices
adb shell
cd data/system
rm *.key
but when i type adb shell
i get the error, closed
so any idea on what is going on, i just want to understand my mistake here since these instructions should work on the Samsung !?
Screen shot of Blackphone
http://postimg.org/image/m0tsja4qn/
janusjanus said:
So, i had to try using the pattern_password_disable.zip in order to see if it is good, and applying the same instruction here i was not able to unlock my Samsung Trend lite 2.
First i downloaded the file into an sdcard, the zip file and tried to flash the .zip from the recovery mood, but the phone did not find anyfiles on the SDcard, so i tried to apply updates from ADB, and when i wrote the comand as instructed on the phone
PHP:
" ad sideload +filename+ "
i got an error
E: footer is wrong
E: signature verification failed
then the phone tried to open it again and i got the same erorr
after that the phone rebooted into the home screen with the pattern lock, i've tried several random guesses but it didnt unlock. ( i know the right one for this phone ).
And since i realized that my mac got connected to the devices while it was in the recovery mood, and i confirmed that by typing adb devices in terminal and the device showed up, i thought of trying the same with the BlackPhone
but i also got the same error
as shown in the picture.
I wanted to apply the same commands mentioned in the post i've mentioned
PHP:
adb devices
adb shell
cd data/system
rm *.key
but when i type adb shell
i get the error, closed
so any idea on what is going on, i just want to understand my mistake here since these instructions should work on the Samsung !?
Click to expand...
Click to collapse
Any suggestions
janusjanus said:
http://postimg.org/image/m0tsja4qn/
Click to expand...
Click to collapse
Still awaiting any suggestions ?
Team Win Recovery Project v3.0.0.0 for D605
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
HOW TO INSTALL:
Flash from old recovery:
Reboot to your current recovery.
And flash the archive.
Flash recovery.img without custom recovery:
Extract contents on your PC
Copy loki_flash and recovery.img to you phone's SD card via MTP connection
Download and start Android Terminal Emulator from Play Store
From terminal emulator type: $ su
Then type (assuming files from zip were copied to external SD card root) :
# cp /storage/external_SD/loki_flash /storage/external_SD/recovery.img /data/local/tmp
# cd /data/local/tmp
# chmod 777 loki_flash
# ./loki_flash recovery recovery.img
# reboot recovery
DOWNLOAD:
Link to flash from recovery:
https://mega.nz/#!fo8DCDbb!wvN9GTN7xzuTGnNMBfu4UwmAo7culclt88qb-qJoZLI
Link to flash without recovery:
https://mega.nz/#!y1dk0KwS!HAwU-Pi6jgfQPe3c1yID9WmX76X_afdNpTpToPbfqSA
STATUS:
Stable (but I have not tested)
Nice work, thx (will you end cm12?)
I Have problem: Loki aboot version does not match device. (LG D605 kitkat 4.4.2) Root:yes
Downgrade to jb
@JackPOtaTo try with another version of windows, i had the same on win7, no problem in win8
Sent with my CM11 Lg D605
Ag0n1a said:
@JackPOtaTo try with another version of windows, i had the same on win7, no problem in win8
Sent with my CM11 Lg D605
Click to expand...
Click to collapse
I have win 10. And i bricked (Hard) LG l9 II
As far as I know this device is not possible to hardbrick.
Again, if your problem is "Loki aboot version does not match device" then your device is not bricked probably
Ag0n1a said:
As far as I know this device is not possible to hardbrick.
Again, if your problem is "Loki aboot version does not match device" then your device is not bricked probably
Click to expand...
Click to collapse
I don't know where you guys get your information from but stop saying phones are not possible to hard brick and spread this word around. It is very easy to hardbrick any phone with root.
I will go just in a little bit of detail to show you.
How does your computer boot?
The hardware you have (CPU, GPU, Memory etc) are searched for (physical addresses) by the motherboard by the BIOS. Delete or erase the BIOS and I bet you any sum that your computer will stop doing anything (starts and sits idle just fans spinning).
With this analogy the BIOS of any mobile device is the bootloader. In the bootloader, that is located on the eMMC (embedded Multi Media Controller; like an SSD but with the controller of memory in the silicon die). eMMC is partitioned like a hard disk.
Your phone has an integrated Primary Loader in the CPU (this is what Qcom 9008 is). By shorting pins you change the boot order. If you short correct pins you can send data into memory (RAM) from the CPU and then write it on the eMMC (if you have the correct communication). This is where the HEX programmer comes in. This is how Qualcomm tools know how to communicate with the SOC.
The 2nd loader is on the eMMC. By default all CPU's boot from eMMC. SBL1->aboot and so on is the bootchain. Where hardware is initialized and recognized. Destroy and of those partitions and you will have a hardbrick (either fallback to 9008 automatically because eMMC is empty or not recognized at all).
Well I ended up giving you kind of a full information. Just stop trowing around this thing "phones can't be hardbricked". Hardbrick describes the state where a phone can't enter the last emergency mode provided by the manufacture (Emergency in this case). And generally buttons don't work, screen isn't either and so on.
Never said that phones cannot be hardbricked....
I said that installing this rom will not hardbrick your phone, cuz only contain kernel and syspartition... plus, if the software prevents u from make changes because the aboot version doesn't match, how can u hardbrick it?
Thanks for the explanation though, learned couple of spec terms...
Ag0n1a said:
Never said that phones cannot be hardbricked....
I said that installing this rom will not hardbrick your phone, cuz only contain kernel and syspartition... plus, if the software prevents u from make changes because the aboot version doesn't match, how can u hardbrick it?
Thanks for the explanation though, learned couple of spec terms...
Click to expand...
Click to collapse
If you flash an aboot version that does fail the check of the bootchain you have a hardbrick.
A
neutrondev said:
If you flash an aboot version that does fail the check of the bootchain you have a hardbrick.
Click to expand...
Click to collapse
With this method you can not, the moment it says the aboot version is different it doesn't allow the copy of it. I had this error 5-6 times before I could successfully change the aboot and all those times in between my phone was always turning on as normal...
If then you are able to flash an aboot version that doesn't match then u r unlucky...
Anyway I'm for sure not as expert as you, but I'm just reporting my experience
Ag0n1a said:
A
With this method you can not, the moment it says the aboot version is different it doesn't allow the copy of it. I had this error 5-6 times before I could successfully change the aboot and all those times in between my phone was always turning on as normal...
If then you are able to flash an aboot version that doesn't match then u r unlucky...
Anyway I'm for sure not as expert as you, but I'm just reporting my experience
Click to expand...
Click to collapse
Yeah you are right. That is just a message it will not flash it for you. But if you see that message and try to flash a lower aboot without flashing full KDZ you are in big trouble.
Can someone "Loki-fy" or something on TWRP because i am in need to use cwm 6.0.5.1 by varcian
AWESOME1092387456 said:
Can someone "Loki-fy" or something on TWRP because i am in need to use cwm 6.0.5.1 by varcian
Click to expand...
Click to collapse
For me the installation works but don't install it... i've installed cm12 and it sayed secure booting failed
and backup/restore doesn't work, it corrupted /data partition but i resolved it.
Kaszke said:
Downgrade to jb
Click to expand...
Click to collapse
How? I couldn't find a working link for a stock jb.
Cristi73 said:
How? I couldn't find a working link for a stock jb.
Click to expand...
Click to collapse
http://lg-phone-firmware.com/index.php?id_mod=37
Find the kdz that coresponds to your region/carrier.
goooooooooD!!!! amazing job ))))
JackPOtaTo said:
I Have problem: Loki aboot version does not match device. (LG D605 kitkat 4.4.2) Root:yes
Click to expand...
Click to collapse
hey here is the solution body
II Flash
GOTO D605 RECOVRY (folder) hold shift and right click on the mouse then open window command here
then copy the commands on the cmd
you need to have adb driver installed and here the download link http://www.mediafire.com/download/u6pdpy77sonjyqh/D605+RECOVRY.rar
1 adb push aboot.img /data/local/tmp
2 adb shell
3 su
4 dd if=/data/local/tmp/aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
4 exit
5 exit
6 adb push loki_flash /data/local/tmp
7 adb push recovery.img /data/local/tmp
8 adb shell
9 su
10 cd /data/local/tmp
11 chmod 777 loki_flash
12 ./loki_flash recovery recovery.img
13 reboot recovery
Hi all! I followed the procedure in terminal emulator from JB with root (through impactor)and I installed successfully twrp.
Then I installed CM11 by Varcain but the phone gives me the message "Secure booting Error! Cause: boot certification verify" .. I really can't figure out the problem after hours of search... can someone help me please?
Now I have to use kdz to reinstall JB?
EDIT: Sorry, The solution is easy, I must unlock the bootloader before flashing cm11... I forgot it! So the problem is not related to twrp
sedi21 said:
Hi all! I followed the procedure in terminal emulator from JB with root (through impactor)and I installed successfully twrp.
Then I installed CM11 by Varcain but the phone gives me the message "Secure booting Error! Cause: boot certification verify" .. I really can't figure out the problem after hours of search... can someone help me please?
Now I have to use kdz to reinstall JB?
EDIT: Sorry, The solution is easy, I must unlock the bootloader before flashing cm11... I forgot it! So the problem is not related to twrp
Click to expand...
Click to collapse
but how did you unlock it? because i don't know how to unlock mine and i don't think its possible
WARNING!
THIS GUIDE REQUIRES DISASSEMBLY, SO YOU WILL DEFINITELY LOSE THE WARRANTY!
DO IT AT YOUR OWN RISK!
If you want to repost this guide to other websites, please let me know before you repost.
For Chinese users: 中文版教程将会在dospy发布。
Click to expand...
Click to collapse
UPDATE: I've updated the new tool for unlocking the phone without understanding how to utilize such long commands.
You can watch the demonstration here: https://youtu.be/whrFsn8h7A4
Click to expand...
Click to collapse
So after I got a Nokia 4.2 prototype by opportunity, I just found the theory of bootloader unlocking.
Tricking development options for allowing "OEM unlocking" no longer works on latest security update.
What you need to have:
- a Nokia 4.2 unit that you finished back cover and upper plastic shell removal
- tweezers, and probably a standard philips screwdriver
- QPST (use at least 2.7.474) or any other app that could access the EDL, and Qualcomm USB port drivers are installed
- Latest Google Platform Tools
- Full backup of your userdata
Step 1: Trigger the phone to EDL mode, then change the driver to "Qualcomm HS-USB QDLoader 9008"
Please take a look at the attachment below, about the location you need to use tweezers.
For Windows users:
If the driver is already indicated as "Qualcomm HS-USB QDLoader 9008", get to Step 2.
If the driver is indicated as either "QHSUSB__BULK" (For users who have installed Windows Device Recovery Tool before) or "Qualcomm HS-USB Diagnostics 9008", you must change the driver to "Qualcomm HS-USB QDLoader 9008".
After driver changed, you need to disconnect the phone, disconnect and reconnect the battery ribbon cable, then trigger the phone to EDL again.
I assume the COM port number is 8 (COM8).
Click to expand...
Click to collapse
Step 2: Write config partition
As we already know, config partition is also the frp partition.
You need to create a config partition image that has "OEM Unlocking" function enabled, which need to alter the last byte, then change the overall checksum to make the config file valid.
For your convenience, I've created one.
Now download and extract the attachment below.
Use QFIL included in QPST to load the firehose file. Choose "Flat Build" and choose the "prog_emmc_firehose_8937_ddr.mbn" you extracted from the attachment.
Choose "Tools" - "Partition Manager", then wait for the partition list appear.
As "Load Image" seems not reliable, we have to use command to write it manually.
For 64-bit Windows users, the command is:
Code:
"C:\Program Files (x86)\Qualcomm\QPST\bin\fh_loader.exe" --port=\\.\COM8 --search_path=D:\path\to\where\you\extracted\N32_N42_unlock --sendimage=config.img --start_sector=16583680 --lun=0 --noprompt --showpercentagecomplete --zlpawarehost=1 --memoryname=emmc
If you use 32-bit Windows, you need to remove the " (x86)" (within space, without quotes) in the command above.
Step 3: Trigger the phone back to fastboot mode
Now hold the Volume down key, keep the phone connected, close the partition manager, then your phone will exit EDL mode and enter Fastboot mode directly.
Now check the unlock ability:
Code:
fastboot flashing get_unlock_ability
Expected output:
Code:
get_unlock_ability: 1
Step 4: Unlock the bootloader!
And you can unlock the bootloader with familiar commands.
Code:
fastboot flashing unlock_critical
Confirm unlock on the phone, then keep the volume down key pressed while the phone is erasing userdata.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Your phone will boot to fastboot mode again, and then:
Code:
fastboot flashing unlock
Confirm unlock on the phone again.
All done, that's how the bootloader is unlocked. You can reassemble the phone.
But strange enough, you can't see any unlock warning.
I will release boot image dumping guide and root guide very soon.
Special thanks:
Wingtech for leaking prototype units
why must Nokia insist on locking their devices down so hard ??
great discovery, will definitely be useful once TWRP is released. just curious, but SafetyNet is tripped with this, right?
Great!
Damn Nokia
I don't even own this phone but I kinda want to weigh in, are we seriously at this point? No honestly, Android as a whole was basically were dev focused iOS is locked down to hell and back here's freedom. Google has the Nexus line made for developers companies embraced it I remember there being multiple Google play editions of phones that ran stock Android. I'm happy we as a community can keep this alive but damn are companies trying to make it difficult to do something I want to do to a device I paid for and own. Samsung you can't root (save for sampwn and samfail) LG locked down bootloaders and gimped fastboot on some models (fastboot seriously?) Nokia now requiring you to take apart the freaking phone to achieve this, I'm half asleep and can't think of any other major brands at the moment. It's a joke. (Above root methods were mainly for US variants and TMobile variants of LG) something has to change I know it won't and I understand the reasoning behind it security and such but still. Sorry for the rant congrats OP on what you did I consider it magic but it's more you accomplished something I could only wish I could do.
Will it be possible to do without disassembly? Just in theory, not now
kir23rus said:
Will it be possible to do without disassembly? Just in theory, not now
Click to expand...
Click to collapse
Unwise to say no with absolute certainly, but doubtful
kir23rus said:
Will it be possible to do without disassembly? Just in theory, not now
Click to expand...
Click to collapse
I think it will be possible.
There's a hidden command in aboot "fastboot reboot-emergency" but unusable, unless some sort of authentication is done or bootloader unlocked.
I still don't know how the authentication is done yet, but it's definitely not something that average developers can access to.
That's why disassembly is required for now.
Very interesting breakthrough. Great work
I'm facing the same bootloader unlock in my infinix hot s 3. I believe I can use your procedure to unlock my device. And if necessary how to make changes to the config file? I will be expecting your reply soon. Thanks
Is it possible to explain how the config.img file is altered ? It might not be difficult to alter the last byte , but what does it mean to Change the overall checksum ? I have been trying to do something similar for a while , it would be great if you answered here or via PM , thank you
awab228 said:
Is it possible to explain how the config.img file is altered ? It might not be difficult to alter the last byte , but what does it mean to Change the overall checksum ? I have been trying to do something similar for a while , it would be great if you answered here or via PM , thank you
Click to expand...
Click to collapse
Fill first 32 bytes with 0x00, then calculate SHA256 checksum and paste the new checksum as hex value at the first 32 bytes.
hikari_calyx said:
Fill first 32 bytes with 0x00, then calculate SHA256 checksum and paste the new checksum as hex value at the first 32 bytes.
Click to expand...
Click to collapse
Thank you for taking the time to explain, great help and great effort, the last byte should be altered to 1 ? Or 0 ?
awab228 said:
Thank you for taking the time to explain, great help and great effort, the last byte should be altered to 1 ? Or 0 ?
Click to expand...
Click to collapse
1 for allow, 0 for disallow
do you have any fastboot rom or rawxml rom for this device ??
mine always reboot in bootloader mode.
malkabhai said:
do you have any fastboot rom or rawxml rom for this device ??
mine always reboot in bootloader mode.
Click to expand...
Click to collapse
We have full OTA zip of it.
You can use payload dumper + img2simg to convert it to fastboot images. If recovery mode working (including unofficial TWRP), you can also reboot your phone to recovery mode to sideload it.
PAN-141B-0-00WW-B03-update.zip
I was able to use "OEM Unlocking" from developer options and after starting at step 3, to obtain a full unlock. After I was also able to fully root my phone using the normal guide. I am running the latest security update (October 5 2019). No idea why this worked for me...
Hello,
I've got the Nokia 3.2 16gb variant. I can get it into edl mode but it seems to be in Sahara mode. How can I put it into firehose mode? Because I can't load anything using qfil.
Any help?
Missing pads
Any idea where these pads could be now? That does not seem to be there anymore?
Missing testpoint pads
piteer1 said:
Any idea where these pads could be now? That does not seem to be there anymore?
Click to expand...
Click to collapse
I has the same problem. Thanks in advance.
I don't see those test point in my mobile
Hi, does this work for Nokia 6.1 plus TA-1083? or do you have any trick for this too?
I am able to load phone in EDL Mode by making EDL Points short.
Just in case you read my comment, I have a emmc problem post, if you can help -
https://forum.xda-developers.com/nokia-6-1-plus/help/nokia-6-1-plus-edl-mode-emmc-failure-t4114507
Hello, I am a windows user and wish to create a multiboot usb which I can use to opt multiple OS to install but I am facing some problem, I used all types of software for making bootable usb like WINUSB, VENTOY and MULTIUSB but when I start the process after adding iso of windows 10 and windows 7, A blue screen of death appears and it says that a system service known as CLASSPNP.SYS has excepted and your pc needs to restart. I face this problem everytime while creating a bootable usb, I even tried this on another pc but this problem is still there, any help regarding this problem will be greatly appreciated.
After multiple failed attempts, I finally called Microsoft and asked. These are the instructions they emailed me:
1. Insert a USB at least 4GB in size
2. Open CMD prompt as Admin
3. Run diskpart
4. Run list disk
5. Select your flash drive by running "select disk"
6. Run clean by typing "clean"
7. Create a partition by typing "create partition primary"
8. Select the new partition by typing "select partition 1"
9. Format the partition by typing "format fs=ntfs quick"
10. Set the current partition as Active by typing "Active"
11. Exit diskpart
12. Mount your ISO. Use Virtual CloneDrive or something similar.
13. Navigate to the mounted image and install a bootsector. Ex. If the mounted ISO is on drive G: you'd navigate to G:\ boot and run:
C:\WindowsSystems32> G:
G:\> cd boot
G:\boot> bootsect.exe /nt60 E: (where E:\ in this case is my flash drive's letter)
14. Copy the entire contents of the ISO to your flash drive by typing " G:\> xcopy g:\*.* e:\ /E /H /F"
Once that's done, your USB is finished.
Bro these tricks are really helpful, I really appreciate your help
Is the SATA setting in the BIOS for the boot machine set to AHCI (which it should be) or something else? I haven't seen it set for something else in a while (multi maybe) but you could check that?
jackmeat said:
Is the SATA setting in the BIOS for the boot machine set to AHCI (which it should be) or something else? I haven't seen it set for something else in a while (multi maybe) but you could check that?
Click to expand...
Click to collapse
Bro what do you mean, actually i have upgraded my laptop with Acer ssd last year.
Manmeet_2008 said:
Bro what do you mean, actually i have upgraded my laptop with Acer ssd last year.
Click to expand...
Click to collapse
And please tell how to check the boot type
Bro, I checked the Bios and it was set to AHCI mode as you told. Now what to do.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Was just an idea of things I have seen. Have you tried different USBs of different sizes? And messed around with choosing ntfs/exfat/fat32? Pretty sure with windows installs now NTFS is preferred but could still try juggling around. Also, is it only with the Windows 10 isos on the multiboot USB? I know that the newer ISOs have had issues with being bootable and maybe they are the problem. Did you try with just a windows 7 ISO and maybe a ubuntu image as well just to see if those work. I personally use ventoy so trying things out like this is a breeze. I know I have had windows 10 isos that didn't work but they never crashed ventoy entirely so it seems something else is going on.
Yes bro You are right, It works if you first make the ventoy iso bootbable using rufus and then we should turn off the secure boot option in BIOS then we should boot into usb, then we should follow the steps of the ventoy live cd. After that the ventoy bootbable drive would be ready. Now I booted into windows and observed that there is no more space left on usb, then i used minitool partition software or any other software (minitool is recommended) and formatted the remaining exfat partition into NTFS or Fat32. After that the partition became visible and I copied both Iso files in that partition, in the end you can turn on secure boot . This should definitely work. You can install the ventoy iso from their github page.
https://github.com/ventoy/Ventoy/releases/download/v1.0.71/ventoy-1.0.71-livecd.iso
Manmeet_2008 said:
https://github.com/ventoy/Ventoy/releases/download/v1.0.71/ventoy-1.0.71-livecd.iso
Click to expand...
Click to collapse
I am not sure why you are telling me how to use something I am already using for years without issue? I was just throwing some ideas at you to try. I know I never had to deal with using a separate partition tool to get the USB ready for ventoy at all. That was all part of the Ventoy2Disk.exe and I didn't mess with the livecd at all. Maybe whatever is causing you to be unable to use Ventoy2Disk.exe is also causing issues with the media creation.
Actually I was just telling how I solved the problem. Ventoy2Disk.exe is not working in my pc as when I start the process to make bootable usb , I get a BSOD and CLASSPNP.SYS exception error. Then I found the alternative of Ventoy2Disk.exe which is Livecd.iso
Manmeet_2008 said:
Actually I was just telling how I solved the problem. Ventoy2Disk.exe is not working in my pc as when I start the process to make bootable usb , I get a BSOD and CLASSPNP.SYS exception error. Then I found the alternative of Ventoy2Disk.exe which is Livecd.iso
Click to expand...
Click to collapse
Have you asked in the ventoy forums about this? I read this as a problem attempting to boot after creation, but this is a problem in actually creating the boot USB?
Bro I havent asked yet but will ask and tell you what they said
Manmeet_2008 said:
Hello, I am a windows user and wish to create a multiboot usb which I can use to opt multiple OS to install but I am facing some problem, I used all types of software for making bootable usb like WINUSB, VENTOY and MULTIUSB but when I start the process after adding iso of windows 10 and windows 7, A blue screen of death appears and it says that a system service known as CLASSPNP.SYS has excepted and your pc needs to restart. I face this problem everytime while creating a bootable usb, I even tried this on another pc but this problem is still there, any help regarding this problem will be greatly appreciated.
Click to expand...
Click to collapse
You'd probably want to keep it on fat32 for older computers and OSes, or ntfs for newer ones. Can't mix and match on the same stick. Then you'd need grub or some usb bootloader menu to input the other OS values.
Manmeet_2008 said:
Hello, I am a windows user and wish to create a multiboot usb which I can use to opt multiple OS to install but I am facing some problem, I used all types of software for making bootable usb like WINUSB, VENTOY and MULTIUSB but when I start the process after adding iso of windows 10 and windows 7, A blue screen of death appears and it says that a system service known as CLASSPNP.SYS has excepted and your pc needs to restart. I face this problem everytime while creating a bootable usb, I even tried this on another pc but this problem is still there, any help regarding this problem will be greatly appreciated.
Click to expand...
Click to collapse
U can use easy to boot to make a multi os bootable flash disk. it supports both legacy and UEFI systems.
Easy2Boot The USB multiboot solution (legacy, UEFI, Secure Boot)
The free USB multiboot solution for professionals (legacy+UEFI, Secure Boot, automate Windows installs, DOS, XP, Ventoy)
easy2boot.xyz
Thankyou everyone for your help, now i have found the exact solution. Actually my antivirus program was interfering with the whole process. I tried the process in safe mode and it worked like a charm. Now i have removed the antivirus and make multiboot usb without any interruptions!!
Please help ....
It's a problem you get notified of by the GRUB bootloader: you have deleted Linux partitions before removing GRUB bootloader.
My recommendation: Remove the GRUB bootloader, will say go back to Windows bootloader.
No problem man