Related
I just rooted my phone last night. I tried to flash cynanogen 10 and forgot to back up the the stock rom. I haven't done this since my last phone. But I got stuck at the cynanogen bootloader screen. I tried to get back to recovery mode but it won"t go. Can someone please help me and give very detailed instructions to get my phone unbricked pleeeeease? I don"t want to to buy another phone. Thank you.
How long did u wait at boot logo screen first boot can take a while and did u flash boot. Img? Are u t mob?
Sent from a man, using a mobile phone
1. Wipe
2. Flash
3. Wipe cache
4. Fastboot boot.IMG
5. Boot
6. Reboot
7. Flash gapps
8. Wipe cache
9. Enjoy the speed
Note this method will only work for hboot under 1.13
k1llacanon said:
How long did u wait at boot logo screen first boot can take a while and did u flash boot. Img? Are u t mob?
Sent from a man, using a mobile phone
Click to expand...
Click to collapse
All I know is that I downloaded the ROM from here, used CWM to flash it on, phone said update installed and rebooted the phone. I waited for an hour and it still did nothing past the bootload screen. Also, yes I'm t-mobile.
Fredfly said:
1. Wipe
2. Flash
3. Wipe cache
4. Fastboot boot.IMG
5. Boot
6. Reboot
7. Flash gapps
8. Wipe cache
9. Enjoy the speed
Note this method will only work for hboot under 1.13
Click to expand...
Click to collapse
If I can't get into recovery, how do I do this, or what can I use to do this?
Fredfly said:
1. Wipe
2. Flash
3. Wipe cache
4. Fastboot boot.IMG
5. Boot
6. Reboot
7. Flash gapps
8. Wipe cache
9. Enjoy the speed
Note this method will only work for hboot under 1.13
Click to expand...
Click to collapse
I have hboot 1.14
Can get ur phone into bootloader mode or fastboot...if yea...then u cn save ur phone...i faced the same problem some days back...and successfully recovered my phone and nw i am using energy rom...
Sent from my HTC VLE_U using xda app-developers app
Okay, let's try something.
Check your drivers on the PC, make sure you have ADB (from Android SDK or other sources).
Power on the phone, plug it in the PC.
Check if any drivers are installing/updating. Also check Device Manager to see if the device is seen in there.
If the PC sees the phone, open a cmd window and navigate to the directory where you have ADB (if using the android SDK, it should be in the tools folder of the installation directory).
In the cmd window, once in the directory containing the ADB, type "adb devices". You should see something about adb server stopping and starting, than, if everything alright, you should see the device as a number.
If you can see your phone, that means you're saved. Just run the command "adb reboot bootloader" and you're good to go.
If the phone cannot be seen by the PC, try and boot the phone holding vloume - pressed, try this with volume + too. Or simply google on how to boot the phone in bootloader mode.
Once in bootloader, again, you're saved. You can go ti fastboot usb mode and from there, do whatever you need to do.
Ruwin said:
Okay, let's try something.
Check your drivers on the PC, make sure you have ADB (from Android SDK or other sources).
Power on the phone, plug it in the PC.
Check if any drivers are installing/updating. Also check Device Manager to see if the device is seen in there.
If the PC sees the phone, open a cmd window and navigate to the directory where you have ADB (if using the android SDK, it should be in the tools folder of the installation directory).
In the cmd window, once in the directory containing the ADB, type "adb devices". You should see something about adb server stopping and starting, than, if everything alright, you should see the device as a number.
If you can see your phone, that means you're saved. Just run the command "adb reboot bootloader" and you're good to go.
If the phone cannot be seen by the PC, try and boot the phone holding vloume - pressed, try this with volume + too. Or simply google on how to boot the phone in bootloader mode.
Once in bootloader, again, you're saved. You can go ti fastboot usb mode and from there, do whatever you need to do.
Click to expand...
Click to collapse
Ok, I downloaded the sdk and my computer recognizes the phone, and I can get into recovery mode, I did a factory reset but it did nothing.
Ruwin said:
Okay, let's try something.
Check your drivers on the PC, make sure you have ADB (from Android SDK or other sources).
Power on the phone, plug it in the PC.
Check if any drivers are installing/updating. Also check Device Manager to see if the device is seen in there.
If the PC sees the phone, open a cmd window and navigate to the directory where you have ADB (if using the android SDK, it should be in the tools folder of the installation directory).
In the cmd window, once in the directory containing the ADB, type "adb devices". You should see something about adb server stopping and starting, than, if everything alright, you should see the device as a number.
If you can see your phone, that means you're saved. Just run the command "adb reboot bootloader" and you're good to go.
If the phone cannot be seen by the PC, try and boot the phone holding vloume - pressed, try this with volume + too. Or simply google on how to boot the phone in bootloader mode.
Once in bootloader, again, you're saved. You can go ti fastboot usb mode and from there, do whatever you need to do.
Click to expand...
Click to collapse
It keeps telling me device not ready
marcus8141981 said:
I just rooted my phone last night. I tried to flash cynanogen 10 and forgot to back up the the stock rom. I haven't done this since my last phone. But I got stuck at the cynanogen bootloader screen. I tried to get back to recovery mode but it won"t go. Can someone please help me and give very detailed instructions to get my phone unbricked pleeeeease? I don"t want to to buy another phone. Thank you.
Click to expand...
Click to collapse
I git it fixed. I thank everyone for their help.
marcus8141981 said:
It keeps telling me device not ready
Click to expand...
Click to collapse
Can you give me more details? Where do you see that message and when exactly? Maybe an ADB logcat?
If you can get into fastboot usb, you can easily google for flashing solutions using fastboot.
always good to say how you fixed it for others who may have similar issue--
Ruwin said:
Okay, let's try something.
Check your drivers on the PC, make sure you have ADB (from Android SDK or other sources).
Power on the phone, plug it in the PC.
Check if any drivers are installing/updating. Also check Device Manager to see if the device is seen in there.
If the PC sees the phone, open a cmd window and navigate to the directory where you have ADB (if using the android SDK, it should be in the tools folder of the installation directory).
In the cmd window, once in the directory containing the ADB, type "adb devices". You should see something about adb server stopping and starting, than, if everything alright, you should see the device as a number.
If you can see your phone, that means you're saved. Just run the command "adb reboot bootloader" and you're good to go.
If the phone cannot be seen by the PC, try and boot the phone holding vloume - pressed, try this with volume + too. Or simply google on how to boot the phone in bootloader mode.
Once in bootloader, again, you're saved. You can go ti fastboot usb mode and from there, do whatever you need to do.
Click to expand...
Click to collapse
I do that and my phone just keeps flickering and goes back in to cwm recovery. Please any ideas?
I want to root my tablet so I flashed TWRP 2.6.0.0 using fastboot everything works fine.
But now I want to install the zip to root the tablet, problem is TWRP cannot mount any storage, internal sdcard external sdcard nothing at all is alway says E:Can't mount 'xxx' on anything I tap.
I tried CWM, and 2.5.0.0 and nothing seems to work.
I can boot fine in the stock OS, everything works fine but that
My bootloader is 10.6.1.27.1-20130711
Can anyone help me?
Ok now it is bad, I tried to factory reset using the bootloader (power + volume down)
It booted in the buged TWRP and now it keeps booting in TWRP and I cannot even reach the bootloader
Try using adb commands to boot into bootloader.
ADB reboot-bootloader is the command that I think you must use. Of course, use adb devices to see if your tab is listed.
______________________________
HTC Evo 4G LTE
aarsyl said:
Try using adb commands to boot into bootloader.
ADB reboot-bootloader is the command that I think you must use. Of course, use adb devices to see if your tab is listed.
______________________________
HTC Evo 4G LTE
Click to expand...
Click to collapse
I cannot get this to work on Windows 8, I have Asus Transformer ADB interface lister in device manager but I cannot see my device with the adb devices command.
Also, in TWRP when I try adb sideload it says failed.
win 8 is the worst OS you want to use when it comes to fastboot/adb (even with secpol.msc full admin access)
get your hands on a win7 / vista /xp
oh and TWRP2.6 is kinda bugged - flash 2.5 or lower
check this http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12 but skip the steps you dont need (system, data userdata etc.)
cheers & gl
-Buster
Buster99 said:
win 8 is the worst OS you want to use when it comes to fastboot/adb (even with secpol.msc full admin access)
get your hands on a win7 / vista /xp
oh and TWRP2.6 is kinda bugged - flash 2.5 or lower
check this http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12 but skip the steps you dont need (system, data userdata etc.)
cheers & gl
-Buster
Click to expand...
Click to collapse
I'm now on my laptop with Win7,
Ok so I tried to reset my device with a needle, but I cannot get it to the bootloader.
Still stuck in TWRP, I tried to go with ADB, I installer google usb driver from Android SDK, I cannot get it to be recognized by ADB, in the device manager I only see Transformer with a yellow "!", I tried with the Asus usb driver, nothing either.
Is there something else I can do to get this recognized with ADB? (fastboot doesn't work either)
I tried unpluging all, uninstalling all and reinstalling like 3 times.
Thanks for your help
Matiosse said:
I'm now on my laptop with Win7,
Ok so I tried to reset my device with a needle, but I cannot get it to the bootloader.
Still stuck in TWRP, I tried to go with ADB, I installer google usb driver from Android SDK, I cannot get it to be recognized by ADB, in the device manager I only see Transformer with a yellow "!", I tried with the Asus usb driver, nothing either.
Is there something else I can do to get this recognized with ADB? (fastboot doesn't work either)
I tried unpluging all, uninstalling all and reinstalling like 3 times.
Thanks for your help
Click to expand...
Click to collapse
fastboot should work. hold Vol-down and reset the device and keep vol-down pressed. it should go to fastboot. when you're in fastboot connect it to your laptop and see if the OS recognized your device - if not you have a driver issue. resolve that by installing the asus driver or the newest google generic drivers.
when you can see your device on dosprompt/powershel with fastboot devices then continue with getting recovery to work.
btw- stuck in twrp means? booting twrp (teamwin screen) but not responding?
good luck
-Buster
The problem is I cannot even get into fastboot, it keeps booting into TWRP, I tried to reset the tab with a needle, but I cannot reach fastboot in any ways
Matiosse said:
The problem is I cannot even get into fastboot, it keeps booting into TWRP, I tried to reset the tab with a needle, but I cannot reach fastboot in any ways
Click to expand...
Click to collapse
but you are still able to boot into android?
I was until I tried a factory reset, it wasn't working in Android so I did it in the fastboot menu.
Matiosse said:
I was until I tried a factory reset, it wasn't working in Android so I did it in the fastboot menu.
Click to expand...
Click to collapse
can you boot into twrp? and i mean just boot into it? so that you see install, backup, restore etc. buttons?
if yes - twrp has an adb mode
connect your tab in twrp to your pc (check that you can see it - adb devices) if yes type: adb reboot bootloader
and you should boot into that. test it with fastboot devices.
most important thing is that you get into fastboot or a working recovery to flash or prepare to flash a (custom) rom back onto your device.
Buster
I can get in TWRP on 2.5.0.0
But when I try ADB sideload it fails
The message is ADB sideload complete - Failed in red + lots of errors like Unable to mount '/data' '/cache' /system' pratically everything (note that I had the same problem of mounting when I was able to boot into Android)
Matiosse said:
I can get in TWRP on 2.5.0.0
But when I try ADB sideload it fails
The message is ADB sideload complete - Failed in red + lots of errors like Unable to mount '/data' '/cache' /system' pratically everything (note that I had the same problem of mounting when I was able to boot into Android)
Click to expand...
Click to collapse
learn to crawl before you run :angel:
Well I rooted 4 different android device and not a single one of them wasn't able to mount anything in recovery mod. I knew exactly what I was doing until I got in the recovery mod who won't even recognize my internal storage meanwhile I was able to perfectly boot in Android
Matiosse said:
Well I rooted 4 different android device and not a single one of them wasn't able to mount anything in recovery mod. I knew exactly what I was doing until I got in the recovery mod who won't even recognize my internal storage meanwhile I was able to perfectly boot in Android
Click to expand...
Click to collapse
dude - you can't boot into android anymore, you can't boot into fastboot to your own accord - yet you try to sideload stuff in twrp for what ever reason.
i gave you more hints and tips in my previous posts and link to get it to work yet it eems you did none.
so don't get me wrong - but what excactly is your goal here?
My goal is to get it working again...
I don't know if you've been reading my post but I did try everything you told me without sucess.
None of the tips I tried got me adb or fastboot working the sideload mode of TWRP doesn't work.
Matiosse said:
My goal is to get it working again...
I don't know if you've been reading my post but I did try everything you told me without sucess.
None of the tips I tried got me adb or fastboot working the sideload mode of TWRP doesn't work.
Click to expand...
Click to collapse
yes i read your posts - but im still unclear what you are trying to accomplish with sideload?
ok from the start:
when in twrp - connect your tab to your laptop - is windows working with it (drivers ok?) "adb devices" shows the device? if yes - adb reboot-bootloader (or fastboot reboot bootloader, not quite sure atm since i'm at work without micro usb cable) when issued the command is the tab rebooting? - and if yes, is it rebooting into twrp or fastboot? what screen is shown after that?
-B
ok from the start:
when in twrp - connect your tab to your laptop - is windows working with it (drivers ok?)
Windows isn't working with it, I tried Google usb driver, asus usb driver, universal adb driver, none of them work, this is where i'm stuck
"adb devices" shows the device? if yes - adb reboot-bootloader (or fastboot reboot bootloader, not quite sure atm since i'm at work without micro usb cable) when issued the command is the tab rebooting? - and if yes, is it rebooting into twrp or fastboot? what screen is shown after that?
Matiosse said:
ok from the start:
when in twrp - connect your tab to your laptop - is windows working with it (drivers ok?)
Windows isn't working with it, I tried Google usb driver, asus usb driver, universal adb driver, none of them work, this is where i'm stuck
"adb devices" shows the device? if yes - adb reboot-bootloader (or fastboot reboot bootloader, not quite sure atm since i'm at work without micro usb cable) when issued the command is the tab rebooting? - and if yes, is it rebooting into twrp or fastboot? what screen is shown after that?
Click to expand...
Click to collapse
when its connected - is device manager at least showing it as faulty or not at all? (yellow triangle exclamation mark thingy, i just installed asus on my VM) -> see attached file
UPDATE: I succeeded to go in fastboot mode
I couldn't get my tab to be recognized by windows so I installer my Nexus 4 using the toolkit, when it was succesfully installed I could manually install my tab since the "android devices" option appeared in the list when you want to manually install a driver in the devices manager. So I could choose Asus ADB interface.
Now I can boot into Android, but it will go into TWRP as soon as I restart my tablet.
Now I will try the link you sent me to get TWRP recognize my storage so I can flash a new rom, I will let you know if something go wrong.
Thanks for helping
hi guys,
i my shield is stuck on the nvidia logo when booting normally, if it brings up the bootloader, it shows unlocked but hitting continue caused it to freeze on the screen, recovery freezes on nvidia logo and fastboot protocol just brings it back to this screen. i orginally installed twrp and it confirmed successful flash of new os .... on reboot it bricked to its now state, i cant get into twrp or get my pc to see it to install a new copy
anyone got any ideas
thanks
@Fairmax don't click continue, it freezes because there is nothing to continue to, as long as you can enter bootloader your device isn't fully bricked. So, to fix your problem you will have to download official ROM from nvidia's site (https://developer.nvidia.com/shield-open-source find your model and click recovery images).
When you download latest ROM unzip it and follow the textual guide, but, there will be one file missing (i can't remember which one, user data maybe or something like that), don't worry and just continue with the next step. After you flash just reboot to system by holding power button. Good luck !
i cant seem to get it to be recognised by windows all i get is this-- Windows has stopped this device because it has reported problems. (Code 43) A request for the USB device descriptor failed.--
trying to install nvidia usb driver via have disk bring up an error that the file is not usable with x64 system
ok after many driver reinstall iv got device manager to say android adb interface but still not showing on on device list in cmd
Fairmax said:
ok after many driver reinstall iv got device manager to say android adb interface but still not showing on on device list in cmd
Click to expand...
Click to collapse
Which command did you type in?
fpozar said:
Which command did you type in?
Click to expand...
Click to collapse
adb devices shows no devices
i tried the 3 different option in the driver install which was android adb, bootloader, and something else and nothing shows in devices. i tried it on my laptop and a different cable and cant get adb to list the device :crying:
Fairmax said:
adb devices shows no devices
i tried the 3 different option in the driver install which was android adb, bootloader, and something else and nothing shows in devices. i tried it on my laptop and a different cable and cant get adb to list the device :crying:
Click to expand...
Click to collapse
Well of course adb devices shows no devices because you are not actually in adb mode, you are in the bootloader mode. Just download minimal fastboot and adb, install it and extract recovery image into the folder where you installed minimal adb and fastboot (you don't need any other drivers).After you did this and your device is in bootloader and connected, click on the path in your fastboot & adb folder and delete everything and type cmd. No need to do adb devices, just proceed with fastboot flash ...
fpozar said:
Well of course adb devices shows no devices because you are not actually in adb mode, you are in the bootloader mode. Just download minimal fastboot and adb, install it and extract recovery image into the folder where you installed minimal adb and fastboot (you don't need any other drivers).After you did this and your device is in bootloader and connected, click on the path in your fastboot & adb folder and delete everything and type cmd. No need to do adb devices, just proceed with fastboot flash ...
Click to expand...
Click to collapse
ah now that makes sence....silly me i dont do this very often . so fastboot saw device and iv uploaded all parts of the recovery image and rebooted but it is still stuck on the nvidia logo, that was the original file so now il try 5.2.0 and see if that works
Fairmax said:
ah now that makes sence....silly me i dont do this very often . so fastboot saw device and iv uploaded all parts of the recovery image and rebooted but it is still stuck on the nvidia logo, that was the original file so now il try 5.2.0 and see if that works
Click to expand...
Click to collapse
You can also try flashing twrp and then lineageos or something from twrp.
fpozar said:
You can also try flashing twrp and then lineageos or something from twrp.
Click to expand...
Click to collapse
good news after a few hours of trying (usb dropped connection a few times then battery died) it finally works again .....been over 2 years since iv had this shield running after nvidia did the recall , now goto put a different rom on there so it dosnt update and kill itself
Hello I had a similar issue with my k1 tablet and ended up flashing factory images via adb fastboot and all flashed fine. Now my tablet is stuck on the boot screen with the green and white nvidia logo. How long does it take to boot please?
I have same issue too. I can load TWRP and flash the other partitions but TWRP shows un-mountable partitions and even a full stock ROM flash will not allow it to boot. I have a similar issue with a recall tablet. what did you do to fix it?
My phone. - Galaxy A51, One UI Version is 4.1, Android version is 12, Product Name – SM-A515F.
Stock ROM up to date.
I can boot into download mode, +/- volume, connect to pc. Works just fine.
But + volume & power boots into safe mode; - volume & power boots into safe mode; +/- volume & power boots into safe mode; +/- volume only boots into safe mode. I have ran out of button sequences to try.
What is wrong with my phone, is it impossoble to boot into recovery mode on my model of phone. This is why I cannot install TWRP as when I install via Odin, it will not boot into recovery post installation.
I am stumped.
Hello!
What is about phone: is it bootlooping or is it in downloading mode?
Other question: from what source did you download the twrp.tar file?
You should be able to force a reboot to recovery using ADB. Enable developer options, then enable USB Debugging. Download the SDK Platform Tools and open a command line in the platform tools directory (where you find the fastboot, adb, etc programs)
First, type adb devices. ADB will then start the ADB daemon.
Next, connect your device via USB cable while unlocked. You should get a prompt on the device screen requesting USB debugging authorization. Go ahead and grant it.
Then, type adb devices again. If you authorized USB debugging correctly, you should see your device listed.
Now, type adb reboot recovery. Your device should reboot into TWRP.
V0latyle said:
You should be able to force a reboot to recovery using ADB. Enable developer options, then enable USB Debugging. Download the SDK Platform Tools and open a command line in the platform tools directory (where you find the fastboot, adb, etc programs)
First, type adb devices. ADB will then start the ADB daemon.
Next, connect your device via USB cable while unlocked. You should get a prompt on the device screen requesting USB debugging authorization. Go ahead and grant it.
Then, type adb devices again. If you authorized USB debugging correctly, you should see your device listed.
Now, type adb reboot recovery. Your device should reboot into TWRP.
Click to expand...
Click to collapse
Guy, to complete the TWRP installation, it is needed to flash Disable_Dm-Verity_ForceEncrypt from TWRP, otherwise the device will not boot properly
vmirrimv said:
Other question: from what source did you download the twrp.tar file?
Click to expand...
Click to collapse
It's in Stock now. But it was stuck in a bootloop, but could boot into download mode. These are the recovery's which all installed but I could not boot into. I cannot boot into recovery now I am in Stock. It's as if there is no recovery option for my A51.
Twrp+vbmeta_A11.tar,
TWRP-11-3.6.0-a51-20220210-1636.tar,
TWRP-11-3.6.1-a51-20220228-2050.tar,
TWRP-11-3.6.1-a51-20220321-1406-hotfix.tar,
TWRP-11-3.6.2-a51-20220602-0515.tar,
twrp-a51-3.5.0_10-1_ianmacd.tar
vmirrimv said:
Guy, to complete the TWRP installation, it is needed to flash Disable_Dm-Verity_ForceEncrypt from TWRP, otherwise the device will not boot properly
Click to expand...
Click to collapse
I was stuck in a bootloop and could not boot into TWRP..
Unless there is a way to flash Disable_Dm-Verity_ForceEncrypt in downlad mode using Odin?
V0latyle said:
You should be able to force a reboot to recovery using ADB. Enable developer options, then enable USB Debugging. Download the SDK Platform Tools and open a command line in the platform tools directory (where you find the fastboot, adb, etc programs)
First, type adb devices. ADB will then start the ADB daemon.
Next, connect your device via USB cable while unlocked. You should get a prompt on the device screen requesting USB debugging authorization. Go ahead and grant it.
Then, type adb devices again. If you authorized USB debugging correctly, you should see your device listed.
Now, type adb reboot recovery. Your device should reboot into TWRP.
Click to expand...
Click to collapse
Hi I am back in stock now, so no TWRP installed. Would this method boot you into Stock recovery?
Do I need to be in download mode or just normal mode when connecting the phone to the pc?
Hello, can you say what version of Android your phone on?
If it is on 12th, then I would say, that the problem is, that this version may not fully supported for TWRP working
Because as I tried, there was a fail in the procces.
Sorry, i did not see that you have already written about it
Yep, think I will have to download Android 10 stock rom; and hopefully be able to install 10 via Odin from 12 back to 10.
Sign1 said:
Hi I am back in stock now, so no TWRP installed. Would this method boot you into Stock recovery?
Do I need to be in download mode or just normal mode when connecting the phone to the pc?
Click to expand...
Click to collapse
ADB commands must be issued in system. The alternative would be from fastboot but it doesn't seem you can access that.
Try flashing TWRP again, but immediately hold Volume Up during boot to force booting into TWRP. Newer Samsung firmware does seem to have some sort of security measure that will replace a custom recovery, so you'll have to flash the Multidisabler to disable stock recovery auto-restoration.
Sign1 said:
Yep, think I will have to download Android 10 stock rom; and hopefully be able to install 10 via Odin from 12 back to 10.
Click to expand...
Click to collapse
I do not want to mislead you, but you will not be able to roll back from Android 12 to Android 10, because the current binary version of your phone (5) cannot be changed to lower one (4).
Maximum as you can do, is to downgrade to the 11th version and there, as I think and tried, the Twrp+vbmeta_A11.tar recovery file will be flashed sucessfuly and you will be able to enter TWRP without issues like bootloop.
Other problems are, as I think, that you may forgot to enable USB Debugging on your phone and authorize it with your computer, you may forgot to set the default USB Configuration as data transfer (MTP), or even you may not unlocked the bootloader.
I think they are the reasons because of which you could not enter TWRP, because, as I have tried to flash One UI 4.1 Android 12 according to this thread recently: https://forum.xda-developers.com/t/...ecovery-project-v3-6-2-android-11-12.4400869/
everything has been sucessful, both flashing and entering and following rebooting to Stock system.
Or you may even not removed the check mark from the parameter "Auto Reboot" in Odin
vmirrimv said:
I do not want to mislead you, but you will not be able to roll back from Android 12 to Android 10, because the current binary version of your phone (5) cannot be changed to lower one (4).
Maximum as you can do, is to downgrade to the 11th version and there, as I think and tried, the Twrp+vbmeta_A11.tar recovery file will be flashed sucessfuly and you will be able to enter TWRP without issues like bootloop.
Click to expand...
Click to collapse
Cheers for that, just downloaded Android 10, took me twelve hours to download, so its no use to me. I need to download Android 11.
vmirrimv said:
Or you may even not removed the check mark from the parameter "Auto Reboot" in Odin
Click to expand...
Click to collapse
Yep did that.
Hi guys, I Have Pixel 3 with Custom twrp recovery one day I accidentally wiped my internal storage and data everything After I cannot get into boot my phone , then I tried with USB it shows 0 mb ,And I mess up with twrp settings everywhere after I changed boot slot b to a and reboot BOOM everything stuck a slot have nothing after I noticed I cannot get into recovery now, its stuck in to fast boot mode but my PC cannot detect my device even though driver installed now what I do please .
Musthafa_3679 said:
Hi guys, I Have Pixel 3 with Custom twrp recovery one day I accidentally wiped my internal storage and data everything After I cannot get into boot my phone , then I tried with USB it shows 0 mb ,And I mess up with twrp settings everywhere after I changed boot slot b to a and reboot BOOM everything stuck a slot have nothing after I noticed I cannot get into recovery now, its stuck in to fast boot mode but my PC cannot detect my device even though driver installed now what I do please .
Click to expand...
Click to collapse
can you get into fastboot? if so, you will probably have to start over. choose the right carrier. if you don't know it or aren't 100% sure, select other. You could also try this one.
DragonFire1024 said:
can you get into fastboot? if so, you will probably have to start over. choose the right carrier. if you don't know it or aren't 100% sure, select other. You could also try this one.
Click to expand...
Click to collapse
I tried google flash tool but my device not detected ,adb not response and fastboot . but it always boot in fastboot but why my PC isn't get device and I tried to go edl but I can't find the way to boot edl please help
Musthafa_3679 said:
I tried google flash tool but my device not detected ,adb not response and fastboot . but it always boot in fastboot but why my PC isn't get device and I tried to go edl but I can't find the way to boot edl please help
Click to expand...
Click to collapse
The standard things to try when the device is not recognized are:
1. Update drivers
2. Make sure you are using the latest version of platform tools from https://developer.android.com/studio/releases/platform-tools
3. Try different USB ports and cables, preferably USB 2.0. USB 3.0 may not work.
4. Try a different PC.
Are you using "fastboot devices" to detect the device? "adb devices" does not work in fastboot mode.
dcarvil said:
The standard things to try when the device is not recognized are:
1. Update drivers
2. Make sure you are using the latest version of platform tools from https://developer.android.com/studio/releases/platform-tools
3. Try different USB ports and cables, preferably USB 2.0. USB 3.0 may not work.
4. Try a different PC.
Are you using "fastboot devices" to detect the device? "adb devices" does not work in fastboot mode.
Click to expand...
Click to collapse
Yes I tried fastboot mode , I installed latest platform tools my mobile don't have any os inside I wiped everything how it will find through platform tools?
And its always fast boot mode whenever I try to boot recovery or normal boot it says error to preloade images , some times no valid slot to boot if I can detect by PC I may be I can change boot slot