Database Info

A Noob's Guide To Rooting

As is the case with any smartphone, the initial ownership period is always the most exciting one. Your phone is new and you can’t wait to try out all the features it has to offer. After a while, though, you tend to get bored with it and that’s when you start thinking about buying a new one. Unfortunately, what many don’t realise is that at times, manufacturers aren’t able to exploit the phone's true capabilities due to various reasons and one of the best ways to achieve that is by rooting it ( assuming it is an Android Smartphone.
{
"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"
}
What is rooting and why do I need it?
At the core, Android is based on Linux and by default, it gives users only limited access to the system. The permissions are set to give users access to everything they would typically need and restrict them from accidentally modifying any system files or permissions, since a novice user can end up bricking their phone. Rooting your Android phone gives you Superuser access, which is similar to having an Administrator account in Windows. Armed with this, you can now perform system level updates; make changes in the UI through specialized apps; modify protected files, etc. With this you can now use Titanium Backup, which is one of the best backup apps in the Marketplace letting you backup virtually all your settings, data, etc, which otherwise is not possible. Adfree is another very handy app that lets you block ads in any free app you download and since it works at the IP address level, it doesn't slow down the system.
Advantages Of Rooting An Android Device
1. You can use custom ROM's such as CyanogenMod & MIUI.
2. You can overclock the processor to increase performance or underclock it to save battery power.
3. You can delete the carrier added crap-ware, use custom themes.
4. You can obtain SuperUser access.
5. You can backup and restore the whole system.
SuperUser Access Granted
Dis-Advantages Of Rooting An Android Device
1. Your warranty will be in great danger.
2. Security Concerns may occur.
3. You can possibly turn your phone into an expensive paper-weight if you don't know what you're doing i.e. Brick you android device.
Your Phone If You Do Something Wrong
How To Root?
Every android device whether it's a smartphone or tablet, have a different method of rooting. In my personal opinion, there are two applications that can almost root any android device.
Using SuperOneClick - Download
This Windows-based application will root (almost) any Android phone in the market and is a good place to start. It works on Windows Vista and above, and requires you to have .NET Framework 2.0 and above pre-installed. For the full list of supported phones and instructions on how to use this on a Mac or Linux, follow this thread. Once you download and install it, just follow these steps:
Put your phone in Debugging mode - For this, go to Settings > Applications > Development > USB Debugging. Some phones have this placed differently, so if you don’t find it here, just browse though all the sub-menus in settings, you will eventually find it.
Make sure the drivers for your phone are installed - If you received a CD with your phone then install it. If not, then go to the support section of your phones website and download it from there. In case you have a phone from a lower tiered company then chances are you may not find drivers for it. Don’t worry, as OneClickRoot will download generic drivers for your phone.
Plug your phone to the PC via USB cable - Remember, not to “Turn on Mass Storage”, if you get the prompt. Just ignore it.
Run the software and it should now detect your phone. Then you simply click ‘Root’ and wait for it to complete. If Windows can’t detect the drivers for your phone, click the second tab on the program and click “Get Drivers”.
Your phone is now rooted! You’ll now have a new app in your list called ‘Superuser’. All that it does is keep a log of which applications require Superuser access.
The other application is Unlock Root, which works in a similar fashion. So, if for some reason OneClickRoot doesn’t work, you can give this a try.
Now that we have rooted the phone, it’s time to install a custom recovery, so we can install custom ROMs and a lot more.
What is Custom Recovery and why do I need it?
Think of recovery as DOS mode in your PC. You access it to make changes to the system, apply updates, change file partitions, etc, which is normally not possible through the OS itself. All Android devices come with a recovery, but the stock one offers very basic options, which won’t let you install custom ROMs or make any other system level changes. For that, we have a custom recovery and the most popular one is the ClockworkMod Recovery or CWM developed by Koush or Koushik Dutta.
A couple of things you can do with CWM are:
Make, restore and manage backups of your current ROM
Install a custom ROM or flash a kernel from internal storage
Mount, format your phones internal storage partitions
Create logs for error reporting
It’s ok, if you don’t know what some of them are, as you’ll seldom be using them. You can install CWM in different ways, but the simplest is through an app called ‘ROM Manager’. Here’s what you do:
Download ROM Manager from the Android Marketplace
Launch the app and the first option itself should say “Flash ClockworkMod Recovery”. Just press that and follow the instructions onscreen. In case you don’t have enough internal memory, you’ll be prompted to insert an SD card, so do that.
Be patient and let it work its magic. Once it’s done, you now have a custom recovery on your phone.
You can get into recovery mode a number of ways. Some phones have a button combo, which you boot into, but again, the simplest way is through ROM Manager. The second option says ‘Reboot into Recovery’, so just hit that and your phone should boot in to recovery mode.
After a reboot you won’t see the screen above directly, if you boot through ROM Manager (sometimes). Instead, you’ll have an Android logo with an exclamation mark. Don’t be alarmed; simply press the ‘Home’ button or any of the soft keys and you’ll see the main menu. You can scroll through the options using the volume keys and enter them using the ‘Home’ or ‘Power’ button. It’s a bit different for each device, but nothing that you can't figure out on your own. CWM will not work with every device, especially the lower end handsets from Spice, Lava, etc. The reason being they aren’t support by the developers, since they are relatively unheard of. However, almost every phone from a Tier 1 brand are supported.
Congratulations! You now have a rooted phone and a custom recovery installed. Don’t worry about loss of data as both these procedures will not affect any of the settings or data on your phone. The next step? How about installing a custom ROM?
About Custom ROM's, you will find loads of them here........at XDA-Developers
Till then, Stay Cool!

galaxy nexus
Is this the same method for the galaxy nexus?

gnasr74 said:
Is this the same method for the galaxy nexus?
Click to expand...
Click to collapse
Sorry to say, but i don't know anything about galaxy nexus as it is not available in india, in the meanwhile, i suggest you to search in galaxy nexus forum for support.

rooting galaxy s2
hi there,
i am very new to rooting. i own galaxy s2 and wud like to try it. my phone is under contract i.e. donot have a sim card.
so can i still root it??

Can I move apps to sd without root with apps such as facebook?

Actually, I do not think I will root again unless I have a replacement or my phone is two years old, the length of the htc warranty. My phone plays up for absolutely no reason at all and it can't read zip files! If I were I noob I would not root.

Thanks for the tutorial! :good:

rooth
How to one klick rooth Tele2fon V1 (MobiWire Aquila)??Can someone pls help me

Coby Kyros MID7048
I've own Coby Kyrus MID7048 Android 4.0 is this tutorial effective to this unit? I'm begging for HELP

How do you take away root?
Sent from my HTC Explorer A310e using xda app-developers app

Is there possibility that any of this "one-click-root" methods above to make unsolved damage (brick) to device?
Can I return to previous (unrooted) state at later time from already rooted device?

[ROM][06 May 2012] Flytouch 3 Superpad 2 TolgaMOD_FT3_v1.0

Hello,
This ROM is based on Tim6a and www_apad_tv-ibex-Flytouch-3-Firmware-V8.
I started customizing Tim's 6a ROM for my own use, basically since I wanted to see all apps compatible with FT3 on Google Play and I wanted to use ADW Launcher. Now that my customization is complete, I wanted to share it with the xda-developers community
The ROM is built to mimic a Samsung Galaxy GIO device. This device has a much smaller screen but has an ARMv6 processor like the FT3. So all apps downloaded from Google Play should work, and with good performance since it will be the app's QVGA version. Gameloft games also recognize this device, so for example you can download and play Ice Age Village.
Credits go to Tim for his great custom ROM, Apad.tv for firmware-V8, Axlien for the build.prop ideas, chairshot215 for performance tweaks. Thank you guys!
mod edit
I hope you enjoy this release!
Tolga
INSTALLATION:
Unzip the contents of mod edit] to the root folder of your SDcard, and reboot FT3. When the installation is complete, don't forget to take out the SDcard and remove the installation files.
If Wi-fi is grayed out after installation, it means that your wifi card is not 0803 v1. (default) Try enabling old FT3 or 0803 v2 using Tim's scripts in Gscript Lite.
To view all apps on Google Play, follow these steps after installation:
1. Open Google Play, accept the upgrade and accept TOS.
2. Go to Settings>Applications>Manage Applications and select ALL tab.
3. Go to Google Play, clear cache and force stop (DO NOT CLEAR DATA)
4. Go to Google Services framework, clear data and force stop
5. Open Google Play, and you should get a server error. (This is normal)
6. Restart FT3 and all compatible apps should be visible on Google Play!
mod edit
SCREENSHOTS:
{
"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"
}
FEATURES:
ADW Launcher (InfoTM Home is also included)
Rooted, superuser
Google Play Store v3.5 (Android Market latest version)
Dolphin Browser, Gmail, Youtube, Terminal Emulator, Root Explorer
Development app for enabling USB debugging
Adobe Flash plug-in 10.1
Tim6a scripts for old FT3 wifi fix, 2MP camera fix etc.
Google Play Store fix and Performance tweaks in build.prop
Minimum apps included for smaller download size and performance
KNOWN ISSUES:
Market fix needs to be applied manually after installation.
TO-DO-LIST:
Custom Kernel to enable HDMI Mirroring and Overclocking (Investigating Stragulus FT Kernel Source atm)
CHANGELOG:
v1.0
Initial Release
Click to expand...
Click to collapse
DISCLAIMER: Please use this mod at your own risk, rooting your device and installing custom ROMs may render your device unusable and VOIDS THE WARRANTY.
I will try to ensure that all info about TolgaMOD_FT3 is up to date here, and will do my best to help in case of problems. It's best to report problems by replying to this thread rather than PM, so that the solution can be viewed by all users.

Hmmm.
I'm useing one of Tim's Roms... not sure wich one. The one where the screen is always dark. I tried dling your fixed stuff put it on my sd card it said it updated took out the sd card than turned it back on, but nothing had changed, everything was still the same? I have tryed the Power button+menu+front button to factory reset it, and still tims rom is still there with no changes. I just am at a loss now... really pissed to be honest. I cant even get the thing back to it's original original settings... I want to use your packet, any suggestions?

Anyone? I have just about tried everything and I'm on my last leg. I'm about ready to just rip the case open and K.O. the battery~

Hi billypaul69,
On my FT3, I just push menu+power to do a factory reset. Perhaps you could try that button combination to do a factory reset.
About flashing my ROM: Apparently the update somehow did not complete for you. I suggest you check out this excellent video tutorial from Axlien to flash a ROM to FT3, and see if it helps: http://www.youtube.com/watch?v=w7xdpnoHLeg
Make sure you don't turn off your device, before you see the following message on the screen:
Updating system firmware completed.
Please shutdown your device and remove the installation card!
Automatic shutdown in 1 minute.
Click to expand...
Click to collapse
If you see any other messages such as "not complete", "wrong system file" etc. and not the one above, please report them here. It's possible that either the .zip file you downloaded got somehow corrupted or the SDcard you are using for the update is faulty. In that case try re-downloading TolgaMOD, or formatting your SDcard and try again.
I hope that my suggestions work for you! Thanks for checking out my ROM!
Regards,
Tolga

Thanks soo much i'm going to try all the steps asap.
\billy

Hi
I just installed your new rom file and everything went Ok. The only problem is that my wifi network is not working. I can activate the wifi but it cannot find any network.
I tried using gscript to install on of the wifi patches but I get the following error message
"stderrermission denide" when I run the script.
Any idea as to why this is happening ? Apart from that, you rom is very snappy in operation.

Hi jammertn,
I'm glad you like the speed of my ROM, that was one of my goals indeed. I'm pretty sure one of the wifi scripts will correct the problem. For example my tablet's wifi works with the "old FT3" fix.
The reason you are getting the "permission denied" error is because gscript was not given superuser permissions.
The first time you run gscript, there should be a pop-up screen from superuser application asking for root rights. You should select "Allow" on this window. If you don't allow it or deny root access, the scripts won't work. If you denied root access and selected "remember" the first time, please launch superuser application from the app drawer and change the status of Gscript Lite to "Allow".
Since you have wifi not grayed out I guess your wifi is 0803 v2. Please try running the "Wifi fix:0803 version2" script and then reboot your tablet.
I hope that helps!

Hi and thanks for the quick reply.
From where do I launch superuser?

Click the middle button (the one with white squares) on the dock, you will have access to all installed apps including superuser.

OK I found the application.
One more question, Something happened and now gscript only sees 3 scripts. How can I make it show all the scripts like before.
Excuse all my dumb questions but I'm new at this.

No problem mate, I think the best way is to simply re-install the ROM You can backup your current apps with Titanium Backup.

Nice, thanks a million
I got it working now.
I'll be watching this thread closely.
Keep up to great work

Yay! I'm glad it worked, c ya around.

Hi Tolga
Is there anyway to activate bluetooth on this tablet? I tried using the gscript but cannnot get is to work. Any ideas ?

Hi jammertn,
This tablet doesn't have a bluetooth chip onboard. Tim's scripts are for driving usb bluetooth dongles. I'm not sure which ones work, but maybe the thread below could have more info.
http://www.apad.tv/apadforum/showthread.php?1358-Flytouch-3-Bluetooth-USB-dongle-testing-thread

Hi Tolga
Thanks for the reply, I have seen that thread but it does not have have any useful info in it. I tried it with an external usb/bluetootyh dongle but still no operation.

Hi,
I ran a quick web search and I haven't seen anyone successfully making a USB bluetooth dongle work on FT3. I think Tim included some kernel modules with the firmware for devs and testing purposes. So please don't assume it will work when you simply plug in any USB BT dongle.
Here's the support thread for Tim6a, there might be more info there:
http://www.apad.tv/apadforum/showthread.php?416-Flytouch-3-Hybrid-ROM-(rooted)&highlight=bluetooth
I think I have a USB BT dongle somewhere, I will take a look if I can find it
Regards,
Tolga

has this been posted on Apad.tv or tested on the iBex Flytouch 3 by people on there?

Do you mean if this ROM has been tested or if USB bluetooth dongle has been tested? I'm pretty sure TolgaMOD runs on Ibex Flytouch 3, since it's basically a modified version of Tim6a.
Here is my ROM's thread on apad.tv:
http://www.apad.tv/apadforum/showthread.php?2675-ROM-06-May-2012-TolgaMOD_FT3_v1.0

i installed rom over Tim 6a rom but still nothing changed,, MENU+power reset also tried.. currently my Huawei data stick does not work since some weeks, thats why i need to install a fresh firmware..
merhaba, yükleme yaptim fakat yine eski tim 6a rom yüklü yani hicbir sey degismedi, hard reset yaptim yine ayni.. ayrica önceden calisan Huawei data stick bi süredir calismiyor, birseyler silinmis olmali diyerek yeni rom yüklemek istiyordum, acaba neden calismiyordur data stick?

[Q] ADB not recognizing phone on USB when its booted android, fine in recovery

Hey everyone, basically just what the title says. I plug it into the computer via USB, and ADB will not see the device when it's booted into Android. However when I boot it into recovery, it sees it fine.
I'm running Cyanogen 9 for a rom and TWRP for recovery.
Booted into android:
C:\Users\Michael>adb devices
List of devices attached
Booted into recovery:
C:\Users\Michael>adb devices
List of devices attached
b3fe68e1 recovery
I've tried installing drivers, deleting drivers, reinstalling drivers, rebooting, countless times now. Samsung's own software Kies won't even recognize the phone.
I am able to use ADB over wifi with ADB Wireless.
C:\Users\Michael>adb devices
List of devices attached
10.0.0.99:5555 device
Oh, and I can turn on USB Storage and access the filesystem with no problems.. so that works fine.
Am I going crazy or has someone else had this same problem? Thanks everyone.

Sorry for the silly question but have you enabled it in settings? That may or may not help you:thumbup:
{
"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"
}
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

I should have posted that in my original thread.. but yes I have it enabled. I tried having ADB over network enabled just to see if it would help.. but it did't.

Is "USB Debugging" in the phone (inside Android) checked ? check this option and see..
PS:sorry if it is enabled ... ROM problem ? did adb work on stock ROM ?

Yep it is enabled. It did not work with the stock rom either and the only reason I know that is because my wife just got the same phone yesterday and I noticed it wasn't working while trying to root it.

Start all over again ...
Uninstall all drivers for the device and kies..
Install adb and USB driver for the phone and try again ...
You seem to have a software problem (a driver issue) somewhere around your PC (are you on Mac or Windows ?)

mahanddeem said:
Start all over again ...
Uninstall all drivers for the device and kies..
Install adb and USB driver for the phone and try again ...
You seem to have a software problem (a driver issue) somewhere around your PC (are you on Mac or Windows ?)
Click to expand...
Click to collapse
+1
try on another comp and c what happens, 2 phones cant be both screwed up so it must b comp

Yeah I agree it must be something to do with Windows. I will try installing the drivers and such on a computer at work on Monday and see what gives.
In the mean time I uninstalled everything and rebooted. Then I downloaded the drivers from Samsung's website, from here:
http://downloadcenter.samsung.com/c...27_GS_II_Skyrocket_USB_Driver_v1_3_2200_0.exe
I also read this post:
http://forum.xda-developers.com/showthread.php?t=1415051
and the #2 article points to: ATT_i777_GS2_USB_Drivers.zip
So I tried installing that too. Still nothing.
I took a couple screenshots during the process, maybe it will raise a red flag to one of you guys because I certainly can't figure this out.
When I plug in my phone, the "Android" device is what comes and goes. I've tried updating the drivers for that and pointing them to the Samsung drivers directory, just says it can't find them.
I admit to still being new around the whole android development thing, but with Windows I'm pretty proficient, I just can't figure out what I'm missing.

Just out of curiosity, why do you need to access adb with the phone not in recovery? You can do push pull commands through adb even if phone is in recovery

yoft1 said:
Just out of curiosity, why do you need to access adb with the phone not in recovery? You can do push pull commands through adb even if phone is in recovery
Click to expand...
Click to collapse
If super user is installed yes you can pull or push even in Android...But if not rooted it's only done while in recovery...

y do u need to use adb, i have returned to stock many times, so i installed cwm many times, all the roms r rooted, so w/cwm and root explorer i have not needed to use adb myself

vincom said:
y do u need to use adb, i have returned to stock many times, so i installed cwm many times, all the roms r rooted, so w/cwm and root explorer i have not needed to use adb myself
Click to expand...
Click to collapse
Well if you ask me I wouldn't trust root and i would modify things using recovery and adb..but that's just me..

mahanddeem said:
Well if you ask me I wouldn't trust root and i would modify things using recovery and adb..but that's just me..
Click to expand...
Click to collapse
k, but r u not installing any custom roms, as far as i know they are all prerooted, or u just need root todo ur own stuff

Personally I just like being able to have access to use adb. I can still use it over wifi using "adb wireless" so it's not a complete loss -- but for some reason the fact that the usb isn't working is just bothering me.
I'm not going to spend much more time fighting with it.. I'm sure it has something to do with the windows and the drivers.

mmerlina said:
Personally I just like being able to have access to use adb. I can still use it over wifi using "adb wireless" so it's not a complete loss -- but for some reason the fact that the usb isn't working is just bothering me.
I'm not going to spend much more time fighting with it.. I'm sure it has something to do with the windows and the drivers.
Click to expand...
Click to collapse
i agree its win7 and drivers

Hey I know this thread is a week old or so, but I just wanted to let you know I found the problem. The problem was actually the Cyanogenmod ROM I had installed.
I was having a few other unrelated problems with that rom so I decided to try SkyICS, and low and behold.. I can now access adb via usb.
Just wanted to put the solution forward and maybe it will shine light on someone else's problem.
Thanks again to everyone for all their help.

mmerlina said:
Hey I know this thread is a week old or so, but I just wanted to let you know I found the problem. The problem was actually the Cyanogenmod ROM I had installed.
I was having a few other unrelated problems with that rom so I decided to try SkyICS, and low and behold.. I can now access adb via usb.
Just wanted to put the solution forward and maybe it will shine light on someone else's problem.
Thanks again to everyone for all their help.
Click to expand...
Click to collapse
Not exactly a solution though, in that Sky ICS is still a TW-based ROM (as in, based off the stock ROM) and not an AOSP-based ROM like CM9 or AOKP.
I also had this issue. The problem was in fact a Windows driver issue though, even though I had installed them already. When I went to Device Manager it would always show up as generic "Android" device with no driver under "other devices". I right-clicked it, Selected "Update device drivers" and then I believe there was an option to select drive from existing installed drivers. I'm on my linux partition right now so I forget what the precise option dialogue was, but it was a separate option from the "Browse my computer" option. From there it opened up a long list and I scrolled down and found one of the Samsung entries listed. I believe it was Samsung Electronics Co. Ltd. (there were others like SAMSUNG in all caps, etc.). I then selected the driver from the list within that Samsung group and ADB worked again.

P6200: Unable to use Heimdall to flash firmware

My brother attempted to root my Galaxy Tab P6200 (and succeeded), and then tried to run an app which increased pixel density which is when everything went downhill.
Thereafter, I constantly get this message "Sorry! The application Tw Launcher (process com.android.launcher) has stopped unexpectedly." and my tab has been rendered useless for the time being.
I have been desperately trying to flash various packages, right from the Official firmware from here to Clockwork Mod from here.
All to no avail, as I am constantly getting the error as shown 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"
}
I am using a Macbook Pro running OSX Lion 10.7.4, Heimdall-Frontend v 1.3.1
I do have access to a Windows machine (running Vista) as well, but there my problem is that the tab is not getting recognised (inspite of installing KIES and Samsung drivers).
Any ideas on how to resolve this? Thank you for your time.

Jambavan said:
My brother attempted to root my Galaxy Tab P6200 (and succeeded), and then tried to run an app which increased pixel density which is when everything went downhill.
Thereafter, I constantly get this message "Sorry! The application Tw Launcher (process com.android.launcher) has stopped unexpectedly." and my tab has been rendered useless for the time being.
I have been desperately trying to flash various packages, right from the Official firmware from here to Clockwork Mod from here.
All to no avail, as I am constantly getting the error as shown below.
View attachment 1227962
View attachment 1227963
I am using a Macbook Pro running OSX Lion 10.7.4, Heimdall-Frontend v 1.3.1
I do have access to a Windows machine (running Vista) as well, but there my problem is that the tab is not getting recognised (inspite of installing KIES and Samsung drivers).
Any ideas on how to resolve this? Thank you for your time.
Click to expand...
Click to collapse
I remember I messed up my tablet using the DPI Changer app when I first got it (I think I tried setting DPI to 170 or 180, I don't remember), but I had already made a backup in CWM which I restored and that fixed the problem.
I don't know whether the following will help or not. Have you used the Play Store on your device to download apps? You could try installing a different launcher (that works at the DPI you set) directly to your device using the Play Store from a web browser on your PC ( https://play.google.com/store?hl=en ). You may need to tap the home button on your tablet to select it/set it as default after it has been installed.
BTW, that CM 9 ZIP you tried to flash should be installed using ClockworkMod (CWM).
It might be worth a try. I hope this helps.

Hi k_t_b, thanks for your reply.
Unfortunately, I am no longer signed in to my account on the tab, and can't seem to sign in either because of the TW launcher problem.

Jambavan said:
Hi k_t_b, thanks for your reply.
Unfortunately, I am no longer signed in to my account on the tab, and can't seem to sign in either because of the TW launcher problem.
Click to expand...
Click to collapse
So, when you visit the play store using a web browser on your computer, signed-in to your account, you aren't able to click "INSTALL" and select your device from the list "SEND TO ANOTHER DEVICE..."? Even if you can't tap the home button on your status bar to select an alternate launcher after installing a different launcher, you should be able to select the other launcher upon rebooting your tablet.
But, If I am understanding you correctly, you signed-out of your google account on the tablet (removed your account or turned off syncing) before you changed the DPI? If that's the case, I suppose my suggestion isn't an option.
If you can get ADB working (you have the Android SDK installed and the USB drivers from Samsung KIES) then you might want to try to pull the build.prop file, edit the DPI value and push build.prop back to your tablet.
Are you able to boot into recovery mode? (With your tablet off, Hold the Volume Up and Power buttons at the same time)

k_t_b said:
So, when you visit the play store using a web browser on your computer, signed-in to your account, you aren't able to click "INSTALL" and select your device from the list "SEND TO ANOTHER DEVICE..."? Even if you can't tap the home button on your status bar to select an alternate launcher after installing a different launcher, you should be able to select the other launcher upon rebooting your tablet.
But, If I am understanding you correctly, you signed-out of your google account on the tablet (removed your account or turned off syncing) before you changed the DPI? If that's the case, I suppose my suggestion isn't an option.
If you can get ADB working (you have the Android SDK installed and the USB drivers from Samsung KIES) then you might want to try to pull the build.prop file, edit the DPI value and push build.prop back to your tablet.
Are you able to boot into recovery mode? (With your tablet off, Hold the Volume Up and Power buttons at the same time)
Click to expand...
Click to collapse
Hi again,
Yes you are right, I am no longer signed in. When I found the tab in its current state, I got into recovery mode and selected 'factory rest'. On rebooting, I found out that I was no longer signed in to my google account, nor could I try to sign back in since at every stage the TW Launcher fails.
Also, as of now, the tab is in Download mode (since I was trying to flash the firmware), and it says something on the lines of "Do not switch off target device". So not sure if I should turn off the tab or not.

Jambavan said:
Hi again,
Yes you are right, I am no longer signed in. When I found the tab in its current state, I got into recovery mode and selected 'factory rest'. On rebooting, I found out that I was no longer signed in to my google account, nor could I try to sign back in since at every stage the TW Launcher fails.
Also, as of now, the tab is in Download mode (since I was trying to flash the firmware), and it says something on the lines of "Do not switch off target device". So not sure if I should turn off the tab or not.
Click to expand...
Click to collapse
Don't worry about that. If this was a phone with a removable battery, then you might remove the battery to get it out of download mode. You should be able to power off this tablet without a problem as long as you aren't in the middle of flashing it.
If you can't use ADB successfully while booted normally or in recovery, then I believe your only option will be to flash a stock firmware with Odin, Heimdall or flash CM 9. If you want to go the CM 9 route, then make sure you flash CWM first ( garyd9's CWM http://forum.xda-developers.com/showthread.php?t=1392348 - you can find instructions in his CWM for the 6210 thread and I think you'll need to have a microSD card to perform this operation ) , then install that CM 9 zip (which you attempted to flash using Heimdall) using CWM.

Thanks once again for your reply, I really appreciate the help. :good:
I will try and use the adb route and reply if I have any luck. Just one thing though, will it make a difference if I am using Linux as a virtual machine? (Ubuntu run via Parallels on a Macbook).
Also, while I agree with each of the three modes suggested by you, as of now I am stuck with both Mac and Windows (running Windows Vista) telling me while using Heimdall that it has "failed to detect compatible download-mode device". Odin on the other hand, doesn't show any signs of the port turning yellow.
I have installed KIES on both the machines, so not sure what the issue is. Also tried the usual restarting and changing USB ports procedures.

I think that with the cmw is possible to install unsigned packages. So is just a question of making a package with a corrected build.prop. the structure of a update package is real simple, look the one on the thread about root.
Just an idea.
Sent from my GT-P6210 using Tapatalk 2

leodfs said:
I think that with the cmw is possible to install unsigned packages. So is just a question of making a package with a corrected build.prop. the structure of a update package is real simple, look the one on the thread about root.
Just an idea.
Sent from my GT-P6210 using Tapatalk 2
Click to expand...
Click to collapse
As of now, my problem is that neither my Mac nor my PC is recognising the P6200 when in "Download" mode. I have installed Kies (on both Windows and Mac), and also the drivers that come with Heimdall (For Windows).

Literally all you have to do is just reflash the Rom in recovery without wiping. Factory reset won't do it. Done it myself a time or 2
Sent from my myTouch 4g via Tapatalk

I finally flashed the stock rom using Odin. Also, I had to install certain drivers for the USB, details of which I will post later.
Sent from my GT-P6200 using xda app-developers app

Cloudfone Excite 350g

This is a rebranded phone in the Philippines running ICS 4.0.4, has 512mb RAM, 1GHZ core. Does anyone know what the original phone is? I've had a hard time looking for pc drivers, but was able to root it with bin4ry.
{
"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"
}
sent from my rooted Cloudfone Excite 350g

I just found out that the phone is a rebranded Mobistar Touch Cream 350.

Rooted the Cloudfone Excite 350g?
Hi mrichiem! I have the same phone but was unable to root it with Bin4ry v17, though I have installed the drivers using Moborobo and also tried with Super OneClick. What process have you made to root it? O_O I tried taking it to safe mode, but still the permission is still denied. I am searching ways to root it but since it was just released last December, I guess the company is suppressing the growth of tutorials of rooting their models. But I guess the company is expecting users to root it because of it's low internal memory. O_O Thanks.

::ROOT:: Cloudfone Excite 350g
Let me set down here exactly what I did to root my excite 350g. The files you will need are attached, but you will have to search and download Moborobo. I had to research the proper way to install the drivers as my first attempt ended up soft-bricking my phone. I had to bring it to the service center to have it repaired. Funny thing was my warranty still covered it, even though it was already rooted and I had changed the boring yellow bootanimation.
So, be warned and root at your own risk!!
Extract the files to a folder or your desktop. Turn off your 350g and remove the battery. The next step will take a bit of dexterity and timing. Plug the USB cable to your PC. Press and hold the Volume up button on the phone and quickly insert the battery. The pc will prompt you to install drivers for the device. Just direct the wizard to the MTK65xx Driver folder. Once drivers are installed release the volume up button. Open the MTK Android PC Sync Tool and select Cloudfone Excite 350g in the popup. This will install the MTK Suite Daemon on the phone. Once done, you can close the tool. Next open Moborobo which will automatically install additional drivers for the phone. Once you have done all of this, you may now proceed with rooting. I have included two versions of bin4ry in the file. Try using Root Mtk Android 4.0.4 v15 first. If this does not work, use Root MTK ICS. The phone should now be rooted.
Download: http://www.4shared.com/rar/kOhRfezo/DEV.html

Great!
Haha. As they were saying that the warranty will be void if you have rooted the phone. Great! Thanks! I'll try it. I hope i won't end up bricking my phone. Thanks mrichiem! :good: I will reply as soon as I have tried the method. :highfive:

Haist... after following all the instruction still after rebooting my phone dont show a super user icon. Even the computer says im already rooted
Sent from my Flare (S100)/A9 using Tapatalk 2

Please try this to know if you are really rooted...
werdna99 said:
Haist... after following all the instruction still after rebooting my phone dont show a super user icon. Even the computer says im already rooted
Sent from my Flare (S100)/A9 using Tapatalk 2
Click to expand...
Click to collapse
Please install this app from the Google PlayStore:
Android Terminal Emulator by Jack Palevich
It is mainly a Linux Command Prompt Emulator that is used to do some functions such as cp (Copy), ifconfig (Get the IP address of your phone), etc.
After you installed it, please follow the instructions below:
Open the Android Terminal Emulator App.
Type: cd root
If you see something like /system/bin/sh: cd: /root - Permission denied, you are not yet rooted. And maybe that is the reason why the SuperUser app was not installed.
Are you rooting the your CM Flare? I guess this trick works only for Cloudfone350g.

Sir, exactly how many seconds does it take for you to plug the phone via usb then hold the volume up and insert the battery?? i cannot seem to get it right. i've tried a dozen times already and i still can't get it.

No sir. Im rooting the cloudfone of my friend. I already root several android phone this unit give me head ache my cm flare ia already rooted
Sent from my Flare (S100)/A9 using Tapatalk 2

Replying to all
HI ALL!
At first I was having difficulty with this method trying this on Windows 7. But I switched to Windows XP in order to see if there would be difference. Use Windows XP instead because I have successfully rooted my phone with that.
I just rooted my phone now, so it took me a long time to reply. It is because I tried to see if someone would verify the trick and to give further instructions to it. But then, it seems no one is willing to share. XD
So here is the reason for each step of the trick.
1. Insert the USB Cable (take note, the USB cable to the PC not to the Phone), insert the battery, then hold Volume UP. This would only take less than 10 seconds. It's aim is to force the PC to detect the MTK Preloader so that you can install it the drivers for it.
2. Run MTK Android PC Sync Tool and let it install the MTK driver for your phone. The aim is to install the "debug mode MTK driver" into your Phone so that the Root by Bin4ry would be able to copy files into your Phone's internal memory and run commands.
3. Lastly, Open moborobo and let it install the Moborobo Suite Daemon into your device. The aim is just like the #2. To add drivers that will support the rooting.
Root it with Root Mtk Android 4.0.4 v15.
I have added some screenshots as a proof Hit thanks for me and mrichiem if you have succeed!

BlueFireSiege said:
HI ALL!
At first I was having difficulty with this method trying this on Windows 7. But I switched to Windows XP in order to see if there would be difference. Use Windows XP instead because I have successfully rooted my phone with that.
I just rooted my phone now, so it took me a long time to reply. It is because I tried to see if someone would verify the trick and to give further instructions to it. But then, it seems no one is willing to share. XD
So here is the reason for each step of the trick.
1. Insert the USB Cable (take note, the USB cable to the PC not to the Phone), insert the battery, then hold Volume UP. This would only take less than 10 seconds. It's aim is to force the PC to detect the MTK Preloader so that you can install it the drivers for it.
2. Run MTK Android PC Sync Tool and let it install the MTK driver for your phone. The aim is to install the "debug mode MTK driver" into your Phone so that the Root by Bin4ry would be able to copy files into your Phone's internal memory and run commands.
3. Lastly, Open moborobo and let it install the Moborobo Suite Daemon into your device. The aim is just like the #2. To add drivers that will support the rooting.
Root it with Root Mtk Android 4.0.4 v15.
I have added some screenshots as a proof Hit thanks for me and mrichiem if you have succeed!
Click to expand...
Click to collapse
Last time i used a windows 7 pc ill try your advice
Sent from my Flare (S100)/A9 using Tapatalk 2

Backup rom
Please backup rom for me, i need rom!!

I also had the same problem as I has already rooted my Excite 350g before backing up the ROM. So I had to search the net to look for a way to restore my phone in case something went wrong. And indeed, something went wrong. I ended up flashing the original Mobiistar firmware and discovered something interesting. The original camera resolution of the device is 3MP, which is what I have now. And after uninstalling the stock Vietnamese files, I ended up with 160MB of free internal memory. The site is in Tieng Viet, so use Chrome to translate the page as it loads and depend more on the screenshots than the actual instructions. As usual, flashing MTK ROMs work best on PCs running Windows XP.
Click Here to Open Link

Posting benchmark results before and after flashing the stock Mobiistar ROM.
sent from my Excite 350g