Related
I was messing around with the root finder and somehow delelted my TouchWiz30Launcher.apk and TouchWiz30Launcher.odex in the system/app folder and now i have a black screen. Any know how to fix this please.....
please dont post a topic in the dev section asking for help, the mods will lock this im sure. i replied to your post in the launcher thread. i need to know more about the state your phone is in before i can point you in the right direction. i see you are rooted. that is good. was debugging enabled before this happened? have you modded 3e recovery so it can run update.zip files?
No I was not in debugging (forgot)
I get a black screen and a task bar, nothing else my buttons dont work.. I can see any apps or anything but black screen, I think I moved or did something to the TouchWiz30Launcher.apk and TouchWiz30Launcher.odex
I was hopeing I might be able to get into the system/app files from m y cpu..
kosherdill34 said:
No I was not in debugging (forgot)
I get a black screen and a task bar, nothing else my buttons dont work.. I can see any apps or anything but black screen, I think I moved or did something to the TouchWiz30Launcher.apk and TouchWiz30Launcher.odex
I was hopeing I might be able to get into the system/app files from m y cpu..
Click to expand...
Click to collapse
you would need to be in debugging mode, have you restarted the phone? if not good! hold the home button for 5 seconds, see if the recent app list pops up. if you have rebooted you need to prey that recovery is adb enabled
Dani897 said:
you would need to be in debugging mode, have you restarted the phone? if not good! hold the home button for 5 seconds, see if the recent app list pops up. if you have rebooted you need to prey that recovery is adb enabled
Click to expand...
Click to collapse
i think i am screwed, I am past all this I have no recent apps and the phone has restarted on me
kosherdill34 said:
i think i am screwed, I am past all this I have no recent apps and the phone has restarted on me
Click to expand...
Click to collapse
no not really screwed. are you on a windows computer?
do you know how to boot into recovery mode?
have you ever used adb before?
how are you with comand line?
On a Mac (which makes this even harder)
Forst android phone
Not to good with adb or command lines....
kosherdill34 said:
On a Mac (which makes this even harder)
Forst android phone
Not to good with adb or command lines....
Click to expand...
Click to collapse
this might be a pain. before you do any mods you want a backup plan. im hopefully gonna get you setup with cwm recovery then after it is fixed(if we can do it) you will have a way to restore from the phone. ill be back with links and instructions
If i go into the Android system recovery and choose delete all user data or something from there will that help or work
Dani897 said:
this might be a pain. before you do any mods you want a backup plan. im hopefully gonna get you setup with cwm recovery then after it is fixed(if we can do it) you will have a way to restore from the phone. ill be back with links and instructions
Click to expand...
Click to collapse
wait you have cwm working?
well no. andriod doesnt work like that. maybe reinstall packages can restore some things but not likely the launcher. but deleting user data is all you will do with a "factory reset" it is kinda a misnomer. it assumes you didnt delete anything.
download this:
http://forum.xda-developers.com/showthread.php?t=909213
what tool did you use to root?
DroidXcon said:
wait you have cwm working?
Click to expand...
Click to collapse
yes! i made a thread about it. the one from the captivate is functional, let me help him. this can take a while!
it's 3:30 in the morning. im not gonna be up all night. do you want help or not?
what program did you use to root? please answer me
Dani897 said:
it's 3:30 in the morning. im not gonna be up all night. do you want help or not?
what program did you use to root? please answer me
Click to expand...
Click to collapse
how can he mount the system if he can not get to shell with root permission...if he trys it from recovery he can not gain root permission
DroidXcon said:
how can he mount the system if he can not get to shell with root permission...if he trys it from recovery he can not gain root permission
Click to expand...
Click to collapse
some phone have adb enabled in recovery. i believe 2e on 2.1 galaxy s phones were. im not sure about 3e
Dani897 said:
some phone have adb enabled in recovery. on an evo to unlock recovery you run rage against the cage in recovery im hoping that is the case here. im pretty sure galaxy s's were adb enabled on 2.1. with 2e recovery. nnot sure about 3e
Click to expand...
Click to collapse
yeah adb works but it wont allow for root access so he cant mount the system.
DroidXcon said:
yeah adb works but it wont allow for root access so he cant mount the system.
Click to expand...
Click to collapse
he's already rooted. or are you suggesting that adb wont cp files to /dev and /system from recovery?
sorry it just needs to go to /system/bin
ok it's 4:00 am. times up. im going to sleep good luck with it.
Dani897 said:
he's already rooted. or are you suggesting that adb wont cp files to /dev and /system from recovery?
sorry it just needs to go to /system/bin
Click to expand...
Click to collapse
keeps getting permission denied in recovery adb
DroidXcon said:
keeps getting permission denied in recovery adb
Click to expand...
Click to collapse
yup you are right. he needs heimdal and a prayer. being that our stock rom is unproven
Hello
I've been trying to take a NANDROID backup of my samsung GT-s5690
Unfortlely the clockworkmod, doesnt work on this phone.
When I try to use the Backup function in ADB, it says:
Code:
ADB: unable to connect for backup
It doesnt matter if I use wireless or cable.
Can anyone tell me how to solve this? I want to take something simmilar to a Nandroid backup
Best regards
Are you rooted? Have you turned on USB debugging in the settings?
yes
post-mortem said:
Are you rooted? Have you turned on USB debugging in the settings?
Click to expand...
Click to collapse
yes and yes.
when i try this on my galaxy s3 it prompts with a password, and then it works very well.. on the gt-s5690 it dons't do anything
Have you been able to successfully communicate with this phone through ADB previously? If yes, was it the same ROM?
Yes I have, the rom is stock. i can communicate with ADB but not take a backup..
You have the latest SDK, right? Is there anything else wrong with the phone which might lead you to believe that the ROM is corrupted?
Alternatively, maybe you could do it through fastboot.
EDIT: Oh, and when you say that CWM doesn't work, do you mean that there is no compatible recovery for your device?
-- Sent from my TouchPad using Communities
Yeah lastest SDK, and the rom doesn't seem to be corrupted works fine. althought I've deleted a lot og boatware on it.
I have tried to flash a new rom to it, nut ODIN dont seem to connect with it.
Yes there is no CWM for that phone
I don't know enough about ADB to help you further there. See if you can communicate properly via fastboot.
-- Sent from my TouchPad using Communities
Hey,
So I think I deleted everything from my phone. I can get to the TWRM screen and play around there, but when I want to restart my phone, it says,' NO OS installaed!'
When I go to restart it, I'm just stuck at the google screen.
I cant transfer a custom rom to my phone because my phone isn't in a state where I can put transfer filed to my phone.
Please help ASAP!
Two options:
1) Adb push a ROM in custom recovery.
2) Flash the factory image with fastboot in the bootloader.
Sent from my Nexus 5
if you can enter fastboot just flash a ROM through it ...you'll be fine
sirajgoku said:
if you can enter fastboot just push a ROM through adb ...you'll be fine
Click to expand...
Click to collapse
Massive contradiction in terms - you can't use adb commands in fastboot, you use fastboot commands in fastboot
Sent from my Nexus 5 using XDA Premium 4 mobile app
If this were me I would adb push a custom rom via recovery. Although I love stock, if I were in your shoes I would go with cataclysm or slim.
mmavani said:
Hey,
So I think I deleted everything from my phone. I can get to the TWRM screen and play around there, but when I want to restart my phone, it says,' NO OS installaed!'
When I go to restart it, I'm just stuck at the google screen.
I cant transfer a custom rom to my phone because my phone isn't in a state where I can put transfer filed to my phone.
Please help ASAP!
Click to expand...
Click to collapse
Have you tried flashing the factory image? This should be a requirement before coming on here and asking for help.
instruction
El Daddy said:
Two options:
1) Adb push a ROM in custom recovery.
2) Flash the factory image with fastboot in the bootloader.
Sent from my Nexus 5
Click to expand...
Click to collapse
can you send me guide? instructions? video?
mmavani said:
can you send me guide? instructions? video?
Click to expand...
Click to collapse
The sticky threads in general and Q&A would be a good place to look.
Sent from my Nexus 5
mmavani said:
can you send me guide? instructions? video?
Click to expand...
Click to collapse
Ay yay yay, I hear kittens dying.
This is a perfect example of why toolkits aren't beneficial to new users. If the OP had rooted manually, he'd be familiar with both fastboot and adb, and would be able to solve this issue easily.
Toolkits should only be used by experienced users, in order to save time... NOT as a pacifier for the uninitiated. :-\
Sent from my Nexus 5 using Tapatalk
@mmavani,
Despite my obvious bemusement, I'm going to try to help out... First, check here - http://forum.xda-developers.com/showthread.php?t=2507905
Also, do a Google search on adb and fastboot, and find out what they do, and why you need to be familiar with them. If you research, read , and understand the information, then you should have no problem doing this - adb push "romxyz.zip" /sdcard/download.
If you can't (or don't want to) take time to educate yourself about unlocking, rooting, and flashing, then you need to reconsider whether you have any business being rooted.
Sent from my Nexus 5 using Tapatalk
Fixed
jjhiza said:
@mmavani,
Despite my obvious bemusement, I'm going to try to help out... First, check here - http://forum.xda-developers.com/showthread.php?t=2507905
Also, do a Google search on adb and fastboot, and find out what they do, and why you need to be familiar with them. If you research, read , and understand the information, then you should have no problem doing this - adb push "romxyz.zip" /sdcard/download.
If you can't (or don't want to) take time to educate yourself about unlocking, rooting, and flashing, then you need to reconsider whether you have any business being rooted.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
It's already fixed.
Thanks for your help
o I rooted my nexus 5. No issues. Installed TWRP. Same. Downloaded CM and GA to the phone. Then, very foolishly, wiped everything to prep for the install - SD card included. Now, all I can load is TWRP. No ROM to be found - obviously. Computer won't recognize the phone to load a ROM that way. Would be VERY appreciative of any help. TY!S
you can use the 'adb push' command in recovery to transfer a rom zip to the phone via your computer
meangreenie said:
you can use the 'adb push' command in recovery to transfer a rom zip to the phone via your computer
Click to expand...
Click to collapse
I have TWRP v2.6.3.0 installed. The bootloader option takes me to TWRP. The Recovery option just hangs at the Google splash screen. Can you be more specific pls? Thanks for the help.
bradley.robt said:
I have TWRP v2.6.3.0 installed. The bootloader option takes me to TWRP. The Recovery option just hangs at the Google splash screen. Can you be more specific pls? Thanks for the help.
Click to expand...
Click to collapse
Install adb drivers on your computer then go to TWRP recovery with your phone connected to your computer. Type 'adb devices', to check if your phone is detected, it should display your phone's serial number. Then you can 'adb push file' to transfer the cm/gapps zips from your computer to phone's internal sdcard.
So you have no idea how to use ADB? You're in for a real long night. -__-
Read this
http://forum.xda-developers.com/showthread.php?t=2513701
And this
http://forum.xda-developers.com/showthread.php?t=2507905
aldyu said:
Install adb drivers on your computer then go to TWRP recovery with your phone connected to your computer. Type 'adb devices', to check if your phone is detected, it should display your phone's serial number. Then you can 'adb push file' to transfer the cm/gapps zips from your computer to phone's internal sdcard.
Click to expand...
Click to collapse
Sorry, assume 'adb devices' is in the command prompt, but noob town - which folder in the ADT parent folder?
RoyJ said:
So you have no idea how to use ADB? You're in for a real long night. -__-
Read this
http://forum.xda-developers.com/showthread.php?t=2513701
And this
http://forum.xda-developers.com/showthread.php?t=2507905
Click to expand...
Click to collapse
That's what I figured, but...challenge accepted. Thanks for the links.
RoyJ said:
So you have no idea how to use ADB? You're in for a real long night. -__-
Read this
http://forum.xda-developers.com/showthread.php?t=2513701
And this
http://forum.xda-developers.com/showthread.php?t=2507905
Click to expand...
Click to collapse
RoyJ,
Appreciate the help. TY, all's good.
Happened to me a few times tinkering with the gnex, n4...boneheadedly wiped the internal storage. Easiest fix in my opinion is to just flash factory stock and start back from stretch. If not like they said you're in for a long night trying to get your phone to sync up to push the files via adb if you aren't familiar with the stuff.
Do wish you the best. Been there.
I have not been in that situation but couldn't you use a OTG cable (a Y type one which accepts power as well) and a SD card or stick and then mount it within TWRP to access a ROM to flash...?
EDIT: Also consider the Nexus Toolkit - very useful.
I really think that the faster way is to flash stock firmware back (if you have no experience with ADB commands).
Don't be so scared of adb. Its hard if you don't know Linux but adb is really really copy and paste for first time use. (That's how I learned anyways) You learn it once and it stays current and useful.
Sent from my Nexus 7 using XDA Free mobile app
Just install official images of nexus 5. No need to learn complex stuff where u have no idea even abt adb.
TheLastSidekick said:
Don't be so scared of adb. Its hard if you don't know Linux but adb is really really copy and paste for first time use. (That's how I learned anyways) You learn it once and it stays current and useful.
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
It's really not that hard.. You plug it in, open a folder, open the prompt and type a few words.. My advice is to try and learn.
sent from my Nexus 5
Seadra said:
Just install official images of nexus 5. No need to learn complex stuff where u have no idea even abt adb.
Click to expand...
Click to collapse
A bit discouraging friend. I say learn on all about adb it's essential for Android. Knowledge is power.
Sent from my Nexus 7 using Tapatalk
Seadra said:
Just install official images of nexus 5. No need to learn complex stuff where u have no idea even abt adb.
Click to expand...
Click to collapse
You need fastboot/adb to do it anyways. Unless you use toolkits, ew.
Glad you got it sorted.
Letharqy said:
You need fastboot/adb to do it anyways. Unless you use toolkits, ew.
Click to expand...
Click to collapse
Yes, just the adb drivers needs to be installed. And I have never used toolkit ever.
TheLastSidekick said:
A bit discouraging friend. I say learn on all about adb it's essential for Android. Knowledge is power.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
No, you didn;t get my point. I told him to straight away restore by images just because his phone wasn't working at all. He can learn all that stuff later, but atleast he should be with no phone at all.
Seadra said:
Yes, just the adb drivers needs to be installed. And I have never used toolkit ever.
Click to expand...
Click to collapse
How would you flash the .imgs without using adb/fastboot?
Letharqy said:
How would you flash the .imgs without using adb/fastboot?
Click to expand...
Click to collapse
by adb drivers, I mean adb/fastboot or SDK and drivers of the phone that's always included.
Is it possible to root one plus one, without deleting any data and apps from it? I just want root access but don't want any custom rom.
yes, of course..
root doesn't delete any of your data
senaferdy79 said:
yes, of course..
root doesn't delete any of your data
Click to expand...
Click to collapse
Thanks for that. How can I do that?
#newtorooting
senaferdy79 said:
yes, of course..
root doesn't delete any of your data
Click to expand...
Click to collapse
That isn't technically true. In order to get root you must have a custom recovery installed. In order to install a custom recovery you must unlock the bootloader. Unlocking the bootloader wipes the device.
---------- Post added at 08:13 PM ---------- Previous post was at 08:10 PM ----------
sourabhkejriwal said:
Thanks for that. How can I do that?
#newtorooting
Click to expand...
Click to collapse
Sorry you got your hopes up, but the other poster isn't right. As per my reply to him you need to unlock your bootloader first, which is going to wipe your device. I'd suggest backing up any files that you have that are important to you. As for your apps and settings, you'll have to set them up again afterwards. Go to my guide thread here:
http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
You need to follow (in order) sections 1, 2, 3, and 4. This will give you root access on your stock ROM. You should also follow section 10, it's very important that you make a backup of your EFS partition.
timmaaa said:
That isn't technically true. In order to get root you must have a custom recovery installed. In order to install a custom recovery you must unlock the bootloader. Unlocking the bootloader wipes the device.[
Click to expand...
Click to collapse
So are you saying all the many how to's that tell you that you can skip installing recover are wrong? Apparently, I don't have enough posts yet to create a link but I've seen posts here on XDA that say other wise and the one I have in front of me at the moment is from ibtimes . com titled "how-root-oneplus-one-install-twrp-recovery-1450708"
Their "Step-7" reads
Step-7: If you want to root the phone without installing TWRP recovery, type the following command
fastboot boot twrp.img
Click to expand...
Click to collapse
I guess the real question being, why would you need a custom recovery?
pdhx said:
So are you saying all the many how to's that tell you that you can skip installing recover are wrong? Apparently, I don't have enough posts yet to create a link but I've seen posts here on XDA that say other wise and the one I have in front of me at the moment is from ibtimes . com titled "how-root-oneplus-one-install-twrp-recovery-1450708"
Their "Step-7" reads
I guess the real question being, why would you need a custom recovery?
Click to expand...
Click to collapse
You're looking at outdated information. They used to be correct, but now they are wrong. This is because you can no longer use the fastboot boot recovery.img command with a locked bootloader. In fact, that functionality was removed quite some time ago.
You need a custom recovery because that's how you flash SuperSU to get root. There's no way around it.
Transmitted via Bacon
The default recovery will only flash cm signed zip, which is another reason for needing a custom recovery. That method you mention at ibtimes meant that it would allow you to, for one boot cycle, do a "live boot" of twrp
Sent From Lollipopified Bacon Goodness!
But how is anything going to be written to the system partition if it is locked ?
timmaaa said:
You're looking at outdated information. They used to be correct, but now they are wrong. This is because you can no longer use the fastboot boot recovery.img command with a locked bootloader. In fact, that functionality was removed quite some time ago.
You need a custom recovery because that's how you flash SuperSU to get root. There's no way around it.
Click to expand...
Click to collapse
Ugh, was afraid of that, you might want to add a comment to that effect to your guide....
Would have been nice to just add a setting to the default recovery to allow you to toggle whether you need a signed zip or not. Sucks that I could root my SGS III (which is far less hacker friendly than the One) without wiping it but I can't do that for the One, all i want is root for the moment. However, after playing around some more I'm getting stick before I even get that far; I can get ADB to find the device but when I adb reboot bootloader I cannot get fastboot to find the device. I've tried multiple drivers, different USB ports. When my One goes into fastboot the screen seems awfully dim, almost like it hasn't completely initialized, is that normal? And if so, any suggestions on why I can get adb to work but not fastboot?
pdhx said:
Ugh, was afraid of that, you might want to add a comment to that effect to your guide....
Would have been nice to just add a setting to the default recovery to allow you to toggle whether you need a signed zip or not. Sucks that I could root my SGS III (which is far less hacker friendly than the One) without wiping it but I can't do that for the One, all i want is root for the moment. However, after playing around some more I'm getting stick before I even get that far; I can get ADB to find the device but when I adb reboot bootloader I cannot get fastboot to find the device. I've tried multiple drivers, different USB ports. When my One goes into fastboot the screen seems awfully dim, almost like it hasn't completely initialized, is that normal? And if so, any suggestions on why I can get adb to work but not fastboot?
Click to expand...
Click to collapse
The one's bootloader is not like a nexus one where you can at least reboot recovery etc, once it boots thats it
what do get when you type fastboot devices ?
bombadier said:
The one's bootloader is not like a nexus one where you can at least reboot recovery etc, once it boots thats it
Click to expand...
Click to collapse
Which seems to be somewhat limiting for such an otherwise developer friendly device?
bombadier said:
what do get when you type fastboot devices ?
Click to expand...
Click to collapse
Nada, nothing, nil. however, "adb devices" works fine... WTF?
pdhx said:
Which seems to be somewhat limiting for such an otherwise developer friendly device?
Nada, nothing, nil. however, "adb devices" works fine... WTF?
Click to expand...
Click to collapse
Point one was just to say there is not anything really you can do in the bootloader, being able to reboot to recovery etc is actually a handy feature
Try a different fastboot.exe ? if you say that adb works perfectly then there has to be something wrong with your fastboot binary
I have attached my one,download and change the name back to .exe and see what happens
Going to need more info in order to help
bombadier said:
Point one was just to say there is not anything really you can do in the bootloader, being able to reboot to recovery etc is actually a handy feature
Try a different fastboot.exe ? if you say that adb works perfectly then there has to be something wrong with your fastboot binary
I have attached my one,download and change the name back to .exe and see what happens
Going to need more info in order to help
Click to expand...
Click to collapse
Fair point about bootloader, what I don't get is why they forced you to have to do the unlock to root? All I started out wanting to do was install Titanium and run a Nandroid or two. Guess if I'm going to have to wipe I guess I may end up installing a Lollipop ROM. However, I still can't get there. The fast boot you supplied gives the same problem. I was running the latest fastboot from the Android SDK and your's appears to be the same (though I haven't done a binary compare). As far as I can tell that leaves the device drivers, the laptop, or the phone itself. I'm running Win 7 SP 1 64 bit and I've tried various drivers including the Samsung the Google generic and they make no difference. Not sure how they would since adb works but I've seen some suggestions that drivers can be finicky in this regard.
What else can I tell you that might help?
Seems since I can get into the recovery that comes with the phone I could maybe get a works around somehow?
pdhx said:
Fair point about bootloader, what I don't get is why they forced you to have to do the unlock to root? All I started out wanting to do was install Titanium and run a Nandroid or two. Guess if I'm going to have to wipe I guess I may end up installing a Lollipop ROM. However, I still can't get there. The fast boot you supplied gives the same problem. I was running the latest fastboot from the Android SDK and your's appears to be the same (though I haven't done a binary compare). As far as I can tell that leaves the device drivers, the laptop, or the phone itself. I'm running Win 7 SP 1 64 bit and I've tried various drivers including the Samsung the Google generic and they make no difference. Not sure how they would since adb works but I've seen some suggestions that drivers can be finicky in this regard.
What else can I tell you that might help?
Seems since I can get into the recovery that comes with the phone I could maybe get a works around somehow?
Click to expand...
Click to collapse
They're "forcing" you to unlock the bootloader in order to root the device because that's the universally accepted standard (unlock bootloader, install custom recovery, flash root). Some devices have super secure bootloaders and that's why you end up needing to use hacks to get those devices rooted, but that isn't the normal way to go about it. Anyway, there's no advantage to leaving the bootloader at all. There's also no disadvantage to unlocking the bootloader at all. You might say that the fact that the device is wiped during the unlocking process is a disadvantage, but that fact is very well documented both here, on the OnePlus forums, and pretty much any other reputable tech site that mentions unlocking the bootloader on this phone. The point to that last sentence? It pays to research a device thoroughly before buying it, or before using it, the wiping of the device is no issue at all if you do it when you receive the phone (prior to using it), like many people have. But in your situation you're just going to have to backup any important media from the phone prior to unlocking.
Anyway, on to your fastboot issue. Exactly which drivers do you have installed on your PC? Do you have any other phone drivers or software installed on the PC? And do you have access to another PC in case the one you're using is the source of the issue?
Got it, 27th try (give or take) is the charm.... Had to use USBdeview and uninstall the Google and the Qualcomm drivers. Reinstalled the Google drivers (after a reboot) and got it to work. Guess I could have figured that out from dev manager by watching what drivers got activated while fastboot was active but nothing ever jumped out at me as an obvious culprit.
Interesting to note that TWRP now automatically prompts you to install SuperSU if you reboot after installing it. Maybe it found the zip but either way, nice touch!
Now to go and decide what ROM to install....
Thanks for your help!
I would suggest temasek unofficial cm12 ROM. Been using it pretty much as a daily driver since version 1.something of the ROM and no problems. At this point it's been almost a month of not having to boot into my cm11s ROM lol. I use it with AK kernel, seems like a good match cuz both devs are working together looks like. Flash AK ukm special edition after flashing his kernel and install synapse from play store if you want to play around with settings of the kernel
Sent From Lollipopified Bacon Goodness!
zenix23456 said:
I have been using AnyRooter for months and it is quite good to root OnePlus phones.
Click to expand...
Click to collapse
Except the Oneplus One.