Related
IT IS POSSSSIIIIIBBBBLLLLLE!
I am rewriting this tutorial from RDS www.yuplaygod.com member's post
This is only meant for users who had rooted their device, in lollipop, have cwm or twrp recovery installed. IF not rooted find guides for it. (Hint: Google it)
I suggest to not use fastboot for flashing roms... It may brick you device (I meant hard brick)
So here is what we are going to do!
STEPS (VERY SIMPLE)
1) Download Back_to_cm11-signed by Abhiram.zip https://drive.google.com/file/d/0B4etFrzyEA01UklKR3N5T2JYeGc/view?usp=sharing
2)Download recovery-yu.img https://drive.google.com/file/d/0B4etFrzyEA01d2VGRXNuY2I1MGs/view?usp=sharing
3)Copy Back_to_cm11-signed by Abhiram.zip to SDCARD
4)Open recovery and flash it
5)Open fastboot mode.
6)Connect to your computer and flash recovery-yu.img
7)Open recovery by pressing "vol+"+"vol-"+"pwr"
8)Flash stock rom zip. Go to this guide to get it http://forum.xda-developers.com/yureka/orig-development/rom-t3042384
9) Rock with it!.
********FOR THOSE WHO ARE NOT GOOD WITH FASTBOOT**********
So yureka is something different. So you have to specify the device id for the fastboot to find it.
Install adb-setup.1****.exe https://drive.google.com/file/d/0B4etFrzyEA01SE9NTVNRWTl4Y0E/view?usp=sharing
Open CMD
Type fastboot -i 0x1ebf devices
If any device is detected you r good to go
Close CMD
Open the place where you have downloaded recovery-yu.img
By pressing shift, right click the folder (in which you have downloaded recovery-yu.img) click open command window here
and type fastboot -i 0x1ebf boot recovery-yu.img
That's it
Have you tried that and didn't face any hardbricks?
Yes
I risked my own device to prove that. Go ahead 10000% sure that this will work. Because my device did not brick at all
Please hit tanks if you got it working! It is working..
Abhiram Shibu said:
I risked my own device to prove that. Go ahead 10000% sure that this will work. Because my device did not brick at all
Please hit tanks if you got it working! It is working..
Click to expand...
Click to collapse
tank you
The OP suggest not to use fastboot mode as it may hard brick device & the steps tht follow are based on fastboot option... I'm confused, Is it safe to use fastboot mode thn?
ujilraj their is nothing to be confused. You can use fastboot mode. But if you flash system.img and data.img via fastboot, which has different partition styles, then you will end up with hard bricked phone... That's why!
Flashing recovery is very safe! GO for it!
I have tested it
For further clarification i'm asking this, pardon me...
First i boot into CM12 recovery & flash Back_to_cm11-signed by Abhiram.zip
Then,
Enter fastboot mode & install recovery-yu.img tht belongs to CM11.
Then,
I boot into CM11 recovery & flash any CM11 rom... Rite???
A bit confuse
Abhiram Shibu said:
I suggest to not use fastboot for flashing roms... It may brick you device (I meant hard brick)
That's it
Click to expand...
Click to collapse
I am a bit confuse here. Could you explain to me what is the different between:
Code:
package_extract_file("firmware-update/tz.mbn", "/dev/block/bootdevice/by-name/tz");
package_extract_file("firmware-update/hyp.mbn", "/dev/block/bootdevice/by-name/hyp");
package_extract_file("firmware-update/sbl1.mbn", "/dev/block/bootdevice/by-name/sbl1");
package_extract_file("firmware-update/rpm.mbn", "/dev/block/bootdevice/by-name/rpm");
package_extract_file("firmware-update/emmc_appsboot.mbn", "/dev/block/bootdevice/by-name/aboot");
package_extract_file("firmware-update/NON-HLOS.bin", "/dev/block/bootdevice/by-name/modem");
AND
Code:
fastboot -i 0x1ebf flash tz tz.mbn
fastboot -i 0x1ebf flash hyp hyp.mbn
fastboot -i 0x1ebf flash sbl1 sbl1.mbn
fastboot -i 0x1ebf flash rpm rpm.mbn
fastboot -i 0x1ebf flash aboot emmc_appsboot.mbn
fastboot -i 0x1ebf flash modem NON-HLOS.bin
ujilraj said:
For further clarification i'm asking this, pardon me...
First i boot into CM12 recovery & flash Back_to_cm11-signed by Abhiram.zip
Then,
Enter fastboot mode & install recovery-yu.img tht belongs to CM11.
Then,
I boot into CM11 recovery & flash any CM11 rom... Rite???
Click to expand...
Click to collapse
Ujilraj That is absolutely correct ! You got it man.:good:
tirta.agung said:
I am a bit confuse here. Could you explain to me what is the different between:
Code:
package_extract_file("firmware-update/tz.mbn", "/dev/block/bootdevice/by-name/tz");
package_extract_file("firmware-update/hyp.mbn", "/dev/block/bootdevice/by-name/hyp");
package_extract_file("firmware-update/sbl1.mbn", "/dev/block/bootdevice/by-name/sbl1");
package_extract_file("firmware-update/rpm.mbn", "/dev/block/bootdevice/by-name/rpm");
package_extract_file("firmware-update/emmc_appsboot.mbn", "/dev/block/bootdevice/by-name/aboot");
package_extract_file("firmware-update/NON-HLOS.bin", "/dev/block/bootdevice/by-name/modem");
AND
Code:
fastboot -i 0x1ebf flash tz tz.mbn
fastboot -i 0x1ebf flash hyp hyp.mbn
fastboot -i 0x1ebf flash sbl1 sbl1.mbn
fastboot -i 0x1ebf flash rpm rpm.mbn
fastboot -i 0x1ebf flash aboot emmc_appsboot.mbn
fastboot -i 0x1ebf flash modem NON-HLOS.bin
Click to expand...
Click to collapse
That is good question, I appreciate that.
So.... I got to say is that. When you use "fastboot -i 0x1ebf flash aboot emmc_appsboot.mbn " This will format the desired partition and put files there. If the partition table is modified then more likely it would not flash but erase the whole partion. That will lead to a hard bricked phone. The procedure you told will work.
But zip just copies these files to that location..... Sounds great, i think.
IN my opinion ONLY FASTBOOT CAN CAUSE HARD BRICK which is the greatest issue faced by yureka users.
If you managed to flash a 32bit rom in recovery without flashing the zip I have given you, the chances are you end up into a boot loop or Soft Brick. But do the same with fastboot you will end up with Hard bricked phone!
Zip method is always safe. I mean the safest!
Flashing recovery via fast boot don't cause anu Hard Bricks. I tried in my phone, i ended up with Soft Brick.... I repaired it by using unsafe method flashed ROM via fast boot. Luckily there was no partition mismatch. I could have flashed recovery and flashed my zip file!
So my advise please don't use fastboot. It is too dangerous for your phone ( As most of them can't even contact the customer care ) I don't want you to end up like this....
Note: Most of them flash system.img and data.img first .... don't do that... If you r so sure flash the files you mentioned first. As they contain boot loader(Priorety), Modem, Partiton Style, Touch Drivers.......
Good Luck! :good:
I hope this information helped you
Please hit thanks if I helped you in any manner!
Abhiram Shibu said:
That is good question, I appreciate that.
So.... I got to say is that. When you use "fastboot -i 0x1ebf flash aboot emmc_appsboot.mbn " This will format the desired partition and put files there. If the partition table is modified then more likely it would not flash but erase the whole partion. That will lead to a hard bricked phone. The procedure you told will work.
But zip just copies these files to that location..... Sounds great, i think.
IN my opinion ONLY FASTBOOT CAN CAUSE HARD BRICK which is the greatest issue faced by yureka users.
If you managed to flash a 32bit rom in recovery without flashing the zip I have given you, the chances are you end up into a boot loop or Soft Brick. But do the same with fastboot you will end up with Hard bricked phone!
Zip method is always safe. I mean the safest!
Flashing recovery via fast boot don't cause anu Hard Bricks. I tried in my phone, i ended up with Soft Brick.... I repaired it by using unsafe method flashed ROM via fast boot. Luckily there was no partition mismatch. I could have flashed recovery and flashed my zip file!
So my advise please don't use fastboot. It is too dangerous for your phone ( As most of them can't even contact the customer care ) I don't want you to end up like this....
Note: Most of them flash system.img and data.img first .... don't do that... If you r so sure flash the files you mentioned first. As they contain boot loader(Priorety), Modem, Partiton Style, Touch Drivers.......
Good Luck! :good:
I hope this information helped you
Please hit thanks if I helped you in any manner!
Click to expand...
Click to collapse
Rather than flashing your zip via recovery, can I not use fastboot to flash the following in the order mentioned:
modem, sbl1, aboot, rpm, tz, hyp, recovery. The files that would be used are a part of cm11 fastboot package. After flashing all of these, boot to recovery and then flash the cm11 zip. I'll be essentially doing the same like you did. But I'll be using fastboot to flash firmware specific stuff. I strongly believe that these would not cause the infamous brick.
Thanks,
Sanjay
Abhiram Shibu said:
That is good question, I appreciate that.
So.... I got to say is that. When you use "fastboot -i 0x1ebf flash aboot emmc_appsboot.mbn " This will format the desired partition and put files there. If the partition table is modified then more likely it would not flash but erase the whole partion. That will lead to a hard bricked phone. The procedure you told will work.
But zip just copies these files to that location..... Sounds great, i think.
IN my opinion ONLY FASTBOOT CAN CAUSE HARD BRICK which is the greatest issue faced by yureka users.
If you managed to flash a 32bit rom in recovery without flashing the zip I have given you, the chances are you end up into a boot loop or Soft Brick. But do the same with fastboot you will end up with Hard bricked phone!
Zip method is always safe. I mean the safest!
Flashing recovery via fast boot don't cause anu Hard Bricks. I tried in my phone, i ended up with Soft Brick.... I repaired it by using unsafe method flashed ROM via fast boot. Luckily there was no partition mismatch. I could have flashed recovery and flashed my zip file!
So my advise please don't use fastboot. It is too dangerous for your phone ( As most of them can't even contact the customer care ) I don't want you to end up like this....
Note: Most of them flash system.img and data.img first .... don't do that... If you r so sure flash the files you mentioned first. As they contain boot loader(Priorety), Modem, Partiton Style, Touch Drivers.......
Good Luck! :good:
I hope this information helped you
Please hit thanks if I helped you in any manner!
Click to expand...
Click to collapse
2 questions :-
1. ) As you said that do not use the fastboot method to flash kitkat rom. My question is, Can i use fastboot method to flash the lollipop 64bit zip file (that is basically the same OTA update file), using same method which was used to flash kitkat (by extracting the zip file contents to a common folder containing flash-all.bat, if u remmeber?). Basically i want to know a method to re-flash lollipop 64 bit , if any1 knows?
2.) Once i suceed to get kitkat rom back , from the lollipop 64 bit. Can i use FASTBOOT method in FUTURE flashes to flash kitkat based custom roms or should i permanently DISCONTINUE flashing through fastboot, even after getting kitkat rom back by your method?
thanks in advance .... :good:
---------- Post added at 12:51 AM ---------- Previous post was at 12:41 AM ----------
Also i want to know. is there something like 32bit and 64 bit recovery. I hv heard that flashing incoatiable recovery can also lead to hard brick.
which recovery to flash when.??
could be great if any1 has positive information and can guide....
coolboyforeva said:
2 questions :-
1. ) As you said that do not use the fastboot method to flash kitkat rom. My question is, Can i use fastboot method to flash the lollipop 64bit zip file (that is basically the same OTA update file), using same method which was used to flash kitkat (by extracting the zip file contents to a common folder containing flash-all.bat, if u remmeber?). Basically i want to know a method to re-flash lollipop 64 bit , if any1 knows?
2.) Once i suceed to get kitkat rom back , from the lollipop 64 bit. Can i use FASTBOOT method in FUTURE flashes to flash kitkat based custom roms or should i permanently DISCONTINUE flashing through fastboot, even after getting kitkat rom back by your method?
thanks in advance .... :good:
---------- Post added at 12:51 AM ---------- Previous post was at 12:41 AM ----------
Also i want to know. is there something like 32bit and 64 bit recovery. I hv heard that flashing incoatiable recovery can also lead to hard brick.
which recovery to flash when.??
could be great if any1 has positive information and can guide....
Click to expand...
Click to collapse
There is nothing to be confused. there are 32 bit and 64 bit recoveries. Flashing wrong recovery will only softbrick your phone. I did it ones accidentally
32bit recovery https://drive.google.com/open?id=0B4etFrzyEA01d2VGRXNuY2I1MGs&authuser=0
64bit recovery https://drive.google.com/open?id=0B4etFrzyEA01NnZBWHcxWlVHTW8&authuser=0
If you want to flash lollipop then download lollipop flash-able zip file click here for zip file
There are some good working fastboot upgrade packages. So if you have one of them ( Tried it yourself to upgrade and worked earlier) Then use that package it will work!. Flashing with zip file with recovery reduces risk!:good:
Abhiram Shibu said:
There is nothing to be confused. there are 32 bit and 64 bit recoveries. Flashing wrong recovery will only softbrick your phone. I did it ones accidentally
32bit recovery https://drive.google.com/open?id=0B4etFrzyEA01d2VGRXNuY2I1MGs&authuser=0
64bit recovery https://drive.google.com/open?id=0B4etFrzyEA01NnZBWHcxWlVHTW8&authuser=0
If you want to flash lollipop then download lollipop flash-able zip file click here for zip file
There are some good working fastboot upgrade packages. So if you have one of them ( Tried it yourself to upgrade and worked earlier) Then use that package it will work!. Flashing with zip file with recovery reduces risk!:good:
Click to expand...
Click to collapse
ok . m not gonna use fastboot. But how will i flash signed lollipop zip file on custom recovery and unlocked bootloader. it wont boot. I would need an unsigned lollipop 64 bit zip file or rather a locked bootloader + stock 64 bit recovery . Any link for stock 64 bit recovery ? is above link for stock or custom recovery?
coolboyforeva said:
ok . m not gonna use fastboot. But how will i flash signed lollipop zip file on custom recovery and unlocked bootloader. it wont boot. I would need an unsigned lollipop 64 bit zip file or rather a locked bootloader + stock 64 bit recovery . Any link for stock 64 bit recovery ? is above link for stock or custom recovery?
Click to expand...
Click to collapse
Yes it will boot.
Link above is for custom CWM recovery.
Warning ******** Boring Story Ahead*********
So i purchased my yureka from Amazon. When i got it, I unlocked boot loader, installed cwm recovery right away. When the lollipop upgrade showed up I tried to download it via system upgrade. It downloaded but wont flash because of a custom recovery. So... I downloaded a signed zip file from xda attachment which i gave you. I cleared cache and tried installing the zip file.... It actually works.
Why it worked?
Stock rom looks for signed zips and it should be signed my their developer. But custom recoveries installs any zip file which is flashable regardless they are signed or unsigned. The only thing it looks for is the scripts and device compactability.
So try flashing the lollipop signed zip file. It will surely work...
So... What will the zip file do?
It will wipe system, modem, recovery etc exept data. Resize them and copy files in.
So ... What will you end up with.
Obviously,
A locked bootloader ( Which when unlocked wipes data)
A stock old cyanogen recovery.
Non rooted CM12.....
So this means that if you want to be a power user you have to start form beginning. So... consider taking a nandroid backup before you upgrade.....
STEPS TO BACKUP DATA ON CYANOGEN 11
So... Abhiram I cant find my backup on sdcard
answer to this question is very simple. You know that your sdcard and app memory are same. So they created a new folder 0 and mounted as your sdcard.
So... How do you get that out....
There are 2 methords
Common step boot into recovery and connect your mobile to your computer. Make sure that ADB drivers are installed
Methord 1
Type
"adb shell
cp -r /sdcard/clockworkmod/ /sdcard/0/android/
adb reboot"
So after the phone rebooted. Open file manage ( anyone ) Browse into android folder in your sdcard, you will find your backup there. If you cant find your whole backup , the chances are you r running out of memory.
Methord 2
type
"adb pull /sdcard/clockworkmod/ %UserProfile%/documents/backup_from_nandroid/ "
Your backup can be found in c:/users/<your user name here>/documents/backup_from_nandroid/
So that is it....
So when you unlock boot loader you can copy this backup into your phone by....
1) Copy backup to adb folder
2) Type adb push <Directory name> /sdcard/clockworkmod/
Then do a advanced restore. Select data and restore
done!
Abhiram Shibu said:
Yes it will boot.
Link above is for custom CWM recovery.
Warning ******** Boring Story Ahead*********
So i purchased my yureka from Amazon. When i got it, I unlocked boot loader, installed cwm recovery right away. When the lollipop upgrade showed up I tried to download it via system upgrade. It downloaded but wont flash because of a custom recovery. So... I downloaded a signed zip file from xda attachment which i gave you. I cleared cache and tried installing the zip file.... It actually works.
Why it worked?
Stock rom looks for signed zips and it should be signed my their developer. But custom recoveries installs any zip file which is flashable regardless they are signed or unsigned. The only thing it looks for is the scripts and device compactability.
So try flashing the lollipop signed zip file. It will surely work...
So... What will the zip file do?
It will wipe system, modem, recovery etc exept data. Resize them and copy files in.
So ... What will you end up with.
Obviously,
A locked bootloader ( Which when unlocked wipes data)
A stock old cyanogen recovery.
Non rooted CM12.....
So this means that if you want to be a power user you have to start form beginning. So... consider taking a nandroid backup before you upgrade.....
STEPS TO BACKUP DATA ON CYANOGEN 11
So... Abhiram I cant find my backup on sdcard
answer to this question is very simple. You know that your sdcard and app memory are same. So they created a new folder 0 and mounted as your sdcard.
So... How do you get that out....
There are 2 methords
Common step boot into recovery and connect your mobile to your computer. Make sure that ADB drivers are installed
Methord 1
Type
"adb shell
cp -r /sdcard/cyanogenmod/ /sdcard/0/android/
adb reboot"
So after the phone rebooted. Open file manage ( anyone ) Browse into android folder in your sdcard, you will find your backup there. If you cant find your whole backup , the chances are you r running out of memory.
Methord 2
type
"adb pull /sdcard/clockworkmod/ %UserProfile%/documents/backup_from_nandroid/ "
Your backup can be found in c:/users/<your user name here>/documents/backup_from_nandroid/
So that is it....
So when you unlock boot loader you can copy this backup into your phone by....
1) Copy backup to adb folder
2) Type adb push <Directory name> /sdcard/clockworkmod/
Then do a advanced restore. Select data and restore
done!
Click to expand...
Click to collapse
Ok.. I want to revert back to kitkat. i wont be using fastboot to flash rom(only to flash recovery image). Is there anything else which i should avoid and keep in mind in order to prevent hard brick?? please suggest
coolboyforeva said:
Ok.. I want to revert back to kitkat. i wont be using fastboot to flash rom(only to flash recovery image). Is there anything else which i should avoid and keep in mind in order to prevent hard brick?? please suggest
Click to expand...
Click to collapse
Tips to avoid hardbrick.
Don't flash ROM via fastboot
Don't Format partition using fast boot
You can flash boot and recovery via fastboot.
You can do anything in recovery.
Advice backup ROM before you install kernel, or any zip files. That will help you if you soft brick your phone.
Hit thanks if I help you in anyway till now.
On reading the OP's comments another doubt occurred, Do i need to unlock bootloader all the time when switching between KK & LP? (Will the internal SD memory gets wiped all the time... Do i need to backup every data on the internal SD memory onto PC before switching from KK to LP & vice-versa?)
Yes, but in case of upgrading and unlocking boot loader
Nice Question
When you downgrade from CM12 to CM11 your data will be safe. Unlocking boot loader will not do anything with your data:angel:
But When you are upgrading from CM11 to CM12 your data will be also safe, but the problem occurs when you try to unlock boot loader It will wipe all of your data.:crying:
When we unlock boot loader in kitkat CM11 by using command fastboot -i 0x1ebf oem unlock
It doesn't ask for any confirmations.
But in case of CM12 when you unlock boot loader by using the same command, before wiping data, it asks for confirmation. ie It tells to push vol+ to confirm or push vol - to stop.
If you see like this. Fastboot is going to erase your sdcard.
Its a good practice to backup your data when you r playing with your phones firmware, It will help you get back your memorable moments, favorite music etc.
If you have an otg cable. Keep a pendrive for backup
So concluding in unlocking CM11 no data loss unlocking in CM12 there is data loss.
Good luck:good:
One more doubt, suppose i'm on KK & want to upgrade to some custom CM12.x rom, do i need to go through the process of installing stock cm12 all the time, or do u suggest any other simple way to directly do the same?
Anyone know how I can unbrick my phone? cuz now the device manager only shows my phone as Qualcomm HS-USB Qloader 9008(com4). My phone when power on will still have black screen and can't go into download mode or recovery, just black screen even tho I know it's on. I really need help if anyone knows.
I'm thinking about trying this method (http://forum.xda-developers.com/show....php?t=2660566) to try and boot from sdcard so that I can go into download mode and reflash stock, but I need someone with a LG G3 S/Beat d722k to run this and the output will be a debrick image I can use: busybox dd if=/dev/block/mmcblk0 of=/sdcard/backup.bin bs=1M count=200 if it does not work for me then I'll ask to change the last number (count=) to something larger and try it. I really need help.
This is the only guide I found that maybe could solve your problem:
Guide
.tot file
Hy nexus friends,
I need help from someone with a 791F 32GB. I dont know if a 790 or a 16gb version is identical.
It would be great if someone with a rooted device can make a backup for me of the bootloader bin files.
aboot, sbl1, rpm, tz, sdi, sbl1b, tzb, rpmb, abootb, misc, laf, persist.
I flashed the hammerhead bootloader and stuck at 9008 mode.
It will be ver great if someone could help me.
Some partition apps could make a backup or with the dd command.
If i fet a solution, i would post it here. At the moment i had the device and the tools that i flashed for test a nexus 5 sbl. So write is possible.
Thanks for help guys
Where can I see if my phone is 791F?
i have the US Nexus 5X 32GB. Tell me what to do and I'll get you what you need.
tacofromhell said:
Where can I see if my phone is 791F?
Click to expand...
Click to collapse
Model number on the phone box and I believe in the bootloader screen: turn off phone then hold volume down and power.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Model number on the phone box and I believe in the bootloader screen: turn off phone then hold volume down and power.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Ok. Just rebooted into bootloader and under "Variant" it says LGH791 but no F, sorry
Thx for your help.
You can backup the partitions with some partition backup apps or with dd.
If you look with a file explorer in /dev/block/platform/soc.0/f9824900.sdhci/by-name/XXXXX , XXXX there are the partiton names.
If you want to copy with adb, make adb shell, su, and then:
dd if= /dev/block/platform/soc.0/f9824900.sdhci/by-name/cmnlib of=sdcard/cmnlib.img
Around 36 partitons are in the MM build. System, cache, userdata are not needed..
konsolen said:
Thx for your help.
You can backup the partitions with some partition backup apps or with dd.
If you look with a file explorer in /dev/block/platform/soc.0/f9824900.sdhci/by-name/XXXXX , XXXX there are the partiton names.
If you want to copy with adb, make adb shell, su, and then:
dd if= /dev/block/platform/soc.0/f9824900.sdhci/by-name/cmnlib of=sdcard/cmnlib.img
Around 36 partitons are in the MM build. System, cache, userdata are not needed..
Click to expand...
Click to collapse
Have you found a solution to get booting again? Been searching and tried multiple methods to repair my boot image on the H791 I own.
I have worked with another XDAer who extracted and now have the bootimage files from several stock H791 files available. They include the GPT from the stock image MDA89E and the boot image files from bootloader-bullhead-bhz10i.img bootloader-bullhead-bhz10k.img and bootloader-bullhead-bhz10m.img. Let me know if you still need these. I see 11 files in the boot image. During some testing I flashed over the sbl1 on my device and lost the ability do anything but go into QUSB DL mode 9008 as well.
As I am writing this I am now wondering if there is a separate set of SBL etc. files for the International variant? We may need to extract from the 791 tot file available the needed files if we do not have another method of obtaining them. Let me know if you have found a workable way to flash the needed boot images in place. Thanks.
nate0 said:
Have you found a solution to get booting again? Been searching and tried multiple methods to repair my boot image on the H791 I own.
I have worked with another XDAer who extracted and now have the bootimage files from several stock H791 files available. They include the GPT from the stock image MDA89E and the boot image files from bootloader-bullhead-bhz10i.img bootloader-bullhead-bhz10k.img and bootloader-bullhead-bhz10m.img. Let me know if you still need these. I see 11 files in the boot image. During some testing I flashed over the sbl1 on my device and lost the ability do anything but go into QUSB DL mode 9008 as well.
As I am writing this I am now wondering if there is a separate set of SBL etc. files for the International variant? We may need to extract from the 791 tot file available the needed files if we do not have another method of obtaining them. Let me know if you have found a workable way to flash the needed boot images in place. Thanks.
Click to expand...
Click to collapse
I'm on the same boat , hope you have something to boot it up
It's been more than 3 weeks, my 5X just brick itself . And LG doesn't support 5X in my country . I'm very very hoping you will find solution.
Apayah said:
I'm on the same boat , hope you have something to boot it up
It's been more than 3 weeks, my 5X just brick itself . And LG doesn't support 5X in my country . I'm very very hoping you will find solution.
Click to expand...
Click to collapse
I think the only way from my perspective so far is to manually flash the needed QComm/boot image/boot loader files with something that can interface with the phone. I am pretty sure I know a method to manually do this but need the flash programmer that works with this device to accomplish. Or if there is a way to add MSM8992 support to the BoardDiag tool, that would work...I have not given up, just have not had a whole lot of time to work on this the past 2 days.
nate0 said:
I think the only way from my perspective so far is to manually flash the needed QComm/boot image/boot loader files with something that can interface with the phone. I am pretty sure I know a method to manually do this but need the flash programmer that works with this device to accomplish. Or if there is a way to add MSM8992 support to the BoardDiag tool, that would work...I have not given up, just have not had a whole lot of time to work on this the past 2 days.
Click to expand...
Click to collapse
I see boardiag for n5 , please don't give up ?.
And i see blank flash file for N6
Try to connect the usb cable with the pressed vol up button. Normaly the lg download screen should pop up.
Its possible then to flash a tot file with the lg up tool.
But i found only one tot file around the i net.
It will be flashed but hang in the bootscreen.
A org. tot or kdz file were great or a solution to create such a file.
konsolen said:
Try to connect the usb cable with the pressed vol up button. Normaly the lg download screen should pop up.
Its possible then to flash a tot file with the lg up tool.
But i found only one tot file around the i net.
It will be flashed but hang in the bootscreen.
A org. tot or kdz file were great or a solution to create such a file.
Click to expand...
Click to collapse
I can go to download mode but it can't hang , the screen turns to black Immediately. I'm just waiting for another way .
Apayah said:
I can go to download mode but it can't hang , the screen turns to black Immediately. I'm just waiting for another way .
Click to expand...
Click to collapse
Yes. The FW download screen is not an option here. Seems those of us currently needing a solution or method is do to the phone being in QC emergency mode only. I can see my phone in device manager only as with the QC HUSB 9008 drivers.
nate0 said:
Yes. The FW download screen is not an option here. Seems those of us currently needing a solution or method is do to the phone being in QC emergency mode only. I can see my phone in device manager only as with the QC HUSB 9008 drivers.
Click to expand...
Click to collapse
Yes it same , i got that to.
So what is blank flash? on N6 thread .
链接：https://pan.baidu.com/s/1TmQ9jmdAym2NYt_YGyt2Cg 引脚：g5cg
Hello,
I tried to install TWRP unsuccessfully on my D852. In the process, I removed my laf.img. The strange thing is that I see two files on my phone, one in the internal storage size 16.5MB and one on the SDcard size 32MB. How do I know which one to install? Is there a difference between them? If I install the wrong one, will my phone still work?
I am running the Telus Lollipop 5.0.1 from storagecow, if this could help you giving me the right answer.
Thank you,
Update - I was able to extract laf_393216.bin from the Telus KDZ (TELUS D85220F_00.kdz) I installed on my phone. The size of this file is 19MB.
What do I do with a BIN file? How to I install it on the phone?
Thank you,
Hello, me, again,
I can't believe no one knows how to do this. Please help! I can't do anything on my phone, luckily it still boots to LP 5.0.1.
laf.img was removed using ADB. I backed it up before removing it and now I can't seem to be able to restore it because the phone doesn't go to download mode.
It was very easy to remove and I can't find a way or someone to help me restore it...
I tried to enter Download Mode by powering the phone off, pressing Vol+ and plugging USB cable.
I get a black screen with the following:
[500] Fastboot mode started
[590] -Reset-
[590 -Portcharge-
[710] Fastboot: processing commands
Anyone knows how to get into download mode from here?
Thank you,
U must restore your phone from 9008 Qualcomm DLoad.
Update - I was able to restore my laf.img and boot.img using adb.
After that, I got download mode working and was able to complete flashing original Rogers MM on my phone. Perfect!!!
LG V30 Recovery UnBrick Zips
So as some of you are aware, I released a h932 rom that soft bricked a few devices. well in the process of that I (with @runningnak3d help) figured out a way to unbrick those devices. As long as you have TWRP or download mode with ADB then you can unbrick. These zips here are NOT meant to be flashed to just flash. These zips are for those people that have a non 9008 brick only! DO NOT FLASH THESE ZIPS OR RUN THESE COMMANDS FOR ANY REASON EXCEPT FOR A NON 9008 BRICK! DO NOT FLASH OR RUN THIS COMMANDS BECAUSE YOU HAVE A BOOTLOOP! ONLY FOLLOW THIS THREAD FOR NON 9008 BRICKS! PLEASE BE SMART!
Now on to the good stuff.......
Only download and flash the zip made for your original device model. Do NOT flash whatever your converted too. for example i have a ls998 converted to us998. I would flash the ls998 THEN convert to us998 later on...
NOTE: After flashing the unbrick zip for your model youll need to have a rom zip on your sdcard or internal storage. You'll need to flash that rom zip (aosp or stock) in order to boot
Recovery Zips
H932_Dump.zip [Download]
See Post 2 [Post 2] for what to do if you do NOT have TWRP
See Post 3 [Post 3] if you want to contribute to this thread and backup your device models EMMC for others to be able to recover. ( NO PERSONAL DATA WILL BE USED )
Don´t forget to hit the thanks-button if you like this zip! :good:
You want to help me with a [donation?] Not asking for it, I have fun doing this for you, but feel free...
#RESERVED1
For those of you that dont have TWRP but have download mode and ADB, you have a second option of just manually running the commands to unbrick.
Step 1 - Make sure you have ADB installed on your computer
Step 2 - Download the zip for your orginal device model
Step 3 - Extract the zip and place all the files into a folder called dump
Step 4 - ADB push the folder to your device ( adb push <file path to dump> /sdcard/ )
Step 5 - Open the update-binary file inside the extracted zip inside META-INF/com/google/android
Step 6 - Run all the make_ext4fs commands in adb shell (adb shell make_ext4fs <partition name>
Step 7 - Run all the write_raw_image commands in adb shell ( NOTE : remove $INSTALLER in your commands and replace write_raw_image with dd ) ( EXAMPLE : adb shell dd if=/sdcard/<partition name> of=/dev/block/bootdevice/by-name/<partition name> )
Step 8 - Once this is done you'll need to reboot and profit.
If any questions about this guide please feel free to tag me and ask and i will help you
thank you
#RESERVED2
Make sure you have enough space on internal storage before flashing the backup zip. You'll likely need 10GB+. this new zip now checks free storage on internal and aborts if not enough. it also now creates a flashable restore zip so now youll have the restore zip internal storage/dump/backup.zip and you can flash this zip when you get a non 9008 brick
Dumps can be done with aosp or custom roms but please try to backup only stock roms if possible. Thanks Everyone!
EDIT: NEW ZIP HAS BEEN ATTACHED.
#RESERVED3
#RESERVED4
I'll be releasing the flashable zip to dump your partitions later today!
Added a flashable backup zip. please flash in twrp and then upload Backup.zip from internal storage Dump folder somewhere and send link here. ill make a restore zip so we can make the v30 almost unbrickable :good:
LG V30 bricked
Hi!
I need your help please, if there is any help... (I hope this is the right thread for my topic)
I got my LG V30 a few days ago (on 8.April 2019, EU version, H930). I schwitched it on and made the initial setup (wifi, region, ...). And the "normal" system update. (I think, it was sec.update from 1.1.2019).
After 2 days I wanted to root the phone. My mistake ....
The steps in short:
1. adb and fastboot installed (on my laptop with Windows 10). I copied SR5-SuperSU-v2.82-SR5-20171001224502.zip into the root of the phone (no sd card in the phone).
2. with adb and fastboot (and LG develpoer account + imiei & co) I managed to unlock with my unlock.bin
3. phone restarted. Since then I see an additional start screen "Lock the bootloader." for 1-2 sec at every start/restart. After this the boot process continues with the standard screen : LG V30 ThinQ powered by Andriod
4. restarting the phone with volume up + power buttons did not funtcion (I gave 4-5 times a try). It never ever succeed for me on this phone. Maybe this is an important point...
5. restarting into the new feature of the phone worked out only with adb reboot bootloader
6. I flashed TWRP in Win10's cmd with fastboot flash recovery recovery.img (I renamed TWRP-3.2.3-7-DataIMG.img to recovery.img)
7. restarting the phone with volume up + power buttons still did not funtcion (I gave it a try 4-5 times)
8. I found this hint : fastboot boot recovery.img. It did the job, TWRP was started (Version 3.2.3-7 DataIMG).
9. I made a backup in TWRP, copied the BACKUP directrory to my laptop. (maybe the only smart thing of me...)
10. TWRP started with fastboot boot recovery.img again
11. in TWRP -> intsall -> SR5-SuperSU-v2.82-SR5-20171001224502.zip selected and the 'restart' option checked.
12. I have seen, that SuRoot....zip was succesful installed (without any errors) and the phone rebooted automatically (it was connected via USB cable to the laptop, but it should not be the problem)
13. since then nothing happens, but the boot screen: for short time the screen with bootlocker text, then only the black screen with LG v30 ThinQ powered by Andriod
I can not boot in to TWRP with volume up + power buttons. This never worked for me. I tried it 20-30 times... :crying:
With volume up + power buttons I can restart, but only the screen with bootlocker text, then only the black screen with LG v30 ThinQ powered by Andriod appiers.
My laptop does not recognise the phone on USB.
Before I destroy the phone with a hammer, any hints?
sicci75 said:
Hi!
I need your help please, if there is any help... (I hope this is the right thread for my topic)
I got my LG V30 a few days ago (on 8.April 2019, EU version, H930). I schwitched it on and made the initial setup (wifi, region, ...). And the "normal" system update. (I think, it was sec.update from 1.1.2019).
After 2 days I wanted to root the phone. My mistake ....
The steps in short:
1. adb and fastboot installed (on my laptop with Windows 10). I copied SR5-SuperSU-v2.82-SR5-20171001224502.zip into the root of the phone (no sd card in the phone).
2. with adb and fastboot (and LG develpoer account + imiei & co) I managed to unlock with my unlock.bin
3. phone restarted. Since then I see an additional start screen "Lock the bootloader." for 1-2 sec at every start/restart. After this the boot process continues with the standard screen : LG V30 ThinQ powered by Andriod
4. restarting the phone with volume up + power buttons did not funtcion (I gave 4-5 times a try). It never ever succeed for me on this phone. Maybe this is an important point...
5. restarting into the new feature of the phone worked out only with adb reboot bootloader
6. I flashed TWRP in Win10's cmd with fastboot flash recovery recovery.img (I renamed TWRP-3.2.3-7-DataIMG.img to recovery.img)
7. restarting the phone with volume up + power buttons still did not funtcion (I gave it a try 4-5 times)
8. I found this hint : fastboot boot recovery.img. It did the job, TWRP was started (Version 3.2.3-7 DataIMG).
9. I made a backup in TWRP, copied the BACKUP directrory to my laptop. (maybe the only smart thing of me...)
10. TWRP started with fastboot boot recovery.img again
11. in TWRP -> intsall -> SR5-SuperSU-v2.82-SR5-20171001224502.zip selected and the 'restart' option checked.
12. I have seen, that SuRoot....zip was succesful installed (without any errors) and the phone rebooted automatically (it was connected via USB cable to the laptop, but it should not be the problem)
13. since then nothing happens, but the boot screen: for short time the screen with bootlocker text, then only the black screen with LG v30 ThinQ powered by Andriod
I can not boot in to TWRP with volume up + power buttons. This never worked for me. I tried it 20-30 times... :crying:
With volume up + power buttons I can restart, but only the screen with bootlocker text, then only the black screen with LG v30 ThinQ powered by Andriod appiers.
My laptop does not recognise the phone on USB.
Before I destroy the phone with a hammer, any hints?
Click to expand...
Click to collapse
Your mistake was not following any of the rooting Instructions in this V30 forum. If you did, you know we don't use SuperSu, we use Magisk. That's probably what messed up your phone.
I understand you obtained an "official" bootloader unlock code from LG for your H930 -- which is not necessary now for almost a year with the WTF exploit -- but you still need to follow the rooting instructions guide.
The unlocked bootloader warning screen is normal. Ignore it, it's just a harmless annoyance. You would have learned that if you read the instructions.
Try manually going into Download mode (power off completely, then hold volume up button while plugging in USB cable) -- if you can, then reflashing most recent full stock H930 KDZ via Dev Patched LGUP in "Refurbish" mode. Dev Patched LGUP is attached to post #1 of that thread.
If/when you recover, your bootloader should still be unlocked, but you'll have install TWRP again and this time use Magisk. Read the WTF instructions, but you can skip the bootloader part, as you've already done that. You can start with Section 6. Read those instructions on a web browser, not an app.
ChazzMatt said:
Try manually going into Download mode (power off completely, then hold volume up button while plugging in USB cable) -- if you can, then reflashing most recent full stock H930 KDZ via Dev Patched LGUP in "Refurbish" mode. Dev Patched LGUP is attached to post #1 of that thread.
Click to expand...
Click to collapse
Thank you for your quick reply!
I'm learning this forum threads, intstuctions and flashing... And I am now preparing for the unbricking.
After installing LGUP, what dev zip files do I need?
LGUP+V30DLL_PATCHED.zip
LGUP_common_DLL_V30_ALLVARIANTS.zip
LGUP_common_OREO.zip
I can take this kdz: H93021w_00_OPEN_EU_OP_0121.kdz, right?
sicci75 said:
Thank you for your quick reply!
I'm learning this forum threads, intstuctions and flashing... And I am now preparing for the unbricking.
After installing LGUP, what dev zip files do I need?
LGUP+V30DLL_PATCHED.zip
LGUP_common_DLL_V30_ALLVARIANTS.zip
LGUP_common_OREO.zip
I can take this kdz: H93021w_00_OPEN_EU_OP_0121.kdz, right?
Click to expand...
Click to collapse
Are you able to get into Download mode?
You want the "patched" version, but be sure to read the installation instructions.
Yes, you can use that KDZ.
If for some reason your bootloader is not still unlocked, you can run your code again.
ChazzMatt said:
Are you able to get into Download mode?
Click to expand...
Click to collapse
Yessss!!After reading very focused the guidelines you mentioned, it was everything fine.
Thank you!
sicci75 said:
Yessss!!After reading very focused the guidelines you mentioned, it was everything fine.
Thank you!
Click to expand...
Click to collapse
Glad to help.
Sent via open market LG US998 V30/V30+
So just uploaded a new zip in post 3. this new zip now checks for free space and will abort if theres not enough to create the backup and flashable restore zip. need at least 10GB in Internal Storage. the zip will now create automatically a flashable restore zip :good: i designed this around the v30 but in theory it should be able to work on all qualcomm devices and maybe even some other SoCs as well. but this has not been tested on other devices. ive fully tested this on my ls998 and everything works great! Enjoy!
john, did i ever tell you, that i like your work and efforts? good man! :good:
Lg v30 h932 brick
Hello, I need your help.
My LG V30 H932 phone is left as a BRICK after installing an erroneous kdz, it does not enter download mode or emergency mode, is there any way to revive it?
JohnFawkes said:
#RESERVED1
For those of you that dont have TWRP but have download mode and ADB, you have a second option of just manually running the commands to unbrick.
Step 1 - Make sure you have ADB installed on your computer
Step 2 - Download the zip for your orginal device model
Step 3 - Extract the zip and place all the files into a folder called dump
Step 4 - ADB push the folder to your device ( adb push <file path to dump> /sdcard/ )
Step 5 - Open the update-binary file inside the extracted zip inside META-INF/com/google/android
Step 6 - Run all the make_ext4fs commands in adb shell (adb shell make_ext4fs <partition name>
Step 7 - Run all the write_raw_image commands in adb shell ( NOTE : remove $INSTALLER in your commands and replace write_raw_image with dd ) ( EXAMPLE : adb shell dd if=/sdcard/<partition name> of=/dev/block/bootdevice/by-name/<partition name> )
Step 8 - Once this is done you'll need to reboot and profit.
If any questions about this guide please feel free to tag me and ask and i will help you
thank you
Click to expand...
Click to collapse
---------- Post added at 03:26 AM ---------- Previous post was at 03:23 AM ----------
My LG V30 H932 phone is left as a BRICK after installing an erroneous kdz, it does not enter download mode or emergency mode, is there any way to revive it?
It was a big mistake and I don't know what to do, my phone does nothing, totally dead
JohnFawkes said:
#RESERVED1
For those of you that dont have TWRP but have download mode and ADB, you have a second option of just manually running the commands to unbrick.
Step 1 - Make sure you have ADB installed on your computer
Step 2 - Download the zip for your orginal device model
Step 3 - Extract the zip and place all the files into a folder called dump
Step 4 - ADB push the folder to your device ( adb push <file path to dump> /sdcard/ )
Step 5 - Open the update-binary file inside the extracted zip inside META-INF/com/google/android
Step 6 - Run all the make_ext4fs commands in adb shell (adb shell make_ext4fs <partition name>
Step 7 - Run all the write_raw_image commands in adb shell ( NOTE : remove $INSTALLER in your commands and replace write_raw_image with dd ) ( EXAMPLE : adb shell dd if=/sdcard/<partition name> of=/dev/block/bootdevice/by-name/<partition name> )
Step 8 - Once this is done you'll need to reboot and profit.
If any questions about this guide please feel free to tag me and ask and i will help you
thank you
Click to expand...
Click to collapse
---------- Post added at 04:04 AM ---------- Previous post was at 03:26 AM ----------
Hello, I need your help.
My LG V30 H932 phone is left as a BRICK after installing an erroneous kdz, it does not enter download mode or emergency mode, is there any way to revive it?!!!
JohnFawkes said:
LG V30 Recovery UnBrick Zips
So as some of you are aware, I released a h932 rom that soft bricked a few devices. well in the process of that I (with @runningnak3d help) figured out a way to unbrick those devices. As long as you have TWRP or download mode with ADB then you can unbrick. These zips here are NOT meant to be flashed to just flash. These zips are for those people that have a non 9008 brick only! DO NOT FLASH THESE ZIPS OR RUN THESE COMMANDS FOR ANY REASON EXCEPT FOR A NON 9008 BRICK! DO NOT FLASH OR RUN THIS COMMANDS BECAUSE YOU HAVE A BOOTLOOP! ONLY FOLLOW THIS THREAD FOR NON 9008 BRICKS! PLEASE BE SMART!
Now on to the good stuff.......
Only download and flash the zip made for your original device model. Do NOT flash whatever your converted too. for example i have a ls998 converted to us998. I would flash the ls998 THEN convert to us998 later on...
NOTE: After flashing the unbrick zip for your model youll need to have a rom zip on your sdcard or internal storage. You'll need to flash that rom zip (aosp or stock) in order to boot
Recovery Zips
H932_Dump.zip [Download]
See Post 2 [Post 2] for what to do if you do NOT have TWRP
See Post 3 [Post 3] if you want to contribute to this thread and backup your device models EMMC for others to be able to recover. ( NO PERSONAL DATA WILL BE USED )
Don´t forget to hit the thanks-button if you like this zip! :good:
You want to help me with a [donation?] Not asking for it, I have fun doing this for you, but feel free...
Click to expand...
Click to collapse
robertojha said:
Hello, I need your help.
My LG V30 H932 phone is left as a BRICK after installing an erroneous kdz, it does not enter download mode or emergency mode, is there any way to revive it?
Click to expand...
Click to collapse
You tried to cross flashed another variant stock KDZ over your T-Mobile H932? Not sure why you would do that, but normally that results in 9008 brick which needs remote viewer Octoplus help to recover.
Lg v30 h932 brick
I was following a guide and installed a kdz different from the original of my phone, and now I have no download mode or emergency mode, it's totally a brick,...
ChazzMatt said:
You tried to cross flashed another variant stock KDZ over your T-Mobile H932? Not sure why you would do that, but normally that results in 9008 brick which needs remote viewer Octoplus help to recover.
Click to expand...
Click to collapse
ChazzMatt said:
You tried to cross flashed another variant stock KDZ over your T-Mobile H932? Not sure why you would do that, but normally that results in 9008 brick which needs remote viewer Octoplus help to recover.
Click to expand...
Click to collapse
From what I know, there is no fire hose for the H932.
Sent from my LG-H932 using XDA Labs
---------- Post added at 02:40 PM ---------- Previous post was at 02:37 PM ----------
robertojha said:
I was following a guide and installed a kdz different from the original of my phone, and now I have no download mode or emergency mode, it's totally a brick,...
Click to expand...
Click to collapse
I don't think think there is any guide that says to do this. If there was, @ChazzMatt would have gotten it shut down.
Sent from my LG-H932 using XDA Labs
BROKEN1981 said:
From what I know, there is no fire hose for the H932.
Click to expand...
Click to collapse
Ah, yeah you're right.
---------- Post added at 03:33 PM ---------- Previous post was at 02:43 PM ----------
BROKEN1981 said:
I don't think think there is any guide that says to do this. If there was, @ChazzMatt would have gotten it shut down.
Click to expand...
Click to collapse
The T-Mobile root guide does say flash the LAF partition of the H933. But only the LAF partition. Some people do not pay attention and flash the entire H933 kdz over the T-Mobile H932 and brick their phone.
Just had a guy in the Frankenstein thread who said he followed instructions. I didn't believe, told him so, and asked him to tell me step-by-step what he did... Turns out rather than flash US998 Nougat, then Master Reset, then Oreo of choice -- he flashed 20f (Oreo), Master Reset, 20g Oreo.
I asked him why he did that. He said US998 20f was Nougat. That's like saying a banana is an apple. "10" is Nougat, "20" is Oreo. Plus, in my instructions I have specific download links to all requisite firmware, which he ignored.
He said he downloaded KDZ from LG-Firmwares website who told him US998 20f was Nougat -- which they didn't. But even if they did, who cares? You're following MY instructions, so use my download links. Once he downloaded actual Nougat from my download link -- hey that worked!
Also use the Dev Patched LGUP which I recommend. Some guy over the telegram thread said he was following my instructions, but used Uppercut. Of course that's going to fail. None of my instruction mention Uppercut and never will because it doesn't work on Oreo or later and conflicts with Dev Patched LGUP. I always include the specific version of Dev Patched LGUP you should be using. (The Dev for Uppercut is amazing, but it just doesn't work on our phones past Nougat. If it's NOT in the Instructions, don't use it.)
This isn't a recipe where you can substitute your own ingredients.
You need to read carefully and pay attention.
I'm happy to help -- but while some people's problems are quite preventable, once occurred may not be fixable.