[Q] [SL4A] Noob problem: SL4A + Pyton doesn't work. - Android Q&A, Help & Troubleshooting

Hello
I have started to read "Pro Android Python with SL4A" by Paul Ferril & immediately failed while trying to execute Python script. I'd be very thankful to anybody who can provide a little explanation about SL4A + Python installation process.
So, my steps:
1) I opened this page, read QR code, downloaded and installed sl4a_r6.apk.
2) I opened previously installed SL4A app on my phone, press Menu > View > Interpreters, the list of the interpreters appeared with only one item - "Shell".
3) I pressed Menu > Add > Python 2.6.2, this started downloading of the "PythonForAndroid_r5.apk". I downloaded that file & installed it.
4) I opened newly installed "Python for Android" and press "Install" button in the app. Some components and scripts were installed successfully.
5) I opened the "SL4A" app again, press Menu > View > Interpreters, the "Python 2.6.2" item appeared in the list together with the "Shell".
6) I pressed "Back" button, the "Scripts" screen appeared with a list of scripts with the "py" extension.
7) I pressed on the "hello_world.py", the little pop-up appeared with the buttons "Execute", "Settings" (at least, with the settings icon), "Edit" and so on.
8) If I press the "Execute" button, I get only the black screen with the label "hello_world.py exited".
9) If in "SL4A" app I press Menu > View > Interpreters and the select "Shell" I will get terminal with the Linux Prompt ".... $". But If I go to the SL4A > View > Interpreters and the select "Python 2.6.2" I will receive black screen with the label at the top: "Python 2.6.2 exited."
So, as from the novice's point of view, the Python process is terminated each time I try to start it. What can be done in this situation?
--
Device: Lenovo Vibe Z2 Pro (international version) / Android 5.0.2, Stock Rom - K920_S230_150506_ROW / Rooted

It seems I've created this topic in the wrong forum section, so I ask the respectable moderators to delete this topic. Thank you.

Related

[Q] SL4A + Pyton doesn't work.

Hello
I have started to read "Pro Android Python with SL4A" by Paul Ferril & immediately failed while trying to execute Python script. I'd be very thankful to anybody who can provide a little explanation about SL4A + Python installation process.
So, my steps:
1) I opened this page, read QR code, downloaded and installed sl4a_r6.apk.
2) I opened previously installed SL4A app on my phone, press Menu > View > Interpreters, the list of the interpreters appeared with only one item - "Shell".
3) I pressed Menu > Add > Python 2.6.2, this started downloading of the "PythonForAndroid_r5.apk". I downloaded that file & installed it.
4) I opened newly installed "Python for Android" and press "Install" button in the app. Some components and scripts were installed successfully.
5) I opened the "SL4A" app again, press Menu > View > Interpreters, the "Python 2.6.2" item appeared in the list together with the "Shell".
6) I pressed "Back" button, the "Scripts" screen appeared with a list of scripts with the "py" extension.
7) I pressed on the "hello_world.py", the little pop-up appeared with the buttons "Execute", "Settings" (at least, with the settings icon), "Edit" and so on.
8) If I press the "Execute" button, I get only the black screen with the label "hello_world.py exited".
9) If in "SL4A" app I press Menu > View > Interpreters and the select "Shell" I will get terminal with the Linux Prompt ".... $". But If I go to the SL4A > View > Interpreters and the select "Python 2.6.2" I will receive black screen with the label at the top: "Python 2.6.2 exited."
So, as from the novice's point of view, the Python process is terminated each time I try to start it. What can be done in this situation?
--
Device: Lenovo Vibe Z2 Pro (international version) / Android 5.0.2, Stock Rom - K920_S230_150506_ROW / Rooted
Did you ever find an answer to this? I'm having the same issue.

[Help!] Update System with Terminal Emulator with Error "no space left on device"

[Help!] Update System with Terminal Emulator with Error "no space left on device"
I follow the following instruction to update my Meizu Pro5 with success for several times, but i got an error message "no space left on device" this time. Is there any way to solve this?
1. Enable root
Enable root by tapping on Settings-> Accounts-> My Flyme-> Personal settings (first option) -> System privileges and set it to open - accept disclaimer and confirm.
2. Download and successfully install Busybox (from Google Play or see .apk below)
3. Download and install a Terminal Emulator (from Google Play or see apk below)
4. Download the correct and desired international (i) ROM/firmware (update.zip) for your device
5. Download and use the update.zip (firmware) converter that creates the required system-i.img
Click here to download converter first
Copy system.new.dat and system.transfer.list (from the update.zip) to the folder “in” (see converter folder)
Then start the converting process by starting System-conVERTER.cmd and pressing option 1 [enter]
If successfully converted you can find the system-i.img in the ‘‘out’’ folder.
6. Copy the converted system-img from ‘‘out’’ to the internal memory of your Meizu device
7. Go to Settings-> Display-> Sleep and set it to at least 10 minutes
8. Start the Terminal Emulator and run (type) the super user command
su
A permission popup will come; give permission by tapping allow (always allow).
9. Now run (type) the command for installing the system-img.
dd if=/sdcard/system.img of=/dev/block/platform/XXXXXXX/by-name/system
Replace XXXXXXX with the correct partition system for your device
MX4 Pro = 15540000.dwmmc0
M2 note = mtk-msdc.0
MX4 = mtk-msdc.0 (OR mmcblk0p6)
MX5 = mtk-msdc.0 (OR mmcblk0p18)
Pro 5 = 15570000.ufs
Example for MX5 : dd if=/sdcard/system.img of=/dev/block/platform/mtk-msdc.0/by-name/system
Note: Pro5 might require: dd if=/storage/emulated/0/system.img instead of /sdcard/
10. The installation should start after the ‘‘dd if’’ command, but please note…
…it may seem that the copying/process did NOT start because you didn’t notice it, but it DID start.
do NOT type a new command or whatsoever, just…
…be patient and give your device 5-10 minutes to process.
11. When the process is done you’ll see a # at the very end
Your device should be unresponsive by now - this is normal
12. Now just shutdown your phone (hold power button) and reboot it
13. Once successfully booted your device should be running an I-rom
Once in Flyme again it is wise - but not necessary - to completely reset your phone. Go to settings->about phone->memory->factory data reset-> check both boxes and click start cleaning (this could take 5-10minutes). Always backup your stuff if necessary.

Moto E 2nd Gen XT1527 FRP By Pass Google but Build number can't open developer

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

Automated TWRP Nightly Backup

Love flashing @Travisholt92 's Custom ROMs but want to make sure you have a backup on hand? Here's your solution.
1) Download Tasker
2) Open Tasker, under profiles tab click the + button in the bottom right corner
3) Click Time, set a time you'd like to perform a backup. (Both start and end times make the same [i.e. 4AM;4AM])
4) Click the back button once time is selected, then click the + on the new task button
5) Type "Nightly Backup" and click the ✓
6) In the "Task Edit" window click the +, scroll down to "code"
7) Enter
Code:
rm -rf [COLOR="Red"]/storage/2151-1D18/TWRP/BACKUPS/LGMP2602ef1e4ad/nightlybackup*[/COLOR];
chmod 664 /cache/recovery;
echo "set tw_storage_path /external_sd";
echo "backup SDBOM nightlybackup \ncmd reboot" > /cache/recovery/openrecoveryscript
Note: Go into a Root Browser add a folder in your backup location called "nightlybackup". Copy the location of the folder and paste it into the red area specified, add the * after
8) Check off "Use Root"
9) Go back to the previous (Task Edit Screen) and press the + button again, scroll down and click "System" and then "Reboot"
10) Select "Type" as Recovery
11) Finally, press the ► button in the bottom left of your screen. It should reboot, backup and then reboot automatically again (May prompt to press power button as usual)
Note: I set my backup at 4AM after my Titanium Backup at 3AM so my phone is completely backed up and rebooted for my alarms to go off in the morning!
This code will also remove the previous Nightly Backup in that folder to be replaced with the new one upon Reboot to Recovery so you don't max out your storage! Enjoy!
Credit to @MishaalRahman for the original Tasker source!
Credit to @Travisholt92 for making awesome Custom ROMs

[SOLVED] Soft boot-loop/brick on Eken GC10X Tablet

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.

Categories

Resources