[Q] Just installed prime. It looks the same? - Eee Pad Transformer Q&A, Help & Troubleshooting

I had my tablet set up a certain way, etc..
I went ahead and installed prime and the OC kernel.
I go ahead and boot it up and it came up looking the same as before. I do have the Prime kernel in the settings section and I was able to OC it.
So I assume that I dont have to worry anymore about the whole rom being replaced now?

your question is a bit vague.
are you asking if you will lose your data if you install new roms? no you will not lose you data.
unless the rom installation instructs you to do a factory reset, you'll typically end up with your data intact. (this includes your user data, user apps, and desktops,etc)

Well, what I mean is I expected to lose all of the data, apps, desktop etc.
And it looked exactly the same as before.
I guess I just wanted to make sure that I did it correctly and the result is correct..

if you didn't wipe anything you don't lose anything so it would look the same yes

if you want it to 'look' different then you have to theme it.
custom ROMs mostly change how the rom works with custom modified files and different versions of system files.
ROM modder usually don't change the UI components unless it is something useful

I would have thought that Flashing a custom ROM would wipe whatever you had installed before completely.
When I flash my phone there is nothing left from the previous install.

magicdave26 said:
I would have thought that Flashing a custom ROM would wipe whatever you had installed before completely.
When I flash my phone there is nothing left from the previous install.
Click to expand...
Click to collapse
If you don't wipe data you don't loose anything. its important to wipe just in case a setting is not compatible with something on the new rom. With that said since all these rom still all base on the stock rom you might get away with flashing and no wipe, not recommended.
Now on a phone where its truly custom and stuffs get ported, full wipe is a must going from one rom to another.

magicdave26 said:
I would have thought that Flashing a custom ROM would wipe whatever you had installed before completely.
When I flash my phone there is nothing left from the previous install.
Click to expand...
Click to collapse
Everything a ROM does on installation is up to the dev. They choose whether the script will format system and data partitions or not. Phone devs add the formatting in the scripts because phones constantly have new bases and ports, and people are typically too dumb to understand the concept of "always wipe". With these tablets, there are no ports and very few ROM bases, so wipes are not really required since most people are flashing different ROMs that are based off the same version stock ROM.

Related

[Q] A Couple (Possibly) Simple Questions

OK. So I bought this tablet the other day at a local Best Buy, and so far I am loving it. Already have it rooted and have a custom ROM installed. However, I have a couple questions that are pretty simple, but I just want to make sure before I screw it up.
1) What is the proper way to flash a rom on this tablet? I know on my phone, I have to first wipe data, then format /system, and then format /boot. I am not sure if doing the same method would be safe on this tablet or not, and I don't want to brick it by accident.
2) What is the best kernel? I am using Revolver's ROM, and am currently using the Prime OC kernel, but have also used the Blades kernel pandatest @ 1.5GHz. I tried to push it to a little over 1.6GHz on the Blades kernel and got some stability issues.
That's pretty much all I really need to know about this tablet. So far I am loving it, and won't part with it anytime soon. Thanks again for reading.
Some roms have a script that you download then flash. This script will wipe everything in your internal memory (and external I believe). Then after flashing this, you go and flash the rom you want.
Other Roms simply have you wipe data/cache just like on a phone, then flash the Rom.
I guess it depends on the developers themselves, so look at the instructions on their page.
I have found the Prime OC kernal to be the one I liked the most. Very stable, and good battery life. Also very stable at 1.4-1.5GHz
You really shouldn't have any reason to go higher then that to be honest.
somethinamazinn said:
Some roms have a script that you download then flash. This script will wipe everything in your internal memory (and external I believe). Then after flashing this, you go and flash the rom you want.
Other Roms simply have you wipe data/cache just like on a phone, then flash the Rom.
I guess it depends on the developers themselves, so look at the instructions on their page.
Click to expand...
Click to collapse
I was just wondering if I go into the recovery, go into mounts and storage, and format the system and data from that, if it could damage anything crucial like the bootloader or anything. I just don't want to end up bricking, but I also want to make sure I am doing a proper full wipe when installing a new ROM.
somethinamazinn said:
I have found the Prime OC kernal to be the one I liked the most. Very stable, and good battery life. Also very stable at 1.4-1.5GHz
You really shouldn't have any reason to go higher then that to be honest.
Click to expand...
Click to collapse
I will probably stick with Prime. Seems to run the best so far.
Thanks for the reply!
stompysan said:
I was just wondering if I go into the recovery, go into mounts and storage, and format the system and data from that, if it could damage anything crucial like the bootloader or anything. I just don't want to end up bricking, but I also want to make sure I am doing a proper full wipe when installing a new ROM.
I will probably stick with Prime. Seems to run the best so far.
Thanks for the reply!
Click to expand...
Click to collapse
Do not format System ever. When installing roms it will do that for you. Data is fine to format. If you are having problems with a rom you Factory reset which wipes data then wipe the cache partition.
mrevankyle said:
Do not format System ever. When installing roms it will do that for you. Data is fine to format. If you are having problems with a rom you Factory reset which wipes data then wipe the cache partition.
Click to expand...
Click to collapse
OK. That's what I was wondering. I know on my Nexus S 4G, a full wipe makes you wipe system as well. I wasn't sure if that was safe to do on this tablet.

[Q] Best Nexus S GSM Rom.

Hi, I'm new to the forum, so please excuse any stupidity on my behalf.
I have a Australian, vodafone GSM Nexus S, currently running 4.0.3.
I am currently feeling stock android to be very limited, and want to move a custom rom, but I have never done any rooting/modding before. So just a couple of questions.
1) How do you root and install a custom rom? Does anybody have any video (I prefer video as I am less prone to making mistakes) tutorials for rooting and installing a custom rom for Nexus S GSM ICS 4.0.3?
2) What is the best rom, kernal etc, as I want to get my phone as smooth as ios or pretty dam close to it. Also I like changing customizing home screens, etc and would also like on screen buttons. Also I would like it to be very very stable.
3) Would it be possible to reverse all this in case my nexus screws up as the sides of my nexus are kinda creaky, and though this doesn't really effect my usability, I might end up rma'ing my phone in the future, so I would like to be able to reverse all this so it doesn't void my warranty.
4) Is there any point is overclocking and undervolting a phone. My PC is overclocked, but I have a huge fan, so overclocking would mean more heat + more battery use, and on the other hand you are lowering the voltage. Wouldn't this be very unstable?
This is my first post, so I apologize for anything I did wrong, and I did try searching, but all the roms look very good, there are some very talented devs here, and I say thanks for the help in advance.
Cheers,
Continuum
EDIT: INSTRUCTIONS ON HOW TO UNLOCK BOOTLOADER + INSTALL CLOCKWORK RECOVERY TOUCH
1. Download the CyberGR-MOD|NS.NGN ICS v8 HYBRID
http://clockworkmod.com/rommanager/d...le Nexus S
Why Cyber, seems fast, stable, and is not a beta.
2. Download and install the windows drivers for my phone (I'm on windows 7)
http://downloadandroidrom.com/file/N...ussrootICS.zip
3. Follow these until step 7
http://nexusshacks.com/nexus-s-root/...r-gingerbread/
n.b: don't worry about the cd \nexussrootthing. Just go to that folder, shift + right click, and click start command prompt instead.
4. Download clockwork recovery touch
(Link: http://downloadandroidrom.com/file/N...overytouch.zip )
and follow these instructions:
http://nexusshacks.com/nexus-s-hacks...or-nexus-s-4g/
5. Go into clockwork recovery (while still plugged into pc) and perform a nandroid back up
and click the following after:
data/factory reset
under mount and boot
format /boot
format /system
Next mount usb, and copy CyberGR-MOD|NS.NGN ICS v8 HYBRID over to sdcard, and unmount USB.
6. Plug out cable, and flash rom by going into clockwork recovery and clicking install zip from sdcard, to flash rom
7. Reboot phone and enjoy
1. NexusSHacks.com has a video tutorial on how to unlock your bootloader and Root the phone. Rooting won't be necessary to go to a custom ROM, but unlocking the bootloader is highly recommended for doing so. You will lose all personal data (including from internal SD card) once you unlock.
2. Best ROM and Kernel are the ones that fit your needs. Try a few of them, you'll find a sweet spot somewhere. The Nexus S has some of the (if not THE) best ROMs and kernels of any android, in quality, features, speed and stability.
3. All reversible from a software side. Hardware issues are covered for 1 year under warranty even if you've rooted it, technically. You can lock the bootloader and flash a stock ROM very easily.
4. Overclocking can give a significant performance increase at the cost of battery life and possibly stability. Undervolting uses very slightly less power, but generally not significant enough to notice, especially with the instability risk (rebooting will use far more power than undervolting will save you). Some chips are made more perfect than others, so some can handle high OC and extreme UV, some gag at the thought of 25mV less.
Also, remember to do a backup via recovery (NANDROID backup) when you want to try something new and when you are happy and stable with a ROM/Kernel/Settings combo. This can save lots of wasted time
Hi Harbb, thanks for the reply.
1. Sorry new to xda so couldn't link url, but I think I got it thanks, and I found one for unrooting. But how do you install a custom rom without rooting?
2. Well I was looking into roms, and codename looks good but does not come with Gapps. CM9 also looks good, but still in beta, I think I'll wait for the final release of CM9. Got any specific ones you like? Also what is the point in changing kernel?
3. Since there is a vodafone flag under your name I presume you work for voda aus? So do I have to flash it back to stock to rma it, or can I just give it in, rooted + custom rom, and expect them to replace it for me granted the phone is still <1yr, and if it is not, I guess it costs a bit to fix it.
4. But wouldn't overclocking cause your phone to overheat. Sometimes my stock nexus is sunning really hot, and other times the screen is not responsive, and I presume overclocking will just add to that. I see undervolting as a benefit, but you could just configure your phone to go into aeroplane mode/turn of 3g/etc using timerifficor tasker if battery is an issue.
Thanks for the help, but whats a NANDROID backup. Also, isn't there another one called titanium or something?
Cheers,
continuum
Nandroid is a backup you make in ClockworkMod Recovery.
Titanium Backup is a backup of all your apps (+ data).
1. Once you have an unlocked bootloader, you are given permission to use "fastboot" to flash a custom recovery. The custom recovery has, practically, full access to the rest of the system (which is essentially what root/su is). From the new custom recovery you can flash the .zip file which is the ROM, or kernel, or backup all of your files that you couldn't even access before, or format several partitions to your liking. Rooting is just copying over the su command so you can have access to the entire system, which you can't have without it.
2. CodeName Android has a seperate gapps .zip file, it's linked in the thread somewhere. Just wipe (a full wipe includes data/factory reset, format /system and format /boot, i recommend doing this between different ROMs), flash the ROM .zip first, then gapps.zip second, then reboot into your new ROM. I really liked stock. Recently i moved to Slim ICS. It's all about preference, features, etc. All of the devs here are great and there is no harm in trying out a handful of ROMs, say for about 2 days each. See which one you feel at home with. Same with kernels. Pick a handful with the features you want and try them for a couple of days.
3. No, I don't work for Vodafone. That just says which carrier I'm with. With regard to warranty, put it this way. Unless you get some serious hardware failure or storage failure, you will be able to put the phone back into the locked and stock state. If the phone just up and dies one day, feel free to send it in as-is and they should sort it out for you as it is a hardware problem. This -could- be due to overclocking, and they can argue it, but i can't recall anyone having issues like that so nothing to stress about, just don't abuse your phone. Otherwise, you can usually be able to bring it back to a locked state and in this case i would do that just in case. You can find the warranty policy here. It's quite broad, but so long as it's a manufacturing problem it is clearly covered.
4. Possibly, yes. As i said before, different CPUs are better in general than others due to variances in manufacturing. Lowering voltage may lower temperatures too, so if it is stable this could be an upside to UVing. It's all about being stable though, if your phone can't handle 1200mhz, don't OC it. If it is and you are happy with the battery life and possible lessened lifetime of the phone while stable, go right ahead. Generally no harm in trying, just go up (or down) incrementally. I'll note that while not in use, the phone should be in "Deep Sleep", which completely shuts off nearly all components of the phone aside from the radio (for cellular reception). Undervolting or Overclocking has no effect whatsoever here.
Icecoldmeat said:
Nandroid is a backup you make in ClockworkMod Recovery.
Titanium Backup is a backup of all your apps (+ data).
Click to expand...
Click to collapse
Cheers, so basically its like a windows recovery image. But for the nexus s 19203 (I think, its the slcd one), nexus hacks is saying to use TWRP. Can you still do nandroid backup with that?
Harbb said:
1. Once you have an unlocked bootloader, you are given permission to use "fastboot" to flash a custom recovery. The custom recovery has, practically, full access to the rest of the system (which is essentially what root/su is). From the new custom recovery you can flash the .zip file which is the ROM, or kernel, or backup all of your files that you couldn't even access before, or format several partitions to your liking. Rooting is just copying over the su command so you can have access to the entire system, which you can't have without it.
Click to expand...
Click to collapse
So for a beginner, your suggesting it would be easier to unlock the bootloader, and load a custom rom with root already incuded, such as CM9, right?
Harbb said:
2. CodeName Android has a seperate gapps .zip file, it's linked in the thread somewhere. Just wipe (a full wipe includes data/factory reset, format /system and format /boot, i recommend doing this between different ROMs), flash the ROM .zip first, then gapps.zip second, then reboot into your new ROM. I really liked stock. Recently i moved to Slim ICS. It's all about preference, features, etc. All of the devs here are great and there is no harm in trying out a handful of ROMs, say for about 2 days each. See which one you feel at home with. Same with kernels. Pick a handful with the features you want and try them for a couple of days.
Click to expand...
Click to collapse
So essentially:
1. Find a rom, and the drivers for my device, store these on my pc
2. Wipe phone (I presume by going into settings and pressing factory reset? and then wiping everything)
3. Turn off phone
4. Follow the nexusshacks to fastboot oem unlock and TWRP recovery
5. Nandroid backup??
6. Flash the rom
7. Flash Gapps
8. Reboot, disconnect from pc, and then let everything initialize.
9. Enjoy
Harbb said:
3. No, I don't work for Vodafone. That just says which carrier I'm with. With regard to warranty, put it this way. Unless you get some serious hardware failure or storage failure, you will be able to put the phone back into the locked and stock state. If the phone just up and dies one day, feel free to send it in as-is and they should sort it out for you as it is a hardware problem. This -could- be due to overclocking, and they can argue it, but i can't recall anyone having issues like that so nothing to stress about, just don't abuse your phone. Otherwise, you can usually be able to bring it back to a locked state and in this case i would do that just in case. You can find the warranty policy. It's quite broad, but so long as it's a manufacturing problem it is clearly covered.
Click to expand...
Click to collapse
Ahh, my bad, new to this forum, and though you were a voda rep
So I guess as long as your not extreme overvolting, you'll be fine.
Harbb said:
4. Possibly, yes. As i said before, different CPUs are better in general than others due to variances in manufacturing. Lowering voltage may lower temperatures too, so if it is stable this could be an upside to UVing. It's all about being stable though, if your phone can't handle 1200mhz, don't OC it. If it is and you are happy with the battery life and possible lessened lifetime of the phone while stable, go right ahead. Generally no harm in trying, just go up (or down) incrementally. I'll note that while not in use, the phone should be in "Deep Sleep", which completely shuts off nearly all components of the phone aside from the radio (for cellular reception). Undervolting or Overclocking has no effect whatsoever here.
Click to expand...
Click to collapse
I'll try mucking about eventually, but am a bit scared about heat build up.
Also, any word on when the full CM9 will come out?
I believe the initial estimation was around march, and by how early CM9 ROMs are going i tend to believe them. Likely more toward the end, though, before a stable is released.
A NANDROID backup basically copies: /system, /boot, /data, /cache, the recovery, kernel and .android_secure (on the sdcard). Pretty much everything android on your phone is backed up and you can go back to that exact state anytime you want by restoring, or restore each one individually. I personally recommend the ClockWorkMod, TWRP isn't in development anymore and CWM now has a touch version too, though i still prefer the non-touch myself. Just make sure to get the latest version from here.
You can feel when the phone gets hot as long as you don't have a full cover, and some apps can tell you what the battery temperature is too. Stick to what is comfortable for you. Don't be worried though, you can always just clock it back to stock speeds and volts.
Harbb said:
I personally recommend the ClockWorkMod, TWRP isn't in development anymore and CWM now has a touch version too, though i still prefer the non-touch myself. Just make sure to get the latest version from here[/URL].
Click to expand...
Click to collapse
Ok, so this is what I am going to do:
1. Download the CyberGR-MOD|NS.NGN ICS v8 HYBRID, from the link you gave me, I presume this works for i9023
2. Download and install the windows drivers for my phone
3. Root my phone, with TWRP, according to that method shown by nexusshacks
4. Then install clockwork recovery touch using fastboot flash recovery ,also shown by nexus s hacks
5. Preform a nandroid back up ?? not sure how to do this
6. Flash rom ?? not sure how to do this either
7. Reboot phone and enjoy
I am presuming Gapps in included with the rom.
Please correct anything wrong, and also, how do I get onscreen buttons? The code name rom looks like it comes with them.
!!!
I recommend you to use the latest CyanogenMod Nightlie (it's already smooth and stable enough) and some great custom kernel: AirKernel of Matrix kernel
novic_dev said:
I recommend you to use the latest CyanogenMod Nightlie (it's already smooth and stable enough) and some great custom kernel: AirKernel of Matrix kernel
Click to expand...
Click to collapse
Cool, but would I have to do the whole process all over again, once the final CM9 comes out, and does it update automatically, or must you update manually?
No need for twrp, you can flash cwm straight away. Before unlocking remember to backup all your data that you can (you will lose save games and app settings). Make sure to do the wipes I told you about or your phone may not boot or be very unstable. Copy the from .zip to sdcard and while in recovery choose to install a .zip and choose which one. It's quite simple, I'm sure you'll figure it out. Backing up is done by clicking backup of course.
There is a thread in development dedicated to onscreen buttons, that might be of use. I haven't tried it before.
Harbb said:
No need for twrp, you can flash cwm straight away. Before unlocking remember to backup all your data that you can (you will lose save games and app settings). Make sure to do the wipes I told you about or your phone may not boot or be very unstable. Copy the from .zip to sdcard and while in recovery choose to install a .zip and choose which one. It's quite simple, I'm sure you'll figure it out. Backing up is done by clicking backup of course.
Click to expand...
Click to collapse
Well I don't have much data on there, so I'm just going to copy a couple of photo's, and then factory reset, but I thought to flash cwm you have to have root first? My nexus is just pure, stock.
Harbb said:
There is a thread in development dedicated to onscreen buttons, that might be of use. I haven't tried it before.
Click to expand...
Click to collapse
Thanks, but I can't post there yet.
http://[www].androidegis.com/how-to/now-root-your-nexus-s-in-one-click-root-method/ Is this any good?
Unsure if that one still works for ICS, possibly not. There are other methods to root 4.0.3 though without unlocking the bootloader, but it often makes it much harder to do some things. Since we don't get scalded for unlocking the bootloader (and it can be undone, AND it's easy), it is the best and preferred way by most accounts. It saves alot of hassle and we are free to use fastboot if anything goes awry. Much better than needing to do that rooting procedure again, then flashing recovery within android, etc. Since you have nothing on your phone, definitely just unlock the bootloader. Nothing like freedom
Unlocking the bootloader allows you to use fastboot, as i said. fastboot allows you to flash a custom recovery (and boot with a custom kernel, and some other less-used things). TWRP and CWM are both custom recoveries, so as long as you can use fastboot (via "fastboot flash recovery recovery.img") you can replace recovery.img with twrp.img, cwm.img and so on. Same process, different file.
I'll give you another hint since you'll probably run into this eventually: Stock recovery has an android and exclamation (!) mark as a splash screen. You have to press a volume key and power button to go through that splash screen. The main time you'll see this is if you flash an official Stock ROM. There is a script that reinstalls the stock recovery on boot in Stock ROMs. To get rid of it, you'll need to rename the file /system/etc/install-recovery.sh to something else (like install-recovery.sh.bak), or just delete it. You need su to do this, of course.
Harbb,
is it "OK" before reverting to a previous NANDROID backup in CWM recovery to do format system/boot/data/cache/dalvik and factory defaults ? or not or harmful ?
What is the word on that ?
Alright, thanks guys, I will try this soon.
mahanddeem said:
Harbb,
is it "OK" before reverting to a previous NANDROID backup in CWM recovery to do format system/boot/data/cache/dalvik and factory defaults ? or not or harmful ?
What is the word on that ?
Click to expand...
Click to collapse
No need to, it is done automatically before restoring. Essentially it doesn't make a difference either way.
continuum51 said:
Alright, thanks guys, I will try this soon.
Click to expand...
Click to collapse
You're welcome, it'll all make alot more sense once you're doing it.
Ok guy, about to do it now. These are the steps I'm taking,
1. Download the CyberGR-MOD|NS.NGN ICS v8 HYBRID
http://clockworkmod.com/rommanager/...CyberGR-MOD|NS-NGN.&deviceName=Google Nexus S
Why Cyber, seems fast, stable, and is not a beta. Only question is how are updates going to work?
2. Download and install the windows drivers for my phone (I'm on windows 7)
http://downloadandroidrom.com/file/NexusS/rooting/nexussrootICS.zip
3. Follow these until step 7
http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/
4. Then install clockwork recovery touch (Link: http://downloadandroidrom.com/file/NexusS/cwm/nexussrecoverytouch.zip)
and follow these instructions:
http://nexusshacks.com/nexus-s-hack...orkmod-touch-on-rooted-nexus-s-or-nexus-s-4g/
5. Preform a nandroid back up, I'm guessing this is a part of clockwork recovery, and click the following after:
data/factory reset
format /boot
format /system
From advanced, click reboot recovery, and wipe data/factory reset & cache again.
Next, storage select, format /system /data /cache /boot & format /sdcard, mount usb, and copy CyberGR-MOD|NS.NGN ICS v8 HYBRID over to sdcard.
6. Plug out cable, and lash rom by going into clockwork recovery and clicking install zip from sdcard, top flash rom
7. Reboot phone and enjoy
Before I go ahead, if something screws up, and the phone completely dies (software side), is there a way to force it back to stock? And are these steps correct?
continuum51 said:
Ok guy, about to do it now. These are the steps I'm taking,
1. Download the CyberGR-MOD|NS.NGN ICS v8 HYBRID
http://clockworkmod.com/rommanager/...CyberGR-MOD|NS-NGN.&deviceName=Google Nexus S
Why Cyber, seems fast, stable, and is not a beta. Only question is how are updates going to work?
2. Download and install the windows drivers for my phone (I'm on windows 7)
http://downloadandroidrom.com/file/NexusS/rooting/nexussrootICS.zip
3. Follow these until step 7
http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/
4. Then install clockwork recovery touch (Link: http://downloadandroidrom.com/file/NexusS/cwm/nexussrecoverytouch.zip)
and follow these instructions:
http://nexusshacks.com/nexus-s-hack...orkmod-touch-on-rooted-nexus-s-or-nexus-s-4g/
5. Preform a nandroid back up, I'm guessing this is a part of clockwork recovery, and click the following after:
wipe data/factory reset
wipe/cache partition
And download the following Dalvik-wiper.zip, and wipe Cache. ?? for this, do I put it on phone sd card?
From advanced, click reboot recovery, and wipe data/factory reset & cache again.
Next, storage select, format /system /data /cache /boot & format /sdcard, mount usb, and copy CyberGR-MOD|NS.NGN ICS v8 HYBRID over to sdcard.
6. Plug out cable, and lash rom by going into clockwork recovery and clicking install zip from sdcard, top flash rom
7. Reboot phone and enjoy
Before I go ahead, if something screws up, and the phone completely dies (software side), is there a way to force it back to stock? And are these steps correct?
Click to expand...
Click to collapse
Data/factory reset also formats /cache. For a full wipe: data/factory reset, format /boot, format /system. No need to worry about any wiping .zips. No reason to do it twice either, but if you really want peace of mind do as you wish. This is ALL you need to do for wiping.
They are correct, but also somewhat redundant. Follow my wiping directions and you will be perfectly fine. If you ever want to flash a new kernel, you only need to wipe dalvik cache prior to flashing it.
Thanks mate. I've edited step 5, and am doing it now.
As i said too, no need to do the wiping again as you have at the bottom of step 5. Also note that data/factory reset formats /data, /cache and .android_secure (on sdcard), so doing the separate formats is essentially the same as doing the data/factory reset.
There is a sticky at the top of the general section with all of the stock OTA ROMs (Full and Update ones). Just wipe and flash one of the Full ROMs and you'll be back to stock in no time.

"Can't Connect to Camera" on AOSP only

As the title states, I can't get my camera to run on any AOSP ROMs. Camera works fine as soon as I switch to something TW based, but breaks as soon as I load anything AOSP.
I've searched everywhere I can think for this issue and have tried solutions that have worked for others but with no success. I've tried flashing back to stock unrooted, then rooting and starting all over again. I've tried copying cameradata files from TW based to AOSP (in several variations). I've tried reflashing (and I've done nothing but clean flashes each time I'm flashing anything). If it matters, my normal method is to wipe data/factory reset, then clear cache and dalvik, then install ROM + gapps, and then reboot.
I'm using CWM touch recovery v6.0.2.3, firmware VRBMF1 (and one or two others), and have tried leankernel in addition to stock kernels.
It may be worth mentioning that this is a refurbished device and I used Casual's One Click Root, whereas previously (Jan 2013) I rooted the long way and had no issues with anything really.
I had this problem for months. I did a clean install and it fix the problem. Try doing that and it might work for you too.
What do you mean by clean install?
Gigatrig said:
What do you mean by clean install?
Click to expand...
Click to collapse
He's probably meaning to wipe everything in CWM. Data, system, sdcard, etc. Pretty much everything and you'll probably fix your problem. Maybe even flashing latest firmware again wouldn't hurt.
Sent from my SCH-I535 using xda app-developers app
kude87 said:
He's probably meaning to wipe everything in CWM. Data, system, sdcard, etc. Pretty much everything and you'll probably fix your problem. Maybe even flashing latest firmware again wouldn't hurt
Click to expand...
Click to collapse
Do you mean in the "mounts and storage" menu? Use format /system... /data... /sdcard? I think that's what you mean, but I've not had to use those before, so I wanna make sure.
Thanks
:laugh:
Gigatrig said:
As the title states, I can't get my camera to run on any AOSP ROMs. Camera works fine as soon as I switch to something TW based, but breaks as soon as I load anything AOSP.
I've searched everywhere I can think for this issue and have tried solutions that have worked for others but with no success. I've tried flashing back to stock unrooted, then rooting and starting all over again. I've tried copying cameradata files from TW based to AOSP (in several variations). I've tried reflashing (and I've done nothing but clean flashes each time I'm flashing anything). If it matters, my normal method is to wipe data/factory reset, then clear cache and dalvik, then install ROM + gapps, and then reboot.
I'm using CWM touch recovery v6.0.2.3, firmware VRBMF1 (and one or two others), and have tried leankernel in addition to stock kernels.
It may be worth mentioning that this is a refurbished device and I used Casual's One Click Root, whereas previously (Jan 2013) I rooted the long way and had no issues with anything really.
Click to expand...
Click to collapse
I had the same problem with my phone, I made a thread a little while ago with what I did. http://forum.xda-developers.com/showthread.php?t=2492304 ask any questions you have on there I want to improve it as this was a very frustrating and time consuming fix for me.

[Q] Wondering what to expect by an overwrite of a ROM?

I was tinkering with my TF101 and sort of accidentally (lol) overwrote my installation of Timduru's KatKiss-4.3.1_029.zip with his KatKiss-4.4.2_016.zip without wiping anything before doing so. (Actually didn't have any data to speak of - as I formatted and wiped in proper fashion on the install of KatKiss-4.3.1_029), and it hadn't been run for more than a couple of days.
I've developed a severe addition to ROM experimentation, and so may install and backup every few days it seems. Don't have a nickname for that habit yet, but I sense that they are many similar addicts around this site.
What I would like to know, since all seems, at least to this n00b, to be just fine - what "might" happen w/ my TF101 since the overwrite of a newer ROM?​
Staying put, until I hear from a forum guru, or at least anyone with more experience than me (and that will include most all members).
Thanks,
Cal
If you overwrite a ROM with a different one (different android version, or by a different developer) you may run into issues where it will not boot, or it may run poorly, random reboots, sleep o death.
When changing ROMs it is HIGHLY recommended to wipe the system, caches and the data partition (wiping data is not the same as FORMAT DATA in TWRP). There are some system settings stored in the /data/ partition that may conflict with different ROMs.
Most of TimDuru's KatKiss ROMs you can forward flash (even to new versions of Android) but you CANNOT go backwards. I flashed from 4.2.2 to 4.3 without wiping data and had no issues. However, if you tried to flash from 4.3 to 4.2.2 without wiping data, it will not boot until you wipe the data partition.
I have not tried this with the 4.4 version of his ROM (I am still on 4.3 for now.)
Oh, and yes, the addiction is called CrackFlashing.
Always ALWAYS make a backup in TWRP before flashing a new ROM or even an upgrade to the current ROM. If you want to go back to 4.3, make a backup and then use Titanium Backup Pro version to extract any apps and data from the 4.4 version and restore to 4.3. Do not restore any system settings or apps.
frederuco said:
<snipped a bit>
When changing ROMs it is HIGHLY recommended to wipe the system, caches and the data partition (wiping data is not the same as FORMAT DATA in TWRP). There are some system settings stored in the /data/ partition that may conflict with different ROMs.
Most of TimDuru's KatKiss ROMs you can forward flash (even to new versions of Android) but you CANNOT go backwards. I flashed from 4.2.2 to 4.3 without wiping data and had no issues. However, if you tried to flash from 4.3 to 4.2.2 without wiping data, it will not boot until you wipe the data partition.
Oh, and yes, the addiction is called CrackFlashing.
Always ALWAYS make a backup in TWRP before flashing a new ROM or even an upgrade to the current ROM. <some stuff snipped>
Click to expand...
Click to collapse
Ahh...then the addiction is obviously not curable unless one destroys the tablet, BUT the new ROM may be just fine as is, I take it. That was what I was hoping to hear.
Thanks, and any idea when a new experimental ROM will come from Tim? Just felt a slight twitch. I've tried the other team's creations and seem to only feel really satisfied with Kits - (guess 'CrackFlashing' addiction picks a really hard one to withdraw from).
Many thanks!
Cal
Cal-123 said:
Ahh...then the addiction is obviously not curable unless one destroys the tablet, BUT the new ROM may be just fine as is, I take it. That was what I was hoping to hear.
Thanks, and any idea when a new experimental ROM will come from Tim? Just felt a slight twitch. I've tried the other team's creations and seem to only feel really satisfied with Kits - (guess 'CrackFlashing' addiction picks a really hard one to withdraw from).
Many thanks!
Cal
Click to expand...
Click to collapse
I think it will be a while until timduru starts to work in a experimental rom , since there is no Android 5 yet.
But Tim has marked katkiss as stable and for my daily use it is. But you could try 4.4.2.
schwigi said:
I think it will be a while until timduru starts to work in a experimental rom , since there is no Android 5 yet.
But Tim has marked katkiss as stable and for my daily use it is. But you could try 4.4.2.
Click to expand...
Click to collapse
Read the original post again -- I've been on the 4.4.2_16 forever now it seems!! The urge to try something new is over-bearing! :silly: :victory:
Ah-Ha! I see that Tim's put up a new 'stable' one. KK 4.4.2_17! Yeah!! This should be a super easy fix for the 'crack-itis' I have developed...as I will overwrite this one also.

Android is starting...

So once in a while i reboot my tablet for optimizing purposes however when it boots up to android is starting.. It reboots again then hangs for a few sec and poof "Android process has stop" then its normal again.
Unlocked: yes
Rooted: yes
custom rom: yes - just the optimized rom with blob(pushed with fastboot)
Kernel: stock
Anything that i did wrong why it reboots again?
Did you flash anything besides the stock optimized(excluding the dtb?) Also do you wipe dalvik cache when you reboot, as I can't figure out why your tablet would be optimizing apps everytime you reboot?
Questions aside I would do a system, data, cache, dalvik cache wipe in your custom recovery and reflash the ROM to see if that fixes things. Just note to backup anything in your internel SD card if you decide to go the full wipe route instead. If you do a full wipe you'll need to flash the ROM from a external SD card or a USB via OTG.
Just a small disclaimer I would note to know what everything is doing before following my suggested potential fix if you choose to go that route. I'm guessing you do but just a friendly safety precaution!
Gapps(open) and the zip for xposed, respectively, thats it. Every week i purposely restart the device so everything is in good condition.
I did that before i installed the rom and etc. All the files where in the SD card am not putting any flashable files in the internal.
Bitcloud30 said:
Gapps(open) and the zip for xposed, respectively, thats it. Every week i purposely restart the device so everything is in good condition.
I did that before i installed the rom and etc. All the files where in the SD card am not putting any flashable files in the internal.
Click to expand...
Click to collapse
So you are using the Optimized Stock ROM from GtrCraft correct? If so I will tell you right now that Gapps does not need to be flashed with that ROM as it comes preloaded with Gapps and that could have possibly caused these errors(Any devs, correct me if I'm wrong here.) I would wipe system in that case, reflash the ROM, SuperSU, Xposed in that order and see if the problems exist. If that doesn't work I suggest doing what I suggested in my first reply. Android OS can go a little haywire over the smallest things and it seems something you flashed caused the problems you are having.
@KentuckyGuy447 will try that very soon! Yes that is the rom that i am using. No doubt about that but it lacks a more information about the rom xD, any how. Thanks for the help . I didnt know that in the first place cuz it didn't say anything about Gapps thats why i DL right away and installed above it.
Bitcloud30 said:
@KentuckyGuy447 will try that very soon! Yes that is the rom that i am using. No doubt about that but it lacks a more information about the rom xD, any how. Thanks for the help . I didnt know that in the first place cuz it didn't say anything about Gapps thats why i DL right away and installed above it.
Click to expand...
Click to collapse
Yeah I understand where your coming from. Just as future reference any ROM over the size of 350mb usually has a lot going on behind the scenes. I would try my suggested fixes and see if they will work. If not just notify us in your thread and I'm sure someone with more knowledge as I will try to help. Have a great day friend!

Categories

Resources