Is anyone else having issues while in recovery? I am running CWM and I can't see my tablet properly. Windows tells me it can't identify the device and when I try to make it use nvidias drivet (or any driver) it tells me it's not compatible and something about it not being 64bit even though there are x64 drivers available. Works perfect everywhere else, just looking to see if anyone else has dealt with that.
Sent from my One M8
Keithn said:
Is anyone else having issues while in recovery? I am running CWM and I can't see my tablet properly. Windows tells me it can't identify the device and when I try to make it use nvidias drivet (or any driver) it tells me it's not compatible and something about it not being 64bit even though there are x64 drivers available. Works perfect everywhere else, just looking to see if anyone else has dealt with that.
Sent from my One M8
Click to expand...
Click to collapse
Figured out my issue in a way. While in CWM it doesn't appear to report to windows properly, stock recovery works fine.
Keithn said:
Figured out my issue in a way. While in CWM it doesn't appear to report to windows properly, stock recovery works fine.
Click to expand...
Click to collapse
Could you send me stock recovery so I can take a look inside the init.rc
Yeah, I'll do that today
Sent from my One M8
Keithn said:
Yeah, I'll do that today
Sent from my One M8
Click to expand...
Click to collapse
I found it inside the stock nvidia images for testing on the k1 board thanks.
This appeared to be the issue https://github.com/cm-ardbeg/androi...b4fd46180/rootdir/etc/init.recovery.ardbeg.rc
Unjustified Dev said:
I found it inside the stock nvidia images for testing on the k1 board thanks.
This appeared to be the issue https://github.com/cm-ardbeg/androi...b4fd46180/rootdir/etc/init.recovery.ardbeg.rc
Click to expand...
Click to collapse
If you want me to test anything out with it let me know. Maybe this will help pinpointing the issues for the touch driver if I can pull logs while in recovery.
Keithn said:
If you want me to test anything out with it let me know. Maybe this will help pinpointing the issues for the touch driver if I can pull logs while in recovery.
Click to expand...
Click to collapse
I compiled this one earlier let me know if it works. It doesn't have touch support but I can add it once adb is confirmed working
Unjustified Dev said:
I compiled this one earlier let me know if it works. It doesn't have touch support but I can add it once adb is confirmed working
Click to expand...
Click to collapse
Still having issues in windows it shows up as "Unknown USB Device (Configuration Descriptor Request Failed)" and gives me
Code:
Windows has stopped this device because it has reported problems. (Code 43)
A request for the USB configuration descriptor failed.
for device status.
I'll give it a try in Linux but if it is not reporting properly then I don't think it will work there either.
__________________________
Nothing in Ubuntu either, even lsusb doesn't list it.
Keithn said:
Still having issues in windows it shows up as "Unknown USB Device (Configuration Descriptor Request Failed)" and gives me
Code:
Windows has stopped this device because it has reported problems. (Code 43)
A request for the USB configuration descriptor failed.
for device status.
I'll give it a try in Linux but if it is not reporting properly then I don't think it will work there either.
__________________________
Nothing in Ubuntu either, even lsusb doesn't list it.
Click to expand...
Click to collapse
This is crazy does adb work in the recovery you compile from their git?
Unjustified Dev said:
This is crazy does adb work in the recovery you compile from their git?
Click to expand...
Click to collapse
I can't even get the menu to pop up. On stock it's just vol + and power and then you can see the menus and select adb sideload etc. On my compiled one it just sits at the No Command screen even after pressing those buttons, and it shows up as the same thing in my PC as CWM did.
Keithn said:
Is anyone else having issues while in recovery? I am running CWM and I can't see my tablet properly. Windows tells me it can't identify the device and when I try to make it use nvidias drivet (or any driver) it tells me it's not compatible and something about it not being 64bit even though there are x64 drivers available. Works perfect everywhere else, just looking to see if anyone else has dealt with that.
Sent from my One M8
Click to expand...
Click to collapse
I am having same issue
---------- Post added at 02:50 AM ---------- Previous post was at 02:46 AM ----------
Keithn said:
I can't even get the menu to pop up. On stock it's just vol + and power and then you can see the menus and select adb sideload etc. On my compiled one it just sits at the No Command screen even after pressing those buttons, and it shows up as the same thing in my PC as CWM did.
Click to expand...
Click to collapse
I have same issue but have a boot loop so I am bricked at the moment
---------- Post added at 02:55 AM ---------- Previous post was at 02:50 AM ----------
Okay now when I also enter recovery mode I have a blank screen can not boot into the system because of a boot loop, does anyone have any surgestions ?????????
MRobbo80 said:
I am having same issue
---------- Post added at 02:50 AM ---------- Previous post was at 02:46 AM ----------
I have same issue but have a boot loop so I am bricked at the moment
---------- Post added at 02:55 AM ---------- Previous post was at 02:50 AM ----------
Okay now when I also enter recovery mode I have a blank screen can not boot into the system because of a boot loop, does anyone have any surgestions ?????????
Click to expand...
Click to collapse
go into fastboot and flash a recovery then boot into recovery
Just tested stock recovery and the device doesn't even show as being connected until I select sideload then all I get is sideload.
Keithn said:
go into fastboot and flash a recovery then boot into recovery
Just tested stock recovery and the device doesn't even show as being connected until I select sideload then all I get is sideload.
Click to expand...
Click to collapse
My screen is black I can not see any options I am using the custom new cwm
Did you try what I said? Can you at least get into the boot loader?
Sent from my SHIELD Tablet
Keithn said:
Did you try what I said? Can you at least get into the boot loader?
Sent from my SHIELD Tablet
Click to expand...
Click to collapse
sorry not sure how to boot in to fastboot?
MRobbo80 said:
sorry not sure how to boot in to fastboot?
Click to expand...
Click to collapse
I meant to say boot into the bootloader so you can use fastboot. From Nvidia
Code:
HW method:
Turn off the device
Press "Volume Down" -> "Power", hold "Volume Down" and leave Power buttons till device boots
So basically just hold vol - then press power and keep the vol button held but not the power. Should give you a black screen with some words on it and you can select a few different things. When you are there use fastboot like you would adb. Get a cwm image and give it the command
Code:
fastboot flash recovery cwm.img
Put what ever name and location you have for your recovery image in place of cwm.img.
Keithn said:
I meant to say boot into the bootloader so you can use fastboot. From Nvidia
Code:
HW method:
Turn off the device
Press "Volume Down" -> "Power", hold "Volume Down" and leave Power buttons till device boots
So basically just hold vol - then press power and keep the vol button held but not the power. Should give you a black screen with some words on it and you can select a few different things. When you are there use fastboot like you would adb. Get a cwm image and give it the command
Code:
fastboot flash recovery cwm.img
Put what ever name and location you have for your recovery image in place of cwm.img.
Click to expand...
Click to collapse
Thanks for your fast reply here is whats happening I have been working with a dev to get acip up and running, I have cwm recovery and have fully wiped the device and installed acip which currently is bootlooping. Now my problem is when I try to enter fastboot holding down -volume key and pressing the power it just splashes to the boot logo so no luck there but when I hold down volume + and power key I can hear the sound of a usb connecting to my computer but have a black screen only. So when I check device manager under windows I can see a yellow caution mark APX unknown device so at the moment trying to find a driver that will work so that's where I am really
MRobbo80 said:
Thanks for your fast reply here is whats happening I have been working with a dev to get acip up and running, I have cwm recovery and have fully wiped the device and installed acip which currently is bootlooping. Now my problem is when I try to enter fastboot holding down -volume key and pressing the power it just splashes to the boot logo so no luck there but when I hold down volume + and power key I can hear the sound of a usb connecting to my computer but have a black screen only. So when I check device manager under windows I can see a yellow caution mark APX unknown device so at the moment trying to find a driver that will work so that's where I am really
Click to expand...
Click to collapse
Grab theses and see if they work. They are included with Nvidias tegra development tools.
Nvidia Drivers (shouldn't be much different than googles drivers but here they are.)
I don't think you are going to want it in APX anyways. I noticed it can be a pain to get the bootloader try keeping vol - held and only pressing power for a couple of seconds at most and give it a second for the screen to turn on. If you hit the splash screen then you missed the bootloader.
Keithn said:
Grab theses and see if they work. They are included with Nvidias tegra development tools.
Nvidia Drivers (shouldn't be much different than googles drivers but here they are.)
I don't think you are going to want it in APX anyways. I noticed it can be a pain to get the bootloader try keeping vol - held and only pressing power for a couple of seconds at most and give it a second for the screen to turn on. If you hit the splash screen then you missed the bootloader.
Click to expand...
Click to collapse
M8 IM IN MASSIVE THANK YOU :good::good::good::good::good::good::good::good::good::good::good::good::goodAM THAT TEXT IS SMALL HONESTLY thank you very much :good:
---------- Post added at 12:18 AM ---------- Previous post was at 12:07 AM ----------
MRobbo80 said:
M8 IM IN MASSIVE THANK YOU :good::good::good::good::good::good::good::good::good::good::good::good::goodAM THAT TEXT IS SMALL HONESTLY thank you very much :good:
Click to expand...
Click to collapse
My tablet is now fully restoring my backup in cwm as I speak have one big grin on my face at the mo.
MRobbo80 said:
M8 IM IN MASSIVE THANK YOU :good::good::good::good::good::good::good::good::good::good::good::good::goodAM THAT TEXT IS SMALL HONESTLY thank you very much :good:
---------- Post added at 12:18 AM ---------- Previous post was at 12:07 AM ----------
My tablet is now fully restoring my backup in cwm as I speak have one big grin on my face at the mo.
Click to expand...
Click to collapse
No problem good to hear :good:
Related
So recently my phones been acting up. I had just installed the TEUV kernel from trinity and began noticing some irregularities.
1) the home button started to open the desk clock
2) the power button stopped turning off the screen
3) in bootloader, the up and down volume rocker doesn't work
So naturally i tried to wipe the rom and start new again. However, the phone won't boot up and most far i can go is bootloader. I cant do anything here because the volume rockers don't respond. I tried doing it manually throught ADB but the computer doesn't see the device.
any help guys? I'm really out of ideas so any would be great.
baolongn said:
So recently my phones been acting up. I had just installed the TEUV kernel from trinity and began noticing some irregularities.
1) the home button started to open the desk clock
2) the power button stopped turning off the screen
3) in bootloader, the up and down volume rocker doesn't work
So naturally i tried to wipe the rom and start new again. However, the phone won't boot up and most far i can go is bootloader. I cant do anything here because the volume rockers don't respond. I tried doing it manually throught ADB but the computer doesn't see the device.
any help guys? I'm really out of ideas so any would be great.
Click to expand...
Click to collapse
besides for the home button opening the deskclock, i experience everything else. but for me, its because my power button is broken. sometimes it partially works but acts like its stuck even though its not. in bootloader the volume keys dont work unless i flick the phone with my fingers right by the power button. then every so often the volume buttons work in bootloader. i use the twrp recovery btw, because it has on option to not use the power button to select.
anything else i can do?
my computer cant even recognize the phone for some reason.
baolongn said:
anything else i can do?
my computer cant even recognize the phone for some reason.
Click to expand...
Click to collapse
do you have the drivers installed? what i meant was did it recognize your phone before?
simms22 said:
do you have the drivers installed? what i meant was did it recognize your phone before?
Click to expand...
Click to collapse
Yeah it did when I unlocked the phone.
baolongn said:
Yeah it did when I unlocked the phone.
Click to expand...
Click to collapse
try updating the drivers, or uninstalling then reinstalling the drivers.
---------- Post added at 05:31 PM ---------- Previous post was at 05:28 PM ----------
baolongn said:
Yeah it did when I unlocked the phone.
Click to expand...
Click to collapse
also, try this.. pull your battery for two minutes, then put it back in and try booting. if it boot, you can boot into recovery via the terminal.
via terminal? is that command prompt? oh and what drivers do you think ill need? thanks man.
simms22 said:
try updating the drivers, or uninstalling then reinstalling the drivers.
---------- Post added at 05:31 PM ---------- Previous post was at 05:28 PM ----------
also, try this.. pull your battery for two minutes, then put it back in and try booting. if it boot, you can boot into recovery via the terminal.
Click to expand...
Click to collapse
baolongn said:
via terminal? is that command prompt? oh and what drivers do you think ill need? thanks man.
Click to expand...
Click to collapse
you can install the nexus s driver via pdanets website, thats the easy way http://www.junefabrics.com/android/index.php
download and install the free program(its a tethering app) onto you desktop/laptop, then open it and follow the onscreen instructions. it will install the right nexus s driver for you. you might have to uninstall the other driver, if you had it installed.
about the terminal, yea, its a command prompt right from your phone. if you dont have the terminal emulator installed, you can get a free one from the android market. open the terminal and type..
su(press enter)
reboot recovery(press enter)
i dont use adb at all, i use the terminal emulator instead. there are lots of cool things that you can use it for. for example, i flash/update my recovery through the terminal and sometimes also push boot.img through it to my phone too. plus lots of other stuff
Thanks Simms!
the one problem is I can't turn on my phone either. Its stuck on a bootloop. That is why i'm trying ADB. I'm trying to install PDAnet but its still not locating it. I'm going to try on another computer and check back in a bit.
simms22 said:
you can install the nexus s driver via pdanets website, thats the easy way http://www.junefabrics.com/android/index.php
download and install the free program(its a tethering app) onto you desktop/laptop, then open it and follow the onscreen instructions. it will install the right nexus s driver for you. you might have to uninstall the other driver, if you had it installed.
about the terminal, yea, its a command prompt right from your phone. if you dont have the terminal emulator installed, you can get a free one from the android market. open the terminal and type..
su(press enter)
reboot recovery(press enter)
i dont use adb at all, i use the terminal emulator instead. there are lots of cool things that you can use it for. for example, i flash/update my recovery through the terminal and sometimes also push boot.img through it to my phone too. plus lots of other stuff
Click to expand...
Click to collapse
baolongn said:
Thanks Simms!
the one problem is I can't turn on my phone either. Its stuck on a bootloop. That is why i'm trying ADB. I'm trying to install PDAnet but its still not locating it. I'm going to try on another computer and check back in a bit.
Click to expand...
Click to collapse
you pulled the battery for two minutes before powering on this time?
yeah, endless bootloop
other computer is the same problem
simms22 said:
you pulled the battery for two minutes before powering on this time?
Click to expand...
Click to collapse
baolongn said:
yeah, endless bootloop
other computer is the same problem
Click to expand...
Click to collapse
:-\ ......
is there nothing i can do?
simms22 said:
:-\ ......
Click to expand...
Click to collapse
baolongn said:
is there nothing i can do?
Click to expand...
Click to collapse
does fastboot recognize your phone? not adb but fastboot.
what do you mean by that?
simms22 said:
does fastboot recognize your phone? not adb but fastboot.
Click to expand...
Click to collapse
baolongn said:
what do you mean by that?
Click to expand...
Click to collapse
The fastboot program you run in command line. Like ADB but for flashing img's real quick.
im not sure. maybe im not doing it right but on bootloader mode, under device manager, the phone doesn't show up so im guessing USB debugging doesnt work? thanks so much for the responses guys!
any more suggestions?
BlackHawkA4 said:
The fastboot program you run in command line. Like ADB but for flashing img's real quick.
Click to expand...
Click to collapse
holy crap, it suddenly moved in bootloader. it went to recovery but then it automatically pressed reboot -_-
back to square 1 folks
simms22 said:
besides for the home button opening the deskclock, i experience everything else. but for me, its because my power button is broken. sometimes it partially works but acts like its stuck even though its not. in bootloader the volume keys dont work unless i flick the phone with my fingers right by the power button. then every so often the volume buttons work in bootloader. i use the twrp recovery btw, because it has on option to not use the power button to select.
Click to expand...
Click to collapse
baolongn said:
holy crap, it suddenly moved in bootloader. it went to recovery but then it automatically pressed reboot -_-
back to square 1 folks
Click to expand...
Click to collapse
thats how i was the first time i saw it move after i knew the power button was broken now i can get it to move within a few minutes by flicking the back, with the cover removed, between the battery and speaker, when pressing on the volune keys.
Haha i got it to work! went right to recovery and quickly restored my last backup!
finally, the nexus is back. thanks everyone!!!
simms22 said:
thats how i was the first time i saw it move after i knew the power button was broken now i can get it to move within a few minutes by flicking the back, with the cover removed, between the battery and speaker, when pressing on the volune keys.
Click to expand...
Click to collapse
When I try to boot the phone, either through the power button or bootloader, it tries to get into recovery over and over again but can never get in (to TWRP recovery). It always just gets to the TWRP splash screen but then goes black and repeats. The bootloader is unlocked. I am not sure what state the actual OS is in. ADB doesn't recognise the phone (adb devices shows nothing). Oh, and I can't get into recovery through bootloader either.
Can anyone offer any advice?
Thanks in advance
Possible power button issue? ADB commands do not work in fastboot mode. Is the phone detected in fastboot mode? Did you try re-flashing TWRP?
audit13 said:
Possible power button issue? ADB commands do not work in fastboot mode. Is the phone detected in fastboot mode? Did you try re-flashing TWRP?
Click to expand...
Click to collapse
Definately not a power button issue, it was fine before. What is fastboot mode and how would I get into it?
The power button issue can appear out of nowhere, at least it did for me. The constant reboots are also an indication.
To get into fastboot, power off the phone, hold volume up, volume down, and press power button.
I had the adb issue once .. Connect the phone to your PC then go to device manager and select your phone .. Click on update drivers and click browse your PC instead of the internet if I am correct you will see two driver options . select the USB component driver and install it .. Should work now ...
---------- Post added at 04:06 PM ---------- Previous post was at 03:30 PM ----------
Corneliusvinyo said:
I had the adb issue once .. Connect the phone to your PC then go to device manager and select your phone .. Click on update drivers and click browse your PC instead of the internet if I am correct you will see two driver options . select the USB component driver and install it .. Should work now ...
Click to expand...
Click to collapse
Disregard this . I assumed you could get it into recovery . sorry
I have bought Oppo R7 PLUS from china so basically it doesnt have google services which I want to use in INDIA. I have read many post here and in oppo community forum about flashing custom rom (CYANOGEN 13) and GAPPS to make google services work on my phone as well as have cyanogen. As a newbie I read everything I could. I havent ever rooted a phone or flashed anything on an android. I read the articles here and interestingly learnt a lot about adb and fastboot to flash the same.
Under usb debugging mode open, i tried to use the command 'adb fastboot bootloader' but my oppo didnt rebooted to fastboot mode, instead it rebooted as normal.
While giving commands 'adb devices', it returned back with a serial number. When i gave the command 'fastboot devices' it didnt returned anything.
I also used the hot keys, volume up and power simultaneously to reboot into fastboot but it did not. I even tried first pressing volume up and then power, but its didnt boot.
I am not able to use fastboot commands as well as cant reboot into fastboot through hot keys.
I have checked in device manager for drivers and there are no issues with it. Its showing there 'ANDROID COMPOSITE ADB INTERFACE'.
Your help would be highly appreciated.
I just want google services on my chinese oppo r7 plus, so if there is any alternate method, it would be appreciated too.
NOTE: MY PHONE IS NOT ROOTED RIGHT NOW AND I AM A NEWBIE TO THIS.
Thank you in advance.
asakshatshukla said:
I have bought Oppo R7 PLUS from china so basically it doesnt have google services which I want to use in INDIA. I have read many post here and in oppo community forum about flashing custom rom (CYANOGEN 13) and GAPPS to make google services work on my phone as well as have cyanogen. As a newbie I read everything I could. I havent ever rooted a phone or flashed anything on an android. I read the articles here and interestingly learnt a lot about adb and fastboot to flash the same.
Under usb debugging mode open, i tried to use the command 'adb fastboot bootloader' but my oppo didnt rebooted to fastboot mode, instead it rebooted as normal.
While giving commands 'adb devices', it returned back with a serial number. When i gave the command 'fastboot devices' it didnt returned anything.
I also used the hot keys, volume up and power simultaneously to reboot into fastboot but it did not. I even tried first pressing volume up and then power, but its didnt boot.
I am not able to use fastboot commands as well as cant reboot into fastboot through hot keys.
I have checked in device manager for drivers and there are no issues with it. Its showing there 'ANDROID COMPOSITE ADB INTERFACE'.
Your help would be highly appreciated.
I just want google services on my chinese oppo r7 plus, so if there is any alternate method, it would be appreciated too.
NOTE: MY PHONE IS NOT ROOTED RIGHT NOW AND I AM A NEWBIE TO THIS.
Thank you in advance.
Click to expand...
Click to collapse
I have the exact same problem. Would be great to get some info on what to do. R7 PlusM Chinese version with Snapdragon.
marlinsters said:
I have the exact same problem. Would be great to get some info on what to do. R7 PlusM Chinese version with Snapdragon.
Click to expand...
Click to collapse
Same here...just got the 4gb version but can't make any use of it until someone can help with this...
mikejasonsmith said:
Same here...just got the 4gb version but can't make any use of it until someone can help with this...
Click to expand...
Click to collapse
How do you confirm whether its snapdragon or not? in about phone menu, mine is showing octa core, android 5.0 and color os 2.1... Do you,think this issie can be resolved or anyone here would help us?
mikejasonsmith said:
Same here...just got the 4gb version but can't make any use of it until someone can help with this...
Click to expand...
Click to collapse
I have also the 4gb version. Cannot do anything with it. No bootloader, nothing. Cannot even do a factory reset.
---------- Post added at 08:58 AM ---------- Previous post was at 08:53 AM ----------
asakshatshukla said:
How do you confirm whether its snapdragon or not? in about phone menu, mine is showing octa core, android 5.0 and color os 2.1... Do you,think this issie can be resolved or anyone here would help us?
Click to expand...
Click to collapse
What does it say in about phone "CPU"? Mine sais Qualcomm MSM8939 Octa Core.
marlinsters said:
I have also the 4gb version. Cannot do anything with it. No bootloader, nothing. Cannot even do a factory reset.
---------- Post added at 08:58 AM ---------- Previous post was at 08:53 AM ----------
What does it say in about phone "CPU"? Mine sais Qualcomm MSM8939 Octa Core.
Click to expand...
Click to collapse
Mine says 'octacore'
maelinsters : you can enter into factory reset mpde by simultaneously pressing volume up and volume down and ppwer button when your phome is switched off. keep buttons pressed till the time you feel a vibrate. check youtube on how to use the factory rest mode because as i have checled factory reset mode is in chinese.
asakshatshukla said:
maelinsters : you can enter into factory reset mpde by simultaneously pressing volume up and volume down and ppwer button when your phome is switched off. keep buttons pressed till the time you feel a vibrate. check youtube on how to use the factory rest mode because as i have checled factory reset mode is in chinese.
Click to expand...
Click to collapse
I have tried this:
Power + Volume Up - Black screen. Nothing happens.
Power + Volume Down - Endless loop with vibrate and logo flashing
Power + Volume Up and Down - Endless loop with vibrate and logo flashing
I cannot get into the recovery mode like before after rooting with oppo tools. I cannot do a factory reset from setting either. Nothing works as it should.
Now the problem arises with me that i tried to root my pphone with oppotools apl version 1.6.5 but now its stuck on oppo boot logo. Usbdebugging is not enabled. Fastboot mpde doesnt works ony phone. What should I do?
marlinsters said:
I have also the 4gb version. Cannot do anything with it. No bootloader, nothing. Cannot even do a factory reset.
---------- Post added at 08:58 AM ---------- Previous post was at 08:53 AM ----------
What does it say in about phone "CPU"? Mine sais Qualcomm MSM8939 Octa Core.
Click to expand...
Click to collapse
Did you have any luck? I've got the 4gb version too but it useless to me at the moment.
mikejasonsmith said:
Did you have any luck? I've got the 4gb version too but it useless to me at the moment.
Click to expand...
Click to collapse
I have not had any luck yet. I am struggeling with the cualcomm 9006 / 9008 drivers at the moment as seen in the other thread .. :\
guys you just have to hold down the "volume up" button for a couple seconds (maybe 3-4 seconds) AND THEN press the "power" button to go to fastboot mode
jnkayak said:
guys you just have to hold down the "volume up" button for a couple seconds (maybe 3-4 seconds) AND THEN press the "power" button to go to fastboot mode
Click to expand...
Click to collapse
anyway to downgrade? anyone have a link tq
Basically you can't enter in FastBoot Mode with newest device like R7PlusM.
You must Root with Oppo Tools and than Flash TWRP Recovery.
Check this guide I've made....only if you have R7PlusM (but it should work with others devices without FastBoot, at least the Rooting Tool).
i tried like this:
1. First of all turn off the device by holding the Power button.
2. Afterwards hold down the Volume Up and Volume Down button for a couple of seconds.
3. While holding these buttons press the Power button for a short while.
4. Release held keys when you see an Andoid image.
5. Then press the Camera button to enter Recovery Mode.
and noting. there is no android image.
and also when i press and hold power+ volume up the phone turn on and then after 2-3 sec the phone vibrate 3 time.
what is that 3 vibrations?
so how do i enter the recovery???
thanks!
UP
Shlomi93 said:
UP
Click to expand...
Click to collapse
Power down your device.
Press and hold POWER + VOLUME DOWN
After the Sony logo disappears, release the POWER button and continue to hold VOLUME DOWN for 3 seconds.
This will allow you to boot to recovery.
Sent from my Nexus 6 using XDA-Developers mobile app
fast69mopar said:
Power down your device.
Press and hold POWER + VOLUME DOWN
After the Sony logo disappears, release the POWER button and continue to hold VOLUME DOWN for 3 seconds.
This will allow you to boot to recovery.
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
there is no logo. if i press and hold volume up + power i feel one vibration and the after 2 sec i feel 3 more vibrations and it keep going like that in a loop.
and there is no logo. the screen doesnt even turns on.
Shlomi93 said:
there is no logo. if i press and hold volume up + power i feel one vibration and the after 2 sec i feel 3 more vibrations and it keep going like that in a loop.
and there is no logo. the screen doesnt even turns on.
Click to expand...
Click to collapse
I may have given you incorrect steps and that's my fault. I was reading about a different device. My bad. Try this:
Power off your device.
Press and hold VOLUME UP + POWER at the same time.
Release all buttons when the Sony Xperia C3 screen flickers and in a few seconds the Recovery screen will appear.
You can also try this:
Reboot your phone, as it's rebooting, press volume down + power. You should then see the Android robot after restart, release buttons and press camera shutter.?
---------- Post added at 11:37 PM ---------- Previous post was at 11:26 PM ----------
Okay, quick question. Have you installed a custom recovery? If not, your device was not shipped with a stock recovery in and therefore you will not be able to boot into recovery.
fast69mopar said:
I may have given you incorrect steps and that's my fault. I was reading about a different device. My bad. Try this:
Power off your device.
Press and hold VOLUME UP + POWER at the same time.
Release all buttons when the Sony Xperia C3 screen flickers and in a few seconds the Recovery screen will appear.
You can also try this:
Reboot your phone, as it's rebooting, press volume down + power. You should then see the Android robot after restart, release buttons and press camera shutter.?
---------- Post added at 11:37 PM ---------- Previous post was at 11:26 PM ----------
Okay, quick question. Have you installed a custom recovery? If not, your device was not shipped with a stock recovery in and therefore you will not be able to boot into recovery.
Click to expand...
Click to collapse
well, no. i didnt flashed a custom recovery since i cant.
the only thing i can do is access to fastboot and i get an error while trying to send commands through SDK
fastboot failed remote unknown command
i searched in google but i havent found any solution.
any idea?
Shlomi93 said:
well, no. i didnt flashed a custom recovery since i cant.
the only thing i can do is access to fastboot and i get an error while trying to send commands through SDK
fastboot failed remote unknown command
i searched in google but i havent found any solution.
any idea?
Click to expand...
Click to collapse
Lemme take a look at my Sony stuff and see if I can find a solution.
Sent from my Nexus 6 using XDA-Developers mobile app
fast69mopar said:
Lemme take a look at my Sony stuff and see if I can find a solution.
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
ok i will wait for your replay! thanks a lot man.
Shlomi93 said:
ok i will wait for your replay! thanks a lot man.
Click to expand...
Click to collapse
Try using this guide to install recovery
http://forum.xda-developers.com/sony-xperia-c/help/comprehensive-guide-rooting-flashing-c3-t3277939
Shlomi93 said:
ok i will wait for your replay! thanks a lot man.
Click to expand...
Click to collapse
Do something for me first... Let's make sure your ADB fastboot is working properly.
If your device will boot normally, navigate to DEVELOPER OPTIONS and make sure you have enabled USB DEBUGGING.
Next, open a COMMAND PROMPT window and type:
adb devices
If the adb daemon is not running, you will see the COMMAND PROMPT say that it is starting the daemon on a certain port number.
Type this again:
adb devices
Your COMMAND PROMPT should return with a list of attached devices with your serial number.
Next, type this:
adb reboot bootloader
If it's working properly you should be booted into the bootloader and your LED should be a solid blue.
If you want to boot to the bootloader with the hard keys then do this:
Power off your device
Connect the USB cable to your PC
Press and hold POWER UP and plug in the USB cable to your device while still holding POWER UP.
This should boot you into the bootloader with a solid blue LED.
Let me know if these steps are working and post back with what you find
Sent from my Nexus 6 using XDA-Developers mobile app
fast69mopar said:
Do something for me first... Let's make sure your ADB fastboot is working properly.
If your device will boot normally, navigate to DEVELOPER OPTIONS and make sure you have enabled USB DEBUGGING.
Next, open a COMMAND PROMPT window and type:
adb devices
If the adb daemon is not running, you will see the COMMAND PROMPT say that it is starting the daemon on a certain port number.
Type this again:
adb devices
Your COMMAND PROMPT should return with a list of attached devices with your serial number.
Next, type this:
adb reboot bootloader
If it's working properly you should be booted into the bootloader and your LED should be a solid blue.
If you want to boot to the bootloader with the hard keys then do this:
Power off your device
Connect the USB cable to your PC
Press and hold POWER UP and plug in the USB cable to your device while still holding POWER UP.
This should boot you into the bootloader with a solid blue LED.
Let me know if these steps are working and post back with what you find
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
yes this works. i mean the volume up and usb cable let me go into bootloader. i see blue led and device is on debuging mode but i am unable to get into the device since i forgot the pass code.
this is why i want to get into recovery. i want to wipe data so the pass code will be removed.
beacuse of the pass code i cannot send adb commands through the lock screen.
anyway, there is somthing i can do to wipe data or flash a new rom or remove passcode through bootloader? (the black screen with the blue led)
fast69mopar said:
Do something for me first... Let's make sure your ADB fastboot i..............................................
XDA-Developers mobile app
Click to expand...
Click to collapse
my friend, thank you for your help but i found a solution.
The Solution​
1. find a ftf file (firmware for sony device) i used this ------------->>>> https://docs.google.com/uc?id=0B1AAC4lt7nzOM0plZW56MHZXYkE&export=download
2. download FlashTool (by Androxyed) from the official site --->>>> http://www.flashtool.net/index.php
3. flash the phone like this guy here --------------------------------->>>> https://www.youtube.com/watch?v=vlyVdz1CIbY
and boom. no password. you can choose if to wipe data or not.
btw:
still didnt found a way to get into recovery
Shlomi93 said:
my friend, thank you for your help but i found a solution.
The Solution
1. find a ftf file (firmware for sony device) i used this ------------->>>> https://docs.google.com/uc?id=0B1AAC4lt7nzOM0plZW56MHZXYkE&export=download
2. download FlashTool (by Androxyed) from the official site --->>>> http://www.flashtool.net/index.php
3. flash the phone like this guy here --------------------------------->>>>
and boom. no password. you can choose if to wipe data or not.
btw:
still didnt found a way to get into recovery
Click to expand...
Click to collapse
I was actually putting together a post for you with the exact same solution. I read over the details a little while ago. Glad you got it working. Good job.
I (stupidly) decided to repartition my Moto G3 using this guide. Now, when trying to turn my phone on, the screen stays blank and there's no indication that it's working but it reboots once every two to five seconds or so (telling you how I can tell it's rebooting would be a long story and I'm sure it's irrelevant to the issue).
Am I just hooped or is there hope?
Can you boot in to bootloader?
If yes just flash stock firmware (should include partition layout)
HelpMeruth said:
Can you boot in to bootloader?
If yes just flash stock firmware (should include partition layout)
Click to expand...
Click to collapse
Nope, all attempts to get into the bootloader fail. The screen just stays blank with no indication that it's doing anything at all (although behind the scenes it's actually rebooting once every few seconds). My (uneducated) guess is it can't even access any of the partitions.
sensi277 said:
Nope, all attempts to get into the bootloader fail. The screen just stays blank with no indication that it's doing anything at all (although behind the scenes it's actually rebooting once every few seconds). My (uneducated) guess is it can't even access any of the partitions.
Click to expand...
Click to collapse
Try to connect it to your pc and see if adb/fastboot sees the device.
michkost858 said:
Try to connect it to your pc and see if adb/fastboot sees the device.
Click to expand...
Click to collapse
adb shell doesn't see anything.
sensi277 said:
adb shell doesn't see anything.
Click to expand...
Click to collapse
Hey, since according to what you say your device is currently stuck in a boot-loop, I suggest you first take out the battery out for a few seconds and then put it back then enter recovery mode using the device buttons right after. only then connect your device to PC and use adb...
Jewshua said:
Hey, since according to what you say your device is currently stuck in a boot-loop, I suggest you first take out the battery out for a few seconds and then put it back then enter recovery mode using the device buttons right after. only then connect your device to PC and use adb...
Click to expand...
Click to collapse
Or, since the battery is not officially removable, wait till the battery dies and then try to boot into bootloader.
Volume down broken
Hi! My mom's phone started to heavily slow down with its stock firmware so I tried to install a custom firmware since I installed one on mine and we both have Moto G3s.
Thing is, it bricked and the volume down button is dead since a few month so I don't have access to the bootloader, otherwise I would just flash the stock firmware. Only buttons working are volume up and on/off buttons.
Is there any way to access the bootloader with this button or am I screwed on this one ?
tyty48 said:
Hi! My mom's phone started to heavily slow down with its stock firmware so I tried to install a custom firmware since I installed one on mine and we both have Moto G3s.
Thing is, it bricked and the volume down button is dead since a few month so I don't have access to the bootloader, otherwise I would just flash the stock firmware. Only buttons working are volume up and on/off buttons.
Is there any way to access the bootloader with this button or am I screwed on this one ?
Click to expand...
Click to collapse
Can you boot the ROM?
If so, you should be able to turn on usb debugging and run 'adb reboot recovery' and reflash from there
---------- Post added at 05:27 PM ---------- Previous post was at 05:26 PM ----------
sensi277 said:
adb shell doesn't see anything.
Click to expand...
Click to collapse
what about fastboot devices (with admin/root privileges) ?