Hello, well today i was going through the second hand market on my town for a phone and i saw this mb865, impecable but as is.. with no charger cables or anything whatsoever.. the price was cheap enough so i got it..
After getting to my home i noticed that on the back under the cover and on the display at the right side of the screen it has some engravings saying this phrase.
"Confidential Motorola property not for sale"
so whats the deal with this phone? is it a prototype? or what?
Im from Mexico and the phone has a Iusacell rom.
What do you guys think?
If i were you, i would go to that store again, and return it. Perhaps you'll have some bad experiences with that phone, because maybe it's not the final release and may had some changes than ours phone.
And on the other hand, it may be an engineering device with an unlocked bootloader....
snowplow said:
And on the other hand, it may be an engineering device with an unlocked bootloader....
Click to expand...
Click to collapse
im now officially praying for this.. as of right now.. i have asked for an unlock code from cellunlocker.net..
any of yoou know them? they seem reliable enough...
No idea about sim-unlocking it, I doubt that you will be able to though if it is carrier locked. Have you tried different sim cards in it?
snowplow said:
No idea about sim-unlocking it, I doubt that you will be able to though if it is carrier locked. Have you tried different sim cards in it?
Click to expand...
Click to collapse
Well i have tried my sim ( which is from another carrier) and it asks me for asubsidiary code.. so im hoping ill be able to unlock it the same way i did with my xt610 some time ago..
So far i dont see anything special in this phone, other than those words... mm well see.. tomorrow ill try to flash some roms, recoveries.. etc..
and ill be expecting my unlock code..
Sent from my iPad using Tapatalk
enable usb debugging, open command prompt, go to the folder you have adb in, and type the following post the output.
Code:
adb shell
su
cat proc/omap_dev_type
if you dont have adb, just download android terminal from google play and type in the same except 'adb shell'. of course, your phone has to be rooted.
Ravikirancg said:
enable usb debugging, open command prompt, go to the folder you have adb in, and type the following post the output.
Code:
adb shell
su
cat proc/omap_dev_type
if you dont have adb, just download android terminal from google play and type in the same except 'adb shell'. of course, your phone has to be rooted.
Click to expand...
Click to collapse
What is this Iusacell ROM he mentioned? & I hope anyone can post the root file for Gingerbread & ICS and "eetu' can use it to root as per GB or ICS he would have on his phone & for then executing the above command on android terminal .
Eetu, you need to follow above instructions and advise what output you get on screen. Your phone may be one of a kind most special and our developers need all help to unlock bootloader & they may get in touch with you based on your reply that is sought & until then preferably do not alter stock settings by flashing custom ROM's, Mod's etc. We need all help we can get. Thanks!
RAD7 said:
What is this Iusacell ROM he mentioned? & I hope anyone can post the root file for Gingerbread & ICS and "eetu' can use it to root as per GB or ICS he would have on his phone & for then executing the above command on android terminal .
Click to expand...
Click to collapse
Iusacell is a service provider from México (use mostly CDMA pones), the "oficial Iusacell rom" stayed in GB not ICS (http://sbf.droid-developers.org/edison/list.php)
There is a lot of chance that will be a engineer phone, but will be the same case of the other Atrix 2 with unlocked bootloader.
Saludos
serch_mx said:
Iusacell is a service provider from México (use mostly CDMA pones), the "oficial Iusacell rom" stayed in GB not ICS (http://sbf.droid-developers.org/edison/list.php)
There is a lot of chance that will be a engineer phone, but will be the same case of the other Atrix 2 with unlocked bootloader.
Saludos
Click to expand...
Click to collapse
Noted & I guess eetu must have given reply in PM to developers!
RAD7 said:
Noted & I guess eetu must have given reply in PM to developers!
Click to expand...
Click to collapse
doubtful about that.. dosent look like he returned to this.
Ravikirancg said:
doubtful about that.. dosent look like he returned to this.
Click to expand...
Click to collapse
Gee, sucks, Eeetu, Man do revert.
When Jim said he is looking at stuff from user Amritin's phone, I was thinking prolly something more like Eetu's phone can surely add to the database.
IM HERE
Sorry guys i have had some in house problems.. but im here now..
Well blast i have probably ****ed this up now.. you see i was trying to root the phone in order to see things under the hood, but the usual superonelick, methond didnt work ( i tried other 2 thati cant remember they were mostly sripts with a runme.bat file on them)...
So with no avail.. i decided to flash the rom to a LATAM stock GB rom.. after i did.. i tried superoneclick and voila...
I havent been able to tinker with it past then.. but now im afraid of what i did.. ****..
So tell me do i try to reflash the iusacell rom( it is avaliable).. do i leave it like this.. or what?
on the meantime i have uploaded some pics of the phones messages of confidential property.. for you to see.. and im checking the ADB stuff.. getting the terminal emulator from the playstore as im typing this..
Let me know how to proceed..
{
"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"
}
Sorry for the quality.. i couldnt take better ones at the moment.. and the words on the front (on the side of the screen) are just impossible to take.. but believe me they are there..
well i downloaded the terminal from the store.. and i tried the commands with no avail.. yes i am rooted..
it looks something like this
[email protected]:/$
i type su and it says not found.. same as with the other command.. i know im doing something wrong here.. so please help.. im no linux wiz here..
eetu1923 said:
well i downloaded the terminal from the store.. and i tried the commands with no avail.. yes i am rooted..
it looks something like this
[email protected]:/$
i type su and it says not found.. same as with the other command.. i know im doing something wrong here.. so please help.. im no linux wiz here..
Click to expand...
Click to collapse
Try:
adb shell
Then, su...
Or use a root explorer and check /system/xbin and/or /system/bin for a file called "su"... And let us know..
Edit: Ahh.. You're using an app, not by usb.. Forget the first part of what I said - or try to find the adb files and do what Ravi said a few posts back with a usb from your computer..
Sent from my MB865 using xda app-developers app
alteredlikeness said:
Or use a root explorer and check /system/xbin and/or /system/bin for a file called "su"... And let us know..
or try to find the adb files and do what Ravi said a few posts back with a usb from your computer..
Click to expand...
Click to collapse
Well.. i tried using Root Exploirer and i searched both System/xbin and system/bin directories but there is no SU file in sight...
as for the other way .. where do i look for the ADB files? how do i use USB??
eetu1923 said:
Well.. i tried using Root Exploirer and i searched both System/xbin and system/bin directories but there is no SU file in sight...
as for the other way .. where do i look for the ADB files? how do i use USB??
Click to expand...
Click to collapse
Make sure its rooted properly.. open the superuser or supersu app and make sure the binary is updated..
A little more info and we can help you
What version of android are you on right now?
And what super one click did you use? I don't remember having a super one click for our phone..
Sent from my MB865 running PAC-man using Tapatalk 2
Ravikirancg said:
Make sure its rooted properly.. open the superuser or supersu app and make sure the binary is updated..
A little more info and we can help you
What version of android are you on right now?
And what super one click did you use? I don't remember having a super one click for our phone..
Click to expand...
Click to collapse
mybad it wasnt superoneclick.. damn names are the same.. i use a script called
1-click_exploit.zip
with these files inside.
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
busybox
runme.bat
su
Superuser.apk
zerg
Im on GB 2.3.6 and yes my superuser is updated.
eetu1923 said:
mybad it wasnt superoneclick.. damn names are the same.. i use a script called
1-click_exploit.zip
with these files inside.
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
busybox
runme.bat
su
Superuser.apk
zerg
Im on GB 2.3.6 and yes my superuser is updated.
Click to expand...
Click to collapse
If you have no su binary file in xbin or bin, then it's going to be difficult for things to recognize root.
You opened Superuser and tapped to check for binary updates in settings?
You could also try to install SuperSU instead..
Another thing to try: get busybox installer from Play Store and update busybox.
And about adb debugging - go to settings>developer options (or maybe security on GB?) - and enable USB debugging.
Plug in your phone to your computer by USB. Switch to each USB connection type on your phone (mass storage, mtp, camera..) and wait to let the drivers install if they haven't already.
Open a command prompt on that folder that contains adb.exe - do this by holding shift and right-click on the folder and choose open command prompt from the list (or just open the command prompt and type cd C:\Users\Desktop\1-click_exploit or whatever your path is to adb).
Type adb devices
If you get a serial number and the word "device" as output, then you should be OK to use adb
Sent from my MB865 using xda app-developers app
Related
Hello all, I just completed an app I'd like to share with you all.
It's called Search2Play, it lets you play and pause your music by pressing a button on your device. On most devices, it is the search key. Currently, the Nexus & MyTouch 3G both use the Search key, whereas the Droid uses the Camera key. If you have physical keys (i.e. Droid, MT3G, G1, etc) then it will work when the phone is locked, but if you have capacitive keys (Nexus, Moment, Eris, Incredible, etc) then the screen must be on (lockscreen works, and fully unlocked of course).
It is available on the market under the name "Search2Play (Root Required)". It's totally free.
It requires root permissions to install. It also requires that you have a version of BusyBox that supports the "cp" command. Only Droid users probably have to worry about the busybox version, as most other custom ROMs have that already. Droid users, I recommend CyanogenMod for Droid or Bugless Beast as I know both of them have the right version.
It does not run in the background or install a service, just makes some changes to a few files on the /system partition.
The UI is very simple, just two buttons and some text explaining the app. Once you hit install, it will ask for permission to use root, you must hit accept or the app won't serve its purpose
The other button, "Restore", lets you remove the mod and go back to stock settings, where the search button brings up search, etc.
Supported Devices:
Nexus
Spica
Hero (GSM & CDMA)
Galaxy S devices (all US variants and probably the i9000 as well. It's not tested)
MyTouch 3G
Droid 1 (I've been told DX & D2 work as well, though I'm not sure how :?)
Evo (must be NAND unlocked or S-OFF)
Desire (must be NAND unlocked or S-OFF)
Free Version on Market:
{
"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"
}
Or click this from your device: Search2Play Free
See the Market to view a screenshot. Please give me some feedback. Thanks! Hope you enjoy the app :
FOR DEVICE REQUESTS SEE POST #3
Changelog:
1.4.1 thru 2.1:
Add support for Evo, GSM Hero, CDMA Hero, & Samsung Spica (thanks to Aasheet Kumar for the files I needed for Spica support!)
1.4:
Fixed rare root checking bug on some Droid ROMs, and maybe some Nexus ROMs too
1.6+ only now, sorry, it's not like any device this works for isn't updated to at least 1.6
1.3:
Now checks if the SD card is present on launch instead of just crashing if it's not there
Cleaned things up more
Merged some code between the donate & free versions
Better checks to see if it can be installed
1.2.5:
FINALLY stopped it from causing buttons to stop working. Checks for compatibility, and throws an error if it detects it can't run.
1.2:
Droid support!!
More should fix a few FC issues some people have seen. Let me know if you have problems.
1.1.2:
Fixes the not restoring bug
1.1.1:
Failed attempt at fixing the not restoring bug.
1.1:
Support for low res devices.
Now works with MT3G! Since it has a hard search key, it will even work when the phone is locked
Deletes files from SD card once done installing.
Cleaned up more code.
1.0.1:
Sets system back to Read-Only once finished installing
Cleaned up some code, if you have FCs let me know.
1.0:
Base release
If you want to request support for your device here's what I need. Note that your device must be able to be rooted and the system partition must be able to get read/write access from userspace. I.E. any Desire or Evo or any other recent HTC device with a NAND lock will not work, unless it has been NAND unlocked with an S-OFF bootloader, like via Unrevoked.. If your device has all that, get this info and send me an email at [email protected]
Run the command "adb shell mount" and tell me the output. I don't need the whole thing, just the line referring to the system partition. I.E. "/dev/block/mtdblock3 on /system type yaffs2 (ro,relatime)" is the line on the Nexus, it should be similar to that.
Then, run "adb shell getprop" and tell me the 1-4 lines related to the keyboard, like hw.keyboards.*.devname and tell me those lines. I.E the Nexus returns "mahimahi-keypad". Yours should be similar.
Finally, run "adb shell ls /system/usr/keylayout/". It should return a list of files all ending in ".kl"
Remember the keypad name from step 2? Good
There should be a ".kl" file matching that name (like mahimahi-keypad.kl). Pull that file with "adb pull /system/usr/keylayout/keypadname.kl directory" with directory being the folder you want to pull the file to and keypad name being the name from step 2.
Zip that file, and then send it to me please.
That should be it, if you have any questions or problems with this list hit me up on GTalk or email me. [email protected] for both GTalk & email.
Dear geniusdog
I just tried out your app.
I installed it, run it, pressed the install button, allowed root access and rebooted mynexus one. But after that reboot, my sell doesn't react on anypressed buttons anymore. I can only use the touchscreen...
I also tried to restore in your app, but there appeared a window saying that the app is not responding anymore.
How can I manually restore it? Is there a command or some files, I can edit?
Thanks for your help
bayoffire said:
Dear geniusdog
I just tried out your app.
I installed it, run it, pressed the install button, allowed root access and rebooted mynexus one. But after that reboot, my sell doesn't react on anypressed buttons anymore. I can only use the touchscreen...
I also tried to restore in your app, but there appeared a window saying that the app is not responding anymore.
How can I manually restore it? Is there a command or some files, I can edit?
Thanks for your help
Click to expand...
Click to collapse
Sorry for the issue. I have uploaded a new version of both apps that should fix the problem. If you can download the app and install it again, otherwise, PM me & I will give you manual instructions to restore it.
Also, just some technical details, the problem was caused because I had set it to create the directory on the start of the application. After that I removed it once you clicked the button & the install was finished. Because of that, if you clicked restore after install, it would fail to find the directory and then proceed to FC. Sorry for the trouble
Droid Support!!!!
Help!!!!!
I have installed V1.0.4, but my touch keys(back, Menu, Home and Search) don't work.
Then I have tried to restore it, but it's failed.
How could I fix it? Thanks.
My Rom is 2.1-update1 rooted.
hahabear said:
Help!!!!!
I have installed V1.0.4, but my touch keys(back, Menu, Home and Search) don't work.
Then I have tried to restore it, but it's failed.
How could I fix it? Thanks.
My Rom is 2.1-update1 rooted.
Click to expand...
Click to collapse
Hmm I dont have this issue, how does it fail? Does it just freeze, or does it FC, or does it say it finishes then do nothing? Also, what ROM, CM? Enomther? Please let me know so I can work on this.
Also, to fix it, download the attached file, & run the following commands (you must have ADB set up):
adb remount
adb shell rm /system/usr/keylayout/mahimahi-keypad.kl
adb push *path to downloaded file* /system/usr/keylayout/mahimahi-keypad.kl
Or you can just reflash your ROM, either way you'll get the same thing.
My phone is Nexus one.
My rom is Official v2.1-updated1.
When I execute the command as your indication.
"adb shell rm /system/usr/keylayout/mahimahi-keypad.kl"
rm failed for /system/usr/keylayout/mahimahi-keypad.kl, No such file or directory
What's wrong? And thank you for your quick reply.
hahabear said:
My phone is Nexus one.
My rom is Official v2.1-updated1.
When I execute the command as your indication.
"adb shell rm /system/usr/keylayout/mahimahi-keypad.kl"
rm failed for /system/usr/keylayout/mahimahi-keypad.kl, No such file or directory
What's wrong? And thank you for your quick reply.
Click to expand...
Click to collapse
Ok excellent that answers the second part of my question its failing to copy the file back over after deleting the original on certain ROMs.
You can just skip that step and go on to the "adb push" step. Also, can you run the command "adb shell cp" and tell me the output?
bingo! Thanks for your help. It's resolved.
On the other hand, I could get the mod.kl from SD Card, push again, Search2play will work, is that right?
hahabear said:
bingo! Thanks for your help. It's resolved.
On the other hand, I could get the mod.kl from SD Card, push again, Search2play will work, is that right?
Click to expand...
Click to collapse
Yes, but can you tell me what it says if you run the command "adb shell cp"
That will tell me if the issue is with the version of BusyBox on some ROMs.
Geniusdog254 said:
Yes, but can you tell me what it says if you run the command "adb shell cp"
That will tell me if the issue is with the version of BusyBox on some ROMs.
Click to expand...
Click to collapse
C:\N1root>adb shell cp
cp: not found
My god!!! It means there is not cp command in my phone?
hahabear said:
C:\N1root>adb shell cp
cp: not found
My god!!! It means there is not cp command in my phone?
Click to expand...
Click to collapse
Yeah exactly lol. Not sure if that was sarcasm or what, but thats what is causing the FC's and the failures some people are getting. And theres not a damn thing I can do about it.
I would recommend installing the CyanogenMod ROM, since it is fast, adds extra features, and supports cp Then the app will work just fine
Anyway. Thanks for your help. You are so kind. I will try new ROM later. And I will support your work. cu.
hahabear said:
Anyway. Thanks for your help. You are so kind. I will try new ROM later. And I will support your work. cu.
Click to expand...
Click to collapse
Thanks you very much for your support. Glad I could help you, if you have any other problems please email me, email listed in the market
Donate version now just to support me, added support for all devices to free version.
Please donate!
1.3 version uploaded
See changelog.
Any updates on newer phones?
KaliKot said:
Any updates on newer phones?
Click to expand...
Click to collapse
I can make it work for any phone without a NAND lock. Any requests?
I need to do the Galaxy S series, but the only one I can test is the Epic and I'm not sure if the others have different mount tables or not. Desire still has NAND lock so I can't do it. Not sure about Droid2/X. Just email/Twitter/PM me or post here with a request. I'll get back to you.
[Background]
A few users have gotten Transformers with Android 2.2 installed with diagnostic tools included. So far there have been 3 confirmed users who have gotten these units.
These units are shipped rooted from Asus
Unfortunately, t0dbld has confirmed that the sbk is locked on these devices
[Photos]
{
"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"
}
[System Dump]
System Archive:
http://db.tt/p3p14Ez
MD5 for Archive:
http://db.tt/DWpL8U7
Or
85c584c6f425fbd6ab111b9f73251fe0
[Reference Thread]
http://forum.xda-developers.com/showthread.php?t=1054120
[Credits]
mmsson - Took time to provide system dump
t0dbld - Helping with users with 2.2 TF and confirming sbk is locked
Welshiren - Currently taking his time to provide more details on his 2.2 TF
*I did not create the system dump or the photographs, and i take no credit for it
Placeholder For Later Or For Important Temporary Information
The MD5 link might be broken.
FYI it should be:
85c584c6f425fbd6ab111b9f73251fe0
Roach2010 said:
The MD5 link points to the system dump.
FYI it should be:
85c584c6f425fbd6ab111b9f73251fe0
Click to expand...
Click to collapse
Yup just realized that lol, corrected the link, thanks
Just some findings i found that i thought where interesting
in \system\lib\hw\wlan\ there are specific broadcom files
bcm4329.ko
fw_bcm4329.bin
fw_bcm4329_apsta.bin
fw_bcm4329_mfg.bin
The Broadcom 4329 supports FM according to specs
http://www.broadcom.com/products/Blu...utions/BCM4329
and look what i found in the app folder
FMTesttool.apk
Interesting...
The FMTesttool.apk wont run for me
I dont know if it is a honeycomb issue or a issue with it being disable in the Broadcom bin files
One user told me when he ran it it displayed radio frequencies but everything was in Chinese, and there was no audio output or any type of RF noise coming from the TF
Do any of these users have root access, a system dump is nice but we could use alot more than that.. we need to see if there partitions are hidden etc we need to see if they have an available partition map or at least a blkid command, next we should dd these partitions etc, the best we could gain from this is to see if the partitions still match up the same as in hc builds and than know where to look to unlock our devices
t0dbld said:
Do any of these users have root access, a system dump is nice but we could use alot more than that.. we need to see if there partitions are hidden etc we need to see if they have an available partition map or at least a blkid command, next we should dd these partitions etc, the best we could gain from this is to see if the partitions still match up the same as in hc builds and than know where to look to unlock our devices
Click to expand...
Click to collapse
I am unsure since the 3 known users who have gotten these units seem to be regular end users, the dump that was acquired was done through a walkthrough by another member on xda from what i was told
If you want to contact welshiron and walk him through the steps in doing a dd image of the partitions and go over any other things you want to know about the device
(dont know if he is familiar with linux, maybe have him do it through a live CD if he is up to it, or maybe use Cygwin to run DD if it even supports it)
Im still an Android noob so i cant really help him too much
If he is the trusting type he might let someone remote in via teamviewer, logmein, etc. lol
Anyways, my theory is these are shipping mistakes because of the limited supply, and once supply increases we may never see any of these test units again
You Dont need linux for a DD, we need root and that is all, also if they are on 2.2 and linux kernel .32 than super one click should work for a quick root and unroot when done. after than we need to get them to open an adb shell,
C:\ adb shell
$ su
# blkid
this will get us some output that we can go on from there also there maybe be a partition map on the tab... i wont get mine till tuesday so i can only guess on where it is . either way we would want to start dd the partitions he has or tha came up for example from the same adb shell with su
C:\ adb shell
$ su
# dd if=/dev/block/mmcblk0p1 of=/sdcard/mmcblk0p1.img
t0dbld said:
You Dont need linux for a DD, we need root and that is all, also if they are on 2.2 and linux kernel .32 than super one click should work for a quick root and unroot when done. after than we need to get them to open an adb shell,
C:\ adb shell
$ su
# blkid
this will get us some output that we can go on from there also there maybe be a partition map on the tab... i wont get mine till tuesday so i can only guess on where it is . either way we would want to start dd the partitions he has or tha came up for example from the same adb shell with su
C:\ adb shell
$ su
# dd if=/dev/block/mmcblk0p1 of=/sdcard/mmcblk0p1.img
Click to expand...
Click to collapse
Didnt know dd was built into android shell, thats cool
Can you contact him and walk him through it, i contacted asking him if he ever used ADB before, haven't gotten a response yet
SlimDan22 said:
Just some findings i found that i thought where interesting
in \system\lib\hw\wlan\ there are specific broadcom files
bcm4329.ko
fw_bcm4329.bin
fw_bcm4329_apsta.bin
fw_bcm4329_mfg.bin
The Broadcom 4329 supports FM according to specs
http://www.broadcom.com/products/Blu...utions/BCM4329
and look what i found in the app folder
FMTesttool.apk
Interesting...
The FMTesttool.apk wont run for me
I dont know if it is a honeycomb issue or a issue with it being disable in the Broadcom bin files
One user told me when he ran it it displayed radio frequencies but everything was in Chinese, and there was no audio output or any type of RF noise coming from the TF
Click to expand...
Click to collapse
new roms have the same bcm4329 files, look in /system/vendor in any rom (prime for example).
and lol i'm stupid, dd is the obvious answer for the boot.img.
We could theoretically make a cool testing rom with that.
also, if a wipe/factory reset got rid of testing apps, that means they were in /data, so we need a dump of that too, almost for sure. you see, i've never had a factory reset that so much as TOUCHED system partition, so if the apps disappeared after a reset, they were in data, not /system.
Hi!
Sorry if it has been posted already .
There is another guy who has received a 2.2 TF, and he cannot post in this thread.
I beg any master please go to this link (look in the pages 19 and 20) and help this man before he returns his TF tomorrow. Maybe there is still time to get something useful.
http://forum.xda-developers.com/showthread.php?t=1054120&page=20
Regards.
CalvinH said:
Hi!
Sorry if it has been posted already .
There is another guy who has received a 2.2 TF, and he cannot post in this thread.
I beg any master please go to this link (look in the pages 19 and 20) and help this man before he returns his TF tomorrow. Maybe there is still time to get something useful.
http://forum.xda-developers.com/showthread.php?t=1054120&page=20
Regards.
Click to expand...
Click to collapse
Are you talking about mmsson, if so he already returned it, he is the one who provided the partial system dump
But if you are talking about welshiron then i am in contact with him, it seems that no one has contacted him yet which is disappointing, i am trying my best to help him but i am not as experienced as other users in the community
Im working on showing how how to check for root
Yes I was talking about welshiron.
Thank you for your efforts. I would like to be able to do something by myself, but can't do much (well, apart from annoy you really expert guys by posting here and there).
Good luck.
Regards.
what exactly are the advantages of a 2.2 dump? will you be able to make older apps work?
I wonder if they have a different bootloader.. Is the partition layout the same? Thats a different tegrastats than my gtab.. Has anyone confirmed that this rom is not already rooted.. certainly seems like it would be. I really hope I get one of these treats.
Update:
The dev units do have root access!, welshiron has confirmed it and was able to run the su command to enable root privileges via adb
i need help from other experienced members here, i am going to have him run the blkid command, but after that i am unable to reliably walk him through and dumps through dd, due to lack of experience
I seem to have permission to post here now, how do I run the blkid command and what will that tell us?
Just a reminder, Android and Linux are alien to me so I will need help with the syntax
welshiron said:
I seem to have permission to post here now, how do I run the blkid command and what will that tell us?
Just a reminder, Android and Linux are alien to me so I will need help with the syntax
Click to expand...
Click to collapse
Im not sure either, i cant run it on my rooted phone with cyanogen
Im really surprised there is not a lot of activity or help, maybe its a slow day lol
I'm no expert but on my Desire I do this...
Download Mini ADB.
Have mine if ya need Link!
Run the Runme.Bat file
In the pop-up box type: adb shell
when it gets a console type: blkid
EDIT: Just in case it wasn't obvious, connect your Transformer to PC with USB and enable USB Debugging.
EDIT2: I think it's possible you will need to push Busybox to your device.
Here's a couple alterations to the quickpanel toggles in the dropdown of Supercharged V4 (the 3rd one is the original if you want to revert back).
You need to replace your SystemUI.apk found in /system/app/
cogeary said:
Here's everything you need to do, make sure you follow the directions exactly (especially with renaming)
-Download one of the .apk's
-Rename it to "SystemUI.apk" without the quotes. Note that .apk is the file extension, and on windows by default you can't change the file extension just by a simple right click->rename, so just make sure that the file is called "SystemUI.apk" and not "SystemUI.apk.apk"
-Connect your phone to your computer. Select any type of USB Connection other than "Charge Only."
-Drag and drop the "SystemUI.apk" directly into your phone's storage "In "My Computer" or "Computer)
-You can change the connection type to "charge only" now
-Open up a command prompt (Start->Search/Run->cmd.exe
-Make sure you have the android SDK set up and you have adb in your PATH... or you have a functioning method to access adb
-Now inside the command prompt, type:
adb shell
su
cp /sdcard/SystemUI.apk /system/app/
reboot
-Your phone will reboot and the notification toggles should be installed!
Click to expand...
Click to collapse
Let me know how you all like it and if I should change them. I was going for toggles that were more distinct from their on/off states. Hit the "thanks" if you like 'em and enjoy!
First:
{
"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"
}
Second:
No Bars:
Thanks to lfaber06 for the great ROM we have available to us.
Hey so i was jw... will this be on supercharged v5? Either way. Nice job!
Deliberate said:
Hey so i was jw... will this be on supercharged v5? Either way. Nice job!
Click to expand...
Click to collapse
I have no idea if lfaber06 will include it. I'm perfectly fine with that if he chooses so. Thanks for the compliment!
Is he working on a v5? Jw. I guess I should of asked him. But still to new for the development section. Lol
Looks great. Was wondering if it was possible to remove the blue indicator line all together since its not really needed now. Would clean it up some and go better theme-wise for those who have different colors in their status bar icons.
Thanks a lot if you can do it!
loderjm said:
Looks great. Was wondering if it was possible to remove the blue indicator line all together since its not really needed now. Would clean it up some and go better theme-wise for those who have different colors in their status bar icons.
Thanks a lot if you can do it!
Click to expand...
Click to collapse
I can do that this evening when I get back home. Shouldn't be too hard (just set full transparency to 3 images).
Sent from my MB865 using XDA App
loderjm said:
Looks great. Was wondering if it was possible to remove the blue indicator line all together since its not really needed now. Would clean it up some and go better theme-wise for those who have different colors in their status bar icons.
Thanks a lot if you can do it!
Click to expand...
Click to collapse
It's up now. There is a way to get rid of the padding under the icons (since the bars are no longer there--well, they're actually there, but invisible), but I'd rather not tackle that right now. It involves xml edits that I've done before (back in my Captivate days ), but I don't remember exactly and would rather not spend the time right now (sorry).
I hope it's what you had in mind.
Awesome. Looks great. Thanks for the quick turnaround!
so i dont know what im doing wrong but when i put the file in the root of my sd and do all the adb shell stuff. IDK but it reads everything but the file?
what am i doing wrong?
Deliberate said:
so i dont know what im doing wrong but when i put the file in the root of my sd and do all the adb shell stuff. IDK but it reads everything but the file?
what am i doing wrong?
Click to expand...
Click to collapse
Do you mean you do the
cp /sdcard/SystemUI.apk /system/app/
but it doesn't actually copy it over? Do you get an error when you try this? If you do this with your phone on, you will get a force close right away and then you need to type "reboot" while still in the adb shell and then your phone will reboot and everything is cool.
Could you explain a little more of what you did? I'll try to help, but I'm not very experienced with adb yet (Jim or lfaber06 among others and tutorials can help better with this).
Ya i put adb shell
Su
Then that code and it said there was no such file. I renamed it though
Do you see the file on your sdcard as "SystemUI.apk" without the quotes? This is what it needs to be (I assumed that's what you mean when you renamed it, but just making sure). If it's not that exact name, it won't overwrite the old one in /system/app/. Also make sure you have permissions set to write to /system/ (I actually would just use rom toolbox or something and use the script in there).
If nothing else, have you tried to reboot both your phone and computer? Sorry I can't be more help. I personally had the files named on my computer to "SystemUI.apk" before putting it on my sdcard (instead of renaming it after it's already on the phone). That might be something else to try, but I doubt that would be the reason. Someone smarter than I could probably figure it out.
Ya im not so good with adb... and also is it possible to do this with the phone off? If so how? Thank u for your reply by the way!
Deliberate said:
Ya im not so good with adb... and also is it possible to do this with the phone off? If so how? Thank u for your reply by the way!
Click to expand...
Click to collapse
I'm in the same boat with you on the adb thing . I'm making guesses on what it might be without truly understanding how to efficiently use adb. I believe you can use it with the phone off, but I haven't tried yet. Ultimately, I hope to get around to making a flashable zip for things like this. However, I need to spend a little less time tinkering for right now (and I brought my phone back to stock in preparation/hope of the pre-release soak). Let me know if you figure anything out (I'd like to learn as well).
I tried renameing it from my computer and from my phone and it still didnt work. How do u set the permissions from adb? Sorry for so many questions. I just really suck at adb.
---------- Post added at 10:23 AM ---------- Previous post was at 10:10 AM ----------
Ya i will for sure. Prerelease soak? Are u gonna be one of the update testers? Has that been decided yet?
I used this to mount it as write (after "adb shell" and "su"):
mount -o rw,remount /dev/block/stl9 /system
I found this thread useful for adb:
http://forum.xda-developers.com/showthread.php?t=872128
Deliberate said:
I tried renameing it from my computer and from my phone and it still didnt work. How do u set the permissions from adb? Sorry for so many questions. I just really suck at adb.
---------- Post added at 10:23 AM ---------- Previous post was at 10:10 AM ----------
Ya i will for sure. Prerelease soak? Are u gonna be one of the update testers? Has that been decided yet?
Click to expand...
Click to collapse
I hope I will be...I filled out the survey pretty quick after getting the email [fingers-crossed]. I haven't heard anything since (Sunday).
One other thought I just had:
When you rename the file, did it show the extension (.apk) or just SystemUI_second (or whichever one you're trying to use)? I'm wondering if by renaming it "SystemUI.apk" that it's actually seeing "SystemUI.apk.apk" or something. Doubtful, but just another thing to check.
No i wonderd that 2 so i tried SystemUI without anything and it still didnt work. Idk. Thanks for all your help though and good luck with the soak!
Oops sorry forgot to turn the page, didn't see the whole next page of replies XD
Anyways... just making sure, when you say you did "Su" did you type in "su" or "Su"?
Here's everything you need to do, make sure you follow the directions exactly (especially with renaming)
-Download one of the .apk's
-Rename it to "SystemUI.apk" without the quotes. Note that .apk is the file extension, and on windows by default you can't change the file extension just by a simple right click->rename, so just make sure that the file is called "SystemUI.apk" and not "SystemUI.apk.apk"
-Connect your phone to your computer. Select any type of USB Connection other than "Charge Only."
-Drag and drop the "SystemUI.apk" directly into your phone's storage "In "My Computer" or "Computer)
-You can change the connection type to "charge only" now
-Open up a command prompt (Start->Search/Run->cmd.exe
-Make sure you have the android SDK set up and you have adb in your PATH... or you have a functioning method to access adb
-Now inside the command prompt, type:
adb shell
su
cp /sdcard/SystemUI.apk /system/app/
reboot
Click to expand...
Click to collapse
-Your phone will reboot and the notification toggles should be installed!
::::::::::::::::::::::::EDIT:::::::::::::::::::::::::::::::::::::::::::::
Bin4ry has come up with a way to root many android phones
http://forum.xda-developers.com/showthread.php?p=31545627
UltimateSeo at Android Forums has made a version that will work on the Hydro
http://androidforums.com/hydro-all-things-root/619232-kyocera-hydro-confirmed-working-root.html
I will leave the info in this thread intact, someone may find some use for it
::::::::::::::::::::::::EDIT:::::::::::::::::::::::::::::::::::::::::::::
Hi all
I am new here, I hope it is OK that I posted this in this forum, if not please delete.
I could not find the ADB USB drivers for the Kyocera Hydro, on the Kyocera web site, so I decided to modify the Kyocera Milano driver to work with this phone
View attachment kyocera_hydro_adb_usb_driver.zip
This driver is for Windows 32/64 systems, and does not have an install utility, you have to manually install from the device manager.
I did this so that I could start trying to find a root exploit on this phone, so far I have had no luck, but I have never tried to find an exploit before, so I am a noob at it.
Maybe if we get more people looking at it, we can find something.
In my opinion the security seems pretty tight, the kernel is patched to other ICS kernel exploits, the file permission are very strict, there is no way to access the boot loader/fastboot that I know of with button combos, or doing an “adb reboot bootloader” command, the stock recovery has less options than most stock recoveries.
I do not think I have the skills needed to find an exploit, I am hoping some mad genius will come along and be able to find one, of course they will be given full credit for doing such. I am going to post some information and files that may help us find an exploit, please see post number three.
For those who may know me, I am not really starting to do any dev work again just yet, I just want my new phone to be rooted, so that I can do dev work on it at some later time
If we are able to get root, this will probably be the thread I release any stuff I make for this phone, so I made a few "reserved posts" hope that is OK
.,
reserved
I am going to put information and some files in this post that may help someone find a vulnerability, of course there are a lot of things I cannot get because the phone is locked down
General Info
This phone has an MSM8655 processor and the ROM and Kernel seem to be made from CAF (Code Aurora) source code using the msm7630_surf platform , of course it would have been modified a lot by Kyocera
Android Version 4.0.4 - Build IML77 - Kernel Version 3.0.8-perf
Dump of /system, "adb pull / c:\dump"
It is not a complete ROM, it is only the files I was able read and pull from ADB, it cannot be used for anything, but maybe someone who looks at it may find a hole somewhere.
www.mediafire.com/?cuppd1dj29nvbl1
De-Compiled .apk and .jar These are all the .apk and .jar files in the app and framework folders de-compiled with apktool
https://github.com/hroark13/hydro_decompiled
De-Odexed "/system/app" Files All the /system/app files de-odexed
http://www.mediafire.com/?rs77g1tiwvk2hbv
De-Odexed "/system/framework" Files All /system/framework files de-odexed
http://www.mediafire.com/?g12wcmpdpojj1yz
Kernel configuration “adb pull /proc/config.gz”
View attachment hydro_config.txt
Mounts "adb shell mount > hydro_mounts.txt"
View attachment hydro_mounts.txt
Folder Permissions “adb shell ls –l –R / > hydro_permissions.txt”
The /data folder is locked down tight so there really is no info about it there, this was a big text file, so I had to zip it
View attachment hydro_permissions.zip
logcat "adb shell logcat > hydro_logcat.txt"
View attachment hydro_logcat.txt
dmesg "adb shell dmesg > hydro_dmesg.txt"
View attachment hydro_dmesg.txt
Props"adb shell getprop > hydro_props.txt"
View attachment hydro_props.txt
Well, if anyone finds anything, has any good ideas, or needs me to upload something else, please post a reply
.
Here are some dial codes I found that work
##22767# or ##BCSMS#
##25327# or ##CLEAR# ACCESS CODE
##3282# or ##DATA# MSL TO EDIT
##33284# or ##DEBUG# ACCESS CODE
##3424# or ##DIAG# MSL
##4772579# or ##GPSCLRX# MSL
##564#
##72786# or ##SCRTN# MSL
##786# or ##RTN# MSL TO RESET
##8378# or ##TEST# MSL
##9526# or ##WLAN#
ACCESS CODE = SPRINT (777468)
One thing that I found interesting "at least it was interesting to me, hey I am new at this"
/system/etc/firmware/wlan/volans/KCJ/Wifi_Mac_Set.sh
there also seems to be a copy of busybox at /system/etc/firmware/wlan/volans/KCJ/busybox
If I do an "adb shell /system/etc/firmware/wlan/volans/KCJ/Wifi_Mac_Set.sh"
I get
Code:
/system/bin/sh: /system/etc/firmware/wlan/volans/KCJ/Wifi_Mac_Set.sh: cannot exe
cute - Permission denied
If I do a "adb shell mksh /system/etc/firmware/wlan/volans/KCJ/Wifi_Mac_Set.sh"
I get
Code:
mount: Operation not permitted
Unable to chmod /system/etc/firmware/wlan/volans/KCJ/busybox: Read-only file sys
tem
Unable to chmod /system/etc/firmware/wlan/volans/KCJ/fer_measure_step1.sh: Read-
only file system
Unable to chmod /system/etc/firmware/wlan/volans/KCJ/fer_measure_step2.sh: Read-
only file system
Unable to chmod /system/etc/firmware/wlan/volans/KCJ/iwpriv: Read-only file syst
em
Unable to chmod /system/etc/firmware/wlan/volans/KCJ/kcj_wifi_on.sh: Read-only f
ile system
/system/etc/firmware/wlan/volans/KCJ/Wifi_Mac_Set.sh[45]: /system/etc/firmware/w
lan/volans/KCJ/busybox: cannot execute - Permission denied
/system/etc/firmware/wlan/volans/KCJ/Wifi_Mac_Set.sh[69]: /system/etc/firmware/w
lan/volans/KCJ/busybox: cannot execute - Permission denied
MACADDR NOT CHANGE
Unable to chmod /system/etc/firmware/wlan/volans/WCN1314_qcom_cfg.ini: Read-only
file system
rm failed for /data/fcc/fcc.zip, No such file or directory
rm failed for /data/fcc/, No such file or directory
rm failed for /system/etc/firmware/wlan/volans/FCC/fcc_daemon, No such file or d
irectory
mount: Operation not permitted
I do not know why I can execute that script with mksh
.
Another thing that may be a potential vulnerability is
/system/xbin/updateue
This seems to be the Kyocera System Updater
I really would not know how to exploit this, but I figured I would just point it out, and I am trying to get past my 10 post thingy
.
I have tried using the debugfs exploit from miloj, but /data/local is owned by root so I can not "mv /data/local/tmp /data/local/tmp.bak"
I have tried the mempodroid / mempodipper exploit from saurik but that vulnerability seems to be patched in this kernel
I have also tried some of the older GB exploits methods with no luck
.
your link
www.mediafire.com/?cuppd1dj29nvbl1
I hope someone does help with this. I can vouch for Hroark and his work (His kernel work on the ZTE Warp was most helpful). Good luck big guy! Your work is still appreciated!
Sent from my N860 using xda premium
atlharp said:
I hope someone does help with this. I can vouch for Hroark and his work (His kernel work on the ZTE Warp was most helpful). Good luck big guy! Your work is still appreciated!
Sent from my N860 using xda premium
Click to expand...
Click to collapse
yeah, I am trying to provide a lot of information, just so anyone who wants to help, does not have to waste time on doing some of the things I am able to do myself, this way they will be more encouraged to help out
do you have a Hydro
I just got mine a few days ago, I like it, it is a pretty good phone
.
OK so I only need two more posts to get to my 10 post thing, so here is a nice picture of my girl friend
{
"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"
}
shabbypenguin said:
your link
www.mediafire.com/?cuppd1dj29nvbl1
Click to expand...
Click to collapse
thank you Shabster, I think I can post external links now since this is my 10th post
hroark13 said:
yeah, I am trying to provide a lot of information, just so anyone who wants to help, does not have to waste time on doing some of the things I am able to do myself, this way they will be more encouraged to help out
do you have a Hydro
I just got mine a few days ago, I like it, it is a pretty good phone
.
Click to expand...
Click to collapse
No, but I am trying to steer a friend to it. It looks promising though.
yes finally
ive had this phone since day one and cant even get a case or screen protector i had to cut one to fit it seems this phone didnt get much air on lauch but i love the wate thing cause i am a auto mechanic and iam always geting my phone wet ,i wish i could help with the root issue but i have no experience and no one to how me the ropes iam sure i could catch on with all help any one game to help a noob who wants needs a master to whom i can ask questions
fordefied said:
ive had this phone since day one and cant even get a case or screen protector i had to cut one to fit it seems this phone didnt get much air on lauch but i love the wate thing cause i am a auto mechanic and iam always geting my phone wet ,i wish i could help with the root issue but i have no experience and no one to how me the ropes iam sure i could catch on with all help any one game to help a noob who wants needs a master to whom i can ask questions
Click to expand...
Click to collapse
this phone is great for the price, I paid $115.00 plus tax at a Boost store,
even if we do not get root, the phone is worth having, so far I am happy with mine
I have not tried getting it wet yet
I even dropped it a couple of times, and it held up pretty good
atlharp said:
No, but I am trying to steer a friend to it. It looks promising though.
Click to expand...
Click to collapse
it is worth it, in my opinion
I have had no problems so far, but it has been less than a week, so who knows
hroark13 said:
this phone is great for the price, i paid $115.00 plus tax at a boost store,
even if we do not get root, the phone is worth having, so far i am happy with mine
i have not tried getting it wet yet
i even dropped it a couple of times, and it held up pretty good
Click to expand...
Click to collapse
yea iagree it is a durable phone
why is it freezein
Ive had this phone from its release, it was good at first ,but now it keeps freezing and its so slow i don't know what happened i had a evo flashed to boost before this phone and it has same snapdragon process er,why is this phone not as smooth ,has any one else experience d this
fordefied said:
Ive had this phone from its release, it was good at first ,but now it keeps freezing and its so slow i don't know what happened i had a evo flashed to boost before this phone and it has same snapdragon process er,why is this phone not as smooth ,has any one else experience d this
Click to expand...
Click to collapse
I was having slow data issues, so I switched to Metro PCS and got the new LG Motion, so far I am very happy with it.
I will probably sell my Hydro, because I can not return it, since I have more than one hour of talk time on it.
Hroark
Good to see you back at it Hroark.
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