Hey guys, I spent the last week looking for a clear guide on how to install a custom rom on the Kurio 7 (Not the Kurio 7 S)
I have taken all of these demos and put them together into one guide. I take no credit for the information found here all I did was organize it in hopes it will help someone.
Here are the reference links to the original work-
Root: http://androidforums.com/general-tablet-talk/671444-root-kd-kurio-7-a.html
Play Store: https://www.youtube.com/watch?v=4WSuFvjyeRc
Recovery:http://forum.xda-developers.com/showthread.php?t=1802268
Rom and Gapps: http://www.slatedroid.com/topic/57538-rom-aokp-jelly-bean-android-412-allwinner-a10/
Disclaimer: You are doing this at your own risk, I am not responsible at all for your device. Just because it worked for me does not mean you will have the same outcome.
Download all of the files found here...
Lets get started: Bold = On the Tablet
1. Access the Android system (Done through parental controls)
2. Enable USB Debugging in Developer Options
3. Unzip and run the bat file found in Android Root.zip (Follow on screen instructions)
4. Extract the Install_google_play_allwinner.rar and run Install_Google_Play (Follow on screen instructions)
5. Open Google Play and download a Terminal Emulator
6. Extract and copy the contents of Kurio Recovery to your Tablet (not inside a subfolder)
7. Copy the files Kurio Rom and Kurio Gapps to your Tablet (not inside a subfolder)
8. Open Terminal Emulator and run the following commands
su
cd /mnt/sdcard
sh install-recovery.sh
sh reboot-recovery.sh
9. Select "Wipe data/factory reset, Wipe dalvik cache, & Wipe battery stats"
10. Select "install zip from sdcard" -> "choose zip from sdcard" and flash, in this order, Rom Then Gapps
11. Reboot your System
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Known Issues:
My daughter has been using it for a week and only noticed that the built in home and back buttons do not work. But the Roms has built in soft keys so she doesn't complain.
I hope this helps someone out there.
Reminder
I am not a developer, feel free to report bugs to but I will not be able to help resolve these bugs.
Link for files is down
Is there any chance you could repost the dropbox files? The link is 404. Thanks.
Does it work?
I have tried many times but it didn't work though.
What I'm gonna do now?
Please let me know?
Doesn't work
Hi,
I have tried rooting my Kurio 7 using the ICS_Root_Unlocker script in that Android_Root_1.0 zip file, but I get a ton of errors:
failed on '/data/local/tmp' - Permission denied link failed File exists
Press any key to continue . . .
/system/bin/sh: can't create /data/local.prop: Permission denied
Press any key to continue . . .
uid=2000(shell)gid=2000(shell)groups=1003(graphics),1004(input),1007(log),1009(mount),1011(adb),1015(sdcard_rw),1028(sdcard_r),3001(net_bt_admin),3002(net_bt),3003(inet),3006(net_bw_stats) context=u:r:shell:s0
Press any key to continue . . .
remount failed: Permission denied
failed to copy 'files\su' to '/system/xbin/su': Read-only file system
Unable to chown /system/xbin/su: No such file or directory
Unable to chmod /system/xbin/su: No such file or directory
Removing changes except ROOT...
rm failed for /data/local.prop, No such file or directory
rm failed for /data/local/tmp, Permission denied
failed on '/data/local/tmp.bak' - No such file or directory
Installing superuser...
failed to copy 'files\superuser.apk' to '/system/app/superuser.apk': Read-only file system
Press any key to continue . . .
My Kurio 7 is running Android 4.4.2 KitKat (the tablet is only a year old and already has Google Play on it) whereas the script appears to be for ICS, could this be the problem?
Anyone know how to adapt the script to work with KitKat?
Anyone have a kurio 7 ROM .IMG file?
Related
So I installed widgetlocked from the market and it all runs lovely. However, I wanted to use the Ultralinx mods for it.
I tried a few different ways, extracting it with root explorer. Copying the .apk to my desktop and modding the files there and signing them with signapk, but the modified .apk will not install no matter what I try. It always comes up with 'Application not installed'.
I am a bit newb at this I admit but have installed other apks just fine.
Any help appreciated
Figured it out. HAD to use adb. No other method would I tried would work, but that did first time!
I was trying to PM you, but they weren't going through...
Anyway, is there any chance you could tell me how you did this? I've tried every other method and nothing has happened. Whether it's because I own a Nexus S or a Mac, I don't know, but it's pretty hard (though I am new to this).
Regards,
Jon.
I usually use WidgetLocker, would you mind explaining what the modded one is? Thanks
The modded version I mention is UltraLinx's lovely unlock slider mod as in these pics.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Both available from here: http://www.theultralinx.com
As I mentioned the only method I could get to work was using ADB and Ultralinx actually has a youtube video on his site about how to do it, but I will list it here anyway.
Your phone needs to be rooted to do any of this...
Install WL as normal from market.
Copy the file com.teslacoilsw.widgetlocker-1.apk from data/app to /sdcard somewhere using astro or rootexplorer etc.
Then move that file to your computer desktop into the /sdk/tools dir where adb.exe is.
Add the WL modded files from Ultralinx to that .apk in the /res/drawable-hdpi/ directory using winrar or whatever program you use to open/mod .apk files. Make sure it has overwritten the original files!
Fire up a command promt and change dir to where adb.exe is sdk/tools or whatever.
type these next couple of lines and enter after each one;
abd shell mount /system
adb push com.teslacoilsw.widgetlocker-1.apk /system/app
Then reboot your phone and that should be it done. You can select the new slider from WL options (it modded the iphone slider so select that).
As I say, this is the only way I could get the thing to work.
Coming from windows mobile this whole abd thing of modding stuff seemed a right pain in the arse but I guess like anything once you have done it once you know it for next time and I think this mod is worth it.
Hi,
thanks for the instructions!
I've encountered an issue and would appreciate if you could help. So i follow your steps, however i get the following issue after the push command:
failed to copy 'com.teslacoilsw.widgetlocker-1.apk' to '/system/app/com.teslacoilsw.widgetlocker-1.apk': Read-only file system
I'll really appreciate if you could help, thanks!
Update: So i managed to push it successfully. Problem was I needed to enter the command adb remount beforehand in order for it to let me write.
sage: mount [-r] [-w] [-o options] [-t type] device directory
Red-Teams-MacBook-Prolatform-tools cloakroom$ adb push com.teslacoilsw.widgetlocker-1.apk /system/app
3158 KB/s (1202848 bytes in 0.371s)
However, even after rebooting the phone I am still stuck with the old iphone slider and not the one made by ultralinx. Any thoughts as to why this is?
Do i have to uninstall widgetlocker from my phone before i pushed the modded apk?
[TUTO] How to deodex stock rom for galaxy S DUOS S7562
In the world of Android, a lot of themes, tweaks and tricks require the need of a Custom Deodexed rom. Deodexed roms are firmwares where the .APK files of the System Software itself are packaged in a way so that they can be modified easily without causing any harm to the framework or the Android Environment.
This tutorial will cover all the steps required to deodex stock rom for galaxy s duos s7562, so that you don’t need to install a Custom Rom yourself!
Disclaimer: Follow all the instructions carefully mentioned in this article, I should not be held responsible in any manner if your Android Device doesn’t boot up or gets bricked due to not following the instructions.
Required :
1. Your device should already be rooted.
2. You should already have Android ADB in your computer and should have basic ADB knowledge.
3. JDK already installed in you’re PC (http://www.oracle.com/technetwork/java/javase/downloads/jdk7u9-downloads-1859576.html)
4. 7zip installed (http://www.7-zip.org/download.html)
5. Cygwin installed (http://www.cygwin.com/)
6. dsixda's Android Kitchen installed (http://forum.xda-developers.com/showthread.php?t=633246)
7. Busybox should already be installed in your device.
8. CWM already in you’re phone
9. Make nandroid backup (just in case).
10. sgs2toext4.jar ((created by drphrozen) attached
11. DiskInternals LinuxReader (http://www.diskinternals.com/download/Linux_Reader.exe)
Tutorial :
1. Download you’re favorite stock rom
2. Use 7zip to extract it (ignore errors)
You will have these files, we need only system.img.ext4
3. We have to convert it to ext4 format with sgs2toext4.jar
Open a command window and set the directory where you have sgs2toext4.jar file.
Now type sgs2toext4.jar and press enter
The .jar will run in a new window & will ask you to drag & drop the system.img.ext4 file there.
Do the same and wait till the process completes
4.Open the results file with DiskInternals LinuxReader an extract all files in new folder named system
5.Compress the system folder with 7zip (tar and store format) named system.img.ext4.tar
6.Put the file in kitchen folder (in original_update)
7.Lunch Cygwin terminal an cd to kitchen folder and load the menu (./menu)
You have to modify the API from 10 to 15
Look the file in C:\cygwin\home\user\kitchen\tools\deodex_files (api_level.txt)
8.Choose option (1) and do like these :
9.Choose option (0) ADVANCED OPTIONS
10.And then option (11) deodex files in your ROM
Then (b) deodex both folders and then
Take a caffe and be patient, the operation take a time to finish, if all operation finish without problem you will have this :
However, some apks failed to deodex, see the screenshot, for me only one apk failed it’s not very important
To resolve this, go to :
C:\cygwin\home\user\kitchen\WORKING_xxxxxx_xxxxxx\system\app\
and delete the odex apks (you can recognize them by their respective .odex files present in the same folder)
Make sure to delete both apk as well as its respective .odex file.
you can close the kitchen now if you do not want to add more MODs
THATS IT ! you have successfully deodexed both /system/app as well as /system/framework/.
Now to port the deodexed rom do the following :
11.Copy both app and framework folders to your sdcard, from :
C:\cygwin\home\user\kitchen\WORKING_xxxxxx_xxxxxx\system\
12.Connect your phone to computer.(Make sure you have select USB debugging in Settings>Developer options>USB debugging
13.Open Command prompt, Goto folder where android sdk installed. Then goto platform-tools folder in it. Right click on free space in folder while pressing shift key.Select open command prompt here.
Now enter commands. )
14.Enter following codes:
Code:
adb shell
su
stop
mount -o rw,remount /system/ /system/
cp /sdcard/app/* /system/app/
rm /system/app/*.odex
cp /sdcard/framework/* /system/framework/
rm /system/framework/*.odex
mount -o ro,remount /system/ /system/
reboot
(if you are using adb shell in su for the first time, keep phone screen on. After entering "su" code, super user request prompt in phone. Press allow )
who look for my cygwin i used in this tuto
https://docs.google.com/folder/d/0B7VA567j483ubnBUMXBvamswN3M/edit?pli=1
just extract it in c:\ lunch Cygwin.bat it will creat your user folder in c:\cygwin\home
then move kitchen folder in cygwin\home to your user folder created
cheers
all credits goes to devs from this great forum
Que
what is the use of deodexing Rom.what is its main advantage. in galaxy s duos
Cool.. is there any themes available for S duos?
Phelin said:
Cool.. is there any themes available for S duos?
Click to expand...
Click to collapse
Yes, check out the theme I made
http://forum.xda-developers.com/showthread.php?t=2276756
Hit thanks if I helped
sent from GT-S7562 , with a better stock ROM
Check out the theme I made specially for galaxy s duos.c1
This is the v2.00
Here are the screen snaps
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The link to theme is
http://forum.xda-developers.com/showthread.php?t=2279483
Sent from my GT-S7562 using xda app-developers app
V3.00 greenblast theme for s duos is released
Link
http://forum.xda-developers.com/showthread.php?t=2279483
Lockscreen
Tap to select in toggles is changed
Have a look
Sent from my GT-S7562 using xda app-developers app
I will not take any responsibility if something bad happens to your phone, or if you have to reflash the stock rom. This method is only tested on my own Xperia M2 D2303 and works fine so far.
If you did use the Towel Root method to gain root access to your M2, you probably tried to install Folder Mount or GL2SD in order to move some of your games and apps to your SD card. Unfortunately they will keep rebooting your phone unless you stop the SONY Ric service. Here is a temporary workaround.
Root your device first and follow the Towel Root guide, including the Super SU installation!
Make sure that your SD card is FAT32 formatted and there is sufficient space left to actually move the app/game
First download and install busybox from the play store and make sure that the install path says /system/xbin
Then also install Script Manager from the play store and open the app.
Tap the three dots on the bottom right of your screen to open the menu and select "New Script"
Give it a convinient name, "ric" will do just fine
Select SM Editor from the list
Type in the following (the first line is already there)
Code:
#!/system/bin/sh
mount -o rw,remount /system
stop ric
busybox pkill -f /sbin/ric
Save the file and close it
Now find the newly created "ric" in the list and tap it.
Make sure you select the "SU" and "Boot" icons and that "is script" is selected. Tap the save button.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Reboot and try if it works.
There are couple of "rootfixes" here on XDA that will attempt to fix the problem, but since they are all written for different Xperia devices they won't work. Also, this is NOT the same "halfroot" problem as on other Xperia phones since you can freely remount /system in RW mode, change permissions or delete/edit files inside.
This small script will be usable for all rooted M2's with locked bootloaders, while others will get custom kernels with blocked RIC sooner or later.
Remember: When you are done playing, unmount the folder in GL2SD/FolderMount before connecting the USB cable or stuff may happen.
Let me know if it works for you.
Currently, I'm not playing any large file gaming but Many of friends from M2 group experiencing bootloop when trying to folder mount, I'll let them know for this temp fix and post it here how the outcome.
Sent from my D2305 using XDA Free mobile app
Thank you very much !!!!!
Works very well and now, I can move my obb folder !!!!
Great script
it does'nt work
If I write these commands on terminal it work but the script produce no result.
How to instal busybox if system is read only?
Thanks
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This tool is not meant to be used on Android devices with dm-verify or Android Verify Boot (AVB) enabled
Every Android device has a stock recovery installed. That default recovery typically at least offers you the 4 options
reboot system now
apply update from sd card
wipe data factory reset
wipe cache partition
thus you can place any valid update.zip in device's SD-card slot and update your Android from external SD-card.
Because being in recovery mode Android isn’t loaded, the Android system files are not placed in memory, which means they can be accessed, edited and replaced.
That fact allows Android users to enable ADB on their devices what natively support ADB, if they haven't done it yet, for whatever reason.
Download the signed ADB.Enabler.OTA.ZIP from here . IMPORTANT: Rename it to UPDATE.ZIP before you make use of it.
If you get error "Signature verification failed" means that OEM/Carrier blocked to flash a 3rd-party OTA. You would need to have a Custom Recovery like CWM/TWRP already installed and use that to flash the ADB.Enabler.OTA.
HTH
link not working
I am looking for zip that can enable usb-debugging and disable RSA keys without touching /data (encrypted/not mountable):
- boot.img
- system.img A-only SAR system-as-root device
I tried modifying build.prop and default.prop manually but it seems adbd is not running at all
got inspired by @ehteshamxa and created some flashable zip which does NOT modify system files. instead own files added
Code:
/system/etc/init/99userinit.rc
/system/xbin/99userinit_daemon
/sdcard/userinit.sh
/sdcard/rsa_copy
Instructions:
- install userinit-rsa_copy-flashable.zip
- install Magisk.zip
- copy adbkey.pub to SD Card
USE AT OWN RISK
aIecxs said:
got inspired by @ehteshamxa and created some flashable zip which does NOT modify system files. instead own files added
Code:
/system/etc/init/99userinit.rc
/system/xbin/99userinit_daemon
/sdcard/userinit.sh
/sdcard/rsa_copy
Instructions:
- install userinit-rsa_copy-flashable.zip
- install Magisk.zip
- copy adbkey.pub to SD Card
USE AT OWN RISK
Click to expand...
Click to collapse
is root required?
No root required. Magisk is recommended for easy avb/dm-verity disable, but of course one can also place the files manually by unpack/repack (simg2img/sdat2img) flash tool method.
optional:
- copy sqlite3 binary to SD Card
(get it from here credits: @DiamondJohn)
- copy Magisk-v23.0.apk to SD Card
(credits: topjohnwu you all know of course)
have added example code in userinit.sh that can authorize su permissions for adb shell. useful on broken screen in case one can't get scrcpy to work on boot-loop
(credits: @mirfatif for magisk.db injection)
rsa_copy works also from emulated storage if one edit the path in first line:
Code:
sdcard=/sdcard
on locked screen external MicroSD Card is only available location as MTP might not work. in that case place files from PC card reader and insert back
remember the whole purpose of that backdoor is inaccessible userdata partition, otherwise one could just add rsa_copy or 99userinit_daemon to /data/adb/service.d systemless-ly instead (or most straightforward inject /data/misc/adb/adb_keys directly).
once got su shell one can backup partitions, for example:
Code:
adb shell su -c "cat /dev/block/dm-0 2> /dev/null" > userdata.img
edit: visit main thread for more discussion
https://forum.xda-developers.com/showthread.php?t=2965462
FIX THE LINK
@AlinTecsanSo let me see f I understand well.T enable adb ub )I have stock A71 with android 11 I download this file (ADB.Enabler.OTA.ZIP file missing can u uplad it please?) the rename it in UPDATE.ZIP ,put it n SD restart handy n recovery mode selecting "Apply update fron SD card" and that will be all?
helen2 said:
@AlinTecsanSo let me see f I understand well.T enable adb ub )I have stock A71 with android 11 I download this file (ADB.Enabler.OTA.ZIP file missing can u uplad it please?) the rename it in UPDATE.ZIP ,put it n SD restart handy n recovery mode selecting "Apply update frn SD card" and taht will be all?
Click to expand...
Click to collapse
i didnt try yet i need this file this is gone as a cloud
AlinTecsan said:
i didnt try yet i need this file this is gone as a cloud
Click to expand...
Click to collapse
me to maybe I will sort ut all my troubles let we wait post is quite old :/
This won't work on stock recovery anyway, it's for custom recovery only
Not sure which channel to put this in, please move if this is not the correct one.
I am unable to copy a certain file. At first I tried using a cloud share app, then USB file transfer, then ADB, then local file browsing apps, finally a terminal emulator. All fail. I can see the file and the app that created it can interact with it, but I cannot copy the file, permission denied. Phone is rooted. This is a large file created by TitaniumBackup. It's large because the backed up app has a lot of data, about 4 GB worth. I can copy all the small files that Titanium creates during its backup process, including the apk and properties files. And I can rename the big file, even delete it, just not copy.
I don't think it matters but this is a rooted Pixel 5 with stock ROM.
Apparently the same issue is within Titanium itself. It can delete backups but not upload to the cloud using the built-in function to Sync to Google Drive. I am thoroughly confused.
Can you run 'chmod 777' for that special file in advance as your system has been rooted?
James_Watson said:
Can you run 'chmod 777' for that special file in advance as your system has been rooted?
Click to expand...
Click to collapse
No issue chmoding but then can't copy still. Tried copying to the same dir and to my Download and Documents folders, same result.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
PRL77 said:
No issue chmoding but then can't copy still. Tried copying to the same dir and to my Download and Documents folders, same result.
View attachment 5147605
Click to expand...
Click to collapse
According to the screenshot, it means that you have no permission to create cp.gz in this directory. So, try to run chmod for the directory at first.
James_Watson said:
According to the screenshot, it means that you have no permission to create cp.gz in this directory. So, try to run chmod for the directory at first.
Click to expand...
Click to collapse
I was told that chmod doesn't function in /sdcard due to how it's mounted. So I went into /data/media/0/TitaniumBackup that can chmod there but still can't adb pull the file.
Before chmod: -rw------- 1 u0_a256
After chmod: -rwxrwxrwx 1 u0_a256
But pull still fails:
adb pull /data/media/0/TitaniumBackup/ws.clockthevault-20201130-045341.tar.gz vaultcopy.tar.gz
adb: error: failed to stat remote object '/data/media/0/TitaniumBackup/ws.clockthevault-20201130-045341.tar.gz': Permission denied
It's gotta be size related. This file is just over 4.3 GB.
This is resolved. Someone helped me on another forum: https://android.stackexchange.com/questions/231624/unable-to-copy-a-certain-file