Develop Bugs

[Q] what does "E:error in TMP/sideload/package.zip (status 7) mean?

Trying to install a leak thru stock recovery. Does anyone Known how to get past that issue? Thanks
Jake

themadzionist said:
Trying to install a leak thru stock recovery. Does anyone Known how to get past that issue? Thanks
Jake
Click to expand...
Click to collapse
As far as I can tell, I believe it means you're rooted still. I had the same problem so I Odin'd stock UVALH2 and then installed the leak without issue.

Not trying to hijack this thread but have been wondering why do you guys try to install leaks throw stock recovery. It is super easy to root this phone. Why not root install custom recovery then jush flash leaks?
Sent from my SGH-T999

Because you have to be 100% stock to install the leaks. This is the source of the error btw op. Prob not root but a custom recovery. Must be stock everything, modem and kernel must match too.
Sent from my SGH-T999 using xda app-developers app

DocHoliday77 said:
Because you have to be 100% stock to install the leaks. This is the source of the error btw op. Prob not root but a custom recovery. Must be stock everything, modem and kernel must match too.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
This is just not true. I install those OTA leaks every time they are released. Never once used stock recovery to do it.

Aerowinder said:
This is just not true. I install those OTA leaks every time they are released. Never once used stock recovery to do it.
Click to expand...
Click to collapse
Same here, I didn't come from a stock rom. Oh well.

So are you flashing the deodexed roms then?
Im talking about the actual ota you download from somewhere like sammobile.
It patches the existing system (UVDLI8 patches UVALI5) if anything is modded in UVALI5 the patch wont work, or if it does it can cause problems.
If you're flashing roms from development section then yes you can flash normally with custom recovery. But those roms are based on the otas, they're not the actual otas themselves.
Sent from my SGH-T999 using xda app-developers app

I don't bother with TW custom roms. Not really my thing, but I understand why people might want them.
I flash the OTA updates from the link in my signature (sammobile) in order to pull modems. Although there hasn't been a point lately, because you are working at the speed of light. But I flashed UVALEM, UVALH2, I1, 2, 3, 4, 5, 6, you get the idea.
Are you using TWRP? That recovery might not work with the OTA updates, but I've proven myself, and through many other people, that you can indeed flash OTA leaks from sammobile with CWM Touch 6.0.1.2. I'm unsure about the workings of TWRP because I don't use it. I don't use it because I don't like the buggy keyboard.

Yeah i tried everyway possible. The only way that worked was going uvahl2 thru odin, and then thru stock recovery i applied the ota jb uvdli7 from external sd. It was the only way to get it to work. I think the reason why the error message was coming up was because even though i unrooted my phone, the phone status still said "modified". Once i reflashed hl2 and it didn't say modified it updated the leak.

I think its going to take a video to prove you don't need stock recovery for this operation.

Aerowinder said:
I don't bother with TW custom roms. Not really my thing, but I understand why people might want them.
I flash the OTA updates from the link in my signature (sammobile) in order to pull modems. Although there hasn't been a point lately, because you are working at the speed of light. But I flashed UVALEM, UVALH2, I1, 2, 3, 4, 5, 6, you get the idea.
Are you using TWRP? That recovery might not work with the OTA updates, but I've proven myself, and through many other people, that you can indeed flash OTA leaks from sammobile with CWM Touch 6.0.1.2. I'm unsure about the workings of TWRP because I don't use it. I don't use it because I don't like the buggy keyboard.
Click to expand...
Click to collapse
Lol! Im just usually online when they drop! Theres only been a couple where I wasn't.
If cwm touch recovery does flash these otas as is then it just means they've disabled the check the ota does to verify the system meets the requirements. Or they just disable the recovery check/patch to protect their own recovery. I hope its the latter.
Not saying it cant be done but till now I hadn't heard of it. I use TWRP (just personal preference) but actually never bothered to try with it becsuse too many people early on got errors like the OP when anything wasn't matching stock.
I use Mobile Odin for the otas since it not only allows me to meet the stock requirements but it also injects root so you never have to worry about rerooting or anything.
At this point I just want to know how CWM does the otas. Does it completely disable the system check, or just the recovery part of that check.
Sent from my SGH-T999 using xda app-developers app

The zip file still runs the verification process. I've always done it properly, so I don't know what a flashing failure looks like. I have a background in programming, and I'm an amateur for sure, but I suspect that when the update checks for stock recovery, it thinks CWM is the stock recovery. I'm not sure of the code behind this, but I equate it to user-agents in browsers. CWM is saying it is stock recovery, OTA update accepts that, or some such. Without seeing the code, I can't say for sure, but this is my guess.
You get the option to disable the recovery patch, and to keep root when you attempt to exit recovery after the OTA flash.
I never saw much use for Mobile Odin. I did buy it, because the dev is amazing, but I've never used it. It allows you to flash zip files? I've always just done it through CWM. I flash everything through CWM... even other recoveries.

However it does it, I guess it works. Only reason I wanted to know if it bypassed the entire check is because that could cause problems for the more inexperienced.
Yeah, I love Chainfires work. The ability to flash zips with Mobile Odin was just added a few weeks ago and has worked flawlessly for me.
Sent from my SGH-T999 using xda app-developers app

fix it
you need to flash your kernel to man. most stock kernel wouldnt work with cyanogenmod. Update your kernel with unofficial kernel that are compatible with your device

raaaaarrrr!!!
Has no one figured this out yet...i unrooted my phone using odin mobile ...then attempted to do the 4.3 manual update and im getting the same errors! this is bs...i even tried to use odin to flash mdl and it dint do anything to my phone. very unhappy.

atheistics1 said:
Has no one figured this out yet...i unrooted my phone using odin mobile ...then attempted to do the 4.3 manual update and im getting the same errors! this is bs...i even tried to use odin to flash mdl and it dint do anything to my phone. very unhappy.
Click to expand...
Click to collapse
Well, first, there is not an Odin flashable 4.3 file, but you said you tried to flash MDL? Not sure what this is exactly. The most likely issue is you are using an incompatible recovery. Probably one that is too old.

I think you are totally confused between odin flashable files and recovery flashable files....

Okay so maybe this will help...omni version is jfltecan...which is Canadian and my baseband is l720vpuemja ...that's sprint which my phone is...I'm getting no data...and I'm not able to revert back to 4.3 or 4.2.
Sent from my SGH-I337M using XDA Premium 4 mobile app

you should probably consider asking in your devices forum. if you use anything here youll likely brick.
Sent from my T-Mobile MyTouch 3G Slide(HTC Espresso) using Tapatalk 2

wolverine
themadzionist said:
Trying to install a leak thru stock recovery. Does anyone Known how to get past that issue? Thanks
Jake
Click to expand...
Click to collapse
Just downgrade to 4.0.4 and install cwm then flash it through it. it works for me.

[Q] Tmobile update on stock rooted rom

Can I let the Tmobile Update download and flash if I am rooted on the stock ROM and have Clockwork recovery? I would use ota root keeper to disable root also before the update.
Sent from my SGH-T999 using Tapatalk 2

When it is rooted even if you try to use the OTA update it won't let you, while rooted, you could alternatively flash the update via ODIN w/ root support. Or try some of the sweet ROMs available , the reason I switched to a custom ROM because I was going to have to erase my phone anyway if I wanted to update, so I thought why not just try a custom ROM?
I use LiquidSmoothRC7, but if you want a more stock feel with touchwiz you can try Wicked, Wicked stays true to the "official stock ROMs" and just adds roots and tweaks the ROM to make it as stable as possible

If you are rooted, with a custom recovery, there is absolutely no reason for you to be playing around with Odin or OTAs... your updates are available in the development section

cobraboy85 said:
If you are rooted, with a custom recovery, there is absolutely no reason for you to be playing around with Odin or OTAs... your updates are available in the development section
Click to expand...
Click to collapse
OR you could listen to this dude

cobraboy85 said:
If you are rooted, with a custom recovery, there is absolutely no reason for you to be playing around with Odin or OTAs... your updates are available in the development section
Click to expand...
Click to collapse
Actually there is. There are 10 partitions rewritten with the Odin and OTA update. Only 5 get rewritten if you flash via custom recovery, so you don't get the full update.
Sent from my SGH-T999 using Tapatalk 2

zul8er said:
Can I let the Tmobile Update download and flash if I am rooted on the stock ROM and have Clockwork recovery? I would use ota root keeper to disable root also before the update.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
go to doc's thread, flash his firmware update, reboot, then flash whatever JB ROM you desire. there is absolutely no need to ODIN your phone with the OTA fw, resetting your device completely. you just need to make sure you flash the latest firmware first before you flash a ROM that is based off the latest OTA

cobraboy85 said:
go to doc's thread, flash his firmware update, reboot, then flash whatever JB ROM you desire. there is absolutely no need to ODIN your phone with the OTA fw, resetting your device completely. you just need to make sure you flash the latest firmware first before you flash a ROM that is based off the latest OTA
Click to expand...
Click to collapse
I stayed on 4.0.4 with the base of UVLH2 and just clean installed JB roms so should I update the base? Or is it already updated?
Sent from my SGH-T999 using xda app-developers app

Towle said:
Actually there is. There are 10 partitions rewritten with the Odin and OTA update. Only 5 get rewritten if you flash via custom recovery, so you don't get the full update.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Some of those 10 partitions that are getting rewritten are... for one, your recovery... so that makes 9 actually...
My point is, and I'm not trying to be argumentative in any way, merely objective, is that unless it is reformatting the ext4 partition to new file structure (for example) there should be no need to do this. I suppose I would ask somebody to define in depth "rewritten" and how exactly this is being done and why. Every single update we have had since the release of this device I have not once updated my own device with odin merely to put it back to stock. And I have run into zero issues. Seems like a waste of time to me unless there is something highly critical being restructured entirely. In the end, its all the same disk, and disk size for any given partition.
---------- Post added at 05:51 AM ---------- Previous post was at 05:47 AM ----------
neim81094 said:
I stayed on 4.0.4 with the base of UVLH2 and just clean installed JB roms so should I update the base? Or is it already updated?
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
If you are on LH2, with that same baseband, I would go ahead and update your baseband via docs packaged update in his thread, and just reboot, then move on to the jelly bean updates. Do a factory reset through recovery before you flash the JB ROM tho since you are coming from a completely different version of android.

zul8er said:
Can I let the Tmobile Update download and flash if I am rooted on the stock ROM and have Clockwork recovery? I would use ota root keeper to disable root also before the update.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
If you want to avoid all the weird miscellaneous problems listed in the Q&A forum, update using Odin and the rooted rom in Docs' thread. If you choose not to use Odin do not be surprised if odd things happen.

Just stating my experience, I was rooted stock ics and ran the ota update. I was able to update, keep root and ran stock jelly bean without any problems at all.
Now I am running frosty jelly and still no problems at all. I am not saying for you to do it (dont want anyone blaming me) just stating that it can be done. Do whats most comfortable for you.
Sent from my SGH-T999 using xda app-developers app

jcbofkc said:
If you want to avoid all the weird miscellaneous problems listed in the Q&A forum, update using Odin and the rooted rom in Docs' thread. If you choose not to use Odin do not be surprised if odd things happen.
Click to expand...
Click to collapse
Again looking for some technical clarity here. Haven't had a single issue myself. With anything. And I have not factory odined my device once since I got it. It is not critical to do this, otherwise I would be suffering from "weird miscellaneous problems"
Hopin doc can jump in here and set me straight if I am wrong, but it seems to me you will be fine just updating your radios and then moving to the latest build (4.1.1) as long as you clear data before flashing your ROM of choice

cobraboy85 said:
Again looking for some technical clarity here. Haven't had a single issue myself. With anything. And I have not factory odined my device once since I got it. It is not critical to do this, otherwise I would be suffering from "weird miscellaneous problems"
Hopin doc can jump in here and set me straight if I am wrong, but it seems to me you will be fine just updating your radios and then moving to the latest build (4.1.1) as long as you clear data before flashing your ROM of choice
Click to expand...
Click to collapse
You could very well be correct. Not trying to debate you.
but....I am seeing thread after thread of issues. Based on experience I suggest using the full proof method. I have updated many phones using many different methods and never have problems, but apparently many have had issues.
I also hope Doc chimes in on this thread.

jcbofkc said:
You could very well be correct. Not trying to debate you.
but....I am seeing thread after thread of issues. Based on experience I suggest using the full proof method. I have updated many phones using many different methods and never have problems, but apparently many have had issues.
I also hope Doc chimes in on this thread.
Click to expand...
Click to collapse
Totally dig it. And yeah, just want to know what exactly is being done differently in odin

cobraboy85 said:
Totally dig it. And yeah, just want to know what exactly is being done differently in odin
Click to expand...
Click to collapse
If I understand the process correctly
ODIN flashes the entire phone OS like the kernel, Rom, baseband, etc
Using recovery to flash only updates the Rom,recovery,boot,kernel
Sent from my SGH-T999

neim81094 said:
If I understand the process correctly
ODIN flashes the entire phone OS like the kernel, Rom, baseband, etc
Using recovery to flash only updates the Rom,recovery,boot,kernel
Sent from my SGH-T999
Click to expand...
Click to collapse
Sorry, I will clarify, I am curious to know why Odin is such a critical issue. I know how it works as far as it being a flashing tool

I am not sure maybe it's just preference and how much you want to use your computer and what how much you want to download etc
Sent from my SGH-T999

neim81094 said:
I am not sure maybe it's just preference and how much you want to use your computer and what how much you want to download etc
Sent from my SGH-T999
Click to expand...
Click to collapse
The file used to flash with Odin is much larger because it is a complete rom. The OTA is a patch that attempts to patch and modify existing files.

I basically said that on the last post not the one you quoted
Sent from my SGH-T999

Finally got the time to Odin Route66 Jelly bean.
Sent from my SGH-T999 using Tapatalk 2

Everything good?

T999L Roms

As of right now i can install any Rom from the T999 that does not require the new boot loader upgrade but i get a status 7 when i try to install the newer roms is there any boot loader for the T999L that supports the Roms

Edit the update script of the zip files to remove the bootloader asserts.

Aerowinder said:
Edit the update script of the zip files to remove the bootloader asserts.
Click to expand...
Click to collapse
How would i do that

There are lines in the with in the roms.zip
meta-inf>com>google>android>updater-script>
assert(getprop("ro.bootloader") =="t999.......) and the three other bootloaders it checks for.
I'm guessing you can remove these lines and rezip and it will flash, but I am not going to do so, and don't plan on trying... I can remove those lines and rezip it for you to try and flash and see how it goes. I would put 20$ down that it won't harm the phone but not 600 (new) or 180 (insurance) lol.

Until someone else tries i will wait

I edit lines in there when roms fail to install cause they are specific to att, just incase anyone else really wants it, just post and let me know. I'm off til Thursday so I have time at some point each day to do so. if anyone with more knowledge wants to confirm let me know, so that there is more comfort to this.

If you could edit it out that would be nice and upload the new package that would be nice

Bray90820 said:
If you could edit it out that would be nice and upload the new package that would be nice
Click to expand...
Click to collapse
I'll work on it in a little bit. Got to do one for an att rom I wanna try anyways. What rom did you wanna try?

Cyanogenmod 10.1 RC4

Wait are you going to be editing the rom or the bootloader

Updater Script in the .zip for the rom.

I was actually looking for the bootloader so i could install whatever rom i wanted

Bray90820 said:
I was actually looking for the bootloader so i could install whatever rom i wanted
Click to expand...
Click to collapse
Ohhhhh not possible yet. And if I remove those and it installs fine, you may still run into errors cause the CM team asks for people to be on the latest bootloaders to have it run no issues.
I'm sure your phone will be apart of the CM/AOSP builds soon enough.

Well I do have RC2 on it right now

That was before all the changes. My personal favorite

I Guess i'll just wait then

Bray90820 said:
Well I do have RC2 on it right now
Click to expand...
Click to collapse
How did you install this? Did you edit the updater-script or did it just flash over?
I'm using TWRP on a T999L and am looking to go custom ROM with CM10.1, but am trying to find more info. I know that I can always go back since @DocHoliday77 & @MotoDefier got the stock ROM all squared away: http://forum.xda-developers.com/showthread.php?t=2308514

DJ_SpaRky said:
How did you install this? Did you edit the updater-script or did it just flash over?
I'm using TWRP on a T999L and am looking to go custom ROM with CM10.1, but am trying to find more info. I know that I can always go back since @DocHoliday77 & @MotoDefier got the stock ROM all squared away: http://forum.xda-developers.com/showthread.php?t=2308514
Click to expand...
Click to collapse
The d2tmo has been updated tir the T999L and the latest nightly is fully working without any modifications needed

Awesome!! Thanks, I was thinking that I might have to flash the ROM then flash the T999L modem. What date are you using? Any issues?
Sent from my SGH-T999L using xda app-developers app

DJ_SpaRky said:
Awesome!! Thanks, I was thinking that I might have to flash the ROM then flash the T999L modem. What date are you using? Any issues?
Sent from my SGH-T999L using xda app-developers app
Click to expand...
Click to collapse
No issues on june 18th

ZV8 to ZVA Modified OTA (Flash in TWRP)

Thanks to everyone working on the OTA, such as Savoca and Autoprime checking the OTA status.
The ZVA update has a lot of good and some bad things. I've "tinkered" with Samsung OTAs before and gotten them to flash but there was always a problem with Sprint's Chameleon implementation on Samsung that caused things not to behave the same when flashing the modified zip.
Fortunately, that doesn't seem to be the case with LG. :good:
So here are two ZIPs for your use. Use at your discretion and as usual, I give my standard disclaimer: Your phone, your flash, your responsibility.. not mine.
Link to ZIPs:
http://www.rwilco12.com/downloads.php?dir=Files/Garwynn Projects/LS980/ZV8toZVA
Why two versions? Both skip recovery and revert aboot image so that Loki can still work.
But during first set of tests I received an assert error on magazines.odex.
If you get this try the second one, in which I removed that assert and update.
If you get a build.prop assert error on the second you'll want to try and find yourself a stock version and flash again.
For me I had to do the TOT again to get it to work.
Now the other bits of information:
1) Both remove the device assert because TWRP doesn't use that model ID. So make sure you only use this on the SPRINT model.
2) I do recommend taking a backup before as I had some funky results after the update. One time system disappeared... another time took especially long to restart. After doing a second time it does seem to be working properly. So may not hurt to back up right after flashing the zip so that you have a good copy of ZVA to work off of.
3) You can stay rooted and you do not need to re-root afterwards. The first time I got a prompt from SuperSU to update the su binary, but not the second time. In either case root was not checked during OTA so you don't need to mess with it.
Any questions feel free to let me know. Again thanks to all and enjoy!
(Added 10:50 CST)
I want to also caution one thing at the moment. Those wanting to keep using AOSP ROMs should not flash ZVA at the moment.
At the moment it's causing a boot loop and several of us are trying to figure out what the cause is.

Awesome! Testing this now, I'll post my own results too.
Sent from my LG-LS980 using xda app-developers app

One other precaution because it seems a person just bricked testing radio packages...
Don't be a hero. If it's acting up, go back to recovery and restore a backup or flash the ZV8 TOT.
Updates are cool and everyone wants it, but it's not worth bricking over.

garwynn said:
Thanks to everyone working on the OTA, such as Savoca and Autoprime checking the OTA status.
The ZVA update has a lot of good and some bad things. I've "tinkered" with Samsung OTAs before and gotten them to flash but there was always a problem with Sprint's Chameleon implementation on Samsung that caused things not to behave the same when flashing the modified zip.
Fortunately, that doesn't seem to be the case with LG. :good:
So here are two ZIPs for your use. Use at your discretion and as usual, I give my standard disclaimer: Your phone, your flash, your responsibility.. not mine.
Link to ZIPs:
http://www.rwilco12.com/downloads.php?dir=Files/Garwynn Projects/LS980/ZV8toZVA
Why two versions? Both skip recovery and revert aboot image so that Loki can still work.
But during first set of tests I received an assert error on magazines.odex.
If you get this try the second one, in which I removed that assert and update.
If you get a build.prop assert error on the second you'll want to try and find yourself a stock version and flash again.
For me I had to do the TOT again to get it to work.
Now the other bits of information:
1) Both remove the device assert because TWRP doesn't use that model ID. So make sure you only use this on the SPRINT model.
2) I do recommend taking a backup before as I had some funky results after the update. One time system disappeared... another time took especially long to restart. After doing a second time it does seem to be working properly. So may not hurt to back up right after flashing the zip so that you have a good copy of ZVA to work off of.
3) You can stay rooted and you do not need to re-root afterwards. The first time I got a prompt from SuperSU to update the su binary, but not the second time. In either case root was not checked during OTA so you don't need to mess with it.
Any questions feel free to let me know. Again thanks to all and enjoy!
Click to expand...
Click to collapse
Only question I can come up with is should folks be on stock rooted ODEX rom before doing this or is ANY rooted ODEX/DEODEX rom ok? If you don't know one way or the other, what where you on when you did it?
I am "assuming" by the stock statement you meant stock odex rom but figured I'd ask just to make it crystal clear for all. As we've seen in the last 24hr, crystal clear is very much needed.
Thanks!

Any chance this will for stock based ROMs?
Sent from my LG-LS980 using xda app-developers app

@garwynn do you have the stock build.prop from the zv8 update? not the one from the stock rooted rom.

mrrogers1 said:
Only question I can come up with is should folks be on stock rooted ODEX rom before doing this or is ANY rooted ODEX/DEODEX rom ok? If you don't know one way or the other, what where you on when you did it?
I am "assuming" by the stock statement you meant stock odex rom but figured I'd ask just to make it crystal clear for all. As we've seen in the last 24hr, crystal clear is very much needed.
Thanks!
Click to expand...
Click to collapse
If you have debloated the ROM, it probably won't work. I ended up flashing the TOT (pure stock) to get it to flash.
I want to also caution one thing at the moment. Those wanting to keep using AOSP ROMs should not flash ZVA at the moment.
At the moment it's causing a boot loop and several of us are trying to figure out what the cause is.

youdug said:
@garwynn do you have the stock build.prop from the zv8 update? not the one from the stock rooted rom.
Click to expand...
Click to collapse
Sorry, didn't pull it before I flashed. Really should have.
If I flash it again today I'll pull it.

garwynn said:
Sorry, didn't pull it before I flashed. Really should have.
If I flash it again today I'll pull it.
Click to expand...
Click to collapse
im not sure if ill need it but might as well grab it just in case before i start.
thanks man.

mrrogers1 said:
Only question I can come up with is should folks be on stock rooted ODEX rom before doing this or is ANY rooted ODEX/DEODEX rom ok? If you don't know one way or the other, what where you on when you did it?
I am "assuming" by the stock statement you meant stock odex rom but figured I'd ask just to make it crystal clear for all. As we've seen in the last 24hr, crystal clear is very much needed.
Thanks!
Click to expand...
Click to collapse
Sorry, didn't clarify the second. I tried stock odex ROM and didn't work. That's why I went the TOT route.

Wasn't able to flash. I got a bunch of asset errors.
Sent from my LG-LS980 using xda app-developers app

Williek113 said:
Wasn't able to flash. I got a bunch of asset errors.
Sent from my LG-LS980 using xda app-developers app
Click to expand...
Click to collapse
i flashed testupdate 2 no problems here

Williek113 said:
Wasn't able to flash. I got a bunch of asset errors.
Sent from my LG-LS980 using xda app-developers app
Click to expand...
Click to collapse
What rom were you on?
latoso said:
i flashed testupdate 2 no problems here
Click to expand...
Click to collapse
and what rom were you on?

mrrogers1 said:
What rom were you on?
and what rom were you on?
Click to expand...
Click to collapse
i was on stock rom

latoso said:
i was on stock rom
Click to expand...
Click to collapse
Stock rooted with just TWRP or Stock rooted Odex or Deodex that @youdug provided here >>> http://forum.xda-developers.com/showthread.php?t=2560115?

latoso said:
i was on stock rom
Click to expand...
Click to collapse
All stock with twrp right?
Sent from my LG-LS980 using xda premium

mchlbenner said:
All stock with twrp right?
Sent from my LG-LS980 using xda premium
Click to expand...
Click to collapse
yes stock rom with twrp

Flashed from stock rom with TWRP 2.6.3.3 using testupdate.zip with no issues. Did not need to use update 2.

If someone that has NOT ran this yet could, please post or PM me their build.prop from the stock + TWRP rom before doing the update?
Thanks:good::good:

garwynn said:
One other precaution because it seems a person just bricked testing radio packages...
Don't be a hero. If it's acting up, go back to recovery and restore a backup or flash the ZV8 TOT.
Updates are cool and everyone wants it, but it's not worth bricking over.
Click to expand...
Click to collapse
RIP @dougie187
:victory:

[ROM][STOCK][PORT][*ODIN*] Stock rooted TW 4.4.2 (ported from sprint SGS3)

This, for the most part, is not my work. What this is is @DocHoliday77 's port of the sprint SGS3 4.4.2 ROM, which I have repackaged into an Odin .tar.md5; the point being for those who would rather flash this via ODIN instead of twrp/cwm.
You can thank DocHoliday77 for his hard work here, all I did was edit the build.prop and repackage with multiboot. Download link below.
Included in this .tar.md5:
-System image, with build.prop edited to accurately reflect our device.
-multiboot 2.12 recovery image (for those who don't know, it's TWRP 2.7 with the added ability to boot other ROMs in a sandbox)
-KT747 boot image, which is included with the original port flashable zip.
YOU MUST HAVE AN OFFICIAL 4.3 BOOTLOADER / MODEM INSTALLED. THERE IS NO WAY TO CIRCUMVENT THIS.
Download: Stock rooted 4.4.2 TW

Nice
First too. Didn't even realize
Sent from my SGH-I317 using Tapatalk

Thanks:laugh:

Not going to need this but great work man!

Choice for a flash able zip?
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app

Duffman14 said:
Choice for a flash able zip?
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
There already is one here
http://forum.xda-developers.com/showthread.php?t=2749495

talkingmonkeys said:
There already is one here
http://forum.xda-developers.com/showthread.php?t=2749495
Click to expand...
Click to collapse
Ty sir
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app

You're all quite welcome. I may reupload sometime soon with boot loader / modem included to make it easier for people. (There would be two different versions, one with the at&t modem and one with the bell/telus/rogers one)

Can anyone confirm whether or not this is a daily driver?

n_alvarez2007 said:
Can anyone confirm whether or not this is a daily driver?
Click to expand...
Click to collapse
Aside from not being able to send MMS with WiFi on (SMS works fine) this should be fully capable of being a DD.

Use Handcent messaging app, set it as default and mms while Wi-Fi is active will work

Restl3ss said:
This, for the most part, is not my work. What this is is @DocHoliday77 's port of the sprint SGS3 4.4.2 ROM, which I have repackaged into an Odin .tar.md5; the point being for those who would rather flash this via ODIN instead of twrp/cwm.
You can thank DocHoliday77 for his hard work here, all I did was edit the build.prop and repackage with multiboot. Download link below.
Included in this .tar.md5:
-System image, with build.prop edited to accurately reflect our device.
-multiboot 2.12 recovery image (for those who don't know, it's TWRP 2.7 with the added ability to boot other ROMs in a sandbox)
-KT747 boot image, which is included with the original port flashable zip.
YOU MUST HAVE AN OFFICIAL 4.3 BOOTLOADER / MODEM INSTALLED. THERE IS NO WAY TO CIRCUMVENT THIS.
Download: Stock rooted 4.4.2 TW
Click to expand...
Click to collapse
I cant seem to get this to flash with odin..... STOCK_ROOTED_4.4.2_TW_I747.tar.md5 is invalid

Can I install on i747m like this?
Sent from my SGH-I747M using XDA Premium 4 mobile app

Confirmed, this is not working at the moment. The system image is broken and I'm not sure why, bear with me

chivas1311 said:
Can I install on i747m like this?
Sent from my SGH-I747M using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Not sure as I cant read your language, sorry. But one part says its LI1 and another says ND3. First, the bootloader/firmware version MUST be a 4.3 build.
Second, what is the ND3? Is that some sort of test build? Or did I miss something somewhere?
Restl3ss said:
Confirmed, this is not working at the moment. The system image is broken and I'm not sure why, bear with me
Click to expand...
Click to collapse
Does it fail at the md5 check?
Sent from my SGH-T999 using Tapatalk

DocHoliday77 said:
Not sure as I cant read your language, sorry. But one part says its LI1 and another says ND3. First, the bootloader/firmware version MUST be a 4.3 build.
Second, what is the ND3? Is that some sort of test build? Or did I miss something somewhere?
Does it fail at the md5 check?
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
It does yeah, but I tried it without the md5sum and it failed as well, just after nand write start. On the download here the md5 check fails because the binary is supposedly invalid.
The system image was made by running mkfs-yaffs2-x86 on the system folder from the original port zip, running unyaffs does unpack it, but something is definitely not right with this image, I tried using unpack-ext4 on windows which usually works on odin system images but it didn't on this one.

Making an odin flashable isnt a straight forward process for the S3 it seems. MrRobinson is the only one I know of off hand that has an effective process to do so. He only gives clues to his process in his op. Ive done one a long time ago, but I think what I had to do was take tar the system.img dumped directly from the device using the dd command.
If I remember right, it had to be done immediately after flashing, been too long though so I cant remember for certain.
So if I am recalling it correctly, flash the rom, factory reset, then while still in recovery, using either adb or the built in terminal emulator, use dd to dump the image to your sd card.
Sent from my SGH-T999 using Tapatalk

DocHoliday77 said:
Not sure as I cant read your language, sorry. But one part says its LI1 and another says ND3. First, the bootloader/firmware version MUST be a 4.3 build.
Second, what is the ND3? Is that some sort of test build? Or did I miss something somewhere?
Does it fail at the md5 check?
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
It's a Stock 4.3 bulid from Telcel, Mexico, in SamMobile says this:
In english:

Ok, thanks for the clarification on that. Once its confirmed working, you should be able to flash it just fine. If that baseband is not 4.3 though, you will likely have to update it as well.
For now though, you can always just flash the rom this was built from. Should get you exactly the same thing, only the method is different.
Sent from my SGH-T999 using Tapatalk