mods delete this thread
droid.riz said:
Pre-requisites - Drivers Installed,ADB,Fastboot.
Download - cm-12.0-YNG1TAS0YL-bacon-signed-fastboot
Download - user_data(64gb variant) (also you can use cm11s one if you have it place it inside the extracted fastboot files)
-Reboot your device into Fastboot Mode (power + volume up).
-connect your phone to your PC via usb cable.
-Unzip the file you downloaded and put its contents into your fastboot folder (the same folder that you have adb.exe and fastboot.exe located in on your PC).
-Open CMD in that folder (Shift+Right click and open new cmd window here)
-first check the device by entering this command
Code:
fastboot devices
- Enter these commands one by one
Code:
fastboot flash modem NON-HLOS.bin
Code:
fastboot flash recovery recovery.img
Code:
fastboot flash sbl1 sbl1.mbn
Code:
fastboot flash dbi sdi.mbn
Code:
fastboot flash rpm rpm.mbn
Code:
fastboot flash aboot emmc_appsboot.mbn
Code:
fastboot flash tz tz.mbn
Code:
fastboot flash LOGO logo.bin
Code:
fastboot flash oppostanvbk static_nvbk.bin
Code:
fastboot flash boot boot.img
Code:
fastboot flash cache cache.img
Code:
fastboot flash system system.img
Code:
fastboot flash userdata userdata_64G.img
or fastboot flash userdata userdata.img if you have the 16gb model)
P.S This Userdata will wipe ur internal storage you can skip it if you want.
Click to expand...
Click to collapse
What the hell? You plagiarized these instructions directly from my guide thread here:
http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
You've barely even bothered to change the wording.
Transmitted via Bacon
@timmaaa added credits.
droid.riz said:
@timmaaa added credits.
Click to expand...
Click to collapse
Too late for that now, the damage is done. You can't just steal someone else's work and try to pass it off as your own. I worked damn hard on my guide thread, to make sure it's accurate and safe for people to use, I didn't do all that work only to have someone steal it and claim authorship.
Transmitted via Bacon
And about userdata_64G.img from here
timmaaa said:
Too late for that now, the damage is done. You can't just steal someone else's work and try to pass it off as your own. I worked damn hard on my guide thread, to make sure it's accurate and safe for people to use, I didn't do all that work only to have someone steal it and claim authorship.
Transmitted via Bacon
Click to expand...
Click to collapse
okay great ! i am requesting mod to delete the thread.
anagramgenius said:
And about userdata_64G.img from here
Click to expand...
Click to collapse
hahah i never saw your post!
I'll just leave this here:
12. Using the work of others.
"If you are developing something that is based on the work of another Member, you MUST first seek their permission and you must give credit to the member whose work you used. If a dispute occurs about who developed / created a piece of work, first try to settle the matter by private message and NOT in open forum. If this fails, you may then contact a Moderator and provide clear evidence that the work was created by you."
Thread closed
Related
Hi there
I've built Firefox OS for the Galaxy Nexus but I'm struggling to find a way of creating a flashable zip to distribute.
This is my first ROM that I have successfully compiled, but everything seems to be working so I wouldn't mind sharing it with the rest of the internet. Any tips?
Thanks!
ojdon said:
Hi there
I've built Firefox OS for the Galaxy Nexus but I'm struggling to find a way of creating a flashable zip to distribute.
This is my first ROM that I have successfully compiled, but everything seems to be working so I wouldn't mind sharing it with the rest of the internet. Any tips?
Thanks!
Click to expand...
Click to collapse
After building from the B2G directory (the folder from where you run ./config.sh and ./build.sh) you should locate boot.img, userdata.img and system.img and copy them over to a folder, then you can flash using fastboot via:
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash userdata userdata.img
fastboot flash system system.img
fastboot erase cache
fastboot reboot
janjongboom said:
After building from the B2G directory (the folder from where you run ./config.sh and ./build.sh) you should locate boot.img, userdata.img and system.img and copy them over to a folder, then you can flash using fastboot via:
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash userdata userdata.img
fastboot flash system system.img
fastboot erase cache
fastboot reboot
Click to expand...
Click to collapse
Firefox OS in Galaxy Nexus, I want to take a look! Keep us up to date man!
janjongboom said:
After building from the B2G directory (the folder from where you run ./config.sh and ./build.sh) you should locate boot.img, userdata.img and system.img and copy them over to a folder, then you can flash using fastboot via:
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash userdata userdata.img
fastboot flash system system.img
fastboot erase cache
fastboot reboot
Click to expand...
Click to collapse
Ah didn't know this thread had replies so sorry for a bit of a bump. I was kind of after directions on how to create a flashable zip? It's just that I was aiming to avoid end users from using adb and fastboot. Do you know how to create a flashable zip instead?
Thanks for the guidance!
So, you've unlocked your bootloader and are enjoying some rooted goodness on your phone. You then realise you've got an issue with the phone and forgot to make a backup of your stock ROM! Not to fear, this guide is for you! This will reset the phone back to it's out-the-box state, locked bootloader and all, running the latest ZNH2KAS3P0 build so you can return it for RMA/sell it. This also works to go back to CM13.1.2 from Oxygen OS.
It's recommended that you have adb/fastboot in your System Path. This makes it easier to run commands as you don't always have to 'in' your adb/fastboot folder to run the commands. This guide should help you with this but if you don't want to do this, please copy/extract any files into your adb/fastboot folder before continuing...
1. Download the factory image
Cyanogen released the factory image for the OPO but didn't include any batch files to automate the process. I've repackaged the images into two seperate ZIPs:
ZNH2KAS3P0 16GB: DOWNLOAD
md5: be471f6bfc707f86a0af1eb175ec9aad
ZNH2KAS3P0 64GB: DOWNLOAD
md5: c371bc0cb4ef67999d21f5275c5a587b
*** These ZIPs are not flashable so cannot be flashed via TWRP ***
2. Extract the factory image
Using your favourite file extraction program to extract the package to your Desktop (I use 7-ZIP). *** Remember, if you don't have adb/fastboot in your Path, extract the image into your adb/fastboot folder ***
3. Flash the factory image
Once you've unlocked the bootloader, and rebooted the phone, turn the phone off and back on into fastboot mode and reconnect it to the PC. You can now run the flash-all.bat (Windows) or flash-all.sh (Linux) file. These automate the flashing process. Once complete, the phone will reboot.
*** Some users have had issues using the script in Linux so in these cases extract the ZIP file and flash each IMG individually ***
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot flash oppostanvbk static_nvbk.bin
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img (the filename is the same in both ZIPs so make sure you're using the right one for your device)
fastboot reboot
4. Reset the tamper flag/lock the bootloader
There is a flag/bit on the phone that is triggered when you unlock the bootloader and even relocking it won't change this flag back to standard. Luckily, @Mnt-XDA has a script that you can flash which resets these flags so OP/anyone else is none the wiser! To do this, read and follow THIS thread
5. Reboot the phone
Says it all really - you're done!
EddyOS said:
3. Unlock the bootloader on your OPO
Click to expand...
Click to collapse
And why do you need to unlock the bootloader to flash the factory image ????
RalphLauren said:
And why do you need to unlock the bootloader to flash the factory image ????
Click to expand...
Click to collapse
Because you need access to flash the partitions. If the bootloader is locked you cannot do this. If you're device is still locked from day 1, this guide isn't for you as you're already 100% stock and a factory reset will do this job just fine
EDIT: Actually, it's a bit redundant as why would you need this if you're NOT unlocked! I'll edit the OP
EddyOS said:
Because you need access to flash the partitions. If the bootloader is locked you cannot do this. If you're device is still locked from day 1, this guide isn't for you as you're already 100% stock and a factory reset will do this job just fine
EDIT: Actually, it's a bit redundant as why would you need this if you're NOT unlocked! I'll edit the OP
Click to expand...
Click to collapse
Somehow I was thinking that if the signatures match, flashing the FACTORY image would be allowed without unlocking bootloader, hence the question has arisen.
In a way, you are right that if someone is 100% stock, why to bother flash a stock...
But the reasons could be different, like from pure laboratory experiment to the unable to install OTA (for whatever reason) and need to update OS...
May be worth including this work here by Mnt-XDA
If you are returning to stock for selling / returning etc people may want to reset the tamper flag too.
RalphLauren said:
Somehow I was thinking that if the signatures match, flashing the FACTORY image would be allowed without unlocking bootloader, hence the question has arisen.
In a way, you are right that if someone is 100% stock, why to bother flash a stock...
But the reasons could be different, like from pure laboratory experiment to the unable to install OTA (for whatever reason) and need to update OS...
Click to expand...
Click to collapse
I know what you mean, but it's the same with Nexus devices - you cannot flash the image unless the bootloader is unlocked
indesisiv said:
May be worth including this work here by Mnt-XDA
If you are returning to stock for selling / returning etc people may want to reset the tamper flag too.
Click to expand...
Click to collapse
Yeah was looking to add that in at some point, this is still a work in progress as it were...I'll add it in when I get a chance
EDIT: Added
To make this thread more useful for those who aren't familiar with command line, make sure to tell them to:
1) Download the zip file and extract it onto desktop (what a mess)
2) command line cd desktop
3) Enter each one of those command lines
4) Be happy in the end.
lemonspeakers said:
To make this thread more useful for those who aren't familiar with command line, make sure to tell them to:
1) Download the zip file and extract it onto desktop (what a mess)
2) command line cd desktop
3) Enter each one of those command lines
4) Be happy in the end.
Click to expand...
Click to collapse
To be fair, of someone doesn't know how to do that they really shouldn't be here in the first place!
Sent from my HTC One_M8 using XDA Premium 4 mobile app
This should be a sticky!
banjotrold said:
This should be a sticky!
Click to expand...
Click to collapse
I agree! This definitely should be a sticky.
Sent from my One using XDA Premium 4 mobile app
Which one of these files would be the kernel? I am having wifi issues and am wondering if I would be able to reflash and fix it.
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata_64g.img (or userdata.img for 16G version)
fastboot oem lock (if you wish to relock the bootloader. If not, ignore this part)
fastboot reboot
boot.img
EddyOS said:
boot.img
Click to expand...
Click to collapse
Thank you. Any reason why I can't just fast boot the boot.img file only (ala carte)? I am on CM11s rooted with TWRP.
I fastboot flashed the boot.img file sucessfully. It did not fix my wifi problem. So, I tried fastboot flashing the NON-HLOS.bin file. It appears to have an error code. Here is the result.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Kevin work>cd desktop/android-sdk-windows/platform-tools
C:\Users\Kevin work\Desktop\android-sdk-windows\platform-tools>fastboot devices
9f66970a fastboot
C:\Users\Kevin work\Desktop\android-sdk-windows\platform-tools>fastboot flash mo
dem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (56241 KB)...
FAILED (data transfer failure (Too many open files in system))
finished. total time: 0.306s
C:\Users\Kevin work\Desktop\android-sdk-windows\platform-tools>fastboot reboot
< waiting for device >
^C
C:\Users\Kevin work\Desktop\android-sdk-windows\platform-tools>
Any idea as to why it failed?
reboot time
I had done all the steps above but stuck at the boot screen now for 10 minutes is it so post to take this long
Xeon_IV said:
I had done all the steps above but stuck at the boot screen now for 10 minutes is it so post to take this long
Click to expand...
Click to collapse
As you can see from my command prompt script mine did not want to reboot. I ended up unplugging the phone and rebooting.
i get this message on mine
C:\>fastboot flash system system.img
sending 'system' (765700 KB)...
FAILED (remote: data too large)
finished. total time: 0.015s
and will not restore any ideas please
---------- Post added at 10:41 AM ---------- Previous post was at 10:35 AM ----------
Xeon_IV said:
i get this message on mine
C:\>fastboot flash system system.img
sending 'system' (765700 KB)...
FAILED (remote: data too large)
finished. total time: 0.015s
and will not restore any ideas please
Click to expand...
Click to collapse
I just want to get back to stock and quit playing with rooting for my customizations now its dead
Xeon_IV said:
i get this message on mine
C:\>fastboot flash system system.img
sending 'system' (765700 KB)...
FAILED (remote: data too large)
finished. total time: 0.015s
and will not restore any ideas please
---------- Post added at 10:41 AM ---------- Previous post was at 10:35 AM ----------
I just want to get back to stock and quit playing with rooting for my customizations now its dead
Click to expand...
Click to collapse
Is your phone the Chinese OPO or the CM OPO?
CM OPO coming from paranois android
I managed to soft brick my Storm with one of the CM13 updates (both normal boot and recovery just resulted in a black flickering screen), it seems others are having similar issues so here are instructions for restoring your phone to the stock image, this fixed the brick for me.
You need fastboot so download and install the Android SDK if not already present: http://developer.android.com/sdk/installing/index.html
Download and uncompress the stock Cyanogen OS fastboot zip: https://cyngn.com/support
Boot your phone into fastboot mode, (plug in USB then hold down vol+ and power until rebooted, keep holding vol+ until in fastboot)
Start a shell/command prompt on your computer to execute the commands below.
THIS WILL WIPE EVERYTHING!!! - THIS IS A COMPLETE STOCK RESTORATION!!!
Execute these fastboot commands from within the extracted stock zip directory:
Code:
fastboot flash aboot emmc_appsboot.mbn
fastboot flash abootbak emmc_appsboot.mbn
fastboot erase DDR
fastboot flash sbl1 sbl1.mbn
fastboot flash sbl1bak sbl1.mbn
fastboot flash tz tz.mbn
fastboot flash tzbak tz.mbn
fastboot flash hyp hyp.mbn
fastboot flash hypbak hyp.mbn
fastboot flash rpm rpm.mbn
fastboot flash rpmbak rpm.mbn
fastboot flash modem NON-HLOS.bin
fastboot flash cache cache.img
fastboot erase splash
fastboot flash splash splash.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
If the cache command gives an error try continuing anyway.
If you want to try to save your user data skip the userdata command, but no guarantees.
Search the other threads on XDA for instructions on booting or flashing custom recoveries, ROMs, root etc.
I've also bricked my Storm with cm13 update in January . I flashed every img using fastboot and it recovered. i skipped the other files and it still works. Good that someone written tutorial for others. I was planning to write it by myself but you were faster
I have made a simple batch script that executes the commands by itself. You need to unzip and place these 2 files into images direction. It should look like this:
View attachment 3656958
Click on picture to make it bigger
then just connect your device in fastboot mode and open the FLASH-ALL.bat file. Press enter. It will flash all the images. IT WILL ONLY WORK IF FILES WILL BE PLACED LIKE ON THE SCREENSHOT!!
I got blinking brick. I can not go into fastboot
@up Don't connect the usb cord. While it's blinking press and hold vol up+ power for 10 seconds, release power button and it should go into fastboot.
If no, let it fully discharge, and then try volup + power
95% of the time flashing system should do the trick. Otherwise the flashall argument should save you a lot of typing.
aciupapa said:
I've also bricked my Storm with cm13 update in January . I flashed every img using fastboot and it recovered. i skipped the other files and it still works. Good that someone written tutorial for others. I was planning to write it by myself but you were faster
Click to expand...
Click to collapse
my storm is dead, i cant get into recovery or download mode....any advice...i did get it rooted and the recovery...i flash the cm 13 kipper and it went dead...red light comes on when charging or usb connection.
miSAKe said:
I managed to soft brick my Storm with one of the CM13 updates (both normal boot and recovery just resulted in a black flickering screen), it seems others are having similar issues so here are instructions for restoring your phone to the stock image, this fixed the brick for me.
You need fastboot so download and install the Android SDK if not already present: http://developer.android.com/sdk/installing/index.html
Download and uncompress the stock Cyanogen OS fastboot zip: https://cyngn.com/support
Boot your phone into fastboot mode, (plug in USB then hold down vol+ and power until rebooted, keep holding vol+ until in fastboot)
Start a shell/command prompt on your computer to execute the commands below.
THIS WILL WIPE EVERYTHING!!! - THIS IS A COMPLETE STOCK RESTORATION!!!
Execute these fastboot commands from within the extracted stock zip directory:
Code:
fastboot flash aboot emmc_appsboot.mbn
fastboot flash abootbak emmc_appsboot.mbn
fastboot erase DDR
fastboot flash sbl1 sbl1.mbn
fastboot flash sbl1bak sbl1.mbn
fastboot flash tz tz.mbn
fastboot flash tzbak tz.mbn
fastboot flash hyp hyp.mbn
fastboot flash hypbak hyp.mbn
fastboot flash rpm rpm.mbn
fastboot flash rpmbak rpm.mbn
fastboot flash modem NON-HLOS.bin
fastboot flash cache cache.img
fastboot erase splash
fastboot flash splash splash.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
If the cache command gives an error try continuing anyway.
If you want to try to save your user data skip the userdata command, but no guarantees.
Search the other threads on XDA for instructions on booting or flashing custom recoveries, ROMs, root etc.
Click to expand...
Click to collapse
Perfect, thanks.
Would have worked FIRST time if I'd read your instructions properly, instead it worked the SECOND time. Important to download "the stock Cyanogen OS fastboot zip" from the Cyngn support page - there are two similar looking files and obviously I picked the wrong one first.
Thanks again.
miSAKe said:
Hello,
As you know, cyngn.com is unavailable. i need kipper files, specially original recovery.img
do you know any alive link(s)? or can you upload/send to me?
thanks very much
Click to expand...
Click to collapse
ftabashir said:
miSAKe said:
Hello,
As you know, cyngn.com is unavailable. i need kipper files, specially original recovery.img
do you know any alive link(s)? or can you upload/send to me?
thanks very much
Click to expand...
Click to collapse
here
https://www.androidfilehost.com/?w=files&flid=59917
Click to expand...
Click to collapse
ghertas said:
ftabashir said:
here
https://www.androidfilehost.com/?w=files&flid=59917
Click to expand...
Click to collapse
thanks. but this is the whole ROM. i downloaded it and couldn't find "recovery.img". how can i find original recovery for kipper (wileyfox storm)?
Click to expand...
Click to collapse
ftabashir said:
ghertas said:
thanks. but this is the whole ROM. i downloaded it and couldn't find "recovery.img". how can i find original recovery for kipper (wileyfox storm)?
Click to expand...
Click to collapse
cm-13.1.2
instal via ADB Fastboot
youtube help you to how instal
recovery.
https://www.androidfilehost.com/?fid=24727376692773052
full rom
https://www.androidfilehost.com/?fid=24727369092694607
Click to expand...
Click to collapse
ghertas said:
ftabashir said:
cm-13.1.2
instal via ADB Fastboot
youtube help you to how instal
recovery.
https://www.androidfilehost.com/?fid=24727376692773052
full rom
https://www.androidfilehost.com/?fid=24727369092694607
Click to expand...
Click to collapse
Thanks. but I downloaded recovery from this link.
Then i tried to run "fastboot flash recovery cm-13.1.2-ZNH2KAS3NA-kipper-boot-debuggable-6c1a30b194.img"
but it said:
OEM locked device can't boot unsigned image. Do you want to continue?
Yes
No
I pressed no and it said:
target reported max download size of 268435456 bytes
sending 'recovery' (20866 KB)...
OKAY [ 0.791s]
writing 'recovery'...
FAILED (remote: Image could brick the device. Flashing canceled.)
finished. total time: 2.129s
I ran the command again and this time I chose Yes and it said:
target reported max download size of 268435456 bytes
sending 'recovery' (20866 KB)...
OKAY [ 0.783s]
writing 'recovery'...
OKAY [ 16.962s]
finished. total time: 17.751s
but as it said, when i try to boot recovery i saw this message: OEM locked device can't boot unsigned image. oem unlock or flash signed boot image.
I need a signed recovery, but i couldn't find such recovery anywher. Please help me
Also when i try to run fastboot oem unlock it says that: FAILED (remote: oem unlock is not allowed)
So the only solution would be installing a signed recovery.
Note: 3day ago i installed a custom recovery without oem unlock. now my device stops at boot animation and i cant boot into android. also i can't boot into recovery because oem is locked and recovery is not signed. I need a signed recovery.
Click to expand...
Click to collapse
miSAKe said:
I managed to soft brick my Storm with one of the CM13 updates (both normal boot and recovery just resulted in a black flickering screen), it seems others are having similar issues so here are instructions for restoring your phone to the stock image, this fixed the brick for me.
You need fastboot so download and install the Android SDK if not already present: http://developer.android.com/sdk/installing/index.html
Download and uncompress the stock Cyanogen OS fastboot zip: https://cyngn.com/support
Boot your phone into fastboot mode, (plug in USB then hold down vol+ and power until rebooted, keep holding vol+ until in fastboot)
Start a shell/command prompt on your computer to execute the commands below.
THIS WILL WIPE EVERYTHING!!! - THIS IS A COMPLETE STOCK RESTORATION!!!
Execute these fastboot commands from within the extracted stock zip directory:
Code:
fastboot flash aboot emmc_appsboot.mbn
fastboot flash abootbak emmc_appsboot.mbn
fastboot erase DDR
fastboot flash sbl1 sbl1.mbn
fastboot flash sbl1bak sbl1.mbn
fastboot flash tz tz.mbn
fastboot flash tzbak tz.mbn
fastboot flash hyp hyp.mbn
fastboot flash hypbak hyp.mbn
fastboot flash rpm rpm.mbn
fastboot flash rpmbak rpm.mbn
fastboot flash modem NON-HLOS.bin
fastboot flash cache cache.img
fastboot erase splash
fastboot flash splash splash.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
If the cache command gives an error try continuing anyway.
If you want to try to save your user data skip the userdata command, but no guarantees.
Search the other threads on XDA for instructions on booting or flashing custom recoveries, ROMs, root etc.
Click to expand...
Click to collapse
How did you enter fastboot without enabling usb debugging/developer option?
This method is for Kitkat, and lollipop.
Now i'm going to introduce how to unbrick your G3 Cat.6.
First, you need to download these files.
1. TOT,KDZ files
http://forum.xda-developers.com/lg-g3/general/lg-g3-cat-6-f460-kdz-tot-download-t3470250
2. Windows LG Firmware Extract
http://forum.xda-developers.com/showthread.php?t=2600575
3. LG United Driver
https://drive.google.com/file/d/0B2UHjr8om-8QT1RFME9UOHBEaTQ/view?usp=sharing
4. Debrick.img (You should download all)
http://1drv.ms/1LnSioU
5. Win32Diskimager
https://sourceforge.net/projects/win32diskimager/?source=directory
6. LG Flash Tool 2014
https://drive.google.com/file/d/0B1NxfQr9J2JUZnFQbGlaaU11Mmc/view?usp=sharing
7. ADB Fastboot
https://drive.google.com/file/d/0B1NxfQr9J2JUWExQdnk2RVlENXc/view?usp=sharing
Second, Put debrick.img files into Micro SD Card!
Extract the Zip file, and you can see
5 Debrick files.
and open the 'Win32DiskImager' Program.
and select the debrick file. and write.
After, the progress finished,
insert Micro SD card into G3 Cat.6
And Turn On your phone.
(Or Press Power + down button)
If you can see ADB Download mode, you can go to next method!
And If you can't see nothing on screen,
Try flash another file.
(like debrick 220-> debrick200 -> debrick180->...)
But if you can't see nothing (if you flashed these 5 files)
then you can't unbrick your G3 Right now...
Third, Extract your KDZ Files!
Open 'WindowsLGFirmwareExtract' Program,
and extract your KDZ files.
then you can see .dz file.
now go back to program,
Select Dz file, and Extract DZ files.
(Make sure you should check all boxes!)
And you can see .bin files.
Finished!
Fourth, Flash .bin Files into G3 Cat.6 (with using ADB)
Move ADB Fastboot files and Extracted Files into one file...
Like this.
http://imgur.com/a/8rRzV
Click SHIFT+M2 (Right mouse)
And click 'Open Command Window Here' on folder.
Then you can see the CMD.
Now Connect USB to your Phone.
and type 'adb devices'
after you can see demon started sucessfully, move on to next method.
NOW you need to replace your .bin files.
First, erase files in your phone,
and Flash all .bin files.
After you typed 'adb devices'
Type these all commands
fastboot erase aboot
fastboot erase BackupGPT
fastboot erase boot
fastboot erase factory
fastboot erase laf
fastboot erase misc
fastboot erase modem
fastboot erase persist
fastboot erase PrimaryGPT
fastboot erase recovery
fastboot erase rpm
fastboot erase sbl1
fastboot erase sdi
fastboot erase sec
fastboot erase tz
If you finished, type these commands
fastboot flash aboot aboot.bin
fastboot flash BackupGPT BackupGPT.bin
fastboot flash boot boot.bin
fastboot flash factory factory.bin
fastboot flash laf laf.bin
fastboot flash misc misc.bin
fastboot flash modem modem.bin
fastboot flash persist persist.bin
fastboot flash PrimaryGPT PrimaryGPT.bin
fastboot flash recovery recovery.bin
fastboot flash rpm rpm.bin
fastboot flash sbl1 sbl1.bin
fastboot flash sdi sdi.bin
fastboot flash sec sec.bin
fastboot flash tz tz.bin
IF YOU FINISHED TYPE/FLASH THESE FILES,
REBOOT YOUR PHONE (must eject the micro sd card)
AND IF YOU CAN SEE LG LOGO,
YOUR PHONE CAN ALIVE
Now you must do this last method.
Final, Flash KDZ File.
http://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
If you sucessed to flash KDZ file...
now you can see your phone is alive...!
congratulation!
Q&A
Q. Why theres no debrick files for marshmallow?
A. I'm sorry, i only found debrick files for Kitkat,Lollipop.
(Now I'm Trying to find debrick for MM)
Q. Why i can't see my phone in ADB?
A. If you can't see, try to install LG United Driver.
Q. Your Grammar is SO BAD.
A. Sorry. I'm from South Korea... and that's why I CAN'T SPEAK ENGLISH WELL (Somebody Help Me..)
Q. Your explanation is SO BAD.
A. I'm sorry. I can mistake, and it's hard to write this method.
If you find Something WRONG, please Help me!
I'll Appreciate to your help!
Thanks For reading!
Asking...Hoping...
Vega_Kangmin said:
This method is for Kitkat, and lollipop.
Now i'm going to introduce how to unbrick your G3 Cat.6.
First, you need to download these files.
1. TOT,KDZ files
http://forum.xda-developers.com/lg-g3/general/lg-g3-cat-6-f460-kdz-tot-download-t3470250
2. Windows LG Firmware Extract
http://forum.xda-developers.com/showthread.php?t=2600575
3. LG United Driver
https://drive.google.com/file/d/0B2UHjr8om-8QT1RFME9UOHBEaTQ/view?usp=sharing
4. Debrick.img (You should download all)
http://1drv.ms/1LnSioU
5. Win32Diskimager
https://sourceforge.net/projects/win32diskimager/?source=directory
6. LG Flash Tool 2014
https://drive.google.com/file/d/0B1NxfQr9J2JUZnFQbGlaaU11Mmc/view?usp=sharing
7. ADB Fastboot
https://drive.google.com/file/d/0B1NxfQr9J2JUWExQdnk2RVlENXc/view?usp=sharing
Second, Put debrick.img files into Micro SD Card!
Extract the Zip file, and you can see
5 Debrick files.
and open the 'Win32DiskImager' Program.
and select the debrick file. and write.
After, the progress finished,
insert Micro SD card into G3 Cat.6
And Turn On your phone.
(Or Press Power + down button)
If you can see ADB Download mode, you can go to next method!
And If you can't see nothing on screen,
Try flash another file.
(like debrick 220-> debrick200 -> debrick180->...)
But if you can't see nothing (if you flashed these 5 files)
then you can't unbrick your G3 Right now...
Third, Extract your KDZ Files!
Open 'WindowsLGFirmwareExtract' Program,
and extract your KDZ files.
then you can see .dz file.
now go back to program,
Select Dz file, and Extract DZ files.
(Make sure you should check all boxes!)
And you can see .bin files.
Finished!
Fourth, Flash .bin Files into G3 Cat.6 (with using ADB)
Move ADB Fastboot files and Extracted Files into one file...
Like this.
http://imgur.com/a/8rRzV
Click SHIFT+M2 (Right mouse)
And click 'Open Command Window Here' on folder.
Then you can see the CMD.
Now Connect USB to your Phone.
and type 'adb devices'
after you can see demon started sucessfully, move on to next method.
NOW you need to replace your .bin files.
First, erase files in your phone,
and Flash all .bin files.
After you typed 'adb devices'
Type these all commands
fastboot erase aboot
fastboot erase BackupGPT
fastboot erase boot
fastboot erase factory
fastboot erase laf
fastboot erase misc
fastboot erase modem
fastboot erase persist
fastboot erase PrimaryGPT
fastboot erase recovery
fastboot erase rpm
fastboot erase sbl1
fastboot erase sdi
fastboot erase sec
fastboot erase tz
If you finished, type these commands
fastboot flash aboot aboot.bin
fastboot flash BackupGPT BackupGPT.bin
fastboot flash boot boot.bin
fastboot flash factory factory.bin
fastboot flash laf laf.bin
fastboot flash misc misc.bin
fastboot flash modem modem.bin
fastboot flash persist persist.bin
fastboot flash PrimaryGPT PrimaryGPT.bin
fastboot flash recovery recovery.bin
fastboot flash rpm rpm.bin
fastboot flash sbl1 sbl1.bin
fastboot flash sdi sdi.bin
fastboot flash sec sec.bin
fastboot flash tz tz.bin
IF YOU FINISHED TYPE/FLASH THESE FILES,
REBOOT YOUR PHONE (must eject the micro sd card)
AND IF YOU CAN SEE LG LOGO,
YOUR PHONE CAN ALIVE
Now you must do this last method.
Final, Flash KDZ File.
http://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
If you sucessed to flash KDZ file...
now you can see your phone is alive...!
congratulation!
Q&A
Q. Why theres no debrick files for marshmallow?
A. I'm sorry, i only found debrick files for Kitkat,Lollipop.
(Now I'm Trying to find debrick for MM)
Q. Why i can't see my phone in ADB?
A. If you can't see, try to install LG United Driver.
Q. Your Grammar is SO BAD.
A. Sorry. I'm from South Korea... and that's why I CAN'T SPEAK ENGLISH WELL (Somebody Help Me..)
Q. Your explanation is SO BAD.
A. I'm sorry. I can mistake, and it's hard to write this method.
If you find Something WRONG, please Help me!
I'll Appreciate to your help!
Thanks For reading!
Click to expand...
Click to collapse
Sir vega, have you found debrick image for Marshmallow.
t0m0y0143 said:
Sir vega, have you found debrick image for Marshmallow.
Click to expand...
Click to collapse
No, not yet.
I'm still find that files.
But it's gonna hard to find.
Or Someone (or me) need to make Derrick files, but that's very hard.
Thanks
Vega_Kangmin said:
No, not yet.
I'm still find that files.
But it's gonna hard to find.
Or Someone (or me) need to make Derrick files, but that's very hard.
Click to expand...
Click to collapse
Okay. If ever you find something please PM me? Thank You Very Much.
Asking
Vega_Kangmin said:
No, not yet.
I'm still find that files.
But it's gonna hard to find.
Or Someone (or me) need to make Derrick files, but that's very hard.
Click to expand...
Click to collapse
Can you please search it in here Sir Vega Kangmin? I cannot enter it as I cannot understand korean.
bbs.sonyue.com
Hi, thanks for sharing this info
t0m0y0143 said:
Can you please search it in here Sir Vega Kangmin? I cannot enter it as I cannot understand korean.
bbs.sonyue.com
Click to expand...
Click to collapse
that site is from China.. not korea...
Vega_Kangmin said:
that site is from China.. not korea...
Click to expand...
Click to collapse
Oh sorry, I did not know Forgive my ignorance.
Does anyone have Nougat debrick images? LOL
BTW, im guessing that with the correct kdz and tot files, this would also work in the d855 right?
And finally, my phone bricked when i was updating the firmware to stock, the furthest it got was 38% with the lg flash tool, so will the phone need 4.4.2 or 7.1 debrick img?
BoardDiag2014
someone developed new boarddiag which can detect our broken LG G3 Cat6 F460 S K L
but price is high for me he asks 60 dollar for the new BoardDiag
http://www.lgbbs.com.cn/forum.php?mod=viewthread&tid=1107
i hope someone can put it with low price we can pay we are just a single users not a repairing shops
I have successfully repaired my F460S with debirck img MM! Although my phone run lollipop before
Thanks
Hi everybody...I'm in trouble with my Yotaphone YD201.
I done format data with TWRP.
Then, I run these commands with Win10 for clean flash of RU144:
Code:
fastboot flash boot {Directory_firmware/boot.img}
fastboot flash -S 512M system {Directory_firmware/system.img}
fastboot flash recovery {Directory_firmware/recovery.img}
fastboot flash cache {Directory_firmware/cache.img}
fastboot flash modem {Directory_firmware/radio/NON-HLOS.bin}
fastboot flash sbl1 {Directory_firmware/radio/sbl1.mbn}
fastboot flash rpm {Directory_firmware/radio/rpm.mbn}
fastboot flash tz {Directory_firmware/radio/tz.mbn}
fastboot flash userdata {Directory_firmware/userdata.img}
fastboot flash aboot {Directory_file__emmc_appsboot.mbn}
fastboot reboot
After the last one, Screen gone black and nothing appends...
Now, adb and fastboot can't contact with Yota ("adb devices" give "<waiting for devices") .
Now, In Win devices, I can find " QHSUSB_BULK".
After some search, I found out that my phone is in a recovery mode of Qualcomm. Does anybody know how to unblock it? Problably I need of specific driver to contact with this phone. Thanks so much!
P.S.: do not esitate to contact me if my english is not clear =)
How about a method like this https://forums.oneplus.net/threads/solution-bricked-oneplus-one-recovery.306306/ but use Yotaphone files instead?
evilracer123 said:
How about a method like this (...) but use Yotaphone files instead?
Click to expand...
Click to collapse
This discussion uses Msm8974DownloadTool.exe from the directory of ColorOS but the wire connection does not work (the file is no longer available, from Mega).
Also, not sure if I can use Msm8974DownloadTool.exe with Yotaphone. Alternatively, what can I use?