Related
Hello, i am currently trying to root my sisters galaxy s 4g... Her Baseband is T949VUVKI1. Firmware is 2.3.5, Build Number is GINGERBREAD.VUVKI1. i remember flashing her phone to 2.3.5 and download mode working perfectly fine, and for some reason it wont go into download mode at all... the computer is not recognizing her phone either. YES, i do have usb drivers installed otherwise my galaxy s 4g wouldnt be recognized on my computer(odin specifically, not turning yellow). Please help, i have searched everywhere in the internet and tried almost everything... Volume up and down and plug charger, batter out volume up and down usb and battery in etc. PLEASE HELP!! Thank You in Advance.
Nvm
10c
1. Try reinstalling to drivers. Also make sure you're using the same USB port as Windows can be funny about it it sometimes.
2. if download mode is being difficult, go download the Android SDK from www.android.com. Install it, run it, and only download the platform tools. When that's done, open a command promt, CD to where the plaform tools installed (either c:\program files\Android\Android-sdk\platform-tools or c:\program files (x86)\Android\Android-sdk\platform-tools ), then issue the command: adb reboot download.
3. I suggest you check the dev section for bhundven's one-click collection. Uses Java and Heimdall vs. ODIN and works easily.
Sent from my SGH-T959V using XDA App
i have this issue 2.3.5 messed me up. Odin sees my phone in debug mode but not in download mode...using odin 1.85 sinse it is the only version that responds to my phone at all. help please!
Tytan0007 said:
i have this issue 2.3.5 messed me up. Odin sees my phone in debug mode but not in download mode...using odin 1.85 sinse it is the only version that responds to my phone at all. help please!
Click to expand...
Click to collapse
Get it back into download mode, go grab a bhundven's one-click. The one-clicks utilize Heimdall vs. ODIN, which means they use open-source USB drivers instead of the proprietary Samsung drivers. See if that enables the computer to see the phone. If so, flash the one-click
Should I uninstall the samsung drivers prior to using Heimdall's One-Click?
Tytan0007 said:
Should I uninstall the samsung drivers prior to using Heimdall's One-Click?
Click to expand...
Click to collapse
That's a good idea. Some people have reported conflicts between the drivers.
Why would only Odin 1.85 see my phone in USB Debugging and not in download mode? And all other Odin verisions never see my phone, no matter what state it is in... I am at work so I will give the one click another try when I get home. I never thought of uninstalling the Samsung drivers prior to install; however, I did use the one click method to no avail. However, Heimdall's one-click was able to see my device it just kept giving me a driver error. This is so crazy it might just work.
Tytan0007 said:
Why would only Odin 1.85 see my phone in USB Debugging and not in download mode? And all other Odin verisions never see my phone, no matter what state it is in... I am at work so I will give the one click another try when I get home. I never thought of uninstalling the Samsung drivers prior to install; however, I did use the one click method to no avail. However, Heimdall's one-click was able to see my device it just kept giving me a driver error. This is so crazy it might just work.
Click to expand...
Click to collapse
I wish I had a good answer. ODIN's a funny animal. I've been fortunate and not had any problems with it. I am hoping you are correct - maybe it was just a driver conflict. Let me know how it goes.
didn't work...
You could try downloading a terminal app from the market. Open the terminal and type:
reboot download
See if that does it.
***Update***
Okay, so Oneclick was not working at all no matter what I did with the drivers. However, in all my tinkering with it I installed the Samsung Driver, the Open Source one, and some gadget driver as well from oneclick.
Doing this put all these drivers in my computer. Then I went into my Device manager (Win 7) and looked at my USB driver and I uninstalled everything and went to the stock win 7 usb driver. Then I plugged my phone in and my computer began searching for drivers for this device when it decided that it would be a good idea to load all three drivers at once and voila my phone was then showing up on ODIN 1.85.
I then proceeded to flash my phone with a rom, probably the wrong one considering I was coming from 2.3.5 and my phone boot looped and then soft bricked(sorry if I used these term incorrectly, noobin it).
After, some nervous moment of scouring XDA I found the god-send of a post on getting in to download mode, using odin, and flashing stock 2.3.6 - thank you Raver(I believe). When I did this, my phone magically started obeying ODIN like a devout viking and is now running 2.3.6 superbly.
Keeping with my phones newly found viking heritage, I intend to figure out how to properly root it, update the kernal and modem(not sure which one is best), get CWM, and subsequesntly put in Valhalla Black.
Seeing as though this last rendevous with flashing caused me a little scare I may hold off and wait to see what the next big update is (maybe a port ICS variant) and then go with that.
Anyway, thank you Stephen for helping me out with this and to everyone in this post.
Here's some reading for you Tytan,
http://forum.xda-developers.com/wiki/Samsung_Galaxy_S_4G#FAQ_.28with_answers.29
PS: Unless you wanna brick your phone, do not flash anything that isn't intended for the SGH-T959V Samsung Galaxy S 4G. You're saying you wanna flash a Vibrant ROM. You can, if you want an expensive paperweight. Happy flashing!
2.3.5 may have been for vibrant...yeah I think I got lucky. I did it prior to knowing about xda.
Sent from my SGH-T959V using XDA App
Tytan0007 said:
didn't work...
Click to expand...
Click to collapse
How are you getting into download mode?
There was a post in another thread where the person apparently was using the power menu to get into download mode or maybe the adb command.
Have you tried both the old fashion volume +/- and plug in usb cable? Or the adb command?
Do you have access to another computer? Believe it or not sometimes just changing computers will make the difference.
Weird when I replied there was no posts other than the ones on the first page...oh well glad its working now.
Hey, I managed to brick my Infuse 4G trying to get Entropy's CM9 on it. I flashed it once and it was stuck on the samsung screen like it was suppose to but when I tried to go to CWM, I would get various colors, mostly blue and orange on the top and a big grey spot in the middle. I am trying to get it back to stock but I am having issues getting my computer to recognize that I plugged my phone in, neither Hermidall nor Odin recognize when my phone is plugged in in Download mode. I have downloaded Kies. Any suggestions?
If you had read any of the numerous other posts on this you would find that Kies creates issues so get rid of it and the colors are caused by the Froyo bootloaders on your phone, something that is fixed when you get GB bootloaders.
Watch this video for a how to on installing Heimdall
http://www.youtube.com/watch?v=sHyY7WHx4zc
Use this as a guide to actually installing Heimdall
http://forum.xda-developers.com/showthread.php?t=1524081 , many thanks to qkster.
If you do everthing correctly and completely, it will get you to stock GB.
From there you can go to ICS and then if you want, to JB. Do not skip ICS and try going to JB. Hope this helps.
Pony Express said:
If you had read any of the numerous other posts on this you would find that Kies creates issues so get rid of it and the colors are caused by the Froyo bootloaders on your phone, something that is fixed when you get GB bootloaders.
Watch this video for a how to on installing Heimdall
http://www.youtube.com/watch?v=sHyY7WHx4zc
Use this as a guide to actually installing Heimdall
http://forum.xda-developers.com/showthread.php?t=1524081 , many thanks to qkster.
If you do everthing correctly and completely, it will get you to stock GB.
From there you can go to ICS and then if you want, to JB. Do not skip ICS and try going to JB. Hope this helps.
Click to expand...
Click to collapse
Thanks for replying. The issue is that my computer and my friend's computer do no realize when I plug it into the computer in Download mode, on the of chance I sucessfully get it into that mode. I have tried with and without the Kies software.
Lefaid said:
Thanks for replying. The issue is that my computer and my friend's computer do no realize when I plug it into the computer in Download mode, on the of chance I sucessfully get it into that mode. I have tried with and without the Kies software.
Click to expand...
Click to collapse
No prob... it can be a process the first time... after that it is a breeze.
Make sure you have the Infuse drivers on your computer (I am assuning you are running windows) here, courtesy of bigjoe2675 are the drivers.
http://d-h.st/sKF
Pony Express said:
No prob... it can be a process the first time... after that it is a breeze.
Make sure you have the Infuse drivers on your computer (I am assuning you are running windows) here, courtesy of bigjoe2675 are the drivers.
http://d-h.st/sKF
Click to expand...
Click to collapse
I tried installing the setup file in the driver and the computer still does not recognize my phone.
I have been without Windows OS for a couple of months and will be w/o for another 3 weeks, sorry.
You must uninstall kies and do not have your phone plugged in to the computer during the driver install. If I remember correctly, once you download the zip with the drivers to the computer, you have to extract them and then run the setup. Once that is done, reboot the computer and plug your phone into a usb port on your puter that you know to be working.
Should you go forward and use Heimdall, use the same port each time.
Again, I am assuming you are using Windows. With Linux there is no need to install drivers, it recognizes the phone. With mac- no idea.
Maybe try this: http://forum.xda-developers.com/showthread.php?t=1683036
Can also use the search above -- 'computer won't recognize phone'
Pony Express said:
I have been without Windows OS for a couple of months and will be w/o for another 3 weeks, sorry.
You must uninstall kies and do not have your phone plugged in to the computer during the driver install. If I remember correctly, once you download the zip with the drivers to the computer, you have to extract them and then run the setup. Once that is done, reboot the computer and plug your phone into a usb port on your puter that you know to be working.
Should you go forward and use Heimdall, use the same port each time.
Again, I am assuming you are using Windows. With Linux there is no need to install drivers, it recognizes the phone. With mac- no idea.
Maybe try this: http://forum.xda-developers.com/showthread.php?t=1683036
Can also use the search above -- 'computer won't recognize phone'
Click to expand...
Click to collapse
I do have a Linux setup ready. Is there a way I can do it with Linux? Thanks again for being so helpful.
Edit: I have been toying with it on Ubuntu and am having the same issue of the computer not recognizing it as far as I can tell. I did get Heimdall working on it.
Lefaid said:
I do have a Linux setup ready. Is there a way I can do it with Linux? Thanks again for being so helpful.
Edit: I have been toying with it on Ubuntu and am having the same issue of the computer not recognizing it as far as I can tell. I did get Heimdall working on it.
Click to expand...
Click to collapse
The only thing you should have to do for Ubuntu to recognize the phone is enable usb debugging in settings on the phone and after that, enable it, most likely from your drop down menu on the phone.
Heimdall will be a .jar file - let me know if you need help getting it to open.
Pony Express said:
The only thing you should have to do for Ubuntu to recognize the phone is enable usb debugging in settings on the phone and after that, enable it, most likely from your drop down menu on the phone.
Heimdall will be a .jar file - let me know if you need help getting it to open.
Click to expand...
Click to collapse
Shame the phone is bricked right now ;/ . Back to my Windows computer. Thanks for trying to help but I think something is busted in my phone that isn't allowing it to tell the computer what it is or something. I don't know. I am going to try my friends computer to see if it is something weird with my own Thanks again for trying to help. If I find a solution, I will post it.
I used to have a rooted EVO 4G through work, but recently they switched me over to an iSheep, and as you can imagine I absolutely hate it. And since it’s for work they’ve installed AirWatch so I can’t jailbreak it. But I also have a TF101 that's currently not rooted.
I got my TF101 about a year ago and rooted it like every good android user should. But after about 6 months, I found a small hair line crack in the touch screen. I unrooted it and sent it in to ASUS for them to repair. I always keep my tablet closed in the docking station when it wasn’t in use. I then found this thread, http://forum.xda-developers.com/showthread.php?t=1498237 that stated this is why the screen cracked. So ASUS and I went back and forth for about a month before they finally covered it under warranty and repaired my tablet.
When I got my tablet back I found they upgraded it to 9.2.1.27. I connected it to a computer so I could reroot it, but my tablet is no longer detected by a computer. I tried two computers and two data cables. I’ve also tried all the methods for installing the drivers. I didn’t want to send it back to ASUS due to the issues I previously had with them. I’ve been following Thing O Doom’s thread, http://forum.xda-developers.com/showthread.php?t=1681155 because he stated he's working on a rooting apk, but he no longer has his TF101 so progress has been slow.
But in my searching I found this thread,http://www.transformerforums.com/fo...rmed-fix-gain-root-after-8-6-5-21-update.html that stated I can get the zip out of an old ASUS update and put that on my sdcard and let the tablet update itself to an older version. ASUS made an instruction sheet for manually updating with a zip, http://dlcdnet.asus.com/pub/ASUS/EeePAD/TF101G/e6754_TF101_Update_SOP.pdf. Once downgraded I could use RazerClaw http://forum.xda-developers.com/showthread.php?t=1345049 to root, and then flash a recovery, rom, etc.
Will this method work? I have to believe no, it just seems too easy. I haven’t tried it yet because I worried about bricking my tablet and not being able to fix it since it won’t connect to a computer.
Any response, opinion, recommendation, experience would be greatly appreciated.
I am not sure that will work. It worked when you had 8.6.5.X because it was upgrading to a "newer" version that is 8.6.6.X (for the TF101G).
Now you are on a 9.X, so it most likely will not work.
Have you tried APX mode? I used that to root from the .27 firmware without having to downgrade. Turn off your tablet, hold VOL UP and then press the POWER button for about 3 seconds. The screen will be black, but when you plug it into a computer it should be detected.
If it does work, use EasyFlasher and install a custom recovery (HIGHLY recommend TWRP over CWM).
Here is a guide I wrote on how to root and ROM: LINKY
frederuco said:
I am not sure that will work. It worked when you had 8.6.5.X because it was upgrading to a "newer" version that is 8.6.6.X (for the TF101G).
Now you are on a 9.X, so it most likely will not work.
Have you tried APX mode? I used that to root from the .27 firmware without having to downgrade. Turn off your tablet, hold VOL UP and then press the POWER button for about 3 seconds. The screen will be black, but when you plug it into a computer it should be detected.
If it does work, use EasyFlasher and install a custom recovery (HIGHLY recommend TWRP over CWM).
Here is a guide I wrote on how to root and ROM: LINKY
Click to expand...
Click to collapse
Thanks for the reply. I did try APX mode but I would get a message on both computers I tried stating the device was unrecognizable. I then tried to load the drivers but it still didn't work on either computer.
I guess you could try the other method. Since it is using stock recovery there is very little chance of bricking IMO. It will either install the older firmware, or it will not.
You may be able to use Wolf's tut for this...
benmatlock said:
You may be able to use Wolf's tut for this...
Click to expand...
Click to collapse
Thanks for the response, but I'm unable to successfully connect my tablet to a computer so I can't use ADB. I'm looking for a way to root it without a computer.
air adb, there's at least 1 good free one in the play store.
Lethe6 said:
air adb, there's at least 1 good free one in the play store.
Click to expand...
Click to collapse
Thanks for the response, I looked into that and I thought you had to be rooted for it to work. I'll look at it again.
akt27x said:
Thanks for the reply. I did try APX mode but I would get a message on both computers I tried stating the device was unrecognizable. I then tried to load the drivers but it still didn't work on either computer.
Click to expand...
Click to collapse
Just curious, did you reboot your PC after you installed/uninstalled the drivers?
I had this same problem once. What I did was pulled up Device Mgr and checked for APX drivers. If there was some, I uninstalled and Rebooted the PC. I downloaded these Universal Naked Drivers and saved them where I knew where they would be. I left the Device Mgr open and booted into APX mode. It asked to install drivers. I said yes and it failed. I then pointed it to the Naked Drivers and and it found them pretty easily. Once I saw APX pop up in Device Mgr, I was good to go. I then used EasyFlasher to flash back to .27 with Root. The link in the EasyFlasher OP for stock firmware is off for some reason. I posted the direct link near the last pages. Here it is.
akt27x said:
Thanks for the response, but I'm unable to successfully connect my tablet to a computer so I can't use ADB. I'm looking for a way to root it without a computer.
Click to expand...
Click to collapse
You don't /need/ adb to root it this way, all you need is a terminal interface on your tablet. If you can download and unpack the zip file containing the blob for whatever recovery you wanna use, then link the mmcblk0p4 to tmp, you should be able to be good to go after a dd and reboot.
--edit--
start here: Instructions - Method 2 - UnRooted
then replace step two with "download terminal emulator from the play store"
then replace step three with 'open terminal emulator'
continue with the rest of the tut, using whatever recovery you want (i use Rogue XM)
frederuco said:
I guess you could try the other method. Since it is using stock recovery there is very little chance of bricking IMO. It will either install the older firmware, or it will not.
Click to expand...
Click to collapse
I tried this and you're right it didn't install the older firmware. It looked like it was going to because the status bar was moving at the bottom, but after a few minutes it went to an android laying down with his guts open and a exclamation mark above him.
benmatlock said:
You don't /need/ adb to root it this way, all you need is a terminal interface on your tablet. If you can download and unpack the zip file containing the blob for whatever recovery you wanna use, then link the mmcblk0p4 to tmp, you should be able to be good to go after a dd and reboot.
--edit--
start here: Instructions - Method 2 - UnRooted
then replace step two with "download terminal emulator from the play store"
then replace step three with 'open terminal emulator'
continue with the rest of the tut, using whatever recovery you want (i use Rogue XM)
Click to expand...
Click to collapse
I think I've tried this. I have a terminal emulator installed and I followed some instructions about entering things like this in but I think I got a message stating access denied. But I'll try it again tonight and reply back with the results.
Re: [Q] Possible Downgrade to Root
Using wolf's instructions I tried this with a terminal app on my tablet and got the following.
[email protected]:/ $ mv /data/local/tmp /data/local/tmp.bak
failed on '/data/local/tmp' - Permission denied
I then tried this and got the following.
[email protected]:/ $ dd if=/sdcard/recoveryblob.bin of=/dev/block/mmcblk0p4
/dev/block/mmcblk0p4: cannot open for write: Permission denied
Sent from my Transformer TF101 using XDA Premium HD app
Woody said:
Just curious, did you reboot your PC after you installed/uninstalled the drivers?
I had this same problem once. What I did was pulled up Device Mgr and checked for APX drivers. If there was some, I uninstalled and Rebooted the PC. I downloaded these Universal Naked Drivers and saved them where I knew where they would be. I left the Device Mgr open and booted into APX mode. It asked to install drivers. I said yes and it failed. I then pointed it to the Naked Drivers and and it found them pretty easily. Once I saw APX pop up in Device Mgr, I was good to go. I then used EasyFlasher to flash back to .27 with Root. The link in the EasyFlasher OP for stock firmware is off for some reason. I posted the direct link near the last pages. Here it is.
Click to expand...
Click to collapse
This weekend I tried to install the drivers again. I first went through the control panel and device manager and deleted anything that said android and asus, then rebooted my computer. I then tried to install PDANet because I read that it'll install the drivers needed and if you're having a problem it's an easy way to install them. During the PDANet install it told me to plug my transformer in to load the drivers. When I did it said it was installing new drivers but then it said they didn't install. My transformer came up as an unknown device in device manager.
I then went through and deleted the unknown device and checked in the control panel again, then rebooted my computer. I then put my tablet in APX mode to try and get it to load the drivers. Again it didn't install them and my transformer came up as an unknown device. I deleted the unknown device agian, rebooted, and went to ASUS website and installed ASUS Sync. When it finished I rebooted and then started ASUS Sync. Again when I connected my transformer to my computer it said it was loading the drivers, then it failed, and the computer showed my transformer as an unknown device. ASUS Sync also stated there was no device connected to it.
All the reading I've been doing, it seems like there are some other people experiencing the same issues I am, and I haven't seen where anybody has posted a solution. If anybody has any input please let me know.
I think I'm getting closer. I downloaded WLanAdb from the play store and followed the directions and downloaded the needed files to my computer. In the command prompt I type "WLanAdbTerminal devices" and my tablet will show in the list of devices. But WLanAdb is only setup to except a few commands, the main purpose of the app is for pushing files. It was the only wireless ADB app that I could find that didn't require root.
I then found SSHDroid in the play market and I downloaded putty to my computer. I connect to my computer using that. When I type "adb devices" I get a mesage that states
daemon not running. starting it now on port 5038
daemon started successfully
List of devices attached
I then left putty and went back to the command prompt and typed "adb connect (with my ip address and port from SSHDroid)" and it said it connected to that ip address and port. I then type "adb devices" and there are no devices listed.
Again I think I'm very close to getting my tablet connected wirelessly to adb. I think there is just one simply thing I'm missing. Any help would be greatly appreciated.
I'll continue to update this thread until my tablet is rooted or I reach a dead end, so this will be a reference for anybody experiencing the same issues as me.
Thanks in advance.
akt27x, did you ever come to a solution?
presbypenguin said:
akt27x, did you ever come to a solution?
Click to expand...
Click to collapse
I haven't. I'm now trying to make a Linux boot flash drive to see if I can get my tablet to connect that way, since I've read that Linux doesn't require drivers. I downloaded LinuxLive USB Creator but haven't had the time to try it yet.
I did a really, really dumb thing a few months ago. I flashed a wrong something or another to fix an issue I had with my keyboard crashing after flashing another wrong thing..
Anywho, I couldn't get the damn keyboard to stop crashing for the life of me, so I set out to FORMAT/ CLEAR EVERYTHING ON MY PHONE. Yikes.
At this point, I can boot into recovery(CWM) and DL mode, but my PC will not recognize my phone at all. I installed your S3 toolkit v7.0, hoping it would help, but nay.
I cannot boot fully into Android to allow usb debugging, etc.
I can mount and unmount internal sd, cache, etc, but no drivers are being installed because it is not being recognized.
I've uninstalled Kies, etc.
HALP!HALP!
Daniel_NC said:
I did a really, really dumb thing a few months ago. I flashed a wrong something or another to fix an issue I had with my keyboard crashing after flashing another wrong thing..
Anywho, I couldn't get the damn keyboard to stop crashing for the life of me, so I set out to FORMAT/ CLEAR EVERYTHING ON MY PHONE. Yikes.
At this point, I can boot into recovery(CWM) and DL mode, but my PC will not recognize my phone at all. I installed your S3 toolkit v7.0, hoping it would help, but nay.
I cannot boot fully into Android to allow usb debugging, etc.
I can mount and unmount internal sd, cache, etc, but no drivers are being installed because it is not being recognized.
I've uninstalled Kies, etc.
HALP!HALP!
Click to expand...
Click to collapse
If you boot into DL mode and run odin on your PC does it fail to see the device?
apacseven said:
If you boot into DL mode and run odin on your PC does it fail to see the device?
Click to expand...
Click to collapse
I'm waiting on my PC to free up again(currently on a Mac). I had not tried Odin because in the past I was unable to mount internal SD, which I understood was keeping it from being recognized. I instead thought the Toolkit would do the trick automatically, though I most likely had the wrong idea. Everything is mountable again (for some odd reason), so I will give it a go.
Could I accomplish downloading drivers and flashing rom to device using Odin alone? Or should I use the Toolkit?
Thanks!
Daniel_NC said:
I'm waiting on my PC to free up again(currently on a Mac). I had not tried Odin because in the past I was unable to mount internal SD, which I understood was keeping it from being recognized. I instead thought the Toolkit would do the trick automatically, though I most likely had the wrong idea. Everything is mountable again (for some odd reason), so I will give it a go.
Could I accomplish downloading drivers and flashing rom to device using Odin alone? Or should I use the Toolkit?
Thanks!
Click to expand...
Click to collapse
Installing the drivers is independent from using odin. Install the drivers on the PC, fire up odin, connect phone (that has been booted into DL mode) and see if it connects. If it does, just flash a stock image and you are back in business.
You can use this driver http://d-h.st/vMk
apacseven said:
Installing the drivers is independent from using odin. Install the drivers on the PC, fire up odin, connect phone (that has been booted into DL mode) and see if it connects. If it does, just flash a stock image and you are back in business.
You can use this driver ...
Thanks!! I'll give it a shot now.
Click to expand...
Click to collapse
apacseven said:
Installing the drivers is independent from using odin. Install the drivers on the PC, fire up odin, connect phone (that has been booted into DL mode) and see if it connects. If it does, just flash a stock image and you are back in business.
You can use this driver......
Click to expand...
Click to collapse
Odin is not recognizing the device. Should I unmount or mount anything on the device for this to work properly? I have drivers installed.
How do I install recovery on a soft bricked galaxy S7 edge. Sprint, that the boooafsr is still locked on. I can access recovery mode and device is recognized when i click apply update from adb, but it disabled updates from external sources. So they all fail. I didn't install recovery beforehand and now I'm in a quadary. Does anyone know if it's even possible to install recovery at this point? And if so, how?
ZiggyJapheth said:
How do I install recovery on a soft bricked galaxy S7 edge. Sprint, that the boooafsr is still locked on. I can access recovery mode and device is recognized when i click apply update from adb, but it disabled updates from external sources. So they all fail. I didn't install recovery beforehand and now I'm in a quadary. Does anyone know if it's even possible to install recovery at this point? And if so, how?
Click to expand...
Click to collapse
You are saying you want to install recovery, but you can reboot to recovery (?) if you mean that how you can recover your device see the exact build number in recovery screen, download the firmware file and flash it through Odin, tap on "reboot bootloader", this will lead you to Odin, also you can enter to it manually.
O
SubwayChamp said:
You are saying you want to install recovery, but you can reboot to recovery (?) if you mean that how you can recover your device see the exact build number in recovery screen, download the firmware file and flash it through Odin, tap on "reboot bootloader", this will lead you to Odin, also you can enter to it manually.
Click to expand...
Click to collapse
Ok, now we're talking. I can see you know what your speaking about. I meant to say, how can I install a recovery app , like TWRP or clockworkmid. Ok i can enter download mode easily enough by clicking the side and power buttons, however, the device isn't recognized by my moto E5 anymore. It's only recognized when i click apply update from adb....even tho when i try to sideload anything that way it ultimately aborts saying updates from external sources is disabled. So...back to Odin.its only runable from a windows OS....is there a version of Odin i can run on a Motorola and flash from it onto my softbricked Samsung Galaxy that's connected via otg cable? Thanks for all the time and insight by the way
ZiggyJapheth said:
Ok, now we're talking. I can see you know what your speaking about. I meant to say, how can I install a recovery app , like TWRP or clockworkmid. Ok i can enter download mode easily enough by clicking the side and power buttons, however, the device isn't recognized by my moto E5 anymore. It's only recognized when i click apply update from adb....even tho when i try to sideload anything that way it ultimately aborts saying updates from external sources is disabled. So...back to Odin.its only runable from a windows OS....is there a version of Odin i can run on a Motorola and flash from it onto my softbricked Samsung Galaxy that's connected via otg cable? Thanks for all the time and insight by the way
Click to expand...
Click to collapse
If this is the case and your issue is with a Motorola e5, then it is off-topic to give support here.
Just a side note, Odin is exclusive for Samsung devices, Motorola devices has its own way, you have here all that you want https://forum.xda-developers.com/c/moto-e5.7642/
But if you are trying to revive a Samsung device using your Motorola by installing a flashing tool app as a Windows fashion then you are out of luck, you should need a PC for that.
SubwayChamp said:
If this is the case and your issue is with a Motorola e5, then it is off-topic to give support here.
Just a side note, Odin is exclusive for Samsung devices, Motorola devices has its own way, you have here all that you want https://forum.xda-developers.com/c/moto-e5.7642/
But if you are trying to revive a Samsung device using your Motorola by installing a flashing tool app as a Windows fashion then you are out of luck, you should need a PC for that.
Click to expand...
Click to collapse
SubwayChamp said:
If this is the case and your issue is with a Motorola e5, then it is off-topic to give support here.
Just a side note, Odin is exclusive for Samsung devices, Motorola devices has its own way, you have here all that you want https://forum.xda-developers.com/c/moto-e5.7642/
But if you are trying to revive a Samsung device using your Motorola by installing a flashing tool app as a Windows fashion then you are out of luck, you should need a PC for that.
Click to expand...
Click to collapse
Yes that's exactly what I'm attempting. See, i had my Samsung Galaxy S7 edge which is soft bricked in recovery mode, while connected to a moto E5 play, which i used as a master device to send adb commands to my Samsung. I am trying to recover my Galaxy. I know that Odin only works on windows, and my inability to secure access to a PC is a major obstacle. The circumstances causing that are extremely varied and complicated, lol, however, impossible. So...i have other androids to serve as the master device or i can download zip files on to SD cards and try to apply updates from them through recovery mode,tho it says those options are disabled when i try. But those are my options, bro. Is there no way to run Odin or a android version of Odin to accomplish this? Can I somehow run a windows OS on an Android just for the purpose of running Odin 3 to flash firmware on my bricked Galaxy?
ZiggyJapheth said:
Yes that's exactly what I'm attempting. See, i had my Samsung Galaxy S7 edge which is soft bricked in recovery mode, while connected to a moto E5 play, which i used as a master device to send adb commands to my Samsung. I am trying to recover my Galaxy. I know that Odin only works on windows, and my inability to secure access to a PC is a major obstacle. The circumstances causing that are extremely varied and complicated, lol, however, impossible. So...i have other androids to serve as the master device or i can download zip files on to SD cards and try to apply updates from them through recovery mode,tho it says those options are disabled when i try. But those are my options, bro. Is there no way to run Odin or a android version of Odin to accomplish this? Can I somehow run a windows OS on an Android just for the purpose of running Odin 3 to flash firmware on my bricked Galaxy?
Click to expand...
Click to collapse
I know you can use other device as a master to serve some files but if the stock Samsung recovery doesn't allow updates this way then it is out of reach, but you should try it using ADB sideload not updates from external devices BUT only you could flash this way official updates not TWRP nor any custom zip, if you have some OTA update you should try it using an external SD Card if I don't remember bad your device has a slot for that.
Odin only can run in Windows PC, and its equivalent for Linux is Heimdall, there is not actually a version that completely support into Android.
Probably you could further investigate something like "Running Linux on Android devices", there were some Linux distros in Play Store that can boot, this way you could install Heimdall and get it a try using download mode, but this just theoretically, I didn't try it my self, fixing it through a PC sometimes is hard enough that not even think of this way.
SubwayChamp said:
I know you can use other device as a master to serve some files but if the stock Samsung recovery doesn't allow updates this way then it is out of reach, but you should try it using ADB sideload not updates from external devices BUT only you could flash this way official updates not TWRP nor any custom zip, if you have some OTA update you should try it using an external SD Card if I don't remember bad your device has a slot for that.
Odin only can run in Windows PC, and its equivalent for Linux is Heimdall, there is not actually a version that completely support into Android.
Probably you could further investigate something like "Running Linux on Android devices", there were some Linux distros in Play Store that can boot, this way you could install Heimdall and get it a try using download mode, but this just theoretically, I didn't try it my self, fixing it through a PC sometimes is hard enough that not even think of this way.
Click to expand...
Click to collapse
Nothing wrong at all with theory, as it forms the basis of every action. And I'm about to try that next. Check this out tho. That sideload thing that's entertwined with apply updates via adb. See I'll try to attach picture, but when in recovery i click apply updates via adb it asks to sideload files. That's the one way i can get the device to register . Abd even send files to the device. It's just that they don't install as it says updates from external sources is disabled. I feel you are correct tho, about Odin mode, i can put the phone in download mode but it just doesn't register on the otg apps, maybe because it must be Odin. So yeah i gotta find a way to run Odin on Android. Listen they do have a version of Odin that runs on Android , called mobile Odin...but i think it only flashes to the device that it's on....not to other devices....
ZiggyJapheth said:
Nothing wrong at all with theory, as it forms the basis of every action. And I'm about to try that next. Check this out tho. That sideload thing that's entertwined with apply updates via adb. See I'll try to attach picture, but when in recovery i click apply updates via adb it asks to sideload files.
Click to expand...
Click to collapse
Yes, it's a two-way road, while your Samsung is waiting a file to be transferred you have to put in somewhere in the other device adb sideload packagename.zip this is how ADB sideload works, in Windows you open a CMD through ADB/fastboot and send a package.zip to the device so your Samsung device accepts this package.zip plus as I said you previously it has to be an official update something like an OTA firmware. Resuming, you are sending nothing to the device.
ZiggyJapheth said:
That's the one way i can get the device to register . Abd even send files to the device. It's just that they don't install as it says updates from external sources is disabled. I feel you are correct tho, about Odin mode, i can put the phone in download mode but it just doesn't register on the otg apps, maybe because it must be Odin.
Click to expand...
Click to collapse
No, your Motorola device is not capable to detect device just with OTG support, you need the binaries to run on it either for ADB or fastboot or download mode.
ZiggyJapheth said:
So yeah i gotta find a way to run Odin on Android. Listen they do have a version of Odin that runs on Android , called mobile Odin...but i think it only flashes to the device that it's on....not to other devices....
Click to expand...
Click to collapse
Odin for Android, the paid version worked same way that Odin through PC sending device to download mode and then applying an update, but it is deprecated as per I know.
Your only way by now would be trying to get ADB working correctly on your Motorola through a terminal or running a simpler distro like Ubuntu that can boot on Android, sometime ago I boot some of them from Play Store, but I didn't try so much.
K
SubwayChamp said:
Yes, it's a two-way road, while your Samsung is waiting a file to be transferred you have to put in somewhere in the other device adb sideload packagename.zip this is how ADB sideload works, in Windows you open a CMD through ADB/fastboot and send a package.zip to the device so your Samsung device accepts this package.zip plus as I said you previously it has to be an official update something like an OTA firmware. Resuming, you are sending nothing to the device.
No, your Motorola device is not capable to detect device just with OTG support, you need the binaries to run on it either for ADB or fastboot or download mode.
Odin for Android, the paid version worked same way that Odin through PC sending device to download mode and then applying an update, but it is deprecated as per I know.
Your only way by now would be trying to get ADB working correctly on your Motorola through a terminal or running a simpler distro like Ubuntu that can boot on Android, sometime ago I boot some of them from Play Store, but I didn't try so much.
Click to expand...
Click to collapse
Ok, thanks so much,I'm about to download mobile Odin first , altho i think i tried that and it needed SuperSU permissions which the moto E5 isn't rooted...so looks like I'm about to research your other suggestions. It gives me a direction to experiment in. Again,thanks so much. Oh one last thing.. but it is sending files to the phone in sideload form. Because before it aborts, the phone I'm sending files from goes through a percentage until 100% of any given file is sent. And on the galaxy i see it received because it says installing this or that zip file before saying...updates fron external sources disabled and aborting mission. I'll be back. Thanks for the time bro
SubwayChamp said:
Yes, it's a two-way road, while your Samsung is waiting a file to be transferred you have to put in somewhere in the other device adb sideload packagename.zip this is how ADB sideload works, in Windows you open a CMD through ADB/fastboot and send a package.zip to the device so your Samsung device accepts this package.zip plus as I said you previously it has to be an official update something like an OTA firmware. Resuming, you are sending nothing to the device.
No, your Motorola device is not capable to detect device just with OTG support, you need the binaries to run on it either for ADB or fastboot or download mode.
Odin for Android, the paid version worked same way that Odin through PC sending device to download mode and then applying an update, but it is deprecated as per I know.
Your only way by now would be trying to get ADB working correctly on your Motorola through a terminal or running a simpler distro like Ubuntu that can boot on Android, sometime ago I boot some of them from Play Store, but I didn't try so much.
Click to expand...
Click to collapse