Database Info

how to get on the phone system without enabling usb debug android

anyone know how to get into the system and change any file in there with access to computers without enabling usb debug on android phone ??

ycusoy said:
anyone know how to get into the system and change any file in there with access to computers without enabling usb debug on android phone ??
Click to expand...
Click to collapse
Are you on stock rom or a rooted one? It is possible through recovery. In CWM and 4EXT recoveries, there's an option to mount system. Then you should be able to access it from a pc. In recovery you dont have the ADB option so I guess it'll work. If you're not rooted and do not have custom recovery installed, I don't know. You might also try QtADB program, is like a file explorer on your pc with which you can access phone files in a graphical manner, without need to know ADB commands. You need to have Android SDK installed on your pc for these methods to work
Sent from nowhere over the air...

Rapier said:
Are you on stock rom or a rooted one? It is possible through recovery. In CWM and 4EXT recoveries, there's an option to mount system. Then you should be able to access it from a pc. In recovery you dont have the ADB option so I guess it'll work. If you're not rooted and do not have custom recovery installed, I don't know. You might also try QtADB program, is like a file explorer on your pc with which you can access phone files in a graphical manner, without need to know ADB commands. You need to have Android SDK installed on your pc for these methods to work
Sent from nowhere over the air...
Click to expand...
Click to collapse
hmm .. that's my fault. I forgot to backup the data from the phone. There are two mistakes here that I made:
A. I tried upgrading my android phone to a higher level, but the one included with the correct phone model in the / system / build.prop.
2. I also already remove the formal application in the directory / sytem / app.
therefore, I want to ask if there are other ways that I can use to get to the root without interference adb.exe? for example with special commands in windows or ubuntu, or by flashing using a particular application, or the fastboot command which allows root can be accessed with ease ..

ycusoy said:
hmm .. that's my fault. I forgot to backup the data from the phone. There are two mistakes here that I made:
A. I tried upgrading my android phone to a higher level, but the one included with the correct phone model in the / system / build.prop.
2. I also already remove the formal application in the directory / sytem / app.
therefore, I want to ask if there are other ways that I can use to get to the root without interference adb.exe? for example with special commands in windows or ubuntu, or by flashing using a particular application, or the fastboot command which allows root can be accessed with ease ..
Click to expand...
Click to collapse
Ok... But you can still enter in recovery right? I mean, don't know exactly what phone model you have, but there's power on key combination that usualy allow to boot in recovery. For ex, on Desire S I keep pressed vol-down+ power then select recovery. And from there I can acces system or flash another ROM. You cannot do the same?
Sent from nowhere over the air...

Rapier said:
Ok... But you can still enter in recovery right? I mean, don't know exactly what phone model you have, but there's power on key combination that usualy allow to boot in recovery. For ex, on Desire S I keep pressed vol-down+ power then select recovery. And from there I can acces system or flash another ROM. You cannot do the same?
Sent from nowhere over the air...
Click to expand...
Click to collapse
yup ... It is true bro. I can still access the recovery mode. rom to install it but I always fail. My cell phone specs, Nexian nx-a892. congenital previous 2.2.1 version, then I tried upgrading to 2.2.2 from GSmart G1315 product. Here I make text editing the wrong file build.prop. I change only the G1315 model only, without including the GSmart. Then came the refusal every time I go in recovery mode.
Various tools have been tried, but all to no avail. One way that I think can be done only with fastboot. But until this moment I have not managed to solve the secret of accessing the android system, without the ADB and USB Debug ...
At other times, I had also tried the Linux operating system. Because Android applying the same thinking with linux. but just the same, I stopped in there a way to access the root ...

ycusoy said:
yup ... It is true bro. I can still access the recovery mode. rom to install it but I always fail. My cell phone specs, Nexian nx-a892. congenital previous 2.2.1 version, then I tried upgrading to 2.2.2 from GSmart G1315 product. Here I make text editing the wrong file build.prop. I change only the G1315 model only, without including the GSmart. Then came the refusal every time I go in recovery mode.
Various tools have been tried, but all to no avail. One way that I think can be done only with fastboot. But until this moment I have not managed to solve the secret of accessing the android system, without the ADB and USB Debug ...
At other times, I had also tried the Linux operating system. Because Android applying the same thinking with linux. but just the same, I stopped in there a way to access the root ...
Click to expand...
Click to collapse
anyone can help me ???????:crying::crying::crying::crying::crying::crying::crying::crying::crying:

I'm having the same problem. Can anyone help accessing files on a soft-brick with android stock rom, with USB debugging disabled?

MyTab brick
And what if I have also softbricked tab (Mytab 10 dual core) I have messed up with build.prop file probably but I don't have any bootloader mode or any option like that. Is there any way to get to the Android system files? I have now sent it for a warranty however I'm sure they won't accept it. Tab launches but hungs at boot screen (computer can see it). I have USB debugging off. Any help would be apreciated much

[Q] Unfortunately Launcher has stopped and other issues

Hi guys,
I've been reading you for a while, but this is actually my first post.
Currently stuck with a "Unfortunately, Launcher has stopped" on my tablet, with no access to any menus except my Settings. The menu bar (back, home and multitasking) is now gone. I've got my keyboard to navigate, but something in the display is also quite wrong, image seems to be zoomed, or set at the wrong resolution. Tried to search on the forum, but all posts found were not about the same rom or the same issue. Sorry if I missed one.
Here's a little background story:
I've rooted my TF300T about a month ago and installed Hydro 4.1. It has been working very well since then, but in the last days, I thought that my tablet felt a little slower than usual, so I started searching if an update to 4.2 was available.
I'm not sure if this is what caused the issue or not, but I went into my "Power button" menu and went into "Recovery" mode (instead of Shutdown, reboot, etc.), which then restarted my unit into TWRP menu.
I then selected the "System" submenu and simply touched "Reboot". (terms might not be exact). At the first reboot, I got the problems that I described.
Can't do much, popup keeps appearing on my screen. I haven't tried yet to clear the cache of my Launcher, which I'm trying to avoid as I would prefer to avoid rearranging 5 pages of icons, but between that and reinstalling everything, obviously I prefer to simply lose my display preferences.
Can anyone help me about what caused my issue, and what can I do now?
Here are 2 screenshots that I took, showing that my bottom menu is missing and that the fonts aren't set right (clock and left icon). Also, my notifications menu now appears near the middle of my screen.
EDIT: I unfortunately cannot post links yet
I remember installing an app (with root access) that gave me a menu about my resolution. One thing that I'm wondering, could it be that the resolution got changed and I simply never rebooted since the change, which now caused my Launcher to crash? How can I launch an app without having access to the app menu?
Thanks in advance for your help.

irepressed said:
Hi guys,
I've been reading you for a while, but this is actually my first post.
Currently stuck with a "Unfortunately, Launcher has stopped" on my tablet, with no access to any menus except my Settings. The menu bar (back, home and multitasking) is now gone. I've got my keyboard to navigate, but something in the display is also quite wrong, image seems to be zoomed, or set at the wrong resolution. Tried to search on the forum, but all posts found were not about the same rom or the same issue. Sorry if I missed one.
Here's a little background story:
I've rooted my TF300T about a month ago and installed Hydro 4.1. It has been working very well since then, but in the last days, I thought that my tablet felt a little slower than usual, so I started searching if an update to 4.2 was available.
I'm not sure if this is what caused the issue or not, but I went into my "Power button" menu and went into "Recovery" mode (instead of Shutdown, reboot, etc.), which then restarted my unit into TWRP menu.
I then selected the "System" submenu and simply touched "Reboot". (terms might not be exact). At the first reboot, I got the problems that I described.
Can't do much, popup keeps appearing on my screen. I haven't tried yet to clear the cache of my Launcher, which I'm trying to avoid as I would prefer to avoid rearranging 5 pages of icons, but between that and reinstalling everything, obviously I prefer to simply lose my display preferences.
Can anyone help me about what caused my issue, and what can I do now?
Here are 2 screenshots that I took, showing that my bottom menu is missing and that the fonts aren't set right (clock and left icon). Also, my notifications menu now appears near the middle of my screen.
EDIT: I unfortunately cannot post links yet
I remember installing an app (with root access) that gave me a menu about my resolution. One thing that I'm wondering, could it be that the resolution got changed and I simply never rebooted since the change, which now caused my Launcher to crash? How can I launch an app without having access to the app menu?
Thanks in advance for your help.
Click to expand...
Click to collapse
What you describe is likely caused by changing the resolution. Are you still running hydro 4.1?
You can likely recover by replacing your build.prop or editing the one you now have. build.props are usualy rom specific so you need one from the rom you are using.

tobdaryl said:
What you describe is likely caused by changing the resolution. Are you still running hydro 4.1?
You can likely recover by replacing your build.prop or editing the one you now have. build.props are usualy rom specific so you need one from the rom you are using.
Click to expand...
Click to collapse
Yes, still using Hydro 4.1. I do have a build.prop editor installed on my tablet, but since I can't launch app, I don't know how to do it.
I'll try to connect the tablet to my PC and see if I can get access to my file from there.
Thanks!

irepressed said:
Yes, still using Hydro 4.1. I do have a build.prop editor installed on my tablet, but since I can't launch app, I don't know how to do it.
I'll try to connect the tablet to my PC and see if I can get access to my file from there.
Thanks!
Click to expand...
Click to collapse
I'm presently downloading 4.1 hydro to retrieve the build.prop. If you unzip it the build.prop is /system/build.prop also located there on your tab. I have another fifteen minutes to download if you wish for me to supply the file!

tobdaryl said:
I'm presently downloading 4.1 hydro to retrieve the build.prop. If you unzip it the build.prop is /system/build.prop also located there on your tab. I have another fifteen minutes to download if you wish for me to supply the file!
Click to expand...
Click to collapse
If you could, I would appreciate it!
Only thing left, how can I send the file to my TF300T without access to my apps? I'm currently trying to cheat by opening my apps using the Share feature with screenshots taken, but so far, no success.

irepressed said:
If you could, I would appreciate it!
Only thing left, how can I send the file to my TF300T without access to my apps? I'm currently trying to cheat by opening my apps using the Share feature with screenshots taken, but so far, no success.
Click to expand...
Click to collapse
We should be able to push with adb, set permissions, and reboot.
---------- Post added at 04:58 PM ---------- Previous post was at 04:36 PM ----------
http://www.mediafire.com/?tk3cifzci0vw24e
place the build.prop from the zip file into the directory with fastboot.
Open terminal or cmd in the directory with fastboot.
Boot into twrp – twrp provides adb access by default.
Use twrp mount menu and check mount system.
Then type
adb push build.prop /system/build.prop
adb shell chmod 644 /system/build.prop
in twrp reboot system
type
adb kill-server

tobdaryl said:
We should be able to push with adb, set permissions, and reboot.
---------- Post added at 04:58 PM ---------- Previous post was at 04:36 PM ----------
place the build.prop from the zip file into the directory with fastboot.
Open terminal or cmd in the directory with fastboot.
Boot into twrp – twrp provides adb access by default.
Use twrp mount menu and check mount system.
Then type
adb push build.prop /system/build.prop
adb shell chmod 644 /system/build.prop
in twrp reboot system
type
adb kill-server
Click to expand...
Click to collapse
Ok, my Fastboot folder is currently at the root of my C drive on my PC
I entered your command and got after the first one "adb server is out of date. killing...
* daemon started successfully *
error: device not found
FYI, before I got your last post, I used Android commander to push the build.prop that I still had on my PC when I installed the custom hydro 4.1 rom.
After my reboot, I got the Asus logo, than a black screen that does nothing.
I then rebooted in Fastboot and followed your instructions.
So now, it seems that my pc doesnt see my tablet anymore when in TWRP. is this normal? Do I need to restart it after checking "Mount system"?

irepressed said:
Ok, my Fastboot folder is currently at the root of my C drive on my PC
I entered your command and got after the first one "adb server is out of date. killing...
* daemon started successfully *
error: device not found
FYI, before I got your last post, I used Android commander to push the build.prop that I still had on my PC when I installed the custom hydro 4.1 rom.
After my reboot, I got the Asus logo, than a black screen that does nothing.
I then rebooted in Fastboot and followed your instructions.
So now, it seems that my pc doesnt see my tablet anymore when in TWRP. is this normal? Do I need to restart it after checking "Mount system"?
Click to expand...
Click to collapse
Ok, I just killed my adb.exe, tried the command again and that got rid of the out of date error.
But, still stuck with the "device not found".

irepressed said:
Ok, my Fastboot folder is currently at the root of my C drive on my PC
I entered your command and got after the first one "adb server is out of date. killing...
* daemon started successfully *
error: device not found
FYI, before I got your last post, I used Android commander to push the build.prop that I still had on my PC when I installed the custom hydro 4.1 rom.
After my reboot, I got the Asus logo, than a black screen that does nothing.
I then rebooted in Fastboot and followed your instructions.
So now, it seems that my pc doesnt see my tablet anymore when in TWRP. is this normal? Do I need to restart it after checking "Mount system"?
Click to expand...
Click to collapse
Slowdown, I'm getting behind. I'm willing to help but you are now worse off than before.
Sit tight for five minutes and I'll try to give you a twrp flashable zip for your build.prop and hope that is the extent of the damage.
If not we'll try to go from there.
http://www.mediafire.com/?ybplc1ws8uvskhf
This is a twrp flashable zip that only replaces your build.prop with the one from hydro 4.1.

tobdaryl said:
Slowdown, I'm getting behind. I'm willing to help but you are now worse off than before.
Sit tight for five minutes and I'll try to give you a twrp flashable zip for your build.prop and hope that is the extent of the damage.
If not we'll try to go from there.
This is a twrp flashable zip that only replaces your build.prop with the one from hydro 4.1.
Click to expand...
Click to collapse
Alright, I'll wait for your answer before trying anything else.
So now, I've got your latest .zip file.
Still can't see my TF300T from my PC, so, ADB is a no go for now.
In fact, I do see it in the Device Manager, but since my last reboot, it now shows an exclamation mark on it as if my drivers weren't good.
Since you mentioned the file is a flashable zip, I'm guessing that I can flash it using TWRP without going through my PC?
Can you give me precise info on that, since I do not want to mess with my system more than I already did.
Thanks

irepressed said:
Alright, I'll wait for your answer before trying anything else.
So now, I've got your latest .zip file.
Still can't see my TF300T from my PC, so, ADB is a no go for now.
In fact, I do see it in the Device Manager, but since my last reboot, it now shows an exclamation mark on it as if my drivers weren't good.
Since you mentioned the file is a flashable zip, I'm guessing that I can flash it using TWRP without going through my PC?
Can you give me precise info on that, since I do not want to mess with my system more than I already did.
Thanks
Click to expand...
Click to collapse
Look at the bottom of my previous post. You will find a new link there. Just flash with twrp and reboot. Don't worry about wiping or any of that, just flash and reboot.

tobdaryl said:
Look at the bottom of my previous post. You will find a new link there. Just flash with twrp and reboot. Don't worry about wiping or any of that, just flash and reboot.
Click to expand...
Click to collapse
Yep, that's the file I was talking about.
I now need to flash and reboot, your file is at the root of an SDcard in my TF300T, I go through the Install menu and then, can't seem to view the content of my sdcard. Tried to mount it first but can't select it either, it will simply stay on "Internal Storage".
EDIT: The RCK icon is the only one right now that boots me into something. If I try the USB icon, it just stays on that screen forever.

Trash the two zips you have downloaded. I'm providing a new one for when we get back to that point. And there will be no doubt about which zip you are using.
http://www.mediafire.com/?hagehu5qu5ky6sf
OK. First I'll explain your earlier comment about adb being old. Twrp expects a recent adb or refuses to allow adb access ( we'll not worry at the moment about that but it is something you need to address later (I hope).
If you have a cord between your tablet and pc remove it. The sdcard may be mounted as data on the pc and not allow twrp to mount it.
You have been using this sdcard prior to this exercise?
Do you have any backups or flashable zips or anything of that nature on your internal sdcard?
If so what?

tobdaryl said:
Trash the two zips you have downloaded. I'm providing a new one for when we get back to that point. And there will be no doubt about which zip you are using.
OK. First I'll explain your earlier comment about adb being old. Twrp expects a recent adb or refuses to allow adb access ( we'll not worry at the moment about that but it is something you need to address later (I hope).
If you have a cord between your tablet and pc remove it. The sdcard may be mounted as data on the pc and not allow twrp to mount it.
You have been using this sdcard prior to this exercise?
Do you have any backups or flashable zips or anything of that nature on your internal sdcard?
If so what?
Click to expand...
Click to collapse
Zips trashed, kept only the one provided in your latest answer.
No cord between PC and tablet. Still unable to click on "Using external SD" or "Mount SDCard". It simply won't let me check the box or switch the bullet.
As for using this SDcard before, yes in a PC, but no, first time in my Asus. Also tried with another one just in case and same result.
As for backups and flashable zips, I kept everything from when I did my root and rom install.
I do know that I have a backup in the Restore menu of TWRP, which seems about the time I installed it. I suppose I could simply do a restore and avoid additional headaches, but my question is, what exactly will it restore? At this point, I'm mentally prepared to go back to what I had after installing Hydro 4.1, as long as I can use the tablet ASAP.

Asap = restore your backup.
If I'm restoring a different rom I'll wipe Cache, Dalvik Cache, and Factory Reset. If the backup is from the same rom I'm flashing and I want to keep the apps I have Installed since the backup I won't Factory Reset.
Good Luck!

tobdaryl said:
Asap = restore your backup.
If I'm restoring a different rom I'll wipe Cache, Dalvik Cache, and Factory Reset. If the backup is from the same rom I'm flashing and I want to keep the apps I have Installed since the backup I won't Factory Reset.
Good Luck!
Click to expand...
Click to collapse
So, I did the restore, and I'm up and running, but, no more Hydro 4.1. I guess my backup was probably what got done right before the installed it.
The good thing is, my tablet is working again and my root is still active. The bad part is that I'm gonna have to dig my head again in all the tutorials and try to find the best one.
Hey, I wanted to say a huge thank you for all your help, if it wasn't for guys like you, newbies like me would be stuck with useless thin computers.

irepressed said:
So, I did the restore, and I'm up and running, but, no more Hydro 4.1. I guess my backup was probably what got done right before the installed it.
The good thing is, my tablet is working again and my root is still active. The bad part is that I'm gonna have to dig my head again in all the tutorials and try to find the best one.
Hey, I wanted to say a huge thank you for all your help, if it wasn't for guys like you, newbies like me would be stuck with useless thin computers.
Click to expand...
Click to collapse
Great I'm glad you are happy. I had hoped for the outcome you expressed but this works also.
You're welcome!

Telsda A198

I bought a chinese phone Telsda/TSD A198 . The firmware reports it as an MT6589 CPU but the computer reports it as a spreadtrum phone. I need to root the phone to get rid of some apps on this to make space. Also without rooting is there anyway to backup the stock rom on my phone before I mess up to root? I have seen a method on XDA but that requires root. Now I am trying to backup to get to rooot !!!! Also I have also researched researchdownload but without a ROM backup and not knowing which CPU model to flash its impossible to it right. I also looked into mtkdroidtools and it tells me "unstructured rom backup not possible" , so I am guessing its a fake MTK CPU that is being reported by tweaking the firmware.
This is the link to the phone
http://www.aliexpress.com/item/New-...3-MTK6589-4-0-INCH-smart-phone/879312434.html
Any help is appreciated.
Thanks

I also interesting for this phone, but I have some doubt about the specs of this item. If you could clear some important properties for me, such as:
Does it have GPS functionality?
If not, this indirectly indicates that CPU is not MTK-based (likely Spreadtrum SC6820 if 3G functionality is absent or Spreadtrum SC8810 if it is present)
What is the real width of the phone?
It seems to me it is about 64mm, not 60.8 (as described in seller specs)
What is the RAM size?
Does it have 256 or 512MB RAM?
What is the real Andriod version?
Does it have Android 2.3.X disguised as Android 4.X.X?
I will be grateful for your response.

Villis1251 said:
I also interesting for this phone, but I have some doubt about the specs of this item. If you could clear some important properties for me, such as:
Does it have GPS functionality?
If not, this indirectly indicates that CPU is not MTK-based (likely Spreadtrum SC6820 if 3G functionality is absent or Spreadtrum SC8810 if it is present)
What is the real width of the phone?
It seems to me it is about 64mm, not 60.8 (as described in seller specs)
What is the RAM size?
Does it have 256 or 512MB RAM?
What is the real Andriod version?
Does it have Android 2.3.X disguised as Android 4.X.X?
I will be grateful for your response.
Click to expand...
Click to collapse
Ok, first my honest suggestion dont buy this phone it has pathetic performance. For the same price go for a real MTK6577 dual core. ANyways below are the answers to your question
> Real CPU frequence seems to be 1GHZ
>Mali 300 GPU
>no 3G
>no GPS
>256MB RAM and 256 MB ROM
>I am not sure if its real JB and I cant figure it out but it says JB 4.2.1 and the kernel is 2.6.35.7 and hence I guess its a fake JB. The funny part is under baseband version it says "MT6589 1.5GHZ quad cores" !!!! offcourse it means the firmware/build.prop has been tweaked and is reporting false values. Also when I ran Antutu it gives a score of about 3500 which is useless when compared to what is required to run games ..etc. I hope I have helped.

Thank you much - you helped me to avoid hasty purchase. And good luck in rooting your device.

custom recovery
Villis1251 said:
Thank you much - you helped me to avoid hasty purchase. And good luck in rooting your device.
Click to expand...
Click to collapse
Finally I was able to stitch a ROM, using bits and pieces from different sources and its perfectly working. I only need to build a CWM recovery image based on the recovery image I have attached. Can someone help me do that? so that I can do a nandroid and ump my rom in case someone needs to recover their telsda A198

I need help. I have the same smartphone. But I need it to flash. Do You have the firmware for it?

aspirus said:
I need help. I have the same smartphone. But I need it to flash. Do You have the firmware for it?
Click to expand...
Click to collapse
I have stitched firmware which works perfectly and is rooted. I also got google play store installed. Its not original firmware, the original one is supposedly 4.2.1 (I think its fake), what I have got installed is 4.0.4 if that works for you let me know.

hel me please!!!
braindia said:
I have stitched firmware which works perfectly and is rooted. I also got google play store installed. Its not original firmware, the original one is supposedly 4.2.1 (I think its fake), what I have got installed is 4.0.4 if that works for you let me know.
Click to expand...
Click to collapse
braindia hello ... I bought the same phone and I have problems with the sims do not have to call or receive coverage ..... could you explain you did and how you did it?
there say that you put android 4.0 not work quite right? ... greetings from chile

Braindia hello...I have a bad microphone works, but only when you call. So there are 2 options: trash or firmware.I need a firmware that works correctly works. So 4.2.1 or 4.0.4 for me is not important. I am new in the firmware of the phone (did the firmware only the tablet). Thankful for step by step instructions from the specialist. While I couldn't even get the root.:silly:

aspirus said:
Braindia hello...I have a bad microphone works, but only when you call. So there are 2 options: trash or firmware.I need a firmware that works correctly works. So 4.2.1 or 4.0.4 for me is not important. I am new in the firmware of the phone (did the firmware only the tablet). Thankful for step by step instructions from the specialist. While I couldn't even get the root.:silly:
Click to expand...
Click to collapse
ok looks like lot of people have issues with this phone. Its a junk phone, all fake stuff on it. ANyways I will upload the firmware images and then you guys can use those to flash on your phones. Below is what I have done
1> Patched a 4.0.4 ROM which works perfectly
2>Removed useless preinstalled apps
3>rooted
4>Perfectly working dual sim,GPRS,WIFI,Camera,Camcorder .,..etc etc
4>The issue is with the IMEI, because of the way its stored you guys will need to use your own NV files.
The only thing I havent been able to do is get a working CWM, but you dont need it as you can flash the firmware images using researchdownload.

Braindia, you even pierced smartphone using researchdownload? Maybe I need a USB driver or researchdownload? What have you used? I can't understand how to enable the firmware on this phone: food & + -test menu; food & - picture with your phone and the triangle, but windows does not find the device driver.

working firmware files
aspirus said:
Braindia, you even pierced smartphone using researchdownload? Maybe I need a USB driver or researchdownload? What have you used? I can't understand how to enable the firmware on this phone: food & + -test menu; food & - picture with your phone and the triangle, but windows does not find the device driver.
Click to expand...
Click to collapse
Here you go, you flash at your own risk. If there are bricks/issues you are responsible for your own device.(Standard disclaimer) . I have uploaded all the files except system and NV, system image is kind of big and I am trying to figure it out where to upload it.. You dont need to worry about NV unless you completely erased the flash(never erase the complete flash or format it). If you havent done so then you are good to go.
Please google to find researchdownload and use it to flash the attached files. I wont be able to write the tutorial on using researchdownload so google is your friend.
I have also uploaded the gapps zip which will get you up and running with google play store. You need root to copy these files directly into system/apps folder.
I will be able to upload a system file which works, not the patched one with google play store, root ...etc etc . You do that on your own, I will help you do it.
Thanks !

Tutorial researchdownload not needed. I installed the USB driver and researchdownload. When the phone is loaded, I can connect it to your computer . BUT when I try to flash the phone with the help of researchdownload I need to enable firmware on your phone. In the mode of firmware (if I understand it correctly) phone is not detected by Windows. I wanted to know what USB drivers and version researchdownload used you, and as included mode firmware on your phone.
I have the original firmware.

aspirus said:
Tutorial researchdownload not needed. I installed the USB driver and researchdownload. When the phone is loaded, I can connect it to your computer . BUT when I try to flash the phone with the help of researchdownload I need to enable firmware on your phone. In the mode of firmware (if I understand it correctly) phone is not detected by Windows. I wanted to know what USB drivers and version researchdownload used you, and as included mode firmware on your phone.
I have the original firmware.
Click to expand...
Click to collapse
your phone is probably not detected due to 2 reasons
1> windows disabling non signed driver.. if thats the issue while you start the PC keep hitting F8 you will be shown various options
Select disable windows driver signature enforcement
2> Second reason is you need to add an entry in adb_usb.ini file I think its 0x1782 which is for SPRD enumerator. There are tons of links for this one of which is
http://forum.xda-developers.com/showthread.php?p=37271476

Possible causes checked. NO 1 and NO 2 Everything correctly, but still not working.To go the other way, I've tried about 10 of options to get the root, but the result is zero. You got root?

aspirus said:
Possible causes checked. NO 1 and NO 2 Everything correctly, but still not working.To go the other way, I've tried about 10 of options to get the root, but the result is zero. You got root?
Click to expand...
Click to collapse
getting root is simple, flash a CWM I have attached one, please note this does not work but it works enough to get you root. follow the below steps
1> Flash attached recovery
2> boot into recovery ... this will not show the normal CWM options but dont worry just connect to your pc
3> run ADB shell, you will be automatically in root mode
4> perform mount /system and then exit shell
5> push su binary & busybox directly to /system/bin (from the command prompt using adb push)
6>change permissions for su & busybox to make them runnable
7> exit from the shell and reboot
8> do adb install superuser.apk(optional this can be done later)
thats it you have su, and then you can sideload the superuser apk or you can do step 8 as above. Once you have rebooted and verified that you indeed have superuser you can flash the stock recovery back on the phone.
Note note note : The CWM recovery image is only for you to get root and it doesnt work and doesnt show the normal CWM options... you have been warned. You should flash your old recovery/stock recovery after you have achieved root.
Also can you give me the stock recovery image so that I can build a working CWM out of it. I overwrote mine and now stuck with another recovery which works but is not for this phone.
Thanks

:cyclops:
1> Flash attached recovery
2> boot into recovery ... this will not show the normal CWM options but dont worry just connect to your pc
3> run ADB shell, you will be automatically in root mode
error:device not fround
TADAN
I have a magic smartphone. In recovery he annihilated.

aspirus said:
:cyclops:
1> Flash attached recovery
2> boot into recovery ... this will not show the normal CWM options but dont worry just connect to your pc
3> run ADB shell, you will be automatically in root mode
error:device not fround
TADAN
I have a magic smartphone. In recovery he annihilated.
Click to expand...
Click to collapse
Hmm... I am not sure what is the issue please try attached drivers and pray that they work . use either 64bit or 32bit depending on your OS.
Also you said you have the firmware can you upload it ? I can do something more with the stock/original firmware, so please upload it

I installed a different driver for windowsXP and windows7, but the result is the same. Too much time for 54$. I buried this smartphone. So good luck to you on the path to custom firmware. One month firmware will be available my personal archive: http://files.mail.ru/A9FBE04381094135959559784E5F49A4

aspirus said:
I installed a different driver for windowsXP and windows7, but the result is the same. Too much time for 54$. I buried this smartphone. So good luck to you on the path to custom firmware. One month firmware will be available my personal archive: http://files.mail.ru/A9FBE04381094135959559784E5F49A4
Click to expand...
Click to collapse
Thanks ... I know this phone is a waste of time and money both. I am just using this phone as an experiment platform knowing fully well that this piece of junk will die anytime.

[Q] Need help! on accessing android root system on PC

Hi Guys
I wonder if there's anyway to access android root system folder on Windows PC? where the build.prop file is? well the reason is i pretty much screw my build.prop by editing it with a line to remove the soft button on screens. And now my tablet is showing nothing but i can still get it connected through USB.

how about use root explorer and copy the file u want to sd card..then connect sd card to pc..and change whatever u want there..:laugh:

dukesinclair said:
how about use root explorer and copy the file u want to sd card..then connect sd card to pc..and change whatever u want there..:laugh:
Click to expand...
Click to collapse
I think you don't understand what i am trying to say, I meant i can't access my Galaxy Tab now since it's all blank and it is not displaying anything. the reason why it's not displaying anything is because i wanted to remove those on screens buttons and i found out that people said here by adding this script at build.prop qemu.hw.mainkeys=1 and reboot it will remove them. But instead all i get is a blank screen
I wonder if there's a way to access Android root system dir on Windows PC you know the place where you can find the build.prop file.
Can someone help me with this?

Is it rooted??
If it is you could reflash ur Rom without wiping anything. Just flash the same Rom u are currently using and don't wipe anything. When done dix permissions and reboot.
Sent from my HTC Glacier using Tapatalk 2

mickeyasamoah said:
Is it rooted??
If it is you could reflash ur Rom without wiping anything. Just flash the same Rom u are currently using and don't wipe anything. When done dix permissions and reboot.
Sent from my HTC Glacier using Tapatalk 2
Click to expand...
Click to collapse
Yes my Galaxy Tab is rooted with a custom rom installed. i can still access my CWM. Ugh.. i really wonder if it's possible to access the android root system on a PC or not.
I'm not going to reflash it if i could just remove that line i added earlier at build.prop. which is qemu.hw.mainkeys=1 i am hoping that after removing that line might return everything to normal

dc2mx said:
Yes my Galaxy Tab is rooted with a custom rom installed. i can still access my CWM. Ugh.. i really wonder if it's possible to access the android root system on a PC or not.
I'm not going to reflash it if i could just remove that line i added earlier at build.prop. which is qemu.hw.mainkeys=1 i am hoping that after removing that line might return everything to normal
Click to expand...
Click to collapse
Hello bro ... you can access the android root files ( but not view directly as a file manager) and edit the build prop ..... but for this you need android sdk ( android development kit ) on pc through which you can type the adb shell commands for the build prop changes you made... but it still needs usb debugging to be activated...... If you can flash stock rom it is better ...
HIT THANKS IF I HELPED
Sent From My GT-I9082

asifcheer said:
Hello bro ... you can access the android root files ( but not view directly as a file manager) and edit the build prop ..... but for this you need android sdk ( android development kit ) on pc through which you can type the adb shell commands for the build prop changes you made... but it still needs usb debugging to be activated...... If you can flash stock rom it is better ...
HIT THANKS IF I HELPED
Sent From My GT-I9082
Click to expand...
Click to collapse
Hello
I can still access my Tablet through USB mode using CWM to set it on. I wonder if i can see the android root system dir when using android SDK? or i am screwed ? Does the Android SDK really need USB Debug Mode turn on to make changes to the build.prop file? If yes, i wonder is there a way to turn USB Debug mode on at SDK?
Since my tablet is not displaying anything so i can't manually turn it on there.

dc2mx said:
Hello
I can still access my Tablet through USB mode using CWM to set it on. I wonder if i can see the android root system dir when using android SDK? or i am screwed ? Does the Android SDK really need USB Debug Mode turn on to make changes to the build.prop file? If yes, i wonder is there a way to turn USB Debug mode on at SDK?
Since my tablet is not displaying anything so i can't manually turn it on there.
Click to expand...
Click to collapse
Hey... try this link ... it mentions about the kind of software you need ...
http://forum.xda-developers.com/showthread.php?t=1587717
But It would be useless if it asks for root permission on your phone ( as you can't access your screen)
HIT THANKS IF I HELPED
Sent From My GT-I9082

asifcheer said:
Hey... try this link ... it mentions about the kind of software you need ...
http://forum.xda-developers.com/showthread.php?t=1587717
But It would be useless if it asks for root permission on your phone ( as you can't access your screen)
HIT THANKS IF I HELPED
Sent From My GT-I9082
Click to expand...
Click to collapse
Flash the stock build prop back from recovery first..
and reboot.
or
connect the device flash the stock kernel..

You need spend some money to buy one software to slove this problem.

Ebmmki said:
Root android phone ,you will lost all data ,files,apps on android phone
Click to expand...
Click to collapse
Wrong. You don't lose anything rooting unless you use some nonsense.
It's unlocking the bootloader that wipes the phone.
Please learn what you are talking about before posting.

[Q] NEC Medias W N-05E root? (dual screen phone)

Hi!
Is there a root available or in the works for the dual-screen NEC Medias W N-05E?
The question has been asked (no answer so far) at the end of a thread under the N-05D but that's a quite different model.
I'd like to create a separate thread for this model to give it more visibility. Hope that's ok!
Thanks in advance!

bohemianRhapsody said:
Hi!
Is there a root available or in the works for the dual-screen NEC Medias W N-05E?
The question has been asked (no answer so far) at the end of a thread under the N-05D but that's a quite different model.
I'd like to create a separate thread for this model to give it more visibility. Hope that's ok!
Thanks in advance!
Click to expand...
Click to collapse
OK! I've made some progress on this: the japanese blogger "dupondroid" appears to say that run_root_shell (hosted at github)
successfully gives temp root. At least, that's my necessarily blurry understanding via google translate. Would any japanese readers here be able to post a better translation?
And a thread at r-2ch dot com links to the github commit in run_root_shell which made that possible: it's commit ID 811be8639aed64c158798a72a1d520a4d21e8b8b "Support N-05E"
Code:
+ { "N-05E", "A1000311", 0xc0094430, 0xc0093ebc }
So it definitely seems temp root is possible.
Sorry for the lack of links but I'm a new user so can't add them for now.

root is easy
bohemianRhapsody said:
OK! I've made some progress on this: the japanese blogger "dupondroid" appears to say that run_root_shell (hosted at github)
successfully gives temp root. At least, that's my necessarily blurry understanding via google translate. Would any japanese readers here be able to post a better translation?
And a thread at r-2ch dot com links to the github commit in run_root_shell which made that possible: it's commit ID 811be8639aed64c158798a72a1d520a4d21e8b8b "Support N-05E"
Code:
+ { "N-05E", "A1000311", 0xc0094430, 0xc0093ebc }
So it definitely seems temp root is possible.
Sorry for the lack of links but I'm a new user so can't add them for now.
Click to expand...
Click to collapse
root is easy via a tool called impactor.
however it's only temporary, I couldn't get /system mounted for rw. so I made a new recovery image to push.
that didn't work either, although I cannot write to recovery there is no error. recoverybkp was successful.
Also I found that the code to enter in recovery mode is based on your imei.
If I remember correctly digit 2,12,13,14 of your imei.
So possible attack vectors are:
1) kernel module to unlock partitions
2) figure out how update.dat files are constructed.
3) write to recovery partition

it0 said:
root is easy via a tool called impactor.
however it's only temporary, I couldn't get /system mounted for rw. so I made a new recovery image to push.
that didn't work either, although I cannot write to recovery there is no error. recoverybkp was successful.
Also I found that the code to enter in recovery mode is based on your imei.
If I remember correctly digit 2,12,13,14 of your imei.
So possible attack vectors are:
1) kernel module to unlock partitions
2) figure out how update.dat files are constructed.
3) write to recovery partition
Click to expand...
Click to collapse
I can't seem to get anything to work i'v tried Impactor did not work just gave me errors also tried run_root_shell but had to have some device.db file with I didn't really figured out, could some one please help?

Lukas_a_1996 said:
I can't seem to get anything to work i'v tried Impactor did not work just gave me errors also tried run_root_shell but had to have some device.db file with I didn't really figured out, could some one please help?
Click to expand...
Click to collapse
I used impactor 0.9.14, you just hook up the phone using microusb and put the phone in usb debugging mode under development options. then selecct "# start telnetd as root on port 22" from the pulldown and click start.
Then using a tool like putty ,telnet to your phone on port 22 (make sure it's connected to you wifi network when you do).
What android version are you running ? 4.1.2 is vulnarable for this attack.

it0 said:
I used impactor 0.9.14, you just hook up the phone using microusb and put the phone in usb debugging mode under development options. then selecct "# start telnetd as root on port 22" from the pulldown and click start.
Then using a tool like putty ,telnet to your phone on port 22 (make sure it's connected to you wifi network when you do).
What android version are you running ? 4.1.2 is vulnarable for this attack.
Click to expand...
Click to collapse
Thanks for the reply . I tried to run the command in impactor but whatever i do i get "Signature bugs unavailable" could it be that i have the wrong ADB drivers installed or is my Impactor setup wrong?
Edit: yeah im running 4.1.2 Build A1001231

You could try if you can just get an adb connection working.
with commands like
adb devices
adb shell
If that works then the rest should work as well.

it0 said:
You could try if you can just get an adb connection working.
with commands like
adb devices
adb shell
If that works then the rest should work as well.
Click to expand...
Click to collapse
All the adb commands basically work but nothing works with impactor i just get error

it0 said:
You could try if you can just get an adb connection working.
with commands like
adb devices
adb shell
If that works then the rest should work as well.
Click to expand...
Click to collapse
Bump!

How to Root Medias N05e
Dear All Pro
Does anyone show me how to root N05e? because there is very few information about that. I want to Swapfile to increase Ram size but it required N05e must be rooted.
So if anyone have any information about N05e, please share. Thanks

nguyenbuulam said:
Dear All Pro
Does anyone show me how to root N05e? because there is very few information about that. I want to Swapfile to increase Ram size but it required N05e must be rooted.
So if anyone have any information about N05e, please share. Thanks
Click to expand...
Click to collapse
There is a way for temp root N05E, basically u can use pm disable command or other su stuff. But u cannot mount system rw right now.

Some news about rooting
If someone in doubt, temp root is 100% working with run_root_shell https://github.com/android-rooting-tools/android_run_root_shell
With this I was able to copy full system, boot and recovery image. But I can't push new boot or recovery.
More than that, almost all fuctions in standard recovery mode (available through "reboot recovery" in root shell) are protected with some code. And it's not 2,11,12,13 numbers of IMEI.
Anyone know where to get this code? Or how to write new boot, recovery image? If we do so, we can get permanent root access =)
Maybe someone have Japanese friends? Search all English web, but maybe in Japan web there are some info.
P.S. with Impactor you only can start talnetd from root, becouse Impactor can't remount /system in rw mode and ro.kernel.qemu=1 option is not working

How to enter recovery mode?
Despite starting this thread, in the end I never did bother to attempt rooting.
Anyway, unfortunately now the phone refuses to boot. Not triggered by anything obvious, haven't installed any new software recently, etc. Just hung one day and then when I removed and re-inserted the battery, it won't get any further than the "docomo" splash screen. I.e. the OS doesn't appear to be getting bootstrapped at all. The "docomo" splash screen appears and disappears then the phone sits there with both screens powered up but blank.
As it happens, I had ADB Debug enabled in the developer options at the time, so I've tried to see if I can adb shell into the device, but no luck. Not surprised as it's clearly not getting far enough into the boot for that to work.
Any other suggestions? From the way it happened I do suspect it might just be hardware failure....
Not even sure how I enter recovery mode -- what are the key combinations for this?

bohemianRhapsody said:
Despite starting this thread, in the end I never did bother to attempt rooting.
Any other suggestions? From the way it happened I do suspect it might just be hardware failure....
Not even sure how I enter recovery mode -- what are the key combinations for this?
Click to expand...
Click to collapse
In recovery mode, clear cache, etc..
To get there hold volume down and power at the same time,then you'll see the broken android then wait/ press vol down a couple of times to see the menu.

GRbit said:
Some news about rooting
If someone in doubt, temp root is 100% working with run_root_shell https://github.com/android-rooting-tools/android_run_root_shell
With this I was able to copy full system, boot and recovery image. But I can't push new boot or recovery.
More than that, almost all fuctions in standard recovery mode (available through "reboot recovery" in root shell) are protected with some code. And it's not 2,11,12,13 numbers of IMEI.
Anyone know where to get this code? Or how to write new boot, recovery image? If we do so, we can get permanent root access =)
Maybe someone have Japanese friends? Search all English web, but maybe in Japan web there are some info.
P.S. with Impactor you only can start talnetd from root, becouse Impactor can't remount /system in rw mode and ro.kernel.qemu=1 option is not working
Click to expand...
Click to collapse
did you ever figure out the recovery keys?

hamishhhhs said:
did you ever figure out the recovery keys?
Click to expand...
Click to collapse
No I didn't(
I'm actually sold this phone and lost interest in the topic.

GRbit said:
No I didn't(
I'm actually sold this phone and lost interest in the topic.
Click to expand...
Click to collapse
do you by chance still have the files you dumped?
Ive teamed with a friend in twitter to try and make a rom for this but I haven't gotten very far

hamishhhhs said:
do you by chance still have the files you dumped?
Ive teamed with a friend in twitter to try and make a rom for this but I haven't gotten very far
Click to expand...
Click to collapse
Sorry, but this was too long time ago. Nothing left

GRbit said:
Sorry, but this was too long time ago. Nothing left
Click to expand...
Click to collapse
how would j be able to get the files from my phone?

hamishhhhs said:
how would j be able to get the files from my phone?
Click to expand...
Click to collapse
I dunno man.
I've already described (in the first post you have quoted) what I achieved with this github repo https://github.com/android-rooting-tools/android_run_root_shell . That's all I've got.