Moto X Pro system.zip - Nexus 6 Q&A, Help & Troubleshooting

Since so many people are interested in Motorola's system ,I decided to ask help here to get a flashable .zip of the system .
Here is the link to the system files https://docs.google.com/file/d/0By2Nq4_gBuTQYUhmSXlBMDZPZFE/edit?usp=docslist_api
We only need an updater-script to get these files flashed .
I hope someone helps us to make this possible
In short terms :
We have access to the Motorola's Moto X Pro system dump .And since it is way more advanced in features ,we want to "PORT" it to our Nexus 6 since both devices share identical Hardwares .What we have is the whole System Dump ,system files ,boot.img even bootloader ,but we need to make the ROM flash-able for our device ,(since I personally don't feel safe flashing a factory image which is actually made for another device ,let it be same or identical ,it's still not safe ), so to make it flash-able we need update-script , which I have no enough knowledge to make one. So if someone can help us, it'd be great
If needed ,here is the Factory Image of the Moto X Pro :
https://docs.google.com/file/d/0By2Nq4_gBuTQMzh6OVNhUTdpVms/edit?usp=docslist_api
{
"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"
}
Nexus 6 Specifications
___________________
Moto X Pro Specifications
Edit : The Moto X Pro's codename is also Shamu ,as Nexus 6 ,just a "_retcn" added to the end . Shamu_retcn ,Shamu-Nexus 6 , ret-Retail , cn-China (not sure what ret means , but the only explanation I can give is retail)

Is there not a moto x pro forum m

rootSU said:
Is there not a moto x pro forum m
Click to expand...
Click to collapse
Dunno ,but what if there was .We want to make this ROM install-able on Nexus 6 ,not on Moto X Pro .

blinqipa said:
Dunno ,but what if there was .We want to make this ROM install-able on Nexus 6 ,not on Moto X Pro .
Click to expand...
Click to collapse
Perhaps then, you could make that more clear in your first post.
Oh and has anyone actually proven it will run without bricking an n6 yet? It has slightly different hardware so its a brave man who flashes untested

rootSU said:
Perhaps then, you could make that more clear in your first post.
Oh and has anyone actually proven it will run without bricking an n6 yet? It has slightly different hardware so its a brave man who flashes untested
Click to expand...
Click to collapse
From what we know ,both devices share "IDENTICAL ,COMPLETELY IDENTICAL" (sorry for caps) hardwares ,besides moto x pro has one thing extra which is I think IR sensor .That's why we want to make it flash-able ,so we can test it .Either way we have access to the factory image ,we could flash it all away ,but no one feels safe .

Set up dsixda's kitchen which can be found here on xda and drop the images in the kitchen and convert them from the images they are in to directories where you can then either leave it odexed or you can deodex it and then wrap it back up in to a zip... The kitchen will create the updater script for you... Its a very generic one but it will create one.. You mag have to add some lines for certain things but that isn't difficult at all..... You can also use a Nexus 6 updater script and if it fails while flashing the recovery will tell you why it failed and you go back in and fix it and try again!!!! Let me know if you need help, I can turn the dump in to a flashable zip if you really want to try this... I don't see why you would want to though if the only difference is an IR blaster/sensor... That is physical hardware something the Nexus 6 is not equipped with so the code built in to the ROM would be useless....

blinqipa said:
Since so many people are interested in Motorola's system ,I decided to ask help here to get a flashable .zip of the system .
Here is the link to the system files https://docs.google.com/file/d/0By2Nq4_gBuTQYUhmSXlBMDZPZFE/edit?usp=docslist_api
We only need an updater-script to get these files flashed .
I hope someone helps us to make this possible
In short terms :
We have access to the Motorola's Moto X Pro system dump .And since it is way more advanced in features ,we want to "PORT" it to our Nexus 6 since both devices share identical Hardwares .What we have is the whole System Dump ,system files ,boot.img even bootloader ,but we need to make the ROM flash-able for our device ,(since I personally don't feel safe flashing a factory image which is actually made for another device ,let it be same or identical ,it's still not safe ), so to make it flash-able we need update-script , which I have no enough knowledge to make one. So if someone can help us, it'd be great
If needed ,here is the Factory Image of the Moto X Pro :
https://docs.google.com/file/d/0By2Nq4_gBuTQMzh6OVNhUTdpVms/edit?usp=docslist_api
Click to expand...
Click to collapse
Working on this now.
I can't verify anything will work, and will need a tester tomorrow.

Murrda said:
Set up dsixda's kitchen which can be found here on xda and drop the images in the kitchen and convert them from the images they are in to directories where you can then either leave it odexed or you can deodex it and then wrap it back up in to a zip... The kitchen will create the updater script for you... Its a very generic one but it will create one.. You mag have to add some lines for certain things but that isn't difficult at all..... You can also use a Nexus 6 updater script and if it fails while flashing the recovery will tell you why it failed and you go back in and fix it and try again!!!! Let me know if you need help, I can turn the dump in to a flashable zip if you really want to try this... I don't see why you would want to though if the only difference is an IR blaster/sensor... That is physical hardware something the Nexus 6 is not equipped with so the code built in to the ROM would be useless....
Click to expand...
Click to collapse
It's not that I want the IR sensor ,I want the whole system because it has great useful features.Between thank you so much ,will try to make a flashable zip with dsixda's kitches asap .

Murrda said:
Set up dsixda's kitchen which can be found here on xda and drop the images in the kitchen and convert them from the images they are in to directories where you can then either leave it odexed or you can deodex it and then wrap it back up in to a zip... The kitchen will create the updater script for you... Its a very generic one but it will create one.. You mag have to add some lines for certain things but that isn't difficult at all..... You can also use a Nexus 6 updater script and if it fails while flashing the recovery will tell you why it failed and you go back in and fix it and try again!!!! Let me know if you need help, I can turn the dump in to a flashable zip if you really want to try this... I don't see why you would want to though if the only difference is an IR blaster/sensor... That is physical hardware something the Nexus 6 is not equipped with so the code built in to the ROM would be useless....
Click to expand...
Click to collapse
ALL the Motorola proprietary apps (Moto Assist, Moto Voice, Moto Actions, etc.) are supposed to be on the Moto X Pro, and there are many Nexus 6 owners who really want these apps to make the N6 the whole package.

We dont even need a flashable ROM. Ideally we would figure out how to install just the Moto Apps. We already have the Moto Apps apks, so all we need to figure out is which system/bin or system/lib or whatever files they depend on to run. How do you determine every other file in an OS that a file uses when running?
For example the Nexus 6 uses bootanimation.zip containing a bunch of png images in folders, strung together as an animation, whereas the Moto X Pro uses actual video files in its bootanimation.zip. Getting the Moto X Pro bootanimation to work on the Nexus 6 only required copying over /system/bin/bootanimation along with the bootanimation.zip.
How do we determine what other files the Moto apps depend on? Does it just involve decompiling and looking through source code? It wouldnt be hard to make a flashable zip of just the apps and necessary files if we knew what those were.
Hmm this thread has some useful info but it sounds like the best way to start would be to copy over the Moto X Pros moto apps apks to your Nexus 6, start recording a logcat, try to run the apps and when they fail, stop the logcat, look through it for errors relating to unknown reference/nullpointer exception and the logcat will have info on what the apk is trying to call that it cant find.

KnifeSkills said:
We dont even need a flashable ROM. Ideally we would figure out how to install just the Moto Apps. We already have the Moto Apps apks, so all we need to figure out is which system/bin or system/lib or whatever files they depend on to run. How do you determine every other file in an OS that a file uses when running?
For example the Nexus 6 uses bootanimation.zip containing a bunch of png images in folders, strung together as an animation, whereas the Moto X Pro uses actual video files in its bootanimation.zip. Getting the Moto X Pro bootanimation to work on the Nexus 6 only required copying over /system/bin/bootanimation along with the bootanimation.zip.
How do we determine what other files the Moto apps depend on? Does it just involve decompiling and looking through source code? It wouldnt be hard to make a flashable zip of just the apps and necessary files if we knew what those were.
Hmm this thread has some useful info but it sounds like the best way to start would be to copy over the Moto X Pros moto apps apks to your Nexus 6, start recording a logcat, try to run the apps and when they fail, stop the logcat, look through it for errors relating to unknown reference/nullpointer exception and the logcat will have info on what the apk is trying to call that it cant find.
Click to expand...
Click to collapse
Or ,another great thing ,is to make a flashable .zip of whole System .I know this is just too much of flashing ,but it's safer and it's way easier to replace .Then if it works ,we can make a flashable .zip of only NEEDED files ,libraries ,bin files etc.

KnifeSkills said:
We dont even need a flashable ROM. Ideally we would figure out how to install just the Moto Apps. We already have the Moto Apps apks, so all we need to figure out is which system/bin or system/lib or whatever files they depend on to run. How do you determine every other file in an OS that a file uses when running?
For example the Nexus 6 uses bootanimation.zip containing a bunch of png images in folders, strung together as an animation, whereas the Moto X Pro uses actual video files in its bootanimation.zip. Getting the Moto X Pro bootanimation to work on the Nexus 6 only required copying over /system/bin/bootanimation along with the bootanimation.zip.
How do we determine what other files the Moto apps depend on? Does it just involve decompiling and looking through source code? It wouldnt be hard to make a flashable zip of just the apps and necessary files if we knew what those were.
Hmm this thread has some useful info but it sounds like the best way to start would be to copy over the Moto X Pros moto apps apks to your Nexus 6, start recording a logcat, try to run the apps and when they fail, stop the logcat, look through it for errors relating to unknown reference/nullpointer exception and the logcat will have info on what the apk is trying to call that it cant find.
Click to expand...
Click to collapse
We need to deodex first , but I keep getting errors ..
---------- Post added at 06:15 AM ---------- Previous post was at 06:13 AM ----------
Murrda said:
Set up dsixda's kitchen which can be found here on xda and drop the images in the kitchen and convert them from the images they are in to directories where you can then either leave it odexed or you can deodex it and then wrap it back up in to a zip... The kitchen will create the updater script for you... Its a very generic one but it will create one.. You mag have to add some lines for certain things but that isn't difficult at all..... You can also use a Nexus 6 updater script and if it fails while flashing the recovery will tell you why it failed and you go back in and fix it and try again!!!! Let me know if you need help, I can turn the dump in to a flashable zip if you really want to try this... I don't see why you would want to though if the only difference is an IR blaster/sensor... That is physical hardware something the Nexus 6 is not equipped with so the code built in to the ROM would be useless....
Click to expand...
Click to collapse
I've made a flashable zip and flashed it but I keep getting symlink errors really want just flash via mfastboot but afraid of bricking on the process

Omar1c said:
We need to deodex first , but I keep getting errors ..
---------- Post added at 06:15 AM ---------- Previous post was at 06:13 AM ----------
I've made a flashable zip and flashed it but I keep getting symlink errors really want just flash via mfastboot but afraid of bricking on the process
Click to expand...
Click to collapse
All I can say ,the bootloader flashing can result in a "soft brick" which renders the phone unusable ,and it directly gives you QHUSB BULK mode .That's caused by bootloader downgrading from new (5.1) to the old one (5.0.2) .

blinqipa said:
All I can say ,the bootloader flashing can result in a "soft brick" which renders the phone unusable ,and it directly gives you QHUSB BULK mode .That's caused by bootloader downgrading from new (5.1) to the old one (5.0.2) .
Click to expand...
Click to collapse
"There's an app for that" > http://forum.xda-developers.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518

cam30era said:
"There's an app for that" > http://forum.xda-developers.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518
Click to expand...
Click to collapse
App? Perhaps you mean , guide to fix .But why put yourself on a "recoverable situation" which is much of hard to fix for non-advanced users .

blinqipa said:
App? Perhaps you mean , guide to fix .
Click to expand...
Click to collapse
Yes, it was meant as a joke...

cam30era said:
Yes, it was meant as a joke...
Click to expand...
Click to collapse
LOL ,my sense of humor sometimes fails to the ground XD .Enough out of topic discussion XD have you tried getting a working .zip ? Or has anyone tried that? Seems like dsixda's kitchen has been abandoned as of 2013 (I guess) ,and since I've seen posts that it does not work for KK ,it would literally not work on Lollipop either :/

blinqipa said:
LOL ,my sense of humor sometimes fails to the ground XD .Enough out of topic discussion XD have you tried getting a working .zip ? Or has anyone tried that? Seems like dsixda's kitchen has been abandoned as of 2013 (I guess) ,and since I've seen posts that it does not work for KK ,it would literally not work on Lollipop either :/
Click to expand...
Click to collapse
No, I've not. Doing that is way out of my league. I want to thank you for all of your efforts, though. :good:

Though guys if you want a more active community on Nexus 6 and Moto X Pro head over here http://bbs.ihei5.com/forum-234-1.html , though it is on chinese , I almost understand nothing , but just translate the page into English .

just so that you all know, the moto x pro and nexus 6 are similar hardware wise, they are not the same and do differ, and would probably brick your nexus 6 if you actually flashed it onto your n6.

Related

What is a "deodex" file? What does it mean?

My Hero is running Damages 2.09.1 and it works perfectly in every respect. But when I was considering the update it was mentioned that this version was "deodexed" and this was a better file. What is deodex? What does it mean? Is it better then a version that is not deodexed?
Thanks for the education. I see the term and want to know what it means.......
Lisa
◦An odex file is basically a chunk of source code that has already been extracted from the apk and put on /system/. This is done to speed up the first boot of a rom (you know how your first boot takes a long time… that’s while it is extracting all of these dex files) and also to save space on /data/. Our stock sprint rom comes with this odex files to give you those benefits, however it also prevents us from “hacking” those files and modifying them. This build has taken all those odex files and injected them back in the apk’s. So expect a slower first boot, and more space taken up on /data/, but you get benefits from it such as the vanilla lock screen being fixed and live wallpapers in Rosie.
Taken from Flipz' website
Great explanation!
I so appreciate you taking your time to explain this....
Lisa
No problem....
Thank you Brian M!
jesus not again............
how the hell do yall even find these ancient threads to bump serously i want to know.
This is actually good. It's showing that he's learning and willing to go deep in our forum to find a solution. Bravo pimpin.
I also found this right now and it answered my question very well. Thanks biran m. =)
yea me to. Thanks brian m
Yah me 2, Thanks mr brian M
You can search it by google.：D
Google Search brought me here

[HOW TO]The Big N00B how-to!

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

[ROM] [4.2.2] Archos 80 Cobalt - CyanogenMod 10.1

CyanogenMod 10.1 working on the Archos 80 Cobalt!
This is oma7144's ROM, I've been able to get it running under a bit of guidace from oma and I thought I'd share it here if anyone else is interested.
The original thread is here - but this ROM is designed for Odys Genio tablet, which has basically the same specs as the 80 Cobalt. (RockChip 3066 chip)
As always, only flash if you know what you are doing, I am not responsible for anything you do or break.
New Version 1.3.4
Thanks danielo83 for putting this zip together
Oma CM10.1 v1.3.4
Battery problem fixed and ROM is now ready for daily use
- CWM 6.0.1.5 recovery
- System ext4
- Internal Storage 2,5 GB
- PhabletUI & Multiuser
- Device spoofed as Nexus
- Ethernet Support
- Init.d support
- USB-Hub enabled
- Gameloft compatible
- Gamepad (PS2, XBox, ...)
- Kernel modules (cifs, tun, lan, serial)
- latest hosts, su, su-binary, busybox
- MX Video-Player, Apollo & FX Sound
- Reboot Menue, CPU Tweaker, Pimp my Rom
- Dateimanager HD (Root)
- Trebuchet & Nova Launcher
Instructions
Before you do anything, download the file below and extract everything to your desktop, find 'Oma RK30 CM10.1 Format NAND.zip' and copy to your externalSD card
then unmount and remove the externalSD, this is very important because if you try to boot after flashing the rom, you will not have access to the internal SD - which means you can't flash files from CWM or do anything basically
Boot to bootloader
Turn off the tablet
Unplug from charger and USB
Hold the 'volume down' button and then hold the 'power button' to turn the device on and boot into bootloader, keep holding both until you see the boot screen
Connect USB and you will get "Unknown Device" message in windows
Install device drivers included in the zip below under x64 or x86 depending on your system - see gavroche's root thread if you are having trouble
Open up RKandroidTool.exe as administrator (located in RKDevelopTool_v1.35 folder)
- if you have trouble try different USB ports on your computer
You should see at the bottom of the RKAndroidTool "Found RK Android Loader Rock USB"
Click 'erase IDB' button - this will only take a few seconds
Now click 'Run' button, this will take a few minutes to install the ROM
Insert your external SD card
The device will boot into CWM, now choose install zip from sdcard (not internal), install Oma RK30 CM10.1 Format NAND.zip that you copied to your external SD earlier
Reboot, and enjoy CM10.1
--------------------------------------------------------
Downloads
http://www.mediafire.com/download/15wh4o4xwhec11o/OMA_4.2.2_CM10.1_Rom.zip
--------------------------------------------------------
What is working
Wifi
Camera
Display
Touchscreen
Battery info showing
...everything apart from mentioned below
Known Problems -
Scren flicker when rotating screen,
When battery is low the tablet wont wake up from sleep and the power button will only reboot it instead of waking it up
- Thanks to danielolsman
- To "fix" this you could install "no sleep" from the play store.
--------------------------------------------------------
If anyone is interested in helping get rid of these three problems please don't be shy.
I'm not a dev and I'm looking at fixing the bugs but don't really know where to start...
Credits
oma7144, gavroche
kage00,
Thanks for your effort!!! You're breathing new life into our tablets. We (I am sure there's a very big community alongwith me) who have been waiting for this.
I don't have my cobalt with me right now but will try and install at some point and feedback how it goes.
Are you also willing to work actively on issues and improvements. I am happy to help wherever I can. Perhaps, others will join in as well.
Thanks
Looking at the forum feedback from HUKD, the rom is not far from being a stable rom for day to day use. I see following general issues raised with this rom so far
1. Waking up issues after deep sleep in case when the battery is low
2. Rotation issues
3. Default language
4. Nexus port and therefore certain apps incompatibility
As mentioned earlier, I am happy to help wherever I can.
Thanks
Hey nikunj87,
Thanks for your support! I would love to be able to work on the issues with this rom but to be honest, I'm not a dev, not even close, and I wouldn't even know where to begin to start fixing the problems.
For the moment I'm looking at putting together a kernel from Archos' source and adding overclocking, I've never built a kernel before so it's a learning curve... don't hold your breath, haha!
I just thought I'd post this rom here to see if we could get some interest in the project and maybe get a dev's (or two's) attention to take a look at the problems, but for the moment it's just you and me who are interested in this..
I think the best we can do is wait for an update to this rom from Oma (the original dev), as you mentioned all the problems with this rom on the cobalt are problems that exist with the same rom on other devices. So maybe with a new update it will work a bit better.
Unless if we can get someone else who knows what they are doing to take a look at it...
kage00 said:
Hey nikunj87,
Thanks for your support! I would love to be able to work on the issues with this rom but to be honest, I'm not a dev, not even close, and I wouldn't even know where to begin to start fixing the problems.
For the moment I'm looking at putting together a kernel from Archos' source and adding overclocking, I've never built a kernel before so it's a learning curve... don't hold your breath, haha!
I just thought I'd post this rom here to see if we could get some interest in the project and maybe get a dev's (or two's) attention to take a look at the problems, but for the moment it's just you and me who are interested in this..
I think the best we can do is wait for an update to this rom from Oma (the original dev), as you mentioned all the problems with this rom on the cobalt are problems that exist with the same rom on other devices. So maybe with a new update it will work a bit better.
Unless if we can get someone else who knows what they are doing to take a look at it...
Click to expand...
Click to collapse
willing to lend a hand tho I am only new to this stuff as well!
I tried this ROM, it seems that OMA posted an AKKU Fix here
I will trie it soon....
There are some problems with the camera; its inverted. The provides fix did not solve the problem, does someone know how to fix it ?
Akku fix does not work
Sent from my Nexus 4 using xda app-developers app
Cool! looks like we've got some attention from the devs!
So there is a new version of this ROM over at this thread
edit ----> please take note, if anyone tests this ROM you will need to keep the same kernel from the existing package in OP and use that to flash with new ROM, Otherwise you risk having a bricked device
Aparently the battery problem exists, but netlars has a possible fix on this thread if anyone can test it that would be great. My tablet is off getting fixed, I had some problems with the touchscreen.
Also Oma was asking if anyone could test this too
Are these paths there?
/sys/devices/platform/rk30-battery/startget
/sys/class/rk30_battery/rk30_battery_start_timer_work
Click to expand...
Click to collapse
If anyone can test and reply here please, then I can tell him on the other thread.
Thanks
Battery problem is solved (see original thread)
CM10.1 is now ready for daily use.
(@Kage00: maybe its possible for you to make a new zip package with the new boot image found here?)
EDIT:
made a zip package myself : CrewRKTablets_RK30_Cobalt 80 by Oma_CM10.1_v1.3.4.zip
Thanks danielo83,
Nice one, I'll update the OP,
I got news back from Archos repair about my tablet / touchscreen problem. They decided to replace the whole unit, so I'm going to sell the brand new one and get a Nexus 7, which means I won't be able to play around with this ROM anymore becuase I won't have the tablet. I'm happy to still keep the thread open and you guys can tell me if there's anything to update in the OP
Thanks
edit----------
In the new version do you still have the screen flicker artifacts on rotate?
danielo83 said:
Battery problem is solved (see original thread)
CM10.1 is now ready for daily use.
(@Kage00: maybe its possible for you to make a new zip package with the new boot image found here?)
EDIT:
made a zip package myself : CrewRKTablets_RK30_Cobalt 80 by Oma_CM10.1_v1.3.4.zip
Click to expand...
Click to collapse
Not sure if anyone will see this but I own an unrooted/untouched Archos 80 Cobalt which I haven't used for months. Decided to dig it out for my son to play with but I can hardly fit any apps on it so looking in to alternative roms.
Came across this rom which I want to flash but I'm unsure on how to start. Do I have to root and flash CWM on to the tablet before doing anything in this thread or are the instructions in this thread all that I need to do in order to flash this rom on to an unaltered tablet?
Yes you will need to be rooted first before using this ROM, please follow this thread to get root and CWM on your tablet then you can flash this ROM with the instructions in the OP
Yeah the storage space is limited for some stupid reason on the stock ROMs, that shouldn't be a problem on this ROM, also if you find you dont like this ROM there is also another custom ROM here based on stock 4.0.4 firmware with better app storage space
the new version still has the rotate "problem".
Sent from my Nexus 4 using xda app-developers app
I just wanted to say as well, that Archos have released kernel sources (downloadable from their website) that are from May or June 2013 from memory. The last stock ROM built for this device was released in February 2013. Which means if anyone wants to try their hand at compiling the kernel from Archos source, it would be a newer kernel than what you are using now and it could possibly fix any left over problems with this ROM. I don't have any spare time to do it anymore, but if anyone was interested I'm sure you could find a walkthrough on XDA to tell you how to do it easily enough.
The kernel for this ROM at the moment is still the stock kernel from the stock 4.0.4 ROM, which is working, but maybe if a newer kernel was made from the sources it may work a lot better
app space and vold.fstab
Does anyone know if this ROM exists with 6gb of app space? I currently have the supersport ROM with 6gb app space and edited the vold.fstab to swap the internal and external sd cards. I’d like to do the same with this JB ROM.
How difficult would it be to edit the ROM to change the app space?
Does this ROM use the vold.fstab to set where the internal and external sd cards are mounted? (I think this has been changed in JB 4.3 but I’m not sure about 4.2.2)
Cheers, T
To be honest I'm not sure if it is possible, but you could ask the devs who made the ROM they would probably be able to tell you if it was possible or not. Have a look over at http://www.arctablet.com
You'd need to ask oma7144 or netlars
You could try to post in this thread and see what they say
kage00 said:
Yes you will need to be rooted first before using this ROM, please follow this thread to get root and CWM on your tablet then you can flash this ROM with the instructions in the OP
Yeah the storage space is limited for some stupid reason on the stock ROMs, that shouldn't be a problem on this ROM, also if you find you dont like this ROM there is also another custom ROM here based on stock 4.0.4 firmware with better app storage space
Click to expand...
Click to collapse
Can you please tell me why I'm getting this error when trying to follow the root instructions from?
http://forum.xda-developers.com/showthread.php?t=2066972
{
"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"
}
I'm using Windows 8.1 64 bit
I'm doing this with USB debugging enabled and the device switched on as this is the only way I can get the 'ARCHOS' device to show in Device Manager under 'Other Devices.
If I put the tablet in to download mode (power + vol down) I get a dead Android symbol with red exclamation, is this normal? However when I insert USB cable in to the device at this point my computer doesn't bring up the 'ARCHOS' device in Device Manager...
All I get then is this:
I don't actually have this tablet anymore, but I remember mine being a bit strange when I first tried to root it too. It can be a bit temperamental... I remember reading someone saying somewhere about leaving the charger plugged in when trying to reboot into download or recovery mode, if that doesn't work try with the USB cable (or both) plugged in while you try.
I also remember with mine I had to direct windows to the specific driver folder extracted from the zip based on which drivers you need, eg, x86 or x64 etc.
You could also look at this thread http://www.freaktab.com/showthread.php?3244-Archos-80-Cobalt-900-supersport-rom where the might be more info on root.
I'm using windows 7 though, so I don't know exactly what differences there are with win 8.
If all else fails just keep searching and reading all/any forums you can find about rooting the thing, I'm sure you'll find that someone has had the same or similar problem
good luck
kage00 said:
I don't actually have this tablet anymore, but I remember mine being a bit strange when I first tried to root it too. It can be a bit temperamental... I remember reading someone saying somewhere about leaving the charger plugged in when trying to reboot into download or recovery mode, if that doesn't work try with the USB cable (or both) plugged in while you try.
I also remember with mine I had to direct windows to the specific driver folder extracted from the zip based on which drivers you need, eg, x86 or x64 etc.
You could also look at this thread http://www.freaktab.com/showthread.php?3244-Archos-80-Cobalt-900-supersport-rom where the might be more info on root.
I'm using windows 7 though, so I don't know exactly what differences there are with win 8.
If all else fails just keep searching and reading all/any forums you can find about rooting the thing, I'm sure you'll find that someone has had the same or similar problem
good luck
Click to expand...
Click to collapse
Hi do you have any idea how to get XBMC working with this rom? XBMC just goes back to home screen whenever i try launching it?
For xbmc you will need an older version of it. The one from August seemed to be the one to use for most people with the same issues on the HP slate 7 so am guessing it will sort your issue too. A quick search on Google should locate the archives for you
Sent from my ARCHOS 80G9 using Tapatalk

[Q] [UPDATED] Probelm Bootloop error with dsixda's kitchen cooked ROM

Hello guys:laugh:
I searched every forum thoroughly but didn't found a proper and working solution for Xperia devices
I am trying to make a custom ROM from stock using dsixda kitchen
I used stock 12.1.A.201 as the base ROM
I believe that it's either the updater script error or kernel probelm as I am using stock kernel and my zip is like this
Data
META-INF
system
boot.img
check_data_app
Click to expand...
Click to collapse
This happens when rom is created
De-odexed it rooted it and added X-Reality engine and created the rom
First on installing I got error of status 0 so I changed my update binary file from same de-odexed version from this link http://forum.xda-developers.com/showthread.php?t=2704312 by @dipesh1502 (thanks to him for that awesome rom)
Next I am getting error status 7
ROM Starts flashing then it comes to this part
formatting system bla bla
expected 5 args got 3
Click to expand...
Click to collapse
something like that and then it stops on error status 7
here is the updater-script please have a look. I really want to create this ROM. Please help
Updater-Script Download
here is my build prop build.prop download
Help guys please I'll be highly grateful
My device is C5302 rooted and unlocked bootloader with 12.1.A.205 stock kernel
EDIT : Got past the error status 7 now ROM gets installed
But unfortunately now it ends in a bootloop :/ Got stuck on Sony splash logo and then reboots constantly :/
Had a nandroid backup ready x)
Had to flash the ftf file over and over again. :/
Phone is allright just want to catch this error of bootloop.
I changed kernel with the dipesh1502's ROM but still no luck. Modified Updater script but still no luck. help me I am soo confused and screwed!! :'( :'(
My new Updater-Script
There's a HUGE difference in creating boot animations and creating a ROM.
Don't expect to teach yourself how to make a ROM in just a few days.
It takes, weeks, months, years...
If you're mainly planning to make some exterior changes, which I think you're currently doing, I would focus on making complete themes and not ROMs.
People are not waiting for a ROM which is already available but that looks somewhat different and maybe has some extra or removed apps.
Regarding your problem, I will not be able to help you since I don't have that kind of knowledge.
Anyway, good luck!
Gamm86 said:
There's a HUGE difference in creating boot animations and creating a ROM.
Don't expect to teach yourself how to make a ROM in just a few days.
It takes, weeks, months, years...
If you're mainly planning to make some exterior changes, which I think you're currently doing, I would focus on making complete themes and not ROMs.
People are not waiting for a ROM which is already available but that looks somewhat different and maybe has some extra or removed apps.
Regarding your problem, I will not be able to help you since I don't have that kind of knowledge.
Anyway, good luck!
Click to expand...
Click to collapse
Thanks for the reply.
Yeah I know that it's not easy to create ROM and also it takes a lot of time. I am ready to give it a shot
I am just making some small changes just for my sake I'll be using this ROM personally for my own use I know that there are a thousand times better ROM's than mine
Anyway glad you considered my probelm.
Bootloop can be cause by:
- Wrong permissions
- Corrupt installation
It is nice if you collect either the last_ksmg or logcat when bootlooping. (if possible)
~~Regard
---------- Post added at 08:08 PM ---------- Previous post was at 08:04 PM ----------
But first:
Share me the .zip you have created perhaps I can take a small look
~~ Regards
mrjraider said:
Bootloop can be cause by:
- Wrong permissions
- Corrupt installation
It is nice if you collect either the last_ksmg or logcat when bootlooping. (if possible)
~~Regard
Click to expand...
Click to collapse
Thanks for the reply
Can you please have a look at my new updater-script and tell me what is wrong?
I will surely try to get logcat but before that if you can just analyze this updater-script and pinpoint the mistakes it'll make my work a lot easier.
Thanks in advance :good:
Sent me the entire .zip file instead (but start with updater-script)
~~Regards
mrjraider said:
Sent me the entire .zip file instead (but start with updater-script)
~~Regards
Click to expand...
Click to collapse
Sure thing I'll
I am compressing it to maxium extent using KGB archiver and it'll become around 10~20 mb only
It's still compressing so it'll take some time before it reaches it's max compression.
I'll surely send you asap

APK Manager / Deodex / Odex Manager

So, I have put together an actual Windows program for a lot of Rom Builders. I used to build a lot of Roms, but really don't do much of it any longer. What I know though, is the tool I built is extremely easy to use and very effective. I thought some of you would very much enjoy this tool. It will also allow a lot more people to start theming and tinkering It has built in Draw9 support and will automatically detect what versions of Java you have and allow you to select which one you would like to use.
So I am going to post it here for now in the Note 4 forum for a few of you to install it and check it out. It will support many phones, if not all. All you have to do is make sure you have some type of Java program installed on your PC. The rest is all self-contained and updated.
The first thing you are going to need to do after install is to go into setup and setup the paths accordingly, to your liking. Once this program is setup it runs great. I have built it with threading, so it won't lag as you are working along.
I will post some screen shots for you all to check out.. I would use these as examples of what your environment should look like. Also, make sure you pull the system, from the adb options tab, from your phone as the first step before doing anything else, it will use the framework files as needed to work. This path is also where your deodex setup paths of originals should point to, the pulled files for app and framework.
Enjoy !!!
Link: https://drive.google.com/file/d/0B31X8bH_5Gl-eUtJODBhcUdPRDg/view?usp=sharing
Update: ** Updated file to fix a small issue.. ** EST: 10:24 p.m.
Thank you for this! Going to take a look into it here tonight!
Updated OP..
Made some modifications to the build..
Very Cool, thank you for creating this tool, I'm going to give it a try tonight after a few Christmas parties this evening.
Sounds like a useful tools. I will check it out when my retail phone gets rooted.
za33ck said:
Very Cool, thank you for creating this tool, I'm going to give it a try tonight after a few Christmas parties this evening.
Click to expand...
Click to collapse
Oh great, it will be even better after a few drinks in you..
Can you post source code as well ?
This looks awesome, so what do we use? Do we take a Odin flash able ROM....I don't understand how to use it?
Sent from my Definitive v1.4 Note 4 using Tapatalk
bdorr1105 said:
This looks awesome, so what do we use? Do we take a Odin flash able ROM....I don't understand how to use it?
Sent from my Definitive v1.4 Note 4 using Tapatalk
Click to expand...
Click to collapse
You just plug your phone in and wait for it to detect it.
From there you need to setup the program, look at the screen shots.
gatesjunior said:
You just plug your phone in and wait for it to detect it.
From there you need to setup the program, look at the screen shots.
Click to expand...
Click to collapse
So basically whatever mods you currently have you then make flushable?
I guess what I am asking is should we Odin the stock base that's odex, pull the folders with your program, deodex it and make whatever mods?
Biggest question, how do we make it flushable, I am extremely new to this
Sent from my Definitive v1.4 Note 4 using Tapatalk
Normal
Normal ? when selecting device? See attached Picture
bdorr1105 said:
So basically whatever mods you currently have you then make flushable?
I guess what I am asking is should we Odin the stock base that's odex, pull the folders with your program, deodex it and make whatever mods?
Biggest question, how do we make it flushable, I am extremely new to this
Sent from my Definitive v1.4 Note 4 using Tapatalk
Click to expand...
Click to collapse
So, I am assuming, you mean flashable. Look around for update.zip files associated with Android. You need to make sure you are rooted / dev edition in order to even pursue this. If you are then do some research on update.zip files and understanding our partition table for our phone or your phone, etc..
Wifi tethering unlock
I have my Note 4 DE ordered/shipped by Samsung. I have never used this program before, how easy is it to do your own Native WiFi Hotspot modification? Or is there any step by step I have missed somewhere? Basically, I am wanting to root, TWRP and then change a few things on my own.
Thanks!
gatesjunior said:
So, I have put together an actual Windows program for a lot of Rom Builders. I used to build a lot of Roms, but really don't do much of it any longer. What I know though, is the tool I built is extremely easy to use and very effective. I thought some of you would very much enjoy this tool. It will also allow a lot more people to start theming and tinkering It has built in Draw9 support and will automatically detect what versions of Java you have and allow you to select which one you would like to use.
So I am going to post it here for now in the Note 4 forum for a few of you to install it and check it out. It will support many phones, if not all. All you have to do is make sure you have some type of Java program installed on your PC. The rest is all self-contained and updated.
The first thing you are going to need to do after install is to go into setup and setup the paths accordingly, to your liking. Once this program is setup it runs great. I have built it with threading, so it won't lag as you are working along.
I will post some screen shots for you all to check out.. I would use these as examples of what your environment should look like. Also, make sure you pull the system, from the adb options tab, from your phone as the first step before doing anything else, it will use the framework files as needed to work. This path is also where your deodex setup paths of originals should point to, the pulled files for app and framework.
Enjoy !!!
Link: https://drive.google.com/file/d/0B31X8bH_5Gl-eUtJODBhcUdPRDg/view?usp=sharing
Update: ** Updated file to fix a small issue.. ** EST: 10:24 p.m.
Click to expand...
Click to collapse
Nice,
I just pulled my /system/
Thanks!!!
radionerd said:
Nice,
I just pulled my /system/
Thanks!!!
Click to expand...
Click to collapse
Great..

Categories

Resources