Quote:
Originally Posted by justanothercrowd View Post
CREDIT:sxfx
Ok Guys.
I created this thread cause in the JACHero thread on at least every page everyone asks how to install it, what am I doing wrong, and why is it broken.
So let me give you step by steps of what exactly I have done for me and others to run Hero with out a problem. I will also create a thread with step by step on how to use Ubuntu Linux Live distro to partition your card.
Things you will need to make this work.
Your Brain
G1 Phone
SD Card reader
And the files I included in this thread.
My phone right now is running.
JACHero 2.3
NEW SPL
cyanogens recovery 1.2
8gb class 6sd with Swapper(Swap file on ext2 sd)
setCPU slightly overclock.
Results.
Ever since I did my new Buttons, and the SPL I included in this write up, I have not had one problem flashing any hero rom at all on my phone, nor did I ever have problem actually running hero roms.
So here goes.
First before you partition your card or do anything make sure your card is at least portioned to fat32, don't worry about any other partitions yet.
OK once you do that go ahead and take the radio zip file I am including in this thread and flash it on your phone.
But first make sure you don't already have new radio installed which is 2.22.19.26I THIS IS VERY IMPORTANT. To check what radio you have, power off your phone, and power it on while holding the camera button.
If you do have new radio you can continue on to flashing the new SPL.
Flashing your SPL. (PLEASE MAKE SURE YOU HAVE THE NEW BUTTONS INSTALLED)
Ok this is where it might get a little tricky, and you might require a SD card reader I know I did and frankly I think this is the best way to do it and I recommend every time you do put a new update on your sd card to update your phone do it through a card reader.
Now after you flash your SPL you might or I should say more then likely will get stuck at the T-Mobile G1 screen, this also might happen after new radio flash in the previous step. If this is the case do not freak out it's normal and your phone is not bricked, but this is why having a sd card reader is important.
Ok so Here is what you do after you have flashed new Radio and SPL(Note:The steps on running Linux live distro and using it to partition your card is coming up). Boot up Live distro of Ubuntu, when its done booting, go ahead and go into the partitioning program while your sd card is hooked up in the computer.
Go ahead and set up two partitions at this time. One EXT3, and of course the other one Fat32. Your ext3 partition doesn't have to be all that big. I actually have mine set up to 512.
Once you are done creating partitions, go ahead and put the latest JACHero on the FAT32 portion and flash away (don't forget to rename to update.zip).
At this point if you follow all of these steps there is no way possible that your phone should not boot right into the system to run the initial setup.
These steps pretty much walk you through steps as if you were starting with a phone that has completly nothing on it.
Also the first boot up after flashing the new ROM, might take a few mins at the HTC screen.
Once your phone loads up and you go through the setup process go ahead and run swapper, it should be an APP that's already pre-installed.
Once you run swapper go into the setting and change the location of your swap file from /sdcard/swapfile.swp to /system/sd/swap.swp
Here is the reason why. The default location is your FAT32 partition. If you all of a sudden mount your phone to the computer with the swap file running on FAT32 you will corrupt your sd card, and then you will have to wipe and reinstall everything.
If you set the location of your swap file on /system/sd/ that's actually your ext2/3 partition and never gets mounted and you never have to turn swapper off.
Well I hope this helps some of you out. I will be writing the walk through on loading up live distro of Linux and partitioning your card sometime today.
I have used this method on a couple different phones and it has worked each time. Also I really recommend installing cyanogens recovery 1.2, as its an excellent way of making a back up of your phone and doing future flashing.
If there is anything anyone thinks that could be done better feel free to post in here.
Remember different people have different ways. I have posted this way cause it has worked for me on my phone and two other phones I setup, and each time there was no hicups.
FILES:
Radio 2_22_19_26I
NEW SPL
CM-Recovery-1.2
Ubuntu Linux Download
DISCLAIMER:
I am not responsible for anything that you might have done to your phone by following these directions. Like I mentioned before so far every time I have used this method, I have had nothing but success.
================================================== =============================
XDA Users, KEEP THIS THREAD ON TOPIC OR IT TOO WILL GOTO THE TRASH!!!
================================================== =============================[/CENTER]
Click to expand...
Click to collapse
Hey everyone,
I was trying to follow the guide posted after the OP (quoted above), and had a few questions that didn't seem all that clear to me. I've searched all of last night looking for answers.
-What does he mean by "PLEASE MAKE SURE YOU HAVE THE NEW BUTTONS INSTALLED", and how do I install them if I must?
-The cyanogen recovery image, is that installed just as any other rom, via update.zip, ALT+S, etc.?
-Lastly, is it really that much better if I get a Class 6 card? I currently have a regular microSD, but am willing to stick with it if the build runs fine, any other reports on this?
I'm currently at a very basic build, JFv1.51 with no other mods. Thanks in advance!
Buttons in the post refers to the Radio. Yes the CM recovery image is installed just like a ROM, alt+s. Yes it is worth it to get a class 6 sd card. I myself don't have one but I know it's worth it. Got to newegg I think you can get one there for under 20$ Hope i helped you!
Hey, I just wanted to confirm that I will be taking all of the proper steps in putting CyanogenMod 3.6.8.1. Here's what I will be doing (I'm going to start from complete scratch - figured it would help a bit):
CURRENTLY ON JF1.51 CRB43
-------------------------------
Repartitioning 8GB Class 4 card with 700MB Ext2
Reverting back to RC29 via DREAIMG.nhb
Flashing recovery image in terminal
Installing HardSPL through recovery console
Installing JF1.51 ROM (Heard its smart to do this first)
Installing HTC Radio from http://www.htc.com/www/support/android/adp.html
Installing Cyanogen Recovery Console
Flashing CyanogenMod 3.6.8.1 ROM
Recovery console: upgrade_fs (EXT2 -> EXT3)
-----------------------
QUESTIONS THAT I HAVE
-----------------------
Will this ROM smoothly support the modified Rosie.apk from
http://forum.xda-developers.com/showthread.php?t=532822 ?
Am I correct in assuming I do not need to install the Haykuro SPL?
Should I use Compcache from http://forum.xda-developers.com/showthread.php?t=537236 ? I have no experience whatsoever with swap files
Am I correct in assuming that I do not need to manually set up Apps2SD?
And most importantly: DID I MISS ANY CRUCIAL STEPS THAT I WILL REGRET DOWN THE LINE? Dont believe so, but better safe than sorry!!
Thanks every so much!!!!!!!!!!!
Oh, I will be using Paragon Partition manager to partition MicroSD card if that makes a difference
you shouldnt have to redo all the steps. just wipe and flash his rom. also to my knowledge rosie will not run on a non-hero rom. you do not need haykuro's spl. i have put cm rom on phones straight from rc-29 with no problems. i do not know how to use paragon, but it is very easy to partition an sdcard through cyanogens 1.3.1 recovery. apps2sd is automatic with his rom. if it feels slow you can use compache but do not have to if you do not feel you need to. if you do want to go through the steps you have listed then you are set. hope i was able to answer some of your questions
Your ext2 partition is really large. 500MB should be well enough.
torturedsoul802 said:
Hey, I just wanted to confirm that I will be taking all of the proper steps in putting CyanogenMod 3.6.8.1. Here's what I will be doing (I'm going to start from complete scratch - figured it would help a bit):
CURRENTLY ON JF1.51 CRB43
-------------------------------
Repartitioning 8GB Class 4 card with 700MB Ext2
Reverting back to RC29 via DREAIMG.nhb
Flashing recovery image in terminal
Installing HardSPL through recovery console
Installing JF1.51 ROM (Heard its smart to do this first)
Installing HTC Radio from http://www.htc.com/www/support/android/adp.html
Installing Cyanogen Recovery Console
Flashing CyanogenMod 3.6.8.1 ROM
Recovery console: upgrade_fs (EXT2 -> EXT3)
-----------------------
QUESTIONS THAT I HAVE
-----------------------
Will this ROM smoothly support the modified Rosie.apk from
http://forum.xda-developers.com/showthread.php?t=532822 ?
Am I correct in assuming I do not need to install the Haykuro SPL?
Should I use Compcache from http://forum.xda-developers.com/showthread.php?t=537236 ? I have no experience whatsoever with swap files
Am I correct in assuming that I do not need to manually set up Apps2SD?
And most importantly: DID I MISS ANY CRUCIAL STEPS THAT I WILL REGRET DOWN THE LINE? Dont believe so, but better safe than sorry!!
Thanks every so much!!!!!!!!!!!
Click to expand...
Click to collapse
It sounds like you are coming from a brand new g1. If you already have root i wouldnt go back to RC29. And really dont see a point in installing JF 1.51 if your going to cyanogens. You'll just wipe it off anyways.
1. I suggest installing the Cyan's Recovery image first.
2. Then the newest radio and SPL.
3. Make sure you have adb setup (it makes things way easier)
if you want to run cyanogens i suggest 3 partitions although ive heard you can get by with 2. The 3 partitions are generally fat32, ext2/3/4 (2 or 3 is fine and usually is around 500 MB) and a linux-swap partition which is usually around 32 MB, and whatevers left out of your space on your sd card goes to your fat32.
4. If you want to upgrade from ext2 to ext3 then do the upgrade_fs
5. Use ADB and push over the update file or if you have a SD card reader i think you can do it that way.
6. Boot into recovery and do an alt-w (wipe) and alt-s (apply update).
7. Should be good to go from there.
Now for your questions:
1. No you dont need hykuro's SPL (sorry if i mis-spelled i dont use)
2. I personally do not use compcache and it runs ridiculously fast ( I do use linux swap)
3. As far as steps you may have missed. I believe the suggested advice is radio first then spl.
Lastly: There are guides and links to all the files you need right here on XDA. Use the search function as much as possible and the community will be glad to help out. If you have any questions you can get my contact info out of my profile, ill help as i can (im still pretty new to this).
Disclaimer: I AM NOT RESPONCIBLE FOR ANY BAD ADVICE THAT MAY OR MAY NOT LEAD TO THE BRICKING OF YOUR DEVICE.
Thanks for the replies everyone! Flashing it now, I'll report back on how it runs!
I'll be doing this tomorrow as well. Pretty straightforward.
Its so damned fast!!! lol It really feels like things open before I even push the button sometimes!
Many many thanks Cyanogen!!!!!!!!!!!!!!
I always love a happy ending.
Another happy root user = possible next gen dev!
All I would of recommended was installing his Recovery image 1.31 and running a nandroid backup just incase you want to revert back to your old build.
Done and done
New sig speaks for itself...its ultra sexy (screenshots to follow once I find an old apk)
Hi all, I wanted to start a thread for beginners like me to not get confused from all the similar threads and to keep it clean for instructions that are related for basic setting up the phone.
It would be nice to keep the first post updated with data that are 100% correct for any region or provider based phone.
So, to get started with me, i have read through the threads for a couple of days but still have some questions that hopefully someone will answer.
1) SIM-Unlock
I recently got my Mini from my provider Telenor in Serbia, and the first thing for carrier based phones someone will probably want is to SIM-unlock them. You can check if your phone is locked by entering *#7465625# in the dialer pad.
The cleanest and fastest solution that works 100% so far is from this thread
http://forum.xda-developers.com/showthread.php?t=1335548
I used the second method since I'm on OSX and have no way of installing Android SDK but can find a hex editor ("Hex Fiend" ) that works under OSX.
2) ROM-Upgrade
For people that have SIM-free phones the first step may be upgrading to newer ROM(and since Ginger is the favorite ROM my guess that I don't need to write any info for Froyo based devices), my suggestion is that you download Official ROM-s from sammobile.com because they are guaranteed 100% clean and you can also find carrier based ROM-s if you mess something up and want to take your phone for warranty reparation.
How to update your phone to Ginger is described here
http://forum.xda-developers.com/showthread.php?t=1255305
After the update it is recommended to do cache and data cleanup. And a hard reset by entering *2767*3855# in the dialer pad.
Go into restore mode(Power off your phone, hold Home and Power button), and when a menu comes up select "clear cache", and "clean data", select reset afterwards and wait for it to boot .
After this you are ready to go and explore Android OS
3) Install CWM
And that's it for people who want to just use their phone as an android device. But. If you want to get the maximum potential from your device custom ROM-s are a must. For flashing custom ROM-s you will need Clock Work Mod to be installed, which is described here
http://yagyagaire.blogspot.com/2011/09/installing-clock-work-mod-recovery-in.html
4) Custom ROM
Afterwards download the custom Rom of your choice from xda , the installation instructions may wary form ROM to ROM but they always are described in their threads( SO READ THEM CAREFULLY ), here
http://forum.xda-developers.com/showthread.php?t=1318735
And here is where i stopper, and need further help from experienced people
My questions are:
1. After i installed the custom ROM, I need to repartition and reformat my sd-card to a different file system ex. ex-fat for faster performance using Clock Work Mod???
2. Do I have to do some zip-aligning and how???
3. How many partitions do i must have on my sd-card and what size/file system must they be??? ( i know one must be for swap, one for dalvik, and one to expand internal storage but I don't know how big and which file system).
4. I want to use a custom kernel for undervolting(no OC is needed) and thus i need to move the dalvik to sd card as far as I understood, is there a tutorial or is it intuitive from the app that is used to do this???
Bump, does anyone know any of the related questions?
1. After i installed the custom ROM, I need to repartition and reformat my sd-card to a different file system ex. ex-fat for faster performance using Clock Work Mod???
--> Two options:
-ClockWordMod Recovery.. CWM partitions the sd-ext in ext3 format. Also, swap can be partirioned here. Partitioning in CWM will reformat the whole sd card.
-If you want ext4 format, you can dowload Minitool Partition Wizard. I don't know if there is an OS X version though. If you can partition drives on OS X without 3rd party software, that's great.
2. Do I have to do some zip-aligning and how???
--> I don't think you have to zip-align it yourself. Depends on the ROM I think, it's probably a feature.
3. How many partitions do i must have on my sd-card and what size/file system must they be??? ( i know one must be for swap, one for dalvik, and one to expand internal storage but I don't know how big and which file system).
--> You need:
sd-ext (ext3 or ext4) - partition used to expand internal memory
fat/fat32 - normal partition
swap - depends on the ROM, CM7 by squad supports swap.. emanon v3 does not since it uses s2e, no option for swap..
--> Depending on the number of apps that you are planning to install, sd-ext can be 512MB or 1GB or 2GB. Swap value deplends as well, 32MB to 128MB, I think. I have not come across an article on what's the best value for this.
4. I want to use a custom kernel for undervolting(no OC is needed) and thus i need to move the dalvik to sd card as far as I understood, is there a tutorial or is it intuitive from the app that is used to do this???
--> did not find any.. not sure with other models.. for our mini, CM7 by squad has an undervolt option but not sure if it is working..
I bought the original Nook Color back in Nov. 2010. I went through all the methods back in the day, when guys first started rooting the Nook and all the problems we had back then ... side loading apps ... adhoc issues ... B&N updates ect ... we got CWM recoveries and finally we got fully working froyo's and Gingerbread's. Then CM7's and the Phiredrop's.
I been through it all. I ended up giving my Nook to my son, and he loved it. I got into Android Development Cell (ROMS). I Now got my Nook back from my son. It is working, but I have forgotten a lot about how to mod it .... mainly the partition tables, and how the bootloader runs. Does it look to the eMMC first ? or the SD-Card ? Can we flash from both locations ?
Anyways ... He has it setup weird now. It has a dual boot menu, I can boot into CM7 or CM9, But it is acting up and some stuff doesn't work. He also says it can boot into Stock 1.4.2 somehow *shrug*
I have done some searching here on xda but it is a lot of OLD posts and dead links.
Could you guys help me out with a few questions ?
01) I would like to wipe EVERYTHING from eMMC abd SD-Card and start over. I know I can format the uSD and also format the eMMC, but Can I flash a SD with a CWM image and then install Stock 1.4.2 on the eMMC. Do I even need to install stock first ? What is the best method for this ?
02) Will I need to nooter my nook again at this point if I do that ?
03) Can I run CWM on the SD and run a nandroid backup to that same SD if it is a large SD-Card ? I thought I could since the bootloader looks at uSD first (but I guess it looks at the boot partition huh ? ) my son says NO you can not run CWM and have a nandroid backup on that same SD. Yes or No ?
Bottom line is this is what I’m trying to do……
01a) I could care less about stock B&N.
02a) I just want a Nook that will dual boot into CM7 and / or CM9 preferably from my 16 GIG SD-Card but it really doesn’t matter, as long as I can install app’s to the external SD-Card.
03a) I want a way to backup the entire CM7 or CM9 via CWM to my SD-Card.
NOTE: I have a (1) 16 GIG SD-Card (1) 4 GIG SD-Card and (1) 8 GIG SD-Card.
If you could help me out with any info at all on any of this, please do so. I am mostly Android literate and I have a working ADB on my win7. I just have forgotten exactly how the nook operates at the lowest level, and how the newer CM's are flashed now after a clean format
Thank you for your time and help to any of my questions.
Peace
Thibor69 said:
the partition tables, and how the bootloader runs. Does it look to the eMMC first ? or the SD-Card ? Can we flash from both locations ?
Click to expand...
Click to collapse
Partition talbes and mount points
The Nook Color boots from uSD first... then eMMC if there is no bootable uSD in the card slot.
Thibor69 said:
I have done some searching here on xda but it is a lot of OLD posts and dead links.
Could you guys help me out with a few questions ?
Click to expand...
Click to collapse
Browsing the developer forum would be very beneficial... as there are constantly new posts... so almost all of this is covered in recent posts.
Thibor69 said:
01) I would like to wipe EVERYTHING from eMMC abd SD-Card and start over. I know I can format the uSD and also format the eMMC, but Can I flash a SD with a CWM image and then install Stock 1.4.2 on the eMMC. Do I even need to install stock first ? What is the best method for this ?
Click to expand...
Click to collapse
Create a new bootable CWM recovery uSD and place one of the files from here on it.
Boot into CWM and flash the file you downloaded.
Thibor69 said:
02) Will I need to nooter my nook again at this point if I do that ?
Click to expand...
Click to collapse
Only if you want stock to be rooted... not necessary if are going to flash a different ROM to eMMC or don't care about stock root access. If you choose to root stock.... use this thread
Thibor69 said:
03) Can I run CWM on the SD and run a nandroid backup to that same SD if it is a large SD-Card ? I thought I could since the bootloader looks at uSD first (but I guess it looks at the boot partition huh ? ) my son says NO you can not run CWM and have a nandroid backup on that same SD. Yes or No ?
Click to expand...
Click to collapse
Yes.... I do that frequently.. the thing is... the nandroid backup will be of the eMMC unless you use one of the modified CWM's designed for SD installs.
Additionally... if you are going to run that from a uSD with another ROM on it... you will certainly have to adjust the boot partition on the uSD to be large enough to hold the nandroid you are creating.
Thibor69 said:
Bottom line is this is what I’m trying to do……
01a) I could care less about stock B&N.
02a) I just want a Nook that will dual boot into CM7 and / or CM9 preferably from my 16 GIG SD-Card but it really doesn’t matter, as long as I can install app’s to the external SD-Card.
03a) I want a way to backup the entire CM7 or CM9 via CWM to my SD-Card.
NOTE: I have a (1) 16 GIG SD-Card (1) 4 GIG SD-Card and (1) 8 GIG SD-Card.
If you could help me out with any info at all on any of this, please do so. I am mostly Android literate and I have a working ADB on my win7. I just have forgotten exactly how the nook operates at the lowest level, and how the newer CM's are flashed now after a clean format
Thank you for your time and help to any of my questions.
Peace
Click to expand...
Click to collapse
DizzyDen said:
Create a new bootable CWM recovery uSD and place one of the files from here on it.
Boot into CWM and flash the file you downloaded.
Click to expand...
Click to collapse
So you are saying that I can do it in this order:
1) Format eMMC ( only boot partition right ? )
2) Format uSD ( resize boot partition to a larger size for backups )
3) Create bootable CWM uSB ( any particular one you recommend ? )
4) Put one of the stocks 1.4.x files on the uSB then flash it
5) Put CM7 or CM9 on uSB and flash it
Question: Do I need to flash stock 1.4.x even tho I dont want it ? or can I skip step #4 ?
Thanks
Thibor69 said:
So you are saying that I can do it in this order:
1) Format eMMC ( only boot partition right ? )
2) Format uSD ( resize boot partition to a larger size for backups )
3) Create bootable CWM uSB ( any particular one you recommend ? )
4) Put one of the stocks 1.4.x files on the uSB then flash it
5) Put CM7 or CM9 on uSB and flash it
Question: Do I need to flash stock 1.4.x even tho I dont want it ? or can I skip step #4 ?
Thanks
Click to expand...
Click to collapse
Item 1) highly NOT recommended. There is no point to format /boot.
Item 2) if "uSD" means the external microSD card, then, no, you don't need to format it since it will be done in step 3 of your list.
Item 3) Get the CwMR version 3.2.0.1. And call it "flashable CwMR uSD", not uSB.
Item 4) If you don't want stock, leave it out as no point to touch it.
Item 5) After done step 3 above, put CM7 OR CM9 in there, the CwMR uSD, and flash.
Strongly suggestion: before doing anything. Be sure you know what you trying to do or at least, pls let us know what you try to accomplish. For example, do you try to run CM7 or CM9? Do you want to run it from the external uSD card or from eMMC? Instructions are different.
votinh said:
Item 1) highly NOT recommended. There is no point to format /boot.
Item 2) if "uSD" means the external microSD card, then, no, you don't need to format it since it will be done in step 3 of your list.
Item 3) Get the CwMR version 3.2.0.1. And call it "flashable CwMR uSD", not uSB.
Item 4) If you don't want stock, leave it out as no point to touch it.
Item 5) After done step 3 above, put CM7 OR CM9 in there, the CwMR uSD, and flash.
Strongly suggestion: before doing anything. Be sure you know what you trying to do or at least, pls let us know what you try to accomplish. For example, do you try to run CM7 or CM9? Do you want to run it from the external uSD card or from eMMC? Instructions are different.
Click to expand...
Click to collapse
Hello -
Thank you for the update info. Glad I asked first. Thank you Dizzy for your help, you have been a big help to me in the past also. Votinh thank you for your reply. Looking back at what I wrote I see many mistakes in my process. Thanks for correcting them.
Now ... as to your question Votinh. What is it I am trying to do.
First off this is what I currently have. Nook is working, but not well and just a mess in general. Sometimes it locks up or just runs at a crawl. ( I have CPU oc'd to 1200 ) I have CM7 and CM9 but can't seem to boot into CM9 anymore at all. I also have CWM v3.2.0.1 installed on my external SD-Card with a nandroid backup.
I just want to erase it all and start over : )
I want my Nook to be able to Dual Boot into CM7 and CM9. I would like both CM9 and CM7 on my 16 GiG SD-Card, BUT if that is not easy or possible then I would like CM7 on internal and CM9 on external. I dont need stock.
If all else fails ... or just to complicated I could live with just CM9 (nightlies or stable) with all APPS installed to external SD. and forget about dual boot.
Again thank you .... and please ask me any more questions you might need to help clarify my goal.
Peace
Thibor69 said:
Hello -
Thank you for the update info. Glad I asked first. Thank you Dizzy for your help, you have been a big help to me in the past also. Votinh thank you for your reply. Looking back at what I wrote I see many mistakes in my process. Thanks for correcting them.
Now ... as to your question Votinh. What is it I am trying to do.
First off this is what I currently have. Nook is working, but not well and just a mess in general. Sometimes it locks up or just runs at a crawl. ( I have CPU oc'd to 1200 ) I have CM7 and CM9 but can't seem to boot into CM9 anymore at all. I also have CWM v3.2.0.1 installed on my external SD-Card with a nandroid backup.
I just want to erase it all and start over : )
I want my Nook to be able to Dual Boot into CM7 and CM9. I would like both CM9 and CM7 on my 16 GiG SD-Card, BUT if that is not easy or possible then I would like CM7 on internal and CM9 on external. I dont need stock.
If all else fails ... or just to complicated I could live with just CM9 (nightlies or stable) with all APPS installed to external SD. and forget about dual boot.
Again thank you .... and please ask me any more questions you might need to help clarify my goal.
Peace
Click to expand...
Click to collapse
So far, everything you've asked are doable, in fact, a lot of members currently having the same system you describe.
Firstly, "I would like both CM9 and CM7 on my 16 GiG SD-Card" is called "dual-boot, it is a true dual-boot.
Go thank "racks11479" for his tremendous work
Link: http://forum.xda-developers.com/showthread.php?t=1448186
Note: both CM7 AND CM9 are on the external uSD card.
Secondly, "then I would like CM7 on internal and CM9 on external."; since your wish is granted , this is just an option for you. Yes, you can easily install CM7 in eMMC (aka internal memory) and booting CM9 off uSD as you want.
For references:
Boot CM7/CM9 off uSD, thank verygreen.
Link: http://forum.xda-developers.com/showthread.php?t=1000957
---------- Post added at 05:27 PM ---------- Previous post was at 05:21 PM ----------
Update from my last link
http://forum.xda-developers.com/showthread.php?t=1576879
Ok ... got it. But If I just want to install to SD external ... can I format the internal eMMC ? And my last question .... I see your signature and what you run. You recomend CM7.2RC1 MiRAGE KANG on eMMC and Dalingrins kernel. You like that setup the best ? I think I will try that setup now. What version of CWM should I use for that and were will CWM be eMMC also ? or can I backup to SDCard.
Thanks once again
Wait a minute. Alan Moore doesn't live in Scottsdale!
Whatever. Swamp Thing is awesome. You can live wherever you want
mateorod said:
Wait a minute. Alan Moore doesn't live in Scottsdale!
Whatever. Swamp Thing is awesome. You can live wherever you want
Click to expand...
Click to collapse
Wow ... good call brother. Not many people know the face.
Peace
Thibor69 said:
Ok ... got it. But If I just want to install to SD external ... can I format the internal eMMC ? And my last question .... I see your signature and what you run. You recomend CM7.2RC1 MiRAGE KANG on eMMC and Dalingrins kernel. You like that setup the best ? I think I will try that setup now. What version of CWM should I use for that and were will CWM be eMMC also ? or can I backup to SDCard.
Thanks once again
Click to expand...
Click to collapse
Once again, NEVER format the eMMC short of a catastrophic event, (sometimes referred to in tech circles as a Mountain Dew Event.)
Mr72 has good instructions for getting 7.2 up and running on eMMC, http://forum.xda-developers.com/showthread.php?t=1443292
You'll want to use his directions to load the image found in mrg666's thread here, http://forum.xda-developers.com/showthread.php?t=1344873
Dalingrins would be redundant as it is already part of this build. You *will* want to run the V6 script as it is well worth it.
Once you've got that going well you should have read around enough to be able to load CM9 nightlies on an SD card. You *do* have a Sandisk card, right?
Thibor69 said:
Ok ... got it. But If I just want to install to SD external ... can I format the internal eMMC ? And my last question .... I see your signature and what you run. You recomend CM7.2RC1 MiRAGE KANG on eMMC and Dalingrins kernel. You like that setup the best ? I think I will try that setup now. What version of CWM should I use for that and were will CWM be eMMC also ? or can I backup to SDCard.
Thanks once again
Click to expand...
Click to collapse
In bold: sure, but what do you try to do? Format the internal so that you can install something else on it?
I currently have CM7.2-RC1 Kang running on eMMC, it is really good.
Booting off uSD is more like for experimental, play it for a while to see if we like it or not. For trying, I recommend using uSD.
I have not spent more time on CM9 since I don't see much of the benefit of it.
Also, MisRy covered pretty well there.
MISRy said:
Once again, NEVER format the eMMC short of a catastrophic event, (sometimes referred to in tech circles as a Mountain Dew Event.)
Mr72 has good instructions for getting 7.2 up and running on eMMC, http://forum.xda-developers.com/showthread.php?t=1443292
You'll want to use his directions to load the image found in mrg666's thread here, http://forum.xda-developers.com/showthread.php?t=1344873
Dalingrins would be redundant as it is already part of this build. You *will* want to run the V6 script as it is well worth it.
Once you've got that going well you should have read around enough to be able to load CM9 nightlies on an SD card. You *do* have a Sandisk card, right?
Click to expand...
Click to collapse
Thanks for the info Misry. I have many sd cards and have used them all will good results. My Sandisk is only 4 gig ... so it was not going to be my first choice. I also have a Class 4 8 Gig Kinston I was thinking of using. Or a Class 10 16 Gig Patriot, which I know people dont like, but it seems to work fine in my phones ....?
Magus-
The difference in the SD card class as far as speed comes down to the size of the information we want to write. The lower classes aren't very fast with the large hunks of info, but excel with the tiny byte exchange used in the ROM. As the speed of your system will really be affected by the slow I/O rates of something like a class 10, compromise on size before class. It may be counter intuitive, but people have given up on cyanogen in general only because they had the wrong sdcard. This is especially true if you have a dual boot and are running the ROM off of the sdcard itself.
Look at the "strange results or how I learned to love cm" or something thread. Google that with xda and nook and you'll find it. That has all the info you'd want and way more.
Do another book with Eddie Campbell and we'll call it square. You know you want to.
MISRy said:
Once again, NEVER format the eMMC short of a catastrophic event, (sometimes referred to in tech circles as a Mountain Dew Event.)
Click to expand...
Click to collapse
Well I was testing a homemade script and I believe I did in fact format eMMC and either scrambled the boot partition or deleted it also on emmc. No mater what I do I can not get eMMC to boot. I can boot cwm from SD-card, but nothing on eMMC.
Advice ?? please be as technical as needed. I do not have Linux right now, but I do have adb on win7 and 3 sd-cards
THanks
Well, let's see what we're working with...
$ su
# fdisk -l /dev/block/mmcblk0
Post the output of the above. It'll show what partitions are left (if any) and then we can take it from there. This can be a hassle indeed, and it will require some research as I have avoided doing this myself. I am hoping your ROM partition is still intact, at least.
Anybody else who can help, please do. I may not be able to respond as often as I would like.
I was gonna suggest 8+1 to see if we can get back to square one.
http://nookdevs.com/NookColor/RestoreToStock
He's gonna need a ROM partition for that to work.
For a long time, 8 failed boots would (as a last resort) result in a working Nook for just about every problem. But, as users are getting more experienced across the board, more advanced and dangerous stuff is being attempted.
When everything goes right, it can be pretty rewarding, but when it goes wrong...well, let's just say the solutions become a lot more advanced as well.
The output of the command will let us know which partitions are erased and if any are still intact. Considering the information we have so far, I am not hopeful. If the emmc was erased and formatted...well, we'll see.
Here's what has occoured:
over-wrote the following partitions with "0":
# 0p7 = /cache
# 0p1 = /boot
# 0p5 = /system
# 0p6 = /data
Then formatted 5-7 ext4. Flashing a ROM with a blank boot partition has been done on another device many times with no issues, for some odd reason this nook responded poorly and I believe the the boot.img never copied over to 0p1.
I am not sure what all he tried but I know he tried the flashable emmc fixer, which didnt' fix it. I am actually concerned that made it worse, but that's my opinion and I don't have my hands on the device. For what ever reason he couldn't get adb working with the device. I found this thread:
http://forum.xda-developers.com/showthread.php?t=919353
And since ADB wouldn't work, I wrote a script and created a flashable zip for him so it would perform the same operation, but it stopped saying bad zip. He tested it with 7zip and there were no errors, I checked my script and I see no errors in it and yes, I used a proper program for it as well, NotePad++. He's a bit frustrated and sending it to me. I am confident that if none of the things he tried didn't completely scramble the internal partitions that I can get it working. But if anyone has any idea as to why the script would fail, let me know.
Edit: And correct me if I am wrong, but it's the lack of a kernel which caused it to respond so badly. A similar thing happened on our phone but was due to powering off with a blank boot partition (not our noob moment but someone else's), but being that it's a tegra 2 system we have Nvflash and all is easily rectified. My theory is that there's something, most likely memory, which is loaded by the kernel and is required for a recovery to run.
He tried the 8 failed boot and it did bring up something which ended with an error about no boot partition, I'll try to get the picture he showed me later, I need to run off to work right now.
... Nevermind
Волк said:
For what ever reason he couldn't get adb working with the device.
And since ADB wouldn't work...
But if anyone has any idea as to why the script would fail, let me know.
Click to expand...
Click to collapse
First, why in heaven's name would you purposely want to write zeros on the boot partition?
Second, adb was not working because there was no kernel or ramdisk on the boot partition since you had him zero it out. Adb needs both.
If he was trying to flash your zip with CWM from a bootable SD card, then the zip needs to be properly signed before CWM will flash it. You can have CWM toggle off that check, but I doubt he did that. Hence the bad zip error.
Also if he has his CM7 SD card still working, he can repair the emmc partitions using the terminal emulator from CM7. All the adb type commands can be run from there.
The boot partition probably needs to be reformated to vfat before it can accept any files from a CWM restore.
This always confuses and creates a lot of anguish and anger and rage.. i've had to redo the plaster on the apartment walls seven times and replace 4 LCD screens from my violent outbursts as a result of this.
This it it:
EMMC and SD.
EMMC, sure, easy, simple - install, get rom manager, use TWRP as a tool for flashing and updating roms.
SD, single and dual-bootable, not so easy. Error messages. Update failures. Screams, tears, coffee-shop outbursts resulting in numerous police calls and once to a mental ward facility.
Question:
How do I manage between the two. I eff up the EMMC trying to update the SD, and so on. They don't make it easy, unless I'm just for some reason blindsided by this.
Rundown:
TWRP 2.2 with its touchscreen feature, love it. Cool, stylish, features, yeah. Easy got that on my EMMC.
So question question, is there anyway to get TWRP installed on my SD, or any type of usable interface that doesn't muck up and just flash something if it has update-*.zip in it standalone without gui functionality. It's annoying, and I've had numerous problems with it breaking down and having to reinstall everything or go deep into it and fix a broken sector to get it working.
There has to be a fix for this, no?
Myself (and those around me as a result of this) would greatly appreciate any input.
Thanks
echoedge said:
This always confuses and creates a lot of anguish and anger and rage.. i've had to redo the plaster on the apartment walls seven times and replace 4 LCD screens from my violent outbursts as a result of this.
This it it:
EMMC and SD.
EMMC, sure, easy, simple - install, get rom manager, use TWRP as a tool for flashing and updating roms.
SD, single and dual-bootable, not so easy. Error messages. Update failures. Screams, tears, coffee-shop outbursts resulting in numerous police calls and once to a mental ward facility.
Question:
How do I manage between the two. I eff up the EMMC trying to update the SD, and so on. They don't make it easy, unless I'm just for some reason blindsided by this.
Rundown:
TWRP 2.2 with its touchscreen feature, love it. Cool, stylish, features, yeah. Easy got that on my EMMC.
So question question, is there anyway to get TWRP installed on my SD, or any type of usable interface that doesn't muck up and just flash something if it has update-*.zip in it standalone without gui functionality. It's annoying, and I've had numerous problems with it breaking down and having to reinstall everything or go deep into it and fix a broken sector to get it working.
There has to be a fix for this, no?
Myself (and those around me as a result of this) would greatly appreciate any input.
Thanks
Click to expand...
Click to collapse
I'm not really sure what you are asking. No kind of recovery program (either CWM or TWRP) can flash roms to the verygreen SD setup (what you called single boot). They have to be installed using the copy to boot partition method. And on Racks' dual boot SD you have to use his specially modified version of CWM to flash roms there. And the roms to be flashed there have to be specially modified before flashing too.
If you try to flash any unmodified rom zip with either TWRP or CWM it will always get put on emmc. That's what the roms are hard coded to do. It makes no difference whether the recovery is on emmc or SD, it will always install the rom to emmc.
Also remember, even if you somehow get TWRP installed on your SD, whatever you tell it to do, it does it to emmc. If you say wipe system, it wipes emmc system, not SD system, and same with other functions in TWRP. The same is true using an unmodified version of CWM.
I have heard that eyeballer may be working on a modified version of TWRP that may do things to SD, but I don't think he has released it.
Look on my tips thread linked in my signature for an explanation for the difference between flashing to emmc and installing on SD. There is also an explanation of the difference between the two types of SD installations.