I didn't find an image here, so I built my own. Details are here: http://www.slatedroid.com/index.php?/topic/16152-mod-hri66-system-backup-and-root-prepped/
Basically, I took their HRI39 system.img, injected the HRI66 changes via a system dump I made, then added su, Superuser.apk and Busybox. You still need fastboot and adb to complete the process but I find it easier to use this system.img for my testing versus having to go back and re-run HRI39 system.img, then patch to HRI66, then add su / Superuser.ask / Busybox.
As always, Use At You Own Risk. I believe I got all the HRI66 files, but I might have missed something. EDIT: I did miss a few, reuploading a build 2. I got all the patches, but missed the two new lib files.
Thanks, much appreciated!
Nice. Hey do you think you could throw together a boot.img for me. Noone in the 1.5 Ghz post will reply to me about it and I would really like the option to be able to reset my kernel to stock. I would do it myself but I haven't the slightest on how to do that
jmc2543 said:
Nice. Hey do you think you could throw together a boot.img for me. Noone in the 1.5 Ghz post will reply to me about it and I would really like the option to be able to reset my kernel to stock. I would do it myself but I haven't the slightest on how to do that
Click to expand...
Click to collapse
X2 really good idea.
Sent from my Xoom using XDA Premium App
Not following 100% -- do you just need a stock boot.img (unaltered)? I figured that it was already floating around here.
EDIT: Someone already posted HRI39 stock here -- http://forum.xda-developers.com/showthread.php?t=988942. You can grab the stock boot.img from that.
HRI66 was only a system update - the kernel and ramdisk were not touched.
nice work!
Btw, the last step for rooting requires a boot.img that is, in itself, unlocked. If you use stock, the adb remount won't work. Someone PM'd me and I forget that a stock boot.img wouldn't work. So, you'd still have HRI66, but rooting would still be a problem to enable.
roebeet said:
Not following 100% -- do you just need a stock boot.img (unaltered)? I figured that it was already floating around here.
EDIT: Someone already posted HRI39 stock here -- http://forum.xda-developers.com/showthread.php?t=988942. You can grab the stock boot.img from that.
HRI66 was only a system update - the kernel and ramdisk were not touched.
Click to expand...
Click to collapse
Yea I posted those files a week or so ago. Guess I showed my arse there a little. I feel like a total noobe at the moment with not realizing that the boot.img was the same. That makes sense. I was under the impression that being that we are seeing a little bit more of a snap to things that something was altered with the kernel or something in the boot.img was different. Thanks for clearing that up.
jmc2543 said:
Yea I posted those files a week or so ago. Guess I showed my arse there a little. I feel like a total noobe at the moment with not realizing that the boot.img was the same. That makes sense. I was under the impression that being that we are seeing a little bit more of a snap to things that something was altered with the kernel or something in the boot.img was different. Thanks for clearing that up.
Click to expand...
Click to collapse
No worries - I feel kinda dumb that I responded by directing you to your own post. Doh! I need to look at usernames more, when I do that.
Sorry, stupid question, thought this might be relevant to the wifi only model, found the answer.
Dwould you mind if I include this in RootMyXoom?
Sent from my Xoom using XDA App
nice work, thanks
jwtyler said:
Dwould you mind if I include this in RootMyXoom?
Sent from my Xoom using XDA App
Click to expand...
Click to collapse
Sorry, I didn't see this right away -- feel free, of course! It's meant to be used for everyone.
Been so busy with the GTAB Woot! stuff the last few days that I haven't had a chance to update myself on the Xoom posts.
is this esstentially an image for a stock kernel rooted wifi xoom?
Sent from my Xoom using Tapatalk
100mbit mirror:
http://gititbit.ch/xRx6 - xoom.hri66.system.build2.zip
Related
So what is this?
I have always wondered would it be safe and easier to flash custom roms using Odin if we had odin packages for custom roms. So I started to poke around and research. Rwilco12 has been a great help. I was working on this before new year and was getting somewhere. I had created quite a few full Odin tars for couple ROMs but none of the packages had successfully flashed the whole ROM. These tar packages are similar to the stock .tar files that sextape posts but they are rooted and are not stock Sprint builds.
As some of you may know, I got sick and caught flu on new year so had to stop working on this and hasn't worked on this since 27th Dec plus now new college semester has started so I am somewhat short on time.
So the reason I am posting this here is that I want to know from you whether you would be interested in using Odin to flash custom roms? OR Would you rather continue to flash custom ROMs using CWM?
If more people are interested in this and would seriously use these to flash custom ROMs then I will continue to work on it. I want honest responses. I wouldn't mind a bit if you think Odin custom ROM flashing is not the way you would go. Also you can use the poll for your response.
I will appreciate any useful responses.
Im actually working on something similar for my Note 2 rom. Gonna have the choices of a zip, tar or aroma install. Going the extra tar route to include files for people rolling back from higher firmware with errors so they dont have to flash modems and the fix separately and can just odin 1click back. It would actually probably work well for any rom it makes it much easier for a noob to flash without fear of using an unsafe kernel on et4g and without having to learn everything all at once before they can try something out. Odin has been fairly safe for me minus one incident with a leak when I flashed an incomplete tar and bricked nyself but other than that never had a single hiccup using odin with complete files. It would make it easy for people to flash without recovery as well since they could mobile odin the new rom instead :thumbup:
I give this idea :thumbup::thumbup:
Sent from my SPH-L900 using Xparent ICS Tapatalk 2
It has its ups of convenience but is not practical for developers. From my understanding, it is much easier to break into a zip file to update stuff for the new builds fix bugs and find bugs to fix, as well as it being easier to build a zip to flash. Also, as the end user of a ROM, I like to go in and add or remove things before I flash my ROM. I can't do that easily if at all if it is Odin based.
Sent from my SPH-D710 using xda app-developers app
I've been talking about this for months, since we had the eMMC super brick issue. No one listened...
Sent from my SPH-D710 using xda premium
graydiggy said:
It has its ups of convenience but is not practical for developers. From my understanding, it is much easier to break into a zip file to update stuff for the new builds fix bugs and find bugs to fix, as well as it being easier to build a zip to flash. Also, as the end user of a ROM, I like to go in and add or remove things before I flash my ROM. I can't do that easily if at all if it is Odin based.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
I hear you but its only couple linux commands to unpack the system folder and then you can make any changes.
Mattix724 said:
I've been talking about this for months, since we had the eMMC super brick issue. No one listened...
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
I heard you, I just had no clue how to pack a tar for odin yet lmao. I know how to create one in linux in place of a rar or zip file but didnt have the first clue what I needed to pack for odin to pick it up and flash. Now I have a nifty little tool that builds the oneclicks for me
Sent from my SPH-L900 using Xparent ICS Tapatalk 2
-EViL-KoNCEPTz- said:
I heard you, I just had no clue how to pack a tar for odin yet lmao. I know how to create one in linux in place of a rar or zip file but didnt have the first clue what I needed to pack for odin to pick it up and flash. Now I have a nifty little tool that builds the oneclicks for me
Sent from my SPH-L900 using Xparent ICS Tapatalk 2
Click to expand...
Click to collapse
Is this the tool you use that came from the N2 forum?
http://www.xda-developers.com/android/package-odin-roms-with-gzip-compression-hidden-menu-gets-an-update/
And Blues - I was attempting this for the deodexed and couldn't get it to clean flash properly. I'd be interested in seeing if odexed/deodexed can be used in this manner since there were people asking for it.
MoHoGalore said:
Is this the tool you use that came from the N2 forum?
http://www.xda-developers.com/andro...-gzip-compression-hidden-menu-gets-an-update/
And Blues - I was attempting this for the deodexed and couldn't get it to clean flash properly. I'd be interested in seeing if odexed/deodexed can be used in this manner since there were people asking for it.
Click to expand...
Click to collapse
Might be im not at my pc to check the package name atm. But if its the one garwynn told me about then yeah that be it
Sent from my SPH-L900 using Xparent ICS Tapatalk 2
BluesRulez said:
I hear you but its only couple linux commands to unpack the system folder and then you can make any changes.
Click to expand...
Click to collapse
But how many of the average users have either a dedicated Linux box or even a VM to do that? On top of that, How many of the average users that don't have either want to set all that up then learn those commands to unpack the tar, edit what they extracted, re-pack it, then re-sign the tar? Yeah there are programs that will pretty much do that for you, but like I said, it is more convenient to keep the official and unchanging builds for Odin and and keep the custom ROMs that are changing every week in the zip format.
Why try to fix something that isn't broken and is much easier to do?
Am I saying "no you can't do it."? Not at all. If you want to spend the time to do all that, go for it. But I can bet you money that half of the developers that are pushing weekly and nightly builds will not want to do all the extra stuff. Look at the bigger picture, most people want pure convenience. There are also big risks with flashing ROMs via Odin.
Bricks being the biggest one.
This topic has been brought up quite a few times in many device forums including this one, and what I have said has been said by many others.
It's just not logical.
That's why im giving 3 install options. Zip tar and aroma. You choose how you wanna install each have their own pros and cons. The biggest pro for odin is I can pack fixes that cant be flashed in a typical zip and can AIO everything so its a single flash and not a zip stack to get it working
I like to break stuff!
If a developer wants to offer tar files for their ROMs then they can do it. It is their decision, not the end user.
Just because you want to dissect someone else's work, does not mean that they are going to cater to your every desire.
Yes, there are risks in flashing via Odin such as flashing the wrong pit, boot.bin, data... but if the developer has tested the tar like all developers should always be testing their own work before releasing to the general public. The only other issue would be bad downloads, which it is entirely up to the user to always check the MD5 before flashing.
Sent from my SPH-D710 using xda premium
Ok I want to clarify something. I am not saying rom devs have to do this.
I will be creating them for the various roms.
Sent from my SPH-D710 using xda app-developers app
BluesRulez said:
Ok I want to clarify something. I am not saying rom devs have to do this.
I will be creating them for the various roms.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
And you have my approval for my FK23 and any future ROMs that I may or may not make.
Sent from my SPH-D710 using xda premium
My thoughts are that it is great for a noob. That is they only want to flash a rom and run with. If you are a dev or like me trying to get the hang of theming and more the zip is the way to go. It its possible to brick your phone ether way. But its is much easer for the noob to do a one click than installing a cwm zip. That they tend to mess up and post after post about all the problems. LoL
But for a dev I can see the problem. I say yes sofpr the noobs. We were all anoob at one point in time. Thanks op I was thinking of this too.
monkeytools said:
My thoughts are that it is great for a noob. That is they only want to flash a rom and run with. If you are a dev or like me trying to get the hang of theming and more the zip is the way to go. It its possible to brick your phone ether way. But its is much easer for the noob to do a one click than installing a cwm zip. That they tend to mess up and post after post about all the problems. LoL
But for a dev I can see the problem. I say yes sofpr the noobs. We were all anoob at one point in time. Thanks op I was thinking of this too.
Click to expand...
Click to collapse
Well, in the words of garyd (search if you don't know to whom I refer to), it seems that 75%, or more, of people aren't here to dev.
I'll be honest; when I first came here a short time ago, I wanted to root so I could add all the tweaks and themes because a fellow co-worker showed me what could be done. Then the inner geek came out and now I am like a dog on a squirrel going tree to tree trying to soak up all I can. Just gotta focus..
My point = this is a place for "stuff". I'm not taking away from the roots of XDA nor it's intentions because I now understand what a dev told me (Venum, cough, cough, good guy, cough) - This is a place to learn.
I hope Blues follows through with this because he can help me figure out where I may have failed or vice versa.
Who cares about the "numbers" that want it..
Ask a teacher - "If you can reach one.. " What they'd say..
My 2 cents... I have always kept a blu kuban nandroid that is a fully functional backup that's ready to go if I crap up the phone and don't have time to rebuild before say going to work. Even if it's out dated, it's ready to go. To turn said backup into a one click would be that much cooler if the recovery is blown too. Could a script be made to turn a nandroid folder into a one click?
As for the roms being released for odin, it sounds cool but I would miss adding stuff like swype and other system apps myself.
Sent from my SPH-D710 using xda premium
Hey Blues, if you need any help building tar files for the vast number of ROMs out there, I am waiting for more work to be available before I can go back to work... damn construction.
I have at least this week maybe some of next week available to help.
Sent from my SPH-D710 using xda premium
Mattix724 said:
Hey Blues, if you need any help building tar files for the vast number of ROMs out there, I am waiting for more work to be available before I can go back to work... damn construction.
I have at least this week maybe some of next week available to help.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Thanks. So far I have used couple ICS roms. Took the system folder and packaged that into factoryfs.img and then a blank data.img and zimage with all remaining files which are standard in stock .tar such as boot.bin, param.lfs etc to create a full rom .tar. It flashes all the parts but when the time comes for it to boot, it goes to samsung flash screen. Tries 2 times to boot and then boots into custom recovery (agat for the zimage I used).
Rwilco has suggested couple things but haven't had a chance to try those so may be I will get on it!
Hey Moho. How much have you done yet?
BluesRulez said:
So what is this?
I have always wondered would it be safe and easier to flash custom roms using Odin if we had odin packages for custom roms. So I started to poke around and research. Rwilco12 has been a great help. I was working on this before new year and was getting somewhere. I had created quite a few full Odin tars for couple ROMs but none of the packages had successfully flashed the whole ROM. These tar packages are similar to the stock .tar files that sextape posts but they are rooted and are not stock Sprint builds.
As some of you may know, I got sick and caught flu on new year so had to stop working on this and hasn't worked on this since 27th Dec plus now new college semester has started so I am somewhat short on time.
So the reason I am posting this here is that I want to know from you whether you would be interested in using Odin to flash custom roms? OR Would you rather continue to flash custom ROMs using CWM?
If more people are interested in this and would seriously use these to flash custom ROMs then I will continue to work on it. I want honest responses. I wouldn't mind a bit if you think Odin custom ROM flashing is not the way you would go. Also you can use the poll for your response.
I will appreciate any useful responses.
Click to expand...
Click to collapse
Yessssssss do it!!! It will be less bricks out there cuz ppl don't know wat safe recovery to use! Like certain peeps like to flash using blu Kuban kernel! Then wonder why the ROM don't boot!!! Do it BluesRulez
Sent from my SPH-D710 using Xparent Blue Tapatalk 2
BluesRulez said:
Hey Moho. How much have you done yet?
Click to expand...
Click to collapse
Slightly different way of making the fs.img and only doing a Rom flash.
Was working with deoxdexed flashing on top of a stock base.
Boots but ui crashes. Like a blank ui..
Sent from my SPH-D710 using Xparent ICS Tapatalk 2
Hey Guys,
I know it is probably not possible, but in case it is, I wanted to post the question.
I have been working with MotoDefier for a few days now learning about the new model S3 (SGH-T999L). Because there is no firmware available for download yet, we are trying to find a way to either pull the stock recovery before rooting, or figure a way to root without flashing CWM or TWRP first.
The ultimate goal here is to pull all of the parts that are included in firmware updates, and create the firmware from there. This way, if anyone runs into problems, they will be able to Odin back to stock.
Moto has already tried several different rooting methods, including CF-AutoRoot, and has had no luck so far. So if anyone has any ideas on how we can get this done, please do share!
Thanks!
Doc
This may be out of place but perhaps the 999l is closer recovery to the s4? I don't know. But have you tried to pull it with the paid version of the s3 toolkit?
I wish I could help. Sorry Doc
Sent while sleeping in chair.
Doesnt the toolkit flash recovery though? Ive never actually used it. Ill look into it though, thanks.
As far as it being closer to the S4, im just not sure. I do know you can root by flashing the T999 CWM or TWRP, then superuser. Plus.from what I see the overall layout is the same as the original T999.
Thanks for the reply!
Sent from my SGH-T999 using xda premium
I don't have an answer for your question, but wouldn't the only way be through flashing an insecure kernel (exploit)? Then you could push SU and you would have your recovery. But then you lose the kernel.
Can't you download the firmware through Kies? I know it's not on sammobile, but I would think that Kies would be able to restore the factory image. The prospect of Kies not being able to do this is ridiculous. If that's the case, it's even more useless than I previously thought.
Aerowinder said:
I don't have an answer for your question, but wouldn't the only way be through flashing an insecure kernel (exploit)? Then you could push SU and you would have your recovery. But then you lose the kernel.
Can't you download the firmware through Kies? I know it's not on sammobile, but I would think that Kies would be able to restore the factory image. The prospect of Kies not being able to do this is ridiculous. If that's the case, it's even more useless than I previously thought.
Click to expand...
Click to collapse
I was actualy thinking the same thing about the kernel. Just sent a PM to one of the guys who already rooted to see if they would pull the boot.img for me. Im not worried about losing the kernel, as I will still have the original copy after setting it to insecure.
Moto already tried getting the firmware through kies, but it didnt work. We figure that its because there is no publicly released firmware to begin with. As to the uselessness of Kies......completely!
.......I was just thinking, when you flash CM, it flashes its own kernel with it, right? (Its been a long time since Ive messed with CM, sorry). If thats the case, i wont be getting the kernel from the guy I PM'd.
Does anyone else have the new model T999L? If so have you rooted yet, or do you plan to? If so, please PM me if you are willing to help us out with this.
And by all means, hit me with any other ideas you guys may have!
Yes, it flashes it's own battery hog kernel.
Well, I hope I dont jinx anything by announcing too early, but I think we got it!
It appears that using the motochopper exploit did the job. It was originally created for a Motorola device, but as it turns out it will work on a number of Qualcomm based devices.
I got the info from the S4 forums.
It appears the main thread is in the ATT forum here:
http://forum.xda-developers.com/showthread.php?t=2252248
Here it is reposted in the Tmobile S4 forum:
http://forum.xda-developers.com/showthread.php?t=2258633
Just wanted to share in case anyone's interested in taking a look.
Note: it looks like the latest updates may have been patched against this exploit. Just fyi.
Sent from my SGH-T999 using xda premium
I love you Doc. (Hetero)
Sent while sleeping in chair.
Lol!
Be sure to hit thanks when you see MotoDefier. He took all the risk and did all the hard work! I mostly just helped with ideas and such. (Most of which didnt work!)
Ill be working tonight and tomorrow on getting some sort of flashable firmware put together so you guys have a way back to stock if need be.
Also I have a deodexed rom based on the T999L almost ready in case anyone wants to mess with it. Just got to double/triple check my work and test first. There are a few differences from the original T999 so im curious to see if any of it is noticeable while its running.
Let the fun begin!
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
Doesnt the toolkit flash recovery though? Ive never actually used it. Ill look into it though, thanks.
As far as it being closer to the S4, im just not sure. I do know you can root by flashing the T999 CWM or TWRP, then superuser. Plus.from what I see the overall layout is the same as the original T999.
Thanks for the reply!
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
What I meant was pulling files from device without pushing anything to it. I believe this is an option within the toolkit, not sure if paid version required. Hmmm.
Sent from my Transformer Prime TF201 using xda premium
What I was getting at, was that we didnt want to use the toolkit because it flashes recovery. And I could be mistaken, but Im pretty sure the toolkit requires you to root first, then it can pull system firmware for you. Either way though, we got what we needed. I am uploading files now and will post shortly.
Note that most of what I am doing is currently untested. I do not have a T999L, and I dont want to take the chance of flashing certain parts of the T999L to it. I am confident that it will work, or i wouldnt release any of it, but just for full disclosure.....!
I dont believe it needs root and it wont do anything you dont want it to do unless you tell it to do it. All of that aside, I wasnt trying to pimp the toolkit, I just thought it might work, but as I have little knowledge about that which I am talking, I'll just defer to you fellows as you seem to know a thing or two about a thing or two.
:screwy:
Sent while sleeping in chair.
I have the T999L, I used the Toolkit to flash TWRP and then updated it to 2.5.0.0 from Doc's page, I then flashed SuperSU 1.30, wiped Cache and Dalvik, then rebooted. Bam, Rooted. But it not 100%, ROM Manager doesn't seem to have root, but Adfree Android, TiBackup and ES File Explorer. I'm going to uninstall ROM Manager and then reinstall to see if that helps.
Thanks again to DocHoliday77 for his help.
EDIT: I found out why ROM Manager was failing, BusyBox was not installed. I installed it and everything works.
ok so I finally got my sgh-t999L through warranty exchange, and i'm excited to play with it. I rooted it with motochopper and have been looking around, but can't find anything quite concrete, seeing as the original threads discussing the t999L are rather dated. What is the progress on the stock odin? have most roms updated their scripts to include the t999L? Can I flash my previous rom with little to no issues?
Fimrware and radios I'm already aware, albeit I'm concerned about mb7 as it feels a little hot during use. kernels and roms it seems are ok, but I'm curious if there are extra steps to do and such. I can flash twrp 2.6 through odin right?
Naturesretard said:
ok so I finally got my sgh-t999L through warranty exchange, and i'm excited to play with it. I rooted it with motochopper and have been looking around, but can't find anything quite concrete, seeing as the original threads discussing the t999L are rather dated. What is the progress on the stock odin? have most roms updated their scripts to include the t999L? Can I flash my previous rom with little to no issues?
Fimrware and radios I'm already aware, albeit I'm concerned about mb7 as it feels a little hot during use. kernels and roms it seems are ok, but I'm curious if there are extra steps to do and such. I can flash twrp 2.6 through odin right?
Click to expand...
Click to collapse
I wouldn't say any of it is dated...its barely been out over a month if I'm remembering right. And the development thread is still fairly active. I am stalled on the Odin part until we get another dump of some of the partitions, (motodefiers working on that) but this really is a non issue anyway. It may take an extra step or two but we can easily get the same result as a full firmware flash already.
Besides, other than kernel, system and recovery, everything should still be MB7 on your phone, and you should not be looking at changing that.
As far as roms having added the asserts, I don't know. The only way to know is to try them. Or open them and check the asserts.
And what is your previous rom? Cant tell you anything about it unless I know what it is. Why are you concerned over mb7 firmware. I wouldn't put much worry about that as its all that's available for now. What extra steps are you looking for? What is it you are trying to do?
And yes, you can flash 2.6.0.0 twrp.
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
I wouldn't say any of it is dated...its barely been out over a month if I'm remembering right. And the development thread is still fairly active. I am stalled on the Odin part until we get another dump of some of the partitions, (motodefiers working on that) but this really is a non issue anyway. It may take an extra step or two but we can easily get the same result as a full firmware flash already.
Besides, other than kernel, system and recovery, everything should still be MB7 on your phone, and you should not be looking at changing that.
As far as roms having added the asserts, I don't know. The only way to know is to try them. Or open them and check the asserts.
And what is your previous rom? Cant tell you anything about it unless I know what it is. Why are you concerned over mb7 firmware. I wouldn't put much worry about that as its all that's available for now. What extra steps are you looking for? What is it you are trying to do?
And yes, you can flash 2.6.0.0 twrp.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Not dated like really old, but at that time you hadn't made much progress. Just found your thread about the stock rom. So you have made much progress. At the moment I was furrently running vanilla rootbox latest nightly, hiw would I check asserts? Not really worried about changing firmware, just felt a little hot. This being new I understand there are no other radios.
Also thanks for the quick reply
Sent from my SGH-T999L using xda premium
I don't see any reason it wouldn't work. I think I misunderstood something earlier, but ant rom you see in this forum should work fine, its just some won't flash without "help".
The asserts ar in the updater scripts. They determine if certain properties match before allowing something to flash.
Ill be posting a lot of info soon...
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
I don't see any reason it wouldn't work. I think I misunderstood something earlier, but ant rom you see in this forum should work fine, its just some won't flash without "help".
The asserts ar in the updater scripts. They determine if certain properties match before allowing something to flash.
Ill be posting a lot of info soon...
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Tyvm. It will come in handy. I haven't even gotten to the ROM flash yet, though I have installed twrp. Will be creating a new thread... But I'm having the WEIRDEST bug trying to pull everything off my internal SD on my t999. If its more than one file, windows gets stuck on "calculating time required to copy"
Sent from my SGH-T999 using xda premium
This is a Plain Stock ODEXED Rooted ZVC ROM. It has Root and Qualcom app removed. If you need the ZVC radio, get it from HERE
Must have unlocked bootloader.
In TWRP, factory reset, then wipe /system, /cache, /dalvic, and /data. (Do not wipe internal data, /data/media - that's your SD.)
When it boots up, turn off Wifi. For some reason it always turns itself on when first booted up.
Then go to Settings>System Updates and update Profile, PRL.
Then Settings>Activate this device.
____________________________________________________________________________
New March 2 2014
New ZVC with all LG markings, kernel also. Only difference is it's rooted. YOU DO NOT HAVE TO UPDATE, unless you want to. With this, if you re-lock and then remove root, you will have a factory looking phone.
It is also zipaligned
New Download
Here's the Stock LG flashable kernel. All LG Markings
LG Stock Kernel
__________________________________________________________________
Older Versions
Download
Download 2
The kernel will say ShabbyPenguin, but it is the Stock ZVC Kernel
__________________________________________________________________
So Thanks to:
ShabbyPenguin
xboxfanj
Google Search
XDA
Awesome, thank you! :highfive:
Nice bro!
Sent from my LG-LS970 using Tapatalk
You're the best man! Thanks!
Sent from my LG-LS970 using xda app-developers app
Nice one bro. Nice
Sent from my LG-LS970 using xda app-developers app
engine95 said:
Better late than never. This is my first attempt at something like this. So be gentle.
This is a Plain Stock ODEXED Rooted ZVC ROM. It has Root and Qualcom app removed. If you need the radio, get it from HERE
Must have unlocked bootloader.
In TWRP, factory reset, then wipe /system, /cache, /dalvic, and /data. (Do not wipe internal data, /data/media - that's your SD.)
When it boots up, turn off Wifi. For some reason it always turns itself on when first booted up.
Then go to Settings>System Updates and update Profile, PRL.
Then Settings>Activate this device.
Download
The kernel will say ShabbyPenguin, but it is the Stock ZVC Kernel
So Thanks to:
ShabbyPenguin
Google Search
XDA
Click to expand...
Click to collapse
Thanks for this! I've been having endless problems getting ANYTHING to bring my device past a bootload screen or recovery. This managed to get through successfully and load (no data, but phone calls were OK) However it would constantly reboot anytime I altered settings. This, I believe is due to whatever issue it is I am having with the phone, and not this ROM. I was just pleased to find a original stock rom and actually see an OS on my phone (however brief it may have been)
I should also mention I had to sideload this as it was the only method available in my current situation. After a reboot it hung on the LG screen for a solid 20 minutes or so before moving onto the Sprint 4GLTE and then Android itself.
This upload at least gave me hope that no other rom had yet to achieve (that my phone's emmc or internal memory is just fried?!
Either way. Thanks again for your efforts
Link isn't working. Anyway you can post or mirror link that works?
TIA
chicodelta said:
Link isn't working. Anyway you can post or mirror link that works?
TIA
Click to expand...
Click to collapse
I can, but by the time I do, it'll probably be fixed. The link is good, just the mirrors are goofy ATM. Give it some time, and in the meantime I'll upload to Devhost.
chicodelta said:
Link isn't working. Anyway you can post or mirror link that works?
TIA
Click to expand...
Click to collapse
engine95 said:
I can, but by the time I do, it'll probably be fixed. The link is good, just the mirrors are goofy ATM. Give it some time, and in the meantime I'll upload to Devhost.
Click to expand...
Click to collapse
Mirror in OP.
MD5's will be different between the Androidfilehost and the DevHost. I think I just cleaned up the updater script on the Dev Host version.
Disregard the above post. Files are the same now. Had to reupload to fix issue.
Is this Deodexed or Odexed? Which ROM is more stock: ZVC_Deodexed_V2 or this? I want full stock rooted without having to hook up phone to computer.
RegKilla said:
Is this Deodexed or Odexed? Which ROM is more stock: ZVC_Deodexed_V2 or this? I want full stock rooted without having to hook up phone to computer.
Click to expand...
Click to collapse
Odexed. The short and sweet..Odexed Roms are like from the factory. Deodexed is for theming. Neither one needs to hook to your computer. Odexed Roms are harder to modify/theme. Hope that helps you decide.
Sent from my LG-LS970 using XDA Premium 4 mobile app
engine95 said:
Odexed. The short and sweet..Odexed Roms are like from the factory. Deodexed is for theming. Neither one needs to hook to your computer. Odexed Roms are harder to modify/theme. Hope that helps you decide.
Sent from my LG-LS970 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm running ZVC_Deodexed_V2 and it seems to lag on app start up and seem slower to boot up phone.
RegKilla said:
I'm running ZVC_Deodexed_V2 and it seems to lag on app start up and seem slower to boot up phone.
Click to expand...
Click to collapse
An unmodified, deodexed, ROM will boot up slower. Not quite sure on this part, but, it has something to do with how Deodexed isn't cached like odex, so it makes it a little slower.
If you're looking for the most stock experience, odexed will run like factory.
Sent from my LG-LS970 using XDA Premium 4 mobile app
My anal-ness made me do this. And thanks to Shabbypenguin and xboxfanj, I got what I wanted.
What is different in this version is the kernel is straight from the ROM. So this Rom will have ALL the markings of stock. Kernel included. If you install this, relock your phone and un-root, it'll look like factory.
Also added is a flashable zip for the LG Stock Kernel. All LG Markings.
When I get time, I'll update the Deodexed version.
EDIT. You DO NOT have to use this if you downloaded a prior one. Unless you want to.
EDIT2. I forgot to mention, I did zipalign this version
Another, and the main reason I made this, is that this would be like a simple version of LGNPST. IT WILL NOT REPLACE LGNPST. But it may help to fix simpler problems.
For instance:
Flash ZVC modem in OP
While still in recovery flash ROM
Voila! ZVC ALMOST like LGNPST
You the man bro!
Sent from my LG-LS970 using xda app-developers app
Just to be clear so you'll become unrooted if you flash this Rom
Jamesredmond82 said:
Just to be clear so you'll become unrooted if you flash this Rom
Click to expand...
Click to collapse
No. You'll still have root and you'll still be unlocked. You have to be both to flash it.
This'll just return everything to a bone stock rooted/unlocked phone.
Sent from my LG-LS970 using XDA Premium 4 mobile app
Well I learned a lesson just now on how I should really step out of original dev thread more often and check this one out. I literally just finished lgnpst -_-. But my problem isn't fixed so I'm downloading anyway. Great job, this is needed more than people may realize.
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: