This build is ported from http://forum.xda-developers.com/showthread.php?t=1867986 using Portadroid forum.xda-developers.com/showthread.php?t=1094372 Credits and thanks to Rick_1995, boonbing for Portadroid, cyanogenmod, cmhtcleo team (arif-ali, milaq, charansingh and all other cm developers) for device tree, tytung for kernel, Darkstone1337 for SuperRAM concept, and any others we forgot.
Instructions:
Well you know just extract everything and put the build folder (the one with all the files in, for example ics, jelly) in the root of your sd card. If WM6.5 tap on clrcad (nothing appears to happen) then haret, if magldr navigate to build folder using ad-sd dir and select build folder name then boot AD SD.
Please remember to REBOOT X 3.
Magldr users can get different sized blank data.ext4 from here forum.xda-developers.com/showpost.php?p=24930501&postcount=1353 edit; may get boot loops, please test. Magldr default=512Mb if you leave empty. edit2 here is blank 256mb one http://www.mediafire.com/?ey40c1wti77ni2w
Downloads
Barebone CM7 V3 -Latest SuperRAM build from Rick_1995 see this post http://forum.xda-developers.com/showpost.php?p=42007074&postcount=64
note that this is not a port from nand rom, but an exclusive SuperRAM build from Rick_1995
There is a problem for magldr users changing lcd density, a solution is posted here http://forum.xda-developers.com/showpost.php?p=47161712&postcount=78 (thanks to Calisto1986 for the heads up). HaRET users are unaffected and can edit startup.txt as usual
Barebone CM7 V2b SRAM
DEV-HOST LINK
Barebone CM7 V2 SRAM
DEV-HOST LINK
Barebone CM7 SRAM
DEV-HOST LINK
This is from parent thread by Rick_1995
Note: I compiled this rom for myself but figured sharing won't hurt, and hence I don't plan to provide much support though I'll see what i can if you find a bug.
What is the difference between this and the nightly ?
All libraries and native code is compiled in ARM mode (except for libwebkit which is still in thumb mode due to it's excessive size) and compiler side optimization is turned on (again, exception being libwebkit using -Os and sqllite using -fno-fast-math).
Important function calls and syscalls are aligned for faster response time.
I re-implemented some of the cpu atomic functions based on what I've learned so far, swp is used for atomic swap instead of ldrex/strex, register swapping of old value is done at success so if a context switch does occur, the loop will be aligned at the same boundary as the function. On best case, there shouldn't be any difference but can improve execution time for worst case of context switches.
Java libraries and bionic libc are compiled with NDEBUG, and the debug variable for java is also set to false.
Most crap (stuff that "I" do not use, has been removed ie. VPN, live wallpaper support etc..)
Fixed a few memory leaks in bionic, dalvik and ppp (also tether).
I've removed most locales except en_US and en_GB, though android still seems to be compiling strings from other languages in the build, so they might work but i can't guarantee anything with locales other than en_(US|GB). Arabic patch
Reverted the patch which auto closed notification bar when all notifications are canceled/removed. It was irritating me..
more stuff i don't remember.
For now the kernel is tytungs-r1 ics kernel patched for gingerbread, though I will be patching/updating and working on the cmhtcleo kernel once i have the build known to be bug free after some time.
Click to expand...
Click to collapse
One more............
thans wiss....very quick port ....
Touch selection sound does not work for me.... others looks good so far...
Is it possible to run SD build from CLK? Just dont wanna install MAGLDR again, it`s so terrible for compability with Linux
Just get new micro sd card from SanDisk, its class 10, 95 mb per second -- its the most speediest micro sd in the world (micro SDHC UHS-I Card: Extreme Pro 8 GB)
Update: I`ve installed this rom twice with custom size about 4096 but everytime ive got near 512 mb. WHY?
aion92 said:
Is it possible to run SD build from CLK? Just dont wanna install MAGLDR again, it`s so terrible for compability with Linux
Just get new micro sd card from SanDisk, its class 10, 95 mb per second -- its the most speediest micro sd in the world (micro SDHC UHS-I Card: Extreme Pro 8 GB)
Update: I`ve installed this rom twice with custom size about 4096 but everytime ive got near 512 mb. WHY?
Click to expand...
Click to collapse
Because you're not setting proper command line, if you're booting from magldr, you just can't do this. If you're booting from clk, while creating boot image, set the cmdline exactly as in startup.txt and modify the partition size then flash that to a secondary boot partition, now just boot on secondary boot partition for the SD rom. I think suspend wasn't working properly with clk on sd roms, have to see why.
If it's from haret (unlikely) just edit size in startup.txt
@wis, thanks for the port, might use it sometime in the future when i try the new WP builds
Thanks Rick_1995 and Learning Never Ends team for this GREAT ROM!
I tried to change the LCD density in the system.ext4/build.prob. 192 is shown if i open the /system/build.prob in root explorer but this doesnt effect the rom... What can i do to set it to 192?
Thanks Wis (although I think you should be concentrating on something outside xda!).
Any advice on how to get option for "Corporate" Accounts?
This could be my favourite
Cheers
Tom
Sent from my HTC HD2 using Tapatalk 2
Please make this ROM compatible with NativeSD mod. Cm7 is the most perfomance android series for me, for now...
aion92 said:
Please make this ROM compatible with NativeSD mod. Cm7 is the most perfomance android series for me, for now...
Click to expand...
Click to collapse
Hmm... I may be wrong here, but from my understanding...
The NativeSD method writes to partitions on an SDCard...
SuperRAM ROMS mount to RAM which is faster than both NAND and SDCard...
So I would assume by modifying this to use NativeSD would be more detrimental than good?
yep, RAM is faster but, for my needs, more free RAM better than overall speed and this rom\Android build eats as little RAM as possible, so its just great rom which perfactly fits for my needs but NativeSD gives me internal storage (up to 32 gigs from 512 mb) and it can be launched from CLK loader.
aion92 said:
yep, RAM is faster but, for my needs, more free RAM better than overall speed and this rom\Android build eats as little RAM as possible, so its just great rom which perfactly fits for my needs but NativeSD gives me internal storage (up to 32 gigs from 512 mb) and it can be launched from CLK loader.
Click to expand...
Click to collapse
For your internal storage needs (NativeSD's "internal" storage is determined by your ext partition size, you still require fat partition with nativesd, so, unless you have a 64gb card working with your hd2, you likely wouldn't have 32gigs "internal") you can resize your data.img file to whatever size you like. You can use the tool "Toporesize" I believe it's called, or something like that. Also, you can investigate other scripts to install such as Apps2sd.
Other than that, the only thing to tell you is that as of right now, from my understanding, the NativeSD method requires certain kernel mods apparently, which means it's limited to ics/jb builds for now.
Version V2 please!This is great, thanks:good:
strikelight said:
For your internal storage needs (NativeSD's "internal" storage is determined by your ext partition size, you still require fat partition with nativesd, so, unless you have a 64gb card working with your hd2, you likely wouldn't have 32gigs "internal") you can resize your data.img file to whatever size you like. You can use the tool "Toporesize" I believe it's called, or something like that. Also, you can investigate other scripts to install such as Apps2sd.
Other than that, the only thing to tell you is that as of right now, from my understanding, the NativeSD method requires certain kernel mods apparently, which means it's limited to ics/jb builds for now.
Click to expand...
Click to collapse
Ok, thanks, I`ll try expand my storage with "Toporesize" then.
Update: after some researching ive managed to have 4 gigs of storage even without toporesize - with MAGLDR startup.txt config of 4096 gb does nothig for me earlier, but with sboot + CLK it works great! My problem is solved, yay!
Update2: aaand... after 1 reboot the rom just doesnt boot at all ... ill try to install one more time then.
Barebone CM7 V2 SRAM
Barebone CM7 V2 SRAM is now on post 1:good:
So, every time when i make a reboot or shut down from working rom, the data.ext4 clean itself to 0 bytes. I use CLK + sboot \ sboot tools, 4096 mb automatic generated data file. Any ideas?
Strychnin said:
Thanks Rick_1995 and Learning Never Ends team for this GREAT ROM!
I tried to change the LCD density in the system.ext4/build.prob. 192 is shown if i open the /system/build.prob in root explorer but this doesnt effect the rom... What can i do to set it to 192?
Click to expand...
Click to collapse
As this a super ram version you need to change it in a special way but for the life of me i cant remember howlol
When Robbie reads this im sure he will post the instructions
Sent from my HTC HD2 using Tapatalk 2
This is so great project but why not releasing NativeSD version? Such minimal ROM would act routinely writing on SD much less than Paranoid or AOKP so it seems ideal SD-born! This way we could have fast SD Android for regular use dual booted with WM like Artemis (which is still maintained) thus yielding the fastest and the most versatile smartphone of the world!
ictimai said:
This is so great project but why not releasing NativeSD version? Such minimal ROM would act routinely writing on SD much less than Paranoid or AOKP so it seems ideal SD-born! This way we could have fast SD Android for regular use dual booted with WM like Artemis (which is still maintained) thus yielding the fastest and the most versatile smartphone of the world!
Click to expand...
Click to collapse
At the moment there is no surport for cm7 but i dont think it will be long
Sent from my HTC HD2 using Tapatalk 2
wis1152 said:
As this a super ram version you need to change it in a special way but for the life of me i cant remember howlol
When Robbie reads this im sure he will post the instructions
Sent from my HTC HD2 using Tapatalk 2
Click to expand...
Click to collapse
:laugh:
edit line in /bootsystem/build.prop ro_lcd_density=240 to whatever using a root browser, and reboot.
Related
My HD2 have flash everything include HSPL and radio (2.08.HSPL & radio 2.15.50.14) and my ROM is 1.48.832.1(71294)CHT . l don't know why my HD2 can't run android . Can anyone answer me?
The only thing left really is your SD card. Do you have a different one you can try?
Also, what actually happens when you run Android?
johncmolyneux said:
The only thing left really is your SD card. Do you have a different one you can try?
Also, what actually happens when you run Android?
Click to expand...
Click to collapse
sorry l just have a sandisk class 2 4GB....
btw l will post a image later and let you know what is happened
ccl1996312 said:
sorry l just have a sandisk class 2 4GB....
btw l will post a image later and let you know what is happened
Click to expand...
Click to collapse
No need for an image - just tell us what you do and what the result is.
johncmolyneux said:
No need for an image - just tell us what you do and what the result is.
Click to expand...
Click to collapse
when my hd2 is booting android ,it stopped at here...
Running an fsck on SD card
dosfsck 3.0.1 23 Nov 2008, FAT32, LFN
logical sector size zero
mount: mounting /dev/block/mmcblk0p1 on /sdcard failed:invalid argument
failed
failed to mount sd card ,cannot continue
/bin/sh: can't access tty; job controlled turned off
Okay. Try reformatting your SD card. Use Disk Management (not right-click and format) on your PC and set the cluster size to the largest it will let you use.
Then copy Android back onto it and give it another try.
Just to be sure as well, are you definitely putting the Android folder directly onto the root of your SD card?
Also, finally, can you paste the contents of startup.txt here, just in case.
johncmolyneux said:
Okay. Try reformatting your SD card. Use Disk Management (not right-click and format) on your PC and set the cluster size to the largest it will let you use.
Then copy Android back onto it and give it another try.
Just to be sure as well, are you definitely putting the Android folder directly onto the root of your SD card?
Also, finally, can you paste the contents of startup.txt here, just in case.
Click to expand...
Click to collapse
set mtype 2524
set ramaddr 0x20000000
set ramsize 0x0fc00000
set initrd_offset 0x00a00000
set KERNEL zImage
set initrd initrd.gz
set cmdline ""
boot
^
^
this is the content of startup.txt
btw thx for your help , l'll follow your instruction to configure it
Which build are you using?
johncmolyneux said:
Which build are you using?
Click to expand...
Click to collapse
dan1j3l-LeoFroyo-Sense-PR1
From what I can see, he stopped work in July on his Sense builds. I can't even find a thread for that particular build.
I strongly recommend you get something new. The old builds had lots of problems that have been resolved in most, if not all, newer builds.
What in particular are you looking for from your build, because if you just want Sense, but something stable then give this a try...
http://forum.xda-developers.com/showthread.php?t=859817
I'm using that at the minute and after a slow start (a few reboots sorted it), it's running like a dream now.
johncmolyneux said:
From what I can see, he stopped work in July on his Sense builds. I can't even find a thread for that particular build.
I strongly recommend you get something new. The old builds had lots of problems that have been resolved in most, if not all, newer builds.
What in particular are you looking for from your build, because if you just want Sense, but something stable then give this a try...
http://forum.xda-developers.com/showthread.php?t=859817
I'm using that at the minute and after a slow start (a few reboots sorted it), it's running like a dream now.
Click to expand...
Click to collapse
Agree with you sir; MDJ FroYo HD builds runs like a charm.
Hi All.
It's my thread - port Android on Wave S8500(also S8530).
Wellcome developers and designers.
Last state of project:
06/13/2011 Now working on Android 2.3.3 (Source GB for GT-I9000 and M130K)
not working - modem and GPS.
04/04/2011 Memory allocation now is correct!
05/11/2011 I have full schematic for phone
and we're ready to get a fully working kernel.
Full decriptions of GPIO is attached.
source for kernel and initramfs here:
github.com/Oleg-k/S8500_Kernel_2.6.32
github.com/Oleg-k/initramfs_2.6.32_S8500
(real shame if you ask me)
Click to expand...
Click to collapse
Please expect not too much from me.
1.
My other handsets are from 2006... NEVER hold Android handset in my own Hand...
2.
I'm Windows User.
Linux/Unix ... I know only 1 or 2 Commands
I've never formated my SD Card nor any Harddrive with Linux ext4, JFS, ReiserFS or XFS
3.
I NEVER worked with IDA or something similar.
Installed yes, but then my Head exploded
Brain too small.
4.
Many missing parts...
Why I should kill my alive handset, as I have no real chance to reanimate it...
- no Riff Box
- no PCB to play with
I AM NOT the right man to port Android nor to find Security hole
You can make this post sticky.
NO joke, expect not too much from me. We can learn together... but this takes time.
Many time. Months, maybe years...
Best Regards
after many many variant, i found the right boot+sbl+param.lsf for kernel message output.
this is my last bootlogo.
how it can be seen, there is a problem with memory allocation.
oleg_k said:
after many many variant, i found the right boot+sbl+param.lsf for kernel message output.
this is my last bootlogo.
how it can be seen, there is a problem with memory allocation.
Click to expand...
Click to collapse
Great of you to keep us posted! \o/
hmmm... as a matter of interest - I noticed you're using kernel 2.6.35.7, when I look at the original I9000 source that's 2.6.29....
what does that source say as to why it failed in bootmem.c @ line 341?
Not enough memory, permissions, wrong offset?
oleg_k said:
not yet( Starting but don't finish.
Click to expand...
Click to collapse
Whats not happening? Oleg_k would you be able to PM me with a copy of your work, files and so forth i might be able to help you out.
t0mm13b said:
+1 for bootloaders - abso-frickin-lutely....there should be a standard bootloader... meh.... not sure about meteor - haven't seen it...
Click to expand...
Click to collapse
Well I'm holding a meteor wave here, bought around christmas. How much onboard storage does you device have? mine says it only has 512 i think... stupid meteor thinking i wouldn't notice....
sabianadmin said:
Well I'm holding a meteor wave here, bought around christmas. How much onboard storage does you device have? mine says it only has 512 i think... stupid meteor thinking i wouldn't notice....
Click to expand...
Click to collapse
You mean to tell me that Meteor bundled a 512Mb memory card?
I have 4Gb on mine...this memory thing is a bit mystifying dontcha think, despite the discussion on another thread about the nand chipset.... on the one hand some say its 256Mb, others say 512Mb...
I tried the versions 2.6.32 and 2.6.35.
I post sbl+boot+param.lfs and config file for kernel making.
Last time u had problem with lcd_rst pin..did u figure that out?
t0mm13b said:
You mean to tell me that Meteor bundled a 512Mb memory card?
I have 4Gb on mine...this memory thing is a bit mystifying dontcha think, despite the discussion on another thread about the nand chipset.... on the one hand some say its 256Mb, others say 512Mb...
Click to expand...
Click to collapse
No i mean Meteor gave me some (seeminly non existant) version of the wave that has 512 internal storage. Im pretty sure its meant to have 2-4gb at the minimum.
sabianadmin said:
No i mean Meteor gave me some (seeminly non existant) version of the wave that has 512 internal storage. Im pretty sure its meant to have 2-4gb at the minimum.
Click to expand...
Click to collapse
Wave have 2gb of internal storage, but only 512mb are free for the user.
Otacon_ahs said:
Wave have 2gb of internal storage, but only 512mb are free for the user.
Click to expand...
Click to collapse
Wave S8500 have 2Gb of internal storage which are partitioned (bada 1.0.2):
-about 512Mb for messages (mail+sms);
-about 420Mb for user files;
-about 1Gb for system files (os+apps+widget+java)
You can find it in: Setting-->Memory-->Memory Status-->Common Memory
@ oleg_k
1.
How to bypass to write/overwrite Boot without JTAG?
I stuck in problems with Multiloader to write decrypted unmodified Original Boot. See here:
http://forum.xda-developers.com/showpost.php?p=12607344&postcount=34
2.
How to build valid Bootimage for JTAG or file(s) to use your uploaded files.
Maybe you could please upload your working Bootimage from S8500?
So we had something to start with...
3.
You have working fallback/recovery plan? To get back to working bada S8500.
Or only JTAG...
4.
Anyway. Thanx for uploading files for study.
Best Regards
To adfree,
1)now the steps bada->android or android->bada is only via JTAG.
i'm don't know any other way.
2)i posted full working bootloader files in first message of my thread.
3)i will post full jtag image with semi-working android in 2 hours.
Regards
my friend
Thank you oleg_k
Last Question for today.
So I should use simple Flashtool from I9000 to flash these Boot Files into S8500 ?
Sorry for stupid Question. But I'm totally Android Noob.
Thank you for uploading files.
Best Regards
oleg_k said:
To adfree,
1)now the steps bada->android or android->bada is only via JTAG.
i'm don't know any other way.
2)i posted full working bootloader files in first message of my thread.
3)i will post full jtag image with semi-working android in 2 hours.
Regards
my friend
Click to expand...
Click to collapse
We can think about running SBL or any other bootloader (anybody with sources for that?) through the FOTA hole as I described in the thread:
http://forum.xda-developers.com/showthread.php?t=1020444
This way we don't need JTAG for initial flashing. It'd be also good to perform testing without touching BADA in the NAND, but we either need to reorganize partitions or boot from SD card
Best Regards,
mijoma
I think an combination will lead to success... so work together.
At this status it is maybe tooo risky to play without JTAG.
As we not know, how Android will handle Memory...
Okay, correction. I don't know.
In worst case scenario you need JTAG to reanimate Wave...
We have 2 steps/parts.
Android part.
Display, Kernel, Memory, etc...
This part is mandatory in my opinion.
Then second part, how to start Android. Then there are several theories...
BootLoader, No BootLoader, FOTA... inject via JTAG into RAM...
internal Memory or Dual Boot from SD Card...
Anyway, without proper modified Android part we can't use all our Security Holes.
As more infos we have, better, as more working solution we have.
So more chance to improve something.
At the moment we can only improve Video Quality.
Best Regards
Mijoma,
I totally agree with you,maybe this is the way to deploying android on S8500.
But now,i think about build working kernel for our s8500.
Maybe you helping with analize memory init on original bootloader?
like this - http://code.google.com/p/jetdroid/wiki/OriginalDramInit
Regards
Seems like using mijoma's discovery you should be able to replace booting and maybe make it to boot from SD card using a open source booter a compatible android kernel with selfmade drivers.
Maybe that could be the way, sadly we'd lose internal storage since we wouldn't be touching bada partition, anyway Android should be working fine from a SD card, It does properly on other handsets which internal storage is nothing more than a microSD card instead of flash memory.
I think losing 2GB on internal and XMB on microSD is a good deal for having android on our handsets. Happily I got 16GB SD on my wave xP. Anyway once you achieved that we could gather to use the internal flash memory partition
Jioma I suggest you to work with adfree (along your knowledge) and oleg_k they're our wave masters, baybe you together could gather to achieve this great project. I require you to work on this oh please jioma=(
Ok thats great news! Finally we have a method of booting other platforms on the Wave. What we need is as much information on the s5800 chipset as we can get so we know exactly what to compile and what drivers are needed in the linux kernel for android. Someone get in touch with Cyanogen mod and ask him for help and offer him a wave or something ha.
Gentlemen,
Lately I have found myself experimenting with Debian on my beloved Leo. It's very much WIP, but even right now it may be fun to play around for some. And most of the stuff that *doesn't* work, well, solutions are in the line of sight.
I won't have time to finish it anytime soon. So, partly in hope someone will join the effort, and partly to simply make sure I won't lose effects of my work in the darkest corners of my hard drive, I upload it as it is.
It's very much bare-bones Debian Unstable system. To install it, copy all three unpacked files (rootfs.ext4, zImage, initrd.gz) to "debian" directory on your SD card. Then, choose this directory in MAGLDR settings. Then boot from SD.
It boots directly into the desktop and allows you to connect to wifi and launch terminal (and install any software you want using apt-get/aptitude).
DOWNLOAD:
http://www.multiupload.nl/8D7ZS99UTX
http://d-h.st/Tx9 (thanks to Robbie P)
MD5: 9f5a9961d8ace10d38f7ea493a12ab4a
(mirrors appreciated)
Features:
*Touchscreen, UI works perfectly fine
*Wifi works perfectly fine too
*Sound kinda works (playback is too fast for me, please test)
*It's full Debian GNU/Linux - 15901141666 packages to apt-get!
Various technical info:
*Kernel based on linux_on_wince_htc from gitorious with some modifications:
-applied USB host patch by liiochen
-applied patch from tytung kernel that enables ALSA driver to be compiled as module (without that it wouldn't work at all)
-custom defconfig
*Rootfs size is 1GB. Filesystem is ext4 (to avoid data corruption).
*Window manager is E17, it's optimized for phones, very beautiful, and very impressive overall. Network manager is Wicd.
*Also installed: Xterm, SSH server.
*Default username is "htcleo". Default password for this account is "htcleo". Default root password is..."htcleo".
*As it is Debian Unstable, anything can break at any time and not much can be done about it. I also recommend using aptitude over apt-get (it is better at solving dependency problems).
Important To-Do:
*Phone functionality & suspend/resume (all of this should be supported! sadly, fso-deviced in Debian repositories is currently broken)
*Landscape mode (easy)
*Hardware buttons (easy)
*Bluetooth (at least partial support should be easy)
*??? to be continued
Wish-list (the less important stuff):
*Switch to armhf for performance gains (should be easy)
*At least partial hardware acceleration (should be possible thanks to xf86-video-msm driver)
*Bully someone into cooking newer kernel (2.6.32 is old)
*If the above doesn't work, backport brcmfmac wifi driver to current kernel
*Compass, GPS, camera, multitouch (aka the stuff not many really care about)
*??? to be continued
If you want to help me in the effort to make this port work perfectly, take a look at this:
http://www.multiupload.nl/BXNBMMECH0
It's a package with everything you need to reconstruct my rootfs on your own. There are some files and there is a dirty bash script ("createrootfs") that does everything that has to be done. Instructions are inside of it.
There is a lot of valuable information on htc-linux wiki (http://htc-linux.org). I'm available in this topic, on pm, and on #htc-linux freenode channel.
Big thanks to #htc-linux, Cotulla, liiochen, tytung, dcordes, many others I forgot about and will add later.
[EDIT 16.09.12]
Some people requested kernel sources, here they are:
http://www.multiupload.nl/IWL07GL78D
MD5: c698454af38ad7ed3dbec120eae84daa
Clever ones will notice ".git" subdirectory. There's full history and anyone's more than welcome to upload it onto github/gitorious/similar.
Please refer to this htc-linux wiki page for compiling: http://htc-linux.org/wiki/index.php?title=QuickDeveloperStartGuide#Kernel . Use htcleo-gnu_defconfig (it's in arch/arm/configs/ directory).
I would appreciate someone testing USB host functionality. It should work (proper patches were applied), but I don't have cables to check it out myself.
Won't load from magldr-stop on " 123fatal hit 3 "
Sent from my HTC HD2
USB host works, keyboard and mouse. Connected to wifi ok. But when I tried to take a screenshot, it just hung and had to press soft reset button. Will test more.
Excellent work bardzusny, BTW there are Ladies on this forum too
@ivicabrus, be sure to unzip the .tar.gz, the .tar and also the rootfs.zip
Edit; mirror- http://d-h.st/Tx9
In my debian folder...is it correct?
Sent from my HTC HD2
ivicabrus said:
In my debian folder...is it correct?
Sent from my HTC HD2
Click to expand...
Click to collapse
Looks good m8
Robbie P said:
Looks good m8
Click to expand...
Click to collapse
But won't load..
Sent from my HTC HD2 using xda premium
ivicabrus said:
But won't load..
Sent from my HTC HD2 using xda premium
Click to expand...
Click to collapse
magldr>10.services>1.bootsettings>1.bootsource>3.AD SD Dir>DEBIAN
maldr>2.boot ad sd
Did you do the above?
Edit; magldr 1.13?
Robbie P said:
magldr>10.services>1.bootsettings>1.bootsource>3.AD SD Dir>DEBIAN
maldr>2.boot ad sd
Did you do the above?
Edit; magldr 1.13?
Click to expand...
Click to collapse
Yes,do everything and mgldr 1.13 i have android 4 on nand , ext 512 on sd card 8gb class 6, android load but this stop on 123 in magldr when load zlmage and initrd.gz
Sent from my HTC HD2 using xda premium
ivicabrus said:
Yes,do everything and mgldr 1.13 i have android 4 on nand , ext 512 on sd card 8gb class 6, android load but this stop on 123 in magldr when load zlmage and initrd.gz
Sent from my HTC HD2 using xda premium
Click to expand...
Click to collapse
Try 10.services>1.bootsettings>1.boot source>1.android from sd
Then the above
@Robbie maybe is problem my nand partition 220mb for android?
But debian load from sd...no understand
Sent from my HTC HD2
Will test it
Sent from my HTC HD2
ivicabrus said:
@Robbie maybe is problem my nand partition 220mb for android?
But debian load from sd...no understand
Sent from my HTC HD2
Click to expand...
Click to collapse
did you check md5 sum of download, else can't think why it isn't booting for you.
searching fatal hit 3 only brings up someone who dropped their phone
I cant boot too. But i use a2sd script in nand droid. Its that?
Sent from my HTC HD2 using XDA
[zozi] said:
I cant boot too. But i use a2sd script in nand droid. Its that?
Sent from my HTC HD2 using XDA
Click to expand...
Click to collapse
Can you boot sd android builds?
It could be that any ext partition confuses matters IDK.
humm i dont test if i can boot sd android builds... but now i can boot but, after a few code lines the hd2 reboots automaticly...
[zozi] said:
humm i dont test if i can boot sd android builds... but now i can boot but, after a few code lines the hd2 reboots automaticly...
Click to expand...
Click to collapse
Check my post earlier you have to unzip the rootfs.zip too
There is no link on the download page.
Must register on this site to be able to see the download link?
Sorry, is the first time I come across this download site.
Thanks.
Your rootfs.ext4 seems destoryed.
Sent from my HTC HD2
I did some test on this build and performance is much better than ubu. Ui is very smooth and keybord is good as for smartphone. Tried to test sound but clicking mplayer does not give result. Wifi works but sometimes needs system restart to connect. Dont try screenshot option (just like above). Good work!
Sent from my HTC Sensation (HD2) using XDA
First -
I'm new to Nook ROM development. I have an Android mobile phone onto which I've loaded several ROMs over the past couple of years...bricked on trying to flash a stock upgrade.
I acquired this Nook Tablet (8gb version) and found this XDA forum for the device. Maybe it's because the Nook is one of just a few tablet versions, but this development thread - to me - is all over the place. I can't seem to find a unifying thread that explains all the ROMs available, along with the pros/cons, etc. of each.
What would be a good stable ROM (no stock) for the Nook Tablet 8GB?
I see that we have CM7, 9, and 10. And there seem to be several varieties of each - with various tweaks, nips, and tucks.
Any insights?
Thank you,
Dan
DanGeorges said:
What would be a good stable ROM (no stock) for the Nook Tablet 8GB?
I see that we have CM7, 9, and 10. And there seem to be several varieties of each - with various tweaks, nips, and tucks.
Any insights?
Click to expand...
Click to collapse
And as with every other one of these threads, it will be locked and edited. This question is not allowed due to 10 different people giving 10 different answers.
My personal experience is that CM7 currently has the least number of glitches. CM 7 and CM 9 are no longer in development so what you see is what you get. CM10 has come a long way and some people can daily drive it and others(myself 1 of those people) can't due to its quirks. Read, read and read some more and make your own informed decision.
SlowCobra96 said:
And as with every other one of these threads, it will be locked and edited. This question is not allowed due to 10 different people giving 10 different answers.
My personal experience is that CM7 currently has the least number of glitches. CM 7 and CM 9 are no longer in development so what you see is what you get. CM10 has come a long way and some people can daily drive it and others(myself 1 of those people) can't due to its quirks. Read, read and read some more and make your own informed decision.
Click to expand...
Click to collapse
So you're saying there are that many ROMs?
The only reason I posted this question was because I've read, re-read, and read some more. And I still can't make heads or tails of which ROMs are in development, which CM10 is the most current, which is the most stable, etc.
And as for this thread being locked and edited - What is the "Questions" section for if not to ask questions?
DanGeorges said:
So you're saying there are that many ROMs?
The only reason I posted this question was because I've read, re-read, and read some more. And I still can't make heads or tails of which ROMs are in development, which CM10 is the most current, which is the most stable, etc.
And as for this thread being locked and edited - What is the "Questions" section for if not to ask questions?
Click to expand...
Click to collapse
It's too much of an open ended opinion based question and the moderators just don't like it being asked. I however do understand the validity of it.
CM 10 there are only 2 main ones right now the SGT7 and Chrmhoffmann CM 10 currently 0.6 SGT7 is based off of chrmhoffmanns work with some add-ons.
SlowCobra96 said:
It's too much of an open ended opinion based question and the moderators just don't like it being asked. I however do understand the validity of it.
CM 10 there are only 2 main ones right now the SGT7 and Chrmhoffmann CM 10 currently 0.6 SGT7 is based off of chrmhoffmanns work with some add-ons.
Click to expand...
Click to collapse
That helps a lot - thanks for the info.
I can do more research on these. I don't think I want to load CM7. Old and no more development as you say...
Thank you again!
Dan
DanGeorges said:
That helps a lot - thanks for the info.
I can do more research on these. I don't think I want to load CM7. Old and no more development as you say...
Thank you again!
Dan
Click to expand...
Click to collapse
Honestly don't rule out CM7. I love its stability and after modifying build.prop the fact it runs pretty much everything. Make it easy on yourself and load all of them on SD cards and compare them to find the best for you.
DanGeorges said:
...
The only reason I posted this question was because I've read, re-read, and read some more. And I still can't make heads or tails of which ROMs are in development, which CM10 is the most current, which is the most stable, etc.
...
Click to expand...
Click to collapse
You can use the info and tools posted here to build a SD card version of Chrmhoffmann's CM10 (and/or CM9) and try them out to see if their performance fit your need.
I've been using Chrmhoffmann's CM10 v0.06 off a SDcard and am quite happy with it (although some games like Temple Run currently don't work with it). Chrmhoffmann's CM9 v0.05.3 is also very good.
digixmax said:
You can use the info and tools posted here to build a SD card version of Chrmhoffmann's CM10 (and/or CM9) and try them out to see if their performance fit your need.
I've been using Chrmhoffmann's CM10 v0.06 off a SDcard and am quite happy with it (although some games like Temple Run currently don't work with it). Chrmhoffmann's CM9 v0.05.3 is also very good.
Click to expand...
Click to collapse
What file(s) did you image to the SD card? The zip file he has on his site has the following:
flashing_boot.img
MLO
note.txt
recovery.img
u-boot.bin
Thanks,
Dan
DanGeorges said:
What file(s) did you image to the SD card?
...
Click to expand...
Click to collapse
Here the process I follow to build a CM10 SD card for my 16GB Nook Tablet:
Create 3 partitions using MiniTool Partition Wizard Home Edition per the instructions in step #1 here: sdcard, system, and data. Make sure that you set the partition ID type for the sdcard partition to 0x0C FAT32 LBA and set its Active flag, otherwise the SDcard will not be bootable. Once this is done, the sdcard partition should appear as a (read/write accessible) drive under Windows. (Note that you can adjust the suggested sizes of the partitions upward to fill up the entire SDcard).
Copy the following files from cm10-acclaim-0.06_sd_hd_10_11.zip (obtained here) to the sdcard partition: boot.img (in folder p2), flashing_boot.img, MLO, recovery.img, u-boot.bin.
Replace updater-script in cm10-acclaim-0.06-full-of-bugs (in folder META-INF\com\google\android) with the updater-script from cm10-acclaim-0.06_sd_hd_10_11.zip (in folder p2).
Replace updater-script in gapps-jb-20120726-signed.zip (in folder META-INF\com\google\android) with the updater-script from gapps-jb-20120726_sd_hd.zip (obtained here) (in folder p2).
Copy to the sdcard partition cm10-acclaim-0.06-full-of-bugs and gapps-jb-20120726-signed.zip with the replacement updater-scripts files (which cause the CM10 ROM and JellyBean Google apps to be installed on the SDcard rather than on your NT itself).
You should now have a bootable SD card with 7 files on it, ready for the 2nd phase of the SDcard build described in step #4 here.
A few additional points worth noting in building CMx on SD card:
The NT OMAP3 SD boot process is very finicky about the SDcard boot-partition's setup. Fortunately MiniTool Partition Wizard generally does very good job in creating a FAT32 boot-partition with the expected cylinder/sector geometry and alignment, especially from scratch (i.e., on a SD card with no existing partition on it). So if an SD card repeatedly fails to boot it's best to delete all the partitions and start over fresh.
I have found it helps to first copy the MLO and u-boot files then the rest of the files, since MLO and u-boot are to be loaded first, and it appears that OMAP only scans the first few entries of the partition-table to look for these two files.
If your NT is like mine, you will have to plug in the powered USB cable to the NT in its power-off state -- in order for the NT to boot from the SDcard.
Generally the lower rating (and also cheaper) class 4 SD cards are more suitable for running a ROM than the higher classes 6 and 10 cards (since the latter are optimized for large & sequential block read/write at the expense of random read/write). So if you happen to use a class 10 or 6 card and your apps frequently crash or freeze, consider switching to a lower class SD card.
most stable?
the CM7 versions ARE the most stable versions- currently
all the cm10/cm9's they all have the same "bugs" - mostly random reboot/lockup problems- we fix this one problem and cm10 would be golden on our NT's
that said, it's weird, sometimes i can go Days without having to reboot the system using CM10, other times, the same rom, just a fresh boot, with lockup with the black screen forcing a reboot, in minutes-hell i've had it lockup to black screen/forcing a reboot less than a minute after bootup.
lenardo said:
most stable?
the CM7 versions ARE the most stable versions- currently
all the cm10/cm9's they all have the same "bugs" - mostly random reboot/lockup problems- we fix this one problem and cm10 would be golden on our NT's
that said, it's weird, sometimes i can go Days without having to reboot the system using CM10, other times, the same rom, just a fresh boot, with lockup with the black screen forcing a reboot, in minutes-hell i've had it lockup to black screen/forcing a reboot less than a minute after bootup.
Click to expand...
Click to collapse
Thank you for this information.
I am going to try CM7 via SD card to see how it performs.
Right now, I have the Stock 1.4.2 ROM, rooted, with CWM 5.0.2.8 installed (via ADB push) - no Cyanoboot loaded at all. I just boot into recovery via the normal method.
I'm wondering if I can just install a CM7 zip via CWM without Cyanoboot...
Any thoughts?
On all cm10 roms i have experienced download problems where after i few minutes i download something and it finishes but still says in progress and then everyhting freezes
...
Sent from my Nook Tablet using xda app-developers app
lenardo said:
most stable?
the CM7 versions ARE the most stable versions- currently
all the cm10/cm9's they all have the same "bugs" - mostly random reboot/lockup problems- we fix this one problem and cm10 would be golden on our NT's
that said, it's weird, sometimes i can go Days without having to reboot the system using CM10, other times, the same rom, just a fresh boot, with lockup with the black screen forcing a reboot, in minutes-hell i've had it lockup to black screen/forcing a reboot less than a minute after bootup.
Click to expand...
Click to collapse
My experience has been the opposite: my CM7 would get into a boot-loop state every couple of months, whereas CM9 (v0.05.3) and CM10 (v0.06) have been pretty solid.
digixmax said:
Here the process I follow to build a CM10 SD card for my 16GB Nook Tablet:
Create 3 partitions using MiniTool Partition Wizard Home Edition per the instructions in step #1 here: sdcard, system, and data. Make sure that you set the partition ID type for the sdcard partition to 0x0C FAT32 LBA and set its Active flag, otherwise the SDcard will not be bootable. Once this is done, the sdcard partition should appear as a (read/write accessible) drive under Windows. (Note that you can adjust the suggested sizes of the partitions upward to fill up the entire SDcard).
Copy the following files from cm10-acclaim-0.06_sd_hd_10_11.zip (obtained here) to the sdcard partition: boot.img (in folder p2), flashing_boot.img, MLO, recovery.img, u-boot.bin.
Replace updater-script in cm10-acclaim-0.06-full-of-bugs (in folder META-INF\com\google\android) with the updater-script from cm10-acclaim-0.06_sd_hd_10_11.zip (in folder p2).
Replace updater-script in gapps-jb-20120726-signed.zip (in folder META-INF\com\google\android) with the updater-script from gapps-jb-20120726_sd_hd.zip (obtained here) (in folder p2).
Copy to the sdcard partition cm10-acclaim-0.06-full-of-bugs and gapps-jb-20120726-signed.zip with the replacement updater-scripts files (which cause the CM10 ROM and JellyBean Google apps to be installed on the SDcard rather than on your NT itself).
You should now have a bootable SD card with 7 files on it, ready for the 2nd phase of the SDcard build described in step #4 here.
A few additional points worth noting in building CMx on SD card:
The NT OMAP3 SD boot process is very finicky about the SDcard boot-partition's setup. Fortunately MiniTool Partition Wizard generally does very good job in creating a FAT32 boot-partition with the expected cylinder/sector geometry and alignment, especially from scratch (i.e., on a SD card with no existing partition on it). So if an SD card repeatedly fails to boot it's best to delete all the partitions and start over fresh.
I have found it helps to first copy the MLO and u-boot files then the rest of the files, since MLO and u-boot are to be loaded first, and it appears that OMAP only scans the first few entries of the partition-table to look for these two files.
If your NT is like mine, you will have to plug in the powered USB cable to the NT in its power-off state -- in order for the NT to boot from the SDcard.
Generally the lower rating (and also cheaper) class 4 SD cards are more suitable for running a ROM than the higher classes 6 and 10 cards (since the latter are optimized for large & sequential block read/write at the expense of random read/write). So if you happen to use a class 10 or 6 card and your apps frequently crash or freeze, consider switching to a lower class SD card.
Click to expand...
Click to collapse
These are great instructions. Thank you!
I created the card, popped it into the Nook, plugged it into the USB port, and Cyanoboot came up. I didn't stop it, and the Nook booted to a blank screen.
Is there something I need to do in Cyanoboot? Do I just let it run and wait?
I selected "SDC Boot" and it still went to a blank screen.
Thanks,
Dan
Thread closed. Normally it doesn't take this long but missed this thread in skimming through.
As has already been said at the start of this thread "best" or "most stable" ROM question threads are not allowed due to the fact everyone has their own opinion and it's probably a good thing this has had a number of replies already as it's shown how subjective it can be with one person saying CM7 is the most stable then someone finding the opposite. Believe it or not devices are unique and react differently to ROM's and kernels so the only way to know the answer to your question is to try them all or the one's that have the features you like. We're all here to learn about our devices and trial and error is the best way to learn
Dirty Unicorns Android 9, PIE by Flintman for HP TouchpadClick HERE for How to Flash the ROM
________________________________________________________________
Work in progress, not workingBluethooth
Camera
Home button________________________________________________________________
Disclaimer: I am not a developer, just a regular user like YOU.
That have found a way to improve the Tablet and would like others to benefit by sharing the information.
I am not the creator of the ROM or Recovery mentioned.
All credits goes to the developer@flintman and the Dirty Unicorns Team.
________________________________________________________________
Nice Find Thanks!
Touchie Pad said:
Nice Find Thanks!
Click to expand...
Click to collapse
You are welcome!
The following does not work, installing only the ROM.
Camera
Bluetooth
Youtube plays very well
Very smooth
Microphone works.
Wifi works perfectly.
The only problem is that the internal storage is not accessible.
It can not even save screenshots, no access. ( it is fix on the 3-28-2019 version )
I dirty flashed the 13.x over 12.5x and did not do the open gapps, so I will have to sideload them I guess at some point since I cannot get to internal storage like you said.
It boots up, but lots of stuff does not work (like bluetooth). At least the March 2019 security updates are in place!
Thanks
I can't believe we now have Pie on the old work horse. Thank you so much. I wiped everything but internal storage and did a clean install with open pico gapps. I had previously installed the DU swap in the boot directory and booting with it goes to a boot loop. I went back to 8.1 and deleted the DU swap in the boot directory and did another clean install of 9. It came right up and the few apps I have installed work. I tried installing YouTube but the play store says this version is not compatible. It won't even show it as an option. There is no access to storage from either the files app or ES File Explorer. I even tried USB with Windows and android shades out the file transfer option. All my other Pie devices give you an option in setting to set up the SD as either removeable or internal memory. I am wondering if we need to reformat internal memory to get access. I hate to kill it since I have all my install files there as well as TP Toolbox. Any suggestions welcome.
This is the first version of Pie and it boots and works, but the permissions are set for root as the user and it does not allow access to the internal storage. ( is all fixed on version 3-28-2019 )
Flintman is working on it and fixing that issue. Keep in mind it takes time and dedication to do this.
I installed the full version of Google Open gapps that comes with youtube and it works perfectly fine. Pie will be optimize as soon as the access permission is fix.
The Tablet soon will be working better than ever and all updated to the latest software available!
HP_TOUCHPAD said:
This is the first version of Pie and it boots and works, but the permissions are set for root as the user and it does not allow access to the internal storage.
Flintman is working on it and fixing that issue. Keep in mind it takes time and dedication to do this.
I installed the full version of Google Open gapps that comes with youtube and it works perfectly fine. Pie will be optimize as soon as the access permission is fix.
The Tablet soon will be working better than ever and all updated to the latest software available!
Click to expand...
Click to collapse
First
First, A big thank you to Flintman! I went ahead and flashed with mini gapps as the smallest package containing YouTube and it works fine. I will wait for the storage until it is fixed. The only other question I have is on partition sizes. I left them at the recommended sizes for the DU swap. I may be wasting memory but all appears to be working. I have TP Toolbox resident just in case. Thanks again. Also I assume we should not use the SKZ kernel since this looks later.
johnbelloh said:
First
First, A big thank you to Flintman! I went ahead and flashed with mini gapps as the smallest package containing YouTube and it works fine. I will wait for the storage until it is fixed. The only other question I have is on partition sizes.
The partition sizes applied using the following:
HP TOUCHPAD Optimize for Android with Swap Partition and SKZ Kernel_ Flash Files_
Will work with Pie, Q and any future release of Android.
The /system partition is set to 1.8G, which can accommodate a Super variant of the google open gapps.
I left them at the recommended sizes for the DU swap. I may be wasting memory but all appears to be working.
Is storage space not Memory or RAM. It will be about 500MB to 600MB extra of storage space not Memory, it does not affect performance.
I have TP Toolbox resident just in case. Thanks again. Also I assume we should not use the SKZ kernel since this looks later.
Click to expand...
Click to collapse
There is no SKZ kernel for Pie at the moment and it will not work with Pie 9 as it only works with 8.1.
The stock Kernel of Pie 9 is not optimize yet to use the swap partition, as soon as Pie is fix it will be available and the system will improve performance and stability as more RAM (Memory) will be available in Android. (Update Pie is completely optimize more than any other ROM
https://download.dirtyunicorns.com/?device=tenderloin du_tenderloin-v13.0-20190328-1316-RC.zip
28 de marzo de 2019
293.42M
---------- Post added at 05:22 PM ---------- Previous post was at 05:21 PM ----------
du_tenderloin-v13.0-20190328-1316-RC.zip
28 de marzo de 2019 excelent room for TouchPad
larrywilson said:
https://download.dirtyunicorns.com/?device=tenderloin du_tenderloin-v13.0-20190328-1316-RC.zip
28 de marzo de 2019
293.42M
---------- Post added at 05:22 PM ---------- Previous post was at 05:21 PM ----------
du_tenderloin-v13.0-20190328-1316-RC.zip
28 de marzo de 2019 excelent room for TouchPad
Click to expand...
Click to collapse
Thanks for the update ! The direct link now is updated to 03-28-2019 built.
Very impressive. Every app I have installed works including storage. I have 6 touchpads including a brand new 4G model. Is the plan to add swap to the ROM or will it be a separate install? If I can be of any assistance testing just ask. Thank you to all involved.
johnbelloh said:
Very impressive. Every app I have installed works including storage. I have 6 touchpads including a brand new 4G model. Is the plan to add swap to the ROM or will it be a separate install? If I can be of any assistance testing just ask. Thank you to all involved.
Click to expand...
Click to collapse
Android Pie is optimize and is swap enable from the core, all settings are set to be use with the swap partition.
Flintman did a marvelous job incorporating all the changes and making Pie available for the HP Touchpad with more improvement on its way that it could be the best ROM ever. I will update this guide soon.
It is worth it if i'm on 8.1 with swap ? I saw that yesterday we have got a update..
Steelskinz said:
It is worth it if i'm on 8.1 with swap ? I saw that yesterday we have got a update..
Click to expand...
Click to collapse
If you are using 8.1 now and enjoying your setup, then my recommendation is to keep using it that way until Pie which is 100% stable now with more features than 8.1, gets Bluetooth working and any other minor issues resolved. As of now Pie is working as Oreo. Pie is using the swap partition and fully optimized as 8.1 and 7.1.2. The only thing to do is to flash it just like any other ROM.
Hi all,
I keep popping back from time to time, and each time just keeps getting better and better... We're now up to Android 9 Pie ?? WOW !!! Fantastic work guys to all involved...
Couple of questions if you don't mind...
1) I'm currently on Android 8.1 Oreo, not sure which build or when.. without picking it up yet. Is it likely this will already be using SWAP partition, or do I still have to go ahead with it?
2) If I don't have a SWAP partition, and go ahead and create one... If I want to use an older DM rom at a later date. Do I have to remove SWAP, or will it just ignore the partition on older builds?
3) So we can use WebOS and Android 9 side by side, sharing the SWAP ??
4) Is there anyway to make the Boot partition larger than 32mb, or is that set in stone?? - and where can I find the uImage file for ToolBox, so I can have that as one of my selectable boot options.
Thanks, Lister
Lister Of Smeg said:
Hi all,
I keep popping back from time to time, and each time just keeps getting better and better... We're now up to Android 9 Pie ?? WOW !!! Fantastic work guys to all involved...
Yes Flintman still providing support and now has created the best ROM.
Couple of questions if you don't mind...
1) I'm currently on Android 8.1 Oreo, not sure which build or when.. without picking it up yet. Is it likely this will already be using SWAP partition, or do I still have to go ahead with it?
The swap partition must be created as in this guide:
HP TOUCHPAD Optimize for Android with Swap Partition and SKZ Kernel_ Flash Files_
2) If I don't have a SWAP partition, and go ahead and create one... If I want to use an older DM rom at a later date. Do I have to remove SWAP, or will it just ignore the partition on older builds?
WebOS came with a swap partition and all the ROMS were install side by side with WebOS but never implemented the use of SWAP, Android 9 is the first ROM to completely take advantage of swap thanks to Flintman for applying all the changes. And all future version of Android for the HP Touchpad will have support for the swap partition.
3) So we can use WebOS and Android 9 side by side, sharing the SWAP ??
Yes the partition that is created is the original from WebOS dev/store/swap.
In WebOS is a 400 MB
The new partition is 500 MB, it can be change to any size if the user wants to.
If you want to use any new ROM, 7.1.2 ,8.1 and 9 the /system partition must be 1400 MB, it can be resize using the ToolBox.
4) Is there anyway to make the Boot partition larger than 32mb, or is that set in stone?? - and where can I find the uImage file for ToolBox, so I can have that as one of my selectable boot options.
The /boot partition is a fix 32MB can not be change and there is no need for it to be larger.
Download the ToolBox from Here
Unzip the file rename TPToolbox-2015-01-08-v42.bin to uImage.ToolBox
Using TWRP Recovery mount /boot and using the TWRP File Manager copy uImage.ToolBox to /boot.
Using TWRP any boot uImage can be move from /boot to the SDCARD and then can be copy back.
There is no need for /boot to be larger as the boot files can easily be copy to it when need it to be use.
Think of it as a CD or USB disk that you insert into the PC to boot from, is the same concept. If you need to use the ToolBox make some space by removing a boot uImage and then copy the ToolBox in /boot.
Thanks, Lister
Click to expand...
Click to collapse
You are welcome!
Hi @HP_TOUCHPAD,
First of all, thank you for the very prompt and DETAILED reply, this is perfect and contains EXACTLY what I need to know. And apologies for the delay getting back to you, my brothers son has been in hospital last couple of days... So been a bit back and forth.
Thank you for your post, very clearly laid out and full of useful information. I shall follow that guide and re-create a swap partition. Had a quick look last night, and looks like Flintman has re-compiled all his old roms to support SWAP partition too. So should make them smoother still..
Thanks once again...
Lister
HP_TOUCHPAD said:
You are welcome!
Click to expand...
Click to collapse
Hi @HP_TOUCHPAD,
I've just picked up my Touchpad, and I appear to be running a build of Oreo 8.1.0, the Dirty Unicorns 12.5.xx.
However, in TWRP.... I only appear to have around 296k free, and not enough to store the Toolbox uImage (around 10mb) in there?? Any idea's what I can free up??
The largest files I can see are:
uImage.Android 5.4mb (boots my Android install)
uImage.moboot 63.KiB (boot manager)
uImage.TWRP 8.7mb (boots TWRP)
uImage.webOS 3.2mb (boots WebOS)
uImage-2.6.35-palm-tenderlion 3.2mb (no idea??)
System.map-2.6.35-palm-tenderlion 1.4mb (no idea??)
There are many other files and folders in the \boot partition. But not sure what, or if... I can free up any of those files/folders??
Thanks, Lister
Lister Of Smeg said:
Hi @HP_TOUCHPAD,
Thank you for your post, very clearly laid out and full of useful information. I shall follow that guide and re-create a swap partition.
Had a quick look last night, and looks like Flintman has re-compiled all his old roms to support SWAP partition too. So should make them smoother still..
The ROMS Kernels available from my guide for Evervolv 7.1.2 and DU 8.1 are my changes to make use of swap with optimization.
Flintman integrated all the changes posted on my guide to the Kernel, Ramdisk and also to the ROM of Pie (9).
Android Pie (9) is the first ROM to completely take advantage of the swap partition thanks to Flintman for improving and making the extra changes.
Thanks once again...
Lister
Click to expand...
Click to collapse
You are welcome.
Lister Of Smeg said:
Hi @HP_TOUCHPAD,
I've just picked up my Touchpad, and I appear to be running a build of Oreo 8.1.0, the Dirty Unicorns 12.5.xx.
However, in TWRP.... I only appear to have around 296k free, and not enough to store the Toolbox uImage (around 10mb) in there?? Any idea's what I can free up??
The largest files I can see are:
uImage.Android 5.4mb (boots my Android install)
uImage.moboot 63.KiB (boot manager)
uImage.TWRP 8.7mb (boots TWRP)
uImage.webOS 3.2mb (boots WebOS)
uImage-2.6.35-palm-tenderlion 3.2mb (no idea??)
System.map-2.6.35-palm-tenderlion 1.4mb (no idea??)
There are many other files and folders in the \boot partition. But not sure what, or if... I can free up any of those files/folders??
Thanks, Lister
Click to expand...
Click to collapse
The /boot partition is 32MB, It shows that WebOS is also installed. Before moving any files from /boot make sure to do a backup just in case if the wrong file gets removed. The ToolBox does not need to be in the /boot directory to be use . It can be loaded into the memory by placing the Tablet into Recovery Mode and from the PC with the novacom drivers install load it.
novacom boot mem:// <uImage.ToolBox
The ToolBox will be loaded into memory and use for anything need it, there is no need to keep it in the /boot.
The most important file to be in /boot uImage.moboot 63.KiB (boot manager)