Database Info

IF You have gotten FAIL-PU or partition errors in recovery, please read!

I'm currently trying to round up commonalities between cases of cache, etc not being able to be mounted, which seems to happen with FAIL-PU when trying to use PD15IMG. Unfortunately, to figure this out, I need at least two people who have recovered from this issue and still have the original phone.
So please, if you've had this issue and recovered, post here so i can contact you and figure some stuff out.

In the post emmc thread there was a guy who recovered from it..get with him and you are halfway there

Good to see people here took my cause and now I got the whole community involved in this grimy issue that none would shed light upon it. Far as me getting another MT4G goes for pure emmc hack goes I am still waiting maybe I can get soon. But you folks keep on with your research and collect all the people who is involved in single thread as it will be much easier for me then.

Not sure what u r looking for but I have recovered my gf mt4g a few weeks ago from this using PD15IMG
sent from my demonSPEED_EXT4 Glacier using XDA Premium App

thederekjay said:
Not sure what u r looking for but I have recovered my gf mt4g a few weeks ago from this using PD15IMG
sent from my demonSPEED_EXT4 Glacier using XDA Premium App
Click to expand...
Click to collapse
Fail-PU means failed partition update. At that point the block wouldn't update along with the radio will fail now are you absolutely sure it was fail-pu? How did you determine it was fail-pu? The E:\ can't mount on recovery is just the side effect which you see after its corrupted. So in terms you can recover from E:\ can't mount but when you receive fail-pu flag game is over as we know it. Since how our mmcblk is allocated it we can't low level format to reconstruct it. So at that point the motherboard has to be replaced.
I successfully recovered from it as I was the one who initially started this investigation few months back. I was able to push the recovery image manually. But as I stated there are alot of variables unaccounted for specially the chip difference as the device I tested was on SEM04G.
1) Make a poll between 2 chips and check which ratio is higher.
2) Those effected by the fail-pu which chip they have.
3) Which rooting meth did they use and effected the higher ratio.
Until I get my hand on another MT4G or I upgrade to newer device I can't risk my current working phone as I use it for biz.

i have gotten those cache errors on clockworkmod and i still do once in awhile but i have the SEM04G Emmc chip and i thought those errors were normal and i proceeded on flashing other roms and everything would work fine

I just encountered this fail pu when trying to get my mt4g back working after it just was stuck on splash screen and did not want to boot up. I don't know how the engineering bootloader is supposed to help since I have it and it has not helped. I loaded PD15IMG to root of sdcard and pressed vol down and power button and then got the fail-pu still.

Engineering bootloader doesn't help in case of Fail-PU, only on case of "can't mount recovery, cache, etc" but without Fail-PU.

Fail-pu doesn't let me do anything to revert to a returnable MT4G. Not cool
Sent from my SGH-T959 using XDA App

U recovered from fail-pu? How exactly ?.
UsrBkp said:
Fail-PU means failed partition update. At that point the block wouldn't update along with the radio will fail now are you absolutely sure it was fail-pu? How did you determine it was fail-pu? The E:\ can't mount on recovery is just the side effect which you see after its corrupted. So in terms you can recover from E:\ can't mount but when you receive fail-pu flag game is over as we know it. Since how our mmcblk is allocated it we can't low level format to reconstruct it. So at that point the motherboard has to be replaced.
I successfully recovered from it as I was the one who initially started this investigation few months back. I was able to push the recovery image manually. But as I stated there are alot of variables unaccounted for specially the chip difference as the device I tested was on SEM04G.
1) Make a poll between 2 chips and check which ratio is higher.
2) Those effected by the fail-pu which chip they have.
3) Which rooting meth did they use and effected the higher ratio.
Until I get my hand on another MT4G or I upgrade to newer device I can't risk my current working phone as I use it for biz.
Click to expand...
Click to collapse
Sent from my SGH-T959 using XDA App

UsrBkp said:
I successfully recovered from it as I was the one who initially started this investigation few months back. I was able to push the recovery image manually. But as I stated there are alot of variables unaccounted for specially the chip difference as the device I tested was on SEM04G.
1) Make a poll between 2 chips and check which ratio is higher.
2) Those effected by the fail-pu which chip they have.
3) Which rooting meth did they use and effected the higher ratio.
Until I get my hand on another MT4G or I upgrade to newer device I can't risk my current working phone as I use it for biz.
Click to expand...
Click to collapse
tjhnf said:
U recovered from fail-pu? How exactly ?.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
He says it "I was able to push the recovery image manually."
I've heard alot of talk about that being one of the options, but now knowing that the failpu error is caused by a hardware issue, I cant credit this method or believe that it works..

I had the error, recovered from it then got the error again a week later. Have not been able to recover again though using the same method I used last time or any other method I could find on the site. I still have the bricked device if I can help shoot me a PM. I wanna get this little demon off our back!

Where do I check to see which chip it is?
Sent from my HTC Glacier using XDA Premium App

JDV28 said:
He says it "I was able to push the recovery image manually."
I've heard alot of talk about that being one of the options, but now knowing that the failpu error is caused by a hardware issue, I cant credit this method or believe that it works..
Click to expand...
Click to collapse
For me manually pushing the recovery via fastboot did work, but I never got the failed PU error. The reason I never got it was because I never tried to flash the image the FIRST time my phone got the CWM errors. I didn't know about that being an option and off the cuff tried the whole flashing an old CWM thing and basically got lucky. Now that my phone has gotten the error again NOTHING works and I get the failed PU error. Whether I would have got this error the first time or not I have no idea.

Dcwiker05:
What command did u use? Where does the recovery get pushed to?
~noob
XDA App

fastboot flash recovery your_recovery_image.img
Obviously, recovery goes to recovery partition.

Jack_R1 said:
fastboot flash recovery your_recovery_image.img
Obviously, recovery goes to recovery partition.
Click to expand...
Click to collapse
what he said. I found it is easiest just to rename the recovery you download to recovery.img so you dont have to type as much. Also all this is done in fastboot under the hboot menu

I will try that and see if another rom loads... or at least to load original recovery to return. XDA App

Well... tried to push recovery through fastboot and nothing. Tried going and putting the command to make mt4g unable to boot or charge and still nothing.
I still have access to cwm recovery but can't do anything with it or even revert back to stock recovery. Aaaah
XDA App

tjhnf said:
Well... tried to push recovery through fastboot and nothing. Tried going and putting the command to make mt4g unable to boot or charge and still nothing.
I still have access to cwm recovery but can't do anything with it or even revert back to stock recovery. Aaaah
XDA App
Click to expand...
Click to collapse
Me too I tried hard to change S=OFF and realised that I can´t yet. God Damn Chip!

[Q] [REQ] Stock EE1 Modems

Anyone out there which have the stock EE1 radios?
LTE Modem
Code:
dd if=/dev/block/stl11 of=/sdcard/ee1_lte_modem.bin bs=256 count=48
CDMA aka CPMODEM
Code:
dd if=/dev/block/stl12 of=/sdcard/ee1_cp_modem.bin bs=256 count=2

Do you mean stock ED1 radios? I would say one of the devs would be your best bet, imnuts, DroidXcon, kejar31, etc.

RaptorMD said:
Do you mean stock ED1 radios? I would say one of the devs would be your best bet, imnuts, DroidXcon, kejar31, etc.
Click to expand...
Click to collapse
The baseband reports itself as
Baseband Version
i510.06 V.EE4
SCH-I510.EE1
Click to expand...
Click to collapse
I'm assuming that's what he means.

DeathWalking said:
The baseband reports itself as
I'm assuming that's what he means.
Click to expand...
Click to collapse
Yup was thinking that it would be a good idea for us to keep the versions in the event we may find issues with the new deltas.
Based on the PIT info on the stl device these were what we need for being able to flash future radios as well. Ie controlled updates.
Thnx for the replies!
Sent from my SCH-I510 using XDA Premium App

RaptorMD said:
Do you mean stock ED1 radios? I would say one of the devs would be your best bet, imnuts, DroidXcon, kejar31, etc.
Click to expand...
Click to collapse
Yeah I've already msgd them as well.
Sent from my SCH-I510 using XDA Premium App

Safe to assume that the same data would pull the EE4 radio?
The risk here is if we get it wrong, no way to fix it...

distortedloop said:
Safe to assume that the same data would pull the EE4 radio?
The risk here is if we get it wrong, no way to fix it...
Click to expand...
Click to collapse
As i understand it yes. Looking at the updates in the ee update files i didntt see any partitioning. if in doubt pull the pit info to validate.
Measure twice cut once.
Sent from my SCH-I510 using XDA Premium App

c0ns0le said:
Anyone out there which have the stock EE1 radios?
LTE Modem
Code:
dd if=/dev/block/stl11 of=/sdcard/ee1_lte_modem.bin bs=256 count=48
CDMA aka CPMODEM
Code:
dd if=/dev/block/stl12 of=/sdcard/ee1_cp_modem.bin bs=256 count=2
Click to expand...
Click to collapse
Thought I'd try this on my phone to get the EE4 modems saved. First command runs fine, second command errors out.
Code:
# dd if=/dev/block/stl11 of=/sdcard/ee1_lte_modem.bin bs=256 count=48
48+0 records in
48+0 records out
12288 bytes transferred in 0.008 secs (1536000 bytes/sec)
# dd if=/dev/block/stl12 of=/sdcard/ee1_cp_modem.bin bs=256 count=2
/dev/block/stl12: cannot open for read: Invalid argument
Also, after looking at imnut's instructions on making a backup there's a conflct in the stl numbers you gave. stl11 appears to be /dbdata, not the cpmodem.
I posted the EE4 pit and dd -h of the phone in the other thread if you want to check them out.

We were never able to dump the radio files from the phone on the Fascinate. I wouldn't be suprised if the same applies here. What we need is a source, preferably one who can provide a full Odin package for any one of the official builds.

s44 said:
We were never able to dump the radio files from the phone on the Fascinate. I wouldn't be suprised if the same applies here. What we need is a source, preferably one who can provide a full Odin package for any one of the official builds.
Click to expand...
Click to collapse
There was a fellow in the i9000 forums who was pumping out leaked ROMs from Samsung like a madman. I always suspected he was a Samsung employee. I wonder if he might be able to help us out. I'll see if he's still around and ask him.

[ROOT] Think-tank

So, I'm starting this thread to start trying to put a root method together.
I've started work on a unsecure boot image using the at&t boot.img from 1.68
(going to try and get a 'INSECURE BOOT AND ROOT' going for our devices that paulobrien already has going for teg3 models)
I'd like a confirmation that the at&t 1.68 ruu does indeed work 100% without issue on the rogers devices. As there's no Rogers RUU, I'm taking a big leap with semi-bricking a pretty expensive device that I bought outright and would like to minimize risk (I still am willing to take the risk)
Also, any other information/help/idea's from other dev's or users alike would also be appreciated.
Let's get this ball rolling without waiting for the at&t release...
Edit: Has anyone attempted to compare the partition table to the one already somewhat put together for the Tegra 3 One X ?
PS: I'm going over information regarding the regular one x, and comparing them to the extracted items from the 1.68 evita ruu (so I can get a sense of the makeup of our devices) ... I might have to make us a partition table comparison similar to mike1986's

from my understanding and research... the Rogers and AT&T are identical minus the HIGHEND bloadware

Even the CID is the same?!
Wow that's good news for AT&T people, they can flash the Rogers RUU to gain more features
For rooting... Possible to unlock with htcdev?
Then we only need a custom recovery to push busy box and whatever to get root

ytwytw said:
Even the CID is the same?!
Wow that's good news for AT&T people, they can flash the Rogers RUU to gain more features
For rooting... Possible to unlock with htcdev?
Then we only need a custom recovery to push busy box and whatever to get root
Click to expand...
Click to collapse
I haven't done it myself yet, but some misguided users did unlock their bootloader and flashed the CWM for the Tegra edition of the One X. So I'd assume we're good on that front. I was going to start trying to compile CWM for our device on the weekend, but life got in the way.

I've unlocked my bootloader through HTCDev. I also believe the CID are the same but please don't quote me on that. I spent hours trying to correct my device so everything is a blur.
I believe that outside the carrier bloatware that the Rogers and AT&T devices are completely identical. I've killed just about every piece of Sense software too and my device is running flawlessly. On a side note, I'm quite impressed at how polished this is and that Sense isn't the beast it was on previous devices. Re-enabled a lot of features and I quite enjoy them.

LNKNPRKFN said:
from my understanding and research... the Rogers and AT&T are identical minus the HIGHEND bloadware
Click to expand...
Click to collapse
The same was the case between the Telus DHD and the Inspire 4G... But one was the PD9814000, while the other was a PD9812000 (ordered respectively). I wouldn't doubt the same. The original DHD was PD9810000 (DHD 9191), and there was also a PD9815000 as well floating around in the asian market (I think Korea) and was simply another variant of the TelusDHD/Inspire (9192).
If someone were to hop into an at&t store and check their display model, what it says on the back under the FCC logo .. or better yet install terminal on it and run /sbin/grep and get the androidboot.mid value to accurately get the CID, would be best.
Sent from my HTC One X using xda premium

craig0r said:
I haven't done it myself yet, but some misguided users did unlock their bootloader and flashed the CWM for the Tegra edition of the One X. So I'd assume we're good on that front. I was going to start trying to compile CWM for our device on the weekend, but life got in the way.
Click to expand...
Click to collapse
Well, if our recovery sits in the same partition as the teg3 device, then we might actually have a chance.
Sent from my HTC One X using XDA premium

Also, here's a link to a 1.68 mirror I put up. More reliable that the one's currently available.
http://d-h.st/hoA
Will upload more as I get them (clicking my user name will get the full listing of items I have available; 'ER3BUS' is NOT for the One X if anyone's wondering)
Sent from my HTC One X using XDA Premium

JSLEnterprises said:
The same was the case between the Telus DHD and the Inspire 4G... But one was the PD9814000, while the other was a PD9812000 (ordered respectively). I wouldn't doubt the same. The original DHD was PD9810000 (DHD 9191), and there was also a PD9815000 as well floating around in the asian market (I think Korea) and was simply another variant of the TelusDHD/Inspire (9192).
If someone were to hop into an at&t store and check their display model, what it says on the back under the FCC logo .. or better yet install terminal on it and run /sbin/grep and get the androidboot.mid value to accurately get the CID, would be best.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
On the Rogers unit, it's NM8PJ83100.
I believe some AT&T customers here said they had the same number on their pre-orders.

JSLEnterprises said:
Well, if our recovery sits in the same partition as the teg3 device, then we might actually have a chance.
Sent from my HTC One X using XDA premium
Click to expand...
Click to collapse
(This may be a dumb question.)
Even if it's not on the same partition, does that really matter when we can just "fastboot flash recovery cwm.img?" Of course we'd have to find the partition locations, but I think fastboot should be enough to get us off to a start. Maybe I'm wrong. I've never had the chance to work on rooting a device, but with this one being so new, I'm hoping I get a chance to help out.

craig0r said:
(This may be a dumb question.)
Even if it's not on the same partition, does that really matter when we can just "fastboot flash recovery cwm.img?" Of course we'd have to find the partition locations, but I think fastboot should be enough to get us off to a start. Maybe I'm wrong. I've never had the chance to work on rooting a device, but with this one being so new, I'm hoping I get a chance to help out.
Click to expand...
Click to collapse
Compiling a proper working cwm 'port' (if you will), kinda requires adaptation of code to correspond to the device's partition table... values need to change for commands for it to work properly and not cause your device to brick (you wouldnt want to flash the recovery to mmcblk0p05 if the recovery isnt in that partition)
(think back to the sd partition issue with cwmrecovery early last year which repartitioned some device's emmc instead of the sd)
I personally havent dabled in kernel / recovery compiling... so I'm only going off the amount of knowledge that I know; I could be wrong however.

I'm an AT&T rep, and I have a One X on hand. I can't take it home with me, but here's some info that you guys have been needing. Let me know what else you guys need me to find out/dump.
CID is CWS_001
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

danielsaenz said:
I'm an AT&T rep, and I have a One X on hand. I can't take it home with me, but here's some info that you guys have been needing. Let me know what else you guys need me to find out/dump.
CID is CWS_001
[ two images]
Click to expand...
Click to collapse
Thanks.
I also have a modelid confirmation that the 1.68 is indeed the same as the 'release' firmware, and that our devices are identical.
I'll be attempting a down n dirty 'boot n root' tonight.

k4p741nkrunch said:
Also, I think the only holdup is finding and verifying the partitions then you just sign up to HTCdev, get the unlock.bin file and fastboot flash the modded cwm.
Click to expand...
Click to collapse
I'd rather fastboot flash a modded boot image (since thats easy to change) rather than flash an untested recovery, espeically since I'm the one changing the default prop values, and permissions in init.rc the boot.img. lol.
Edit: The boot image i'll be modifying is the 1.68 boot image.
k4p741nkrunch said:
Root access shouldn't be necessary to cat the init file and list the partitions right?
Click to expand...
Click to collapse
no, you dont need root for that.

danielsaenz said:
What is the command to get the partition table?
Is it done on the phone, fastboot, or adb?
Let me know and I will find that out for you.
Click to expand...
Click to collapse
dev: size erasesize name
mmcblk0p23: 000ffa00 00000200 "misc"
mmcblk0p22: 00fffe00 00000200 "recovery"
mmcblk0p21: 01000000 00000200 "boot"
mmcblk0p33: 67fffc00 00000200 "system"
mmcblk0p30: 00140200 00000200 "local"
mmcblk0p34: 0ffffe00 00000200 "cache"
mmcblk0p35: 97fffe00 00000200 "userdata"
mmcblk0p26: 01400000 00000200 "devlog"
mmcblk0p28: 00040000 00000200 "pdata"
mmcblk0p36: 27be00000 00000200 "fat"
mmcblk0p31: 00010000 00000200 "extra"
mmcblk0p17: 02d00000 00000200 "radio"
mmcblk0p18: 00a00000 00000200 "adsp"
mmcblk0p16: 00100000 00000200 "dsps"
mmcblk0p19: 00500000 00000200 "wcnss"
mmcblk0p20: 007ffa00 00000200 "radio_config"
mmcblk0p24: 00400000 00000200 "modem_st1"
mmcblk0p25: 00400000 00000200 "modem_st2"
---
Using ADB - adb shell cat /proc/emmc
dsixda's kitchen auto root did not work for the stock ROM, it results in bootloop. Also, my other bootimg decompilation tools aren't working either. I know what to do, just not how to get it to boot on my phone. logcat doesn't pick anything up, either. If anyone has any ideas on how to get the boot.img decompiled/recompiled, feel free to send it my way.

So, I think Paul may have beaten me to it.
But I'm still going to test my edits later tonight anyways. heh

RMatt1992 said:
dev: size erasesize name
mmcblk0p22: 00fffe00 00000200 "recovery"
Click to expand...
Click to collapse
Just make's you wonder what's actually sitting in our 5th partition (the recovery location of the endeavor)
RMatt1992 said:
dsixda's kitchen auto root did not work for the stock ROM, it results in bootloop. Also, my other bootimg decompilation tools aren't working either. I know what to do, just not how to get it to boot on my phone. logcat doesn't pick anything up, either. If anyone has any ideas on how to get the boot.img decompiled/recompiled, feel free to send it my way.
Click to expand...
Click to collapse
dsixda's kitchen is really only for gingerbread devices.
I use that kitchen... just to 'cook' the final release into a signed zip.

FYI, Rogers CID = ROGER001, so they are different unfortunately.

RMatt1992 said:
FYI, Rogers CID = ROGER001, so they are different unfortunately.
Click to expand...
Click to collapse
doesnt matter...
ro.aa.modelid=PJ831000 <- key value (this is what usually denotes hardware variance... usually the third last '0' becomes a different number)
same as the at&t one x.
the maincid and cidlist values mean nothing other than software branding.

JSLEnterprises said:
doesnt matter...
ro.aa.modelid=PJ831000 <- key value (this is what usually denotes hardware variance... usually the third last '0' becomes a different number)
same as the at&t one x.
the maincid and cidlist values mean nothing other than software branding.
Click to expand...
Click to collapse
Cheers, I thought the CID was important for something.

Rogers Infuse Full Rom

I recently have a problem with my Rogers infuse. I searched the internet, and even ask this via PM from another person who have the same problem, but no solution. Here is my problem:
During one of my recovery attempts, I flashed a ATT ROM using Odin which also includes the infuse.pit file. After that, the initial logo of ROGERS which was shown in the beginning is gone. I later installed ROGERS rom, but the logo is still not there.
I had full nandoird backups before that, but restoring none of them solved the problem. Is it possible for one of the people who have a ROGERS infuse to create a full back (using heimdall) and share the .pit file and the different partitions (mainly non system and non data partitions)?
I could not find any complete ROGERS rom. Although there are some complete ATT roms (such as SGH_I997-UCKE3-Stock-Noboot-One-Click ), there is no one for ROGERS.

utfrazier said:
I recently have a problem with my Rogers infuse. I searched the internet, and even ask this via PM from another person who have the same problem, but no solution. Here is my problem:
During one of my recovery attempts, I flashed a ATT ROM using Odin which also includes the infuse.pit file. After that, the initial logo of ROGERS which was shown in the beginning is gone. I later installed ROGERS rom, but the logo is still not there.
I had full nandoird backups before that, but restoring none of them solved the problem. Is it possible for one of the people who have a ROGERS infuse to create a full back (using heimdall) and share the .pit file and the different partitions (mainly non system and non data partitions)?
I could not find any complete ROGERS rom. Although there are some complete ATT roms (such as SGH_I997-UCKE3-Stock-Noboot-One-Click ), there is no one for ROGERS.
Click to expand...
Click to collapse
I believe you can use any of the ATT STOCK Firmware but under the APN, just put in Roger's network for connection.
Roger's natively start at 2.3.3 GB.
Some of the Roger's users may have a stock version around in cyberspace

qkster said:
I believe you can use any of the ATT STOCK Firmware but under the APN, just put in Roger's network for connection.
Roger's natively start at 2.3.3 GB.
Some of the Roger's users may have a stock version around in cyberspace
Click to expand...
Click to collapse
Thanks for your reply. However, as I said, my problem is not the ROM. I installed a ATT Full recovery ROM that includes the .pit file, and I think a series of partitions other than system and data. So although I reinstall a Rogers ROM, I still have no initial ROGERS logo in boot up, and instead, it shows a random series of lines. I have no other problem in the functionalities of the phone.

utfrazier said:
Thanks for your reply. However, as I said, my problem is not the ROM. I installed a ATT Full recovery ROM that includes the .pit file, and I think a series of partitions other than system and data. So although I reinstall a Rogers ROM, I still have no initial ROGERS logo in boot up, and instead, it shows a random series of lines. I have no other problem in the functionalities of the phone.
Click to expand...
Click to collapse
that's because you flashed an att param.ifs. you must have used a froyo unbrick package. i dont know if there is a rogers dump with param.ifs but there are captivate threads (old ones) that have tools to change that splash screen and i have heard it works on the infuse but the mod never became popular around here. if i were you i'd flash an att rom and modem with a custom kernel,(better camera performance, and better battery life) change the apn and then change the splash and boot animation to something cool! unless of coarse you are worried about the warranty. if you are worried about insurance just report the thing missing...

Dani897 said:
that's because you flashed an att param.ifs. you must have used a froyo unbrick package. i dont know if there is a rogers dump with param.ifs but there are captivate threads (old ones) that have tools to change that splash screen and i have heard it works on the infuse but the mod never became popular around here. if i were you i'd flash an att rom and modem with a custom kernel,(better camera performance, and better battery life) change the apn and then change the splash and boot animation to something cool! unless of coarse you are worried about the warranty. if you are worried about insurance just report the thing missing...
Click to expand...
Click to collapse
I tried to flash att roms, but they never boot after flash. That was why I return to Rogers rom, and now I am using ICS. Could you provide more detail about those splash screen changing tools? And also, is there anyone here with an Rogers Infuse that can send me the param.ifs file from his phone?

Mine's a Rogers Infuse and I'm sure at one point I used an unbrick package that changed my splash screen from Rogers to At&t.
If I remember correctly, I used Odin and a "return to stock" which brought back my Rogers splash screen.
I'll try and track down the package I used...
*edit* try this: http://forum.xda-developers.com/showthread.php?t=1193927

prairied0gg said:
Mine's a Rogers Infuse and I'm sure at one point I used an unbrick package that changed my splash screen from Rogers to At&t.
If I remember correctly, I used Odin and a "return to stock" which brought back my Rogers splash screen.
I'll try and track down the package I used...
*edit* try this: http://forum.xda-developers.com/showthread.php?t=1193927
Click to expand...
Click to collapse
Thanks for the link. I had tested this one. It did not solve my problem. I think that my phone's param.lfs partition is overwritten by something else. I am mainly searching for for a heimdall stock. Is it possible for you to create a backup using heimdall, and send it to me?

utfrazier said:
Thanks for the link. I had tested this one. It did not solve my problem. I think that my phone's param.lfs partition is overwritten by something else. I am mainly searching for for a heimdall stock. Is it possible for you to create a backup using heimdall, and send it to me?
Click to expand...
Click to collapse
I'll take a look and see what I can come up with - I've never used Heimdall before, only Odin.

prairied0gg said:
I'll take a look and see what I can come up with - I've never used Heimdall before, only Odin.
Click to expand...
Click to collapse
Heimdall for one click is great, but get with jedi master qkster he can provide....

prairied0gg said:
I'll take a look and see what I can come up with - I've never used Heimdall before, only Odin.
Click to expand...
Click to collapse
Hey, pd0gg.
We can try to put together a heimdall for Rogers' users.
If you have odin'ed to rogers stock, flash an insecure gb kernel (bedwa, zen, entropy..doesn't matter which one) and run adb or terminal to get access to system files.
this shows you how to dump the partition:
http://forum.xda-developers.com/showthread.php?t=1348392
from adam's op:
su
#Mount The /system folder as RW so we can read and write to it
mount -o remount,rw /system /system
#Make our folder to write the firmware package onto the SDCard
mkdir /sdcard/firmwarepackage
#Begin transfer of all relevant blocks to sdcard
dd if=/dev/block/stl9 of=/sdcard/firmwarepackage/factoryfs.img bs=4096
dd if=/dev/block/bml7 of=/sdcard/firmwarepackage/zImage bs=4096
dd if=/dev/block/stl10 of=/sdcard/firmwarepackage/dbdata.img bs=4096
dd if=/dev/block/stl11 of=/sdcard/firmwarepackage/cache.img bs=4096
dd if=/dev/block/bml12 of=/sdcard/firmwarepackage/modem.bin bs=4096
#Done
echo done
Use the lines above. The other parts doesn't apply.
Pull the pit file from the unbrick or any of the 1 click package.
Make up the 1click from the op.
The other option would be to pull the data from the odin tar and put them into a 1 click
As Dani897 has stated though, I think it's really pointless as the Roger's Firmware is inferior. No hdmi or Hd video etc...using the att firmware, change out the boot screen and add roger's apn is a better idea.

qkster said:
Hey, pd0gg.
We can try to put together a heimdall for Rogers' users.
If you have odin'ed to rogers stock, flash an insecure gb kernel (bedwa, zen, entropy..doesn't matter which one) and run adb or terminal to get access to system files.
this shows you how to dump the partition:
http://forum.xda-developers.com/showthread.php?t=1348392
from adam's op:
su
#Mount The /system folder as RW so we can read and write to it
mount -o remount,rw /system /system
#Make our folder to write the firmware package onto the SDCard
mkdir /sdcard/firmwarepackage
#Begin transfer of all relevant blocks to sdcard
dd if=/dev/block/stl9 of=/sdcard/firmwarepackage/factoryfs.img bs=4096
dd if=/dev/block/bml7 of=/sdcard/firmwarepackage/zImage bs=4096
dd if=/dev/block/stl10 of=/sdcard/firmwarepackage/dbdata.img bs=4096
dd if=/dev/block/stl11 of=/sdcard/firmwarepackage/cache.img bs=4096
dd if=/dev/block/bml12 of=/sdcard/firmwarepackage/modem.bin bs=4096
#Done
echo done
Use the lines above. The other parts doesn't apply.
Pull the pit file from the unbrick or any of the 1 click package.
Make up the 1click from the op.
The other option would be to pull the data from the odin tar and put them into a 1 click
As Dani897 has stated though, I think it's really pointless as the Roger's Firmware is inferior. No hdmi or Hd video etc...using the att firmware, change out the boot screen and add roger's apn is a better idea.
Click to expand...
Click to collapse
Thank-you, qkster! I very much appreciate you taking the time to help.
I'll give it a whirl and see what happens.

prairied0gg said:
Thank-you, qkster! I very much appreciate you taking the time to help.
I'll give it a whirl and see what happens.
Click to expand...
Click to collapse
Thank you guys. I will wait to see if it can help me.

With it being a long weekend I'm likely going to be away from my computer til Tuesday.
I have the files we need I just need to package then into a one-click.

prairied0gg said:
With it being a long weekend I'm likely going to be away from my computer til Tuesday.
I have the files we need I just need to package then into a one-click.
Click to expand...
Click to collapse
If you run into problems, let me know.
It is usually advisable to try it before you post it.
For the record, I'm not keen on flashing Roger firmware on my native att Infuse.
Gl

qkster said:
If you run into problems, let me know.
It is usually advisable to try it before you post it.
For the record, I'm not keen on flashing Roger firmware on my native att Infuse.
Gl
Click to expand...
Click to collapse
The one-click has been generated; however, I have not had a chance to test it. It's been a busy day and I simply ran out of time.
As an aside, I had never even looked at Heimdall until I responded to this thread. I can see now why folks use it and recommend it

prairied0gg said:
The one-click has been generated; however, I have not had a chance to test it. It's been a busy day and I simply ran out of time.
As an aside, I had never even looked at Heimdall until I responded to this thread. I can see now why folks use it and recommend it
Click to expand...
Click to collapse
Thanks for your help. Any update? Can you upload it to somewhere?

utfrazier said:
Thanks for your help. Any update? Can you upload it to somewhere?
Click to expand...
Click to collapse
I'm sorry, no update yet. Usb drivers are giving me grief so I've still not managed to test it.
I do have it uploaded but, because it is still untested, I am reluctant to give the url.
---------- Post added at 05:58 PM ---------- Previous post was at 05:45 PM ----------
utfrazier said:
Thanks for your help. Any update? Can you upload it to somewhere?
Click to expand...
Click to collapse
Okay, got the usb things sorted out and just finished flashing. Everything looks a-okay.
Here's the link:
https://docs.google.com/open?id=0B8hYM72TRTvzZzh0ZHplZFBjOTA
Or here:
http://db.tt/l1Y0LgXM
*edit* I should note, this is not a complete return to stock as it is rooted.

prairied0gg said:
I'm sorry, no update yet. Usb drivers are giving me grief so I've still not managed to test it.
I do have it uploaded but, because it is still untested, I am reluctant to give the url.
---------- Post added at 05:58 PM ---------- Previous post was at 05:45 PM ----------
Okay, got the usb things sorted out and just finished flashing. Everything looks a-okay.
Here's the link:
https://docs.google.com/open?id=0B8hYM72TRTvzZzh0ZHplZFBjOTA
Or here:
http://db.tt/l1Y0LgXM
*edit* I should note, this is not a complete return to stock as it is rooted.
Click to expand...
Click to collapse
If this works as intended, we may want to link this to the Rogers thread or Big Joe, you may want to ISet this
Sent from my SAMSUNG-SGH-I997

If so...shot me post in the iset page, plz so don't forget...
Sent from my SAMSUNG-SGH-I717 using xda premium

Ya, hopefully this helps utfrazier out and if so I would be happy to see it linked to from the Rogers thread or a mention in iset.

Well crap... I have a hard brick

Ok I got overly excited with the news of the bootloader being unlocked. So I flashed the unsecure boot loader to my phone and everything went fine. So I decided to go ahead and extract the the kernel I was using from the zip so I didn't have to use kexec anymore. Anyway I read a post incorrectly and flashed the kernel to the wrong partition on my phone and got a hard brick. I can't get into odin or clockwork recovery, only a black screen. I saw another post I accidently flashed it to dd if=/sdcard/aboot.img of=/dev/block/mmcblk0p5
If I plug it into my computer I get the popup to install the QHSUSB_DLOAD. If there is anyway to recover this please let me know!

Time to get your story straight.... "I just turned it off and it won't turn back on??? Maybe my chargers broken?"
Sent from my SCH-I535 using xda app-developers app

dushotgun said:
Ok I got overly excited with the news of the bootloader being unlocked. So I flashed the unsecure boot loader to my phone and everything went fine. So I decided to go ahead and extract the the kernel I was using from the zip so I didn't have to use kexec anymore. Anyway I read a post incorrectly and flashed the kernel to the wrong partition on my phone and got a hard brick. I can't get into odin or clockwork recovery, only a black screen. I saw another post I accidently flashed it to dd if=/sdcard/aboot.img of=/dev/block/mmcblk0p5
If I plug it into my computer I get the popup to install the QHSUSB_DLOAD. If there is anyway to recover this please let me know!
Click to expand...
Click to collapse
Not to be a **** but damn dude WTF..Why would you do that. Anyways i think the only way to recovery is jtag since you are getting qhsusb_dload but i dont know. pm adam and ask him maybe he can help you out

Wait you tried to unzip the kernel in your pc? For what exactly? How did you flashed it back unzipped?
VERIZON GALAXY S 3

jgrimberg1979 said:
Not to be a **** but damn dude WTF..Why would you do that. Anyways i think the only way to recovery is jtag since you are getting qhsusb_dload but i dont know. pm adam and ask him maybe he can help you out
Click to expand...
Click to collapse
Yeah I effed up majorly. I was on a droid x for 2 years before so I'm new with kernel flashing. So jtag is the only option?

dushotgun said:
Yeah I effed up majorly. I was on a droid x for 2 years before so I'm new with kernel flashing. So jtag is the only option?
Click to expand...
Click to collapse
You can try a USB Jig to force your phone into Download mode, but if it's truly hardbricked then JTAG or getting a replacement are your only options.

I hate to go off topic and say this but this could be one potential reason as to why the idiots at Verizon want to lock stuff.
Why not wait for things to settle down before trying it out without knowing?

Coderedpl said:
I hate to go off topic and say this but this could be one potential reason as to why the idiots at Verizon want to lock stuff.
Why not wait for things to settle down before trying it out without knowing?
Click to expand...
Click to collapse
we're only human if i had this phone and saw this unlocked bootloader i would get excited about it as well lol i feel for the man/woman

Coderedpl said:
I hate to go off topic and say this but this could be one potential reason as to why the idiots at Verizon want to lock stuff.
Why not wait for things to settle down before trying it out without knowing?
Click to expand...
Click to collapse
Yeah thanks I realize I screwed up. I guess I was overconfident after two years of flashing stuff. I just need to know if there are any tools to reflash the aboot I effed up.

dushotgun said:
Yeah thanks I realize I screwed up. I guess I was overconfident after two years of flashing stuff. I just need to know if there are any tools to reflash the aboot I effed up.
Click to expand...
Click to collapse
Does pressing power home + vol down not do anything?
Contact Adam he might be able to help

jgrimberg1979 said:
Not to be a **** but damn dude WTF..Why would you do that. Anyways i think the only way to recovery is jtag since you are getting qhsusb_dload but i dont know. pm adam and ask him maybe he can help you out
Click to expand...
Click to collapse
Sucks, OP.
And don't even bother writing Adam. I don't know him, but I read his threads. He just had a major accomplishment (with help) and he will probably not even respond. Let him have his day/peace. He earned it. You admit that you jumped the gun.
Sent from my SCH-I535 using Tapatalk 2

Coderedpl said:
I hate to go off topic and say this but this could be one potential reason as to why the idiots at Verizon want to lock stuff.
Why not wait for things to settle down before trying it out without knowing?
Click to expand...
Click to collapse
Ohhh..c'monnnn- he/she was a Droid X user. As a fellow X2 encrypted bootloader ****ing never unlocked I was excited as **** about it being cracked too.
I'm not ****ing with my kernel or nothing.. but.. I couldn't resist. Been on lock down for 2 years- pre ordered the phone and come to find out they locked this ****er too.
Don't be so hard on the guy/gal.. :angel:

Coderedpl said:
Does pressing power home + vol down not do anything?
Contact Adam he might be able to help
Click to expand...
Click to collapse
I sent him a message but no response yet. I tried that and I still get nothing thanks though. I've read every page of the bootloader research by adam I saw this on his original post:
"op5= aboot
This block is signed by Samsung, we will not be able to modify it
This block contains HTML information. It would appear that it is possible to put the device into a mode where it will provide a webserver which displays state information.
This block appears to be a complete operating system
This block contains the Loke Daemon which communicates with Odin3."
I take this to mean there is no way for me to communicate with odin now and jig wouldn't be able to force it into odin either since I overwrote the 0p5 block. I guess thats it since I don't have a jtag set up.

Have you considered inquiring about JTAG rates from these folks?
http://www.youtube.com/watch?v=XnA8Djs55Ds&list=UUpntFTjw320ZgqHUEndzg0g&index=2&feature=plcp
- ooofest

You flashed the kernel to the aboot partition, most likely meaning no booty booty to get into a state (download mode) where you can ODIN to stock. That being said, looks like you'll be JTAGing in your near future. Curious about prices, if you do it!

ooofest said:
Have you considered inquiring about JTAG rates from these folks?
http://www.youtube.com/watch?v=XnA8Djs55Ds&list=UUpntFTjw320ZgqHUEndzg0g&index=2&feature=plcp
- ooofest
Click to expand...
Click to collapse
It's $60
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-iii-jtag-brick-repair/

ooofest said:
Have you considered inquiring about JTAG rates from these folks?
- ooofest
Click to expand...
Click to collapse
Thanks for the link, it looks like thats my only option for getting it fixed.

This is why using dd to flash stuff can be dangerous. "I'm fairly certain it will flash Tetris.Apk to your bootloader partition if you tell it to" to quote one of the devs from my Thunderbolt days.

JBO1018 said:
This is why using dd to flash stuff can be dangerous. "I'm fairly certain it will flash Tetris.Apk to your bootloader partition if you tell it to" to quote one of the devs from my Thunderbolt days.
Click to expand...
Click to collapse
It will and it will ENJOY it.

JBO1018 said:
This is why using dd to flash stuff can be dangerous. "I'm fairly certain it will flash Tetris.Apk to your bootloader partition if you tell it to" to quote one of the devs from my Thunderbolt days.
Click to expand...
Click to collapse
dd = disk destroyer :laugh: