Hi Everyone!
I was trying to change the sales code using remount command by rotohammer but at terminal emulator and ADB I get remount: not found.
ROM: Overcome 1.4.2 with 2.1.2 kernel
Terminal Emulator
ROOTED.
Regards.
Dear DarkPal ,
if u only want to actually change your product code, u can use SGS csc selector
after that when it reboot u , it will see yellow words show
"installing multicsc-XXX" XXX is the product code.
For the overcome rom, there have 7 product code for u to choose, but I don't exactly know which is for your country.
To verify , u can connect it to KIES and it will show your product code.
For the ADB issue, which kind of flashing process u use? hemediall or odlin?
I sometimes can't have ==> adb devices as I have 2 I9000 and 1 TAB, always flash TAB and I9000 for my friends. So the usb driver sometime can't work. as too many device have being connected. If this happened, I will try step by step in the following until the driver work again.
re-install device driver by KIES
adb kill-server and than reboot the computer
control pannel=>system manager=>device manager=>uninstall samsung usb driver and than connect the phone and window will reinstall the driver.
regedit user-local-key =>samsung=>kies=>deviceDB=>clear all things and then reboot
usually these steps will let me redetect the device
But in some older rom of I9000 , it never be connected as the rom fault in USB connection app. But this will not the case for overcome rom itself as I tried it before and have no issue,it work fine..
hope this help
p.s. if u just want to hack KIES, use spoofFW, it have some preset product code for the western country, after hack you can update through KIES to the newest official firmware of your own country.
p.s. use this command in adb shell or terminal emulator on your tab to get in to csc selection section:
am start -a android.intent.action.MAIN -n com.android.Preconfig/com.android.Preconfig.Preconfig
ADB does detect the device my friend and gives it a number. The issue is that some commands in adb are not working. Remount command being one of them.
I flash through ODIN.
Thanks for SGS selector
bump.
I still get the remount: not found which is rendering ADB not usable for me. Any help would be appreciated.
I asked the same question a few weeks ago, using same odlin.
I was hoping rotohammer would chime in and state the issue.
Went to Android SDK and downloaded all they said to get, and still no remount.
Related
I have rooted my phone once before like a year ago, and it worked like a charm - but when the official 1.6 came out it apparently unrooted me (I assume thats what happened?) All I know is now when I try to run root required apps it tells me I'm not rooted.
So I figured to just start over from the beginning. I downgraded to RC29 no problem, but when I get to the telnet step it shows a pattern of question marks in diamonds, with boxes separating them. Like this:
<?><?>[]<?><?>[]<?><?> <?><?>[]<?><?> #
I run the commands anyway, (with the Recovery Image and HardSPL on the root of my SD card) - with each command returning two hash marks # #. But the commands don't seem to do anything, because even when I finish ROM Manager tells me I'm not rooted.
Back in Telnet, I can 'ls' to see my directories, including a root folder - but I'm not sure that means anything.
Not sure where to go from here - any help would be greatly appreciated...
-TQ
........................................
The following Observation was made :
Wrong Section. Belongs in Q/A
K so when u go in adb and type adb shell do you see # or $
Please let us know.
Apologies for posting in the wrong forum. And thanks for moving it.
I can't connect to my phone via ADB - I just get 'device not found' even though I have the USB drivers downloaded. If I do 'adb devices' it shows a blank list.
I've looked into how to resolve this, but with no luck. The phone shows up in device manager under the 'Disk Drives' category as "HTC Android Phone USB Device" when everywhere I read says it should show up under the ADB interface section as "HTC Dream Composite ADB Interface".
I've tried USBDeview to reinstall it properly - no dice. And I tried manually updating the driver with ones I downloaded, but windows says I already have the best driver installed.
I don't know what to do now...
First off ,I like to say hello. Since the "Sprint " tab been out, Im thinking second thoughts of what capacities it can do (not all good). Ive re-programmed it so many times and yes bricked it and resurrected it too :0. Close one
Id tried rom manager (sprint not supported), Put in another kernal just to get rom manager too worked but crashed system (cant win).
Anyway I found Roto backup instructions, no help here. What I have is:
the tab is connected to pc.
cmd prompt which goes to abd.exe
-all is good, this is where i get stuck
adb shell su -c"dd if=/dev/block/bml1 of=/sdcard/boot.bin bs=4096"
The -c of the above code! it says it cant find it or sometimes denied access.
what is it looking for if anything or what folder should adb be in to make this work. Where should i be entering all this into (terminal on tab or pc)
I looked for at least a month (seemed like forever)trying to find some instructions that would help.
Thanks
I think it would he best to send a personal message to rotohammer for more clarifications regarding this.
Sent from my Galaxy Tab via Tapatalk Pro
I have Imilika's AOSP ICS ROM V6,
I changed the buid.prop
ro.sf.lcd_density=213
for tablet mode. after I reboot, my GNote is not booting. I cannot go to recovery mode or download mode.
Please help. I don't know what to do
Got it
OK, I was really sad about what happens to my phone, but finally I managed to fix it .
As I told you, my phone was not booting to recovery or download modes (key combinations not worked). finally I try to connect to PC via USB and luckily my PC could detect my phone . So i realized that the problem is the display not coming but phone is halfway booted.
So, I tried to change my build.prop via adb but failed due to cannot grant root permission (becoz display is off).
Finally I issue a adb commad to reboot in recovery mode.
"adb reboot recovery"
yeah, that command directly take me to the CWM recovery. then I flash AOSP v6 again.
Now, my phone is working again.
P.S. I just note this down for others if they get same problem future !
I have question.. I don't understand the term adb. What that actually and why need that? I did so many flashing so far and I didn't use this adb yet!
priyanv said:
I have question.. I don't understand the term adb. What that actually and why need that? I did so many flashing so far and I didn't use this adb yet!
Click to expand...
Click to collapse
If you don't know what ADB is, you probably shouldn't be flashing so regularly. Anyway, ADB stands for "Android Debug Bridge" and it is a protocol for device control, development, and debugging.
Sent from my GT-N7000 using Tapatalk
priyanv said:
I have question.. I don't understand the term adb. What that actually and why need that? I did so many flashing so far and I didn't use this adb yet!
Click to expand...
Click to collapse
adb is a connection type. we can run shell commands (in the phone), file transfer via adb by using our PC. for that we should have to enable usb debug mode in our mobile.
Actually you might used adb, when you root your phone in the first place . If you have CF-Root zip file, just extract it. you will see a folder called "files", in there you can see adb.exe .
If you need test run,
connect phone via USB(make sure you've enabled USB debug), open command prompt, navigate to that "files" directory.
run "adb shell ls" (to run "ls" command in phone)
run "adb push <anyfile in the PC> /system/sdcard/" (copy files from PC to sdcard)
like that
OK now I got it.. But why do we need to push some file like this when we are able to transfer files like mass storage??? Or what else can be done??? Sorry for the basic questions..
priyanv said:
OK now I got it.. But why do we need to push some file like this when we are able to transfer files like mass storage??? Or what else can be done??? Sorry for the basic questions..
Click to expand...
Click to collapse
Its functionality is not only to copy files from pc to mobile and vice versa.You can use it to get logs due to bad flashing,zip align apps,reboot into recovery,DL mode,normal reboot etc...
I got my Cap to stock GB 2.3.5 finally, after it being in the "firmware upgrade fail" screen. I flashed the file with no bootloader, since I was already on GB before. All went well until I tried to get rooted through Super One Click, short fuse 1.9.1.0. I got everything started and tapped the Captivate tab and it went through the whole process and in the end, failed . Once more, same thing. Tried universal tab, driver check, some kind of windows pop up saying either stop now or sect continue. I continued and tapped root tab and killing adb, starting adb, daemon not running, daemon started successfully waiting for device, failed to get root. One more try, same thing. Now my battery is showing very low, like in the red low. So I left the phone plugged in the wall charger while I reinstalled the Samsung drivers, and that is when I noticed the phone went black and when I connected it to the laptop to try Super One Click with new drivers ans the laptop doesn't recognize the device. Says no drivers are installed, etc...,etc... . One click starts though recognizing the phone and starts trying the root sequence and everything is good until after daemon starts successfully, it says OK, waiting for device... - that's it. I can't get it into download mode even with with the USB jig. I had already sent this phone in and had the unbrickable mod done by Josh at Mobiletech video. So, does anyone have any suggestions or answers, as to how I get this phone working
Use this...[Utility]KK4 Easy Root to get Root.
Sent from my SAMSUNG-SGH-I777 using xda premium
Thanks for that link. I've got bigger issues than trying to get root though. My phone won't go into download, even when I use a USB jig. I have nothing but a black screen. I can't get recovery, my computer recognizes it but only as a Samsung USB device with no drivers installed. I've installed drivers from Kies, from Samsung, and from Gingerbread rom. I have unbutu installed, but I have no idea how to input commands. I have had the phone repaired and had the unbrickable mod performed on it by Josh at Mobiletechvideo back in February. I can't get unbrickable resurrector to work because I don't know how to run Linux / Unbutu. So now I'm out of ideas/options that I'm capable of implementing. If anyone that may read this has an idea of what I should do next, please let me know.
Sent from my SGH-T989 using xda premium
I did a quick google search on this unbrickable resurrector and it looks to be just a .jar file that is able to discover what mode the captivate is in and correct issues. I do not have experience with this exact program but I did find a thread with documentation / how-to. You should be able to follow those instructions + adapt for your device. If you have any specific questions pertaining to ubuntu / linux, let me know.
http://forum.xda-developers.com/showthread.php?t=1397393
broknbottle said:
I did a quick google search on this unbrickable resurrector and it looks to be just a .jar file that is able to discover what mode the captivate is in and correct issues. I do not have experience with this exact program but I did find a thread with documentation / how-to. You should be able to follow those instructions + adapt for your device. If you have any specific questions pertaining to ubuntu / linux, let me know.
http://forum.xda-developers.com/showthread.php?t=1397393
Click to expand...
Click to collapse
I appreciate you trying to help. I hit the "Thanks " button so you will have your first on your meter. LOL. I already read that post and it didn't quite get me what I needed unfortunately. I may have to send it back to Josh at MobileTechVideo and let him see what he can do. But I'm still trying to do it myself in the meantime.
khkaiser13 said:
I appreciate you trying to help. I hit the "Thanks " button so you will have your first on your meter. LOL. I already read that post and it didn't quite get me what I needed unfortunately. I may have to send it back to Josh at MobileTechVideo and let him see what he can do. But I'm still trying to do it myself in the meantime.
Click to expand...
Click to collapse
Do you have java & the .jar file downloaded? If so just open up a terminal and try these commands, substituting file for the actual filename
Code:
cd ~/Downloads
-- This is assuming you've left the .jar file in Downloads directory
Code:
chmod +x file.jar
-- This will give the file execute permissions
Code:
java -jar file.jar
-- This will run the java jar file.
You will need java installed, If you don't have it installed run these commands.
Code:
sudo add-apt-repository ppa:webupd8team/java
sudo apt-get update
sudo apt-get install oracle-java7-installer
Code:
sudo java -version
-- will display the version of java installed.
Let me know if you need anymore help.
Hello, im using O+ 3 and just installed the Oxygen 3.2.2 OS
I wanna root it but got problem because my ADB says unauthorized
Ive already tried to dig some similar case and possible answers thru the internet but none of them work for me
Ive tried to enable disable the debug permission
I also already make sure my ADB is the latest one.
Also already try to delete the 'adb_key' files from my PC (im using windows 7 64bit)
The problem is most user which has similar problem with me got the 'authorized debug prompt' popped up again on their phone, but its not working on my phone.
It appear only one time at the very first time i connect it to my phone, but i accidentaly click 'cancel' on that prompt
But after that it never re-appeared again.
Can someone kindly help me? Thanks a lot
Install the Android SDK or install the OnePlus 3 drivers
Sent from my ONEPLUS A3003 using XDA-Developers mobile app
speedyjay said:
Install the Android SDK or install the OnePlus 3 drivers
Sent from my ONEPLUS A3003 using XDA-Developers mobile app
Click to expand...
Click to collapse
What does the Android SDK do mate?
I never used it before, so would be great if u can give me some hints
Thanks
toughkid said:
Hello, im using O+ 3 and just installed the Oxygen 3.2.2 OS
I wanna root it but got problem because my ADB says unauthorized
Ive already tried to dig some similar case and possible answers thru the internet but none of them work for me
Ive tried to enable disable the debug permission
I also already make sure my ADB is the latest one.
Also already try to delete the 'adb_key' files from my PC (im using windows 7 64bit)
The problem is most user which has similar problem with me got the 'authorized debug prompt' popped up again on their phone, but its not working on my phone.
It appear only one time at the very first time i connect it to my phone, but i accidentaly click 'cancel' on that prompt
But after that it never re-appeared again.
Can someone kindly help me? Thanks a lot
Click to expand...
Click to collapse
Make sure debugging is clicked on under developer options in the main menu. Then disconnect the phone from the pc and reboot the pc. Reconnect the phone after it reboots and hope that you get the adb prompt on the phone again.
android sdk have the latest tools including latest ADB. There is ADB standalone install, that means that if you tell us that you have the latest ADB, that only mean that someone extracted the ADB and lastest fastboot and did a repack and in the end it's not an official repack.
but "disable the debug permission" reset all the recorded device for debug so you should have another prompt.
If in the end you don't have another prompt, verify you adb version by installing the lastest android SDK, uninstall and reinstall the oneplus drivers.
Then if no prompt there is 2 choices :
- wipe the phone, it will reset the prompt for sure, 100%
- use another computer (well you have to have another computer).
I have a computer at home where this happened and I have never been able to straighten it out...tried everything.
Sent from my ONEPLUS A3000 using XDA-Developers mobile app
tdamocles said:
Make sure debugging is clicked on under developer options in the main menu. Then disconnect the phone from the pc and reboot the pc. Reconnect the phone after it reboots and hope that you get the adb prompt on the phone again.
Click to expand...
Click to collapse
Le_Zouave said:
android sdk have the latest tools including latest ADB. There is ADB standalone install, that means that if you tell us that you have the latest ADB, that only mean that someone extracted the ADB and lastest fastboot and did a repack and in the end it's not an official repack.
but "disable the debug permission" reset all the recorded device for debug so you should have another prompt.
If in the end you don't have another prompt, verify you adb version by installing the lastest android SDK, uninstall and reinstall the oneplus drivers.
Then if no prompt there is 2 choices :
- wipe the phone, it will reset the prompt for sure, 100%
- use another computer (well you have to have another computer).
Click to expand...
Click to collapse
Hello sir, i've been trying all of this method, include the wipe the phone (except using another computer) but still no prompt re-appear. Another advice would be greatly appreciated.
Thanks
joho5 said:
I have a computer at home where this happened and I have never been able to straighten it out...tried everything.
Sent from my ONEPLUS A3000 using XDA-Developers mobile app
Click to expand...
Click to collapse
Then how's in the end it goes mate? Do you root your phone? I just wanna root it, if u got any other way except the adb that would be great tho
toughkid said:
Then how's in the end it goes mate? Do you root your phone? I just wanna root it, if u got any other way except the adb that would be great tho
Click to expand...
Click to collapse
Have you checked all of your USB ports? I know in the past (with other phones), problems arise if you're not using a direct USB port (one soldered into your MoBo).
toughkid said:
Hello, im using O+ 3 and just installed the Oxygen 3.2.2 OS
I wanna root it but got problem because my ADB says unauthorized
Ive already tried to dig some similar case and possible answers thru the internet but none of them work for me
Ive tried to enable disable the debug permission
I also already make sure my ADB is the latest one.
Also already try to delete the 'adb_key' files from my PC (im using windows 7 64bit)
The problem is most user which has similar problem with me got the 'authorized debug prompt' popped up again on their phone, but its not working on my phone.
It appear only one time at the very first time i connect it to my phone, but i accidentaly click 'cancel' on that prompt
But after that it never re-appeared again.
Can someone kindly help me? Thanks a lot
Click to expand...
Click to collapse
Go to Control Panel > Hardware and Sound > Device Manager > expand Universal Serial Bus controllers. Now connect your phone. You'll now see USB Mass Storage Device. Right click on it. Select Properties, then go to Details. In the Details section, under Property, select Hardware ids. You'll then see the device id. It will be shown something like this: USB\VID_2A70&PID_9011&MI_01. From this you have to take the 2A70 code ~ the code between the first _ and &. Now go to desktop and create a new text document and copy paste this using your device id as shown:
Code:
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x2A70
Now open the Save As menu. In Save As type select All Files. Save the file as adb_usb.ini
Copy this .ini file from desktop and paste it in C:\Users\YourPCName\.android
Disconnect your phone, reboot your pc. Now with USB Debugging turned on, connect your phone to your pc, you'll surely get the permission thingy popup in your phone.
For completion:
If you DO NOT have access to your phone for any reason but still want to use ADB you can simply boot your phone into TWRP and follow these steps.
Windows:
1. Open %userprofile%\.android
2. Copy "adbkey.pub" to your phone (adb push %userprofile%\.android\adbkey.pub /sdcard/adb_keys)
3. Switch to your phone.
4. Go to Advanced > Open Terminal
5. Type in "stop adbd"
6. Move "adb_keys" from /sdcard to /data/misc/adb (mv /sdcard/adb_keys /data/misc/adb/adb_keys)
7. Type in "start adbd"
8. Switch to computer
9. Type "adb shell setprop persist.service.adb.enable 1"
10. Type "adb shell setprop persist.sys.usb.config mtp,adb"
11. Reboot your phone - DONE
Linux / Maybe Mac:
Same steps, but use "~/" instead of "%userprofile%"
Please note:
You may have to repeat the steps 1-7 after boot when still not having permissions so it makes sense to use cp (copy) instead of mv (move) and only repeat steps 5-7.
Edit: Please also check if your drivers are all installed and enabled.
Sent from my OnePlus 2 using XDA Labs
?k