Hi X10 mates, I was facing a typical SMS notification problem when i used "Handcent SMS" or "GO SMS". I was repeatedly receiving an invalid SMS notification of an old message which i deleted long back. Though it goes off when i clear the notifications, the notification comes back whenever i get a new message or open the "Handcent SMS" or "GO SMS" software. It was annoying me until i sat for 4 hours to crack it. I did all the crap (spend few hundreds too ) to crack it. If you are ready to do all the crap, here it goes,,,
PREREQUISITES
1.Get access to your ROOT folder
- I used "SuperOneClick1.7(Free)" - It works with the latest firmware 2.1.A.0.435 - Pinch Zoom
2.Get a file explorer for your mobile
- I installed "Root Explorer(2.5 pounds)/(Free)"
3.Get a ".db" editor
- I installed "SQLLite Editor(1.8 pounds)"
SOLUTION
4.Open the Root Explorer and grant "SuperUser" Access when it pops up (This is the case with SuperOneclick)
5.Go to /data/data/com.android.providers.telephony/databases
6.Open the "mmssms.db" (This is where all the mms and sms are stored) and select to SQLLite Editor in the pop up
7.Open the "sms" table and view for a row which has empty value in "thread_id" column.
8. Just press the row and delete the record ! And we are done !!
Though this may not be the easiest way, but i did at last!
Interesting. Can this help on MMS unsendable & unreceivable?
Related
Is there a way to do this? I had a Nook Color and it there was an app to change the gamma. Anyone know of an app that can do this for our TouchPads?
You can change the LCD density in the build.prop. Adjust it in increments of 10 until you find what you like.
Sent from XDA Premium on Thunderbolt
Stock dpi is 160.
I'm running 140 (slightly smaller). Valid is 0 to 255, but numbers over 240 caused issues with other devices so not a bad idea to have a current recovery backup.
How to edit your dpi manually:
Get Root Explorer from Market and scroll down to system, and tap it to open it. Then at the top, tap the [ Mount R/W ] button. It'll change to [ Mount R/O ] so you have read/write privilege. (If you're using a different editor, you'll have to figure out how to get read/write privilege.) Then long-press on your build.prop file, choose "edit".
Scroll down until you find this line (bottom section in ADDITIONAL BUILD PROPERTIES):
ro.sf.lcd_density=160
Tap to position your cursor at the end of the line and carefully change 160 to 140:
ro.sf.lcd_density=140
When done, tap the menu button, choose "save and exit" and tap the top button in Root Explorer to change back to [ Mount R/W ] and reboot.
There are other programs that let you edit system files, but you need one that uses root since this is a system file that can't be edited with some file managers.
Colchiro said:
Stock dpi is 160.
I'm running 140 (slightly smaller). Valid is 0 to 255, but numbers over 240 caused issues with other devices so not a bad idea to have a current recovery backup.
How to edit your dpi manually:
Get Root Explorer from Market and scroll down to system, and tap it to open it. Then at the top, tap the [ Mount R/W ] button. It'll change to [ Mount R/O ] so you have read/write privilege. (If you're using a different editor, you'll have to figure out how to get read/write privilege.) Then long-press on your build.prop file, choose "edit".
Scroll down until you find this line (bottom section in ADDITIONAL BUILD PROPERTIES):
ro.sf.lcd_density=160
Tap to position your cursor at the end of the line and carefully change 160 to 140:
ro.sf.lcd_density=140
When done, tap the menu button, choose "save and exit" and tap the top button in Root Explorer to change back to [ Mount R/W ] and reboot.
There are other programs that let you edit system files, but you need one that uses root since this is a system file that can't be edited with some file managers.
Click to expand...
Click to collapse
Does 140 give you any market app compatibility issues with some apps (Maps) for example. I know on my Thunderbolt there are only a few DPI's to chose from or I have app compatibility errors and can't update apps.
I use Nitrality from the market to change the DPI. It's under the UI section of the application I believe. I set my DPI at 200 and now I can actually see my icons.
180 Seems good. 160 a little too smal and 200 a bit too big for my taste.
I'm on 150 right now and think I'll keep it there until something goofy, like missing market apps happens.
Had that problem on the Nook and didn't even know it until I flashed a version with 160 dpi and instantly had about 6 updates in Market.
How does one get back to 160 dpi? The bar in nitrality wont go below 182 in portrait or landscape
Sent from my HTC Eva 4G using Tapatalk
For reason I'm getting launcher force close with anything under 160. Any idea why?
Mine's set to 150 and I just opened LPP, backed it up and uninstalled it. (I use it on my phone, but not optimal for tables, IMO. No FC's here.
Please post non development Questions into General Forum of device when there is no direct Q & A Forum.
How or where can I assign permissions for apps that use floating notifications?
I use a couple of these apps, and after updating to a new firmware (official) in my Ascend P6 they say they don't have permission for "showing the area of placement" or something like that (I'm not quite sure how to translate this properly - the message in Spanish is: "Esta aplicación no tiene permisos para mostrar el área de colocación") and niether of them show the floating notifications.
I tried checking the permission manager of the phone (which I had to dig out from the shurtcuts because it dissapeared from the settings menu) but there are no permissions for that.
I'm running Android 4.4.2 with B512 firmware.
Thanks in advance
I found a solution to this issue:
The problem, apart from the fact the phone was not allowing apps to show these types of messages on screen, was that the option to manage this permissions was hidden in B512.
The solution involves modifying a specific line in the build.prop file that hides or shows a particular option inside the built in phone manager app.
The line is ro.config.DelStartupManager=true and needs to be changed to ro.config.StartupManager=true. This enables a menu inside the phone manager that leads to the "placement area" permission settings (again, not sure if this is the actual string in English) from which you can assign these permissions to any app.
Hope it helps.
Model Number Moto E (2nd Generation) with 4G LTE
Hardware SKU
XT1527
Android version 5.1
Andriod security patch level
2016-04-01
Build Number
LPIS23 29-18.9-2
by pass google and now in setting but build number no work by pressing can't open developer plz help someone
No One Knows !
I have solution
Mod Edit
My services are not required here
help plzzz
please help me, I have no way to pay you, I have no credi card, but I really need to have this phone ...
wrong place
This section is for Moto E first gen (condor) not for Moto e second gen (surnia).
iazmatkhan said:
Model Number Moto E (2nd Generation) with 4G LTE
Hardware SKU
XT1527
Android version 5.1
Andriod security patch level
2016-04-01
Build Number
LPIS23 29-18.9-2
by pass google and now in setting but build number no work by pressing can't open developer plz help someone
Click to expand...
Click to collapse
Take my skype i give you solution
Arsalan.shahab1
desirlowens said:
please help me, I have no way to pay you, I have no credi card, but I really need to have this phone ...
Click to expand...
Click to collapse
add me on skype:
arsalan.shahab1
This model of AT & T version 5.1 does not allow unlock bootloader
It not allowed to also upload version 6.0 for retail and still has not left the AT & T version.
Test dpc does not work for this security because itis not gives the option of encryption as Owner.
ByPass:
1. Playing in email and keep pressed the @ until a menu of options.
2. keyboard settings Google
3. orthographic / staff / Dictionary correction for all languages
4. On the next screen tap the magnifying glass and press the letter "c". Several options were deployed and there
Google Pinyin Input to choose. On the next screen we chose the same option.
5. Then choose "about" Open Source Licenses"
6. On the next screen may maintain finger pressing and the option will appear
"Share" to choose "messages" typing 112 and send. At that time the call keyboard appears
delete 112 and type * # * # 4636 # * # *
7. On the next screen you can choose info or battery usage statistics.
8. Then go to back with the arrow on the top left
9. ByPass done.
10. Here you can not enable the developer and we can not restore option. It's just bypass
---------- Post added at 01:34 AM ---------- Previous post was at 01:24 AM ----------
Process FRP
Download four app
Aptoide
Es fileExplorer
Kingo Root
Terminal Emulator
The accecibilidad this phone is very poor so that the process is as follows:
1. In the menu go to Use data / You Tube / Application Settings / About
2. chose Google Privacy Policy
3. Open Google Chrome and from there download each of the applications but do not open.
4. Then return to the phone menu with the option "back"
5. We will install fromStorage File Explorer and open it
6. From the File Explorer install the other three applications
7. Open Aptoide and install the Nova Launcher, open and see the phone menu
8. Execute Kingo Root and Root and wait to tell you Done
9. Let back and look for the Terminal Emulator, enter and type "SU" to give us the option
root access #
10. Write in the amulador the following command:
content insert --uri content://settings / secure --bind name: s: user_setup_complete --bind value: s: 1
11. After that go back out from terminal emulator. Enable developer and OEM Unlockif not does not imortant.
12. Go to account and fill your own google account. The phone let you fil up.
13 Very importante do no delete the phone
14. Restart the phone and when start again you can enter your own google account. Then delete the phone.
15. Done. Credits: arsalrock55
---------- Post added at 01:38 AM ---------- Previous post was at 01:34 AM ----------
Note:
You can add the app Multi Windows that offers a fast accessibility when the process fails and you have not to do all the ByPass again butI had problems with this app.
He also clarified that does not always go in the first time is because the root with Kingo Root maybe you have to do many times.
I hope you serve the process.
Tested 100%
Hallo....
arsalrock55 said:
Mod Edit
My services are not required here
Click to expand...
Click to collapse
Cual es la solucion?
Cannot Open File
At number 5 of the process, I get a (Cannot open file message) on any apk. do you know why?
ByPass:
1. Playing in email and keep pressed the @ until a menu of options.
2. keyboard settings Google
3. orthographic / staff / Dictionary correction for all languages
4. On the next screen tap the magnifying glass and press the letter "c". Several options were deployed and there
Google Pinyin Input to choose. On the next screen we chose the same option.
5. Then choose "about" Open Source Licenses"
6. On the next screen may maintain finger pressing and the option will appear
"Share" to choose "messages" typing 112 and send. At that time the call keyboard appears
delete 112 and type * # * # 4636 # * # *
7. On the next screen you can choose info or battery usage statistics.
8. Then go to back with the arrow on the top left
9. ByPass done.
10. Here you can not enable the developer and we can not restore option. It's just bypass
---------- Post added at 01:34 AM ---------- Previous post was at 01:24 AM ----------
Process FRP
Download four app
Aptoide
Es fileExplorer
Kingo Root
Terminal Emulator
The accecibilidad this phone is very poor so that the process is as follows:
1. In the menu go to Use data / You Tube / Application Settings / About
2. chose Google Privacy Policy
3. Open Google Chrome and from there download each of the applications but do not open.
4. Then return to the phone menu with the option "back"
5. We will install fromStorage File Explorer and open it
6. From the File Explorer install the other three applications
7. Open Aptoide and install the Nova Launcher, open and see the phone menu
8. Execute Kingo Root and Root and wait to tell you Done
9. Let back and look for the Terminal Emulator, enter and type "SU" to give us the option
root access #
10. Write in the amulador the following command:
content insert --uri content://settings / secure --bind name: s: user_setup_complete --bind value: s: 1
11. After that go back out from terminal emulator. Enable developer and OEM Unlockif not does not imortant.
12. Go to account and fill your own google account. The phone let you fil up.
13 Very importante do no delete the phone
14. Restart the phone and when start again you can enter your own google account. Then delete the phone.
15. Done. Credits: arsalrock55
---------- Post added at 01:38 AM ---------- Previous post was at 01:34 AM ----------
Note:
You can add the app Multi Windows that offers a fast accessibility when the process fails and you have not to do all the ByPass again butI had problems with this app.
He also clarified that does not always go in the first time is because the root with Kingo Root maybe you have to do many times.
I hope you serve the process.
Tested 100%[/QUOTE]
root moto e
Greetings you can become root to motorola e second generation of at & t.
I'd appreciate your help
iazmatkhan said:
Model Number Moto E (2nd Generation) with 4G LTE
Hardware SKU
XT1527
Android version 5.1
Andriod security patch level
2016-04-01
Build Number
LPIS23 29-18.9-2
by pass google and now in setting but build number no work by pressing can't open developer plz help someone
Click to expand...
Click to collapse
1. Charge phone up to 100%, keep charger connected.and make sure you insert a correct working sim card.
2. Start the phone, connect to WiFi, get to the last screen (input Google email) and press on text input and
open Google keyboard settings (long press @ on bottom left).
3. press Google keyboard settings, and select Languages, Deselect `use system language` and scroll down to activate
Vietnamese.
4. Go back to the screen whereby the phone is asking for your email address, pop up the keyboard and
press and hold the Globe symbol near the `@` a tab will pop out showing `Change keyboard` ,select `Google voice typing`
5. you will see a keyboard emoji at your down right, click on it and select choose keyboards,after that activate
`Google pinyin input and iwnn IME` go back and press and hold `@` key and select google keyboard settings and choose Text
correction
6. choose personal dictionary and tap on `for all languge` click on the magnifier glass,type `C` scroll down and select
Google pinyin input and select the same option,select about and click open source licenses,select a text and click on
the share option and choose messaging
Send the composed message to emergency number 112
7. Press the phone icon that just appeared on the top right part of the screen
8. Delete 112 from number selection and input *#*#4636#*#*
9. In the opened window chose 'Usage statistics' and press back arrow on the TOP of the screen, not bottom!
10. You are now in the phone's settings
11. Go to About in settings
12. enable debugging mode
12. Use miracle box to remove frp using adb Tab
It works 100% search in youtube: Bypass Google account moto E 2nd gen Android 5 1
Link
Video solution here https://www.youtube.com/watch?v=UUnOiJolKHI
NB: I edited some of the instruction above as some sections were wrong or hard to understand. You still have to muddle through to get a proper understanding. My model was AT&T version 5.1
This model of AT & T version 5.1 does not allow unlock bootloader
It not allowed to also upload version 6.0 for retail and still has not left the AT & T version.
Test dpc does not work for this security because it does not give the option of encryption as Owner.
ByPass:
1. Playing in email and keep pressed the @ until a menu of options.
2. keyboard settings Google
3. orthographic (text correction / staff(personal dictionary) / Dictionary correction for all languages
4. On the next screen tap the magnifying glass and press the letter "c". Several options were deployed and there
Google Pinyin Input to choose. On the next screen, we chose "google hindu input".
5. Then choose "about" Open Source Licenses"
6. On the next screen may maintain finger pressing and the option will appear
"Share" to choose "messages" typing 112 and send. At that time the telephone icon appears
select telephone icon
delete 112 and type * # * # 4636 # * # *
7. On the next screen you can choose info or battery usage statistics.
8. Then go to back with the arrow on the top left
9. ByPass done.
10. Here you can not enable the developer and we can not restore option. It's just bypass
---------- Post added at 01:34 AM ---------- Previous post was at 01:24 AM ----------
Process FRP
Download four app
Aptoide
Es fileExplorer
Kingo Root
(Instead of Kingo Root use Croowt for rooting.)
Terminal Emulator
The accessibility of this phone is very poor so that the process is as follows:
1. In the menu go to Use data (Data Usage)/ You Tube / Application Settings / About
2. chose Google Privacy Policy
3. Open Google Chrome and from there download each of the applications but do not open.
4. Then return to the phone menu with the option "back"
5. We will install fromStorage File Explorer and open it
6. From the File Explorer install the other three applications
7. Open Aptoide and install the Nova Launcher, open and see the phone menu
(sometimes the phone will send you back to the beginning,. If this happens use some of the previous instructions to help you get back to this point. Use your common sense or ingenuity to decide what instructions get you back)
8. Execute Kingo Root and Root and wait to tell you Done
(sometimes the phone will send you back to the beginning,. If this happens use some of the previous instructions to help you get back to this point. Use your common sense or ingenuity to decide what instructions get you back)
9. Let back and look for the Terminal Emulator, enter and type "SU" to give us the option root access #
10. Write in the amulador the following command:
content insert --uri content://settings/secure --bind name:s:user_setup_complete --bind value:s:1
11. After that go back out from terminal emulator. Enable developer and OEM Unlockif not does not imortant.
12. Go to account and fill your own google account. The phone let you fil up.
13 Very important: do no delete (reset) the phone as yet
14. Restart the phone and when start again you can enter your own google account. Then delete (reset) the phone.
15. Done. Credits: arsalrock55
HELP
arsalrock55 said:
mod edit
my services are not required here
Click to expand...
Click to collapse
i would like ur help
Additional help
madrick73 said:
at number 5 of the process, i get a (cannot open file message) on any apk. Do you know why?
bypass:
1. Playing in email and keep pressed the @ until a menu of options.
2. Keyboard settings google
3. Orthographic / staff / dictionary correction for all languages
4. On the next screen tap the magnifying glass and press the letter "c". Several options were deployed and there
google pinyin input to choose. On the next screen we chose the same option.
5. Then choose "about" open source licenses"
6. On the next screen may maintain finger pressing and the option will appear
"share" to choose "messages" typing 112 and send. At that time the call keyboard appears
delete 112 and type * # * # 4636 # * # *
7. On the next screen you can choose info or battery usage statistics.
8. Then go to back with the arrow on the top left
9. Bypass done.
10. Here you can not enable the developer and we can not restore option. It's just bypass
---------- post added at 01:34 am ---------- previous post was at 01:24 am ----------
process frp
download four app
aptoide
es fileexplorer
kingo root
terminal emulator
the accecibilidad this phone is very poor so that the process is as follows:
1. In the menu go to use data / you tube / application settings / about
2. Chose google privacy policy
3. Open google chrome and from there download each of the applications but do not open.
4. Then return to the phone menu with the option "back"
5. We will install fromstorage file explorer and open it
6. From the file explorer install the other three applications
7. Open aptoide and install the nova launcher, open and see the phone menu
8. Execute kingo root and root and wait to tell you done
9. Let back and look for the terminal emulator, enter and type "su" to give us the option
root access #
10. Write in the amulador the following command:
Content insert --uri content://settings / secure --bind name: S: User_setup_complete --bind value: S: 1
11. After that go back out from terminal emulator. Enable developer and oem unlockif not does not imortant.
12. Go to account and fill your own google account. The phone let you fil up.
13 very importante do no delete the phone
14. Restart the phone and when start again you can enter your own google account. Then delete the phone.
15. Done. Credits: Arsalrock55
---------- post added at 01:38 am ---------- previous post was at 01:34 am ----------
note:
You can add the app multi windows that offers a fast accessibility when the process fails and you have not to do all the bypass again buti had problems with this app.
He also clarified that does not always go in the first time is because the root with kingo root maybe you have to do many times.
I hope you serve the process.
Tested 100%
Click to expand...
Click to collapse
[/quote]
how to open aptoide
kingo root fail
how to open aptoide[/QUOTE]
it keeps telling me root failed
---------- Post added at 10:48 AM ---------- Previous post was at 10:08 AM ----------
bromass said:
NB: I edited some of the instruction above as some sections were wrong or hard to understand. You still have to muddle through to get a proper understanding. My model was AT&T version 5.1
This model of AT & T version 5.1 does not allow unlock bootloader
It not allowed to also upload version 6.0 for retail and still has not left the AT & T version.
Test dpc does not work for this security because it does not give the option of encryption as Owner.
ByPass:
1. Playing in email and keep pressed the @ until a menu of options.
2. keyboard settings Google
3. orthographic (text correction / staff(personal dictionary) / Dictionary correction for all languages
4. On the next screen tap the magnifying glass and press the letter "c". Several options were deployed and there
Google Pinyin Input to choose. On the next screen, we chose "google hindu input".
5. Then choose "about" Open Source Licenses"
6. On the next screen may maintain finger pressing and the option will appear
"Share" to choose "messages" typing 112 and send. At that time the telephone icon appears
select telephone icon
delete 112 and type * # * # 4636 # * # *
7. On the next screen you can choose info or battery usage statistics.
8. Then go to back with the arrow on the top left
9. ByPass done.
10. Here you can not enable the developer and we can not restore option. It's just bypass
---------- Post added at 01:34 AM ---------- Previous post was at 01:24 AM ----------
Process FRP
Download four app
Aptoide
Es fileExplorer
Kingo Root
(Instead of Kingo Root use Croowt for rooting.)
Terminal Emulator
The accessibility of this phone is very poor so that the process is as follows:
1. In the menu go to Use data (Data Usage)/ You Tube / Application Settings / About
2. chose Google Privacy Policy
3. Open Google Chrome and from there download each of the applications but do not open.
4. Then return to the phone menu with the option "back"
5. We will install fromStorage File Explorer and open it
6. From the File Explorer install the other three applications
7. Open Aptoide and install the Nova Launcher, open and see the phone menu
(sometimes the phone will send you back to the beginning,. If this happens use some of the previous instructions to help you get back to this point. Use your common sense or ingenuity to decide what instructions get you back)
8. Execute Kingo Root and Root and wait to tell you Done
(sometimes the phone will send you back to the beginning,. If this happens use some of the previous instructions to help you get back to this point. Use your common sense or ingenuity to decide what instructions get you back)
9. Let back and look for the Terminal Emulator, enter and type "SU" to give us the option root access #
10. Write in the amulador the following command:
content insert --uri content://settings/secure --bind name:s:user_setup_complete --bind value:s:1
11. After that go back out from terminal emulator. Enable developer and OEM Unlockif not does not imortant.
12. Go to account and fill your own google account. The phone let you fil up.
13 Very important: do no delete (reset) the phone as yet
14. Restart the phone and when start again you can enter your own google account. Then delete (reset) the phone.
15. Done. Credits: arsalrock55
Click to expand...
Click to collapse
i got the kingo root to work but i cant get te emulator to work
arsalrock55 said:
Take my skype i give you solution
Arsalan.shahab1
Click to expand...
Click to collapse
Same problem over here, the one issue is no one wants to even help Android 5.1 or older users seems everyone has gotten spolied
Checked posts / searched for an existing answer... didn't see anything (please move this post if it is in the wrong section)
So I have a app, when I open it asks me what Google ID to uses (preferred ID) but after selecting a Google ID I can not change to a different ID
- If I clear the App Cache the selected ID persists
- If I clear the App Data the selected ID clears and the app returns to the select ID option
- I keyword searched for the App name on my device (Nexus 5x)with Root Explorer (12 different file locations, with subfolders and a bunch of empty folders)
Clearing App Data is a working interim solution, the downside is that every time I clear the App Data the app "downloads assets" (40mb+ ~40 times per day - 1.6Gb!)
What I am hoping to find is a app / script / terminal / log solution that will tell me what file is being modified when I select the Google ID, so I can delete that file re-open the app and change Google Logon
(I contacted the app developer, they said they may be able to fix the problem on the next patch eta 12-24 months)
So I have tried these apps:
https://play.google.com/store/apps/details?id=file.observer
https://play.google.com/store/apps/details?id=scd.lcex
https://play.google.com/store/apps/details?id=eu.thedarken.sdm
But I didn't see system changes (root level) or I didn't know what to look for in LogCat
Any help or suggestions are appreciate!
- I do not have a computer with me (ADB) will be about 7 days before I can try that
- I have been experimenting with deleting files / folders and testing to see if I get lucky (probably not the best method)
- I am not a developer
My current process (as of today) - I clear the app data, then restore the app data with TB (just restoring doesn't clear the sign in status)
As long as my TB backup is "always" in the signed out state, then the "app assets" restore with no issues (and I don't have to keep downloading them)
I am looking for a way to get these (2) operations into a single script / file / shortcut, but it is working for now
I did try the terminal with cp -a (copy the assets - app had a error on library permissions when the files were restored) chmod, chown, and find (try and locate the file) but had minimal success
Greetings!
First, this message will be rather long, for which I apologize. I am providing headings that allow whomever is interested to skip to whatever is relevant to them.
About the device:
It is one of two Eken GC10X tablets, purchased from Micro Center a while back dirt cheap. The second one is 6000 miles away in Europe. . . .
It is currently running Android 4.2.2
Its firmware revision is v2.0patch1
Its kernel version is 3.4.39+, dated Friday, October 18th, 2013, at 18:11:40 CST
Its build number is wing_k70-eng 4.2.2 JDQ39 20131028 test-keys
It comes pre-rooted by default. All that needs to be done is to install a terminal program and pay attention to certain paths.
About me:
I have been messing with computers, programming, and operating systems since the time of "wood burning computers"
I know my hosts file from my fstab, I have run various flavors of both Linux and Windows in both client and server configurations, and I know that both man pages and a good search engine Are Your Friends. (which is how I came to be here!)
Issue:
Since this Eken tablet comes with a bare minimum of internal memory, I was researching ways to mitigate this. I found an article that mentioned a workaround:
Copy everything in root to a large external SD card
Transpose the settings for the internal and external memory in the /etc/vold.fstab file
Save and Reboot
The result of this is a tablet that - regardless of the presence or absence of any external SD card - always boots as if it had never been booted before, (returns to "first-boot / out-of-box" setup). Any installed apps are gone and the "internal" memory - which is about 1-2 gigs - shows absolutely full. In addition to all that, I cannot do anything with the ADB port since it requires setting the "USB Debugging" flag, which gets reset on reboot. (i.e. The ADB interface is not available.
Examining the vold.fstab shows that the original setup of that file has been returned after I did a nuke-and-reboot.
I can reboot and re-install a terminal program and advanced file manager. (X-plore is my favorite)
I see three possible solutions:
Find the reason why it's booting like this and fix it.
Find a compatible firmware release for this tablet and re-flash it - if possible - from an external SD card.[/INDENT]
Do some kind of "nandroid" backup from the other Eken GC10X tablet I have and copy it to this one. Unfortunately it's 6000 miles away and I won't be able to get to it until sometime after January 2019. In addition, I cannot access the device via the ADB port.
Research I have done:
gsmhosting's allwinner forums
This site claims to have a (ahem!), "modified" version of the firmware, which I have downloaded.
The androidmtk site
This site has the "PhoenixCard" software which alleges that it can be used to create external SD card images of firmware files that can:
Install firmware from the SD card to the device.
Allow you to run the firmware from the SD card to verify it. It should be noted that MalwareBytes flags the updater.exe file because it attempts to download from a known Trojan site. Renaming the extension, (exe.bad), solves that problem.
I have not tried re-flashing any firmware version, though I have tried running the firmware from SD, which doesn't work.
Can someone help me with suggestions on how to return this tablet to normal?
Thanks in advance for any help you can provide!
Solution:
I guess it's "umpteenth time's the charm!" :highfive:
Having done considerable research, (with everything pointing to an issue with the busybox file being in the wrong place), I decided to revisit this, did a little more digging and ultimately found a solution.
Since nothing irritates me more than someone posting "I fixed it!" without telling everyone else HOW they fixed it, here are the steps I used to solve this problem.
Please be careful. You will be mucking around with your tablet's/phone's root file system in ways that can be fatal if you're not paying attention. It's not that difficult but you DO have to PAY ATTENTION to what you're doing.
TO-DO:
Instead of copying the busybox file, it should really be a symlink to /sbin/busybox.
If anyone figures out a way to create a symlink in Android that actually works, I'd like to know.
Here it is:
Pre-requisites:
The device MUST be rooted for this to work. I cannot help you with advice on how to root individual devices. This Eken tablet comes rooted by default.
Download off-line from Android Archives, (using a different system), an early version of X-plore, which is an excellent file manager.
Load X-plore onto a thumb-drive or a micro-SD card, (I used a micro-SD), and then install the SD card / thumb drive into the tablet you're trying to fix.
Steps to solve the problem:
First, go to Settings => Security and enable "unknown sources"
Open your device's file manager
Find the copy of X-plore you downloaded, and tap it to begin the off-line installation process.
Once it installs, open it and go to the "configuration" menu. This is within the three-dot menu drop-down in the upper right-hand corner.
Select:
* (near the top) Show hidden files => select the check-box. (optional)
* Root Access => Superuser + mount writable (this allows you to change permissions to permit writing the root filesystem)
* (scroll down) Dark mode => select the check-box. (this is a personal preference; IMHO it makes it easier to read.)
* Exit configuration by using the "back" button or back arrow in the upper left corner.
* You should now see two columns representing two views of the device's file-system.
On the left side, open the "Root" filesystem, also labeled with a "/"
Scroll down and find the "/sbin" folder and open it by tapping on it.
* You may, or may not, see several folders and files. You are looking for the file "busybox"
* If you don't see it there, you may have to "find" it using the magnifying glass icon in the center row of icons.
* Open the "find" dialog and replace the "*.*" with "busybox" and then select "OK".
* (assuming you found it), tap at the right-hand edge of the row with the file-name to "select" it - a big check-mark will appear there.
Go to the right-hand side list now. Find and open:
* Root (/) like you did before.
* system
* bin
* At the top of that column, you should see a folder icon, followed by "/system/bin"
Look to see if there is a file named "busybox" there. (In my case, it was missing - which is the problem)
(assuming it's missing)
Collapse the "bin" folder by tapping on it - it might take a couple of taps.
Touch-and-hold the "bin" folder until a long list appears. Scroll down to the bottom of that list and select "permissions"
Within the permissions dialog, there are three columns: Read, Write, and Execute.
* There should be three selected boxes under "Read".
* There should be ONE selected box, the top one, under "Write"
* There should be three selected boxes under "Execute"
* Directly below the last box under "Read", the box labeled "Recursive" should NOT be selected.
* To the far right of "Recursive" should be a note that reads "Mode: 755"
Under the heading "Write", select the other two boxes so that all three are selected. The word "Mode" should now be followed by "777" Close the permissions dialog by selecting "OK".
Verify the following:
* The arrow at the top of the center column is pointing to the right. If it is not pointing to the right, tap it until it points toward the right-hand column.
* The file "busybox" on the left-hand pane has a check-mark next to it and no other files are selected.
* The "bin" folder on the right-hand side has been collapsed and is selected by being a darker black with NO check-mark.
* The top of that column shows the folder icon and "/system/bin" as the selected path.
Copy the "busybox" file into the /system/bin folder by doing the following:
* Tap the "copy" icon in the center column - it will look like two pieces of paper stacked together.
* Verify that the dialog that opens:
* Just below the top right it says "busybox" (the file you're copying)
* Under that, "Copy to"
* Under that, a folder icon and then "/system/bin".
* Under that, the selection "Move mode (delete source files) is NOT selected!
* Tap "OK" to copy the file to /system/bin. Once the copy is done, the dialog will close.
Tap "bin" on the right hand side to open it if it does not open by itself.
Verify that "busybox" appears in both the left and right hand panes.
Press and hold the "busybox" file until the list dialog re-appears.
* Select "permissions".
* Verify that all three "Read" permissions are set, only the top "Write" permission is set, and all three "Execute" permissions are set. (You may have to clear the bottom two "Write" check-boxes.)
* Verify the "Mode" is set to "755"
* Close the permissions dialog by tapping "OK"
Collapse the "bin" folder by tapping on it.
Long-press the "bin" folder, select "permissions", and set the permissions of the bin folder to "755" the way you did for the busybox file above.
Return to the "Configuration" menu by following the steps at the beginning and select "Superuser" or "Normal User" instead of "Superuser + mount writable" to prevent accidental changes in the future.
At this point, you should be able to close and re-open X-plore and verify that "busybox" actually exists within /system/bin. If it does, you can reboot and your should be good to go.
If it's not there, re-trace the steps I listed above, paying particular attention to the "Superuser" setting in "configuration" and the various file permissions.
If you're still having trouble, post a reply below and I will try to provide what help I can.
Thanks for your patience and I hope this helps others who were puzzling with this as long as I was.