HELP : ADP mode only detected in recovery not on fastboot - Nexus 4 Q&A, Help & Troubleshooting

I softbricked my phone. I was in TWRP and wiped everything including the rom that was on it. So i have tried flashing the stock back on using the various toolkits out there. I have also tried to push a rom file onto the sdcard. However it seems my computer is only detecting the phone in adp mode when its in recovery or sometimes when its stuck on the google logo screen. as soon as it goes into fastboot mode no more detection. Also it seems the bootloader is locked again. hwoever i cant unlock it as i cant get it into the adb mode on thr fastloader screen. someone please help. ?

Related

[Q] Ruined Fastboot mode, but regular boot works?

Okay, so not sure what I did here.
I have an LG G2 ATT version with 4.2.2 installed.
I was trying to install CM, which I already have on my Nexus 7 and love. But the LG G2 doesn't have a nice one-click install app like the Nexus 7 does.
So, I managed to root it, and got SuperUser installed and Clockworkrecoverymod.
At one point I also had TWRP installed, and I think that is where I went wrong. I went to flash a new fastboot / recovery mode and think I selected the wrong one (LG G2 International).
Ever since then, attempting to reboot into recovery using the hardware method (volume down + power) doesn't work. If i force it into fastboot mode using Clockworkrecoverymod or ioroot, I get a strange message.
All the phone shows is white text on a black background:
[830] Fastboot mode started
[940] -- rest --
[950] fastboot; processing commands
then, if i unplug the USB port, I get a few messages. If I replug it in, I get the above message again, with different time stamps.
If I boot normally, it pulls up the normal stock OS, but any attempt to boot into fast mode gets me this message. I can also boot into download mode, but it hangs at 0 %. I tried Flashing a new Recovery using clockworkmod, and it says it worked, but booting into recovery just results in ending up in the same Fastboot mode deadend.
I see the same message if I try to factory reset the phone through the normal software method in options.
So, it is great that I didn't completely brick my phone when I idiotically installed for the wrong mode, but without being able to get into fastboot mode, what are my options for getting back on there and back to stock so I can try again?
And yes, I tried to make a backup on my device, but when I went to go back to it, clockworkmod said it isn't there. Not sure how I messed that up, but anyone have any suggestions on what I can do going forward?
As I understand; If you're trying to boot it to recovery mode, it goes to fastboot mode, right?
If I understood right; you need just flash recovery to your device.
G2 has a different boot process from other devices. If bootloader failed to boot the thing you want to boot, it goes to fastboot mode. That's why it goes fastboot mode when you try to boot it to recovery.
Ah yeah, i just couldn't figure out how to get it out of Fastmode. I was a little confused about the difference between fastmode and recovery.
I seemed to have fixed the problem by AutoRec, for whatever that is worth. Now it boots into TWRP's recovery mode. Shouldn't be hard to get cyanogenmod now.
TheAmericannomad said:
Okay, so not sure what I did here.
I have an LG G2 ATT version with 4.2.2 installed.
I was trying to install CM, which I already have on my Nexus 7 and love. But the LG G2 doesn't have a nice one-click install app like the Nexus 7 does.
So, I managed to root it, and got SuperUser installed and Clockworkrecoverymod.
At one point I also had TWRP installed, and I think that is where I went wrong. I went to flash a new fastboot / recovery mode and think I selected the wrong one (LG G2 International).
Ever since then, attempting to reboot into recovery using the hardware method (volume down + power) doesn't work. If i force it into fastboot mode using Clockworkrecoverymod or ioroot, I get a strange message.
All the phone shows is white text on a black background:
[830] Fastboot mode started
[940] -- rest --
[950] fastboot; processing commands
then, if i unplug the USB port, I get a few messages. If I replug it in, I get the above message again, with different time stamps.
If I boot normally, it pulls up the normal stock OS, but any attempt to boot into fast mode gets me this message. I can also boot into download mode, but it hangs at 0 %. I tried Flashing a new Recovery using clockworkmod, and it says it worked, but booting into recovery just results in ending up in the same Fastboot mode deadend.
I see the same message if I try to factory reset the phone through the normal software method in options.
So, it is great that I didn't completely brick my phone when I idiotically installed for the wrong mode, but without being able to get into fastboot mode, what are my options for getting back on there and back to stock so I can try again?
And yes, I tried to make a backup on my device, but when I went to go back to it, clockworkmod said it isn't there. Not sure how I messed that up, but anyone have any suggestions on what I can do going forward?
Click to expand...
Click to collapse
if you want go back to stock and you can't enter in download mode you can try follow this but USE THE CORRECT FILES FOR YOUR DEVICE!!!!!!!!
http://forum.xda-developers.com/showthread.php?t=2477595
to extract laf.img from kdz.
http://forum.xda-developers.com/showthread.php?t=2600575
Give a thank to the OP of the threat.

Samsung galaxy grand neo plus - i9060i

greetings people,
a few days ago my friend brought me a phone for me to flash a custom rom onto it. I can't REGRET anything more then accepting this phone.
I rooted the phone on stock android 4.4.4 with Kingroot and after that, **** went down real bad.
I realised I couldn't acces recovery NOR download modus anymore, i try'd to boot into download/recovery with the hardware button way, but I also try'd to boot with adb reboot download / recovery
neither of those options worked, the phone either normally booted up or it kept trying to reboot with a black screen.
after I rooted it the boot image u get like " Samsung XXX "" were also gone.
after ALOT of searching and stuff and attempting things ive found a really old thread that stated to use fastboot reboot bootloader. I were really amazed that that worked but instead of booting up to the regular download modus it booted into fastboot, I read somewhere someone had the similair issue like me and they told him his boot img were corrupted. so ive headed to sammobile and downloaded the stock firmware for the device, I extracted the packages since I couldn't use odin because I am/was not able to acces download modus, while in fastboot i flashed the single boot.img with the command "Fastboot flash boot boot.img" it succeeded but after it succeeded I tried to boot it up but it fails booting to OS,recovery and download. it keeps attemping to reboot, I am CLUELESS at this point. I am able to try some things when I can enter that fastboot mode I had before but I can't acces the phone with ADB since it just keeps rebooting and stays inresponsible
I am planning to buy a USB JIGG, i use to have one but I can't find it anywhere.
any idea's/information would be soo helpful..
thanx in advance
Grand Neo Plus Root
a
omametsnor said:
greetings people,
a few days ago my friend brought me a phone for me to flash a custom rom onto it. I can't REGRET anything more then accepting this phone.
I rooted the phone on stock android 4.4.4 with Kingroot and after that, **** went down real bad.
I realised I couldn't acces recovery NOR download modus anymore, i try'd to boot into download/recovery with the hardware button way, but I also try'd to boot with adb reboot download / recovery
neither of those options worked, the phone either normally booted up or it kept trying to reboot with a black screen.
after I rooted it the boot image u get like " Samsung XXX "" were also gone.
after ALOT of searching and stuff and attempting things ive found a really old thread that stated to use fastboot reboot bootloader. I were really amazed that that worked but instead of booting up to the regular download modus it booted into fastboot, I read somewhere someone had the similair issue like me and they told him his boot img were corrupted. so ive headed to sammobile and downloaded the stock firmware for the device, I extracted the packages since I couldn't use odin because I am/was not able to acces download modus, while in fastboot i flashed the single boot.img with the command "Fastboot flash boot boot.img" it succeeded but after it succeeded I tried to boot it up but it fails booting to OS,recovery and download. it keeps attemping to reboot, I am CLUELESS at this point. I am able to try some things when I can enter that fastboot mode I had before but I can't acces the phone with ADB since it just keeps rebooting and stays inresponsible
I am planning to buy a USB JIGG, i use to have one but I can't find it anywhere.
any idea's/information would be soo helpful..
thanx in advance
Click to expand...
Click to collapse
Hi There, I just came across your thread, because I'm in the same position you are, fortunately though, I've managed to root this phone without any problems, however it seem though that there is no custom ROM available for this device, at least nothing past KK, and that one I found didn't seem so stable, I tried to flash it and came back with an error!! So my friend won't be able to bring his phone out of the Dark Ages!! at least it's Rooted! and now he may be able to use some apps that do require root, It's the best I can do at this point. I used the link below to root sucessfully:
https://www.google.com/url?q=http://forum.xda-developers.com/android/general/root-galaxy-grand-neo-plus-gt-i9060i-ds-t3070302&sa=U&ved=0ahUKEwjds_Tn-sDOAhVG1B4KHe8xDC0QFggEMAA&client=internal-uds-cse&usg=AFQjCNFDnwTNwiFG6H8TI_hKXAeeWEOlRw
I realize it's kinda late but luck to you my friend:fingers-crossed:
By the way, This one is the Dual Sim Version, don't know if that will make a difference?!

a6000 shut down during MIUI flash, won't boot into recovery

Hey guys I was trying to flash MIUI 8 on my a6000 lenovo. Bear with me because I'm new to this so I might have screwed up.
Rooted and installed TWRP perfectly. Phone was running kitkat.
I then, through TWRP tried to flash MIUI 8 from http://forum.xda-developers.com/lenovo-a6000/development/rom-miui-7-lenovo-a6000-a6000-t3355692
After first swiping right to install the zip, i got an "error executing binary in zip" error. Wiped dalvik,etc. again and tried again and then I got a MD5 file not found "warning". It was not in red letters and after that message there was no progress bar or anything and the phone just stopped responding. I assumed it wasn't working and few minutes later took the battery out. After trying to boot again it would give me the "mi.com" boot screen (not the default lenovo I used to get) and won't boot into neither recovery nor normal mode. (for recovery boot I'm trying holding both volume buttons and the power button at the same time. perhaps that is different now?)
I'm guessing the flashing was going on and i interrupted it. How can I fix this?
Update: It boots into MIUI now however pretty much nothing works as expected. It wont even go into settings. Recovery still seems botched and i cant boot into it.
TLDR: Recovery broken cant boot into it. Can boot into MIUI with very limited capabilities. Cannot select USB debugging and "adb devices" won't find the phone. What can I do?
Alright nevermind guys I managed to fix it. for anyone wondering or having the same issue, i tried many things but what I think worked is this:
Turnt on my phone in fastboot mode (hold volume - and power button) , connected it to the computer and used command "fastboot flash recovery recovery.img" to flash the old TWRP i had on my computer. After that I managed to boot my phone in recovery mode and reflash the rom properly. The weird thing is, my phone could not be recognized by the computer and "adb devices" gave me nothing back so I thought using any fastboot command wouldn't work. Oddly, it did and it flashed TWRP back into my phone.

phone bricked while trying to go back to stock rom

hello,
as the title says, my phone bricked while trying to go back to stock rom. this is what i did: i had a well working meticulus custom rom + the meticulus twrp recovery on my phone. thing is i need the google apps and they are not supported on meticulus roms. so i tried to go back to rom, downloaded a stock rom and tried to flash it with dragging it onto my sdcard and installing it from there. so this is when it bricked, the huawei logo appears at the start but it stays and nothing will install.
i tried to reinstall the adb drivers, no success. i can only use the bootloader but i can only flash a recovery, after trying to boot into the recovery via fastboot boot recovery.img it won´t do a thing. also the recovery is stock recovery all of a sudden (erecovery). and there i only have the option to "download latest version and recovery" but that gives an error aswell.
i´ve tried to reinstall drivers, no luck. when i do a fastboot devices it shows my device but when i do adb devices it doesn´t show up anything. so the usb driver is somewhat corrupted. my computer detects the phone when in fastboot only.
i´ve tried to reinstall the drivers a hundred times, i can´t get the phone to work anymore.
i would really appreciate it if someone helps me out.

Question Help with Nothing phone stuck in Fastboot mode (A13 Beta 1.5.1)

Hello,
I was trying to downgrade my phone from the beta to Android 12 and it's now stuck in Fastboot mode. Won't let me enter recovery. Tries to boot but just stays on the nothing logo. My bootloader is unlocked. I'm assuming I need the same firmware I was running to reload onto the phone. Any other files needed?
Thank you so much! cheers
https://www.theupdatebox.com/how-to-downgrade-nothing-phone-1-from-android-13-to-android-12/
https://rootmygalaxy.net/how-to-roll-back-your-nothing-phone-1-from-android-13-to-android-12/
I can't enter recovery mode. Only fastboot.
Flash boot and vendor_boot and you'll be right back in recovery
If it's not booting try set active slot to either a or B and flash the images mentioned above
bariz143 said:
Flash boot and vendor_boot and you'll be right back in recovery
If it's not booting try set active slot to either a or B and flash the images mentioned above
Click to expand...
Click to collapse
I'm having a similar issue coming off a fastboot stuck device. I guess I managed to delete the recovery mode from slot B so I can't get into fastbootd to flash some of the lower level partitions to make my fingerprint sensor work.
The vendor_image is the recovery?
Did you guys find any solution? I am stuck with my phone stuck in the bootloader mode and I can't seem to do anything.
Here's what I did:
1) Unlocked bootloader while being on NOS 1.5.1 Beta. Successfuly did it.
2) Restarted my phone to bootloader mode and flashed dtbo, boot and vendor_boot from SuperiorOS 11th Feb build.
3) Proceeded to restart to recovery as mentioned in the instructions but instead of restarting to recovery, it restarted to bootloader.
4) Stuck in bootloader mode ever since!
Nothing seems to be working. I have tried literally everything but cannot get past the bootloader. Please help. I don't have any secondary device to use.
dizz232 said:
Hello,
I was trying to downgrade my phone from the beta to Android 12 and it's now stuck in Fastboot mode. Won't let me enter recovery. Tries to boot but just stays on the nothing logo. My bootloader is unlocked. I'm assuming I need the same firmware I was running to reload onto the phone. Any other files needed?
Thank you so much! cheers
Click to expand...
Click to collapse
solution available https://forum.xda-developers.com/t/unbrick-tool-edl-flash-read-repair-region-change-tool.4552471/

Categories

Resources