I have backup starting 150MB of sda partition.. get it from link, use class 10 SDCARD 16GB atleast i have tested, format sdcard with FAT32, open win32 disk imager, write unbrick img to sdcard. Remove battery, put sdcard in your dead xt1766, put battery, press volume down and insert usb cable.. you will see fastboot menu.. flash latest xt1766 from Motorola firmware.
That's all folks!
Link to debrick img..
https://mega.nz/#!NmwjWJ7a!shXGk8euTf000ehVsveRy0ZPVj3tyDxRV15m7NS_7dk
Hi Thanks For This Detailed How-To I Hope This Will Help A Lot Of People Since The Blank-Flash Dont Work.
---------- Post added at 04:33 PM ---------- Previous post was at 04:29 PM ----------
And How This Work The Sd Card Is Used Just To Bring Fastboot And Flash To the EMMC or Flash To The SD-Card And Use The System on it ?
Salik Iqbal said:
I have backup starting 150MB of sda partition.. get it from link, use class 10 SDCARD 16GB atleast i have tested, format sdcard with FAT32, open win32 disk imager, write unbrick img to sdcard. Remove battery, put sdcard in your dead xt1766, put battery, press volume down and insert usb cable.. you will see fastboot menu.. flash latest xt1766 from Motorola firmware.
That's all folks!
Link to debrick img..
https://mega.nz/#!NmwjWJ7a!shXGk8euTf000ehVsveRy0ZPVj3tyDxRV15m7NS_7dk
Click to expand...
Click to collapse
This is good stuff. Nice to know there's a working unbrick method for the xt1766. Nice work OP.
ozmage said:
Hi Thanks For This Detailed How-To I Hope This Will Help A Lot Of People Since The Blank-Flash Dont Work.
---------- Post added at 04:33 PM ---------- Previous post was at 04:29 PM ----------
And How This Work The Sd Card Is Used Just To Bring Fastboot And Flash To the EMMC or Flash To The SD-Card And Use The Systematic on it ?
Click to expand...
Click to collapse
When you see fastboot use ur finger nail to just slide sdcard little, it will deattach the sdcard from phone, flash phone using rsd lite will fixed it like it was before.
ozmage said:
Hi Thanks For This Detailed How-To I Hope This Will Help A Lot Of People Since The Blank-Flash Dont Work.
---------- Post added at 04:33 PM ---------- Previous post was at 04:29 PM ----------
And How This Work The Sd Card Is Used Just To Bring Fastboot And Flash To the EMMC or Flash To The SD-Card And Use The System on it ?
Click to expand...
Click to collapse
If downgrade SBL1 in Moto E4 by flashing older bootloader.img on (bootloader unlocked phone or by fastboot flash sbl1 old_sbl1) the phone becomes bricked and it goes to Emergency download mode (EDL / QHS_BULK 9008).
by writing a backup of mmcblk0 (with at least a few hundred MBs - that contains sbl1 and other bootloaders) on good quality SD card is enough to fetch phone to bootloader/fastboot on many qcom Motorola phone. I think it works this way: if bootloader is erased or old in phone and it goes to 9008 and you put SD card with latest bootloader in it, then eMMC tries to boot from SD card. It is kind of secondary option for eMMC to boot or something else.... I remember I used to repair Samsung qcom and exynos phones this way a few years back.
How to create a 256 MB debrick/unbrick/super magic file from a working Motorola phones:
1. rooted phone by any means or unlocked bootloader + twrp.
2. with terminal if rooted type su first then : dd if=/dev/block/mmcblk0 of=/sdcard/debrick.img bs=1024 count=2621244
2a. with cmd if twrp: adb shell dd if=/dev/block/mmcblk0 of=/sdcard/debrick.img bs=1024 count=2621244
This will make a 256mb debrick/unbrick/super magic file on your sdcard....
copy debrick.img from SD card to PC or pull using adb pull /sdcard/debrick.img - writing file to SD card I believe is explained in the first post.
How to create a debrick file from E4 Verizon phone that cannot bootloader unlock or root ???
Well, you could use Verizon Software Assistant Motorola for this and connect a working phone on fastboot mode, it will download most recent repair file that includes mbm and mbm-ci - that contains blank flash for many new Motorola phones.
Another way is by using MetroPCS /T-Mobile debrick file on Verizon phone (BB.32 bootloader is latest). Because both are MSM8917 CPU and both have BB.32 bootloader. Last time I repaired a Verizon phone with SD card method and using a debrick file from MetroPCS 64-6 version. If you need file, let me know. I can upload it tomorrow....
Cheers guys!
---------- Post added at 10:34 PM ---------- Previous post was at 10:23 PM ----------
Salik Iqbal said:
When you see fastboot use ur finger nail to just slide sdcard little, it will deattach the sdcard from phone, flash phone using rsd lite will fixed it like it was before.
Click to expand...
Click to collapse
There is no need for SD card to detach, because fastboot mode will not flash anything on SD card.... It just boots from SD card and nothing else
ozmage said:
Hi Thanks For This Detailed How-To I Hope This Will Help A Lot Of People Since The Blank-Flash Dont Work.
---------- Post added at 04:33 PM ---------- Previous post was at 04:29 PM ----------
And How This Work The Sd Card Is Used Just To Bring Fastboot And Flash To the EMMC or Flash To The SD-Card And Use The System on it ?
Click to expand...
Click to collapse
ALI12 said:
If downgrade SBL1 in Moto E4 by flashing older bootloader.img on (bootloader unlocked phone or by fastboot flash sbl1 old_sbl1) the phone becomes bricked and it goes to Emergency download mode (EDL / QHS_BULK 9008).
by writing a backup of mmcblk0 (with at least a few hundred MBs - that contains sbl1 and other bootloaders) on good quality SD card is enough to fetch phone to bootloader/fastboot on many qcom Motorola phone. I think it works this way: if bootloader is erased or old in phone and it goes to 9008 and you put SD card with latest bootloader in it, then eMMC tries to boot from SD card. It is kind of secondary option for eMMC to boot or something else.... I remember I used to repair Samsung qcom and exynos phones this way a few years back.
How to create a 256 MB debrick/unbrick/super magic file from a working Motorola phones:
1. rooted phone by any means or unlocked bootloader + twrp.
2. with terminal if rooted type su first then : dd if=/dev/block/mmcblk0 of=/sdcard/debrick.img bs=1024 count=2621244
2a. with cmd if twrp: adb shell dd if=/dev/block/mmcblk0 of=/sdcard/debrick.img bs=1024 count=2621244
This will make a 256mb debrick/unbrick/super magic file on your sdcard....
copy debrick.img from SD card to PC or pull using adb pull /sdcard/debrick.img - writing file to SD card I believe is explained in the first post.
How to create a debrick file from E4 Verizon phone that cannot bootloader unlock or root ???
Well, you could use Verizon Software Assistant Motorola for this and connect a working phone on fastboot mode, it will download most recent repair file that includes mbm and mbm-ci - that contains blank flash for many new Motorola phones.
Another way is by using MetroPCS /T-Mobile debrick file on Verizon phone (BB.32 bootloader is latest). Because both are MSM8917 CPU and both have BB.32 bootloader. Last time I repaired a Verizon phone with SD card method and using a debrick file from MetroPCS 64-6 version. If you need file, let me know. I can upload it tomorrow....
Cheers guys!
---------- Post added at 10:34 PM ---------- Previous post was at 10:23 PM ----------
There is no need for SD card to detach, because fastboot mode will not flash anything on SD card.... It just boots from SD card and nothing else
Click to expand...
Click to collapse
Good guide on unbrick for Motorola phones! Yes its not nessecary to remove sdcard but i don't know if old phones are used by sdcard as primary storage after bricked. Too avoid replying everyone's post for sdcard deattach i preferred saying yes deattach it
Salik Iqbal said:
Good guide on unbrick for Motorola phones! Yes its not nessecary to remove sdcard but i don't know if old phones are used by sdcard as primary storage after bricked. Too avoid replying everyone's post for sdcard deattach i preferred saying yes deattach it
Click to expand...
Click to collapse
one of the colleague confirmed it worked on Motorola Titan which I believe is MSM8226 / older phone. I haven't tested it myself, so....
Salik Iqbal said:
I have backup starting 150MB of sda partition.. get it from link, use class 10 SDCARD 16GB atleast i have tested, format sdcard with FAT32, open win32 disk imager, write unbrick img to sdcard. Remove battery, put sdcard in your dead xt1766, put battery, press volume down and insert usb cable.. you will see fastboot menu.. flash latest xt1766 from Motorola firmware.
That's all folks!
Link to debrick img..
https://mega.nz/#!NmwjWJ7a!shXGk8euTf000ehVsveRy0ZPVj3tyDxRV15m7NS_7dk
Click to expand...
Click to collapse
but after that phone is coming on NO SERVICE and Radio is OFF. how do i fix it?
skyrio said:
but after that phone is coming on NO SERVICE and Radio is OFF. how do i fix it?
Click to expand...
Click to collapse
Try this
fastboot oem config bootmode " "
fastboot oem fb_mode_set
fastboot -w
fastboot oem fb_mode_clear
fastboot reset
Moto E4 XT 1765 hard brick
Salik Iqbal said:
Good guide on unbrick for Motorola phones! Yes its not nessecary to remove sdcard but i don't know if old phones are used by sdcard as primary storage after bricked. Too avoid replying everyone's post for sdcard deattach i preferred saying yes deattach it
Click to expand...
Click to collapse
ALI12 said:
If downgrade SBL1 in Moto E4 by flashing older bootloader.img on (bootloader unlocked phone or by fastboot flash sbl1 old_sbl1) the phone becomes bricked and it goes to Emergency download mode (EDL / QHS_BULK 9008).
by writing a backup of mmcblk0 (with at least a few hundred MBs - that contains sbl1 and other bootloaders) on good quality SD card is enough to fetch phone to bootloader/fastboot on many qcom Motorola phone. I think it works this way: if bootloader is erased or old in phone and it goes to 9008 and you put SD card with latest bootloader in it, then eMMC tries to boot from SD card. It is kind of secondary option for eMMC to boot or something else.... I remember I used to repair Samsung qcom and exynos phones this way a few years back.
How to create a 256 MB debrick/unbrick/super magic file from a working Motorola phones:
1. rooted phone by any means or unlocked bootloader + twrp.
2. with terminal if rooted type su first then : dd if=/dev/block/mmcblk0 of=/sdcard/debrick.img bs=1024 count=2621244
2a. with cmd if twrp: adb shell dd if=/dev/block/mmcblk0 of=/sdcard/debrick.img bs=1024 count=2621244
This will make a 256mb debrick/unbrick/super magic file on your sdcard....
copy debrick.img from SD card to PC or pull using adb pull /sdcard/debrick.img - writing file to SD card I believe is explained in the first post.
How to create a debrick file from E4 Verizon phone that cannot bootloader unlock or root ???
Well, you could use Verizon Software Assistant Motorola for this and connect a working phone on fastboot mode, it will download most recent repair file that includes mbm and mbm-ci - that contains blank flash for many new Motorola phones.
Another way is by using MetroPCS /T-Mobile debrick file on Verizon phone (BB.32 bootloader is latest). Because both are MSM8917 CPU and both have BB.32 bootloader. Last time I repaired a Verizon phone with SD card method and using a debrick file from MetroPCS 64-6 version. If you need file, let me know. I can upload it tomorrow....
Cheers guys!
---------- Post added at 10:34 PM ---------- Previous post was at 10:23 PM ----------
There is no need for SD card to detach, because fastboot mode will not flash anything on SD card.... It just boots from SD card and nothing else
Click to expand...
Click to collapse
i have brick Moto E4 XT 1765
CPU MSM 8917
metropcs
please help me, flash.bat not work i have trying lots of methood but not success
can i try above methood on my brick device
or plz give me suitable debrick file for my device
ALI12 said:
If downgrade SBL1 in Moto E4 by flashing older bootloader.img on (bootloader unlocked phone or by fastboot flash sbl1 old_sbl1) the phone becomes bricked and it goes to Emergency download mode (EDL / QHS_BULK 9008).
by writing a backup of mmcblk0 (with at least a few hundred MBs - that contains sbl1 and other bootloaders) on good quality SD card is enough to fetch phone to bootloader/fastboot on many qcom Motorola phone. I think it works this way: if bootloader is erased or old in phone and it goes to 9008 and you put SD card with latest bootloader in it, then eMMC tries to boot from SD card. It is kind of secondary option for eMMC to boot or something else.... I remember I used to repair Samsung qcom and exynos phones this way a few years back.
How to create a 256 MB debrick/unbrick/super magic file from a working Motorola phones:
1. rooted phone by any means or unlocked bootloader + twrp.
2. with terminal if rooted type su first then : dd if=/dev/block/mmcblk0 of=/sdcard/debrick.img bs=1024 count=2621244
2a. with cmd if twrp: adb shell dd if=/dev/block/mmcblk0 of=/sdcard/debrick.img bs=1024 count=2621244
This will make a 256mb debrick/unbrick/super magic file on your sdcard....
copy debrick.img from SD card to PC or pull using adb pull /sdcard/debrick.img - writing file to SD card I believe is explained in the first post.
How to create a debrick file from E4 Verizon phone that cannot bootloader unlock or root ???
Well, you could use Verizon Software Assistant Motorola for this and connect a working phone on fastboot mode, it will download most recent repair file that includes mbm and mbm-ci - that contains blank flash for many new Motorola phones.
Another way is by using MetroPCS /T-Mobile debrick file on Verizon phone (BB.32 bootloader is latest). Because both are MSM8917 CPU and both have BB.32 bootloader. Last time I repaired a Verizon phone with SD card method and using a debrick file from MetroPCS 64-6 version. If you need file, let me know. I can upload it tomorrow....
Cheers guys!
---------- Post added at 10:34 PM ---------- Previous post was at 10:23 PM ----------
There is no need for SD card to detach, because fastboot mode will not flash anything on SD card.... It just boots from SD card and nothing else
Click to expand...
Click to collapse
I tried this procedure with the xt1768 and was unable to get it to boot to fastboot. That command generates a ~2gb file, I write to to the sdcard with the win32diskimager and place it in the disabled unit, put battery in and hold volume down and insert usb, and nothing happens. QHSUSB__BULK device shows in the device manager but that happens regardless of the volume down or the presence of the sdcard. Thining this might be because the xt1766 has a mediatek while the xt1768 has a qualcomm cpu?
Mirani said:
i have brick Moto E4 XT 1765
CPU MSM 8917
metropcs
please help me, flash.bat not work i have trying lots of methood but not success
can i try above methood on my brick device
or plz give me suitable debrick file for my device
Click to expand...
Click to collapse
Will upload on weekend..
Mirani said:
i have brick Moto E4 XT 1765
CPU MSM 8917
metropcs
please help me, flash.bat not work i have trying lots of methood but not success
can i try above methood on my brick device
or plz give me suitable debrick file for my device
Click to expand...
Click to collapse
xeropressence said:
I tried this procedure with the xt1768 and was unable to get it to boot to fastboot. That command generates a ~2gb file, I write to to the sdcard with the win32diskimager and place it in the disabled unit, put battery in and hold volume down and insert usb, and nothing happens. QHSUSB__BULK device shows in the device manager but that happens regardless of the volume down or the presence of the sdcard. Thining this might be because the xt1766 has a mediatek while the xt1768 has a qualcomm cpu?
Click to expand...
Click to collapse
Both are Qualcomm, processor's are different.. xt1765 will hopefully work will upload this weekend
Salik Iqbal said:
Both are Qualcomm, processor's are different.. xt1765 will hopefully work will upload this weekend
Click to expand...
Click to collapse
i have unlock boot loader working fine on stock firmware version 7.1.1
NCQ 26.69.46_cid22_subsidy-MPCS_regulatory. but not rooted working charm, after few day i have connected on wifi server suddenly i have received pop up OTA new security patch ready for install i have just installed this patch and my mobile going installing, then erasing after that now not showing anything i have hard brick my own phone with my little negligence.
when i connected to pc just tray icon show HS_USB_Qdloader 9008 and only detected by flash.bat and Qualcomm Snapdragon Flash Tool
plz help me out this headache
im waiting for your responce
Thanks sir
Mirani said:
i have brick Moto E4 XT 1765
CPU MSM 8917
metropcs
please help me, flash.bat not work i have trying lots of methood but not success
can i try above methood on my brick device
or plz give me suitable debrick file for my device
Click to expand...
Click to collapse
Hello, I have followed these directions with unlocked bootloader in TWRP on XT1765
Code:
How to create a 256 MB debrick/unbrick/super magic file from a working Motorola phones:
1. rooted phone by any means or unlocked bootloader + twrp.
2. with terminal if rooted type su first then : dd if=/dev/block/mmcblk0 of=/sdcard/debrick.img bs=1024 count=2621244
2a. with cmd if twrp: adb shell dd if=/dev/block/mmcblk0 of=/sdcard/debrick.img bs=1024 count=2621244
I am uploading it now as I type this. I will update post once its done. The file ended up being 446MB instead of 256MB however I hope that doesn't matter. I havent used the file just yet or had the chance. Pleases let me know if it works for you. I think my battery on dead phone is dead also, lol.
Device the .img was made from is as follows:
ROM: Slim-7.1.2.build.2.0-UNOFFICIAL-20180310-1717
Model: Moto E4 XT1765
Carrier: MetroPCS
Color: Gold
Posted it here:
https://forum.xda-developers.com/moto-e4/how-to/untested-moto-e4-xt1765-metropcs-t3843657
hi, do you have an image for xt1776 moto E4 Plus, sprint/boost
jamiedoe said:
hi, do you have an image for xt1776 moto E4 Plus, sprint/boost
Click to expand...
Click to collapse
This should be asked on the XDA Moto E4 Plus forum, but you can find a copy here. The one dated September 19, 2018 is right in the middle, and should be the newest.
hitokage004 said:
This should be asked on the XDA Moto E4 Plus forum, but you can find a copy here. The one dated September 19, 2018 is right in the middle, and should be the newest.
Click to expand...
Click to collapse
Hi.
Sorry, i meant the image for unbricking not the firmware
jamiedoe said:
Sorry, i meant the image for unbricking not the firmware
Click to expand...
Click to collapse
Partially my fault as well, I was scanning through threads and didn't realize that you probably meant an unbrick image - I've been seeing lots of firmware requests recently. If you ask in the E4 Plus forum though and reference this thread, you might be able to find someone willing to make you the bootloader image needed.
Related
Some? Samsung devices support a special kind of unbricking hard-bricked* phones.
This thread tries to provide that to the i927/glide..
Who wants this?
If you have hard-bricked* your device (please see the next post about difference between hard- and soft-bricked)
there is no other reason to use this!
Current state:
Totally untested and absolutely without any warranty.
I have no idea if the image itself is good or not - neither if the whole process would work for the i927!
As I do not own a hard-bricked device and I do not want to damage mine I cannot test this by myself.
The reason creating this is because a user had requested it: click here for the origin user request
Please give me feedback if you have tested it!!!
Known issues:
who knows..
Instructions
Requirements
First of all you need a micro SD card. If you have none you cannot continue (man.. buy one!).
Then you need a PC which is able to read this SD card or an external SD card reader.
Basic
Here in short the basic steps you need to take (detailed in the next section):
Download
Extract
Flash unbrick image to SD card
Insert SD card into the Glide
boot
wait
soft-unbrick
Detailed (Linux)
Some parts taken from here
Download i927_unbrick.zip
unzip -d /tmp/unbrick i927_unbrick.zip
Insert SD card into your PC
dmesg | grep dev | tail
--> you should see something like "/dev/sdc1" or "/dev/mmcfoo1" or similar which is your SD card you inserted just before. In the next parts we refer to it as "/dev/FROM-DMESG-OUTPUT"
The next commands will make your SD card UNUSABLE until you reformat it! Ensure that you do not have any data you need on it!
sudo umount /dev/FROM-DMESG-OUTPUT (do not use any GUI clickable eject action instead)
sudo dd if=/tmp/unbrick/unbrick.img of=/dev/FROM-DMESG-OUTPUT
pull out the SD card from the PC
remove the battery, sim and any external SD card from your device
insert your unbrick SD into your phone
insert the battery and down your power button (at this point your phone might actually boot completely and you can recovery any software/data you want)
reboot into Download mode either via adb or Volume Up while powering on
Once the device is booted into bootloader remove the SD card and start ODIN or heimdall to flash a STOCK firmware or use the OneClick Soft-unbrick tool
Detailed (Windows)
Some parts taken from here
Download win32diskimager
Download i927_unbrick.zip
Extract i927_unbrick.zip and win32diskimager
Insert your SD card into your PC and wait until it gets detected
Run win32diskimager
browse for your extracted unbrick image
Select your SD in the dropdown box
The next step will make your SD card UNUSABLE until you reformat it! Ensure that you do not have any data you need on it!
Click write
pull out the SD card from the PC
remove the battery, sim and any external SD card from your device
insert your unbrick SD into your phone
insert the battery and down your power button (at this point your phone might actually boot completely and you can recovery any software/data you want)
reboot into Download mode either via adb or Volume Up while powering on
Once the device is booted into bootloader remove the SD card and start ODIN or heimdall to flash a STOCK firmware or use the OneClick Soft-unbrick tool
Download
Please go to the Download page
Background of the unbrick.img
todo
Sources
First, Second, Third
Thanks
Please report back if it has or has not worked for you!
Thanks
xdajog
.
XDA:DevDB Information
Unbrick/Debrick hard-bricked i927, Tool/Utility for the Samsung Captivate Glide
Contributors
xdajog, alvcross
Version Information
Status: Alpha
Created 2016-01-04
Last Updated 2016-01-12
FAQ
hard-bricked?
When do we speak about hard-bricked? If one or more of the following matches your situation you have hard-bricked your device
powering on leaves the device black like it is still powered off
you cannot get into the download mode anymore
soft-bricked?
When do we speak about soft-bricked? If one or more of the following matches your situation you have soft-bricked your device and you should not use the instructions made in this thread:
you can go into the download mode
you can start recovery mode
you see the samsung logo
you see the boot animation
If you have soft-bricked your device: There is an easy one available for our device (untested by me but many tell it works fine) --> http://forum.xda-developers.com/showthread.php?t=1153310
Reserved
does it actually work?
If you brick your bootloader, you wouldnt boot from SD card IMHO.
Our phone could recovery from APX mode. More info http://forum.xda-developers.com/showthread.php?t=1528256
bubor said:
does it actually work?
If you brick your bootloader, you wouldnt boot from SD card IMHO.
Our phone could recovery from APX mode. More info http://forum.xda-developers.com/showthread.php?t=1528256
Click to expand...
Click to collapse
Thats the big question. e.g the T999 will boot from the SD card even when the bootloader is blown. So as stated above I have no idea if the same process will work for this phone so I need testers who tries it actually...
The unbrick image was made the way it should work IF yes IF the i927 will boot from the SD card in case of corrupted bootloader. so without any test I cannot tell you if it would work..
.
xdajog said:
Thats the big question. e.g the T999 will boot from the SD card even when the bootloader is blown. So as stated above I have no idea if the same process will work for this phone so I need testers who tries it actually...
The unbrick image was made the way it should work IF yes IF the i927 will boot from the SD card in case of corrupted bootloader. so without any test I cannot tell you if it would work..
.
Click to expand...
Click to collapse
There is always a preloader, what loads bootloader, I think that loads sd card. Preloader does APX mode on tegra 2.
I doubt it would work, but who knows?
Hi guys,
i came up with a temporary to unbrick LG G4 H815 , you just need a 32 GB SD card ( i used Sandisk 10 class) , the dump that i will link , and Win32 disk Imager, the SD card must low level formatted.
1- download this dump
http://www.4shared.com/rar/NzSqsBziba/EMMC_ROM1_032G74_1803230737_00.html
2- put the SD card in the PC and chose the dump file and write ( run as admin ):
3- put the sd card in the phone plug the battery and power on.
Bam
unbrick H811 T-MOBILe
how i can get H811 LG G4 Dump file...?
T.E.I.M said:
how i can get H811 LG G4 Dump file...?
Click to expand...
Click to collapse
From the 1st post?
Sent from my SM-G930F using Tapatalk
bender_007 said:
From the 1st post?
Sent from my SM-G930F using Tapatalk
Click to expand...
Click to collapse
i need H811 Model dump file...the 1st one its for h815 Euro Model!!!!!
T.E.I.M said:
i need H811 Model dump file...the 1st one its for h815 Euro Model!!!!!
Click to expand...
Click to collapse
Ah I see now. You have to ask someone from 811 thread to dump it for you. Your keyboard "!" got stuck also?
Is the SD Card must be 32 GB?
aes1151 said:
Is the SD Card must be 32 GB?
Click to expand...
Click to collapse
no, 8 gb enough
Thanks for the answer.
I tried 8GB SD card before and it working but gave me an error (security Error) when I went to get into Download mode ..or gave Boot loop at normal mode ..
Finally it stopped working .. also when I repeated the steps again not running any more
(but with another dump file.)
T.E.I.M said:
i need H811 Model dump file...the 1st one its for h815 Euro Model!!!!!
Click to expand...
Click to collapse
I posted one here for h811 v20o. It booted mine up.
culot said:
I posted one here for h811 v20o. It booted mine up.
Click to expand...
Click to collapse
thanx
size of sd-card you used....?
32 or 8 Go
T.E.I.M said:
thanx
size of sd-card you used....?
32 or 8 Go
Click to expand...
Click to collapse
32gb.
culot said:
32gb.
Click to expand...
Click to collapse
can i use the full dump "Dump_H811_1GB.img"
http://www.gsm-file.com/files/dumph8111gbzip-2702.html
or i must use dump file *.BIN that i cant find it
link me *.bin file for h811
T.E.I.M said:
can i use the full dump "Dump_H811_1GB.img"
http://www.gsm-file.com/files/dumph8111gbzip-2702.html
or i must use dump file *.BIN that i cant find it
link me *.bin file for h811
Click to expand...
Click to collapse
That specific dump did not work at all for me. The singleimage.bin I posted worked for me right away. It's inside the archive i linked in that post.
---------- Post added at 03:15 PM ---------- Previous post was at 02:58 PM ----------
T.E.I.M said:
can i use the full dump "Dump_H811_1GB.img"
http://www.gsm-file.com/files/dumph8111gbzip-2702.html
or i must use dump file *.BIN that i cant find it
link me *.bin file for h811
Click to expand...
Click to collapse
Image is is q.zip in the download link in that post.
thanx
Awesome! I'm sure you will be a lifesaver for many people. Now I don't have to worry as much if I try to port ROMs.
BTW, just curious, but does the SD card execute the dump when the phone boots up or something? (just curious as to how it works by putting a dump on an external sd card).
Thanks
leptdre said:
Hi guys,
i came up with a temporary to unbrick LG G4 H815 , you just need a 32 GB SD card ( i used Sandisk 10 class) , the dump that i will link , and Win32 disk Imager, the SD card must low level formatted.
1- download this dump
2- put the SD card in the PC and chose the dump file and write ( run as admin ):
3- put the sd card in the phone plug the battery and power on.
Bam
Click to expand...
Click to collapse
Hello!
When I put SD in phone and turn it on - it enters download mode and do nothing.
What did I do wrong?
darkommm said:
Hello!
When I put SD in phone and turn it on - it enters download mode and do nothing.
What did I do wrong?
Click to expand...
Click to collapse
you did nothing Wrong , now u need to flash KDZ with LGUP , and you are good to go
qualcomm 9008
my lg g4 h811 stuck on qualcomm 9008 mode,no display, phone does not turned on, but connect as qualcomm 9008 while connected through usb. will this method work for me??
AwaisTariq20 said:
my lg g4 h811 stuck on qualcomm 9008 mode,no display, phone does not turned on, but connect as qualcomm 9008 while connected through usb. will this method work for me??
Click to expand...
Click to collapse
yes use this mothod
Help me
I just follow ur instructions and my phone alive again but one thing after 4 or 5 min later my phone goes blank and turn into Qualcomm 9008 and when i pull battery and insert again phone booted again in normal. Plz help me in this meter i tried all kdz firmwares and also custom roms but still facing this problem. My phone model is h811.
Tested Devices:
Huawei GR5 BLL-L22.
Hello all,
I just wanted to put this guide out there for anyone struggling with restoring stock after flashing a custom nougat rom/TWRP. It took me several days to figure out this method, which has never failed to get me back to stock after screwing with my phone. You can also use this if you accidentally wiped data without removing your fingerprint.
Prerequisites:
- Stock firmware for your device. If you were using a BLL-L22, you need the firmware which matches your phone's model and it has only been tested with the same firmware version. You can use the Huawei firmware update finder to get it.
- You'll need HuaweiUpdateExtractor, find it here: https://forum.xda-developers.com/showthread.php?t=2433454 . All credit goes to the original creator of the tool, @worstenbrood .
- You also need a Micro SD card in your phone, along with a micro SD card reader/ SD card reader (if you have a micro SD to SD card converter).
- You need a functioning computer with ADB commands installed system wide.
Anyways, here goes:
1. Unzip the update zip file, and ensure you have the update.app .
2. Using Huawei Update Extractor, extract only the boot.img, recovery.img, system.img, and vendor.img from the update.app . Those are the only files you need.
3. Boot into TWRP and format data. then wipe ALL partitions.
HINT: If you had your Micro SD card merged with internal storage, MAKE SURE you partition your micro SD card in TWRP via the partition SD card functionality, using EXT3/4.
4. Reboot into TWRP, and flash the vendor.img using the install image functionality in TWRP.
5. Wipe all partitions and format data as well, and reboot into the bootloader (fastboot).
6. Flash the BOOT, RECOVERY, and SYSTEM images, in that order, using fastboot.
7. Reboot into fastboot, and remove your micro SD card.
8. Create a folder called dload in the folder where the update.app file is located, and place the update.app file inside the dload folder.
9. Copy the dload folder to the micro SD card you have connected to your PC via a card reader.
10. Place the micro SD card back inside the phone, and then hold power + volume up + volume down.
11. This should begin the flashing process, wait till it finishes flashing and reboots.
12. Boot into the stock recovery, and factory reset and also clear data.
13. Reboot.
14. PROFIT! You should be back on EMUI 5.0 with a fully functional phone once more.
If you have any questions at all, feel free to ask. Also, if the guide worked for you, please let me know and I'll compile a list of devices it has been tested on. Thanks guys!
DISCLAIMER: This method works flawlessly for me, and I have used it countless times with my Huawei GR5 2017 (BLL-L22). I am not responsible for any damage done to your phone, nor can I guarantee this will work on every single variant of the Honor 6X. Do to this at your own discretion.
Hit thanks if I helped.
Nice guide dude!
Awesome job bro keep it up
very nicely put together mate. nice work.
I backed up my stock emui 5 boot,system,vendor but after restoring backup I stucked on boot animation what i can do now
Sent from my HONOR-6X using Tapatalk
arshilhonor6x said:
I backed up my stock emui 5 boot,system,vendor but after restoring backup I stucked on boot animation what i can do now
Click to expand...
Click to collapse
This guide concerns rolling back via dload, not via TWRP. You'd be better off asking in the TWRP thread, or asking the OpenKirin team.
I haven’t follow this guide
I just used dload directly with the same firmware (i was only rooted)
Phone doesn’t enter fastboot using volume down and power
But i can go to fastboot using adb command (adb reboot bootloader)
I am actually exactly doing this right now. Honor was not able to help me, after the BETA UEMI 5.0 put the system into a non-upgradable state. I tried to upgrade it/rollback etc. but that made it worse.
So- my current problem is, I don't have TWRP (It is installed, but won't start because I am in the rollback-version of the firmware). what can I do to actually go on with it?
When you say: 3. Boot into TWRP and format data. then wipe ALL partitions.
So - I used the recovery from HAWEI to format the data partition (That should do it).
As I said - I only have fastboot at hand right now.
Also - the vendor image flash returns this:
Code:
$ fastboot flash vendor VENDOR.img
target reported max download size of 471859200 bytes
sending 'vendor' (419273 KB)...
OKAY [ 11.443s]
writing 'vendor'...
FAILED (remote: Command not allowed)
finished. total time: 11.448s
Any hints?
Use dload method to flash full latest firmware from firmware finder
Sent from my BLN-L22 using Tapatalk
---------- Post added at 09:33 AM ---------- Previous post was at 09:32 AM ----------
If u are unable to boot any recovery then go to service centre they will replace your mobo
Sent from my BLN-L22 using Tapatalk
arshilhonor6x said:
Use dload method to flash full latest firmware from firmware finder
Sent from my BLN-L22 using Tapatalk
---------- Post added at 09:33 AM ---------- Previous post was at 09:32 AM ----------
If u are unable to boot any recovery then go to service centre they will replace your mobo
Click to expand...
Click to collapse
No, it just won't allow me to write the vendor image.
I can go into the regular recovery etc., but I can' t do anything. Not even reset the system etc.
xda_jm said:
No, it just won't allow me to write the vendor image.
I can go into the regular recovery etc., but I can' t do anything. Not even reset the system etc.
Click to expand...
Click to collapse
Flash twrp using fastboot or use dload method
Sent from my BLN-L22 using Tapatalk
arshilhonor6x said:
Flash twrp using fastboot or use dload method
Click to expand...
Click to collapse
I have the BLN-L21C432 device (Berlin). You know which TWRP I have to flash?
Using the twrp from https://dl.twrp.me/berlin/ ->
twrp-3.1.1-0-berlin.img
That twrp won't show up. Probably because I don't have the right Vendor-image or so. No logs available etc. A real bummer ... :crying:
Stuck here:
Code:
You're device has been unlocked and can't be trusted.
To learn more, visit:
Blabla UYRL ...
Your device is booting now...
My assumption is that I have a mismatch between Vendor/recovery/system and boot.img files. Only, how do I look into these images (I could mount them as loopback device under linux? Linux only here, no windows). And I need to identify the verison of these images/build to flash the right versions for the dload to actually handle the right upgrade.
xda_jm said:
You know which TWRP I have to flash?
Using the twrp from https://dl.twrp.me/berlin/ ->
twrp-3.1.1-0-berlin.img
That twrp won't show up. Probably because I don't have the right Vendor-image or so. No logs available etc. A real bummer ... :crying:
Click to expand...
Click to collapse
That TWRP won't work, sadly even if hosted on official site it never worked. Grab the TWRP from here https://forum.xda-developers.com/honor-6x/development/twrp-t3583413 and flash via fastboot, it'll surely works. Vendor partition is separated from recovery one, so don't worry because even with an incorrect vendor.img it'll works anyway
RedSkull23 said:
That TWRP won't work, sadly even if hosted on official site it never worked. Grab the TWRP from here https://forum.xda-developers.com/honor-6x/development/twrp-t3583413 and flash via fastboot, it'll surely works. Vendor partition is separated from recovery one, so don't worry because even with an incorrect vendor.img it'll works anyway
Click to expand...
Click to collapse
Yeah. That was it.
So I am able to actually get into the TWRP recovery. Nice
Now - following your guide, I am unable to format data partition:
Code:
Full SELinux support is present
MTP Enabled
Formating data using mkfs.f2fs
mkfs.f2fs -t 0 /dev/block/mmcblk0p49 process ended with ERROR: 255
unabel to wipe data
unable to format to remove encryption
Any idea?
Shall I continue with the process?
I could change the filesystem of data to ext4 or so for testing?
UPDATE: Actually changing data to ext4, formating it as ext4 + rebooting into recovery and changing back to f2fs and formating f2fs worked in the end. What a crap.
I'll write down exactly what I do!
So - everything worked, except the factory reset showed a red exclamation mark.
It is now rebooting. And - no. I still have the BETA EMUI 5.0 showing, BuildNr. BLN-L21C900B300
Opening a new post for the next steps...
So - the cleaning has not worked.
After checking the imags in the update package, I noticed they are all different.
Why did the system-reset fail at all? Where does that come from?
Here the file-checksums:
Code:
$ cat BLN-L21C432B360-FullOTA-MF-PV/md5sums.txt
cbc1a5b85deb8caca46d7ed691f1d5d7 BOOT.img
78ccf0ff58d189284293e219f2aa8ce2 CACHE.img
eef4f7d2c4187b7cd195df1c1139950e CRC.img
f6594819938b923bccf075349b250347 CURVER.img
a181b39b6095f221ffb207268d10d540 DTS.img
aa3a0518794c16bb22849676c13ba55c EFI.img
0f1fcd32afb2db5183d86e527510c6b4 FASTBOOT.img
8379cfc96d5ddd57993da668c0e68da7 FW_HIFI.img
d60eb96f274cab285fe1bc5cb8ac874c FW_LPM3.img
afd9223813961adfbf71b0a51c310f66 MODEM_FW.img
176c0d4b0489a639f5bd371b5445a466 MODEMNVM_UPDATE.img
f07fcca53b5337e003e9894ec4b231e6 PRODUCT.img
40c8ce310fb8dde705c6b29ce316a215 RECOVERY2.img
a3883873ca0054ec12fb8d0a71835ca9 RECOVERY.img
cd22975bcc99a3436a74d6123e9c2796 SENSORHUB.img
2c4fab4df4b00c7dcb08fd8a47c0228f SHA256RSA.img
0565a9f075122ebf46c9f623eb6b22d2 TEEOS.img
e6a5b518daa00ea67a2a360408534dd9 TRUSTFIRMWARE.img
09e9dcef68ffddce4c1a41f1bbeae435 UPDATE.APP
19324f9cd1351119b4efdfa5c235200e VENDOR.img
9219d25ed7eb999fb08c03bf493929a3 VERLIST.img
83c5d8c7866c34f4ff901e17536ad3b4 XLOADER.img
Code:
$ cat RollBack_DE/md5sum.txt
6682ebf3c4c59b58e27cac42bc0a5760 BOOT.img
c9026aa21284a5c6575573bad6c67531 CACHE.img
643062216ba9a1a9c43091a56407b4e4 CRC.img
e665793d69c041c1a67ce25e342bb665 CURVER.img
862d05d2ac39567d48db9d4a996698e8 CUST.img
0c66cff221dd1adade7060d93f9f14db DTS.img
997a84cac4901d8d47a13d03a41645c1 EFI.img
cfdb3c574a4e22e6918021eb551af744 FASTBOOT.img
6534c81facf064c61fbe838a844bcf53 FW_HIFI.img
2c6cf6c896c17ed938563779d4bc015d FW_LPM3.img
330f6c5fe86c9c716ba675ade522a4c4 MODEM_FW.img
77ca34a576955b1aa7b09adcc43183aa MODEMNVM_UPDATE.img
bf696a2a9eb149bf3d409ab3fab8da1b RECOVERY2.img
ba1a5ef8d2d77dd03a4e5a3fb8be724b RECOVERY.img
e73ae0c33807474e61caaf2f5864bd93 SENSORHUB.img
53d8a3d3afcfd61a73d4446d37602249 SHA256RSA.img
713c288402f5d540efc722e442218fc0 SYSTEM.img
29a07ee1454ece337416b595101a016f TEEOS.img
15a226f7741aee2d026d760f755d6991 TRUSTFIRMWARE.img
b8100f45c08c2b54ec089e52d945fae9 VERLIST.img
7eb918861de29526259611fe95365e90 XLOADER.img
The rollback one is supposed to be an intermediate entry - C900B300 - which was supposed to make a rollback to EMUI 4.x (Tried that route, because I couldn't update any EMUI 5 releases).
Any idea what to do?
Reloaded twrp. When I chec the internal storqage, I see:
Cache
Data
System
Vendor
Product
Micro SDCard
USB OTG
Could it be the Product partition? What's inside?
xda_jm said:
Reloaded twrp. When I check the internal storage, I see:
Cache
Data
System
Vendor
Product
Micro SDCard
USB OTG
Could it be the Product partition? What's inside?
Click to expand...
Click to collapse
Actually, there are 48 Partitions *lol* Amazing.
And - to write an image manually using adb shell in twrp (That's where it works), the extracted images from UPDATE.APP need to be uncompressed first with:
Code:
/external_sd # simg2img PRODUCT.img PRODUCT.raw
/external_sd # dd if=PRODUCT.raw of=/dev/block/mmcblk0p48
393216+0 records in
393216+0 records out
201326592 bytes (192.0MB) copied, 7.405686 seconds, 25.9MB/s
Alas, the images are identical. So no changes.
Still debugging under the hood.
If anyone has an idea, let me know :}
So - last post from me probably. It has not worked.
My wife decided to stay with the beta EMUI 5.0.0.1 until a decent Lineage OS 14.1 version is there (Stable). I'll then put it on the Honor 6x.
It is amazing to see that actually 8GB of space from the disk is reserved for HUAWEI and GOOGLE tools, dispersed in 48 partitions, all to prevent people from using the device freely.
And I bet in future it will get worse and worse. Anyway - have learned a lot regarding the tools and how to use these, and what to take into account when doing things with phones.
I personally still use an old BQ E4.5 Aquaris Ubuntu phone which does most of what I need very nicely IO know why I hate Apple devices, and not so much Android devices.
in 5% i get failed
software install failed
my build is NRD90M test-keys
after write system recovery boot but faild in dload mode
bootloader is unlock
dark_boy99 said:
in 5% i get failed
software install failed
my build is NRD90M test-keys
after write system recovery boot but faild in dload mode
bootloader is unlock
Click to expand...
Click to collapse
I'll PM you the files. Certain update.app files fail to write, I don't know why. Give me a few hours to get the files to you.
Can someone please help me link to Stock firmware for my device? I honestly don't know what's my model number
What do I download?
First......This is a work in progress meaning it is not a fully working solution yet.
So that's the bad news.
The good news is that this provides an opportunity to learn something.
Everything we learn should also apply to any of the newer Samsung Qualcomm Based Devices.
Lets investigate some of the past methods used to unbrick dead samsung devices.
Also please note that these methods are for Hard Bricked Devices. ( NO Download Mode / NO Recovery Mode / Unresponsive )
Any device that can boot into download mode can easily be fixed with ODIN.
#1) Methods of possible DeBrick That I know of.
A) Use Recovery SD Card.
B) Use Firehose to flash in QDL 9008 / 9006 mode.
C) Boxes - JavaCard - Hardware type solutions.
For now lets look at option A). Hopefully this option is still viable. Although I have tested this a little and so far I am still unable to get booted into download mode.
So in researching Debrick image or Debrick rom of samsung devices you will find some things.
This is what we are interested
https://www.scribd.com/document/272...de-Qualcomm-APQ8084-Includes-SM-N910F-Rev-3-0
Looking at that we should be able to use ODIN and select T-Flash to create the Boot-Recovery-Image.
Unfortunately I tried this and it did not work. The T-Flash just hangs and eventually errors out.
This could be due to the version of Odin i used.
I tried a couple of different Odin versions without any luck.
And also YES you have to do this on a working device.
Since the ODIN method didn't work I know from past experience how to make a bootable EMMC Clone onto a SD-Card.
You can do this in windows or in linux or in the device Terminal ( TWRP Terminal)
This command will make a byte for byte copy of the device EMMC onto a SD Card.
Here are the steps.
1) Insert Blank 16GB SD card into the working device. ( The sd card must be high quality Like V30 or U1 Class. " 95 to 100 mbs speed " )
2) The bootloader version of the device you are using to make the sd card has to match the version on the bricked device. (Flash good device with odin to match factory software before making sd card) <-- <-- <-- " Probable reason my Card is not working yet to boot my bricked device "
3) After that its pretty simple.
We know that the main EMMC of the Tablet is MMCBLK0
We know that the SD Card is assigned MMCBLK1
So executing the following command will clone the emmc to the sd card.
Code:
dd if=/dev/block/mmcblk0 of=/dev/block/mmcblk1
It will take between 30 min and a hour to copy.
I have created this image and tested it but no luck yet.
The image is of the factory T560NUUEU1CQK2_T560NUXAR1CQK2 firmware.
I bricked my tab by flashing the aboot.bin alone from COMBINATION_XAR_FA51_T560NUUEU1APH1.
I flashed just the aboot without flashing the rest of the booloaders from COMBINATION_XAR_FA51_T560NUUEU1APH1.
So what i need to do next is make a card that has the complete set of bootloaders from COMBINATION_XAR_FA51_T560NUUEU1APH1.
Once we have a clone of the emmc we can flash seperate partitions on the sd card just like if we did on the device.
I know for sure the bootloader versions have to match. This is a likly cause for my card not to bring my Tab back to life.
Another possibility is that the card has the whole emmc backup. Mirror of the device. Realistically it should be just the bootloaders.
I have looked at some of the boot-recovery images for other devices. Some have only the bootloaders. Some have all the partitions but only the bootloaders flashed. And even the fact that it is a direct copy of the emmc and not its own unique GPT could all factor into it not working at the moment.
All these different combinations of things could be the difference between the card working or not working.
I will upload the image for you if you want to test it.
You can also dump each partition to an individual backup image in case you need any of them.
Do it in linux using "dd" or do it on the device using "dd" and mmcblk1 rather than mmcblk0
If you don't know what i'm talking about don't worry. I will go over things like that at some point in time.
Here is a upload of the SD Card - EMMC Clone for 16GB T560NU
http://www.mediafire.com/file/5m0b7r11nc3nn5q/16GB-T560NU-.img.zip/file
Unzip the file.
Use win32diskimager to flash the image to the sdcard.
After win32diskimage is complete a bunch of file windows will pop up. On windows 10.
It will say disk must be formatted. Do NOT format the disks.
Close them all and remove the sd card from the computer.
Put sd card in bricked device.
Plug in usb.
Try to boot.
Try to boot into download mode.
Let it sit 5 or 10 min.
See if anything happens.
If you have any luck please let us know.
Unfortunately I think were gonna end up having to do it this way.
https://forum.xda-developers.com/galaxy-s8/help/s8-g950u-hardbrick-t3668572
But we need the .elf programmer for APQ8016.
If anyone can get me the firehose programmer I can build the service rom.
BigCountry907 said:
Unfortunately I think were gonna end up having to do it this way.
https://forum.xda-developers.com/galaxy-s8/help/s8-g950u-hardbrick-t3668572
But we need the .elf programmer for APQ8016.
If anyone can get me the firehose programmer I can build the service rom.
Click to expand...
Click to collapse
Did you ever figure yours out? I did the same thing you did (downgraded aboot and hard bricked). I've been able to create a debrick img using another identical device, but the bricked one still won't respond when the sd card is inserted
iBowToAndroid said:
Did you ever figure yours out? I did the same thing you did (downgraded aboot and hard bricked). I've been able to create a debrick img using another identical device, but the bricked one still won't respond when the sd card is inserted
Click to expand...
Click to collapse
I ended up changing the mainboard.
It was like $60 on amazon. Not sure how many are available.
I tried using a good device to T-Flash a sd card in odin.
The t-Flash never worked.
I also did a direct dump to a sdcard, Literally mirroring the emmc onto the sdcard.
dd if=/dev/block/mmcblk0 of=/dev/block/mmcblk1
The device did not respond to the sd card.
I have recently un-bricked a N950U Note 8 but in order to do that i needed things.
In order to get into edl mode there is a test point somewhere on the board.
You short the test point to ground and then plug in the usb and it will boot edl.
I do not know where the test point of the t560nu is at.
Second you will need the Firehose programmer for the t560nu specifically.
It needs to match the bootloader rev as well.
I don't think its revision that causes the brick but it could be.
I flashed the engineering aboot to a normal running device and that's how i bricked.
I believe you have to flash the whole bootloader set if your going to flash bootloaders.
Someone with a octoplus box got me the test point location.
Octoplus software has photos of the test points.
The edl package was from a different source.
It's possible someone with octoplus or medusa or similar boxes may be able to get the test point and the firehose.
I asked my guy for it but i don't think he looked yet.
I still have my bricked board so if you find the firehose and the testpoint let me know.
I will ask my guy again to check.
BigCountry907 said:
I believe you have to flash the whole bootloader set if your going to flash bootloaders
Click to expand...
Click to collapse
Correct, with qualcomm devices the revision of aboot needs to match the sbl.
Sbl checks the version of aboot if it doesn't match it refuses to boot.
Been there done that.
However I have yet to attempt a hardware repair. Debrick images unsuccessful, no response.
My next step(when I can be bothered to get around to it) is to use an sd card adapter wired directly to the emmc as both use the same protocols and an sd card controller should be able to communicate with an emmc.
As long I can get the partitions to show up on the EMMC, should hopefully be a case of flashing the correct aboot to the right partition.
BigCountry907 said:
I ended up changing the mainboard.
It was like $60 on amazon. Not sure how many are available.
I tried using a good device to T-Flash a sd card in odin.
The t-Flash never worked.
I also did a direct dump to a sdcard, Literally mirroring the emmc onto the sdcard.
dd if=/dev/block/mmcblk0 of=/dev/block/mmcblk1
The device did not respond to the sd card.
I have recently un-bricked a N950U Note 8 but in order to do that i needed things.
In order to get into edl mode there is a test point somewhere on the board.
You short the test point to ground and then plug in the usb and it will boot edl.
I do not know where the test point of the t560nu is at.
Second you will need the Firehose programmer for the t560nu specifically.
It needs to match the bootloader rev as well.
I don't think its revision that causes the brick but it could be.
I flashed the engineering aboot to a normal running device and that's how i bricked.
I believe you have to flash the whole bootloader set if your going to flash bootloaders.
Someone with a octoplus box got me the test point location.
Octoplus software has photos of the test points.
The edl package was from a different source.
It's possible someone with octoplus or medusa or similar boxes may be able to get the test point and the firehose.
I asked my guy for it but i don't think he looked yet.
I still have my bricked board so if you find the firehose and the testpoint let me know.
I will ask my guy again to check.
Click to expand...
Click to collapse
It's only ever been on bootloader rev 1, so i figured i was fine going back as far as possible with aboot, like how it is for sboot on Exynos. Obviously not correct though.
Yeah, I dumped to an SD, but only did the first 200MB, instead of an entire image. I have no idea if that even works on this model - I was just hoping it would, like it used to for the S3 and other devices.. I have no idea where i'd get the firehose so this might be SOL
respected brother plz give me your whatsap no# my tablte t560nu dead after flash
respected brother plz give me your whatsap no# my tablte t560nu dead after flash
My whatsap 03103615995
---------- Post added at 12:47 PM ---------- Previous post was at 12:39 PM ----------
respected brother plz give me your whatsap no# my tablte t560nu dead after flash
My whatsap 03103615995
SM-T560NU Does not Turn On After Software Flash
Hello All,
I have been told this is the right place to find a solution to this problem. I have a Galaxy Tab E (SM-T560NU) that had an attempt made to get around FRP using Odin and Sboot firmware. Unfortunately the thing has not been able to turn on since the flash was done & I am told it has been soft bricked. Is there a proven method of brining this thing back to life?
Datsys said:
Hello All,
I have been told this is the right place to find a solution to this problem. I have a Galaxy Tab E (SM-T560NU) that had an attempt made to get around FRP using Odin and Sboot firmware. Unfortunately the thing has not been able to turn on since the flash was done & I am told it has been soft bricked. Is there a proven method of brining this thing back to life?
Click to expand...
Click to collapse
If it won't even turn on, then it's hard bricked - not soft bricked. And no, no proven method to fix it
Datsys said:
Hello All,
I have been told this is the right place to find a solution to this problem. I have a Galaxy Tab E (SM-T560NU) that had an attempt made to get around FRP using Odin and Sboot firmware. Unfortunately the thing has not been able to turn on since the flash was done & I am told it has been soft bricked. Is there a proven method of brining this thing back to life?
Click to expand...
Click to collapse
How have you managed to flash firmware for Exynos to a Snapdragon device? Sboot is the Exynos boot loader.
ashyx said:
How have you managed to flash firmware for Exynos to a Snapdragon device? Sboot is the Exynos boot loader.
Click to expand...
Click to collapse
I'm sure he meant aboot
iBowToAndroid said:
I'm sure he meant aboot
Click to expand...
Click to collapse
Well if he flashed aboot without sbl then there's not much hope.
SBL checks the integrity of aboot and if it doesnt match it refuses to proceed.
Can't even use qualcomm low level tools.
The only way that may be possible which I have never tried is to wire the emmc direct to an sdcard adapter and hope the controller is able to boot it and see the partitions.
Then flash the correct aboot or sbl.
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.