I made it for all of you who prefer to have their Android to be installed on SD card.
What do we need:
SD card with ext2 as a second partition (I believe that most of you know how to use gparted or any other linux partition manager)
filesystem: http://www.2shared.com/file/8p5Ci18r/SDAndroid.html
fota (the same as in Shodow's tut, so if you have this, there is no need to reflash it)
Step 1
Unzip downloaded filesystem.
Step 2a
Copy the "galaxyboot" folder into internal memory of your phone (or, as Shadow named it "Bada root").
Step2b
Copy the content of "filesystem" folder into ext2 partition on your card.
Step3
Open the terminal in this directory and type:
sudo chmod -R 0777 ./*
sudo sync
Step4
Unplug your sd card and boot by pressing start call button + on/off button.
Of course, all those steps must be done under Linux.
For those who do not have custom fota flashed:
Step5
Under Windows open Multiloader, select LSI, serach for fota and download it to your phone.
This is mixed version of first version of Android port and the filesystem posted by mylove90. It provides all functions which the newest version of Android from Shadow's tutorial has.
Great thanks to Bedson from bada-os.info for keeping all the old files.
Would this port still have "easy crash" after several reboot?
*yet again mumbles something about the annoyances of more than one tutorial*
part of the reason we moved to the scripted moviNAND version is because people time and again have difficulty running commands on a Linux commandline, if someone wants to create more tutorials it would be preferred that their filesystems have chmodding and partitioning scripted requiring no user intervention through a Linux distro, if possible.
EDIT: also be prepared to answer questions and to make it known that your tutorial isn't dev-created and thus for people following it to not PM devs asking why it won't work
@nbates66
As you said, the version for movinand is a way more simple to apply. On the other hand using this version is meant to be only for those with fast small files write on their SD card (fast, i mean aroud 1 - 2MB for 4KB Q1, where most of cards are about 0,01 - 0,04MB).
And there is one more thing... Bada 2.0 which made this section a bit less popular within couple of last weeks (and I think this won't change till Oleg give us new version).
@NitramNach
The entire process hasn't been changed when compared to the old version from Shadow's TUT, so it might be as unstable as you said. I think it's rather the matter of SD card, cause I haven't crashed my phone yet.
I'm using Class 4 Sandisk SDSDQM-032G-B35, but it's like rebranded Class 2 (9MB sequential read, about 5,5MB sequential write, 1MB random 4KB Q1 read, and 2MB random 4KB Q1 write).
i'm sorry, so may i ask, it means it's stable now?
does installing android on sd card will affect the already presend bada in the phone by any way ?
am asking this becoz am very very newbie,,, never tried flashing and dont want to have the risk of flashing ,,, so , if this way dont affect the already presend bada 1.2 in the phone , i may try to install android on sd card coz really want to c android on my s8500 ...
my firmware is jpkc1 ....
@chriszue
It depend on that what do you mean by stable.
It's the same version as published by devs in Shadow's tut, but this one is prepaired to be installed on SD card.
Though the speed and stability depends on your card I can say that I've used it for 4 days without any problem.
Now I'm using Bada 2.0, so I had to resign of Android.
@sarmoodi
Nor this or the version presented on Shadow's tut have any influence to Bada.
But if, you're not familiar with linux I suggest using the movinand version.
@Qron
thanx alot for the super fast reply..
Was the microphone working in this version?
Dude I want u r help...
i compare galaxy 3 and wave 723 and they are almost got same things..>
so i m thinking about about port galaxy 3 android froyo on wave 723 is that possible to do?
if wave 2 can run android they y not wave 723?
I'm not capable to help you. I simply made a conversion of newest filesystem so it could be installed on SD card. Nothing less, nothing more. I don't have proper knowledge to make any port.
what do you meaning by "It provides all functions"?
can you make calls on this methods?
Are You kidding me??
You rip this out of context. The whole sentense was "It provides all functions which the newest version of Android from Shadow's tutorial has."
So NO!, you can not make calls using this method.
Terminal commands
I cannot access the ext2 partition through the terminal and execute sudo chmod -R 0777 ./* and
sudo sync, that is I cannot find the folder in the FileSystem where Ubuntu places the mounted partitions. Could you tell me how to do this?
I have Ubuntu 11 installed through wubi if that makes any difference.
10x in advance
Root
It would be really helpful if someone could give the syntax for rooting froyo for this SD card version.
rohitman said:
It would be really helpful if someone could give the syntax for rooting froyo for this SD card version.
Click to expand...
Click to collapse
chmod -v -R 4755 ./system/xbin/*
badelemental said:
chmod -v -R 4755 ./system/xbin/*
Click to expand...
Click to collapse
Thanks for the reply.
I've come up with another problem though, On starting Market a white screen opens & the market closes, no message though.
Should I reinstall Android to fix the problem ?
rohitman said:
Thanks for the reply.
I've come up with another problem though, On starting Market a white screen opens & the market closes, no message though.
Should I reinstall Android to fix the problem ?
Click to expand...
Click to collapse
Yes, give it a try, as far as I'm aware it should work. Maybe the installation went a little wrong, probably nothing to do with you ^^.
Hope I've helped.
i followed all the steps several times and my phone keeps hanging at galaxy s screen.
any idea of what im doing wrong?already tried ext2 and ext3.
I am unable to use the touchscreen functionality properly in android on bada. I have loaded on SD card dual boot with Bada 2.0.
I am finding difficulty in scrolling or long-press (to create shortcut in home screen) or play "angry bird" , I cannot pull and hold the catapult.
Is there any workaround ? Have others faced this problem ?
Related
Hi there, i was trying to run Debian on my pro, but i cant install it! i try two methods, the Linux installer Beta 1.7 (say kernel dosnt have ext and loop support) and the SU terminal emulator way (cant chmod to 4755 any file, even using the su command - from here: http://www.talkandroid.com/android-forums/android-development/1091-install-debian-android.html )...
My pro is ROOTED with latest z4root, i even do a factory repair with pc companion...
Any advice???
Regards!
I tried this as well... no loop is no loop ( required for chroot type runs )
works on a Samsung i5700 I have at work tho...
thnx for the reply, so i can add loop and the ext thing? or we need a custom kernel? , what rom have the samsung?, in other hand i dont know why i cant chmod the files, even using root explorer! regards...
needs a new kernel yes.
i5700 is running samdroid cooked ( forget which version, but added multitouch )
damn :/
now why i cant chmod the files using su terminal emulator or root explorer? maybe is because my sdcard is formated in fat32, regards!
fat32 knows nothing about *nix style permissions, in a way though... all files on a fat32 are set 0777, but not really... heh
For what it's worth, I've just had Debian running in a chroot on my X10 Mini Pro, using the instructions at talkandroid.com, as mentioned by the original poster. Sorry, but as a new poster, I'm not allowed to link directly to those directions. This is with stock ROM, upgraded to Android 2.1, rooted with SuperOneClick.
A few modifications are necessary to make it work. I'm going to try to describe what I've done, but I am working backwards, so it's entirely possible that I'll leave something out and you could suffer disastrous consequences. So please be sure you back up all crucial data before proceeding, and be prepared to accept the possibility that your phone could be destroyed in the process.
First of all, the instructions tell you to run scripts from your SD card, which isn't going to work unless the card has a partition with a Linux-compatible file system. I suggest following the directions as far as step 4. Then replace the "bootdeb" file in the "debian" directory with the modified version attached to this post. Rename it "bootdeb". Then you will have to run the following commands manually, preferably using adb shell, but it can be done in a terminal on the phone. Either way, using the ash shell helps by providing command completion and history.
As root (su):
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock0 /system
mkdir /data/local/mnt
cd /sdcard/debian
cp bootdeb /data/local/bin #note: you may need to mkdir /data/local/bin first
cd /data/local/bin/
chmod 4777 bootdeb
You should now be able to run the bootdeb script to start up Debian.
The installation file says, "Be sure to run /scripts/onetime.sh as root from the shell after your FIRST 'boot'." This will prompt you to set a root password.
At this point, the Debian installation is command line only and root only. The image file needs to be resized before much can be added.
The other files in the Debian directory may be useful, but they all need to be modified before they can be used.
This is only a beginning. I don't know that I'm likely to get very far with it, so anyone else who's inclined to jump in and make this work better is welcome to do so!
edit: correcting grammatical error
Just in case anyone else shares my obsession -- I mean interest in getting Debian to run on an X10 Mini Pro, I thought I should report my progress. Or lack thereof.
Actually, as I said in the previous post, command line Debian works, and that's a lot of power to have available. But it would be nice to get X working, despite the lack of video drivers.
There's a lot of information out there about setting up X with a VNC server on an Android phone, then running a VNC client to access the graphic environment. The source of most accounts seems to be a thread at the androidfanatic forums, with the title "Gnome, KDE, IceWM or LXDE Desktop on your Android!"
(Sorry, I'm still too new at this to be allowed to post links, so this is the only way I can indicate where to find the information.)
I've tried lots of variations on those directions, trying to adapt them to the X10 Mini Pro. And I've had a little success. I can get to the Icewm or LXDE desktop and run the terminal program, but I can't start any programs that use X. Invariably, I get this error:
Error: Can't open display: :1.0
I've run out of ideas, so I'm taking a break from the project. If anyone else is interested enough to try, good luck to you!
For what it's worth, the most recent and comprehensive account of running Debian with X on Android phones appears to be at lanrat.com, in the "android" directory, filename "debian".
@RobbH
Very interesting! I'm waiting a new 8gb card so that I try it! Should you come up with any new progress please report here
This is a very short guide for all of you looking to dual boot android from the sd card now that you have windows phone 7 taking up the nand space. It's originally posted by letama and I added a bit to it.
It's actually quite simple. All you have to do is add nand_init to one line in the init.rc file. For most builds, you will need to use a linux distro and mount the rootfs.img file, then edit the init rc file, add nand_init to this line:
Code:
service ril-daemon /system/bin/rild -l /system/lib/libhtc_ril_wrapper.so -- -d /dev/smd0
so it looks like this
Code:
service ril-daemon /system/bin/rild -l /system/lib/libhtc_ril_wrapper.so -- -d /dev/smd0 nand_init
For builds that uses the cedesmith initrd method, you have to mount the system.ext2 file, everything else is the same.
Save your file. Make sure you haven't changed the permissions and unmount the image. Copy the build to your microsd, set magldr to boot from the directory you copied it to and boot ad sd, you should be good to go.
Problems: booting it this way does not read from your startup.txt, you have to wait for cotulla to add it in future magldr. I'm not sure if the old method of updating (dumping everything in a folder named root) still works.
Disclaimer: I've tried this with jdms, hd2one, superram, desire_hd2 and mdj rEVOlution 2.3 and they all work fine with my old data image, your mileage may vary. This is a very quick guide because that's all I know Anymore I'll have to search google, so you might as well do that yourself Anyone who have a better method of editing feel free to post it. I'll add it here if you post it in this thread.
Tip from aled99 to edit without linux.
Corias said:
I've managed to mount system.ext2 to Windows 7. Without VM and Linux at all.
What tools are needed:
1. Windows Ext2/Ext3 driver. You can get it from here.
2. Any software to mount image to virtual drive. I've used Gizmo Drive, but there are others also working.
Tip: Gizmo doesn't show ext2 as supportable image type, when you browse for image. So, manually type *.* filter.
Click to expand...
Click to collapse
Some files that are already edited:
CoreDroid HD 0.4 edited by ricola7
Desire_hd2 system.ext2 file
HD2ONE 0.3.5 system.ext2
JDMS 1.62
MDJ HD v4.6
MDJ rEVOlution 2.3 rootfs.img
NexusHD2-FRG83D v1.8 from nzxtneo
Superram 1.5 from letama
Builds that already work with magldr:
DL DesireZ v2.2 from dandiest
HD2 Gingerbread/CyanogenMod7 from copenhagen
Is this a method to boot a NAND Rom from SD Card without flashing?
blax123 said:
Is this a method to boot a NAND Rom from SD Card without flashing?
Click to expand...
Click to collapse
No it boots the sd builds from this subforum. Not the nand builds.
will this work if I have android in my nand, and want to run a different android off of sd card? Like if I wanna test drive gingerbread roms off the sd, while sticking with a froyo based rom in nand? I really want to do this.
izzy spun said:
will this work if I have android in my nand, and want to run a different android off of sd card? Like if I wanna test drive gingerbread roms off the sd, while sticking with a froyo based rom in nand? I really want to do this.
Click to expand...
Click to collapse
I haven't tried copenhagen's build but it should work the same way. Try it and let us know how it worked out
Edit: Actually I got curious and checked it out. Copenhagen's build does not require editing. You can boot it from sd using magldr as it is. Nice too. I think I'll play with that for a while
Sorry but I'm stuck on the first line. What is a linux distro? How do I edit the line? I'll be able to take care of the rest. This is the part that confuses me.
buzz killington said:
This is a very short guide for all of you looking to dual boot android from the sd card now that you have windows phone 7 taking up the nand space. It's originally posted by letama and I added a bit to it.
It's actually quite simple. All you have to do is add nand_init to one line in the init.rc file. For most builds, you will need to use a linux distro and mount the rootfs.img file, then edit the init rc file, add nand_init to this line:
Code:
service ril-daemon /system/bin/rild -l /system/lib/libhtc_ril_wrapper.so -- -d /dev/smd0
so it looks like this
Code:
service ril-daemon /system/bin/rild -l /system/lib/libhtc_ril_wrapper.so -- -d /dev/smd0 nand_init
For builds that uses the cedesmith initrd method, you have to mount the system.ext2 file, everything else is the same.
Save your file. Make sure you haven't changed the permissions and unmount the image. Copy the build to your microsd, set magldr to boot from the directory you copied it to and boot ad sd, you should be good to go.
Problems: booting it this way does not read from your startup.txt, you have to wait for cotulla to add it in future magldr. I'm not sure if the old method of updating (dumping everything in a folder named root) still works.
Disclaimer: I've tried this with jdms, hd2one, superram, desire_hd2 and mdj rEVOlution 2.3 and they all work fine with my old data image, your mileage may vary. This is a very quick guide because that's all I know Anymore I'll have to search google, so you might as well do that yourself Anyone who have a better method of editing feel free to post it. I'll add it here if you post it in this thread.
Click to expand...
Click to collapse
thanks.. so i must use linux? any tools available in win?
buzz killington said:
I haven't tried copenhagen's build but it should work the same way. Try it and let us know how it worked out
Edit: Actually I got curious and checked it out. Copenhagen's build does not require editing. You can boot it from sd using magldr as it is. Nice too. I think I'll play with that for a while
Click to expand...
Click to collapse
can you elaborate on this please.
can you give a step by step.
i am real interested in trying this.
thanks in advance.
Anthonayy said:
Sorry but I'm stuck on the first line. What is a linux distro? How do I edit the line? I'll be able to take care of the rest. This is the part that confuses me.
Click to expand...
Click to collapse
It's just short for Linux distribution, such as ubuntu or redhat. I used ubuntu. Once you have it mounted you can use any text editor available.
vista1984 said:
thanks.. so i must use linux? any tools available in win?
Click to expand...
Click to collapse
Sorry, I don't know if there are. Maybe others can chime in. Anything that'll let you mount an ext2 image and edit its contents will do. Unfortunately I'm not familiar with any windows tools.
Will this hack enable me to run Android from my SD card, with WP7 installed on the phone?
I just want to make sure, because I've been searching around, and several indidual sources have said that WP7 doesn't recognize any SD cards, including compatible SD cards.
I would really love to try WP7, but without losing my android.
Sent from my HTC HD2 using XDA App
WOOZ!E said:
Will this hack enable me to run Android from my SD card, with WP7 installed on the phone?
I just want to make sure, because I've been searching around, and several indidual sources have said that WP7 doesn't recognize any SD cards, including compatible SD cards.
I would really love to try WP7, but without losing my android.
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
Dude, it has nothing to do with WP7, You boot Android from MAGLDR not WP7. So you would either use a different SD card to boot into Android BEFORE booting windows or you would partition your SD card in a way that it allows you to use it for WP7 and Android at same time.
How can I mount the system.ext2 by using terminal?
Code:
[email protected]# mount -o loop system.ext2 /mnt
system.ext2: No such file or directory
asdfg2010 said:
How can I mount the system.ext2 by using terminal?
Code:
[email protected]# mount -o loop system.ext2 /mnt
system.ext2: No such file or directory
Click to expand...
Click to collapse
you have to specify where your file is and I believe you have to create a mount point, you can't just put it in /mnt. Somebody correct me if I'm wrong
Code:
cd /mnt
sudo mkdir sys
sudo mount -o loop -t ext2 /home/usr/Desktop/system.ext2 /mnt/sys
buzz killington said:
you have to specify where your file is and I believe you have to create a mount point, you can't just put it in /mnt. Somebody correct me if I'm wrong
Code:
cd /mnt
sudo mkdir sys
sudo mount -o loop -t ext2 /home/usr/Desktop/system.ext2 /mnt/sys
Click to expand...
Click to collapse
I try but not successful
windows ext2 editing
buzz killington said:
It's just short for Linux distribution, such as ubuntu or redhat. I used ubuntu. Once you have it mounted you can use any text editor available.
Sorry, I don't know if there are. Maybe others can chime in. Anything that'll let you mount an ext2 image and edit its contents will do. Unfortunately I'm not familiar with any windows tools.
Click to expand...
Click to collapse
I think you can edit an ext2 image with windows using the method in post #4 from this thread: http://forum.xda-developers.com/showthread.php?t=808169
Corias said:
I've managed to mount system.ext2 to Windows 7. Without VM and Linux at all.
What tools are needed:
1. Windows Ext2/Ext3 driver. You can get it from here.
2. Any software to mount image to virtual drive. I've used Gizmo Drive, but there are others also working.
Tip: Gizmo doesn't show ext2 as supportable image type, when you browse for image. So, manually type *.* filter.
Click to expand...
Click to collapse
I've tried editing the file and it seemed to save the changes, but I haven't tried booting android yet.
I am trying to do this method in super ram Rom but no success. I have successfully mount system.ext2 but there wasn't any init.rc file. After a lot Google search I have managed to discover that this file is in file initrd.gz and I made the change. But the build starts and hangs in first screen.any suggestion;
Sent from my HTC HD2 using Tapatalk
can anyone uploade the files? i dont have linux..
Cool, thanks! I seems to be working for me with MDJ FroYo HD v4.6. Has anyone had any success getting two Android ROMs running from their microSD card? I was doing this when booting from WM6.5 by putting them in different directories and modifying rel_path in the startup.txt for one of them, but obviously this method won't work until MAGLDR supports startup.txt...
clio94 said:
I am trying to do this method in super ram Rom but no success. I have successfully mount system.ext2 but there wasn't any init.rc file. After a lot Google search I have managed to discover that this file is in file initrd.gz and I made the change. But the build starts and hangs in first screen.any suggestion;
Sent from my HTC HD2 using Tapatalk
Click to expand...
Click to collapse
I didn't do the superram built myself, but letama posted a full version later in that magldr thread. Try to see if you can find it. If not I'm sure I still have it somewhere I can post it for you.
You can change Android folder on SD using MAGLDR
Enter Magldr
Select 9. Services
then 1. BootSettings
then 3. AD SD Dir
*ALL THE USUAL DISCLAIMERS AND WARNINGS*
*THIS IS FOR VERSION 1.1 ONLY, DON’T TRY ON 1.0.0 OR 1.0.1*
Credit goes to: GabrialDestruir for the original auto-nooter, GLa’DOS for the boot animation, pokey9000 for nooter, Mistar Muffin for Market and GTalk Fix, clockworx for the “non-ugly” patch that is used to get androidID, mastapsi for testing and coding of the original auto-nooter, lewellyn for coding, [mbm] for ABI Fix, Hotaru for the Gingerbread keyboard, rpollard00 for DroidX keyboard with bigger font, bpk for Soft Keys, Ben74 for NookColor Tools which enables Non Market Installs and re-enable of ADB , Freenode's #nookcolor chat for code checking. A special thanks to all developers out there, without all of you this community would not be as great as it is.
Please Note: If you are the developer of an app that is included in this work, and would like me to remove it, feel free to contact me.
*I am copying the following step from the original auto-nooter, because they are tried and true, and people are already familiar with seeing them*
What it does:
Installs su and Superuser.apk
Installs Busybox with whoami
Installs Softkeys 3.0.6
Installs NookColor Tools (To Enable Non-Market Installs, and re-enable ADB)
Installs Calendar and Calculator.
Installs Android Market, Gmail, Youtube
Installs Gingerbread Keyboard
Enable ADB
Enable Multi-touch for Android Apps
Enables Live Wallpapers
Enables Android Market and Gmail.
App Auto Install (Open up NooterFiles from sdcard drop in /data/app)
Known Problems:
With the version 1.1 update, ADB will not stay active after a reboot or unplug of the cable. To enable each time you want to use it, you will have to go into NookColor Tools /All Settings/Development/USB debugging, you will have to uncheck the box and then recheck it.
How to Use:
Before you begin:
* To update to 1.1 you must do a complete wipe.
* You must update to 1.1 to use Auto-Nooter 3.0.0 Instructions HERE.
1 You must already have a registered NOOKcolor
2 You must have a Gmail/Youtube linked Account. IF you used a Gmail account for B&N Registration you should use that one for this process.
3 You must either have dd (Linux) or WinImage (Windows) software.
4 You must have an external microSDCard reader or this will not work. Do NOT use the NC.
5 You must have enough intelligence to follow instructions.
Let's get started:
1 Download Auto-Nooter from here: MultiUpload or MediaFire
*MD5 FB74865663B8D797A486A85022FAD9B2*
2 Linux: Unzip and use dd if=auto-nooter-3.0.0.img of=/dev/sdcard
2 Windows: Unzip and use WinImage to "Restore Virtual Hard Disk Image" to your SDcard.
2 Windows Alternative: https://launchpad.net/win32-image-writer/+download
3 Unplug your NOOKcolor from computer. (If Plugged in.)
4 Insert AutoNooter SDcard into your NOOKcolor.
5 Plug the USB cable into your computer and your NOOKcolor. (This will boot up the NOOKcolor.)
6 Your NookColor will reboot when it's done.
That was the hard part, now to the simple stuff.
7 Upon boot unlock your screen.
8 At the Android Welcome Screen skip Sign In.
9 Enable Location Services when given the option.
10 Connect to Wifi and launch Youtube from "Extras".
11 Click the Menu button (The one RIGHT of the Up Arrow).
12 Select "My Channel" and Login using your Gmail Account.
13 Exit Youtube and Launch Gmail from "Extras".
14 Sync your Gmail Account and Exit. (If it fails to sync that is fine.)
15 Open up Market and Accept Terms and Service.
If you made it this far your nook should be successfully Rooted. Go Download an App to make sure.
16 Enable Non-Market Installs by running the NookColor Tools App.
17 If your Youtube fails to launch, download the attached EVO HQ, and follow this code in adb
Code:
adb shell mount -o remount,rw /dev/block/mmcblk0p5 /system
adb uninstall com.google.android.youtube
adb push YouTube.apk /system/app
adb reboot
18 Go to Settings > Device Info > SdCard > UnMount > Format
Complete Wipe:
1 8 Failed Boots > Wipes /system
2 Factory ResetFactory Reset > Wipes /data
*You must do both of these to completely wipe clean your NOOKcolor.*
*Before anyone starts to say that I took this project away from GabrialDestruir, I posted this file in the original post, and sent the OP a PM asking to update the current project. I have yet to hear back, and the post was not updated. My post can be found HERE, dated February 2, 2011. I felt that this would be of a benefit to the community, so I am posting it now. If I am asked at some point to take it down I will do so at that time.*
Forgive my ignorance here, but I thought you were never supposed to use the NC to format your SD card? (last step)
I thought I read somewhere that it messes up something in the emmc?
Hopefully I'm wrong and just paranoid
danbutter said:
Forgive my ignorance here, but I thought you were never supposed to use the NC to format your SD card? (last step)
I thought I read somewhere that it messes up something in the emmc?
Hopefully I'm wrong and just paranoid
Click to expand...
Click to collapse
I have never really seen an explanation as to why you don't format on the NC. I have formated via the NC and the card works fine both in the NC and my PC. When I want to burn an image, I have been able too. Been able to flash other images on it too.
Excellent!
Can you please add an MD5 to the first post?
Homer
danbutter said:
Forgive my ignorance here, but I thought you were never supposed to use the NC to format your SD card? (last step)
I thought I read somewhere that it messes up something in the emmc?
Hopefully I'm wrong and just paranoid
Click to expand...
Click to collapse
Formatting the SDcard doesn't touch the onboard storage. It is one of the easier ways to remove bonus partitions to recover the full card. UPDATE: I should clarify this: when running Eclair internally.
Homer
Any benefit of this over the 1.1r2 many of us did from autonootered 1.0.1?
danbutter said:
Forgive my ignorance here, but I thought you were never supposed to use the NC to format your SD card? (last step)
I thought I read somewhere that it messes up something in the emmc?
Hopefully I'm wrong and just paranoid
Click to expand...
Click to collapse
You're thinking of Nookie Froyo. The stock B&N system is fine for formatting the card.
I think formatting the SD card is an issue when you use one of the Froyo images and boot from eMMC. When you format the SD card it actually formats the internal boot partition or some such. I remember reading it in one of the threads which led me to only boot the Froyo images from an external card.
I am at 1.1.0. When did 1.1.1 appear & how do I get it?
BTW Is this exactly the same as the interim A-N 2.12.25 modified for 1.1?
k
I'd say it's a typo and should be v1.1?
Canadoc said:
Any benefit of this over the 1.1r2 many of us did from autonootered 1.0.1?
Click to expand...
Click to collapse
also interested to know that!
And if there is benefits, can we use the auto nooter?
Just for clarification, in steps 3 & 4 should the NC be turned off? I have never been sure if it matters, but the following statement makes me think that it should be off,
"5 Plug the USB cable into your computer and your NOOKcolor. (This will boot up the NOOKcolor.)"
Thanks,
kev
danbutter said:
Forgive my ignorance here, but I thought you were never supposed to use the NC to format your SD card? (last step)
I thought I read somewhere that it messes up something in the emmc?
Hopefully I'm wrong and just paranoid
Click to expand...
Click to collapse
Only with the froyo image.
Canadoc said:
Any benefit of this over the 1.1r2 many of us did from autonootered 1.0.1?
Click to expand...
Click to collapse
The main difference I see is that Clockwork recovery is not involved.
johnny054 said:
also interested to know that!
And if there is benefits, can we use the auto nooter?
Click to expand...
Click to collapse
I guess it should be the same, but I had a couple of games break after up'ing with 1.1_r2. So I wanted to try stock/clean 1.1 and then root...hoping this would bring them back.
help please
I'm having a problem rooting my nook color. 2 weeks ago I was fully rooted and for some reason I forget why? but I went back to stock. recently I updated to the newest Barnes & noble firmware. seeing the recent developments of honeycomb I wanted to root my nook again. so I tried downgrading to firmware before the most recent update and using that version of auto nooter. I followed the instructions exactly to a tee. the problem is my nook wont load the disk image from the sd card. I made sure to fully format the sd card before writing the img with Win32DiskImager. I made sure the nook was completely off then plugging in the usb to into the pc to wake up the nook. but nothing? the nook boots up like normal then says sd card damaged. I've formatted the sd card again and have used the newest nooter for my current 1.1. but nothing. the only difference is the first time I rooted I was at my mothers and used her pc. it was a windows vista 64 bit. my computer is windows seven 64 bit. anyone have any idea's as to why the nook wont load the sd card with the nooter image? I'm using the same sd card I was able to root from before. so I seriously doubt its the sd card. I am properly formatting it before writing the img. I am having no problem writing the img. any help would be appreciated
danbutter said:
Forgive my ignorance here, but I thought you were never supposed to use the NC to format your SD card? (last step)
I thought I read somewhere that it messes up something in the emmc?
Hopefully I'm wrong and just paranoid
Click to expand...
Click to collapse
brianf21 said:
Only with the froyo image.
Click to expand...
Click to collapse
Ok thanks for that clarification. I was pretty sure I read it somewhere!!
trentmaynard said:
I'm having a problem rooting my nook color. 2 weeks ago I was fully rooted and for some reason I forget why? but I went back to stock. recently I updated to the newest Barnes & noble firmware. seeing the recent developments of honeycomb I wanted to root my nook again. so I tried downgrading to firmware before the most recent update and using that version of auto nooter. I followed the instructions exactly to a tee. the problem is my nook wont load the disk image from the sd card. I made sure to fully format the sd card before writing the img with Win32DiskImager. I made sure the nook was completely off then plugging in the usb to into the pc to wake up the nook. but nothing? the nook boots up like normal then says sd card damaged. I've formatted the sd card again and have used the newest nooter for my current 1.1. but nothing. the only difference is the first time I rooted I was at my mothers and used her pc. it was a windows vista 64 bit. my computer is windows seven 64 bit. anyone have any idea's as to why the nook wont load the sd card with the nooter image? I'm using the same sd card I was able to root from before. so I seriously doubt its the sd card. I am properly formatting it before writing the img. I am having no problem writing the img. any help would be appreciated
Click to expand...
Click to collapse
You probably have a bad burn on the sdcard. Are you writing to the sdcard from the sd card reader or from the nook? Also, if you return to stock, (8 failed boots, then Power+N) You should be on firmware 1.0.0 or 1.0.1. Then root using one of the two original auto nooters, download rom manager from the market and flash the 1.1 pre-rooted firmware.
Thanks buddy, I try doing that. and I don't have an sd card reader so I just put the sd card that I'm going to write into my cell phone. then mount the sd card and write the img to the same storage device that represents the sd card. I'm sure this is the wrong way of doing it but I have gotten root doing the same thing before
Giving this a go now, coming from auto-nootered 1.0.1.
WARNING: This script can be dangerous if you do not know what you're doing!!! I am not responsible for any of your files or hard drives that are deleted if the script is used the wrong way.
The following Bash script (built for Ubuntu) is a simple script that I wrote that does the following:
1. Lets you chose any non-SD ROM.
2. Lets you chose the drive to partition. (WARNING: This ONLY ignores /dev/sda as it assumes that it's your main hard drive. If you have more than one hard drive, do NOT use this unless you know what you're doing!!!)
3. Automatically partitions a Boot partition, a system partition (large enough to hold some BIG ROMs...), a data partition and the rest of your SD card (whatever size it may be) is partitioned as a standard FAT32 space.
4. It modifies both the ramdisk and the vold to boot from the SD and to see that 4th partition as the SD card.
5. If the ROM doesn't have gapps built in and uses the install script to copy them from your last ROM (like CM and MIUI do), it will download and install the gapps.
6. It creates all the required symlinks.
I've only tested it with my 8GB microSD and with MIUI. The permissions are not set up correctly for now due to a bug of sorts... but the ROM that I tested boots and works fine. (Set it all to 777 for now.)
This is only the first version. I just wrote it today. If you find bugs or have a better idea on how to do certain things (like ONLY display USB drives and SD cards) PLEASE let me know here.
If nothing in this thread makes sense, it's because I'm tired...
Update: Adding a bit more info.
Its a really good idea, but not many people can try it unless it's ported to Windows or Mac.
ikingblack said:
Its a really good idea, but not many people can try it unless it's ported to Windows or Mac.
Click to expand...
Click to collapse
I know most people use Windows but Windows isn't very well equipped to do the stuff that this script does. I could always try to make an actual program (make it in c or something) but that would require a complete rewrite. I mostly wrote this for myself (to make my life easier while I'm porting a ROM to the Nook) but figured someone else might be able to use it. (Mostly the people who make the SD img's for everyone else, not the general public.)
ivanmmj said:
I know most people use Windows but Windows isn't very well equipped to do the stuff that this script does. I could always try to make an actual program (make it in c or something) but that would require a complete rewrite. I mostly wrote this for myself (to make my life easier while I'm porting a ROM to the Nook) but figured someone else might be able to use it. (Mostly the people who make the SD img's for everyone else, not the general public.)
Click to expand...
Click to collapse
Well yeah, it is pretty hard. Anyways, your script works for me. Its really nice.
You can run bash in Windows using Cygwin
What's the benefit from using this script on the pc and not using verygreens installer on the nook?
joej said:
You can run bash in Windows using Cygwin
Click to expand...
Click to collapse
Does Cygwin include parted, mkfs.ext4 and mkfs.msdos?
TDO said:
What's the benefit from using this script on the pc and not using verygreens installer on the nook?
Click to expand...
Click to collapse
What installer? I didn't realize he had an installer that would let you install any "non-SD compatible" ROM into an SD card and make it SD-compatible. >.<
Just look at the thread directly below this one ... ;-)
http://forum.xda-developers.com/showthread.php?t=1000957
I am using it in this setup: http://forum.xda-developers.com/showthread.php?t=1022786
as alternate boot option.
TDO said:
Just look at the thread directly below this one ... ;-)
http://forum.xda-developers.com/showthread.php?t=1000957
I am using it in this setup: http://forum.xda-developers.com/showthread.php?t=1022786
as alternate boot option.
Click to expand...
Click to collapse
Reading that it looks like the differences are:
Mine:
Can do all that in the PC without having to touch the nook.
It's all automated. (Like downloading the gapps.)
You run the script then just pop the SD card into the Nook and go.
Meant more for devs who are testing new builds left and right or who are building an image for others to use.
His:
Doesn't require Linux nor any Linux experience (to choose the correct drive from the drive list that the script gives you.)
Meant for the average usage who wants to be able to easily update their ROMs and install new kernels without "wiping" the SD card's data partition.
ivanmmj said:
Reading that it looks like the differences are:
Mine:
Can do all that in the PC without having to touch the nook.
It's all automated. (Like downloading the gapps.)
You run the script then just pop the SD card into the Nook and go.
Meant more for devs who are testing new builds left and right or who are building an image for others to use. <snip...>
Click to expand...
Click to collapse
I like this... Thanks
I am using verygreen's installer on my Nook right now, but I am going to start playing with this script
P.S. Linux rocks, everyone should have it...for those who don't want to let go of Windows, you should at least have Linux installed as a virtual machine on your box using VirtualBox.
So I was playing with this for a few moments on my Mac at work today. Am I copying the ROM archive, say MIUI_us_encore_1.8.5_Eng_Deo_ZipA_Signed_andmer.zip or cm_encore_full-163.zip, into the same location as the Install2SD script?
Or am I to uncompress these roms into their respective folders and copy that folder into the same location as the Install2SD script?
I have yet to get another uSD to play with, so I have obviously not gotten to far with this just yet. I will be back to my Ubuntu machine after I get home from work with a new uSD to play with.
cdaters said:
So I was playing with this for a few moments on my Mac at work today. Am I copying the ROM archive, say MIUI_us_encore_1.8.5_Eng_Deo_ZipA_Signed_andmer.zip or cm_encore_full-163.zip, into the same location as the Install2SD script?
Or am I to uncompress these roms into their respective folders and copy that folder into the same location as the Install2SD script?
I have yet to get another uSD to play with, so I have obviously not gotten to far with this just yet. I will be back to my Ubuntu machine after I get home from work with a new uSD to play with.
Click to expand...
Click to collapse
I haven't tested to see if this works on a mac. That said, just run the script and it will tell you where to put the files (in linux (in nautilus to be exact...)) If not, when you run it the first time, it will create the necessary folder and you can put the files there.
Please excuse asking questions as a first post, but I'm at the stage where I'm stumped and a search isn't helping.
Mlais MX28 fresh from MM pre-rooted. Managed to get the ROM backed up and CWM installed with Rua1's excellent MTK Droid Root & Tools. However, removing the Chinese useless (for me - no offence intended) apks proved not to be happening from the one-click button in that excellent piece of software. No bother, thought I, I'll just use adb and remove the relevant apks manually from /system/app. Famous last words.
Here's where things get really odd. I can mount root fine using the usual procedure but mount -o rw,remount /[email protected] /system works once and once only. Even stranger is that the first time gets you a rw mounted filesystem for about 10 seconds, at which point it gets remounted ro and no amount of faff will get it back to rw without a full power off and restart. All it does is spits out
Code:
mount: Read-only file system
Any ideas, please? I suspect there's some write protection going on but I haven't the first idea where to look.
Edit: Having done a little more searching on this issue, it seems there's a few Acers with the same behaviour, caused by a compiled-in kernel option. Looks like it may well be "wait for a custom ROM" is the answer. Not sure if rolling our own is possible unless anyone knows where to get the Mediatek sources for this device from?
Anyway, :good: to all those who have viewed my question. It's appreciated.
Edit 2: There's an S4UI ROM on needrom<dot>com that is rumoured to have solved this issue. Note that if you have installed CWM using the "magic" MTK Droid Root & Tools method, chances are you can't mount /system rw using ADB in CWM either - I suspect they share the same kernel. I haven't tried the S4UI ROM myself as the recovery needed to install it seems to be in Chinese. Possible solution for anyone with a grasp of that language and script but that someone isn't me
[Q] Mlais MX28 Recovery in Chinese Any help with translation
Hello, bud Any help yet also gut stuck in this.
I'm afraid not at the moment. The S4UI ROM on needrom does indeed enable /system rw but the WiFi and Bluetooth will not activate. Replacing mtk_stp_wmt.ko in /system/lib/modules/ with the version from the stock ROM that should fix this issue, doesn't fix this issue. It's a shame as the S4UI ROM is rather pleasant to use and if I could get that fully operational I expect I would be quite happy with this device. Oddly, the stock ROM came back with a different MAC for the WiFi. As I restored from a backup created with MTKDR&T, this is a little perplexing.
I'll update if I find any more clues.
{Possible solution/nasty hack]
Here's a way to get full /system access on the stock ROM. It requires
Clockwork Mod recovery
ADB
Courage
Install/create Clockwork Mod with MTKDR&T. Now boot into recovery by holding Vol+ and power until the boot selection screen appears and then select recovery with Vol+ and press Vol- to accept.
Do not mount /system in CWM.
On your ADB equipped computer, start
Code:
adb shell
Now issue the following at the root shell prompt:
Code:
tune2fs -e continue /dev/block/mmcblk0p5
Reboot the system and enjoy the power of full root.
This may well be a nasty hack. I was convinced the issue was a protected kernel module but it seems the ext4fs image of the system block is corrupt in some way and the default error action is to mount -o ro. We're disabling that default action and letting the mount remain unchanged.
As always with these things, proceed at your own risk. If you break it, you have the privilege of keeping both bits.
Good way around mate, but risky as no CWM yet installed, seem's the mobile gut some bug problem, should expect an official update rom soon enough, Root method you used for this? i intend flashing Clockwork Mod can seem to understand fully as i'm new to android development and customizing, again problem with battery do you get a full day (few moment on screen) light usage? Feel its no actual 25000mah on board.
codedmax said:
Good way around mate, but risky as no CWM yet installed, seem's the mobile gut some bug problem, should expect an official update rom soon enough, Root method you used for this? i intend flashing Clockwork Mod can seem to understand fully as i'm new to android development and customizing, again problem with battery do you get a full day (few moment on screen) light usage? Feel its no actual 25000mah on board.
Click to expand...
Click to collapse
It appears there's an fsck implementation in the shell of CWM as well.
Code:
e2fsck -pfv /dev/block/mmcblk0p5
That should fix most of the errors in the filesystem.
The device came with su and SuperSU installed but it was fairly useless without /system access.
CWM can be easily installed using MTK Droid Root & Tools to extract the boot image, auto-patch, build CWM and install the lot. It really is a slick piece of software.
As for the battery, an even bigger issue is the supplied charger which is puny. Of course, looking at the battery and then looking at a proper, honest-to-goodness 2.2Ah Panasonic 18650 cylindrical cell you have to wonder if 2.5Ah isn't awfully optimistic.
Chron0s said:
It appears there's an fsck implementation in the shell of CWM as well.
Code:
e2fsck -pfv /dev/block/mmcblk0p5
That should fix most of the errors in the filesystem.
The device came with su and SuperSU installed but it was fairly useless without /system access.
CWM can be easily installed using MTK Droid Root & Tools to extract the boot image, auto-patch, build CWM and install the lot. It really is a slick piece of software.
As for the battery, an even bigger issue is the supplied charger which is puny. Of course, looking at the battery and then looking at a proper, honest-to-goodness 2.2Ah Panasonic 18650 cylindrical cell you have to wonder if 2.5Ah isn't awfully optimistic.
Click to expand...
Click to collapse
Very Well concerned,
once again good job, but how do i go about implementing this,
would you be kind enough to put in some more details on the file system code and CWM flashing with MTK Droid root & Tool did you manage to get a translation on the chinese langauage recovery problem,
(a tutorial is just fine) Thanks alot bud.
Okay, give me a little time to set it all up for screenshots as I don't generally use Windows unless I have to. It's all fairly straightforward. The CWM installation is four clicks and some waiting and repairing the /system block is a couple of commands.
Oscarblue48 has a tutorial on installing CWM on Mediatek devices here or here if your MX28 isn't rooted which is the procedure I followed. Then it's just a case of booting into CWM, connecting your device to USB and using adb's shell to fsck the filesystem on that block.
really nice, okay as you say,
i would look forward to it (some screen shots aid), in the main time with full study & concentration on the CWM tutorial you gave, quite interesting if you ask me.
#back to studying, looking forward to a bug free final optimization of the Mlais MX28 as its a great buy for such a price.
codedmax said:
really nice, okay as you say,
i would look forward to it (some screen shots aid), in the main time with full study & concentration on the CWM tutorial you gave, quite interesting if you ask me.
#back to studying, looking forward to a bug free final optimization of the Mlais MX28 as its a great buy for such a price.
Click to expand...
Click to collapse
Sorry for the delay, I ran into a few issues and had to work out what was going on. Basically the e2fsck in CWM cannot write back to the block device so is useless. I extracted the system.ext4.img, added it as a file backed memory disk on my main computer and ran an e2fsck from there, which found and fixed the errors in the FS image. Writing that back after changing a few MD5sums in the file MTKDR&T creates allowed me to flash it back.
However it makes absolutely no difference to the mount behaviour. It still drops back to ro without the tune2fs -e continue set so that is, barring someone else coming up with a more elegant fix, the workaround. In a nutshell, follow the guide for either root or CWM recovery installation that others have posted linked above (no point wasting board space on repetition) and then simply follow my instructions for setting the error behaviour on the mmcblk0p5 slice and you should be good to go.
It's still an awful hack IMHO but, since there's nothing else so far that works, it's the uncomplicated way to get full root. Most of us will install CWM anyway, so it's no big chore just to boot into recovery and type one command "tune2fs -e continue /dev/block/mmcblk0p5" at the ADB shell.
Chron0s said:
Sorry for the delay, I ran into a few issues and had to work out what was going on. Basically the e2fsck in CWM cannot write back to the block device so is useless. I extracted the system.ext4.img, added it as a file backed memory disk on my main computer and ran an e2fsck from there, which found and fixed the errors in the FS image. Writing that back after changing a few MD5sums in the file MTKDR&T creates allowed me to flash it back.
However it makes absolutely no difference to the mount behaviour. It still drops back to ro without the tune2fs -e continue set so that is, barring someone else coming up with a more elegant fix, the workaround. In a nutshell, follow the guide for either root or CWM recovery installation that others have posted linked above (no point wasting board space on repetition) and then simply follow my instructions for setting the error behaviour on the mmcblk0p5 slice and you should be good to go.
It's still an awful hack IMHO but, since there's nothing else so far that works, it's the uncomplicated way to get full root. Most of us will install CWM anyway, so it's no big chore just to boot into recovery and type one command "tune2fs -e continue /dev/block/mmcblk0p5" at the ADB shell.
Click to expand...
Click to collapse
Greetings bud, gut CWM installed, all thanks to you (indeed greatful), have you been lucky with any custom rom as of now that works efficently on your device?
I seem to find a few bug here and there on the manufacturer stock, puny wifi & gps lock in, slight screen maulfuctions a little times.
As with most mtk gps can not finding a lock in hows it with your device.
codedmax said:
Greetings bud, gut CWM installed, all thanks to you (indeed greatful), have you been lucky with any custom rom as of now that works efficently on your device?
Click to expand...
Click to collapse
None of the custom ROMs on needrom work correctly which is a shame. The stock ROM's UI is awful.
codedmax said:
I seem to find a few bug here and there on the manufacturer stock, puny wifi & gps lock in, slight screen maulfuctions a little times. As with most mtk gps can not finding a lock in hows it with your device.
Click to expand...
Click to collapse
Now you have root you can use FasterGPS from FDroid to intialise the gps.conf file with appropriate settings for your location. My GPS is rock solid now, even in a moving vehicle. Not had any screen malfunctions. What version is your stock ROM? Mine's the 20140221 update.
Chron0s said:
None of the custom ROMs on needrom work correctly which is a shame. The stock ROM's UI is awful.
Now you have root you can use FasterGPS from FDroid to intialise the gps.conf file with appropriate settings for your location. My GPS is rock solid now, even in a moving vehicle. Not had any screen malfunctions. What version is your stock ROM? Mine's the 20140221 update.
Click to expand...
Click to collapse
Hello great bud,
Sorry for late reply, been up with alot on my plate from work lately, gps has been improved upon using that wonderful app "FasterGPS" now able lock in under a split couple of min not as before were it take like forever *Nice*
gut the same stock version "20140221" gusse its down to my own unit with the screen ish
Did a little searching around found a recent update from a online retailer outlet via their forum "merimobiles"
forum.merimobilesdotcom.previewdnsdotcom/showthread.php?465-Unified-thread -for-Mlais-MX28-stock-ROM-updates
Hope im not infringing on any xda TOS as i just seek some help.
Thanks
Please i need help, i have a mlais mx28 buy in buyincoins, with the refer gordete200, it´s all ok.
i´m very happy with the mlais mx28, but i used a 8 gigas sd card, it´s all ok.
My problem: i have install with flashtools the new rom stock update : mx28_0312_N2.rar from the official mlais mx28 web
When i have install this ultimate ( update ) ROM, it´s was with reebots, and the wifi and blutooth crash 0_0 !!! what happend?
I back to the Rom stock : 0115 but the sd partitions was changed : 1 gb for apps, and 1.75 gb for internal memory, it´s very strange, before install the Update, i had 2,3 gb for apps and 256 gb for internal memory...
I´m very worry, the actual problem is the sd card:
With 8 gb sd card class 10, it´s all ok, all correct, but when i put the 16 gb sd card class 10, it´s don´t mount sd correctly always.
I´m very crazy for all...
codedmax said:
Hello great bud,
Sorry for late reply, been up with alot on my plate from work lately, gps has been improved upon using that wonderful app "FasterGPS" now able lock in under a split couple of min not as before were it take like forever *Nice*
Click to expand...
Click to collapse
Good stuff. Once you have the gps.conf set up, try using Mobileuncle Tools to pull in the EPO (extended prediction orbit, basically a nice big list of keplers for the satellites so it knows which to expect to be in view at a given time without having to scan the sky for what's actually there) data which should stabilise the GPS even further.
codedmax said:
gut the same stock version "20140221" gusse its down to my own unit with the screen ish
Did a little searching around found a recent update from a online retailer outlet via their forum "merimobiles"
forum.merimobilesdotcom.previewdnsdotcom/showthread.php?465-Unified-thread -for-Mlais-MX28-stock-ROM-updates
Hope im not infringing on any xda TOS as i just seek some help.
Thanks
Click to expand...
Click to collapse
I wonder if it's the bodged Trebuchet they're using? It's a bit of a disaster as they've taken the CM launcher, bodged bits of MIUI into it and given the whole thing a "that'll do" look and feel. I replaced it with the real Trebuchet after a thorough decrapify, along with the AOSP stock keyboard. There's a "modified" apk of Trebuchet (all the dev did was lower the base API level so it would install on 4.1) floating about on the 'net somewhere. The various KitKat-alikes work fairly well but I wanted something open source that I could slam into /system/app without worrying.
It has taken a lot of faff to get to this stage but I now have a very usable and fast device for not a great deal of outlay.
gordo100 said:
Please i need help, i have a mlais mx28 buy in buyincoins, with the refer gordete200, it´s all ok.
i´m very happy with the mlais mx28, but i used a 8 gigas sd card, it´s all ok.
My problem: i have install with flashtools the new rom stock update : mx28_0312_N2.rar from the official mlais mx28 web
When i have install this ultimate ( update ) ROM, it´s was with reebots, and the wifi and blutooth crash 0_0 !!! what happend?
I back to the Rom stock : 0115 but the sd partitions was changed : 1 gb for apps, and 1.75 gb for internal memory, it´s very strange, before install the Update, i had 2,3 gb for apps and 256 gb for internal memory...
I´m very worry, the actual problem is the sd card:
With 8 gb sd card class 10, it´s all ok, all correct, but when i put the 16 gb sd card class 10, it´s don´t mount sd correctly always.
I´m very crazy for all...
Click to expand...
Click to collapse
Do you have a backup of the original ROM and scatter (partition layout) file? You really should (read: MUST) back up these devices before flashing new firmware as there's often bits missing, as you found with the WiFi and Bluetooth issue. MTK Droid Root & Tools will create a useful backup of the partition layout and contents for you without too much difficulty.
Please do not write to the preloader partition with the SP flash tool. Once the preloader is corrupt, your device is a brick which only JTAG will recover. I seriously doubt anyone has a JTAG solution for this device right now. There is no need to rewrite the preloader at all in any case so simply deselect the preloader block in SP Flash tool before downloading.
As for the SD cards, you need to make sure your card is formatted FAT, not NTFS, and the card must be partitioned correctly, i.e. the FAT partition must be the first primary. The MX28 will accept a card of up to 32GB if I recall correctly, which is the limit of SD-HC. Clockwork Mod can format your card for you.
Chron0s said:
Do you have a backup of the original ROM and scatter (partition layout) file? You really should (read: MUST) back up these devices before flashing new firmware as there's often bits missing, as you found with the WiFi and Bluetooth issue. MTK Droid Root & Tools will create a useful backup of the partition layout and contents for you without too much difficulty.
Please do not write to the preloader partition with the SP flash tool. Once the preloader is corrupt, your device is a brick which only JTAG will recover. I seriously doubt anyone has a JTAG solution for this device right now. There is no need to rewrite the preloader at all in any case so simply deselect the preloader block in SP Flash tool before downloading.
As for the SD cards, you need to make sure your card is formatted FAT, not NTFS, and the card must be partitioned correctly, i.e. the FAT partition must be the first primary. The MX28 will accept a card of up to 32GB if I recall correctly, which is the limit of SD-HC. Clockwork Mod can format your card for you.
Click to expand...
Click to collapse
Many thanks for your help. I have a back up of my mlais, i have a back up with mtk droid and tools 2.5.3 ( new version ), but when i put it on the flash tools, the cache and user is missing, and it´s imposible to download it. and then i put a recovery CWM on the mlais with droid and tools ( very easy ), and use a nandroid back up, it´s no problem, but the internal sd partition is always changed : 1 gb for apps and 1.75 for sd internal, i´m very sad because i would like back to the 2,3 gb for apps ( original partition )
Yes... always fat32 sd cards of course, but i have problems with the sd up to 8 gb, the mlais freeze, or sd desmount ( it´s imposible sometimes write in sd external ) i don´t find the problem with this... i have the rom stock : 115.
Other problem, i would like to up the ultimate ROM stock 221. but the wifi and bluetooth crash, and reboot the phone sometimes ( terrible...) , what can i do ? your solution is don´t stick the PRELOADER on the Flashtool when i upload the firmware ? it´s correct? ( i think that if don´t mark the preloader it´s imposible flash... ?¿ )
Many thanks for your help !
gordo100 said:
Other problem, i would like to up the ultimate ROM stock 221. but the wifi and bluetooth crash, and reboot the phone sometimes ( terrible...) , what can i do ? your solution is don´t stick the PRELOADER on the Flashtool when i upload the firmware ? it´s correct? ( i think that if don´t mark the preloader it´s imposible flash... ?¿ )
Click to expand...
Click to collapse
No, what I'm saying is we don't yet know why the WLAN and Bluetooth stop working when a different ROM from the one flashed at the factory is installed. There is clearly some mechanism at work here that is blocking those two devices after an update and it's not the usual shared objects as it is on other devices. It also doesn't seem to be NVRAM related as the MAC and BDaddr remain once the old firmware is re-flashed.
This same problem occurs with all the custom ROMs on needrom.
The reason I say do not needlessly flash the preloader is the danger of a full brick from which you cannot recover. The preloader code very rarely changes - its only purpose is to provide an interface to SP flash tools or boot; think "BIOS" in PC terms - so it is a pointless risk. You most certainly can flash the other blocks with the preloader block deselected.
The bottom line right now is stick with the factory ROM, install CWM, apply the system mount fix and use Xposed and suchlike to customise until we come up with something a little more sensible or at least find out why the WLAN and Bluetooth stop working.
Given that the Wiko Darkmoon is based on the same SoC and has full sources available <EDIT: It isn't. It's just the kernel as usual.>, it may be prudent to wait until someone with more clue than I has a look at what makes these things tick.
Chron0s said:
No, what I'm saying is we don't yet know why the WLAN and Bluetooth stop working when a different ROM from the one flashed at the factory is installed. There is clearly some mechanism at work here that is blocking those two devices after an update and it's not the usual shared objects as it is on other devices. It also doesn't seem to be NVRAM related as the MAC and BDaddr remain once the old firmware is re-flashed.
This same problem occurs with all the custom ROMs on needrom.
The reason I say do not needlessly flash the preloader is the danger of a full brick from which you cannot recover. The preloader code very rarely changes - its only purpose is to provide an interface to SP flash tools or boot; think "BIOS" in PC terms - so it is a pointless risk. You most certainly can flash the other blocks with the preloader block deselected.
The bottom line right now is stick with the factory ROM, install CWM, apply the system mount fix and use Xposed and suchlike to customise until we come up with something a little more sensible or at least find out why the WLAN and Bluetooth stop working.
Given that the Wiko Darkmoon is based on the same SoC and has full sources available <EDIT: It isn't. It's just the kernel as usual.>, it may be prudent to wait until someone with more clue than I has a look at what makes these things tick.
Click to expand...
Click to collapse
Many thanks Chronos!, The problem is also with the official ROMS on mlais.com/mlaismx28 i don´t understand it...
Please i need help to back restore the partitions of my sd internal ( ROM ), i would like back to 2,3 gb for apps, actually i have only 0,98 gb and 1,75 gb internal store.
I think that the solution is back up for flash tools and reflash with the rom stock ( the back up of mlais mx28 of my friend, he have other new mx28 )
But my BIG problem with the flash with flash tools is the USER DATA and CACHE is always empty, and then it´s imposible to reflash it it´s always and error : Rom changed PTM ...
Please, what can i do for have USER DATA and CACHE with mtk droid and tools 2.5.3 versión?? ( in this version to click User data and Cache with to do the back it´s imposible, this option is missing in 2.5.3. version )
http://dl.xda-developers.com/attachdl/b2f11c741aab592a8f66616d932af983/533c2dcc/2/6/6/4/5/2/2/Sin_t_tulo.jpg
[ROM] Official Update
Hello guys, there's a new rom update for the mx28
Official Mlais MX28 version: Mlais_MX28_20140312
www.needrom.com/mobile/mlais-mx28-2/
Try it out seems, it works perfect.
Cheers!!