First things first, I hold no responsibility for bricked phones, you flash, you break, you fix.
This is the korean kk release just slightly modified by me to install without the need to freegee after installation so you should maintain your current recovery.
To get camera working I compiled the lg source release which was a pain in the ass because someone at LG doesn't know how to zip a file properly.
I trimmed it down by removing the Korean Olleh branding apps and boot/shutdown animations. Forgot, I deleted the LG Music app because it stinks. Doesn't do gapless mp3's which I have a lot of.
I replaced it with AOSP music app with gpu acceleration enabled so it scrolls smoothly and plays gapless mp3's.
No modem is flashed either, just make sure you are running the jb modem.
Only other thing I removed was the root checker daemon because it was spamming logcat (rctd: similar to this: http://forum.xda-developers.com/show....php?t=2267909)
Don't expect a lot of support for this, its not my work, I'm just sharing it because I feel that all our north american providers are going to screw us OG owners out of kitkat.
New rom is pre-rooted, flash super su if you want, but its not required.
Furthermore, new (June 4th) rom does not include busybox, just install from play store.
For all variants flash the main rom zip, boot it up, set up the phone:
Full Canadian E971/E973 Rom
You're done.
After some work from gourab4u, myself and Level99 testing we have sdcard support for you E970 folks.
Level99 built these flashable zip files for E970 AT&T people, credit to him for these zips.
This zip has all E970 patches from below applied, no need to flash any fixes:
Full E970 Rom
If you flashed the Canadian zip and want E970 specific fixes use these:
E970 External SD Fix: This flashes boot.img, framework-res.apk, and platform.xml to allow external sd to be seen on the E970.
AT&T Build.prop mod: This flashes modified build.prop to change phone to identify as US AT&T.
Both zips above combined into 1: This flashes the above two fixes and incorporates NFC fix if NFC is not working for you. Seems most people are saying NFC works as is from the main rom zip.
Install this to get the Accuweather widget to work:
Weather Theme
Enjoy.
Just a couple screenshots from On Screen Phone to show you guys whats coming...oh ya, I LOVE QSLIDE!
Paulicat said:
First things first, I hold no responsibility for bricked phones, you flash, you break, you fix.
This is the korean kk release just slightly modified by me to install without the need to freegee after installation so you should maintain your current recovery.
...
Enjoy.
Click to expand...
Click to collapse
You, sir, kick some serious ass. Looking forward to trying this out as soon as work is over today!
I'm already downloading. Will see how this behaves.. I'll post my feedback in around 2~3 hours.
Thanks for the hardwork Paulicat!
Paulicat said:
First things first, I hold no responsibility for bricked phones, you flash, you break, you fix.
This is the korean kk release just slightly modified by me to install without the need to freegee after installation so you should maintain your current recovery.
To get camera working I compiled the lg source release which was a pain in the ass because someone at LG doesn't know how to zip a file properly.
I trimmed it down by removing the Korean Olleh branding apps and boot/shutdown animations. Forgot, I deleted the LG Music app because it stinks. Doesn't do gapless mp3's which I have a lot of.
I replaced it with AOSP music app with gpu acceleration enabled so it scrolls smoothly and plays gapless mp3's.
No modem is flashed either, just make sure you are running the jb modem.
Only other thing I removed was the root checker daemon because it was spamming logcat (rctd: similar to this: http://forum.xda-developers.com/show....php?t=2267909)
Don't expect a lot of support for this, its not my work, I'm just sharing it because I feel that all our north american providers are going to screw us OG owners out of kitkat.
For E970 owners, I have no idea how your phones will react to the sdcard and red only led as this is the Korean rom...if someone who has an E970 can test/fix great but I can't help much in that regard.
There's a couple different ways to accomplish this so here goes easy way first:
2 Steps to follow:
flash this large rom zip, flash supersu.zip, boot it up, set up the phone:
http://www.androidfilehost.com/?fid=23487008491966757
Grab boot img from here (my kernel build for our cameras): http://www.androidfilehost.com/?fid=23501681358541637
Then reboot to bootloader and "fastboot flash boot boot.img"
You're done.
Alternative is to download the large rom, download the boot.img and replace the boot.img in the large rom with my boot.img from link above.
I have no computer at home so I can't do the boot.img swap and re-upload for the time being.
Large rom zip mirror provided by Liindberg in the international forum:
http://goo.gl/iRuRAI
Enjoy.
Click to expand...
Click to collapse
I have E970 AT&T I let you know. Downloading.
There will be a new boot.img soon, our north american kernel defconfigs have not been updated fully for kitkat changes.
Currently there is some logcat spam that will be gone soon.
Will also try doing a E970 specific kernel build, if someone can edit the storage_list.xml for you E970 peeps would help, I don't know anything about that part...
Thanks Pauli for the rom and kernel. I will be flashing your boot.img and see. While I was trying to port the kernel from Korean release, I have edited the storage_list.xml. I can help in editing the storage_list.xml for e970 for your rom, if you/someone can upload the framework-res.apk from your rom, as I do not have the connection to download GBs.Will report after flashing your compiled boot image.
Stuck at LG boot logo after reboot from bootloader.
Edit:
Come from CM11 nightly. TWRP 2.7.0.0.
After reboot to recovery and format cache/dalvik then reboot, the recovery said there is no OS installed
Stuck at LG boot logo after reboot from bootloader.
E970 ROM
RECOVERY TWRP KITKAT
external SD not working. camera working perfectly.
I have checked the ramdisk and saw many lines needs to be modified for external SD(probably) the fstab ones do have a "#" to comment out the sdcard1 mount code. after some changes in init.device.rc, I got a directory called sdcard1 created in media_rw how ever sdcard is not mounting. In settings, in the sd card section, there is an option called "mount sd card", however it is functionless. Can anyone of you please indicate what am I missing?
romeo_coi said:
Stuck at LG boot logo after reboot from bootloader.
Click to expand...
Click to collapse
Which recovery do you use?
I use CWM...
Paulicat said:
Which recovery do you use?
I use CWM...
Click to expand...
Click to collapse
I use TWRP. I'll switch to CWM and try again.
ChummyDays said:
The reason you guys are stuck on the lg logo is probably the same reason the people on e975 forums were. Your system partion is 1.5 gb and the Rom needs 2 gb to flash so it isn't flashing the entire thing . There is no easy fix yet. We'll have to wait
Click to expand...
Click to collapse
Good point. I thought E970's were closer to our canadian phones than that.
ChummyDays said:
The reason you guys are stuck on the lg logo is probably the same reason the people on e975 forums were. Your system partion is 1.5 gb and the Rom needs 2 gb to flash so it isn't flashing the entire thing . There is no easy fix yet. We'll have to wait
Click to expand...
Click to collapse
Attempting to build a regular flashable zip from philz recovery instead of the img files. This should get around the img file being 2gb.
Will upload later tonight.
[edit]It didnt build the zip correctly, failed to flash on my phone. Will have to look at alternatives.[/edit]
Paulicat said:
Attempting to build a regular flashable zip from philz recovery instead of the img files. This should get around the img file being 2gb.
Will upload later tonight.
[edit]It didnt build the zip correctly, failed to flash on my phone. Will have to look at alternatives.[/edit]
Click to expand...
Click to collapse
My Stop on LG Logo.
LG E970
Paulicat said:
[edit]It didnt build the zip correctly, failed to flash on my phone. Will have to look at alternatives.[/edit]
Click to expand...
Click to collapse
What if you try to unpack the system.img and from there build a flashable zip?
http://forum.xda-developers.com/showthread.php?t=2294909
jimbo77 said:
What if you try to unpack the system.img and from there build a flashable zip?
http://forum.xda-developers.com/showthread.php?t=2294909
Click to expand...
Click to collapse
Trying, symlinks are a pain in the ass...
Just the fact that this was even brought over to our devices from the Korean source is enough. I thought the geeb was on its last legs, this is a fantastic shot in the arm! Flashing shortly.
Paulicat said:
Trying, symlinks are a pain in the ass...
Click to expand...
Click to collapse
You could try my meta-inf folder here below which i use to got the Optimus g rom extracting.
https://drive.google.com/file/d/0B1u3mnq0nstfcVRDN3V3XzJBblE/
Also flashable boot.img without the need of fastboot.
https://drive.google.com/file/d/0B1u3mnq0nstfUU9RSDBpVzBKdVU/
I dont know or all the symlinks are really good correct but i think so cause i could flash my optimus g port build without any symlink error. i based my optimusgrom port on yours paulicat so it shouldnt be a problem at all lol goodluck further i hope that these files could help you guys further here also. I extracted the img file using ext2explore on windows.
I also got the boothang on the LG icon, system shows 1.5gb in CWM.
I have a working zip (regular zip not img based) now. I am taking an extra day to tweak it a bit more.
I'll also compile e970 specific kernel and release that as a separate boot.img.
LG still uses the nfc firmware file which is OK for Canadian phones but I don't know yet for e970.
Default kernel in the rom will be the Canadian kernel.
I'll upload it tomorrow night.
Bare with me as I don't have a working computer at home, bad luck killed my imac.
Sent from my SGP312 using XDA Free mobile app
Related
Hello,
I have an AT&T HTC One X+ (plus). Currently, I have unlocked the bootloader, rooted, and now have the TWRP recovery on my phone. I will admit I am a n00b at Android, but some help on the following issue will be greatly appreciated. I believe I got the proper cyanogenmod and gapps files, and I then push them to my device via Terminal (Mac). However, when I go to install them, they come back as failed. It says "E:Unable to open zip file." If someone could tell me what the issue is, that would be great. I feel that I am very close to flashing a new rom, but I am in desperate need of assistance. If you could possibly link proper gapps and cyanogenmod (or other custom rom) files, I would really appreciate it.
Thanks,
JCarrot
JohnCarrot said:
Hello,
I have an AT&T HTC One X+ (plus). Currently, I have unlocked the bootloader, rooted, and now have the TWRP recovery on my phone. I will admit I am a n00b at Android, but some help on the following issue will be greatly appreciated. I believe I got the proper cyanogenmod and gapps files, and I then push them to my device via Terminal (Mac). However, when I go to install them, they come back as failed. It says "E:Unable to open zip file." If someone could tell me what the issue is, that would be great. I feel that I am very close to flashing a new rom, but I am in desperate need of assistance. If you could possibly link proper gapps and cyanogenmod (or other custom rom) files, I would really appreciate it.
Thanks,
JCarrot
Click to expand...
Click to collapse
First try re-downloading the zip file to rule out a bad download
Jonnibravo said:
First try re-downloading the zip file to rule out a bad download
Click to expand...
Click to collapse
If I download it and it decompresses and becomes a folder, should i compress it? Could the file not be compatible with Macs?
JohnCarrot said:
If I download it and it decompresses and becomes a folder, should i compress it? Could the file not be compatible with Macs?
Click to expand...
Click to collapse
You MUST NOT uncompress the zip file you have downloaded.
Check the MD5 checksum, as said by the previous user, it might be a bad download.
I hope you have taken care of moving all your data to the 0 folder...
Also, before trying non Sense ROMs on ATT - see the thread carefully (I have heard there are isues.. but I am not sure the truth because I don't own one )
Addicted2xda said:
You MUST NOT uncompress the zip file you have downloaded.
Check the MD5 checksum, as said by the previous user, it might be a bad download.
I hope you have taken care of moving all your data to the 0 folder...
Also, before trying non Sense ROMs on ATT - see the thread carefully (I have heard there are isues.. but I am not sure the truth because I don't own one )
Click to expand...
Click to collapse
I was able to get the file uncompressed. Then, I used adb push to put the file on my phone. I wiped the phone. When I tried to install the .zip file, it fails. Any suggestions?
If I do "adb push" for the files I want on my phone and I boot into recovery before it show something like "1309 KB/s (1050533 bytes in 0.783s)," the files may not have fully loaded onto the phone. Should I just wait a until they display something like that? Could this the source of my issues (that the files are not fully loaded)?
JohnCarrot said:
If I do "adb push" for the files I want on my phone and I boot into recovery before it show something like "1309 KB/s (1050533 bytes in 0.783s)," the files may not have fully loaded onto the phone. Should I just wait a until they display something like that? Could this the source of my issues (that the files are not fully loaded)?
Click to expand...
Click to collapse
I am assuming you have TWRP? Use adb sideload and not adb push. Since you want to install CM - I am assuming you have downloaded a file called CM10.1xxxxxxxxxxxxxxxxxx.zip (may be cm-10.1-20130607-UNOFFICIAL-enrc2b).
Use adb sideload to copy this zip file to your pone
Now use adb side load the ROM, the file should be renamed sideload.zip when it is copied on your phone.
Addicted2xda said:
I am assuming you have TWRP? Use adb sideload and not adb push. Since you want to install CM - I am assuming you have downloaded a file called CM10.1xxxxxxxxxxxxxxxxxx.zip (may be cm-10.1-20130607-UNOFFICIAL-enrc2b).
Use adb sideload to copy this zip file to your pone
Now use adb side load the ROM, the file should be renamed sideload.zip when it is copied on your phone.
Click to expand...
Click to collapse
I was able to get cm to work using advice push. I am using TWRP. Could it be possible that cm is really buggy because I used adb push. Sorry question mark not working. CM literally ceases and reboots every five minutes. It is practically not usable.
JohnCarrot said:
I was able to get cm to work using advice push. I am using TWRP. Could it be possible that cm is really buggy because I used adb push. Sorry question mark not working. CM literally ceases and reboots every five minutes. It is practically not usable.
Click to expand...
Click to collapse
nope, it's just super unstable right now. Not by any means a daily driver. Most of the other issues are not really being looked at currently until the devs manage to fix the current lack of call audio.
NasaGeek said:
nope, it's just super unstable right now. Not by any means a daily driver. Most of the other issues are not really being looked at currently until the devs manage to fix the current lack of call audio.
Click to expand...
Click to collapse
Are there devs still working on it? I thought they abandoned the HTC One X+.
There is certainly still work being done, as evidenced by this thread, though it is slow going. Lloir in particular should be commended for doing as much work on AT&T HOX+ as he does considering he doesn't even use the phone. All of that being said, from the looks of it our hopes of call audio being fixed (among other things) are slim
NasaGeek said:
There is certainly still work being done, as evidenced by this thread, though it is slow going. Lloir in particular should be commended for doing as much work on AT&T HOX+ as he does considering he doesn't even use the phone. All of that being said, from the looks of it our hopes of call audio being fixed (among other things) are slim
Click to expand...
Click to collapse
Could my issue of CM being so buggy and rebooting every 5 minutes be because I did not change the kernel? I am somewhat of an Android n00b, but I did get CM working on my HOX+ and unlock the bootloader. I just don't entirely understand why I need to change the kernel. Thanks for responding btw.
It's worth a shot. Just open up the zip and flash the boot.img inside using fastboot.
NasaGeek said:
It's worth a shot. Just open up the zip and flash the boot.img inside using fastboot.
Click to expand...
Click to collapse
Oh...I've already done that. I got my CM from lloir.com and I downloaded the boot.img along with the rom. I didn't know what the fastboot flash boot boot.img did. I just knew that I had to do it. I didn't know that was the kernel.
Different HOX+ ROM
NasaGeek said:
It's worth a shot. Just open up the zip and flash the boot.img inside using fastboot.
Click to expand...
Click to collapse
Do you know of any different roms (AOKP/Paranoid/others) that are less glitchy for the AT&T HOX+? The CM10.1 that is currently on my phone just is not daily driver material by any stretch of the imagination. I want a somewhat stable (it can reboot like twice a day but not every 5 minutes) kind of stock rom because Sense 4+ is killing me. Well, I've been using CM, but that constant rebooting is killing me, as well.
JohnCarrot said:
Do you know of any different roms (AOKP/Paranoid/others) that are less glitchy for the AT&T HOX+? The CM10.1 that is currently on my phone just is not daily driver material by any stretch of the imagination. I want a somewhat stable (it can reboot like twice a day but not every 5 minutes) kind of stock rom because Sense 4+ is killing me. Well, I've been using CM, but that constant rebooting is killing me, as well.
Click to expand...
Click to collapse
AFAIK all non Sense ROM are little unstable in ATT
I have CM 10.1 on the HOX+ International and it works just fine. no random reboots and pretty smooth. excellent battery life. Snappier than Viper, which I was on before this.
surfatwork said:
I have CM 10.1 on the HOX+ International and it works just fine. no random reboots and pretty smooth. excellent battery life. Snappier than Viper, which I was on before this.
Click to expand...
Click to collapse
The problem is with the ATT version...
We are lucky
OKay,
Philz/Advanced CWM build for;
SM-T230/NU/31 Philz 6.59 and Aromafm [Marvell]
https://www.androidfilehost.com/?w=files&flid=28382
SM-T237p Philz 6.59 [QCOM/MSM] Thanks @hookem2oo7 for testing.
https://www.androidfilehost.com/?fid=95916177934549969
SM-T230nt Philz 6.59 [QCOM/MSM] Thanks @Erus Tyrannus for testing.
https://www.androidfilehost.com/?fid=23991606952612934
SM-T330/NU/31 Philz 6.58.9
https://www.androidfilehost.com/?w=files&flid=23544
SM-T530NU/31/35 Philz 6.58.9
https://www.androidfilehost.com/?w=files&flid=23537
SM-T533 Philz 6.58.9 <-this is a temporary test build - no noobs.
https://www.androidfilehost.com/?fid=24336189125296272
After usage you may need to reflash the stock LP 5.1 releases recovery.
https://www.androidfilehost.com/?fid=24338798368260119 <-This zip is recovery flashable.
Click to expand...
Click to collapse
NOTE remove .md5 extension if Odin complains -- 64gig sdcards must be formatted exfat
As soon as i get reorganized i will get device trees reconstructed and posted.
My hard drive failed and i lost most of what i had.
the source code for Philz recovery is here https://github.com/PhilZ-cwm6/philz_touch_cwm6
----------------------------------------------------------------------------------
Thanks to the following for support and testing
Huge thanks to @g_ding84 for testing the SM-T230/NU31 process
A special thanks to @Aben314 for supporting me in my efforts.
On the SM-T33XX- @Rusell - the main man , primary tester @pre4speed initial tester and moral support @Flashalot device tree and moral support
On the SM-T53XX thanks to @tgalal @sub77 for their previous work and @mariojuniorjp for testing on the sm-t531
-----------------------------------------------------------------------------------
These are the tools you need if you don't have them already - Odin and Samsung USB Drivers
https://www.androidfilehost.com/?w=files&flid=25040
----------------------------------------------------------------------------------
For builders, this is the default.prop of the sm-t330nu recovery, to make sure your rom assert entries will be correct
Code:
# PHILZ SM-T330NU-MB74
#
persist.security.ams.enforcing=0
ro.adb.secure=0
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.sys.usb.config=adb
persist.sys.root_access=1
ro.build.product=milletwifi[COLOR="Red"]ue[/COLOR]
ro.product.device=milletwifi[COLOR="Red"]ue[/COLOR]
ro.product.model=SM-T330NU
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=US
ro.board.platform=msm8226
Sources
Device Trees Per Build
MOD EDIT: LINKS REMOVED
dev host link does not work for me.
rsktkr1 said:
dev host link does not work for me.
Click to expand...
Click to collapse
Did you read the OP completely?
If so, my apologies. Sometimes devhost goes down for inexplicable reasons.
Try again later.
m
UPDATE; see OP
SM-T330NU Philz/ADV CWM recovery
corrected storages, sdcard1 , usb-otg
TODO - orient to landscape, adjust/optimize read/write speeds
I now have the sm-t330nu so, hopefully, things will pick up.
m
EDIT- Okay, new version, storages corrected, no landscape orientation yet.
YOU MUST MAKE A NEW BACKUP AFTER INSTALL !
Backups made with previous version encounter selinux context/permission problem
and result in bootloop.
Double-checking file info for Odin
Does the sm-t330nu-philz-recovery-D-3.tar file for Odin contain the same update as the zip? I'm still new to Odin, but I've gleaned from searching that it can't use flashable zip files, they must be tar or tar.md5. Want to make sure I get the correct file before giving this a go. Thanks for a small bit of hand-holding.
K,
hi, no, odin flash d-3 first then flash the update in recovery.
i'm working on final build, so once that's done the current odin flashable file and the update zip
will be replaced, read the update post as well as the OP and be aware of the selinux issue ,
i believe i've corrected that issue in the current/final build i'm working on and should hopefully
have it up soon
thanks.
m.
Final Build Uploaded
Okay,
see OP for link, will be moving things over to android file host soon [mirror], will add link to OP
Final Build, orientation will remain in portrait, from what i've been reading, i would need to modify
kernel source to achieve landscape, which i won't be doing until after i get a rom [successful] to build through, sorry.
I tried increasing font size but, in portrait the text becomes jumbled and looks sloppy, [ yuck ! ]
The virtual keys will come in handy
Storages and selinux issue corrected, sdcard1 :good: usb-otg :good:
As a precaution, make a brand new backup, especially to preserve your full stock rom !
When/if i get landscape orientation and font sizes done i will release a really final version,
provided someone else doesn't do it first.
Sorry for the goofs and delays.
m
Thank you all!!!!
I'm getting a MD5 error when attempting to flash this Recovery to my T330NU Galaxy tab 4 8.0 Via ODIN
I tried redownloading it several times and got the same results.. I tried to flash this over the TWRP recovery port, its not mounting Cache so I can't flash the Zip..
Zaphodspeaks said:
I'm getting a MD5 error when attempting to flash this Recovery to my T330NU Galaxy tab 4 8.0 Via ODIN
I tried redownloading it several times and got the same results.. I tried to flash this over the TWRP recovery port, its not mounting Cache so I can't flash the Zip..
Click to expand...
Click to collapse
Z,
hi,
the .md5 extension can be removed, meaning, rename blah.recovery.tar.md5 to blah.recovery.tar
i scripted the odin packing process for my recovery builds a while back so, the md5 gets added as a matter of course.
the recovery will flash, as a step to defeat the automatic restoration of the stock recovery by the rom,
uncheck auto restart/reboot in odin and perform your flash, wait for the RES OK message, give it a second or two longer,
then disconnect your tab and use the three button combo to force boot to recovery, home,volume-up,power
from recovery reboot as normal.
m
moonbutt74 said:
Z,
hi,
the .md5 extension can be removed, meaning, rename blah.recovery.tar.md5 to blah.recovery.tar
i scripted the odin packing process for my recovery builds a while back so, the md5 gets added as a matter of course.
the recovery will flash, as a step to defeat the automatic restoration of the stock recovery by the rom,
uncheck auto restart/reboot in odin and perform your flash, wait for the RES OK message, give it a second or two longer,
then disconnect your tab and use the three button combo to force boot to recovery, home,volume-up,power
from recovery reboot as normal.
m
Click to expand...
Click to collapse
Ill do just that.. While I was sleeping, that idea did occur to me
Edit, yup that worked! Thanx..
Edit: Like the TWRP recovery, this recovery won't mount Cache..?
deleted, no longer relevant.
Pulling this conversation into the right thread.
I have the milletwifiUE SM-T330NU. This recovery wouldn't flash on it. The title is misleading b/c this recovery isn't for all of the SM-T330NU devices. Since it wouldn't flash, there isn't any harm done, but having read almost every other thread in the Tab 4 forum, I'd suggest pointing out the code name of each device is important in the OP. There are differences between the SM-T330NUs apparently.
Still, M, thank you for your work on the device. If you can link me to directions on how to pull a recovery.log or boot.img or whatever you may need to include the milletwifiue, I'd be glad to. If you've already posted those directions and I missed them, point me to the post.
Can you make one for smt331
Dewang rocky said:
Can you make one for smt331
Click to expand...
Click to collapse
D,
hi, try this version, flash via odin. http://d-h.st/de2u click the download now button.
the name of the file is sm-t331-Philz-6_58_9-recovery-round1.tar
m
xnatex21 said:
Pulling this conversation into the right thread.
I have the milletwifiUE SM-T330NU. This recovery wouldn't flash on it. The title is misleading b/c this recovery isn't for all of the SM-T330NU devices. Since it wouldn't flash, there isn't any harm done, but having read almost every other thread in the Tab 4 forum, I'd suggest pointing out the code name of each device is important in the OP. There are differences between the SM-T330NUs apparently.
Still, M, thank you for your work on the device. If you can link me to directions on how to pull a recovery.log or boot.img or whatever you may need to include the milletwifiue, I'd be glad to. If you've already posted those directions and I missed them, point me to the post.
Click to expand...
Click to collapse
The recovery is for the milletwifi sm-t330nu, again if you read the op you will see the codename clearly stated in the posted default.prop.
If i understand your issue, you either attempted to flash this recovery's .zip installation from another recovery, or you attempted to flash
a modified repackaged "stock" rom in which, during the process, the assert in the updater-script determined your device to be incorrect.
In which case your custom rom and/or previous custom recovery are in error.
I say this bluntly yet, without malice, I have done this before and have a fairly good handle on it. I would certainly modify a version for you
if you provide me with the actual original stock boot or recovery image for your device. Images from custom/modded roms will not do.
m
moonbutt74 said:
The recovery is for the milletwifi sm-t330nu, again if you read the op you will see the codename clearly stated in the posted default.prop.
If i understand your issue, you either attempted to flash this recovery's .zip installation from another recovery, or you attempted to flash
a modified repackaged "stock" rom in which, during the process, the assert in the updater-script determined your device to be incorrect.
In which case your custom rom and/or previous custom recovery are in error.
I say this bluntly yet, without malice, I have done this before and have a fairly good handle on it. I would certainly modify a version for you
if you provide me with the actual original stock boot or recovery image for your device. Images from custom/modded roms will not do.
m
Click to expand...
Click to collapse
If I'm one of the only people that would benefit from it, lets not worry about it. At this point I don't have the stock recovery b/c I flashed twrp first and then tried to flash this.
I see you did post the code name in the OP but I think it would help to point out that there are sm-t330nu variants, like mine. Coming from years of flashing, I know most people here are used to checking model #s that are posted in the title. Its very unusual to get a model with different code names and not a different carrier, in this case wifi (as opposed to Verizon ot Sprint etc).
Edit: typos
X,
hi,
the ue thing is weird, , i am wondering if my tab might have been a refurbished device.
this should do you, it the same recovery adjusted to milletwifiue
Derp on me, sorry https://www.androidfilehost.com/?fid=95887005526787734
the name of the file is sm-t330nu-Philz-6_58_9-milletwifiue-recovery.zip
I'll add it to OP and make an edit. Let me know if you have an issue.
m
moonbutt74 said:
X,
hi,
the ue thing is weird, , i am wondering if my tab might have been a refurbished device.
this should do you, it the same recovery adjusted to milletwifiue
https://www.androidfilehost.com/?fid=95887005526787126
I'll add it to OP and make an edit. Let me know if you have an issue.
m
Click to expand...
Click to collapse
M,
I flashed it in twrp .3 and it failed. It didn't give me the wrong device error though.
My device is a refurb too. I pulled this from bug report, not sure if it helps:
milletwifiue-user 4.4.2 KOT49H T330NUUEU1ANCA
This is a ROM Base of the latest LP VS985 23C & 23B for all devs who work on Stock LG system. It was a part of JasmineROM, but since it's Unmodified Stock/Rooted ROM, it should be just a ROM base. It makes it easy to upgrade to LP without the OTA hassle & to prepare partitions for future updates. It also keeps Bump-signed images (TWRP recovery & custom kernels) working without affecting any of the current ROMs/Kernels. You might need to just flash modem & kernel (check this post for official firmware) if you'd like to downgrade or switch ROMs (only if they're not already included in that ROM).
I went the image route (the new method) because I had some issues with some firmware. It run perfectly on my device, but failed to boot (or stuck in a bootloop) for some testers. The reason for Data/WiFi & other issues I've experienced during testing was due Symlinks, Permissions, & SELinux context. They should be identical to stock system. So, to avoid any other unforeseen issues, I decided to write stock images (so it works as expected) & updates will automatically follow the correct symlinks/permissions/context. I can make a working updater-script, but this way is much easier & straightforward.
23C Installation Instructions: - Official
BACKUP your apps via TitaniumBackup
REBOOT to TWRP recovery (the latest TWRP v2.8.6.0 can be found here)
WIPE everything (system/data/cache/dalvic)
FLASH JasmineROM_v7.0.zip - BE PATIENT !
FLASH SuperSU for ROOT access
RESET factory from within ROM (in Settings) is required.
If you run into WiFi/Sync issues, flash CRONTAB_DisableIPv6.zip
Click to expand...
Click to collapse
23C Installation Instructions: - Leak
BACKUP your apps via TitaniumBackup
REBOOT to TWRP recovery (the latest TWRP v2.8.6.0 can be found here)
WIPE everything (system/data/cache/dalvic)
FLASH JasmineROM_v6.0_Unmodified.zip - BE PATIENT !
RESET factory from within ROM (in Settings) is required.
If you run into WiFi/Sync issues, flash CRONTAB_DisableIPv6.zip
Click to expand...
Click to collapse
23B Installation Instructions: - Leak
The installation of 23B is quite simple (much less complicated than it sounds): you just need to run installROM.sh script; the other steps are just for preparation/clarification. This method just works in all situations (coming from Stock KK 10B/11C/12B or AOSP LP) we tested to update all relevant partitions. The future updates will be in the form of a regular flashable .ZIP file.
1. Make Nandroid backup of your ROM via TWRP recovery
2. Download & extract JasmineROM_v5.0.zip (use Zarchiver)
3. Make sure you don't have any partition images in internal storage (/sdcard)
4. Copy all files in JasmineROM_v5.0 directory to internal storage (/sdcard)
5. (Re)boot into TWRP recovery
6. Use Terminal Command (in TWRP) OR ADB (from PC/Mac/Linux via adb shell) to run the following 3 commands:
Code:
cp /sdcard/installROM.sh /sbin/
chmod 0755 /sbin/installROM.sh
sh /sbin/installROM.sh
The first two commands shouldn't print anything.
The 1st command copies the script to /sbin & the 2nd sets its permissions.
The 3rd command runs the script only if it's in /sbin (1st command) & has executable permissions (2nd command).
If you've messed up with your partitions layout or filesystem (e.g., formatting f2fs), revert to factory setup (e.g., ext4 filesystem - since stock kernel doesn't support f2fs).
The last command will take some time (~10 minutes). BE PATIENT !.
Some entries will appear to hang, do not interrupt or disconnect cable!
The "No space left on device" warning is NORMAL
You should see command prompt & ROM info/release date at the end !
Click to expand...
Click to collapse
7. Flash Download Mode Fix + Debuggable Kernel & Reboot
If you run into issues, it's because you've conflicting data from KK.
Do a factory reset in Settings to restore default LP databases!
You may use TitaniumBackup instead of factory reset > Tap batch actions on the top right > Scroll down to "Manipulate data" > Run "Wipe data for user & system apps"
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Downloads:
Please read carefully the instructions above before proceeding at you own risk!
JasmineROM v7.0 Release: JasmineROM_v7.0.zip
md5: 7ac04a41e1f6bb26f51e50760023395d
JasmineROM v6.0 Unmodified: JasmineROM_v6.0_Unmodified.zip
md5: 18887557219ccbf428a4fe99733698da
CRONTAB + Disable IPv6: CRONTAB_DisableIPv6.zip
md5: c6487922357b330cbb6257d91076ca7d
JasmineROM v5.0 Unmodified: JasmineROM_v5.0.zip
md5: 4e6aec50ab9763c4396dcb5e45408a95
Click to expand...
Click to collapse
Thanks to:
All devs/testers/users contributed to it
@HolyAngel for collaboration on Stock-based ROMs
@bweN diorD & @autoprime for the images!
@annoyingduck & @krazy_smokezalot for final tests
Click to expand...
Click to collapse
You guys are the best! I know everyone has been looking forward to this day. If you wanted to flash KK back, would it work to just flash the modems/KK ROM over this?
guitarbedlam said:
You guys are the best! I know everyone has been looking forward to this day. If you wanted to flash KK back, would it work to just flash the modems/KK ROM over this?
Click to expand...
Click to collapse
Yep, just flash the KK ROM + proper kernel & modem
Will this method work for 23a stock? I can't get any method to work for kdz, tot, or root. I lost root when I used active launcher to push 23 a.
jthompson0019 said:
Will this method work for 23a stock? I can't get any method to work for kdz, tot, or root. I lost root when I used active launcher to push 23 a.
Click to expand...
Click to collapse
This method is for those coming from Stock KK 10B/11C/12B or AOSP LP with KK firmware.
hsbadr said:
This method is for those coming from Stock KK 10B/11C/12B or AOSP LP with KK firmware.
Click to expand...
Click to collapse
Is there a method you would recommend? I can't seem to get anything to work.
jthompson0019 said:
Is there a method you would recommend? I can't seem to get anything to work.
Click to expand...
Click to collapse
You may try this at your own risk. It may work, but not tested.
hsbadr said:
This is a ROM Base of the latest LP VS985 23B for all devs who work on Stock LG system. It was a part of JasmineROM, but since it's Unmodified Stock/Rooted ROM, it should be just a ROM base. It makes it easy to upgrade to LP without the OTA hassle & to prepare partitions for future updates. It also keeps Bump-signed images (TWRP recovery & custom kernels) working without affecting any of the current ROMs/Kernels. You might need to just flash modem & kernel (check this post for official firmware) if you'd like to downgrade or switch ROMs (only if they're not already included in that ROM).
I went the image route (the new method) because I had some issues with some firmware. It run perfectly on my device, but failed to boot (or stuck in a bootloop) for some testers. The reason for Data/WiFi & other issues I've experienced during testing was due Symlinks, Permissions, & SELinux context. They should be identical to stock system. So, to avoid any other unforeseen issues, I decided to write stock images (so it works as expected) & updates will automatically follow the correct symlinks/permissions/context. I can make a working installer-script, but this way is much easier & straitforward.
The installation is quite simple (much less complicated than it sounds): you just need to run installROM.sh script; the other steps are just for preparation/clarification. This method just works in all situations (coming from Stock KK 10B/11C/12B or AOSP LP) we tested to update all relevant partitions. The future updates will be in the form of a regular flashable .ZIP file.
Installation Instructions:
Did you know that... You are the best? ?????
Click to expand...
Click to collapse
Thanks a lot. Worked great. Is anyone having trouble with ADB after updating? My ADB worked fine before. I'm trying to find new drivers to install but can't seem to get it.
Coming from the stock KK running AOSP based LP ROMs right now should I install this to get my modem updated to the LP one? Or can I just flash the LP modem to get that updated?
AngryManMLS said:
Coming from the stock KK running AOSP based LP ROMs right now should I install this to get my modem updated to the LP one? Or can I just flash the LP modem to get that updated?
Click to expand...
Click to collapse
You can just flash the modem, but I have no idea if the 23B modem works with AOSP/CM 12.
Sent from my VK810 4G
I'm having trouble installing the original jasmine from page 200. I go through all the steps to run the install script, and everything goes fine and it installs correctly. When I boot it up, however, it won't load and it gives me the stock verizon boot animation and it hangs there. I didn't flash the download mode fix, was going to do that after I booted up for the first time
EDIT: I reinstalled the script, again, everything goes fine and it shows the release data at the end. Then, I flash the last zip, goes fine, and I reboot just like in the instructions and it gives me a blue and green light from the notification light and it's hanging at the stock verizon boot animation and it doesn't look like it's going anywhere. Anyone can help??
cap1tal1sm said:
I'm having trouble installing the original jasmine from page 200.
Click to expand...
Click to collapse
You shouldn't post the same thing in multiple threads.
Sent from my VK810 4G
cap1tal1sm said:
I'm having trouble installing the original jasmine from page 200. I go through all the steps to run the install script, and everything goes fine and it installs correctly. When I boot it up, however, it won't load and it gives me the stock verizon boot animation and it hangs there. I didn't flash the download mode fix, was going to do that after I booted up for the first time
EDIT: I reinstalled the script, again, everything goes fine and it shows the release data at the end. Then, I flash the last zip, goes fine, and I reboot just like in the instructions and it gives me a blue and green light from the notification light and it's hanging at the stock verizon boot animation and it doesn't look like it's going anywhere. Anyone can help??
Click to expand...
Click to collapse
Hey, friendly advice. Don't cross post. Especially 3 different threads.
From my VS985 - Jasmine 5.0.11
whatever gets the fastest response
cap1tal1sm said:
whatever gets the fastest response
Click to expand...
Click to collapse
Lol. Ok, not really the best justification. This isn't an IT help desk.
Sent from my Nexus 7 2013
True that, and let me give you a counter point: How does one extra marginal post in a different forum deteriorate your life in any way possible or imaginable? What is the cost of one more forum post, which by mathematical truth can only lead to one extra page at most?
Is it the opportunity cost of reading my post, and realizing you read the same text somewhere else? Is my ire at my cross post really just anger at re-posts in general? The concept of copying content and under valuing originality? If this is the case, I concede you have a point. I too am an effervescent searcher for good, funny, original and insightful content. My jimmies become quite rustled when I see something I've already seen before.
But here's the irony: just now, you've taken more time to read this post, than the last one!!! Isn't that funny? And it's interesting to think about, for the following reason: What is a post's ultimate value? It's a + b , where a is the value I gain from my post being answered, and b is the value you gain from reading it. Let's think about this post again; this post is literal poop. It is worthless, it's a waste of my time and yours. So really, this post is valueless for everyone involved. Yet, according to the logic of this website's forum, this post is completely fine since it's an original, non-cross post.
Yet my cross posts, which are bad as you suggest, give me immense value! Because my question is answered nearly (but not perfectly) twice as fast, so I get 2a + b return on the post. Do you see how illogical your conception of what is good posts/content, and what is bad?
Eh, but what do I know: I just go to the number 1 school in the US.
cap1tal1sm said:
True that, and let me give you a counter point: How does one extra marginal post in a different forum deteriorate your life in any way possible or imaginable? What is the cost of one more forum post, which by mathematical truth can only lead to one extra page at most?
Is it the opportunity cost of reading my post, and realizing you read the same text somewhere else? Is my ire at my cross post really just anger at re-posts in general? The concept of copying content and under valuing originality? If this is the case, I concede you have a point. I too am an effervescent searcher for good, funny, original and insightful content. My jimmies become quite rustled when I see something I've already seen before.
But here's the irony: just now, you've taken more time to read this post, than the last one!!! Isn't that funny? And it's interesting to think about, for the following reason: What is a post's ultimate value? It's a + b , where a is the value I gain from my post being answered, and b is the value you gain from reading it. Let's think about this post again; this post is literal poop. It is worthless, it's a waste of my time and yours. So really, this post is valueless for everyone involved. Yet, according to the logic of this website's forum, this post is completely fine since it's an original, non-cross post.
Yet my cross posts, which are bad as you suggest, give me immense value! Because my question is answered nearly (but not perfectly) twice as fast, so I get 2a + b return on the post. Do you see how illogical your conception of what is good posts/content, and what is bad?
Eh, but what do I know: I just go to the number 1 school in the US.
Click to expand...
Click to collapse
we got us a arrogant lill fellow here...haha thinks he's the only smart person in the world all that schooling and can't even correct a minor android problem kinda ironic having that attitude will not get u any help '
update:
have u ever changed ur file system from ext4 to f2fs? mind the same but it was bc i had changed my filesystem to f2fs...i reformatted it to ext4 and it booted no problem...initial boot takes quite a bit...5 mins or so
I never bothered doing Bump to get a custom recovery installed. I simply got root on 10B and then disabled automatic updates. As such, I figure this method won't work for me as it involves steps within TWRP. Would my best bet for getting stock rooted Lollipop be to enact Bump to get a custom recovery, and then follow these steps? The Bump stuff didn't make sense to me so I didn't dare venture down that road, and am hoping I can still avoid it...
crazy4android said:
we got us a arrogant lill fellow here...haha thinks he's the only smart person in the world all that schooling and can't even correct a minor android problem kinda ironic having that attitude will not get u any help '
update:
have u ever changed ur file system from ext4 to f2fs? mind the same but it was bc i had changed my filesystem to f2fs...i reformatted it to ext4 and it booted no problem...initial boot takes quite a bit...5 mins or so
Click to expand...
Click to collapse
It's called trolling son. Back in my day, it was an art. Now I just do it for the thrill.
I have no idea how to change file systems. The whole boot partition thing is what weirded me out, I have no idea about that stuff. I ended up flashing back to my kit kat recovery (which had a date of like january 5, lol. So I had been off stock rooted xposed for almost 4 months) and running the commands. Then instead of hanging at the verizon screen at boot, it went into the android is upgrading thing fine.
So I guess it's a directional thing, where you can go forwards in time but not backwards. Which was where I was coming from on Illusion 6.0.
[VK810.4G] [altev] [ViKtory810ROM] official 36B 5.0.2 & 24A 4.4.2 - updated 8/30/2016
First, the thanks:
@AndroidFileHost for the Android File Host website and especially their changes allowing for the reorganization of already uploaded files.
@KyPbP for letting us know it's availability and giving the link to download the VK810 35A_08 KDZ.
@hsbadr for giving me permission to kang his Verizon G3 VS985 JasmineROM 7.0 update script for this use.
@rant for giving a link to the official Verizon PDF detailing this release.
@Chainfire for SuperSU!
@Hnk1 for continued support, advise and ideas, and for experimenting to find out how to root 35A_08 without downgrading. His two updated guides:[VK810][Altev][Guides][Information] Root Recovery Repair [4.4.2][5.02]
[VK810][ROOT][Lollipop][5.02] No downgrade requiredDebloat scripts that you can flash in TWRP or CWM (ClockworkMod Recovery) after flashing the ROM and SuperSU.zip are located in the second post.
Donator's Thanks:
@middle_road
@k3ttle
@JBurch/cry
@habatchaNow
@b52apl
@Protonus
@Carolinaherps
@thvoicwethin
@random.mannix
@raghublr
@megadrive007
Thank you!!!
Just a fair warning, not trying to sound like a you know what, but no Xposed-related comments in this thread. If anyone wishes to post a new thread in General for what Xposed experiences they have under Lollipop, that would be a good idea.
Disclaimer: The usual. I am not responsible for what you do with this nor what happens when you do whatever you do with it.
Instructions to flash:
0. If you haven't previously updated TWRP to the latest version (v2.8.7.0 still as of January 3rd, 2016), do so by:
0A. Download TWRP v2.8.7.0 from http://forum.xda-developers.com/lg-g-pad-83/orig-development/recovery-twrp-2-8-7-0-t3150812
Credit and thanks @AndroidUser00110001 !
0B. (in TWRP v2.7.0.1) choosing "Install", navigating to where you downloaded the TWRP v2.8.7.0 zip (probably in internal storage in the Download folder), and choosing to flash the zip.
1. Download my ROM from my section on Android File Host at https://www.androidfilehost.com/?w=files&flid=32160. I use ADM "Advanced Download Manager" from the Play Store at https://play.google.com/store/apps/details?id=com.dv.adm&hl=en, especially for downloading larger files like ROMs.
2. Check the MD5 Hash of the ROM zip:
2A. Copy (to the clipboard) the MD5 hash that I have in the filename of the ROM zip you downloaded in step 1 above.
2B. Install @scary alien 's "AFV File Verifier for Android" from the Play Store at https://play.google.com/store/apps/details?id=sa.afvx&hl=en.
2C. Run the AFV app.
2D. Choose "Input checksum for comparison".
2E. Paste the MD5 hash previously copied to the clipboard in step 2A above.
2F. Choose "Select File".
2G. Navigate to where you have the ROM zip.
2H. Long-press on the ROM zip and choose "Calc MD5 Checksum".
2I. When it's done calculating the MD5 hash of the ROM zip, it'll automatically compare it to the MD5 hash you pasted in step 2E above.
If the hashes match, the downloaded ROM zip is non-corrupt. If the hashes don't match, you have to re-download the ROM zip.
3. Optionally download one or more of my debloat zip files in the third post below. If you don't flash my "no OTA" debloat zip, then don't take any OTAs you get offered if there are ever any more, or you might get soft bricked, which I won't go into recovering from here.
4. (Not needed for 24A KitKat 4.4.2 pre-rooted ROM) Download the latest non-beta SuperSU zip from http://download.chainfire.eu/supersu (XDA thread with this link at http://forum.xda-developers.com/showthread.php?t=1538053) or the latest Beta version from a link in @Chainfire 's thread at http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133.
5. Copy/move anything you want to keep from internal storage like the files you downloaded in the previous sections.
6. I strongly suggest wiping everything from TWRP (Data, Cache, System, Dalvik and Internal Storage). Wiping all of these things, especially if you use my debloat zip(s) will clear up garbage/folders that were left behind by previous bloat.
7. Flash my ROM.
8. (Not needed for 24A KitKat 4.4.2 pre-rooted ROM) Flash SuperSU.zip (downloaded in step 4 above). This step is VERY IMPORTANT on 35A Lollipop 5.0.2 and above if you want to get back into custom recovery without having to re-flash a stock ROM and go through the whole process again.
9. Optionally flash one or more of my debloat zip files. If you don't flash my "no OTA" debloat zip, then don't take any OTAs you get offered if there are ever any more, or you might get soft bricked, which I won't go into recovering from here.
Flashing the debloat zip(s) before the first boot of the ROM will give the advantage of never having the data/cache entries or internal storage folders for the debloated apps created, the latter is why I recommend a wipe of internal storage.
In order to get back into TWRP/custom recovery from rooted Lollipop 35A 5.0.2 or above ROMs (not needed for 24A KitKat 4.4.2 pre-rooted ROM):
1. Download the corresponding "aboot only" (aboot is the bootloader) found in the same place to download as my ROM zip. Corresponding means if you installed the latest 36B VK810 stock ROM, then download the 36B VK810 aboot zip file.
2. Download the 4.2.2 aboot package from http://forum.xda-developers.com/showpost.php?p=54533937&postcount=2
Credit and thanks @paperWastage !
The download link is about three quarters down in that second post.
3. Move this aboot.4.2.2.img file into the top of the internal storage (meaning, not in a folder).
4. In Terminal Emulator type (make sure no typos, or can copy/paste to be sure):
Code:
su
dd if=/sdcard/aboot.4.2.2.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
5. You can now reboot into recovery via your preferred method.
6. Once you're finished in TWRP, you need to re-flash the newer aboot zip downloaded in step 1 above. If you forget, the ROM won't boot. You should be able to long-press the power button to force the device off, then use the manual method to get back into TWRP mentioned in step 22 in the previous section above. Re-flash the newer aboot zip, then reboot from TWRP and the ROM will boot.
You can alternatively dirty flash my ROM zip instead of just the aboot. You'd have to re-flash SuperSU.zip, any debloat zips and Xposed if you had before, too.
Reserved
LG G Pad 8.3 & Verizon LG G3 DEBLOAT SCRIPTS - updated 4-6-2016
These will work with both the VK810 Verizon LG G Pad 8.3 35A through 36B, and VS985 Verizon LG G3 23C up through 47A. They will NOT work on KitKat for debloating apps yet, they will work for various other non-app files I debloat. I'm working on updating them.
Again, thanks to @hsbadr for giving me permission to kang "anything I want" for this use.
Thanks to @abced123 for figuring out the root/sbin/lge_fota file is what was still allowing OTAs even after LGFOTA.apk was removed.
Thanks to @alfadon for making me aware of the two additional files that needed removed (at least on the VS985) in order to stop OTAs.
Thanks to @xdabbeb for his VS985 v2.0 ROM, with which I made a comparison to find things I could still debloat that I hadn't yet. If he didn't already figure out what we could lose without loss of functionality, this wouldn't have been possible.
INSTRUCTIONS: Backup in TWRP or read list of files deleted and make sure you don't mind, first. Debloat scripts that you can flash in TWRP after flashing the ROM and SuperSU.zip are located in my debloat script section on Android File Host.
@joshua70448 was kind enough to make an online tool to automate making custom debloat zips according to what a user selects to debloat:
joshua70448 said:
I put together an online tool that lets you pick exactly which files to remove in a debloat script and builds the flashable ZIP and MD5 files for you (as well as a full list of deleted files). Check it out at LG G3 VS985 (Verizon) and G Pad 8.3 VK810 (Verizon) debloat generator.
Click to expand...
Click to collapse
Please thank him at his original post here and take note of his other Android tools in his signature: http://forum.xda-developers.com/showpost.php?p=66192766&postcount=238.
Note that these are most effective if flashed before booting the ROM for the first time, or after a data/cache/Dalvik/internal storage wipe since the data, etc for them are built on first boot but if you flash the debloat script(s) before booting the ROM, then it never gets a chance to create the data and cache for them.
That said, it's completely fine to flash them any time.
Which package removes what (additionally there is a "all" zip that removes all of these EXCEPT it still has OTA and doesn't remove the apps affected by Xposed - you'll need to flash the "no OTA" zip separately). I remove all except for OTA, so I'm aware when OTAs arrive if I don't see notice about it here first, and so I can capture the OTA files. ):
Amazon
delete_recursive("/system/app/AmazonIMDb");
delete_recursive("/system/app/AmazonKindle");
delete_recursive("/system/app/AmazonMobile");
delete_recursive("/system/app/AmazonWidget");
delete_recursive("/system/priv-app/AmazonAppstore");
delete_recursive("/system/priv-app/AmazonAudible");
delete_recursive("/system/priv-app/AmazonKindle");
delete_recursive("/system/priv-app/AmazonMobile");
delete_recursive("/system/priv-app/AmazonMP3");
Google
delete_recursive("/system/app/Books");
delete_recursive("/system/app/Chrome");
delete_recursive("/system/app/CloudPrint");
delete_recursive("/system/app/Drive");
delete_recursive("/system/app/Gmail2");
delete_recursive("/system/app/Hangouts");
delete_recursive("/system/app/Maps");
delete_recursive("/system/app/Music2");
delete_recursive("/system/app/Newsstand");
delete_recursive("/system/app/NewsstandStub");
delete_recursive("/system/app/PlayGames");
delete_recursive("/system/app/PlusOne");
delete_recursive("/system/app/Street");
delete_recursive("/system/app/talkback");
delete_recursive("/system/app/Videos");
delete_recursive("/system/app/YouTube");
delete_recursive("/system/priv-app/Velvet");
delete_recursive("/system/tts/google/es-es-x-ana-phone-hmm");
delete_recursive("/system/tts/google/es-us-x-sfb-phone-hmm");
LG Apps
delete_recursive("/system/app/elt_test");
delete_recursive("/system/app/GnssAirTest");
delete_recursive("/system/app/GnssLogCat");
delete_recursive("/system/app/GnssPosTest");
delete_recursive("/system/app/GnssTest");
delete_recursive("/system/app/LGHome_Theme_Marshmallow");
delete_recursive("/system/app/LGLW_Feather");
delete_recursive("/system/app/LGLW_PolarBear");
delete_recursive("/system/app/LGLW_Prince");
delete_recursive("/system/app/LGNotebook");
delete_recursive("/system/app/LGSearchWidgetProvider");
delete_recursive("/system/app/LGSpringCleaning");
delete_recursive("/system/app/LGVZWHelp");
delete_recursive("/system/app/LGWernickeManager");
delete_recursive("/system/app/OBDM_Permissions");
delete_recursive("/system/app/WfdService");
delete_recursive("/system/media/shutdownanimation.zip");
delete_recursive("/system/priv-app/BioITPlatform_SDService");
delete_recursive("/system/priv-app/LGActionManager");
delete_recursive("/system/priv-app/LGConciergeBoard");
delete_recursive("/system/priv-app/LGCover");
delete_recursive("/system/priv-app/LGEasyHome");
delete_recursive("/system/priv-app/LGFavoriteContactsWidget");
delete_recursive("/system/priv-app/LGFormManager");
delete_recursive("/system/priv-app/LGLIA");
delete_recursive("/system/priv-app/LGLW_MultiPhoto");
delete_recursive("/system/priv-app/LGMemo");
delete_recursive("/system/priv-app/LGMusicWidget");
delete_recursive("/system/priv-app/LGMyGuide");
delete_recursive("/system/priv-app/LGMyWellness");
delete_recursive("/system/priv-app/LGNLPService");
delete_recursive("/system/priv-app/LGPCSuite");
delete_recursive("/system/priv-app/LGPolarisOffice");
delete_recursive("/system/priv-app/LGQMemoplus");
delete_recursive("/system/priv-app/LGQVoiceplus");
delete_recursive("/system/priv-app/LGThinkFreeViewer");
delete_recursive("/system/priv-app/LGTTS");
delete_recursive("/system/priv-app/LGVoiceCommand");
delete_recursive("/system/priv-app/LGVZWHelp");
delete_recursive("/system/priv-app/LIAInformant");
delete_recursive("/system/priv-app/LIAS4URecommender");
delete_recursive("/system/priv-app/LocationAgent");
delete_recursive("/system/priv-app/Maluuba_QVoice");
delete_recursive("/system/priv-app/SSO_P3");
LG Audio
delete_recursive("/system/media/audio/effects/KeypressDelete.ogg");
delete_recursive("/system/media/audio/effects/KeypressReturn.ogg");
delete_recursive("/system/media/audio/effects/KeypressSpacebar.ogg");
delete_recursive("/system/media/audio/effects/KeypressStandard.ogg");
delete_recursive("/system/media/audio/effects/VideoRecord.ogg");
delete_recursive("/system/media/audio/ui/af_failure.ogg");
delete_recursive("/system/media/audio/ui/af_success.ogg");
delete_recursive("/system/media/audio/ui/Audible_Selection.ogg");
delete_recursive("/system/media/audio/ui/camera_click.ogg");
delete_recursive("/system/media/audio/ui/camstart.ogg");
delete_recursive("/system/media/audio/ui/camstop.ogg");
delete_recursive("/system/media/audio/ui/circle_lock.ogg");
delete_recursive("/system/media/audio/ui/circle_unlock1.ogg");
delete_recursive("/system/media/audio/ui/circle_unlock2.ogg");
delete_recursive("/system/media/audio/ui/circle_unlock3.ogg");
delete_recursive("/system/media/audio/ui/circle_unlock4.ogg");
delete_recursive("/system/media/audio/ui/circlemosaic_lock.ogg");
delete_recursive("/system/media/audio/ui/circlemosaic_touchdown.ogg");
delete_recursive("/system/media/audio/ui/circlemosaic_unlock.ogg");
delete_recursive("/system/media/audio/ui/clear_ram.ogg");
delete_recursive("/system/media/audio/ui/continuous_shot.ogg");
delete_recursive("/system/media/audio/ui/crystal_lock.ogg");
delete_recursive("/system/media/audio/ui/crystal_unlock.ogg");
delete_recursive("/system/media/audio/ui/dewdrop_lock.ogg");
delete_recursive("/system/media/audio/ui/dewdrop_touchdown.ogg");
delete_recursive("/system/media/audio/ui/dewdrop_touchrelease.ogg");
delete_recursive("/system/media/audio/ui/dewdrop_unlock.ogg");
delete_recursive("/system/media/audio/ui/Effect_Tick.ogg");
delete_recursive("/system/media/audio/ui/Email_Sent.ogg");
delete_recursive("/system/media/audio/ui/FullBattery.ogg");
delete_recursive("/system/media/audio/ui/Homescreen_Remove.ogg");
delete_recursive("/system/media/audio/ui/Homescreen_Uninstall.ogg");
delete_recursive("/system/media/audio/ui/hulahoops_lock.ogg");
delete_recursive("/system/media/audio/ui/hulahoops_touchdown.ogg");
delete_recursive("/system/media/audio/ui/hulahoops_unlock.ogg");
delete_recursive("/system/media/audio/ui/ink_lock.ogg");
delete_recursive("/system/media/audio/ui/ink_touchdown.ogg");
delete_recursive("/system/media/audio/ui/ink_unlock.ogg");
delete_recursive("/system/media/audio/ui/KeypressDelete.ogg");
delete_recursive("/system/media/audio/ui/KeypressReturn.ogg");
delete_recursive("/system/media/audio/ui/KeypressSpacebar.ogg");
delete_recursive("/system/media/audio/ui/KeypressStandard.ogg");
delete_recursive("/system/media/audio/ui/LG_Cable_Connect.ogg");
delete_recursive("/system/media/audio/ui/LG_Media_volume.ogg");
delete_recursive("/system/media/audio/ui/light_lock.ogg");
delete_recursive("/system/media/audio/ui/light_touchdown.ogg");
delete_recursive("/system/media/audio/ui/light_unlock.ogg");
delete_recursive("/system/media/audio/ui/Lock_Cover.ogg");
delete_recursive("/system/media/audio/ui/Lock.ogg");
delete_recursive("/system/media/audio/ui/LowBattery.ogg");
delete_recursive("/system/media/audio/ui/mosaic_lock.ogg");
delete_recursive("/system/media/audio/ui/mosaic_touchdown.ogg");
delete_recursive("/system/media/audio/ui/mosaic_unlock.ogg");
delete_recursive("/system/media/audio/ui/particle_lock.ogg");
delete_recursive("/system/media/audio/ui/particle_unlock.ogg");
delete_recursive("/system/media/audio/ui/ripple_lock.ogg");
delete_recursive("/system/media/audio/ui/ripple_touchdown1.ogg");
delete_recursive("/system/media/audio/ui/ripple_touchdown2.ogg");
delete_recursive("/system/media/audio/ui/ripple_touchdown3.ogg");
delete_recursive("/system/media/audio/ui/ripple_touchrelease1.ogg");
delete_recursive("/system/media/audio/ui/ripple_touchrelease2.ogg");
delete_recursive("/system/media/audio/ui/ripple_touchrelease3.ogg");
delete_recursive("/system/media/audio/ui/ripple_unlock.ogg");
delete_recursive("/system/media/audio/ui/shot_snap.ogg");
delete_recursive("/system/media/audio/ui/soda_lock.ogg");
delete_recursive("/system/media/audio/ui/soda_touchdown.ogg");
delete_recursive("/system/media/audio/ui/soda_unlock.ogg");
delete_recursive("/system/media/audio/ui/switchoff.ogg");
delete_recursive("/system/media/audio/ui/switchon.ogg");
delete_recursive("/system/media/audio/ui/Unlock.ogg");
delete_recursive("/system/media/audio/ui/vector_lock.ogg");
delete_recursive("/system/media/audio/ui/vector_touchdown.ogg");
delete_recursive("/system/media/audio/ui/vector_unlock.ogg");
delete_recursive("/system/media/audio/ui/VideoRecord.ogg");
delete_recursive("/system/media/audio/ui/volume_key.ogg");
delete_recursive("/system/media/audio/ui/whitehole_lock.ogg");
delete_recursive("/system/media/audio/ui/whitehole_unlock.ogg");
No OTA
delete_recursive("/sbin/lge_fota_launcher");
delete_recursive("/sbin/lge_fota");
delete_recursive("/sbin/lge_gota_launcher");
delete_recursive("/system/app/LGDMWebViewer");
delete_recursive("/system/app/LGFOTA");
delete_recursive("/system/priv-app/LGDMSClient");
Verizon
delete_recursive("/data/app/air.com.sgn.cookiejam.gp-1");
delete_recursive("/data/app/air.com.sgn.juicejam.gp-1");
delete_recursive("/data/app/com.mapquest.android.ace-1");
delete_recursive("/data/app/com.sgn.geniesandgems.gp-1");
delete_recursive("/data/app/com.verizonmedia.go90.enterprise-2");
delete_recursive("/system/app/LGVZWHelp");
delete_recursive("/system/media/bootanimation.zip");
delete_recursive("/system/priv-app/com.gotv.nflgamecenter.us.lite");
delete_recursive("/system/priv-app/com.verizon.mips.adpt");
delete_recursive("/system/priv-app/ECID");
delete_recursive("/system/priv-app/iHeartRadio");
delete_recursive("/system/priv-app/LGVZWHelp");
delete_recursive("/system/priv-app/MyInfozone");
delete_recursive("/system/priv-app/MyVerizon");
delete_recursive("/system/priv-app/SlackerRadio");
delete_recursive("/system/priv-app/VerizonIgnite");
delete_recursive("/system/priv-app/VerizonMessage");
delete_recursive("/system/priv-app/VVM");
delete_recursive("/system/priv-app/VZCloud");
delete_recursive("/system/priv-app/VZMessages");
delete_recursive("/system/priv-app/VZMobileSecurity");
delete_recursive("/system/priv-app/VZNavigator");
Apps affected by Xposed
delete_recursive("/system/app/LGWeather");
delete_recursive("/system/app/LGWeatherService");
delete_recursive("/system/app/LGWeatherTheme");
For the VK810 only, there are also 7-Zip archives of the apps and files that are removed in case any user needs them located in the "35A_08 debloated apps-files" or "36B_00 debloated apps-files" subfolders of my section on Android File Host. They are virtually identical to the separate packages listed above for which debloat script removes what, with the only two exceptions being self-explanatory.
Enjoy!
Claimed again.
Ok....now I'm excited. Any more info?
ddodge68 said:
Ok....now I'm excited. Any more info?
Click to expand...
Click to collapse
Hi! I added some preliminary info in the OP. Thanks for asking!
Looking forward to it, thank so much for taking this on. My poor G Pad had been feeling neglected for far too long since my Nexus 6 gets all the ROM love
rant said:
Looking forward to it, thank so much for taking this on. My poor G Pad had been feeling neglected for far too long since my Nexus 6 gets all the ROM love
Click to expand...
Click to collapse
Will this be something we can flash right from TWRP ?
rant said:
Looking forward to it, thank so much for taking this on. My poor G Pad had been feeling neglected for far too long since my Nexus 6 gets all the ROM love
Click to expand...
Click to collapse
You're welcome! I was doing some preliminary work before CleanROM was released to release something like this for 24A but I didn't want to bother duplicating the effort once it was released. There's others who are trying quietly to give our tablet more love than I can give it.
Anthony-m said:
Will this be something we can flash right from TWRP ?
Click to expand...
Click to collapse
Yes.
ROM's done uploading for anyone interested. I'll work on a debloat zip, but that'll take longer than a day.
roirraW "edor" ehT said:
ROM's done uploading for anyone interested. I'll work on a debloat zip, but that'll take longer than a day.
Click to expand...
Click to collapse
Sorry for the questions and thanks a lot for making this rom happen for us. I am using the clean rom right now and the TWRP you mention above, do I just flash the rom and then Supersu and I will have rooted stock lollipop correct? Then I would need to follow the directions in your 4.22 aboot image (which I am pretty sure I already did when I installed TWRP the first time)..again thanks for your hard work..
Anthony-m said:
Sorry for the questions and thanks a lot for making this rom happen for us. I am using the clean rom right now and the TWRP you mention above, do I just flash the rom and then Supersu and I will have rooted stock lollipop correct? Then I would need to follow the directions in your 4.22 aboot image (which I am pretty sure I already did when I installed TWRP the first time)..again thanks for your hard work..
Click to expand...
Click to collapse
No problem. Just flash the ROM and SuperSU, and yes you'll have rooted stock lollipop.
You don't need to follow the directions regarding the 4.2.2 aboot image unless you want to get back into TWRP. But if flash the 4.2.2 aboot.img, you won't be able to boot the ROM, only TWRP. You can do it, to make a backup, to flash something else like Xposed Alpha for Lollipop, etc (unsupported by me), then you'll have to flash the 35A_08 aboot.img zip file I also provide from TWRP so that you can boot the ROM again.
I'll try to figure out a way to make this all clearer.
Thanks for the fast replies, you are so damn helpful I really appreciate it. Crap should I do a factory reset from TWRP before flashing this lol..you knew one more question was coming lol
Anthony-m said:
Thanks for the fast replies, you are so damn helpful I really appreciate it. Crap should I do a factory reset from TWRP before flashing this lol..you knew one more question was coming lol
Click to expand...
Click to collapse
Well thank you back! I appreciate it.
Yes wipe system, data, cache and Dalvik before flashing. Just remember to flash the SuperSU.zip after.
Do i have to wipe/factory reset or wiil this update from cleanrom
4218kris said:
Do i have to wipe/factory reset or wiil this update from cleanrom
Click to expand...
Click to collapse
Hello!
Answered a few posts above yours.
roirraW "edor" ehT said:
Hello!
Answered a few posts above yours.
Click to expand...
Click to collapse
Android is upgrading
Damn I installed the rom and it was working perfectly than I did the aboot update and restarted the tablet and it says secure booting error cause boot certification verify and it stays on the LG screen...FML lol...
Anthony-m said:
Damn I installed the rom and it was working perfectly than I did the aboot update and restarted the tablet and it says secure booting error cause boot certification verify and it stays on the LG screen...FML lol...
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=60879291&postcount=11
You need to flash the 35A_08 aboot zip file I provided in the same place as the ROM download on AFH in order to boot the ROM. The 4.2.2 aboot is only for getting into custom recovery. Once you flash the ROM, the *only* reason for re-flashing the 4.2.2 aboot is to get into custom recovery. But then you need to reflash the 35A_08 5.0.2 aboot in order to boot back into the ROM.
Never mind *****es, did a factory reset and it went to TWRP and I did the update exactly like roirraW "edor" ehT instructed in his OP and I am all set with the new rooted Lollipop rom and TWRP Nice work brother....
---------- Post added at 05:22 PM ---------- Previous post was at 05:20 PM ----------
Yup I just didn't realize I wasn't going to automatically go into TWRP after flashing the 4.2.2 aboot image, once I got in I applied the 35A_08 aboot zip and all is well...
This Rom Is ONLY for the G730A and the G730V variant of the s3 mini, i am not responsable if this bricks your phone. (this is untested on the G730V model but it should work)
How to Flash:
1. Root phone with KingoRoot and install SuperSu(must be superSU)
2. Install SafeStrap (click here for download)
3. Flash the Rom with gapps
Bugs:
WiFi doesn't work
Root
Power off/restart button doesn't work
You tell me
Features:
Deodexed
Zip aligned
Debloated
Faster than the regular rom
Download for G730A
Download for G730v
Credits:
KachowPow (for the boot animation)
Update: WiFi is working and the build will be uploaded soon!!!!!
turnert said:
Update: WiFi is working and the build will be uploaded soon!!!!!
Click to expand...
Click to collapse
Upload please deodexed rom for G730a with working wifi.
Thank you
Dr_Wolodya said:
Upload please deodexed rom for G730a with working wifi.
Thank you
Click to expand...
Click to collapse
I will upload it later today.
Dr_Wolodya said:
Upload please deodexed rom for G730a with working wifi.
Thank you
Click to expand...
Click to collapse
If you don't want to wait you should be able to unzip the current version and add this it the update script(META-INF/com/google/Android)
symlink("/system/lib/modules/prima/prima_wlan.ko", "/system/lib/modules/wlan.ko");
Then just compress the files back into a zip file and it should fix wifi.
Corrupt Zip File
Whenever I try to flash your ROM in Safestrap for my G-730A it always tells me I have a corrupt zip file and it is unable to flash it. I have tried to download it multiple times (the first time failed for the Mediafire link) and copy it back onto my SD card but to no avail. I have followed all the necessary steps to get this Samsung Galaxy S3 Mini somewhat custom ROM ready. I installed the busybox scripts, enabled safestrap, set the SELinux mode to permissive, installed Xposed and the libraries, now I just need to know how to flash a modded version of the Kitkat 4.4.2 stock ROM onto this device properly. Do you have another version that's more stable, or possibly even a link to an entirely different de-bloat ROM? Thanks!
ROMmon1941 said:
Whenever I try to flash your ROM in Safestrap for my G-730A it always tells me I have a corrupt zip file and it is unable to flash it. I have tried to download it multiple times (the first time failed for the Mediafire link) and copy it back onto my SD card but to no avail. I have followed all the necessary steps to get this Samsung Galaxy S3 Mini somewhat custom ROM ready. I installed the busybox scripts, enabled safestrap, set the SELinux mode to permissive, installed Xposed and the libraries, now I just need to know how to flash a modded version of the Kitkat 4.4.2 stock ROM onto this device properly. Do you have another version that's more stable, or possibly even a link to an entirely different de-bloat ROM? Thanks!
Click to expand...
Click to collapse
My suggestion would just be to manually debloat the rom by just uninstalling all the useless system apps. The stock rom I made is very buggy and because you can't root on this rom you have to flash back to stock with Odin if something goes wrong. I can try and reupload to Google drive if that helps, but I am unable to test it because I bricked all 3 of my s3 mini's. I also ported another rom called tencent os but that has more bugs than this one so it's not worth using.
Noted
turnert said:
My suggestion would just be to manually debloat the rom by just uninstalling all the useless system apps. The stock rom I made is very buggy and because you can't root on this rom you have to flash back to stock with Odin if something goes wrong. I can try and reupload to Google drive if that helps, but I am unable to test it because I bricked all 3 of my s3 mini's. I also ported another rom called tencent os but that has more bugs than this one so it's not worth using.
Click to expand...
Click to collapse
I will take you suggestion and just do the following on the stock ROM manually. I will heed your advice that the ROM you created just isn't ready for primetime, and I would honestly rather trade stability for convenience any day. You don't have to go to the trouble of re-uploading a new one to Google Drive if you don't want to. Speaking of Tencent OS, while I was doing research for this device on XDA that did come up in the search results. I thought nothing of it and I didn't even look at the author of it, but I'm pretty sure it was you Turnert. At this point I think I will just stick to the stock 4.4.2 image and stop looking for what isn't there.
UPDATE: I was able to get the number of system apps down to about 150. So far so good, initially there was some black screens and random apps opening after the preliminary uninstall. All seems to be fine after a soft reset though. I'm liking the performance and the added storage benefit without all that bloatware running in the background taking up room.
ROMmon1941 said:
I will take you suggestion and just do the following on the stock ROM manually. I will heed your advice that the ROM you created just isn't ready for primetime, and I would honestly rather trade stability for convenience any day. You don't have to go to the trouble of re-uploading a new one to Google Drive if you don't want to. Speaking of Tencent OS, while I was doing research for this device on XDA that did come up in the search results. I thought nothing of it and I didn't even look at the author of it, but I'm pretty sure it was you Turnert. At this point I think I will just stick to the stock 4.4.2 image and stop looking for what isn't there.
UPDATE: I was able to get the number of system apps down to about 150. So far so good, initially there was some black screens and random apps opening after the preliminary uninstall. All seems to be fine after a soft reset though. I'm liking the performance and the added storage benefit without all that bloatware running in the background taking up room.
Click to expand...
Click to collapse
Honestly I might buy an s3 mini and see if I can improve this rom a bit considering it's been quite a while since I've done any work on this device. I would love to work on this device again and see if I could maybe get aosp or something running on it even if it's not very likely that aosp will ever run on it.
Hi guys! is this 4.4.2 because basically 4.4.4 was never released for this phone? thx.
kbuss said:
Hi guys! is this 4.4.2 because basically 4.4.4 was never released for this phone? thx.
Click to expand...
Click to collapse
Ya its 4.4.2 it may show 4.4.4 but it's not.