[Q] Not able to root on Mac OSX - Galaxy S III Q&A, Help & Troubleshooting

I have the been trying all different methods (primarily OSX, but also Windows and Ubuntu [through VMWare Fusion]) and I have recently run into a wall. Normally in OSX I get the “Failed to initialise protocol” error, Windows it Odin does not even recognize the device, and Ubuntu the “failed to detect compatiable Download-Mode” error keeps coming up even after rebooting.. Would i need to wipe data/factory reset in the 3e recovery? (i’d prefer not to, but I want a ROOT!) This is my third Android device and you have helped me through it all on the previous 2!
Sent from my GT-I9300 using Tapatalk 2

Bump, please help
Sent from my GT-I9300 using Tapatalk 2

failed to detect compatiable Download-Mode” error keeps coming up even after rebooting
Click to expand...
Click to collapse
Are you _SURE_ you are in download mode? It seems like you simply reboot your phone and expect it to work.
Download mode can be reached by:
- Unplug phone
- Power off your phone
- Press and hold Vol-Down and Menu button
- Press Power button until Logo appears
- Keep other 2 buttons pressed until text appears on the screen
- Follow on-screen instructions
- Plug phone into computer

Here is a good guide for rooting on Mac OSX. Follow it and you should have no problems.

Related

[Q] Can't root, tried everything, need some help

Ok, So i'm having a heaping pile of rooting problems. Brand new phone. Installed and updated Kies on my computer.
First problem: can't enter download mode without having usb plugged in. Volume down+power and volume up+ power just turns the phone on again. volume up+ volume down+ power enters 3e recovery. If I hold both volume buttons and plug the usb in, then it goes to the "press volume up to enter download mode" screen and that's the only way i can do it.
Second Problem: perhaps due to the fact that i have to plug in my usb in order to get to usb mode, superone click and odin don't recognize my phone. When i open those programs it doesn't show "[0:COM8]" (or something similar) like it should.
Third Problem: many methods for rooting I have found want me to use Odin 1.x (usually odin3 v1.85) I have windows 7 prompt me for permission to use that program. Then, I get a small dialogue box that says "Odin3" followed by several characters in what appears to be japanese. The only option on that box is "ok" and when you press that the box goes away and odin never opens...
I have not found a root method that doesn't run headlong into one or more of those issues. Any help would be great, I have no idea why this is so difficult.
justlaxin13 said:
Ok, So i'm having a heaping pile of rooting problems. Brand new phone. Installed and updated Kies on my computer.
First problem: can't enter download mode without having usb plugged in. Volume down+power and volume up+ power just turns the phone on again. volume up+ volume down+ power enters 3e recovery. If I hold both volume buttons and plug the usb in, then it goes to the "press volume up to enter download mode" screen and that's the only way i can do it.
Second Problem: perhaps due to the fact that i have to plug in my usb in order to get to usb mode, superone click and odin don't recognize my phone. When i open those programs it doesn't show "[0:COM8]" (or something similar) like it should.
Third Problem: many methods for rooting I have found want me to use Odin 1.x (usually odin3 v1.85) I have windows 7 prompt me for permission to use that program. Then, I get a small dialogue box that says "Odin3" followed by several characters in what appears to be japanese. The only option on that box is "ok" and when you press that the box goes away and odin never opens...
I have not found a root method that doesn't run headlong into one or more of those issues. Any help would be great, I have no idea why this is so difficult.
Click to expand...
Click to collapse
for one. you have to plug usb in to get into download mode.
for two. you have to hold volume up and volume down, then plug the usb in to get into download mode.
exactly, but then my phone isn't recognized in odin or anything else for that matter. And i have seen numerous instructions for this phone that tell you to enter download mode with Volume down+ power alone...
justlaxin13 said:
Ok, So i'm having a heaping pile of rooting problems. Brand new phone. Installed and updated Kies on my computer.
Click to expand...
Click to collapse
That should take care of the driver issue, but it's still possible (an outside chance) you will have to uninstall and reinstall the usb driver.
First problem: can't enter download mode without having usb plugged in. Volume down+power and volume up+ power just turns the phone on again. volume up+ volume down+ power enters 3e recovery. If I hold both volume buttons and plug the usb in, then it goes to the "press volume up to enter download mode" screen and that's the only way i can do it.
Click to expand...
Click to collapse
You are trying to use the I9100 key combinations. The one that works for you is the only one that works on the I777.
Second Problem: perhaps due to the fact that i have to plug in my usb in order to get to usb mode, superone click and odin don't recognize my phone. When i open those programs it doesn't show "[0:COM8]" (or something similar) like it should.
Click to expand...
Click to collapse
Could be a driver problem or is could be a faulty connection of your usb port or cable. Try a different usb port, try a different cable.
Third Problem: many methods for rooting I have found want me to use Odin 1.x (usually odin3 v1.85) I have windows 7 prompt me for permission to use that program. Then, I get a small dialogue box that says "Odin3" followed by several characters in what appears to be japanese. The only option on that box is "ok" and when you press that the box goes away and odin never opens...
Click to expand...
Click to collapse
Odin3 v1.85 work fine on Windows 7. But you don't need Odin3 v1.85 if you are using the One-click Downloader executable, which is also an Odin. If you want to use Odin3 v1.85, delete the one you have and redownload it.
I have not found a root method that doesn't run headlong into one or more of those issues. Any help would be great, I have no idea why this is so difficult.
Click to expand...
Click to collapse
Once you get Odin to recognize your phone, you will be fine.
justlaxin13 said:
exactly, but then my phone isn't recognized in odin or anything else for that matter. And i have seen numerous instructions for this phone that tell you to enter download mode with Volume down+ power alone...
Click to expand...
Click to collapse
Not familiar with it, but those may be for I9100. Download mode on I777 is, as previously mentioned, hold both volume buttons, not power, while powered off, and then plug in. If your device isn't recognized in odin, try going to the samsung site and download the newest drivers there
Edit: ninja'd
Sent from my SGH-I777 using XDA App
Holding power to enter download mode is not valid for I9100 either.
justlaxin13 said:
exactly, but then my phone isn't recognized in odin or anything else for that matter. And i have seen numerous instructions for this phone that tell you to enter download mode with Volume down+ power alone...
Click to expand...
Click to collapse
those numerous instructions are wrong then dude. i just told you how to get into download mode for the i777. do you have an i777, or an i9100???
Watch
http://youtu.be/9YMtkkRpgEY
I have an I777 for sure. so not my problem boils down to odin not recognizing my phone when in download mode. Or, when i try to use DooMLorD V3 root... i have seen that highly recommended but it doesn't recognize that my device either.
You need to update your driver. get it from the Samsung site
Sent from my SAMSUNG-SGH-I777 using Tapatalk
That's what I'm working on, but even that can't be easy. The .exe file to update the drivers has a problem opening and windows shuts it down...ugh.
Are you opening Odin with your phone already plugged in on dl mode... Mine never works unless I open Odin first then plug my phone in...
Sent from my SGH-I777 using xda premium
^this. Odin must be open first then go into download mode on the phone. Doing it another order, Odin won't always recognize your device
Sent from my SGH-I777 using XDA App
Rob_Wing said:
Are you opening Odin with your phone already plugged in on dl mode... Mine never works unless I open Odin first then plug my phone in...
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
+1. Have Odin already open before you even start putting your phone in download mode.
Or try another computer. You could always just use Odin 1.85 and flash a kernel tar file, such as entropy or siyah.

Bricked my MSI Enjoy 10" Plus

I've got an MSI Windpad Enjoy 10" Plus (http://www.msi.com/product/windpad/Enjoy-10-Plus.html) and I tried to flash it this ROM (http://forum.xda-developers.com/showthread.php?t=1540616).
The rom is for MSI Windpad Enjoy 10", while mine is called Enjoy 10" Plus. So GG, I think I got owned. So retarded you don't even have to tell me.
Now whenever I try to turn on the tablet, it would simply vibrate, show the logo and then turns off. PC doesn't detect it.
However, I tried holding Power button + Reset button together, the PC detects it, but it's unknown and it can't identify it (even though I have MSI's drivers installed and all).
...Any ideas on how to overcome it?
I'm going to sleep now, and will check tomorrow. Thanks in advance.
[UPDATE] 2/22/2013 11:00pm gmt
I'm able to boot it only if I have it plugged in. I can only use Power + Volume controllers + Reset buttons. I can enter Recovery Mode but I cannot confirm/click on any selection.
Tablet does not get recognized by the computer in "Flashing Mode".
I forced to install the driver for the "Flashing mode" when the tablet is in recovery mode but programs like MSIFlashtool, RKBatchTool, RKAdnroid. (not sure if i correcly used the last 2... but whatever)
spilot said:
I've got an MSI Windpad Enjoy 10" Plus (http://www.msi.com/product/windpad/Enjoy-10-Plus.html) and I tried to flash it this ROM (http://forum.xda-developers.com/showthread.php?t=1540616).
The rom is for MSI Windpad Enjoy 10", while mine is called Enjoy 10" Plus. So GG, I think I got owned. So retarded you don't even have to tell me.
Now whenever I try to turn on the tablet, it would simply vibrate, show the logo and then turns off. PC doesn't detect it.
However, I tried holding Power button + Reset button together, the PC detects it, but it's unknown and it can't identify it (even though I have MSI's drivers installed and all).
...Any ideas on how to overcome it?
I'm going to sleep now, and will check tomorrow. Thanks in advance.
Click to expand...
Click to collapse
i dont think that that is called brick
anyways go download Odin and the stock image for your phone (in tar format)(just search on XDA)
put phone into download mode nd open odin
select PDA and select the tar file u downloaded
click start and it should take u back to stock
forgot if this unroots ur phone or not so u might have to root again.
Jack Jake said:
i dont think that that is called brick
anyways go download Odin and the stock image for your phone (in tar format)(just search on XDA)
put phone into download mode nd open odin
select PDA and select the tar file u downloaded
click start and it should take u back to stock
forgot if this unroots ur phone or not so u might have to root again.
Click to expand...
Click to collapse
This is not Samsung or a phone. Read what you are told
If you have a splash screen, you are not bricked. Does adb recognise your tablet? Can you access any recovery/download mode?
Sent from my ARCHOS 80G9 using Tapatalk HD
Quinny899 said:
This is not Samsung or a phone. Read what you are told
If you have a splash screen, you are not bricked. Does adb recognise your tablet? Can you access any recovery/download mode?
Click to expand...
Click to collapse
ADB doesn't recognize it. I tried holding Power + Reset button and did 'adb devices' on Ubuntu and it didn't show anything. On Windows, if I held these 2 buttons, it would show an unknown device in Device Manager. (Mind you, I don't have the Android SDK on Windows, just Linux.)
I can't access any recovery/download mode. Any combination of buttons (Power+VolDown, Power+VolUp/VolDown, Power+VolUP, Power+Home, Power+Back, Power+Settings) would do nothing.
-----------------------------------------------------------------------------------------------------
This what it does when I press Power + Reset Button with a needle. It boots up, splash screen, and stays on black screen (Btw, in this stage, it's Unknown Device in Windows Manager).Once I let go of Reset or Power button, it shuts down.
Turning it on without holding Reset, it would show splash screen, black screen and turns off in about 2 seconds.
Bump.
I've tried playing with it for some time. I can't get it to stay working without pressing power+reset buttons, it always shuts off...
Go to the device website, and download section, get the latest firmware and forget to download the flash driver.
Follow the steps that in firmware folder after unzip it, and you'll get your tablet on
Sent from my Enjoy 10 Plus using xda app-developers app
mramzi said:
Go to the device website, and download section, get the latest firmware and forget to download the flash driver.
Follow the steps that in firmware folder after unzip it, and you'll get your tablet on
Click to expand...
Click to collapse
... I was trying all the time to get it work on the PC without plugging the charger. Anyways~
(Tablet's turned off), I plugged charger, I plugged USB, I turned on the tablet and viola it actually worked and booted into OS. However, no buttons work AT ALL, and touch input doesn't work as well.
I tried to get into Recovery Mode and it worked, but I can go up/down using VolUp/VolDow buttons but I cannot click on any thing because the home button don't work nor any other.
Only Power + VolUp + VolDown + Reset buttons work... What to do now?
TL;DR I want to click on 'Update from SD Card' from the Android Recovery but I couldn't get the 'home' button to click enter on the selection. So what's the solution?
bump.
updates:
I tried to place the firmware from the official website as update.img on an SD Card and placed it in the tablet and went into the recovery mode and selected the 'update from sd card' but i couldn't click it. I tried to tap power, home, search, settings and back and nothing worked.
what I've got up until now:
I can boot into the ROM / RecoveryMod as long as I have the charger plugged in the tablet.
For Ubuntu, when I use the command $ tail -f /var/log/syslog and plug in my tablet, it shows this log http://pastebin.com/pBpBUA2Q (it identifies the tablet) [note, the tablet is booted into the ROM]
Also, if I'm in the recovery mode and I plug in the tablet, it would enumerate the USB... ~,~
Bump
bump
spilot said:
bump
Click to expand...
Click to collapse
Please don't bump your thread more than once in 24 hours, it's against the rules
Sent from my Galaxy Nexus using Tapatalk HD
bump
Hello,
I know it has been long since this thread stopped.
I'm currently in his shoes and for the life of me cannot find anything on the web to help me solve my problem.
My MSI Enjoy 10" Plus was flashed with the wrong MSI Enjoy 10" update. Now the tablet only turns on when in "Recovery Mode", but selecting in that mode is not possible using 10" Plus' buttons. Is there anyone from you good people that can help? Please? Thanks.
Uhm...bump?
Bump? Need help from the experts here. Please. I'm desperate.
Thank you very much in advance.

[Q] Is my phone bricked? Or do I still have a chance?

Plz Help if you can,
I have rooted my Verizon Note 2 and unlocked the boot loader and installed mean-bean - it worked awesome and should have stayed with it but everything went so well I wanted to try another ROM. The new ROM failed so I went back to mean-bean by selecting the backup I made on my sd card before I tried another ROM. My phone stuck on the "Samsung Note 2" boot up screen and never moved after mins. I did the "power + volume down + Power" and I get a warning asking me to press the volume up key to download a custom ROM or the volume down key to cancel. When I press the volume down button I get stuck at the Samsung note 2 screen, if I press volume up I get stuck at the downloading screen. When I connect the phone to my computer I can hear a ding in windows 7 64bit but am unable to see the device. I have read some of the forums and have downloaded a stock rom as suggested by several of them and oden 3.07. Oden does not show a com port as the posts suggest and my computer does not see the device. The forums that deal with not seeing your device says to download and install the latest usb drivers. I have re-downloaded the latest Samsung usb drivers and rebooted my computer. The computer still just makes a noise when i plug my phone in but does not see it in oden or in the computer. I have read so many forums and other peeps seem to still see their phone in oden. Maybe my phone is now trashed do I still have a chance or is it done. can anyone help a noob plz?
Thanks in advance.
Quick notes:
1: phone only boots to samsung note 2 screen
2: Phone will only go to download mode when I try to go to recovery
3: can hear ding on my computer when I connect but can't find see device
4: Oden does not see device
Try Odin 1.87
Curtis Craig said:
Try Odin 1.87
Click to expand...
Click to collapse
I will try that when I get home. all day at work and can't wait to try it. Thank you for the responce.
pacoabq said:
I will try that when I get home. all day at work and can't wait to try it. Thank you for the responce.
Click to expand...
Click to collapse
Thank you, but it still did not see the device, or at least the com port did not show anything. I can see it in my device manager though. Any other suggestions?
pacoabq said:
Thank you, but it still did not see the device, or at least the com port did not show anything. I can see it in my device manager though. Any other suggestions?
Click to expand...
Click to collapse
Have you been running Odin as admin?
Sent from my SGH-T889 using xda app-developers app
kintwofan said:
Have you been running Odin as admin?
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
yes. I wish had not been though, would have been great to have fixed it. Any other suggestions? Plz
pacoabq said:
Plz Help if you can,
I have rooted my Verizon Note 2 and unlocked the boot loader and installed mean-bean - it worked awesome and should have stayed with it but everything went so well I wanted to try another ROM. The new ROM failed so I went back to mean-bean by selecting the backup I made on my sd card before I tried another ROM. My phone stuck on the "Samsung Note 2" boot up screen and never moved after mins. I did the "power + volume down + Power" and I get a warning asking me to press the volume up key to download a custom ROM or the volume down key to cancel. When I press the volume down button I get stuck at the Samsung note 2 screen, if I press volume up I get stuck at the downloading screen. When I connect the phone to my computer I can hear a ding in windows 7 64bit but am unable to see the device. I have read some of the forums and have downloaded a stock rom as suggested by several of them and oden 3.07. Oden does not show a com port as the posts suggest and my computer does not see the device. The forums that deal with not seeing your device says to download and install the latest usb drivers. I have re-downloaded the latest Samsung usb drivers and rebooted my computer. The computer still just makes a noise when i plug my phone in but does not see it in oden or in the computer. I have read so many forums and other peeps seem to still see their phone in oden. Maybe my phone is now trashed do I still have a chance or is it done. can anyone help a noob plz?
Thanks in advance.
Quick notes:
1: phone only boots to samsung note 2 screen
2: Phone will only go to download mode when I try to go to recovery
3: can hear ding on my computer when I connect but can't find see device
4: Oden does not see device
Click to expand...
Click to collapse
easy answer bro hopefully you have windows 7 or windows period. Easy way to do it is to go to your drivers deleted what it shows prob says samsung something stupid like that delete that also click driver files delete also button. then go to my computer and program files delete samsung folder then after you did all the deleteing plug in your phone and wala should work like a charm worked for me let me know!!
zactheandroidmac said:
easy answer bro hopefully you have windows 7 or windows period. Easy way to do it is to go to your drivers deleted what it shows prob says samsung something stupid like that delete that also click driver files delete also button. then go to my computer and program files delete samsung folder then after you did all the deleteing plug in your phone and wala should work like a charm worked for me let me know!!
Click to expand...
Click to collapse
Thanks bro, I removed the drivers and still nothing in odins comport. I reinstalled kies and it sees the phone but can't connect to it. My computer sees it in device manager, and i have tried 3 different odin versions. Still the little green android guy with the downloading msg.
Anything esle you can think of?
pacoabq said:
Thanks bro, I removed the drivers and still nothing in odins comport. I reinstalled kies and it sees the phone but can't connect to it. My computer sees it in device manager, and i have tried 3 different odin versions. Still the little green android guy with the downloading msg.
Anything esle you can think of?
Click to expand...
Click to collapse
Try a different cord...
Or press volume up (not down) power and home...go into recovery and run your back up (nandroid)...if you dont have a nandroid clean wipe and flash your mean bean
Sent from my SCH-I605 using xda premium
---------- Post added at 06:50 AM ---------- Previous post was at 06:22 AM ----------
In your description you said volume down power and home...probably looking at down load mode...your not even close to bricked YET...
Sent from my SCH-I605 using xda premium
pacoabq said:
I will try that when I get home. all day at work and can't wait to try it. Thank you for the responce.
Click to expand...
Click to collapse
Open Odin up on your computer without phone plugged in. Power off the phone then plug it in and boot into download and see if that does anything.

[Q] HDX 7 stuck in boot loop

Help! I have a newer HDX 7 that is stuck trying to reboot. The device powers up to the gray kindle fire screen but sits there for a minute or so and then the screen flashes and it starts all over. The device does not recognize the power button. I've tried the hold the button for 40 seconds to reset but it just keeps going through this loop while holding the power button. When I connected it to my PC (Win7), it does not see the device. If I connect another Andriod device, it sees it imeadiately.
I'm a complete noob with this but I'm actually in IT, just not in this area. This is my sons device so I'm not sure exactly what he was doing at the time it started this but my guess would be playing MineCraft. Amazon's wonderful support says it just needs to be replaced but it's out of warranty. My son and I were just about to start an online coding course so I'd like to get this back up and running so we can start that. Any help would be appreciated. After searching the web, you guys seem to be the only ones able to root or fix any software/os issues with these devices.
Thanks,
Doug
Leav320 said:
Help! I have a newer HDX 7 that is stuck trying to reboot. The device powers up to the gray kindle fire screen but sits there for a minute or so and then the screen flashes and it starts all over. The device does not recognize the power button. I've tried the hold the button for 40 seconds to reset but it just keeps going through this loop while holding the power button. When I connected it to my PC (Win7), it does not see the device. If I connect another Andriod device, it sees it imeadiately.
I'm a complete noob with this but I'm actually in IT, just not in this area. This is my sons device so I'm not sure exactly what he was doing at the time it started this but my guess would be playing MineCraft. Amazon''s wonderful support says it just needs to be replaced but it's out of warranty. My son and I were just about to start an online coding course so I'd like to get this back up and running so we can start that. Any help would be appreciated. After searching the web, you guys seem to be the only ones able to root or fix any software/os issues with these devices.
Thanks,
Doug
Click to expand...
Click to collapse
Your options are limited given the device is largely invisible via tether (even then there would be little recourse as adb is probably disabled). Did you try a factory reset? Amazon's crippled recovery environment can be accessed via power + vol-up from a cold start. Release the power button after the gray Kindle logo appears. If the recovery menu comes up the only option is 'factory reset'. I realize you may not be able to access recovery given the non-responsive power button.
Any chance you son is old/savvy enough to trying rooting the device? The symptoms suggest either a failed automatic update (rare but it does happen) or botched attempt to root via the wrong method. Obviously a spontaneous hardware failure is also possible albeit unlikely.
Do you know what version of Fire OS was running just prior to the boot loop?
There is still a small chance adb may help even if the device is not recognized by Windows explorer. However, if as Davey said, it is disabled, things are limited.
Again, do you know what version is you were running?
Have you installed adb?
Have you tried recovery?
Sent from my KFTHWI using Tapatalk
Davey126 said:
Your options are limited given the device is largely invisible via tether (even then there would be little recourse as adb is probably disabled). Did you try a factory reset? Amazon's crippled recovery environment can be accessed via power + vol-up from a cold start. Release the power button after the gray Kindle logo appears. If the recovery menu comes up the only option is 'factory reset'. I realize you may not be able to access recovery given the non-responsive power button.
Any chance you son is old/savvy enough to trying rooting the device? The symptoms suggest either a failed automatic update (rare but it does happen) or botched attempt to root via the wrong method. Obviously a spontaneous hardware failure is also possible albeit unlikely.
Do you know what version of Fire OS was running just prior to the boot loop?
Click to expand...
Click to collapse
No, Unless it updated automatically, it was the same version that was on there when it was delivered around 4/14.
No, My son would not have tried rooting this on his own.
I was incorrect when I stated that the system wasn't recognizing the power button. When I try the hold the power button for 40 secs or the Power button + Vol up button to restart, the boot loop gets shorter.
lekofraggle said:
There is still a small chance adb may help even if the device is not recognized by Windows explorer. However, if as Davey said, it is disabled, things are limited.
Again, do you know what version is you were running?
Have you installed adb?
Have you tried recovery?
Sent from my KFTHWI using Tapatalk
Click to expand...
Click to collapse
I have installed ADB on my PC but it doesn't see the device (although I'm not sure I'm using it correctly). What command should I be issuing to see if the device is connected. If I use "adb devices" I get the response in the attached screen shot.
If by recovery, you mean the recovery on the device, the power+volume up button doesn't work.
I appreciate all of the help!
Leav320 said:
No, Unless it updated automatically, it was the same version that was on there when it was delivered around 4/14.
No, My son would not have tried rooting this on his own.
I was incorrect when I stated that the system wasn't recognizing the power button. When I try the hold the power button for 40 secs or the Power button + Vol up button to restart, the boot loop gets shorter.
I have installed ADB on my PC but it doesn't see the device (although I'm not sure I'm using it correctly). What command should I be issuing to see if the device is connected. If I use "adb devices" I get the response in the attached screen shot.
If by recovery, you mean the recovery on the device, the power+volume up button doesn't work.
I appreciate all of the help!
Click to expand...
Click to collapse
Given the delivery date and age of device I STRONGLY recommend you reach out to Amazon for a replacement vs trying to resolve on your own. A new version of Fire OS is currently rolling out which MAY have triggered the behavior you are seeing. Bit of a bummer given your son's course plans but a worthwhile delay IMHO.
I agree with Davey.
Sent from my KFTHWI using Tapatalk

Recovery / ADB question with regards to USB debug mode

Good day to all,
I have someone's phone but I need some help to resolve it's issue. It's an Alcatel One touch pop c1 4015a. The owner asked me how to factory reset it, so I gave step by step instructions as to how to do it. After resetting the phone, it some how got soft bricked, just stays at the logo screen.
So right now, I have it trying to flash it with so flash tools. Tried accessing recovery mode but it was not working. So I thought of if it was possible to flash a recovery image via so flash tools, which I found and tried but it wouldn't start downloading. Afterwards, all of a sudden the recovery mode was working (I swear it was not working before) so I am trying to install the stock rom via sdcard, but it starts and stops.
So right now I am think if the USB debugging feature may have anything to do with it or maybe I have to install cwm or twrp. Which is why I am here with the following questions:
1 Is it possible to install cwm via the phone stock recovery mode?
2 Is it possible to use ADB to install cwm? If so can I get some noob friendly instructions to do so
3 Can I somehow enable USB debug via recovery mode or ADB?
4 What on earth can I do to fix this phone if all of the above is not possible?
I do apologize as well if I posted this question in the wrong area or if there are similar topics like this one which I didn't see.
Thanks much
Sent from my Timmy E86 using XDA Free mobile app
Okay bud, I can tell you're new to this, answer to your first question is NO, you have to do that via fast boot which I can tell you how to get into, second questions answer is MAYBE, but fast boot is easier and uses the same drivers (on your of) third questions answer is NO only on custom recoveries like cwm and twrp. Fourth questions answer is, if you have a cwm recovery image, boot the phone into fast boot (two ways: look in recovery for an option called "reboot boot loader" if you can't find it, try booting up the phone while holding volume down (-) and power. Then connect it to your pc and open a terminal or command prompt and type: fastboot flash recovery (now drag and drop the recovery file in the command prompt, it should automatically enter its file path) and hit enter. That should work, if you need more help ask
Sent from my iPhone using Tapatalk
MeowDude said:
Okay bud, I can tell you're new to this, answer to your first question is NO, you have to do that via fast boot which I can tell you how to get into, second questions answer is MAYBE, but fast boot is easier and uses the same drivers (on your of) third questions answer is NO only on custom recoveries like cwm and twrp. Fourth questions answer is, if you have a cwm recovery image, boot the phone into fast boot (two ways: look in recovery for an option called "reboot boot loader" if you can't find it, try booting up the phone while holding volume down (-) and power. Then connect it to your pc and open a terminal or command prompt and type: fastboot flash recovery (now drag and drop the recovery file in the command prompt, it should automatically enter its file path) and hit enter. That should work, if you need more help ask
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Ok I dont see that option in recovery mode at all. Which leaves the vol - + power button combo. Is something specific suppose to happen while holding these buttons? The phone might just continuously restart until i let go then it would go to the logo screen. If I try vol + & - with the power button, it will stay blank for a while as after i let go the button then it would power on to the logo screen.
It should either show a custom screen (pic maybe?) or freeze at the boot logo.
Sent from my iPhone using Tapatalk
---------- Post added at 11:02 PM ---------- Previous post was at 11:01 PM ----------
Or you can try pressing power for a second (until you see the boot logo or feel it vibrate) then releasing it, and then holding volume down. This process varies on phones
Sent from my iPhone using Tapatalk
Still no luck. And for some reason, it won't detect the phone in ADB mode. I have installed drivers for it, more than once.
Sent from my Timmy E86 using XDA Free mobile app
Are you sure they're the right drivers? If you're on Windows plug in the device while in recovery, and open control panel, then click devices and printers, and it should show you a list of device attached to your computer,now find yours (or tell me what you see) and ill help you from there. Oh, and also, what SPECIFIC device is this?
Sent from my iPhone using Tapatalk
It's an Alcatel one touch c1. Right now , I connected it to the pc while in recovery mode. But it gives a drive descriptor request error. I installed all drivers I came across for this phone.
Sent from my Timmy E86 using XDA Free mobile app
It gives an option in recovery mode to update via ADB as well
Sent from my Timmy E86 using XDA Free mobile app
EDIT: If i try to use the sdcard option, it immediately stops
AnoitedOne347 said:
It gives an option in recovery mode to update via ADB as well
Sent from my Timmy E86 using XDA Free mobile app
EDIT: If i try to use the sdcard option, it immediately stops
Click to expand...
Click to collapse
Try updating it through adb
Sent from my iPhone using Tapatalk

Categories

Resources