Related
Hello, i'm a web developer and have no experience in developing android roms. Anyways, i'm planning to develop a free website which will let any developer create an online kitchen for his rom, where users like me can come and bake rom according to their needs. Now as i don't have any experience with cooking roms, i would like a little help from the developers. Help i am seeking in is, what features a fully customizable kitchen has, how to change the update.zip for the changes, and adding applications to the zip. I have a little bit idea, but want a clear process.
you will get flamed for this
shararti said:
Hello, i'm a web developer and have no experience in developing android roms. Anyways, i'm planning to develop a free website which will let any developer create an online kitchen for his rom, where users like me can come and bake rom according to their needs. Now as i don't have any experience with cooking roms, i would like a little help from the developers. Help i am seeking in is, what features a fully customizable kitchen has, how to change the update.zip for the changes, and adding applications to the zip. I have a little bit idea, but want a clear process.
Click to expand...
Click to collapse
This really is an admirable goal, but you're attempting to bite & chew WAY more than your mouth can handle!!!
You're a web developer, good.
You have no experience in developing android roms, bad.
You want to develop a free kitchen, good.
You have no experience with cooking roms, bad.
You want developers to help you in exchange for a free kitchen for their rom, bad & good.
You don't know how to update the "update.zip" file and re-sign it, bad.
You don't know how to add an APK to the above mentioned "update.zip" file and re-sign it, bad.
You have a little bit of an idea, but want a clearer process, bad.
All of the above noted BAD points, have been discussed, referenced, and linked on these forums countless times shararti.
You really need to search, read, search some more, and apply what you've learned.
I too am a Web Developer/Designer. I've been in the business of creating websites since 1999 (off & on). And the above mentioned project it something I WON'T EVEN DARE ATTEMPT.
Good luck!
I did search, countless times, everywhere. But as lack of my experience with rom development, it was quite confusing. Well I do know signing and adding apk part, and the rest, i agree, i need some help. I'm willing to give my summer to this project and develop this kitchen for the xda community (i'm also willing to give it away to xda). Now if anyone is willing to help me, please pm me.
Actually, it isn't that difficult.
There are quite a few scripts and programs that you could simply employ on your website. I'm sure those developers wouldn't mind
You would have to tier your ROM baking based on the major ROM cores, and the features swappable between flavors of those cores.
It's simply letting the user choose what he wants in his base ROM, pushing the files into the zip, and running the script to sign them.
I'd be glad to guide you in the structure of ROMs, and showing you what can be mixed and matched.
PM me. We'll get started.
Sounds like a very cool idea and I wish you all the best and hope you find some programmers willing to teach you about roms, and you can do the web coding and make your idea a reality.
I'd use it for sure, would be wicked. Imagine going to this web page on your N1 customizing a ROM, building it and then flashing it. All without going near a computer. Sounds unreal!
APrinceAmongMen said:
I'd be glad to guide you in the structure of ROMs, and showing you what can be mixed and matched.
PM me. We'll get started.
Click to expand...
Click to collapse
Perhaps, share the information here once you two have things worked out?!
shararti said:
I did search, countless times, everywhere. But as lack of my experience with rom development, it was quite confusing ...
... I'm willing to give my summer to this project and develop this kitchen for the xda community ...
Click to expand...
Click to collapse
XDA is such a huge resource, full of solutions, bricked devices and lost newbs LOL.
After trolling for a few months, I was ready to flash my first WinMo SmartPhone a few years ago. I haven't used a 'regular phone' ever since.
This would be an ideal summer project. As I said, I'm also a Web Developer.
Hit me up for some theme/template ideas. I do most of my work with Notepad++ and Adobe Fireworks CS4.
Goonish said:
I'd use it for sure, would be wicked. Imagine going to this web page on your N1 customizing a ROM, building it and then flashing it. All without going near a computer. Sounds unreal!
Click to expand...
Click to collapse
hhmm, never thought of that!
You're right ... sounds unreal!
Something the iFans would never be able to attain.
Even better, how about, instead of flashing some large file, only the ones affected by an update are flashed, resulting in a much SMALLER file (thus saving on data usage) and a FASTER flashing (saying on battery life).
shararti said:
Hello, i'm a web developer and have no experience in developing android roms. Anyways, i'm planning to develop a free website which will let any developer create an online kitchen for his rom, where users like me can come and bake rom according to their needs. Now as i don't have any experience with cooking roms, i would like a little help from the developers. Help i am seeking in is, what features a fully customizable kitchen has, how to change the update.zip for the changes, and adding applications to the zip. I have a little bit idea, but want a clear process.
Click to expand...
Click to collapse
Well it all depends on what you want. I would suggest you have a base rom without the boot.img stored with minimal capability in a folder. then allow the user to choose what type of kernel and capabilities they would like with it. That will be the minimum amount for a rom. Then you can follow it up with additions such as extra scripts and applications that can be added and moved to the appropriate directories. at the end, you would zip up the selection and sign it, with the appropriate update-script (which should be the same as the stock rom's unless the additions require something drastic)
So the folder tree should look something like this for one specific ROM:
ROM/ROM Core Files (this is the base rom without boot.img)
ROM/ROM Core Files/META-INF (this is for the update zip)
ROM/ROM Core Files/system (this is where the system apps go)
ROM/ROM Core Files/data (this is where certain apps go)
ROM/ROM Kernels (this is where kernels are/boot.img)
ROM/ROM Kernels/boot.img.1 etc
ROM/Modifications (this is where apps and other mods go)
ROM/Custom Build (this is where the baked rom should go)
Then all you need to figure out is how to move everything to the custom build directory
Move the core to custom directory and a boot.img (rename it from whatever it is to boot.img) and then move and modifications to the appropriate directory inside the custom build folder. Then zip the custom build folder and sign it
That should be about right. its 3 am here lol so i may be missing something. pm me if you need more help or post here
Exactly.
The great thing about it. The ROM core files can be optional. You can bake a kernel or you can bake CM w/ custom kernel and custom mods, i.e. modded phone.apk. You can bake anything and everything.
Mmm baking never sounded so good.
Check this website out:
http://theunlockr.com/2010/03/26/ho...om-for-android-part-1-setting-up-the-kitchen/
My small contribution to this project
The basic kitchen:
forum.xda-developers.com/showthread.php?t=633246
Sorry it's not a link, apperantly new users cannot post links
flybyme said:
So the folder tree should look something like this for one specific ROM:
ROM/ROM Core Files (this is the base rom without boot.img)
ROM/ROM Core Files/META-INF (this is for the update zip)
ROM/ROM Core Files/system (this is where the system apps go)
ROM/ROM Core Files/data (this is where certain apps go)
ROM/ROM Kernels (this is where kernels are/boot.img)
ROM/ROM Kernels/boot.img.1 etc
ROM/Modifications (this is where apps and other mods go)
ROM/Custom Build (this is where the baked rom should go)
Then all you need to figure out is how to move everything to the custom build directory
Move the core to custom directory and a boot.img (rename it from whatever it is to boot.img) and then move and modifications to the appropriate directory inside the custom build folder. Then zip the custom build folder and sign it
Click to expand...
Click to collapse
Ok so after reading it 3 times carefully, this is what i got to:
All roms have same common files, which are:
1. the META-INF folder.
2. the system folder.
3. the data folder.
This is a basic skeleton of any rom, and every rom has these exact files.
Now what i have to do is, when a user cooks a rom, i have to pick the required boot.img and put it into the basic skeleton, in addition to any apps/modifications user want. Then zip the whole package and sign it.
Is that it?
PS: you also said that i may need to change update-script, in what cases that would be required?
PPS: Do i have to make changes to some other files too? cause it sounds too easy to be true =p
shararti said:
Ok so after reading it 3 times carefully, this is what i got to:
All roms have same common files, which are:
1. the META-INF folder.
2. the system folder.
3. the data folder.
This is a basic skeleton of any rom, and every rom has these exact files.
Click to expand...
Click to collapse
They usually have the same folders, not files
the META-INF has the signature files but most importantly the update-script which tells the phone what to do when your flashing the update.
shararti said:
Now what i have to do is, when a user cooks a rom, i have to pick the required boot.img and put it into the basic skeleton, in addition to any apps/modifications user want. Then zip the whole package and sign it.
Is that it?
PS: you also said that i may need to change update-script, in what cases that would be required?
PPS: Do i have to make changes to some other files too? cause it sounds too easy to be true =p
Click to expand...
Click to collapse
that SHOULD be it but remember that you may have to remove some apps from the core files of the rom such as amazon mp3 that people may not want, so you will have to see what apps can be removed and decide whether you want users to be able to remove it or not.
You MAY have to change the update-script if for example you want to put some things in the data partition and symlink them or change the data partition to include the ext partition instead of just for apps. Changes like that are usually for ROMs that are too big to fit properly on the nexus ( youll also have to check the size of the system and data folders to make sure they fit on the phone without modification)
Most of this stuff will be figured out in testing haha but ya at the very basicee its what you have here. You really have to know what you actually want users to be able to cook and then build the kitchen to that effect
flybyme said:
They usually have the same folders, not files
the META-INF has the signature files but most importantly the update-script which tells the phone what to do when your flashing the update.
Click to expand...
Click to collapse
So does that mean i can use same core for all custom baked roms? Except for the update-script, which in rare cases, may need to be altered.
flybyme said:
that SHOULD be it but remember that you may have to remove some apps from the core files of the rom such as amazon mp3 that people may not want, so you will have to see what apps can be removed and decide whether you want users to be able to remove it or not.
Click to expand...
Click to collapse
I took a look at system folder and it's quite populated. Can you tell me what are the basic files that are common for all roms? For the rest of the files, i guess i'll give the user choice to include them or not.
Also can you tell me what is zipalign? Will that be required in baking process?
And to let everyone know, I have already started the working on the kitchen =]
shararti said:
So does that mean i can use same core for all custom baked roms? Except for the update-script, which in rare cases, may need to be altered.
I took a look at system folder and it's quite populated. Can you tell me what are the basic files that are common for all roms? For the rest of the files, i guess i'll give the user choice to include them or not.
Also can you tell me what is zipalign? Will that be required in baking process?
And to let everyone know, I have already started the working on the kitchen =]
Click to expand...
Click to collapse
Well it really depends on what ROM's your looking at. Some devs change the apps to their liking. For example, CyanogenMod has a modified Settings.apk that has features specific to his rom. However, all ROMs have Settings.apk. As such, you will probably have to have a Core ROM folder for each specific rom.
I would suggest looking at other online kitchens and see what features they offer, come up with a specific feature set and then decide what direction that you want to take.
zipalign is a compression technique that optimizes how .apk files are accessed in android. it makes things faster and is not required but would be nice to have. you lose the benefits if you open and modify any files from a zipaligned apk
Let's clear some things up here.
First, core files are not interchangeable between main roms but only flavors of those main roms.
As of now, we have 3 main roms for the nexus one.
CyanogenMod, Modaco Custom ROM, and Desire/Sense Roms.
Each of these roms have their own unique cores amd features and are not interchangeable.
There are flavors of each of these roms.
Flavors of CM has parts that are interchangeable with other flavors but use Cyans core.
Say there is one CM flavor that has some themieing and a few other changes you don't want. You can take the themed files and put them into your CM base and leave the rest out.
You can't put that themeing into a Modaco Custom ROM though.
Kernels I believe are the only things can be put into any ROM base. Most apps are as well.
Now that I look at it. Doing a Nexus One kitchen isn't that difficult but making a full featured HTC kitchen would be a mountainous task. There are so many mods, roms and themes to keep track of. We'd have to designate people from each device forum to feed us the ROMs and parts that are active and functional.
P. S. Lectures are over at 7 today. ill be able to crack down on it with you then
Kitchens are for the Food Network...
well thanks flybyme and APrinceAmongMen, these 2 posts really cleared up somethings. I'm in the process and will keep you guys updated.
QUESTION: how do i change the radio and boot animations in a rom?
PS: the good news is, i'm done with all the hard part, and just few small things remaining. Probably if anything else doesn't comes up, you guys should have a n1 kitchen within few days =D
shararti said:
QUESTION: how do i change the radio and boot animations in a rom?
PS: the good news is, i'm done with all the hard part, and just few small things remaining. Probably if anything else doesn't comes up, you guys should have a n1 kitchen within few days =D
Click to expand...
Click to collapse
boot animations are located either in /data/local or /system/media
radio flash will require you to change the update-script
you can look at the FRF50 update with the radio to figure it out ( or pm me if thats too difficult, its a little late else id do it myself)
Just make sure the radio is excluded by default.
Another thing about radios, the newest radio usually works on older roms, but old radios don't work on the roms released with and after the newest radio.
ROOT
DO IT YOURSELF
FOLLOW THIS VIDEO TUTORIAL by wagstuff13
Wanna make your own rooted software? It's quite simple, due to navossoc! Thanks for this guide and the tool.
[TOOL] Lg Extract Tool
Follow the guide, and first extract the kdz file into a cab file. Extract this cab file, then you ll get a v00y.wbd file and a LGP970.dll. 00 represents your SW version, e.g. 10 or 20 and y stands for a letter like B,N,...
So you e.g. get a file called v20N.wdb file.
Then again open the programm in cmd and extract the wdb file (see in the link above). Be sure it is in the same folder as the lgextract.exe file, or add the patch of the file. Copying it to the same folder is the easier solution
Now you ll get a new folder and in it a few bin files and one fls file.
First cd ti the new bin folder.
You need to add up all the files with this command:
copy /b "LGP970_AP
[*].bin" "LGP970_AP.bin"
Now you have a flashable bin and fls file for Smartflashtool.
If you wanna root it, you need Ubuntu or another linux distribution, which supports the dd command.
Then follow THIS
It's really easy, so dont ask for rooted software anymore, but make it on your own.
To flash and actually root the SW, you need to follow THIS guide, from Step 2 on, and it will be perfectly rooted and you can be sure, that noone patched anything else in your software, cause you made it on your own
Now you can link to this post directly, if anyone is asking for ANY rooted version
There already is an updated tool, which does the unpacking and injecting CWM automatically. I am sorry, but I dont have time, to update the post, so here is the link: http://forum.xda-developers.com/showthread.php?t=1692191
Here you can get every kdz firmware, you need: http://lg-phone-firmware.com/index.php?id_mod=1
More more detailed information will be found here
Catching a logcat:
Whenever you QQ (cry) around because anything doesnt work, every dev can only guess, what s your problem. If you wanna provide the necessary information to him, give him a logcat and he will be happy and fix the bug you are getting.
Ricardo Cerqueira once posted this pic about this topic
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So here is what you need to do, before you report the next bug/error to your dev.
1. Download QtADB from HERE (Find their HP here: http://qtadb.wordpress.com/)
2. Extract it to some place you wanna have it.
3. Now Open QtADB.exe
4. Connect your phone in debug mode
5. Click logcat on the left side (it's the last one)
6. Now Reproduce the problem, that you have, like force closes or other stuff.
7. Maybe reproduce it a second time
8. Push ctrl+A to mark all the lines
9. Right click it and choose, export selected to file
10. Save it to a place, where you can refind it.
11. Upload it somewhere (e.g. mediafire.com)
12. Post in the corresponding thread and give them a description of the error, so they know, what they need to look for and the link to the uploaded logcat.
This will improve a lot of ROMs around here, cause everyone uses it, but hardly anyone (including myself) can contribute to cooking/deving. So do us all the favour, that if you experiance an error and it's cause by the ROM and not a buggy installation, make a logcat and post it to the threads of the devs
Here is how it typically looks (Zeus ROM v4.02 + LG kernel without dimming light):
Code:
01:05:11.781 Error LockPatternKeyguardView 1351 [KeyguardUpdateMonitor.java:344:onReceive()] showAlmostAtAccountLoginDialog()
01:05:11.781 Debug KeyguardUpdateMonitor 1351 [KeyguardUpdateMonitor.java:347:onReceive()] received broadcast android.intent.action.BATTERY_CHANGED
01:05:11.781 Debug KeyguardUpdateMonitor 1351 [KeyguardUpdateMonitor.java:451:handleBatteryUpdate()] handleBatteryUpdate
01:05:27.203 Error LockPatternKeyguardView 1351 [KeyguardUpdateMonitor.java:344:onReceive()] showAlmostAtAccountLoginDialog()
01:05:27.203 Debug KeyguardUpdateMonitor 1351 [KeyguardUpdateMonitor.java:347:onReceive()] received broadcast android.intent.action.TIME_TICK
01:05:27.203 Debug KeyguardUpdateMonitor 1351 [KeyguardUpdateMonitor.java:441:handleTimeUpdate()] handleTimeUpdate
01:05:28.515 Warning Watchdog 1351 Watchdog Big Brother Watching : com.android.server.PowerManagerService
01:05:28.515 Warning Watchdog 1351 Watchdog Big Brother Watching : com.android.server.am.ActivityManagerService
01:05:28.515 Warning Watchdog 1351 Watchdog Big Brother Watching : com.android.server.WindowManagerService
01:05:54.656 Error LockPatternKeyguardView 1351 [KeyguardUpdateMonitor.java:344:onReceive()] showAlmostAtAccountLoginDialog()
01:05:54.656 Debug KeyguardUpdateMonitor 1351 [KeyguardUpdateMonitor.java:347:onReceive()] received broadcast android.intent.action.BATTERY_CHANGED
01:05:54.656 Debug KeyguardUpdateMonitor 1351 [KeyguardUpdateMonitor.java:451:handleBatteryUpdate()] handleBatteryUpdate
01:06:04.937 Error LockPatternKeyguardView 1351 [KeyguardUpdateMonitor.java:344:onReceive()] showAlmostAtAccountLoginDialog()
01:06:04.937 Debug KeyguardUpdateMonitor 1351 [KeyguardUpdateMonitor.java:347:onReceive()] received broadcast android.intent.action.BATTERY_CHANGED
01:06:04.937 Debug KeyguardUpdateMonitor 1351 [KeyguardUpdateMonitor.java:451:handleBatteryUpdate()] handleBatteryUpdate
Added ADB package, from my PC, which is needed from QtADB... See attachments
More detailed information to come here, like governors and schedulers, ...
This is going to be a big NOOB how to, since I read the same questions OVER AND OVER again! If anyone then asks a question, that is already answered here, just redirect them here and close/delete their thread.
I am sorry for not having updated this in a long time, but there is simply stuff, that seems more important to me, than Android
Important Terms:
NooB: My own definition: A person who is new to a subject and knows hardly anything about it. And since you read this, you seem to be one of them Since I am reading and thinking this in this moment, I am, too
CWM: Clock Work Mod (Recovery Menu)
SFT: Smartflashtool
B2C: Lg Mobile Update Tool
ADB: a command prompt, which is very power- and usefull. Instead, you can also use THIS(credits to achyut)
SoD: Screen of Death, which means, that your phone is frozen, and you can't do anything at all. Often combined, with a heating up, of the device.
su/SU: Can have two meanings, either the the Superuser rights, that permit programms/apps root privileges, or superuser binaries (a part of the Superuser app).
UV: Undervolting, which means setting a lower voltage to your CPU/GPU
--> Saves battery, may cause instability.
OC: Overclocking, means setting higher speed to your CPU/GPU
-->Higher speed, but mostly also higher battery drain, or instability.
Nandroid: A backup of the whole system, made with CWM, can be restored within minutes.
OTA: Over The Air, Update via Wifi/network, I suggest you not do use it.
FC: Force Close, error with apps, which forces them to be closed.
chmod: Set permissions to a file. E.g. make it read/writeable.
Lets start with ROMs/kernels:
ROM is practicly the whole Operating System of your android device. It includes all software needed, plus a kernel.
Then there are kernels, which mostly tweak some stuff, in order to save battery, provide more speed, provide stuff like OC(overlocking) and UV(undervolting).
A modified kernel is not a whole ROM! It only is additionally to a ROM, in order to tweak it
A kernel is the HEART of a ROM. (Thanks to gabwerkz) Also see here: Kernel
AVAILABLE ROMs:
There are several ROMs:
Stock Roms:
Froyo (Android 2.2.x) (V10x)
Gingerbread (GB) (Android 2.3.x) (v20x)
Ice Cream Sandwich (ICS) (Android 4.0) Not yet officially available for our device yet.
Custom ROMs
Based on Froyo:
Nova ROM
Pays ROM
Based on Gingerbread:
Zeus ROM
Noa ROM
Marvel ROM
Lemmings ROM
Optimus MAX ROM
several Versions of Suppressed ROM
Marvel v9
Stock ROM Nandroids
Marvel v B, different bases
Based on CM7:
CM7 Tant ROM
Boype's Kang (ROM+Kernel)
Blindsmoke ROM
LewaOS ROM
CICI ROM, Mokee OS
MIUI 2:
Miui 2 Flatzki
Original CM7, which is a Gingerbread ROM build from scratch.
Based on ICS:
Ultrasound ROM
My pride FOP CM9/AOKP
Tezian ROM
Blur ROM
Pandroid ROM
Paranoidandroid ROM
[4.0.4][V30B] XXX Rom
Marvel v D
[ROM+KERNEL][ICS] V30B Repack pure
[P970][ROM] SUPRESSED ROM
[ROM][REPACK] KU5900 ICS
[ROM][4.0.4] IceBOOM
MIUI 4
[ICS] Ultrasound ROM v4 v30C/A (New)
[ROM][ICS] [AROMA] [v30b] Marvel ICS
[ROM][Stock] Marvel Full ROM
[ROM] IZS v0.4 [ICS 4.0.4 V30C] by Huexxx ...
Based on Jellybean:
[ROM 4.1.2 - 4.2] JELLYBAM
[ROM][4.1/4.2][CM10/10.1] Black Jelly Bean Project
[ROM][CM10] (CAMERA,AUTOBRIGHTNESS,AGPS) Dark Mod
PARANOIDANDROID JB
[ROM 4.1.2 - 4.2] JELLYBAM
[ROM][JB:4.1.2] PACman V18.0.0 [AOKP]+[PARANOID]+[CM10] All-In-One
[JellyBean][ROM][4.1.2] Slim Bean
[ROM][CM10][MIUI 2.11.30] EMINENT ROM
[ROM] MIUI V5 Official v3.4.12 Multilanguaje
[JB 4.2.2][ROM]Mackay ROM
[CM10.1|4.2.2][Unofficial] JellyBeer
[ROM][JB 4.2.2][PA3.1.5][PAC22.1.0][AOKP-MR1][CM10.1]P.A.C. man ROM
[ROM][JB] [4.2.2] Avatar ROM for LG Optimus Black (p970)
[ROM/THEME][CM10] OPTIMUS Z ROM | XPERIENCE
[ROM][4.2.2]WizardRom
These are not all by far, so just head over to the Developer Section and check the others out on your own.
Available Kernels:
Froyo:
Nova Kernel, watch out this is not a ROM! It is a modified kernel for CM7 ONLY until now!
Gingerbread-Kernel:
Huexxx kernel, another CM custom kernel
Quasar Kernel for NOVA ROM
ICS kernels:
My blue and white LED kernels
ZeroGravityKernel
v30c Kernel Compiled with Linaro
[Kernel][3.0.8] StrongAccord Kernel for ICS based roms
Find Huexxx' Diana kernel in his blog
Jellybean kernels
Makay ROM kernel
ZeroGravityKernel
What's the best ROM for you:
If you wonder what's the best ROM for you go to: Best ROM for Optimus Black
Or go here: Best ROM for Optimus Black
I gave some information to the ROMs here, and which MIGHT fit you best, just try them.
Root:
Why would u want it?
Cause this gives you something like admin privileges in windows.
This allows you to modify/add, delete,... files, that ususally are protected.
It also allows you to install ClockWorkMod, which in turn allows you to flash custom ROMs, which we all like so much, because of their smoothness, battery saving possibilities, OCing, UVing, and so on
ROOT ON Froyo (2.2.x, v10x)
For the v10x Versions (Froyo, Android 2.2.x), BlackJack should work in most cases, find it here:
[STARTER] Upgrade Kit 3.6 | Apps 1.9 | Root, Flash, Unbrick, Tuts...
Also find a CWM installer in this package, or download ROM Manager from android market and install CWM (ClockWorkMod) from there.
CWM gives you the possibility, to boot to a special kind of OS, that allows you to delete data, mount system, data,... And most important flash .zip files.
If a version cant be rooted by using Blackjack, try SOC (SuperOneClick).
If this still doesnt work, leave a comment, of your version and a link or description, of how to root it.
You also might wanna try UnlockRoot.
ROOT FOR Gingerbread (V20x, 2.3.x)
For v20x(GB, Android 2.3.x): ROOT V20x
see v20a UAE: ROOT v20a (made by myself, hope it works)
see v20S: ROOT v20sYou can download a pre-rooted V20s here. Follow the link HERE
If you still are unable to root it, discuss it here: [Q] How to root P970 Gingerbread V20N
OR here: LGE P970 V20* GB Rooting
DO IT YOURSELF
FOLLOW THIS VIDEO TUTORIAL by wagstuff13
To flash and actually root the SW, you need to follow THIS guide, from Step 2 on, and it will be perfectly rooted and you can be sure, that noone patched anything else in your software, cause you made it on your own
There already is an updated tool, which does the unpacking and injecting CWM automatically. I am sorry, but I dont have time, to update the post, so here is the link: http://forum.xda-developers.com/showthread.php?t=1692191
Here you can get every kdz firmware, you need: http://lg-phone-firmware.com/index.php?id_mod=1
Root on ICS:
It's really simple. Download: THANKS TO ILKO for the clean installer.
Install, run, reboot your phone and your done
Please do not try to install CWM on ICS. You'll get a security error and will have to unbrick your device!
If you already have ICS stock on your phone, there is a simply procedure, that will allow you to get CWM again, but you'll have to install a new ROM via Smartflashtool.
1. You need a V20 ROM, that has been patched with CWM, like THIS ONE.
2. You need Smartflashtool
3. Download Superuser.zip from here: http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.1.3-arm-signed.zip and put it on your SD card.
4. Unpack the V20S patched .7z file
5. Flash the .bin file using SFT
6. Your phone will reboot to recovery
7. Do a factory reset and if you wanna stick with a rooted v20S, just flash the superuser.zip and reboot. If you already want to install a custom ROM, just put that on your sd card and flash it (see how to install a custom ROM).
8. Reboot and enjoy your new ROM
The UNROOT
If you wanna unroot your device, why so ever, the easiest way is to use Unlock Root (Link above) open it, connect your phone via USB, enable Debugging Mode and click unroot. If you wanna unroot it, e.g. to be able to send it back to LG on warranty, better use the method below, to unbrick your device with R&D tool.
Because like this, you will get back an unrooted device, which has also been hardresetted. So LG will hardly/never get a clue, that it has ever been rooted.
Dont forget to format your SD card as well
How to install Custom ROM's
First of all, you need a rooted phone already. See above, how to do it
Then you need to install CWM (Clock Work Mod), you can do this e.g. by downloading ROM Manager, install it, open it
and find Install Clockwork Mod Recovery. Hit it, wait some seconds and click LGE optimus Black. Wait again, till the file has been downloaded and installed and your all set Now you can reboot into Recovery, with the second option. It says, what it does: Reboot to recovery
Now grab the ROM you desire the most and download the zip. Plug your phone to the PC (via USB) open up the folder of your SD card, and copy the file you downloaded in there. Dont copy it into a subfolder, since it will only be harder to find.
Now go back to ROM Manager and click reboot recovery, or if you have adb installed, just type reboot recovery in a terminal on your pc.
You are in recovery menu now.
First of all do a nandroid backup (explained on top). To do so, go to Backup and Restore, then Backup and wait.
It will now make a complete backup of the whole system, settings, and so on.
If something goes wrong during the installation of the new ROM, you can simply revert back to the state you had before.
Your ready to install the new ROM now.
Now it depends, on if you only update a ROM, like CM, or if you install a completely new ROM.
If you install a new ROM, do a full wipe. This means, wipe data/factory reset, wipe cache, go to advanced, wipe dalvik, wipe battery stats and go back. now select install zip from SD card. Then choose zip from sdcard and then select the file you downloaded.
Wait till all is set up and enjoy your new ROM
If you only update a ROM, follow the instructions given in the thread about the ROM.
What to do if the Update failed?
Well it depends on how much you failed, what u had installed before and if Huexxx Recovery fix was applied.
First scenario:
Huexxx's patch was applied in the ROM before.
This enables to boot to recovery by repeatedly pushing a hard key, like volume- or g-key directly after you start the phone.
Push em fast, while the softkeys are flashing(turn on and off). As soon as they stop flashing, you will be in recovery and can either restore a backup, or install another zip file.
Second scenario:
CWM is still enterable via adb.
You first of all need to download and "install" ADB.
Best will be, to simply extract the files to C: and also rename the new folder to a short term like "ADB" without "".
Then open the command prompt, navigate to the folder of adb: e.g.
Code:
C:
cd ADB
cd adb
Now you should be in the adb folder, where you can find adb.exe and some other files.
If not, check out, how it is called and navigate there in another way.
"cd" means change directory, so if you didnt rename it to ADB, but e.g. ADB-sdk, type cd ADB-sdk instead.
Ok, now simply type adb reboot recovery and wait.
Now your phone should restart to Recovery Mode.
But watch out, if you do this with a working ROM, and forgot to install CWM, you will get a factory reset!
Third scenario:
None of the above worked. Then you have no chance, but to to use the unbricking method below. Then root your device, install CWM and you can have a new try
Unbricking:
Your Phone doesnt boot anmore or only shows the LG screen contantly!
If your phone is stuck in bootloop, have a look in here: SMARTFLASHTOOL
You can download the patched V20s from ABOVE or take the v10a from here
Flash with R&D Tool:
The upper is the easier and faster solution, but if you really need R&D Testtool, because Smartflash didnt help, grab R&D tool HERE(it's in the package), and then follow THIS guide
You can also use the latter method, if you wanna return your phone on warranty. But I would make a Factory reset afterwards anyway. And don't forget to remove all files from your SD card as well, since this could show them as well, that the phone might have been rooted.
Themes And Apps
Themes are modifications to the look of your UI (UserInterface). This gives your Operating System a different Look.
There are a lot of things, you need to pay attention to.
For example there are ODEXED = easier on space, tougher on tweaking and ram usage (just a short explanation)
and Deodexed = easier to tweak, lighter on ram, heavier on space
Find more information on this HERE
Now you need to know, if your ROM is odexed, or deodexed. You mostly find information on this directly in the thread of the ROM you are using (see above).
If you know what kind of ROM you are using, go to the Themes link above and choose whatever you like. There is almost always written, for which specific ROM this was made (e.g. Zeus ROM, Stock GB, stock Froyo,...) And mostly, if you need a odexed or deodexed Version of a ROM, or not.
It's pretty much like odexed files also work on deodexed Software, but not the other way around. (NOT ALWAYS)
Then you encounter bugs like missing statusbar, display bugs, glitches, ...
So check if the theme you are willing to try will REALLY work for your device.
If you wanna make your own Themes, check out UOT KITCHEN Or these two threads: HERE AND HERE Credits to gabwerkz and Huexxx.
More to come, leave comments with topics, I am supposed to add, or critics
To come
Whatever you want me to post here
Couldnt find what you were looking for? Did you already use the search in upper right corner?
If not, go to Q&A section and post your questions there pls.
Only post here, if I am supposed to add something, or explain it a better way
AND THANK ME IF IT HELPED YOU OUT!
N00BY0815 said:
A kernel is not a whole ROM! It only is additionally to a ROM, in order to tweak it
Click to expand...
Click to collapse
Just a correction. Kernel is not an addition, it is the heart of a ROM. May it be stock or modified.
Insert "A modified kernel" at the beginning without modifying your sentence.
N00BY0815 said:
A modified kernel is not a whole ROM! It only is additionally to a ROM, in order to tweak it
Click to expand...
Click to collapse
yup, kernel is not addition
about kernel from wiki http://en.wikipedia.org/wiki/Kernel_(computing)
gabwerkz said:
Just a correction. Kernel is not an addition, it is the heart of a ROM. May it be stock or modified.
Insert "A modified kernel" at the beginning without modifying your sentence.
Click to expand...
Click to collapse
I suppose you could always say that a "custom" kernel is an addition... the stock kernel is already there.
avcosta said:
I suppose you could always say that a "custom" kernel is an addition... the stock kernel is already there.
Click to expand...
Click to collapse
No, it's not. It is overwritten. It's not an addition, but a replacement.
Hi... Thanks for the NOOB info.... just requesting HOW TO unroot V20B for NOOB...
Thanks,
NOOB from Malaysia
oato7 said:
Hi... Thanks for the NOOB info.... just requesting HOW TO unroot V20B for NOOB...
Thanks,
NOOB from Malaysia
Click to expand...
Click to collapse
Can you tell me, why anyone with a rooted phone would want it? I mean, sending it back to the provider for repair or similar is a reason, I can understand, but what are other reasons? Idk if it's enough to flash it with smartflash and afterward go to hidden menu and do a factory reset, but I guess this should work fine
Any suggestions on this? Or maybe the R&D tool and workaround?
This is not a Q&A thread
Do not post questions in this thread, they will be reported and deleted.
Zaihanzainal said:
dude...... read the first post...............
Click to expand...
Click to collapse
The means to unroot isn't in the first post, and the OP is discussing this issue with him so - don't post unnecessary chides, it is a legitimate question, posted before I warned that this isn't a Q&A thread. Hopefully the answer will be included in the OP, as it is something that will be asked - over and over again .
N00BY0815 said:
AND THANK ME IF IT HELPED YOU OUT!
Click to expand...
Click to collapse
You have helped me out quite a few times earlier and now I thank you for the "real thing": being generous enough to go through the trouble of making things easier to everyone else. That takes patience and a really good deal of generosity. And maturity above everything else.
When I began working with IT by 1981 I was nice to my peers. Then I became more and more technical and efficient at my job, and harder and harder at my peers and everyone else.
In return (despite all my capacity) I only drew drawbacks. My career sank. I had to start it all over again, with a different drive. ;-)
Today IT is just a hobby, and it's encouraging to see that at least a few of the most gifted people are showing that gift and contempt are not always bound to each other! :-D
Attitudes like yours, although they don't warrant you (1) a $300K/Y job, they DO warrant you (2) a very, very nice feeling that is hard to describe (albeit I suspect that you already know it) and (3) raise the suspicion that there's really a God and that (4) we are really above the rest of the animal kinds. I hope you get all four.
Congratulations and just forgive me for the last kitsch words
Whammamoosha said:
You have helped me out quite a few times earlier and now I thank you for the "real thing": being generous enough to go through the trouble of making things easier to everyone else. That takes patience and a really good deal of generosity. And maturity above everything else.
When I began working with IT by 1981 I was nice to my peers. Then I became more and more technical and efficient at my job, and harder and harder at my peers and everyone else.
In return (despite all my capacity) I only drew drawbacks. My career sank. I had to start it all over again, with a different drive. ;-)
Today IT is just a hobby, and it's encouraging to see that at least a few of the most gifted people are showing that gift and contempt are not always bound to each other! :-D
Attitudes like yours, although they don't warrant you (1) a $300K/Y job, they DO warrant you (2) a very, very nice feeling that is hard to describe (albeit I suspect that you already know it) and (3) raise the suspicion that there's really a God and that (4) we are really above the rest of the animal kinds. I hope you get all four.
Congratulations and just forgive me for the last kitsch words
Click to expand...
Click to collapse
Thank you very much, for such an encouraging post I like and appreciate it very much. But there is one thing, that I can't stop wondering about, how could I help you out already? I mean you should probably know more bout IT and programming and stuff than me... Just curious Anyway, I like to help ppl out a lot. I also do this in real life a lot, but the problem is, that a lot of ppl dont pay you back at all. Just using one's knowledge/money/whatever and not giving back anything, or even ignoring advices and stuff is something I hate the most! Just like some of the Noobs here. I have nothing against questions and there never will be a stupid one, so dont stop asking, it is an important part in life. But I hate the ignorant noobs, that dont even try to use the search, dont look around in the forum, are simply too lazy, to look around but simply create their own threads, with questions, or information, that can already be found here. And mostly you can't only find it once, but already several times, because of them.
So dont stop asking, but use search first, pls... I'm also still a noob, so I also gotta ask a lot of questions, and this will never stop, until I either throw away all the IT around me, a solar storm makes it impossible for us to use any kind of IT, or I am dead
So to all the others here, share your knowledge with the ones, who also would like to have it. I also know, that it is time consuming, but trust me, giving, will mostly/always be warranted in any way later. I believe in karma and who gives good, will receive good. So maybe one day, when you dont have time/dont wanna mod anymore, but still wanna use good modded software, you need someone else to do it for you and who could do this better, but a person, that learned from you? So I never will stop supporting this community as long, as I got some time.
And I also know, I was writing a lot now and better stop now
Just one last thing, keep me posted, if we need some information added, so it can be found more easily, as long as it can be explained in a way, even I will understand
N00BY0815 said:
Thank you very much, for such an encouraging post I like and appreciate it very much. But there is one thing, that I can't stop wondering about, how could I help you out already? I mean you should probably know more bout IT and programming and stuff than me... Just curious
Click to expand...
Click to collapse
It depends on the time frame.
I know a lot of old-school stuff that is still valid, but when it comes to Android I'm a complete moron. Got my OB by Oct 2011 and I'm still trying to leave the craddle. BTW this OB is my first SP, and I wanted to take the most out of it.
Yes I need help, and XDA is BY FAR the best Android site I've seen in the net.
N00BY0815 said:
Anyway, I like to help ppl out a lot. I also do this in real life a lot, but the problem is, that a lot of ppl dont pay you back at all. Just using one's knowledge/money/whatever and not giving back anything, or even ignoring advices and stuff is something I hate the most! Just like some of the Noobs here. I have nothing against questions and there never will be a stupid one, so dont stop asking, it is an important part in life. But I hate the ignorant noobs, that dont even try to use the search, dont look around in the forum, are simply too lazy, to look around but simply create their own threads, with questions, or information, that can already be found here. And mostly you can't only find it once, but already several times, because of them.
So dont stop asking, but use search first, pls... I'm also still a noob, so I also gotta ask a lot of questions, and this will never stop, until I either throw away all the IT around me, a solar storm makes it impossible for us to use any kind of IT, or I am dead
Click to expand...
Click to collapse
That's the spirit!
N00BY0815 said:
So to all the others here, share your knowledge with the ones, who also would like to have it. I also know, that it is time consuming, but trust me, giving, will mostly/always be warranted in any way later. I believe in karma and who gives good, will receive good. So maybe one day, when you dont have time/dont wanna mod anymore, but still wanna use good modded software, you need someone else to do it for you and who could do this better, but a person, that learned from you? So I never will stop supporting this community as long, as I got some time.
Click to expand...
Click to collapse
For some time I used to post frequently at ABXZone (used to be a more populated community) under the same nickname and believed EXACTLY the same thing. I don't post so often these days, since my kids keep me busy enough. But as I said, when it comes to Android phones I'm still a complete moron, so in some way I'm being paid back here for that I did there.
N00BY0815 said:
And I also know, I was writing a lot now and better stop now
Just one last thing, keep me posted, if we need some information added, so it can be found more easily, as long as it can be explained in a way, even I will understand
Click to expand...
Click to collapse
Don't need to ask!
N00BY0815 said:
Updated first post, hope you like it, if not, or if anything is still missing, tell me pls and I ll try to add it And yes it is starting to get BIG
-edit-
Updated again, pls check it out and leave feedback, if everything is fine the way it is. Or if I need to change anything
Click to expand...
Click to collapse
Maybe you could include Huexx method for handling bootloop to get into cwm
Sent from my LG-P970 using xda premium
can you upload eRecovery for CM7. Link in original thread is unavaible.
And where do I get it from? PM the original poster of the topic pls ;-)
-edit-
Ask Huexxx either in a PM, or simply in his thread, since I am sure, he still has got it somewhere on his PC
Or anyone else might mirror it.
Firstpost Updated.
Sent from my LG-P970 using Tapatalk
Good job with the guide
I wish I had something like this back in the day when I was starting to play with Android phones
Why don't you add a small reference to how to theme? (by Gabwerkz)
http://forum.xda-developers.com/showthread.php?t=1469987
And how to flash/create bootanimations:
http://forum.xda-developers.com/showthread.php?t=1096068
It'll help some people who want to fully customize their phones in their own way
kingzain900 said:
Good job with the guide
I wish I had something like this back in the day when I was starting to play with Android phones
Why don't you add a small reference to how to theme? (by Gabwerkz)
http://forum.xda-developers.com/showthread.php?t=1469987
And how to flash/create bootanimations:
http://forum.xda-developers.com/showthread.php?t=1096068
It'll help some people who want to fully customize their phones in their own way
Click to expand...
Click to collapse
Read the first post carefully and you will already find the link to gabwerkz and another theming guide and about making bootanimations, is nothing for a noob guide. This is meant to help ppl who start out with android. Not list every single topic in here I think this is a bit too advanced for noobs. And as soon, as anyone is a bit into the whole android thing, he will know, where to search for and find sources of knowledge, he/she is willing to get But thanks anyway, maybe I'll add it to the second or third post
Sorry guys, I am really busy last time and will still be for a while, but read this meanwhile http://forum.xda-developers.com/showthread.php?t=1242323
Welcome to the [STICKY] I9505G GE GALAXY S IV ( INDEX ) ROM's / LINKS / HOW TO THREAD formally the DISCUSSION GUIDE
This is the Official Index Roll up thread for the I9505G Google Edition Galaxy S IV. In this Index you will find helpful, links, guides, how to's and instructions for your I9505G.
Please Post any links or helpful information in this thread or you can PM me so I can link it in the OP ( If your on the I9505/I9500 Please do NOT ASK about development for your device this is for the I9505G ONLY
(DISCLAIMER) As always I nor anyone is responsible if you cannot follow instructions in this or any other thread. We assume NO liability for bricks, loss of job, or the end of life as we know it.
GUIDES & LINKS
How to get CM 10.1 & CM 10.2 working on the I9505G
How Unlock the Bootloader for the I9505G
[OTA] OTA ZIP 4.3 for I9505G
How to Update your Baseband to get the 4.3 OTA
TOUCHWIZ Development Thread Q&A
Camera Save to SD Card for Google Edition ROM's
I9505G How to Set Device Mount Points in Android Kitchen GE S IV
4.3 SD Card Issue Fixed
How to upgrade a Stock+Root+Custom_Recovery I9505G from 4.3 to 4.4 and keep all Data
ROOTING THREADS
How to Root 4.2, 4.3, 4.4 JB, Kit Kat I9505G
ROM's
[ROM][Linaro-4.8] XenonHD-4.4.2 Alpha 1 (5/1/14) *Truly Stable, Fast & Butter
GOOGLE LITE EDITION 4.2.2 v.2 MFD
GOOGLE LITE EDITION 4.3 I9505GUEUBMH1 Ktoonsez Kernel
TOUCHLITE GE TOUCHWIZ ROM
[ROM] Google Edition 4.3 [Clean][Deodex][276MB]
RECOVERY
How to install TWRP via Odin on the I9505G
TWRP for the I9505G
[BETA][RECOVERY] ClockworkMod Recovery 6.0.3.6
[ODIN[TAR] Stock Recovery Images
MODEMS
ODIN TAR MODEMS
STOCK FIRMWARE LEAKS
Stock ODIN FIRMWARE Leaked 4.3 MFP
Stock ODIN FIRMWARE Leaked 4.3 MG8
ODIN AND HEIMDAL PACKAGES
Stock HEIMDAL 4.2.2 MFD back to Stock
[ODIN][TAR] I9505GUEUAMFD 4.2.2 Full Rooted Restore
[ODIN][TAR] I9505GUEUBMH1 4.3 Full Rooted Restore
[ODIN][TAR] I9505UEUBMH5 4.3 Full Rooted Restore
[ODIN][TAR] I9505GUEUBMKG 4.4 Full Rooted Restore
[ODIN][TAR] I9505GUEUBML4 [4.4.2] Full Rooted Restore
[ODIN][TAR] 4.4.3 I9505GUEUCNE3 Full Rooted Restore
[ODIN][TAR] 4.4.4 I9505GUEUCNF3 Full Rooted Restore
Reserved
Big Thanks to Illogic6 for being the Very 1st Person to get Touchwiz Booted to the I9505G post #31 and SamuriHL for solving the Baseband Update Issue and Chainfire
Modem Update : Due to the secure boot loader we cannot flash modems via cwm or any other custom recovery. You MUST update your firmware via Odin
Touchwiz Works with some ROM's like BareBones from the I9505 forum being successfully booted on the I9505G. TW Development is ongoing for the I9505G but with the small partition size some issues exist, and are being researched and worked out.
http://forum.xda-developers.com/showthread.php?t=2405273
11/28/2013 : KitKat initial release this week New Updated Odin Packages and ROM's please check A&D section
DONT FORGET TO THANK THE MEMBERS AND DEVS WORKING HARD ON THE I9505G DEVELOPMENT
07/21/2014: I just wanted to make a note that I still get emails and requests for help and although I am no longer doing any sort of work on the I9505G I will try to help you out if you PM me. PLEASE BIG THANK YOU TO @SamuraiHL he is really the one maintaining everything for I9505G Owners and if you have not thanked him please do. Actually without volunteering him he is your best POC for anything current. I will maintain the thread for organization now and then. ALOHA
MJHawaii said:
Reserved :good:
Click to expand...
Click to collapse
Nice to see someone do this. Hope this will build up and morph into ROM's, etc.
How is your ROM coming along?
wilbarger said:
Nice to see someone do this. Hope this will build up and morph into ROM's, etc.
How is your ROM coming along?
Click to expand...
Click to collapse
Right now just standard kitchen tweaks on 4.3 but I am trying to get the whole device mount points set up in Cygwin and I'm having trouble because when I extract everything and open up the recovery.fstab file with notepad ++ it does not show anything but 0p1 nothing for system, boot & data so I'm lost and need help
Sent from my GT-I9505G using Tapatalk 2
MJHawaii said:
Right now just standard kitchen tweaks on 4.3 but I am trying to get the whole device mount points set up in Cygwin and I'm having trouble because when I extract everything and open up the recovery.fstab file with notepad ++ it does not show anything but 0p1 nothing for system, boot & data so I'm lost and need help
Sent from my GT-I9505G using Tapatalk 2
Click to expand...
Click to collapse
One person you might contact is mohan_kr. He has come over to the S4 from the Skyrocket recently. Excellent at working on the ROM's. Sorry I can not be of assistance, but I am not very advanced on Android.
wilbarger said:
Nice to see someone do this. Hope this will build up and morph into ROM's, etc.
How is your ROM coming along?
Click to expand...
Click to collapse
wilbarger said:
One person you might contact is mohan_kr. He has come over to the S4 from the Skyrocket recently. Excellent at working on the ROM's. Sorry I can not be of assistance, but I am not very advanced on Android.
Click to expand...
Click to collapse
That's what this thread is for though for everyone to get together share information and collaborate.
Chahk's post about mount points and getting other CM/AOSP ROMs working on I9505G deserves its own link:
http://forum.xda-developers.com/showpost.php?p=43843048&postcount=30
MJHawaii said:
Right now just standard kitchen tweaks on 4.3 but I am trying to get the whole device mount points set up in Cygwin and I'm having trouble because when I extract everything and open up the recovery.fstab file with notepad ++ it does not show anything but 0p1 nothing for system, boot & data so I'm lost and need help
I saw Chahk post and it is helpful this is where I'm at right now read above. I did pm Chahk and a few others for help. I will work on it a little later this weekend
Sent from my GT-I9505G using Tapatalk 2
Click to expand...
Click to collapse
Sent from my GT-I9505G using Tapatalk 2
irishrally said:
Chahk's post about mount points and getting other CM/AOSP ROMs working on I9505G deserves its own link:
http://forum.xda-developers.com/showpost.php?p=43843048&postcount=30
Click to expand...
Click to collapse
x2
I've found that very useful. Been able to get every AOSP/CM based ROM to boot by editing the updater-script to match the correct partition.
Has anybody noticed that photos taken with the front facing camera on CM sometimes have green distortion? That was the only bug I've found. Unfortunately, that flared up my phone OCD enough to go back to the 4.3 leak.
Thanks for putting this thread together, OP!
illogic6 said:
x2
I've found that very useful. Been able to get every AOSP/CM based ROM to boot by editing the updater-script to match the correct partition.
Has anybody noticed that photos taken with the front facing camera on CM sometimes have green distortion? That was the only bug I've found. Unfortunately, that flared up my phone OCD enough to go back to the 4.3 leak.
Thanks for putting this thread together, OP!
Click to expand...
Click to collapse
Your Welcome. So I read on the other thread and I know myself and others are looking at how we can port other ROMs specifically touchwiz over to the G the partition as you know is an issue but I think with collaboration can be solved soon.
Keep it coming let's solve problems!
Sent from my GT-I9505G using Tapatalk 2
MJHawaii said:
Your Welcome. So I read on the other thread and I know myself and others are looking at how we can port other ROMs specifically touchwiz over to the G the partition as you know is an issue but I think with collaboration can be solved soon.
Keep it coming let's solve problems!
Sent from my GT-I9505G using Tapatalk 2
Click to expand...
Click to collapse
I took a TW ROM and edited the script for our devices. It boots, but the display never kicks on. You get the boot animation sound and it even mounts the storage on my computer.
illogic6 said:
I took a TW ROM and edited the script for our devices. It boots, but the display never kicks on. You get the boot animation sound and it even mounts the storage on my computer.
Click to expand...
Click to collapse
Wow that's great maybe you can help me with my script it sounds like your further along than some. I wonder what would cause the display bug doesn't sound like a boot issue
Sent from my GT-I9505G using Tapatalk 2
MJHawaii said:
Wow that's great maybe you can help me with my script it sounds like your further along than some. I wonder what would cause the display bug doesn't sound like a boot issue
Sent from my GT-I9505G using Tapatalk 2
Click to expand...
Click to collapse
Here's the ROM I was messing with. I used the "old firmware" because it was the newest one when I first looked. http://forum.xda-developers.com/showthread.php?t=2349369
I've attached my modded updater script. (You will have to remove the .txt extension. Wouldn't let me upload without it.) All I had to do was edit which /dev/block the script mounts before it copies stuff over. If I recall correctly, I only had to change the dev it flashes the boot.img to. See this post: http://forum.xda-developers.com/showpost.php?p=43843048&postcount=30
include 'standard_disclaimer.php';
illogic6 said:
Has anybody noticed that photos taken with the front facing camera on CM sometimes have green distortion?
Click to expand...
Click to collapse
I think this might be fixed in the newest CM nightly. I've took about 20 selfies with the front facing camera and haven't had distortion at all. Before I'd get it every 3 or 4 photos.
Edit: Disregard the above. The problem is back, but I'm thinking it might be the 4.3 camera zip I've been using. Hmmmmmmm......
I think I jumped the gun a bit on rooting my I9505G right when I got it. I've never successfully rooted it, but I managed to get on the 4.3 ROM with a few quirks here and there. My ultimate goal is to get Paranoid Android with halo running, but I'll have to dedicate a day to the whole process. I'll be keeping track of this thread.
illogic6 said:
Here's the ROM I was messing with. I used the "old firmware" because it was the newest one when I first looked. http://forum.xda-developers.com/showthread.php?t=2349369
I've attached my modded updater script. (You will have to remove the .txt extension. Wouldn't let me upload without it.) All I had to do was edit which /dev/block the script mounts before it copies stuff over. If I recall correctly, I only had to change the dev it flashes the boot.img to. See this post: http://forum.xda-developers.com/showpost.php?p=43843048&postcount=30
include 'standard_disclaimer.php';
Click to expand...
Click to collapse
Thanks a lot I will take a look tomorrow and see what I can do
Sent from my GT-I9505G using Tapatalk 2
illogic6 said:
Here's the ROM I was messing with. I used the "old firmware" because it was the newest one when I first looked. http://forum.xda-developers.com/showthread.php?t=2349369
I've attached my modded updater script. (You will have to remove the .txt extension. Wouldn't let me upload without it.) All I had to do was edit which /dev/block the script mounts before it copies stuff over. If I recall correctly, I only had to change the dev it flashes the boot.img to. See this post: http://forum.xda-developers.com/showpost.php?p=43843048&postcount=30
include 'standard_disclaimer.php';
Click to expand...
Click to collapse
Great work Illogic I wonder why TW will not display I tried as well but I did not get as far as you mine fails during the installation.
Also did you see my post on getting Cygwin to set device mount points that in itself will speed things up
Sent from my GT-I9505G using Tapatalk 2
MJHawaii said:
Great work Illogic I wonder why TW will not display I tried as well but I did not get as far as you mine fails during the installation.
Also did you see my post on getting Cygwin to set device mount points that in itself will speed things up
Sent from my GT-I9505G using Tapatalk 2
Click to expand...
Click to collapse
I haven't used Cygwin before. I'll take a look at it today.
Also going to mess around with TW a little more. Maybe we just need some libs from the stock 9505g rom or something.
Update: I'm afraid I may have mislead you earlier. It appears that you need more than just the updated update-script in order to get touchwiz to boot. You also need a kernel from one of the 4.3 leaks. Here's the one I've been using. (Attached) Not only does it boot, but the soft keys work and you can hear the sound effects of the lock screen. I'm very close.
illogic6 said:
I haven't used Cygwin before. I'll take a look at it today.
Also going to mess around with TW a little more. Maybe we just need some libs from the stock 9505g rom or something.
Update: I'm afraid I may have mislead you earlier. It appears that you need more than just the updated update-script in order to get touchwiz to boot. You also need a kernel from one of the 4.3 leaks. Here's the one I've been using. (Attached) Not only does it boot, but the soft keys work and you can hear the sound effects of the lock screen. I'm very close.
Click to expand...
Click to collapse
Wow Illogic your close bro thanks for your hard work the libs does sound like it would cause the display problem I'm gonna play around with this too. All I did was unpack stock 4.3 and zip and deo the files with root. The problem I am having is that I am still learning U-scripts and so I cannot get anything to flash. I get failed on 0p21 even though its changed. Maybe I can pm you what I did later and get your feedback cuz your miles ahead of me
Sent from my GT-I9505G using Tapatalk 2
I've merged libs from the leaked 4.3 build into the TW ROM without overwriting anything. Didn't seem to change anything. At this point, I'm playing with magic I don't understand so not sure how much farther I'm going to get.
Would really like figure out which files in the system are responsible for the display. Perhaps we need to overwrite those files. Google is failing me so far.
---------- Post added at 04:45 PM ---------- Previous post was at 04:29 PM ----------
Tada! :victory:
The error message goes away. Right now, the web browser force closes... that might be because of the ROM I was modifying. What I did was use the 4.2.2 kernel that shipped with the google play phones. That booted AND activated the display.
http://i.imgur.com/HZaraPK.jpg
I have decided to rework the thread to ovoid any confusion as the intent of posting this thread was to ask questions about compiling custom Roms from AOSP source that someone like myself who gained their development experience on other devices that building from pure AOSP code was not an option and are not as familiar working with AOSP. In the past my own experience comes from using and modifying for example the Cyanogenmod source so after attempting to now base my Rom on AOSP this time around with Lollipop have run into a few unfamiliar differences. As each question or topic is addressed I will update the Op. The hope is not only will I find solutions or answers to my own questions but that others in the same position will also be able to find use of the discussions posted in this thread.
Compiling the AOSP source into a format that can be safely flashed using a custom recovery. This was a 3 part question the first was just simply how to compile AOSP in a format other then .img files that can be flashed using a custom recovery without the need of flashing through fastboot or needing to use the adb sideload option.
1, Compiling AOSP into the for of an update.zip.
This was answered in short by know.patience by suggesting to use the “make otapackage” command in place of "make" to start the build. Was also made aware that a few modifications would need to be made to avoid producing an update package that does not use the new block format but instead the old style zips we are most used to seeing.
2, Now can create an update.zip using the “make otapackage” command ran into an issue that by flashing the update.zip produced would in the process replace the custom recovery used to flash with the Nexus Stock recovery. This was answered by Lethargy who suggested and provided a Link for the following commit.
For getting rid of the AOSP recovery:
https://github.com/Lethargy/android_build/commit/48521e167c642db76c9d4f52b1c63f9abc7f707f
https://github.com/Lethargy/android_build/commit/1d9224bd45ef2b4f5601a157de2bfe3bb1c95558
3, Now can create an update.zip using the “make otapackage” and after applying the above commit are now able to flash the update.zip without replacing the recovery Lethargy also provided links for the following commits.
To get rid of the block-based zip format:
https://github.com/Lethargy/android_build/commit/4d458300d935a3a9d893a590286cb578dcf54db2
You'll also want to make sure you have this commit so it doesn't flash awfully slow in recovery (8~ minutes, but only around 1-2 minutes with this commit):
https://github.com/Lethargy/android_system_extras/commit/52f8d5fc3edfacd112827d0a41516c1dc5f4a468
This one isn't required but you may as well:
https://github.com/Lethargy/android_build/commit/242be9ae4f05e3cb1d39d635cac7147ff904700c
Compiling using the AOSP Master branch vs release branches. In following the directions provided on the Google development site are given the command for downloading the source code using the Master branch. Using the Master branch as apposed to a release branch such as android-5.0.2_r1 or lower have found that the source compiles just fine but have run into one issue and just a general question that a little explanation would be helpful for general understanding of the AOSP Master branch.
The issue is that after flashing a Rom compiled using the Master branch everything in the Rom works as expected other than the radio. I have so far using the same exact vendor blobs as compiling a release branch have not had a signal and baseband version is listed under about phone as unknown.
The general question is that the android version listed compiling a Rom using the Master branch is version 5.0.50.50.50.50. In general I have yet to understand what this version number represents and very little to no information available via the Google Box.
Between the both I now wounder if the Master branch is intended for actual use or if so what changes are required so the baseband version is recognized and radio / Ril will work?
Quick Answer:
Google first commits new code into master and then is later tagged with an update for realease so in generall many things can be broken and the master branch is and not intended to be stable so if building from master expect that things will be broke or buggy.
Compiling Rom and Kernel together. For those of us again used to compiling using say the CM code are now used to compiling the Kernel along with the rest of the code. I know it is easy to just compile the Kernel and include in the device tree but for those of us who would still like the Kernel compiles with the rest of the code there is no information available on the Google Developers site for doing so and there seems to be a few differences as have tried just using the lines used in the CM Hammerhead device repository. I have come across these commits from Cl3Kener that should help. Hate posting other developers code but is on Github so is there for the public at large. So far have only tested as is so will update if finding not all changes are necessary or can be modified.
Inline Kernel Building
https://github.com/OptiPop/device_lge_hammerhead/commit/7de8fd95b6df16cb6311161d5048874d69cf1cb1
https://github.com/OptiPop/device_lge_hammerhead/commit/87768896f4eb8fcd989ce3b8492ca65305513851
https://github.com/OptiPop/device_lge_hammerhead/commit/5460eb3aa76ea5d813f64a3b3bab6ace1be6de68
Adding Pre-Built APK's
Seems Sprint users need a few apk's for updating prl and what not that are included into the Stock release but are not part of the AOSP code. For some reason through vendor or even device have tried adding these apk's into the build. First try I created a sprint vendor section and received a few errors untill learning would need to add sprint into a vendor white list found in build. Will post link to file later. After found the extra "Services.jar" I found in the stock image not found in the aosp compiled Rom did copy into the build but the apk's had not. Looking in the other vendor blobs noticed lge adds "qcrilmsgtunnel.apk" so followed the example and even tried just adding the other spk's into lge expanding the list used for adding in "qcrilmsgtunnel.apk" but still no luck. Also have tried adding through the device files for Hammerhead just to get them into the Rom for testing and still no luck. If this was CM or any other Rom not using pure aosp this would have been a 5 minut project so need to do some aditional homework.
Again think this thread could be a good resource for developers who are new to building their Roms around AOSP so wanted to include everything I run into during the process of moving away from using a heavily modified CM based code as the base of my Rom to using AOSP in its place so developers who are or in the same process or for those in the future can use as a resource to quickly adjusting. I have been building CM based Roms like Starship for years and after hours of working on other aspects to suddenly be stumped by these small differences between platforms can be very frustrating.
to the OP:
answer to your first question comes in two parts.
a) use 'make -j# otapackage' will generate a zip that is flashable in custom recovery.
b) if you plan on adding other files after the zip is made, you will need this info here:
https://github.com/android/platform_build/commit/26e6619c37e294fe2ee63aaa759e0ac861775ce8
There are some modifications needed to generate the OG zip files instead of the new "block" format.
Google hasn't released the 5.0.1 image for the N5 but that doesn't mean you can't build it and install it yourself. I'm running it and it seems okay to me so far although I'm hardly an expert.
simms22 said:
op.. this section is only for developers, to get work done. if you have questions, they belong in the q&a section. you arent new, you should know this. again, this section is only for developers, mot for the normal xda folk to post questions. you have a q&a section just for asking questions. please, ask a mod to move your thread there.
Click to expand...
Click to collapse
I am building a customized AOSP Rom I am interested in sharing so was looking for help or direction in creating an update zip that can be flashed in a custom recovery like TWRP. I am not used to compiling AOSP and with the help of know.patience in the first reply am now able to compile an update.zip I can flash in TWRP but in doing so it also replaces TWRP with the Stock recovery. I have still been using the .img files to flash personally but am still trying to figure out how to solve the recovery replacement issue. I still have other features I am adding and testing before I would like to post my work but before I get to that point I still need to figure out my recovery replacement issue. Maybe using the words personal use may have been confusing but at the moment until ready I have only been using my work personally but would like to at some point post and share. I also have work that is not AOSP based I am sharing in the Android Development section but I have been building CM and other source based Roms and sharing for years. This is the first device I have been able to build AOSP and still have a few things to figure out before sharing any of my AOSP based work. I am otherwise not sure why you think these are questions for general Q&A.
I started this thread in Android Development as there was only about 4 posts in this section and I see many AOSP based Roms in Android Development who's developers obviously know the answers to my questions so tried to get away posting there in hope one of these developers could help or like in the first response point me in the direction of a commit before the thread was moved by a mod into this section. Do you think someone in the general Q&A section is better equipped to help answer questions about compiling an AOSP based Rom in the form of an update.zip that can be flashed in TWRP without also replacing TWRP with the Stock recovery?? Would also be nice knowing what changes in the code need to be made in compiling an old style update.zip that does not use the new block format. This would be a bonus but overall not %100 needed as instead of moving files around after the code has been compiled have added init.d support and first have all the files I want moved into a staging directory and then form an init,d bash script to move the files during first boot and remove those that are not needed like this example I used in my CM based version of the Rom I am trying to update for AOSP for 5.0.
https://github.com/Starship-Android/android_device_starship-common/blob/cm-11.0/app-update
https://github.com/Starship-Android/android_device_starship-common/blob/cm-11.0/cleanup
I must seriously be underestimating the knowledge and in general the types of questions being asked and answered in the general Q&A section.
Honestly if not for the amount of times thanked I would think this comment was not so much about helping or community but more about someone trying to puff themselves up by trying to appear important by making decisions about what questions are worthy of being asked but judging by the number of times they have been helpful I am thinking its either a case of not reading or understanding the question being asked or my own inability to express my questions in the proper manor. Either way its definitely not about taking up resources in a section with less than 10 total posts. The frustrating part as a community as I like to believe we are all in is that why I worked on other parts in updating my Rom had expected that at least more than one developer out of all the AOSP based Roms posted in the development section would have helped me with this one part. Its not like I am asking how to be a developer just a resource to help with two simple things I am sure I could have figured out and will most likely still figure out without any help. Overall my thoughts behind posting this question was that why I am working to figure out something a bit more time consuming at least more than one person would be helpful enough to copy and past a commit.
XDA is weird in that with other devices all the developers would join a team and start a shared group of repository’s for one another to use in trying to make the best possible experience and options for everyone. For example in the op I posted an example of hours of work I did showing what libraries are needed by one another just so others could use it also in trying to port as much as possible for in that case the Galaxy Mini. Then with other devices like seems to be the case with the N5 its all about competition and what I am starting to call the smartest person in the room syndrome. Its just a shame there are only 5 maybe 6 threads posted in this section and I think that says allot about the community in general. So many good things could come about if we just tried to be helpful and pull as much knowledge together as we could. Anyhow think its time for ending this rant.
chairshot215 said:
compiling an AOSP based Rom in the form of an update.zip that can be flashed in TWRP without also replacing TWRP with the Stock recovery?? Would also be nice knowing what changes in the code need to be made in compiling an old style update.zip that does not use the new block format.
Click to expand...
Click to collapse
To get rid of the block-based zip format: https://github.com/Lethargy/android_build/commit/4d458300d935a3a9d893a590286cb578dcf54db2
You'll also want to make sure you have this commit so it doesn't flash awfully slow in recovery (8~ minutes, but only around 1-2 minutes with this commit): https://github.com/Lethargy/android_system_extras/commit/52f8d5fc3edfacd112827d0a41516c1dc5f4a468
This one isn't required but you may as well: https://github.com/Lethargy/android_build/commit/242be9ae4f05e3cb1d39d635cac7147ff904700c
For getting rid of the AOSP recovery: https://github.com/Lethargy/android_build/commit/48521e167c642db76c9d4f52b1c63f9abc7f707f then https://github.com/Lethargy/android_build/commit/1d9224bd45ef2b4f5601a157de2bfe3bb1c95558
Lethargy said:
To get rid of the block-based zip format: https://github.com/Lethargy/android_build/commit/4d458300d935a3a9d893a590286cb578dcf54db2
You'll also want to make sure you have this commit so it doesn't flash awfully slow in recovery (8~ minutes, but only around 1-2 minutes with this commit): https://github.com/Lethargy/android_system_extras/commit/52f8d5fc3edfacd112827d0a41516c1dc5f4a468
This one isn't required but you may as well: https://github.com/Lethargy/android_build/commit/242be9ae4f05e3cb1d39d635cac7147ff904700c
For getting rid of the AOSP recovery: https://github.com/Lethargy/android_build/commit/48521e167c642db76c9d4f52b1c63f9abc7f707f then https://github.com/Lethargy/android_build/commit/1d9224bd45ef2b4f5601a157de2bfe3bb1c95558
Click to expand...
Click to collapse
Thank you this is well beyond what I was looking for and don’t worry I make it a point not to send out PM's with questions that can be helpful for others as well. Otherwise would have blown up the AOSP Rom posters in development but thanks for the information.
chairshot215 said:
.. and don’t worry I make it a point not to send out PM's with questions that can be helpful for others as well..
Click to expand...
Click to collapse
If you mean "I'll probably ignore you if you try asking for support over PM.", that's part of my forum signature.
If you need anything else feel free to @mention me in a thread, though.
I reworked the Op to avoid confusion as Mods have been moving the thread around into different sections. I personalty believe these questions are more geared towered development than general Q&A but at least at the moment I appear to be wrong about that. Never know though as in the past one day one of the mods may decide to move the thread back into its intended location but until then I guess these topics will be of better use to general users than developers.
chairshot215 said:
I reworked the Op to avoid confusion as Mods have been moving the thread around into different sections. I personalty believe these questions are more geared towered development than general Q&A but at least at the moment I appear to be wrong about that. Never know though as in the past one day one of the mods may decide to move the thread back into its intended location but until then I guess these topics will be of better use to general users than developers.
Click to expand...
Click to collapse
You should include the other commit (https://github.com/Lethargy/android_build/commit/1d9224bd45ef2b4f5601a157de2bfe3bb1c95558) which fixes building since the first one results in "IndentationError: unexpected indent".
Lethargy said:
You should include the other commit (https://github.com/Lethargy/android_build/commit/1d9224bd45ef2b4f5601a157de2bfe3bb1c95558) which fixes building since the first one results in "IndentationError: unexpected indent".
Click to expand...
Click to collapse
Thanks for the heads up, when testing these I also cherry picked a few other things that looked related. Have to double check but may have forked the repository’s from you so would receive credit if anyone decided to look over my repository’s. Well overall my personal Github has been pretty bare as in the past most work was done on more obscure Virgin Mobile devices with only a few developers so we would pretty much create an organization for all the developers to use.
https://github.com/MTDEV-CM7
https://github.com/MTDEV-CM10
https://github.com/vmobi-triumph
https://github.com/MTDEV-KERNEL
https://github.com/MTDEV-MIUIv4
https://github.com/MTCM9
https://github.com/MTCM10
https://github.com/HTCCM9
https://github.com/HTCCM10
https://github.com/HTCStarShip
https://github.com/HTCUbuntu
https://github.com/vmobi-shooter
https://github.com/vmobi-gogh
These days have been keeping everything under Starship-Android.
https://github.com/Starship-Android
Have 2 other members listed who I had worked with in the past but has otherwise been a solo organization with one of the other members who decided on going with the Moto X and Verizon over the N5 and showed little interest in his 2012 version of the N7 as it was intended for being a Nexus only device line up and the second being my Kernel Guru from a few devices back who mainly joined to help me out with a few things but ultimately what I am getting around to is this is the first time working %100 solo. Have to say without having anyone to bounce off ideas and share findings with things definitely move much slower and take a bit of getting used to. Is also the reason for starting threads like this. Most of this stuff looking in the developer section appeared to be pretty common knowledge but having never worked from pure AOSP before was slowing down other development for about a week just to figure out what seemed like half the community had already known and with what probably took at the most 5 or 10 minutes of copying and pasting commits probably saved me a weekend of sifting through github and testing. I hope by creating a thread like this will be able to do the same for others.
Hi guys,
Anyone manage to fix RIL problems with master branch?
I also build AOSP roms so for sure i will hangout here
Sent from my AOSP on HammerHead using XDA Free mobile app
malcho said:
Hi guys,
Anyone manage to fix RIL problems with master branch?
I also build AOSP roms so for sure i will hangout here
Sent from my AOSP on HammerHead using XDA Free mobile app
Click to expand...
Click to collapse
Never tried.
ODEXED
i am successfully build cm12 with fully odexed. now i like to odex some prebuilt apk also but LOCAL_DEX_PREOPT=true not odexing prebuilt apk. can somebody help me? already DEX_PREOPT=true working fine.
soorajj said:
i am successfully build cm12 with fully odexed. now i like to odex some prebuilt apk also but LOCAL_DEX_PREOPT=true not odexing prebuilt apk. can somebody help me? already DEX_PREOPT=true working fine.
Click to expand...
Click to collapse
Why do you need to odex a prebuilt apk?
Not sure if what you want is even possible.
But if odexing your prebuilt apk is necessary then why not odex it then include the .odex with the prebuilt?
Lethargy said:
Why do you need to odex a prebuilt apk?
Not sure if what you want is even possible.
But if odexing your prebuilt apk is necessary then why not odex it then include the .odex with the prebuilt?
Click to expand...
Click to collapse
suppose i want to odex gapps. how to?
malcho said:
Hi guys,
Anyone manage to fix RIL problems with master branch?
I also build AOSP roms so for sure i will hangout here
Sent from my AOSP on HammerHead using XDA Free mobile app
Click to expand...
Click to collapse
Nothing so far, I downloaded the master and 5.0.2_r1 branches and have loaded both in meld for looking over differences but have not yet identified from the dif between the 2 branches that is responsible for ril working in release branch but not master. Still have allot to look over though still. Still have not found a decent explanation of the master branch to know if its recommended to build from but still just for Knowledge sake am interested in knowing. At first thought maybe apn's but not so sure with baseband also listed as unknown from my Master branch builds.
chairshot215 said:
Nothing so far, I downloaded the master and 5.0.2_r1 branches and have loaded both in meld for looking over differences but have not yet identified from the dif between the 2 branches that is responsible for ril working in release branch but not master. Still have allot to look over though still. Still have not found a decent explanation of the master branch to know if its recommended to build from but still just for Knowledge sake am interested in knowing. At first thought maybe apn's but not so sure with baseband also listed as unknown from my Master branch builds.
Click to expand...
Click to collapse
As far as i know all the patches goes to master branch then from this branch ,if they are ok,is distributed to lower branches.I also didn't find info why is named as 5.0.50.50.I will try to investigate this ril problem
malcho said:
As far as i know all the patches goes to master branch then from this branch ,if they are ok,is distributed to lower branches.I also didn't find info why is named as 5.0.50.50.I will try to investigate this ril problem
Click to expand...
Click to collapse
Thanks will definitely update the Op with any findings. Was very surprised to find the thread again as it has now been moved 4 times by 4 different Mods, some bounce it to general Q&A and then is bounced back here by another. I understand its not comprised of the most advanced development topics but with that said is still way more advanced than the topics being discussed by general users over in the general Q&A section. I had just thought it would be a nice one stop place for learning the basics of AOSP development. With the constant moving and scolding messages being received one would think the threads very existence is up there with crossing the streams and threatens the existence of Android development.
@chairshot215 Thank you for starting this thread. Thank you @Lethargy for all of your insight. I like to do my own perosnal builds every once in a while for my nexus devices. What I have observed over the years is that the Master Branch will sometimes have funky version numbers like you have described. One thing to consider is what @malcho mentioned. If all commits indeed go there first before the respective branches(although this may not entirely be the case), then it is likely that some things may be broken in the master branch from time to time, hence the ril problem. I think with the galaxy nexus I ended up running into issues from time to time with the master branch, and from there learned to build for specific branches/tags. For instance, there are times when items within a specific branch will be ahead of master in some areas and behind it in others, as in this link to platform_build for lollipop release https://github.com/android/platform_build/tree/lollipop-release. So with that, it is probably in our best interests to just use specific branches.
Milly7 said:
@chairshot215 Thank you for starting this thread. Thank you @Lethargy for all of your insight. I like to do my own perosnal builds every once in a while for my nexus devices. What I have observed over the years is that the Master Branch will sometimes have funky version numbers like you have described. One thing to consider is what @malcho mentioned. If all commits indeed go there first before the respective branches(although this may not entirely be the case), then it is likely that some things may be broken in the master branch from time to time, hence the ril problem. I think with the galaxy nexus I ended up running into issues from time to time with the master branch, and from there learned to build for specific branches/tags. For instance, there are times when items within a specific branch will be ahead of master in some areas and behind it in others, as in this link to platform_build for lollipop release https://github.com/android/platform_build/tree/lollipop-release. So with that, it is probably in our best interests to just use specific branches.
Click to expand...
Click to collapse
Thanks for the response and have definitely learned its better building from branches with a release tag. Still very curious why and how the branches are structured so thanks for the explanations.
Way totally off topic for the thread but landed a brand new SSD and decided to install everything fresh. After everything was set back up and wanted to start building I ran my usual,
-j'grep 'processor' /proc/cpuinfo | wc -l'
a very old habit before fully understanding what number to use after -j so used grep to figure it out based on Googles recommendation. The command did not work so removed the grep and just made it -j4 but also with 0 success. At first just figued I missed somthing setting everything back up and "make" is just not working but wrong again as running "make" command without -j of any number works just fine.
Also tried this with CM12 as I am doing 2 versions of my Starship Rom. One from AOSP and one using CM. Figured AOSP would be special for Nexus users why also having a version for CM I can make most changes by adding a Starship Device Tree could easily port the Rom to any device running CM supported or not.
https://github.com/Starship-Android/android_device_starship-common/tree/cm-12.0
Also found why compiling CM that -j also results in an error
Invalid lunch combo: cm_hammerhead--j4
No such item in brunch menu. Try 'breakfast'
So far have not found anything using the Google Box so figured may as well ask. If have not figured out by now I have no shame in asking questions. Oddly enough that is for things that are probably relatively simple. Took a better part of a week figuring out how to start CM using the Now Launcher and setting up init.d bash scripts for moving around and replacing libs after learning the Gapps package includes libs that will not work so the solution needed to be that the CM Gapps package libs needed to be replaced with either stock or libs pulled after installing the Now Launcher from the Play Store after flashing Gapps and the Rom staring. Also then what if user updates and wipes the system partition after the new and updated llibs have been moved into place. Anyhow point of story is things like this I will just figure out without bothering anyone but for the cant believe I need to stop what I am working on to figure out something most likely very simple and can be answered with very little time spent I have no shame in just asking. Not that someone else’s time is less important but like I have mentioned before is frustrating just after spending hours or days figuring out something asked in dozens of threads is just frustrating getting caught up or loosing momentum and thought processes over something so simple there are little resources available. Also I assume most devs have the same experience when you have an idea or thought behind resolving an issue that once you stop and change direction it just sometimes never comes back and that short time you had I guess can be called an epiphany is gone once going back. Otherwise thats how I justify asking dumb ars questions.
Hey there interweb!
This thread is meant as a general area to organise the mess of files scattered across the internet for the original Wi-Fi version of the Samsung Galaxy Tab S 8.4.
This Google Drive folder contains the following:
Stock Odin TAR/MD5 firmware files
ROMs, and their accompanying files + install instructions that have been confirmed to boot,
Kernels that have been confirmed to boot,
Useful mods which are confirmed to work and add genuine capability to your device;
and anything else which I think is useful to those wishing to mod their Tab S.
Link:
androiddev - Google Drive
drive.google.com
If you know of any files which you think should be included, and are not already here, please feel free to either reply to this thread or DM me. If you want any assistance at all, please feel free to do the same, and I will try to assist you to the best of my ability.
All the best,
Cessna
I must reiterate, as always, that although I have tested each of these mods, I am not responsible for bricks, loss of data, or permanent damage to your device. You yourself are choosing to make these modifications, and although they have my quality assurance, I can not guarantee their 100% safety. Just because they worked on my device, does not necessarily mean they will work on yours.
CessnaBroon said:
Hey there interweb!
This thread is meant as a general area to organise the mess of files scattered across the internet for the original Wi-Fi version of the Samsung Galaxy Tab S 8.4.
This Google Drive folder contains the following:
Stock Odin TAR/MD5 firmware files
ROMs, and their accompanying files + install instructions that have been confirmed to boot,
Kernels that have been confirmed to boot,
Useful mods which are confirmed to work and add genuine capability to your device;
and anything else which I think is useful to those wishing to mod their Tab S.
Link:
klimtwifi - Google Drive
drive.google.com
If you know of any files which you think should be included, and are not already here, please feel free to either reply to this thread or DM me. If you want any assistance at all, please feel free to do the same, and I will try to assist you to the best of my ability.
All the best,
Cessna
I must reiterate, as always, that although I have tested each of these mods, I am not responsible for bricks, loss of data, or permanent damage to your device. You yourself are choosing to make these modifications, and although they have my quality assurance, I can not guarantee their 100% safety. Just because they worked on my device, does not necessarily mean they will work on yours.
Click to expand...
Click to collapse
Good idea to gather everything on one place and make the mess a bit easier to handle..
I helped myself with the TWRP and the LOS17, much obliged. Don't really need help otherwise.
That is, unless you know why my t705 (i have one of those too) keeps messing with me and losing charge even when switched off...
prkfsz said:
Good idea to gather everything on one place and make the mess a bit easier to handle..
I helped myself with the TWRP and the LOS17, much obliged. Don't really need help otherwise.
That is, unless you know why my t705 (i have one of those too) keeps messing with me and losing charge even when switched off...
Click to expand...
Click to collapse
I'll be honest, my Tab s battery has decreased to about 2100 mAh from 4900 so it's probably just age I'm afraid. If you use it more, you could do a battery transplant, but I don't have ROMs for klimtlte. Thanks for using my mirror
CessnaBroon said:
I'll be honest, my Tab s battery has decreased to about 2100 mAh from 4900 so it's probably just age I'm afraid. If you use it more, you could do a battery transplant, but I don't have ROMs for klimtlte. Thanks for using my mirror
Click to expand...
Click to collapse
Not battery. Changed it. And the same battery works fine on T700 and does not lose charge when off. Tried flashing other ROM as well, but i can't find solution.
prkfsz said:
Not battery. Changed it. And the same battery works fine on T700 and does not lose charge when off. Tried flashing other ROM as well, but i can't find solution.
Click to expand...
Click to collapse
That's odd. Have you tried flashing a custom kernel in TWRP? If not, I'll upload one to the Google Drive in the /androiddev/klimtlte folder. Will create it soon, along with instructions.
CessnaBroon said:
That's odd. Have you tried flashing a custom kernel in TWRP? If not, I'll upload one to the Google Drive in the /androiddev/klimtlte folder. Will create it soon, along with instructions.
Click to expand...
Click to collapse
Odd indeed. And really frustrating. :-/
Have not tried with custom kernel but can of course do that, if it's simple. But, like i said - it's a T705, you mean there is one already made or are you just going to make one on a coffee break?
prkfsz said:
Odd indeed. And really frustrating. :-/
Have not tried with custom kernel but can of course do that, if it's simple. But, like i said - it's a T705, you mean there is one already made or are you just going to make one on a coffee break?
Click to expand...
Click to collapse
There's one already made I think. I'll see if I can find one and alert you when it's up. Obvs I can't do a check for safety without the hardware so make a full backup of the boot partition just in case. I'll make sure to find one with good reviews
CessnaBroon said:
There's one already made I think. I'll see if I can find one and alert you when it's up. Obvs I can't do a check for safety without the hardware so make a full backup of the boot partition just in case. I'll make sure to find one with good reviews
Click to expand...
Click to collapse
Not sure if i have the time to do it tonight or this weekend, but i will try as soon as i get the chance.
Very gratefull for all the help. I actually have two of them, with the same behaviour and i almost written them off, so..
prkfsz said:
Not sure if i have the time to do it tonight or this weekend, but i will try as soon as i get the chance.
Very gratefull for all the help. I actually have two of them, with the same behaviour and i almost written them off, so..
Click to expand...
Click to collapse
kernel - Google Drive
drive.google.com
Shouldn't take more than 5 minutes. Good luck!
CessnaBroon said:
kernel - Google Drive
drive.google.com
Shouldn't take more than 5 minutes. Good luck!
Click to expand...
Click to collapse
Thank you kindly, sir.
Will try right away, but can't really see if had any effect untill morning.
I thought first to ask you if it is possible to use this on stock too, but then it struck me how stupid idea that is, since it's not the same Android version. Because one of them is on stock and behaving the same way. Which basically leads me to believe that it actually is a hardware fault...
prkfsz said:
Thank you kindly, sir.
Will try right away, but can't really see if had any effect untill morning.
I thought first to ask you if it is possible to use this on stock too, but then it struck me how stupid idea that is, since it's not the same Android version. Because one of them is on stock and behaving the same way. Which basically leads me to believe that it actually is a hardware fault...
Click to expand...
Click to collapse
This should work on stock marshmallow too. I will give it a go and get back to you.
Thank you kindly!
lafinjack said:
Thank you kindly!
Click to expand...
Click to collapse
You're very welcome!
CessnaBroon said:
This should work on stock marshmallow too. I will give it a go and get back to you.
Click to expand...
Click to collapse
Sorry for delay in answering..
Unfortunatelly the error is still present. Like i said, probably a software issue.
Bit thanx anuway!
Thanks for creating a section specifically for the SM-T700! I hope that I can get some practical help on moving forward
On my post here (https://forum.xda-developers.com/t/...d-but-ok-with-resurrection-remix-why.4332701/) I describe my attempt to install a variation of LineageOS 17.1 on my device -- always running into 'E1001'. I eventually settled on an older Resurrection Remix, since someone mentioned that it would ultimately make it possible to move to LineageOS (I have not tried that yet).
Here are some of my questions:
1) In a much larger/older thread (https://forum.xda-developers.com/t/...t700-sm-t705-sm-t800-sm-t800-sm-p600.4270943/) the first step is "Flash latest official Samsung Firmware with ODIN". Is this even relevant to me?
2) In preparation for successfully installing LineageOS, what TWRP clearing/formatting options should I be using? On a completely different device, the instructions were to delete *everything*. Could my wrong choices when doing this for my SM-T700 have contributed to my failures?
3) Now that I (currently) have Resurrection Remix on my SM-T700, can I expect -- with the binaries mentioned in this new subgroup -- to be able to install LineageOS 17.1 *without* running into the 'E1001' problem?
Thanks for any help!
darethehair said:
Thanks for creating a section specifically for the SM-T700! I hope that I can get some practical help on moving forward
On my post here (https://forum.xda-developers.com/t/...d-but-ok-with-resurrection-remix-why.4332701/) I describe my attempt to install a variation of LineageOS 17.1 on my device -- always running into 'E1001'. I eventually settled on an older Resurrection Remix, since someone mentioned that it would ultimately make it possible to move to LineageOS (I have not tried that yet).
Here are some of my questions:
1) In a much larger/older thread (https://forum.xda-developers.com/t/...t700-sm-t705-sm-t800-sm-t800-sm-p600.4270943/) the first step is "Flash latest official Samsung Firmware with ODIN". Is this even relevant to me?
2) In preparation for successfully installing LineageOS, what TWRP clearing/formatting options should I be using? On a completely different device, the instructions were to delete *everything*. Could my wrong choices when doing this for my SM-T700 have contributed to my failures?
3) Now that I (currently) have Resurrection Remix on my SM-T700, can I expect -- with the binaries mentioned in this new subgroup -- to be able to install LineageOS 17.1 *without* running into the 'E1001' problem?
Thanks for any help!
Click to expand...
Click to collapse
Hey there! I'll take a closer look once I'm home. Speak to you then
darethehair said:
Thanks for creating a section specifically for the SM-T700! I hope that I can get some practical help on moving forward
On my post here (https://forum.xda-developers.com/t/...d-but-ok-with-resurrection-remix-why.4332701/) I describe my attempt to install a variation of LineageOS 17.1 on my device -- always running into 'E1001'. I eventually settled on an older Resurrection Remix, since someone mentioned that it would ultimately make it possible to move to LineageOS (I have not tried that yet).
Here are some of my questions:
1) In a much larger/older thread (https://forum.xda-developers.com/t/...t700-sm-t705-sm-t800-sm-t800-sm-p600.4270943/) the first step is "Flash latest official Samsung Firmware with ODIN". Is this even relevant to me?
2) In preparation for successfully installing LineageOS, what TWRP clearing/formatting options should I be using? On a completely different device, the instructions were to delete *everything*. Could my wrong choices when doing this for my SM-T700 have contributed to my failures?
3) Now that I (currently) have Resurrection Remix on my SM-T700, can I expect -- with the binaries mentioned in this new subgroup -- to be able to install LineageOS 17.1 *without* running into the 'E1001' problem?
Thanks for any help!
Click to expand...
Click to collapse
Hey! Sorry for the delay. You should flash the latest firmware (it's on updato.com) Using Odin, and then twrp with Odin, and then the custom ROM from twrp, wiping data dalvik and cache before rebooting. Other two are in the mirror.
CessnaBroon said:
Hey! Sorry for the delay. You should flash the latest firmware (it's on updato.com) Using Odin, and then twrp with Odin, and then the custom ROM from twrp, wiping data dalvik and cache before rebooting. Other two are in the mirror.
Click to expand...
Click to collapse
Just an FYI...I was reluctant to start everything over again with Odin and latest Samsung firmware, so I opted to take a chance and merely 'adb push' the LineageOS and GApps that you have on your Google drive (along with some cache erasures as you suggested) and everything seemed to upgrade properly from Resurrection Remix to LineageOS 17.1
A few minor problems so far: camera doesn't work, and initial signon to the tablet with a PIN doesn't work so well (seems to take multiple attempts). In any case, now running Android 10!
These were issues that I faced too - I never found a way to fix them. Neither did the original Dev, but apparently updating to the latest webview fixes chrome crashes. PIN you need to wait 30seconds after boot. Camera works only with clean install and even then sometimes doesn't work.
Hope this helps,
Cessna
I was trying to install TWRP but after reboot when I go to the Recovery mode there is no TWRP. I installed the LOS on my Tab Pro 8.4 and wanted to install LOS on Tab S 8.4 but can't flash the TWRP. Any ideas what I'm doing wrong?
Thanks