Database Develop

Need help with METROPCS FLASH. Talk Text and Web but...

Hey guys I basically did everything that the Cricket how to said, but with the Metropcs logins and passwords. I have flashed several phones before, but not an Android OS. The phone works with internet and picture text coming in, but the apps. like Youtube and Google maps will only work on WIFI and not on the network and MMS out will also not work.
My assumption is that it has to do with this whole autostart file thing. I am so new to this programming stuff that I am not sure what to do when it comes to this.
So I used QPST and CDMAW to program the back end so that is probably why the Internet works. APN and Proxy settings are all correct, but here is the only place I have an error.
These are the directions:
Before starting the next step make sure you have the u2nl file and autostart.sh in this folder c:/android/tools
"Now go to the command prompt on your pc and type the following commands:
cd c:\android\tools
adb remount
adb push c:\android\tools\u2nl /system/bin/u2nl
adb push c:\ android\tools\autostart.sh /data/opt/autostart.sh
Now:
adb shell
chmod 0755 /system/bin/u2nl
chmod 0755 /data/opt/autostart.sh
reboot"
My error begins when I type the adb remount.... it states unable to find device or something like that.
I plugged phone to computer not in Diag mode or any mode, just turned it off then back on and plugged it in. Is there a setting on the phone I need to check?
Then I go ahead and do those push commands just for the hell of it, it just scrolls through this whole display of things.. not sure what its doing.
The adb shell part works and so do those other commands after....
When I am done with the last line that has the autostart.sh and hit enter...
The phone doesn't reboot, I just unplug and then turn off and then back on. I would have thought there would be a script to reboot phone or something...
So what am I missing or is it not even possible to get Google maps and youtube to work on Metroweb... has to be on wifi??? I have seen people say they have done it...
Any help would be appreciated..

[Q] Android stock messaging app

Has anyone pulled an apk for the stock messaging app and tried running it on an x8? x8 stock app drives me mad, I've been using go which is a bit of an improvement, but nothing beats the stock! (having been using it on my G2).

Do you have a screenshot how it looks?
Sent from my E15i using XDA App

why don't you try handcent sms?it's great

If you check out any screen shots from cyanogen mod site thats the stock.
And I used hand cent for a while, found it horrible and I hate the ads... Not willing to pay for a messaging app! Using go messager at the moment which is much better then hand cent
Sent from my E15i using XDA App

please rename this thread.. add [FOUNDED] or [SOLVED]
Cheers.

But its not solved, handcent and go sms aren't the stock android messaging app?

Here You go! The file's attached. I recommend it to install it with ADB. You may also use (I think) something like Root Explorer, which I don't use, because it is a paid app Here I present you a free way to do it.
How to do it? Here (I'm assuming you use Windows):
1) First make sure You install Your phone's USB drivers in your system
2) Download Android's SDK:
http://developer.android.com/sdk/index.html
3) Don't really remember how it went after Installation, but you should have an "android-sdk-windows" folder (assuming you use Windows). Put it on your Desktop.
4) Enable USB Debugging in your phone (Under Applicaions -> Development in Settings). Then connect your phone to PC via USB
5) Do a WinKey+R combo. "Run" window should appear. Type
Code:
cmd
and hit Enter.
6) A black console should appear. Type:
Code:
cd Desktop
cd android-sdk-windows
cd platform-tools
dir
you should be able to do a bunch of files, including adb.exe. If you don't, you either messed up folder names or didn't put android sdk folder in your Desktop.
7) Now (in normal Windows Explorer) move Mms.apk to your platform-tools folder inside android-sdk-windows.
8) Now, in console do:
Code:
adb start-server
adb remount (if at this point it says "no device found" you either screwed up your phone's USB drivers, or USB connection, or something else, no idea)
adb shell
9) Now type:
Code:
cd /system/app
cp Mms.apk Mms.apk.bak (to backup your current messaging app, in case something goes wrong, you just do the opposite - cp Mms.apk.bak Mms.apk)
exit
10) Now type:
Code:
adb push Mms.apk /system/app/Mms.apk (should say it's fine)
adb kill-server
Remove your phone from USB, reboot it. Should be done just fine.

Can anyone conform the above method works...

[Q] Stuck at "Touch Android To Begin" after reboot

I rooted my DS7 and changed the "phone.apk" name, and I couldn't get past "Force Close" message, so I reset (Vol+ + Power?).
I got the option of "0. Boot", "1. Wipe"..., and selected 1.
Rebooted and was stuck at "Touch Android To Begin" - Android turns white, but does not move forward.
I reset and selected a different option of complete wipe of internal and personal data.
Rebooted and am still stuck at "Touch Android To Begin".
Any suggestions?
I have 2 SD7's, so do I need to back up a ROM off the good one and reflash the stuck one? If so, how would I do that?

Change the name of phone.apk back and see if that helps. You ought to change phone.apk, get a bunch of force closes, and then be able to restart and have it work OK. If you restarted and still had issues, then I'm not sure why that would be (unless you didn't also change telephonyprovider.apk).

Z4nd4r said:
Change the name of phone.apk back and see if that helps. You ought to change phone.apk, get a bunch of force closes, and then be able to restart and have it work OK. If you restarted and still had issues, then I'm not sure why that would be (unless you didn't also change telephonyprovider.apk).
Click to expand...
Click to collapse
I never got a chance to change telephonyprovider.apk . After changing phone.apk, I kept getting force close messages without a chance to do anything...reboot, shut down, etc., so I just reset and did a "wipe"/restore...or at least I thought it was a restore to factory. Maybe I should have waited and tried the reboot first.
Anyways, I'm stuck now. If I cannot get past the Android, how would I even change the file name back to phone.apk ? Also, shouldn't a wipe/restore/clear cache have changed all of that...by replacing all files/kernal/rom to factory?

S4F4M said:
I never got a chance to change telephonyprovider.apk . After changing phone.apk, I kept getting force close messages without a chance to do anything...reboot, shut down, etc., so I just reset and did a "wipe"/restore...or at least I thought it was a restore to factory. Maybe I should have waited and tried the reboot first.
Anyways, I'm stuck now. If I cannot get past the Android, how would I even change the file name back to phone.apk ? Also, shouldn't a wipe/restore have changed all of that...by replacing all files/kernal/rom to factory?
Click to expand...
Click to collapse
Wipe/restore, if I understand it correctly, only wipes out cache and data; basically, all of your personal information and files for apps and such (not your SD card). This leaves the kernel as it was.
Do you have CWR on there? If so, simply install a new ROM. If not, you can flash it on there via ADB, I think (check the CWR thread).
Your other option is to change the file name via ADB, or push a new one to it. I've uploaded the stock Phone.apk here:
http://www.megaupload.com/?d=EEBPHB4H
You can push it by doing
Code:
adb push Phone.apk /system/app
I think there's an adb command to simply rename, but I don't recall what it is. Once you do this, you ought to be good to go. Get signed in, then change/move both the apps and restart. It might be annoying with the force closes; not sure if you'll have to use the pinhole reset.
Good luck!

Thanks, Z4nd4r! I'll give it a whirl.

I just moved/deleted the files to test it out (and run some battery tests). I had the force close issue to the point that I couldn't do anything, so I used the pinhole reset. Booted up fine and no cell signal, just as it ought to.

What Z4nd4r recommended worked.
1. Had to install ADB and drivers.
2. Had to point Command Prompt to drivers
- Go to the Windows "Control Panel".
- Click on "System".
- Click on "Advanced system settings" in the left column of the window you're in.
- Find the button called "Environment Variables" in the window that opens (it's at the bottom on the first tab).
- Scroll down in the "System variables" box until you find "Path".
- Select "Path" and click the "Edit" button.
- At the very beginning of the input field called "Variable value" enter where the ADB drivers were located.
For example: "C:\program files\android-sdk\platform-tools;" (without the quotes).
NOTE: Do not remove any of the other paths, and make sure you have a semi colon at the end of the new path you're adding.
- OK/APPLY > EXIT
3. Root tablet with SuperOneClick.
4. Mounted /system directory as Read/Write (have to use the appropriate /dev/block device path. I found it by typing the following
# adb shell
# su
# cat /proc/mounts
# mount -o rw,remount -t yaffs2 /dev/block/**** /system
where **** is the appropriate device path from the list generated by cat /proc/mounts
5. Making sure that the ADB file was in the same folder as the phone.apk, push apk to /system/app:
adb push Phone.apk /system/app
Yes, it was a pain, but I figured it all out.

S4F4M said:
What Z4nd4r recommended worked.
1. Had to install ADB and drivers.
2. Had to point Command Prompt to drivers
- Go to the Windows "Control Panel".
- Click on "System".
- Click on "Advanced system settings" in the left column of the window you're in.
- Find the button called "Environment Variables" in the window that opens (it's at the bottom on the first tab).
- Scroll down in the "System variables" box until you find "Path".
- Select "Path" and click the "Edit" button.
- At the very beginning of the input field called "Variable value" enter where the ADB drivers were located.
For example: "C:\program files\android-sdk\platform-tools;" (without the quotes).
NOTE: Do not remove any of the other paths, and make sure you have a semi colon at the end of the new path you're adding.
- OK/APPLY > EXIT
3. Root tablet with SuperOneClick.
4. Mounted /system directory as Read/Write (have to use the appropriate /dev/block device path. I found it by typing the following
# adb shell
# su
# cat /proc/mounts
# mount -o rw,remount -t yaffs2 /dev/block/**** /system
where **** is the appropriate device path from the list generated by cat /proc/mounts
5. Making sure that the ADB file was in the same folder as the phone.apk, push apk to /system/app:
adb push Phone.apk /system/app
Yes, it was a pain, but I figured it all out.
Click to expand...
Click to collapse
Glad to hear it worked!
Are you going to brave removing the files, again? You know you want to!

Z4nd4r said:
Glad to hear it worked!
Are you going to brave removing the files, again? You know you want to!
Click to expand...
Click to collapse
Oh, I did. What was left out of the procedure I found was the mention of continuous FORCE CLOSE and the use of the pin reset.
I will write up detailed instructions for a new thread in case anyone else wanted to know.

I know this is a really old thread, but I am stuck on this as well in the same situation that the OP had. However, SuperOneClick 2.2 and 1.55 both seem unable to root the streak so I can use the adb server to push the proper apk back! Anyone have any advice? I need to rename or push both TelephonyProvider.apk *and* Phone.apk. I have tried using adb and of course it errors since the device is unrooted.

turn device vertical.
start upper right touch
lower right touch
lower left touch
upper left touch

[Q] No usb connect?

Had to factory reset kfhd7 and when I did, it booted up like an android phone. ... Now there's no browser and I can't get play to work. Usb debug is enabled but when I connect to the computer to try and push a browser, my computer doesn't recognize it. I have all the newest drivers installed and just about every program that I can think of (adb, sdk, jdk) What I don't have is a fastboot cable. Any ideas?
Missing my kindle
Edit* So I do have chrome installed but when I open it, I get an error message saying "critical functionality required to run chrome is missing; either your chrome installation is incomplete, or not compatible with this version of android"
Terminal emulator installed too but when I try to open it I get a "terminal emulator has stopped" error.
Super SU installed, works.
No es file explorer
edit#2
Ok, so I decided to open cmd just to see if I can recognize my device.... and it did! So how can I fix my kindle if adb is connecting?
Edit#3 adb devices shoes device but when running a command, it says "device offline"....
Edit#4 plugged usb into another port and reloaded drivers = adb connects, device is online. I have tested by pushing an app to the sdcard. My goal now is to be able to push es file explorer to /system/app/ .... or ..... /data/app/ ...... or where ever it will become active for use. (you know what I mean?) I don't know how to change the permissions via adb and push to system folder. I believe I have successfully pushed es file explorer to the /sdcard/ but I have no idea where to go next.
Now what..... ?

How to Install Packages using adb install
Krsmqn said:
Had to factory reset kfhd7 and when I did, it booted up like an android phone. ... Now there's no browser and I can't get play to work. Usb debug is enabled but when I connect to the computer to try and push a browser, my computer doesn't recognize it. I have all the newest drivers installed and just about every program that I can think of (adb, sdk, jdk) What I don't have is a fastboot cable. Any ideas?
Missing my kindle
Edit* So I do have chrome installed but when I open it, I get an error message saying "critical functionality required to run chrome is missing; either your chrome installation is incomplete, or not compatible with this version of android"
Terminal emulator installed too but when I try to open it I get a "terminal emulator has stopped" error.
Super SU installed, works.
No es file explorer
edit#2
Ok, so I decided to open cmd just to see if I can recognize my device.... and it did! So how can I fix my kindle if adb is connecting?
Edit#3 adb devices shoes device but when running a command, it says "device offline"....
Edit#4 plugged usb into another port and reloaded drivers = adb connects, device is online. I have tested by pushing an app to the sdcard. My goal now is to be able to push es file explorer to /system/app/ .... or ..... /data/app/ ...... or where ever it will become active for use. (you know what I mean?) I don't know how to change the permissions via adb and push to system folder. I believe I have successfully pushed es file explorer to the /sdcard/ but I have no idea where to go next.
Now what..... ?
Click to expand...
Click to collapse
Krsmqn,
Sorry for the delayed response, we have been real busy the last few days. You may use the
following command to install or reinstall software on the Kindle:
Code:
adb kill-server
adb start-server
adb devices
android update adb
If adb is working move on to install software:
Code:
adb install package-whatever.apk
You need to make sure the .apk software package in in the same directory as adb. If
you can not get the Kindle stable you may need a USB Factory Cable, you may order
one from XDA User SkOrPn just send him a PM with the subject Factory Cable Info Please,
include your ship to country and number of cabled needed. He will respond with a PayPal
Invoice. The cable is about $15 USD and is worth every penny since it allows quick
recovery of your Kindle.

prokennexusa,
I want to thank you for all your help. Unfortunately, my issue was kind of a rare issue. I had deleted some amazon apps that were system apps. I tried your solution time and time again to no avail. I was stumped until I remembered a thread I saw in development.
http://forum.xda-developers.com/showthread.php?t=1886189
I was able to download and unzip the 7.2.3 update version and simply install the apks that I was missing. Then, as far as google play went, I just went into System>Applications>Installed Applications>Appstore (Amazon)> Force stop, clear data & cache. Reinstalled Vendor.apk and then updated. Viola!
The USB notification came back, as well as all the other options in settings. Problem solved. Hope this helps future users.

Follow Up - Feedback
Krsmqn said:
prokennexusa,
I want to thank you for all your help. Unfortunately, my issue was kind of a rare issue. I had deleted some amazon apps that were system apps. I tried your solution time and time again to no avail. I was stumped until I remembered a thread I saw in development.
http://forum.xda-developers.com/showthread.php?t=1886189
I was able to download and unzip the 7.2.3 update version and simply install the apks that I was missing. Then, as far as google play went, I just went into System>Applications>Installed Applications>Appstore (Amazon)> Force stop, clear data & cache. Reinstalled Vendor.apk and then updated. Viola!
The USB notification came back, as well as all the other options in settings. Problem solved. Hope this helps future users.
Click to expand...
Click to collapse
Krsmqn,
Great post Krsmqn, I am glad to hear your problems are solved! We offer a fresh copy of the /system/app
folder here: https://dl.dropbox.com/u/54456659/app.zip
Anyone who is experiencing odd issues can download this folder and side load it back to the Kindle through
adb or ES File Explorer. Thank you again, I was getting a bit worried.

Broken Screen, Not Rooted, Lockscreened.

SOLVED
(No success for me personally, but I'd still like to explain how I realised there's no hope left - description is at the bottom of this post)
Hi, not a regular poster in the S3 mini section, but a friend of mine has had his entire screen smashed. Somehow though, the phone is still breathing and can be turned on/off.
The problem is: My friend has asked me to extract his photos and similar media from the device's memory.
The device isn't rooted and I'm not sure if there's a default recovery mode or something like that built in the device.
I've tried connecting the device to my PC and it gets recognized and the drivers install themselves, but the device is empty. Moreover, I've downloaded KIES which also recognized the device, but says that there's a lockscreen and he can't go any further.
Any advices? Most of the other xda answers are for rooted phones so they haven't been very helpful, unfortunately.
There's a picture of the device in the attachments below, and KIES interface aswell.
<<EDIT>>
I'm using this http://forum.xda-developers.com/showthread.php?t=2339530 Recovery operation but it keeps saying "adb.exe" not found. I've installed ADB via the 15sec install ( http://forum.xda-developers.com/showthread.php?t=2588979 ) and entered the path correctly, but it still can't detect it. Any tips? perhaps i'm using the wrong ADB - I don't have c:\android\platform-tools folder - it's simply c:\adb\adb.exe.
SOLVED PROBLEM:
After messing with this for 2-3 days, I've decided to go with the simplest method - find a way to list all directories on the device and then see if there's anything in "sdcard" or a similar folder. To do this, after ADB recognizes your device, type : adb shell ls -R
adb shell ls -R will list a zillion directories so you may want to save the data into a .txt file. to do this, type adb shell ls -R > output.txt (or any other name).
After that, open the output.txt file and then use ctrl-f to find the sdcard folders and check if there's any data left in them.
IMPORTANT:
I've read that, without root permission, one cannot access the data or sdcard directories. The device I was working on had USB debugging OFF so there was no way I could root the phone in order to access the data directories.

Silly question, but did you use option 2 in RecoverData to change the path of ADB to c:\adb\?

aumedina said:
Silly question, but did you use option 2 in RecoverData to change the path of ADB to c:\adb\?
Click to expand...
Click to collapse
Yup, but it still can't find it. That's why I think the ADB-15sec install might be flawed.
There's a screencap of the Recovery + TotalCMD in the background in the attachments.
<EDIT>
Alright so I've followed an ADB tutorial (http://forum.xda-developers.com/showthread.php?t=2266638), installed all the SDK packages just to be sure.
ADB now recognizes the device after I've booted it into recovery mode. I've tried doing adb pull /data and it says 0 files pulled, 0 files skipped. Does this mean the device's internal memory is blank? No it doesn't, only the folder "data" is blank, other system data is present.
<EDIT 2> Can anyone please tell me the path to the internal camera storage folder? I may have fixed the problem if only I knew the correct path. SOLVED: The correct path is one of 4 combinations, usually these: /mnt/sdcard0/ /mnt/sdcard/ /storage/sdcard0/ /storage/sdcard/