Develop Bugs

help please!

i think i bricked my epic 4g touch. i had ics fb21 on it and i tried to restore a gingerbread rom back onto it via cwm and something went terribly wrong. i tried all the steps in qbking77s youtube video about unbricking/unrooting. my phone successfully went through the steps but when it reboots it just boot loops. when i try to boot into recovery it continues to bootloop. download mode is still available? any suggestions? thanks in advanced

Have you tried putting it into download mode and then using one of the one click restores via odin? If its bootlooping, your not at a total loss
Sent from my SPH-D710 using xda premium

r2hudson said:
i think i bricked my epic 4g touch. i had ics fb21 on it and i tried to restore a gingerbread rom back onto it via cwm and something went terribly wrong. i tried all the steps in qbking77s youtube video about unbricking/unrooting. my phone successfully went through the steps but when it reboots it just boot loops. when i try to boot into recovery it continues to bootloop. download mode is still available? any suggestions? thanks in advanced
Click to expand...
Click to collapse
Did you have cwm touch on it ?
Sent from my SPH-D710 using Tapatalk

rshudson---use this lick
use this link and it will restore your epic completely with roon access and than find the recovery zip/tar and you will be fixed ...the link has directions and videos
http://forum.xda-developers.com/showthread.php?t=1433101
GOOD LUCK BRO !!!!!!!!!!!

andhow said:
Have you tried putting it into download mode and then using one of the one click restores via odin? If its bootlooping, your not at a total loss
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
i tried these but they seem to get stuck right before it completes. it freezes right before the end, no reboot, no nothing

Epix4G said:
Did you have cwm touch on it ?
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
actually i did, installed it straight from rom manager. has this been a common problem?

r2hudson said:
actually i did, installed it straight from rom manager. has this been a common problem?
Click to expand...
Click to collapse
so in odin it stops at data. something ...u got A BRICK should have read what all the devs were saying and the other 10 threads that did the same as you ..... read read read ... when going from ics to gb always odin back to stock first then restore ... look in general you will find many threads about this already
http://forum.xda-developers.com/showthread.php?t=1504808
http://forum.xda-developers.com/showthread.php?t=1509795
http://forum.xda-developers.com/showthread.php?t=1509886&page=3

rocketman228 said:
use this link and it will restore your epic completely with roon access and than find the recovery zip/tar and you will be fixed ...the link has directions and videos
http://forum.xda-developers.com/showthread.php?t=1433101
GOOD LUCK BRO !!!!!!!!!!!
Click to expand...
Click to collapse
i have tried this, it just gets stuck at the data.img step, been stuck for over an hour. thanks all for your help

Epix4G said:
so in odin it stops at data. something ...u got A BRICK should have read what all the devs were saying and the other 10 threads that did the same as you ..... read read read ... when going from ics to gb always odin back to stock first then restore ... look in general you will find many threads about this already
Click to expand...
Click to collapse
wow, thought so, i guess there hasnt been a way to undo this? it only gets stuck when i use the one click odin. when i use the regular odin it completes but just bootloops. could i take this to a sprint repair center?

read links
u have a bad data partition and are bricked .... read before doing anything like this ....many people before you did this and there is no way back besides jtag ....
you can take to sprint and they may replace but who knows they may turn you away

r2hudson said:
actually i did, installed it straight from rom manager. has this been a common problem?
Click to expand...
Click to collapse
Oh man...ROM Manager and Touch recovery?... not sure if that's fixable
Sent from my Nexus S 4G using xda premium

I believe a few people have said it already. But don't use from manager to flash recoveries. Especially the touch one. You will brick your phone and can't fix it. Only a JTAG service would fix it or a replacement by sprint. Either way good luck and read up on stuff before you try it out.
Sent from my SPH-D710 using xda premium

How many bricks does this make now? I had one. Lol
Sent from my Nexus S 4G using xda premium

musclehead84 said:
How many bricks does this make now? I had one. Lol
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
I swear more than 30 but who knows how many didn't post and such
Sent from my SPH-D710 using Tapatalk

OH Shix, Dang Dawg, I didn't know there was a such thing as a soft/full brick! I am lucky, I was using mobile odin and flashed the md5 check instead of the tar for fb21 modem and my phone was acting very similar but I just flashed the ONE CLICK EL29 and I was back to stock. hope if you havent tried that, you do and it works for you. I didn't like the touch cwm. but now I am deleting it from sdcard so i dont mistakenly soft/full brick my device. Keep us updated!

UPDATE
UPDATE
after using odin to unroot/unbrick my epic4gt and having still it fail to turn on passed the boot screen, i took my busted phone back to sprint on monday. told them what the problem was, "my phone wont go passed the first screen when i turn it on". they said "ok, we'll just erase everything off, should be as good as new".
i stood around waiting for about 45 minutes, i was so bored i even shamefully sent out a tweet from an iphone..smh. sales associate then came back to me saying," ive never seen anything like this, nothing will work on it, you must have rooted this phone?" my response was "i have done nothing to that phone".
with a kinda upset smirk on his face he says, "it had to be rooted buuuuut since we have no proof we will order you a phone for free, come pick it up friday."
life has been so tough w/out my epic for a whole week, happy that i get my new one on friday

You know...
I'm starting to wonder how I feel about ppl that brick their phones, through fault of their Own, then take them into sprint claiming the "update broke it!", "i never rooted that! i have No Idea what you're talking about!", and I wonder if this is going to make it harder for people with Legitimate issues to get replacements, and affect the way Sprint looks at rooting our phones in general. This Affects Their Bottom Line.
Sent from my calculator watch.

kingdazy said:
You know...
I'm starting to wonder how I feel about ppl that brick their phones, through fault of their Own, then take them into sprint claiming the "update broke it!", "i never rooted that! i have No Idea what you're talking about!", and I wonder if this is going to make it harder for people with Legitimate issues to get replacements, and affect the way Sprint looks at rooting our phones in general. This Affects Their Bottom Line.
Sent from my calculator watch.
Click to expand...
Click to collapse
I wonder this same thing....I get that people want their phone working g but on the other hand its not Sprints fault you bricked it. And then just flat out lying? Its a grey area for sure .
Sent from my SPH-D710 using XDA App

dodgerbluehero said:
I wonder this same thing....I get that people want their phone working g but on the other hand its not Sprints fault you bricked it. And then just flat out lying? Its a grey area for sure .
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
Uh Oh here comes the moral police.... Not saying you are wrong but really if people can get something replaced for free, do you really think the majority would not try it... We live in a grey world.... It is what it is
Men Lie, Women Lie, Numbers Never Lies - "Jay-Z" Just felt like saying that....lol
---------- Post added at 06:49 PM ---------- Previous post was at 06:47 PM ----------
r2hudson said:
UPDATE
after using odin to unroot/unbrick my epic4gt and having still it fail to turn on passed the boot screen, i took my busted phone back to sprint on monday. told them what the problem was, "my phone wont go passed the first screen when i turn it on". they said "ok, we'll just erase everything off, should be as good as new".
i stood around waiting for about 45 minutes, i was so bored i even shamefully sent out a tweet from an iphone..smh. sales associate then came back to me saying," ive never seen anything like this, nothing will work on it, you must have rooted this phone?" my response was "i have done nothing to that phone".
with a kinda upset smirk on his face he says, "it had to be rooted buuuuut since we have no proof we will order you a phone for free, come pick it up friday."
life has been so tough w/out my epic for a whole week, happy that i get my new one on friday
Click to expand...
Click to collapse
Congrats... next time dont start a new thread about something that already had a million other threads and a Official How I Bricked my phone thread.... I KNOW YOU SAW IT.....lol

Yeah say what you want but I pay 8 dollars a month to sprint for insurance so weather its my fault or not they should replace my device which they did and I could give a **** less how it effects everything because I pay for insurance.
Sent from my SPH-D710 using XDA App

DONT WANT A BRICK? Check here

As of right now, the roms for your S3 are not meant to be used on other S3 variants. Bricks might happens or a soft one might happen. Before flashing a Rom make sure you are in the right development section an you read the entire op, twice. Until other devs or experienced users find a way to make them cross compatible, please refrain from using other carriers S3 roms.

I am working on this so that all roms will work on all carriers
http://forum.xda-developers.com/showthread.php?t=1735482

Man 90% of the time memebers don't read the "everyone read this" thread on any forum
Mostly cause its just filled with rules and etiquite
How have to capture there attention with the title
Sent from my SPH-D710 using xda premium

Tell me about it, I guess you just be glad you did and move on

Lol it was my idea I just pmed it to Mr.highway
Sent from my SPH-D710 using xda premium

incubus26jc said:
I am working on this so that all roms will work on all carriers
http://forum.xda-developers.com/showthread.php?t=1735482
Click to expand...
Click to collapse
That's slick!:good:

hard brick - a pretty paperweight (tonight)
should have been more careful, soft bricked the phone, 2 times trying to change the dpi.
once trying to flash a rom - the rom flash, took it to QHSUSB_DLOAD mode, not impressed but i'll take this downtime as a time to relax.

Another way to avoid a brick; Don't use a mod, theme, tool or ROM until it's confirmed by multiple people in the community that it's working properly. Read the last 3-4 pages of a thread
Sent from my SPH-L710 using Tapatalk 2

fergie716 said:
Another way to avoid a brick; Don't use a mod, theme, tool or ROM until it's confirmed by multiple people in the community that it's working properly. Read the last 3-4 pages of a thread
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
What fun is that?

piiman said:
What fun is that?
Click to expand...
Click to collapse
lol
Sent from my SPH-L710 using xda premium

Simple...
Do like we all have done: read everything you can find and then ask an intelligent question. Otherwise, XDA denizens get grumpy... :cyclops:

Aint' that the truth, I'm one of them!
gtuansdiamm said:
Man 90% of the time memebers don't read the "everyone read this" thread on any forum
Mostly cause its just filled with rules and etiquite
How have to capture there attention with the title
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
I agree with you, I ended up with a soft brick stuck at the samsung glowing logo after trying to unroot because I got a crack the front plastic near the headphone jack. I managed to reset the flash counter and install the rom but odin failed at the end. Now I'm hesitant to flash another ROM. Anyone else here waiting for JellyBean Rom? Definitely take your time and always make sure your computer installs the drivers before doing anything! I got BB to exchange it for me since they couldn't get it to boot and the mystery crack wasn't my fault. I only had it for like 3 days IN A CASE TOO. Happy Flashing dudes.

I'm just glad i saw a forum for the gs3. I would've bricked my phone after i got it.

Another bricker my own fault went to unroot to take in for service and went and loaded a wrong .tar file of the stock system. Anyway...not looking for sympathy..just wanted to say thanks for the forum that gave me the tools to fix my mistake :thumbup:
Sent from my SPH-L710 using Tapatalk 2

Just a question that seems to pertain to this thread, what's the difference between sprint sgs3 android development and original android development?
Sent from my SPH-L710 using xda app-developers app

xblackvalorx said:
Just a question that seems to pertain to this thread, what's the difference between sprint sgs3 android development and original android development?
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Original is usually built from scratch/source. Android development is based from stock, leaks or ports

Shadefactor said:
Original is usually built from scratch/source. Android development is based from stock, leaks or ports
Click to expand...
Click to collapse
So as long as it's in the Sprint sgs 3 forums it's safe?
Sent from my SPH-L710 using xda app-developers app

You are correct sir!

biglos201 said:
I agree with you, I ended up with a soft brick stuck at the samsung glowing logo after trying to unroot because I got a crack the front plastic near the headphone jack. I managed to reset the flash counter and install the rom but odin failed at the end. Now I'm hesitant to flash another ROM. Anyone else here waiting for JellyBean Rom? Definitely take your time and always make sure your computer installs the drivers before doing anything! I got BB to exchange it for me since they couldn't get it to boot and the mystery crack wasn't my fault. I only had it for like 3 days IN A CASE TOO. Happy Flashing dudes.
Click to expand...
Click to collapse
Mystery crack is the best

The Archangel said:
As of right now, the roms for your S3 are not meant to be used on other S3 variants. Bricks might happens or a soft one might happen. Before flashing a Rom make sure you are in the right development section an you read the entire op, twice. Until other devs or experienced users find a way to make them cross compatible, please refrain from using other carriers S3 roms.
Click to expand...
Click to collapse
I think I just made that mistake...wrong directory in a mirror...
ANyhow I ended up with a QHSUSB_DLOAD device...looking hard to unbrick...

Bricked (complicated)

My Galaxy s3 is now what appears to be a hard bricked phone. The only response I get is a red light when I plug it in and a bing when I plug it into the usb port. No recognition by the computer though.
This was caused by me trying to flash the kernel to a very common one (siyah) and after it completed successfully I did a reboot, now it won't turn on or go into CWM recovery or basic android recovery.
I've exhausted every possibility I can think of /googled to solve it such as.
1) Taking the battery out
2) Trying to make Odin recognize it
3) Trying to boot into the various recoveries
4) Trying many a different button combos
5) Leaving it to charge for a while
The only think I can think of that I haven't tried is a USB jig.
My question is, what now? Help me, please.

Well your first issue is that we don't have a siyah kernel for the i747. So, yeah.
You might need to try a jig. I if that doesn't work then you will need to send it off to get jtag fixed.
Sent from my SGH-I747 using xda premium

d3athsd00r said:
Well your first issue is that we don't have a siyah kernel for the i747. So, yeah.
You might need to try a jig. I if that doesn't work then you will need to send it off to get jtag fixed.
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
+1 with sending the device to jtag
Sent from my SGH-I747 using Tapatalk 2

Since you flashed an i9300 kernel, likely with bootloaders, and it won't do anything you will need to send it off for JTAG repair.

JTag time. You've flashed a kernel not meant for our device.

Thanks guys, I figured that was probably my only option. And I feel really dumb now. I'm used to jailbreaking, rooting it seems, requires you to be much more vigilant.
Thanks again.

kshawn123 said:
Thanks guys, I figured that was probably my only option. And I feel really dumb now. I'm used to jailbreaking, rooting it seems, requires you to be much more vigilant.
Thanks again.
Click to expand...
Click to collapse
I'd say it requires common sense. Don't flash something that's not meant for your phone!

mbc663 said:
I'd say it requires common sense. Don't flash something that's not meant for your phone!
Click to expand...
Click to collapse
ding ding ding
Sent from my SGH-I997 using xda premium

mbc663 said:
I'd say it requires common sense. Don't flash something that's not meant for your phone!
Click to expand...
Click to collapse
Not helpful.
task650-JTag time. You've flashed a kernel not meant for our device.
Helpful

kshawn123 said:
Not helpful.
task650-JTag time. You've flashed a kernel not meant for our device.
Helpful
Click to expand...
Click to collapse
What is jtag and what does it do? Just curious lol
Sent from my SAMSUNG-SGH-I747 using xda premium

Smittyzz said:
What is jtag and what does it do? Just curious lol
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Youtube and research my friend. Nearly can fix any phone no matter how bad you mess it up. Very rare that a JTAG can't fix a phone.

xThe Enforcer said:
Youtube and research my friend. Nearly can fix any phone no matter how bad you mess it up. Very rare that a JTAG can't fix a phone.
Click to expand...
Click to collapse
sure you can't get into download mode? try this? http://forum.xda-developers.com/showthread.php?t=1727443 (that link is for AT&T only)

xThe Enforcer said:
Youtube and research my friend. Nearly can fix any phone no matter how bad you mess it up. Very rare that a JTAG can't fix a phone.
Click to expand...
Click to collapse
Thanks for the reply, shouldn't have been so lazy lol, headed to youtube now
Sent from my SAMSUNG-SGH-I747 using xda premium

[Q] Mobile Odin made Brick

I attempted to flash newest CWM and got a brick. The phone will not boot into any mode and I pulled the battery and held the three keys and cannot get it to boot into any mode. Is there a way to flash somehow back to stock and start over?

If you can't detect any life at all from the phone after attempting to charge it or boot into recovery or download mode then I'm sorry but your phone is now hard bricked.. There is no way to fix it unless you get a jaytag repair through mobiletechvideos.com
Sent from my SGH-T999 using xda premium

Bummed
LuigiBull23 said:
If you can't detect any life at all from the phone after attempting to charge it or boot into recovery or download mode then I'm sorry but your phone is now hard bricked.. There is no way to fix it unless you get a jaytag repair through mobiletechvideos.com
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I ordered a warranty replacement but am without a phone for a few days so I am really down that this small app was able to hard brick the darn thing. Makes no sense but I will never use Mobile ODIN ever again! Odd that no warning were there on the thread to download the tool.

photolarry said:
I ordered a warranty replacement but am without a phone for a few days so I am really down that this small app was able to hard brick the darn thing. Makes no sense but I will never use Mobile ODIN ever again! Odd that no warning were there on the thread to download the tool.
Click to expand...
Click to collapse
it does say use at your own risk.. lol I've used mobile odin before and had 0 issues. did you flash the correct cwm? anyways sucks that you got a brick. hopefully you'll get your replacement real soon

Let me see the file you flashed.

It was the touch img I downloaded
Aerowinder said:
Let me see the file you flashed.
Click to expand...
Click to collapse
I do not think I did it with wrong files. I made a tar from the img file I got from clockworkmod.com so I am sure it was clean. I am wondering if perhaps it screwed up because I had changed build.prop to say the device was "Galaxy Nexus" for Wallet to work properly. And maybe that mod I made confused it and somehow flashed something for a Nexus instead and that is why it wont function. If I had it to do again, I would have changed the build.prop back for few moments while I changed the recovery image. All of this was simply to update CWM to newest 6.0.2.8 since ROM Manager told me there was new one. I wish I had ignored it and just said no. Is there no way to hard reset this thing somehow with ODIN or a key combination that say a Samsung employee tool may "flash factory" to it? Seems odd I cannot fix this on my own. No tool nothing?

I've heard the wallet needs to be reset and all that before anything new is flashed.
I haven't flashed anything since the wallet, so I haven't looked into it yet.
Sent from my SGH-T999 using xda app-developers app
---------- Post added at 10:54 PM ---------- Previous post was at 10:50 PM ----------
photolarry said:
Is there no way to hard reset this thing somehow with ODIN or a key combination that say a Samsung employee tool may "flash factory" to it? Seems odd I cannot fix this on my own. No tool nothing?
Click to expand...
Click to collapse
Look for JTAG repair. If you can't even get it to turn on, that's what needs to be done.
It's not a home job - to tools cost several times more than the service and require more specialised knowledge.
If you can get it to turn on, look into making or buying a micro-usb jig - cheap and might work if you have time to mess around.
Sent from my SGH-T999 using xda app-developers app

Yes
Pennycake said:
I've heard the wallet needs to be reset and all that before anything new is flashed.
I haven't flashed anything since the wallet, so I haven't looked into it yet.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
I am certain that is the reason I have hard brick. If I had changed build.prop....changed the recovery with mobile odin....then gone and changed it back afterwards...I am sure it would not have broken the phone. At any rate, I just will have to await warranty replacement since I get mixed readings about this MTV solution that costs almost 100 bucks.

No need to change it back. Once wallet is set up and your card activated, you can set your build.prop back to t999 and Wallet will still work perfectly, it only needs to say Nexus for the install/activation.
Sent from my SGH-T999 using xda premium

That is definitely the reason for what happened.

A little late now but this has been covered
http://forum.xda-developers.com/showthread.php?t=1928196
KCCO

Sad
bfranklin1986 said:
A little late now but this has been covered
http://forum.xda-developers.com/showthread.php?t=1928196
KCCO
Click to expand...
Click to collapse
Wish I could go back 1 day. somehow.

bfranklin1986 said:
A little late now but this has been covered
http://forum.xda-developers.com/showthread.php?t=1928196
KCCO
Click to expand...
Click to collapse
Again, if you simply change your build.prop back to the correct values for the T999 afyer you activate Google Wallet, the entire issue would be avoided and Mobile Odin should be safe to use. I know its too late for that for the OP, but hopefully someone somewhere can learn from this. :beer:
Sent from my SGH-T999 using xda premium

Does anyone have a copy of the link for the JTAG repair ? I know I've seen it before but I cant find it now
Sent from my SGH-T889 using XDA Premium 4 mobile app

Top of the development section. Can't miss it!
Sent from my SCH-I535 using Tapatalk 4

Need help - Probably Bricked S3

Hi all. I am pretty sure I bricked my wife's S3 when I tried to root it using the following http://forum.xda-developers.com/showthread.php?t=1746682 - has nothing to do with the tool kit, more like user error. I have rooted multiple past phones and my current note 2. I got to the odin part and it did it's thing but nevere rebooted to go to the next step. I cannot get into recovery, the computer doesn't recognize the phone now and the screen doesn't do anything. Any ideas? I am pretty sure I bricked it and will need to get a new phone for her.
Appreciate any help or confirmation of a new paper weight.
Sent from my Samsung Galaxy Note 2 via Tapatalk!

Does the device do anything at all when you try to power it on? What exact steps did you take when you attempted to root the device? If the phone does ABSOLUTELY NOTHING, not even vibrate, then your looking at a hard brick. If it does vibrate and/or you can at least get to the splash screen, then it's a soft brick and stuck in a boot loop.
Sent from my SGH-T999 using xda premium
---------- Post added at 11:20 PM ---------- Previous post was at 11:18 PM ----------
And was re-partition checked or unchecked when you tried to root with Odin?
Sent from my SGH-T999 using xda premium

LfnsR said:
Hi all. I am pretty sure I bricked my wife's S3 when I tried to root it using the following http://forum.xda-developers.com/showthread.php?t=1746682 - has nothing to do with the tool kit, more like user error. I have rooted multiple past phones and my current note 2. I got to the odin part and it did it's thing but nevere rebooted to go to the next step. I cannot get into recovery, the computer doesn't recognize the phone now and the screen doesn't do anything. Any ideas? I am pretty sure I bricked it and will need to get a new phone for her.
Appreciate any help or confirmation of a new paper weight.
Sent from my Samsung Galaxy Note 2 via Tapatalk!
Click to expand...
Click to collapse
It does sound like it is bricked. In the future, never unplug the phone while Odin is flashing it. (Im assuming this is what you did?) Always wait until it says PASS, RESET, or FAIL. Sometimes it can hang for 20 or more minutes, but it should always eventually show one of those 3 results.
Just to be sure though. Pull the battery, then put it back in. Try to boot into Download Mode. Try to boot into Recovery. If you can get one of these you are probably not bricked. If you cannot get to either one, and you cannot boot normally, then I am afraid you are bricked.
This does not mean you need to buy a new phone however. What it needs is something called a JTAG fix. You can probably find several shops online that will do this for you, but the one that always gets mentioned around here is http://mobiletechvideos.com
Sorry to hear about your misfortune, but I hope this helps you. If you do get it fixed, next time I suggest rooting with the root66 method. It is much safer imo, at least I see a lot fewer problems with it.
Good Luck!

Thanks for the info. I did get the reset and waites for just over 15 minutes. Nothing was happening and I thought it was bricked so I did unplug it. When I used the same tool to root my N2 it took less than 5 minutes for the entire process.
I will check out the link. Appreciate your help! Thank you.
Sent from my Samsung Galaxy Note 2 via Tapatalk!

Thanks for getting back. He screen doesn't come on at all, but it does vibrate once after a battery pull and then nothing. I followed the steps and got to "reset" in odin where it was waiting for the phone to reboot and after 15+ minutes I thought "crap" bricked it. Unplugged, which I would screw it up which it did. I am going to look into the company DocHoliday77 mentioned below. Worth a shot as cheaper than buying another phone.
Sent from my Samsung Galaxy Note 2 via Tapatalk!

There is this thread don't know if anyone has tried it with tmobile but should be doable in theory. http://forum.xda-developers.com/showthread.php?t=2369125
Sent from my SGH-T999 using xda premium

mt3g said:
There is this thread don't know if anyone has tried it with tmobile but should be doable in theory. http://forum.xda-developers.com/showthread.php?t=2369125
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Thanks for the link. I wonder if its just the aboot.mbn on that image or if there's something else. (Ill read through the threads later to see if its mentioned). Either way if we can make a version using our aboot it should work for us too. I don't think using Sprints will work for us, but I could be wrong.
Definitely interesting though!
Sent from my SGH-T999 using xda premium

DocHoliday77 said:
Thanks for the link. I wonder if its just the aboot.mbn on that image or if there's something else. (Ill read through the threads later to see if its mentioned). Either way if we can make a version using our aboot it should work for us too. I don't think using Sprints will work for us, but I could be wrong.
Definitely interesting though!
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Agreed I just skimmed it the other week and just remembered it a couple days ago and now finally brought its attention over here. Still haven't looked at it yet fully.
Sent from my SGH-T999 using xda premium

DocHoliday77 said:
Thanks for the link. I wonder if its just the aboot.mbn on that image or if there's something else. (Ill read through the threads later to see if its mentioned). Either way if we can make a version using our aboot it should work for us too. I don't think using Sprints will work for us, but I could be wrong.
Definitely interesting though!
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
mt3g said:
Agreed I just skimmed it the other week and just remembered it a couple days ago and now finally brought its attention over here. Still haven't looked at it yet fully.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Inside the 20MB.xz file (open with 7z), is an 80MB img file. Need to dd it somewhere to make any more progress.