Good Afternoon Everyone !
I'm new to the XDA , but not a Newbie in the delevoping section.
Because of a hardware problem when i changed the display of my phone
my volume keys aren't working anymore.
Today I flashed the Beanstalk ROM from the user TH3Bill, but unusally it won't start.
So i got the problem right now that it wont boot and I'm stuck with the Motorola Logo,
because I can' get into recovery. Is there any option to get into recovery without the volume
buttons or fastboot ?
PS : sry for the bad english
If you can access adb you can type "adb reboot recovery"
jorno88 said:
If you can access adb you can type "adb reboot recovery"
Click to expand...
Click to collapse
tried it, but it just says that now device was found , but the device is listet in the device manager as adb device interface.
that seems correct, only way to go into recovery without volume is adb or fastboot or ofcourse rebooting into recovery...(as far is i know)
do you know how to use adb?
can you see your device listed when you type adb devices?
jorno88 said:
that seems correct, only way to go into recovery without volume is adb or fastboot or ofcourse rebooting into recovery...(as far is i know)
do you know how to use adb?
can you see your device listed when you type adb devices?
Click to expand...
Click to collapse
Not really, my firstime , but i used fastboot before . but for fastboot you have to go into the fastboot mode, and without wokring volume keys that isnt possible.
No when i type in adb devices, there is no device listed at all , just the line " List of all ADB devices"
First you have to activate android debugging in settings for adb to show ur device.
Secondly, even if u boot into recovery, u cannot use recovery without volume buttons unless you flash a touch recovery, for which I think u need to boot into fastboot which again needs volume buttons...
any other solution anyone?
Sent from my cm_tenderloin using xda app-developers app
sa.guly10 said:
First you have to activate android debugging in settings for adb to show ur device.
Secondly, even if u boot into recovery, u cannot use recovery without volume buttons unless you flash a touch recovery, for which I think u need to boot into fastboot which again needs volume buttons...
any other solution anyone?
Sent from my cm_tenderloin using xda app-developers app
Click to expand...
Click to collapse
I cant activate anything, i flashed a new Rom and then I got into a Boot Loop, and yes i have a touch recovery
Edit: I found some threads using adb in a Boot loop, is it possible that i have the wrong drivers ? i used two different mehtods but i can't update the adb interface driver
look
Method 1 :hxxp://atrix4ghacks.com/atrix-4g-hacks/how-to-install-atrix-4g-drivers/ this is where i got stuck
I also found a second with a package to extract which was accesable from the cmd, adb started but the phone wasn't rechable
Edit Edit: It worked with the officila motorola drivers, and the normal adb-tools , thx for your support
Related
Well, I have a problem, my EVO doesn't boot, I was first on meanrom and made a nandroid backup(system and boot), after that I wanted to install MIUI, so I flashed with flash GUI, all worked fine in the ROM, but after I wanted go back to meanrom I went to recovery, nandroid menu, cleared caches and restore partitions(I always do the same if the ROM I have don't like me), but for my surprise, phone doesn't boot, it shows the HTC white screen and after that just shows a black screen, the phone isn't turned off, it seems like a dimmed black screen. I tried to run adb to flash the boot.img but the pc doesn't recognize the device, I tried to restore only the boot partition in recovery and install meanrom again(ROM i had before) with no luck. I don't know what to do, any suggestions? Oh, I'm on hboot 1.5
You need to also wipe data when flashing a rom with a different base or boot.img. What I would do is boot recovery through adb and flash ROM/kernel from there.
Edit: also check out this thread for flashing boot.img on hboot 1.5
http://www.forums.infectedrom.com/showthread.php?p=10100
ssojyeti2 said:
You need to also wipe data when flashing a rom with a different base or boot.img. What I would do is boot recovery through adb and flash ROM/kernel from there.
Edit: also check out this thread for flashing boot.img on hboot 1.5
http://www.forums.infectedrom.com/showthread.php?p=10100
Click to expand...
Click to collapse
Yes, i wiped data and system too. And the first i tried was to flash ROM through adb but it says phone not found, is there a way to make the pc recognizes the phone?
luis4ever said:
Yes, i wiped data and system too. And the first i tried was to flash ROM through adb but it says phone not found, is there a way to make the pc recognizes the phone?
Click to expand...
Click to collapse
Yes install HTC sync for our phone and after it installs you need to uninstall it. This will install the drivers for our phone. You need to make sure usb debugging is enabled and plug your into your pc. It should work now.
Sent from my PG86100 using xda premium
ssojyeti2 said:
Yes install HTC sync for our phone and after it installs you need to uninstall it. This will install the drivers for our phone. You need to make sure usb debugging is enabled and plug your into your pc. It should work now.
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
Mmmmm, and how can i enable usb debugging if the phone doesn't boot to select that option?
luis4ever said:
Mmmmm, and how can i enable usb debugging if the phone doesn't boot to select that option?
Click to expand...
Click to collapse
Didn't think of that, but it should still work. Try getting into recovery by holding volume and power to turn phone on.
Sent from my PG86100 using xda premium
Well, i tried another pc and adb reboot bootloader works but when i write fastboot flash boot boot.img just says <waiting for device> and nothing happens. What should i do?
luis4ever said:
Mmmmm, and how can i enable usb debugging if the phone doesn't boot to select that option?
Click to expand...
Click to collapse
you dont try and do it from adb then... go to your bootloader screen by holding volume down and then the power button.....select fastboot and then hook your phone up to your data cable an use this command
fastboot flash boot boot.img
boot.img being the file that was saved in your backup flash that and that may fix your problem
wloftus said:
you dont try and do it from adb then... go to your bootloader screen by holding volume down and then the power button.....select fastboot and then hook your phone up to your data cable an use this command
fastboot flash boot boot.img
boot.img being the file that was saved in your backup flash that and that may fix your problem
Click to expand...
Click to collapse
In the message above i said adb worked in other pc but when i write fastboot flash boot boot.img just says waiting for device and nothing happens.
luis4ever said:
In the message above i said adb worked in other pc but when i write fastboot flash boot boot.img just says waiting for device and nothing happens.
Click to expand...
Click to collapse
fastboot and adb work at different times....adb is for when youre booted into the android
OSwith debugging turned on.... if you can run any adb commands then you can push any file you want.... but if no adb commands work you have to be in the bootloader area for fastboot to work....fast boot doesnt work when your at any htc boot screen it says its waiting for device bc its not set into fastboot usb modeagain.... turn the device off then hold the volume down buttonand press power.... friom there a screen will pop up and go through a file list and then come to a screen where the first option selected is "fastboot" press the power button from there and then hook up the data cable....you should see it say "fastboot usb" nowand from there you run
fastboot flash boot boot.img
fastboot commands only work in one spot in the set up just like adb commands only work when youre fully booted into the android os
wloftus said:
fastboot and adb work at different times....adb is for when youre booted into the android
OSwith debugging turned on.... if you can run any adb commands then you can push any file you want.... but if no adb commands work you have to be in the bootloader area for fastboot to work....fast boot doesnt work when your at any htc boot screen it says its waiting for device bc its not set into fastboot usb modeagain.... turn the device off then hold the volume down buttonand press power.... friom there a screen will pop up and go through a file list and then come to a screen where the first option selected is "fastboot" press the power button from there and then hook up the data cable....you should see it say "fastboot usb" nowand from there you run
fastboot flash boot boot.img
fastboot commands only work in one spot in the set up just like adb commands only work when youre fully booted into the android os
Click to expand...
Click to collapse
Yes i do that but cmd just says waiting for device
luis4ever said:
Yes i do that but cmd just says waiting for device
Click to expand...
Click to collapse
Are you able to boot into recovery holding volume down?
Sent from my PG86100 using xda premium
Idk if windows matters but i tried on a tablet with windows 8 with no luck, after I tried on a 64 bits windows 7 pc witness no luck but on a 32 bits windows 7 worked in the first try.
Your stuck in a bootloop and also you have lost you boot.IMG and you will have to exract from the zip folder of the Rom you have flashed and when that's done you will go to that folder and scroll down and you will see boot.IMG now copy and past it in the same folder that you have your adb and fastboot now open cmd and type fastboot flash boot boot.IMG and press enter and your EVO should reboot enjoy
Sent from my HTC EVO 3D X515m using xda premium
Droid DNA with Supercharged Hatka DNA got stuck in bootloop after running fine for over a year (ROM flashed last February)
I have a *fairly* recent backup if I could get it to boot to recovery, but I would prefer not to considering the 20ish Litecoins walleted on the device. I will be willing to give a whole Litecoin to whoever can fix my problem
Esploded said:
Droid DNA with Supercharged Hatka DNA got stuck in bootloop after running fine for over a year (ROM flashed last February)
I have a *fairly* recent backup if I could get it to boot to recovery, but I would prefer not to considering the 20ish Litecoins walleted on the device. I will be willing to give a whole Litecoin to whoever can fix my problem
Click to expand...
Click to collapse
Do you have adb? If you do the command is adb reboot recovery. Need to know more it just cycles? If so then try to push both power button and and both volumes until it has lights flashing at the bottom and reboots dont let go until it reboots. Other then that I am not sure. I tried to boot to recovery the manual way and it doesnt work. Which is why i Always use that to reboot recovery. Wait, I figured it out. Hold down volume power dont let go until bootloader comes up then let go of both. use volume down and select recovery and bam!
Okay so I tried holding down power and down volume to get into bootloader, it got me there and I could scroll to recovery, but it kept cycling the reboot before it would boot into recovery. I tried plugging it into the computer to use adb, but it just makes the plug/unplug USB sound in Windows. I also tried holding down all three buttons, and it makes no difference.
Esploded said:
Okay so I tried holding down power and down volume to get into bootloader, it got me there and I could scroll to recovery, but it kept cycling the reboot before it would boot into recovery. I tried plugging it into the computer to use adb, but it just makes the plug/unplug USB sound in Windows. I also tried holding down all three buttons, and it makes no difference.
Click to expand...
Click to collapse
Ok so if you have fastboot you should be able to use fastboot to flash recovery. If you are going to use a backup then you would need to have the same recovery image you used for the original. My suggestion is go to twrp and get the image. make sure you are plugged in at bootloader and fastboot is selected. IT should say fastboot usb if you are connected correctly on the top. I am assuming you have fastboot? If not my suggestion is to get minimal adb and fastboot it is the easiest. after you have installed run this command.
fastboot devices
it should come up with your device number if it doesnt then you need fastboot drivers. If it does then take the recovery.img you downloaded and place it in the same folder as your fastboot and adb folder. I suggest changing name to make it easier, I usually just change it to recovery.img instead of whatever it downloaded as. Then enter this command
fastboot flash recovery recovery.img
It should say sending and complete then enter this command
fastboot reboot recovery
bam you are in recovery!
jhr5474 said:
Ok so if you have fastboot you should be able to use fastboot to flash recovery. If you are going to use a backup then you would need to have the same recovery image you used for the original. My suggestion is go to twrp and get the image. make sure you are plugged in at bootloader and fastboot is selected. IT should say fastboot usb if you are connected correctly on the top. I am assuming you have fastboot? If not my suggestion is to get minimal adb and fastboot it is the easiest. after you have installed run this command.
fastboot devices
it should come up with your device number if it doesnt then you need fastboot drivers. If it does then take the recovery.img you downloaded and place it in the same folder as your fastboot and adb folder. I suggest changing name to make it easier, I usually just change it to recovery.img instead of whatever it downloaded as. Then enter this command
fastboot flash recovery recovery.img
It should say sending and complete then enter this command
fastboot reboot recovery
bam you are in recovery!
Click to expand...
Click to collapse
I'll give the fastboot utility a shot, hopefully it works. Thank you
Esploded said:
I'll give the fastboot utility a shot, hopefully it works. Thank you
Click to expand...
Click to collapse
IT is a lifesaver and so is adb once you learn how to use them you will be freed from lots of problems! Good luck.
jhr5474 said:
IT is a lifesaver and so is adb once you learn how to use them you will be freed from lots of problems! Good luck.
Click to expand...
Click to collapse
ADB tool is no help, computer will not recognize my phone even with all the HTC drivers installed. I'm at my wit's end, starting to believe something in the phone's hardware is messed up because nothing is working
Esploded said:
ADB tool is no help, computer will not recognize my phone even with all the HTC drivers installed. I'm at my wit's end, starting to believe something in the phone's hardware is messed up because nothing is working
Click to expand...
Click to collapse
Which adb drivers did you install and you need the fastboot drivers also. I have never found a phone that would not accept a fastboot command what OS are you on?
jhr5474 said:
Which adb drivers did you install and you need the fastboot drivers also. I have never found a phone that would not accept a fastboot command what OS are you on?
Click to expand...
Click to collapse
I only installed the HTC Sync and the ADB utility, I didn't know about ADB drivers. I'm on Windows 7
Esploded said:
I only installed the HTC Sync and the ADB utility, I didn't know about ADB drivers. I'm on Windows 7
Click to expand...
Click to collapse
All this stuff has been asked and answered a hundred times... Look here
http://forum.xda-developers.com/showthread.php?t=2131284
Get your ADB and Fastboot working. You will be fine.
sdamark said:
All this stuff has been asked and answered a hundred times... Look here
http://forum.xda-developers.com/showthread.php?t=2131284
Get your ADB and Fastboot working. You will be fine.
Click to expand...
Click to collapse
ADB and fastboot don't help, since it won't connect to any computer. I'm starting to think this is a hardware issue
I figured out what caused this. About a month ago, I was deleting unnecessary files, and it had been a year since I'd flashed my custom ROM so I forgot what the process involved. I accidentally deleted the 'sdcard' folder, and the phone became a ticking time bomb for it to stop working. I bricked it didn't I?
Esploded said:
I figured out what caused this. About a month ago, I was deleting unnecessary files, and it had been a year since I'd flashed my custom ROM so I forgot what the process involved. I accidentally deleted the 'sdcard' folder, and the phone became a ticking time bomb for it to stop working. I bricked it didn't I?
Click to expand...
Click to collapse
No, If you have twrp use adb push and push a rom to your phone and then flash it and your fine.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Esploded said:
Okay so I tried holding down power and down volume to get into bootloader, it got me there and I could scroll to recovery, but it kept cycling the reboot before it would boot into recovery. I tried plugging it into the computer to use adb, but it just makes the plug/unplug USB sound in Windows. I also tried holding down all three buttons, and it makes no difference.
Click to expand...
Click to collapse
If you can get into your rom, go to settings..power and at the bottom disable fastboot
Esploded said:
ADB and fastboot don't help, since it won't connect to any computer. I'm starting to think this is a hardware issue
Click to expand...
Click to collapse
1. Charge your phone (about 24 hours).
2. Let him rest (about 24 hours) without turning on.
3. Connect device to PC with original wire (Win7 preferred).
There is possibility that your BB will recognize phone.
Dear Community,
I got my Note 3 Pro Snapdragon Version today and I tried unlocking the bootloader, installing root and TWRP.
Unfortunately after I installed TWRP, WiFi didnt work anymore so I wanted to go back to where I was before.
i tried flashing the GlobalRom with the MiFlash Tool but somehow I'm now stuck with a bootloop.
The phone starts up and shows the MI Logo but doesnt go on. I tried booting TWRP temporarily via fastboot commands so that I can try to flash flashable zip files
but it doesnt let me execute "fastboot boot xyz.img" anymore because my device is locked.
I would really love to hear any solutions or ideas. I dont want any root or something anymore. If someone has an idea Im very happy!!!
thanks a lot in advance and tell me if you need any more infos
Paul/shisaya24
1. keep vol + and vol - pressed while connecting USB to enter adb mode
2. check if phone is connected with "adb devices" in command line, if phone shows up, enter "adb reboot edl"
3. now you can flash via MiFlash
Alex3oe said:
1. keep vol + and vol - pressed while connecting USB to enter adb mode
2. check if phone is connected with "adb devices" in command line, if phone shows up, enter "adb reboot edl"
3. now you can flash via MiFlash
Click to expand...
Click to collapse
First of all, HUGE thanks for your fast answer!
Unfortunately I couldnt get this to work. Since I am stuck at the Logog screen here is what I tried:
Pressing both volume buttons while Logo Screen and plugging USB.
Pressing both colume buttons while fastboot screen is up.
These two didnt enter adb mode, I guess because of the bootloop I'm in
I also tried antering recovery mode with volume up + power button. Pressing both volume buttons didnt help either but when I am in recovery like that it shows my device in adb as "sideload" device.
Maybe that helps ? Can you give further advice or am I doomed?
My idea would be: Is it possible to reflash the device completely only usinf fastboot? The only thing I seem to be able to enter is fastboot...
Is there a way from fastboot to "working phone" ?
or maybe through the "adb sideload" state?
thanks a lot in advance!
Paul
EDIT
tried installing via "adb sideload xyz.zip" command but after shortly showing a status bar on phone screen it aborted and said "Total xfer: 0.00x" on PC screen .
Also: I read "adb reboot edl" brings you to download mode so you can flash something. Tried it but the phone just rebooted the normal system, so it stuck on Logo again...
search miui forum for unbrick, there is 2 or 3 method without opening your device
exp: http://en.miui.com/forum.php?mod=viewthread&tid=257227
Unfortunately they all do not work because they always require either a phone in download mode, and i only get to fastboot and adb sideboard or they require flashing something via fastboot but I can't do that either because it says my device is locked if I try...
Any suggestions how to flash a ROM with fastboot only or with adb sideload?
Thanks a lot
Paul
shisaya24 said:
Unfortunately they all do not work because they always require either a phone in download mode, and i only get to fastboot and adb sideboard or they require flashing something via fastboot but I can't do that either because it says my device is locked if I try...
Any suggestions how to flash a ROM with fastboot only or with adb sideload?
Thanks a lot
Paul
Click to expand...
Click to collapse
I Had The Same Issue Brother ! There are only 2 Things which you can do now .
1. Test Point Method to enter EDL
2.Give it to Service Center . I Gave Mine to Service Center ,They Fixed it in 30 mins or less and it was free
Dharani_V said:
I Had The Same Issue Brother ! There are only 2 Things which you can do now .
1. Test Point Method to enter EDL
2.Give it to Service Center . I Gave Mine to Service Center ,They Fixed it in 30 mins or less and it was free
Click to expand...
Click to collapse
Can I do the test point thing myself or is it risky?
What kind of service center? A general mobile phone repair shop or a Xiaomi special one?
shisaya24 said:
First of all, HUGE thanks for your fast answer!
Unfortunately I couldnt get this to work. Since I am stuck at the Logog screen here is what I tried:
Pressing both volume buttons while Logo Screen and plugging USB.
Pressing both colume buttons while fastboot screen is up.
These two didnt enter adb mode, I guess because of the bootloop I'm in
I also tried antering recovery mode with volume up + power button. Pressing both volume buttons didnt help either but when I am in recovery like that it shows my device in adb as "sideload" device.
Maybe that helps ? Can you give further advice or am I doomed?
My idea would be: Is it possible to reflash the device completely only usinf fastboot? The only thing I seem to be able to enter is fastboot...
Is there a way from fastboot to "working phone" ?
or maybe through the "adb sideload" state?
thanks a lot in advance!
Paul
EDIT
tried installing via "adb sideload xyz.zip" command but after shortly showing a status bar on phone screen it aborted and said "Total xfer: 0.00x" on PC screen .
Also: I read "adb reboot edl" brings you to download mode so you can flash something. Tried it but the phone just rebooted the normal system, so it stuck on Logo again...
Click to expand...
Click to collapse
I've been facing the same (or a similar?) problem about a week ago but managed to get out. Knowing me for having a head like a sieve I made some notes, sadly quite rudimentary
Did you try to flash with MiFlash after "adb reboot edl"? If I remember rightly after "adb reboot edl" you got the logo like booting another way, but the light is blinking red. Then I could flash via MiFlash.
I'm quite sure that if you get a "reboot" after entering "adb reboot edl", your phone will be in edl mode.
I will try that this evening when I am at home again and report. Thanks
Alex3oe said:
I've been facing the same (or a similar?) problem about a week ago but managed to get out. Knowing me for having a head like a sieve I made some notes, sadly quite rudimentary
Did you try to flash with MiFlash after "adb reboot edl"? If I remember rightly after "adb reboot edl" you got the logo like booting another way, but the light is blinking red. Then I could flash via MiFlash.
I'm quite sure that if you get a "reboot" after entering "adb reboot edl", your phone will be in edl mode.
Click to expand...
Click to collapse
Unfortunately this doesnt work. Phone reboots and shows MI Logo but red light doesnt blink and MiFlash doesnt recognize any devices.
Do you have another idea? :/
How did you unlock the bootloader, via official permission or that unofficial hack?
Sent from my Moto G using Tapatalk
I didnt use the official way :/ Im so hoping my phone isnt broken. I wish i owuld have been more patient
shisaya24 said:
I didnt use the official way :/ Im so hoping my phone isnt broken. I wish i owuld have been more patient
Click to expand...
Click to collapse
Only options you have right now are:
1) using test points method which is a but cumbersome and voids warranty if you care about that.
2) go to a xiaomi service center of you have any nearby.
It is hard bricked.
So there is absolutely no option to unlock bootlader via adb sideload or fastboot ?
shisaya24 said:
So there is absolutely no option to unlock bootlader via adb sideload or fastboot ?
Click to expand...
Click to collapse
Apparently, no! Whenever using unofficial methods, read precautions carefully and you missed all as I can see. Wait if someone can help you out.
apply official unlock. then unlock your device from fastboot mode.
asaharaSK said:
apply official unlock. then unlock your device from fastboot mode.
Click to expand...
Click to collapse
That sounds nice and easy. I already applied for official unlock.
But: do you know if u can use the official unlock now? I can only access fastboot and adb sideload mode. Is it possible to activate official unlock from there? Or do I need a working ROM rather?
I would have thought that official unlock doesn't work from fastboot /adb sideload...
shisaya24 said:
That sounds nice and easy. I already applied for official unlock.
But: do you know if u can use the official unlock now? I can only access fastboot and adb sideload mode. Is it possible to activate official unlock from there? Or do I need a working ROM rather?
I would have thought that official unlock doesn't work from fastboot /adb sideload...
Click to expand...
Click to collapse
Does anyone know this?
I have the same problem. I made the same mistakes as shisaya24. I have followed every procedure for unbricking and nothing works. I even applied for an unlock code and got it from Xiomi. I used their mi-unlock app which requires fastboot (pwr/vol-) but it gets to 50% and bombs out. It states it can't verify the phone. Can anyone please help me??
smiley1960 said:
I have the same problem. I made the same mistakes as shisaya24. I have followed every procedure for unbricking and nothing works. I even applied for an unlock code and got it from Xiomi. I used their mi-unlock app which requires fastboot (pwr/vol-) but it gets to 50% and bombs out. It states it can't verify the phone. Can anyone please help me??
Click to expand...
Click to collapse
out of sheer desperation I tried MiPhone again and after a few tries, MiPhone started updating the OS. My phone now works again and I have an unlock code as well.
Hi all, I wonder if anybody can help with this.
my volume buttons are not working (hardware issue) and I was trying to install TWRP and a custom rom but, after installing TWRP the phone now always boots in recovery mode (at least this is what adb tells me) but TWRP does not really start, I keep seeing only "honor, powered by android" black screen.
adb is working but not fastboot. I tried to reboot to bootloader but it always go to recovery instead. I have no su, and I am stuck just with adb in recovery.
any idea?
If you have full adb access maybe you can restore your backup directly from it
Thanks Rayan
how? what do you mean by "full adb access"?
I tried to run adb sideload but it does not work (it says "closed" shortly after without doing anything)
I don't really understand what the issue is, do you have access to TWRP menu or not at all? And when you say that you can use adb, is the device recognized when you type adb devices ? And what happens when you try to boot in bootloader and use fastboot? Can you try to the command "adb reboot bootloader"?
Rayan19997 said:
I don't really understand what the issue is, do you have access to TWRP menu or not at all? And when you say that you can use adb, is the device recognized when you type adb devices ? And what happens when you try to boot in bootloader and use fastboot? Can you try to the command "adb reboot bootloader"?
Click to expand...
Click to collapse
Thanks Rayan, I finally solved replacing the volume buttons (found cheap ones). However adb was working but no matter which command I was sending (adb reboot bootloader) the phone was always rebooting in recovery mode but TWRP was not starting properly (could not see anything)
with volume buttons I managed to enter into bootloader, reflash TWRP and do everything I needed
Thanks
So I want access the TWRP through fastboot command( since volume up + power botton wont work) but it's not reconizing the device.
I have USB debug on and I don't know if i have OEM unlock mode on because I can't find it in the developer tab.
I only want to root the device so I can install the google cam.
Any suggestions ?
Tiigs said:
So I want access the TWRP through fastboot command( since volume up + power botton wont work) but it's not reconizing the device.
I have USB debug on and I don't know if i have OEM unlock mode on because I can't find it in the developer tab.
I only want to root the device so I can install the google cam.
Any suggestions ?
Click to expand...
Click to collapse
RR should also have advanced reboot in developer options. You can than simply reboot into recovery.
Noter2017 said:
RR should also have advanced reboot in developer options. You can than simply reboot into recovery.
Click to expand...
Click to collapse
Thanks for the reply.
The problem is that I have no way of reaching TWRP , If I do the Power+ volume up I will go to the MI-recovery 3.0.
What I do is, I restart the phone and only hold down the volume up button after the screen goes black. That always gets me into TWRP. But I usually use the advanced power menu because that's way easier.
Fixed the fastboot not get recognized on my computer.
I had to disable driver signature verification. Then I installed the proper TWRP version. Now the Volume up + power goes strait to the TWRP.
I am just posting here someone might find useful.
ty all for the help.
Tiigs said:
Fixed the fastboot not get recognized on my computer.
I had to disable driver signature verification. Then I installed the proper TWRP version. Now the Volume up + power goes strait to the TWRP.
I am just posting here someone might find useful.
ty all for the help.
Click to expand...
Click to collapse
Did you forget to boot into your recovery.img after flashing TWRP via fastboot? "fastboot boot recovery.img". A lot of guides stupidly leave that out.
sk8223 said:
Did you forget to boot into your recovery.img after flashing TWRP via fastboot? "fastboot boot recovery.img". A lot of guides stupidly leave that out.
Click to expand...
Click to collapse
No my problem was that I could not even call fastboot through console because my computer wont recognize the device. If i called "fastboot devices" on the console it would not show any answer. Disabling driver signature verification made my computer recognize the smartphone usb , so all the fastboot commands worked as intended again .
You have driver problems, donwload the latest adb or install a virtual machine with Ubuntu or Debian, after that install android-tools-adb and android-tools-fastboot. Then connect your phone to the virtual machine and access adb from there.