Related
Ok this is a newb question but is there any integration between these three?
I would like to do some relatively basic customization to ROMs I install and be able to reapply them. It would also be nice to work in a PC environment and test there. Any guidance?
I guess you can backup either smartphone or emulated device via activesync with more expensive version of sprite backup, and then restore the backup to any device or emulator again... should be enough.
As far as I know, it's not possible to emulate the ROMS on a PC using an emulator. I remember someone else asking about this. Yep... you're reviving part of this topic.
ok, forget about the emulator...
If I run sprite backup on a ROM and do a backup, does it just save the changes that I made to the ROM or does it save everything in the ROM?
If it is the former, it would seem that I could reapply my changes to a new ROM after an upgrade...
owner information
carrier MMS and phone information
updated styles
softbutton location assignments
adding new icons
registry install information for programs
added and deleted icons
etc.
...and I could keep reapplying these same changes to new ROM builds as long as the changes didn't break a new build.
Or am I missing something?
If Sprite Backup is only good for a given build and I switch ROM builds every quarter it doesn't seem worth doing a backup.
ROM Cooking
bipinsen said:
As far as I know, it's not possible to emulate the ROMS on a PC using an emulator... this topic.
Click to expand...
Click to collapse
Well I have even more respect for ROM builders now. I can't imagine having to apply changes without being able to test them in an emulator, although if you can apply your changes to your phone and save that image to make a ROM later, it seems like you wouldn't need Sprite Backup. You would just use the ROM tools to backup your whole ROM.
kkrull said:
If I run sprite backup on a ROM and do a backup, does it just save the changes that I made to the ROM or does it save everything in the ROM?
If it is the former, it would seem that I could reapply my changes to a new ROM after an upgrade...
owner information
carrier MMS and phone information
updated styles
softbutton location assignments
adding new icons
registry install information for programs
added and deleted icons
etc.
...and I could keep reapplying these same changes to new ROM builds as long as the changes didn't break a new build.
Or am I missing something?
If Sprite Backup is only good for a given build and I switch ROM builds every quarter it doesn't seem worth doing a backup.
Click to expand...
Click to collapse
It's a hit or miss depending on the ROM version. I have noticed that the registry entries among the different versions for WM6 (different builds) are sometimes different enough that registry restores don't always work. Here's been my strategy (you have to do a search yourself for these softwares):
- Connect with Mobile Registry Editor from my PC to phone => backup as separate .reg files all pertinent locations of the registry that I want
- Have a permanent location in my SD card where I can keep these .reg files
- When I have downloaded a new ROM, I use Resco Registry Editor to import the reg files back in registry. Since I'm not importing the entire hive, I have been reasonably successful with this. Note: there are many different ways of importing registry files on the phone; I just like Resco.
Hi!
First off, if I have posted in the wrong place, I am sorry and if necessary please move to relevant location!
Right, I have had a major problem with my HTC Desire, I spent all day & night yesterday trying to fix!
I rebooted the device as it was running short of memory, then phone just got stuck on the white HTC boot screen & wouldnt move from that, so I restored a backup of the phone using Nandroid, but I had the same result, fine I thought, Id just download a RUU to reflash the device, this didnt work and came up with errors, BUT what I did manage to do is take the rom.zip and make a new ROM in Cygwin which flashed perfectly and I ended up with a stock 2.2 and all seemed to be back to normal, so I then tried to restore a backup again, but same problem, white HTC screen so I have came to the conclusion that I will have to TRY to re-create my old ROM & settings using this stock ROM!
So far I have managed to root the ROM & add everything that my old ROM had (was using the latest Lee Droid ROM - man big respect to you for what you do!!) but there are a few things missing which I do not know about and this is where I need all your help with!
Below are the bits I desperately need including with the ROM (my phone wont install any other ROMS other than the stock 2.2 I said earlier) I am not expecting the members here to do it all for me, BUT if you could point me in the right direction to either the posts with directions for what I need or other places where I can find the bits & how to do it!
*** Wireless N support (my router is N & so are the other wireless devices)
*** An overclocked kernel (such as Lee Droid's V2.2e_A2SD ROM)
*** The ability to wake up & unlock the phone with the optical thumb trackpad
*** The reboot option when long press on unlock button (ideally the nice, clear menu that includes Hibernate from the new HD ROMS)
*** Branding & naming the ROM (as Lee Droid does on his ROMS)
*** Custom wallpapers instead of stock wallpapers
I am sorry for the long post, but I really NEED this completed ASAP and I know with all your help, I can do it!
Also, I am making a simple program on my PC to custom ROMS (add & delete apps, alarms, ringtones & notifications etc) which I will upload for the community when it has been completed & working 100%!
Thanks in advance & I hope that you can find it in your hearts to help me!
Arty
I don't think nandroid restores the kernel. After you do a restore with it, you need to flash a kernel that is compatible with the rom being restored.
Personally, when I restore I backup on my phone, I reinstall the rom and then just restore /data from my nandroid backup.
Thanks for your fast reply DiGi760, however I think you misunderstand!
I need a kernel that supports overclocking the CPU as I use SetCPU and so far its just the standard 998MHZ I can set the clock to, where I would like it to be higher, like 1038MHZ or whatever it is
Your backup copy is broken. You can't "really" recover from this. Just reflash 2.2 and update it to whatever you had before and start over. You may be able to manually pull stuff from your SD card where the nandroid backup was written to but that would be a tedious amount of work.
Thanks Syn Ack, why would the backup AND the info on my phone corrupt at the same time?
I do actually have a copy of the Clockwork folder from memory card stored onto my PC, but none of the backups will restore (I have a total of 10 going back a few months) but none will restore, not even any other ROMS that Ive downloaded with ROM Manager or from forums will install to it, only the 2.2 ROM that came with the RUU file I downloaded.
An update on my progress of making my new ROM:
I have managed to get the Reboot menu integrated into my ROM, so now I am just stuck on the following:
Wireless N support
Overclocked Kernel
Unlock the phone with trackpad
Branding & naming
Custom wallpapers
so if anybody can help me I'd really appreciate it!
Wow, its been over a week and no replies, why cant anybody see it in themselves to help? after all, you all was newbies once too, just remember how you felt when nobody answered a post you *REALLY* needed help with!!!
Just saying
Gees thanks for nothing u lot!!!!
HTC Desire CDMA (BravoC) Thread
I wanted to create this thread to show that there are CDMA Desire users that there are users that want to help ourselves, and we need more ROMs! With the addition of 1.06 HBOOT Desire's being able to be rooted now, there is a large influx of these users new to rooting.
Most of the content was rewritten by me, but I must give thanks to the XDA Forums, Cyanogenmod Forum, Team US Cellular Forums, MIUI forums, and 2fast ROMS! This took a while to put together for me!
Of course, thanks to fllash for the Desire Index thread and for being awesome, but with the influx of CDMA users, it's time to branch off slightly.
This was written by a US Cellular user, but most information is for all CDMA phones. I have owned both a 0.98 HBOOT and a 1.06 HBOOT device.
Contents:
Tips
ROM List
Rooting Guide 0.98
Rooting Guide 1.06
Backup Guide
USCC Return to Stock Guide
USCC Lost 3G Fix - ADDED 7/24
Tips for CDMA Users:
Red comments are by 2fast4u88
Blue comments are rebuttals by me.
Most things in this forum are for GSM users, the CDMA Desire was added a year ago but never got an official forum on XDA.
Your phone is CDMA if you do not have a SIM card port by your SD card.
CDMA users do not need to worry about radio's as much as GSM users do. Most CDMA desire's only have 1 or 2 different radio's depending on the carrier.
It is recommended to not mix h-boots and radios. Use the radio with the right h-boot. The newer radio's have better battery life. The older radio's have better signal strength
Don't worry people, I haven't seen a ROM that updated your radio without specifying it very well before you download!
CDMA users do not need to use different HBOOT images for ROMs.
Gsm roms do not need h-boots. All the modded h-boots are for is for memory like cmtd does for us.
Backup your APNs!
You do not need to backup your apn list when the rom dev supply's the zips to flash.
Not all ROM devs supply this unfortunately, and it's always useful to have one just in case, especially with easy apps like APNs Backup & Restore!
There is no Gingerbread Sense ROM for CDMA users yet. Official Gingerbread for the Desire will not have Sense built in due to the limited space on the Desire's memory.
Gingerbread update will have sense but with some stuff downloadable last I heard. Even the the uscc desire will not have it along with probably other carriers. Uscc made it public one update per device.
Yeah, unfortunately it's not likely to happen for us CDMA users.
If you do any fixes to your phone like repairing your 3G service (detailed below for USCC members) or getting your MSL Number, you must do so on a Sense ROM with EPST.apk, which most Sense ROMs have. Keep a backup of your original ROM! The official 2.3 update should fix this problem, but no guarantees.
What are you even talking about here in all honesty? There is no issue flashing anything that I am aware to break 3g?
On the Cyanogenmod forums, a lot of people happen to ask about lost 3G service for US Cellular, and many of these people are roaming. I've had this happen to me and found the official fix by the USCC Roaming Tech Support. Guide added to the third post!
If you ever ask for support, specify you're a CDMA user and your carrier.
Use BravoC recoveries, not Bravo!
If you need more space for apps, use either App2SD, Data2SD/EXT, CMTD, or for CM7: S2E from the market.
This a problem a little bit and bugs me everytime I see it. Skuddy is the only one to use data2sd. All the other roms running what is to be called data2sd is a knock of of darktremors apps2sd+ with out dalvik moved. Also every rom has one built in so using a app to do it is going to cause issues.
The market app S2E seems to be a universal Cyanogenmod addon that works on most devices. I personally use and love it.
DO A NANDROID BACKUP
Only needed for having a backup of sense. If you have a ruu it isn't needed. You can of course due backups of a rom if you want but isn't needed everytime. I don't waist my time with backup's anymore.
Yes, but it's good practice for those who are just starting, as they're very likely to miss a step when flashing a ROM, or trying out CMTD for the first time.
-------------------------------------------
ROM List:
Gingerbread (Android 2.3.x) ROMS:
Oxygen - http://forum.xda-developers.com/showthread.php?t=971904 USE THE CDMA LINK TO DOWNLOAD
Cyanogenmod 7.0.3 (CM7 CDMA) - http://forum.cyanogenmod.com/topic/20119-cyanogenmod-7-for-the-htc-desire-cdma-v703-5-may-2011/
Cyanogenmod 7.1-RC1 - http://forum.cyanogenmod.com/topic/...or-the-htc-desire-cdma-v710-rc1-26-june-2011/
Etheral - http://teamuscellular.com/Forum/viewtopic.php?f=27&t=381
MIUI - http://2fastroms.com/viewtopic.php?f=23&t=139
Dirty Money - http://2fastroms.com/viewtopic.php?f=23&t=128&sid=4c702bfc9aeb69582f22198bf5c04eaa
Phoenix 2.x - http://2fastroms.com/viewtopic.php?f=23&t=46&sid=4c702bfc9aeb69582f22198bf5c04eaa
Froyo (Android 2.2.x) ROMS:
Rooted US Cellular Stock 2.2 - http://forum.xda-developers.com/showthread.php?t=947481
ThunderSense - http://www.teamuscellular.com/Forum/viewtopic.php?f=71&t=427
SleekSense Stable - http://2fastroms.com/viewtopic.php?f=23&t=16&sid=4c702bfc9aeb69582f22198bf5c04eaa
Sensible 1.1 - http://2fastroms.com/viewtopic.php?f=23&t=12&sid=4c702bfc9aeb69582f22198bf5c04eaa
LeeDroid CDMA Port - http://forum.xda-developers.com/showthread.php?t=1183020
RUUs (Stock ROMs, used to update or return to stock)
US Cellular Stock 2.2 Update - http://www.htc.com/us/support/desire-uscellular/downloads/ Look at the third post for more information.
Alltel - http://shipped-roms.com/download.ph...8.11_NV_Alltel_1.70_release_150765_signed.exe
-------------------------------------------
More information in the next 2 posts!
Rooting Guides
DISABLE HTC SYNC ON YOUR PC
THIS WILL VOID YOUR WARRANTY, at least software wise. Insurance should still cover physical damage I believe.
-------------------------------------------
How to root HBOOT 0.98:
To make this easier, create a new folder on your desktop (or wherever you prefer) to hold everything. Let's name it Rooting.
Download unrEVOked: http://unrevoked.com/recovery/
If you're on Windows, you'll need special drivers. Linux and Mac user's have it easy for this one.
When I rooted my first Desire, they instructed to install HTC Sync then uninstalling it, which keeps the drivers on your system. While some say these drivers aren't the best ones, they will most likely work anyway.
You must also install the unrEVOked HBOOT drivers located here: http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
You can either follow the guide in the link above, or follow this one:
Driver Download (WINDOWS ONLY): http://unrevoked.com/rootwiki/lib/e...unrevoked.com/recovery/android-usb-driver.zip
New recovery (ClockworkMod 4.0.1.0 by 2fast4u88): http://2fastroms.com/viewtopic.php?f=22&t=40
Open the zip and place the recovery image in the folder like pictured below.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
1) If on Windows: Unzip the contents of the driver zip file into a folder inside the folder we're using to keep everything together. Let's rename this folder to Android HBOOT Driver. Download the UnrEVOked program and place into the rooting folder. Save the recovery to the same folder.
2) Turn off the phone and make sure it's unplugged. Hold down the Volume Down button first, then hold the power button. You should see 3 Androids on the bottom of the screen, you are now in HBOOT. It will check your SD card whenever it goes in here, so don't worry if it takes a second.
3) Make sure your HBOOT is 0.98, the second line of text should say something like HBOOT-0.98. If it is 1.06, check the other guide.
4) Plug in your phone. If you're on Linux or Mac, skip the rest of this step. Windows will look for a driver and likely fail, and your phone should say HBOOT USB PLUG. We will now install the driver. Make sure you're an administrator on your computer! Click on the Start button and right click on Computer, then click on Manage. A window will open, and click on Device Manager on the left hand side. (OR just search for Device Manager in the search bar). Look for Other Devices, expand the list and you'll see Android 1.0. Right click on this and choose Update Driver Software, click browse and find the folder you extracted your driver files to. You'll get a warning about unsupported drivers and clikc Yes/OK. You should now see Android Phone at the top with an entry named Android Bootloader Interface. It is recommended to restart your PC after this. Might want to bookmark this thread and return!
5) Now unplug your phone and turn if off (Pull out the battery or use the Volume Buttons and Power button to navigate the menu to select fastboot, then select reboot). Once rebooted, go to your home screen and press Menu and choose settings. Go to Connect to PC, select Default connection type, select Charge only and uncheck Ask me.
6) Go back to settings, choose Applications, select Development, and check USB Debugging, and go back to Applications and check the Unknown Sources.
7) Run reflash_package.exe and select custom recovery, and select recovery-bravoc-3.0.2.8.img.
8) Plug in your phone and start the process. Your phone will reboot a few times, DO NOT UNPLUG YOUR PHONE. Wait until unrEVOked says done! You should be rooted,S-OFF, and custom recovery! Install Titanium Backup from the market to make sure your phone is rooted then follow the Backup Guide! Backup your APNs as listed below!
-------------------------------------------
-------------------------------------------
How to root HBOOT 1.06:
To make this easier, create a new folder on your desktop (or wherever you prefer) to hold everything. Let's name it Rooting.
Download AlphaRevX Beta: http://alpharev.nl/x/beta/
Keep this page open, because while running the program you'll need to generate a key.
Clockworkmod 4.0.1.0 by 2fast4u88 Fastboot Recovery Image A.K.A. PB99IMG for ClockworkMod: http://2fastroms.com/viewtopic.php?f=22&t=40
Extract the zip file and place PB99IMG.zip like pictured below.
If you're on Windows, make sure to install the Windows drivers provided on the page or get them from here: http://www.multiupload.com/2OFYWZFCCR
1) Turn off the phone and make sure it's unplugged. Hold down the Volume Down button first, then hold the power button. You should see 3 Androids on the bottom of the screen, you are now in HBOOT. It will check your SD card whenever it goes in here, so don't worry if it takes a second. Make sure you have HBOOT 1.06 and you have S-ON. If your Desire has S-OFF, skip to step 7.
2) Unzip the AlphaRevX file into a folder inside the rooting folder and name it AlphaRevX. Place the other 2 files in the rooting folder.
3) Install the HTC Drivers, it should be fairly easy to follow its instructions.
4) Go to your home screen and press Menu and choose settings. Go to Connect to PC, select Default connection type, select Charge only and uncheck Ask me. Go back to settings, choose Applications, select Development, and check USB Debugging, and go back to Applications and check the Unknown Sources.
5) Plug in your phone, and run AlphaRevX. Go back to the AlphaRevX download page and enter in the details provided to you. Copy the serial number, and right click paste into the window. If right click doesn't work, right click the top left icon in the window, choose Edit>Paste. Hit enter, and it should follow the process. It will reboot your phone, DO NOT UNPLUG YOUR PHONE UNTIL IT IS SAFE.
6) Once completed, your phone should be rooted and S-OFF, but not recovery. Close AlphaRevX and install Titanium Backup from the market to see if you have root, and follow the Backup guide after finishing the next few steps. In case you're just S-OFF, but no root access, you have two options: Try SuperOneClick: http://forum.xda-developers.com/showthread.php?t=803682 Or Try unrEVOked found in the 0.98 HBOOT Guide.
7) Now we must install custom recovery, place the PB99IMG.zip file onto the the SD card, do not place it into a folder. Once copied, unplug your phone and turn it off. Go back into HBOOT by holding down Volume Down and then the Power button. This time, when it does its scan, it will find the PB99IMG.zip file. It should say Press Volume Up to apply update or something like that. Your phone will reboot normally, and then remove PB99IMG.zip from your SD card. Finally, turn off your phone again, boot into HBOOT and select recovery, and you should see ClockworkMod 3.0.2.8 boot up. Finally you are done with the rooting process!
-------------------------------------------
-------------------------------------------
Backup Guide
There are many processes to backup your phone. We can divide these processes into 2 categories:
DATA BACKUP and NANDROID BACKUP
Data backups are backups of certain things such as Apps, Data, Text messages, and even system preferences.
-------------------------------------------
Nandroid backups are backups of everything on the phone, from every partition of SYSTEN, DATA, BOOT, SD-EXT, CACHE, and .ANDROID_SECURE. This is a byte-for-byte copy of everything on your phone (and if you have a partitioned SD Card).
System is your phone's ROM area, holding the internal components of the ROM and the built in apps.
Data is the area where applications and app data is kept if not installed to the SD Card.
Boot is the ROM's boot image. You will have very little interaction with this.
SD-EXT is on your SD Card, standing for SD EXT Partition. EXT2/3/4 is a file system used by linux (which android uses) and can be used to store data. Commonly used for Apps2SD or Data2SD/Data2EXT.
Cache is the area on your phone that data is temporarily written to, like web page content and app data.
.Android_secure is used for the normal Android Apps to SD system. Some apps keep data on your sd card.
Before you EVER DO ANYTHING like flashing another ROM, or try a modification like Data2SD or other ROM modifying scripts, DO A NANDROID BACKUP. This is the most important thing you'll ever need in case soemthing goes wrong.
-------------------------------------------
Data backups are backups of parts inside the phone, and certain parts such as user apps and app data can be applied to whatever ROM you use. Say you are going from your Stock Sense ROM and you want to try Cyanogenmod, but you don't want to replay all your games like Plants Vs Zombies and Angry Birds. Using an app like Titanium Backup, you can backup the app and all of its data and restore it on another ROM like nothing happened.
Data backups can even include things like ringtone settings, text messages, preferences, and contact data.
If you care about anything like those on your phone, you should do a weekly backup.
-------------------------------------------
Nandroid backups are completed by your recovery image. Say you want to do a Nandroid backup on Clockworkmod, you simply boot into recovery, select Backup and Restore, and choose Backup (make sure you have enough space on your SD card, such as 1GB free). The process will copy everything on your phone and place into a folder on your SD card, and you can restore these backups any time you like.
Data backups are done by certain apps. Titanium Backup and My Backup (Normal or Pro) are the common suggestions. Titanium Backup has been around forever and works great, but My Backup will also backup other things like text messages, call logs, and other core phone features. I personally use Titanium Backup, SMS Backup and Restore (https://market.android.com/details?id=com.riteshsahu.SMSBackupRestore His other apps are useful as well).
-------------------------------------------
Titanium Backup Guide
Once you are rooted and install Titanium Backup, if you're on Stock ROM, open up Titanium Backup, and hit the Problems? button in the bottom center. There should be a Upgrade or install Superuser button, which is required for many root options and required for backing up! Install it!
For a quick and easy app backup, just go to Titanium Backup and hit Menu, then select batch. Find the Backup all user apps + system data option with the button that says RUN in black. Hit Run the batch operation at the top, and make sure you have enough space on your SD card, around 200mb. It will now start the backup and complete in a few minutes. The more apps, the more time it takes.
When you install your new ROM, install Titanium backup (Superuser is built into most custom ROMS) and hit menu, Batch. Find Restore missing apps + all system data. Some ROM apps will clash, like camera and dialer, so uncheck those and reinstall them manually.
-------------------------------------------
One of the most important things to do is to backup your APNs. APNs are what allow for picture messaging/MMS and in some cases internet browsing. This app will streamline the process: https://market.android.com/details?id=com.riteshsahu.APNBackupRestore
Simply backup the APNs from your stock ROM and restore them onto any ROM you'd like.
If you must remake your APN and you are on a US Cellular Desire, this should help you:
http://teamuscellular.com/Forum/viewtopic.php?f=72&t=60
I would suggest making a Sense APN backup and a non-Sense APN backup and restore one to whichever ROM you're using.
-------------------------------------------
-------------------------------------------
Returning to Stock (US Cellular users)
So say your phone screen cracked somehow, like your girlfriend had it in her lap, and she got out of the car. Concrete + perfect angle + force of gravity = cracked glass. (I still love her don't worry)
Hopefully you have insurance on your phone, and the software works fine and the touch screen works.
For those returning it, you should definitely flash back to the stock ROM or apply the 2.2 Update. This will not S-ON your phone, but it likely won't matter.
To do this, proceed to http://www.htc.com/us/support/desire-uscellular/downloads/ and follow its instructions for installing the update. However, many people have problems with this, but don't worry, I found out how to install the update without the program working.
1) Download the update and open the executable file. It will unpack the files to the temporary directory (%temp%) but we can find this easily. After opening it and waiting for it to complete unpacking, open your task manager and find either ARUWizard.exe or ISBEW64.exe. Right click on one of these files, click Open File Location. Find rom.zip, which should be about 163mb. Copy this into a folder of your choosing, like Rooting/Stock Froyo.
2) Do a Nandroid Backup on your phone!
3) Rename the rom.zip into PB99IMG.zip and place onto your SD Card of your phone.
4) Reboot into HBOOT (Hold Volume Down and Power) and it should find it with seconds, but will take a minute to load.
5) Apply the update, and you should be back to Stock Froyo. Your HBOOT will be 1.06, but you will be S-OFF still. They most likely won't care.
Optional steps!
6) Say you're on US Cellular, and need to send it back to Assurant Solutions, the insurance carrier of US Cellular. You will need a $100 deductable payment. They should send your new Desire in the mail pre-loaded with Froyo, along with a return envelope. Take out your SD card of your old phone, and place your old phone in the envelope.
7) Take your new phone and activate it by calling 888-944-9400 on another phone or Google Voice on the desktop, follow the menu to talk to a representative by dialing zero as your last step. Make sure to have the ESN DEC number of the new phone (Under the phone or on the box), the last 4 digits of the account holder's Social Security Number, and of course the phone number.
8) The person you speak to will activate the phone and ask you to dial *228 to update the PRL, which will take about 2 minutes. Say thanks to the helpful representatives!
9) Follow the rooting guide for HBOOT 1.06, restore ClockworkMod, (optionally nandroid the stock ROM), and restore the update for your previous ROM.
10) Go get a good protective case for your phone and KEEP IT ON.
-------------------------------------------
-------------------------------------------
Lost USCC 3G/1x Fix
For some reason, for a select few users, they lose 3G service, and in some cases 1x all together! If this happens to you, don't fret! USCC Tech Support is great, just don't tell them that you're rooted. In most cases, these fixes are only avaliable for Sense ROMs, because EPST.apk is a Sense-Framework only tool that handles core functions of the phone, such as programming the number and other items. If you need to call tech support, flash a Sense ROM or the best case: your stock ROM. Keep a Nandroid restore set of your stock rom backup up on your computer or dropbox just in case this happens. This is the official fix they gave me.
While attending college 100 miles away from all US Cellular Towers, my 3G lost service. When you roam on a USCC device, you're bouncing off of Verizon towers, and sometimes they block your device for some reason. Not even Tech Support always knows why. I had them send me the fix since I had to run to class, and I noticed on the Cyanogenmod forums a lot of people lose their data signal, so I shared it for them.
[COLOR="#FF00000"]YOU MUST DO THIS ON A SENSE ROM, STOCK IS PREFERRED. ROOTED OR NOT.
CALL TECH SUPPORT FIRST, THEY'LL GIVE YOU YOUR SUBLOCK CODE AND GUIDE YOU THROUGH THIS.[/COLOR]
You can find your Sublock code (MSL) by getting the MSL Reader app from market and running it on your stock ROM.
When finished, make sure your data works, and then you can boot back into whatever ROM you'd like.
HTC Desire
1. Press "Phone," dial ##778#.
2. The screen will display EPST "View Mode," "Edit Mode," Select "Edit Mode."
3. Enter the SUBLOCK code, press "Ok."
4. The screen will show about 20 different fields.
5. Tap on "Modem Settings."
6. Tap on "Preferred Mode.
7. Tap on “CDMA Only”, Press "OK".
8. Tap on "HDR Hybrid Preferred."
9. Tap on "Disable". Press "OK."
10. Press the "Menu" button at bottom of phone.
11. Tap on Commit Modifications.
12. Press OK to reset device.
13. The phone will reboot and "1X" will appear at the top. . Your customer should now be able to access data.
14. When the customer returns to our coverage area, go through the same process and reselect "Automatic" in the "Preferred Mode" and "Enable" in the "HDR Hybrid Preferred."
Click to expand...
Click to collapse
great thread, we needed something like this for us unloved cdma users. its good to have all the cdma stuff in one place for everyone to access.
Wow! Thundersense is not one im familar with..
http://2fastroms.com/viewforum.php?f=23
Add those to the roms. Sleeksense is the only froyo rom with working undervolt and faster than any of the other sense roms also.
Added a couple of those that seem to be updated the most. Also, since you know your ROMs, what is your explanation on why we don't have CDMA Gingerbread Sense ROMs?
Change the miui links as my forum has the most up to date miui's since myself and skuddy does them for miuiandroid.
As for why we don't have gingerbread sense. It would probably be because we don't have a leak. No leak no kernel. No source no kernel made easy.
2fast4u88 said:
Change the miui links as my forum has the most up to date miui's since myself and skuddy does them for miuiandroid.
As for why we don't have gingerbread sense. It would probably be because we don't have a leak. No leak no kernel. No source no kernel made easy.
Click to expand...
Click to collapse
So I'm guessing there's no way to port the GSM leaked kernel? After all, the EVO 4G uses the same processor, or does this factor other things like the built in memory and others?
any way we can help get the kernel out faster? like email htc once a day asking about a kernel source for the desire?
darkmage1991 said:
any way we can help get the kernel out faster? like email htc once a day asking about a kernel source for the desire?
Click to expand...
Click to collapse
Unfortunately, that's not likely to happen. Then again we'll never know until we try. Still doubt it though.
um, probably a stupid question but at http://developer.htc.com/ it shows the us cellular desire having the source code, though it says eclair im guessing that is not what we need?
Correct. We want a Froyo or Gingerbread Kernel.
Even though a phone has the same cpu doesn't mean a thing. The kernel controls more than a cpu. Like anything setup on the board. The cdma and gsm has a difference in the board. Which our phones really are not all that common to the gsm.
Though the difference between a gsm and cdma kernel source isn't all that different. Just stuff missing in the gsm source. I believe the gsm source could be used if we port the cdma stuff up to froyo (Not even sure that would be needed) the port the cdma stuff over to the gsm stuff.
Now I was going to try to do that if it was possible. But I don't understand it really all that much. I can tweak the kernel source, build source and tweak, port roms and look at the main differences in stuff. When you ask for some help you either get confronted by a why or the dev you pm ignores you. I believe I have pm'd nearly every gsm dev to the point of having a ? with doing a kernel or porting something. The only one I ever got a reply from was benne. Now the ones with other devices seem to be willing to help though.
Which takes me to have sense hd. I have it all ported, setup what I believe to be correct. Where it starts to boot and freezes at a couple .jar files saying they can't be found when they are in the sense hd rom any way. Have yet to figure that one out.
Though thinking logical why waist time porting the sense froyo kernel when we should have the source? Every other phone has the source code after every update. I was told I would get it no later than a 120 days I think it was. Then they weren't in a gpl bind as android was w/e it is. I think it has been 6 months no with out the source. Where they are in violation of gpl as the android kernel is a linux kernel under gpl.
With that said if you search on here other devices got the same reply's to e-mails some of us have got. Which they got in no later than a month by doing constant e-mail's from people. They posted a generic type e-mail to send demanding the kernel source. Which is all it would take. This is honestly what I recommend to do since you will have issues starting out porting it. When you could start with something that works like it should.
Edit: Also the desire never got a official gingerbread sense. They got a leak which as I am aware all the gingerbread roms still use the stock kernel that was leaked with it. If it is using a different one I am guessing it was ported. Which leads to the other thing. Porting a gsm rom to cdma most will work but you will get force closes on some things. This is likely due to stuff in the frameworks for the cdma that is missing. I haven't looked into it much in all honesty. As sense is a different animal then aosp.
With that said though uscc said one update per device. Where my leak inside uscc said no gingerbread a month ago. Where uscc I figure would be the first to get it. So if we done get it. It would depend on the other carriers. If they don't I doubt we see it.
Jereso said:
Correct. We want a Froyo or Gingerbread Kernel.
Click to expand...
Click to collapse
Ok this is the first warning before contacting a admin. You never contacted me to use my clockworkmod files. Let alone ask to host them yourself. Heck you never even gave credit for the files. You also never contacted lohp75 to use the pb99img.zip on top of it.
Being it is known that myself or weasel compiles the cwm files. I had a feeling you jacked them off my forum with out permission. My forum is open pubicly for people to stop in and download w/e. This doesn't me take the gift of getting something for free. Upload it to a different host and claim it as your own.
A little hint what do you think the 2fs after the clockworkmod is for? Sure isn't for looks.
So since you never contacted me to re host them or use in your guide. You will not have my permission to have them in your guide. You also jacked all the info in this guide from other guides and posts with out giving credit. Thanks for trying to take credit for nothing you did
Official gingerbread update?
HTC released the official gingerbread update for the Desire recently.
Is that only for GSM? Is there a way to get it on our cdma phone. I currently have CM7, but I miss sense.
Maybe someone made a rom that's basically the official Desire gingerbread, but works on the CDMA Desire?
Thanks
2fast4u88 said:
Ok this is the first warning before contacting a admin. You never contacted me to use my clockworkmod files. Let alone ask to host them yourself. Heck you never even gave credit for the files. You also never contacted lohp75 to use the pb99img.zip on top of it.
Being it is known that myself or weasel compiles the cwm files. I had a feeling you jacked them off my forum with out permission. My forum is open pubicly for people to stop in and download w/e. This doesn't me take the gift of getting something for free. Upload it to a different host and claim it as your own.
A little hint what do you think the 2fs after the clockworkmod is for? Sure isn't for looks.
So since you never contacted me to re host them or use in your guide. You will not have my permission to have them in your guide. You also jacked all the info in this guide from other guides and posts with out giving credit. Thanks for trying to take credit for nothing you did
Click to expand...
Click to collapse
Koush is the maintainer of CWM, and personally I would appreciate it if you didn't put "2fs" after the version because it looks silly and nobody really gives a hoot who compiled it.
Zhenya13 said:
HTC released the official gingerbread update for the Desire recently.
Is that only for GSM? Is there a way to get it on our cdma phone. I currently have CM7, but I miss sense.
Maybe someone made a rom that's basically the official Desire gingerbread, but works on the CDMA Desire?
Thanks
Click to expand...
Click to collapse
No there's no official CDMA Gingerbread kernel. There is a Sense 2.0 ROM testing right now from 2fast4u88.
I have managed to compile (from source) and install CM7.2 on my HTC dream, but my questions below are related to Android:
1. Is there a way to find out which packages (.apk) were installed on my system and if so, how do I do that?
2. Is there a way to find out each package dependencies (I need to figure out this as I am bent on removing the vast amount of guff installed on the phone - I won't need 90% of this stuff)?
3. Similarly to 2 above - is there a way to look at dependencies of a package not yet installed on my system (i.e. the .apk file)?
4. How do I actually remove a package for good from the system?
5. Similarly to 3 above, how do I actually install a package from within the root system - I know I can do this via adb, but is there a way to do this inside the, say, command line terminal?
6. Is there a way to alter (understand remove) certain program permissions which I could see "granted" to a particular program/package? I know there are various ways to look at these, but I wish to remove permissions I am not happy being granted to that particular program/package.
And one last a bit more advanced query: I would like to build a single package from the source tree and then install the resulting .apk file on my system.
Basically, I will try to upgrade a package with a new revision and add a few patches to the package source of my own before compiling it and building it again.
I usually build the whole lot (all packages + the rootfs image itself) with "mke bacon", but if I want to alter the source and build a single package how do I do that?
I am not very familiar with the Android make system, so I don't want to go heads-first into something and make a real mess of it.
Thanks a lot for any assistance given.
Small addition as apparently I cannot post a reply (too few posts) in this thread: http://forum.xda-developers.com/showthread.php?p=9055790#post9055790
Question to ezTerry (if he is reading this!): the advice given in that post above was absolutely splendid! I followed it religiously and it worked an absolute treat!
There is one exception though - I've LOST all of my IMEI, IMEI SV and Baseband information after applying these fixes. As soon as I installed the radio updates and then installed my newly-compiled kernel + CM7.2 (successfully!) I then checked the above fields from Settings and they were all gone!
After a while, the baseband, IMEI and IMEI SV appeared, but the IMEI and IMEI SV stuff have now different values than what I've had previously (I've had T-Mobile IMEI, now it appears that I was "assigned" O2 IMEI & IMEI SV values - very bizarre!).
Is this something I need worry about and (I don't yet have a sim card, but I plan to get one soon after I fix my phone), more importantly, how the hell do these IMEI numbers appeared on my phone - where did they came from?!
josh36 said:
Small addition as apparently I cannot post a reply (too few posts) in this thread: http://forum.xda-developers.com/showthread.php?p=9055790#post9055790
Question to ezTerry (if he is reading this!): the advice given in that post above was absolutely splendid! I followed it religiously and it worked an absolute treat!
There is one exception though - I've LOST all of my IMEI, IMEI SV and Baseband information after applying these fixes. As soon as I installed the radio updates and then installed my newly-compiled kernel + CM7.2 (successfully!) I then checked the above fields from Settings and they were all gone!
After a while, the baseband, IMEI and IMEI SV appeared, but the IMEI and IMEI SV stuff have now different values than what I've had previously (I've had T-Mobile IMEI, now it appears that I was "assigned" O2 IMEI & IMEI SV values - very bizarre!).
Is this something I need worry about and (I don't yet have a sim card, but I plan to get one soon after I fix my phone), more importantly, how the hell do these IMEI numbers appeared on my phone - where did they came from?!
Click to expand...
Click to collapse
Any takers?
@1 Check out the respective directories, i.e. for system apps /system/app
@2 Trial and Error, or someone might have made such a list for your device already
@3 No simple way, you would have to look through the decompiled code i guess
@4 Remove the apk from the folder (for example /system/app) and reboot your device, after wards you might have to clean up some extra folders, i.e. settings of that app. (you can use SD Maid from my signature for that)
@5 Some can just be installed the usual way, by opening it. Some .apk files have to be put in the system folders, afterswards reboot and the app should be "installed". To put those apps there use a rootcapable file explorer of your choice. To edit /system you will need to remount it as it is read only by default, you can do that through command line, but most good file explorers have an option for that.
@6 Yes thats possible, there was an app to do that, just not sure what it was called... It is very likely though, that those apps will not work correctly or just FC.
For the make system, if you just change a package, and build again, it will most likely just rebuild the changed files. I'm not so sure either though... damn make system can be pretty messy... and get upset real fast if you change something ;-).
Dark3n said:
@1 Check out the respective directories, i.e. for system apps /system/app
Click to expand...
Click to collapse
Yep, that indeed helped - I didn't realise that the .apk files are "intact" and do not behave in the "standard" (in Linux terms) way a "package" behaves - the app is "installed" as soon as .apk is placed in /data/app or /system/app. The PacketManager does the rest on reboot.
It also cleans up the mess "automagically" if I delete .apk file and reboot, which is nice.
Dark3n said:
@2 Trial and Error, or someone might have made such a list for your device already
Click to expand...
Click to collapse
Yeah, that's a real bugger - I can't see a way of finding the dependencies, but I haven't looked properly at "pm" (the Package Manager command line tool) - maybe I could use something there.
Dark3n said:
@6 Yes thats possible, there was an app to do that, just not sure what it was called... It is very likely though, that those apps will not work correctly or just FC.
Click to expand...
Click to collapse
A very simple example will issustrate my point - my calendar application is installed and needs some sort of GOOGLE_MAIL and access to the internet permissions, neither of which I am happy to grant, because 1) I won't be using online calendars; and 2) I won't use (google) mail.
The truth is, I deliberately did not install any google apps as I won't be using any of them - ever!
Now, every time I boot up and look at my log files with logcat I see a bunch of error messages that this application (the calendar) needs a bunch of permissions which do not exist (naturally, as I haven't installed a single google app on my phone).
So, I wish to wipe out these permissions from the calendar so that logcat is not filled with junk every time I start my phone.
As I already pointed out above, there are also some installed apps who are listed to "need" permissions I am not happy to grant - like the internet access to calendar for example (there are more apps, but I think you get the point).
Dark3n said:
For the make system, if you just change a package, and build again, it will most likely just rebuild the changed files. I'm not so sure either though... damn make system can be pretty messy... and get upset real fast if you change something ;-).
Click to expand...
Click to collapse
Yeah, that was my plan B - there must be another - easier - way though.
I wish to update a lot of stuff (I will be recompiling/refreshing existing packages as well as adding new things I developed for "standard" Linux), but with this Android make system I am blind - it is very different to what I am used to in the Linux world.
To top it all off, I can't post in any of the devs forums yet as I do not have 10 posts!
Further to my previous post - I just found out a superb article about stripping out Android and removing unnecessary packages from it - http://wiki.cyanogenmod.com/wiki/Barebones
It lists various dependencies and shows what could be deleted and what cannot be - what I wanted really.
My only remaining problem - at least for now - is the making of specific packages without building the whole image.
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!