Related
▐▄▀▄▀▌ TUTORIAL CWM roms are the way to go right now!!!
THIS IS A TUTORIAL TO GET CWM ROMS UP AND RUNNING ON UR RHODIUM
SO i felt completely compelled to share my amazing experience and results with my CWM rom!!!!
i almost always try to keep the development process here away from other sites
if you want a REALLY GOOD WORKING version of android on your device without trying NAND ... follow my instructions...
first off i have a ATT Tilt 2 i have been using with this..
to find anything you need to know on android for our phones go HERE
(Neopeek site)
any size card should do for runing CWM builds,,, i however am runnig an 8gb class 4 sdhc and all is well
MY recommended partition sizes... (i set 300mb as all my EXT2 partitions just to make calculating it easier...)
(primary) FAT32 - storage for music videos pics etc... rest of space
(primary) EXT2 - 200-300mb (system) holds rom build... none are over 250mb
(primary) EXT2 - 200-300mb (data) data for android... i believe is the space for app install... so bigger is better..
(primary) EXT2 - 50-100mb (cache) like ram sorta...
with these sizes... worryin about the size of the rom will not matter ..
look on the site link i posted above on how to install and use CWM if you havent before... (dont worry newbs... its easier then everyone makes it seem...)
with CWM builds the standard Gapps are not included...
THIS SITE is the repository to go to... i am using "gapps-hdpi-20101114-signed.zip" but feel free to try others to see if they load...
this is the the most frustrating part of CWM, finding GAPPS that install...
u install them the same way you do a rom... by installing the zip from the sd card...
i do recommend installing gapps zip after you have already installed the rom and booted and restarted android a couple of times
otherwise i recommend THIS ROM as it is the one i use... i know it is only Froyo but it has a themed gingerbread taskbar with black pull down so it still looks nice!!!
lastly
((((technically test kernel.. so not recommended!!... but proven to fix screen not coming on problem...))))
for you crazy tester ppl waiting for the day you brick your phone(im totally kidding dont worry newbs) i use the WIS-Tilt2 kernel the newer test one to be specific...
GO HERE
With this kernel my device goes in to deep sleep with the GReen light and wakes up perfect every time!!!!!
the zip is just modules package and a zImage.. just have to replace and boot...
WARNING... when i updated with the working kernel it looked like it wasnt going to work.. didnt seem to be anywhere enough scrolling text and the boot animation barely played and then the screen went black... i played around with the buttons and found the device to be opperating with out the screen on i kept pressing buttons and the screen finally woke up!!!! be patient!!!! after that it worked perfectly everytime...
other tips... for people experiencing wifi unable to scan problem ..
use the Wifi-nvram.txt trick look it up in xda... once command is entered no need to reboot just turn on wifi and connect!!!
i hope that this has been helpful i couldnt find any where that had all the tips and tutorial in one place to get CWM up and running at least once... had to do it trial and error.. hope my hard work will help you newbs out!!! hahaha
---
Here is the CMW version of the normal FRX06 by arrrghhh. Credits to arrrghhh for the build and to preston74 for making it ready for CMW.
G-apps are already included in this build so you don't have to flash them separate.
http://www.multiupload.com/2VS5ZKUFBA
jellenl said:
Here is the CMW version of the normal FRX06 by arrrghhh. All credits goes to him, I only made it ready for clockwork mod. Gapps are already included so you don't have to flash them seperate with this build.
http://www.multiupload.com/TQSN4TG28U
Click to expand...
Click to collapse
thanks guy...
\
i want to make it as easy on peopl eto get a stable working version of android on their TP2's
Well, i used CWM with an 1GB SD and worked like a charm...
and first time i did it with a 2gb... i just said more cause there is more room for apps... lol
should prolly clarify that...
Trekfan422991 said:
thanks guy...
\
i want to make it as easy on peopl eto get a stable working version of android on their TP2's
Click to expand...
Click to collapse
Yes you are doing a good job
I first made a cmw version of frx06 without gapps, but argghhh told me it was ok if I include the gapps, so I did
You may also integrate my link in your first post, then I'll delete my post.
Forgive me here... I am new to the CWM builds. If I have a CWM build on an SD card, with the appropriate ex2 partitions and all, can I use CWM to put on a different build? That would be a whole lot easier than having to reformat and start over...
Well if you run in to any problems the support here is going to be limited.
On the other hand if you use XDAndroid the support here is maximal.
For testing and dev reasons, I will stay with my current build. I quite like my bluetooth.
For any beginners I would very much recommend that you use 'standard' (see intro to android sticky). Well, at least until you are confident you don't need to be hand-guided through this and know what to do if something goes wrong.
ppcfly said:
Forgive me here... I am new to the CWM builds. If I have a CWM build on an SD card, with the appropriate ex2 partitions and all, can I use CWM to put on a different build? That would be a whole lot easier than having to reformat and start over...
Click to expand...
Click to collapse
It actually is pretty easy - you can backup your current system & data partitions, and throw a new build on - if you don't like it, wipe and revert to the backup.
The only problem is if you have CWM installed, other 'normal' (looped mount) builds will not work - the rootfs will see the partitions and think you want to run from partitions - of course, this results in a failure to boot... I like having many builds on my card at one time so I can flip between them - this also makes testing a heckuva lot easier, so heads up folks!
Nice tutorial and thanks for putting my build in it,but you should put proper credits as Neopeek(and his team) made cwm and i made the build you linked(you can avoid doing this)
And it's gingerbread like themed and the theme name is minimal green..
You can avoid doing 300 mb system as almost all the builds are less than 100 mb,so doing it 150mb is good
CWM and loopmounted builds can co-exist.
arrrghhh said:
The only problem is if you have CWM installed, other 'normal' (looped mount) builds will not work - the rootfs will see the partitions and think you want to run from partitions
Click to expand...
Click to collapse
To avoid this you can just add the "no_partitions" (without the quotes) switch to your cmdline on your startup.txt of the loopmounted build and you should be good to go.
It may depend on your rootfs, but I'm using F22's rootfs and it works like a charm.
i'm trying cwm with frx6 and it keep saying fail rootfs., what am i doing wrong?
Do you followed the tutorial on how to set up your sd-card for cmw? I think you are using a wrong rootfs. As far as I know you need the rootsf from neopeek's cmw.
jellenl said:
Do you followed the tutorial on how to set up your sd-card for cmw? I think you are using a wrong rootfs. As far as I know you need the rootsf from neopeek's cmw.
Click to expand...
Click to collapse
i"ve gotten into CWM but now its telling cand find the zip find even after scroll down to the update. do need to just rename update_frx6 to just plain update. It say installation aborted. I'm using update-frx6
drynaps said:
To avoid this you can just add the "no_partitions" (without the quotes) switch to your cmdline on your startup.txt of the loopmounted build and you should be good to go.
It may depend on your rootfs, but I'm using F22's rootfs and it works like a charm.
Click to expand...
Click to collapse
Damnit, hyc even told me about this - and I forgot about it.
Thanks for mentioning it!
villa15 said:
i"ve gotten into CWM but now its telling cand find the zip find even after scroll down to the update. do need to just rename update_frx6 to just plain update. It say installation aborted. I'm using update-frx6
Click to expand...
Click to collapse
I think you are choosing the wrong item in cmw, you need to choose 'Install zip from sd-cart' and then 'choose zip from sdcard'. Don't choose 'apply sdcart/update.zip' or something like that.
And if that doesn't work, maybe try another build. There is a (really small, because I tested it myself) option that the frx06 cmw build doens't work well.
jellenl said:
I think you are choosing the wrong item in cmw, you need to choose 'Install zip from sd-cart' and then 'choose zip from sdcard'. Don't choose 'apply sdcart/update.zip' or something like that.
And if that doesn't work, maybe try another build. There is a (really small, because I tested it myself) option that the frx06 cmw build doens't work well.
Click to expand...
Click to collapse
No thats not it. i did just just what u are saying. I even tried the CherryPieV3 and it still installation aborted. I'm using CWM 1.8 could that be the problem
If you already have CWM files on your phone, then do not just install the CherryPieV3.zip file. You must extract the zip file which has another zip file inside that you should use to install in CWM.
bleuleon said:
If you already have CWM files on your phone, then do not just install the CherryPieV3.zip file. You must extract the zip file which has another zip file inside that you should use to install in CWM.
Click to expand...
Click to collapse
Yes, you´re right. But he said that he also tried frx06, and that doesn´t worked for him too, and with the frx06.zip bundle, you don´t need to extract it first (if i'm right ;p)
jellenl said:
Here is the CMW version of the normal FRX06 by arrrghhh. All credits goes to him, I only made it ready for clockwork mod. Gapps are already included so you don't have to flash them seperate with this build.
Click to expand...
Click to collapse
I tried to install your CMW version of he Arrghhh FRX06 build but it fails on installing.
I have followed all the steps closely but still can't get it installed.
In the CWM tool when I choose Install zip from SD card and then choosing the FRX06 update the install process starts and within a few seconds aborts.
This is what I see on my screen:
Installing: // sdcard/npkboot/update-frx06.zip
Finding update package...
Opening update package...
Installing update...
Installation aborted
Using the FRX06 CWM build from this thread with the WIS-Tilt2 kernel.
Does anybody have a clue about why this is not working?
I have an 8gb nook tablet that I rooted probably 2 and a half years ago and haven't changed anything on it since. I am wanting to undo and update to current root and flash a 4.4 rom like on my phone. What is the best way to go about this? I know how to unroot, I just need to know the best way to root currently. Thanks.
Custom ROMs like CM comes with built-in root capability, and moreover once installed replaces completely the existing ROM currently in place (be it stock ROM, rooted stock ROM, or another custom ROM). As such, there is no need to root (or re-root) prior to flashing a custom ROM. See http://forum.xda-developers.com/showthread.php?t=2575489 for more background info and pointers.
Cool, thanks for the reply and links. I have some reading to do.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Will your guide for Installing CM10.1 Internally on Nook Tablet work for the 8gb model also? Will it work for CM11 also?
ryknow27 said:
Will your guide for Installing CM10.1 Internally on Nook Tablet work for the 8gb model also?
Click to expand...
Click to collapse
Yes.
Will it work for CM11 also?
Click to expand...
Click to collapse
It should work (with the usual caveat YMMV). Flashing CM11 requires CWM version 6.0.4.5 or later, or TWRP version 2.6.3.0 or later (in step 2(b) of http://forum.xda-developers.com/showpost.php?p=43326042&postcount=123); you can find the SD version of TWRP 2.6.3.x at http://techerrata.com/browse/twrp2/acclaim. You also need a recent Gapps version corresponding to the CM11.
Alternatively, if your NT is already on CM10.x (as my NT was), you can:
download CM11 ROM and the corresponding Gapps zip files onto your NT (user content media partition).
use SD based recovery to flash a flashable emmc CWM zip (http://forum.xda-developers.com/showpost.php?p=48855275&postcount=2) or flashable emmc TWRP zip (http://forum.xda-developers.com/showpost.php?p=49111924&postcount=8) into emmc.
remove SD then boot onto emmc recovery (which is installed in step 2) and use it to install the ROM and Gapps zip files downloaded in step 1.
Remember to use SD based recovery to backup your current ROM before flashing CM.
I need help once again. In step 2a. of Installing CM10.1 Internally on Nook Tablet, I do not see the boot.zip with the 3 files needed and I am not sure how to extract them from the .img file from the pre-made SDcard images. I've only used linux like once and that was to root my Droid DNA. Thank you for your patience with me.
Nevermind...I found a Linux Reader program that let me extract them.
Thanks again.
ryknow27 said:
I need help once again. In step 2a. of Installing CM10.1 Internally on Nook Tablet, I do not see the boot.zip with the 3 files needed and I am not sure how to extract them from the .img file from the pre-made SDcard images. I've only used linux like once and that was to root my Droid DNA. Thank you for your patience with me.
Nevermind...I found a Linux Reader program that let me extract them.
Thanks again.
Click to expand...
Click to collapse
For future reference, you can use 7-zip (which is available for windows) to open .img files and extract its content.
digixmax said:
For future reference, you can use 7-zip (which is available for windows) to open .img files and extract its content.
Click to expand...
Click to collapse
I did try 7-zip first and it didn't work. I may have just done something wrong. I'll try it again. Thanks for all the help.
So I was trying to package a rom and let the kitchen create the meta-inf folder along with the updater-script but the problem is that it's not using the specified mount points.
My phone isn't supported in the kitchen so I had to make a file in the edify_defs folder for my phone. I did all the right steps, I renamed the file to that of the ro.produc.device, used the template and made the necessary edits using notepad ++, and checked the file for any incorrect syntax yet after all that, the kitchen isn't using the mount points I put but instead uses the default value "mount("MTD", "system", "/system")".
Any help?
bump
Don't rely on kitchen's mount. Instead, use the update binary of a working zip for your device and edit the updater-script manually to make it work.
iZLeeP said:
Don't rely on kitchen's mount. Instead, use the update binary of a working zip for your device and edit the updater-script manually to make it work.
Click to expand...
Click to collapse
Yah, the thing is there are no roms for my device not even a stock rom. This is the reason why I'm trying to learn how to build a rom.
Anyways, I got the kitchen to detect the mount points. Turns out i had put the kitchen in the wrong directory. Made the zip flash correctly but now i encountered a new problem. After flashing the zip, the interface on my phone becomes really small. It's like my display went into tablet mode. Any idea on this?
black_fire21 said:
Yah, the thing is there are no roms for my device not even a stock rom. This is the reason why I'm trying to learn how to build a rom.
Anyways, I got the kitchen to detect the mount points. Turns out i had put the kitchen in the wrong directory. Made the zip flash correctly but now i encountered a new problem. After flashing the zip, the interface on my phone becomes really small. It's like my display went into tablet mode. Any idea on this?
Click to expand...
Click to collapse
What's your device and android version? Much better if you could post on your device's specific thread.
It's a local phone called starmobile quest, running jellybean. Sadly, there is absolutely no support for the device not even from the manufacturers. There are no developers either. The only thing we have is root and cwm.
@superr
I'm having some trouble with ROM builds for the pixel XL. I made a bone stock ROM. It boots but has Bluetooth share force close. I think it's due to not being able to use sparse for perms. Currently trying with may build. I'm on Linux mint 18.1
toknitup420 said:
@superr
I'm having some trouble with ROM builds for the pixel XL. I made a bone stock ROM. It boots but has Bluetooth share force close. I think it's due to not being able to use sparse for perms. Currently trying with may build. I'm on Linux mint 18.1
Click to expand...
Click to collapse
It could be missing metadata. Are you starting with this fimware? I can unpack it and locate the files with unique permissions. It may help figure out what is missing. Not using sparse dat is not your issue. set_metadata will work once we track down the problem.
SuperR. said:
It could be missing metadata. Which firmware are you starting with? I can unpack it and locate the files with unique permissions. It may help figure out what is missing. Not using sparse dat is not your issue. set_metadata will work once we track down the problem.
Click to expand...
Click to collapse
Do you want a copy of the current project I have in kitchen. I can upload it to my drive. I just used the zip from the may factory image.
Edit
Wow I just realized that was a link lol. I totally misread lol. Yes I'm using that firmware.
toknitup420 said:
Do you want a copy of the current project I have in kitchen. I can upload it to my drive. I just used the zip from the may factory image.
Edit
Wow I just realized that was a link lol. I totally misread lol. Yes I'm using that firmware.
Click to expand...
Click to collapse
You did not misread, i changed it I will check it out when I get a chance. No need to upload your project.
toknitup420 said:
@superr
I'm having some trouble with ROM builds for the pixel XL. I made a bone stock ROM. It boots but has Bluetooth share force close. I think it's due to not being able to use sparse for perms. Currently trying with may build. I'm on Linux mint 18.1
Click to expand...
Click to collapse
Can you try this updater-script to see if it fixes the issue? There are actually 2 attached, with_vendor and no_vendor in case you extracted vendor too. If you replace it in the kitchen, make sure you zip the ROM manually because the kitchen will change it before zipping based on the files you have.
SuperR. said:
Can you try this updater-script to see if it fixes the issue? There are actually 2 attached, with_vendor and no_vendor in case you extracted vendor too. If you replace it in the kitchen, make sure you zip the ROM manually because the kitchen will change it before zipping based on the files you have.
Click to expand...
Click to collapse
so i cant zip manually because i dont have perms for one file in system. heres a pic. ill just add the script into an existing zip i built from kitchen.was
update
so i was able to move the script into the correct location and zip up the file. however when it flashes the updater script is somehow becoming merged with the original instead of just the new script. it still shows the original script text when flashing.
toknitup420 said:
so i cant zip manually because i dont have perms for one file in system. heres a pic. ill just add the script into an existing zip i built from kitchen.was
update
so i was able to move the script into the correct location and zip up the file. however when it flashes the updater script is somehow becoming merged with the original instead of just the new script. it still shows the original script text when flashing.
Click to expand...
Click to collapse
I will build a rom and upload for you to try. Are you building with vendor included or without?
SuperR. said:
I will build a rom and upload for you to try. Are you building with vendor included or without?
Click to expand...
Click to collapse
I built it without. Do you recommend to build it with vendor. Should that file be root like that. The one that's in that pic I sent.
toknitup420 said:
I built it without. Do you recommend to build it with vendor. Should that file be root like that. The one that's in that pic I sent.
Click to expand...
Click to collapse
Here is the marlin n2g47o test rom:
https://www.androidfilehost.com/?fid=817550096634774971
It is up to you about vendor. You must have matching vendor and system or the rom will not boot. If you inform users they must flash the corresponding vendor.img along with the rom you don't need to include it. The test rom does not include vendor so make sure you have the correct vendor flashed.
The root file you refer to is actually a directory symlink and should not be there at all. I have fixed this behavior locally and in this test rom. If all works, I will push the update.
SuperR. said:
Here is the marlin n2g47o test rom:
https://www.androidfilehost.com/?fid=817550096634774971
It is up to you about vendor. You must have matching vendor and system or the rom will not boot. If you inform users they must flash the corresponding vendor.img along with the rom you don't need to include it. The test rom does not include vendor so make sure you have the correct vendor flashed.
The root file you refer to is actually a directory symlink and should not be there at all. I have fixed this behavior locally and in this test rom. If all works, I will push the update.
Click to expand...
Click to collapse
OK I'll try it now. Good looks.
SuperR. said:
Here is the marlin n2g47o test rom:
https://www.androidfilehost.com/?fid=817550096634774971
It is up to you about vendor. You must have matching vendor and system or the rom will not boot. If you inform users they must flash the corresponding vendor.img along with the rom you don't need to include it. The test rom does not include vendor so make sure you have the correct vendor flashed.
The root file you refer to is actually a directory symlink and should not be there at all. I have fixed this behavior locally and in this test rom. If all works, I will push the update.
Click to expand...
Click to collapse
it flashes with no errors but it wont boot past splash screen.
toknitup420 said:
it flashes with no errors but it wont boot past splash screen.
Click to expand...
Click to collapse
Please try marlin n2g47o test rom 2:
https://www.androidfilehost.com/?fid=745425885120737663
SuperR. said:
Please try marlin n2g47o test rom 2:
https://www.androidfilehost.com/?fid=745425885120737663
Click to expand...
Click to collapse
flash went through without error but still boot looping at splash screen.
toknitup420 said:
flash went through without error but still boot looping at splash screen.
Click to expand...
Click to collapse
Moved to a dedicated thread as this issue is only about Pixel.
I will do more thinking on what could be causing it. I was pretty sure the last rom would fix it but clearly I was wrong lol
SuperR. said:
Moved to a dedicated thread as this issue is only about Pixel.
I will do more thinking on what could be causing it. I was pretty sure the last rom would fix it but clearly I was wrong lol
Click to expand...
Click to collapse
Lol good stuff. Keep me posted. I'll test whatever you throw at me.
toknitup420 said:
Lol good stuff. Keep me posted. I'll test whatever you throw at me.
Click to expand...
Click to collapse
Here is a new approach so I don't have to keep uploading full roms. Use the kitchen to extract the last rom I sent into a new project. In your file manager, navigate to your project directory and delete the 00_project_files directory. Extract the attached file into your project directory. Build rom with kitchen. Test rom.
Next time, you won't need to extract the rom zip again, just replace the 00_project_files directory.
edit: forgot to mention, after replacing the 00_project_files directory with the one in the zip, change perm types to something else, then back to set_metadata. Then build your rom
SuperR. said:
Here is a new approach so I don't have to keep uploading full roms. Use the kitchen to extract the last rom I sent into a new project. In your file manager, navigate to your project directory and delete the 00_project_files directory. Extract the attached file into your project directory. Build rom with kitchen. Test rom.
Next time, you won't need to extract the rom zip again, just replace the 00_project_files directory.
edit: forgot to mention, after replacing the 00_project_files directory with the one in the zip, change perm types to something else, then back to set_metadata. Then build your rom
Click to expand...
Click to collapse
flashing seemed to hang at setting perms. but it eventually went through. still looping at splash screen though.
toknitup420 said:
flashing seemed to hang at setting perms. but it eventually went through. still looping at splash screen though.
Click to expand...
Click to collapse
Can you send the original updater script that booted but did not have bluetooth?
SuperR. said:
Can you send the original updater script that booted but did not have bluetooth?
Click to expand...
Click to collapse
https://drive.google.com/file/d/0B4VEhClrJEWpNnJNVUJTRFV4ODQ/view?usp=sharing
https://drive.google.com/file/d/0B4VEhClrJEWpTmlYWC1CQ0s3LVE/view?usp=sharing
thats the binary and the script. i converted script to binary when i was building rom. this rom boots and runs ok other than bluetooth. its not completely stock though. i have my modded framework settings and system ui apks in there. but they are all signed so i dont think they would mess with anything.
toknitup420 said:
https://drive.google.com/file/d/0B4VEhClrJEWpNnJNVUJTRFV4ODQ/view?usp=sharing
https://drive.google.com/file/d/0B4VEhClrJEWpTmlYWC1CQ0s3LVE/view?usp=sharing
thats the binary and the script. i converted script to binary when i was building rom. this rom boots and runs ok other than bluetooth. its not completely stock though. i have my modded framework settings and system ui apks in there. but they are all signed so i dont think they would mess with anything.
Click to expand...
Click to collapse
Did you convert the new one you just tried after swapping 00_project_files to update-binary? If not, try it please. If so, try without please
Hey all,
So I downloaded hexagon OS for mt6580 and LineaseOS13 for mt6580.. of course installing them gives me a bootlop since they are not ported for the K-touch i10... so I followed a guide to replace the files in those custom roms with the required ones from the stock rom to get them to work. zipped them up, put the zip on the phone, and twrp gives me the "invalid zip file" error when trying to flash them...
help?
@SaucemanBangorang
Isn't the error message "Invalid Zip File Format"?
0
Seppppx said:
1. You used the wrong compression method (most likely.)
You need to set the compression method to "store"
2. Don't port ROMs. Build them from source as they were intended to be. It is much easier to build them than port.
Click to expand...
Click to collapse
Thanks for replying.
I did something dumber, when it zipped, it put the files into a folder, hence the error, re-zipped so it wouldn't do that, and it installed, but the roms of course don't work despite porting them.
2. Building the rom from source sounds way beyond me. Porting meant coping files from the stock rom to the custom rom.. is building a rom easier than that? I actually hate this iteration of the i10 I was given, since it is actually weaker and less functional than my i9.. so I just wanted to see if a better rom would at least make it a usable phone.. I already spent hours flashing and rooting just to get past the stupid trojans/spyware that were installed on the phone.. irritates me that I would have to spend even more time building a rom for it.. especially when it's not a popular phone and said no rom would be of no use to anyone.