Related
I9000 unlock instructions
1. Power on the phone and go to Applications->Settings->About Phone->USB
settings
2. Select Mass Storage
3. Connect the phone to USB cable
4. Swipe down the top notification bar then tap “USB Connected” then select
MOUNT
5. Copy update.zip file to phone mass storage root
6. Power off the phone
7. Press Volume Up+Home+Power on key to start the phone into recovery
mode
8. Go to “apply sdcard:update.zip” using volume keys then select it using
home key
9. Power on the phone then go to Andoid Market and install Terminal
Emulator
10. Run Terminal Emulator
11. Type cat /efs/nv_data.bin >> /sdcard/nv_data.bin into terminal then type
Enter
12. Connect the phone to PC in USB Storage Mode then copy nv_data.bin file
to your pc
13. Open nv_data.bin file with any hex editor (ex. Hex workshop) then go to
address 00181460
14. There are the codes
15. Power on the phone with any unaccepted sim card inside then type in the
first code to unlock the phone
I9000 drivers
I9000 drivers
This solution is is not working for me. The problem is that the Update.zip says:
E: Signature verfication failed
Installation aborted
Any advice? How to install that update.zip package?
cellularhut said:
I9000 unlock instructions
1. Power on the phone and go to Applications->Settings->About Phone->USB
settings
2. Select Mass Storage
3. Connect the phone to USB cable
4. Swipe down the top notification bar then tap “USB Connected” then select
MOUNT
5. Copy update.zip file to phone mass storage root
6. Power off the phone
7. Press Volume Up+Home+Power on key to start the phone into recovery
mode
8. Go to “apply sdcard:update.zip” using volume keys then select it using
home key
9. Power on the phone then go to Andoid Market and install Terminal
Emulator
10. Run Terminal Emulator
11. Type cat /efs/nv_data.bin >> /sdcard/nv_data.bin into terminal then type
Enter
12. Connect the phone to PC in USB Storage Mode then copy nv_data.bin file
to your pc
13. Open nv_data.bin file with any hex editor (ex. Hex workshop) then go to
address 00181460
14. There are the codes
15. Power on the phone with any unaccepted sim card inside then type in the
first code to unlock the phone
Click to expand...
Click to collapse
Fantastic find if it works, my phone is unlocked so I can't test it but thanks a lot for sharing!!! Priceless
N.B. The first 8 steps are the process for rooting your phone, since you need to be root to do step 11. If you already have a rooted phone, start from step 10.
tyxerakias said:
fantastic find if it works, my phone is unlocked so i can't test it but thanks a lot for sharing!!! Priceless
n.b. The first 8 steps are the process for rooting your phone, since you need to be root to do step 11. If you already have a rooted phone, start from step 10.
Click to expand...
Click to collapse
1000000000000000% working tested before post here !!!!!
I am following 100% tutorial but I am unable to unlock my I9000. Look at the screenshot for the error that I encounter.
I have put the update.zip in root of phone memory, root of MicroSD etc but no chance. Do I need to root the phone or what's the problem?
Thanks
erreterr said:
I am following 100% tutorial but I am unable to unlock my I9000. Look at the screenshot for the error that I encounter.
I have put the update.zip in root of phone memory, root of MicroSD etc but no chance. Do I need to root the phone or what's the problem?
Thanks
Click to expand...
Click to collapse
Please read my post above. By doing this, you are rooting your phone.
It seems that the update.zip has not been properly signed, I see that it contains a new busybox, maybe the OP tried to optimise it and failed?
Use the original update.zip from the FAQ (http://www.multiupload.com/JHIFK9K80P) to root your phone, then continue from step 9.
The same happens with the file that I downloaded from your posted link!!!
Whats going wrong here?
Tyxerakias said:
Please read my post above. By doing this, you are rooting your phone.
It seems that the update.zip has not been properly signed, I see that it contains a new busybox, maybe the OP tried to optimise it and failed?
Use the original update.zip from the FAQ (http://www.multiupload.com/JHIFK9K80P) to root your phone, then continue from step 9.
Click to expand...
Click to collapse
No idea. Have you rooted your phone already? Have you installed any mods or firmwares?
No need to root
You dont need to root your phone to get to Step 11. The Terminal Emulator I installed from the Market let me do Step 11 directly.
All I then just did was email the nv_data.bin file to my inbox and later just open it in Textpad.
So, it was a bad tutorial. I tried to go step by step but now I begin from step 11 and everything is OK. My first I9000 unlocked like a charm
Thanks
knkartha said:
You dont need to root your phone to get to Step 11. The Terminal Emulator I installed from the Market let me do Step 11 directly.
All I then just did was email the nv_data.bin file to my inbox and later just open it in Textpad.
Click to expand...
Click to collapse
Huh. Interesting. I would have thought /efs is a protected folder.
I have a Bell one, i asked their staff when i bought my phone if i still on WARRANTY when i unlock the phone by Bell, they said yes.
Anybody know if i will lose my phone WARRANTY after i unlock the phone? Or can i lock it back if my phone have any problem in the future?
Thanks
could somebody point out which value in the address 00181460 says the unlock code?
erreterr said:
The same happens with the file that I downloaded from your posted link!!!
Whats going wrong here?
Click to expand...
Click to collapse
you should put the update.zip file on your internal sd card directory.
i encountered the same error when i put the update.zip file in the external sd card
erreterr said:
So, it was a bad tutorial. I tried to go step by step but now I begin from step 11 and everything is OK. My first I9000 unlocked like a charm
Thanks
Click to expand...
Click to collapse
which of the values in the said address gives the unlock code?
Hi,
I have a NSPRO box and read the unlock code, but as I insert it, it doesn't unlock the phone.
As this didn't work, I tried your method, and the code that showes up is the same as read by NSPRO box, and... it still doesn't work.
Attached is the printscreen of the HEX area where the code is. I've noticed it says "18146D" and not "181460" as your indicated. Could this be the reason why the code doesn't work?
Please help...
Samsung Vibrant SGH-T959 Recovery Mode
I've tried all sorts of button combinations to get the Samsung Vibrant T959 into recovery mode. I think since this device is a T-Mobile phone, the firmware has been modified for VolUp+VolDn+Pwr recovery mode.
As of now, the only way I know how to get the phone into recovery mode is by using the Android SDK and sending off a command: adb reboot recovery
I've been putting together an Android SDK & Rooting tutorial as well as other Samsung Vibrant T959 findings here: jordanpeterson.me/content/t-mobile-samsung-vibrant-sgh-t959
Sorry.. the external references aren't working.. Good spam rules on new users.
Thanks
Jordan
It worked great, althoug the address on my I9000 was 00181462. My suggestion is try to find closest address to the given by the tuturial....
Thanks for everything
Don't need to root the device. Download terminal emulater from Market. Went straight to step 10. Works like a charm. Thanks for the instructions.
Sent from my GT-I9000M using XDA App
HOW CAN I ACCES root directory SDCARD from PC so I can place there my Rom to Flash it?
I Have formated everything, including the SDCARD, And now I only can get into RECOVERY mode,
Is there any way I can Flash my rom from Recovery?
How can I get acces to the SDcard ROOT directory so tha I can place there my Rom in order to Flash It ?
Is ther an ODIN type of flashing Roms in Nexus 7 just like in the S3?
How can I flash Rom from a Formatted SDCARD?
If you are in Recovery, then you can still use ADB. That means you can push files to your device.
Sent from my Nexus 7
BillGoss said:
If you are in Recovery, then you can still use ADB. That means you can push files to your device.
Sent from my Nexus 7
Click to expand...
Click to collapse
Plese Tell me HOW to use ADB ? What do I have to do to push the Rom files into Root Directory of SDCARD?
I am using CWM recovery TOUCH 6.0.1.0
If you are connected to your PC you are seeing the sdcard root directory. Not sure what you are looking for
Sent from my SPH-L710 using Tapatalk 2
Moricon said:
If you are connected to your PC you are seeing the sdcard root directory. Not sure what you are looking for
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
I aM Connected to PC in RECOVERY mode,
The driver is installed OK
BUT I DONT SEE MY DEVICE IN PC
So I can not Push Rom fils to Root SDCARD directory becasuse I DONT SEE IT
When I PLUG in and Unplug I hear the USB installing BUT I DONT SEE THE DEVICE in my EXPLORER...So I dont Know Where I must Put Rom files to flash my Nexus 7...
My Device is ATTACHED into RECOVERY MODE
But I dont see it in my FileExplorerSo I dont Know HOW can I copy Rom to my SDCARD root directory...
Is there a COMMAND to copy rom from the CMD ?
OR is there a COMMAND for FLASHING ROM from within CMD
HELP NEEDED PLEASE:silly:
WHAT is the COMMAND to DUMP ROM into the SDCARD with Android. SDK and the CMD?
I am using the DEXDUMP.exe command but I dont know how it works...
NDUTU said:
I aM Connected to PC in RECOVERY mode,
The driver is installed OK
BUT I DONT SEE MY DEVICE IN PC
So I can not Push Rom fils to Root SDCARD directory becasuse I DONT SEE IT
When I PLUG in and Unplug I hear the USB installing BUT I DONT SEE THE DEVICE in my EXPLORER...So I dont Know Where I must Put Rom files to flash my Nexus 7...
Click to expand...
Click to collapse
Then you don't have the right drivers loaded if your pc can't see your device...
Sent from my Nexus 7
krelvinaz said:
Then you don't have the right drivers loaded if your pc can't see your device...
Sent from my Nexus 7
Click to expand...
Click to collapse
Yes I DO HAVE the right drivers loaded see the attached file,
The command is adb push. I'm not at my computer and it's too hard to type and example on my phone for you. Just Google adb push and you should get your answer. Hope this helps.
adb push <where rom is stored>/<name of zip>.zip /sdcard/<any name here>.zip
ie adb push E:/cm10-UNOFFICIAL-i777.zip /sdcard/cm10.zip
you might have to reboot the device back into recovery, even if you're already in recovery, for it to come up. Then just flash it like normal. You do have CWM or TWRP, right?
THANKS
OK guys thank you all , I managed to flash STOCK rom with the tool kit using the : put_google_factory_image_here , FOLDER
{
"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"
}
Setup, Preparation and Prerequisites
I know there are already a few root guides out there for this phone, but I found that they weren't very detailed. This guide is thorough and explains each and every step in a noob-proof manner.
Basic tasks that I may refer to throughout this guide:
Open command prompt - Press Window Key + R, type in "cmd" (without the quotes), and hit enter.
Enter fastboot mode- Turn the phone off. Hold volume up + power until the "fastboot" screen appears.
ADB and Fastboot Installation
Download the full Android SDK here (scroll to the bottom of the page>DOWNLOAD FOR OTHER PLATFORMS>SDK Tools Only) or get a slimmed version containing only the essential components here
Extract the zip and place the android-sdk-windows folder on your desktop.
**If you chose to download the slimmed sdk skip to step 5**
Only if you downloaded the full sdk: Go into the android-sdk-windows folder and run SDK Manager.exe. Install the following packages (there are a total of 4 packages):
- Tools > Android SDK Tools, Android SDK Platform-tools
- Extras > Android Support Library, Google USB Driver
Only if you downloaded the full sdk: Go back into the android-sdk-windows directory, and you should see a new folder named platform-tools. If you don't see this new folder, repeat the step above.
To confirm that it is indeed working, open a command prompt window and enter the following commands:
Code:
cd Desktop/android-sdk-windows/platform-tools
adb version
If it displays "Android Debug Bridge version x.x.xx" it is working. If it is gives an error saying that adb is not a recognized command, it has not been successful. Carefully repeat the steps above if this is the case. Close the command prompt window when you are done.
Show File Extensions - Open a command prompt window and run "Control folders" (without the quotes). Go to the View tab and uncheck the "Hide extensions for known file types" option. This will help avoid confusion when renaming files.
Battery - Ensure that your phone has at least 60% battery remaining, and that your PC is plugged in and wont shut down spontaneously during the process. The procedure doesn't take very long (5-15 minutes), but its best to have enough charge in case something goes wrong.
Backup (Optional) - Unlocking the bootloader will completely wipe all data from the device. This includes apps, settings and even the contents of the internal sdcard (pictures, music, etc.). Copy all important files off the phone onto a PC or upload them to a cloud.
Driver Installation - Download and install the Universal ADB Driver. Alternatively, use this method.
Downloads
Download a custom recovery and the SuperSU zip below. Place both files (recovery image and root zip) in the platform-tools folder located on your desktop within the android-sdk-windows folder.
Custom Recovery:
TeamWin Recovery Project (TWRP)
Root:
SuperSU
Information
Rooting this device is actually quite a simple and easy process. Before you begin, it is recommended that you at least try to understand what each part of the process will do. Although this guide will elongate each step in order to show all of the details, the method used can be broken up into 3 main steps: Unlocking the Bootloader, Installing a Custom Recovery and finally Rooting. Each new step relies on the previous step to have been completed, and a basic summary of each part is:
Unlocking Bootloader: Opens the door to the internal memory of the device to be written on to. This allows you to flash images onto the main partitions of the phone.
Installing a Custom Recovery: A custom recovery is flashed onto the recovery partition of the device and overwrites the stock recovery that exists by default. Custom recoveries bring lots of functionality and give you the ability to perform wipes, install flashable zips, create full backups of your NAND (Nandroid backup), and various other features. An unlocked bootloader is needed to install a custom recovery.
Rooting: You can gain root by either flashing via recovery a pre-rooted custom rom, or flashing a zip containing the SuperSU binaries. A custom recovery is necessary to do this.
After completing these steps your phone will be rooted, the phone will have a custom recovery installed, and the phones bootloader will be unlocked. This, in my opinion, is the most practical and beneficial method for rooting your phone. It gives you some basic adb/fastboot knowledge, and should hopefully help you have a decent understanding of what is going on. Also this method will work regardless of what android version your phone has.
If you are confused by anything in this guide, I would highly suggest getting it clarified being before moving on. Ask your question in this thread and I or someone else will likely answer. Also I'd suggest that you read over the whole thread a few times before actually doing anything to the phone.
Understand? Good...lets begin:
1. Unlocking Bootloader
Turn the phone off. Then boot it into fastboot mode by holding volume up + power. The phone will display "fastboot" text indicating that it has successfully entered fastboot mode.
Plug the phone into your PC, then open a command prompt window and type:
Code:
cd Desktop/android-sdk-windows/platform-tools
Code:
fastboot devices
This command will list the connected devices. If your phones serial number shows up you are good to go and may continue. If the phone is NOT listed this indicates that your drivers are not installed correctly. In order for you to continue you must fix your drivers so that your phone is listed under fastboot devices.
If the phone has been recognized by the command above, proceed to unlocking the bootloader with the following command:
Remember that this step will wipe EVERYTHING off the phone
Code:
fastboot oem unlock
After the above command has finished excuting, run the following
Code:
fastboot reboot
The phone will reboot. Wait until the phone has fully booted up into android, then adjust the following settings on the phone:
USB Debugging - On your phone go to Settings > About phone > Tap on Build number 7 times. This will enable Developer options. Now go back to Settings > Developer options > Enable USB debugging
Disable CM Recovery Protection - On your phone go to Settings > Developer options. Then disable the 'Update recovery with system updates' option.
Close the command prompt window and proceed onto the next section of the guide.
2. Installing a Custom Recovery
Turn the phone off. Then boot it into fastboot mode by holding volume up + power.
Rename the recovery file that you downloaded above to recovery.img. *Make sure that you rename it to recovery.img NOT recovery.img.img* Remember that this file should be placed in the platform-tools folder inside of the android-sdk-windows folder on your desktop.
Open a new command prompt and run the following commands:
Code:
cd Desktop/android-sdk-windows/platform-tools
Code:
fastboot flash recovery recovery.img
Once the flash has completed type the following command to reboot the phone:
Code:
fastboot reboot
After the phone has booted back up, turn it off. Now to enter your newly installed custom recovery, hold volume down + power. The phone should boot into recovery mode. Now that you have a custom recovery, you may continue to the final step.
Close the command prompt window.
3. Rooting
Now that your phone has an unlocked bootloader and a custom recovery installed you have a two options to gain root (Pick one or the other. You don't need to do both)
Option A) Flash SuperSU binaries which will give you root with the stock ROM
Confirm that you have downloaded the SuperSU zip from the downloads section above and that it is located in the platform-tools folder inside of the android-sdk-windows folder on your desktop.
Turn the phone off then boot into recovery mode by holding volume down + power. Leave the phone at the main screen of the custom recovery for now.
Open a command prompt window and run the following commands:
Code:
cd Desktop/android-sdk-windows/platform-tools
Code:
adb push UPDATE-SuperSU-v[COLOR="Red"]X[/COLOR].[COLOR="red"]XX[/COLOR].zip /sdcard/
This will copy the SuperSU zip onto your phone. Once the command has completed continue.
Instructions for TeamWin Recovery Project (TWRP):
Install > browse to SuperSU zip and select the it
Swipe to confirm the installation. Then reboot.
Instructions for ClockworkMod (CWM):
install zip from sdcard > choose zip from sdcard.
Next, browse to the location where you previously copied the SuperSU zip and select the it.
To confirm the installation, scroll down to "Yes" and select it. The installation shouldn't take very long, and once it has completed you may reboot.
Option B) Flash a custom rom which will come pre-rooted
Note that not all custom roms will be pre rooted, however the majority of them are. Read the OP of the ROM thread to see what the verdict is.
Copy a custom rom (you can find these in the ONE Android Development and ONE Original Android Development section) onto the phone (remember the location of where you copy it to)
Turn the phone off then boot into recovery mode by holding volume down + power. To install a custom ROM the general procedure to follow is: factory reset, wipe cache + dalvik cache, flash ROM, flash GApps. Here are the recovery specific instructions:
Instructions for TeamWin Recovery Project (TWRP):
Wipe > Swipe to Factory Reset
Install > browse to the location where you previously copied the ROM zip and select it > Swipe to confirm the installation
Install GApps using same process as ROM, then reboot.
Instructions for ClockworkMod (CWM):
wipe data/factory reset
wipe cache partition
advanced > wipe dalvik cache
install zip from sdcard > choose zip from sdcard > navigate to the location of the ROM > select the ROM > confirm the installation by selecting "Yes"
After that you may install the GApps using the same method for flashing the ROM, and finally reboot the phone.
Keep in mind that the first boot after installing a custom ROM & wiping the phone may take longer than usual, as the phone will need to rebuild the dalvik cache and initialize other first boot stuff.
Congrats! That is all! Your phone now has an unlocked bootloader, a custom recovery installed and is rooted. Enjoy
Reserved.
Thanks Dude For making this Helpful... Sure it will help us with our one plus one..........
Nice guide!!
Sent from Mallorca to your face
Great guide! Will definitely follow when my OPO arrives! :victory:
Thanks a lot for the thread sir ! Btw have some problems I m running and old XP and seems the commands don't work for me .. Would you show me a pics of your root folder on your desktop for the sdk please ?
And I have kies installed before .. Maybe drivers aren't working together ?
pro castinato said:
Thanks a lot for the thread sir ! Btw have some problems I m running and old XP and seems the commands don't work for me .. Would you show me a pics of your root folder on your desktop for the sdk please ?
And I have kies installed before .. Maybe drivers aren't working together ?
Click to expand...
Click to collapse
What do you mean the commands don't work? Could you explain if you are getting an error, what the error is, etc.
Chromium said:
What do you mean the commands don't work? Could you explain if you are getting an error, what the error is, etc.
Click to expand...
Click to collapse
Hum , so I will try to translate my commands from French lol
First I try to install 15 seconds adb installer and failed . Told me all files already copied and "stex" is missing .
After I install the sdk as you said , I put the folder on my desktop and try to get adb worked with the test entry . But my command said that there is a invalid way
pro castinato said:
Hum , so I will try to translate my commands from French lol
First I try to install 15 seconds adb installer and failed . Told me all files already copied and "stex" is missing .
After I install the sdk as you said , I put the folder on my desktop and try to get adb worked with the test entry . But my command said that there is a invalid way
Click to expand...
Click to collapse
Could you post a screenshot of the command prompt output? Thanks.
Chromium said:
Could you post a screenshot of the command prompt output? Thanks.
Click to expand...
Click to collapse
Yeah of course man , let me an hour I will show you all with pics . Thanks a lot again for helping us and for the thread sir ! I just received my One 64GB official this morning . Damn I love CM11S and this beast don't leave my hand since this morning ahah . Hope your like yours too ...
Can't wait for great PA , Carbon , Omni roms on dat crazy phone
pro castinato said:
Yeah of course man , let me an hour I will show you all with pics . Thanks a lot again for helping us and for the thread sir ! I just received my One 64GB official this morning . Damn I love CM11S and this beast don't leave my hand since this morning ahah . Hope your like yours too ...
Can't wait for great PA , Carbon , Omni roms on dat crazy phone
Click to expand...
Click to collapse
Nice, you're lucky I dont even have the phone yet...hopefully I can get my hands on it in the next couple of weeks or so, otherwise I'll probably have to go with a Nexus 5. Once you've installed a custom recovery check out my SlimRom build. I'm also planning on compiling Carbon, but first I'd like to make sure that Slim is functioning properly.
Chromium said:
Nice, you're lucky I dont even have the phone yet...hopefully I can get my hands on it in the next couple of weeks or so, otherwise I'll probably have to go with a Nexus 5. Once you've installed a custom recovery check out my SlimRom build. I'm also planning on compiling Carbon, but first I'd like to make sure that Slim is functioning properly.
Click to expand...
Click to collapse
Awesome man! Thanks for the help and ports ! If you need I should get like 3 invites this week or less so if you need one let me know , give me your mail address and I will send one your way to thank you
Hey man so here is the problem . I can recognize my One with adb , but can't fasboot after on my mac ...
Here are the commands :
macbook:android NikonografferZ$ ./adb devices
List of devices attached
51cf713e device
macbook:android NikonografferZ$ fasboot devices
-bash: fasboot: command not found
macbook:android NikonografferZ$
And if I plug my phone in Fastboot mode from start on my mac he don't recognize it ..
pro castinato said:
Hey man so here is the problem . I can recognize my One with adb , but can't fasboot after on my mac ...
Here are the commands :
macbook:android NikonografferZ$ ./adb devices
List of devices attached
51cf713e device
macbook:android NikonografferZ$ fasboot devices
-bash: fasboot: command not found
macbook:android NikonografferZ$
And if I plug my phone in Fastboot mode from start on my mac he don't recognize it ..
Click to expand...
Click to collapse
>macbook:android NikonografferZ$ fasboot devices
>fasboot
pro castinato said:
Hey man so here is the problem . I can recognize my One with adb , but can't fasboot after on my mac ...
Here are the commands :
macbook:android NikonografferZ$ ./adb devices
List of devices attached
51cf713e device
macbook:android NikonografferZ$ fasboot devices
-bash: fasboot: command not found
macbook:android NikonografferZ$
And if I plug my phone in Fastboot mode from start on my mac he don't recognize it ..
Click to expand...
Click to collapse
You are missing the "t" in fastboot. You wrote "fasboot", but it should be "fastboot". If that doesnt work, try adding the ./ prefix. ie: "./fastboot devices".
Chromium said:
You are missing the "t" in fastboot. You wrote "fasboot", but it should be "fastboot". If that doesnt work, try adding the ./ prefix. ie: "./fastboot devices".
Click to expand...
Click to collapse
Man I win i Unlock Bootloader and I flash TWRP but is it normal when I restart in recovery I still have the Cyanogen Simple Recovery ?? Damn .....
EDITED !!!! FINALLY ROOTED MY ONE PLUS ONE !!!!!!! Finally read read read 18536 threads and I win ahahha
pro castinato said:
Man I win i Unlock Bootloader and I flash TWRP but is it normal when I restart in recovery I still have the Cyanogen Simple Recovery ?? Damn .....
Click to expand...
Click to collapse
Open settings > developer options. Then look for an option that says 'Update recovery with system updates' and disable it.
Thank you for this guide, it was very easy to follow. I am now rooted and ready to spice this phone up
Sent from my One using Tapatalk
pro castinato said:
l
EDITED !!!! FINALLY ROOTED MY ONE PLUS ONE !!!!!!! Finally read read read 18536 threads and I win ahahha
Click to expand...
Click to collapse
Haha, nice. What got it to finally work?
Sent from my HTC Desire using XDA Free mobile app
Chromium said:
Haha, nice. What got it to finally work?
Sent from my HTC Desire using XDA Free mobile app
Click to expand...
Click to collapse
Some problems with the T of fastboot lol nope some drivers weird to install .. I needed to install driver even for fastbooted device with Pda.net app who work really fine !! I really thanks the pdanet software <3
HERE is the system.img firmware only from 10F KDZ file, should work with all variants of the G4 (i hav'nt tried it myself yet, as im away in hospital all day)
DOWNLOAD HERE
It's google drive so quata will go fast, so if youd like you can mirror it.
Download the system.zip file and extract it.
instructions by TEAM_CodeFire modified by smaberg
1.) install all windows driver and adb, fastboot files, download and extract LG_Root for appropriate files http://d-h.st/uO8h
2.) Enable ADB debugging on your device, Go to Settings > About Phone > Software Information and tap build number until you are presented with "You are now a developer"
Exit back to Settings main screen. In Developer Options enable USB Debugging (Some devices require enabling PTP for debugging to work)
3.) In the root of LG_Root folder start a command prompt, Inside of LG_Root folder hold shift and right click a blank space you should see "Open command window here"
4.) Well that was easy , let's continue (Now that we have the files on our device we want to put our device is download mode)
Power off your device
When the device is powered off, hold volume up and insert a USB cable connected to the PC
Wait for the drivers to install
5.) Let's find which COM port our device is connected to
Double click ports.bat (This will give us the COM port in which our device is connected we are looking for the Diag port)
Let's run Send_Command.exe (It couldn't connect? Make sure you COM port number is correct it varies)
Code:
Send_Command.exe \\.\COM3
6.) in command prompt Type "id" and press enter (no quotes).
You should get back some text starting with "uid=(0)root gid=(0)root". If not, press CTRL-C, and do step 9 again (the application sometimes doesn't respond on the first command).
7.) in command prompt type
dd if=/data/media/0/system.img bs=8192 seek=55296 count=529920 of=/dev/block/mmcblk0
For other variants then eu815 look here
8.) After a few minutes of sitting, you should get back a "#" prompt. This indicates the process has finished.
Type "LEAVE" (no quotes) and press enter. Your phone should reboot. DONE!!!!!!!!!!!!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
All flashing is on your own risk, i cant help if you get a seagull in your face
It´s rooted?
no, stock at the moment.
No possibility to have a zip file? I do not have windows, but only Mac.. with a zip file for who has the unlocked bootloader is simpler
I tried it on my Sprint variant but it did not work.
emilyrugburn said:
I tried it on my Sprint variant but it did not work.
Click to expand...
Click to collapse
Ofc, its for the H815.
is it possible to change the build.prop in this .img before i flash it into my G4?
Could you post a link to the 10f kdz file?
Where did you get that? Was there another update this week?
speedzioch said:
Where did you get that? Was there another update this week?
Click to expand...
Click to collapse
Look at the date of the OP. This was posted weeks ago.
There are different version upgrade paths for different G4 devices.
For example, my TWN (Taiwan) device latest is 10C. You should really only use the version designed for your own device.
You're right. I didnt check that after being redirected here from rooted img thread. This software misleading stuff provided by LG is confusing. Sorry once again.
LG G4 H815 ®
when I flash the system.img I lose the exfat support for sdcard , I downgraded back to v10E with kdz flash and it fixed sdcard issue.
I will be very thankful to get 10F kdz
I think this way I won't lose exfat support .
Hey nechmadi,
i'm quite sure that any available KDZ is and will be listed here http://storagecow.eu/index.php?dir=Xda/LG+G4/ (link is from this thread). depending on what device you are using (it appears to me that there's a mess with version numbers among carriers etc... i'm using a no-carrier H815 international device) v10d/e* is the latest.
(sais v10d in UI, but v10e in build.prop)
my humble advice, stick with what you have, enjoy your sd card and just wait for future upgrades to see the light of day
edit:
hmm, i see 10f mentioned here.. i didnt get anything 10f related so far... since i'm using a dull no-carrier device i think that's where 'LG updates' arrive first? i'm fairly new to this whole ordeal so take anything i say with a grain of salt - however i'll stick to my previous statement. sit and wait
Use it if you cannot flash with any flash tool (no root needed)
Note: Use this at your own risk! Use it as a last resort!
I'm not responsable for anything, this may not work with yours
Sorry for my poor english. I tested this method with MY bricked LG F320L, no root, no boot, no many partition pop up, partial
downloadMode (just download mode and can't see the USB logo nor S/W update) then can't flash with KDZ/TOT file,with adb mode
recovery when holding pwr and vol+ ( lucky ), with stock recovery but I have to write adb reboot recovery to get it
what you need (sorry, I'm too lazy to put a direct link, I found all of them in xda):
- Install driver for your device
- .kdz file of your model
- WindowsLGFirmwareExtract-1.2.5.0-Release
- Send_Command.exe and ports.bat (ports.bat is optional if you know the port where your device is plunged can be in LG_root.zip)
This methode needs that you can access to downloadmode or partial downloadmode like me (vol+ and plug USB cable)
1- Run WindowsLGFirmwareExtract
. browse your .kdz file with "Open" button
. click to "Extract KDZ" button and wait until finish
. browse the .dz file abd extract it with the appropriat button
. click to "Extract DZ" button and wait until finish
. select all system files and clic Merge system-bin (you will get system.img in another folder and you don't need all system****.bin)
. copy all files in same folder
2- change extension of all files .bin to .img and remove any numbers
example: aboot156.bin => aboot.img / 1-aboot.bin =>aboot.img
3- Push or copy all files to your device. You have to find also the laf.img of your device, sometime it's not in the KDZ file.
Maybe it's optional, but I'm not sure.
Remember the path, for this tuto I'm using adb and push all files to /data/local/tmp/
You can also copy all files with another method
4- Run Ports.bat
Double click ports.bat (This will give us the COM port in which our device is connected we are looking for the Diag port)
keep in mind the COM of \Device\LG*******DIAG*
5- Go to downloadMode
6- Run send_command.exe in command prompt
type: Send_Command.exe \\.\COM3 if COM3 is the port where your device is pluged
wait for #
flash all .img like this, replace NAME by the name of the file ex: aboot.img replace NAME by aboot
dd if=/data/local/tmp/{NAME}.img of=/dev/block/platform/msm_sdcc.1/by-name/{NAME}
ex: dd if=/data/local/tmp/aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
Except for backupGPT.img, I don't know what is it. Maybe in this partition:
dd if=/data/local/tmp/backupGPT.img of=/dev/block/platform/msm_sdcc.1/by-name/gpt
personally , I have not flashed this one
If you have finished type: LEAVE
Flash completed
Thank you guy, your tuto saved my device
santatralalaina said:
Use it if you cannot flash with any flash tool (no root needed)
Note: Use this at your own risk! Use it as a last resort!
I'm not responsable for anything, this may not work with yours
Sorry for my poor english. I tested this method with MY bricked LG F320L, no root, no boot, no many partition pop up, partial
downloadMode (just download mode and can't see the USB logo nor S/W update) then can't flash with KDZ/TOT file,with adb mode
recovery when holding pwr and vol+ ( lucky ), with stock recovery but I have to write adb reboot recovery to get it
what you need (sorry, I'm too lazy to put a direct link, I found all of them in xda):
- Install driver for your device
- .kdz file of your model
- WindowsLGFirmwareExtract-1.2.5.0-Release
- Send_Command.exe and ports.bat (ports.bat is optional if you know the port where your device is plunged can be in LG_root.zip)
This methode needs that you can access to downloadmode or partial downloadmode like me (vol+ and plug USB cable)
1- Run WindowsLGFirmwareExtract
. browse your .kdz file with "Open" button
. click to "Extract KDZ" button and wait until finish
. browse the .dz file abd extract it with the appropriat button
. click to "Extract DZ" button and wait until finish
. select all system files and clic Merge system-bin (you will get system.img in another folder and you don't need all system****.bin)
. copy all files in same folder
2- change extension of all files .bin to .img and remove any numbers
example: aboot156.bin => aboot.img / 1-aboot.bin =>aboot.img
3- Push or copy all files to your device. You have to find also the laf.img of your device, sometime it's not in the KDZ file.
Maybe it's optional, but I'm not sure.
Remember the path, for this tuto I'm using adb and push all files to /data/local/tmp/
You can also copy all files with another method
4- Run Ports.bat
Double click ports.bat (This will give us the COM port in which our device is connected we are looking for the Diag port)
keep in mind the COM of \Device\LG*******DIAG*
5- Go to downloadMode
6- Run send_command.exe in command prompt
type: Send_Command.exe \\.\COM3 if COM3 is the port where your device is pluged
wait for #
flash all .img like this, replace NAME by the name of the file ex: aboot.img replace NAME by aboot
dd if=/data/local/tmp/{NAME}.img of=/dev/block/platform/msm_sdcc.1/by-name/{NAME}
ex: dd if=/data/local/tmp/aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
Except for backupGPT.img, I don't know what is it. Maybe in this partition:
dd if=/data/local/tmp/backupGPT.img of=/dev/block/platform/msm_sdcc.1/by-name/gpt
personally , I have not flashed this one
If you have finished type: LEAVE
Flash completed
Click to expand...
Click to collapse
help please
santatralalaina said:
Use it if you cannot flash with any flash tool (no root needed)
Note: Use this at your own risk! Use it as a last resort!
I'm not responsable for anything, this may not work with yours
Sorry for my poor english. I tested this method with MY bricked LG F320L, no root, no boot, no many partition pop up, partial
downloadMode (just download mode and can't see the USB logo nor S/W update) then can't flash with KDZ/TOT file,with adb mode
recovery when holding pwr and vol+ ( lucky ), with stock recovery but I have to write adb reboot recovery to get it
what you need (sorry, I'm too lazy to put a direct link, I found all of them in xda):
- Install driver for your device
- .kdz file of your model
- WindowsLGFirmwareExtract-1.2.5.0-Release
- Send_Command.exe and ports.bat (ports.bat is optional if you know the port where your device is plunged can be in LG_root.zip)
This methode needs that you can access to downloadmode or partial downloadmode like me (vol+ and plug USB cable)
1- Run WindowsLGFirmwareExtract
. browse your .kdz file with "Open" button
. click to "Extract KDZ" button and wait until finish
. browse the .dz file abd extract it with the appropriat button
. click to "Extract DZ" button and wait until finish
. select all system files and clic Merge system-bin (you will get system.img in another folder and you don't need all system****.bin)
. copy all files in same folder
2- change extension of all files .bin to .img and remove any numbers
example: aboot156.bin => aboot.img / 1-aboot.bin =>aboot.img
3- Push or copy all files to your device. You have to find also the laf.img of your device, sometime it's not in the KDZ file.
Maybe it's optional, but I'm not sure.
Remember the path, for this tuto I'm using adb and push all files to /data/local/tmp/
You can also copy all files with another method
4- Run Ports.bat
Double click ports.bat (This will give us the COM port in which our device is connected we are looking for the Diag port)
keep in mind the COM of \Device\LG*******DIAG*
5- Go to downloadMode
6- Run send_command.exe in command prompt
type: Send_Command.exe \\.\COM3 if COM3 is the port where your device is pluged
wait for #
flash all .img like this, replace NAME by the name of the file ex: aboot.img replace NAME by aboot
dd if=/data/local/tmp/{NAME}.img of=/dev/block/platform/msm_sdcc.1/by-name/{NAME}
ex: dd if=/data/local/tmp/aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
Except for backupGPT.img, I don't know what is it. Maybe in this partition:
dd if=/data/local/tmp/backupGPT.img of=/dev/block/platform/msm_sdcc.1/by-name/gpt
personally , I have not flashed this one
If you have finished type: LEAVE
Flash completed
Click to expand...
Click to collapse
@santatralalaina
I'm in a similar situation like you. No download, fastboot or recovery and phone is not detected by Windows. As u said PARTIAL Download mode only. I'm not very good with adb also. Could you please guide me about force pushing of the .img files please! Where can I get send command.exe and ports.bat? Could you please attach some screen shot of Step:6. Renaming the file and command is bit confusing for me.
sms473 said:
@santatralalaina
I'm in a similar situation like you. No download, fastboot or recovery and phone is not detected by Windows. As u said PARTIAL Download mode only. I'm not very good with adb also. Could you please guide me about force pushing of the .img files please! Where can I get send command.exe and ports.bat? Could you please attach some screen shot of Step:6. Renaming the file and command is bit confusing for me.
Click to expand...
Click to collapse
Hi, Don't panic! Take a deep breath.
Firstly: What is your phone model?
Secondly: What happen when you plug your phone to your PC?
Finaly: What you have did to try unbricking you phone?
santatralalaina said:
Hi, Don't panic! Take a deep breath.
Firstly: What is your phone model?
Secondly: What happen when you plug your phone to your PC?
Finaly: What you have did to try unbricking you phone?
Click to expand...
Click to collapse
Hi..thanks for the reply....My phone is G2 F320L..Korean version with removable battery and SD card....I tried to install a non compatible ROM..got bricked with only fastboot...Then I try to flash aboot.bin..boot.bin..laf.bin..etc files (which I have extracted from the kdz) through fastboot...during flashing my phone was disconnecting and connecting back again...thats where all the problem started I guess. Now I dont have fastboot also. If i connect my phone to PC.. LG logo comes on the phone screen...on PC it try to detect as LGE android MTP devices and try to install the driver of the same. But the driver installation fails eventually.... At windows device manager it show as LGE Android MTP devices with error code 10...and showing connected to port:COM3....If I try to get in to the download mode..it get stuck at the (.............) download page...it is not going to the page with big USB picture...
My thinking is...Since the device manager is showing that it is connected at COM3.....Can I force flash the boot.img, aboot.img, laf.img etc files with "Send command.exe?
At least I can try to force flash right? If it is possible..may be I will be able to enter in to the download mode:fingers-crossed: Right? Where can I get this "Send command.exe" and how it works?
sms473 said:
My thinking is...Since the device manager is showing that it is connected at COM3.....Can I force flash the boot.img, aboot.img, laf.img etc files with "Send command.exe?
At least I can try to force flash right? If it is possible..may be I will be able to enter in to the download mode:fingers-crossed: Right? Where can I get this "Send command.exe" and how it works?
Click to expand...
Click to collapse
Hello,
It was easy to unbrick the fastboot but now... ok, you are stuck in LG LOGO but after no black screen? can you charge you battery? And if you try to go to RecoveryMode, what's happen? do you have multiple partitions and QHSUSB_DLOAD trying to be instaled? It's also easy to unbrick the QHSUSB and if it is the case, don't use send_command to flash manualy your device.
Maybe, you can force flash. You have to find a solution to push all .img files to your device. If you cannot use ADB, try to put the img files to sdcard.
you can found send_command.exe and ports.bat in this zip file, it's an utilities for having root on LG G2 :
LG_Root.zip
you can use all root command with it!
Added to index thread
[INDEX][LG G2] ROMs, Kernels, Guides and more
can this fix demigod crash handler? it has a partial download mode (located in drivers, but LG Flash Tool gets stuck in 4%)
I have a f320k, and because it died (i await u to answer me and tell me if its possible that it will fix it(
i am currently using a nearly dead battery nexus 5.
reply in ur free time
Well, I need help. how do i copy these files to my device? my device is not located in adb. cant i just flash the files from there place in my pc?
hi - I have t mobile d801 .it has boot loop - show lg logo and then the android robot and then lg logo again.
it does enter download mode(but with the 4 blue dots - but in the device manager cant install the drivers.
when the phone is plugged in to computer normally without download mode' it shows lge phone and drivers in device manager.
I tried to flash kdz bit stuck on 60%. it shows on phone download mode - but not show the firmware update logo.
what should I do?? when I d.mode not the regular d.mode - device isn't detected in pc. so I think this is my main problem.
try with srk tools no luck. its says waiting for device..is there any solution? thanks!
foxyfoxyblah said:
can this fix demigod crash handler? it has a partial download mode (located in drivers, but LG Flash Tool gets stuck in 4%)
I have a f320k, and because it died (i await u to answer me and tell me if its possible that it will fix it(
i am currently using a nearly dead battery nexus 5.
reply in ur free time
Click to expand...
Click to collapse
Hi!
As I known, LG G2 is unbrickable
This method is for last resort because I havn't complete documentation about this!
I've tested it with my own LG F320L only
Try to flash with TOT files or LGUP
Try to repair the download mode http://forum.xda-developers.com/showthread.php?t=2706590
Try to force the QHS_USB to appear then use the appropriate tools http://forum.xda-developers.com/lg-g2/general/file-unbrick-qualcomm-9006-qhsusb-t3056800
Try send_commande before shorting testpoint (it's less dangerous IN MY OPINION)
santatralalaina said:
Hi!
As I known, LG G2 is unbrickable
This method is for last resort because I havn't complete documentation about this!
I've tested it with my own LG F320L only
Try to flash with TOT files or LGUP
Try to repair the download mode http://forum.xda-developers.com/showthread.php?t=2706590
Try to force the QHS_USB to appear then use the appropriate tools http://forum.xda-developers.com/lg-g2/general/file-unbrick-qualcomm-9006-qhsusb-t3056800
Try send_commande before shorting testpoint (it's less dangerous IN MY OPINION)
Click to expand...
Click to collapse
I don't have ADB, so most of these i cant do.
im scared of touching the motherboard....
so im not shorting test point.
santatralalaina said:
Use it if you cannot flash with any flash tool (no root needed)
Note: Use this at your own risk! Use it as a last resort!
I'm not responsable for anything, this may not work with yours
Sorry for my poor english. I tested this method with MY bricked LG F320L, no root, no boot, no many partition pop up, partial
downloadMode (just download mode and can't see the USB logo nor S/W update) then can't flash with KDZ/TOT file,with adb mode
recovery when holding pwr and vol+ ( lucky ), with stock recovery but I have to write adb reboot recovery to get it
what you need (sorry, I'm too lazy to put a direct link, I found all of them in xda):
- Install driver for your device
- .kdz file of your model
- WindowsLGFirmwareExtract-1.2.5.0-Release
- Send_Command.exe and ports.bat (ports.bat is optional if you know the port where your device is plunged can be in LG_root.zip)
This methode needs that you can access to downloadmode or partial downloadmode like me (vol+ and plug USB cable)
1- Run WindowsLGFirmwareExtract
. browse your .kdz file with "Open" button
. click to "Extract KDZ" button and wait until finish
. browse the .dz file abd extract it with the appropriat button
. click to "Extract DZ" button and wait until finish
. select all system files and clic Merge system-bin (you will get system.img in another folder and you don't need all system****.bin)
. copy all files in same folder
2- change extension of all files .bin to .img and remove any numbers
example: aboot156.bin => aboot.img / 1-aboot.bin =>aboot.img
3- Push or copy all files to your device. You have to find also the laf.img of your device, sometime it's not in the KDZ file.
Maybe it's optional, but I'm not sure.
Remember the path, for this tuto I'm using adb and push all files to /data/local/tmp/
You can also copy all files with another method
4- Run Ports.bat
Double click ports.bat (This will give us the COM port in which our device is connected we are looking for the Diag port)
keep in mind the COM of \Device\LG*******DIAG*
5- Go to downloadMode
6- Run send_command.exe in command prompt
type: Send_Command.exe \\.\COM3 if COM3 is the port where your device is pluged
wait for #
flash all .img like this, replace NAME by the name of the file ex: aboot.img replace NAME by aboot
dd if=/data/local/tmp/{NAME}.img of=/dev/block/platform/msm_sdcc.1/by-name/{NAME}
ex: dd if=/data/local/tmp/aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
Except for backupGPT.img, I don't know what is it. Maybe in this partition:
dd if=/data/local/tmp/backupGPT.img of=/dev/block/platform/msm_sdcc.1/by-name/gpt
personally , I have not flashed this one
If you have finished type: LEAVE
Flash completed
Click to expand...
Click to collapse
i have flashed wrong firmware ..now my phone have same symptoms like urs with partial download mode and no recovery....but i m unable to push files via adb bcz adb debugging is not active and i m getting error that phone not found.....now what can i dooo...plz plz plzzzz help me
I just wrote and shared my experiences. Forcing the qshusb by shorting the right pins in the motherboard is the only solution if you cannot push the img files to your phone with adb, by sdcard, by MTP or something else
santatralalaina said:
I just wrote and shared my experiences. Forcing the qshusb by shorting the right pins in the motherboard is the only solution if you cannot push the img files to your phone with adb, by sdcard, by MTP or something else
Click to expand...
Click to collapse
and how to do that?
Thank you your topic was helped me to find a solution for my phone lg g3