1. In regards to recently combined carrier specific root forums, if your device forum was affected, please see this poll/thread!

OK to delete PG05IMG.zip file after successful root?


  1. cmotion

    cmotion Well-Known Member

    Hello fellow Thunderboltees,

    So I successfully rooted my Thunderbolt (yay!) after trying multiple times with my old-ass Macbook (OS v_10.4.11) and having NO luck, despite the very helpful, patient people at the Thunderbolt #root help chat site, and finally tried on my girlfriend's much newer, much nicer Mac and everything went great. Now I was wondering about that PG05IMG.zip file that's on my sd card... should I delete it? Leave it? Does it matter? I'm just thinking if I don't need it, and it could possibly cause any problems I'd rather just get rid of it, but I'm not sure if it's necessary to keep on there for any reason? Anyway, thanks for any help/insight.

    Advertisement
  2. bjanow

    bjanow Well-Known Member

    Delete it.

    Edit: (as per scotty) Now!
    cmotion likes this.
  3. scotty85

    scotty85 Guides Guide

    what he said. ^

    not only is it ok to delete it,but its really important that you SHOULD delete it. if you left this file there,it would find it,go thru that whole check process,and ask you to update every time you boot into hboot.

    if you accidentally told it yes,youd need to perform the steps again to get root and su.
    cmotion likes this.
  4. cmotion

    cmotion Well-Known Member

    Thanks you two. Deleted!
  5. cmotion

    cmotion Well-Known Member

    So I'm just curious, I deleted the PG0IMG.zip file using ES file explorer, then I downloaded Root Explorer and saw the file again. Did I not really delete it the first time??
  6. bjanow

    bjanow Well-Known Member

    Prob not. Delete it with root explorer and it will be gone.
  7. cmotion

    cmotion Well-Known Member

    That's really weird that it doesn't show up in EStrongs at all...? Like when I deleted it the first time, it didn't actually delete but just got hidden. Oh well. Double-deleted!
  8. SpaceBolt

    SpaceBolt Well-Known Member

    Iv'e rooted my TBolt already and have installed BAMF, but I still don't know what PG05IMG.zip is exactly. Is that just the name of the file that the TBolt looks for upon boot up or something?
  9. WormDoes

    WormDoes Well-Known Member

    PG05IMG.zip is what you name a file that can only be flashed in hboot. It's the only file that hboot will search for and install. Like others have said above it's imperative that you remove this file after you use it. That way every time you enter hboot you're not prompted to install this file.
    SpaceBolt likes this.
  10. Rick607

    Rick607 Well-Known Member

    I like to rename it so that I have the radio on my phone in case I need to reflash.. I usually rename it to something like (MR2)PG05IMG.zip so that I can identify it later.
    lgldrgdlr likes this.
  11. SpaceBolt

    SpaceBolt Well-Known Member

    This is probably the smarter move - to just rename the files and leave them there. I've deleted all of mine but will probably make a habit of just renaming them in the future.
  12. sm0ked

    sm0ked Member

    I have just flashed my second ROM and radio...


    for what ever reason my computer is not seeing my SD card... Thoughts? I would like to go in and take out my MR2 file (PG05IMG.zip)
  13. jcnyc

    jcnyc Well-Known Member

    Ya I prefer to just rename it just incase I ever needed to flash a different radio. I just rename it PG01IMG_mr2OTA.zip or something like that and it's all good. If you ever needed to reflash your radio, just go into any file explorer and take the _mr2OTA outta the filename and you're good to go. No need to ever connect to PC again!
  14. scotty85

    scotty85 Guides Guide

    if youre on a GB leak rom now thats par for the course-an issue with the leak and roms based on it. the easiest workaround is to put the phone in internet pass thru mode for a few seconds,and then select disc drive.

    actually this is what i do too... but i change roms like i change my socks so its nice to have the radios on there without havin to trasnfer them.

    another option is to hide them inside another folder. better yet,rename them and hide them inside another folder ;)

    one thing you definately want to delete is the downgrade PG05IMG. you wont ever have need for that(unless youre re-rooting),plus its buggy and unsafe,so just go ahead and delete it. :)
    sm0ked likes this.
  15. sm0ked

    sm0ked Member

    Worked perfect!! Tons of thanks!
  16. m130carbine

    m130carbine Member

    I have put the PG05IMG.zip on the SD card. I rebooted per the instructions. It says that it can't fint an .img file. I chose HBOOT since there was not an options to jut reboot. When I was in the console I had root I thought since the # was there. I used PG05IMG.downgrade first, then copied all the items in the instructions, then the last thing was to take the exploits and rename to PG05IMG.zip so it would flash. I don't think that it ever worked and I don't have root on the Thunderbolt. I have Rom Manager and it tells me that I must have root. Ideas? I sure don't want to brick it.
  17. SpaceBolt

    SpaceBolt Well-Known Member

    Can you show us the exact instructions that you're following, and what step you're at?
    m130carbine likes this.
  18. m130carbine

    m130carbine Member

    Sure, here are the ones that I was following:

    Step 1

    First, download these files:​




    • Downgrade RUU PG05IMG_downgrade.zip (md5sum : aae974054fc3aed275ba3596480ccd5b):
    After downloading these files, please check the md5sums!
    For instructions on how to do so, see:
    Windows: http://helpdeskgeek.com/how-to/check-md5sum-in-windows-7/
    Linux: https://help.ubuntu.com/community/HowToMD5SUM
    Mac OSX: http://ubuntuforums.org/showthread.php?t=373879
    If the md5sums do not match, please stop and re-download that file.
    Step 2

    Note that adb is required.
    Push misc.img, busybox, and psnueter using the following commands:
    adb push psneuter /data/local/
    adb push busybox /data/local/
    adb push misc.img /data/local/
    adb shell chmod 777 /data/local/psneuter
    adb shell chmod 777 /data/local/busybox
    Step 3

    This step will gain temp root and flash the custom misc.img. Run:
    adb shell
    Now the shell should display "$".
    Run:
    /data/local/psneuter
    You will now be kicked out of adb, and adb will restart as root. Let's confirm the md5 of misc.img:
    adb shell
    At this point, the shell should display "#".
    Run:
    /data/local/busybox md5sum /data/local/misc.img
    Output should be "c88dd947eb3b36eec90503a3525ae0de." If it's anything else, re-download the file and try again.
    Now let's write misc.img:
    dd if=/data/local/misc.img of=/dev/block/mmcblk0p17
    exit
    Step 4

    Here you will rename PG05IMG_downgrade.zip as PG05IMG.zip and place it on your SD card. Then, run the following command:
    adb reboot bootloader
    Choose the bootloader option and press power; let the ROM flash. When asked to upgrade, choose yes. Don't freak, it's a long reboot.
    Once done, reboot and delete PG05IMG.zip from your SD card.
    Set up the two part exploit, to gain root and unlock MMC.
    Push wpthis, busybox, and psnueter.
    adb push psneuter /data/local/
    adb push busybox /data/local/
    adb push wpthis /data/local/
    adb shell chmod 777 /data/local/psneuter
    adb shell chmod 777 /data/local/busybox
    adb shell chmod 777 /data/local/wpthis
    Step 5

    Next, enter the following commands:
    adb shell
    /data/local/psneuter
    To unlock eMMC:
    adb shell
    /data/local/wpthis
    exit
    Step 6

    Please pay attention - this is very important. This step involves a small chance of bricking if you mess up.
    To push the eng bootloader:
    adb push hbooteng.nb0 /data/local/
    adb shell
    /data/local/busybox md5sum /data/local/hbooteng.nb0
    If the output does not match "6991368ee2deaf182048a3ed9d3c0fcb" exactly, stop, delete it, and re-download it. Otherwise, continue.

    Now we will write the new bootloader.
    dd if=/data/local/hbooteng.nb0 of=/dev/block/mmcblk0p18
    Confirm proper write:
    /data/local/busybox md5sum /dev/block/mmcblk0p18
    If the output does not match "6991368ee2deaf182048a3ed9d3c0fcb," try again; if it still doesn't work, seek help from chat.andirc.net in channel #thunderbolt. DO NOT REBOOT.
    Now, reboot your phone, rename PG05IMG_stock.zip as PG05IMG.zip and put on your SD card. Then flash it. This will upgrade you to release firmware with an S-OFF bootloader.
    Next, run this command:
    adb reboot bootloader
    Choose the bootloader option, and press power; let the ROM flash. When asked to upgrade, choose yes. Don't freak, it's a long reboot.
    Once done, reboot and delete PB05IM.zip off of your SDCard. You are now fully rooted.
    If you prefer videos, you might be interested in the following, however it uses an older method and will be slightly different:

    Step 6 is where I name the PG05IMG_stock.zip and rename to PG05IMG.zip so the phone will see the file. I have removed the other PG05IMG_downgrade.zip also and replaced it with the PG05IMG.zip (which is PG05IMG_stock.zip file).

    Thanks a bunch.
  19. scotty85

    scotty85 Guides Guide

    You have not successfully written the s-off bootloader,Wich is the first part of step 6
    m130carbine likes this.
  20. m130carbine

    m130carbine Member

    I am re-doing the PG05IMG_stock.zip part again to see if I missed something.
  21. m130carbine

    m130carbine Member

    Below is my output of doing the first parts of Step 6:

    C:\android-sdk-windows\platform-tools>adb shell
    # /data/local/busybox md5sum /data/local/hbooteng.nb0
    /data/local/busybox md5sum /data/local/hbooteng.nb0
    6991368ee2deaf182048a3ed9d3c0fcb /data/local/hbooteng.nb0
    # dd if=/data/local/hbooteng.nb0 of=/dev/block/mmcblk0p18
    dd if=/data/local/hbooteng.nb0 of=/dev/block/mmcblk0p18
    2048+0 records in
    2048+0 records out
    1048576 bytes transferred in 0.485 secs (2162012 bytes/sec)
    # /data/local/busybox md5sum /dev/block/mmcblk0p18
    /data/local/busybox md5sum /dev/block/mmcblk0p18
    6991368ee2deaf182048a3ed9d3c0fcb /dev/block/mmcblk0p18
    #
  22. scotty85

    scotty85 Guides Guide


    That's not your problem,if I am understanding your situation correctly. You need to redo all of step 6,and be very careful cause you can brick your phone here.

    A copy of your session would be helpful.
    m130carbine likes this.
  23. scotty85

    scotty85 Guides Guide

    Did you Reboot before trying the 2nd hboot flash?
    m130carbine likes this.
  24. scotty85

    scotty85 Guides Guide

    If you're going right to hboot without a reboot it will still be s-on and the upgrade wont work
    m130carbine likes this.
  25. m130carbine

    m130carbine Member

    Here I am at the terminal now starting with step 4:

    C:\android-sdk-windows\platform-tools>adb devices
    List of devices attached
    HT11TS012039 device

    C:\android-sdk-windows\platform-tools>adb push psneuter /data/local/
    1666 KB/s (585731 bytes in 0.343s)
    C:\android-sdk-windows\platform-tools>adb push busybox /data/local/
    1663 KB/s (1062992 bytes in 0.624s)
    C:\android-sdk-windows\platform-tools>adb push wpthis /data/local/
    1635 KB/s (679475 bytes in 0.405s)
    C:\android-sdk-windows\platform-tools>adb shell chmod 777 /data/local/psneu
    C:\android-sdk-windows\platform-tools>adb shell chmod 777 /data/local/busyb
    C:\android-sdk-windows\platform-tools>adb shell chmod 777 /data/local/wpthi
    C:\android-sdk-windows\platform-tools>adb shell
    $ /data/local/psneuter
    /data/local/psneuter
    property service neutered.
    killing adbd. (should restart in a second or two)
    C:\android-sdk-windows\platform-tools>adb shell
    # /data/local/wpthis
    /data/local/wpthis
    Build: 25
    Section header entry size: 40
    Number of section headers: 45
    Total section header table size: 1800
    Section header file offset: 0x00014e90 (85648)
    Section index for section name string table: 42
    String table offset: 0x00014cc7 (85191)
    Searching for .modinfo section...
    - Section[16]: .modinfo
    -- offset: 0x00000f80 (3968)
    -- size: 0x000000c4 (196)
    Kernel release: 2.6.32.21-g2447a8d
    New .modinfo section size: 204
    Loading module... OK.
    Write protect disabled.
    Searching for mmc_blk_issue_rq symbol...
    - Address: c02d3114, type: t, name: mmc_blk_issue_rq, module: N/A
    Kernel map base: 0xc02d3000
    Kernel memory mapped to 0x40001000
    Searching for brq filter...
    - Address: 0xc02d3114 + 0x34c
    - 0x2a000012 -> 0xea000012
    Done.
    # exit
    exit
    C:\android-sdk-windows\platform-tools>adb push hbooteng.nb0 /data/local/
    1641 KB/s (1048576 bytes in 0.624s)
    C:\android-sdk-windows\platform-tools>adb shell
    # /data/local/busybox md5sum /data/local/hbooteng.nb0
    /data/local/busybox md5sum /data/local/hbooteng.nb0
    6991368ee2deaf182048a3ed9d3c0fcb /data/local/hbooteng.nb0
    # dd if=/data/local/hbooteng.nb0 of=/dev/block/mmcblk0p18
    dd if=/data/local/hbooteng.nb0 of=/dev/block/mmcblk0p18
    2048+0 records in
    2048+0 records out
    1048576 bytes transferred in 0.485 secs (2162012 bytes/sec)
    # /data/local/busybox md5sum /dev/block/mmcblk0p18
    /data/local/busybox md5sum /dev/block/mmcblk0p18
    6991368ee2deaf182048a3ed9d3c0fcb /dev/block/mmcblk0p18
    #

Share This Page