I have tried this on both the pure/stock first ICS leak and a custom ROM based upon that leak (ScV7) and in both cases, when I connect my Atrix 2 to the Lapdock 500, it *very* briefly displays the correct Webtop 3.0 welcome screen, and then just abandons that and jumps right into "mirror mode" with the notification bar still at the top as usual, and everything blown up to ridiculous size. Exactly ONCE it went into true Webtop/ICS Tablet mode as it was supposed to (notification bar at bottom), but every time after that it just insists on Mirror mode and doesn't under any circumstances allow me to choose Webtop 3.0, in other words ICS tablet mode.
Does anyone know how to fix this?
This turned out to be related to the "Entitlement Check" which blocked Webtop from starting up. I disabled that check and Webtop now loads correctly.
paleozord said:
This turned out to be related to the "Entitlement Check" which blocked Webtop from starting up. I disabled that check and Webtop now loads correctly.
Click to expand...
Click to collapse
I'm having the same issues. What exactly is this "entitlement check" and how do I access it. Thanks.
dwilbur said:
I'm having the same issues. What exactly is this "entitlement check" and how do I access it. Thanks.
Click to expand...
Click to collapse
The entitlement check is a setting built into the AT&T ROM by default to check whether you have permission from your carrier to do things like Wifi and USB Tethering. Why it does this check upon connecting a Webtop accessory I'm not quite sure, but anyway...
Things you will need to disable it:
ES File Explorer (free from play store)
aSQLiteManager (free from play store)
1. Launch ES File Explorer and within its settings, grant it full root permissions (near the bottom of settings, go in and check all four checkboxes).
2. From ES File Explorer navigate upward out of your SD card and onto the root of your device, then go into Data/Data/com.motorola.android.providers.settings/databases
3. Copy the "settings.db" file found there over to your SD card
4. Using aSQLiteManager select "Open Database" and pick that settings.db file on your SD card.
5. Select "settings" from the four tables you are presented with
6. Select "Data" from the top button menu
7. You'll see a long list of crap. Hit PgDn untiul you see line 113 "entitlement_check". Hit Edit and change the value from 1 to 0.
7b. Also go to line 70 "usb_entitlement_check" and change the value from 1 to 0 as well.
8. While you're here, also go to lines 117 and 118 that start with "dun" and change them both from 0 to 1. This is not necessary for Webtop but will enable wifi hotspot tethering.
9. Exit aSQLiteManager, go back into ES File Explorer and this time copy the modified "settings.db" back into the previous/original folder from Step 2, overwriting the old file.
10. Exit ES File Explorer, reboot your device and Webtop should work as expected.
Fix for Webtop disappearing
paleozord said:
The entitlement check is a setting built into the AT&T ROM by default to check whether you have permission from your carrier to do things like Wifi and USB Tethering. Why it does this check upon connecting a Webtop accessory I'm not quite sure, but anyway...
Things you will need to disable it:
ES File Explorer (free from play store)
aSQLiteManager (free from play store)
1. Launch ES File Explorer and within its settings, grant it full root permissions (near the bottom of settings, go in and check all four checkboxes).
2. From ES File Explorer navigate upward out of your SD card and onto the root of your device, then go into Data/Data/com.motorola.android.providers.settings/databases
3. Copy the "settings.db" file found there over to your SD card
4. Using aSQLiteManager select "Open Database" and pick that settings.db file on your SD card.
5. Select "settings" from the four tables you are presented with
6. Select "Data" from the top button menu
7. You'll see a long list of crap. Hit PgDn untiul you see line 113 "entitlement_check". Hit Edit and change the value from 1 to 0.
8. While you're here, also go to lines 117 and 118 that start with "dun" and change them both from 0 to 1. This is not necessary for Webtop but will enable wifi hotspot tethering.
9. Exit aSQLiteManager, go back into ES File Explorer and this time copy the modified "settings.db" back into the previous/original folder from Step 2, overwriting the old file.
10. Exit ES File Explorer, reboot your device and Webtop should work as expected.
Click to expand...
Click to collapse
THIS WORKED PERFECT! What a relief! :good::good:
just double checking before i get charged a lot of $$$
hey guys, first i just wanna say this is my first post i have watched the noob video but before i start using my tethering or hotspots...i've done everything that the post said and i have my lines 70 (checking) 113, 117, and 118 and i'm rooted (thanks to you awesome guys ) but like i said i just wanna make sure i'm not getting charged for any of this
Didn't work
lavoietg said:
THIS WORKED PERFECT! What a relief! :good::good:
Click to expand...
Click to collapse
Hello everybody.
Well, I must say I have an MB865 (AT&T Branded) quite a long time ago and just a couple of days ago I upgraded to official ICS. Loved it!
But I did not remember that the main reason I rooted my phone when it was in GB it was because wifi tethering. I remember doing something similar with SQLite modifying entitlement_check from 1 to 0, and just doing that It worked.
Now, I see, process is the same, but including now usb_entitlement_check and both lines starting with dun, so I rooted again, and already done that SQLite thing, but it's still not working.
First, I don't know if it's supposed to appear a notification when wifi tethering or usb tethering gets turned on just like it used to be like back in GB, but I'm getting no notification, only when a device "connects to my phone"
I can surf any website from my phone, and devices connecting to it say "connected" but websites don't load, nothing loads. Already tried in PC, Mac, and phones... same to all of them. Did I miss/skip something?
didnt work
Do it as described twice by change line113 from 1 to 0, phone freeze on "rethink possible" screen, must make factory reset. Firmware is 125.en.us 4.0.4 +root (mb865) reason - need for use lapdock 500 in webtop mode when connected over mobile internet connection (will popup message about entitlement check failed then go to mirror mode)
Can provide something for off that check? Maybe must rename field as "disabled"? Or one post on forum say "go to system/app and rename entitlementservice.apk and it's related file. (one other with a similar name) to .bak files and reboot." - which one works correct?
uboat55 said:
Do it as described twice by change line113 from 1 to 0, phone freeze on "rethink possible" screen, must make factory reset. Firmware is 125.en.us 4.0.4 +root (mb865) reason - need for use lapdock 500 in webtop mode when connected over mobile internet connection (will popup message about entitlement check failed then go to mirror mode)
Can provide something for off that check? Maybe must rename field as "disabled"? Or one post on forum say "go to system/app and rename entitlementservice.apk and it's related file. (one other with a similar name) to .bak files and reboot." - which one works correct?
Click to expand...
Click to collapse
From your description it sounds as though you may be trying to edit the settings.db file right in place on your phone, which could cause a reboot/freeze. You have to make sure to copy the settings file over to your SD card, use aSQLitemanager to edit that copied file, not the original one, and then copy the modified file back to the original location, over-writing the unmodified one.
Also, make sure that line 113 does in fact say what it's supposed to, namely "entitlement_check". Sometimes this property can appear on different lines depending on the rom/firmware in use, as can the others starting with "dun". So be sure to change the right property settings.
I have the Lapdock 500 as well with the the MB865 (AT&T unlocked running on Rogers in Canada) and use it all the time without issue after having made these changes. I wouldn't bother with renaming the entitlementcheck.apk as this only half helps, allowing you to activate webtop when connected but still not providing mobile data in this mode. Doing all three of those edits to the settings.db file and then rebooting, should fix everything.
thanks for answer, - i rename entitlementservice.apk to entitlementservice.bak and entitlementservice.odex to .odexbak (as mad try change to .bak but it deny and i think lost that method also, but huh :silly: its just cause have already .bak in same directory. ) direct on same directory by giving root access to file manager then reboot and check mobile connection, it works. will check again for that but seems it already works without any entitlement checking.
I do strongly as posted, put file to sd card and make changes, line 113 was entitlement_check with value 1. after change i overwrite it to system directory but. finally must reset for get back phone to life, mmaybe i do something wrong. i do it after reset also
There is one strange what i catch is a weight of settings.db first was a 15kb but after fall and freeze then reset it was a 14kb.
uboat55 said:
thanks for answer, - i rename entitlementservice.apk to entitlementservice.bak and entitlementservice.odex to .odexbak (as mad try change to .bak but it deny and i think lost that method also, but huh :silly: its just cause have already .bak in same directory. ) direct on same directory by giving root access to file manager then reboot and check mobile connection, it works. will check again for that but seems it already works without any entitlement checking.
I do strongly as posted, put file to sd card and make changes, line 113 was entitlement_check with value 1. after change i overwrite it to system directory but. finally must reset for get back phone to life, mmaybe i do something wrong. i do it after reset also
There is one strange what i catch is a weight of settings.db first was a 15kb but after fall and freeze then reset it was a 14kb.
Click to expand...
Click to collapse
In the Settings.db file, check that line 70 "usb_entitlement_check" is also set to 0 rather than 1.
I believe that in the stock ICS ROM this is how it is already set by default which is why I didn't include it in my main instruction set above in the first post. Nope I'm wrong.. just checked and on stock MB865 ROM it is set to 1, and should be changed to zero as well. I will edit my first post to include this extra step as a result.
uboat55, please let me know if this helps, although none of these changes should be causing crash/freezes in your device upon reboot, so there may still be something else going on.
may you excuse me cause i afraid for again freeze, its very hard to recover programms and other style which i use, i could hardly recover much of it, and it took much time for place icons programs, paswords etc. very hard.. i`m novice in that and dont know how easy recover all after reset. must learn that. But i check again mobile connection and can confirm that no any entitlement check found and lapdock works in webtop mode (not changed to mirror mode), seems renaming files succesful for that
In case you need another example of why CWM & Backup is useful....
paleozord said:
The entitlement check is a setting built into the AT&T ROM by default to check whether you have permission from your carrier to do things like Wifi and USB Tethering. Why it does this check upon connecting a Webtop accessory I'm not quite sure, but anyway...
Things you will need to disable it:
ES File Explorer (free from play store)
aSQLiteManager (free from play store)
1. Launch ES File Explorer and within its settings, grant it full root permissions (near the bottom of settings, go in and check all four checkboxes).
2. From ES File Explorer navigate upward out of your SD card and onto the root of your device, then go into Data/Data/com.motorola.android.providers.settings/databases
3. Copy the "settings.db" file found there over to your SD card
4. Using aSQLiteManager select "Open Database" and pick that settings.db file on your SD card.
5. Select "settings" from the four tables you are presented with
6. Select "Data" from the top button menu
7. You'll see a long list of crap. Hit PgDn untiul you see line 113 "entitlement_check". Hit Edit and change the value from 1 to 0.
7b. Also go to line 70 "usb_entitlement_check" and change the value from 1 to 0 as well.
8. While you're here, also go to lines 117 and 118 that start with "dun" and change them both from 0 to 1. This is not necessary for Webtop but will enable wifi hotspot tethering.
9. Exit aSQLiteManager, go back into ES File Explorer and this time copy the modified "settings.db" back into the previous/original folder from Step 2, overwriting the old file.
10. Exit ES File Explorer, reboot your device and Webtop should work as expected.
Click to expand...
Click to collapse
Well, I followed the instructions, and saved the DB file back in the original location, and when I reboot the phone is is stuck at the 'Rethink Possible' screen. The phone is rooted (SU prompted me for changes) but is running the stock rom. Stupidly, I did not install CWM or make a backup, so how can I install a new rom or CWM or ?? to get things going again? I can go into the standard recovery / fastboot options menu.
johnmbailey said:
Well, I followed the instructions, and saved the DB file back in the original location, and when I reboot the phone is is stuck at the 'Rethink Possible' screen. The phone is rooted (SU prompted me for changes) but is running the stock rom. Stupidly, I did not install CWM or make a backup, so how can I install a new rom or CWM or ?? to get things going again? I can go into the standard recovery / fastboot options menu.
Click to expand...
Click to collapse
Since you don't have a custom recovery installed, you'll have to flash the FXZ for your phone via RSD lite. Make extra sure that you have the correct FXZ because flashing the wrong one has a high probability of bricking your phone.
If I had a dollar for every time I said that, I'd be making money in a very weird way.
I downloaded the FXZ, and it is going again
1BadWolf said:
Since you don't have a custom recovery installed, you'll have to flash the FXZ for your phone via RSD lite. Make extra sure that you have the correct FXZ because flashing the wrong one has a high probability of bricking your phone.
If I had a dollar for every time I said that, I'd be making money in a very weird way.
Click to expand...
Click to collapse
The computer would not recognize the phone using RSD, so I used the script found in another post on the site. Thanks for the input.
Related
http://forum.xda-developers.com/archive/index.php/t-644769.html << I got my idea from there.
If you update the
Code:
/data/data/com.android.providers.settings/databases/settings.db
file so that "install_non_market_apps" = 1 instead of 0, you will be able to install non-market apps off of your sdcard or wherever.
This works for me at least, but you'll have to root first.
I ended up editing the file with the SQLite Manager firefox add-on.
But, since that took me a really long time, I'll just upload the edited settings.db for you. (don't forget to make the extention .db instead of .db.txt)
Now, as far as I know, this won't mess anything up... BUT, I'd feel a lot better if someone who knows more about Android would provide some feedback before anyone else tries this. [It works for me, but I'm not sure if any other user-specific settings are kept in that file that I don't know about!]
But, at least for me, I no longer need to use adb to install apks that aren't from the Android Market.
I hope this is useful to someone...
EDIT::
You will lose your settings if you use the attached settings.db.txt file. Your best bet is to pull the file off your phone, edit it with something that understands sqlite3's database format, and then push it back. It's just better that way.
Further EDIT:: As someone pointed out later in this thread, this file unbeknownst to me when I shared it, actually has a unique ID by which phones can be identified on the android market, etc. While this isn't a huge deal, it can lead to some rather strange behavior... my phone for example has started attempting to download apps from the android market all by itself.
So--- if you want to side-load apps, change the variable in the database like I explained above.
Sorry, completely new to android but where would you put this file so it would allow side-loading?
You'd have to replace
Code:
/data/data/com.android.providers.settings/databases/settings.db
with it. You'll have to have your phone rooted first though. Then you'll have to transfer the file to your phone with adb, and you'll then copy it over the existing settings.db file.
Honestly, it might not even be worth the trouble now that attn1 is just doing the whole ROMs.
But make sure you take off the .txt.
This works. Thanks.
For some reason, i'm getting a permissons error regardless that i successfuly rooted my phone...o_o
justince said:
For some reason, i'm getting a permissons error regardless that i successfuly rooted my phone...o_o
Click to expand...
Click to collapse
did you boot the phone and do adb remount with debugging enabled?
USB debugging? Yeah.
What i did was i used the other method to sideload root explorer, took the settings.db.txt, deleted the .txt part and replaced it via root explorer, and now i can sideload whenever...however, when i try to delete any of the att bloatware, its read only o_o fawking att
Can anyone confirm any other way to remove bloatware without flashing the rom?
justince said:
USB debugging? Yeah.
What i did was i used the other method to sideload root explorer, took the settings.db.txt, deleted the .txt part and replaced it via root explorer, and now i can sideload whenever...however, when i try to delete any of the att bloatware, its read only o_o fawking att
Can anyone confirm any other way to remove bloatware without flashing the rom?
Click to expand...
Click to collapse
That's why made the ROM without all that -er- stuff.
attn1 said:
That's why made the ROM without all that -er- stuff.
Click to expand...
Click to collapse
Attn's Rom is ****ing great. many thanks btw
a little help please
a bit confused..
how do i type in this code "/data/data/com.android.providers.settings/databases/settings.db"?
adb /data/data/com.android.providers.settings/databases/settings.db
or something else because that doesnt work.
fluffyarmada said:
I'm not sure if any other user-specific settings are kept in that file that I don't know about!
Click to expand...
Click to collapse
The only issue I see (as an Android newcomer, but with a development background) is that the settings.db contains an android_id that is supposed to be unique (it gets generated when you boot the phone the first time after a reset). So anyone installing your settings.db is going to have the same ID.
I'm sure it won't be an issue for most people but I wonder if there'd be a collision in any apps that are designed to communicate between Android devices? For this reason I'll be tweaking my own settings.db once the phone arrives later today.
Big thanks for posting this though!
Thanks for that, I honestly had no idea. I'm very new to Android. And this was a kludge.
fluffyarmada said:
http://forum.xda-developers.com/archive/index.php/t-644769.html << I got my idea from there.
If you update the
Code:
/data/data/com.android.providers.settings/databases/settings.db
file so that "install_non_market_apps" = 1 instead of 0, you will be able to install non-market apps off of your sdcard or wherever.
This works for me at least, but you'll have to root first.
I ended up editing the file with the SQLite Manager firefox add-on.
But, since that took me a really long time, I'll just upload the edited settings.db for you. (don't forget to make the extention .db instead of .db.txt)
Now, as far as I know, this won't mess anything up... BUT, I'd feel a lot better if someone who knows more about Android would provide some feedback before anyone else tries this. [It works for me, but I'm not sure if any other user-specific settings are kept in that file that I don't know about!]
But, at least for me, I no longer need to use adb to install apks that aren't from the Android Market.
I hope this is useful to someone...
EDIT::
You will lose your settings if you use the attached settings.db.txt file. Your best bet is to pull the file off your phone, edit it with something that understands sqlite3's database format, and then push it back. It's just better that way.
Further EDIT:: As someone pointed out later in this thread, this file unbeknownst to me when I shared it, actually has a unique ID by which phones can be identified on the android market, etc. While this isn't a huge deal, it can lead to some rather strange behavior... my phone for example has started attempting to download apps from the android market all by itself.
So--- if you want to side-load apps, change the variable in the database like I explained above.
Click to expand...
Click to collapse
NOTE: You MUST have root access in order for this to work
sqlite3 is included in the Android SDK tools, so this would be the best way:
COMMON
Enable USB debugging (settings > applications > development > USB Debugging)
adb remount
adb pull /data/data/com.android.providers.settings/databases/settings.db settings.db
Linux/OS X
echo "update secure set value = 1 where name = 'install_non_market_apps';"|./sqlite3 settings.db
WINDOWS
echo update secure set value = 1 where name = 'install_non_market_apps';|sqlite3 settings.db
COMMON
adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
Reboot phone and sideloading works. (thanks fluffyarmada)
I wonder if this might be why google voice fails to install properly for some...
Sent from my HTC Liberty using XDA App
Cobus said:
I wonder if this might be why google voice fails to install properly for some...
Sent from my HTC Liberty using XDA App
Click to expand...
Click to collapse
It is possible. The Google apps all use the android_id, afaik.
Although, I do remember I was never able to get the settings menu to setup the voicemail forwarding... I always had to use the weird GSM code. (The weird number with a bunch of * and # that you have to type in if you follow google's directions.)
judicious said:
a bit confused..
how do i type in this code "/data/data/com.android.providers.settings/databases/settings.db"?
adb /data/data/com.android.providers.settings/databases/settings.db
or something else because that doesnt work.
Click to expand...
Click to collapse
After you've rooted your phone, download the new settings.db into the same folder as where your adb program is. Then type:
adb push /data/data/com.android.providers.settings/databases/settings.db
in that folder while your phone is connect via usb.
I'm not sure if you have to restart your phone into recovery or not. Can someone check on this?
tiga2001 said:
After you've rooted your phone, download the new settings.db into the same folder as where your adb program is. Then type:
adb push /data/data/com.android.providers.settings/databases/settings.db
in that folder while your phone is connect via usb.
I'm not sure if you have to restart your phone into recovery or not. Can someone check on this?
Click to expand...
Click to collapse
Well, it's
Code:
$ adb push /path/to/file/on/computer/settings.db /path/to/file/on/phone/settings.db
So, if your settings.db is in your tools folder, then you can do
Code:
$ adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
what happen to the file download? i cant find it..
judicious said:
what happen to the file download? i cant find it..
Click to expand...
Click to collapse
Please follow the instructions posted by attn1 on reply number 13 to this thread.
I removed the settings.db, because it actually has a bunch of extra settings I didn't know about like a handset specific android_id variable... that caused me a bit of trouble...
But, follow the instructions on reply #13 on this thread, and you'll be able to fix it yourself.
Sorry for the inconvenience.
so if we already used the file, is there anyway to revert it back to default and then change the settings via the method outlined above? or.. if we failed to make a copy of our original settings.db file.. basically am i SOL?
EDIT: nevermind, just rebooted into Clockwork and wiped the phone.
THIS GUIDE HAS BEEN REDONE. PLEASE VISIT THIS THREAD:
http://forum.xda-developers.com/showthread.php?t=761819
Just reading through the document now, seems the first link, http://www.soft‐go.com/get/Samsung‐Kies_79632.html isn't working. Not sure if the site is just down right now or if there's a mistake.
Rad_Fishy said:
Just reading through the document now, seems the first link, http://www.soft‐go.com/get/Samsung‐Kies_79632.html isn't working. Not sure if the site is just down right now or if there's a mistake.
Click to expand...
Click to collapse
Thank you I didn't actually add that link it was from systoxity, but i will fix it.
nbs11 said:
Thank you I didn't actually add that link it was from systoxity, but i will fix it.
Click to expand...
Click to collapse
I Fixed it
A few small things:
Intel should be intel.
Under CPU Optimization:
"Samsung’s CPU is set by default the run at 1gHz."
The should be to.
Sideloading:
"(don’t forget that after you install it from the market you still have to go to your app drawer and run busybox once so it installs)."
Should this be after you download it from the market?
ClockworkMod Recovery:
"ClockworkMod written for us by a developer that goes by the name of Koush"
Missing is.
"This gent puts a ton of work into helping us captivate owners out"
Replace puts with put and Capitalize Captivate.
Changing Your Messaging Ringtone:
"well the ones that matter anyway.."
Extra period.
Other than that, excellent guide. I'll definitely be using it when my Captivate arrives.
Rad_Fishy said:
A few small things:
Intel should be intel.
Under CPU Optimization:
"Samsung’s CPU is set by default the run at 1gHz."
The should be to.
Sideloading:
"(don’t forget that after you install it from the market you still have to go to your app drawer and run busybox once so it installs)."
Should this be after you download it from the market?
ClockworkMod Recovery:
"ClockworkMod written for us by a developer that goes by the name of Koush"
Missing is.
"This gent puts a ton of work into helping us captivate owners out"
Replace puts with put and Capitalize Captivate.
Changing Your Messaging Ringtone:
"well the ones that matter anyway.."
Extra period.
Other than that, excellent guide. I'll definitely be using it when my Captivate arrives.
Click to expand...
Click to collapse
Thanks! I fixed all those errors but I'm not gonna upload the new version just yet because I will keep finding more errors so it just seems wasteful. I did not actually write most of the guide myself I just formatted it so there may be some mistakes I didn't pick up on.
i used this guide today and it delivered.
orlandoxpolice said:
i used this guide today and it delivered.
Click to expand...
Click to collapse
If there was anything you found difficult or anything you would like to change just tell me and I will add it to tonight's update.
Hi,
Thanks for publishing this. It looks very useful, similar to Energy ROM.. But I am very new to Android phones (trying this on Samsung Captivate from AT&T, bought yesterday). I am running windows 7 ultimate 64bit and I exactly followed this guide. But somehow I am still not able to see the sd card. I tried placing the update.zip at Computer\SGH-I897\Phone and shut down the phone and tried restarting the phone by holding the up/down keys as well as power button. But after selecting reinstall packages it said could not find /sdcard/update.zip.. Pls held. Again very sorry if I did some mistake..
ask_j said:
Hi,
Thanks for publishing this. It looks very useful, similar to Energy ROM.. But I am very new to Android phones (trying this on Samsung Captivate from AT&T, bought yesterday). I am running windows 7 ultimate 64bit and I exactly followed this guide. But somehow I am still not able to see the sd card. I tried placing the update.zip at Computer\SGH-I897\Phone and shut down the phone and tried restarting the phone by holding the up/down keys as well as power button. But after selecting reinstall packages it said could not find /sdcard/update.zip.. Pls held. Again very sorry if I did some mistake..
Click to expand...
Click to collapse
The SD card is simply the root directory of your phone. You do not need to open a folder, it is the highest folder you can place it in. Hope that helps
Somehow it was not able to find the sdcard root. Then I realized that you mentioned something called as Droid Explorer, I searched for it and installed it on my PC. But when I opened Droid Explorer, my device was not recognized, then I clicked on link on the explorer window, upon watching that video I enabled the USB Debugging, then I was able to see my device, then I selected connect to my device. After that I saw an explorer but it had empty root and I was not able to copy anything. There was a menu button at the top row named "Transfer to device or Copy to device" I selected that and selected update.zip file and tried to transfer. Something happened but still explorer was empty. Then from my phone Top slide down menu I selected mount USB storage and I started seeing windows explorer on my PC. Then apart from other folders I could see a folder sd in the root. Then I again put update.zip in the root.
Then followed the restart sequence, this time it found the file but exited after Signal 7. It was trying to asert something but could not find the correct model number I guess. My cell phone's model number is Samsung i897.
Please help
ask_j said:
Somehow it was not able to find the sdcard root. Then I realized that you mentioned something called as Droid Explorer, I searched for it and installed it on my PC. But when I opened Droid Explorer, my device was not recognized, then I clicked on link on the explorer window, upon watching that video I enabled the USB Debugging, then I was able to see my device, then I selected connect to my device. After that I saw an explorer but it had empty root and I was not able to copy anything. There was a menu button at the top row named "Transfer to device or Copy to device" I selected that and selected update.zip file and tried to transfer. Something happened but still explorer was empty. Then from my phone Top slide down menu I selected mount USB storage and I started seeing windows explorer on my PC. Then apart from other folders I could see a folder sd in the root. Then I again put update.zip in the root.
Then followed the restart sequence, this time it found the file but exited after Signal 7. It was trying to asert something but could not find the correct model number I guess. My cell phone's model number is Samsung i897.
Please help
Click to expand...
Click to collapse
I did not write the PC instructions, so I can not help you (I only have a Mac). But the person who did can probably help you his username is systoxity.
Because not enough errors were found to make it worthwhile to update the PDF i will wait till tomorrow to fix the minor errors.
Good source of information
Thank you for putting this together. I am going to sticky this for the time being.
For installing the latest version of busy box, you should include that before the instructions for running titanium backup...the latest version of busybox installed from the market will work with titanium backup so theres no need to have to click the "problems" button...this way you wont have to do the busybox download step twice...should also save a few megs since titanium backup wont have its own copy of busybox installed BTW nice guide
You can also just mount the phone memory using windows explorer and move the file over. I was never able to get droid explorer to transfer the file. It always said it went but then was never there.
Anyway all I did was connected just as I was going to connect to kies but then when windows asked me what I wanted to do I clicked on open file view and dropped updated.zip on my phone.
Only issue that I had with rooting was I accidentally opened the file in windows(winrar). After I moved the file over it found it and attempted to install it but then exited with an error(do not remember exact error), but had to do with mounting. Anyway I re-downloaded file and saw file size was different. After I moved the file over again everything went great. I still haven't removed bloat-ware and such but thats next on the agenda.
Also I was on windows 7 64 bit, saw some other users in other threads saying they had issues connecting the phone. Everything so far has worked great for me
Thank you very much for this handy pdf file!
Somelinks aren't working
First of all I have to say very good guide for noobs!
1. when I downloaded the update.zip folder I didn't work I guess because the name of Samsung captivate is not in the folder or something. So I just downloaded the other file from the forums.
2. Link to CPU optimization doesn't work.
3. I downloaded the droid explorer. It connected to my phone but I was unable to transfer anything. So I just tapped on the USB connected in the notification bar and mounted the phone. This allowed me to use windows explorer to transfer files. I believe one can transfer files by selecting the option of Samsung Kies under USB settings.
I got all your feedback. It will all be corrected by tomorrow night.
Cool guide however the rumor is the GPS only gets turned on when pulling up an App that uses it, so that step in the "battery saving" section might not be necessary.
Also you may want to replace Market Enabler with Market Access. It's a rehash of Market Enabler but also has a Set on Boot option that keeps it persistent versus being reset each time.
You also Might want to add a Tips/Tricks Section..
Here You can put some cool tips like the one i found out about backlight control.
(found here: http://forum.xda-developers.com/showthread.php?t=735394 )
I can't really take credit for this, but I just restored my IMEI without a backup of the efs folder. Keep in mind that I actually deleted my efs folder by accident, so I didn't even have the original efs folder.
The original thread I referenced is here:
http://forum.xda-developers.com/showthread.php?p=31771228#post31771228
FYI, this method will restore your phone to stock Gingerbread.
Here is what you do:
1.)
A) Download and unzip the Gingerbread unbrick package here from (http://forum.xda-developers.com/showthread.php?p=27286083#post27286083):
w/ root - http://d-h.st/ewu
w/o root - http://d-h.st/G6g
B)
Download and unzip the efs zip here:
http://forum.xda-developers.com/attachment.php?attachmentid=1152914&d=1340558510
2.) Place phone in download mode.
3.) If needed, install latest Samsung USB drivers by installing Samsung Kies from HERE.
4.) Open the included Odin exe.
5.) If phone is detected, the window under ID:COM will turn yellow.
6.) Click on "PIT" to browse to and select infuse_gb.pit. Make sure that Re-Partition is selected.
7.) Click on "PDA" to browse to and select PDA_UCLB3.tar.md5.
8.) Click on "PHONE" to browse to and select PHONE_UCLB3.tar.md5.
9.) Click on "CSC" to browse to the efs.tar
10.) Click the Phone EFS Clear checkbox
11.) Click on "Start", and allow Odin to flash the phone. Do not unplug or power off the phone until Odin is finished.
12.) When the Odin dialogue reads "PASS!", the phone should reboot into the stock UCLB3 Setup Wizard. For me this step just proceeded to install an update and the reboot the phone.
Once the phone reboots, if your SIM card is installed you should be good to go, otherwise you will get an alert about your SIM card which means you need to power off and pop in the SIM card.
Thanks to the original thread author for this one.
It works perfect for me even without the .nv_data file. Before this i only get simbols instead the imei number. You save my phone!
recovered IMEI by just flashing the CM10 base
I dunno if it's just me or what. I lost my IMEI on Slim Bean.. so I had this thought. I hadn't had this issue with the CM10 rom, so I decided to do the standard flashing procedure. Once CM10 was installed my IMEI came back. I had full signal and all is good. I decided to go back to Slim Bean to see if it would fix the IMEI issue. I flashed it just like the OP stated and walah! I had my IMEI back and everything worked without having to go back to GB, ICS and then JB again. I don't know if this will help anyone, but just wanted to note other people about it. Why did this work for me?
will this mess up my phone more?
I am running froyo 2.2.1 ,I guess it is stock, as I pick this phone up in pawn shop, and it was already rooted. I was doing the command line argument dd and a bunch of stuff, to get some file to get my unlock code. I didn't get no bak file copy, gave up put my sim card back in and that's when I noticed my imei was gone, then I had go launcher installed, so my screen goes blank I end up having to do the three finger data wipe, then I see I got no wifi either. Then I get this phone, DL some apk files, try to reinstall busy box, no go, teller me it don't think it has su permission after I gave it through that super user program, then it say it cant install into /dev/sh/ what ever, so all I got is a really nice looking video player.
So now that I got all that out of me.
2 questions, will flashing gingerbread overtop of froyo, will not make it worse?
Why do one have to flash in the first place, why can't one just copy over the old-time files, or someone find which file goods the imei number then just to in isinglass a file manager open that file, as it should be just what is caller a flat file, meaning no special formating like a Word file.
Then just save it. I am not an expert at android wse (whatsoever) but I have played with copying over top of files, or deleting the old-time one then replacing it with a new one. Why Doesn't that work, has anyone player around just opening there files to see what they look like and figure out where they stick the imei number?
Seems to me should be an easy manner of doing, but now that I don't have an individual showing I am not even sure which file I should try to type that number in to to see what will happen as I don't want to make this phone completely useless.
Any commentary, ideas, anything?
Thanks
MikieD
mikied12 said:
I am running froyo 2.2.1 ,I guess it is stock, as I pick this phone up in pawn shop, and it was already rooted. I was doing the command line argument dd and a bunch of stuff, to get some file to get my unlock code. I didn't get no bak file copy, gave up put my sim card back in and that's when I noticed my imei was gone, then I had go launcher installed, so my screen goes blank I end up having to do the three finger data wipe, then I see I got no wifi either. Then I get this phone, DL some apk files, try to reinstall busy box, no go, teller me it don't think it has su permission after I gave it through that super user program, then it say it cant install into /dev/sh/ what ever, so all I got is a really nice looking video player.
So now that I got all that out of me.
2 questions, will flashing gingerbread overtop of froyo, will not make it worse?
Why do one have to flash in the first place, why can't one just copy over the old-time files, or someone find which file goods the imei number then just to in isinglass a file manager open that file, as it should be just what is caller a flat file, meaning no special formating like a Word file.
Then just save it. I am not an expert at android wse (whatsoever) but I have played with copying over top of files, or deleting the old-time one then replacing it with a new one. Why Doesn't that work, has anyone player around just opening there files to see what they look like and figure out where they stick the imei number?
Seems to me should be an easy manner of doing, but now that I don't have an individual showing I am not even sure which file I should try to type that number in to to see what will happen as I don't want to make this phone completely useless.
Any commentary, ideas, anything?
Thanks
MikieD
Click to expand...
Click to collapse
This is either a joke or a joke.
Many Thanks
zackdjones said:
I can't really take credit for this, but I just restored my IMEI without a backup of the efs folder. Keep in mind that I actually deleted my efs folder by accident, so I didn't even have the original efs folder.
The original thread I referenced is here:
http://forum.xda-developers.com/showthread.php?p=31771228#post31771228
FYI, this method will restore your phone to stock Gingerbread.
Here is what you do:
1.)
A) Download and unzip the Gingerbread unbrick package here from (http://forum.xda-developers.com/showthread.php?p=27286083#post27286083):
w/ root - http://d-h.st/ewu
w/o root - http://d-h.st/G6g
B)
Download and unzip the efs zip here:
http://forum.xda-developers.com/attachment.php?attachmentid=1152914&d=1340558510
2.) Place phone in download mode.
3.) If needed, install latest Samsung USB drivers by installing Samsung Kies from HERE.
4.) Open the included Odin exe.
5.) If phone is detected, the window under ID:COM will turn yellow.
6.) Click on "PIT" to browse to and select infuse_gb.pit. Make sure that Re-Partition is selected.
7.) Click on "PDA" to browse to and select PDA_UCLB3.tar.md5.
8.) Click on "PHONE" to browse to and select PHONE_UCLB3.tar.md5.
9.) Click on "CSC" to browse to the efs.tar
10.) Click the Phone EFS Clear checkbox
11.) Click on "Start", and allow Odin to flash the phone. Do not unplug or power off the phone until Odin is finished.
12.) When the Odin dialogue reads "PASS!", the phone should reboot into the stock UCLB3 Setup Wizard. For me this step just proceeded to install an update and the reboot the phone.
Once the phone reboots, if your SIM card is installed you should be good to go, otherwise you will get an alert about your SIM card which means you need to power off and pop in the SIM card.
Thanks to the original thread author for this one.
Click to expand...
Click to collapse
I just wanted to thank all of you who have contributed your brain power to the xda forums. This advise worked great and after a lot of self doubt I now consider myself a semi-noob. Thanks again.
A J
Thanks on this. I had a backup of my EFS folder, but the tool I used to create it made a .img file and once I got it into JB, the tool didnt work. UGH.
Just want to say thank you for posting this. I have a friend who had her Infuse stop getting calls, texts, etc. Turns out her IMEI was all question marks and other invalid characters. ATT wouldn't help her at all and either did a full reset.
thank you, this method really works!! finally my imei is back...no more symbols, now is time for a efs back up
Since when do phones lose their imei's? That's a new one on me.
sholsten said:
Since when do phones lose their imei's? That's a new one on me.
Click to expand...
Click to collapse
It happened for me twice on two separate phones when using MIUI. Basically the ROM managed to corrupt the system partition, specifically the efs folder.
I don't know the specifics of why, but it happens to a lot of people. That's why I always now make sure I have a backup of the efs just in case.
Sent from my SAMSUNG-SGH-I717 using xda premium
zackdjones said:
It happened for me twice on two separate phones when using MIUI. Basically the ROM managed to corrupt the system partition, specifically the efs folder.
I don't know the specifics of why, but it happens to a lot of people. That's why I always now make sure I have a backup of the efs just in case.
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
This method didn't work for me :\ Any other ways to solve this issue?
can i use this Efs on galaxy R to repair unknown baseband & Blank imei????
Thank you very much. This is what I need
worked great. thank you.
zackdjones said:
I can't really take credit for this, but I just restored my IMEI without a backup of the efs folder. Keep in mind that I actually deleted my efs folder by accident, so I didn't even have the original efs folder.
The original thread I referenced is here:
http://forum.xda-developers.com/showthread.php?p=31771228#post31771228
FYI, this method will restore your phone to stock Gingerbread.
Here is what you do:
1.)
A) Download and unzip the Gingerbread unbrick package here from (http://forum.xda-developers.com/showthread.php?p=27286083#post27286083):
w/ root - http://d-h.st/ewu
w/o root - http://d-h.st/G6g
B)
Download and unzip the efs zip here:
http://forum.xda-developers.com/attachment.php?attachmentid=1152914&d=1340558510
2.) Place phone in download mode.
3.) If needed, install latest Samsung USB drivers by installing Samsung Kies from HERE.
4.) Open the included Odin exe.
5.) If phone is detected, the window under ID:COM will turn yellow.
6.) Click on "PIT" to browse to and select infuse_gb.pit. Make sure that Re-Partition is selected.
7.) Click on "PDA" to browse to and select PDA_UCLB3.tar.md5.
8.) Click on "PHONE" to browse to and select PHONE_UCLB3.tar.md5.
9.) Click on "CSC" to browse to the efs.tar
10.) Click the Phone EFS Clear checkbox
11.) Click on "Start", and allow Odin to flash the phone. Do not unplug or power off the phone until Odin is finished.
12.) When the Odin dialogue reads "PASS!", the phone should reboot into the stock UCLB3 Setup Wizard. For me this step just proceeded to install an update and the reboot the phone.
Once the phone reboots, if your SIM card is installed you should be good to go, otherwise you will get an alert about your SIM card which means you need to power off and pop in the SIM card.
Thanks to the original thread author for this one.
Click to expand...
Click to collapse
1stly thanks a lot for this thread. Really millions of thanks.
Now one silly question:- I unzipped the efs file attached and it says "efs.rfs" but your instructions above says "efs.tar" needs to be selected under CSC option. Am I missing something?
Punnyabrata said:
1stly thanks a lot for this thread. Really millions of thanks.
Now one silly question:- I unzipped the efs file attached and it says "efs.rfs" but your instructions above says "efs.tar" needs to be selected under CSC option. Am I missing something?
Click to expand...
Click to collapse
Strange things are happening to me.
About 2 weeks back this problem started and today when I reconnected the SIM and restarted the phone everything was back to normal. Phone is picking up signal/3G etc.
Surprised is the word. Leads me to believe some app must be responsible for all of this.
Thanks,
PC
It is showing invalid mds sum...what I do?
At the end of the task odin shows blue screen and show fail.
Now my phone doesnt get start..what I do?
sachinppatel16 said:
At the end of the task odin shows blue screen and show fail.
Now my phone doesnt get start..what I do?
Click to expand...
Click to collapse
Have you tried Odin as administrator ? that's might be the problem
It's actually super-super easy to root.
You have to make sure you:
Have access to the sdcard, either through ADB or a adapter to your computer.
If phone is locked, use an AT&T sim. If unlocked, and using another carriers sim, must have APN info
Have data working on the phone, either wifi or from the carrier. You also must have a Google account to download/install 2 programs from Play Store
Now, I use T-Mobile, and my data speed here is GPRS..Yep, not even dialup speeds. During the unlock process I was following, my wifi mac address got screwy (If, when trying to enable wifi, it keeps shutting off, you may have same issue)
But, I'll also show how to fix that, too.
The following HOWTO does NOT require ADB, but it can make life easier for you. I always enable it at first boot.
The sections in Green are for everybody
The sections in Blue are if, like me, you have no wifi
** This WILL work for the AT&T Avail ZTE-Z990 (MIGHT work for the Z990g Merit. I don't have one, so proceed at your own risk ). It may work on your phone. It may not.
** If you follow this, and you 'brick your phone', start World War III, or your hair falls out, IT'S YOUR PROBLEM, NOT MINE.
Hit the dialer on your phone. Dial *983*7668# (DO NOT PRESS THE GREEN SEND BUTTON)
After the little text saying something about root, go to the Google Play Store, and search for "Superuser". The first on the list you want to install
After Superuser installs, start it, and go to the FAR LEFT, and find where it says "Tap here" for updating. Let it update. If it doesn't, reboot the phone, try again
If you get an error about the * code, you may have a newer update from your carrier installed. Google search for "TCard z990", and reflash for the older rom. The *code will work then.
You got root, Really, It's THAT easy
Now for 'goofy wifi'
After Superuser is up and running, get "Absolute System Root Tools" from the Play Store, and install it.
When you run the program, it should have a dialog from Superuser to allow access. If not, reboot, try again
At the top of ASRT, tap "File Browser", navigate to "/system/etc"
Find the file 'nv_4319.txt', and tap it.
Scroll down to two lines that have "macaddr" in them. One has a '#' infront of it. Swap the '#' from the front of that line to the front of the other 'macaddr'
Press Menu button, and save. Back out of ASRT, and go to the wifi settings. Turn your wifi off, then back on. You should be able to connect to wifi now.
That's about it.
Now if we can just get some headway with a Cyanogen ROM for this thing....
i just rooted and then modified the nv_4319.txt file. i did install superuser but i dont think is needed, no permission was asked. instead of ASRT, any root file explorer with built-in text editor will work. i used root explorer.
el_venga said:
i just rooted and then modified the nv_4319.txt file. i did install superuser but i dont think is needed, no permission was asked. instead of ASRT, any root file explorer with built-in text editor will work. i used root explorer.
Click to expand...
Click to collapse
Better install SuperUser
Why? Because, if you don't, EVERYTHING has su access ALL THE TIME. The Superuser app limits this.
nv-4319 edited but still nothing
i tried your method and edited the file successfully but my wifi still stays white and when i attempt to turn it on it simply flashes and returns to the same error message. i rooted my device successfully several months ago and wifi worked fine until i used the trev e mod tethering app which worked well once, however neither wifi or tethering have worked since. any other suggestions are welcome, and thanks in advance.
Rooting and installing Google Play on the Proscan PLT7035-PL ** UPDATED **
*** Disclaimer ***
I am not responsible for bricked tablets, voided warranties, crashed computers and/or global thermonuclear war! This is what worked for me if you are unsure of anything in the following steps STOP NOW! There is no factory rom released for this tablet. If you brick it your possibly stuck until if and when they release an update!
These instructions assume you are competent to do the folling: get files on and off of your device using the mass storage driver, able to edit and understand changes to inf files, use command prompt, edit system user files and have enough patence to read all of the steps without skipping any. There are a few gotcha's that if are skipped will leave you pulling your hair out. Also these instructions are written for Windows. If your using Linux you shouldn't need my help anyways ..
Click to expand...
Click to collapse
This tutorial may also work on other Chinese generic tablets. You would only need get the hardware vendor and product ID's from the device info for step 2. For the purpose of this post I wont be getting into that but the information is out there.. GOOGLE IS YOUR FRIEND
Introduction
Its likely if you are reading you have recently visited Big Lots and scored a $69 7" tablet. Only to get home and find virtually NO information on rooting it or installing Google Play or GAPPs. I know I was in that boat but after a few hours of messing around I got it. I am writing this to hopefully help the hundreds of others I see out there asking for help on this.
Step 1 Download Stuff (Things to round up before you even think about starting)
Root with Restore by Bin4ry v15 - http://forum.xda-developers.com/showthread.php?t=1886460 .** UPDATE ** I attached the version I used to this post
ADB Drivers - You have several options here, milage may very.** UPDATE ** I attached USB drivers to this post. I had to seperate the 64 and 32 bit drivers to get the files under the 8 mb limit for uploads
install android SDK http://dl.google.com/android/android-sdk_r21-windows.zip and follow instructions to get the google usb drivers. Search XDA there are several guides, I couldn't find the one I used as of writing this article but there are many out there.
Search google and find a zip with just the ADB drivers.
Download Super One Click Root and use the drivers in the tools directory of the zip. http://forum.xda-developers.com/showthread.php?t=803682
Root Explorer - quick way to move and remount file systems rw with ease. I used v2.13.1. Google around and find an APK to install, just be careful there is another completely differnent package out there called "rooted explorer" it may work but I have not tried it. ** UPDATE ** I attached the version I used to this post
Google Apps for ICS - gapps-ics-20120429-signed.zip is what I used from http://goo.im/gapps/gapps-ics-20120429-signed.zip ** Update ** I replaced the URL with a direct download link from goo.im enjoy!
**NOTE** SUPER ONE CLICK ROOT WILL NOT ROOT YOUR TABLET SO DON'T BOTHER TRYING!
Step 2 install and configure your ADB USB Drivers (Let the fun begin)
Extract your zip file containing the ADB USB drivers or Install the Android SDK and follow instructions on how to use the SDK manager to download the lastest drivers from google.
Once downloaded edit the inf file (usually named android_winusb.inf)
Add the following under the [Google.NTx86] heading and again under the [Google.NTamd64] heading: (one is for 32bit systems and the other is for 64 bit Systems)
Code:
;ProScan plt-7035
%SingleAdbInterface% = USB_Install, USB\VID_2207&PID_0010
%CompositeAdbInterface% = USB_Install, USB\VID_2207&PID_0010&REV_0222&MI_01
After saving and exiting. Turn on USB Debugging on your tablet. It is under Settings => Developer Options and is the first option at the top make sure it has a check in the checkbox. Exit the developer screen by pressing back or the home key and plug in your tablet to a usb port on your computer using a micro-USB cable.
Device detection should at this point detect a few devices but at least 1 will fail without drivers. Possibly more on XP systems..
Under Device Manager => Other Devices you should have a device called "PLT7035-PL" use the usb drivers modifed above to install the ADB USB Drivers.
*** Important Note ***
At this point even with the ADB Driver installed ADB will not see the tablet. We have to create or edit the file c:\users\whatever your username is\.android\adb_usb.ini
If you have already run ADB at any time on your system the file and directory should already exist. If not you will need to create the directory and the file.
on a single line simply add this to a blank line in the file and save and exit:
0x2207
This tells ADB to look for that vendor code. (if you allready have ADB on your computer 'adb devices' should now show your tablet.
** UPDATE ** This is still necessary even if using the drivers attached to this post!
Click to expand...
Click to collapse
Step 3 Root your Tablet!
*** Warning ***
I almost bricked my tablet on this step due to an error with a faulty PlayStore I had tried to install just using the APK. It kept the tablet from rebooting properly during the root process! I recommend erasing all user data before continuing YOU HAVE BEEN WARNED!
Click to expand...
Click to collapse
Extract Root with Restore by Bin4ry v15 to the directory of your choosing.
From explorer on your pc double click the RunMe.bat and select option one.
This particular root uses the system restore function to gain root access. If everything goes right you should get a prompt on the table to restore an image.
Click to expand...
Click to collapse
Press restore ON THE TABLET without entering a password or changing anything else and after a minute or two (maybe more) it should reboot.. Do some more stuff then reboot one more time and you should now have a rooted tablet.
Step 4 Copy root explorer and gapps-ics-20120429-signed.zip to the internal storage of the tablet.
Make sure the tablet is plugged into your computer and turn On USB Storage.
Copy rootexplorer.apk and gapps-ics-20120429-signed.zip to the Downloads folder via windows explorer and the removeable drive from the tablet.
Step 5 Install root explorer
ON THE TABLET: to applications => explorer => Internal memory => Download => rootexplorer.apk
This should bring up the apk installer and ask for permission to install rootexplorer. Follow the prompts until rootexplorer is installed.
Open root explorer. The first time you open it if everything is right you should get a prompt from SU to allow root access, hit grant. After that you might get a message that you need to close and reopen root explorer again, this is completely normal.
Step 6 Remount File Systems r/w
Once root explorer is open and has root access you should be in the root directory of the device.At the top you should see a message that says "Mounted as r/o" and a button to the right of it that says "mount as r/w".
Click to expand...
Click to collapse
Click the button to mount / as rw.
The message at the top should change to "mounted as r/w" and the button should change to "mount as r/o"
Click to expand...
Click to collapse
Scroll to the system folder and open it.
At the top you should see a message that says "Mounted as r/o" and a button to the right of it that says "mount as r/w".
Click to expand...
Click to collapse
Click the button to mount /system as rw.
The message at the top should change to "mounted as r/w" and the button should change to "mount as r/o"
Click to expand...
Click to collapse
Now click on the ../ Parent Folder icon on the top to go back to the root directory,
Step 7 Extract GAPPS
Scroll to and tap sdcard
Scroll to and tap Download
You should see the google apps file we copied earlier.
Click to expand...
Click to collapse
tap and hold on gapps-ics-20120429-signed.zip until the menu comes up and select "extract all" this will extract the zip file to /sdcard/extracted/gapps-ics-20120429-signed/
Step 8 Copy Google APPS to /system
Scroll to and TAP .. Parent folder at the top to go back a directory to /sdcard/
Scroll to and TAP extracted
Scroll to and TAP gapps-ics-20120429-signed
You should see 5 items, install-optional.sh, META-INF, optional, system and the ../ Parent Folder link.
Click to expand...
Click to collapse
*** WARNING *** Do not click on the install-optional.sh bad things might happen!
Click to expand...
Click to collapse
TAP and hold on the system folder until the menu comes up and select copy.
This will place a paste button on the bottom of the screen be careful not to hit it yet or you will have problems.
Click to expand...
Click to collapse
TAP ../ Parent Folder until the directory at the top says / (you should have to go back 2 or 3 folders)
You should now see a bunch of folders in the root directory as well as the tablets system folder. There should NOT be a ".. Parent folder" visible.
Click to expand...
Click to collapse
Now hit the paste button on the bottom left. You should get a warning massage saying "system already exist. Do you want to overwrite it?" hit yes
The file copy takes 1 to 2 minutes when it is done all that is left is to remount the / and /system folders r/o and reboot the tablet
Click to expand...
Click to collapse
Step 9 Remount file systems r/o
At the top you should see a message that says "Mounted as r/w" and a button to the right of it that says "mount as r/o".
Click to expand...
Click to collapse
Click the button to mount / as ro.
The message at the top should change to "mounted as r/o" and the button should change to "mount as r/w"
Click to expand...
Click to collapse
Scroll to and TAP system
At the top you should see a message that says "Mounted as r/w" and a button to the right of it that says "mount as r/o".
Click to expand...
Click to collapse
Click the button to mount /system as ro.
click the back icon on the bottom left until you have exited root explorer.
Press the power button on the top of the tablet and turn it off and back on.
If everything went right you should now have a fully functioning rooted tablet with Google Playstore...
Click to expand...
Click to collapse
WASN'T THAT FUN!!?!?!
Ive tried this several times. It hasn't worked yet. Maybe I am doing it wrong, not sure. Ill keep trying but I am losing hope.
I am trying with a Proscan PLT7035-PL
worked ... Many thanks to amjtech ...
Here's how to do it:
Install Android SDK, then install Android SDK Tools, Android SDK Platform-Tools, Google USB Driver (download from google)
Install PdaNet for Android on PC.
Attach Proscan pad, check Settings->Developer options->USB debugging to on
XP install adb driver - if unsuccessful, need modify registry
regedit under HKLM/SYSTEM Permissions -> Advance, check replace permission entries on all child
(http://www.tomshardware.com/forum/252428-45-installation-failed-access-denied)
Install USBDeview, run to see usb device attached, get device ID of PROSCAN pad (0x2207)
Add device ID to file adb_usb.ini in c:\docume~1\<user>\.android, also add google's id:
0x2207
0x18d1
(http://forum.xda-developers.com/showthread.php?t=1479311)
(http://androidforums.com/kindle-fir...k-how-get-adb-running-root-superoneclick.html)
Now device will show running
Install ICS Root Unlocker 1.0, run ... got rooted.
Download Root Explorer (2.21.1).apk, Google Play Store (3.8.16).apk, and gapps-ics-20120429-signed.zip from 4shared
http://www.4shared.com/folder/k86VyEKK/_online.html
follow the rest of the instruction (http://forum.xda-developers.com/showthread.php?t=1993013)
... reboot proscan ... voila !!!
Help me!! please!!
I pushed the reset button then right now it's stay at recovery mode ever and I don't what firmware name it's using.. Someone help me find the link to download firmware and teach me how to restore it!! thanks very, very much!!
Factory ROM
tnan0906 said:
I pushed the reset button then right now it's stay at recovery mode ever and I don't what firmware name it's using.. Someone help me find the link to download firmware and teach me how to restore it!! thanks very, very much!!
Click to expand...
Click to collapse
Unfortunately as stated above there is no factory rom available for these tablets yet... I am looking into using rkflash or rkflashtool to download my rom prerooted so I have a backup and also can post a rooted rom for everyone. Most likely later this week I should have some time to figure out the rkflashtool and get it dumped.
I will post it here once it is done.
I'm going to say this now. I have a very busy schedule so I cannot guarantee when I will get this accomplished.
Also if this works for you please hit the thanks button.
Stuck
Humphrey1989 said:
Ive tried this several times. It hasn't worked yet. Maybe I am doing it wrong, not sure. Ill keep trying but I am losing hope.
I am trying with a Proscan PLT7035-PL
Click to expand...
Click to collapse
How far are you getting? Were you able to get root?
Rom Backup
amjtech said:
Unfortunately as stated above there is no factory rom available for these tablets yet... I am looking into using rkflash or rkflashtool to download my rom prerooted so I have a backup and also can post a rooted rom for everyone. Most likely later this week I should have some time to figure out the rkflashtool and get it dumped.
I will post it here once it is done.
I'm going to say this now. I have a very busy schedule so I cannot guarantee when I will get this accomplished.
Also if this works for you please hit the thanks button.
Click to expand...
Click to collapse
Thanks thanks thanks!! Please upload your backup from you for me! I think it will work because same products!! please as soon as possible!! Thanks you, thanks you very very much!!!
Confused as heck !!
OK, I am confused as heck here. I have the SDK installed. I have the USB Drivers installed. The PC sees the phone just fine, I can browse the internal storage and the external sd card with no problem. Windows XP Device Manager shows Android Phone, and under that the Android Composite ADB Interface.
PDANet works with the phone, no problem. However, adb devices never shows the device, and the Root program cannot find it either. At this point, I'm stumped. Any ideas what I need to do? I have put the android_usb.ini file in c:\Documents and Settings\myusername\Android with the necessary hex codes for the device and for Google. I'm going nuts here!
I know ADB is installed properly, because I can plug my phone into the PC and run adb devices, and it's detected just fine. It's just this tablet it can't find.
FIX: Not as obvious as it might have been, but here is the solution to my problem. I used the Search function to find the adb_usb.inf file - umm... it's in .android, not android. Once I added those ids, everything was fine.
No Market?
Achieved root, copied over the system folder from the zip, but no market. Did I miss something?
What about Recovery?
Just wondering if there is a recovery option as yet? That would be so helpful!
---------- Post added at 08:13 AM ---------- Previous post was at 07:28 AM ----------
spycom773469 said:
Achieved root, copied over the system folder from the zip, but no market. Did I miss something?
Click to expand...
Click to collapse
Yeah, this happened to me too. And for some reason, when you go to the \system folder and look in apps there is another apps folder in there. I think there is something really odd going on with root manager possibly. I don't know what the deal is, but none of the Google Apps are running.
I've tried several older 4.0.x versions of GAPPS, and I will be danged if I can get any of them to work. I'm rooted OK, but that's all that worked thus far.
Good instructions! But failure... and then success
The instructions were great above! The pointer to the version of google play was bad, but I found this link http://forum.xda-developers.com/showthread.php?t=1934441 and after using Root explorer to do the appropriate permissions at / and /system, and on the renamed file, it works!
---------- Post added at 06:17 AM ---------- Previous post was at 06:06 AM ----------
Now that I got Google Play to work...
I am having an odd problem however - the installation of apps stalls at 0% for about 30 seconds, and then continues. And as the percentage is updated, I see app screens cycling. And little google play shopping bags start to stack up in my "task tray" area of the tablet.
Does anybody else have that problem? It's very annoying! It seems like the downloaded apps not only install but open, eating up precious memory.
Speaking of which, how is the flash memory used? (4 GB), and not having apps take up the 500 MB that's available?
jmasters said:
Speaking of which, how is the flash memory used? (4 GB), and not having apps take up the 500 MB that's available?
Click to expand...
Click to collapse
It is 4GB shared. I haven't tried looking at the partition table.
There is only 2GB usable, it's on the TF card, I moved the apps there.
Not sure how to access the SD card to put apps there.
netizenmt said:
Yeah, this happened to me too. And for some reason, when you go to the \system folder and look in apps there is another apps folder in there. I think there is something really odd going on with root manager possibly. I don't know what the deal is, but none of the Google Apps are running.
I've tried several older 4.0.x versions of GAPPS, and I will be danged if I can get any of them to work. I'm rooted OK, but that's all that worked thus far.
Click to expand...
Click to collapse
My GAPPS are working fine. I thought about killing that /system/system folder and manually placing the files via adb.
Try checking the permissions too, I think they need to be 644 or better.
I've put the Tablet away for now, I will tinker again later probably.
Sent from my DIRTY Jelly Bean EVO 3D
How to move apps internally to TF card?
spycom773469 said:
It is 4GB shared. I haven't tried looking at the partition table.
There is only 2GB usable, it's on the TF card, I moved the apps there.
Not sure how to access the SD card to put apps there.
How do you move your apps there? I'm aware of the app called something like app2SD, but the TF card isn't an SD card.
Click to expand...
Click to collapse
jmasters said:
spycom773469 said:
How do you move your apps there? I'm aware of the app called something like app2SD, but the TF card isn't an SD card.
Click to expand...
Click to collapse
If you go to the Apps tab under the system settings you will see a button that says "Move to TF Card"
Sent from my DIRTY Jelly Bean EVO 3D
Click to expand...
Click to collapse
netizenmt said:
Just wondering if there is a recovery option as yet? That would be so helpful!
---------- Post added at 08:13 AM ---------- Previous post was at 07:28 AM ----------
Yeah, this happened to me too. And for some reason, when you go to the \system folder and look in apps there is another apps folder in there. I think there is something really odd going on with root manager possibly. I don't know what the deal is, but none of the Google Apps are running.
I've tried several older 4.0.x versions of GAPPS, and I will be danged if I can get any of them to work. I'm rooted OK, but that's all that worked thus far.
Click to expand...
Click to collapse
You have to extract the zip file, remount the file systems as rw and copy the /system folder from the zip into the / of the device so that all the files goto their proper places... if you have /system/system it was not copied correctly...
as far as those not getting ADB to reconize the tablet.. a) make sure you have usb debugging turned on and b) you put the hardware id in the adb_usb.ini file.. See the ** important note ** in Step 2!
Unzipping Files
I have read and followed your directions to download the files, but, my unit keeps saying it can not open any zip files.
Do you have any idea why it may say this or how to get around this problem so I can continue as instructed?
unzip on your computer and transfer over, or use root explorer
bluetxsteel said:
I have read and followed your directions to download the files, but, my unit keeps saying it can not open any zip files.
Do you have any idea why it may say this or how to get around this problem so I can continue as instructed?
Click to expand...
Click to collapse
You can unzip them on your computer and then transfer them over, or use root explorer on your tablet. You'll have to hold your finger on the .zip file for a few seconds and then the unzip option pops up.
Well, everyone be careful! When my Google Play would not install properly, I tried to clean the tablet up, ie, put it back to its original condition. Somehow, I managed to cause something to crash, and from then on, the tablet won't boot past the Android startup screen, although I can adb into it and it is still rooted, etc. What I've got now is a project tablet - HOW TO UNBRICK THE BRICK.
my bricked too
netizenmt said:
Well, everyone be careful! When my Google Play would not install properly, I tried to clean the tablet up, ie, put it back to its original condition. Somehow, I managed to cause something to crash, and from then on, the tablet won't boot past the Android startup screen, although I can adb into it and it is still rooted, etc. What I've got now is a project tablet - HOW TO UNBRICK THE BRICK.
Click to expand...
Click to collapse
I hope you do so or some body find a way to unbrick this thing as for me i still have 26 days to return mine.i got to the part where I was about to paste the system I hit yes then everything locked up. I noticed before I hit yes it said do you want to merge and copy the files over not do you want to overwrite it but I still hit yes bad idea. can anybody tell me why I said merge and copy. well this is the second one I have bricks follow the steps perfect got all the way to the end and this is what happens so I took the first 1 back guess I'm going to take a second back also and try again until i figure out what I'm doing wrong.has anybody maked a rkimage or a .zip. update that will work to re cover this thing. I would be willing to try it out for you because I can.
netizenmt said:
Well, everyone be careful! When my Google Play would not install properly, I tried to clean the tablet up, ie, put it back to its original condition. Somehow, I managed to cause something to crash, and from then on, the tablet won't boot past the Android startup screen, although I can adb into it and it is still rooted, etc. What I've got now is a project tablet - HOW TO UNBRICK THE BRICK.
Click to expand...
Click to collapse
try doing an ADB shell
then the following commands
su
wipe data
this will reset the user partition. I had something similar happen on mine.. BTW 'wipe all' will definitly brick your tablet so be carefull
If you still cannot get it I was almost in a car accident yesterday and my tablet went flying and broke the screen... If you confident with a soldering iron I now have a plt-7035 mainboard prerooted and playstore installed for sale for $25 including shipping.. it would involve soldering 6 wire and the wifi antenna if your up to it pm me,, I know its good as I was able to ADB into it and run su and wipe data to reset it..
-Andrew