Database Users

HELP! Kinda broke my G530T! (PIT file would help)

Hey, i'm not sure how i'm supposed to start this, so i'll just explain my problem.
I have a (real pain-in-the-neck to root) Galaxy Grand Prime G530T. I decided to root and found this: forum.xda-developers.com/grand-prime/development/kernel-root-root-sm-g530t-5-1-1-t3203476. So I flashed it with Odin. It worked! Until I rebooted, that is. It was (is) stuck in a bootloop (no ADB, no CWM or TWRP, stock recovery, but I can get to odin/download mode). I found the stock ROM on sammobile and tried to flash it. It said there was an error when it got to the "system.img.ext4", saying it was an "invalid ext4 image" and something like "445989734 < 43058000", I don't know exactly. I extracted the boot.img and flashed it and now my phone boots, into a bootloop. I know it's because of the system.img.ext4 and I'd love to know how to fix it. I've heard that if I can get the PIT file it might work. I know how to get the PIT file (run "dd if=/dev/block/mmcblk0 of=/sdcard/out.pit bs=8 count=580 skip=2176" as root), but I can't get it (can't boot, device doesn't appear in ADB).
If anyone can get me the PIT file, that's all I need (8GB phone btw), I can figure the rest out on my own (just run run "dd if=/dev/block/mmcblk0 of=/sdcard/out.pit bs=8 count=580 skip=2176" as root to get it).

facekapow said:
Hey, i'm not sure how i'm supposed to start this, so i'll just explain my problem.
I have a (real pain-in-the-neck to root) Galaxy Grand Prime G530T. I decided to root and found this: forum.xda-developers.com/grand-prime/development/kernel-root-root-sm-g530t-5-1-1-t3203476. So I flashed it with Odin. It worked! Until I rebooted, that is. It was (is) stuck in a bootloop (no ADB, no CWM or TWRP, stock recovery, but I can get to odin/download mode). I found the stock ROM on sammobile and tried to flash it. It said there was an error when it got to the "system.img.ext4", saying it was an "invalid ext4 image" and something like "445989734 < 43058000", I don't know exactly. I extracted the boot.img and flashed it and now my phone boots, into a bootloop. I know it's because of the system.img.ext4 and I'd love to know how to fix it. I've heard that if I can get the PIT file it might work. I know how to get the PIT file (run "dd if=/dev/block/mmcblk0 of=/sdcard/out.pit bs=8 count=580 skip=2176" as root), but I can't get it (can't boot, device doesn't appear in ADB).
If anyone can get me the PIT file, that's all I need (8GB phone btw), I can figure the rest out on my own (just run run "dd if=/dev/block/mmcblk0 of=/sdcard/out.pit bs=8 count=580 skip=2176" as root to get it).
Click to expand...
Click to collapse
i know this isnt your model, but these guys seem helpful in finding some pits. maybe ask there.

any luck?
facekapow said:
Hey, i'm not sure how i'm supposed to start this, so i'll just explain my problem.
I have a (real pain-in-the-neck to root) Galaxy Grand Prime G530T. I decided to root and found this: forum.xda-developers.com/grand-prime/development/kernel-root-root-sm-g530t-5-1-1-t3203476. So I flashed it with Odin. It worked! Until I rebooted, that is. It was (is) stuck in a bootloop (no ADB, no CWM or TWRP, stock recovery, but I can get to odin/download mode). I found the stock ROM on sammobile and tried to flash it. It said there was an error when it got to the "system.img.ext4", saying it was an "invalid ext4 image" and something like "445989734 < 43058000", I don't know exactly. I extracted the boot.img and flashed it and now my phone boots, into a bootloop. I know it's because of the system.img.ext4 and I'd love to know how to fix it. I've heard that if I can get the PIT file it might work. I know how to get the PIT file (run "dd if=/dev/block/mmcblk0 of=/sdcard/out.pit bs=8 count=580 skip=2176" as root), but I can't get it (can't boot, device doesn't appear in ADB).
If anyone can get me the PIT file, that's all I need (8GB phone btw), I can figure the rest out on my own (just run run "dd if=/dev/block/mmcblk0 of=/sdcard/out.pit bs=8 count=580 skip=2176" as root to get it).
Click to expand...
Click to collapse
ive got the same exact problem for the same model number. its so frustrating...ive been searching for days for that pit file online. guess im gonna just have to buy a new phone. oh well at least i learned a few things as what not to do to my phone.

really need that pit file if someone can get it.

facekapow said:
Hey, i'm not sure how i'm supposed to start this, so i'll just explain my problem.
I have a (real pain-in-the-neck to root) Galaxy Grand Prime G530T. I decided to root and found this: forum.xda-developers.com/grand-prime/development/kernel-root-root-sm-g530t-5-1-1-t3203476. So I flashed it with Odin. It worked! Until I rebooted, that is. It was (is) stuck in a bootloop (no ADB, no CWM or TWRP, stock recovery, but I can get to odin/download mode). I found the stock ROM on sammobile and tried to flash it. It said there was an error when it got to the "system.img.ext4", saying it was an "invalid ext4 image" and something like "445989734 < 43058000", I don't know exactly. I extracted the boot.img and flashed it and now my phone boots, into a bootloop. I know it's because of the system.img.ext4 and I'd love to know how to fix it. I've heard that if I can get the PIT file it might work. I know how to get the PIT file (run "dd if=/dev/block/mmcblk0 of=/sdcard/out.pit bs=8 count=580 skip=2176" as root), but I can't get it (can't boot, device doesn't appear in ADB).
If anyone can get me the PIT file, that's all I need (8GB phone btw), I can figure the rest out on my own (just run run "dd if=/dev/block/mmcblk0 of=/sdcard/out.pit bs=8 count=580 skip=2176" as root to get it).
Click to expand...
Click to collapse
Just flash stock firmware with KIES to get back to stock

please ! We really need this pit file. If somebody can help. I have the same problem

Here it is.
I have a link to the pit file.

codyhaugland said:
I have a link to the pit file.
Click to expand...
Click to collapse
ok but where

I need help i jus got the phone on monday
facekapow said:
Hey, i'm not sure how i'm supposed to start this, so i'll just explain my problem.
I have a (real pain-in-the-neck to root) Galaxy Grand Prime G530T. I decided to root and found this: forum.xda-developers.com/grand-prime/development/kernel-root-root-sm-g530t-5-1-1-t3203476. So I flashed it with Odin. It worked! Until I rebooted, that is. It was (is) stuck in a bootloop (no ADB, no CWM or TWRP, stock recovery, but I can get to odin/download mode). I found the stock ROM on sammobile and tried to flash it. It said there was an error when it got to the "system.img.ext4", saying it was an "invalid ext4 image" and something like "445989734 < 43058000", I don't know exactly. I extracted the boot.img and flashed it and now my phone boots, into a bootloop. I know it's because of the system.img.ext4 and I'd love to know how to fix it. I've heard that if I can get the PIT file it might work. I know how to get the PIT file (run "dd if=/dev/block/mmcblk0 of=/sdcard/out.pit bs=8 count=580 skip=2176" as root), but I can't get it (can't boot, device doesn't appear in ADB).
If anyone can get me the PIT file, that's all I need (8GB phone btw), I can figure the rest out on my own (just run run "dd if=/dev/block/mmcblk0 of=/sdcard/out.pit bs=8 count=580 skip=2176" as root to get it).
Click to expand...
Click to collapse
Excuse me can you plz share what rom or firmware you used the first time then it went into a boot loop because every firmware i use goes into a error. Something about ext4 error then my phone says volume size too big but the the numbers on the left are smaller than the right i think with that firmware you used and it got stuck in a boot loop i think it can be fixed by going into recovery mode and wiping cache and factory resetting it. My frp is still on too i dont know how to take it off i think i can get some where with that firmware you used i reallly need it. I have a samsung galaxy grand prime SM-G530T or SM-G530T1 i think they the same I guess

I have extracted my PIT and posted it in this thread along with a detailed tutorial and explanation.
http://forum.xda-developers.com/grand-prime/general/extracted-pit-file-download-sm-g530t-t-t3341242
Hopefully you guys can save your phones.
Reguards

Need help, friend tried to downgrade from N beta and hard bricked phone.

I need someone with a rooted Sprint Galaxy S7 (NOT EDGE) to dump their boot loader debrick image for me to use to fix a friend's phone. Using this zip, you should be able to make one, anyone willing to help out, will be much appreciated.
http://d-h.st/Mui
The tool to dump bootloader.
You can use FlashFire to run the zip, or run the code manually in a terminal emulator.
Code:
su
dd if=/sdcard/debrick.bin of=/dev/block/mmcblk0

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.

Fixing a hardbrick

so i try to unlock the bootloader [GUIDE] Temporary unlock bootloader to flash partitions on Nougat
instead of flashing the emmc_appsboot_service.mbn, I flash prog_emmc_firehose_8937.mbn I've downloaded before.
I didn't see that attachment file in the bottom of the post stupid me!
after executing fastboot reboot-bootloader, my phone gone blank.
I see on Device Manager there's other devices with warning sign QHSUSB__BULK
I updated with Qualcomm driver it changed to Qualcomm HS-USB Diagnostics 900E
I've tried power+vol up, show nothing, QFIL & OST LA doesn't work.
my last effort is tried to boot from external sdcard like in this thread Fixing a bootloader-bricked Galaxy S3
is that posible on nokia 5 TA-1053?
if so, can you guys do me a favor please?
I need that dump file. Thanks in advance.

can you guys who have rooted their phone create .img file please?
Code:
su
busybox dd if=/dev/block/mmcblk0 of=/sdcard/debrick.img bs=1M count=128
and upload it somewhere.
Thanks :crying:

This is exactly what i did.. any news regarding this post....

[Experimental] Recover HardBricked Qualcomm device using sdcard.

Experimental, Not tested.
But if u have hardbricked device u can test it.
So apparently when booting Qualcomm tries to boot internal flash then external and finally OTG, if its mounted, then it gives up 9008 mode or nothing.
However, if we flash the partition layout for our device, it can rework where each partition is on the flash memory and point to it and boot it.
Instructions:
1. Download your device Loader.img or u can create Loader.img from another exact device using cmd, twrp terminal or android terminal using
adb shell
su
dd if=/dev/block/mmcblk0 of=/sdcard/Loader.img bs=1024 count=168960
2. Use Win32 Image Writer to flash the image to a working sdcard, which is same size as your device internal or higher is best.
3.force to your device to fastboot mode by using key combination which apply to your device.
4.if it boot to fastboot, then flash fastboot ROM, or trying to flash twrp.
Contributors:
VK84663
Information:
Statue: Experimental

Reserve

Screenshot

VK84663 said:
Experimental, Not tested.
But if u have hardbricked device u can test it.
So apparently when booting Qualcomm tries to boot internal flash then external and finally OTG, if its mounted, then it gives up 9008 mode or nothing.
However, if we flash the partition layout for our device, it can rework where each partition is on the flash memory and point to it and boot it.
Instructions:
1. Download your device Loader.img or u can create Loader.img from another exact device using cmd, twrp terminal or android terminal using
adb shell
su
dd if=/dev/block/mmcblk0 of=/sdcard/Loader.img bs=1024 count=168960
2. Use Win32 Image Writer to flash the image to a working sdcard, which is same size as your device internal or higher is best.
3.force to your device to fastboot mode by using key combination which apply to your device.
4.if it boot to fastboot, then flash fastboot ROM, or trying to flash twrp.
Contributors:
VK84663
Information:
Statue: Experimental
Click to expand...
Click to collapse
Can u tell me in
dd if=/dev/block/mmcblk0 of=/sdcard/Loader.img bs=1024 count=168960
why sector count is 168960 and not 172032?
{(303103 - 131072) + 1}= 172032
Or am i making some mistake?
I want to know why are we taking 168960 sectors? Why not more or why not less?
If u think this is very noob question, plz enlighten me