Help with a unique D802T brick? (bad partition?) - G2 Q&A, Help & Troubleshooting

So I've got my (recently purchased T_T) Australian G2 (D802T) in a bit of a pickle. Here's the story of my rapid descent into idiocy: Rooted with ioroot (went fine), installed TWRP via autorec (whoops!). From here I installed several roms but none would boot past optimizing apps - after some further reading this is apparently a known issue with the D802T.
From here I followed the instructions at http://forum.xda-developers.com/showthread.php?t=2432476 and successfully reset back to stock firmware using a D802T kdz I found online. On first boot the phone asked for a decryption pin, which I fixed by booting to the stock recovery and letting it do its thing. However, it seems that the image was for the 16GB version - I was left with only 10GB accessible space.
This is where I got double stupid - I followed about half of http://www.droidviews.com/your-32gb-lg-g2-shows-only-16gb-storage-space-heres-the-fix/ to fix the issue, but rather than copying over the blank images and re-imaging the firmware again, I tried to get clever by growing the userdata partition manually. Unfortunately it seems that I screwed up, since on next boot I once again had the decryption lock, and now neither the factory reset nor re-flashing the firmware will fix it. The last thing I tried tonight was installing the LG Mobile Support Tool and letting it automatically download and install the firmware, but it seems to be in the exact same condition. Apparently the kdz re-imaging (even CSE Flash) doesn't actually reformat anything... :/
Any ideas? I have access to:
download mode
stock recovery/factory reset screen
bootable stock ROM that locks me out due to thinking it's encrypted, when in fact it's just an incorrect partition table.
Is there any way to get adb access back? Or perhaps to get the phone in to some kind of usb mass storage mode as described in http://forum.xda-developers.com/showthread.php?t=2582142 ? As it is it's only recognized by linux as a serial device - if I could get rw access to the raw storage I think I could fix it up pretty easily.

Does anyone know of any way to get adb or fastboot working in this situation? All I can think of is to flash the kdz again and pull the usb out in attempt to break it even further, as I've read that the phone goes to fastboot or qhsusb_bulk when a boot partition is corrupted; but this seems very foolhardy.
How exactly do kdz flashes work? Is there any way to feed it a kdz file that will reformat the userdata partition correctly, or is that just never going to happen?

amdpox said:
Does anyone know of any way to get adb or fastboot working in this situation? All I can think of is to flash the kdz again and pull the usb out in attempt to break it even further, as I've read that the phone goes to fastboot or qhsusb_bulk when a boot partition is corrupted; but this seems very foolhardy.
How exactly do kdz flashes work? Is there any way to feed it a kdz file that will reformat the userdata partition correctly, or is that just never going to happen?
Click to expand...
Click to collapse
maybe you should first try downloading your kdz from here and trying that.
You don't want to be in qhsusb bulkmode, but if you want fastboot access you could run this command in your terminal
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
to nuke your laf partition and get fastboot through your button combination. But then you might be asking for a hardbrick.

Art Vanderlay said:
maybe you should first try downloading your kdz from here and trying that.
Click to expand...
Click to collapse
Doubt it'll be much different but I'll give it a shot, thanks.
You don't want to be in qhsusb bulkmode, but if you want fastboot access you could run this command in your terminal
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
to nuke your laf partition and get fastboot through your button combination. But then you might be asking for a hardbrick.
Click to expand...
Click to collapse
I don't have adb access or a custom recovery, so I can't run that command - in fact if I can get a shell open on the device at all I think I'd be most of the way to a fix. Why don't I want to be in bulkmode? It seems to me like exactly what I need - raw access to the internal memory as a block device.

amdpox said:
Doubt it'll be much different but I'll give it a shot, thanks.
I don't have adb access or a custom recovery, so I can't run that command - in fact if I can get a shell open on the device at all I think I'd be most of the way to a fix. Why don't I want to be in bulkmode? It seems to me like exactly what I need - raw access to the internal memory as a block device.
Click to expand...
Click to collapse
It's a last resort and it leaves very little margin for error. If you try to force your way into it by yanking out your cable or something you might find yourself hardbricked.
If you flashed a 20D kdz the method for entering hard reset is vol - power then vol up + vol - on lg logo maybe thats why you can't get in now.

Art Vanderlay said:
It's a last resort and it leaves very little margin for error. If you try to force your way into it by yanking out your cable or something you might find yourself hardbricked.
If you flashed a 20D kdz the method for entering hard reset is vol - power then vol up + vol - on lg logo maybe thats why you can't get in now.
Click to expand...
Click to collapse
Fair enough. It feels like I'm at the point of last resort, though.
I tried that 20D kdz, seems to be in the same state. (I'm guessing that's exactly the image that the automated support tool downloaded and flashed.)

Is this fixed ?

bender_007 said:
Is this fixed ?
Click to expand...
Click to collapse
Sadly not. Totally stuck for ideas here... anyone know anything more sensible to try than the cable-pulling?

Related

LG Flash tools detected wrong Model

Hey, guys Im trying to flash my my lg g2 sprint edition back to stock using the lg flash tool. I downloaded the sprint tot and dll and when it says flashing on the lg flash tools it brings up and error that says wrong dll or model, I looked at the model it detected and it says my sprint g2 was a d801.
How do i fix this?
Thanks.
Still need your help guys
Theboss1242 said:
Still need your help guys
Click to expand...
Click to collapse
same issue,
try to replace the dll file with this one:
http://forum.xda-developers.com/attachment.php?attachmentid=2553245&d=1391282521
good luck
Theboss1242 said:
Still need your help guys
Click to expand...
Click to collapse
What rom is your phone currently using right now?
Thank guys I got it to work using the dll. !!
Theboss1242 said:
Thank guys I got it to work using the dll. !!
Click to expand...
Click to collapse
do you think this dll would work for my at&t lg g2 that thinks its the d802 version??
afrojoc said:
do you think this dll would work for my at&t lg g2 that thinks its the d802 version??
Click to expand...
Click to collapse
i don't know, it worked for my ls980 with a d802 firmware
Alexandercat said:
i don't know, it worked for my ls980 with a d802 firmware
Click to expand...
Click to collapse
where did you get the dll?
OMG ITS WORKING!!!!!!
afrojoc said:
where did you get the dll?
OMG ITS WORKING!!!!!!
Click to expand...
Click to collapse
nice to know :good:
Please Help
I have the same issue. Flashtool thinks my phone is a D801. It boots normally for a few seconds and keep rebooting. Im Reading, dowloading and trying every method around since yesterday afternoon with no luck. I did replace the .dll you provided but i have a different error now, something like mismatch different files and it shows both files names. I just got this phone from a friend. it shows d801 tmo versión in flashtool so i think he was messing around with any tmo based rom (if exits). So flashtool does not let me flash the phone because of this(Think this is a 801 tmo)
I also tried lg suppor tool but it never download the firmware. It get stuck on downloading firmware or checking phone settings (something like that), I found my cell model on the back on the phone so im pretty sure is a SL980. So what comboof files i can use? Do i still can use the.dll provided? Do i have to rename something?(btw...i did and didnt work).
Any other tip? Did i miss something? I have no phone now so im kinda desperate. Thanks in advance for any help.
Sorry for any mistake, english is not my first language.
I will try ti explain you later what i did to fix this issue
Cant you go in fastboot mode?
Sent from my LG-D801 using xda app-developers app
Alexandercat said:
I will try ti explain you later what i did to fix this issue
Cant you go in fastboot mode?
Sent from my LG-D801 using xda app-developers app
Click to expand...
Click to collapse
No...how can i do it? i read pressing vol+ while connecting usb but i get to dowload. I know in fastboot i can flas img to phone but i cant get in to it
ToledoG28 said:
No...how can i do it? i read pressing vol+ while connecting usb but i get to dowload. I know in fastboot i can flas img to phone but i cant get in to it
Click to expand...
Click to collapse
ok this is what i did to unbrick my phone in your same conditions, in some steps maybe i made some mistakes but i went to the fastboot mode and there i replaced all kernel files of ls980 to fix the issue:
first you have to proceed to back to stock your phone with the T-Mobile USA D80110C_1.kdz :
http://forum.xda-developers.com/showthread.php?t=2432476
now your phone is a full d801, it will boot the system but will be unstable, you must be fast to go to make the developer options and debug your phone, make it on plane and and charging mode, maybe you will be able to do it after some reboots, u must insist.
download the ioroot11 program to root your device, remember always that is unstable, your device will be recognized for not long time, so you have to open the ioroot program often until it recognize your device and root it with the program.
after this step, if your phone is rooted but is still too much ustable to use the adb command (i tried to sideload and push the recovery but it always made me a sideload error), download this program:
http://forum.xda-developers.com/showthread.php?t=2633941
is a simple tool to flash the recovery, it worked in my case, you have to install the recovery of the d801, in my case the philz recovery worked, if everything will be right, you will flash the recovery.
When i was inside the recovery i tried to flash the justin sprint t mobile through the sideload command but it didn't work, same with cm11, i flashed the ls980twrp.zip and when i tried to go to recovery again i was in fastboot.
from fastboot i used the command fastboot erase to erase the partitions: aboot, boot, dbi,laf,misc, persist, recovery, rpm, sbl1, tz.
to erase you must use the command fastboot erase aboot aboot for example, to erase the boot you must repeat boot(fastboot erase boot boot) and so on.
after erased all files i flashed the partitions of ls980:
http://downloads.codefi.re/autoprime/LG/LG_G2/LS980/Stock_Firmware/zv7_partitions
cmd fastboot flash aboot aboot and so on, (i didn't flashed the primaryGPT).
when i flashed all these files i pushed power volume+ and i was in upgrade firmware, so i went back to stock with zv7tot and dll..
it wasn't simple to find a way to back to stock, i guess to made some mistakes but i fixed my issue in this way, i am responsible of what i do with my phone, i cannot guarantee the same results with the others
Alexandercat said:
ok this is what i did to unbrick my phone in your same conditions, in some steps maybe i made some mistakes but i went to the fastboot mode and there i replaced all kernel files of ls980 to fix the issue:
first you have to proceed to back to stock your phone with the T-Mobile USA D80110C_1.kdz :
http://forum.xda-developers.com/showthread.php?t=2432476
now your phone is a full d801, it will boot the system but will be unstable, you must be fast to go to make the developer options and debug your phone, make it on plane and and charging mode, maybe you will be able to do it after some reboots, u must insist.
download the ioroot11 program to root your device, remember always that is unstable, your device will be recognized for not long time, so you have to open the ioroot program often until it recognize your device and root it with the program.
after this step, if your phone is rooted but is still too much ustable to use the adb command (i tried to sideload and push the recovery but it always made me a sideload error), download this program:
http://forum.xda-developers.com/showthread.php?t=2633941
is a simple tool to flash the recovery, it worked in my case, you have to install the recovery of the d801, in my case the philz recovery worked, if everything will be right, you will flash the recovery.
When i was inside the recovery i tried to flash the justin sprint t mobile through the sideload command but it didn't work, same with cm11, i flashed the ls980twrp.zip and when i tried to go to recovery again i was in fastboot.
from fastboot i used the command fastboot erase to erase the partitions: aboot, boot, dbi,laf,misc, persist, recovery, rpm, sbl1, tz.
to erase you must use the command fastboot erase aboot aboot for example, to erase the boot you must repeat boot(fastboot erase boot boot) and so on.
after erased all files i flashed the partitions of ls980:
http://downloads.codefi.re/autoprime/LG/LG_G2/LS980/Stock_Firmware/zv7_partitions
cmd fastboot flash aboot aboot and so on, (i didn't flashed the primaryGPT).
when i flashed all these files i pushed power volume+ and i was in upgrade firmware, so i went back to stock with zv7tot and dll..
it wasn't simple to find a way to back to stock, i guess to made some mistakes but i fixed my issue in this way, i am responsible of what i do with my phone, i cannot guarantee the same results with the others
Click to expand...
Click to collapse
ok...i will try that...i was able to flash twrp and get to recovery
ToledoG28 said:
ok...i will try that...i was able to flash twrp and get to recovery
Click to expand...
Click to collapse
if you can go to twrp you can flash with adb, i wasn't able to go in recovery, just download with the d801 firmware, that explains why it was complicated
Thanks for all your help. I was able to erase everything via fastboot and my phone fell down and power off before flashing img and now is dead. I have a big blue pitbull inside the house who makes the disaster.,.lol. i just got one white from a friend for $160. Im sure this thread can help any people with a brick device. Thanks again.
Sent from my unknown using xda premium
Pity, dogs like smartphones :/
Inviato dal mio LG-LS980 utilizzando Tapatalk
but i get no adb?
what ToledoG28 said is exactly what I have been attempting to do to correct this issue but I am facing an additional issue. I had got to the point where I am running the d800 version on my ls980 and it is unstable as you said. I believed I had found a way out but when I connect to the computer no matter what I do I get no adb for no reason as far as I can tell.
makes no sense at all to me as I had adb before all this perfectly fine.
try this
boxorandyos said:
what ToledoG28 said is exactly what I have been attempting to do to correct this issue but I am facing an additional issue. I had got to the point where I am running the d800 version on my ls980 and it is unstable as you said. I believed I had found a way out but when I connect to the computer no matter what I do I get no adb for no reason as far as I can tell.
makes no sense at all to me as I had adb before all this perfectly fine.
Click to expand...
Click to collapse
you gotta go do device drivers and your device will show up as some unknown device so you install the adb devices for your phone and then you should get adb to show.
Alexandercat said:
same issue,
try to replace the dll file with this one:
http://forum.xda-developers.com/attachment.php?attachmentid=2553245&d=1391282521
good luck
Click to expand...
Click to collapse
The magic dll, worked for me d802 A very big thanks to you man. I spend hours trying to fix it all it needed was a magic dll from a MagicMan. Thank you again million times.

Help really need here, big issues

Hello to everybody, so i was thinking my nakasi was really dead this time, the last thing i did was flashing a 5.1.1 rom next when i rebooted got stuck on lolipop boot loop so i restarted the tablet
manually to access the recovery, and to my awe, i couldn't no more access the recovery ! (latest twrp) tried again and again nothing, no recovery no bootloader, can't start the OS
always stuck on google logo with the options above, start, bootloader, recovery etc, today i realized i could access the bootloader and fastboot mode (ADB recognize my device when i type fastboot devices)
so i tried flashing stock image and stuff with no luck, tried many stock roms, tried wug's toolkit and the flash all.bat still no luck, i get all kind of error messages here is a screenshot, help is really appreciated if there is anything i can do to save it :
View attachment 3305126
the problem seems to be that i can't write the things i send to the tablet via ADB, tried the NVflash recovery today and got :
View attachment 3306049
Have you tried not imputing the full file address as you have the emulator already running from that location.
So recovery command would be.
Fastboot flash recovery "name of recovery Img file here"
Just make sure that the image file is in the platform-tools folder.
Probably not your issue but its going to save you some typing.
Good luck
gaosphappy said:
Have you tried not imputing the full file address as you have the emulator already running from that location.
So recovery command would be.
Fastboot flash recovery "name of recovery Img file here"
Just make sure that the image file is in the platform-tools folder.
Probably not your issue but its going to save you some typing.
Good luck
Click to expand...
Click to collapse
Thank you for the tip I'll certainly use it, but i don't think it is the culprit since as you can see in the screenshots
the files get sent successfully but cannot be written, my bootloader is unlocked by the way
Homurato said:
Thank you for the tip I'll certainly use it, but i don't think it is the culprit since as you can see in the screenshots
the files get sent successfully but cannot be written, my bootloader is unlocked by the way
Click to expand...
Click to collapse
Did you try the latest factory image? I noticed you are flashing a very old bootloader, possibly the first one? 4.23 is the current version.
Where is flatline_grouper.img coming from? I've never seen that.
adomol said:
Did you try the latest factory image? I noticed you are flashing a very old bootloader, possibly the first one? 4.23 is the current version.
Where is flatline_grouper.img coming from? I've never seen that.
Click to expand...
Click to collapse
Hello kind sir, of course at first i tried the 5.1.1 full factory image with the NRT toolkit and got the same writing errors next i tried many bootloaders
(one of them found it here as a 100% working bootloader) the Flatline is the recovery of the NVflash tool where you can access it to unbrick full bricked N7s
if you got blobs.bin of your N7 backed up (clearly not my case)
the flashing writing error i get it with everything i try to flash, recoverys bootloader system etc
when i send them with the flash all command they got sent to the tablet okay, but when writing i get the errors
i don't know but there is a small informations if that can help, before it broke my system was in EXT4 and all the rest in F2FS
It's entirely possible your memory has failed. I'm reading more and more people running into corrupted memory issues.
You can get a replacement motherboard cheap on eBay if nothing else works.
fwayfarer said:
It's entirely possible your memory has failed. I'm reading more and more people running into corrupted memory issues.
You can get a replacement motherboard cheap on eBay if nothing else works.
Click to expand...
Click to collapse
I'm still hoping for a software solution since my fastboot works fine, I'll let the motherboard solution my last i guess
Hello some news about the still staggering situations : when the tablet is off and i put the charger i get the battery refiling animation ! so that mean the bootloader isn't broken
and i still can access fastboot mode, even when i push a bootloader i get a signature match message, but the problem is still that the things i push can't be written as i'm still getting a :
FAILED <Remote: <FileWriteFailed>> changed usb cables, changed ports, the last time the tablet was working i had the system on EXT4 and the rest on F2FS, maybe if i can convert everything to EXT4 ?

[Q] Can't get back to stock

I'm having trouble finding a way to fix this:
I have the same problem as this guy
http://forum.xda-developers.com/show....php?t=2704519
I applied a one click root+twrp. Something went wrong and soft bricked my phone.
It boot loops into twrp but twrp's gui is unresponsive. Have got it to factory reset in twrp get but i get "can't mount /data" in red text. I can get into download mode. TOT flash to stock method kind of works. It runs through the process very fast and flash tool returns:
skip system partition
Skip aboot Partition
Skip rpm Partition
Skip boot Partition
Skip tz Partition
Skip misc Partition
Skip persist Partition
skip cache partition
est... for rest of partitions
Finishes the process and phone reboots back into boot loop to broken twrp
the tot and dll files are fine cuz i used them to flash it earlier when i got stuck
I can't get the KDZ method to work. Does anyone know what's wrong
Is there a another way to replace the partitions manually? maybe a linux way? I'm still very noob, hitting a very hard learning curve
KillerMOth said:
I'm having trouble finding a way to fix this:
I have the same problem as this guy
http://forum.xda-developers.com/show....php?t=2704519
I applied a one click root+twrp. Something went wrong and soft bricked my phone.
It boot loops into twrp but twrp's gui is unresponsive. Have got it to factory reset in twrp get but i get "can't mount /data" in red text. I can get into download mode. TOT flash to stock method kind of works. It runs through the process very fast and flash tool returns:
skip system partition
Skip aboot Partition
Skip rpm Partition
Skip boot Partition
Skip tz Partition
Skip misc Partition
Skip persist Partition
skip cache partition
est... for rest of partitions
Finishes the process and phone reboots back into boot loop to broken twrp
the tot and dll files are fine cuz i used them to flash it earlier when i got stuck
I can't get the KDZ method to work. Does anyone know what's wrong
Is there a another way to replace the partitions manually? maybe a linux way? I'm still very noob, hitting a very hard learning curve
Click to expand...
Click to collapse
I don't know how to help you, i can only fix a bricked phone if I have TWRP working..........
But here's a tip, once you fix the phone use IOroot for rooting and AutoRec for TWRP, there is no way you can brick it that way
KillerMOth said:
I'm having trouble finding a way to fix this:
I have the same problem as this guy
http://forum.xda-developers.com/show....php?t=2704519
I applied a one click root+twrp. Something went wrong and soft bricked my phone.
Is there a another way to replace the partitions manually? maybe a linux way? I'm still very noob, hitting a very hard learning curve
Click to expand...
Click to collapse
If you are able to boot into FASTBOOT you may try to manually flash partitions...
4Freedom said:
If you are able to boot into FASTBOOT you may try to manually flash partitions...
Click to expand...
Click to collapse
Yes, I saw few forum posts on doing that.
How can i get into fastboot? Is this possible manually??
KillerMOth said:
Yes, I saw few forum posts on doing that.
How can i get into fastboot? Is this possible manually??
Click to expand...
Click to collapse
Make sure you have installed the last version of d802 driver(search on lg website)
Install "minimal adb and fastboot" search on google or on xda than open windows cmd and type
Code:
cd FOLDER
With folder i mean the path where you have installed adb
Now you can type
Code:
adb devices
If it show something like a number or something that identify your phone
You can type
Code:
adb reboot bootloader
Your phone will be into fastboot mode

[SOLVED]Unbootable D802. - Only TWRP and Download available.

Hi.
Bit of a fail of a day for me, as i seem to have bricked my D802 G2.
It started after flashing the latest dorimanx kernel over CloudyG2 3.3.. Afterwards i was stuck in fastboot mode.
After lots of messing around, i used the TOT method to recover and get back to stock..
Then i used srktools to root, and autorec to get TWRP installed. However after the reboot i was stuck with a black screen bootloop, stupidly i then sideloaded and flashed cloudy over the top..
I can still get into TWRP and Download mode, however TWRP cannot mount any of the partitions - so I attempted to re-flash stock using both TOT and KDZ method however nither work (TOT method just skips the partitions for some reason)
UPDATE: Managed to get it fixed - after trying many things including the 9006 QHUSB fix in SRKtools this adb patch finally allowed me to reflash a stock rom:
http://forum.xda-developers.com/lg-g2/development-d802/fix-lg-flash-tool-stuck-2-t3031112
hi, you could try to get in QHSUSB MODE and then flash partitions using linux's dd command
I do NOT recommend this idea, there could a better solution
you should backup all your current partitions (or important ones), dd will do the trick
force enter to QHSUSB: http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
how to flash partitions: http://forum.xda-developers.com/showthread.php?t=2582142
link for 10b 16GB d802 partitions: http://downloads.codefi.re/autoprime/LG/LG_G2/D802/Stock_Firmware/10b_EUR_16G_partitions
lenesul said:
hi, you could try to get in QHSUSB MODE and then flash partitions using linux's dd command
I do NOT recommend this idea, there could a better solution
you should backup all your current partitions (or important ones), dd will do the trick
force enter to QHSUSB: http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
how to flash partitions: http://forum.xda-developers.com/showthread.php?t=2582142
link for 10b 16GB d802 partitions: http://downloads.codefi.re/autoprime/LG/LG_G2/D802/Stock_Firmware/10b_EUR_16G_partitions
Click to expand...
Click to collapse
Thanks - I think the phone has been in QHUSB mode a couple of times - there have been some occasions where many drive letters have appeared in windows when the phone reboots attached to USB.. I will see if i can get it to happen again then connect to a linux machine.
Ive also just noticed that when the phone is stuck on the LG bootscreen and connected to USB, its showing up as a ADB device and i can run ADB commands through it.
NeoVR said:
Ive also just noticed that when the phone is stuck on the LG bootscreen and connected to USB, its showing up as a ADB device and i can run ADB commands through it.
Click to expand...
Click to collapse
i don't know if ADB could help you if TWRP can't mount partitions
I remember there was a command to boot to a *.img sent from PC, but I don,t know if it was fastboot or adb (pretty sure it was fastboot)...
what's your twrp version?
have you tried the new LGUP?
lenesul said:
i don't know if ADB could help you if TWRP can't mount partitions
I remember there was a command to boot to a *.img sent from PC, but I don,t know if it was fastboot or adb (pretty sure it was fastboot)...
what's your twrp version?
have you tried the new LGUP?
Click to expand...
Click to collapse
Its fastboot that can send img files (im trying to avoid that as it would mean destroying download mode)
twrp is 2.7.0.0
Ive also tried LGUP, it detects the phone but cant detect the version - i cant find where to edit build.prop to force it to recognise.
Update: ITS FIXED!
In the end it was this that fixed it: http://forum.xda-developers.com/lg-g2/development-d802/fix-lg-flash-tool-stuck-2-t3031112
as i had adb access i thought id give it a go, and the TOT flashed correctly after.
Many thanks everyone!

Huawei Ascend XT2 Stock image Fix Brick With Unlocked Bootloader Access

OK so this is where i tell you if you brick your phone and try this and it makes it worse i am not to blame. this has worked on three different phones that i have used no problem.That being said lets dive on in.
ONLY FOR THE H1711!!!!
Downloads (move them all to sd card root)
UPDATED USERDATA thank aslezak for that
https://uploadfiles.io/n5g32 and that
http://www.mediafire.com/file/gybldrcgw8h6x2w/twrp_first%5B1%5D.img you can thank yuweng for that but it is not fully working yet link will be replaced once fully working is released
Steps
get phone to fastboot mode must be unlocked then use the twrp recovery from downloads via this command on your adb/fastboot installed computer connected to phone :
Code:
fastboot flash recovery twrp_first[1].img
Reboot phone to recovery
go to wipe advanced wipe wipe data and system only
go back to home menu open advanced then terminal
enter this command exactly :
Code:
dd if=/external_sd/userdata.img.bz2 | bzip2 -dc | dd of=/dev/block/bootdevice/by-name/userdata
that will take a loooonnnnnnggggg time approximately 30-45 min
after it shows # in terminal again do this command :
Code:
dd if=/external_sd/system.img.bz2 | bzip2 -dc | dd of=/dev/block/bootdevice/by-name/system
reboot and it should take a loooonnnngggg time but eventually it will finish and you restored if not try asking some of the devs for pointers:laugh::fingers-crossed::highfive:
Make sure you thank everyone who helped aslezak gave me the commands and the userdata img as well as the system img yuweng provided the first semi working twrp (and a few later that are experimental)
if you want root check this thread https://forum.xda-developers.com/huawei-ascend-xt/help/huawei-ascend-xt2-h1711-t3689411/post75115521#post75115521
Your first link for the userdata image says file not found when you go to that link.
UPDATED USERDATA
freedomwarrior said:
Your first link for the userdata image says file not found when you go to that link.
Click to expand...
Click to collapse
Sim unlock
Hey guys,
has anyone managed to find a way to simunlock this phone? I bought one on blackfriday for $49 and since then its been sitting in my closet because it does not accept any other network's sim.
aslezak said:
UPDATED USERDATA
Click to expand...
Click to collapse
That one don't work either
FULL ROOT... ON MY HUAWEI XT2!! Twrp supersu and custom rom !!!
Sent from my HUAWEI H1711 using XDA Labs
The problem with this seems to be, at least for me, that a .bz2 file is not recognized by the recovery as an installable zip.
The dd trick worked for me, but the system image here, is not full stock. IT seems to have a mix of super_su and magisk in it.
Root is working, but I can't seem to mount system as r/w
So trying to figure this out. I used this image to do a restore, and my phone was rooted with magisk.
First time a program tried root, it said that super su was installed. When I went to another one, it said that magisk was installed.
Anyrate, at one time I was able to mount system r/w and make changes. Now it seems that I can't for whatever reason. I don't know exactly how I got it
to the state to be able to modify the system.
I actually pulled an entire copy of the rom at one time, with a dd command. Of course that can't be reflashed from twrp. But I'd like to be able to mount it somehow on a pc so I could do a stringsearch for all files that have an ro, in them to find the master files where the filesystems are mounted, and edit those....
crashburn833 said:
OK so this is where i tell you if you brick your phone and try this and it makes it worse i am not to blame. this has worked on three different phones that i have used no problem.That being said lets dive on in.
ONLY FOR THE H1711!!!!
Downloads (move them all to sd card root)
UPDATED USERDATA thank aslezak for that
https://uploadfiles.io/n5g32 and that
http://www.mediafire.com/file/gybldrcgw8h6x2w/twrp_first%5B1%5D.img you can thank yuweng for that but it is not fully working yet link will be replaced once fully working is released
Steps
get phone to fastboot mode must be unlocked then use the twrp recovery from downloads via this command on your adb/fastboot installed computer connected to phone :
Code:
fastboot flash recovery twrp_first[1].img
Reboot phone to recovery
go to wipe advanced wipe wipe data and system only
go back to home menu open advanced then terminal
enter this command exactly :
Code:
dd if=/external_sd/userdata.img.bz2 | bzip2 -dc | dd of=/dev/block/bootdevice/by-name/userdata
that will take a loooonnnnnnggggg time approximately 30-45 min
after it shows # in terminal again do this command :
Code:
dd if=/external_sd/system.img.bz2 | bzip2 -dc | dd of=/dev/block/bootdevice/by-name/system
reboot and it should take a loooonnnngggg time but eventually it will finish and you restored if not try asking some of the devs for pointers:laugh::fingers-crossed::highfive:
Make sure you thank everyone who helped aslezak gave me the commands and the userdata img as well as the system img yuweng provided the first semi working twrp (and a few later that are experimental)
if you want root check this thread https://forum.xda-developers.com/huawei-ascend-xt/help/huawei-ascend-xt2-h1711-t3689411/post75115521#post75115521
Click to expand...
Click to collapse
the system.img requires a monthly membership, could an updated link using something like mega or mediafire be created please?
one789 said:
FULL ROOT... ON MY HUAWEI XT2!! Twrp supersu and custom rom !!!
Sent from my HUAWEI H1711 using XDA Labs
Click to expand...
Click to collapse
what custom rom?
HELP PLEEEASE! Bricked h1711
Badly need mmcblk0.img for H1711! Had TWRP and phone was rooted but I screwed up and flashed a wrong IMG. Now I have the dreaded QHSUSB_BULK issue. Nothing but a black screen and a blue light. I googled "How to fix QHSUSB_BULK or Qualcomm HS-USB QDLoader 9008 error" and went on forum.hovatek.com where it said "This error is an indication that the phone is hard bricked due to a corrupted Bootloader. It could occur randomly or after you make a change to the phone, causing the phone to go into Qualcomm Emergency Download Mode." It also stated that I could fix it by creating a bootable SD card using the phone's original mmcblk0.img file using a program called Win32DiskImager. I don't have mmcblk0.img and I can't boot into recovery or fastboot. PLEASE PLEASE HELP!!!! Also first two links in OP's post don't work. Any files or advise you can contribute would be GREATLY appreciated! THANKS!
mmcblk0.img would contain all phone partitions including those with personal information like IMEI number and the /data partition that should not be shared.
Nobody should be sharing that without understanding it contains their IMEI number and other possibly personal information in /data and I'm sure it would be at least 8-10GB.
And what would you do with the file anyway if you can't get into fastboot or recovery?
Whit3Rabbit said:
Badly need mmcblk0.img for H1711! Hard bricked Dreaded QHSUSB_BULK issue. Need mmcblk0.img PLEASE PLEASE HELP!!!! I've lost recovery and fastboot! Nothing but a black screen and a blue light.
Click to expand...
Click to collapse
divineBliss said:
mmcblk0.img would contain all phone partitions including those with personal information like IMEI number and the /data partition that should not be shared.
Nobody should be sharing that without understanding it contains their IMEI number and other possibly personal information in /data and I'm sure it would be at least 8-10GB.
And what would you do with the file anyway if you can't get into fastboot or recovery?
Click to expand...
Click to collapse
What do you recommend I do? All I have is a black screen and a blue light? thank you btw
If it won't go into fastboot mode and won't boot, I think only Huawei can fix it.
Whit3Rabbit said:
What do you recommend I do? All I have is a black screen and a blue light? thank you btw
Click to expand...
Click to collapse
divineBliss said:
If it won't go into fastboot mode and won't boot, I think only Huawei can fix it.
Click to expand...
Click to collapse
That's what I was afraid of Thank you for the quick response.
Whit3Rabbit said:
Badly need mmcblk0.img for H1711! Had TWRP and phone was rooted but I screwed up and flashed a wrong IMG. Now I have the dreaded QHSUSB_BULK issue. Nothing but a black screen and a blue light. I googled "How to fix QHSUSB_BULK or Qualcomm HS-USB QDLoader 9008 error" and went on forum.hovatek.com where it said "This error is an indication that the phone is hard bricked due to a corrupted Bootloader. It could occur randomly or after you make a change to the phone, causing the phone to go into Qualcomm Emergency Download Mode." It also stated that I could fix it by creating a bootable SD card using the phone's original mmcblk0.img file using a program called Win32DiskImager. I don't have mmcblk0.img and I can't boot into recovery or fastboot. PLEASE PLEASE HELP!!!! Also first two links in OP's post don't work. Any files or advise you can contribute would be GREATLY appreciated! THANKS!
Click to expand...
Click to collapse
What is the link to the info you found?
I have the image you need, but it is 15 GIGs in size, and there is no practical way to send that. I also have a system image, and a boot image with magisk in it, as per the OP.
P.M. me.
I don't see how you can recover this if you don't have recovery or fastboot, and can't boot into the phone. If the bootloader is corrupted, well I just don't know.
Can you get into twrp?
You do know that there are two recoveriess, one erecovery and another recovery.
It seems that POWER and VOL up may get you into one, and POWER and VOL down may get you into another one.
NOTE: I KNOW you can't flash the image via fastboot, cause I tried it. it is just to big.
The files are all to big to post here....
https://nofile.io/f/2sfHn8teU1s/system.img.bz2 I put this up 6 days ago for someone else. I don't know how long the link is good for.
This is the system image from the non-working link. You will need to untar it.
https://nofile.io/f/2sfHn8teU1s/system.img.bz2 <<<<<<<<<< file from Original Post
https://nofile.io/f/vTRffT3CM0s/erecovery.zip <<<<<<<<<< erecovery is same as stock recovery
https://nofile.io/f/3DRA4bYjdsq/twrp-xt2.7z <<<<<<<<<< Hweng's original twrp
https://nofile.io/f/uAET5bTqQVk/patched_boot.zip <<<<<< bootloader patched with magisk for a root that does not touch the system partition.
I'll try to put the 15 gig mmblockp0 up here if it will take it, but it is at the office.
I hope this helps.
I now also have a virgin system image, stock. The image given above appears to also have supersu installed it int.
at least it has a su in the system image. Where magisk, just patches the boot image as I understand it.
Any luck on that stock system.img? I formatted mine like an idiot and now sitting on a phone with no OS
same as above, i will even take the rooted system.img i have all other files needed.
I'm a little bit of a noob at all of this but could someone explain to me how they got twrp and root on their xt2? I can really only process step by step and I haven't found that anywhere yet. I'm getting this phone later today so it'd be really cool to get root on it
littletech said:
I'm a little bit of a noob at all of this but could someone explain to me how they got twrp and root on their xt2? I can really only process step by step and I haven't found that anywhere yet. I'm getting this phone later today so it'd be really cool to get root on it
Click to expand...
Click to collapse
step by step root > https://forum.xda-developers.com/hu...ooting-restoring-huawei-elate-h1711z-t3764391
the files for root are the same for the Elate and the XT2
Blue light black screen fix
Whit3Rabbit said:
That's what I was afraid of Thank you for the quick response.
Click to expand...
Click to collapse
​My device suffered the same fate, only a blue light black screen unable to enter boot or recovery. I slowly removed the back cover using my fingernails and removed the two screws holding the metal plate above battery on the right. Popped the left most plug to disconnect the power flow and allow phone to power off completely. Be careful not to touch any of the metal near the plug or you will short. I plugged it back in and held volume down while I inserted USB connected to computer. Tada!! Back in action fastboot ready... So OK now what?? I can't seem to be able to flash an update. Zip just keeps saying failed to load, and system image is too big. Can someone point me to the correct files I need to get her working again? Thanks in advance.

Categories

Resources