Hey this is gonna sound dumb but can we use hd2 cwm builds
sent by DAN SWAGGER via tapatalk/simple mobile
dswaggz said:
Hey this is gonna sound dumb but can we use hd2 cwm builds
Click to expand...
Click to collapse
No. Neopeek already has made CWM for the RHOD. It's still based on the SD card tho...
If you think we can "just use" the HD2's NAND ROM's, you are kidding yourself...
Ok well I was in the x1 section will there builds work an what is the difference or benifit from using cwm over XDANDROID
sent by DAN SWAGGER via tapatalk/simple mobile
I think you are asking the difference between cwm builds and looped builds.
well IMO updating files like test libs is much easier in cwm but reverting test libs is much easier in looped system. On the whole i think cwm should be used by expert users who know how to use adb and unix commands to repair stuff when things go wrong.
There should be no problem running xdandroid as a cwm build but someone has to be motivated enough to do that.
tovarish said:
There should be no problem running xdandroid as a cwm build but someone has to be motivated enough to do that.
Click to expand...
Click to collapse
Indeed, the X1 is running CWM from Neopeek - SD card installs.
I made a FRX06 CWM build but it was really buggy. I didn't give it the attention it deserved, but since I couldn't get it off the ground on my phone I never posted it.
There's nothing holding anyone back from doing it... It booted for me, just had a ton of bugs - much more than the normal FRX06 build did, so I put it off to the side.
I can confirm frx06 cwm build is working for me
yankees2450 said:
I can confirm frx06 cwm build is working for me
Click to expand...
Click to collapse
Oh nice, i thought that the rootfs differences would be the main cause of problems. was that your experience.
I am running frx06 via cwm too (the same FRX06 build I only made a .zip package of it). Everything works fine for me just like the normal FRX06 build. If people want it, I can post a link.
But this is a bit off topic.
The answer on your question is no, we can't use hd2 cwm builds (if i'm right )
tovarish said:
Oh nice, i thought that the rootfs differences would be the main cause of problems. was that your experience.
Click to expand...
Click to collapse
the roofts is the same. I think neopeek change a few things, like init, initrd etc....
I'm using. [BUILD] **Complete Froyo Bundle!!** FRX06 - "Stable" - Minor Fixes http://forum.xda-developers.com/showthread.php?t=951962
here
frx06 cwm build
http://www.multiupload.com/PGZ7H8KTIT
tovarish said:
I think you are asking the difference between cwm builds and looped builds.
well IMO updating files like test libs is much easier in cwm but reverting test libs is much easier in looped system. On the whole i think cwm should be used by expert users who know how to use adb and unix commands to repair stuff when things go wrong.
There should be no problem running xdandroid as a cwm build but someone has to be motivated enough to do that.
Click to expand...
Click to collapse
I agree to a certain degree. But just to add, with cwm if you mess up it is very easy to fix. Their is a backup/restore function. When you get your build working you backup. Then if you have messed something up or currupted your data you don't even need to reinstall! Just restore the data partition. If you are messing around with the system and you mess up just restore the system partition, your data will even be safe. I find this very handy, it is a pain to havta reinstall everytime something breaks
Well how big can you make the partions
sent by DAN SWAGGER via tapatalk/simple mobile
dswaggz said:
Well how big can you make the partions
Click to expand...
Click to collapse
I don't know if there's an upper limit, AFAIK there's only a lower limit... 120-150mb for system, and at least 250mb I'd say for data...
dswaggz said:
Well how big can you make the partions
sent by DAN SWAGGER via tapatalk/simple mobile
Click to expand...
Click to collapse
This is recommended, but if you want larger partitions, it's also good:
Code:
1st partition: FAT32 (sdcard / Rest)
2nd partition: EXT2 (system / about 150MB -> depends on the build )
3rd partition: EXT2 (data / about 250MB)
4th partition: EXT2 (cache / about 50MB)
You have to make the partitions in that order. If you want a bigger data part, just make it about 500MB or 1GB.
I would recommend a much larger /cache partition (100+ MB) if you plan on installing many apps. This is because the dalvik cache is mounted on the cache partition.
Yes maybe thats better, but I just posted the sizes that are recommended by neopeek (who made CMW avaible on our devices).
But yes, if you have a 2GB sd card or something, it's better to make the partitions larger.
This works faster than the pure FRX06 on the main page. You should post it so others can use this version
bleuleon said:
This works faster than the pure FRX06 on the main page. You should post it so others can use this version
Click to expand...
Click to collapse
It seems faster to me, too... but I don't know if I'm just imagining it or not. Is there a reason it would be faster? I don't really know enough about these things to hazard a guess...
ppcfly said:
It seems faster to me, too... but I don't know if I'm just imagining it or not. Is there a reason it would be faster? I don't really know enough about these things to hazard a guess...
Click to expand...
Click to collapse
I guess because the partitions are dedicated, instead of loop mounts? I wouldn't think this would net much speed... Perhaps it does. Perhaps it's just snake oil and that's your perception .
arrrghhh said:
I guess because the partitions are dedicated, instead of loop mounts? I wouldn't think this would net much speed... Perhaps it does. Perhaps it's just snake oil and that's your perception .
Click to expand...
Click to collapse
I think after switching to partitions on FRX, I have seen a speed improvement. It's very hard to say for sure on this sorta thing, especially since I only spent a few days with FRX (coming from GRX) before partitioning.
However, the amount of times where I wonder whether my device is frozen or just didn't recognize my input has gone down to bearable levels recently, and the only change that seems relevant I've made recently is partitioning.
arrrghhh said:
I guess because the partitions are dedicated, instead of loop mounts? I wouldn't think this would net much speed... Perhaps it does. Perhaps it's just snake oil and that's your perception .
Click to expand...
Click to collapse
A strong possibility... perhaps someone needs to make an app with an dummy dial I can turn up to 11.
Have you tried the cwm fx6 yet arrrghhh? Just curious if you think it's faster or not...
Related
THIS WILL NO LONGER BE MAINTAINED and is officially killed
go here if you want rw access and get the version without a kernel.(assuming you have a kernel installed that has aufs support)
IF YOU FLASHED THE UPDATE.ZIP THAT WAS ON THIS PAGE...PLEASE DO THE FOLLOWING:
You need to remove the init script and static busybox that were installed on your device. You have to do this in recovery mode since your rw access is not real.
Download the version linked to above and place it at the root of your sdcard.
open rom manager
select boot to recovery
boot to recovery while plugged in to computer
then from computer:
Code:
adb shell
mount /system
mount /data
rm /system/etc/init.d/99sysrw
rm /data/bin/busybox
umount /system
umount /data
exit
and from the phone:
flash BlaY0's update.zip you put on the sdcard
Really cool for your contributions.
I have no clue what you said, though. Will I be able to uninstall system apps with this? I'm guessin not as you were mostly speaking of partitions.
Lemme guess, brings ext2/3 etc together for something?
wow, best news that I have heard all day.
Ah! Thank you so much. I was just asking about this a couple weeks ago.
Sent from my T-Mobile myTouch 3G Slide using XDA App
does this mean that we can use metamorph now?
sorry if its a stupid question
Hayzie said:
Really cool for your contributions.
I have no clue what you said, though. Will I be able to uninstall system apps with this? I'm guessin not as you were mostly speaking of partitions.
Lemme guess, brings ext2/3 etc together for something?
Click to expand...
Click to collapse
No, You will not be able to uninstall apps with this (at least I don't think). It doesn't actually let you write to the /system partition, it just creates an overlay.
And No it does not even look for an ext partition, it just uses the data partition.
rodriguez27 said:
does this mean that we can use metamorph now?
sorry if its a stupid question
Click to expand...
Click to collapse
Don't really know, I haven't tried. Bear in mind however since it is on your data partition, space could be an issue. Any files changed would then be stored in /data/sysrw.
thanks for the quick info
I'm gonna try this out with Android Commander. With this I should be able to remove apps and delete files without restarting into recovery and mounting everything. Right?
dumfuq said:
No, You will not be able to uninstall apps with this (at least I don't think). It doesn't actually let you write to the /system partition, it just creates an overlay.
Click to expand...
Click to collapse
apparently I was wrong.
as a test I did...
Code:
rm system/app/com.amazon.mp3.apk
while the phone was booted and it worked!
Even after a reboot I do not have com.amazon.mp3.apk installed
It worked for me too, I used android commander booted and running and removed out of /system/apps android.tether.apk, mytouchmusic-signed.apk, and twitter.apk. I had a force close when I removed one thing (I am sure it was running in the background)
They all were gone after a reboot too, I was also able to update adfree just fine.
Any way this can be built into roms?
Thanks for the hard work!
dumfuq said:
No, You will not be able to uninstall apps with this (at least I don't think). It doesn't actually let you write to the /system partition, it just creates an overlay.
And No it does not even look for an ext partition, it just uses the data partition.
Don't really know, I haven't tried. Bear in mind however since it is on your data partition, space could be an issue. Any files changed would then be stored in /data/sysrw.
Click to expand...
Click to collapse
Hey dumfuq, thanks for this! Great idea on porting this badboy! One question though... from what I understood from the source thread is that will use the EXT. Partition for data if you have it right? So it won't break a2sd? I think I understood that correctly. Plus you need your kernel and that should make it work on any rom. I assume it won't overwite the OC kernel either. I'm excited to try this one out but I'm in the middle of rebuilding my rom so I can make a new backup (my old corrupted finally). I will test out as much as I can and let you know if different roms work. I should be done reinstalling by tomorrow (i have like 200 apps, lol!). This might turn out to be a good way to skip nandroiding and wiping all together if it turns out to work properly with a2sd/a2fat32... don't ya think?
sino8r said:
Hey dumfuq, thanks for this! Great idea on porting this badboy! One question though... from what I understood from the source thread is that will use the EXT. Partition for data if you have it right? So it won't break a2sd? I think I understood that correctly. Plus you need your kernel and that should make it work on any rom. I assume it won't overwite the OC kernel either. I'm excited to try this one out but I'm in the middle of rebuilding my rom so I can make a new backup (my old corrupted finally). I will test out as much as I can and let you know if different roms work. I should be done reinstalling by tomorrow (i have like 200 apps, lol!). This might turn out to be a good way to skip nandroiding and wiping all together if it turns out to work properly with a2sd/a2fat32... don't ya think?
Click to expand...
Click to collapse
This version is not the same as blayo's for the legend. It is closer to the desire one (although I used info from both).
Mine will not even try to detect an ext partition at this point, it just uses the data partition regardless of what is available.
Also nothing at all will get overwritten with this unless you happen to have an /system/etc/init.d/99sysrw file. It doesn't copy the kernel or modules, instead it just assumes you have a supported version . The only thing this update.zip does is add the script into init.d.
dumfuq said:
This version is not the same as blayo's for the legend. It is closer to the desire one (although I used info from both).
Mine will not even try to detect an ext partition at this point, it just uses the data partition regardless of what is available.
Also nothing at all will get overwritten with this unless you happen to have an /system/etc/init.d/99sysrw file. It doesn't copy the kernel or modules, instead it just assumes you have a supported version . The only thing this update.zip does is add the script into init.d.
Click to expand...
Click to collapse
I see... so basically, only cm based roms will work. Well, eventually, most us will move to cm based roms once bluetooth and a few minor bugs are worked out. Well, thanks for the info!
sino8r said:
I see... so basically, only cm based roms will work. Well, eventually, most us will move to cm based roms once bluetooth and a few minor bugs are worked out. Well, thanks for the info!
Click to expand...
Click to collapse
I haven't used them, but I think the newer sense roms support init.d scripts so you should be all good.
Working great on Fenix 2.0 with one of dumfuqs OC kernals...thank you much for this.
V2 is posted. It is essentially BlaY0's script for legend. I've only tested with no ext partition, but hopefully if you have one it will use it to store sysrw.
dumfuq said:
V2 is posted. It is essentially BlaY0's script for legend. I've only tested with no ext partition, but hopefully if you have one it will use it to store sysrw.
Click to expand...
Click to collapse
just so you guys now, v2 probably doesn't work for people with who want it on the ext. Blay0 fixed his though (to support non ext users), so I'll give it a look here soon.
Both versions do not work on stock kernel. Am I missing something? Should I use dumfuq kernel or cyanogenmod kernel in order to use this?
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
WHAT!!?? My slide has finally lost it's parasite, com.amazon.mp3 you are toast now. You and your friends kickback, talkback, soundback, twitter... not sure what else I erased, oh genie widget. Thanks dumfuq!! You are the man
Everyone that does this, make sure to check cyanogen's wiki on making a barebones rom so you don't delete something you actually need (of course you did make a nandroid before doing this so no need to worry if you do).
You won't actually delete anything... overlay just makes you (and system) think it is deleted.
Warning: whether you preform these steps correctly or incorrectly, you may be left with a device which cannot be recovered to a previous state. Because this process operates on the recovery partition it leaves you with little room to recover if flashed incorrectly, especially if your normal Android mode doesn't boot.
(although realistically you can just flash ESPRIMG.zip from HBOOT to recover, or fastboot)
So here it is ladies and gentlemen: Clockwork 3.0.0.5, based on a git version pulled/compiled on January 6th, 2011 from the CyanogenMod 7.x (CM7) repository. So what's new? Nothing that I can tell! Not sure why it deserves version 3.x, but I guess changing the text color and background is considered a 'major upgrade'.
This is provided in .img format - NOT an update.zip format. That means you'll have to flash it to your recovery partition using flash_image. Obviously that means you first need root AND S-OFF. No, I won't tell you how to root your phone or what S-OFF is.
Instructions:
Code:
$ su
# flash_image recovery recovery-cw3-test1.img
'flash_image' isn't included intentionally - if you're smart enough to know how to flash this properly and understand the risks, then you might be smart enough to know where to get 'flash_image'.
How'd I do it? Top Secret - I'd have to kill you if I told you.
Download link: [REMOVED - use one from CM7]http://dl.dropbox.com/u/14943973/recovery-cw3-test1.img
Need to revert back to 2.5.0.1? Flash this: http://koush.tandtgaming.com/recoveries/recovery-clockwork-2.5.0.1-espresso.img
Enjoy it? Thank me!
Is it possible to get it in an update.zip format ? I don't want to mess with s-off for now.
SKAm69 said:
Is it possible to get it in an update.zip format ? I don't want to mess with s-off for now.
Click to expand...
Click to collapse
Not from me, sorry. I don't see any point in supporting the legacy method, especially when this version of CW doesn't give any readily-apparent advantages to the older one.
Nice find. I actually have S-OFF but when I start this recovery it is telling me error mounting system, data and others. Is this normal or is something wrong with my setup?
JAWheat411 said:
Nice find. I actually have S-OFF but when I start this recovery it is telling me error mounting system, data and others. Is this normal or is something wrong with my setup?
Click to expand...
Click to collapse
It IS a test build. I'm about to flash it now, I'll let you know if it's just you or not
And FLASH_IMAGE is indeed included, at least its built into cm6.
Edit: it isn't just you, the recovery is practically nonfunctional haha. There are errors all over when you boot into it, mount usb storage crashes it, and it can't mount anything, including the sd card, so its virtually pointless to flash at this point
MusicMan374 said:
It IS a test build. I'm about to flash it now, I'll let you know if it's just you or not
And FLASH_IMAGE is indeed included, at least its built into cm6.
Edit: it isn't just you, the recovery is practically nonfunctional haha. There are errors all over when you boot into it, mount usb storage crashes it, and it can't mount anything, including the sd card, so its virtually pointless to flash. Might even be as bad as arayrays gingerbread port, that hardly works either
Click to expand...
Click to collapse
But the only new features you see would be the new color?
Ace42 said:
But the only new features you see would be the new color?
Click to expand...
Click to collapse
Pretty much yeah. It was orange instead of green. Some of the menus had different names, easier to understand for noobs, but they had the same content. But don't flash it until it's more functional.
Sent from my T-Mobile myTouch 3G Slide
Ok well can someone post an older Clockwork recovery.img so we can reflash it? We can't use this one to do anything.
MusicMan374 said:
It IS a test build.
Edit: it isn't just you, the recovery is practically nonfunctional haha. There are errors all over when you boot into it, mount usb storage crashes it, and it can't mount anything, including the sd card, so its virtually pointless to flash. Might even be as bad as arayrays gingerbread port, that hardly works either
Click to expand...
Click to collapse
I was at work when I uploaded the image and because of that I only briefly tested it. The errors at the beginning aren't critical, but I'll look into the overall functionality being broken, at some point tonight.
Hence this being a "TEST".
Thanks
I appreciate that. I like beta testing new things. It does seem to have a few more functions. I just couldn't revert back.....
Sent from my T-Mobile myTouch 3G Slide using XDA App
Flash this to go back to 2.5.0.1: http://koush.tandtgaming.com/recoveries/recovery-clockwork-2.5.0.1-espresso.img
Actually.. i see a new option to partition SD card straight from the recovery menu... this is a very useful feature... and i think thats why it deserves that build jump from 2.5 to 3.0..... but at this point... it is in an UNUSABLE state.. i understand it is a test build... but i cannot test anything because it crashes on every single option you can possibly choose... will go back to 2.5 and wait for a stable, or at least more functional test build... hope to see some improvements soon... I do not doubt that you guys can have this thing up and running in no timee.. its a good starting point.. Keep the work going... looking forward to it...
was anyone else hoping for a terminal like in good ol' amon_ra? I was...
Be nice to have it in update.zip form for the ones without s_off
Sent from my T-Mobile myTouch 3G Slide using XDA App
elry567 said:
Be nice to have it in update.zip form for the ones without s_off
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
S-off really is a must have. I attached the working build of 3.0.0.5, you have to either use flash_image with it, or fastboot flash, both of which require s-off.
Thnx
Sent from my T-Mobile myTouch 3G Slide using XDA App
mymomma8 said:
it crashes on every single option you can possibly choose
Click to expand...
Click to collapse
Sounds like youre doing it wrong. You can no longer use the power button to select options but rather the trackball
Sent from my T-Mobile myTouch 3G Slide using XDA App
I don't think that file was cw3 I flashed it and still have 2.5 (file by musicman)
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
MusicMan374 said:
S-off really is a must have. I attached the working build of 3.0.0.5, you have to either use flash_image with it, or fastboot flash, both of which require s-off.
Click to expand...
Click to collapse
I flashed it... it seems to be CW 2.5.... not CW 3.0 :/
guitarist5122 said:
Sounds like youre doing it wrong. You can no longer use the power button to select options but rather the trackball
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
No, i select the options with the trackpad... the problem is a bunch of recovery/cache errorss... that i cannot seem to fix, i tried wiping recovery/cache... and problem still persistess
EDIT: FOUND A TRULLY WORKING BUILD Thanks to whoareyou and can be downloaded from
http://forum.xda-developers.com/attachment.php?attachmentid=490785&d=1295154563
No crashes, everything works... sucessfully partitioned SD card. Will create a guide on how to partition SD card using this recovery.
mymomma8 said:
I flashed it... it seems to be CW 2.5.... not CW 3.0 :/
No, i select the options with the trackpad... the problem is a bunch of recovery/cache errorss... that i cannot seem to fix, i tried wiping recovery/cache... and problem still persistess
EDIT: FOUND A TRULLY WORKING BUILD Thanks to whoareyou and can be downloaded from
http://forum.xda-developers.com/attachment.php?attachmentid=490785&d=1295154563
No crashes, everything works... sucessfully partitioned SD card. Will create a guide on how to partition SD card using this recovery.
Click to expand...
Click to collapse
Alright thanks it works now!
It seems that there are a lot of ROMs out there that are doing some funky stuff from the edify scripting in CWM and providing a poor user experience. This overall hurts the entire custom NookColor community and puts a bad taste in peoples mouths.
This post is to point out best practices when creating CWM flashable zips in a consistant way allowing the user to upgrade and migrate between roms in a predictable way.
Rule #1: Don't touch /data!
There are many reasons why you don't want to touch /data but the most important is to allow the user to be able to upgrade your rom without completely wiping your data.
If you want to bundle in an applications (first of all... don't but if you reaally think it is necessary) put it in /system/app as a system app.
Rule #2: Don't overwrite /boot/uRecRam and /boot/uRecImg!
ROM and CWM should be separate. Users should be able to use your rom with CWM or even the stock recovery if they wish to. Allow the user to choose what version of CWM they want to run and allow them to upgrade it independently of your rom.
This allows you to not re-release roms every time a new version of CWM is released.
Exceptions to the rule are update zip that are intended to install CWM (which is ok) or zips that will restore the entire system to stock.
Rule #3 Learn edify
Edify scripting is quite powerful. It saddens me to open up the updater-script of a rom and see it extracting a script and then executing the script.
Don't store your roms as .tars and require a script to extract them to the right locations, you should be doing this all from edify scripts.
Rule #4: Only touch /system and /boot/uImage and /boot/uRamdisk
All other files should be off-limit! This goes back to rule #1 and rule #2. A rom should consits of a kernel, a ramdisk to boot the system and /system files for running the rom!
Rule #5: NEVER EVER EVER modify partitions or wipe the EMMC completely!
I cannot stress this one enough. Use stock partition scheme for your rom. It may seem like a "waste" to you but this is what will make all our roms compatible with each other!
Also the Nookcolor stores NVRAM type information on /dev/block/mmcblk0p2 and factory restore information and a backup of p2 on /dev/block/mmcblk0p3.
If you wipe these directories in your update.zip you WILL BRICK THE USERS NC! It may work for you but they can never return to stock. Their serial number and mac addresses will be lost!
Just don't even think about doing anything with the partition map or these partitions!
Rule #6: When in doubt look at the CM update.zips
A good example of the rules above is portrayed in the CyanogenMod nightly roms for the NC. Look at the updater-script in META-INF/com/google/android and see how things are done.
If we all agree to follow these rules the NC users will get a better and more consistent experience and you will have more users for your rom.
For the users I will list the ROM that are compatible with the list above and list ROMs that don't follow these rules.
ROMs that follow proper packaging
These rom have been built properly according to the rules in the OP. I highly recommend testing any of these out.
Cyanogenmod Nightlies
phiremod nook V5.2
Nookie Froyo 0.6.8
(Utility Update.zip) Nook Color SDcard and emmc swap
ROMs that DON'T follow proper packaging
Use these roms at your own risk!
Flashable eMMC dual boot ROMs
Dual booting roms violates changing the the parition table! If you want to dual boot I would use a bootable SD. If you get a class 6 or higher SD card the performance difference should be pretty low. The perceived speed boost i believe is negligible.
Avoid this rom if you are new to Android or the NookColor. I would call this rom an "Advanced user" rom and not for new members of the community who are unfamiliar with Android, Linux, or the NookColor
Click to expand...
Click to collapse
HC v4 eMMC 2nd ed. - Flashable ZIP
This rom packaging is the poster child for how to do it wrong. They overwrite your /data for app customization. It uses an external script and tar files for extraction and overwrites all of /boot!
AVOID THIS ROM PACKAGE!
Click to expand...
Click to collapse
This looks very wise and in accord with general programming principles.
In the same area of discussion, can you talk about whether or not to clear cache while doing this same update process.
In fact, some explanation of /cache and Dalvik Cache and Market Cache might help to alleviate confusion, especially in regards to specifically what they are, and when one should clear them.
Sure, a "cache" is a piece of data that is frequently used, and so put in a more accessible place, but in typical confusing fashion, that general term is being used in a specific way in Android.
Thanks !
Nice. Good guidelines.
It would, in a perfect world, be nice if a standard CWM recovery would give a choice to either write to SD or EMMC. Then we would not have many of these more involved boot file and CW file edits and changes that are making things more complicated.
If everyone used CW to right to EMMC, this would be easy. But users like myself are running ROMs from SD and are always looking for a way to easily update and flash mods or ubdate ROMs to SD. Yes I use ADB, and other methods, but often I am traveling and away from my office or studio were my PC's are.
Any ideas on CWM to keep things more unified as the op suggests and be able to write to bootable SD cards?
Thanks for starting the discussion.
12
Good explanation/write-up, nemith. Not being a dev, but a user, it helps me to better understand which ROMs to use on my NC. I really liked HC EMMC, but did not realize that it would make it so I could never return back to stock (losing my S/N and such).
Also concur with ADude about cache....a good explanation would be helpful here. I only clear the cache/Dalvik when installing a new kernel. Not sure if even necessary? And, I clear AFTER installing, not before, so not sure if I am even doing that in the correct order. Setting the record straight would go a long way for us non-devs.
Sorry, one more thing, it would be great to have a consistently updated bootable SD card with latest/greatest of CWR on it. I am still on 3.0.0.6 and I am not sure why??
Thanks!
~ Razir
Could have used this a few months ago.
Thank you.
Nemith, your thread is directed at devs. If you want to make sure people don't flash my HC v4 2nd edition, you might want to invite users to read this as well.
nemith said:
ROMs that DON'T follow proper packaging
Use these roms at your own risk!
Flashable eMMC dual boot ROMs
Dual booting roms violates changing the the parition table! If you want to dual boot I would use a bootable SD. If you get a class 6 or higher SD card the performance difference should be pretty low. The perceived speed boost i believe is negligible.
I would avoid dual booting roms if you can!
Click to expand...
Click to collapse
I have this installed..... I am going to run the dual boot removal zip when I get home.
Am I screwed? Anthing I need to worry about?
12paq said:
Nice. Good guidelines.
It would, in a perfect world, be nice if a standard CWM recovery would give a choice to either write to SD or EMMC. Then we would not have many of these more involved boot file and CW file edits and changes that are making things more complicated.
12
Click to expand...
Click to collapse
I've thought of this. CWM would require a major rewrite to do this and the changes would never be sucked in.
Maybe one of these day's I will may my own CWM Kang that can do this, or better yet a desktop application that takes a update.zip and splits out a SD image!
cromanorn said:
I have this installed..... I am going to run the dual boot removal zip when I get home.
Am I screwed? Anthing I need to worry about?
Click to expand...
Click to collapse
No you are just in the "I am smart enough to use these roms without posting big "help me" posts on XDA.
These roms are not really harmful, but they should be avoided by people who don't understand the nook and how it works.
If you understand Android and how the NC is laid out then there should be minimal risk to using these roms. I just want to spell it out for people who are new to the NC or Android that these are "advanced" roms.
nemith said:
No you are just in the "I am smart enough to use these roms without posting big "help me" posts on XDA.
These roms are not really harmful, but they should be avoided by people who don't understand the nook and how it works.
If you understand Android and how the NC is laid out then there should be minimal risk to using these roms. I just want to spell it out for people who are new to the NC or Android that these are "advanced" roms.
Click to expand...
Click to collapse
THANKS!!! I had the NC for about 4 days now and would hate to have messed it up in the long run. I have a Droid Incredible that has been flashed more times than I can remember. It would be nice if the warnings were incorporated into the OP of these roms. I read the entire thread before flashing and I may not have flashed if this warning was there. I like having the option of going back to Stock without repercussions.
edit: Just saw the update you put in your OP about advanced users. I don't consider myself advanced but I am not a beginner either.
nemith said:
I've thought of this. CWM would require a major rewrite to do this and the changes would never be sucked in.
Maybe one of these day's I will may my own CWM Kang that can do this, or better yet a desktop application that takes a update.zip and splits out a SD image!
Click to expand...
Click to collapse
Yup. That would be very nice.
The Nook having SD boot priority really makes it versatile for testing, and quite recoverable. It also satisfies a unique situation where many users have a family device with Nook magazines and children's books not available on the Nook app, so many like myself are booting experiments and daily runners from SD and keeping the wife happy. LOL.
cromanorn said:
edit: Just saw the update you put in your OP about advanced users. I don't consider myself advanced but I am not a beginner either.
Click to expand...
Click to collapse
If you go digging at nookdevs.com and on your own NC you should be able to figure out what is safe and what is not.
nemith said:
Rule #6: When in doubt look at the CM update.zips
A good example of the rules above is portrayed in the CyanogenMod nightly roms for the NC. Look at the updater-script in META-INF/com/google/android and see how things are done.
If we all agree to follow these rules the NC users will get a better and more consistent experience and you will have more users for your rom.
Click to expand...
Click to collapse
the ironic thing is CM Roms don't fully follow Rule #3 since they have multiple scripts that run inside their packages during rom installation.
I'm not sure you are correct in saying that if you flash one of the HC emmc roms you can not revert back to stock. I know for a fact I have done both the dual boot, and HC emmc roms and reverted back to stock multiple times after doing so
I'm not saying you are wrong but I don't think i did anything to "advanced" to get back.
Quoted:
(I have this installed..... I am going to run the dual boot removal zip when I get home.
Am I screwed? Anthing I need to worry about?)
I had it installed and got back to stock no problem... i'm not sure what he is talking about.... i could be wrong though...
It was dualbooted CM7 and HC
went back to stock, registered with BN and all was well.
nooted it and then install HC on emmc
reverted back to stock to set up the ubuntu on NC
got bored of that and am back on HC on emmc
I went back to stock after both as well. Has anyone not been able to after using one of those two roms? I work at b&n and I had to spend time with the stock since they wanted me on the nook counter. I've been back and forth between all the roms more times then I can count.
Sent from my NookColor using Tapatalk
To the OP again i'm not trying to be rude, but could you respond to the last few commenter on this thread, it seems like my self a few others are having an experience that is quite different from what you described in your first post.
Could you help me understand why it hasn't been that difficult to get back from the roms that you specifically said can make it very hard to go back to stock from for us?
I'm currently on HM on emmc and if i did something fancy to get back the last time i restores i'd like to know if i need to do it again.
(edit) I bring this back up only because I saw this thread referenced again recently, which means it is having an effect on peoples work so i'm just trying to understand it.
[Edit] It was the SD card's fault. It seemingly worked fine in the laptop and it mounted fine in CW Recovery, but as soon as I used a different SD card I could flash zips again.
So, now I'm playing with phiremod v6 and loving the Nook again.
I believe I just bricked my Nook through use of the dual boot script.
I can only boot from SD into CW but not a single zip can be applied to the internal storage. Not even the "reverse dual boot" zip will run. They all error out.
I believe this is due to unexpected partitioning.
I even formatted boot, system and cache and still it will not restore any Roms.
So now I'm hoping to access the Nook through USB and repartition the internal storage manually. But before I do that, I need to learn about ADB and what the correct settings are.
jlt220 said:
To the OP again i'm not trying to be rude, but could you respond to the last few commenter on this thread, it seems like my self a few others are having an experience that is quite different from what you described in your first post.
Could you help me understand why it hasn't been that difficult to get back from the roms that you specifically said can make it very hard to go back to stock from for us?
I'm currently on HM on emmc and if i did something fancy to get back the last time i restores i'd like to know if i need to do it again.
(edit) I bring this back up only because I saw this thread referenced again recently, which means it is having an effect on peoples work so i'm just trying to understand it.
Click to expand...
Click to collapse
I don't think Nemith was saying that the existing dual boot installer is going to prevent you from returning to stock. He singled it out as a "ROM" that modifies the partition table, which can be a dangerous thing to do. There is information stored in the /dev/block/mmcblk0p2 and /dev/block/mmcblk0p3 partitions that is specific to each device and required by the B&N software. This information can't be rebuilt easily if lost.
The dual boot install and removal tools (in their current versions) appear to leave these partitions in tact. They are modifying the partition table though, so they're not recommended for novice users. You were able to install and uninstall it with no problems, so you're clearly not one .
The other point is that future versions of the dual boot (doubtful since it has a good dev) or other similar style "ROMs" may not be so careful with your 0p2 and 0p3 partitions.
While twrp 2.x has been out on a large number of devices, since our team never had a N1 it's been absent from our list. Now we are happy to serve up a version to the last Nexus device on our list.
Team Win Recovery Project 2.2, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
Tablet look:
v2.2.1 - various bugfixes and HTC Dumlock support now built in for latest hboots that don't support flashing to /boot.
CHANGELOG (for 2.2.0):
- On-screen keyboard in recovery! -- supports long press, backspace repeat, and swipe left deletes everything left of the cursor
- Name new backups and rename existing backups
- Rename files and folders in the file manager
- Pseudo-terminal emulator
- Support decrypting an encrypted data partition on Galaxy Nexus (enter password using keyboard)
- Backup archive splitting -- allows backup and restore of data partitions larger than 2GB
- Simplified XML layout support between resolutions
- Added dual storage selection radio buttons to zip install, backup, and restore pages
- Improved zip install compatibility
- Updated update-binary source code
- Numerous small bug fixes and improvements
DOWNLOAD:
The fastest and easiest way to install TWRP is to use the GooManager app
For downloads and instructions please visit our TWRP website and choose your device in the dropdown menu
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 30 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Taking this one too for device specific faqs.....
I compiled this build with the Twrp source against the CM7 source tree.
Very Nice - !!!
sbaeder said:
Very Nice - !!!
Click to expand...
Click to collapse
Glad you like it. I know it's a little late to the party, but I figured better late than never.
I must say I was pretty sceptical this could be better than 4ext, but I am pleasantly surprised how much I like it. It is my new favorite recovery for now.....till I need to reformat my SD ext....4ext just does that better. To not have to wipe the fat partition is invaluable to me...but maybe that will be a possibility one day too. I really prefer every other aspect of this over 4ext though...very well done!
Sent from my Nexus One using xda premium
ctfrommn said:
I must say I was pretty sceptical this could be better than 4ext, but I am pleasantly surprised how much I like it. It is my new favorite recovery for now.....till I need to reformat my SD ext....4ext just does that better. To not have to wipe the fat partition is invaluable to me...but maybe that will be a possibility one day too. I really prefer every other aspect of this over 4ext though...very well done!
Sent from my Nexus One using xda premium
Click to expand...
Click to collapse
Thanks! It's been in dev for little over a year now on different devices. As for sd-ext, we'd be happy to merge a pull request with a better method, but given that most newer devices have large amounts of internal storage it's not likely we'll get to it anytime soon.
But twrp is 100% open source and we are more than happy to get people started compiling!
Sent from my HTC One S using xda premium
Im no developer and dont know what a pull request is, but the difference I am speaking of lies in 4EXT's ability to re-partition the SD card either completely (which this also does) or only the ext partition and leaves the FAT partition untouched (which this does not do). What that would entail is way beyond anything I could hope to know or figure out, but Im certain it can be done. Again, thanks for your hard work on this and for bringing it to us!
ctfrommn said:
Im no developer and dont know what a pull request is, but the difference I am speaking of lies in 4EXT's ability to re-partition the SD card either completely (which this also does) or only the ext partition and leaves the FAT partition untouched (which this does not do). What that would entail is way beyond anything I could hope to know or figure out, but Im certain it can be done. Again, thanks for your hard work on this and for bringing it to us!
Click to expand...
Click to collapse
Oh I see what you mean. Not to re partition ot, but just format/wipe just the ext.
Sent from my HTC One S using xda premium
What about hboot updates from this tread? working?
ViViDboarder said:
Oh I see what you mean. Not to re partition ot, but just format/wipe just the ext.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Sorry I was not clear, with 4EXT you can re-partition JUST the ext partition without completely wiping the whole card. So you can actually change partition size, type, etc....without reformatting the who SD card.
athost said:
What about hboot updates from this tread? working?
Click to expand...
Click to collapse
Haven't tried, but I don't see why it wouldn't work.
ctfrommn said:
Sorry I was not clear, with 4EXT you can re-partition JUST the ext partition without completely wiping the whole card. So you can actually change partition size, type, etc....without reformatting the who SD card.
Click to expand...
Click to collapse
That's interesting as most methods of repartitioning a disk cause the entire disk to be wiped. I know there are some ways around it though, but we haven't looked at them I don't think.
ViViDboarder said:
Haven't tried, but I don't see why it wouldn't work.
That's interesting as most methods of repartitioning a disk cause the entire disk to be wiped. I know there are some ways around it though, but we haven't looked at them I don't think.
Click to expand...
Click to collapse
4EXT is the only one Ive heard of....is very nice too.
So, basically, it is just adjusting the content of the partition table to make it smaller (or use any other "free" space after the FAT partition, and then to format the new partition.
Reminds me of all the old DOS based (i.e. ranish?) partition manager tools...basically a lot of low level manipulation of the data in the partition table.
I love TWRP!
Having an issue installing it on my N1, though - goomanager seems to stall at "Installing recovery image." So I need to do it manually I guess.
I'm assuming I should be able to fastboot flash recovery openrecovery-twrp-2.2.1.4-passion.img - right?
---------- Post added at 04:33 PM ---------- Previous post was at 04:28 PM ----------
JeremyNT said:
I love TWRP!
Having an issue installing it on my N1, though - goomanager seems to stall at "Installing recovery image." So I need to do it manually I guess.
I'm assuming I should be able to fastboot flash recovery openrecovery-twrp-2.2.1.4-passion.img - right?
Click to expand...
Click to collapse
And, to answer my own question, that's exactly what I needed to do.
JeremyNT said:
I love TWRP!
Having an issue installing it on my N1, though - goomanager seems to stall at "Installing recovery image." So I need to do it manually I guess.
I'm assuming I should be able to fastboot flash recovery openrecovery-twrp-2.2.1.4-passion.img - right?
---------- Post added at 04:33 PM ---------- Previous post was at 04:28 PM ----------
And, to answer my own question, that's exactly what I needed to do.
Click to expand...
Click to collapse
Glad you figured it out. The issue has been that goo.im had a mishap when updating their hardware. So a lot of data was lost. Our other download on teamw.in should point to a backup source at techerrata files.
I've been using 4ext for a long time but I recently discovered twrp (installed it on my Kindle and love it). One question before I put it on my N1: Are my nandroid backups from 4ext forward-compatible with twrp? E.g. Will twrp be able to restore old backups?
Thanks for all your work!
i had a dinc4 in the past and I just bought on eon ebay. do we expect a cm12 or other lolipop rom.
does any one know what would need to be done to make one.
Welcome Back, dcooterfrog!
To remain on topic: I have no idea... Hopefully someone here will know more than I.
I very much hope there is still enough interest to get us CM12. This is a great phone.
therreid said:
I very much hope there is still enough interest to get us CM12. This is a great phone.
Click to expand...
Click to collapse
ill have to wait until I get the ebay phone. the guy said it wont get past the prompt.
but was not clearer than that.
I am hoping all needs is a factory reset.
but if needed ill do the whole thing
itgs nto clear to me if we can start with a kk rom to make a lollipop rom (port) but if we can I will give it a try unless I see soemoen else is looking into it. I always wanted to build form scratch.
I believe a kernel needs to be written. I myself don't have the proper experience to write one. Sorry. You cannot just simply port a ROM with a new updated verison of Android without having a Kernel that will run the dang thing. Will someone please PM me about a kernel and a ROM, I'll risk my device to beta testing if someone with experience will write up a kernel and someone bakes a ROM such as CM12 (unofficial). Let's get these users CM12!
it looks like the droid razr m is being put on cm12 (its beta now) using the kit kat bootloader
http://www.phonearena.com/phones/co...4G-LTE,Motorola-DROID-RAZR-M/phones/7043,7346
same processor
Qualcomm Snapdragon MSM8960 chipset
gpu Adreno 225
i am sure other stuff is differnt. but maybe not so much.
never built a rom from scratch.
what exactly is the boot loader (its not a different name for the kernel is it this is the one that gets me confused)
recovery needed
rom it self (system dirs
blobs again not sure exactly what this except it binaries.
i hope to have a phone in my hands soon. I was just going to play around with it but who knows
dcooterfrog said:
it looks like the droid razr m is being put on cm12 (its beta now) using the kit kat bootloader
http://www.phonearena.com/phones/co...4G-LTE,Motorola-DROID-RAZR-M/phones/7043,7346
same processor
Qualcomm Snapdragon MSM8960 chipset
gpu Adreno 225
i am sure other stuff is differnt. but maybe not so much.
never built a rom from scratch.
what exactly is the boot loader (its not a different name for the kernel is it this is the one that gets me confused)
recovery needed
rom it self (system dirs
blobs again not sure exactly what this except it binaries.
i hope to have a phone in my hands soon. I was just going to play around with it but who knows
Click to expand...
Click to collapse
A boot loader is the way to flash [EDIT]ROOT partitions. It's how you load the recovery, it is how you flash the kernel if you are still S-ON in this case. Without an unlocked boot loader, it makes things really hard to work with. There are work-a-rounds but it still makes things difficult. Most locked samsung devices have locked bootloaders and in my case, with the Galaxy Note 3, it prevents AOSP from being installed (or basically anything that isn't TouchWiz). THIS is the reason I want this phone to gain Lollipop capabilities. It should not be hard because we have unlocked bootloader and S-OFF capabilities!! Let's get it done.
sp bootloader is the Hboot portion. it loads first of all (and needn't be changed for CM12)
kernel--- this is what needs to be done first.
i will build up a test machine on a spare PC and see if I can get one to compile.
there are other devices that use the same processor and gpu on verizon, so they may have the same radio as well.
other questions i am not sure about.
will an existing recovery work or will it need ot eb be a lollipop recovery ( and also built)
I guess I should try and build cm11 from source first
I'm pretty sure, but uncertain, that all you need is a recovery that supports SELinux. That is a REQUIREMENT for Lollipop.
dcooterfrog said:
i had a dinc4 in the past and I just bought on eon ebay. do we expect a cm12 or other lolipop rom.
does any one know what would need to be done to make one.
Click to expand...
Click to collapse
Mdmower has a working build of cm12. Search mdmower.cmphys.com
darienms1986 said:
Mdmower has a working build of cm12. Search mdmower.cmphys.com
Click to expand...
Click to collapse
mdmower has one problem (maybe not a a problem for you guys but it is for me) the internal sd converts to data and the data converts to internal sd which i donot want , i tried wtih this modification he said and the rom worked i used it was pretty smooth , but when i tried without making data internal sd rom booted in much lesser time plus stucked at android password the encryption screen , so that's why i came back to my CM11 backup .
CAn anyone solve this issue for me :/
mrroks said:
mdmower has one problem (maybe not a a problem for you guys but it is for me) the internal sd converts to data and the data converts to internal sd which i donot want , i tried wtih this modification he said and the rom worked i used it was pretty smooth , but when i tried without making data internal sd rom booted in much lesser time plus stucked at android password the encryption screen , so that's why i came back to my CM11 backup .
CAn anyone solve this issue for me :/
Click to expand...
Click to collapse
To solve use a different ROM, simple
darienms1986 said:
To solve use a different ROM, simple
Click to expand...
Click to collapse
LOL , and where's the different rom with updated nightly ?
The Pac Man rom works very well. Give that a try........
therreid said:
The Pac Man rom works very well. Give that a try........
Click to expand...
Click to collapse
pac rom has bugs which i have not found in this cm12 nightly
Hi, anyone tried AICP? Swap internal and sd on cm12.1 don't rrally give enough space for sdcard
Both PAC and AICP recent builds use the internal swap that CM 12.1 uses. If you need more SD storage add an SD card. The swap gives you significantly more space for apps rather than pictures and the such that can be stored on an external SD card.
EzraDi said:
Hi, anyone tried AICP? Swap internal and sd on cm12.1 don't rrally give enough space for sdcard
Click to expand...
Click to collapse
wmuflyer said:
Both PAC and AICP recent builds use the internal swap that CM 12.1 uses. If you need more SD storage add an SD card. The swap gives you significantly more space for apps rather than pictures and the such that can be stored on an external SD card.
Click to expand...
Click to collapse
So there's no lollipop rom without swaping the internal cause I need space for obb and data not for pic or something else
I don't know of any that do not use the swap.
EzraDi said:
So there's no lollipop rom without swaping the internal cause I need space for obb and data not for pic or something else
Click to expand...
Click to collapse
wmuflyer said:
I don't know of any that do not use the swap.
Click to expand...
Click to collapse
Thank you, I'll upgrade to a new phone then