Doogee N20 "TEE key not write, Google key not write" message

Doogee N20 "TEE key not write, Google key not write" message - General Questions and Answers

After trying to root this smartphone, it ended up corrupting some system files. I reinstalled stock rom and this message showed up: TEE key not write, Google key not write:
{
"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"
}
Using Google i ended up at this thread here in xda:
https://forum.xda-developers.com/general/help/ulefone-power-3s-problem-t3794521
But this method about using adb platform tools didn't worked for me. There's no Factory Mode even when listing all the packages installed. Is there any other recommendation of what i should do? This is actually very annoying? Thanks.
Listed packages:
package:com.android.fmradio
package:com.mediatek.gba
package:com.mediatek.ims
package:com.android.cts.priv.ctsshim
package:com.google.android.youtube
package:com.android.internal.display.cutout.emulation.corner
package:com.google.android.ext.services
package:com.android.internal.display.cutout.emulation.double
package:com.android.providers.telephony
package:com.google.android.googlequicksearchbox
package:com.android.providers.calendar
package:com.android.providers.media
package:com.google.android.onetimeinitializer
package:com.google.android.ext.shared
package:com.mediatek.location.lppe.main
package:com.android.wallpapercropper
package:com.teslacoilsw.launcher
package:com.android.protips
package:com.android.documentsui
package:android.auto_generated_rro__
package:com.android.externalstorage
package:com.mediatek.ygps
package:com.mediatek.simprocessor
package:com.android.htmlviewer
package:com.mediatek.mms.appservice
package:com.android.companiondevicemanager
package:com.android.mms.service
package:com.android.providers.downloads
package:com.google.android.apps.messaging
package:com.adups.fota
package:com.mediatek.engineermode
package:com.android.partnerbrowsercustomizations.example
package:com.qiku.face.unlock
package:com.mediatek.omacp
package:com.google.android.configupdater
package:com.android.soundrecorder
package:com.mediatek.wfo.impl
package:com.android.defcontainer
package:com.android.providers.downloads.ui
package:com.android.vending
package:com.android.pacprocessor
package:com.android.simappdialog
package:com.android.internal.display.cutout.emulation.tall
package:com.android.certinstaller
package:com.android.carrierconfig
package:com.google.android.marvin.talkback
package:com.adups.privacypolicy
package:android
package:com.android.contacts
package:com.android.egg
package:com.android.mtp
package:com.android.nfc
package:com.android.stk
package:com.android.launcher3
package:com.android.backupconfirm
package:com.sprd.screencapture
package:com.android.statementservice
package:com.google.android.gm
package:com.google.android.apps.tachyon
package:com.mediatek.mdmlsample
package:com.android.settings.intelligence
package:com.mediatek.providers.drm
package:com.android.systemui.theme.dark
package:com.google.android.setupwizard
package:com.android.providers.settings
package:com.android.sharedstoragebackup
package:com.mediatek.batterywarning
package:com.google.android.music
package:com.android.printspooler
package:com.android.dreams.basic
package:com.android.se
package:com.android.inputdevices
package:com.google.android.apps.wellbeing
package:com.android.bips
package:com.mediatek
package:com.google.android.apps.nbu.files
package:com.example
package:com.mediatek.duraspeed
package:com.android.musicfx
package:com.google.android.apps.docs
package:com.google.android.apps.maps
package:com.google.android.webview
package:com.android.server.telecom
package:com.google.android.syncadapters.contacts
package:com.android.keychain
package:com.android.camera
package:com.google.android.calculator
package:com.android.chrome
package:com.android.dialer
package:com.google.android.packageinstaller
package:com.google.android.gms
package:com.google.android.gsf
package:com.google.android.ims
package:com.google.android.tts
package:com.google.android.gmsintegration
package:com.android.calllogbackup
package:com.google.android.partnersetup
package:com.google.android.videos
package:com.android.proxyhandler
package:com.google.android.feedback
package:com.google.android.printservice.recommendation
package:com.google.android.apps.photos
package:com.google.android.calendar
package:com.android.managedprovisioning
package:com.mediatek.calendarimporter
package:com.mediatek.thermalmanager
package:com.mediatek.callrecorder
package:com.android.providers.partnerbookmarks
package:com.android.smspush
package:com.mtk.telephony
package:com.android.wallpaper.livepicker
package:com.google.android.gms.policy_sidecar_aps
package:com.google.android.backuptransport
package:com.android.storagemanager
package:com.android.bookmarkprovider
package:com.android.settings
package:com.themonsterit.EngineerStarter
package:com.fineos.superscreenshot
package:com.mediatek.mdmconfig
package:com.mediatek.lbs.em2.ui
package:com.android.cts.ctsshim
package:com.android.vpndialogs
package:com.android.phone
package:com.android.shell
package:com.android.wallpaperbackup
package:com.android.providers.blockednumber
package:com.android.providers.userdictionary
package:com.android.emergency
package:com.android.location.fused
package:com.android.deskclock
package:com.android.systemui
package:com.android.bluetoothmidiservice
package:com.cryptotel.chamelephon
package:com.android.traceur
package:com.mediatek.mtklogger
package:com.mediatek.sensorhub.ui
package:com.android.bluetooth
package:com.android.wallpaperpicker
package:com.android.providers.contacts
package:com.android.captiveportallogin
package:com.google.android.inputmethod.latin
package:com.google.android.apps.restore

I have same issue on Cubot X19S. No factory mode, but still overlay. Did yo find a solution?

bululu said:
I have same issue on Cubot X19S. No factory mode, but still overlay. Did yo find a solution?
Click to expand...
Click to collapse
hey guys sorry there's probably a solution If you try one or some of the methods for other phones with trial and error
I dont let it bother me much though youll get used to ignoring it

I have the same issue!
The issue appear after formatting and flashing a non backuped ROM, because the TEE (Trusted Execution Environment) key it's not written or it's not the phone's original.
The red sentence (TEE key not write Google key not write) it is positioned in the system app: com.android.systemui
However, I read online that "maybe" could be solved with SN Write Tool (google it), I have not yet been able to try it for various reasons.
If by chance I solve it, I will tell you!
But for now nothing.

tiagao_extremo said:
After trying to root this smartphone, it ended up corrupting some system files. I reinstalled stock rom and this message showed up: TEE key not write, Google key not write:
Using Google i ended up at this thread here in xda:
https://forum.xda-developers.com/general/help/ulefone-power-3s-problem-t3794521
But this method about using adb platform tools didn't worked for me. There's no Factory Mode even when listing all the packages installed. Is there any other recommendation of what i should do? This is actually very annoying? Thanks.
Listed packages:
ecc...
Click to expand...
Click to collapse
I solved the "TEE key not write, Google key not write" issue!
Now I tell you how to solve the issue 100%:
IMPORTANT FOLLOW STEP BY STEP IF YOU DON'T WANT TO HAVE PROBLEMS! ONLY FOR DOOGEE N20!
Make a backup of System and Userdata partition first for precaution!
Requirements:
- The phone must be rooted
- TWRP Recovery (Optional)
- Root File Manager (e.g. Es File Manager)
- A PC with adb installed
- The modded APK that you will find in the attachments
Method:
- Enter the root file manager and navigate to \system\priv-app\MtkSystemUI
- Rename the apk that you will find inside the folder from "MtkSystemUI.apk" to "MtkSystemUI.apk.bck"
- Copy the modded APK and insert it in the \system\priv-app\MtkSystemUI folder
- Enter the PC and run this adb command
(Tips: when entering adb shell right click to paste, "ctrl+v" not work in adb shell. When you run the "su" command you will be asked to provide root access to the adb shell on your phone)
adb shell
su
pkill -TERM -f com.android.systemui; am startservice --user 0 -n com.android.systemui/.SystemUIService
IF you restart the phone and "TEE key not write......" reappears, follow these steps:
- IMPORTANT! Copy the modified apk to the SD card in case of encrypted userdata!
- Restart the phone in recovery mode
- Entered TWRP recovery tap on Advanced and tap on File Manager
- Once in the file manager navigate to \external_sd and look for the folder where you put it; Eg \external_sd\Download (Only if you have inserted the modified apk in the SD card).
- Tap on the modified apk and then tap on "Copy File"
- Now navigate to \system\system\priv-app\MtkSystemUI and tap on the button at the bottom right.
- Restart normally
- Enjoy!:good:

IosifMihaescu said:
I solved the "TEE key not write, Google key not write" issue!
Now I tell you how to solve the issue 100%:
IMPORTANT FOLLOW STEP BY STEP IF YOU DO NOT WANT TO HAVE PROBLEMS! ONLY FOR DOOGEE N20!
Make a backup of System and Userdata partition first for precaution!
Requirements:
- The phone must be rooted
- TWRP Recovery
- Root File Manager (e.g. Es File Manager)
- A PC with adb installed
- The modded APK that you will find in the attachments
Method:
- Enter the root file manager and navigate to \system\priv-app\MtkSystemUI
- Rename the apk that you will find inside the folder from "MtkSystemUI.apk" to "MtkSystemUI.apk.bck"
- Copy the modded APK and insert it in the \system\priv-app\MtkSystemUI folder
- Enter the PC and run this adb command
(Tips: when entering adb shell right click to paste, "ctrl+v" not work in adb shell. When you run the "su" command you will be asked to provide root access to the adb shell on your phone)
adb shell
su
pkill -TERM -f com.android.systemui; am startservice --user 0 -n com.android.systemui/.SystemUIService
- Now you will notice that the "TEE key not write......" is gone, but it is not finished yet! Because if now you will try to restart the phone normally the "TEE key not write......" will reappear!
- IMPORTANT! Copy the modified apk to the SD card in case of encrypted userdata!
- Restart the phone in recovery mode
- Entered TWRP recovery tap on Advanced and tap on File Manager
- Once in the file manager navigate to \external_sd and look for the folder where you put it; Eg \external_sd\Download (Only if you have inserted the modified apk in the SD card).
- Tap on the modified apk and then tap on "Copy File"
- Now navigate to \system\system\priv-app\MtkSystemUI and tap on the button at the bottom right.
- Restart normally
- Enjoy!:good:
Click to expand...
Click to collapse
Thanks, buddy! This message it's finally gone after two months. You helped me more than Doogee's support. I followed your steps after the adb message and it worked. But i could not enter into recovery to move the apk because it says there's encrypted data. Is it really necessary? Because i rebooted the smartphone and the message it's gone. Thanks a lot for your help!

tiagao_extremo said:
Thanks, buddy! This message it's finally gone after two months. You helped me more than Doogee's support. I followed your steps after the adb message and it worked. But i could not enter into recovery to move the apk because it says there's encrypted data. Is it really necessary? Because i rebooted the smartphone and the message it's gone. Thanks a lot for your help!
Click to expand...
Click to collapse
Let's say I tried to solve this problem because I had it too :laugh:
However in TWRP recovery if it tells you that the data is encrypted just tap on cancel, the userdata will remain encrypted but the other partitions es: \system will be uncrypted!
However it's not necessary to put the apk in the system folder with TWRP if the "TEE key......" not reappear after reboot!

IosifMihaescu said:
Let's say I tried to solve this problem because I had it too :laugh:
However in TWRP recovery if it tells you that the data is encrypted just tap on cancel, the userdata will remain encrypted but the other partitions es: \system will be uncrypted!
Click to expand...
Click to collapse
I did that, and the internal memory it's encrypted. After that i used a pen drive through the usb otg, but there was a error message when i tried to copy the file to the system partition. Do you want me to share a photo of the error message?
Since you know a lot about this device, do you know if it's possible to set the selinux policy to permissive definitely? I need to set it everytime i reboot by using the terminal command.

tiagao_extremo said:
I did that, and the internal memory it's encrypted. After that i used a pen drive through the usb otg, but there was a error message when i tried to copy the file to the system partition. Do you want me to share a photo of the error message?
Since you know a lot about this device, do you know if it's possible to set the selinux policy to permissive definitely? I need to set it everytime i reboot by using the terminal command.
Click to expand...
Click to collapse
Ok

tiagao_extremo said:
I did that, and the internal memory it's encrypted. After that i used a pen drive through the usb otg, but there was a error message when i tried to copy the file to the system partition. Do you want me to share a photo of the error message?
Since you know a lot about this device, do you know if it's possible to set the selinux policy to permissive definitely? I need to set it everytime i reboot by using the terminal command.
Click to expand...
Click to collapse
Install this app: https://drive.google.com/file/d/16MvDOlGNZ3v3yNMoeYyAGGE3WjcruHQC/view?usp=drivesdk
This app sets selinux to permissive automatically at boot.

IosifMihaescu said:
Install this app: https://drive.google.com/file/d/16MvDOlGNZ3v3yNMoeYyAGGE3WjcruHQC/view?usp=drivesdk
This app set's selinux to permissive automatically at boot.
Click to expand...
Click to collapse
Thank you again, my friend! This one it's working perfectly!

tiagao_extremo said:
Thank you again, my friend! This one it's working perfectly!
Click to expand...
Click to collapse
You're welcome!

IosifMihaescu said:
I solved the "TEE key not write, Google key not write" issue!
Now I tell you how to solve the issue 100%:
IMPORTANT FOLLOW STEP BY STEP IF YOU DON'T WANT TO HAVE PROBLEMS! ONLY FOR DOOGEE N20!
Make a backup of System and Userdata partition first for precaution!
Requirements:
- The phone must be rooted
- TWRP Recovery (Optional)
- Root File Manager (e.g. Es File Manager)
- A PC with adb installed
- The modded APK that you will find in the attachments
Method:
- Enter the root file manager and navigate to \system\priv-app\MtkSystemUI
- Rename the apk that you will find inside the folder from "MtkSystemUI.apk" to "MtkSystemUI.apk.bck"
- Copy the modded APK and insert it in the \system\priv-app\MtkSystemUI folder
- Enter the PC and run this adb command
(Tips: when entering adb shell right click to paste, "ctrl+v" not work in adb shell. When you run the "su" command you will be asked to provide root access to the adb shell on your phone)
adb shell
su
pkill -TERM -f com.android.systemui; am startservice --user 0 -n com.android.systemui/.SystemUIService
IF you restart the phone and "TEE key not write......" reappears, follow these steps:
- IMPORTANT! Copy the modified apk to the SD card in case of encrypted userdata!
- Restart the phone in recovery mode
- Entered TWRP recovery tap on Advanced and tap on File Manager
- Once in the file manager navigate to \external_sd and look for the folder where you put it; Eg \external_sd\Download (Only if you have inserted the modified apk in the SD card).
- Tap on the modified apk and then tap on "Copy File"
- Now navigate to \system\system\priv-app\MtkSystemUI and tap on the button at the bottom right.
- Restart normally
- Enjoy!:good:
Click to expand...
Click to collapse
Hello sir. I have a blackview max 1 with this red message. I assume I cannot use the same systemui apk... I have rooted it and need to get rid from this message. Could you help? I replaced the apk and the system got the navbar removed, the message was gone, but no navigation buttons and no qs tile notification pulldown panel either.
Any solution? Thanks

Morphine1 said:
Hello sir. I have a blackview max 1 with this red message. I assume I cannot use the same systemui apk... I have rooted it and need to get rid from this message. Could you help? I replaced the apk and the system got the navbar removed, the message was gone, but no navigation buttons and no qs tile notification pulldown panel either.
Any solution? Thanks
Click to expand...
Click to collapse
Yes, the SystemUI mod apk given in this thread is only for Doogee N20.
However, If you send me your phone's original SystemUI apk, I can try to mod it.
Just send me your Blackview Max 1 SystemUI.

IosifMihaescu said:
Yes, the SystemUI mod apk given in this thread is only for Doogee N20.
However, If you send me your phone's original SystemUI apk, I can try to mod it.
Just send me your Blackview Max 1 SystemUI.
Click to expand...
Click to collapse
Thank you so much. I'm uploading it right now. Attached file
I saw about using SN Write Tool , Here and Here
but to be honest that would be a bit of a headache.
Hopefully I can get rid of this text by just replacing your modded systemui for the Blackview Max 1.

Morphine1 said:
Thank you so much. I'm uploading it right now. Attached file
I saw about using SN Write Tool , Here and Here
but to be honest that would be a bit of a headache.
Hopefully I can get rid of this text by just replacing your modded systemui for the Blackview Max 1.
Click to expand...
Click to collapse
Can you try to reupload it with https://wetransfer.com/upload
Because when I try to download it from the attached files, it gives me an Error 404.

IosifMihaescu said:
Can you try to reupload it with https://wetransfer.com/upload
Because when I try to download it from the attached files, it gives me an Error 404.
Click to expand...
Click to collapse
Done: https://wetransfer.com/downloads/e1...d6d1b7704d03dfa3ff07da7820200714024051/503f37

Morphine1 said:
Done: https://wetransfer.com/downloads/e1...d6d1b7704d03dfa3ff07da7820200714024051/503f37
Click to expand...
Click to collapse
Can you give me a screenshot of the message?

IosifMihaescu said:
Can you give me a screenshot of the message?
Click to expand...
Click to collapse
Done, attached

Here it is:
https://we.tl/t-PA2IgNyqD6

Related

[GUIDE] Root Cheat Sheet

All the info and links needed, none of the fluff. If you have questions, simply ask.
This guide aims to be platform independent. However, some cheats may require user contribution. Thanks in advance!
UPDATED 5-4-2010: New, Faster Factory Reset. Thanks rt1oo and johnsongrantr
Root CDMA Hero, Load Custom Recovery & ROM
Forum Post: Step By Step Way to root Using Flashrec(Updated 4/5)
Thanks goku14238
1) Download: flashrec-1.1.3-20091107.apk
1.1) Download: recovery-RA-heroc-v1.6.2.img
1.2) Download ROM ZIP of Choice: XDA Wiki - ROMs
1.3) Market Download: Any File Manager. RootExplorer, ES File Manager, Astro, etc.
2) Rename "recovery-RA-heroc-v1.6.2.img" to "recovery_backup.img"
3) Copy downloads to SD card root (/sdcard/)
4) Fill in check box for: Settings>Applications>Unknown sources
5) Install "flashrec-1.1.3-20091107.apk" via Any File Manager (RootExplorer, ES File Manager, Astro, etc.) or ADB
*Unmount SD Card if mounted through USB*
6) Open "Recovery Flasher" App and select "Restore Backup Image"
7) Power OFF
8) Power ON to Recovery: Press and hold the "Home" button, Continue holding "Home" while pressing and releasing the "Power" button
9) Flash zip from sdcard>select ROM ZIP
10) Reboot
Reset Phone With Loaded ROM (1.5 "Cupcake" ROMs)
Code:
Menu > Settings > Security > Factory data reset > Reset phone > Erase everything
Reset Phone With Loaded ROM (2.1 ROMs)
Code:
Menu > Settings > Privacy > Factory data reset > Reset phone > Erase everything
Factory Reset
Thanks rt1oo: Forum Post
This will return the phone to its out-of-box, factory condition (including radio!).
Search "RUU" if you want it the official Windows way.
NOTE: If you used the 2.1 RUU, this will not work. HBoot version must be 1.41. Read Forum Post for another method.
1) Download: HERCIMG.ZIP
2) Copy to root of SD card (/sdcard/)
3) Turn phone OFF
3) Hold Volume Down while pressing the power button (turn back on)
4) Press trackball when prompted
5) Reboot
Boot to Recovery from Power OFF
Press and hold the "Home" button, Continue holding "Home" while pressing and releasing the "Power" button
Nandroid Backup
-Reboot into recovery mode>Backup/Restore>Nand backup
TIP: If you choose "Nand backup + ext" it will backup your apps2sd apps along with your imaged system.
*CAUTION: you must restore this kind of backup to an SD Card that is similarly formatted (i.e. SWAP/EXT/FAT backup)
COPY THE CONTENTS OF THE "nandroid" FOLDER TO OTHER MEDIA ON REGULAR BASIS IN CASE OF SD CARD FAILURE!
Nandroid Restore
-Reboot into recovery mode>Backup/Restore>Nand restore>Select desired backup
*TIP* If no backups are found, you need to copy the "nandroid" folder back onto your SD Card from your Computer backup (You did make a copy of nandroid to your Computer didn't you!?)
Partition SDCard for apps2sd (A2SD)
-WARNING: This will erase EVERYTHING from the SDCard. Nandroid does NOT backup SD Card data, except for apps2sd apps, and ONLY if you selected "Nand backup + ext"
1) Reboot into recovery mode>Partition sdcard>Follow on-screen instructions (Default values suggested are OK)
Load Custom ROMs
Download ROM ZIP of Choice: XDA Wiki - ROMs
1) Copy ROM ZIP to SDCard Root (/sdcard/)
2) Reboot into recovery mode>Flash zip from sdcard>select ROM ZIP
Load Android SDK [Mac]
1) Download Latest Android SDK: http://developer.android.com/sdk/index.html
2) Unpack and rename the extracted folder to "AndroidSDK", Move it to "Applications"
3) Copy and Paste into TextEdit:
Code:
export PATH=${PATH}:/Applications/AndroidSDK/tools
4) Save as: "~/.bash_profile"
5) Fill check box on Phone: Settings>Applications>Development>USB debugging
How to modify system files from Recovery
Code:
adb shell
mount <MOUNT_POINT>
Replace <MOUNT_POINT> with area you want to modify (ex: /system /data)
Install Apps through ADB
Code:
adb install <PATH_TO_APK>
Replace <PATH_TO_APK> with the location of your apk (ex: ~/Installers/Android/apk/wireless_tether_1_60_htc.apk)
How to tell if apps2sd (A2SD) is working
1) Connect Phone via USB
Code:
adb remount
adb shell
ls /system/sd/app/
If you get a list of applications, or no errors, then apps2sd is *should be* working properly.
Remove Extra Useless Preloaded Apps
Link: Root Explorer
Yes, you CAN do this through adb, but this is MUCH easier. Simply open, hit "mount r/w" button, delete anything in /system/app and /data/app you don't want! I'm well aware of the cost of the app. If you don't want to pay and help the developer, then search the forums and figure it out yourself !

Good stuff. Thanks for the contribution. Would you mind if I put it on GeekFor.Me / would you like to put it on there?
http://geekfor.me/news/wanted-writers-for-faq-tutorial-help/
Let me know.

Please do! Thanks for the read! Also, thank you very much for all of your hard work, the ROMs you make are crucial to all of this stuff advancing forward!

Thanks for putting this together - great post!

Thanks a lot for this Gallias. Definitely helped me out. I wish I had found this a couple weeks ago heh.

When I tried to enable compcache with your instructions I was getting a read-only error. Doing 'adb remount' first seems to have solved it.

AH yes thank you my apologies. Updated.

Hey, I swear i've tried for two hours to get Modacos custom ROM installed. I successfully installed the recovery-RA-heroc-v1.5.2.img and when I power off and reboot into recovery mode, I only get one option -- to CLEARSTORAGE "Delete all user data? <action>yes <send> no, I select YES and it reboots the phone and it looks like the same interface. I've tried flash_image recovery /sdcard/update.zip by renaming the ZIP file modaco 2.2 to (update) and moving it to the SDCARD home directory. I then use Lindas file manager to load the custom recovery image and select SDCARD/update.zip This doesn't work (I'm probably doing something wrong) But I don't understand why I can't boot into recovery mode. I am using the CDMA (sprint) version.
Any tips? I need a bit of some help here.

When you reboot into recovery mode you should see this:
{
"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"
}
If you don't see that, then you haven't actually pushed the new recovery image into the phone. The screen you describe is the default recovery loader that comes with the phone.
Try my "Load Custom Recovery" step over again, or if on a different platform, follow the root guide for your specific platform:
CDMA Hero Guides

I got up to the point of
adb push asroot2 /data/local
it says 836 KB/s <74512 bytes in 0.087s>
C:\hero\tools> aadb shell
$chmod 0755 /data/local/asroot2
chmod 0755 /data/local/asroot2
$ /data/ocal/asroot2 /system/bin/sh
/data/local/asroot2 /system/bin/sh
now get this.... this is what it gives back to me
[+] Using newer pipe_inode_info layout
Opening: /proc/758/fd/3
YES it says 758 NOT 857.
It then says
SUCCESS: Enjoy the shell
Is that right or is it supposed to be 857? I saw the guide and it told me that it should say 857 so it's not giving me the right message I assume.
I'll try again and see if this is right, i'll post an edit later to let you know if I get it workin, if not I guess 758 is incorect

Well, based on the C:\ I'm going to say your using Windows. I don't think that number will be critical, but you do need to perform this after you get the "SUCCESS: Enjoy the shell"
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/bin
cat sh > su
chmod 4775 su
exit
exit
THEN, you also need to push the recovery image. If you are following the link I placed at the top of this guide on how to root with Windows, it should have you go through everything I'm explaining. Don't get worried or hung up on steps that don't exactly match up with what other people are seeing; at the end of the day you may see some differences, but if you are getting "SUCCESS" from asroot2 it means that the technical "rooting" part is working, you just need to finish up and follow through on the rest of the steps. Keep working at it you are really close, don't let inconsistent numbers discourage you!

Just letting you know, you've got a typo in the rooting area. It should be asroot2 not asroot 2

ffolkes said:
Just letting you know, you've got a typo in the rooting area. It should be asroot2 not asroot 2
Click to expand...
Click to collapse
Ah yes very true thanks! Fixed.

I followed the instructions for rooting with a MAC, I did the boot into recovery mode, there is no option for "NANDROID" backup. It just says "Clear User Data" <ACTION> Yes <SEND> No. Wound up clearing everything off my phone.

rlundeen said:
I followed the instructions for rooting with a MAC, I did the boot into recovery mode, there is no option for "NANDROID" backup. It just says "Clear User Data" <ACTION> Yes <SEND> No. Wound up clearing everything off my phone.
Click to expand...
Click to collapse
Ouch! Sorry man, it means something went wrong during "Load Custom Recovery [MAC]". Try that step over again.

theraginasian said:
Ouch! Sorry man, it means something went wrong during "Load Custom Recovery [MAC]". Try that step over again.
Click to expand...
Click to collapse
Did it 3 times, get the same thing over and over. Actually, if you hold the Volume Down key and then power the phone on, I can do the nandroid backup, flash rom, etc.

theraginasian said:
Remove Extra Useless Preloaded Apps
Forum Post 1: How to remove Stocks, Nascar, and other useless apps...
Forum Post 2: APPS that are SAFE to remove
Thanks chuckhriczko and VoXHTC!
Beyond what most custom ROMs remove, I remove:
-Sprint Navigation (Sprint_Navigator.apk/odex)
-Sprint Visual Voicemail (Sprint_Core.apk/odex)
-Device Self-Service (SDSA.apk/odex)
Code:
adb remount
adb shell
cd /system/app
rm <NAME_OF_APP>.apk
rm <NAME_OF_APP>.odex
Replace <NAME_OF_APP> with the name of the app you want removed.
Make sure to check /system/sd/app for duplicate/other unwanted applications if you have apps2sd running.
Click to expand...
Click to collapse
Thanks the cheat sheet. Is this list of apps that can be safely removed still valid for 2.1 ROMs? I am running DC v2.07.2 ROM.

prateekandroid said:
Thanks the cheat sheet. Is this list of apps that can be safely removed still valid for 2.1 ROMs? I am running DC v2.07.2 ROM.
Click to expand...
Click to collapse
Make a NANDROID before removing any of them, so if you remove something you want back or that messes your phone up. You can go back to original.
They arent usually the main choices. But you can if you want to.
Heres some you can remove.
Type this
adb remount
adb shell
cd /system/app
ls
* "ls" this will show you all the apps on your phone.*
These are commonly removed-
Sprint_Navigation.apk
Sprint_TV.apk
Sprint_TVWidget.apk
Sprint_Nscar.apk
Sprint_NFL.apk
Stock.apk
com.htc.StockWidget.apk
HtcRingtoneTrimmer.apk
Youtube.apk
Facebook.apk
There are more, but these are usually the common ones. Pick and choose what you want and what you dont want.

Jus10o said:
Make a NANDROID before removing any of them, so if you remove something you want back or that messes your phone up. You can go back to original.
They arent usually the main choices. But you can if you want to.
Heres some you can remove.
Type this
adb remount
adb shell
cd /system/app
ls
* "ls" this will show you all the apps on your phone.*
These are commonly removed-
Sprint_Navigation.apk
Sprint_TV.apk
Sprint_TVWidget.apk
Sprint_Nscar.apk
Sprint_NFL.apk
Stock.apk
com.htc.StockWidget.apk
HtcRingtoneTrimmer.apk
Youtube.apk
Facebook.apk
There are more, but these are usually the common ones. Pick and choose what you want and what you dont want.
Click to expand...
Click to collapse
Thanks for a prompt response.
Just curious, wat do people prefer instead of Youtube.apk to watch Youtube? Because as far as I know there is no Adobe Flash support yet. So Youtube videos will not work on its website. I use Dolphin browser.

i personally believe the flashrec method is much more practical. i was able to root and flash a custom rom without ever plugging my phone into my computer, i did it all from my phone.
is there a downside to flashrec im not aware of?

[Q] Nexus S voice/sound recorder hidden and not installed?

Hi,i was searching for the stock voice recorder in Ice Cream Sandwich,but i did not find it...
So I've searched into phone memory (root /system/app) and i found Soundrecorde.apk ,bu if i try to install it,installation aborts saying "This application cannot be installed".
Why?

No one use voice recording on Ics?
Neo on Nexus S with Tapatalk®

bump?.......

.:Crack:. said:
bump?.......
Click to expand...
Click to collapse
???
Neo on Nexus S with Tapatalk®

..

Election Day said:
It indeed doesn't seem to work. Just like Tag.apk, SoundRecorder.apk does not show up in the app drawer, even if it's in /system/app. Apparently it just isn't compatible.
What about some Market apps?
Click to expand...
Click to collapse
There is not much compatibility for this kind of apps and Ics...
Stock Sound recorder was perfect for me on Gingerbread,i don't understand why it's not compatible anymore...
Neo on Nexus S with Tapatalk®

not sure how you tried to install but you cant install system apps like other apk you have to sign it first....anyways i signed it and installed fine but dont give an option to open after install and still don't see it
edit
just for future reference if you edit an apk or want to install a system app like a normal apk
download Sighnapktic from the market its free and it does it right from your phone really easy to use
https://market.android.com/details?id=com.stericson.signapktic&hl=en

i used Sanity with gingerbread, but I don't know if it still works with ICS
https://market.android.com/details?..._result#?t=W251bGwsMSwxLDEsImNyaS5zYW5pdHkiXQ..

Election Day said:
It indeed doesn't seem to work. Just like Tag.apk, SoundRecorder.apk does not show up in the app drawer, even if it's in /system/app. Apparently it just isn't compatible.
What about some Market apps?
Click to expand...
Click to collapse
Both of those apps don't show in the drawer because the "LAUNCHER" intent lines in their respective AndroidManifest.xmls are not present/were omitted that instruct the app to be visible in the drawer.
To the best of my recollection, SoundRecorder never officially included the lines because it was supposed to be present solely as a function for other apps to use, despite it having an actual interface. Tag, on the other hand, appears to have had those lines removed in the transition to ICS. Adding the intents in their manifests will cause them to show up in the drawer again.

XK72 said:
Both of those apps don't show in the drawer because the "LAUNCHER" intent lines in their respective AndroidManifest.xmls are not present/were omitted that instruct the app to be visible in the drawer.
To the best of my recollection, SoundRecorder never officially included the lines because it was supposed to be present solely as a function for other apps to use, despite it having an actual interface. Tag, on the other hand, appears to have had those lines removed in the transition to ICS. Adding the intents in their manifests will cause them to show up in the drawer again.
Click to expand...
Click to collapse
Once added,will the app works with its interface?
Neo on Nexus S with Tapatalk®

..

(THE REAL) Neo said:
Once added,will the app works with its interface?
Neo on Nexus S with Tapatalk®
Click to expand...
Click to collapse
{
"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"
}
Correct.
Election Day said:
Probably yes. I'm trying to modify the xml's at the moment, but I can't get any usable output.
If I can get it to work I'll post the modded apk here.
Click to expand...
Click to collapse
Directly after this line:
Code:
<action android:name="android.intent.action.MAIN" />
Add:
Code:
<category android:name="android.intent.category.DEFAULT" />
<category android:name="android.intent.category.LAUNCHER" />

..

You also just can use anycut from market and create a homescreen shortcut to soundrecorder.apk

Election Day said:
I guess this should be it. I unpacked the apk with apktool, added the lines, packed it again, unzipped it, added META-INF and rezipped it.
You can flash it with "adb push SoundRecorder.zip /system/app".
Click to expand...
Click to collapse
No changes here...i've copied the file in sistem/app,but nothing changes.
Neo on Nexus S with Tapatalk®

(THE REAL) Neo said:
No changes here...i've copied the file in sistem/app,but nothing changes.
Neo on Nexus S with Tapatalk®
Click to expand...
Click to collapse
I haven't looked at the attached APK yet, but try these steps:
I'm not sure if it's because the instructions have you install a ZIP file that doesn't exist (because the attachment is an APK).
The command should be: adb push SoundRecorder.apk system/app
If you happened to have changed the command to APK anyway, make sure that you specify the right path for the file
(e.g. adb push path/to/downloaded/file/SoundRecorder.apk system/app) or that you are in the same directory as the file (then use the command listed above).
If the file got pushed successfully, you may need to reboot your phone for the changes to take effect.
Try that out and if you're still not having any luck, let me know what ADB tells you. If it helps, I'll build a version with the Launcher icon visible that'll work.

XK72 said:
I haven't looked at the attached APK yet, but try these steps:
I'm not sure if it's because the instructions have you install a ZIP file that doesn't exist (because the attachment is an APK).
The command should be: adb push SoundRecorder.apk system/app
If you happened to have changed the command to APK anyway, make sure that you specify the right path for the file
(e.g. adb push path/to/downloaded/file/SoundRecorder.apk system/app) or that you are in the same directory as the file (then use the command listed above).
If the file got pushed successfully, you may need to reboot your phone for the changes to take effect.
Try that out and if you're still not having any luck, let me know what ADB tells you. If it helps, I'll build a version with the Launcher icon visible that'll work.
Click to expand...
Click to collapse
Tried this and it didn't worked for me. I get this error from adb:
failed to copy 'SoundRecorder.apk' to 'system/app/SoundRecorder.apk': Permission denied

XK72 said:
I haven't looked at the attached APK yet, but try these steps:
I'm not sure if it's because the instructions have you install a ZIP file that doesn't exist (because the attachment is an APK).
The command should be: adb push SoundRecorder.apk system/app
If you happened to have changed the command to APK anyway, make sure that you specify the right path for the file
(e.g. adb push path/to/downloaded/file/SoundRecorder.apk system/app) or that you are in the same directory as the file (then use the command listed above).
If the file got pushed successfully, you may need to reboot your phone for the changes to take effect.
Try that out and if you're still not having any luck, let me know what ADB tells you. If it helps, I'll build a version with the Launcher icon visible that'll work.
Click to expand...
Click to collapse
I've not used adb,but manually copied the .apk to system/app after renaming of original file.
Obviously i've used EsGestore File,with root permissions/root mounted read and write.
File copied perfectly,rebooted phone.
But nothing happens...
Neo on Nexus S with Tapatalk®

jitzbox said:
Tried this and it didn't worked for me. I get this error from adb:
failed to copy 'SoundRecorder.apk' to 'system/app/SoundRecorder.apk': Permission denied
Click to expand...
Click to collapse
This may not be the most efficient way of doing this, but it always works for me. Assuming that you have root permissions on the phone, try the following steps:
Access the phone through ADB:
Code:
adb shell
Mount the volume as writable:
Code:
mount -o remount,rw /dev/block/mtdblock4 /system
Remove the existing SoundRecorder.apk file:
Code:
rm system/app/SoundRecorder.apk
Exit ADB:
Code:
exit
Copy the APK file (attached below) from your system to your phone, replacing path/to/file with the location of your file (e.g. c:\android) as detailed in previous post.
Code:
adb push [I]path/to/file/[/I]SoundRecorder.apk system/app
Reboot phone (might be optional):
Code:
adb reboot
(THE REAL) Neo said:
I've not used adb,but manually copied the .apk to system/app after renaming of original file.
Obviously i've used EsGestore File,with root permissions/root mounted read and write.
File copied perfectly,rebooted phone.
But nothing happens...
Neo on Nexus S with Tapatalk®
Click to expand...
Click to collapse
I'm sorry, I'm not familiar with using third-party apps for file management duties. Assuming that everything else you're doing is correct, try using the APK file attached below.

XK72 said:
This may not be the most efficient way of doing this, but it always works for me. Assuming that you have root permissions on the phone, try the following steps:
Access the phone through ADB:
Code:
adb shell
Mount the volume as writable:
Code:
mount -o remount,rw /dev/block/mtdblock4 /system
Remove the existing SoundRecorder.apk file:
Code:
rm system/app/SoundRecorder.apk
Exit ADB:
Code:
exit
Copy the APK file (attached below) from your system to your phone, replacing path/to/file with the location of your file (e.g. c:\android) as detailed in previous post.
Code:
adb push [I]path/to/file/[/I]SoundRecorder.apk system/app
Reboot phone (might be optional):
Code:
adb reboot
I'm sorry, I'm not familiar with using third-party apps for file management duties. Assuming that everything else you're doing is correct, try using the APK file attached below.
Click to expand...
Click to collapse
Using this apk,the phone shows me an app called "Recorder" in the app drawer,but i can't tap it,and all the icons showed in the same page of the app drawer.If i change page,icons of other pages are selectable...weird thing...
Now i'm rolled back to previous apk file and everything works...so scary...
Neo on Nexus S with Tapatalk®

[Guide]How to prepare a stock rom for modification (written for beginners)

How to prepare your i9001 stockROM for modding
First of all I want to say that I know that there already are tutorials about this, but this is just my sites "well explained aio tutorial" that everyone should be able to follow successfully, just as my other tutorials. I added loads of screenshots to make everything a lot easier. So please no complaining about duplicates
Short description:
In this tutorial I will explain you how to prepare a stock rom for modding, the files in this tutorial (cwm and root) are for the Samsung Galaxy S Plus (GT-i9001) only!
The deodex part will work for every device, So if you have an other device then the i9001 you can only follow the deodex part if you would like to.
General notes
- I know I already made a tutorial about how to root the i9001, but this method is faster and easier, so forget the old method and use this one!
- In this tutorial I assume that you have installed your new stock ROM (or still have the original one) and made no modifications to it yet (this excludes apps & settings)
Chapters:
1. ClockWorkMod Recovery (CWM)
2. Getting full access to your system files (Root)
3. How to make system apks available for modding (Deodex)
Chapter 1. ClockWorkMod Recovery
The first step of this guide is to get rid of the stock recovery, the stock recovery is very useless if you compare it to CWM.
CWM is a custom recovery that it known worldwide, it has a great number of options and actually should be installed by default on any smartphone!
The method of flashing the recovery will be Odin (Mutli Downloader 4.43), this method doesn’t require root access and is very trusted.
What you have to do on your pc:
1. Download and unpack Odin and AriesVE.ops
2. Download and unpack CWM v5.5.0.4 (ICS Compatible)
3. Download and install Samsung USB Drivers
4. Now go to the folder where you extracted odin and AriesVE.ops, and open odin (Multi_Downloader_v4.43_with_smd0425.exe)
{
"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"
}
5. Click on the “OPS” button, now choose the AriesVE.ops file you downloaded earlier, after this check the “One package” checkbox
6. Now click the “One Package” button and choose the “recovery-clockwork-5.5.0.4-ariesve.tar.md5″ file you downloaded earlier, now it will perform an md5 check
7. Now turn off your i9001 if it’s on at the moment.
8. Turn it on by holding: Volume Down + Home + Power (hold it for about 6 seconds) until the Download Mode comes
9. Now put the USB cable in your phone and computer, your computer will now install all needed drivers
10. Once the driver installation is complete you will see a yellow block in your upper left odin window
This means it’s detected and ready to flash
11. Now click the “Start” button and the flashing will start
(as you see this process only takes a few seconds)
12. Now your phone will reboot and CWM is installed correctly. (You can also press the “Volume up + Power” buttons when you see the Samsung logo (when odin reboots your phone), It will force your device to go to cwm.
What I strongly advice is to make a backup of your current rom (backup & restore > backup)
Now see the next chapter for quick rooting!
Chapter 2. Getting full access to your system files (Root)
Once CWM is installed it’s very easy to root your phone very fast.
1. Download Root-i9001-Signed.zip or scan this barcode on your phone:
2. Put the zip on your sdcards root, and turn off your phone.
3. Now turn your phone on by holding: Volume Up + Power, when you see the Samsung logo wait another 2/3 sec and then release both buttons.
4. Now CWM Recovery will show, use the volume buttons to scroll up and down, use the home button to choose something
5. Scroll to “install zip from sdcard” and press the home button
(using the volume down button to go down in the menu)
(after pressing home in main menu)
6. Now Press home again to go to “choose zip from sdcard, this will let you browse your internal sdcard, now search for the root-i9001-signed.zip file
(my sdcard is a bit messy ^^)
7. When you found the zip press Home to choose it
8. Now scroll up (it’s faster then down) until you reach Yes, then press the home button again. This will install the root zip on your phone
9. Now press the back button once to return to the main menu, with “reboot system now” selected, press the home button once to reboot your phone
10 . When your phone is rebooted you should look for the SuperUser app and open it, now press the menu button and choose “Preferences”
11. Now scroll all the way down to Superuser information, then press the second button “Su Binary v3.0-beta2″, this will open the updater
(dutch language)
12. As you see it’s outdated and needs to be updated, press the Update button to do this
13. Now the updating will start, and soon SuperUser will ask for SuperUser permissions, click Grant
(dutch language)
14. After clicking grant the update process will continue and will be done in a few seconds
15. Now your Su Binaries are updated you need to update the app itself, just go to the market and search for “Super User”
16. Choose the one contributed by: ChainsDD, now click the “Update” button to update it. You are now done with the rooting.
Chapter 3. How to make system apks available for modding (Deodex)
Requirements for deodexing:
- Android SDK (x86)
- Java Development Kit (x86)
- Busybox Installed on your phone (the download from the market is the installer, so you will need to run the app to install it)
1. Download xUltimate Script v2.3.3, unpack it in some folder and if you have an anti-virus, scan the jar folder and add “auto_app.exe” and “auto_frame.exe” to exclusions/trusted files. (at least my anti-virus thinks it’s dangerous, but it’s not..)
2. Run “Main Skip.bat”, now the main menu of xUltimate will open
3. Now connect your phone in debugging mode to your pc (but not in mass storage mode!), and choose “1″ then press enter, this will pull all system apps from your device
4. When the pulling is complete choose “2″ and press enter, this will pull all system framework files.
5. Now that you’ve collected all apks/odex files, you will probably need to remove these apks from the “origi_app” folder, since they will probably fail to deodex.
- GoogleQuickSearch.apk / GoogleQuickSearch.odex
- Maps.apk / Maps.odex
- Phonesky.apk / Phonesky.odex
- PlusOne.apk / PlusOne.odex
- Voicesearch.apk / Voicesearch.odex
These apps can be redownloaded at the market later! (Phonesky is just the market installer, not the actual market installation)
6. Now choose “3″ and press enter, now the deodexing of the system apps will start.
This may take a while, but at least it will deodex until the end, since the trouble makers are already removed.
7. When the deodexing of the system apps is done you will return to the main menu, now choose “4″ and press enter to deodex the framework files
Luckily deodexing the framework goes a lot faster then the apps. When this process is also done you will have 2 output folders, called “done_app” and “done_frame”
8. What you will need to do is copy both folders to your internal sdcard’s root (since you’re still in debugging mode, drag down the status bar and click on the usb notification, then click on “Mount Storage” to mount your internal sdcard on your computer (Mass Storage Mode)
9. After you copied both folders, you need to press “Unmount Storage” on your phone, now it will be back in normal debugging mode, keep the usb cable in because we are not done yet.
10. Download ADB (Android Debug Bridge) and unpack it in some folder, Now in that folder “Shift+Right Click” at some empty spot > Open command window here (This is only for Windows 7). XP users will have to open cmd manually and “cd” to the adb directory
11. Once your in cmd, enter the following commands to successfully deodex your phone (an explanation of the commands can be found below them, make sure you don’t enter the symbols as well, I added those so you can see if you’re in the right mode)
> adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
$ su
# stop
# mount -o remount rw /system
# rm /system/app/*.odex
# rm /system/framework/*.odex
# busybox cp /sdcard/done_app/* /system/app/
# busybox cp /sdcard/done_frame/* /system/framework/
# busybox chmod 644 -R /system/app/*
# busybox chmod 644 -R /system/framework/*
# reboot
What did those commands actually do?:
“adb shell” – opens a shell interface for your phone, this is the same as a unix shell
“su” – asks for superuser permissions (and gets it right away)
“stop” – this command freezes your phone completely, except the adb traffic, that means you can replace system files without crashing your device
“mount -o remount rw /system” - this remounts the system partition but writable
“rm /system/app/*.odex” / “rm /system/framework/*.odex” – This deletes the old .odex files which are not needed anymore after deodexing
“busybox cp /sdcard/done_app/* /system/app/” / “busybox cp /sdcard/done_frame/* /system/framework/” – This copies the apks from the folders in your sdcard to the right destination.
“busybox chmod 644 -R /system/app/*” / “busybox chmod 644 -R /system/framework/*” – This command sets the permissions to RW-R-R, some users say it’s not needed but just remember to do it always, it’s a good thing! (and bad permissions may even crash your device)
“reboot” – well, I think you know what this does.
Ok so If you entered all commands correctly your phone will now reboot and succeed to boot. be ware that it takes a lot longer then a normal boot since the dalvik-cache has to rebuilt, this takes about 1 minute and 30 seconds at the i9001. (also depending on the amount of apps you have)
12. Now that your phone is successfully deodexed it’s ready to be customized! This means you can install Theme’s and Mod’s, but you can also do all other kinds of customization, since your phone is also rooted, such as installing Thunderbolt. But don’t forget to redownload the apps that you removed before deodexing
I hope you’ve learned something in this tutorial, I’ve already written a tutorial about rooting, but this way of rooting is just way better then the traditional method.

As always, good tutorial :good: I'll probably never need it, but good to know i could if i want.
regards

busprofi said:
As always, good tutorial :good: I'll probably never need it, but good to know i could if i want.
regards
Click to expand...
Click to collapse
Thanks . The tutorial is really focussed on beginners, so they have a well explained tutorial to follow, that they will probably understand the first time they read it. (atleast I hope they do ^^)

broodplank1337 said:
Thanks . The tutorial is really focussed on beginners, so they have a well explained tutorial to follow, that they will probably understand the first time they read it. (atleast I hope they do ^^)
Click to expand...
Click to collapse
:thumbup: Always the Best!!!
Sent from my GT-I9001 using xda app-developers app

raptor92 said:
:thumbup: Always the Best!!!
Sent from my GT-I9001 using xda app-developers app
Click to expand...
Click to collapse
Thanks And the good thing is, I keep getting new idea's for apps and tutorials. my idea source will never go dry! (I guess, since sometimes I suddenly have 3 new apps in my mind, that I can make) In a few years I will have loads of stuff lol (If I keep this tempo of developing/writing tutorials)

Wow another awesome noob-friendly guide. Love your work. Keep it up.
Sent from my GT-I9001 using xda premium

iCloud said:
Wow another awesome noob-friendly guide. Love your work. Keep it up.
Sent from my GT-I9001 using xda premium
Click to expand...
Click to collapse
Thanks will do, btw I just noticed that I forgot to post all links! (I just copied it from my blog without thinking about all links). my mistake

I respect your work.thanks for the tutorial,exactly what I need.

john9 said:
I respect your work.thanks for the tutorial,exactly what I need.
Click to expand...
Click to collapse
Thank you, you're welcome Nice that it's exactly what you need haha

broodplank1337 said:
Thank you, you're welcome Nice that it's exactly what you need haha
Click to expand...
Click to collapse
Brood, i have a question on this. After deodexed the app and jar files can these file considered as zipaligned? Because i found that it take a lot of memory compared to the odexed ROM. However, in the xUltimate there is a optimization command available to optimize all the apk files but it also bring many FC after push all the files to the phone.

DreamerTKM said:
Brood, i have a question on this. After deodexed the app and jar files can these file considered as zipaligned? Because i found that it take a lot of memory compared to the odexed ROM. However, in the xUltimate there is a optimization command available to optimize all the apk files but it also bring many FC after push all the files to the phone.
Click to expand...
Click to collapse
The deodex process calls it aligning, and I'm not sure if that's really a zipalign, but it's very easy to zipalign, just run the attached "03zipalign" in script manager, (with su icon checked), But the fc's are are not normal, you must have made a mistake somewhere, do you still have the odex files inside /system/app and system/framework for example?

broodplank1337 said:
The deodex process calls it aligning, and I'm not sure if that's really a zipalign, but it's very easy to zipalign, just run the attached "03zipalign" in script manager, (with su icon checked), But the fc's are are not normal, you must have made a mistake somewhere, do you still have the odex files inside /system/app and system/framework for example?
Click to expand...
Click to collapse
Nope. During the push process i already write the remove command in adb to delete them all. For the FC case this won't happen if i didn't run the command in xUltimate>Advanced>Optimize all apk>Extreme.
After the optimization i found out that the apk files become smaller in size but sometimes some of the apk will get FC in phone. What i have experienced are camera.apk, AxT9IME.apk, Phone.apk and so on.

DreamerTKM said:
Nope. During the push process i already write the remove command in adb to delete them all. For the FC case this won't happen if i didn't run the command in xUltimate>Advanced>Optimize all apk>Extreme.
After the optimization i found out that the apk files become smaller in size but sometimes some of the apk will get FC in phone. What i have experienced are camera.apk, AxT9IME.apk, Phone.apk and so on.
Click to expand...
Click to collapse
Well, I assume you pushed the files while in mass storage mode?, (or did you use adb push?). When you're in mass storage mode you cannot access your sdcard in adb, so what you actually do when using the remove command: nothing.
Then If you place the done_app and done_frame folder in /system/app & /system/framework you will still have the .odex files , Right?
Please follow all steps correctly, I also screwed up at my first deodexes, but when I red the whole tutorial (I believe that was the i9003 one) again it worked
But you can also use deodex packages (KQE for example) which is posted at the KQE rom topic.

broodplank1337 said:
Well, I assume you pushed the files while in mass storage mode?, (or did you use adb push?). When you're in mass storage mode you cannot access your sdcard in adb, so what you actually do when using the remove command: nothing.
Then If you place the done_app and done_frame folder in /system/app & /system/framework you will still have the .odex files , Right?
Please follow all steps correctly, I also screwed up at my first deodexes, but when I red the whole tutorial (I believe that was the i9003 one) again it worked
But you can also use deodex packages (KQE for example) which is posted at the KQE rom topic.
Click to expand...
Click to collapse
Brood, i redownload the xUltimate using the link that you provided in this forum and now the deodex process run smoothly and successfully. Finally i can manage my phone freely. Thanks again~

DreamerTKM said:
Brood, i redownload the xUltimate using the link that you provided in this forum and now the deodex process run smoothly and successfully. Finally i can manage my phone freely. Thanks again~
Click to expand...
Click to collapse
Good! You know I've only managed to deodex roms successfully using the 2.3.3 version, I just think that 2.3.3 is the magical version . Enjoy the deodex

broodplank1337 said:
Good! You know I've only managed to deodex roms successfully using the 2.3.3 version, I just think that 2.3.3 is the magical version . Enjoy the deodex
Click to expand...
Click to collapse
Really? maybe also caused by last time im using the ver 2.4 so this might be the main cause for such problem

Thanks for this guide, but (there's always a but)....
... my I9001 keeps rebooting into CWM now. Whenever I boot it, or reboot it, it will always go back into CWM. I reflashed CWM using this guide, step by step, 4 times with the same result. It's great to have CWM on the phone, but it would be nice to also use the phone as a,... well "phone".
I tried flashing Broodrom (business) and it flashes alright. No way to test it however since all I see after a reboot is,... CWM. I tried 3 different ROMs, but all I see is CWM.
Do I have a seriously strange i9001, or is there something I am missing in this guide? I've flashed quite a few phones so maybe I can't be considered to be a beginner anymore, and maybe that's why this guide won't work for me
Anyways, back to odin and stock ROM for me.

FrepA said:
Thanks for this guide, but (there's always a but)....
... my I9001 keeps rebooting into CWM now. Whenever I boot it, or reboot it, it will always go back into CWM. I reflashed CWM using this guide, step by step, 4 times with the same result. It's great to have CWM on the phone, but it would be nice to also use the phone as a,... well "phone".
I tried flashing Broodrom (business) and it flashes alright. No way to test it however since all I see after a reboot is,... CWM. I tried 3 different ROMs, but all I see is CWM.
Do I have a seriously strange i9001, or is there something I am missing in this guide? I've flashed quite a few phones so maybe I can't be considered to be a beginner anymore, and maybe that's why this guide won't work for me
Anyways, back to odin and stock ROM for me.
Click to expand...
Click to collapse
The problem you're facing is the bootloop bug in cwm, some people experience this bug, you can find the fix in this post: http://forum.xda-developers.com/showpost.php?p=24831012&postcount=1330

broodplank1337 said:
The problem you're facing is the bootloop bug in cwm, some people experience this bug, you can find the fix in this post: http://forum.xda-developers.com/showpost.php?p=24831012&postcount=1330
Click to expand...
Click to collapse
Thanks for your reply. I did try that solution before I posted (I should have mentioned it, sorry). It didn't solve my problem however. I could boot without going into recovery, but nothing would happen, so the ROM would not be loaded. I should mention however that I had no problems with a different i9001, so I might have a phone with some special issues.

# stop
# mount -o remount rw /system
# rm /system/app/*.odex
# rm /system/framework/*.odex
# busybox cp /sdcard/done_app/* /system/app/
# busybox cp /sdcard/done_frame/* /system/framework/
# busybox chmod 644 -R /system/app/*
# busybox chmod 644 -R /system/framework/*
# reboot
Click to expand...
Click to collapse
I could not do the above. when i type stop, there is no #.
Edited: I have done it. It is deodex now but when I flash the mod such as the extended toggle bar, when the the phone restart the status bar missing. How can I fix it???

[MultiTool][28/5/13]ROM TOOLS v3(dex de/recompiler with extended features)

Hi guys,
Here is third version of my ROM Tools PC Version (Automatic decompile classes.dex file to edit smali content). It is major release of this tool but further updates will follow.
After testing the third version on bunch of Devices successfully, here is the general release of it. This tool has been mainly constructed to decompile and recompile classes.dex of apk's and jar files without having to tediously type whole commands. However, there are few features I have added in it which in my opinion are useful bt not that much connected to dex operations.
What's New ?
Here is list of New features and detailed description of them:
Note:- No other fetaure except decompiling/recompiling will work if you have not connected your phone via USB cable and USB debugging is on.
Reboot Options:
Reboot:
Will normally reboot the phone
Necessary when replaced some framework file or pushed a system file
Code used
Code:
adb reboot
Click to expand...
Click to collapse
Recovery:
Reboot your phone in recovery mode
Necessary when thinking of flashing something and want to save time and instead of pressing a combo while phone is turned off.
Code used:
Code:
adb reboot recovery
Click to expand...
Click to collapse
Hot reboot: *May not work on all phones*
Reboots your phone faster
It reboots your phone faster by just killing all system processes forcing the GUI to restart. Preferred as its fast and reliable when pushing themed files. Not recommended if doing more intensive replacing(Sometimes syetem needs rebooting normally to show changes)
Code Used:
Code:
adb shell killall system_server
Click to expand...
Click to collapse
Miscellaneous:
logcat:
1. Display logcat:
Displays logcat with v long formatting with 10000+ lines.
Easy than typing whole command. Its with formatting. Has more lines than normal command prompt display
Code Used:
Code:
adb logcat -v long
Click to expand...
Click to collapse
2. Save logcat:
Saves logcat in main folder. A random prefix is added to each locat so that they do not get replaced by newer one.
Easier than typing the command. With good formatting.
Code used:
Code:
adb logcat -v long > logcat%random%.txt
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Fix permissions: *ignore errors*
Fixes permissions of /system/app, /system/framework/, system/etc/init.d
Necessary when replacing many files in system and saving time to set correct permissions. Sometimes, due to incorrect permissions, phone won't boot or scripts won't run. Very useful command to save you from these headaches.
Ignore errors because there may not be init.d folder present in your device. So it will show error for that, but all other permissions will be corrected
Code Used:
Code:
adb shell chmod 644 /system/app/*
adb shell chmod 644 /system/framework/*
adb shell chmod 777 /system/etc/init.d
adb shell chmod 777 /system/etc/init.d/*
Click to expand...
Click to collapse
Reset Password: *May not work on all devices* *Ignore errors*
Resets your pin, password, pattern lockscreen
Ignore errors because it will try to delete 4 files and there will be only one correct file to be deleted based on what type of password you have set.
May not work on all devices because I have only tested it on Gingerbread Samsung devices. *Confirmed to be working on rooted mobiles only*
Code Used:
Code:
adb shell rm /data/system/gesture.key
adb shell rm /data/system/password.key
adb shell rm /sd-ext/system/gesture.key
adb shell rm /sd-ext/system/passwork.key
Click to expand...
Click to collapse
Screenshot:
{
"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"
}
Changelog :
Code:
Version 3
28 Ma 2013
-Added Reboot
-Added Recovery
-Added Hot Reboot
-Added logcat
-Added Fix Permissions
-Added Reset Password
-Added an ugly easter egg
Version 2
18 April 2013
- Changed it from a script to multi tool
- Added folders for convenience
- Made eye candy
- Made it noob proof
- It's like changing Baichung Bhutiya to Lionel Messi
Version 1
- Just one smali.bat file and one baksmali.bat file with one one line each of commands to Baksmaling and Smaling (duh!)
PHP:
I am not responsible for your device being dead,
you flashing stock ROM,
you using your device as a brick,
or the decrease in love of your Girlfriend because you use your mobile so much
What does it do?
As you are aware, there are smali files in jar files and apks you need to edit for adding 4-way boot into power menu, extending Power options, changing clock colour, adding CRT effect, changing the pop up that comes up when you touch the easter egg image, adding brightness slidebar, adding lidroid toggles, etc and so manyyyy things
In order to edit them, you need to decompile apk and classes.dex
It is not a problem in editing smali files of apk as they are decompiled itself by APK-Multitool(I use it)
But, it does not work for jar files
I know that there is smali.jar and baksmali.jar for it but I don't like repeatedly commading same operations when I can do it with one click
This program decompiles and recompiles classes.dex from any jar or apk in one click(very useful when you only need to decompile dex file only)
Pre-Requisites:-
*PC
*My Tool
*Java JDK(or JRE) (If you are running Windows 7 64 bit, you may need to add Java in environment variable)
*7-Zip (For in zip operations[pull out classes.dex])
*classes.dex file(on which you will operate)
*Android Phone to be connected to PC with USB Debugging on to use features other than decompiling and recompiling
Guide:-
1. Download my Tool.
2. Extract it in any folder.
3. Place classes.dex in the input folder. DO NOT RENAME IT.
4. Run script.bat. Choose Option 1, Decompile classes.dex . In a few seconds, there will be a prompt that it is "Done. Press anykey to continue" (Note:- If you have UAC [User Account Control] on, you may run it as administrator or it might not be able to create folder if you have extracted it in System Drive)
5. Go to decompiled folder. There will BE classout folder. Make any changes in smali in classout folder(ALWAYS USE NOTEPAD++). DO NOT RENAME CLASSOUT FOLDER.
6. Again open script.bat if you had closed it or if not, then return to the window.
7. Choose 2 option "Compile classes.dex" . A new classes.dex will be formed in output folder.
8. Enjoy
Note:- Once you change things in classout folder, and you decompile another classes.dex, previous version in decompiled folder will be deleted. So if you want backup of it, move it somewhere else
Same thing will happen to classes.dex on output folder when you compile another one.
Other options
1. Connect you phone to PC with USB Debugging on and not on USB Tethering. Make sure you aren't using adb before using the tool. If so, Go to Alt+Ctrl+Del and to Task Manager and close adb.exe process
2. Choose the option what you want.
a) Logcat, either view or save it
If you view it, a window will appear with logcat in it. If you are done, just close that window
If you save it, it will be saved in the same folder where Script.bat is present. To stop saving it, Press Ctrl+C and type Y and press Enter
b) Reboot, may take some time in rebboting and rebooting in recovery.
c) Fix permissions and Reset password
3. Try to find Easter Egg
Download:-
ROMToolsPCv3.zip

Reserved

Definitely easier than the "java -jar smali.jar..." command.
Thank you.

Trying it out...

Thank You all
If you have suggestions, please post them here.

Great tool .Try to make one for resources also :thumbup:
Sent from my GT-I9082 using Tapatalk 2

balliboxer said:
Great tool .Try to make one for resources.dex also :thumbup:
Sent from my GT-I9082 using Tapatalk 2
Click to expand...
Click to collapse
Sure
Didn't knew there were such files too

balliboxer said:
Great tool .Try to make one for resources.dex also :thumbup:
Sent from my GT-I9082 using Tapatalk 2
Click to expand...
Click to collapse
Can you tell me which file contain these?
I searched it but did not find much
Are you talking about resources.arsc?

iamareebjamal said:
Can you tell me which file contain these?
I searched it but did not find much
Are you talking about resources.arsc?
Click to expand...
Click to collapse
Yea resources.arsc mistakenly written.dex
Sent from my GT-I9082 using Tapatalk 2

balliboxer said:
Yea resources.arsc mistakenly written.dex
Sent from my GT-I9082 using Tapatalk 2
Click to expand...
Click to collapse
Umm. That is automatically done by apktool
I did not find any way to do it separately

iamareebjamal said:
Umm. That is automatically done by apktool
I did not find any way to do it separately
Click to expand...
Click to collapse
But in apktool we have to manually put commands and sometimes it give error.
Sent from my GT-I9082 using Tapatalk 2

balliboxer said:
But in apktool we have to manually put commands and sometimes it give error.
Sent from my GT-I9082 using Tapatalk 2
Click to expand...
Click to collapse
Use apk multitool or vts instead

Linux Multitool
iamareebjamal said:
Thank You all
If you have suggestions, please post them here.
Click to expand...
Click to collapse
Here is something equal written for Linux.
http://d-h.st/UEh
Hope you like it.
Greetings.

Version 3 Released and OP Updated *Major Release*

iits cool dude thanks it helps a lot

badagila said:
iits cool dude thanks it helps a lot
Click to expand...
Click to collapse
Thanks. But don't quote the whole OP for saying something.
It takes some extra scrolls to move down o the point.
So, can you please remove the quote from you post?
----------------------------------------------------------------------------------------------------------------------------------------------------------
And guys, reset lock feature is now confirmed to be only working on rooted phones
Cheers

I can confirm "reset password" worked on sgs3 i727 on aokp rom, it still asking for a patron but any patron unlock it, for pass lock or pin it just reset it to default, big work thx

juancollado2003 said:
I can confirm "reset password" worked on sgs3 i727 on aokp rom, it still asking for a patron but any patron unlock it, for pass lock or pin it just reset it to default, big work thx
Click to expand...
Click to collapse
Yes, it works like that only
It will show the password screen but phone will get opened if you input any password
Funny though (Good for trolling people)

juancollado2003 said:
I can confirm "reset password" worked on sgs3 i727 on aokp rom, it still asking for a patron but any patron unlock it, for pass lock or pin it just reset it to default, big work thx
Click to expand...
Click to collapse
Yes, it works like that only
It will show the password screen but phone will get opened if you input any password
Funny though (Good for trolling people)

Does this work on linux?

FIX for Monkey Test & Time Service Virus (Without Flashing)

Hello everyone,
This method I'm going to write is tried on my own Lenovo A7600-H Kitkat 4.4.2 tablet, which I did not flash because I'm not sure about stock roms available on the net. If I had found a reliable rom I wouldn't be able learn this
To remove this virus you need to install busybox, Terminal emulator, Root explorer pro and you must have Supersu not superuser which is installed by Kingoroot. If you have rooted your device with kingoroot, so you need to change that.
Here is how to change that:
Google this: how to get ride and replace kinguser with supersu app (Follow first zidroid link)
I'm not able to submit links so im going to write the exact apps with developer names to download from Playstore.
Busybox Installer by JRummy Apps Inc.
Terminal Emulator by Jack Palevich
Root Explorer Pro by Speed Software
Once you have installed everything here is what to do in steps:
[Note: USB DEBUGGING MUST BE ENABLED Turn on Usb Debugging by going to settings> developer options> Usb debugging]
1) Turn off wifi/3G/4G, and then go to settings> apps> all> disable time service and monkey test. (If already frozen via titanium backup or other app) skip this.
2) Open Root explorer go to system/xbin and see if there is any file starting with a dot (eg: .ext.base) also note that every (.) file has diff permission then the rest of other files. So just remember those files with dots because those are the one that you're going to remove in terminal emulator.
3) Go back to system and then go to Priv-app folder and look for these two files
[1] cameraupdate.apk [2] providerCertificate.apk and also notice permission of these two files are different then the rest of Apks so these two are the base of MT TS virus and needs to be deleted.
4) Open Terminal Emulator OR if you have access to your device via adb from a computer.
5) WHAT TO TYPE IN TERMINAL EMULATOR or ADB (CMD Windows)
adb devices (Type this line if you're using adb Windows)
adb shell
su
mount -o remount,rw /system
cd system/priv-app
chattr -iaA providerCertificate.apk
rm providerCertificate.apk
chattr -aA cameraupdate.apk
rm cameraupdate.apk
cd ..
cd system/xbin
chattr -iaA .b
rm .b
chattr -iaA .ext.base
rm .ext.base
chattr -iaA .sys.apk
rm .sys.apk
[NOTE: If you are using older version than KK you need not to type priv-app just type cd system/app]
6) Please make sure you type the file name correctly just as providerCertificate C is capital otherwise permission wont change.
7) Exit Emulator/ADB
8) Go to settings> apps> all> send me the screenshot if you have Monkey test or Time Service there
9) I'm 100% sure if you've followed everything as I mentioned you are good as new and you don't need to flash.
10) I'm not a developer and That's it!

Money test and time service virus removal
In karbonn A 30
x-bin has these files :
.b
.ext.base
.sys.apk
root/system has no priv-app but app file, it has two files:
SettingProvider.apk
cameraupdate.apk
I have given command cd system/app
followed by
chattr -iaA SettingProvider.apk
....Error...
chattr-iaA not found
WHAT TO DO ?

drdkundu said:
In karbonn A 30
x-bin has these files :
.b
.ext.base
.sys.apk
root/system has no priv-app but app file, it has two files:
SettingProvider.apk
cameraupdate.apk
I have given command cd system/app
followed by
chattr -iaA SettingProvider.apk
....Error...
chattr-iaA not found
WHAT TO DO ?
Click to expand...
Click to collapse
If you don't have a priv-app folder than you are not on Kitkat and you have to delete files from system/app folder.
Well anyway you have to delete cameraupdate.apk and providerCertificate.apk
and you are deleting SettingProvider.apk which I never said you have to.
Please look closely

Nuh99 said:
If you don't have a priv-app folder than you are not on Kitkat and you have to delete files from system/app folder.
Well anyway you have to delete cameraupdate.apk and providerCertificate.apk
and you are deleting SettingProvider.apk which I never said you have to.
Please look closely
Click to expand...
Click to collapse
Dearest,
It is 4.0.4 ics , in app folder there is no providerCertificate.apk but SettingProvider.apk which is newer (as per date also AVG prompted it as malware and tried to uninstall but failed) than the original SettingProvider.apk ,i tried to insert screenshots,but prevented by forum thanks if you may share with me your email address i may be able to post
command : chatter... gives error message, is there different procedure for ics ?
Secondly,
I have searched out that karbonn A 30 is a rebranded version of vsun I 1S ,and original rom based on kitkat is available on their site, is it safe to flash vsun rom on it or shall I go for abacada rom available on xda?

drdkundu said:
Dearest,
It is 4.0.4 ics , in app folder there is no providerCertificate.apk but SettingProvider.apk which is newer (as per date also AVG prompted it as malware and tried to uninstall but failed) than the original SettingProvider.apk ,i tried to insert screenshots,but prevented by forum thanks if you may share with me your email address i may be able to post
command : chatter... gives error message, is there different procedure for ics ?
Secondly,
I have searched out that karbonn A 30 is a rebranded version of vsun I 1S ,and original rom based on kitkat is available on their site, is it safe to flash vsun rom on it or shall I go for abacada rom available on xda?
Click to expand...
Click to collapse
Send me screenshot or personally talk to me on www(.)facebook(.)com/99nuh
Btw you are unable to remove providersettings.apk because you might be typing wrong attributes for it.
To see its attribute cd system/app [enter]
then type lsattr to look for attributes of providersettings.apk
and then use those attributes with - and rm that file.
And If you want to flash your phone/tablet go with your brand official rom.

screenshots
Nuh99 said:
Send me screenshot or personally talk to me on www(.)facebook(.)com/99nuh
Btw you are unable to remove providersettings.apk because you might be typing wrong attributes for it.
To see its attribute cd system/app [enter]
then type lsattr to look for attributes of providersettings.apk
and then use those attributes with - and rm that file.
And If you want to flash your phone/tablet go with your brand official rom.
Click to expand...
Click to collapse
Screenshots below:
please add http.. before
//photos(dot)google(dot)com/photo/AF1QipNuigMsljp-1jsPLPqo_QuG_27vDUHS-DzSZZi-
//photos(dot)google(dot)com/photo/AF1QipMUmGdmU7TyETRaomzJzzKSuFYOiW7e53urGT6P
//photos(dot)google(dot)com/photo/AF1QipMRD8sJA0j84yHIzYSohk4KDggUTw2iTcGKZ7mU
//photos(dot)google(dot)com/photo/AF1QipNZQ7TTbDGrDNSMKMAtCt5I7P8_1QFQMyVRi6-_

drdkundu said:
Screenshots below:
please add http.. before
//photos(dot)google(dot)com/photo/AF1QipNuigMsljp-1jsPLPqo_QuG_27vDUHS-DzSZZi-
//photos(dot)google(dot)com/photo/AF1QipMUmGdmU7TyETRaomzJzzKSuFYOiW7e53urGT6P
//photos(dot)google(dot)com/photo/AF1QipMRD8sJA0j84yHIzYSohk4KDggUTw2iTcGKZ7mU
//photos(dot)google(dot)com/photo/AF1QipNZQ7TTbDGrDNSMKMAtCt5I7P8_1QFQMyVRi6-_
Click to expand...
Click to collapse
They are not opening. Error!
Kindly send me @ my fb.

Thanks, its work, no more monkey test and Time service on my android.
before: my Malwarebytes detect there are virus cameraupdate.apk;MusicProvider.apk;
LiveWallpaper.apk;SistemCertificate.apk and providerCertificate.apk .so i delete all on system/app. all can delete except cameraupdate.apk
I try your way but i have different case on my ColorOS android 4.2.2
Using App Master(EasyApps Studio) i find that :
monkey test refer to sytem/app/cameraupdate.apk
but time service refer to data/app/com.android.hardware.ext0-1.apk
so i add
cd data/app
chattr -iaA com.android.hardware.ext0-1.apk
rm com.android.hardware.ext0-1.apk
with Root explorer browse root directory and sd card search cameraupdate.apk and com.android.hardware.ext0-1.apk after find check list all then delete.
No need clear cache just delete
/data/dalvik-cache/[email protected]@[email protected]
/data/dalvik-cache/[email protected]@com.android.hardware.ext0-1.apk @classes.dex
This work
Thanks
Note:
if you find ...Error... chattr -iaA not found
WHAT TO DO ? its mean you only install app not yet istall busybox
after install Busybox Installer by JRummy Apps Inc. from play store open app
on tab installer, select busybox ver1.2 select intall location /system/xbin/ then touch Install

agzpur said:
Thanks, its work, no more monkey test and Time service on my android.
before: my Malwarebytes detect there are virus cameraupdate.apk;MusicProvider.apk;
LiveWallpaper.apk;SistemCertificate.apk and providerCertificate.apk .so i delete all on system/app. all can delete except cameraupdate.apk
I try your way but i have different case on my ColorOS android 4.2.2
Using App Master(EasyApps Studio) i find that :
monkey test refer to cameraupdate.apk
but time service refer to com.android.hardware.ext0-1.apk
so i add
cd data/app
chattr -iaA com.android.hardware.ext0-1.apk
rm com.android.hardware.ext0-1.apk
with Root explorer browse root directory and sd card search cameraupdate.apk and com.android.hardware.ext0-1.apk after find check list all then delete.
No need clear cache just delete
/data/dalvik-cache/[email protected]@[email protected]
/data/dalvik-cache/[email protected]@com.android.hardware.ext0-1.apk @classes.dex
This work
Thanks
Click to expand...
Click to collapse
Yes you don't need cache clear but doing it on a safe side is better.
If this post helped you please give a thumbs up!

i can't change the permission on root explorer.
Nuh99 said:
Hello everyone,
This method I'm going to write is tried on my own Lenovo A7600-H Kitkat 4.4.2 tablet, which I did not flash because I'm not sure about stock roms available on the net. If I had found a reliable rom I wouldn't be able learn this
To remove this virus you need to install busybox, Terminal emulator, Root explorer pro and you must have Supersu not superuser which is installed by Kingoroot. If you have rooted your device with kingoroot, so you need to change that.
Here is how to change that:
Google this: how to get ride and replace kinguser with supersu app (Follow first zidroid link)
I'm not able to submit links so im going to write the exact apps with developer names to download from Playstore.
Busybox Installer by JRummy Apps Inc.
Terminal Emulator by Jack Palevich
Root Explorer Pro by Speed Software
Once you have installed everything here is what to do in steps:
1) Turn off wifi/3G/4G Open settings> apps> all> disable time service and monkey test. (If already frozen via titanium backup or other app) skip this.
2) Open Root explorer go to system/xbin and see if there is any file starting with a dot (eg: .ext.base) also note that every (.) file has diff permission then the rest of other files. So just remember those files with dots because those are the one that you're going to remove in terminal emulator.
3) Go back to system and then go to Priv-app folder and look for these two files
[1] cameraupdate.apk [2] providerCertificate.apk and also notice permission of these two files are different then the rest of Apks so these two are the base of MT TS virus and needs to be deleted.
4) Open Terminal Emulator OR if you have access to your device via adb from a computer.
5) WHAT TO TYPE IN TERMINAL EMULATOR or ADB (CMD Windows)
adb devices (Type this line if you're using adb Windows)
adb shell
su
cd system/priv-app
chattr -iaA providerCertificate.apk
rm providerCertificate.apk
chattr -aA cameraupdate.apk
rm cameraupdate.apk
cd ..
cd system/xbin
chattr -iaA .b
rm .b
chattr -iaA .ext.base
rm .ext.base
chattr -iaA .sys.apk
rm .sys.apk
6) Please see if your device xbin has more files with dots because these are three files I had so if there are more you need to remove them with the same command I mentioned above (e.g:cd system/xbin [Enter] chattr -iaA .New.file & then rm .New.file and make sure you type the file name correctly just as providerCertificate C is capital otherwise permission wont change.
7) Exit Emulator/ADB shutdown your device go to recovery clear cache and restart.
8) Go to settings> apps> all> send me the screenshot if you have Monkey test or Time Service there
9) I'm 100% sure if you've followed everything as I mentioned you are good as new and you don't need to flash.
10) I'm not a developer and That's it!
Click to expand...
Click to collapse
i can't change the permission on root explorer. can you help me to fix it..it says failed to change permission because your sdcard..........something..
plz help me

dsamivai said:
i can't change the permission on root explorer. can you help me to fix it..it says failed to change permission because your sdcard..........something..
plz help me
Click to expand...
Click to collapse
You can't change it with Root Explorer you have to change permissions with Terminal Emulator by the entering the commands I've mentioned in my guide.

Nuh99 said:
You can't change it with Root Explorer you have to change permissions with Terminal Emulator by the entering the commands I've mentioned in my guide.
Click to expand...
Click to collapse
Hi, Im a user of 8.31 O+ phone. Ive downloaded all the 3 apps youve mentioned. But after installing busybox (the app) I cant install any version of it.. thats why everytime I'll type the commands in emulator indicated above, it says error...
please help... thank you

Nuh99 said:
Hello everyone,
This method I'm going to write is tried on my own Lenovo A7600-H Kitkat 4.4.2 tablet, which I did not flash because I'm not sure about stock roms available on the net. If I had found a reliable rom I wouldn't be able learn this
To remove this virus you need to install busybox, Terminal emulator, Root explorer pro and you must have Supersu not superuser which is installed by Kingoroot. If you have rooted your device with kingoroot, so you need to change that.
Here is how to change that:
Google this: how to get ride and replace kinguser with supersu app (Follow first zidroid link)
I'm not able to submit links so im going to write the exact apps with developer names to download from Playstore.
Busybox Installer by JRummy Apps Inc.
Terminal Emulator by Jack Palevich
Root Explorer Pro by Speed Software
Once you have installed everything here is what to do in steps:
[Note: USB DEBUGGING MUST BE ENABLED Turn on Usb Debugging by going to settings> developer options> Usb debugging]
1) Turn off wifi/3G/4G, and then go to settings> apps> all> disable time service and monkey test. (If already frozen via titanium backup or other app) skip this.
2) Open Root explorer go to system/xbin and see if there is any file starting with a dot (eg: .ext.base) also note that every (.) file has diff permission then the rest of other files. So just remember those files with dots because those are the one that you're going to remove in terminal emulator.
3) Go back to system and then go to Priv-app folder and look for these two files
[1] cameraupdate.apk [2] providerCertificate.apk and also notice permission of these two files are different then the rest of Apks so these two are the base of MT TS virus and needs to be deleted.
4) Open Terminal Emulator OR if you have access to your device via adb from a computer.
5) WHAT TO TYPE IN TERMINAL EMULATOR or ADB (CMD Windows)
adb devices (Type this line if you're using adb Windows)
adb shell
su
cd system/priv-app
chattr -iaA providerCertificate.apk
rm providerCertificate.apk
chattr -aA cameraupdate.apk
rm cameraupdate.apk
cd ..
cd system/xbin
chattr -iaA .b
rm .b
chattr -iaA .ext.base
rm .ext.base
chattr -iaA .sys.apk
rm .sys.apk
[NOTE: If you are using older version than KK you need not to type priv-app just type cd system/app]
6) Please see if your device xbin has more files with dots because these are three files I had so if there are more you need to remove them with the same command I mentioned above (e.g:cd system/xbin [Enter] chattr -iaA .New.file & then rm .New.file and make sure you type the file name correctly just as providerCertificate C is capital otherwise permission wont change.
7) Exit Emulator/ADB shutdown your device go to recovery clear cache and restart.
8) Go to settings> apps> all> send me the screenshot if you have Monkey test or Time Service there
9) I'm 100% sure if you've followed everything as I mentioned you are good as new and you don't need to flash.
10) I'm not a developer and That's it!
Click to expand...
Click to collapse
I get also the message : chattr: not found
I tried from adb and terminal
Any idea?

Nuh99 said:
I'm not a developer and That's it!
Click to expand...
Click to collapse
Forgive me, but your statement quoted above is the only one that makes sense here. You were booted from Security Discussion thread and you move here.
You confuse people, give nonsensical advice and don't seem to know what you are talking about. First of all the chattr command is not supposed to work on Android ext4, so, no wonder people can't remove files this way. And anyway, your prolong instructions are not worth the "paper" they are written on. Even if someone would succeed following them, there is no guarantee they remove the virus. The proper way is to completely reformat your phone including internal SD and external SD, which you do in recovery by formatting System, Cache, Dalvik cache, Data and both sd cards. Period. And for the future, don't install any third party apps unless you compile them from source by yourself or someone you trust.

OK

joshuas_79 said:
I get also the message : chattr: not found
I tried from adb and terminal
Any idea?
Click to expand...
Click to collapse
If you are having this error it means you have installed busybox app not busy box.
To do this open busybox app in your device, select busybox ver1.2, select intall location /system/xbin/ and tap install.
Then try the procedure

optimumpro said:
Forgive me, but your statement quoted above is the only one that makes sense here. You were booted from Security Discussion thread and you move here.
You confuse people, give nonsensical advice and don't seem to know what you are talking about. First of all the chattr command is not supposed to work on Android ext4, so, no wonder people can't remove files this way. And anyway, your prolong instructions are not worth the "paper" they are written on. Even if someone would succeed following them, there is no guarantee they remove the virus. The proper way is to completely reformat your phone including internal SD and external SD, which you do in recovery by formatting System, Cache, Dalvik cache, Data and both sd cards. Period. And for the future, don't install any third party apps unless you compile them from source by yourself or someone you trust.
Click to expand...
Click to collapse
but my problem is that I can't find firmware for my tablet: engel tb0725ips

joshuas_79 said:
but my problem is that I can't find firmware for my tablet: engel tb0725ips
Click to expand...
Click to collapse
Get a custom rom. If there is no custom rom, then do a factory reset and then format external and internal sd cards.

Brother Nuh has helped me solving cameraupdate and time service android malwares without flashing, may the Almighty bless him abundantly I really learnt some new things from him Thumbs Up for Brother Nuh:good:

optimumpro said:
Get a custom rom. If there is no custom rom, then do a factory reset and then format external and internal sd cards.
Click to expand...
Click to collapse
I can't find a custom recovery either, so only stock recovery with not many options. :crying:

Database Info

welcome