[Q] Changed build.prop, Broke TwLauncher - Samsung Infuse 4G

Hi all,
I rooted my phone, and changed the LCD density in /system/build.prop. I then hard reset the phone. Now, I have an unrooted phone with a broken TwLauncher, and ADB Debugging is off. I am able to get a shell via recovery mode, but I don't have root. How can I change the /system/build.prop back? Or how can I get root, now? The SuperOneClick method does not seem to be working while in recovery mode. Or what can I do to get a half working phone? I can't even install APKs at this point (via recovery adb.)
Thanks for any ideas!

Through a ridiculous series of steps, I was able to turn adb debugging back on. If you're ever in a similar situation:
* In External Drive mode, put an APK in the /sdcard/.
* Now re-plug in USB cable to bring up "What do you want to do with USB?"
* From there, long hold the home button.
* Now, open the Task Manager.
* Hit the search key.
* Ask for help on using search.
* A browser will pop up.
* Type file:///sdcard/path-to-apk.apk.
* A dialog pops up "do you want to change settings?"
* F yes you do. Now you're in the setting menu and can turn back on Debugging.
* Turn on debugging and root the phone and learn from your mistakes.

Oops, double posted.

press the search key when it is booted. (or does it bot into the ui at all?) if the search function doesnt come up then long press search and use voice commands. search for settings. hopefully you will get into the settings app and enable debugging

Hi Dan, I did try that before the above method! However, a voice search for "settings" (in that context, anyway) brings up the browser.
She's back online and rooted now - 200 seems to be a sweet spot for density.

cool. yeah i wouldnt have though of that but someone else fixed there phone that way.

200?????
Dang! I took it down to 220 and thought it was gonna cry because the pixels were too tight.
Hehehehehehee
Sent from my SAMSUNG-SGH-I997 using XDA App

Related

Captivate wont wake up from sleep.

I have searched everywhere on the forums google. Here is my problem.
I bought Samsung Captivate on eBay. I needed rooted and unlocked of tmobile. Easy I thought..one click root, then unlock from the market..
First..I am NOT rooted. I have tried 2 methods. Samsung captivate root and Superoneclick. Both dont work....
Second...The sleep button wont work. When my phone goes to sleep, I press the unlock button it is still black screen. I have to plug it in the usb to wake it up...Im thinking to upgrade to FroYo from Samsung KIES.
Third. Advise?
Are you sure it's not a hardware problem? When the phone is awake, can you hold the power button down to get the power off context menu?
I honestly am not sure. I just updated to 2.2 FroYo. Same problem. only way to unsleep is to plug into USB
JohnnyP.akaJP said:
I honestly am not sure. I just updated to 2.2 FroYo. Same problem. only way to unsleep is to plug into USB
Click to expand...
Click to collapse
Try holding down the power button, does a menu come up with an option that reads 'Reboot' or 'Power Off'?
Nothing pops up. I just installed this app called "no lock" and i use my volume rocker to unsleep out. Have any idea how to fix? Its a bit annoying.
Was it always like this even before you attempted any root method? My old cappy that had the random shutdowns only did it when it went to sleep. Would hit the unlock button and the screen remained blank. Hit it again and my phone rebooted... But apparently yours isn't shutting down. Never heard of anything like this. The lock button still puts the phone to sleep fine? And if you hold it down while its awake does that Standby, flight mode, power down menu pop up?
Well...i tried holding it. double tap. triple tap. it wont unlock the goddamn screen. It doesnt shutdown though...and if I hold it it wont do flight mode, power down etc. Im on FroYo. Im thinking about rooting it, and installing a STOCK froYo. not that crap by samsung
JohnnyP.akaJP said:
Well...i tried holding it. double tap. triple tap. it wont unlock the goddamn screen. It doesnt shutdown though...and if I hold it it wont do flight mode, power down etc. Im on FroYo. Im thinking about rooting it, and installing a STOCK froYo. not that crap by samsung
Click to expand...
Click to collapse
Won't make a difference, your button is busted. Ask samsung for a replacement.
Sent from my GT-I9000 using XDA App
Alright. Can you direct me somehow? And also when im rooting, it wont work at ALL. Its really pissing me off. Ive used Superoneclick 1.65-1.8. Ive done root, shell root...Ran as admin....ran as window xp sp3 vista sp2 etc. Its not working at alll..it always seem to stop here
SuperOneClick v1.6.5.0
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
OK
Waiting for device...
* daemon not running. starting it now on port 5037 *
OK
Pushing psneuter...
* daemon not running. starting it now on port 5037 *
OK
chmod psneuter...
* daemon not running. starting it now on port 5037 *
OK
Running psneuter...
* daemon not running. starting it now on port 5037 *
FAILED
(my phone is on usb debugging, no sim or sd card in there. android samsung stock 2.2)
Use rage method
Sent from my GT-I9000 using XDA App
Ehhh rage method? hitting the phone?
Lol. No he is referring to rooting with one click. It is an option.
I have tried that..doesnt seem to work. The method by TGA? doesnt load on my computer
The lesson here is that buying Captivates used off eBay and Craig's List is a bad idea. Sounds like someone offloaded their defective phone on you. Search for "random shutdowns" and you'll see why.
Sigh....It doesnt randomly shutdown though..just cant get out of sleep or root.
You likely had a hardware issue. I have read someone I think it's almost a month way back with same issue as you have now his phone was also bought from ebay. The power button (the plastic button in phone casing) of his phone is not touching the internal switch of his phone, all he does is unscrew and open the casing of his phone and found out that the power button is not touching the internal switch and and it was misalign. The problem have been fixed after aligning the latter.
Thank you for getting back on me with an answer. I will do that and try. Anyone have a method to root my phone? one click doesnt work and I wouldnt dare to use update because lack of my power button working. I cant install nonmarket apk files too...so i cant use that rooting apk file
if superoneclick wont work, then NOTHING will......i would honestly odin that sucker back to 2.1 and start over. see if the problem is still there
Hmm..superoneclick has never failed me til now..I still have faith in it. I looked at the log, it cant connect to my phone because it cant access it through the port. reinstalling usb drivers...
And 2 computer later....it does the trick...lol.
Rooted and now can install non markets apps. Going to unlock soon for tmobile. Anyone ever taken apart a captivate?

[q] broken screen need to retrieve files

Hello everyone,
So my screen cracked and my lcd slowly started dying and is now completely black. Touch still works as i am able too unlock the screen and i can hear random noises. Is there any way to retrieve the files of the phone? I can plug it in and the computer recognizes the phone, I just cant mount the SD card. I have all my lecture recordings for school on there! Please help.
if someone could show me with pictures or video how to enable the mass storage so i can enable it blind, that could work too.
Phone is UNROOTED
USB DEBUGGING IS OFF
kallan said:
Hello everyone,
So my screen cracked and my lcd slowly started dying and is now completely black. Touch still works as i am able too unlock the screen and i can hear random noises. Is there any way to retrieve the files of the phone? I can plug it in and the computer recognizes the phone, I just cant mount the SD card. I have all my lecture recordings for school on there! Please help.
if someone could show me with pictures or video how to enable the mass storage so i can enable it blind, that could work too.
Phone is UNROOTED
USB DEBUGGING IS OFF
Click to expand...
Click to collapse
If you can't mount then you need debugging on to use adb to pull the files.
Darknites said:
If you can't mount then you need debugging on to use adb to pull the files.
Click to expand...
Click to collapse
Thank you for the reply. Yes but can I turn on usb debugging remotely? i can not access the system settings and turn it on.
kallan said:
Thank you for the reply. Yes but can I turn on usb debugging remotely? i can not access the system settings and turn it on.
Click to expand...
Click to collapse
Hmm don't think it can. You could try and see if adb is working in the Bootloader.
Darknites said:
Hmm don't think it can. You could try and see if adb is working in the Bootloader.
Click to expand...
Click to collapse
how would i get to bootloader on the one s?
kallan said:
how would i get to bootloader on the one s?
Click to expand...
Click to collapse
If you trust the 'Power of the Force' lol than just turn off phone completley than hold 'Power & Volume Down' and you should be on 'Fastboot' so just use the 'Volume Down' key and I am 98% sure it is the first option with the click of one down, not sure if this is helpful or just blah blah blah but (maybe) sorry?
While plugged in I held the power button and the soft keys on the bottom blinked 15 times and it went off. then i held "power and vol down" and nothing happened. Then phone vibrated and then the tmobile jingle sound. dont think im doing it right?
If the device boots and the touchscreen works, you can enable usb debugging blind:
- Unlock the device: Swipe up from the bottom
- Notifications: Swipe down from the top
- Settings: Tap on the far right side, between 0.5 and 1.5 cm from the top. (Directly underneath the status bar)
- Developer options: It's the 2nd option from the bottom, so first swipe up a few times to get to the bottom of the menu, then tap between 1 and 2 cm from the bottom.
- USB Debugging: It's the first option from the top, underneath the status bar and the menu title. Tap between 1.5 and 2.5 cm from the top.
- Now you have to confirm a dialog. The OK button is on the right side, about 4 cm from the bottom (or 2 cm below the center).
adb should work in bootloader even with debugging off. It did for me.
To make your life easier when you get it connected through adb, you can use my quick adb tool to get a visual interface of your device.
That way you dont have to mess with adb commands in a command prompt window
SUCCESS!!! in the midst of randomly pressing parts of the screen, I somehow turned USB mass storage on and was able to transfer all my files! lol I dont think I ever got debugging on though..
Thank you to all that helped. I got my lectures! just in time too, Big exam tomorrow!
Thanks again!

Enable ADB / USB Debugging with a broken screen

Hello All,
I've recently broken my LCD, not cracked, but the contrast material leaked into the screen, eventually turning everything black. I can still use the digitizer, but have no concept what's going on screen. Let's just say, I've been luck and unlucky. My though was to use a screen viewing tool via adb to grab some phone numbers of recent calls/texts before I send to Samsung for repair (the phone agent said they would wipe it back to stock). What I have been trying to do is enable ADB/USB debugging through recovery.
Here's what I've tried so far:
1) Boot to recovery
2) Mount /system as rw
3) pull default.proc and build.proc from their respective directories
4) add the following lines to each
Code:
persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.usb.config=mtp,adb (this line was already located in the default.proc file)
5) push files back to their respective directories
6) reboot
Upon reboot, I'm stuck in a loop. I can't tell what's going on, how far it's getting etc because no display. I assume I'm getting past the initial splash screen because I feel the initial power on vib, and then another short vibe, followed by a long-ish pause, and a reboot (I assume), another power up vib, and another short vib. If I leave connected to USB during this sequence, The PC tries to install the MTP driver, but then fails when it reboots.
I've got to admit, I'm somewhat of a noob when it comes to this device. I don't understand it as well as some of the other handsets I've had. I'm sure I've made a mistake someplace and would greatly appreciate any help/insight you could offer.
Best Regards
My screen broken, but usb debug disabled
I have the same problems, but usb debug disabled, (xplay vivo 510w)
touch pad have key sounds, seems only display cracked.
is there any way to enable usb debugging?
Some possible way:
1. Engineering code to enable usb debugging
2. Any setting screen snaps to enable usb debugging (developers option)
3. reboot to recovery mode (dangerous to data? )
4. Flash ROM (unfamily & not prefer)
Thanks for any help~!
Black Screen but phone appears to function, need to enable debugging
My phone is broken. Screen cracked and black so I assume the digitizer is also broken. I'd like to access the phone through my laptop so I can view the several important apps I have on there. I don't think I have debugging enabled and I have followed this but find it difficult as I'm a novice (I can follow step by step instructions fine) and also tried to follow this. How do I enable debugging with no way of know what's going on on the phone?
Thanks in advance x

Screen having 'Phantom Touch' problems

A while back, My old Stylo 2 stopped working due to a very strange (I assume hardware-related) bug that made the phone constantly press the same spots over and over and over, and the screen was entirely unresponsive otherwise. Only those few spots ( 1. About 25% up the bottom right side, 2. The very top right corner, and most prominently 3. Just right of the multitasking button, within its 'hitbox'.) have any effects on the screen at all, and I cannot find places on the screen that are 'touchable' due to the multitasking button being hit over and over and it constantly switching me between apps.
More than anything, I just want to change my USB mode to file transfer to get my pictures off the phone, but even as easy as that is in Android 7 (pull down the top menu, select USB settings, change to file transfer right?) I can't even get the top menu down most of the time, let alone get to the USB settings. On the rare occasion that I do get all the way there, either the multitasking button starts acting up again or the screen stops responding to everything altogether, making the one thing I need to select un-selectable. Much to my dismay, it also seems that I have USB Debugging turned off (I honestly have no idea why or how this was turned off, as I use ADB frequently), so I can't even use ADB to get a screen control app to run. Are there any ways to either force USB Debugging to be on via console (Win8) or otherwise, or control the screen and disable touch without the need for a third-party app?
Yes
007manyo said:
A while back, My old Stylo 2 stopped working due to a very strange (I assume hardware-related) bug that made the phone constantly press the same spots over and over and over, and the screen was entirely unresponsive otherwise. Only those few spots ( 1. About 25% up the bottom right side, 2. The very top right corner, and most prominently 3. Just right of the multitasking button, within its 'hitbox'.) have any effects on the screen at all, and I cannot find places on the screen that are 'touchable' due to the multitasking button being hit over and over and it constantly switching me between apps.
More than anything, I just want to change my USB mode to file transfer to get my pictures off the phone, but even as easy as that is in Android 7 (pull down the top menu, select USB settings, change to file transfer right?) I can't even get the top menu down most of the time, let alone get to the USB settings. On the rare occasion that I do get all the way there, either the multitasking button starts acting up again or the screen stops responding to everything altogether, making the one thing I need to select un-selectable. Much to my dismay, it also seems that I have USB Debugging turned off (I honestly have no idea why or how this was turned off, as I use ADB frequently), so I can't even use ADB to get a screen control app to run. Are there any ways to either force USB Debugging to be on via console (Win8) or otherwise, or control the screen and disable touch without the need for a third-party app?
Click to expand...
Click to collapse
Yes, but I'd appreciate a thanks for the solution! I give and give ...
First, what model number is your Stylo? For instance I have the Cricket variety (H634). Once you figure that out check out my link below with particular attention paid to the "how to enable usb debugging via dialup" step. I just tried it with my Stylo (H634), works great. The link pertains to the LG G6 but it will work on your LG Stylo as well.
https://forum.xda-developers.com/tmobile-g6/how-to/frp-unlock-lg-g6-using-headphone-jack-t3616166
Or just try this ...
Dial *#546368#*_ _ _# (Field Test Mode). Enter your devices model number in the three blanks. Mine for instance would be *#546368#*634# (H634 being the Cricket model number). Go to SVC>LDB> Enable usb debugging
Happy USB'n!

Question Stuck in recovery mode PLEASE HELP

I thought this would be a good place to ask this.
A few minutes ago, I accidently pressed the volume up and down buttons for a long time on my zflip 3 and it booted into the recovery menu. Now this normally wouldn't be a problem.. if my power button wasn't dented in.
I refused to fix it due to the sheer cost of the fix and could turn my display off by double tapping. However, this means that I have no way to exit recovery mode. I tried using ADB on both my bac and pc (using usb 2.0, 3.0, and c on my pc and c/thunderbolt ports on mac).
My phone however would not connect of show up under devices, and I am suspecting it is because I have done something to the debugging settings. I let the battery run out and it would just boot back into the recovery interface once charged up. It even once went to a light blue screen that said something along the lines of how a custom os can cause major problems.
I am a noob at phone stuff and I really don't know what to do. I have a bunch of photos of my grandma who passed away last year and they aren't backed up to google cloud. I really need any help I can get. Thank you.
Hi, provided that you have already
- enabled adb debugging;
- installed adb.
Now you have to
1. enter fastboot mode;
2. in adb type
Code:
fastboot erase recovery
then, reinstall recovery if you want to.
s.0105._j said:
I thought this would be a good place to ask this.
A few minutes ago, I accidently pressed the volume up and down buttons for a long time on my zflip 3 and it booted into the recovery menu. Now this normally wouldn't be a problem.. if my power button wasn't dented in.
I refused to fix it due to the sheer cost of the fix and could turn my display off by double tapping. However, this means that I have no way to exit recovery mode. I tried using ADB on both my bac and pc (using usb 2.0, 3.0, and c on my pc and c/thunderbolt ports on mac).
My phone however would not connect of show up under devices, and I am suspecting it is because I have done something to the debugging settings. I let the battery run out and it would just boot back into the recovery interface once charged up. It even once went to a light blue screen that said something along the lines of how a custom os can cause major problems.
I am a noob at phone stuff and I really don't know what to do. I have a bunch of photos of my grandma who passed away last year and they aren't backed up to google cloud. I really need any help I can get. Thank you.
Click to expand...
Click to collapse
How about rebooting to system using volume buttons?

Categories

Resources