Related
[size=+2]This version is now deprecated in favor of the 2.0 APK version. Please see this link: http://forum.xda-developers.com/showthread.php?t=784691[/size]
This version is not recommended for use any longer.
Details about what this fix does:
Creates a VIRTUAL EXT2 filesystem inside the stock RFS filesystem on the internal SD card, with a 4KB block size. This means that this lag fix creates a buffer between the real filesystem and the android system. This buffer should reduce the amount of disk I/O required for all operations by utilizing EXT2 buffering, as well as not writing file access times to disk, etc.
Folders that are currently supported:
/data/data
/data/system
/data/dalvik-cache
/data/app
/data/app-private as a symlink to /data/app/app-private
/dbdata/databases is not supported. It appears to be ROM backed, and can cause problems if overwritten.
Benefits over version 1
1.5GB of application data available, with no data loss.
e2fsck of the EXT2 partition on each boot.
Correct busybox version included! YES!
/app and /app-private directory included in the fix for faster application installs.
/dbdata/databases included in the fix, expected to give a big performance boost for apps that use it.
Mounts instead of symlinks for extra performance as OS does less work (about 100 or so more quadrant).
Benefits over other lag fixes
Open source, with full comments and ease of editing.
Works on any and all firmware versions, including any yet unreleased froyo versions (that don't change file structure).
Credits
Big thanks to mimocan for putting us all on the right track in how to sort out lag problems!
Big thanks to ykk_five for showing us all how well loopback filesystem mounting works!
Big thanks to cyanogen mod for e2fsck
Requirements for One Click Lag Fix 2.0
Rooted phone - http://www.addictivetips.com/mobile...t-samsung-galaxy-s-i9000-with-a-single-click/
Windows computer with SGS Drivers (Samsung Kies), or the ability to read through the batch file and run it yourself.
(Beta Release) The ability to reflash your device if something goes wrong.
No other lag fix installed. If you installed One Click Lag Fix 1.0, then use the uninstall function which came with that lag fix before running this lag fix. (Untested but assumed to be working, please help out here.)
1.5GB of freespace on Internal SD Card for swap files while the fix is working (/sdcard).
"Internal phone storage" in Settings->SD Card must read greater than 500mb (0.5GB) of free space.
How to run One Click Lag Fix 2.0
Place your phone into USB debugging mode: Settings->Applications->Development
Attach your device to your computer. Do not mount the drives.
Download the attached ZIP file.
Unzip to a folder of your choice.
Double click "lagfixme.bat".
Don't double click "unlagfixme.bat".
Wait for it to complete.
You will need your phone to be unlocked when it runs the script, so that you can accept the permissions request that will appear on your device.
How to remove One Click Lag Fix 2.0
Double click "unlagfixme.bat"
Wait for it to complete.
Known Issues For All Versions
Some custom firmwares use up all available space in /system. This fix requires some libraries to be placed in /system/lib. These libraries are used to create the filesystem properly, and to check it for errors on every boot.
If your firmware does not have the available space (around 1mb) in /system, do not use this fix! Your phone will not boot and will have to be restored from backup / reflashed.
Current known firmwares with this issue: None yet. Please provide the firmware version+mods if you encounter this issue. It will show up as an out of space error in the log, under 'Copying libraries'.
Known Issues 2-1, 2-2
Paid apps from the market have issues.
Google maps and other pre-installed ROM-backed applications have issues.
2-3 Changes from 2-2
/dbdata has been removed. This fixes maps issues.
/app-private is now a symlink to /app/app-private. This fixes paid apps issues.
Alternate installation methods for similar fixes
Tayutama has made an update.zip version that is easy to install - http://forum.xda-developers.com/showpost.php?p=7632258&postcount=208
Chainfire has a .NET version of this fix with some nice features - http://forum.xda-developers.com/showthread.php?t=751513
Frequently Asked Questions
Q: My apps are force closing while this fix is running, and I can't use my phone!
A: By design. The script has backed up/copied your apps over to the internal SD card (remember the requirement about 1.5GB of free space on the SD card?). It is now overwriting them with a 1.5GB file. As the file overwrites an app that is trying to do something, it will probably force close. This is normal.
Closing all running apps, and removing widgets before running this fix can make the process much smoother, though.
Q: The script can't transfer files to my phone / The script can't run / Help help I'm dieing!
A: Read the first post again.
Q: My paid apps from the market don't show up.
A: I will hopefully have a fix for this sooner or later. Hold tight! It's in the known issues. I don't have access to paid apps, so I can't test this.
Q: Does this need busybox?
A: No, busybox is included.
Q: I only have 200mb of free space now! What gives?
A: The lag fix has made a 1.5GB file, and is storing all of the data inside there. The side effect is that the free space meter is now incorrect. Sorry, this can't be helped.
You can check real free space by using ADB like this:
Code:
adb shell
su
busybox df -h
Q: When I use a backup tool, the backup is now 1.5GB big! It's taking forever!
A: The backup tool isn't designed to work with this fix. It will work, it just won't work well. Hopefully this fix will be short lived, and either Samsung will give us a new update, or someone will give us a good custom firmware that can natively mount what we need, where we need it. Or someone might come out with a better backup manager. Until then, we suffer.
Q: Will a reflash wipe this fix?
A: Yes, a reflash will wipe everything this fix did.
Q: Can this brick my phone?
A: If you know how to get to the download mode from power off (hint: volumedown+home+power), then almost nothing short of throwing your phone off a tall building can actually brick it. If you can't do this though, or don't know someone who can, then you're better off waiting for samsung to release a fix. Anything that moves files around on your device has the potential to break things, and this fix has no QA department.
Q: Why is /dbdata not included in your fix, but other people have included it?
A: Other people have included it in the same way my 2-2 fix includes it. However, /dbdata is ROM backed. This means that the real files are on ROM, and only the changes appear in the /dbdata folder. When copying or moving files from this folder, you would need to specify each folder by exact name to ensure that it was copied across, and each firmware can have their own names. (This is because RFS wildcard will not catch an unused ROM backed file.) In some cases, you can get lucky and have this work perfectly because you have already used all the files in /dbdata. There is no fail safe method to do this though, and /dbdata does not make a big difference to performance. (It is already on NAND flash.) If you want to try your luck, v2-2 is still available.
Q: Why does this lag fix work? Is it slowly destroying my phone?
A: Let's say an application counts from 1 to 10, and writes the value each time to disk.
Stock:
1 -> App tells RFS to write 1 to disk -> RFS writes 1 to disk -> RFS writes journal saying to changed the value on the disk.
2 -> App tells RFS to write 2 to disk -> RFS writes 2 to disk -> RFS writes journal saying to changed the value on the disk.
..
9 -> App tells RFS to write 9 to disk -> RFS writes 9 to disk -> RFS writes journal saying to changed the value on the disk.
10 -> App tells RFS to write 10 to disk -> RFS writes 10 to disk -> RFS writes journal saying it changed the value on the disk.
Total physical disk writes: 20. Speed: SLOW! Wear and tear on disk: HIGH!
Lag Fix:
1 -> App tells EXT2 to write 1 to disk -> EXT2 stores 1 in RAM.
2 -> App tells EXT2 to write 2 to disk -> EXT2 stores 2 in RAM.
..
9 -> App tells EXT2 to write 9 to disk -> EXT2 stores 9 in RAM.
10 -> App tells EXT2 to write 10 to disk -> EXT2 stores 10 in RAM.
..
EXT2 tells RFS to write 10 to disk -> RFS writes 10 to disk -> RFS writes journal saying it changed the value on the disk.
Total physical disk writes: 2. Speed: FAST! Wear and tear on disk: LOW!
This isn't exactly what is happening, but it gives you the general idea.
Q: Can this mod work on other Android devices? Would we see a performance boost on them as well? If not why is it limited to the Galaxy S?
A: SGS has very very good hardware, but it has some parts of it's hardware poorly implemented. The filesystem that samsung chose to use is custom-built using FAT32 as a base, RFS. It has a lot of the problems that FAT32 has, and should have been left back in the 90s, or even the 80s.
One of the big issues with it is how it handles multiple requests - it blocks. It blocks everything. When your mail app wants to read the mail you just tried to view, but your twitter app is busy writing a new tweat it just received, your mail app is forced to wait.
This is bad, but it could be worse! And it is... your twitter app didn't just get one tweat, it got 50 tweaks. It is busy writing the tweats one by one to the filesystem. This would be fine, since all modern filesystems will buffer writes, so instead of writing each one at a time, they will batch them together and write it as a big chunk. Uh oh - RFS does no buffering at all! After each write, it will also write an update to the grafted-on journal system. Guess what happened to your mail you were trying to view while all this happened? It 'lagged' and you got a black screen for half a second, before the mail popped into view.
Luckily the hardware on the device is so good that you usually don't even notice the problem until you have a lot of apps running, all writing their updates when you unlock the phone.
This is mostly speculation based on experiments done on RFS -- RFS is closed source, and we have no idea if the problems are just badly set settings (such as a block size that is too small), coding bugs in the implementation, or if RFS is just really that badly designed.
This fix just grafts a buffer on top of the RFS filesystem, using a very very simple and fast filesystem, EXT2. It fixes most of the issues by writing to RFS as seldom as possible.
So no, this fix won't fix other devices, since they're already running quite close to maximum speed. The SGS at stock is running nowhere near maximum speed, and this lag fix takes it a bit closer. You could probably speed up other devices by tweaking the filesystem settings to give them a big buffer or similar, but it isn't really needed. (I haven't actually tried to put an EXT2 onto any other Android phone, as I don't have any other Android phone, so this is just speculation.)
Q: My phone is fast now!
A: Yeah.
Oh, awesome. I managed to post this in the wrong forum. Doh!
Could a moderator please move this to Android Dev sub forum?
haha looks awesome dude but you are correct, wrong section im gonna try it now, will report in 5 mins!
A few people in the other thread said they had the first lag fix working on the captivate. Anything that might change that with this release? I came to download the old one, and here a new one is
abra-cadabra...
*POOF*
Done!
E_man5112 said:
A few people in the other thread said they had the first lag fix working on the captivate. Anything that might change that with this release? I came to download the old one, and here a new one is
Click to expand...
Click to collapse
The old one is still here. Nothing has changed that should stop it working on the captivate though, but it is completely untested. Use the 1.0 (which has had a lot of testing) until this one has been put through the paces.
sirphunkee said:
abra-cadabra...
*POOF*
Done!
Click to expand...
Click to collapse
Thanks.
RyanZA said:
The old one is still here. Nothing has changed that should stop it working on the captivate though, but it is completely untested. Use the 1.0 (which has had a lot of testing) until this one has been put through the paces.
Click to expand...
Click to collapse
E_man5112 said:
A few people in the other thread said they had the first lag fix working on the captivate. Anything that might change that with this release? I came to download the old one, and here a new one is
Click to expand...
Click to collapse
I'm running the manual ext2 fix with Q scores 2000+. I'll try 2.0 Util tonight and post feedback....
Someone got some benchmarks?
Maybe for xxjp3? I only reach 1900 in quadrant.. /:
Sent from my GT-I9000 using Tapatalk
gonna test report in 5minutes
RyanZA said:
The old one is still here. Nothing has changed that should stop it working on the captivate though, but it is completely untested. Use the 1.0 (which has had a lot of testing) until this one has been put through the paces.
Click to expand...
Click to collapse
I'm in the process of flashing back to stock on my Captivate so I can give this a legit test. I'll report back here and let you know how it goes. Assuming my Captivate doesn't melt I'll update my OP from the thread about the original fix in the Captivate section!
About what lag is this?
Sent from my HTC Desire using XDA App
Dominik06 said:
Someone got some benchmarks?
Maybe for xxjp3? I only reach 1900 in quadrant.. /:
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
Benchmarks are roughly the same as 1.0. You can expect about 100 points more on average though, at least on my phone.
I just removed the V1 version and finished the V2.
It finally finished and rebooted the phone. now it tells me my internal memory storage is full. None of my Widgets will load.
Looking i see only 14MB free in internal storage.
thoughts?
Zilch25 said:
I'm in the process of flashing back to stock on my Captivate so I can give this a legit test. I'll report back here and let you know how it goes. Assuming my Captivate doesn't melt I'll update my OP from the thread about the original fix in the Captivate section!
Click to expand...
Click to collapse
Just as long as you point out that this fix isn't heavily tested yet!
RyanZA said:
Just as long as you point out that this fix isn't heavily tested yet!
Click to expand...
Click to collapse
Oh I know, I'm going to emphasize that heavily, lord knows I don't want to get stuck on tech support all night
clubtech said:
I just removed the V1 version and finished the V2.
It finally finished and rebooted the phone. now it tells me my internal memory storage is full. None of my Widgets will load.
Looking i see only 14MB free in internal storage.
thoughts?
Click to expand...
Click to collapse
Thoughts? That's bad.
You should be seeing roughly 215mb free. Did you see any errors in the log at all?
Everything is working fine for me. First reboot after lagfix had some problems with downloading apps from market, but after a second reboot it got fixed.
"Biggest" problem now, is just the phone stating that my internal phone storage is too low, with an icon on notification bar that I cannot remove. Already deleted some .bak from /data folder, any more tips what I can delete to get rid from this message?
Regarding the fix. apps are indeed much more snappier, no lag on the system when installing apps from market, and overall if the phone would continue like this for the next 48 hours, lag fix form me is solved. I had some problems after some 24h, with some lag, even with the previous version of the lag fix.
clubtech said:
I just removed the V1 version and finished the V2.
It finally finished and rebooted the phone. now it tells me my internal memory storage is full. None of my Widgets will load.
Looking i see only 14MB free in internal storage.
thoughts?
Click to expand...
Click to collapse
Looking through my old V1 remove script, I believe I was leaving behind the .bak files! Nastyyy... I'll update V2 to remove those if they're there on install. Will hopefully clear up any problems.
Guys, I have been trying to install android for 3 days already. No success. Tried atools 1.0.4, 1.0.5 and finally 1.1.0 today. I got the "bad block" errors. First I thought it is the SD card, changed it with another one, but same thing. Finally tried system and data on NAND and I got the following:
Format system
flash_eraseall: /dev/block/mtdblock2: not a char device
Failed
Failed to format
What should I do?
Any help will be appreciated!
My advice is to use ATOOLS only as NBH EDITOR to set your panel type and/or overclock GPU.
Install the kernel, do the reboot, and then press dpad when you see the message 'press and hold dpad .....'
Select system and data on NAND, install system (androidinstall.tar in andboot folder of course) and quit.
I suggest this way because I think that is little complicated to use a script generated by ATOOLS especially if you do not have much experience.
Millence said:
My advice is to use ATOOLS only as NBH EDITOR to set your panel type and/or overclock GPU.
Install the kernel, do the reboot, and then press dpad when you see the message 'press and hold dpad .....'
Select system and data on NAND, install system (androidinstall.tar in andboot folder of course) and quit.
I suggest this way because I think that is little complicated to use a script generated by ATOOLS especially if you do not have much experience.
Click to expand...
Click to collapse
I've just tried this way too, used atools as a nbh editor, put it in the root folder, then created andboot folder and put the TAR file inside.
Almost the same result:
Freeing init memory: 128K
[ 8.449793] set sdcc vdd to 16
[ 8.781563] clk_set_rate 21:32000000
[ 8.789359] set sd clock - 0 1
[ 8.815143] mmc1: host does not support reading read-only switch. assuming write-enable.
[ 8.832956] mmc1: new high speed SD card at address b368
[ 8.856739] mmcblk0: mmc1:b368 2GU2M 1.87 GiB
[ 8.869113] mmcblk0: p1 p2
After those I got Formatting, lots of bad blocks, then Installing...
Failed.
Not enough space on device...
The only logical explanation for this is that you have so mutch bad blocks on the NAND that not enough space remains for installation.
Try to increase the system partition to 120MB using ATOOLS.
Thanks for your reply!
Just did it. Same thing
The worst part is that I can't see exactly how many bad blocks I have, but they are at least 2 screens
Below is my log file.
Thanks is advance for your help.
Which rom are trying to install? What is the size androidinstall.tar file?
Bad blocks are normal on nand.
Reinstall, probably the androidinstall is too big.
Millence said:
Which rom are trying to install? What is the size androidinstall.tar file?
Click to expand...
Click to collapse
I've tried both Thoughtlesskyle's Not so Super Froyo and the "Gingerbones" rls5.1, one is 112K the other one is like 80-ish and I still got the same problem.
What if I put everything on the SD card, can I do that?
Finally...After increasing my system to 170MB I got it installed. Also tried with 160mb and less, but seems like I have so many bad blocks that there's no space for the system. But now looks like my space for data is very low. What would you guys suggest?
remove some apk from the android install...
Data on ext2 partition.
This is my development based on Takaaki's initrd, during I develop my build at http://forum.xda-developers.com/showthread.php?t=913597, I spent a lot of time to enhance the data2sd and ext4, after studying almost all the popular methods: App2SD, Data2SD, Data2ext, Data2whatever, I develop this:
Features:
1. Support both data 2 data.img or ext4.
2. Support SquareFS.
3. Auto-format the 2nd partition with block size of 4096.
4. Utilize the Nand data partition to improve the performance.
5. Switch the PPP/RMNET.
6. Config the gps_zone
7. Support the update without re-flash. (you can fully customize your build based on this feature)
8. Backup the ext4 to data.img (implement in future)
9. Restore the data.img to ext4 (implement in future).
To enable external data.img
1. create '.data' folde under sdcard (/sdcard/.data).
2. create 'config.txt' under '.data' directory.
3. copy old data.img to '.data' directory, otherwise a new data.img will be created.
4. boot into Android.
Config.txt for data2SD.
data_img=1
data_ext=0
sd_boost=1
nand_data=0
Click to expand...
Click to collapse
To enable ext4
1. create '.data' folde under sdcard (/sdcard/.data).
2. create 'config.txt' under '.data' directory.
3. Config.txt for data2SD.
data_img=0
data_ext=1
sd_boost=0
nand_data=0
format_ext4=0
Click to expand...
Click to collapse
For first installation, it is always good to set the format_ext4=1 to format your ext4 partition with proper block size, after 1st boot, change it back to 0.
To config PPP/RMNET and GPS_ZONE
ppp_mode=1 will enable the ppp, set to 0 will use rmnet.
gps_zone='your country code', - country code, us, fr, jp, etc
To update/customize your build
1. Create a folder /DLZUPDATE under your sdcard.
2. put your app's apk under AndroidApps in /DLZUPDATE, that apps will be automatically installed into your data partition.
3. put your kernel file or other under root in /DLZUPDATE, all the files under root will be copied to your build, if your want to upgrade your kernel, just put zImage in /DLZUPDATE/root/system, and module files under /DLZUPDATE/root/system/lib/modules. etc.
Download
View attachment 492146
Install
1. extract the zip to a folder on your pc
2. backup your existing initrd.gz using adb
3. In "command prompt" env, run install.
4. your existing initrd.gz will be backup at the same folder named backup.initrd.gz.
5. if your have problem to boot into the system, just try: adb push backup.initrd.gz /system/initrd.gz. (even system can not be booted into the launcher or sense, in some point of time, the adb still can function, so just keep trying.)
Caution: if your build current use app2sd, you have to disable it before using this, rename the init.local.rc under etc to init.local.rc.bak, remove the 00start, 04apps2sd from /system/etc/init.d.
If your build uses boot partition, you should change the installation script to push the initrd.gz to replace the existing one wherever it is.
Thanks to
- ownhere (he is the expert of the ext4 or other file systems, and developed the data2ext.)
- melethron (the author of data2whatever)
- Takaaki (the author of data2sd)
- Cedesmith (He is guru of initrd )
Donation
I do not work for money, but it is always nice to know people really like my work and encourage me carrying on.
Please could you provide also information in case that NAND rom already use EXT4 for data2ext4 (like AF403 DesireHD stock based 1.0a)?
Good stuff.. thank you!
I am trying your NAND ROM now....
Good knowledge ... keep up cool stuff
i already use ur nand rom
If you don't want to look into the code to find out the difference, then, how about just try 1st.
totalcmdext said:
Please could you provide also information in case that NAND rom already use EXT4 for data2ext4 (like AF403 DesireHD stock based 1.0a)?
Click to expand...
Click to collapse
Sent from my DL DesireZ v2.5 using XDA App
Ok, i've managed to understand the concept of data2ext, and when on initial setup everything gets what i expect, i've 1 GB (depends on ext partition size) of free memory space, but i get an horrible performance even if formated with your tool, i guess it's SD performance/quality because i can't run any ext build published here where most of users claim to get good performance. So i try data2sd but instead of the 512MB (img size created with this) of memory i get only the 80MB of the free nand internal ram. What is stored on this img file ? only settings ? On 20 applications i use only 4 are movable to sd, so after my initial setup (and of course with good performance) i get a lot of memory low warnings.
Thanks
Looks like the data2sd was not enforced, what's your configuration in config.txt?
jpl69 said:
Ok, i've managed to understand the concept of data2ext, and when on initial setup everything gets what i expect, i've 1 GB (depends on ext partition size) of free memory space, but i get an horrible performance even if formated with your tool, i guess it's SD performance/quality because i can't run any ext build published here where most of users claim to get good performance. So i try data2sd but instead of the 512MB (img size created with this) of memory i get only the 80MB of the free nand internal ram. What is stored on this img file ? only settings ? On 20 applications i use only 4 are movable to sd, so after my initial setup (and of course with good performance) i get a lot of memory low warnings.
Thanks
Click to expand...
Click to collapse
Sent from my DL DesireZ v2.5 using XDA App
This is good and detail steps http://forum.xda-developers.com/showpost.php?p=10666187&postcount=341 on how to config, better than mine
Sent from my DL DesireZ v2.5 using XDA App
If i understand this, this is only change existing inird with modified initrd?
I'm sorry but with all this flash/unflash install/uninstall download configure i've lost my config, but i'm sure data_img=1 and data_ext=0
(just a note gps_zone=pt should configure gps to be used here in Portugal right ?)
If you say that it should work i'm going further with my tests and post here results because i don't want to flame this thread.
Update:
I've a stock 8GB class 4 card swaped with 4GB class 2, results on nand/ext4:
Initial setup (with format ext4) 1/2 time, second boot 1 minute and everything runing muuuch smother and faster so or i've got a malfunction card (?) (and i've read someone complaining about a 16GB class 10) or lowest class gets more speed (?)
Update2:
The diference is really amazing, i've got a completly functional android now with this card.
You should mention on your threads that if you get bad results on initial setup forget about that nand, return to SD builds or get other card.
Can you please post your card type please ?
how long does it take to format the ext4?
Hi,
I am trying to setup this new initrd, i put the format ext4 parameter in the config file and start my HD2.
wondering how long will it take to format my 1G ext4 partition?
thanks!
data.img Question
3. copy old data.img to '.data' directory, otherwise a new data.img will be created. ... Can I somehow set how big will the data.img be ?
Default will be 512M, you can config it by data_size.
BoneMo said:
3. copy old data.img to '.data' directory, otherwise a new data.img will be created. ... Can I somehow set how big will the data.img be ?
Click to expand...
Click to collapse
Sent from my DL DesireZ v2.5 using XDA App
Looks promising
This new initrd and file management seems well thought through and very promising.
In other builds I experienced that there can be a huge performance difference between the different file management choices (full NAND > adsd > ads2+ > data2ext > data2sd). It's good to see that you got into this subject and tried to find an optimal solution which can be configured by other chefs.
I assume that you implemented all this in your own DL DesireZ v2.5 build? If I find time I'm certainly gonna give it a try!
Keep up the good work!
works with AF403 DesireHD stock based 1.0a
there are a lot of discussions on my nand build about mixing using all the parameters, some got the performance improved a lot, some got things worse, your can refer to that to config your build for the best performance.
Dear, i got this error message...
D:\a>install
back your initrd...
remote object '/system/initrd' does not exist
replace your initrd...
1442 KB/s (0 bytes in 1523605.001s)
failed to copy 'mkfs.ext4' to '/system/xbin/mkfs.ext4': No space left on device
1263 KB/s (0 bytes in 303212.000s)
1410 KB/s (0 bytes in 428664.000s)
Unable to chmod /system/xbin/mkfs.ext4: No such file or directory
Unable to chmod /system/xbin/e2fsck: No such file or directory
Press any key to continue . . .
please help... I am using Gauner1986 build
Looks like the system in Gauner1986 build is read only or have the boot partition, or really occupied all the space? anyway, your existing build should be unchanged.
you can try adb shell ls /system, or adb shell ls /boot, whether there is an initrd.gz under it, then, manually push all the necessary files.
rasumia said:
Dear, i got this error message...
D:\a>install
back your initrd...
remote object '/system/initrd' does not exist
replace your initrd...
1442 KB/s (0 bytes in 1523605.001s)
failed to copy 'mkfs.ext4' to '/system/xbin/mkfs.ext4': No space left on device
1263 KB/s (0 bytes in 303212.000s)
1410 KB/s (0 bytes in 428664.000s)
Unable to chmod /system/xbin/mkfs.ext4: No such file or directory
Unable to chmod /system/xbin/e2fsck: No such file or directory
Press any key to continue . . .
please help... I am using Gauner1986 build
Click to expand...
Click to collapse
dandiest said:
Default will be 512M, you can config it by data_size.
Sent from my DL DesireZ v2.5 using XDA App
Click to expand...
Click to collapse
So you mean data_size= ... (512,1024,2048)
This is in cofig.txt?
jan-willem3 said:
So you mean data_size= ... (512,1024,2048)
This is in cofig.txt?
Click to expand...
Click to collapse
Yes, but please don't use 2048.
SO basically im trying something out and i need to add a partition to my android device thats about 100mb big. Is this possible? the Sdcard wont work as a partition
I've seen it done, but for some reason the OS will repartition it back to what it was before you edited it.
Best route would be to dump your current PIT file (partition table and other info is included in there) and modify it to fit your needs if possible. There are probably other threads on this if you search up "modifying PIT file"
CNexus said:
I've seen it done, but for some reason the OS will repartition it back to what it was before you edited it.
Best route would be to dump your current PIT file (partition table and other info is included in there) and modify it to fit your needs if possible. There are probably other threads on this if you search up "modifying PIT file"
Click to expand...
Click to collapse
will modifying that file be able create an extra 100mb partition so when i hook it into my comp two partitions show up?
That file can be used to repartition the phone. If you modify it correctly you should be able to resize other partitions and use that extra space to create your own XXX mb partition.
CNexus said:
That file can be used to repartition the phone. If you modify it correctly you should be able to resize other partitions and use that extra space to create your own XXX mb partition.
Click to expand...
Click to collapse
Alright thanks im looking into it know do you know how to dump one from a phone? as google is not bringing up anything besides info on what it is
You need to use heimdall but there are existing ones out there depending on what size your internal storage is
16 gb or 32?
CNexus said:
You need to use heimdall but there are existing ones out there depending on what size your internal storage is
16 gb or 32?
Click to expand...
Click to collapse
its a 16gb lph 710 ill look into heimdall thanks
What's your current bootloader version? If not known, run
Code:
getprop ro.bootloader
In a shell on your device/terminal emulator app
And then post the last three alphanumeric characters
Sorry I realized the bios of a comp doesn't recognize the android phone as a peripheral or a mountable boot device which ruins my plans as of now I'm going to try to find a way to at least get the bios to pickup the SDcard if I can I'm doubtful though
Noogie was the image to put on the NST so that you could backup or restore the entire internal memory.
It was usually put on the removable SD card.
In fact, it could have been just booted directly through fastboot.
Later, people worked on and succeeded on a way to boot up the NST without any valid internal memory at all.
This made the NST unbrickable.
Neo Noogie is pretty much the same, but updated for the Glow2 & Glow3.
Since these models don't have a removable SD card they need to be able to boot over fastboot.
This means that if you totally wipe out the memory on your Nook (including where fastboot is) you'll be bricked.
(That is, until we get working on a USB bootloader method.) We do have a bootloader, see https://forum.xda-developers.com/nook-touch/general/fix-bricked-glow2-3-4-t4002911
Warning: Windows will offer to format anything it doesn't understand! Do not format!
Code:
C:\>adb reboot fastboot
C:\>fastboot boot nnglow2.img
<use your favorite utility to copy to/from the disk that appears>
C:\>adb reboot
Update
New versions as of 2019-12-18, nnglow2.img, nnglow3.img, nnglow4.img
Download through the signature
Renate NST said:
Noogie was the image to put on the NST so that you could backup or restore the entire internal memory.
It was usually put on the removable SD card.
In fact, it could have been just booted directly through fastboot.
Later, people worked on and succeeded on a way to boot up the NST without any valid internal memory at all.
This made the NST unbrickable.
Neo Noogie is pretty much the same, but updated for the Glow2 & Glow3.
Since these models don't have a removable SD card they need to be able to boot over fastboot.
This means that if you totally wipe out the memory on your Nook (including where fastboot is) you'll be bricked.
(That is, until we get working on a USB bootloader method.)
Warning: Windows will offer to format anything it doesn't understand! Do not format!
Click to expand...
Click to collapse
Can you add md5 sums for the images?
eriol1 said:
Can you add md5 sums for the images?
Click to expand...
Click to collapse
Neo Noogie does four things:
It boots up without mounting any partitions at all
It presents the entire internal SD card as a UMS volume over USB
It supports ADB
It supports the hardware console shell (Ok, most people didn't install a jack in their Nook)
None of this has anything to do with MD5.
But I'm glad you brought it up.
You can get an MD5 of the internal SD card (only when Neo Noogie is running, not when B&N has everything mounted).
Code:
# md5sum /dev/block/mmcblk0
0a1c3941a12abff93b44a2603381ad12 /dev/block/mmcblk0
It reliably generates the same MD5 since nothing is changing.
After you have pulled the 4 or 8 GB over to your host machine, you can likewise calculate the MD5.
Right now I seem to be getting two different MD5's despite the MD5's being repeatable (on either end) and multiple transfers give no differences.
Renate NST said:
Neo Noogie does four things:
It boots up without mounting any partitions at all
It presents the entire internal SD card as a UMS volume over USB
It supports ADB
It supports the hardware console shell (Ok, most people didn't install a jack in their Nook)
None of this has anything to do with MD5.
But I'm glad you brought it up.
You can get an MD5 of the internal SD card (only when Neo Noogie is running, not when B&N has everything mounted).
It reliably generates the same MD5 since nothing is changing.
After you have pulled the 4 or 8 GB over to your host machine, you can likewise calculate the MD5.
Right now I seem to be getting two different MD5's despite the MD5's being repeatable (on either end) and multiple transfers give no differences.
Right now it's a head scratcher.
Click to expand...
Click to collapse
I actually just meant md5 of the bootable img files, so we can make sure the file is intact before booting.
But it seems you hit an interesting issue so I guess we're lucky I didn't explain myself properly
eriol1 said:
I actually just meant md5 of the bootable img files...
Click to expand...
Click to collapse
Oh...
Code:
nnglow2.img
[strike]21ce45fe df9abe3f 882c73fa 4928d091[/strike] [color=red]Obsolete numbers[/color]
nnglow3.img
[strike]1e3975db 5b0a8a3b 7c6cbf60 ef8e2449[/strike] [color=red]Obsolete numbers[/color]
Something strange is going on with the 8G MD5s, but not the files themselves.
I generate 233 MD5s on 32Meg chunks.
All 233 are identical on both sides!
I generate a single MD5 over the entire thing and they are not the same.
Ok, no problem at all.
What I was seeing was an MD5 utility on my Windows box that hadn't anticipated files > 4G.
MD5's of the transferred images (4GB or 8GB) on Nook and host agree.
Renate NST said:
Oh...
Something strange is going on with the 8G MD5s, but not the files themselves.
I generate 233 MD5s on 32Meg chunks.
All 233 are identical on both sides!
I generate a single MD5 over the entire thing and they are not the same.
Ok, no problem at all.
What I was seeing was an MD5 utility on my Windows box that hadn't anticipated files > 4G.
MD5's of the transferred images (4GB or 8GB) on Nook and host agree.
Click to expand...
Click to collapse
I was just about to suggest something along those lines
Good to know there's no deeper issue. Thanks!
Renate NST said:
(That is, until we get working on a USB bootloader method.)
Click to expand...
Click to collapse
Like i.imx6 usb recovery mode?
https://boundarydevices.com/unbricking-nitrogen6x-sabre-lite-i-mx6-board/
But, I don't really think it will be possible without disassembly.
RyogoNA said:
But, I don't really think it will be possible without disassembly.
Click to expand...
Click to collapse
Right, it's not so friendly as the OMAP in the NST.
You have to play with the boot mode jumpers (which don't physically exist on this board).
You might me able to ground an easily accessible test point.
OTOH, if you've gone that far a JTAG interface would work too.
Big oops on my part
I accidentally left the setting in Neo Noogie for the internal SD card in read-only.
It's actually not a big deal (ahem, since no one complained).
Any backups that you made are fine.
It just means that you can't write them back into the Nook this second using that version of Neo Noogie.
Keep on making backups if you like.
I'll put up new versions of Neo Noogie in a bit.
I put new versions of the images in the first post's attachments.
The simple change was just to omit the read-only flag for the internal SD card.
I did a bunch of cleanup that you will probably not notice unless you use the shell.
Rant
Ever see that "__bionic_open_tzdata: couldn't find any tzdata" when running TWRP or other images?
The libc.so wants to get its hands on information about timezones.
Sometimes it's missing and then you get three lines of that gobble-dee-gook error message every time you use any command.
The simple solution is to park the tzdata somewhere (and patch libc.so with the hard-coded path).
All this just to say, "Ok, just use UTC and don't give me the stupid error messages continuously"?
Well, it's stupider. The full tzdata is 0.5 Megs.
Why? So we can have timezones for every podunk village on the globe (576 timezones).
I'm using a modified version of tzdata that includes only UTC and is 194 bytes.
Renate NST said:
Noogie was the image to put on the NST so that you could backup or restore the entire internal memory.
It was usually put on the removable SD card.
In fact, it could have been just booted directly through fastboot.
Later, people worked on and succeeded on a way to boot up the NST without any valid internal memory at all.
This made the NST unbrickable.
Neo Noogie is pretty much the same, but updated for the Glow2 & Glow3.
Since these models don't have a removable SD card they need to be able to boot over fastboot.
This means that if you totally wipe out the memory on your Nook (including where fastboot is) you'll be bricked.
(That is, until we get working on a USB bootloader method.)
Warning: Windows will offer to format anything it doesn't understand! Do not format!
Code:
C:\>adb reboot fastboot
C:\>fastboot boot nnglow2.img
<use your favorite utility to copy to/from the disk that appears>
C:\>adb reboot
Update
New versions as of 2018-05-04
nnglow2.img c52e433e 1340acd8 f4d89f9b fa572334
nnglow3.img 6bf28a03 aaa24b93 584a8c35 09cf3a0c
Click to expand...
Click to collapse
Hello - neewby here - I got the Nook Glowlight Plus -
is this a custom image ?ROM?
Thank you
DanChr79 said:
is this a custom image? ROM?
Click to expand...
Click to collapse
It's not really a ROM because it's doesn't run Android or apps.
It is a custom image because it is a minimal OS.
Its only purpose is to allow you to copy the full internal memory to/from your desktop computer.
There are three ways to boot up an OS:
From the boot partition (normally the regular OS)
From the recovery partition (normally the factory restore routine)
Downloaded over fastboot (normally not used)
Renate NST said:
It's not really a ROM because it's doesn't run Android or apps.
It is a custom image because it is a minimal OS.
Its only purpose is to allow you to copy the full internal memory to/from your desktop computer.
There are three ways to boot up an OS:
From the boot partition (normally the regular OS)
From the recovery partition (normally the factory restore routine)
Downloaded over fastboot (normally not used)
Click to expand...
Click to collapse
Thank you for the reply
Then do you know of a customer rom or how to root the device?
The posts here are super old and I am not sure how to fully use (full android) my new Glowlight Plus?
DanChr79 said:
Then do you know of a customer rom or how to root the device?
Click to expand...
Click to collapse
Well, there's a million ways to root it, but since you're on this thread, we can do it this way.
Code:
C:\>adb reboot fastboot
C:\>fastboot devices
1234567812345678 fastboot
C:\>fastboot boot nnglow2.img [color=red]nnglow2 for Glowlight Plus[/color]
C:\>adb shell
# echo /dev/block/mmcblk0p1 > /sys/devices/platform/fsl-usb2-udc/gadget/lun0/file
# cat /sys/devices/platform/fsl-usb2-udc/gadget/lun0/file [color=red]this is just a check to make sure that it worked[/color]
/dev/block/mmcblk0p1
# ^D
C:\>sdcard /r G p1.img [color=red]might not be G, use File Explorer and see what letter it is[/color]
SD card G, disk #3, 6,258,688 bytes, 512 sector size
C:\p1.img, 0 bytes
Copy SD card G to image (Y or N)? y
Copying SD card G to C:\p1.img
100%
Finished
C:\>imgutil /x p1.img default.prop
[color=red]Use a real text editor (not Notepad!) to change ro.secure=0 and ro.debuggable=1[/color]
C:\>imgutil /r p1.img default.prop
C:\>sdcard /w G p1.img [color=red]we're writing now, make sure everything was correct![/color]
SD card G, disk #3, 6,258,688 bytes, 512 sector size [color=red]make sure that this number is exactly the same as the first time![/color]
C:\p1.img, 4,421,632 bytes [color=red]this number will be somewhere around this, less than the 6.2M[/color]
Copy image to SD card (Y or N)? y
Copying C:\p1.img to SD card G
100%
Finished
C:\>adb reboot
sdcard.exe and imgutil.exe are in the signature, nnglow2.img is in the first post of this thread.
Renate NST said:
Well, there's a million ways to root it, but since you're on this thread, we can do it this way.
Code:
C:\>adb reboot fastboot
C:\>fastboot devices
1234567812345678 fastboot
C:\>fastboot boot nnglow2.img [color=red]nnglow2 for Glowlight Plus[/color]
C:\>adb shell
# echo /dev/block/mmcblk0p1 > /sys/devices/platform/fsl-usb2-udc/gadget/lun0/file
# cat /sys/devices/platform/fsl-usb2-udc/gadget/lun0/file [color=red]this is just a check to make sure that it worked[/color]
/dev/block/mmcblk0p1
# ^D
C:\>sdcard /r G p1.img [color=red]might not be G, use File Explorer and see what letter it is[/color]
SD card G, disk #3, 6,258,688 bytes, 512 sector size
C:\p1.img, 0 bytes
Copy SD card G to image (Y or N)? y
Copying SD card G to C:\p1.img
100%
Finished
C:\>imgutil /x p1.img default.prop
[color=red]Use a real text editor (not Notepad!) to change ro.secure=0 and ro.debuggable=1[/color]
C:\>imgutil /r p1.img default.prop
C:\>sdcard /w G p1.img [color=red]we're writing now, make sure everything was correct![/color]
SD card G, disk #3, 6,258,688 bytes, 512 sector size [color=red]make sure that this number is exactly the same as the first time![/color]
C:\p1.img, 4,421,632 bytes [color=red]this number will be somewhere around this, less than the 6.2M[/color]
Copy image to SD card (Y or N)? y
Copying C:\p1.img to SD card G
100%
Finished
C:\>adb reboot
sdcard.exe and imgutil.exe are in the signature, nnglow2.img is in the first post of this thread.
Click to expand...
Click to collapse
Thank you so much for your time and reply.
This will root the device?
I will still need a custom rom ? android to install on it?
Is there a script available or BAT file since I am a computer noob?
DanChr79 said:
Thank you so much for your time and reply.
This will root the device?
I will still need a custom rom ? android to install on it?
Is there a script available or BAT file since I am a computer noob?
Click to expand...
Click to collapse
This will give you shell root access.
What you want to do with it is another question.
I don't have a script.
There may be other threads on this forum that use different approaches, do a dozen things and have scripts.
I haven't really paid any attention because I just rooted my devices with a hardware root console.
Renate NST said:
This will give you shell root access.
What you want to do with it is another question.
I don't have a script.
There may be other threads on this forum that use different approaches, do a dozen things and have scripts.
I haven't really paid any attention because I just rooted my devices with a hardware root console.
Click to expand...
Click to collapse
Danke Renate....
Usually after rooting, customers image will be applied to phones or tablets no?
So I root it and then.... I am able to use custom apk?
DanChr79 said:
So I root it and then.... I am able to use custom apk?
Click to expand...
Click to collapse
If you just want to install an APK, you can just install an APK without rooting.
Have you tried that yet?
Code:
C:\>adb install whatever.apk
I could be wrong. I've never had an unrooted Nook.
Does anyone has a glow3 backup that can share?
I "managed" to brick mine and I will need images to (hopefully) revive it.
Can anyone point me to a recovery guide via USB?
I suppose I should be able to start u-boot via mfgtool/uuu/imx_usb_loader with fastboot enabled and recover partitions content from there?
Thanks,
C
cipibad said:
I should be able to start u-boot via mfgtool/uuu/imx_usb_loader
Click to expand...
Click to collapse
A late response, but...
I've tried various of the iMX loaders and didn't have much luck, so I wrote my own, imxboot.exe
It's available in the signature.
There are three new Neo Noogie images to download for the Glow2, 3, 4.
There has been a bit of cleanup and a few improvements.
It's easier to mount partions now, no need to do all the parameters yourself.
Code:
# mount system
# mount data
@Renate NST
Please add md5 for images
And update thread name to " & Glow4"
Thank you for all your work!