Related
Android 2.0.1-r5v0.6
Dead:
==============
After spending some time and looking over this rom and ways to make it work with out any legal issues. The most viable option was to build something like what cynanogen has built. His process takes the proprietary bits (all google apps including sync) and copies them off onto the SD card before doing a update. After the update it copies them back to the newly installed rom. This method basically does a automated backup/restore of your licensed applications. I can't do this for several reasons including that we are supposed to be coming from a 1.5 OS to a 2.0.1, which isn't compatible with the older application set.
Temporarily Offline:
==============
I am sorry to have to do this but we are now having more then just a small handful goofing with this ROM and I need to take this offline while I inspect each of the parts and make sure all licensing is in order since its a bit more then the google Opensource framework. I know that several other ROM creators have not paid much attention to it as I am going to now but I really don't want to upset any IP holders like what happened to Cynanogen a couple months back.
I will put it back up but I want to make sure that I am totally covered and don't have any issues.
version 0.6: download (offline)
==============
-fixed wifi thanks to http://forum.xda-developers.com/showthread.php?t=593620
-Now starts up with Android stock keyboard. (No longer needs HTC_IME.apk for second keyboard)
A few have asked for this ROM so I thought I would put it up here for anyone that wants to contribute to or take from it.
This ROM is only compatible with the Sprint CDMA HTC Hero. It is not finished and still requires some work but its good enough for my day to day use and I am sure others may find the same potential.
This ROM is vanilla android and what it takes to actually get it running on a CDMA phone. It is built off of this GSM variant. I am going to try and work to remove the google bits so that you can use Cynanogens method of extracting your own and then doing a follow up update to install them. My efforts for this is not to build a better rom but to build a cleaner base that has limited to no proprietary IP.
Credits to all on this forum how have helped or contributed in any way to building the roms that are here. I would point out names but there are to many to name. I am positive that anyone that pays attention to this forum will know who you are. I used many parts of these ROM's and many others on XDA to build this one.
This is my first ROM and was primarily made for myself to help me learn how to create a custom ROM.
Here is the link to my blog where I originally posted about this and a video of it booting.
Here is the Youtube video of it booting: http://www.youtube.com/watch?v=tRTh-rXKe-E
*Warning*: Don't attempt to flash this ROM onto anything else unless you know what you are doing! I am not responsible for any device malfunctions or "Bricks".
Notes on Installing:
- Run a Nandroid backup before you do anything.
- Make sure you do a full wipe first. (Sorry )
- Run the update zip found * Version 0.6 *(offline) from the recovery console.
To get the HTC keyboard installed: (Now Optional as of Version 0.6)
- Follow the instructions here.
Things that don't work:
- Gallery some times has issues.
- Camera
- Wired or Wireless Tethering (Now Testing)
- Orientation
- Trackball light
- Trackball click (Rolling and moving are fine)
- (Let me know if something else needs to go here.)
Possible issues that are not repeatable:
- speaker not working on out bound calls? I made 30 test calls to my home phone and was not able to replicate this issue. Needs to be verified (see here)
Awesome! Thanks! disregard my PM lol.. Great timing.
VoXHTC said:
Awesome! Thanks! disregard my PM lol.. Great timing.
Click to expand...
Click to collapse
LOL I was just getting to replying to you!
im trying it now nice work
Let me know if any of you have issues flashing. I still have it all right here in front of me if I need to make a change.
FYI: The first boot takes for ever as it registers all the APKS.
i just get the HTC_IME fource close i installed the one from the site like you said and installed it and i get this
thorracing1 said:
i just get the HTC_IME fource close i installed the one from the site like you said and installed it and i get this
Click to expand...
Click to collapse
So you installed both the HTC_IME.apk and the Clicker.apk? Did you do a adb push or a adb install?
Try and go into settings --> Language & Keyboard --> Touch Input --> Text Input?
I think its a force of habit with out really thinking to go there and calibrate but just going there may help.
Try that and let me know.
i just flashed it and pushed the keyboard and calibration app through adb and all is well. its working awesome. Thanks!!!
2.0t03speed said:
i just flashed it and pushed the keyboard and calibration app through adb and all is well. its working awesome. Thanks!!!
Click to expand...
Click to collapse
Awesome, keep the feed back coming as you have it!
please take note orientation doesnt work. please put in first post.
otherwise, great work!
should i do adb install or adb push?
blankd3ckskat3r said:
please take note orientation doesnt work. please put in first post.
otherwise, great work!
Click to expand...
Click to collapse
Got it listed now, that one bugs me... Must have been to worried about building this to remember it.
BTW thanks for the feed back!
thorracing1 said:
should i do adb install or adb push?
Click to expand...
Click to collapse
I would do an install or transfer them to your SD card and grab a app like Astro from the market to install them. Don't worry we will get you worked out.
dchadwick said:
Got it listed now, that one bugs me... Must have been to worried about building this to remember it.
Click to expand...
Click to collapse
lol well its a common problem, cant wait for a fix. really like what you did with this build
dchadwick said:
I would do an install or transfer them to your SD card and grab a app like Astro from the market to install them. Don't worry we will get you worked out.
Click to expand...
Click to collapse
Not able to get a working Keyboard Now I'm stuck in a boot loop. Tried installing through droid explorer.. no go.. tried installing from astro ..no go.. now it loads lockscreen.. dead... reboot..rinse and repeat
removed SDcard.. boots now trying to push.. but where do I push the apk files to?
blankd3ckskat3r said:
lol well its a common problem, cant wait for a fix. really like what you did with this build
Click to expand...
Click to collapse
Thanks, but I really can't take to much credit. Its a "Pick and Pull" from several ROMs. This one actually came from our GSM Brothers and then I used the CDMA tricks in this form to make it work.
I keep watching and playing with the Google Nexus Dumps. I would really like to get one of them up and running.
Based on your posting and replies I assume you are re-using the 2.6.27 kernel like the other roms?
VoXHTC said:
Not able to get a working Keyboard Now I'm stuck in a boot loop. Tried installing through droid explorer.. no go.. tried installing from astro ..no go.. now it loads lockscreen.. dead... reboot..rinse and repeat
Click to expand...
Click to collapse
Wow thats allot in a little space.
What I gather is that it originally booted, then after trying to install via droid explorer and then astro it now just dies after the lockscreen.
I am not sure where to start. I would just say to do a full wipe, then a clean install. Then if you have the sdk try the ADB install method as Cynanogen's post talks about.
I am working on trying to get the stock Android keyboard to work. If we can figure out that then we don't have to mess with the HTC one.
ok i got it i just adb pushed them to system/app works great
obelisk79 said:
Based on your posting and replies I assume you are re-using the 2.6.27 kernel like the other roms?
Click to expand...
Click to collapse
Yeah, actually some of your work if I remember correctly, thats why its got the same issues. My first goal when I built this for my self was to get past the blasted google bits sync loop. The more I worked into it the more I moved on to the 2.0.1 build with some of your stuff in it.
Your welcome to anything I have learned, its really not my work.
Have got the version of flash that's in the CWM sticky, but noticed my N1 today got an upgrade, and am wondering if there is a way to pull that over to my G-tab? Or do I just need to be a little patent and someone will post an update in a day or two?
EwanG said:
Have got the version of flash that's in the CWM sticky, but noticed my N1 today got an upgrade, and am wondering if there is a way to pull that over to my G-tab? Or do I just need to be a little patent and someone will post an update in a day or two?
Click to expand...
Click to collapse
You can try but the flash seems to be device specific in some cases so it may just bork your flash. Make a backup so you can restore it if you try
EwanG said:
Have got the version of flash that's in the CWM sticky, but noticed my N1 today got an upgrade, and am wondering if there is a way to pull that over to my G-tab? Or do I just need to be a little patent and someone will post an update in a day or two?
Click to expand...
Click to collapse
Since you mention CWM I will assume you have root.
Get a free Dropbox account and install on your N1 and gTab. Then it's as easy as copying the Flash apk into the Dropbox folder on your phone and then downloading it from your Dropbox folder on your gTab.
Doesn't get much easier.
I saw the flash update on my N1 this morning. I read the release notes for 10.1.106.16. It states:
Flash Player (10.1.106.16) impacts new users only and is not a mandatory update for existing users. It SHOULD NOT be installed on devices/tablets with the NVIDIA Terga 2 Super Chip including the LG Optimus 2X, Dell Streak 7, and Motorola ATRIX. The pre-installed version of Flash Player is optimized for Tegra 2 (this is my addition... if only there was a pre-installed version of the Flash Player installed on the gtab...) Future updates will include these optimizations. If you are unsure as to whether your device includes the NVIDIA Tegra 2, please consult your device owner's manual.
Maybe the versions prior have the same stipulation I don't know (this is the first time I saw this), but it's probably best to stick with what works for now. Probably won't be a lot of change until the release with the official Tegra 2 support is made available.
sjmoreno said:
Since you mention CWM I will assume you have root.
Get a free Dropbox account and install on your N1 and gTab. Then it's as easy as copying the Flash apk into the Dropbox folder on your phone and then downloading it from your Dropbox folder on your gTab.
Doesn't get much easier.
Click to expand...
Click to collapse
The update says in it's notes that it isn't for tegra devices... kinda useless to us.
Hello,
I have a HTC Touch Diamond 100 and I installed the "Froyo FRX06 XDandroid NEW system update" review in the post "[prj] [XDANDROID] [AOSP] [FroYo | GINGERBREAD] [31.03] System Update" and everything works fine except that it doesn't recognize SDcard applications.
There's no Error Message in the screen, is just that the system doesn't recognice anything in the SDcard. I put my apps in the folder: AndroidApps-> Other. I think it's not the common fault that I have read many people have "Waiting for SDCard error. For people who have problems with sdcard message, add this to your startupmsmsdcc_1bit msmsdcc_fmax=14000000 msmsdcc_nopwrsave" because for instance the phone let me save the pictures i've take with the camera phone or install and recognice any app from the market.
I 've Format the card with the HP tools after initial installation and then i had restore all the files in the internal storage.
P.S. Sorry for my possible spelling mistakes but English is not my native language
Keep in mind if you put the apk in anything other than the AndroidApps folder you will need to install them yourself. See THIS FAQ for further explanation. As far as the wating on sd card message you get when you are booting into Android, I get those all the time and have no problems with taking pictures. I would suggest that you use the full bundle from THIS post to ensure you have the latest. Unless you know what you are doing
R^7Z said:
Keep in mind if you put the apk in anything other than the AndroidApps folder you will need to install them yourself. See THIS FAQ for further explanation. As far as the wating on sd card message you get when you are booting into Android, I get those all the time and have no problems with taking pictures. I would suggest that you use the full bundle from THIS post to ensure you have the latest. Unless you know what you are doing
Click to expand...
Click to collapse
Oh what A noob mistake xD I didn't know that apps in the "Other" folder doesn't follow the "typical rules" for instaling apps (i've come from previous releases of Android, Eclair specifically, and in that version it was only place in this folder to install apps).
I'm using froyo instead of gingerbread builts because HTC touch Diamond it's quite old and i don't know if the performance would be better or slower than froyo performace but if you recomend me to use that gingerbread bundle i would use it.
Thanks R^7Z.
Honestly, Gingerbread is "better" but it is alpha release at the moment. Yes, this means that there are quite a few more "improvements" to under-go! I only recommend it if you like the idea of Android. The latest releases for FroYo aren't bad but it seems there are a few hard instability hits it has taken since FRX03 (last time I really enjoyed running a FroYo build from the XDAndroid project). Since then, I've been playing around with a few things and builds to include but not limited to this new idea of CWM (clockwork mod/Gingercherry tutorial) which is posted in the neopeek forums. So, unless you've got an idea as to how neopeek variants work, it's suggested to stick with the XDAndroid builds...
R^7Z said:
Honestly, Gingerbread is "better" but it is alpha release at the moment. Yes, this means that there are quite a few more "improvements" to under-go! I only recommend it if you like the idea of Android. The latest releases for FroYo aren't bad but it seems there are a few hard instability hits it has taken since FRX03 (last time I really enjoyed running a FroYo build from the XDAndroid project). Since then, I've been playing around with a few things and builds to include but not limited to this new idea of CWM (clockwork mod/Gingercherry tutorial) which is posted in the neopeek forums. So, unless you've got an idea as to how neopeek variants work, it's suggested to stick with the XDAndroid builds...
Click to expand...
Click to collapse
I see what you say but honestly, right now, I'm looking for stability and performace, if you know that gingerbread build GBX0A have better performance (i supose that it's less stable because it's an alpha) than FRX06 i'll choose Ginger
Thanks again R^7Z.
maxdamage2122 said:
Since "official" nightlys have not been compiling for the g-tablet, I have been compoiling them myself on my personal computer. I'll compile the source every so often and upload it here https://www.dropbox.com/s/w3vhon1u5a2orsk/smb_a1002/kang?v=l. The time stamp in the file name (MMDDYYYY-HHMM) is the time that the repo sync was done.
In the meantime I'm setting up an old computer that I have as a buildbot to automatically compile every night for us. I'll let you guys know when I have it up and running.
Click to expand...
Click to collapse
I thought it might be nice to get a thread going for discussion on the CM7 port for harmony for our gtablet device. There are nightly builds which are starting to incorporate some great things such as video acceleration and the new google release of 2.3.4 could be around the corner. In fact some 2.3.4 code made it into nightly#60.
I am in no way associated with CM7. If someone from CM7 or someone in some way associated with CM7 wants to run this thread or create a similar one please do so.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Rule #1 of CyanogenMod: Don't ask about release dates.
CM7 Harmony Stable Releases
http://mirror.teamdouche.net/?device=harmony&type=stable
CM7 Harmony Nightly Releases
http://mirror.teamdouche.net/?device=harmony&type=nightly
Changelog
http://cm-nightlies.appspot.com/?device=harmony
Tablet Tweaks II (original TT is already incorporated)
http://forum.xda-developers.com/showthread.php?t=1002000
For firsties...
How-To Guide:
(slightly edited from Wiki http://wiki.cyanogenmod.com/index.php?title=Viewsonic_G_Tablet:_Full_Update_Guide)
Before you do anything — Make a backup
Don't forget to back up your data. If you have synced the device with a Google account, then the contacts, calendar, Gmail & select other Google-related data will not be lost and will come back after the next sync. However, you should backup anything you want to keep that is not stored on the SD card:
Bookmarks,
Applications; use Titanium Backup or the Astro File Manager, for example,
Any application data not on the SD card.
It would also be a good idea to backup everything stored on the SD card in the rare case the SD card must be formatted to resolve any major problems.
Backup for Root Users is a free application that can assist with backing up your data.
Installing ClockworkMod Recovery
For this guide, it is not necessary to root the Viewsonic G Tablet in order to flash CyanogenMod. You can simply install ClockworkMod Recovery & continue on.
Warning: Installing ClockworkMod Recovery on the Viewsonic G Tablet will void the warranty.
Download the ClockworkMod package: Download
Unzip the ClockworkMod package & copy the recovery folder & the update.zip to the root of the internal memory (NOT in any folders & NOT to the removable SD card).
Power off the Viewsonic G Tablet and reboot holding the Volume Up button and the Power button until the device is in the stock recovery.
While in the stock recovery, use the Volume buttons to navigate to the apply update.zip & press the Home button to select it.
Once the it the update.zip is applied the Viewsonic G Tablet will have ClockworkMod Recovery. Please continue to the next section.
Flashing CyanogenMod
*******************
adampdx said:
...according to this tweet we're not supposed to flash between the stable releases and the nightlies. ....
Click to expand...
Click to collapse
*******************
jerdog said:
Echoing the above -
DO NOT USE ROM MANAGER ON THE VIEWSONIC GTABLET!!!!! IT WILL BORK YOUR DEVICE 99% OF THE TIME. MAGIC VALUE MISMATCH AND OTHER ASSORTED ERRORS.
We've been dealing with these issues for months now - don't discount because you think you know better because you've used it on XYZ phone.
IT CAUSES ISSUES ON THE GTABLET. PLEASE EDIT YOUR OP TO REFLECT THIS. THERE ARE POSTS ALL OVER HERE DETAILING THIS. PLEASE ALSO POST A LINK TO BEKIT's CWM .8 - THAT IS THE ONE THAT WAS MODIFIED TO WORK WITH THE GTABLET GIVEN THE MULTIPLE QUALITY CONTROL ISSUES ASSOCIATED WITH THE PARTITIONS AND WHAT NOT.
Click to expand...
Click to collapse
Place the CyanogenMod update.zip file on the root of the SD card.
Optional: Place the Google Apps .zip on the root of the SD card also.
Boot into the ClockworkMod Recovery.
Once the device boots into the ClockworkMod Recovery, use the side volume buttons to move around, and either the power button or the trackball to select.
Select the option to Wipe data/factory reset.
Then select the option to Wipe cache partition.
Select Install zip from sdcard.
Select Choose zip from sdcard.
Select the CyanogenMod update.zip.
Optional: Install the Google Apps by performing steps 7 - 9 again and choosing the Google Apps update.zip.
Once the installation has finished, select +++++Go Back+++++ to get back to the main menu, and select the Reboot system now option. The Viewsonic G Tablet should now boot into CyanogenMod.
Having issues with finding your Internal Storage?
Check your fstab. CM has a different paradigm. See below from maxdamage2122
maxdamage2122 said:
This is a flashable zip file that I have created to backup the vold.fstab file and replace it with one that mounts the internal storage as /sdcard.
http://goo.gl/DS8u9
Click to expand...
Click to collapse
Edit: Thanks and props to the CM team and all involved. No thanks to me, I am just a copy/past whore.
Edit: Removed RomManager Method (thanks badfrog and jerdog)
Edit: Added reference to fstab mod. Thanks maxdamages 2122
Do not use rom manager on the gtab
do not use anything but bekit 0.8 recovery
do not use rom manager on the gtab
do not use anything but bekit 0.8 recovery
do not use rom manager on the gtab
do not use anything but bekit 0.8 recovery
do not use rom manager on the gtab
do not use anything but bekit 0.8 recovery
do not use rom manager on the gtab
do not use anything but bekit 0.8 recovery
Great job Oozura. Make sure Mad-Murdoch links this thread in his post in the nook forum. I had volunteered to do the same but he didn't get back to me. I'm a long time CM nightlies user on Droid, and now on GTab as well. I'll post as much as I can here.
And that bad frog is right. Use bekit's 0.8 GTab recovery and forget about Rom Manager. You'll just end up having to nvflash...
Thanks!
MC
thebadfrog said:
Do not use rom manager on the gtab
do not use anything but bekit 0.8 recovery
do not use rom manager on the gtab
do not use anything but bekit 0.8 recovery
do not use rom manager on the gtab
do not use anything but bekit 0.8 recovery
do not use rom manager on the gtab
do not use anything but bekit 0.8 recovery
do not use rom manager on the gtab
do not use anything but bekit 0.8 recovery
Click to expand...
Click to collapse
Are you sure about this? If so I dont mind editing that part of the CM instructions.
Echoing the above -
DO NOT USE ROM MANAGER ON THE VIEWSONIC GTABLET!!!!! IT WILL BORK YOUR DEVICE 99% OF THE TIME. MAGIC VALUE MISMATCH AND OTHER ASSORTED ERRORS.
We've been dealing with these issues for months now - don't discount because you think you know better because you've used it on XYZ phone.
IT CAUSES ISSUES ON THE GTABLET. PLEASE EDIT YOUR OP TO REFLECT THIS. THERE ARE POSTS ALL OVER HERE DETAILING THIS. PLEASE ALSO POST A LINK TO BEKIT's CWM .8 - THAT IS THE ONE THAT WAS MODIFIED TO WORK WITH THE GTABLET GIVEN THE MULTIPLE QUALITY CONTROL ISSUES ASSOCIATED WITH THE PARTITIONS AND WHAT NOT.
Search for the endless threads on hard bricked and soft bricked tabs from using rom manager on the gtab. And before all you fanbois jump in and tell me you had no problems understand this....there are at least 2 different partitioning setups on the Gtab from the factory. Sometimes you can't even boot after flashing Gingerbread roms without nvflash.
MicroChip said:
Great job Oozura. Make sure Mad-Murdoch links this thread in his post in the nook forum. I had volunteered to do the same but he didn't get back to me. I'm a long time CM nightlies user on Droid, and now on GTab as well. I'll post as much as I can here.
Thanks!
MC
Click to expand...
Click to collapse
Been a long time droid, dInc user. I had sent you a PM about half way through the OP but decided what the heck. I hope this helps keeps discussion in one place for our gtab and CM7 (soon to be 7.1)
Oozura said:
Are you sure about this? If so I dont mind editing that part of the CM instructions.
Click to expand...
Click to collapse
Yes, I'm sure he is sure about this. Do NOT use Rom Manager to install any of the roms or to update CWM. Only use bekit 0.8 recovery.
I don't even install Rom Manager on my Gtab.
thebadfrog said:
Search for the endless threads on hard bricked and soft bricked tabs from using rom manager on the gtab. And before all you fanbois jump in and tell me you had no problems understand this....there are at least 2 different partitioning setups on the Gtab from the factory. Sometimes you can't even boot after flashing Gingerbread roms without nvflash.
Click to expand...
Click to collapse
Sounds good to me. I will take it out. As long as the other method works then no need to make anyone cry over a bricked tab.
+10000 I learned this the hard way on day one.
Sent from my CM7 GTablet
Oozura said:
Sounds good to me. I will take it out. As long as the other method works then no need to make anyone cry over a bricked tab.
Click to expand...
Click to collapse
Please - don't just take it out - add a warning about it. And provide the link to the known working CWM (Bekit .8).
RomManager method removed
OP Edited. Thanks.
jerdog said:
Please - don't just take it out - add a warning about it. And provide the link to the known working CWM (Bekit .8).
Click to expand...
Click to collapse
I quoted your post. Link was already there to correct version in the clockwork mod package. thanks.
Thank you. There is something flakey about these devices and they don'y like Rom Manager
So who is using the latest nightly? I'm running 60 and seems stable. I occasionally get a stall on browser apps after a long sleep. But can't find any other issues.
Sent from my ADR6300 using Tapatalk
Oozura said:
So who is using the latest nightly? I'm running 60 and seems stable. I occasionally get a stall on browser apps after a long sleep. But can't find any other issues.
Sent from my ADR6300 using Tapatalk
Click to expand...
Click to collapse
I am. No issues to report, camera is still grainy. Video playback is still great.
Sent from Desire HD or Inspire 4G or whatever this thing is called via premium XDA app.
Hardware Decoding?
So I installed AOSP the other day (the one in the Dev forum) because it was claiming hardware acceleration. It loaded up and was super laggy, but also didn't play the same video files that Vegan 5 played. I loaded up CM7 today and found the same thing. It's not nearly as laggy as the AOSP build, but still does not play video. I get volume, but no sound. Am I mistaken is thinking that we in fact have hardware acceleration now?
adampdx said:
So I installed AOSP the other day (the one in the Dev forum) because it was claiming hardware acceleration. It loaded up and was super laggy, but also didn't play the same video files that Vegan 5 played. I loaded up CM7 today and found the same thing. It's not nearly as laggy as the AOSP build, but still does not play video. I get volume, but no sound. Am I mistaken is thinking that we in fact have hardware acceleration now?
Click to expand...
Click to collapse
Progress is being made but we aren't there yet. Did you try mobo player? Engage software decoding and you'll be good to go.
Sent from Desire HD or Inspire 4G or whatever this thing is called via premium XDA app.
I've been using RockPlayer and havent had any issues. Most notably for me though was YouTube HD videos now play with no lag.
I think Irs421 is right. Its progress but not complete hardware acceleration until Nvidia releases GB drivers I would guess.
I figured as much. Progress, even slow progress, is good. I'm liking CM7 so far any how.
I was working on a ICS based hoppy rom. Unfortunately I just had a catastrophic screen failure, apparently when my laptop bag fell last night, it landed with enough force to shatter the screen on my nextbook! Oh well. it may be a while before I can work on anything to further the version I was working on.
FYI- Due to work, my time is very limited for working on the next version of Hoppy Rom. I apologize in advance. The company I work for is
setting up new engine test cells in China, and my self and 2 other people are main points of support! again Sorry for anything new taking so long!
DOCHOPPY HAS BEEN SIGHTED (Other than on a DAYZ server...Stay tuned.
Ok I have decided to pass along what I have been working on.
Warning***
This is for the Nextbook 7 premium ONLY!
Known working on Nextbook 7 premium tablets with serial numbers starting:YF1011
DocHoppy Presents!
DocHoppyRom Full On Root v2.0
and
DocHoppy Cramfs Style 3.0
Based off the official update image released by nextbook.
Major thanks to FINLESS BOB!!! GREAT HELPFUL GUY!
PRESENTING DOC HOPPY ROM
CRAMFS STYLE 3.0
AND
FULL ON ROOT v2.0
Disclaimer: I am not responsible for Bricked Tablets. This is known to work on tablet with SN starting with YF1011, and some YF1211.
First you will need to decide which version of the Rom you are going to load. The CRAMFS Style version has SU but you CANNOT write to the /system directory. This is a good all around Rom for those who may need SU but do not need to write to /system.
Full On Root is just that, you have full read write to the /system and can customize the Rom to your hreats content.
HOW TO INSTALL:
TO FLASH CRAMFS STYLE 3.0 Put the UPDATE.IMG file from the Cramfstyle Folder onto your SD card, while tablet is on and follow the on screen instructions.
After running the self extracting Zip file you will have a directory containing the following folders and files.
Drivers (folder)
CramfsStyle(folder)
FullonRoot(folder)
Log(folder)
Language(folder)
Readmefirst.txt
Rkusb.log
RkusbComm.dll
Setting.ini
RK29update.exe
TO FLASH CRAMFS STYLE 3.0 Put the UPDATE.IMG file from the Cramfstyle Folder onto your SD card, while tablet is on and follow the on screen instructions.
To flash Full On ROOT, Plug your nextbook into your PC via usb cable. Turn your nextbook over and with a safety pin or something of similar size, press and hold the reset button for 2 to 3 seconds.
Run the RK29update.exe
Select your Rom files via the boxes containing the .... And navigate to the correct directory for the rom you want to install.
Insert eache file in order according to the update tool.
Clear IDB. (this is like a lowlevel format for the Rom tool:
After the Tool says OK. Select Run. This will begin to load the Rom onto your tablet. It will go through loading and then checking the Rom install.
After the Rom loads and the tool comes back with an OK, patiently wait for the tablet to reboot, and load the new ROM. If the tablet is still connected to the pc via USB when the rom boots it will show the screen allowing you to select weather or not to turn on USB storage. Press the home key and you will be given a choice of Golauncher or Rklauncher. (go lock is a screen lock program.)
Enjoy the Rom!
Disclaimer: I am not responsible for Bricked Tablets. This is known to work on tablet with SN starting with YF1011, and some YF1211.
Features for both Roms:
Complete and correctly working market. It now correctly associates the tablet to your gmail account allowing purchases from market.
Launcher 3.0 as well as Go launcher ex. Launcher 3.0 was pulled from an rk2918 firmware3.0 update and put into this rom.
Google Calendar is now back and working correctly.
Original Email is back and working correctly.
Included Kindle App
Included Estrongs file explorer.
Both have SU though the Cramfs version cannot write to SW.
Removed Apps Added in last release and return to more of a original rom state.
Rom is pretty clean. And seems speedy.
Cramfs Style 3.0 Rom has 200mb internal Ram +/-
Full On Root 2.0 has 894MB of Free Internal Ram.
Cheers!
DocHoppy
www.freaktab.com
Keep in mind this is the first version of this ROM. There will be updates and changes made.
FUTURE CHANGES:
Custom Theme Changes.
More Tweaks to the system.
Long Term Wants:
Power Menu change to include recovery boot.
Power Menu change to include restart.
This is a work in progress.
Known working on Nextbook 7 premium tablets with serial numbers starting:YF1011
Linked here for image.
Non Add Showing Link.
DocHoppyFullOnRoot2.0
New Cramfs style Rom is still Available Here.
DocHoppyCramfsstyle3.0
To install DocHoppyRomv3.0, rename .img file to update.img, download update.img file, copy to SD card, and follow the prompt.
DocHoppyCramfsstyle3.0
Enjoy.
Disclaimer:
Not responsible for bricked tablets.
Enjoy!
Also visit www.freaktab.com
So freaking sweet, great work on RW!
I used Wendal's tool to decompress the cramfs file system.
As for the /system, Because the device uses cramfs, and based on everything I have read, using Wendal's tool to decompress the file system, make the changes, and compress is the only way I can see to be able to
customize the rom for the device. The image is rooted, but after the update.img is compressed, the /system file remains read only. I tested this using root explorer, but anything requiring su works fine. But all hope may not be lost, I was reading on a chumby forum someone suggested using mkfs.jffs to make it writable, but further down it notes that you would need to change the kernel (easy enough to recompile I think), to utilize a different file system. The boot loader would also need to be modified, something I am not ready to try and tackle just yet, I think I would be bricking my nextbook pretty quickly.
It is a start and I am actually learning a lot as I go.
Any thoughts or suggestions are welcome.
I am definitely a long time user / cyanogenmod / aosp fan, but as far as ripping open .img files its definitely new territory, I tried to find an internal SD card like the nook has, to maybe dump it, but I cannot find such a beast. Any progress you make is awesome. So do things like root explorer work, just not on /system due to cramfs?
Correct, root explorer does work, but due to cramfs, it does not allow you to toggle to rw from ro on the /system.
Working on taking apart apk's and customizing and rebuilding and resigning next.
just flashed this rom and it works great!
How would I go about doing a custom boot animation or image?
... even if it means flashing a new rom from clean?
This is great. Thanks. The only question I have is why do I see so few items in Market? Does it have anyhting to do with compatability?
Calendar & Sync Access
First, thank you for your work.
Before I update by Next7P, have you included Google Calendar and Sync access in this update?
I use MyPhoneExplorer and will need calendar sync to work so I can fully use for business.
Thanks.
There is another method to get Google Market on the Next7P, I am a new user so I can not post the link, but google , forums Whirlpool net au archive 1756859
, very easy and works great, but cannot get sync to work.
Dan,
Thanks for the responses!
sgtfoo : You can use Wendal's rk29xx tool to take a copy of my rom image, or the original update downloadable from nextbookusa.com, and
unpack it. You then have access to the system directory in an editable format. you can go into the system folder /system/media and replace the bootanimation.zip file with another one. Just be sure the image format is 480x 800 and that the zip file has 0% compression ratio. After you make the changes, just repack .img file via Wendal's tool and reflash.
dodoclub : Not sure why. I have a full market. You might try clearing the data and cache for the market. My market shows pretty full, I.E. I got 31050 entries when I searched for facebook in the market.
Danno65: Actually that is something I have been working on. I can get my google calendar to sync, currently I am using a calendar from the market called Jorte, which works great, how ever, googles actual calendar.apk closes unexpectedly, I am thinking it is just a version problem with the calendar, but haven't had a lot of time to follow up on it.
FYI here is the link to Wendal's tool, which makes it much easier to work on the update.img file.
https://docs.google.com/leaf?id=0B8hUXYDeoy_hNTc1YTVkYTMtNTNjZS00YjI2LTgyNDYtYjRjZjFmODdiZTQ1&pli=1
Cheers!
If you have any request or questions please feel free to ask, I will help anyway I can.
Thanks Dochoppy
Got one of these tablets for Christmass to replace an old broken tablet I use for work.
Google hosts our work email, so I still need to get Contacts and Appointments going, but I maybe able to side load them.
Noticed build.prop still has ro.secure=1. This prevents adb from having root access??
Calendar & Sync Access
DocHoppy,
I came across a post where the "Calendar.apk" and "CalendarProvider.apk" files must be in the "system/app" directory to work properly, I tried to copy these files to the above directory but found it to be read/only, will wendalls tool have to be used to get access to the directory?
Also, did you get your google calendars on your desktop to sync with Jorte on the Next7P, I tried but no luck.
Thanks
Dan
The updated image file worked great, thanks again
Thank you so much for your work in building a new rom for this thing. I am anxiously awaiting a new filesystem so we can have true root. How do we manage to recompile the kernel for ext4 support and change the /system fs?
Hello, first of all, thanks for your work!
I am having trouble loading this rom. it says there's an invalid image file in my sd card and if I want to delete.
Now, I don't know if my tablet is a never or older version of what you guys have...
Next7p
2.3.1
kernel: 2.6.32.27
build: v2.0.7.....
my serial is also different from alot..it starts with YF0511
any help or tips?
markmatters said:
Hello, first of all, thanks for your work!
I am having trouble loading this rom. it says there's an invalid image file in my sd card and if I want to delete.
Now, I don't know if my tablet is a never or older version of what you guys have...
Next7p
2.3.1
kernel: 2.6.32.27
build: v2.0.7.....
my serial is also different from alot..it starts with YF0511
any help or tips?
Click to expand...
Click to collapse
I would say the serial number would have something to do with it, check on the site for nextbook and see if your serial is in the same *batch* as ours, if the original serial is in a different group, im assuming the hardware may be slightly different? If so, you can always use his method to repack the original with root.
First off I would like to say that I was very pleased when I came across this thread from another one. I haven't flashed this ROM yet, but plan to. Thank you for your work on this as I have been searching the whole internet since I got this thing [4 weeks now] for some sort of custom ROM. It is hard to use this tablet when I have ICS on my Captivate and Vibrant. GB just isn't as cool.
One thing I hope we can work on is root access, so we then can use Titanium Backup. Then we won't have to manually reload everything when new releases come out.
With all that being said, if there is anything I can do to help, I would love to. Like I said, I plan on flashing this probably tomorrow or Tuesday. Thanks again.
For the record, I got titanium backup working fine on this rooted rom. it is capable. You just need to reboot after it restores a backup.
i'm new to android. glad to see rooted rom finally, keep it up!!!
i have a clarification, any improvement in the booting time? my device took 1min30sec (power ON to ready to use, for me, 90sec seem like not fast enough).
Good luck on improving boot time. And besides a tablet is best used when on all the time... try using the suspend state to quickly wake it. We're just starting with the early versions of this rom... give it time to grow.
Sent from my N7p using XDA App
Build.prop editing
Okay so observation:
Our tablet is not recognized as a "tablet" by the Android market, only and android device.
What prop would I have to edit in order to have us recognized as I tablet. I noticed this when:
I finally managed (through some internet tutorial before this rom) get the market working (the first version, not 3.1+). And when I downloaded apps (I'll use Minecraft Pro as an example) I noticed that the way mine looked and the way the tablet version looked via android market photos and Youtube, ours looks like an enlarged phone version rather than a tablet optimized version. What can I edit to fix this?
Flashed this today... so for it works great. Love the new boot animation. Great work and can not wait for future releases!
Sent from my Nextbook Premium 7 (Doc Hoppy's Rom v02) from the XDA app.
---------- Post added at 12:16 PM ---------- Previous post was at 12:03 PM ----------
One thing that would be great on a future release [not sure if it is possible yet with out r/w], would be a bigger data partition for apps. Moving everything large to the SD is ok, just takes longer to boot those apps. A kernel that would allow voltage control app [like CPU Master] to work also. Just a thought!