Related
What were the first 3 things you did to your phone? Did you install applications that require root and if so what were they? Did you get ClockworkMod Recovery installed and backed up your phone? Just curious to see what everyone did right after rooting your phones.
For me I did the following:
1) Installed ClockworkMod Recovery & backed up my phone
2) Installed Titanium Backup Pro (why does it only show 5 things and not all apps?)
3) Installed ShootMe
For titanium you have to update busybox, you click fix or something I forget but after the update you will see everything
Sent from my HTC Glacier using XDA App
Moved to general forum for further discussion. Development is for development threads only. Thank you
Whosdaman said:
Moved to general forum for further discussion. Development is for development threads only. Thank you
Click to expand...
Click to collapse
Thanks. I wasn't sure which one I should have placed it in.
motorjonny said:
For titanium you have to update busybox, you click fix or something I forget but after the update you will see everything
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Click on problems button and install busybox
Sent from my HTC Glacier
mftek said:
Click on problems button and install busybox
Click to expand...
Click to collapse
THAT fixed it for me! Thank you very much, now it shows 208 applications in there. Much appreciated for the assistance!
Now, what all did you guys/gals do after rooting your phone?
motorjonny said:
For titanium you have to update busybox, you click fix or something I forget but after the update you will see everything
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Yep. Go into Titanium, hit the "Problem?" option on the bottom and you will get a pop-up box saying Auto-upgrade for BusyBox, then hit Yes, do it and it will update and show all your apps afterward
*edit* lmao wow sorry. I had this page open to comment right after you posted this but the phone rang so I had to answer and after I got done typing I now see it's already been addressed lol. Sorry about that. Glad it worked for you.
1. Installed ROM manager.
2. Back everything up
3. Installed root explorer to delete bloatware
Sent from my HTC Glacier using XDA App
the only thing i have done is used it to disable the apps that came on it .. not show in the app list and keeps it from running but gets the updates still if they get one .. figured it was better than removing them since there really wasnt a recovery or restore or other rom to flash again if something goes wrong from an uninstalled app or something .. it has enough memory anyhow.
Setting up adb was a pain in the ass due to the given drivers dont install ... there is some code that you have to copy/paste into the inf file(that wasnt in the guide) for the mytouch 4g.
other than that .. havent done anything .. im waiting till the something solid comes out ... not a big fan of rom manager .. havent tried titanium .. i really did like armon ra recovery .. hope he makes one for this thing.
This is what I did.
ryan562 said:
1. Installed ROM manager.
2. Back everything up
3. Installed root explorer to delete bloatware
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Strapt said:
the only thing i have done is used it to disable the apps that came on it .. not show in the app list and keeps it from running but gets the updates still if they get one .. figured it was better than removing them since there really wasnt a recovery or restore or other rom to flash again if something goes wrong from an uninstalled app or something .. it has enough memory anyhow.
Setting up adb was a pain in the ass due to the given drivers dont install ... there is some code that you have to copy/paste into the inf file(that wasnt in the guide) for the mytouch 4g.
other than that .. havent done anything .. im waiting till the something solid comes out ... not a big fan of rom manager .. havent tried titanium .. i really did like armon ra recovery .. hope he makes one for this thing.
Click to expand...
Click to collapse
Hmmm I'm not all to familiar with ADB yet but I have had to use it to turn S back on after getting it OFF with the rooting process and the driver installed that was on the sd card without problem (I'm assuming seeing as I needed the driver in order to complete the process... again I'm new to it all).
Quick question how can I check it again to make sure I have adb set up right?
*edit* just to make sure I have it right, and correct me if I am wrong, I connected my phone to the computer started a command prompt, typed in "adb devices" and it showed "List of devices attached, HT0********* device" - so is it fair to say I have adb installed correctly?
I also went to my device manager and seen *Android USB Devices and then under it MY HTC - so I'm guessing that is the name the HTC driver took when I installed it.
Again, I am sharing this as a peace of mine to myself and maybe someone else that is new to the process like myself (but learning thanks to every one of you all here) that is just wanting to make sure its done right.
likeitnot said:
Hmmm I'm not all to familiar with ADB yet but I have had to use it to turn S back on after getting it OFF with the rooting process and the driver installed that was on the sd card without problem (I'm assuming seeing as I needed the driver in order to complete the process... again I'm new to it all).
Quick question how can I check it again to make sure I have adb set up right?
*edit* just to make sure I have it right, and correct me if I am wrong, I connected my phone to the computer started a command prompt, typed in "adb devices" and it showed "List of devices attached, HT0********* device" - so is it fair to say I have adb installed correctly?
I also went to my device manager and seen *Android USB Devices and then under it MY HTC - so I'm guessing that is the name the HTC driver took when I installed it.
Again, I am sharing this as a peace of mine to myself and maybe someone else that is new to the process like myself (but learning thanks to every one of you all here) that is just wanting to make sure its done right.
Click to expand...
Click to collapse
hmmm you cant open the command prompt and hit adb devices and there it is from what i know .. you have to cd into it first .. which would be the default of cd C:\android-sdk-windows\tools (if you put the SDK folder into the root of your C: on your comp) .. then you can type adb devices and you should see yours there and then adb shell and I usually do a "su" as well ..
if ya really want to test it out type in reboot and the phone will restart ... but if you see the list of devices that should be confirmation enough really
Strapt said:
hmmm you cant open the command prompt and hit adb devices and there it is from what i know .. you have to cd into it first .. which would be the default of cd C:\android-sdk-windows\tools (if you put the SDK folder into the root of your C: on your comp) .. then you can type adb devices and you should see yours there and then adb shell and I usually do a "su" as well ..
if ya really want to test it out type in reboot and the phone will restart ... but if you see the list of devices that should be confirmation enough really
Click to expand...
Click to collapse
Yep you're absolutely right... I kind of left out a few things (that you mentioned, thank you). And I did the type reboot test and the phone rebooted. I was just doing it for added assurance I was doing it right.
Thanks!!!!
likeitnot said:
Yep you're absolutely right... I kind of left out a few things (that you mentioned, thank you). And I did the type reboot test and the phone rebooted. I was just doing it for added assurance I was doing it right.
Thanks!!!!
Click to expand...
Click to collapse
glad it worked for ya ..
another thing to try if you have not done so yet is to try something like this in the terminal or thru adb.
pm disable com.tmobile.apppack <hit enter>
you should get a message saying something like new status disabled .. and not just killed
then go into menu/settings/applications/manage applications/all/ and find the one that says "com.android.providers.applications" hit that and then force close .. this will restart the launcher to show the change and that damn app pack that comes preloaded that you cant uninstall will be gone from the applications.
However .. this DOES NOT uninstall them it just keeps the icon from showing up in your apps and prevents it from running but will still get the automatic updates if there is one for it .. how damn cool is that
if you are in adb hit pm list package and it will show you all of the com.names of all the apps on the phone and you can type whatever you want using the pm disable thing like about to remove it from the app list but without unstalling them.
if you want to enable them then its just pm enable whatever app name here.
Clockwork mod installed then I tried to over clock but I figured out that the current kernal is not supported! Or something like that. Then i came here to see if any roms were available yet! Unfortunately there's none for now! Hopefully we will see CyanogenMod on our MyTouch 4g! By the way its my first post
Sent from my HTC Glacier using XDA App
titanium back up,bloatware,rom manager recovery
First and foremost, remap that god awful genius button, then used titanium backup to freeze all the garbage t-mobile bloatware and backup all apps and system data, then installed clockwork, flashed the recovery and made a rom backup. And of course added the good ole usb and WiFi router apps to my lineup, since its about to start costing more.
Tried to get the standard froyo lockscreen to work in place of the HTC one, but that failed (kinda) and I had to restore the rom ha..
Sent from my HTC Glacier using XDA App
civicvx94 said:
First and foremost, remap that god awful genius button, then used titanium backup to freeze all the garbage t-mobile bloatware and backup all apps and system data, then installed clockwork, flashed the recovery and made a rom backup. And of course added the good ole usb and WiFi router apps to my lineup, since its about to start costing more.
Tried to get the standard froyo lockscreen to work in place of the HTC one, but that failed (kinda) and I had to restore the rom ha..
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Did you remap the genius button to google search?
Sent from my HTC Glacier
mftek said:
Did you remap the genius button to google search?
Sent from my HTC Glacier
Click to expand...
Click to collapse
Yessir..short is text search and long is visual task switcher/vlingo/Google voice search. Works perfect.
Sent from my HTC Glacier using XDA App
civicvx94 said:
First and foremost, remap that god awful genius button, then used titanium backup to freeze all the garbage t-mobile bloatware and backup all apps and system data, then installed clockwork, flashed the recovery and made a rom backup. And of course added the good ole usb and WiFi router apps to my lineup, since its about to start costing more.
Tried to get the standard froyo lockscreen to work in place of the HTC one, but that failed (kinda) and I had to restore the rom ha..
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
How and what bloatware did you remove? I know that there is a crap on this phone that I will never use. ie guitar hero and those other craps. I just want to know the steps to do the same thing. Thanks
i have a month old galaxy s i9003 sl running the latest froyo build, i rooted it using one click root, for the past few days my phone would sometimes just freeze up when i try to do something, i have installed loads of apps 144 to be precise, most are on the sd card, is that a problem? one thing i have observed is when i switch on wi-fi and the immediately try accessing an app the phone freezes up, although this isnt the only time that happens.
please advice
Whenever you post anything related to ROM, it is a good practice to mention which version of android you are using including firmware PDA version. As of now many ppl are facing freezing issues on I9003, due to initial unfinished FW versions, but some ppl did not face these problem eventhough the same version of ROM they are using. It could be a single apk file which may be incompatible and responsible for freezing your phone. Try to take logcat using ADB, if the freezing is frequent or if the pattern is known or try upgrading the FW to a different region like XXKB3 (though I dont know where you are from). Some ppl have reported SOD on XXKB3 also but some did not face it, so try your luck.
Well i have the xxkb3 build on my phone, can you please elaborate about how do i go about using the logcat?
thanks
For logcat use adb
open CMD (command prompt) Hope you know that. change directory to the adb tools folder
eg: cd E:/ and_sdk/ adb tools
Now type adb shell
You will see this "$"
type su, the sign will change to "#" after providing root permission from Phone.
now type logcat, wait for some time observe the activities that are flashing on cmd screen, these are the processes running in the background of phone firmware. Now perform the task or sequence of activities that freezes the phone and check the logcat. This will tell you exactly which process is causing problem.
woozydevotee said:
Well i have the xxkb3 build on my phone, can you please elaborate about how do i go about using the logcat?
thanks
Click to expand...
Click to collapse
This guide attempts to solve the following problems:-
1. The menu and home buttons' keypresses are detected but the respective actions aren't executed.
2. The lockscreen doesn't get activated.
3. The power menu has only reboot and power off as options. The rest of the options like Airplane Mode and Profiles.
PREREQUISITES:
1. ADB
2. SQLITE3
FIX:
1-Copy sqlite3 to /system/bin
2- chmod 777 /system/bin/sqlite3
3-Type following command in ADB or Terminal Emulator
Code:
sqlite3 /data/data/com.android.providers.settings/databases/settings.db "INSERT INTO secure (name,value) VALUES ('device_provisioned','1');"
4- Reboot
5- Done
This guide is based upon this post.
Have you tested this? Does this fix the anoying bug when you press menu and nothing happens so you have to press 2-3 times? Will the phone wake on back/menu press? Mine takes 2-3 clicks to wake with menu/back key, this is not the case with eclair.
2. The lockscreen doesn't get activated. - What do you mean by this? Is it when the lockscreen takes 1-2 seconds to appear after waking the phone? - this doesn't happen to me anymore thankfully.
ka'cipeder said:
Have you tested this? Does this fix the anoying bug when you press menu and nothing happens so you have to press 2-3 times? Will the phone wake on back/menu press? Mine takes 2-3 clicks to wake with menu/back key, this is not the case with eclair.
2. The lockscreen doesn't get activated. - What do you mean by this? Is it when the lockscreen takes 1-2 seconds to appear after waking the phone? - this doesn't happen to me anymore thankfully.
Click to expand...
Click to collapse
I think u misunderstood...
*Sometimes due to a weired bug in android, there are only 4 options in extended power menu..Power Off,Reboot,Recovery n Download.
*Home button does not works at all.
*Lock-screen is completely gone.
*Power menu just turns on the screen
*Sleep mode is gone.
U can search for the same problem over google but there was no sure shot solution... But now there is..
I myself faced it few times while cooking the roms and each time u face this bug, there is no other way than start from zero again....
Had the same problem ages ago.
It occurs if you remove SetupWizard.apk.
Leave it be, do a factory reset and all will be well.
ka'cipeder said:
Have you tested this? Does this fix the anoying bug when you press menu and nothing happens so you have to press 2-3 times? Will the phone wake on back/menu press? Mine takes 2-3 clicks to wake with menu/back key, this is not the case with eclair.
Click to expand...
Click to collapse
that's no bug. it's the normal behavior of froyo that you have to do a double click on the "outside buttons" to wake up the phone.
sent from the desert
Had this exact same problem yesterday. had to reflasb. And this happens after you switch roms with g3mod multiboot.
Sent from my GT-I5800 using XDA App
dilzo said:
Had this exact same problem yesterday. had to reflasb. And this happens after you switch roms with g3mod multiboot.
Sent from my GT-I5800 using XDA App
Click to expand...
Click to collapse
Exactly! thats why i prefer triboot/dualboot
Is it possible to include this fix in a rom?
Or to do it in recovery with a update.zip?
this is not even needed thomas You have deleted setupwizard.apk from system/app I think. If you delete that apk this happens just place it back. If you apply this but do not have the setupwizard.apk in your system it will come back after a while
I dont deleted it but maybe it is because i deodexed the rom... I wil try to replace it
Sent from my GT-I5800 using XDA App
Thanks Werker. It worked!
Sent from my GT-I5800 using Tapatalk
no problem
This tutorial worked for me. Thanks for the re-post and the shell script!
thanks a lot. i had this the 4th time while using cm9 before i came to this thread. and never had this in any other rom except cm9.
does anyone know what causes this bug?
arnab321 said:
thanks a lot. i had this the 4th time while using cm9 before i came to this thread. and never had this in any other rom except cm9.
does anyone know what causes this bug?
Click to expand...
Click to collapse
no, im still having the same problem on CM 7.2, after you remove Setup Wizard this problem occurs
Thanks a lot, I had this problem so many times, but this is the first time I am handling this without reflashing ROM. Thanks again.
Where can I find setupwizard.apk in not present in system/app
? Can u upload for cm7 a 8.3
Sent from my GT-I5800 using xda app-developers app
thanks! this totally saved my @ss.
I am on a SE Xperia Arc, rooted with CWM recovery, and a generic firmware 4.1.B.0.431.
I went into recovery mode and reset the phone, wiping everything. After that, this exact same problem appeared (home button non-functioning, no lock screen, etc...) Also, the phone would not receive calls! Data was working and was able to receive messages that way, and was able to dial out.
A few tips for people running this fix to save some time.
How to run an ADB terminal command line? Don't bother.
1. Just install something like Root Explorer.
2. copy sqlite3 to the /system/bin directory ON YOUR PHONE
3. change the permissions (that's that chmod 777 means)
4. give owner and group read and write permissions
5. IMPORTANT. copy the fix.sh (it's a script) to the ROOT of the phone. not /sdcard, but ROOT
6. just click on the fix.sh and select "excute) and the script will run and you will see output saying (done, reboot) or something.
good luck! and thanks for everybody's help!
rooted device
Hallo, in advance - sorry for my English (haven't spoke nor written for long time)
Do I need rooted device to go through arunmcops's procedure? I have galaxy Y pro (b5510) and after rooting then unrooting and factory reset, I have the same issue when home button doesn't react... Thanx in advance for any response.
Hi!
I have just encountered this bug (on my I9300) and tried to apply your fix, but sqlite crashes saying
Code:
soinfo_relocate(linker.cpp:1013): cannot locate symbol "sqlite3_load_extension" referenced by "sqlite3" ... CANNOT LINK EXECUTABLE
... what can I do?
I am sure all files have the right permissions, but apart from that I wasn't even able to find that error on google :/
hahaha nevermind... It worked the first time I tried it, I just had to reboot and actually turn the lockscreen on
Hello friends, Please note that i tried installing ClockworkMod 3.1.0.1 but it refused to setup for some reason, even though i did everything right i.e. holding down the down vol key and power button etc but like others i only get the green android with the exclamation mark in the middle, so i do not have a backup unfortunately ;(
Anyway the story starts here:
Please be patient with me though as i am new to all this but learning fast.
Got a new Asus transformer TF101 (with keyboard) for only 5 days with
Device serial: B70KAS3?????
Build number: HMJ37.WW_epad-8.4.4.11-20110711
Android version: 3.1
Didnt know about Razorclaw ability to root B70 :-(
Anyway on going online on the TF101 for the first time, I immediately got a message saying there was a new os update available, the TF101 auto downloaded it and i then immediately updated it, thinking that the new update was best for me :-(
After the update, i then had -
Build number: HTK75.WW_epad-8.6.5.21-20111216
Android version: 3.2.1
Razorclaw doesnt work on my TF101 however i was able to use use the WW_epad-user-8.6.6.19.zip update on it and then was able to root using Razorclaw.
After that everything worked fine until i used 'Rom Manager' to create a script that was to change my hostname to my preferred one instead of the usual 'android_????????????', i then set it to do so on boot within 'Rom Manager'.
I then used 'Rom Manager' 'reboot' script to reboot the TF and now it boots then flashes locked screen for a second and shuts down and the same thing happens when i power it up again
If i am lucky and quick, i can put in the password and see the desktop just before it shuts down.
I have a feeling it the script i created and set to execute on boot is what is causing the shutdown.
Is there anyway to fix this?
It not a low battery issue, already checked that.
Was thinking along the lines of a key combination to prevent scripts running on boot time.
Dont really want to wipe the TF, as it already taken me 5 days to get it setup how i want it and now this!
It sounds like you have a stock recovery and a buggered up system.
You might be able to recover with adb, but you'll have to know what to stop/kill before it reboots. If it's enable, adb will be active well before you see the lock screen. There might also be some tools in the android sdk, perhaps ddms.
What exactly is in this rom manager script? Perhaps it is passing a reboot via one of the partitions. You would need to clear the command to stop the reboots or just kill the process that is rebooting.
That's all I gots. Good luck!
gee one said:
It sounds like you have a stock recovery and a buggered up system.
You might be able to recover with adb, but you'll have to know what to stop/kill before it reboots. If it's enable, adb will be active well before you see the lock screen. There might also be some tools in the android sdk, perhaps ddms.
What exactly is in this rom manager script? Perhaps it is passing a reboot via one of the partitions. You would need to clear the command to stop the reboots or just kill the process that is rebooting.
That's all I gots. Good luck!
Click to expand...
Click to collapse
thanx for responding mate...appreciated.
the script is just a simple script with just one line with tr3ble being the new hostname, its exactly as below:
setprop net.hostname tr3ble
I'll have a tinker with adb but what how do i search for processes to stop/kill using adb as im not that clued up with linux commands
I'm not a pro either, but I think "ps" will show you the process and "kill <pid>" will kill them. There might be a better way and I haven't tested this, so if you end up in a worse situation than then one you are in, it's all on you.
I don't think that changing the hostname will cause a reboot. I think the "reboot" command from rom manager is somehow stuck. I think it passes a reboot command via one of the partitions so that it can "find" it when it restarts. You would just have to clear the command. I think it's somewhere in the /cache directory, but that is just a guess.
gee one said:
I'm not a pro either, but I think "ps" will show you the process and "kill <pid>" will kill them. There might be a better way and I haven't tested this, so if you end up in a worse situation than then one you are in, it's all on you.
I don't think that changing the hostname will cause a reboot. I think the "reboot" command from rom manager is somehow stuck. I think it passes a reboot command via one of the partitions so that it can "find" it when it restarts. You would just have to clear the command. I think it's somewhere in the /cache directory, but that is just a guess.
Click to expand...
Click to collapse
Wow...you are definitely pointing me in the some direction though, in the begining i didnt have a clue what to do and where to look but now i have a few things to try...i'll see how things go with adb and report back.
Thank you for your time and patience mate
Update:
I tried everything i could but just didnt seem to have much time to do much using adb so i bit the bullet and did a data wipe, but to my joy, after the data wipe the TF was still rooted and my adhoc hack was still in place. If only took me bout an hour to then reinstall all my apps, which was more or less easy as i had them all in one folder on my microSD.
So all in all, the data wipe which cured the shutdown after restart wasnt sooo bad afterall.
Thank for your help mate!
....Happy New year!
b00b said:
Update:
I tried everything i could but just didnt seem to have much time to do much using adb so i bit the bullet and did a data wipe, but to my joy, after the data wipe the TF was still rooted and my adhoc hack was still in place. If only took me bout an hour to then reinstall all my apps, which was more or less easy as i had them all in one folder on my microSD.
So all in all, the data wipe which cured the shutdown after restart wasnt sooo bad afterall.
Thank for your help mate!
....Happy New year!
Click to expand...
Click to collapse
Did the same exact procedure when the same thing happened to my TF earlier this month.... Good to know that i wasn't the only one that faced this situation.
Sent from my Transformer TF101 using xda premium
So, I'm attempting to root a Charge that the volume keys do not work. Apparently, 1 and 2 year olds who have great throwing ability is something the Charge, well, anything really, doesn't exactly appreciate. Normally, I root by going into the download mode, and flashing CWM, then installing the ROM. Obviously, not happening here.
My question is, has someone with more knowledge than I figured out how to accomplish this? Its running stock FP5. I really don't want to send it in because of the contract timing and wasteful of money. I'm also willing to experiment replacing parts, if someone knows anything about it...
Thanks.
Sent from my SCH-I510 (Tweaked 3.0) using xda premium
Yep. There's a jig that will force the phone into dl mode. IIRC it's branded for the gnex but it's confirmed to work on the Charge as well. http://forum.xda-developers.com/showthread.php?p=27533069
Sent from my SCH-I535 using Tapatalk 2
Hey, I had a thought of using ADB to root, and somehow forcing CWM on it, then using an app to boot it into dl mode. I've never used and before and don't know if it's possible, although, from what I read, it seems plausible. Can you offer any insight on this idea?
Sent from my SCH-I510 using xda
edji-x said:
Hey, I had a thought of using ADB to root, and somehow forcing CWM on it, then using an app to boot it into dl mode. I've never used and before and don't know if it's possible, although, from what I read, it seems plausible. Can you offer any insight on this idea?
Sent from my SCH-I510 using xda
Click to expand...
Click to collapse
If you have adb all set up and it properly recognizes your phone (something comes up when putting in the adb devices command) you can boot into download mode with
adb reboot download
Actually it's something I looked into recently for another member. I'm not saying it's not possible but I don't think we have the right tools for it. Originally ginger root was used via adb to root the charge but that's not going to work with our version of gb (assuming you could still find it). I'm not sure the format of cwm will work either. I'm not really proficient with adb so someone with more expertise might be able to get you going.
Sent from my Nexus 7 using Tapatalk 2
Awesome. I don't have it installed yet, but it doesn't look like it takes much to make it work. Plus, I have nine that isn't screwed up, so I think I'll see what I can come up with later.
On a side note, I can't post a reply to your tweaked 3.1 thread, but I ran into somewhat of a problem... run tweaktools, did the tweaks thing, phone BARELY would run. I also couldn't get a shell to run to get back in to uninstall. What I ended up doing to fix was a reinstall of SuperSU and installing a bash shell off a different emulator to get back into tweaktools. This was after I played in /system/etc/init.d awhile trying my hand at fixing it. Thought you may want/need to knoknow.
Sent from my SCH-I510 using xda
By the way, thanks for the tip. I'll report one way or another in a day or 2.
Sent from my SCH-I510 using xda premium
edji-x said:
On a side note, I can't post a reply to your tweaked 3.1 thread
Click to expand...
Click to collapse
You need 10 posts minimum to post in the Dev forums, XDA's rules.
Sent from my Droid Charge running [email protected] 3.2a enhanced by dSlice's Scripts & Tweaks
edji-x said:
Awesome. I don't have it installed yet, but it doesn't look like it takes much to make it work. Plus, I have nine that isn't screwed up, so I think I'll see what I can come up with later.
On a side note, I can't post a reply to your tweaked 3.1 thread, but I ran into somewhat of a problem... run tweaktools, did the tweaks thing, phone BARELY would run. I also couldn't get a shell to run to get back in to uninstall. What I ended up doing to fix was a reinstall of SuperSU and installing a bash shell off a different emulator to get back into tweaktools. This was after I played in /system/etc/init.d awhile trying my hand at fixing it. Thought you may want/need to knoknow.
Sent from my SCH-I510 using xda
Click to expand...
Click to collapse
Sorry to hear of the troubles - not sure what would have caused the issue with tweaktools. You weren't able to su, or you weren't able to open terminal emulator? What were you messing with specifically in the tweaks?
dwitherell said:
If you have adb all set up and it properly recognizes your phone (something comes up when putting in the adb devices command) you can boot into download mode with
adb reboot download
Click to expand...
Click to collapse
:banghead:
Sigh, I don't know why I didn't think of that lol. And I was Ninja'd. Double whammy lol
Sent from my SCH-I535 using Tapatalk 2
Okay, Found it in ADB, and am able to reboot into download, so all is well, I think.
On the tweaktools issue, I kinda did something like this...One tweak does okay, so lets install ALL of them....after that, performed the reboot, and everything went very sloooow. So, I tried to get into a term emulator, and nothing happened, the shell wouldn't even start. Blank screen. So, I tried a different outside of ROM toolbox. Nothing. So, I played around with the settings here and there, and still nothing. I then went into root browser, and started trying to manually move the tweaks out, nothing different. So, I downloaded another term emulator, "Better Terminal Emulator" and got a bash shell to at least open, was able to get into tweaktools, erase all tweaks, clear downloads. But the shells still weren't operating right. They'd open and run, but nothing would show on screen. So, a erase/reinstall of SuperSU, everything good....LOL
Well, maybe it'll help, maybe not, but here's the path I used to do this:
Visit samsung's site for the ADB download and install to c:\android-sdk\ (default)
Put USB Debugging on in phone
Start up command line and Odin 1.82
issue following in command line (notably in the c:\android-sdk\platform-tools)
Code:
adb reboot download
Odin up some Tweaked 2.2 with recovery and kernel for root
once rebooted, issue the following in ADB shell:
Code:
adb shell
su (Checked phone to be sure root was granted)
cd /data
rm -R *
cd /cache
rm -R *
cd /dbdata rm -R *
reboot, then adb reboot download.
Flashed EP4 Stock, updated,
Updated to FP5E
Once again, USB debug, adb reboot download, and Odin Tweaked 3.1 with 0302,
follow above code again, reboot, and I think I have it right....
Since the volume keys don't work on here, is there a way to screw around in the recovery mode via ADB rather than only the keys? I see ADB sees the phone in recovery, and seems to want to connect with it....Second is, is there a way to play with this in the *nix enviroment? I also have been searching for the Gingerbreak, etc to root this thing on stock, but haven't been able to do it....and last, is there a way to do a data wipe other than what I did, and think i accomplished with ADB?
Thanks
With the CWM that I am using, you can use the hard buttons at the bottom of the phone to navigate.
Sent from my SCH-I510 using Xparent Red Tapatalk 2