This info is all over the place on the forum so I decided to add it to its own little area for those who need it. Enjoy
I am going to step by step tell you how to root and get CWM recovery in hopes this will help someone and in turn they can help me by at the least giving me a nandroid backup or something so I can restore my brick. I take no credit for these meathods theywere done by other XDA members I am only repeating what I searched and read throughout the XDA threads if you want to know who the members are Google or search XDA.and I take no responsability for anything you do to your device thats on you this is all for your reading pleasure.
ROOT From Klown80's post
Before doing anything make sure your device is completely updated
#1 you can search all over to get the drivers to connect your tablet or use this: Snap Pea Android Connect (Make sure you have USB Debugging checked under the Dev settings before you connect your device when prompted
#2 Use Cydia Impactor for Root its easy just download it to your PC and run it: Cydia Impactor Sero 7 LT Rooter "You should see a drop down menu that currently says "# drop SuperSU su into /system/xbin/su". Make sure that command is showing in the drop down box and press the start button on the right side." Quote Klown80
#3 Add your favorate SU, Super User APP,update the binary and test the root permissions with a root only app. You may also want to get busybox if you perfer
CWM RECOVERY This is from Takenover83's post
#4 First download the ClockworkMod Recovery Image here: CWM Recovery Image Download
#5 Upload the image to your external SD card/ Micro SD and change the name of the file to " update.img "
#6 use a file manager like root explorer or ES file manager or whatever and right click the file and chmod 644 /system/etc/install-recovery.sh (This is extremely important it will not work otherwise)
#7 I just simply plugged my SD card into the tablet and it updated automaticaly but if that isnt the case for you go into the stock recovery and Choose the option to update via rkimage from external storage
Use EXT SD card as Internal Memory
#8 You must be rooted.
#9 Download Root Explorer ( only if you dont have it) from playstore(paying ) or use ES File Explorer ( free) from playstore. Then instal it.
#10 Download vold.fstab from here Moded Vold.Fstab for the Hisense Sero 7 LT , copy it to your sd card.
#11 Open Root Explorer find the vold.fstab in the sdcard hold it and hit copy,Then hold it and hit the move button. Then paste it in the "etc" folder if it ask something hit yes, go back to the "system" folder and paste it. Hold the vold.fstab an change the permisions to 644 rw-r--r--. .
#12 Reboot an enjoy!!!!!
How to access stock recovery power the tablet off. Then hold the power button and - Down at the same time, when the HISENSE logo appears release the power button while continuing to hole the - Down button until the android appears. Then press the power button and the + up buttons at the same time to access the menu if it does not take on the first try continuw to press the power and + up buttons until it appears.
Here is a link to the firmware tools software for rooting,modding and building roms for the rk3066 chip, I wrote to the manufacture to get the stock recovery firmware image so hopefully we will have that soon here the link for the tools:
FIRMWARE TOOLS
Here is the open source firmaware from the Hisense site for anyone who can use it: Hisense Sero 7 Open Source Kernal and firmware 4.1.1
Do we have any ROMs being ported or developed for me to actually need to install CWM? I have two SERO 7 LTS for my girlfriends kids and I love to Tinker with every android I get my hands on. I already have them rooted and over clocked with some Xposed modules.
Sent from my SCH-I545 powered by T-Mobile Unlimited Plan
suckmikehawk88 said:
Do we have any ROMs being ported or developed for me to actually need to install CWM? I have two SERO 7 LTS for my girlfriends kids and I love to Tinker with every android I get my hands on. I already have them rooted and over clocked with some Xposed modules.
Sent from my SCH-I545 powered by T-Mobile Unlimited Plan
Click to expand...
Click to collapse
Some people like to have nandroid backups after rooting their device and as far as ROMs this device may be low priced but after you do the mem swap with 32gb and having a 1.6ghz dual core your batting 100% maybe people will figure out the financial advantage here
Oh that's true, I'm not a developer or anything near it. But I get what you're saying if I take a nandroid back up, than there's not as much worry about me tinkering either as I could just restore my backup +1 to you.
Sent from my SCH-I545 powered by T-Mobile Unlimited Plan
Nandroid backup or RKImage stock?
May you be much blessed, kind sir!
I don't know what your status is yet on Jan 10th but I have successfully fixed a Sero 7 LT for a friend's daughter using the stock recovery bootloader menu and an RK image. Make sure your Sero is fully charged overnight on the 2 amp adapter that comes with it. You will know it is fully charged because if you unplug it and then plug it back in after 10 seconds, there will be no "charging" symbol that comes up on the screen after about 10 seconds from plugging it in. It will stay dark.
Here is the link: http://forum.xda-developers.com/showpost.php?p=48293563&postcount=39
Download Option #1 from Mediafire
Use 7Zip to expand, you'll need at PC card reader adapter for your Micro SDHC and possibly a USB to SDHC reader. For some reason my HP laptop doesn't like to read adapted micros in the normal slot on the laptop, so I used a MediaGear XtraDrive MGXS-200-HC on my Win7x64.
Once 7Zip has expanded the .img file rename it to update.img and then place it on the root of your micro SDHC. I did a quick format with mine beforehand just to be sure there were no other files that were going to interfere.
Do the normal bootloader from your Sero 7 LT: Volume Down & Power until Hisense, then with Android on his back, POWER FIRST and VOLUME UP once.
The option is down about 3/4 of the way "RKimage"
It will be looking for Update on root, which is the only option. Select with Power button and it will tell you it found it and would like to verify. Select OK and then wait. The first time it goes through the file, nothing will happen. It will CRC the file, boot to the spinning circle screen as if it is a bootloop and then the screen will go blank.
Simply press the power button quickly to turn the screen back on and it will tell you it has found the file it needs and are you ready to restore the update.image. Touch yes, and the whole process will start over. This time when Android finishes, it will boot correctly and ask you for your language input as if right from the store!
Good luck!
Who knows if it is working or not?
I followed the steps listed here for using the external memory card as internal memory. Unfortunately, the only thing I can definitively say about it is that it will make ES File Explorer stop working.
harrycontests said:
I followed the steps listed here for using the external memory card as internal memory. Unfortunately, the only thing I can definitively say about it is that it will make ES File Explorer stop working.
Click to expand...
Click to collapse
I have been using ES FILE EXPLORER ever since I did this and have not had that issue. Weird!
Still can't get it to work
I followed the instructions and tried to use the vfold file you created so I can use my external SD card as internal memory. It still won't work. When I try to move your vfold file to the etc folder, it won't let me, saying that it is a read-only drive. This is very frustrating. I can't imagine what on earth Hisense was thinking when they made the SD card internal. Isn't there a way to just switch the names of the SD card and the external SD card?
harrycontests said:
I followed the instructions and tried to use the vfold file you created so I can use my external SD card as internal memory. It still won't work. When I try to move your vfold file to the etc folder, it won't let me, saying that it is a read-only drive. This is very frustrating. I can't imagine what on earth Hisense was thinking when they made the SD card internal. Isn't there a way to just switch the names of the SD card and the external SD card?
Click to expand...
Click to collapse
Its not his sense its the jellybean os that's makes the card internal. Are you rooted? You have to be rooted for this procedure, then you move the vold file using root explorer or some other program that will allow you to change from read only to write.
I desperately want to install CWM to my Hisense Zero 7 Lite but in your instructions I have NO IDEA what "chmod" means. Once I figure that step out I should be good. Thank you in advance.
That is the permissions you need a file explorer then get the option for the file and choose permissions and change the permission and save it
CWM Help : (
Holy cow it has taken me a week to figure this out and now I feel like a total idiot. I was trying to change the permissions of the file "update.img" which it would not allow me. It never occurred to me in days that "/system/etc/install-recovery.sh" WAS the file I needed to change permissions for. I've read that line at least a hundred times, ha ha. Once it clicked that I was trying to alter the wrong file it took me literally 5 seconds to fix the issue and FINALLY install CWM. Thank you for this post and for replying to my question. Awesome. Now I shall go wipe the stupid sweat off my brow.
Question about internal memory
Hey all, thanks to this excellent guide I now have my tablet rooted. Now that I'm rooted I've been using SnapPea to move apps to the SD card, which was my goal all along. But since I'm still new to this, I was wondering if it would be better to follow the part of the guide that says "Use EXT SD card as Internal Memory." Is there any difference between moving apps to SD with SnapPea and making the SD internal memory? It would be nice if it was all one block and I didn't have to choose what went where (plus some apps don't work right if they are on the SD). Thanks!
Cant get my Sero 7 lite to use the sd card as the storage
Hey there, done lots of reading. I got the tablet rooted, (checked with root checker and titanium backup) HOWEVER I cant get Super user to update its binary, it keeps saying fail. I can access the root and move stuff around, but no permission window pops up. I did the vold file and got it transferred into the external SD card, and system and etc folder. Now if I reboot it, it gets stuck on the Smart screen unless I remove the SD card.
The tablet is now reading the internal flash as if it were an external SD card, and not showing a nand flash. I'm quite stuck. I assume its probably a little thing that needs changed but i cant find it anywhere!
16GB Internal SD...with apps?
So I've got my 16GB SD card showing as the internal SD.
Now, I can't install/move apps to the new internal SD storage.
How can I fix this?
Thanks!
First off, I apologize for my noob-ness. but I have no idea what "chmod 644 /" means. How do I initiate the chmod 644? I have managed to root my sero 7 lite, but CWM didn't install.
Also are there any custom roms using a newer version of android available yet? Thanks a lot!
CWM RECOVERY This is from Takenover83's post
#4 First download the ClockworkMod Recovery Image here: CWM Recovery Image Download
#5 Upload the image to your external SD card/ Micro SD and change the name of the file to " update.img "
#6 use a file manager like root explorer or ES file manager or whatever and right click the file and chmod 644 /system/etc/install-recovery.sh (This is extremely important it will not work otherwise)
#7 I just simply plugged my SD card into the tablet and it updated automaticaly but if that isnt the case for you go into the stock recovery and Choose the option to update via rkimage from external storage
Click to expand...
Click to collapse
I'm trying to make an external SD card act as internal. For some reason, I get a fail to copy error when trying to copy the vold.fstab file to the etc folder. It says it doesn't have permission. Any ideas? Did the rooting process not take properly?
http://i.imgur.com/ihkaGZi.png
EDIT: I managed to finally make it work, by downloading another superuser app. This one simply called Superuser. I was able to copy to the root folders and change the file permission in the system folder after this through the ES File Explorer app. How do I know that the system is using the external sd card as internal now? In settings it still looks the way it did before.
We do have a kernel source for this tablet.
http://www.hisense-usa.com/support/firmware.asp
Search for Sero 7 LT
With that we could get CM13 and what not ported over. Something tells me given the info @dolorespark mentioned with the Sero 7 Pro kernel source having quite a bit of bad coding that the Sero 7 LT will have the same issues potentially.
Hi guys and gals, I have a Hisense sero 7 le e2371, as far as I can tell it is the same as the lt lite, the difference is it is the Australian version! My question is, how to install twrp, it is rooted, but i cannot install anything via stock recovery, no fastboot mode, no bootloader mode! Any help will be greatly appreciated. PS, it is running kitkat 4.4.2, i ultimately want to upgrade it to lollipop or even marshmallow, one day, lol thanks in advance
Chris47au said:
Hi guys and gals, I have a Hisense sero 7 le e2371, as far as I can tell it is the same as the lt lite, the difference is it is the Australian version! My question is, how to install twrp, it is rooted, but i cannot install anything via stock recovery, no fastboot mode, no bootloader mode! Any help will be greatly appreciated. PS, it is running kitkat 4.4.2, i ultimately want to upgrade it to lollipop or even marshmallow, one day, lol thanks in advance
Click to expand...
Click to collapse
how did u root
Related
Hi all,
I have a problem with my G1, running on latest Cyanogen mod. After restarting the card cannot be read and it is seems to be checking the sd card, if it really happens I dunno. What is weird is that I can access the card from recovery mode (shell), and it is not damaged (at least the windows doesn't detect damage while it is in the card reader. So that implies that the problem might be in the Android system.. anybody has a clue how to solve this? Thanks a lot.
Edit: solved it, deleted fsck_msdos from bin and it works flawlessly again
Can always wipe and reflash. Or if you have another sd card laying around and put that in to see if it recognizes it.
I'm having the same problem How did you delete the fsck_msdos from the bin?
theinstagator said:
I'm having the same problem How did you delete the fsck_msdos from the bin?
Click to expand...
Click to collapse
your phone should rooted
then download and install root explorer
in the root explorer go to
system /bin
and delete fsck_msdos
now reboot your phone
I was having this same issue..it would typically take up to 5 minutes or more to "check for errors" after a boot.
To fix this I backed up my sdcard, reformatted, copied everything back, then reflashed. Everything was fine after that.
i have somewhat the same problem but in my case it sometimes say blank sdcard or damged sd card it read fine when plugged into an sd card reader any help
Thanks. It worked by simply deleting fsck-msdos but it keeps giving SwiftKey3 error " unable to load language packs". Keyboard still OK. I have xperia x10 mini rooted running android 2.1 E10i.
hmaxos said:
Thanks. It worked by simply deleting fsck-msdos but it keeps giving SwiftKey3 error " unable to load language packs". Keyboard still OK. I have xperia x10 mini rooted running android 2.1 E10i.
Click to expand...
Click to collapse
Well, after getting other errors such as "no enough space" from Platinum Backup (there was a space on SD Card), I had to go to Format the SD after copying everything. Then I copied back the important folder the SD. I also had to reinstall SwiftKey. Now everything is fine and no data loss.
SD card Checking for errors
sajjji said:
your phone should rooted
then download and install root explorer
in the root explorer go to
system /bin
and delete fsck_msdos
now reboot your phone
Click to expand...
Click to collapse
Well I will try to backup and format it.... If it works then good if not then I will have to root my LG P880 .
My Problem is "preparing external sd card checking for errors" now that error is not showing while following above steps but now when i click my memory card that is not opening and after opened my memory card my internal device memory also not opening .
baka.yarou said:
Hi all,
I have a problem with my G1, running on latest Cyanogen mod. After restarting the card cannot be read and it is seems to be checking the sd card, if it really happens I dunno. What is weird is that I can access the card from recovery mode (shell), and it is not damaged (at least the windows doesn't detect damage while it is in the card reader. So that implies that the problem might be in the Android system.. anybody has a clue how to solve this? Thanks a lot.
Edit: solved it, deleted fsck_msdos from bin and it works flawlessly again
Click to expand...
Click to collapse
Simple fix, Difficult decision. Remove SD Card from slot then Factory reset phone. Once it comes too just go through all steps to setting up device then reinsert the SD Card into the slot. BOOM!
thank you very very much it worked for me
baka.yarou said:
Hi all,
I have a problem with my G1, running on latest Cyanogen mod. After restarting the card cannot be read and it is seems to be checking the sd card, if it really happens I dunno. What is weird is that I can access the card from recovery mode (shell), and it is not damaged (at least the windows doesn't detect damage while it is in the card reader. So that implies that the problem might be in the Android system.. anybody has a clue how to solve this? Thanks a lot.
Edit: solved it, deleted fsck_msdos from bin and it works flawlessly again
Click to expand...
Click to collapse
thank you so much but it is read only please help
yeah...
supremeteam256 said:
Can always wipe and reflash. Or if you have another sd card laying around and put that in to see if it recognizes it.
Click to expand...
Click to collapse
i am having same issue i always changes roms please can you halp me..
still not working mine is lenovo K3 Note And my Phone is rooted. It is showing Preparing SD card checking for errors
Didn't work for me.
Hard reset don't work.
Delete the fsck.msdos but don't work.
The fsck.msdos file comes on every wipe back.
I think this is a cm issue.
On stock no problems with my external sd card on my HTC One M8.
I'm going crazy...
No need to go to bin.. just put ur SD card in other mobile.. it will show fcsk files when u open the SD card.. just delete those files. Then remove the SD card and put it back in Ur mobile.. Then restart it mobile.. problem solved..,,,
Anitha Sivakumar said:
No need to go to bin.. just put ur SD card in other mobile.. it will show fcsk files when u open the SD card.. just delete those files. Then remove the SD card and put it back in Ur mobile.. Then restart it mobile.. problem solved..,,,
Click to expand...
Click to collapse
ive deleted the fcsk file on bin
the notif "preparing sd card" was gone but another problem occured, i cant even open my storage, ext sd card and even internal card ive tried your solution, ive put my sd card on another device, i cant find any fcsk files that you mention i cant even delete any file from my card using another mobile :crying::crying::crying:
It worked.... Thanks bro..
:good:
sajjji said:
your phone should rooted
then download and install root explorer
in the root explorer go to
system /bin
and delete fsck_msdos
now reboot your phone
Click to expand...
Click to collapse
sajjji said:
your phone should rooted
then download and install root explorer
in the root explorer go to
system /bin
and delete fsck_msdos
now reboot your phone
Click to expand...
Click to collapse
Bloody Brilliant. I have no idea why I could not find this solution two years ago. I have spent several hours searching for this solution, several times. In my case, I needed to remove the fsck.exfat file in the /system/bin folder.
My attention span is extremely short. I have been living with a 3 to 4-minute card scan for a 256GB microSD in my Samsung Note 3 for two and a half years. For all of the reboots I have done (which must be near a thousand, if that's not severely underestimated) I have had to deal with waiting to use my phone. I can't tell you how discouraging it has been to have such a powerful, useful device crippled by such a stupid flaw: that of checking the SD card that you rarely remove, for errors, every single time the phone is rebooted, even after graceful reboots called by the "proper" methods.
I can't tell you how many times I have rebooted my phone, only to forget the reason I rebooted it, because my phone took 4 minutes to reboot.
Productivity to the cubed-root.Pisses me off.
Someone who has more voice than me please get the Android People to change this. As of Nougat, this is still the default behavior. How can an organization be so stupid...? I have no doubt that just this flaw has sent many people to the Apple camps. Who the cuff in their right mind would want to deal with such a hassle?? Are they seriously unaware of the trend for people to actually believe that their devices, machines and technology ought to be doing things faster than previous generations?
(Please just take the following cynicism with a grain of salt. I just learned the above fix, something I really should have figured out a long time ago/kicking myself!!) :crying:
For the anally-inverted who might bring up the obvious argument that your phone will no longer be able to detect or fix corruption, all that needs to be done is the following:
1) move the fsck.exfat (or whatever the formatting) file to a different folder. In my case I moved it to the /data folder
2) use some delay scripting program that will symlink the fsck.exfat file to a tmpfs location say, 30 seconds after boot; or longer if needed. This intermediary step is necessary in order to create a temporary symlink, which will be nonexistent upon reboot.. If we didn't create a temporary symlink, the fsck.exfat command would be immediately available after each reboot (which we don't want) because symlinks are normally permanent. Therefore, this step will need to be run after every reboot (but again, time-delayed).
3) the last command is to create another symlink, linking the tmpfs fsck.exfat symlink created in the last step back to the /system/bin folder (or wherever it originally resided). So this is a symlink of another symlink. This step actually should only need to be done once, since this symlink should remain after reboot, even though it is initially broken upon reboot until the previous command recreates the intermediary symlink. It should become effective again when the previous step is run by the time-delayed scripting program.
Now your phone has the ability to check the card upon you calling the fsck.exfat routine through normal means, one of which can just be a simple unmount -> mount request from the Android system settings . Your card won't be needlessly fsck-checked to death every bloody time you reboot your phone.
(If you found this tutorial helpful and desire to quote or improve upon it, please cite/credit me for the inspiration! It came through much effort and learning!)
Well day one is over and I think I might have the first bricked NC. I used CWR to flash this ROM:
http://forum.xda-developers.com/showthread.php?t=932211
I kept getting a keyboard input error and it never worked correctly. I've been reading nonstop through the forum and now my NC won't turn on.
I look through the thread again, only to find out that it is locked and in red letters it now says "just keep away from the SDcard formatting option in settings." Anyone want to guess what I did before I read that? Yup, I formatted the SD card through settings.
It says to use a certain file to flash boot again but I have no idea how to do that if the thing won't even turn on. Does anyone have any suggestions? I can't post in the thread because it is locked.
MY NOOK IS ALIVE AGAIN!!!!!!!!
Not sure what all I did but it's up and running again. I started with the partition file mentioned in the closed thread. I then did a full restore to 1.0. This then lead me to a boot loop with the grey N screen. From there I re-rooted and it almost loaded. After that I did the power +N button and it reinstalled 1.0 for me. I have since rooted the NC and am leaving it as is until Cyanogen comes out with their ROM.
you made a big mistake by starting off with that flash to emmc rom. You should have started with rooting the original firmware.
Try this to get back to stock.http://forum.xda-developers.com/showthread.php?t=931720
If this doesnt work use my fool proof guide here:
Code:
http://mrm3.net/2011/01/24/113/
I rooted the NC using Huskermania's video on YouTube. I should have left well enough alone but seeing all the videos of 2.2, I wanted it as well.
Thanks you for the link. I plan to follow every step later in the day, after get some rest and relieve some stress. My only worry is, will the Nook turn on after I pop in the SD card and how long do I hold the power button before I give up?
I'm familiar with rooting and flashing phones, I am currently running CM-6.1 on an Evo and a Hero without any problems. Before that I messed with everything from the PPC-6601 to the TREO 800W.
try this:
http://forum.xda-developers.com/showpost.php?p=10965703&postcount=31
maybe it's like the root sd and you just need to let it run without any on screen indicators. you could pm him and see if he can offer any help.
good luck.
So I've read through everything and when I installed the SDK I had issues with my PC and getting the drivers to load. I didn't install them and went straight to flashing it, so no matter which guide I followed the driver install failed.
I'm now on a Mac and I'm installing the SDK. Any advice on how to take me from step #11 and on.? I can't seem to be able to find the Windows button fo some reason.
hi -- assuming you still need help, this CWR bootable SD saved me many times.
download this file (I think you may already have it)
http://dl.dropbox.com/u/2248236/froyo-eMMC-0.2.img
so open terminal in your mac and insert the microSD card into an sdcardreader or adapter. If you want to be extra safe open Disk Utility in the Utilities folder in Applications and erase the SD card.
then in terminal:
$ diskutil list
(figure out which /dev/disk# is the sd card)
$ diskutil unmountDisk /dev/disk#
$ dd if=/path/to/that/img/file/froyo-eMMC-0.2.img of=/dev/disk# bs=1m
(then wait an inordinate amount of time when terminal won't tell you anything and you think it is not doing anything... for it to image the sd card)
when it is done, it will tell you XXXXXX files in 0 files out
remove that SD from your computer and put it back in -- it should show up in finder as "Boot" and check to make sure a "restore to 1.0.1 zip" is on it -- if not, let me know, and I'll link you that file as well. You can just copy over that zip to the newly imaged SD card if it isn't there.
once you've got that SD card imaged with the complete-restore-1.0.1.zip on it as well, make sure your nook is unplugged and powered off -- I assume, just hold down the power button for like 10 seconds just to be safe. Put the microSD into the microSD slot and plug the nook into the computer -- that tells it to boot from SD.
you should enter Clockworkrecovery at which point you need to navigate the program with the vol up vol down power and home buttons (power is back, home is select) and go to the mount option and reformat system, then data, then boot. It always freezes on me after reformatting boot, so just power off and back on and it should return to CWM. Then go through the steps to flash that recovery zip that is on the sd card! Make sure you select "select zip from SD card" and you should be good to go.
good luck.
How to root your brand new Nook Color - For Noobs on windows - I'm sure this will all work from Mac too, but I do not have one so I don't know
-I know there are plenty of threads our there for this - but I figured I would compile my journey to root so that anyone slightly confused with the process of rooting, starting over and re-flashing stock nook, using root explorer is all in one area.
First things First - Without the Cyanogenmod team, everyone who has a hand in this at XDA, Dalingrin's overclock, everyone who compiled the files for recovery, Clockworkmod team, iomonster, everyone! This wouldn't be possible. Drop by their websites and buy them a beer or two.
Secondly - I am not responsible for any damage at all, if you don't follow simple instruction then too bad for you. Also, none of the above mentioned folks are responsible for any damage to your Nook Color (NC).
NOW FOR ROOT!!!
go to http://nookdevs.com/NookColor_Rooting and follow the instructions. Download the appropriate autonooter for your software version. (this can be checked on the nook by going to settings, device info, about nook)
Follow the helpful people at NookDevs instructions and thank them for their help!
After you achieve root you should see Market app in your extras tab in the Original Nook Software, This is good, if you don't go back and try again. Now pull out your card(dont forget to unmount and format) , and turn off your nook .
Let's Begin With CM7
First you will need to make yourself a bootable clockworkmod (CWM) to run your installation from -
download winimage for your PC - http://www.winimage.com/download.htm and install the appropriate file (obviously x86 for 32 bit PC, and x64 for 64 bit)
install it!
next download 7-Zip to extract the files!!! http://www.7-zip.org/
when installed go to tools/options/ and make sure tar is checked and gz is checked. You might as well select all!
Next download bootable clockwork image http://tsunade.net/nookdev/clockwork/0.1-ext4/
I used the 1GB one on my 8GB class 4 card. It burns faster and works just fine!
Burning Process!
First insure that your already formatted card is formatted by formatting again! woot for the word format! Next-
On a computer open win image
click ok!
plug in your microSD card
click on Disk tab
go down to restore virtual Hard Disk Image
Select your microSD
find the place you saved the image after extracting through 7zip (I saved to Desktop)
Click OK and it should start burning
after five minutes or so the image will be written to the microSD card
Now to install CM7!!!!!!!!!! Drop by their page if you want and donate some beer money!!!!
Download these files!
http://mirror.cyanogenmod.com/?device=encore&type=nightly (CM7 Encore ZIP - Get the latest one)
http://wiki.cyanogenmod.com/index.php?title=Latest_Version/Google_Apps (google apps file!!!!)
http://forum.xda-developers.com/showthread.php?t=925451] (Dalingrins!!!!! OVERCLOCK - even if you don't need this, you WANT THIS (my attempt at a jedi mind trick) just do it).
download the zip files and put them on that 1GB cwm bootable SD card you made!!, and copy the the zip files to the ROOT of the sd card i.e just drag and drop them into the sd card.
Now safely remove and plug the card in to the nook color
it will boot up into CWM - go to this page http://forum.xda-developers.com/showpost.php?p=11535969&postcount=151 and start at the installing section number 2!!! Thanks Faceman66 Only follow the install section and first boot section up until 2 if you have a DLINK router!!!! this is very important!!!! Once your done with the installation again, make sure to format the microSD card, do not use cyanogen it will mess everythin up, format it through your computer.
Dlink router connection issue!
The wifi in cyanogen just scans and disconnects constantly without connecting. Skip all of the first boot process like signing in to google, etc. Just get into the main screen of your new ROM. Connect it via USB to computer and "turn on USB storage" in the drop down notification bar.
Now preferably purchase the Root Explorer App on your phone or on your computer (you wont be able to access the nook color CM7 market yet. If you find it by other means I dont want to hear about it. if you download on your phone, download astro file manager as well, open astro file manager and click menu, tools, application backup. Find root explorer, back it up, pull it off your phone to the computer by searching the SD card for the "backups folder" and then drag and drop it onto your nook SD card. Use CM7 file explorer, find the APK and then install. Now using root explorer go to
/system/etc/wifi/ and find the tiwlan.ini file, at the top of the screen youll notice a button that says Mount R/W, click it. now press and hold on tiwlan.ini and open in text editor. go down about half way to find WifiAdhoc = 1 or something to that affect.
WiFiAdhoc is set to 1 on the cm7 builds but if you need change it to 0 for wpa/wpa2 will work.
Once that is set to 0, reboot, and connect to your internets.
WHAT IF I MESSED EVERYTHING UP AND MY NOOK COLOR IS BRICKED! IMPOSSIBLE! just follow these instructions!!!! Thanks to HittingSmoke over at addictive tips
This guide is broken and bricks the Nook. The problem is, it tells you to format /boot when you should NOT format boot.
If you have the black screen because of following this guide, here’s how to fix it:
Format your SD card and re burn that 1GB cwm image (It worked perfect for Me)
Next, download:
http://www.etoile-laconnex.com/nook-complete-restore-1.0.1.zip
and
http://www.multiupload.com/VEJFMO05BV
Copy them both to the SD card that you made with winImager.
Put in the SD card and hold the power button until it boots into recovery again.
Under Mounts and Storage, format /boot, /system, /data and /cache
Using the “Install zip from sdcard” option, flash “repartition-boot-with-stock.zip” THEN “nook-complete-restore-1.0.1.zip”
Take out the SD, reboot and you’ll be back to a working stock Nook.
After that, follow this guide:
http://forum.xda-developers.com/showpost.php?p=11535969&postcount=151
and/or go to the top to try again.
Note: Do NOT use your Nook to format the SD card after installing CM7. There’s a bug and it will format /boot instead, returning you to the black screen problem and you’ll have to repeat the process. This is TRUE WITH PHONES AND THE NOOK COLOR
Thanks again to everyone's contribution - I do not own the rights to any of this and am not the original finder/creator/designer of any of these tips and tricks.
Sorry you feel that way about Mac users. I will get the information from somewhere else.
Simply one of the best tutorials out there. So many of the custom roms overlook the documentation.
I am stuck on the boot logo ( the part where the android is being scribbled in directly after i plugged in the nook cable after first loading the sd card with winimage. It never goes past halfway on the scribble animation, and i am wondering if I may have done something wrong. Please reply.
You may need to go through the steps again to get it to work, it shouldnt hurt anything to do. Also try to write a different winimage and a different size download. If you have bigger than a 1gb card, i recommend getting the 1gb image file
first post on nook forum just order one after reading for 2 weeks about development cant wait to get it and use this guide to root it...
I'm guessing when you say format sd card your means fat 32 correct? Also once done with everything do you suggest to parition sd card to allow a2sd or data2ext? Our use titanium back up when updating rom...
I actually dont usually use titanium back up but if you want to partition and use titanium backup, cm 7 will defenitely support it. Format in fat 32 definitely. Luckily now CM7 has fixed the D-Link issue so you should be good on text editing and the whole process should be expedited alot with how hard Cyanogenmod team has worked to make a pretty flawless copy of CM7 for Encore (Nook Color). Im running CM7.02 and it is fast, sleek and sexy!
v/r
Drew
I tried this on my nook color and when it booted it showed the default nook icon with the adobe copyright warning, for a second, then it showed a cyanogen mod logo for a second then a screen that said install failed reboot to try again. I thing that some part of the nook android is still there and is messing up the CM install. Any ideas?
candreasen said:
I tried this on my nook color and when it booted it showed the default nook icon with the adobe copyright warning, for a second, then it showed a cyanogen mod logo for a second then a screen that said install failed reboot to try again. I thing that some part of the nook android is still there and is messing up the CM install. Any ideas?
Click to expand...
Click to collapse
First, what version is your Nook Color? These are outdated steps and files. Second, this is rooting (gaining superuser access and installing apps) and not installing CM7 or a custom rom. Can you tell us what exactly you did so we can try and help out more?
It is the BNRV200. I believe it had the latest BN firmware because I got it about 2 weeks ago.
drewbacca said:
Now to install CM7!!!!!!!!!!
Click to expand...
Click to collapse
This seems to say otherwise about the installing CM7.
candreasen said:
It is the BNRV200. I believe it had the latest BN firmware because I got it about 2 weeks ago.
This seems to say otherwise about the installing CM7.
Click to expand...
Click to collapse
If you're installing CM7, go here and read about the new partition guide since you probably have the new partition on yours.
http://forum.xda-developers.com/showthread.php?t=1030227
If you're rooting, go here. (You can also re-partition, go back to stock then root.)
http://forum.xda-developers.com/showthread.php?t=1054027
Hey, I have been looking for a beginner guide to root the nook hd. I am new to rooting so i really have no idea on what to do. I do have windows 8, so i don't know if that would be a problem. If any one knows how to root the nook hd and wants to help it might be easier to chat in Skype, and my Skype name is doodlebuy97. Thanks for your help!!!
P.S. I have looked up guides, but most of them are advanced guides....
SovietRussian said:
Hey, I have been looking for a beginner guide to root the nook hd. I am new to rooting so i really have no idea on what to do. I do have windows 8, so i don't know if that would be a problem. If any one knows how to root the nook hd and wants to help it might be easier to chat in Skype, and my Skype name is doodlebuy97. Thanks for your help!!!
P.S. I have looked up guides, but most of them are advanced guides....
Click to expand...
Click to collapse
By far, the easiest way to root is here: http://forum.xda-developers.com/showthread.php?t=2062613
You just need an SD card, a card reader, some software you download for burning the card, and the downloads in the thread.
Universal root is what is says.
Gapps refers to the Google Applications and Play Store is one of them
Unknown Sources lets you install files not from Barnes and Noble.
For now, ignore the other files until you get that working.
The nice thing is you can't brick your nook, worst case you just have to try to reboot 8 times to be back where you started.
Enjoy and welcome!
Thanks I'll see if this works for me!
dbh369 said:
By far, the easiest way to root is here: http://forum.xda-developers.com/showthread.php?t=2062613
You just need an SD card, a card reader, some software you download for burning the card, and the downloads in the thread.
Universal root is what is says.
Gapps refers to the Google Applications and Play Store is one of them
Unknown Sources lets you install files not from Barnes and Noble.
For now, ignore the other files until you get that working.
The nice thing is you can't brick your nook, worst case you just have to try to reboot 8 times to be back where you started.
Enjoy and welcome!
Click to expand...
Click to collapse
Ok i went to the site and found some of it a little confusing lol. I have everything you said i need accept the software you download for burning the card. I read most all of it, but i really didn't see any steps. Also I'm not good with there terminology like flash and ROM and stuff like that..
SovietRussian said:
Ok i went to the site and found some of it a little confusing lol. I have everything you said i need accept the software you download for burning the card. I read most all of it, but i really didn't see any steps. Also I'm not good with there terminology like flash and ROM and stuff like that..
Click to expand...
Click to collapse
What the site doesn't tell you is the order in which to flash. It's also a lot of info to decipher. Leapinlar has done an incredible job providing all of the resources and info needed. Here's what I did using that thread:
1. Follow the instructions in the thread for burning the cwm image to the sd card. There are easier instructions here that Someone0 posted:http://forum.xda-developers.com/showpost.php?p=34954992&postcount=132. Someone0's directions are for Win7, so it should be close to Win8.
2. Take the sd card out and reboot your Nook like normal.
3. Connect Nook to PC via USB and copy the Universal Root zip and the Gapps zip to your Nook internal storage (on top level so it will be easier to find.
4. Shut down and reinsert your burned sd card. Boot into recovery via power + volume up.
5. Once in cwm, don't hit the N button unless you want to select something. The power button is "nack" i think, but don't quote me on that. Navigate cwm to install the zip from internally storage. Make sure you find internal storage or you won't see any zips.
6. Once flashed, shut down, take out card, and reboot.
7. Discover the wonderful world of a rooted device.
Sent from my Nook HD
natefish said:
What the site doesn't tell you is the order in which to flash. It's also a lot of info to decipher. Leapinlar has done an incredible job providing all of the resources and info needed. Here's what I did using that thread:
1. Follow the instructions in the thread for burning the cwm image to the sd card. There are easier instructions here that Someone0 posted:http://forum.xda-developers.com/showpost.php?p=34954992&postcount=132. Someone0's directions are for Win7, so it should be close to Win8.
2. Take the sd card out and reboot your Nook like normal.
3. Connect Nook to PC via USB and copy the Universal Root zip and the Gapps zip to your Nook internal storage (on top level so it will be easier to find.
4. Shut down and reinsert your burned sd card. Boot into recovery via power + volume up.
5. Once in cwm, don't hit the N button unless you want to select something. The power button is "nack" i think, but don't quote me on that. Navigate cwm to install the zip from internally storage. Make sure you find internal storage or you won't see any zips.
6. Once flashed, shut down, take out card, and reboot.
7. Discover the wonderful world of a rooted device.
Sent from my Nook HD
Click to expand...
Click to collapse
Power button is Home (Top) I think.
You also need ADB running to copy the files over, no? Or are you copying to internal memory using MTP... Can you flash from there? I had just copied the zips to the card while it was in the card reader on the Windows machine. Then the zips are on the CWM card. After you are done, just do a nandroid backup with CWM too in case something gets borked later...
natefish said:
What the site doesn't tell you is the order in which to flash. It's also a lot of info to decipher. Leapinlar has done an incredible job providing all of the resources and info needed. Here's what I did using that thread:
1. Follow the instructions in the thread for burning the cwm image to the sd card. There are easier instructions here that Someone0 posted:http://forum.xda-developers.com/showpost.php?p=34954992&postcount=132. Someone0's directions are for Win7, so it should be close to Win8.
2. Take the sd card out and reboot your Nook like normal.
3. Connect Nook to PC via USB and copy the Universal Root zip and the Gapps zip to your Nook internal storage (on top level so it will be easier to find.
4. Shut down and reinsert your burned sd card. Boot into recovery via power + volume up.
5. Once in cwm, don't hit the N button unless you want to select something. The power button is "nack" i think, but don't quote me on that. Navigate cwm to install the zip from internally storage. Make sure you find internal storage or you won't see any zips.
6. Once flashed, shut down, take out card, and reboot.
7. Discover the wonderful world of a rooted device.
Sent from my Nook HD
Click to expand...
Click to collapse
Wow, you're talking about LeapinLar's Nook HD/HDplus Stock Root - via CWM flashable zips thread. Let me correct and clarify those steps a bit:
1. To burn an image to your sd card in Windows, download the win32diskimager-binary.zip, unzip, and run the exe. Write the unzipped CWM image file (be sure to use the one for your device) to the sd card in your computer/card reader. (The post linked to is for getting adb working which you don't need for this.)
2.-3. Leave the sd card in your computer after burning the CWM image and just copy the zips to it.
4. With your nook off put the sd card in and turn on (no need to press the volume up).
5. Once CWM starts up, install zips from sd card (vol + & - are up and down, n button is select, power is back to previous menu). Do the universal root first, then gapps.
6. After the zips are installed, take out the sd card and select reboot.
7. Look around these forums for more info on enjoying your rooted Nook!
lkmiller said:
Wow, you're talking about LeapinLar's Nook HD/HDplus Stock Root - via CWM flashable zips thread. Let me correct and clarify those steps a bit:
1. To burn an image to your sd card in Windows, download the win32diskimager-binary.zip, unzip, and run the exe. Write the unzipped CWM image file (be sure to use the one for your device) to the sd card in your computer/card reader. (The post linked to is for getting adb working which you don't need for this.)
2.-3. Leave the sd card in your computer after burning the CWM image and just copy the zips to it.
4. With your nook off put the sd card in and turn on (no need to press the volume up).
5. Once CWM starts up, install zips from sd card (vol + & - are up and down, n button is select, power is back to previous menu). Do the universal root first, then gapps.
6. After the zips are installed, take out the sd card and select reboot.
7. Look around these forums for more info on enjoying your rooted Nook!
Click to expand...
Click to collapse
I just reworked my instructions in that thread. After going through it in excruciating detail with SovietRussian, I concluded it needed revising. See if you think it is better.
Sent from my Nook HD+ Running CM10 on SD
leapinlar said:
I just reworked my instructions in that thread. After going through it in excruciating detail with SovietRussian, I concluded it needed revising. See if you think it is better.
Sent from my Nook HD+ Running CM10 on SD
Click to expand...
Click to collapse
They do look better. Honestly, they were pretty clear to me to begin with. But I do have previous experience with the Nookcolor. I just looked at natefish's instructions and thought he was making it a little harder then it had to be.
lkmiller said:
They do look better. Honestly, they were pretty clear to me to begin with. But I do have previous experience with the Nookcolor. I just looked at natefish's instructions and thought he was making it a little harder then it had to be.
Click to expand...
Click to collapse
Actually, I was just combining what others told me with that leapinlar was saying to do. What I wrote is what worked for me, so I was just trying to help.
Rooting by changing internal code
Been searching for something I stumbled along awhile back. It requires disassembling the Nook HD. My eyes are heavy from search. Supposedly there is another SD card in the nook and a few words need changing. Anyone recall were it is?
Hey, I got a Virgin Mobile HTC Desire 510. Y'know, the blue one....
I fudged up severely the other evening and installed another rom which bricked my phone. I did manage however restore a stock back-up I managed to find online, however the phone was still rooted, tampered and TWMP(did I get the abbreviation correct?) is still on it. So I go and install Supersu and Busybox in an attempt to go back to where I left off as I've been attempting to get the phone to do the internal to SD card bit but no success thus far, especially not right now. In anycase, after reinstalling Supersu, I load it up and get the message of "There is no SU binary installed and SuperSU cannot install it. This is a problem! If you just upraded to Android 4.3, you need to manually re-root. consult the relevant forums for your device.". I attempted to reinstall threw recovery and it seems to be working till I get the actual phone's Google ROM running and click on the SuperSU program only to get that message.
Any suggestions or advice on how to do this and get SuperSU back up? How do I exactly re-root or can I somehow install the binary via PC or flash?
Can the HTC Desire 510(Virgin Mobile version) even have the the script/rom/trick setting to have the SD Card used as Internal memory or is this quest just wasted time?
Thanks
EDIT- Device version is 0PCV1
Okkvltist said:
Hey, I got a Virgin Mobile HTC Desire 510. Y'know, the blue one....
I fudged up severely the other evening and installed another rom which bricked my phone. I did manage however restore a stock back-up I managed to find online, however the phone was still rooted, tampered and TWMP(did I get the abbreviation correct?) is still on it. So I go and install Supersu and Busybox in an attempt to go back to where I left off as I've been attempting to get the phone to do the internal to SD card bit but no success thus far, especially not right now. In anycase, after reinstalling Supersu, I load it up and get the message of "There is no SU binary installed and SuperSU cannot install it. This is a problem! If you just upraded to Android 4.3, you need to manually re-root. consult the relevant forums for your device.". I attempted to reinstall threw recovery and it seems to be working till I get the actual phone's Google ROM running and click on the SuperSU program only to get that message.
Any suggestions or advice on how to do this and get SuperSU back up? How do I exactly re-root or can I somehow install the binary via PC or flash?
Can the HTC Desire 510(Virgin Mobile version) even have the the script/rom/trick setting to have the SD Card used as Internal memory or is this quest just wasted time?
Thanks
EDIT- Device version is 0PCV1
Click to expand...
Click to collapse
Hello and welcome to xda,
Where exactly did you get the back-up from that you used to restore?
You were close it is TWRP or Team Win Recovery Project.
I believe the reason you can't install SuperSU is because you don't have a write protect removed kernel installed. You can find one here. Check out their related forums and see which one you like best. They are pretty much all great. Some aren't being supported anymore as a heads up. To flash a kernel, in case you didn't know how:
Go into Settings-About-Software information-More-Kernel version and write down the name of the Kernel
1. Power the phone down
2. Hold "Down" button then hold "Power" key while still holding "Down" button, until you get into the bootloader
3. Release "Down" and "Power" button
4. Tap "Power" key once and it will change from "HBOOT" in white letters with blue background to "FASTBOOT" in white letters with red background on your phone
5. Connect your USB cable and it will say "FASTBOOT USB" on your phone
6. Navigate to the folder you have your fastboot.exe from Android Studio or wherever you obtained it from (Mine is in C:\Users\myusername\Android\sdk\platform-tools)
7. Hold the "Shift" key then right click in any empty space in that folder
8. Select "Open command window here"
9. Type
Code:
fastboot devices
in the command window, then press Enter just to make sure it is picking up your phone
10. You should see something like:
Code:
HT42PXU89475 fastboot
if you don't make sure your USB cable is inserted all the way and you are in "FASTBOOT USB"
11. Make sure your recovery.img or whatever the name of the recovery is, is in the folder you are currently in
11. Type
Code:
fastboot flash boot boot.img
in the command window
You should see something like:
Code:
C:\Users\yourusername\Android\sdk\platform-tools>fastboot flash boot boot.img
sending 'boot' (12932 KB)...
OKAY [ 1.350s]
writing 'boot'...
OKAY [ 1.030s]
finished. total time: 2.385s
Your phone will still be in FASTBOOT USB mode
To test it out to see it was correctly flashed, reboot the phone
Go into Settings-About-Software information-More-Kernel version and see that the version changed
You can follow my little guide to use SD as Internal memory. Let me know if you need any help.
I won't be able to get to this til tomorrow but another issue is I can't d/l apps off Google play. It comes up with some server issue and some weird code that starts with an R. Sorry I can't give full details as I'm at work :/.
Okkvltist said:
I won't be able to get to this til tomorrow but another issue is I can't d/l apps off Google play. It comes up with some server issue and some weird code that starts with an R. Sorry I can't give full details as I'm at work :/.
Click to expand...
Click to collapse
Is your phone completely stock or do you have any custom ROMs? I have seen errors like that.
blaqueknight said:
Is your phone completely stock or do you have any custom ROMs? I have seen errors like that.
Click to expand...
Click to collapse
I'm fairly certain I reinstalled Busybox when I was installing(or trying to) Supersu. I'm giving the kernel bit a shot.
Oh the stock back-up is this(No, I didn't back up my phone since I didn't see a reason, I had everything I needed on the computer/sd) file:
http//qc-.androidfilehost-com/dl/PObYV5uN55P2PGDNrX1pLQ/1430391523/95832962473396445/2014-12-02--16-24-34+KOT49H+Stock.not.rooted.rar
(can't post links since i'm a newb)
Had to make a backup of my empty phone and put the files into the empty back up to restore it.
UPDATE- Flashed over Modded Kernel V2.6.1 since that looked like a safe bet. Installed correctly. Tried to reinstall Supersu. Got "Android is upgrading". Supersu Installed. Next is the SD Card bit.
Okkvltist said:
I'm fairly certain I reinstalled Busybox when I was installing(or trying to) Supersu. I'm giving the kernel bit a shot.
Oh the stock back-up is this(No, I didn't back up my phone since I didn't see a reason, I had everything I needed on the computer/sd) file:
http//qc-.androidfilehost-com/dl/PObYV5uN55P2PGDNrX1pLQ/1430391523/95832962473396445/2014-12-02--16-24-34+KOT49H+Stock.not.rooted.rar
(can't post links since i'm a newb)
Had to make a backup of my empty phone and put the files into the empty back up to restore it.
Click to expand...
Click to collapse
I'm sorry, please disregard that last comment. I was posting like your only problem was the Play Store. lol Sorry. But yea, check out those things I mentioned to you and you should be able to get SuperSU back up, if not I'll help you with anything else.
Okkvltist said:
I'm fairly certain I reinstalled Busybox when I was installing(or trying to) Supersu. I'm giving the kernel bit a shot.
Oh the stock back-up is this(No, I didn't back up my phone since I didn't see a reason, I had everything I needed on the computer/sd) file:
http//qc-.androidfilehost-com/dl/PObYV5uN55P2PGDNrX1pLQ/1430391523/95832962473396445/2014-12-02--16-24-34+KOT49H+Stock.not.rooted.rar
(can't post links since i'm a newb)
Had to make a backup of my empty phone and put the files into the empty back up to restore it.
UPDATE- Flashed over Modded Kernel V2.6.1 since that looked like a safe bet. Installed correctly. Tried to reinstall Supersu. Got "Android is upgrading". Supersu Installed. Next is the SD Card bit.
Click to expand...
Click to collapse
UPDATE 2- When partioning the sd card, it continues to come up as ext2. When I go into Link2SD and I go to select I get the message on whatever I select- "Mount script cannot be created. mount: invalid argument"
Okkvltist said:
UPDATE 2- When partioning the sd card, it continues to come up as ext2. When I go into Link2SD and I go to select I get the message on whatever I select- "Mount script cannot be created. mount: invalid argument"
Click to expand...
Click to collapse
Are you using Aparted? What was the method you used to partition? You should partition as ext4.
Yeah, I downloaded Aparted, went in to partition the SD card("8" gigs) and selected ext4 but it comes out ext2. Do I need S-OFF and/or 4EXT Recovery?
Okkvltist said:
Yeah, I downloaded Aparted, went in to partition the SD card("8" gigs) and selected ext4 but it comes out ext2. Do I need S-OFF and/or 4EXT Recovery?
Click to expand...
Click to collapse
Did you select Create then Format? If it still comes out ext2 after that, I don't know what the problem is. Format will take a while because it is creating journals.
blaqueknight said:
Did you select Create then Format? If it still comes out ext2 after that, I don't know what the problem is. Format will take a while because it is creating journals.
Click to expand...
Click to collapse
It's saying the partition doesn't exist when I go to format after creating the partition. Even when creating the proper ext from the create screen, it still doesn't come up as ext4.
other info
device- /dev/block/mmcblk1.
when I opened up link2sd its asking me for mmcblk1p2 but there is no mmcblk1p2
Okkvltist said:
It's saying the partition doesn't exist when I go to format after creating the partition. Even when creating the proper ext from the create screen, it still doesn't come up as ext4.
other info
device- /dev/block/mmcblk1.
when I opened up link2sd its asking me for mmcblk1p2 but there is no mmcblk1p2
Click to expand...
Click to collapse
Are you trying to partition the whole SDcard as ext4? To properly partition the card to be used with Link2SD you have to:
1. Delete the sdcard
2. Create a FAT32 partition of any size of your choosing
3. Format the FAT32 partition
4. Create an ext4 partition of any size of your choosing
5. Format the ext4 partition (this will take a long time, as it will create journals that are used to recover from an error such as removing the device while files are being copied)
After following those steps, Link2SD should properly create the script/mount and you should be able to link to your sdcard
If you are doing those steps perfectly and you still have an error, we have to find out another solution
Ok, I still can't get it to make Ext4......
However, weirdness- I made a Fat32 Partition and went into Link2SD. Link2SD was able to use/read the Fat32 partition. Tried to create/change the Fat32 and it didn't work. Tried to make a third partition under ext4 and it comes up ext2. Openned Link2SD and it doesn't read/use the ext2. Uses the additional Fat32 no sweat. I don't know how much of it is working(tried downloading Brave Frontier and had to delete loads of stuff in general) usual memory bull**** ensures and I see theres a lock for the full copy of Link2SD....
another thing; I can't get into/mount the open part of my SD card. Should I go back to square one or should I blow the meager 3 bucks for the full copy and see if I can do it from there?
PS- Does the class of the sd decide on if I can partition an ext3-4? Cause if so, mine is only a class 4 SD card.
Okkvltist said:
Ok, I still can't get it to make Ext4......
However, weirdness- I made a Fat32 Partition and went into Link2SD. Link2SD was able to use/read the Fat32 partition. Tried to create/change the Fat32 and it didn't work. Tried to make a third partition under ext4 and it comes up ext2. Openned Link2SD and it doesn't read/use the ext2. Uses the additional Fat32 no sweat. I don't know how much of it is working(tried downloading Brave Frontier and had to delete loads of stuff in general) usual memory bull**** ensures and I see theres a lock for the full copy of Link2SD....
another thing; I can't get into/mount the open part of my SD card. Should I go back to square one or should I blow the meager 3 bucks for the full copy and see if I can do it from there?
PS- Does the class of the sd decide on if I can partition an ext3-4? Cause if so, mine is only a class 4 SD card.
Click to expand...
Click to collapse
I just made a couple of very simple tutorials to use Aparted and Link2SD and they are both working for me. Check them out: Aparted tutorial, Link2SD tutorial. I believe the ext2 that you are talking about is around the 10 second mark in the Link2SD video. Do you mean the /data/sdext2? That is just the name of the second sdcard partition.
If you can, you should buy the full copy of Link2SD to link external data and whatever other options become available.
The class of sdcard shouldn't have anything to do with the partition. That's just a classification of the speed of the card.
If needed, I'll make more videos to show exactly how everything is done. I think sometimes it is better to show than simply explain how something is done.
Hope this helps.
Wow.......I mean seriously, holy zen, it worked.
I had to start over from scratch since my f'ling screwed so much crap up but after everything was reinstalled and flashed and what not, It made the ext4. I don't know why the programming is so touchy you have to create it threw such weird steps but I believe it worked. Upgraded the link2sd. Next question and I'm pretty sure on the answer- Are you able to remove the SD card or is it perma-bound to the phone(IE- if I change SD cards around, will everything crash?)? Thank you so much
Okkvltist said:
Wow.......I mean seriously, holy zen, it worked.
I had to start over from scratch since my f'ling screwed so much crap up but after everything was reinstalled and flashed and what not, It made the ext4. I don't know why the programming is so touchy you have to create it threw such weird steps but I believe it worked. Upgraded the link2sd. Next question and I'm pretty sure on the answer- Are you able to remove the SD card or is it perma-bound to the phone(IE- if I change SD cards around, will everything crash?)? Thank you so much
Click to expand...
Click to collapse
I'm happy it worked out good for you.
Yes, you are able to remove your sdcard. Be aware that your apps are on your sdcard so if you remove it, you remove them. They are placed on your sdcard and symlinked so Android thinks they are still on your phone in the place they would normally be. Nothing should crash, they just shouldn't show up. There is some great info about Link2SD here.
@blaqueknight..
nice videos man.