Related
Anyone else have this problem?
numus said:
Anyone else have this problem?
Click to expand...
Click to collapse
So is fastboot the problem or are you trying to boot to recovery through the bootloader. I would use ADB instead of fastboot. But if what you're asking is that you want to boot to recovery from the bootloader, just connect your USB cable to your computer and then select recovery in the bootloader.
CharliesTheMan said:
So is fastboot the problem or are you trying to boot to recovery through the bootloader. I would use ADB instead of fastboot. But if what you're asking is that you want to boot to recovery from the bootloader, just connect your USB cable to your computer and then select recovery in the bootloader.
Click to expand...
Click to collapse
Pretty sure it is fastboot... You use the volume rocker to select recovery and hit the power button... It shows the Bootscreen but doesn't go any further than that.
Edit: it says in red FASTBOOT MODE.. When i select recovery it goes tot he google screen (witht he unlock icon) and doesn't go any further than that.
numus said:
Anyone else have this problem?
Click to expand...
Click to collapse
I'm having trouble too. I have it plugged in to my laptop. When I select "Recovery" and press Power, it just reboots, and then boots into Android.
No recovery.
So I'm gonna try TWRP..
i had the same issue this is what i did
download new recovery h**p://goo.im/devs/OpenRecovery/grouper/openrecovery-twrp-2.2.1.4-grouper.img
then in fastboot
fastboot erase recovery
fastboot flash recovery name_of_recovery.img
wait 15 seconds
unplug usb cable
then use volume keys to boot in to recovery
hope this helps
so any solution at the same screen, same problem.
dj_denims said:
i had the same issue this is what i did
download new recovery h**p://goo.im/devs/OpenRecovery/grouper/openrecovery-twrp-2.2.1.4-grouper.img
then in fastboot
fastboot erase recovery
fastboot flash recovery name_of_recovery.img
wait 15 seconds
unplug usb cable
then use volume keys to boot in to recovery
hope this helps
Click to expand...
Click to collapse
You want to be in the bootloader mode and select recovery. The trick is that to do that, you have to have your Asus USB cable connected to a live usb port when you do it, and it usually works if recovery isn't damaged.
And you can also use Wug's toolkit on the computer, or if you can boot the tablet, you can use goo manager to reboot to recovery, or the Trinity kernel app, or your rom's advanced power menu.
With the USB cable attached from the computer to tablet, here's what I did:
- Went to bootloader
- Did "fastboot erase recovery"
- Did "fastboot flash recovery IMG"
- Then boot to recovery manually from the device itself via volume buttons and Power
Hasn't failed me yet when trying out different recoveries. There was some issue a while back where you had to have the USB cable hooked to your computer and Nexus 7 in order to get to recovery. Not sure if the bug still exists, but it may be worth trying with the cable in.
Also you probably have to have an unlocked bootloader (lock at bottom of Google boot screen).
dj_denims said:
i had the same issue this is what i did
download new recovery h**p://goo.im/devs/OpenRecovery/grouper/openrecovery-twrp-2.2.1.4-grouper.img
then in fastboot
fastboot erase recovery
fastboot flash recovery name_of_recovery.img
wait 15 seconds
unplug usb cable
then use volume keys to boot in to recovery
hope this helps
Click to expand...
Click to collapse
Thanks for that.
That worked for me
Does the USB port you're plugged into need to be a computer with the fastboot drivers already installed? My unit freezes up in bootloader every time I plug in any live USB cable, whether it's a computer or not. My recovery is fine, but with the bootloader constantly freezing I'm not able to install the N7 drivers on my computer, let alone input any fastboot commands. And no, I don't have access to the computer with the drivers already installed sadly.
Sent from my SGH-T989 using xda premium
Turn it off plug USB lead into PC/laptop and nexus hold volume up and down and turn it on, or it also works via my otg cable in my s3 also, its a bug..
Sent from my Nexus 7 using Tapatalk 2
a stupid bug.buoght yesterday,rooted and unlocked.downloaded 10 roms,all kernels,and now that i'm ok to begin test i tried without luck to enter recovery from fastboot (i didn't know this fact)but my cable was inserted on pc usb port...and strange it doesn't work.yestrerday via fastboot i flashed twrp recovery that i love and use also on mine gnexs.i'm on stock rom yet,and without "reboot to recovery" option in powermenu.i reflashed twrp,cwm touch (in fastboot manually)then the same but with a rootkit,no luck.i began to think i have a problem in my device and i don't know how to do because it's a secondary bug for assistance i think..and i read this post.don't even tried commands in few posts ago,already did same things an hour ago.i installed quickboot frm playstore and now i can boot on TWRP.use this for today,when i begin to test roms i'll have the powermenu option!
Sad this,i'm a bit anxious of this bug,because i soft brick gnex every 2\3 days,always trying things and stuff,kernel with modifications by me etc,and i often have to go in cwm via devices off and fastboot before...i see that my tab attacched at pc don't enter recovery from fastboot mode..and it's a problem for me.hope someone discover where is this bug and find a workaround\fix fro that.
cheers
sert00 said:
a stupid bug.buoght yesterday,rooted and unlocked.downloaded 10 roms,all kernels,and now that i'm ok to begin test i tried without luck to enter recovery from fastboot (i didn't know this fact)but my cable was inserted on pc usb port...and strange it doesn't work.yestrerday via fastboot i flashed twrp recovery that i love and use also on mine gnexs.i'm on stock rom yet,and without "reboot to recovery" option in powermenu.i reflashed twrp,cwm touch (in fastboot manually)then the same but with a rootkit,no luck.i began to think i have a problem in my device and i don't know how to do because it's a secondary bug for assistance i think..and i read this post.don't even tried commands in few posts ago,already did same things an hour ago.i installed quickboot frm playstore and now i can boot on TWRP.use this for today,when i begin to test roms i'll have the powermenu option!
Sad this,i'm a bit anxious of this bug,because i soft brick gnex every 2\3 days,always trying things and stuff,kernel with modifications by me etc,and i often have to go in cwm via devices off and fastboot before...i see that my tab attacched at pc don't enter recovery from fastboot mode..and it's a problem for me.hope someone discover where is this bug and find a workaround\fix fro that.
cheers
Click to expand...
Click to collapse
Paragraphs dude? Or at the very least, proper spacing.
On stock rooted rom, flash latest TWRP recovery. openrecovery-twrp-2.2.2.0-grouper.img
adb reboot bootloader
fastboot flash recovery openrecovery-twrp-2.2.2.0-grouper.img
Then install Rom Toolbox. Use the "Rebooter" to Reboot recovery, and you should have no issues.
..
mvmacd said:
Paragraphs dude? Or at the very least, proper spacing.
On stock rooted rom, flash latest TWRP recovery. openrecovery-twrp-2.2.2.0-grouper.img
adb reboot bootloader
fastboot flash recovery openrecovery-twrp-2.2.2.0-grouper.img
Then install Rom Toolbox. Use the "Rebooter" to Reboot recovery, and you should have no issues.
Click to expand...
Click to collapse
I did this and I still can't boot into recovery. The only way I can boot into recovery is if I use the fastboot command. The rom toolbox does not work for me.
similar problem
I have somewhat similar problem. Well, actually the problem is not very uncommon the way it looks, but usual solutions do not work.
Basically I have erased my old rom (rebooted to recovery from aokp menu) and erased my rom. I've tried mounting the device from the recovery mode, but it was not recognised on my PC. I assumed that this was an Win8 issue.
Once I've rebooted, I could no logger boot to recovery (after selecting recovery all I got was google logo). I've thought of flashing recovery via fastboot, but bootloader seams to freeze with usb cable in (no matter the cable) and resetting does not help (the way it helped others). Also I cannot fastboot at that time either as PC (neither win8 nor win7 machine can see the device).
Any ideas would be appreciated.
When the bootloader freezes with the usb cable plugged into a PC, it is a driver issue. Uninstall and reinstall the drivers. I have experienced this on a win7 x64 system.
It isn't a driver issue as the same thing happens when connecting to a charger and not the PC.
It happens on mine as well.
Well it wouldn't crash with wall charger if it was a PC driver issue.
In either case, I've actually figured out what's the problem. It seems that usb connector is not very reliable. If the it usb connection is poor, the bootloader crashes. To avoid this issue you have to bend the cable towards the screen to ensure the proper connection. It load that way just fine.
Edit: or not... probably bending just removed the connection completely...
Edit2: did not figure out what was the problem, but after playing around some more, the phone has popped up in computer manager and I was able to continue from there. After flashing the recovery (twm -> cwm), the bootloader un-froze as well.
Hi Guys,
I'm stuck in the endless boot logo problem, I installed google drivers, I'm able to get into recovery mode.
the device manager in win7 reports a "android ADB Device" connected.
but when I issues some of the commands in this guide http://forum.xda-developers.com/showthread.php?t=1907796 (like adb devices) it doesn't show anything...
What I've to do?? Am I doing something wrong?
thanks
Can you restore your nandroid/twrp backup? If not, fastboot back to stock and start over.
Sent from my Nexus 7 using XDA Premium HD app
peneoark said:
Can you restore your nandroid/twrp backup? If not, fastboot back to stock and start over.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Already did that with no success... .
If your device is rooted, installed a custom recovery and you're able to get into recovery mode Windows should be able identify your device without asking for RSA fingerprint or something.
Get into recovery mode and try "adb devices" from cmd after connecting your device to pc. What do you see?
Djabolic said:
If are rooted, installed a custom recovery and you're able to get into recovery mode Windows should be able identify your device without asking for RSA fingerprint or something.
Get into recovery mode and try "adb devices" from cmd after connecting your device to pc. What do you see?
Click to expand...
Click to collapse
I'm not rooted,
when rebooting with power and vol- windows recognize the device but "adb devices" gives nothing"
If I select recovery mode the nexus disappears from windows device manager
Check windows device manager to see if you can find any devices without drivers especially something about ADB or Android.
Djabolic said:
Check windows device manager to see if you can find any devices without drivers especially something about ADB or Android.
Click to expand...
Click to collapse
Nothing, when in bootloader (the one with the green robot win belly open) it gets recognized as "bootloader adb interface"; when in recovery (green robot with red exclamation mark) there is nothing in device manager
lmalossi said:
Nothing, when in bootloader (the one with the green robot win belly open) it gets recognized as "bootloader adb interface"; when in recovery (green robot with red exclamation mark) there is nothing in device manager
Click to expand...
Click to collapse
So you can issue commands over fastboot then? You can flash stock firmware images over fastboot to get everything working again.
Djabolic said:
So you can issue commands over fastboot then? You can flash stock firmware images over fastboot to get everything working again.
Click to expand...
Click to collapse
but when if fastboot the command "adb devices" return nothing...
When you're in fastboot mode you don't see your device online over adb, you can freely issue any commands from fastboot if your computer recognizes the bootloader interface.
Follow this guide to flash nexus 7 stock firmware;
http://forum.xda-developers.com/showthread.php?t=1907796
Djabolic said:
When you're in fastboot mode you don't see your device online over adb, you can freely issue any commands from fastboot if your computer recognizes the bootloader interface.
Follow this guide to flash nexus 7 stock firmware;
http://forum.xda-developers.com/showthread.php?t=1907796
Click to expand...
Click to collapse
I was already following your guide....
Didn't know that if I was already in fastboot mode I could issue fastboot commands even if adb devices didn't show anything...
N00b Error!! Now the thing is clearer to me
Flashed image, and the tablet appears to be working :fingers-crossed:
Thank you very much!!
Luca
Introduction
The purpose of this guide is to provide you with step-by-step instructions on how to unlock the bootloader on your Nvidia Shield.
Why Would I want to Unlock my Bootloader?
Unlocking your bootloader allows you to modify all aspects of your device to suite your needs which includes but is not limited to, installing custom Recovery images such as Clockworkmod Recovery or Team Win Recovery Project, installing custom ROM's, custom Kernels, as well as other MOD's and patches.
Will Unlocking my Bootloader Void my Warranty?
Warning: Unlocking your Nvidia Shield's bootloader will void the warranty, please note that even if you re-lock the bootloader the bootloader still show a flag that the device is voided for warranty.
This warning being given please also see this post by JordanKeyes regarding warranty information as it relates to hardware issues or hardware failures.
Unlocking your Bootloader
1. Backup everything on your device that you don't want to loose such any apps (And there respective data), pictures, videos, music, etc. as unlocking your devices bootloader will erase all data on the device. You can fully backup your devices contents without root using ADB's backup command or by using the Holo Backup Tool.
2. Download and install the ADB and Fastboot drivers for your Shield, the drivers can be downloaded here. You can also follow along with wwjoshdew's excellent video tutorial on how to properly install the ADB and Fastboot drivers for your Shield on Windows.
3. Make sure you have ADB and Fastboot setup and installed on your computer. If you haven't already setup and installed ADB and Fastboot a simple ADB and Fastboot installer can be downloaded from here.
4. Fully power off your Shield by long pressing on the Power button until the power menu appears, then select the "Power off" option.
5. Boot your Shield into Fastboot mode using one of the following ways:
5. A. Power on your Shield while simultaneously holding the Power button + Back button + Home button. Release the buttons once the Fastboot bootloader screen appears.
5. B. Run the following ADB command from a command prompt window (USB cable must already be connected from your Shield to your Computer):
Code:
adb reboot bootloader
6.Now that you are at the Fastboot bootloader screen, connect your Shield to your computer using your USB cable. Make sure that your USB cable is plugged into a USB 2.0 port directly connected to your motherboard as sometimes USB 3.0 ports can cause problems and front panel USB connections can be unreliable.
7. Open up a command prompt window (cmd) in the directory where installed ADB and Fastboot to. For example if I installed ADB and Fastboot to a folder on my Desktop which is on my D: drive I would open a command window in "D:\Desktop\Fastboot_ADB".
8. From the command prompt windows enter the following command:
Code:
fastboot devices
If you device is detected and it shows your devices serial number you are ready to move on to the next step. If no device is shown make sure you have the correctly installed the ADB and Fastboot drivers from step number 2.
9. Now that your device is detected by Fastboot the following command is used to unlock your bootloader:
Code:
fastboot oem unlock
10. You will now be presented with the bootloader unlock menu. After reading the disclaimer, use the Back button and the Home button to navigate to the "Unlock" option. Once the "Unlock" option has been highlighted use the Shield button to confirm your selection of unlocking your bootloader. It's important to remember that unlocking the bootloader will wipe all your data from the device, and that a flag showing your warranty is void will appear at the bootloader screen.
11. Once your bootloader has finished being unlocked, you will be taken back to the fastboot bootloader screen. From here you can power off your Shield.
Re-locking your Bootloader
To re-lock your bootloader you can following steps 4-8 of the procedure listed above and when you come to step 9 run the following command instead of "fastboot oem unlock":
Code:
fastboot oem lock
The above command will re-lock your Shield's bootloader. Note: As previously mentioned re-locking your Shield's bootloader will not restore your warranty or remove the warranty void flag on your device's bootloader.
Conclusion
Now that you have successfully unlocked the bootloader on your Nvidia Shield you are free to flash custom Recoveries, ROM's, Kernel's, MOD's etc. enjoy :good:.
If you are stuck with the bootloader unlocking procedure I would recommend checking out this great video tutorial by wwjoshdew.
I'm having an issue unlocking the bootloader. I have the drivers and fastboot install successfully as well as adb and fastboot. I run the command "adb reboot bootloader" which reboots my shield into bootloader but when I run "fastboot devices" nothing shows up. USB debugging is enabled.
When the device is booted normally the command "adb devices" picks up the device. It is only in fastboot that adb commands aren't recognized.
I added a picture, any thoughts?
Edit: followed the instructions in the following video and all is dandy now. http://www.youtube.com/watch?v=XSisjVwcPbE&hd=1
themichael said:
I'm having an issue unlocking the bootloader. I have the drivers and fastboot install successfully as well as adb and fastboot. I run the command "adb reboot bootloader" which reboots my shield into bootloader but when I run "fastboot devices" nothing shows up. USB debugging is enabled.
When the device is booted normally the command "adb devices" picks up the device. It is only in fastboot that adb commands aren't recognized.
I added a picture, any thoughts?
Click to expand...
Click to collapse
Look in device manager and check if the PC recognizes the shield as an adb device when in fastboot.
For me i have to switch between using fastboot and being able to copy files to it.
fastboot error
chevyowner said:
Look in device manager and check if the PC recognizes the shield as an adb device when in fastboot.
For me i have to switch between using fastboot and being able to copy files to it.
Click to expand...
Click to collapse
Hi i am having issue with dab and fast boot drivers.
When I install the driver as adb I can't fast boot to install the thor.img but once it reboots It reverts or reinstalls a shield driver and causes confusion and blocks when I want to mount.
gogul1 said:
Hi i am having issue with dab and fast boot drivers.
When I install the driver as adb I can't fast boot to install the thor.img but once it reboots It reverts or reinstalls a shield driver and causes confusion and blocks when I want to mount.
Click to expand...
Click to collapse
Nvidia just released a new set of USB drivers in their Tegra for Android Development Pack which you can download from here. I would recommend installing the development pack and the drivers it includes.
ok
I have done it and these are the new drivers I have under device manager.
Still can't mount though, operation not permitted Usb debugging enabled.
here are the two new drivers which let me get as far as the mount command but no further
View attachment 2210144
and here's it telling me no in abd and fastboot
View attachment 2210148
gogul1 said:
I have done it and these are the new drivers I have under device manager.
Still can't mount though, operation not permitted Usb debugging enabled.
here are the two new drivers which let me get as far as the mount command but no further
View attachment 2210144
and here's it telling me no in abd and fastboot
View attachment 2210148
Click to expand...
Click to collapse
From that pic you posted the mount command failed because you were not root.
chevyowner said:
From that pic you posted the mount command failed because you were not root.
Click to expand...
Click to collapse
I have updated the original post in my manual rooting procedure thread that includes a new insecure boot.img that has a patched adbd binary to allow the insecure boot.img to provide a root shell when booted from.
shimp208 said:
I have updated the original post in my manual rooting procedure thread that includes a new insecure boot.img that has a patched adbd binary to allow the insecure boot.img to provide a root shell when booted from.
Click to expand...
Click to collapse
Huh??????????
EDIT
Were you trying to answer this post
chevyowner said:
Huh??????????
EDIT
Were you trying to answer this post
Click to expand...
Click to collapse
Oh what I meant chevyowner was since you had responded to that guy's post about him not having a root shell after booting the insecure boot.img I decided to jump in and mention I had updated the original post to include a new updated insecure boot.img that should fix his root shell problem. Sorry for any confusion I caused there buddy!
shimp208 said:
Oh what I meant chevyowner was since you had responded to that guy's post about him not having a root shell after booting the insecure boot.img I decided to jump in and mention I had updated the original post to include a new updated insecure boot.img that should fix his root shell problem. Sorry for any confusion I caused there buddy!
Click to expand...
Click to collapse
No problem.
I had to change to oil in my car in a parking lot earlier because it was cheaper to change it then it would have been add 3-4 quarts and change it when I got home. My car need 5 quarts of oil. I was not in a a good mood then.
I made two videos on the NVIDIA Shield. Please let me know what you think @shimp208.
How To Unlock the Bootloader: http://www.youtube.com/watch?v=7Am5WYRojMs
How To Root the Nvidia Shield: http://www.youtube.com/watch?v=_4-C0CzKoFs
thx. works nice.
wwjoshdew said:
I made two videos on the NVIDIA Shield. Please let me know what you think @shimp208.
How To Unlock the Bootloader: [
How To Root the Nvidia Shield: []
Click to expand...
Click to collapse
Sweet thanks
wwjoshdew said:
I made two videos on the NVIDIA Shield. Please let me know what you think @shimp208.
How To Unlock the Bootloader: http://www.youtube.com/watch?v=7Am5WYRojMs
How To Root the Nvidia Shield: http://www.youtube.com/watch?v=_4-C0CzKoFs
Click to expand...
Click to collapse
I tried another proggie to root and got jammed up.. following the videos josh did had me rooted in minutes. Great job and thanks!
why?
Code:
C:\Users\Thomas>fastboot oem unlock
...
FAILED (command write failed (Unknown error))
finished. total time: 0.582s
I tried it with the Shield RAM tool, but won't work either..
so, i managed to root and install custom recovery without touching the bootloader. the status still reads as locked, but i am free to mod and install custom roms and such. i used towelroot apk. and flashify to flash the recovery image.
mr.dude5660 said:
so, i managed to root and install custom recovery without touching the bootloader. the status still reads as locked, but i am free to mod and install custom roms and such. i used towelroot apk. and flashify to flash the recovery image.
Click to expand...
Click to collapse
Where did you find the towelroot apk? Been searching for over a month with no success.
Sent from my VS980 4G using Tapatalk
BTW, bootloader mode on the tablet:
- Hold "Volume Down" -> Press "Power" and continue to hold "Volume Down" until device boots into bootloader mode.
There is no home or back button to press while the device is off.
Sorry for bump this thread, but i have to.
I want to unlock my bootloader to revert back into KK and then try to do a clean installation of LP. Reading this guide and watching the videos, and also looking into the img downloaded from nvidia, it says i have to install the fastboot drivers. The problem is that i have already installed fastboot and adb drivers since i have some other devices as a Xperia and stuff. For me, there is no Yellow sign as shown in the video, my device is recognized as Portable Device and it already says "Shield Tablet" MTP.
I've tried going into bootloader to see if it prompts any new devices but i got nothing. adb devices show my device, but i'm not sure if i need more.
So I tried to update to KitKat 4.4 and was never able to get passed the loading screen. I booted into ClockworkMod Recovery and wiped everything and now the device will not go passed the Google loading screen. The device is no longer recognized when I plug into the computer and I cannot access through Wugs.
I called Google and they are sending out an RMA for this device (I did not tell them it was unlocked) and they are sending out a replacement.
Is there anyway that I can remove ClockworkMod Recovery and re-lock this device without being able to access the device through a computer?
BrianXP7 said:
Whoa, RMA's should be only used for last resort bootloader bricks! Since you still have the bootloader ("Google" logo at startup), hold Power + Volume Down to enter Fastboot mode and try reflashing the factory images. Just to be safer, use the Universal Naked Drivers and skip with bootloader image. Don't forget to have the ADB and Fastboot binaries in the same folder. I wouldn't recommend toolkits as they don't expose new users with these situations.
If you need anything else, let me know. If I completely missed on what you needed, sorry about that.
Also, just as long as the bootloader update isn't interrupted or type "fastboot erase bootloader" you should be fine without an RMA.
Click to expand...
Click to collapse
thanks for the reply.
I am able to boot in recovery mode on the device and this is recognized by Wugs as "ADB - device on". When I attempt any flash, it checks Fastboot status and I receive notification that the "Fastboot device was not found". I cannot find a compatible driver when I am in fastboot mode running on a Windows 7 x64 machine.
Any idea on how I can get this N7 to function, return to stock, or at least remove ClockworkMod and lock the bootloader so I can RMA?
Hi.
Recently I decided to flash lineage os 15.1 on my MiA1
For that I have downgrade to Android nougat.
After downgrading I booted my device.
After setting up device I booted device in fastboot mode to follow further steps like flashing TWRP and all but the problem is my device goes in fastboot mode and it is not identified by abd and after that it is automatically getting restarted and is not holding in fastboot mode.
Please help??
Odd issue. What are you using to flash? If you are using XiaoMiFlash.exe, you'll want to try the (THIS WILL REMOVE ALL YOUR DATA) "clean all" option. Please note that this removes all your data.
I have used MiFlash tool for this and now My device automatically reboot from fastboot mode so I am not able to use adb as well to flash rom or twrp also Now MiFlash tool is not recognising the device.
MrUsamahh said:
I have used MiFlash tool for this and now My device automatically reboot from fastboot mode so I am not able to use adb as well to flash rom or twrp also Now MiFlash tool is not recognising the device.
Click to expand...
Click to collapse
Hmm. What ROM version are you trying to flash on this? If your device isn't recognized by your PC when in fastboot mode, I'm not sure how you'd flash it.
oreo27 said:
Hmm. What ROM version are you trying to flash on this? If your device isn't recognized by your PC when in fastboot mode, I'm not sure how you'd flash it.
Click to expand...
Click to collapse
I flashed Android N Fastboot rom by selecting Clean and lock option.
After that the problem started
MrUsamahh said:
I flashed Android N Fastboot rom by selecting Clean and lock option.
After that the problem started
Click to expand...
Click to collapse
It should boot if you've fully flashed it and cleaned the user data partition. If it still isn't, you'll want to wait for other members with more experience in bricks to chime in.
oreo27 said:
It should boot if you've fully flashed it and cleaned the user data partition. If it still isn't, you'll want to wait for other members with more experience in bricks to chime in.
Click to expand...
Click to collapse
My device is booting up without any problems.
But the problem is bootloader is still unlocked. So i am not able to update via OTA.
And as the device does not holds in fastboot mode so I am not able to do other flash work.
Is there any way I can share a video of my problem with you?
MrUsamahh said:
My device is booting up without any problems.
But the problem is bootloader is still unlocked. So i am not able to update via OTA.
And as the device does not holds in fastboot mode so I am not able to do other flash work.
Is there any way I can share a video of my problem with you?
Click to expand...
Click to collapse
Oh. If it's booting up fine, then you shouldn't be worried too much.
If it keeps restarting in Fastboot mode, it could be a driver issue which is preventing your PC from recognizing your device and vice versa. I'm on Windows 10 which installs drivers automatically so I've never had experience with it.
oreo27 said:
Oh. If it's booting up fine, then you shouldn't be worried too much.
If it keeps restarting in Fastboot mode, it could be a driver issue which is preventing your PC from recognizing your device and vice versa. I'm on Windows 10 which installs drivers automatically so I've never had experience with it.
Click to expand...
Click to collapse
https://photos.app.goo.gl/TyLendNH7XaY74bs1
Please see this video.
If i boot in fastboot mode the device should be in fastboot mode till power button is not pressed for at least 10 seconds.
But in this case it gets switched off.
I have not connected the USB to pc and nothing else.
MrUsamahh said:
https://photos.app.goo.gl/TyLendNH7XaY74bs1
Please see this video.
If i boot in fastboot mode the device should be in fastboot mode till power button is not pressed for at least 10 seconds.
But in this case it gets switched off.
I have not connected the USB to pc and nothing else.
Click to expand...
Click to collapse
I think that's expected behavior? If it doesn't recognize itself being connected to a device, it'll exit fastboot mode.
I think you need to connect it to the USB cable and into your PC for it to not restart/power off.
oreo27 said:
I think that's expected behavior? If it doesn't recognize itself being connected to a device, it'll exit fastboot mode.
I think you need to connect it to the USB cable and into your PC for it to not restart/power off.
Click to expand...
Click to collapse
No when I connect it to pc at that time also same happens.
Previously when booted in fastboot mode it will stay ther by the time juice is out.
MrUsamahh said:
No when I connect it to pc at that time also same happens.
Previously when booted in fastboot mode it will stay ther by the time juice is out.
Click to expand...
Click to collapse
Yup. I just tested it out. It looks like you're right.
oreo27 said:
Yup. I just tested it out. It looks like you're right.
Click to expand...
Click to collapse
So do you know how can I help myself out?
wait.. what exacly did you do when you booted into fastboot? did you type "adb devices" or "fastboot devices"? also, try rebooting into fastboot mode by typing "adb reboot bootloader" in cmd, with your phone plugged into your pc, and with the proper platform-tools installed. it shouldn't really go away from fastboot mode like that.
Mizuru said:
wait.. what exacly did you do when you booted into fastboot? did you type "adb devices" or "fastboot devices"? also, try rebooting into fastboot mode by typing "adb reboot bootloader" in cmd, with your phone plugged into your pc, and with the proper platform-tools installed. it shouldn't really go away from fastboot mode like that.
Click to expand...
Click to collapse
Hy man, I know basic of adb and I use cmd "adb devices"
My device is recognised when it is on.
I can also give various cmd like boot in recovery or fastboot mode or reboot and the device follow the instructions.
Please see the video that I've shared.
Once fastboot mode is on the device is automatically restarted in about 10 to 15 sec and within this time MiFlash tool or adb cmd prompt bot does not recognise my device.
I have tried to flash OTA via adb side load but it is showing error.
Help me with your input!
MrUsamahh said:
Hy man, I know basic of adb and I use cmd "adb devices"
My device is recognised when it is on.
I can also give various cmd like boot in recovery or fastboot mode or reboot and the device follow the instructions.
Please see the video that I've shared.
Once fastboot mode is on the device is automatically restarted in about 10 to 15 sec and within this time MiFlash tool or adb cmd prompt bot does not recognise my device.
I have tried to flash OTA via adb side load but it is showing error.
Help me with your input!
Click to expand...
Click to collapse
Your device doesn't get detected in your CMD prompt when it's in fastboot AND you type "fastboot devices"?
If it doesnt then you might have flashed something incorrectly.
Also, make sure to have your android drivers up to date in your pc. It's very, very likely that you don't have them installed on your PC, or they are outdated. See this: https://developer.android.com/studio/run/oem-usb.html
And this: https://developer.android.com/studio/releases/platform-tools.html
I have faced this issue. Yesterday i dirty flashed a custom rom. but i forgot how to dirty flash. i just simply flashed the rom and restarted the phone. it was mandatory to flash custom recovery and gapps after flashing a rom dirtily or normally. but i didn't. After the reboot completed, i remembered that i didn't flashed the twrp and gapps. So, i go back recovery mod, guessed i could flash twrp now. But i didn't see any custom recovery on my phone. But the phone boots, and i can use the phone. Still, i'm on that phone, while i'm typing this comment. i didn't lost my data cause i flashed dirtily. But the problem is, as i didn't flashed gapps or magisk (for root access), now i can't use google apps like, play store, and more. As i don't have root access on my phone so, i can't run flasify, to flash custom recovery. neither i can run other apps that need root. As i didn't flash custom recovery, now i can't flash gapps, magisk and whatever that needs a custom recovery.
I told some rom porter about the matter. They told me to flash stock rom. So, i was trying to flash stock rom. but flashing stock rom requires a fastboot mode. But my fastboot logo doesn't appear and it's blank. I told this to a rom porter. But he said, He doesn't know about that and he can't help.