Database Info

[How-To](UPDATED 11/1/10)Working Marketplace in 2.2 Emulator (no system.img)(ROOTED)

This all started out as an experiment to get my nandroid system.img file running in the adb emulator. Well sadly I haven't been able to do that (yet) but I have found something useful. I've Seen several people all over asking how to get a working marketplace app in 2.2 on the adb emulator. After a lot of researching (and trial and error) I've managed to get one. Here are the steps I've taken. (Steps 5 and 6 optional, you can just use the included build.prop if you prefer)
1) Create an avd running 2.2 (froyo,plenty of places explain how to do this so I won't)
2) Download the file (attached below, root files included)
3) Unzip to a location that's easy to remember and find.
4) Load your emulated phone (allow it to load fully)
5) enter this command in a command prompt/terminal window (make sure you "cd" to the directory where you extracted the files)
Code:
adb pull /system/build.prop
6) Remove or comment "ro.config.nocheckin=yes" (no quotes, might be able to just change it to "no" but I haven't tried it that way)
7) enter these commands
Winblows (I mean windows)
Code:
adb remount
adb push build.prop /system/build.prop
adb install GoogleServicesFramework.apk
adb install Vending.apk
adb install Gmail.apk (optional but sometimes signing in here lets the market sign in)
adb shell rm /system/app/SdkSetup.apk
Linux
Code:
adb remount
adb push ./build.prop /system/build.prop
adb install ./GoogleServicesFramework.apk
adb install ./Vending.apk
adb install ./Gmail.apk
adb shell rm /system/app/SdkSetup.apk
8) Sign in. If it works you're done if not reboot and try again, sometimes it takes 3 or 4 reboots to set. If your emulated phone has a data signal from your computer (you'll see a 3G and network icon in the notification area) just wait for it to sign in. The cancel button should grey out within a minute. If it says it can't connect restart the emulator and try again, be patient.
There is a known bug that not all apps show up in the marketplace. I'm not sure why so if someone here knows how to fix that by all means leave a post and let me know. If I see it I'll add it to the first post (provided it works of course )
Edit: Working on getting root on the emulator (just for the hell of it). So far I have su in the xbin directory and superuser.apk installed. Not 100% sure what else I need to do to get the su requests to go through though, I'll probably PM a more experienced member and post back when I have more. Got root? I do (got it working.) Here are the steps you need to take.
Rooting the standard android image on the emulator
1) Open a command prompt (cd to the directoy where you extracted the files)
2) enter these commands
Code:
adb shell mount -o rw,remount -t yaffs2 /dev/block/mtdblock03 /system
adb push su /system/xbin/su
adb shell chmod 06755 /system
adb shell chmod 06755 /system/xbin/su
adb install superuser.apk
That's it! You now have a rooted, market-enabled android emulator.
New! N00b-friendly method
1) create your avd
2) download the emulator files archive attached to this post
3) extract somewhere easy to find
4) open command prompt/terminal and cd to the extracted location
5) start your avd
6) Run your script (windows.bat or linux.sh)
7) sign into market and enjoy root!
Note:
You may have to chmod su again upon restarting the emulator.
To get root back simply run the re-root script for your OS (bat for windows,sh for linux)
To install busybox simply run the re-root script, it will automatically install if you're using the script to install on a new avd.

Post 2
[reserved for updates, explanations, pictures, present/future tweaks in progress, etc]
Pictures:
Superuser list,Marketplace (I like solitaire><), Terminal with su permissions, and re-rooted Terminal​
{
"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"
}
Tweaks:
1: root (done!)
2: busybox (done!)

Wow nice....

Thank you the root resets after reboot, working on making it stick but its not hard to do it again, just start with the "-wipe-data" command and redo the root, market works after reboot though. Still working on getting a dumped system.img to boot, ill post that in its own thread when i get it. Glad you like this.
Sent from my ROOTED T-Mobile myTouch 3G Slide using XDA App
Edit: see first post on how to get root back,no data-wipe!

so cool!! Good job man!

Thanks ^_^ let me know if you find any problems that I haven't already mentioned and I'll see if I can fix them or if they're just an emulator quirk.

Sorry for the double post but I wanted to let you all know busybox is now included! Installation can be performed through scripts (included in the "Emulator Files.rar" archive) or manually. If you wish to do it manually simply open the script in a text editor to see what's going on and enter the commands in a command prompt/terminal window.

I'm not able to make this work, not with a toolkit downloaded yesterday anyway.
Pulling of build.prop works, but pushing fails with a directory related error.
"adb shell" followed by "cd /system" and "ls -l" gives a list of files that does not include build.prop, neither as a file nor as a directory.
"ls -l build.prop" works though, and lists a file with 0644 permissions.
Install of all apks different from Gmail fails, with an error that says that those apks are already installed. Uninstalling them through adb doesn't work, netting instead a simple generic error.
Does anyone know whether I'm doing something wrong or Google has modified the emulator images so to render the Market workaround unusable? If so, where could I download an earlier version of the 2.2 system image?
Many thanks
Rocco

I actually had this issue as well. Try re-making the avd, worked for me. You could also try running the scripts to install, might work. If it doesnt post back and ill post the system.img from my sdk.
Sent from my ROOTED T-Mobile myTouch 3G Slide using XDA App

I have the same problem as ropi. Remade the avd several times with different properties, still no go.
I would really appreciate it if someone could upload a fully set-up avd somewhere.

I'll try again late this afternoon (I'm on CEST). Hope it works. If not, I'd be happy too if some kind soul would upload a link to a working avd
Thanks for the kind help
Rocco

I have no idea why people are having so many problems :/. I had the problem and once I remade the avd it went away. Try starting with the -partition-size 96 option and see if that helps. If not here are the files, just extract to your avd directory, it has the ini and img files you need and it's already setup. Just run re-root to get root back and sign into market and you're good to go.
http://hotfile.com/dl/79959332/3efbade/froyo-avd.rar.html
Edit: I just downloaded the latest revision and everything seems to be working fine :/ As I've said before try starting with -partition-size 96 and also try using the scripts I've provided. That should fix the issues, but if it doesn't there's always the hotfile link I've provided (or if you're just lazy lol)
Edit 2: also,just thought of this, make sure before you push the build.prop you adb remount. Pulling will work fine without doing that but pushing won't. No one said if they had done this and still received the errors so I'm trying to cover all bases. If remount fails try the adb shell mount command posted on the first page.

Thanks dbzfanatic, that avd worked great.

Glad it worked for ya. Let us know how everything works.
Sent from my ROOTED T-Mobile myTouch 3G Slide using XDA App

A lot of apps can not be found in the Market ... I cannot find Lookout....

Yeah, I've mentioned that,firs post. It's a known bug. Nothing I can do to fix it at the moment. You could download the apk on your phone then pull it then install it in the emulator. Bit of a roundabout way of doing things but it's all we can do on the emulator for the time being, at least from what I know.

Ok after a bit of poking around (sorry it took so long) I found out a bit about the market. It seems it's not just your region that it uses to show apps but things like your carrier, presence/absence of a SIM card, Android version, etc. It uses the filters to choose which apps to show and which to exclude (not showing an American user Japanese apps, not showing someone on Verizon T-Mobile apps, etc) so this explains part of the problem. I also found out that the SIM card and IMEI numbers were(are?) hard-coded into the emulator binary, changing these may allow us to see a few more apps. I looked through the binary file a bit and didn't find anything but I'll look more closely in a bit (new job, yay <- read as "groan"). I don't know how to emulate or spoof a carrier so that will still cut us back on some of the apps being seen. If anyone knows how to do this please post here and let us know! It would also be beneficial if a user who has already modified their IMEI and SIM numbers in the emulator to compare the apps list to the one you see in the standard, non-modded emulator binary and let us know if there is a difference or not. The more apps we can see in the marketplace the better!

Just wanted to confirm that I've tried Market Enabler a few days ago and it doesn't seem to work.

Alright thanks for the feedback. Ill keep working on it.
Sent from my ROOTED T-Mobile myTouch 3G Slide using XDA App

Despite several tries, I've so far been unsuccessful in using this method to install the marketplace on a 2.2 avd. Many thanks for having provided ready-made avds, then!
I've been able to install marketplace on the Galaxy Tab images provided by Samsung, though!
Keep up the good work

[GUIDE] How to ROOT your “Bird v1277” MTK 6577 Dual SIM mobile phone

Found this on the Internet not my work, I now have a ROOTED fully working mobile running Ice Cream Sandwich, all credit goes to "TPSparky" for the development of the software.
{
"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"
}
First of all, go to the settings - Developer options and check "USB debugging"
Your phone NEEDS to be recognized as an "ADB Device" in "Device Manager" on your pc, or else this won't work!
Download this file:
https://rapidshare.com/files/1767087805/4.0root.rar
Unpack the RAR.
Double click the TPSparkyRoot.bat
TAKE YOUR TIME!!! Your phone will re-boot several times, be patient!!! The procedure should look something like this:
Once it's successful, your phone should now have a "Superuser" app installed and it should be rooted
YOU ARE DOING THIS AT YOUR OWN RISK!!!!

Will that not stop the Dual Sim Function on hte mobile phone I presume we are on about the same product.
Is this the same product as yours.
http://www.freeyourmobile.com/produ...SIM-Phone-with-4.3inch-touch-screen-M306.html

Can you upload pics somewhere else? Imageshack links are dead.

freeyourmobile said:
Will that not stop the Dual Sim Function on hte mobile phone I presume we are on about the same product.
Is this the same product as yours.
http://www.freeyourmobile.com/produ...SIM-Phone-with-4.3inch-touch-screen-M306.html
Click to expand...
Click to collapse
IcedFlame said:
Can you upload pics somewhere else? Imageshack links are dead.
Click to expand...
Click to collapse
Hi freeyourmobile, Yes it looks the same as my BIRD V1277 mobile.
Hi IcedFlame, no problem, but can you tell me where I should re-upload the pictures to?
RESPECT...

freeyourmobile said:
Will that not stop the Dual Sim Function on hte mobile phone I presume we are on about the same product.
Is this the same product as yours.
http://www.freeyourmobile.com/produ...SIM-Phone-with-4.3inch-touch-screen-M306.html
Click to expand...
Click to collapse
Hi freeyourmobile, dual sims work just fine.

chunky2 said:
Hi IcedFlame, no problem, but can you tell me where I should re-upload the pictures to?
RESPECT...
Click to expand...
Click to collapse
imgur (.com)
tinypic (.com),
photobucket (.com)
postimage (.org)
Thanks :good:

Hi All, Re-uploaded images, this time from photobucket.
RESPECT....

Hello chunky2,
I've searched everywhere on the internet, but I did'nt find an answer.
Does this Phone have a built in compass?

weissgold said:
Hello chunky2,
I've searched everywhere on the internet, but I did'nt find an answer.
Does this Phone have a built in compass?
Click to expand...
Click to collapse
Hi, Not sure at the moment as I did a factory reset to clear out some old data and now its lock in recovery mode and I dont know how to get out of it.

Oh - I feel sorry for that.

Thanks Enelna from Hungary

V12 / v1277
I Think we should call this type of phone by its model which is V1277 and V12 respectively.
V12 looks perfectly the same as V1277 but it has MT6575 cpu which on the otherhand;
V1277 has MT6575 version 2 which they code named MT6577.
I think if we all agree with this we could identify/classify right away which phone was it whether its brand is either star, ulefone, bird or what not. Right?
By the way, Is anyone here got to try flashing a custom rom for this kind of phone like the MIUI? :fingers-crossed:

Rooting failed
I desperately need your help because i know that you are my life saver.
Model number: I9100
CPU: MTK6573
Android version: 4.0.9
Baseband version: I9100XXK13
Kernel version: 2.6.35.7-I9100
Build number: GT_I9100_01
Custom build version: 1341280728
After the first rebooting the output text is : cannot create /data/local.prop: permission denied.
I have tried it 3 times but with the same problems. Is your rooting program dedicated only for MTK 6577 because mine is MTK 6573. Do you have some clues on how to fix this. Thanks for your time in helping me out. :fingers-crossed:

possible solution
shaamt said:
I desperately need your help because i know that you are my life saver.
Model number: I9100
CPU: MTK6573
Android version: 4.0.9
Baseband version: I9100XXK13
Kernel version: 2.6.35.7-I9100
Build number: GT_I9100_01
Custom build version: 1341280728
After the first rebooting the output text is : cannot create /data/local.prop: permission denied.
I have tried it 3 times but with the same problems. Is your rooting program dedicated only for MTK 6577 because mine is MTK 6573. Do you have some clues on how to fix this. Thanks for your time in helping me out. :fingers-crossed:
Click to expand...
Click to collapse
I had a similar problem when trying to root my bird v1277 with Android 4.0.4
I ended up having to do the first steps of the script manually combining the phone's engineer menu and the adb shell.
The objective is to put the local.prop file, with ro.kernel.qemu=1 in it, in the /data directory so that the phone will run in emulater mode and give adb a root shell.
For this I created the local.prop file on my computer and pushed it to /data/local/tmp. Then I entered the engineer mode on my phone and searched around and found a place where you can type shell comands as the system user and copied the local.prop file to /data with busybox.
Hope this helps you
Instructions:
[email protected]$ adb push local.prop /data/local/tmp/local.prop
from PC: adb push busybox /data/local/tmp/busybox
from PC: adb shell chmod 0777 /data/local/tmp/busybox
Enter engineer mode by typing on the dialpad *#15963#* (this may vary from phone to phone so search around if this code doesn't work).
Goto CDS Information / Network Utility. Then run: /data/local/tmp/busybox cp /data/local/tmp/ocal.prop /data/local.prop
You can run: ls /data to confirm local.prop is there.
Reboot.
From here on you can either manually do the rest of the script or copy the rest of it to a new script and run it.
EDIT: amended to make it actually work (originally tred to use mv instead co pushing busybox and using cp.
EDIT2: amended adb chmod to adb shell chmod

Engineer Mode Help for MTK Device
For the last few days i've being trying to get the engineer mode code for my phone but failed until i hit "mtk engineer mode" through googling. There is an application called "Mobileuncle MTK Tools" that could excess the engineer mode of my mtk phone.
Mobileuncle MTK Tools is able to list down the menu in engineer mode but there are no CDS Information / Network Utility in the list. The menu listed are as follows:
Battery Log
TouchScreen
GPRS
Audio
Camera
WiFi
Bluetooth
NetworkInfo
AutoAnswer
YGPS
AGPS
EPO
VideoTelephony
Display
Memory
IO
Power
BaseBand
FM Receiver
SIMMeLock
SystemLog
De-Sense
CPU Freq Test
BandMode
I'm hoping that you may have some clues on the next step of solving this problems of mine. Thanks for your time in helping me and i appreciate it very much.

FrankVM said:
I had a similar problem when trying to root my bird v1277 with Android 4.0.4
I ended up having to do the first steps of the script manually combining the phone's engineer menu and the adb shell.
The objective is to put the local.prop file, with ro.kernel.qemu=1 in it, in the /data directory so that the phone will run in emulater mode and give adb a root shell.
For this I created the local.prop file on my computer and pushed it to /data/local/tmp. Then I entered the engineer mode on my phone and searched around and found a place where you can type shell comands as the system user and moved the local.prop file to /data
Hope this helps you
Instructions:
[email protected]$ adb push local.prop /data/local/tmp/local.prop
Enter engineer mode by typing on the dialpad *#15963#* (this may vary from phone to phone so search around if this code doesn't work).
Goto CDS Information / Network Utility. Then run: mv /data/local/tmp/local.prop /data/local.prop
You can run: ls /data to confirm local.prop is there.
Reboot.
From here on you can either manually do the rest of the script or copy the rest of it to a new script and run it.
Click to expand...
Click to collapse
Hello
I do have a V1277 as well, but I'm not that up to date on android manipulations. Thing is, that I went into the engineer mode, got to CDS info/network utility. Ran ls /data and saw the local.prop. (I'm not sure if I did it before the " Then run: mv /data/local/tmp/local.prop /data/local.prop" or not...sorry...I'm noob). And also I ran the
Anyways. Everything still gives me error messages telling me that access is denied. In fact the mv command as well.
I guess I may be missing the first line of your instructions. If you have time can you please explain it a bit more deeply? (I got the TPSparkyRoot thing, with adb.exe in it, tried running the command adb push from total commander and also adb terminal)
Thanks in advance

Hi everyone.
I recently bougth a micro d-hdmi to hdmi for my v1277 so that I could use it to connect to my lcd tv.
I connected it and it works. The only thing that bothers me is that it won't go on full screen on the tv. The picture is always on portrait and centered at the lcd which kind a disgusted me. I cannot find any options on the hdmi menu to turn it to fullscreen or have it default to landscape mode just to use the whole screen real state.
Does anybody knows howntp do it? Is there an app to solve this that is available on google play.
Help.
Sent from my V1277 using xda app-developers app

shaamt said:
For the last few days i've being trying to get the engineer mode code for my phone but failed until i hit "mtk engineer mode" through googling. There is an application called "Mobileuncle MTK Tools" that could excess the engineer mode of my mtk phone.
.
Click to expand...
Click to collapse
Try these ones *#*#3646633#*#* or *#3646633#
You can also check if SystemLog / NetLog has an operational shell command box
---------- Post added at 01:47 AM ---------- Previous post was at 01:27 AM ----------
Nekem8 said:
Hello
I do have a V1277 as well, but I'm not that up to date on android manipulations. Thing is, that I went into the engineer mode, got to CDS info/network utility. Ran ls /data and saw the local.prop. (I'm not sure if I did it before the " Then run: mv /data/local/tmp/local.prop /data/local.prop" or not...sorry...I'm noob). And also I ran the
Anyways. Everything still gives me error messages telling me that access is denied. In fact the mv command as well.
I guess I may be missing the first line of your instructions. If you have time can you please explain it a bit more deeply? (I got the TPSparkyRoot thing, with adb.exe in it, tried running the command adb push from total commander and also adb terminal)
Thanks in advance
Click to expand...
Click to collapse
ok run these commands and tell me what they say and I'll try and figure out what is going on:
id
ls -ld /data
cat /data/local.prop

All,
I have sucessfully rooted my v1277 using the same procedures on how to root lenovo p700.
[Guide] how to root lenovo p700http://forum.xda-developers.com/showthread.php?t=1774567
You can try it also and please READ, understand, follow and execute the procedures carefully then you will succeed.
Sent from my V1277 using xda app-developers app

Engineer Mode Help for MTK Device
FrankVM said:
Try these ones *#*#3646633#*#* or *#3646633#
You can also check if SystemLog / NetLog has an operational shell command box
---------- Post added at 01:47 AM ---------- Previous post was at 01:27 AM ----------
Click to expand...
Click to collapse
I think i've tried all the engineer code listed on forums/web but anyway i tried again the one given by you and the result are still the same.
SystemLog / NetLog has no operational shell command box. But anyway i've installed "Terminal Emulator" from google play.
From the shell command in the device are there any way for me to check any directory that allowed system user running in emulator mode and give adb a root shell.

[Zte][warp7]Permroot[kingroot]

Will type up better guide later on gonna include my ota i pulled as well maybe help someone
btw do at ur own risk im not responsable if u mess the phone up
added batch script hope it works to automate the process and guide u. before u can use this guide or batch script make sure to enable developer settings and adb
you can download it this https://forum.xda-developers.com/attachment.php?attachmentid=4181698&stc=1&d=1497456929 extract it go into the folder find root.bat double click file.
or follow the guide below
1.need to get temp root with king root first grab that here https://kingroot.net/ grab file for android not windows version
grab this file https://forum.xda-developers.com/attachment.php?attachmentid=4180414&stc=1&d=1497364232
2.once extracted go inside folder. hold down shift key and right click inside the folder. click open command window here
{
"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"
}
unhide for root guide
3. type this "su"
then continue guide
4. type this "getprop ro.product.name"
should show output "ZTE_BEAM"
5. type this "setprop persist.sys.k ZTE_BEAM"
6. type this "getprop persist.sys.k"
output "ZTE_BEAM"
7. type this "cd /dev/block/platform/soc.0/7824900.sdhci/by-name/"
Lets backup recovery
8. type this "dd if=recovery of=/sdcard/recovery.img"
Lets write boot to recovery!
9. type this "dd if=boot of=recovery"
10. type this inside of adb shell "reboot recovery"
if u get black screen just hold power down to reboot
once booted up
make sure your still inside adb command prompt
11. type this "adb shell"
12. type this "su"
13. type this "id"
should show this output
"uid=0(root) gid=0(root) context=u:r:shell:s0"
then to set permissive
14. type this "setenforce 0"
15. type this "getenforce"
output "Permissive"
16. to test if mount system rw while still root type "mount -o remount,rw /system"
if it mounts no errors then system is writeable
reboot
if for some reason u cant write to system u can try
run this command in adb shell or terminal
reboot disemmcwp
to re-enable write protection issue this command
reboot emmcwpenab
working on replacing king with supersu til then perm root with kingroot
enjoy
and u wanna donate for my hard work click here http://paypal.me/riley60
to restore recovery back to stock u can do once u have perm root do this to restore recovery
type this inside of adb shell dd of=recovery if=/sdcard/recovery.img
hit the thanks button if my post was helpful
original guide here
thanks jcase for his guide for me to base on
https://plus.google.com/+JustinCaseA...ts/KzgyHLgVhwo
also dont forget to hit the thank you button if this post was helpful
ota file attached may help some that are bricked
to remove annoying lock screen with ads
open king root then touch the 3 dots goto settings
then touch accelerate charging turn switch it off
then that annoying part is gone if purify is installed remove it and everything should be good.

Awesome, do you know if this will work on the ZTE Warp Elite?

everyone get their phone rooted ok

Well 2 things...
1: can you lost a guide on how you did those steps?
2: if I already did a software update for my phone, would that affect my chances of getting my phone permanently rooted?

those steps are the guide if you dont know what adb is or how to use it or king root then u could look both those up for guides on the 2. after u know how to use both its pretty much gain temp root have adb open then paste commands make sure they say the same as the guide for outputs follow all steps and should be good. unless they released an update that make it android n im sure it will work. once i send in these 2 dead phones to get repaired ill make a video guide of the steps in guide. as i dont know if it will break root to try redo all the steps to show everything i did.i will see if i can automate the process with batch script. aka filename.bat

updated the guide lil for if anyone who is lil new to adb etc

I've used adb when dealing with moto phones. But this has me confused as to what to actually put in cmd prompt. Either way you're a God among us. I'm going to attempt and see if I can get it working. Thank you for your work sir. Hope to see a batch script some day.

added batch script

No errors so far. Just a little sluggish.

Stevenbew said:
No errors so far. Just a little sluggish.
Click to expand...
Click to collapse
um no errors from what and whats sluggish and for anyone who asks i used the lastest kingroot version

Just errors in general. Nothing is giving me any problems. My phone was a little sluggish after first rebooting. Almost acted like a temp root until I ran the reboot disemmcwp cmd. Then no problems.

Stevenbew said:
Just errors in general. Nothing is giving me any problems. My phone was a little sluggish after first rebooting. Almost acted like a temp root until I ran the reboot disemmcwp cmd. Then no problems.
Click to expand...
Click to collapse
did u use script or manual

madvane20 said:
did u use script or manual
Click to expand...
Click to collapse
I did it manually. Knowing exactly what to type after you edited made everything alot easier to understand.

Stevenbew said:
I did it manually. Knowing exactly what to type after you edited made everything alot easier to understand.
Click to expand...
Click to collapse
ok i only asked cause im already rooted so i couldnt really test the script but it should work and at the end it tells what commands to type in to test. looks like i may need to edit the guide lil bit later and edit my script

I read the guide over and over. While I think I may understand, I'm still afraid to attempt this since it is my only phone and I cannot replace it currently if something were to go wrong. Your typing style makes it somewhat difficult to understand but nonetheless, thank you. I'll attempt when I'm able to replace the phone if something goes wrong.

Heartseed said:
I read the guide over and over. While I think I may understand, I'm still afraid to attempt this since it is my only phone and I cannot replace it currently if something were to go wrong. Your typing style makes it somewhat difficult to understand but nonetheless, thank you. I'll attempt when I'm able to replace the phone if something goes wrong.
Click to expand...
Click to collapse
use to batch script after u get temp root it will do most of the work for you and guide u through the rest

I need help, I can not do temporary root, so neither method allows me to enter the ADB get the SU command, should the phone have any condition before trying to apply them? My phone has software version 0B09 and the options are unlocked OEM and USB debugging, which I am doing wrong, any commentary? thank you!

Pirela said:
I need help, I can not do temporary root, so neither method allows me to enter the ADB get the SU command, should the phone have any condition before trying to apply them? My phone has software version 0B09 and the options are unlocked OEM and USB debugging, which I am doing wrong, any commentary? thank you!
Click to expand...
Click to collapse
grab the newest king root then if it fails keep trying it til it goes through. if it fails uninstall king root reboot reinstall try again. also try adding this commands first if it works without root "reboot disemmcwp" without quotes then try install king root and root see if u get temp root. then if it makes it easier i have a batch script made in the minimal adb and fastboot package

madvane20 said:
grab the newest king root then if it fails keep trying it til it goes through. if it fails uninstall king root reboot reinstall try again. also try adding this commands first if it works without root "reboot disemmcwp" without quotes then try install king root and root see if u get temp root. then if it makes it easier i have a batch script made in the minimal adb and fastboot package
Click to expand...
Click to collapse
Mandvane20 Thanks for your answer and interest
It was not possible to have some temp root, I tried with king root apk and pc, also with kingo root, I went to recovery and deleted the cache, I have force stop the application, I uninstalled and reinstalled, use reboot Disemmcwp, I have made multiple attempts and none has worked, I keep reading, searching and learning, I hope to get some way

Pirela said:
Mandvane20 Thanks for your answer and interest
It was not possible to have some temp root, I tried with king root apk and pc, also with kingo root, I went to recovery and deleted the cache, I have force stop the application, I uninstalled and reinstalled, use reboot Disemmcwp, I have made multiple attempts and none has worked, I keep reading, searching and learning, I hope to get some way
Click to expand...
Click to collapse
connect to pc open adb shell run king root while its trying to root keep typing su in adb shell tell it says root. or til it doesnt give u the error saying no su then proceed with guide see if that works

I need help rooting my zte quest 5

Ok so i got a zte quest 5 (z3351s) though qlink. Not the phone i wanted but it was one i could afford. And it works very well just can't run amazon music and other apps at the same time.
But the bloatware is unreal. Used to in my galaxy s3&s4 days i could root and delete all apps i didn't need. I know i can disable them but i want them gone completely.
Majisk didnt work
Kingoroot same even used pc.
I am hoping someone knows of a way i can root this phone or at least delete all the un needed apps for example i have Google maps go (came stock) i put the org google maps which is better plus offers sat view.
Edit i did some math and converting and the useless apps 11 out of 58 come out to 349.72mb which is a lot if your phone only has 16gb of space. Also note i don't have hardly anything.
Worst case i can Hotspot to my note10+ for multitasking but not sure of data limit.

@TexasPride
a phone's Android can get considered "rooted" as soon as in Android the SU-binary is present. Hence you at any time at your own can install the appropriate SU-binary onto your phone's Android by means of ADB.

I heard about adb methods but i haven't messed with it in forever since apk/ios apps came out

jwoegerbauer said:
@TexasPride
a phone's Android can get considered "rooted" as soon as in Android the SU-binary is present. Hence you at any time at your own can install the appropriate SU-binary onto your phone's Android by means of ADB.
Click to expand...
Click to collapse
Are you sure it will always work?
I tried this method of installing supersu: https://github.com/spff/install-supersu-via-adb
As a result, I got my phone eternally showing the boot logo and not booting.
Not a problem to re-flash stock ROM but it is an example that there in no universal way to install SU (or SuperSU) via adb.
If you could give a link to some other method how SU could be installed, I'll give it a try of course.

vp1117 said:
Are you sure it will always work?
I tried this method of installing supersu: https://github.com/spff/install-supersu-via-adb
As a result, I got my phone eternally showing the boot logo and not booting.
Not a problem to re-flash stock ROM but it is an example that there in no universal way to install SU (or SuperSU) via adb.
If you could give a link to some other method how SU could be installed, I'll give it a try of course.
Click to expand...
Click to collapse
I spoke of SU-binary and NOT of SuperSU installer package
Example:
Code:
adb devices
adb push <location-of-matching-su-binary-on-computer> /sdcard/Downloads/ 2>nul
adb shell "chmod 0777 /sdcard/Downloads/su"
Of course you can install SuperSU package by means of ADB and this even when device is booted into Stock Recovery: but this requires to make some mods to SuperSU zip.

TexasPride, sorry I stepped in your thread.​
jwoegerbauer said:
I spoke of SU-binary and NOT of SuperSU installer package
Click to expand...
Click to collapse
I see. It is often mixed in numerous materials one can find in the net. Subject is SU-binary update, but the ultimate goal is to install supersu.
jwoegerbauer said:
Example:
Code:
adb devices
adb push <location-of-matching-su-binary-on-computer> /sdcard/Downloads/ 2>nul
adb shell "chmod 0777 /sdcard/Downloads/su"
Click to expand...
Click to collapse
What should be result of running this code? SU-binary located in Downloads with 777 permission? What is the practical sense/use of it?
What software/application would use SU in that location?
Sorry for my questions. I'm not arguing. I try to understand the idea.
jwoegerbauer said:
Of course you can install SuperSU package by means of ADB and this even when device is booted into Stock Recovery: but this requires to make some mods to SuperSU zip.
Click to expand...
Click to collapse
Somehow, with my almost zero knowledge of edify and linux command line I got the same conclusion: SuperSU zip has to be modified in order to install it via adb on devices that do not have TWRP for sideload. I failed to find any examples of SuperSU modding...

@vp1117
Answering your questions from last to first:
Installing SuperSU.zip via ADB
The SuperSU.zip doesn't come with an EDIFY coded script, but with an Android SHELL script - everyone who has knowledge of LINUX scripting can read / modify it.
Android comes with TAR-binary, but not ZIP-binary. Hence the SuperSu.zip must get repacked into SuperSU.tar thus it can get extracted on Phone. The contents of such a TAR-file would look as shown here
{
"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"
}
Making use of SU-binary
The SU-binary ( ~110KB ) is nothing else then the root user, as known from LINUX.
Running in Android via ADB a command that requires super-user ( root ) rights is done as follows
Example:
Code:
adb devices
adb shell "/sdard/Downloads/su -c '<ommand-that-requires-root-here>'"

jwoegerbauer said:
Answering your questions from last to first:
Installing SuperSU.zip via ADB
The SuperSU.zip doesn't come with an EDIFY coded script, but with an Android SHELL script - everyone who has knowledge of LINUX scripting can read / modify it.
Android comes with TAR-binary, but not ZIP-binary. Hence the SuperSu.zip must get repacked into SuperSU.tar thus it can get extracted on Phone. The contents of such a TAR-file would look as shown here
Click to expand...
Click to collapse
OK. I guess, I can repack zip to tar.
Sorry for my silly question but why should I need to keep superSU as an archive? Could not I just upload all folders + update-binary.sh to the phone? I'm sure I can do it.
Am I right my next step would be running update-binary.sh (~60 KB) from <adb shell> command line?
jwoegerbauer said:
Making use of SU-binary
The SU-binary ( ~110KB ) is nothing else then the root user, as known from LINUX.
Running in Android via ADB a command that requires super-user ( root ) rights is done as follows
Example:
Code:
adb devices
adb shell "/sdard/Downloads/su -c '<ommand-that-requires-root-here>'"
Click to expand...
Click to collapse
Interestingly, I can execute all commands I need without having su-binary (~100 KB) uploaded to my phone. It is strange but I see #-prompt after I ran <adb shell>. This happens on my UNrooted phone, running stock ROM. I guess, it's a specifics of my phone, no need to try explain it.

I done failed trying to read i dont really understand linux all that well. But if anyone has any links so i can download it and try it

vp1117 said:
Sorry for my silly question but why should I need to keep superSU as an archive? Could not I just upload all folders + update-binary.sh to the phone? I'm sure I can do it.
Am I right my next step would be running update-binary.sh (~60 KB) from <adb shell> command line?
Click to expand...
Click to collapse
Of course it's your decision how you transfer the SuperSU package onto phone: many ways lead to Rome.
My decision was to push SuperSU package repacked as TAR-file onto phone, extract it there, and finally run the modified update-binary.sh when phone is booted into recovery mode:
Code:
adb shell "$(cat < %supersu_dir%/update-binary.sh); echo $?"

So I rebooted to stock recovery and then uploaded following from UPDATE-SuperSU-v2.82-20170528234214.zip package to my phone's folder /tmp:
/arm64
/common
/META-INF
update-binary.sh
Here is what I got:
Z:\android\adb>adb shell "$(cat < /tmp/update-binary.sh); echo $?"
127
/system/bin/sh: #!/sbin/sh: not found
And here's what I got running same command from # command line:
# $(cat < /tmp/update-binary.sh); echo $?
/system/bin/sh: #!/sbin/sh: not found
127
In response to # ls -al /sbin I get lots of lines one of them is as follows:
lrwxrwxrwx 1 root root 7 1970-01-01 00:00 sh -> busybox
I feel that I'm doing something wrong, but what exactly?
In attached txt-file I put some more details I got in command line.

jwoegerbauer said:
... and finally run the modified update-binary.sh when phone is booted into recovery mode:
Click to expand...
Click to collapse
Am I right the only modification needed is to rename update-binary to update-binary.sh ?

@vp1117
NO.
When I said modified then I didn't mean simply rename it: The contents of original update-binary file must be rewritten / deleted in some parts. Also, believe me, it makes sense to repack original SuperSU.zip to SuperSu.tar as I demonstrated above. Take also note that, if device's Android isn't rooted yet, the location for unpacked SuperSU mandatory must be /data/local/tmp.
BTW:
I can see BusyBox is installed on your device's Android. Take note that BusyBox by default comes with the SU-binary. Hence your device's Android is rooted! Wondering why you waste your time with trying to completely install SuperSU from scratch?

jwoegerbauer said:
Wondering why you waste your time with trying to completely install SuperSU from scratch?
Click to expand...
Click to collapse
Good question.
Probably, because I see this when phone restarts from recovery to normal android:

jwoegerbauer said:
Also, believe me, it makes sense to repack original SuperSU.zip to SuperSu.tar as I demonstrated above.
Click to expand...
Click to collapse
OK, no problem, I can re-pack zip into tar.
However, what you demonstrated above was a screenshot showing update-binary.sh being inside the tar. At the same time you don't tell how update-binary.sh must be amended. Is it OK?

TexasPride​
I'm very sorry I put so much spam in your thread. Please forgive me. If I knew how to delete my posts here I would deleted them.

vp1117 said:
TexasPride​
I'm very sorry I put so much spam in your thread. Please forgive me. If I knew how to delete my posts here I would deleted them.
Click to expand...
Click to collapse
Its ok, i dont mind at all.

@TexasPride
FYI: I no longer participate this hijacked thread.

Please Help This Has Ruined My Day. Accidentally Disabled or Deleted I Don't Know which one com.android.systemui

Please Help This Has Ruined My Day. Accidentally Disabled or Deleted I Don't Know which one com.android.systemui
So I have a OnePlus 6 with Lineage OS, TWRP and Magisk all installed and i was just looking at apps in App Manager and i accidentally press the same area twice and Disabled or Deleted I don't know com.android.systemui and the screen went black so i rebooted the phone and it says "Android Is Starting" and never fully boots up and I don't know how to fix It without losing my files I tried to flash the Lineage OS image again but didn't work also I have a password (I Know The Password but can't decrypt my files in TWRP) and I don't want to lose my files, i won't reset the storage without decrypting and backing up my files, also pm command In ADB shell does not work it says its "inaccessible or not found". Is there a way i can decrypt my files and move them off my phone or a way i can fix com.android.systemui this has ruined my day please help if you smart. Also maybe i could Reinstall/Reenable com.android.systemui by changing some config file or doing something else just help please If someone can help me get my files off of my phone and/or fix it without a reset I would be so happy and you would be a really good person
My First Thread on this please reply to this that one if you can https://forum.xda-developers.com/t/...-know-which-one-com-android-systemui.4480157/

This is what is in com.android.systemui/cache/
a file called lockscreen_capture_port.png but the image might be different for you device.
{
"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"
}

Raffles727 said:
This is what is in com.android.systemui/cache/
a file called lockscreen_capture_port.png but the image might be different for you device.
View attachment 5686769
Click to expand...
Click to collapse
so what do i do to fix it? do i delete some file or what do i do

If you accidentally deleted the folder I suggest to re-create it and then put the png image , try my image but it is for a Samsung, it may not be the correct dimensions. On my device (Samsung) the folder only had the .png image in it. The full path is Android > data > com.android.systemui > cache > which contains the image lockscreen_capture_port.png
You can try connecting the device to your computer in order to do this.

Oh, so you killed your Android subsystem? What do you need that for? (Just a little joke.)
You do have ADB? Is it rooted? #?
If you can get to ADB, the first thing to do is:
Code:
C:\>adb shell
# stop
# logcat
That stops the Android subsystem from trying to start. Then the logcat will show you what it doesn't like.
You don't have to be a rocket scientist to see what it's complaining about.
===============================
Are you trying to get photos off /sdcard or data in Whatsapp?
Code:
# adb pull /sdcard/Books
Or whatever.
In short, getting stuff off /sdcard is easy, getting application data off requires root.
===============================
Then there's the question of fixing this.
As @Raffles727 says, you need to recreate the directory and the two subdirectories (cache and code_cache).
It's not certain thay you have both, but it wouldn't hurt.
On my device there is /data/data/com.android.systemui/gestures_config
I don't think that any "cache" files are that important, although a missing directory could cause crashes.
A missing XML JSON file could make it unhappy, what does logcat say? Here's my gestures_config:
Code:
{"displayIndicator":false,"enable":true,"enableBehindKeyboard":true,"guestConfigMap":{"gestures_bottom_left":"BACK","gestures_bottom_middle":"HOME","gestures_bottom_right":"TASK_SWITCH","gestures_left_bottom":"NONE","gestures_left_middle":"NONE","gestures_left_top":"NONE","gestures_right_bottom":"NONE","gestures_right_middle":"NONE","gestures_right_top":"NONE","gestures_top_left":"NONE","gestures_top_middle":"NONE","gestures_top_right":"NONE","slide_gestures_left":"VOLUME","slide_gestures_right":"WARM_LIGHT"},"indicatesHeight":50,"indicatesTransparency":50,"indicatesWidth":50,"preventMiscontact":false,"slideEnable":false,"slidingDistance":100}
(Although, since this is JSON, I kind of doubt that you have this.)
Try to fix something, then reboot.

Raffles727 said:
If you accidentally deleted the folder I suggest to re-create it and then put the png image , try my image but it is for a Samsung, it may not be the correct dimensions. On my device (Samsung) the folder only had the .png image in it. The full path is Android > data > com.android.systemui > cache > which contains the image lockscreen_capture_port.png
You can try connecting the device to your computer in order to do this.
View attachment 5686775
Click to expand...
Click to collapse
i think that path is encrypted so i cant do that

Renate said:
Oh, so you killed your Android subsystem? What do you need that for? (Just a little joke.)
You do have ADB? Is it rooted? #?
If you can get to ADB, the first thing to do is:
Code:
C:\>adb shell
# stop
# logcat
That stops the Android subsystem from trying to start. Then the logcat will show you what it doesn't like.
You don't have to be a rocket scientist to see what it's complaining about.
===============================
Are you trying to get photos off /sdcard or data in Whatsapp?
Code:
# adb pull /sdcard/Books
Or whatever.
In short, getting stuff off /sdcard is easy, getting application data off requires root.
===============================
Then there's the question of fixing this.
As @Raffles727 says, you need to recreate the directory and the two subdirectories (cache and code_cache).
It's not certain thay you have both, but it wouldn't hurt.
On my device there is /data/data/com.android.systemui/gestures_config
I don't think that any "cache" files are that important, although a missing directory could cause crashes.
A missing XML file could make it unhappy, what does logcat say? Here's my gestures_config:
Code:
{"displayIndicator":false,"enable":true,"enableBehindKeyboard":true,"guestConfigMap":{"gestures_bottom_left":"BACK","gestures_bottom_middle":"HOME","gestures_bottom_right":"TASK_SWITCH","gestures_left_bottom":"NONE","gestures_left_middle":"NONE","gestures_left_top":"NONE","gestures_right_bottom":"NONE","gestures_right_middle":"NONE","gestures_right_top":"NONE","gestures_top_left":"NONE","gestures_top_middle":"NONE","gestures_top_right":"NONE","slide_gestures_left":"VOLUME","slide_gestures_right":"WARM_LIGHT"},"indicatesHeight":50,"indicatesTransparency":50,"indicatesWidth":50,"preventMiscontact":false,"slideEnable":false,"slidingDistance":100}
Try to fix something, then reboot.
Click to expand...
Click to collapse
adb does not work (it says "adb: no devices/emulators found when i run" adb shell) unless in twrp but in twrp /sdcard is encrypted and twrp cant unencrypt lineage os for some reason also its not a missing driver issue im on linux witch has all android drivers by default when you install platform tools

Renate said:
Oh, so you killed your Android subsystem? What do you need that for? (Just a little joke.)
You do have ADB? Is it rooted? #?
If you can get to ADB, the first thing to do is:
Code:
C:\>adb shell
# stop
# logcat
That stops the Android subsystem from trying to start. Then the logcat will show you what it doesn't like.
You don't have to be a rocket scientist to see what it's complaining about.
===============================
Are you trying to get photos off /sdcard or data in Whatsapp?
Code:
# adb pull /sdcard/Books
Or whatever.
In short, getting stuff off /sdcard is easy, getting application data off requires root.
===============================
Then there's the question of fixing this.
As @Raffles727 says, you need to recreate the directory and the two subdirectories (cache and code_cache).
It's not certain thay you have both, but it wouldn't hurt.
On my device there is /data/data/com.android.systemui/gestures_config
I don't think that any "cache" files are that important, although a missing directory could cause crashes.
A missing XML JSON file could make it unhappy, what does logcat say? Here's my gestures_config:
Code:
{"displayIndicator":false,"enable":true,"enableBehindKeyboard":true,"guestConfigMap":{"gestures_bottom_left":"BACK","gestures_bottom_middle":"HOME","gestures_bottom_right":"TASK_SWITCH","gestures_left_bottom":"NONE","gestures_left_middle":"NONE","gestures_left_top":"NONE","gestures_right_bottom":"NONE","gestures_right_middle":"NONE","gestures_right_top":"NONE","gestures_top_left":"NONE","gestures_top_middle":"NONE","gestures_top_right":"NONE","slide_gestures_left":"VOLUME","slide_gestures_right":"WARM_LIGHT"},"indicatesHeight":50,"indicatesTransparency":50,"indicatesWidth":50,"preventMiscontact":false,"slideEnable":false,"slidingDistance":100}
(Although, since this is JSON, I kind of doubt that you have this.)
Try to fix something, then reboot.
Click to expand...
Click to collapse
sould i try to run adb shell wile booted into twrp and cd to /data/data and use mkdir to make a new /data/data/com.android.systemui

Is /data even mounted?
Code:
# cd /data
# ls -l
Didn't you have ADB enabled on your normal system?
Do you see the normal bootanimation?
Is the USB showing anything in normal system? MTP?

iwanttoroota11walmart said:
sould i try to run adb shell wile booted into twrp and cd to /data/data and use mkdir to make a new /data/data/com.android.systemui
Click to expand...
Click to collapse
never mind it says required key not available so i cant modify /data/data so am i just screwed

Renate said:
Is /data even mounted?
Code:
# cd /data
# ls -l
Didn't you have ADB enabled on your normal system?
Do you see the normal bootanimation?
Is the USB showing anything in normal system? MTP?
Click to expand...
Click to collapse
no i cannot access my phone on my pc from the normal system only in twrp and it shows my normal boot animation

Right, but in TWRP /data is not mounted, it's encrypted and TWRP can't decrypt/mount it?

iwanttoroota11walmart said:
no i cannot access my phone on my pc from the normal system only in twrp and it shows my normal boot animation
Click to expand...
Click to collapse
its liveboot so i can see my logcat when the phones turning on could that help at all

Renate said:
Right, but in TWRP /data is not mounted, it's encrypted and TWRP can't decrypt/mount it?
Click to expand...
Click to collapse
it is encrypted and if i try to do adb pull /data only a coupple folders can copy over to my pc and when i try to decrypt when turning it on it cant decrypt also i have a pattern set and a fingerprint set if that helps at all

iwanttoroota11walmart said:
it is encrypted and if i try to do adb pull /data only a coupple folders can copy over to my pc and when i try to decrypt when turning it to twrp on it cant decrypt also i have a pattern set and a fingerprint set if that helps at all
Click to expand...
Click to collapse

iwanttoroota11walmart said:
it is encrypted and if i try to do adb pull /data only a coupple folders can copy over to my pc and when i try to decrypt when turning it on it cant decrypt also i have a pattern set and a fingerprint set if that helps at all
Click to expand...
Click to collapse
and /scard (where my files are that i need off of it before i would reset the phone) is encrypted

iwanttoroota11walmart said:
and /scard (where my files are that i need off of it before i would reset the phone) is encrypted
Click to expand...
Click to collapse
also i can boot other recoverys if there is a recovery that can decrypt lineage os stuff

Encrypted data makes life awfully difficult.
Yeah, liveboot could give us some info. Does it just keep running and restarts by itself?
Is the bootloader unlocked?
Was ADB enabled before it died?
Was this Magisk'ed?
I can think of two solutions
1) Force ADB to run
2) See if adding the directories to a ramdisk would work.

Renate said:
Right, but in TWRP /data is not mounted, it's encrypted and TWRP can't decrypt/mount it?
Click to expand...
Click to collapse
also twrp can mount /sdcard to mtp but its encrypted

Renate said:
Encrypted data makes life awfully difficult.
Yeah, liveboot could give us some info. Does it just keep running and restarts by itself?
Is the bootloader unlocked?
Was ADB enabled before it died?
Was this Magisk'ed?
I can think of two solutions
1) Force ADB to run
2) See if adding the directories to a ramdisk would work.
Click to expand...
Click to collapse
liveboot runs until the boot animation is over
the bootloader is unlocked i could wipe and reinstall the os but then i lose my data that i really really do not want to lose
adb was enabled before it died and also when the phone is turned on to system it shows "Android is starting' but it never stops doing that
it has magisk installed yes
how would i force adb to run?