Database Info

[Q] Urgent! Stuck at bootloader but cant do anything

Hi u all!
First of all thank you for your time and sorry for my english, I speak spanish.
I have a nexus s i9023. I was using CyanogenMod 11 experimental 24042014.
I was having many problems and decided to downgrade to the stable version 10.1.2
It downloaded ok, installed all the updates, rebooted and then got stuck in the logo screen when booting.
The problem is that my nexus s has a broken the power button, it doesn't work.
As for right now the olny thing I can do is to enter the bootloader screen, but cant move throgh the options with the volume keys, it's like its stuck.
If I plug in the device when in the bootloader (fastboot mode) screen my PC doesn't recognice it, I search in the device manager but it doesn't appear.
If it helps when I plug in the battery the phone starts on in it's on.
Please, any help is appreciated.
Im really sad because I love my nexus.
Thank you!!!

Same here. Any help for us would be great. Thanks.

shd128 said:
Hi u all!
First of all thank you for your time and sorry for my english, I speak spanish.
I have a nexus s i9023. I was using CyanogenMod 11 experimental 24042014.
I was having many problems and decided to downgrade to the stable version 10.1.2
It downloaded ok, installed all the updates, rebooted and then got stuck in the logo screen when booting.
The problem is that my nexus s has a broken the power button, it doesn't work.
As for right now the olny thing I can do is to enter the bootloader screen, but cant move throgh the options with the volume keys, it's like its stuck.
If I plug in the device when in the bootloader (fastboot mode) screen my PC doesn't recognice it, I search in the device manager but it doesn't appear.
If it helps when I plug in the battery the phone starts on in it's on.
Please, any help is appreciated.
Im really sad because I love my nexus.
Thank you!!!
Click to expand...
Click to collapse
kijp15 said:
Same here. Any help for us would be great. Thanks.
Click to expand...
Click to collapse
Seems like a driver issue. Can you try installing the drivers in a different system?
If it goes well, then use install cwm touch recovery from fastboot. You can take backup and flash new ROMs after that.
Try Nexus Root Toolkit to install drivers if you don't have access to a different system.

smit.sanghavi said:
Seems like a driver issue. Can you try installing the drivers in a different system?
If it goes well, then use install cwm touch recovery from fastboot. You can take backup and flash new ROMs after that.
Try Nexus Root Toolkit to install drivers if you don't have access to a different system.
Click to expand...
Click to collapse
Don't I need to have android debugging enabled? If so, I don't think Nexus Root Toolkit will work. I flashed a ROM to my NS4g & I get boot loops. I flashed the wrong Gapps a few months ago.
I was hoping there would be a way to automatically turn android debugging on. I know it may sound dumb & also probably impossible.
Any other tips.
Tell me I'm screwed. Haha.

kijp15 said:
Don't I need to have android debugging enabled? If so, I don't think Nexus Root Toolkit will work. I flashed a ROM to my NS4g & I get boot loops. I flashed the wrong Gapps a few months ago.
I was hoping there would be a way to automatically turn android debugging on. I know it may sound dumb & also probably impossible.
Any other tips.
Tell me I'm screwed. Haha.
Click to expand...
Click to collapse
I disabled USB debugging. Rebooted to bootloader. Fired up 'fastboot devices' on cmd and could see my phone. This tells me that I do not need USB debugging on fastboot.
If you see an unknown device in Device Manager while in fastboot then use Universal Naked Driver to install the drivers. But since you don't, you'll need another PC to do this stuff. Once drivers are installed, you can do a 'fastboot reboot recovery' to get into recovery and fix the the problems. The first thing I advice is to flash a touch recovery. The rest is up to you.

Flash back the original soju firmware back onto your device by first using "nexus s root toolkit v.1.8.2 by wugfresh". It may take a little of your time downloading the roms and installing the drivers but trust me it should be working and your phone will boot into stock android 4.1.2. You can then root your device and install custom recovery as normal. Anything do pm me :laugh: ps, click the bricked option one the software is loaded up and remember to connect your device only and remove other phones from your computer

Help with bricked? XT1039...

HI,
First time posting, but read a lot of great info on here in the past. just made a bit of a stupid mistake tho... I'd rooted my XT1039, and then flashed the custom recovery back as well as the stock 4.4.4 eu retail gb. I was getting the 5.1 OTA update, but the install was failing. In my eagerness, I downloaded the GPe Lollipop 5.1 update from here - http://forum.xda-developers.com/moto-g/general/gpe-lollipop-5-1-1click-installer-t3075522 - and tried to flash that, missing that it is for a different phone. Now I'm stuck at the bootloader menu, with the error "fall-through from normal boot mode." Any attempt to select normal powerup, recovery, etc results in a black screen with "Google" written on it and an unlocked padlock symbol.
I was going to try and flash the stock 4.4.4 image I had, but when connecting the phone to the PC via USB, fastboot isn't recognising it as attached, even though the phone detects that USB is connected...
Any help would be seriously and massively appreciated!!
Thanks in advance!

Hey man, I have a similar problem as you. Maybe I can give you a little hand, but its better if somebody who understan everything well give you the hand, becouse I'm a "starter" with this of Moto G.
Your device is charged? With my XT1040, the bootloader didnt connect with the PC via USB if the batery was low. Other thing, which version of bootloader do you have?

Thanks! Yes, the phone is charged! Not sure what version of the bootloader it is...

Start fastboot mode with "Pwr" + "VolDwn" and in the top of the screen says:
Code:
AP Fastboot Flash Mode (S)
41.xx [COLOR="Red"]<--- version of bootloader[/COLOR]

It's 41.19...

Try flashing the CWM Recovery again ClockWorkMod Recovery by Somcom3X with fastboot.
Then mount USB storage and upload an Lollipop's backup/system for your XT1039.
Finally, try to install the Lollipop's zip. If the instalation finish succesfull, wipe data and cache. Then try to start your device normaly (first option of CWM (restart))
Anyway, yesterday I made a thread explaining what happened to me with my XT1040 and how I solve it. Read it if you have time, maybe helps with your problem XT1040 - Reviving bad Lollipop flash/downgrade/bootloader 41.18
Note: I think that XT1039 and XT1040, both can work with the same Lollipop but I'm not sure, ask arround before try with a XT1040 backup.

Hi,
Thanks for that info. Unfortunately I can't do any of that, because fastboot doesn't see the phone any more. When I plug the phone in by USB, windows recognises it, and the phone says that USB is connected, but "ADB devices" in fastboot doesn't see it... So I don't know if it is completely bricked! Selecting any option in the bootloader menu gives me a screen with "Google" on it and a padlock sign...

It has enough battery? If not, Moto G dont allow you to use ADB comands for safety. If not that, really I have no idea. Hopefully someone who knows more than me pass by your thread

Yes, the battery is fully charged... ok, thanks for your help anyway!

Bootloader : (remote: Command did not succeed)

Hi guys, so I got a problem recently, after i startt my phone (like 30 s or 1 min after) the touchscreen stop working, i mean i can still change the volume, watch the video going on but i can't do nothing. So I tried to take off the tap wake up thing, the lockscreen but still nothing, I did a whole reset and nothing. So I decided to just redo everthing, install a new kernel and rom. I'm trying to take off the bootloader so i can install these but it appears that i can't. I already did all the steps : getting the code, usb debbuging, fastboot, installing drivers [S011 right?] but everytime i try to do it with the cmd it tells me that it failed for some reason. Trying with fastboots tells me i can't unlock it officially. So i'm really lost about what i missed or what i need to do.
Thanks for the help guys

I experienced the same problem. Managed to unlock it via the flashtool method, but then I'm unable to flash a kernel, it also says "remote : command did not succeed".
Booted the device, the camera shows only a blank screen, tested it on service test, still, shows nothing.
Relocked it, then the camera starts to work again.
I'm going to try to unlock on Win XP vm this weekend, I'll update to you if I succeed.

??
abrahamt24 said:
I experienced the same problem. Managed to unlock it via the flashtool method, but then I'm unable to flash a kernel, it also says "remote : command did not succeed".
Booted the device, the camera shows only a blank screen, tested it on service test, still, shows nothing.
Relocked it, then the camera starts to work again.
I'm going to try to unlock on Win XP vm this weekend, I'll update to you if I succeed.
Click to expand...
Click to collapse
Hello friend, I have the same problem, absolutely the same as yours.
I solve it ??
regards

xRDBullx said:
Hello friend, I have the same problem, absolutely the same as yours.
I solve it ??
regards
Click to expand...
Click to collapse
I had a Japanese version of the Z3 (SO-01G docomo) which bootloader unfortunately is not unlockable.
Most likely you have a Japanese Z3 as well.
I was stuck with stock-based ROMs. And some ROM wouldn't boot at all.

need bootloop help please

So far I always found answers to all my questions here without ever asking. This forum is awsome! Thanks to everyone here doing good work!
My problem: I have the European version of the Honor View 10. I opened bootloader, I installed the Magisk correctly with the 15.4 version, worked all fine. (thank you topjohnwu)
Then MY mistake ... I wanted to install Xposed Installer. I was not concentrated that moment and took the wrong version! From my other Honor phone (android 6.0, version 89, arm64). Absolutely stupid!
Phone restarted ... bootloop ... and goes into eRecovery. I tried everything I could there, clear dalvik cache, factory reset. > no change!
Then I thought ok, connect to PC, safe mode ... adb ... but no success. adb devices brings no result. PC does not find my phone anymore. I hoped I could get into my phone by connecting with PC, but it seems I am unable. So I can not help myself this way.
Next try was to force the phone to update with SD card. I only found asian update software, but I already did not care. I want to save my phone. Update starts, but after 5% it stops, update fail.
Now I hope that someone here can help. I have no idea what else I could do. Best regards, Markus

mark_at said:
So far I always found answers to all my questions here without ever asking. This forum is awsome! Thanks to everyone here doing good work!
My problem: I have the European version of the Honor View 10. I opened bootloader, I installed the Magisk correctly with the 15.4 version, worked all fine. (thank you topjohnwu)
Then MY mistake ... I wanted to install Xposed Installer. I was not concentrated that moment and took the wrong version! From my other Honor phone (android 6.0, version 89, arm64). Absolutely stupid!
Phone restarted ... bootloop ... and goes into eRecovery. I tried everything I could there, clear dalvik cache, factory reset. > no change!
Then I thought ok, connect to PC, safe mode ... adb ... but no success. adb devices brings no result. PC does not find my phone anymore. I hoped I could get into my phone by connecting with PC, but it seems I am unable. So I can not help myself this way.
Next try was to force the phone to update with SD card. I only found asian update software, but I already did not care. I want to save my phone. Update starts, but after 5% it stops, update fail.
Now I hope that someone here can help. I have no idea what else I could do. Best regards, Markus
Click to expand...
Click to collapse
Did you already try ro flash ramdisk and system sith stock images via fastboot?

alohahe3000 said:
Did you already try ro flash ramdisk and system sith stock images via fastboot?
Click to expand...
Click to collapse
I would flash anything ... if I could! That is my problem at the moment and I can not solve it.
When I start phone I get into Huawei eRecovery after two tries to boot > does not help!
When I connect to PC > phone gets not detected! (during boot try it gets connected shortly ... but then gets disconnected after some seconds, in between I can not get into phone via PC)
So when I would want to use fastboot .... not possible because of that issue. I tried to connect in fastboot mode ... but no difference. Actually I do not understand why I can not connect to PC anymore!
The only way I can imagine now is flash or update something via SD card. I tried with asian update.zip, but it will only go to 5% .... and then ends.
But to be honest ... I am not very optimistic about finding any solution. I think only some very smart pro from this site might have an idea. But not sure if these guys read questions about bootloops.

mark_at said:
Next try was to force the phone to update with SD card.
Click to expand...
Click to collapse
Try to flash via Fastboot the stock rom... do a full wipe and reboot.
here the link to the stock ROM:
https://mega.nz/#!W9hjiTgZ!_ZGq7V83bkWPF_Ue7_c41wVXNrQ_YjnsQUxRS0_MevU

Taobaibai said:
Try to flash via Fastboot the stock rom... do a full wipe and reboot.
Click to expand...
Click to collapse
Thanks for the link. But how can I flash via fastboot when my phone is not detected from the PC? That is my main problem at the moment!
That is why I wrote about all things I had tried already. And being unable to connect to the computer is really worrying me!
"adb devices" will not find my phone!

mark_at said:
Thanks for the link. But how can I flash via fastboot when my phone is not detected from the PC? That is my main problem at the moment!
That is why I wrote about all things I had tried already. And being unable to connect to the computer is really worrying me!
"adb devices" will not find my phone!
Click to expand...
Click to collapse
You have to boot into fastboot modus. When booting, push power and Volume down button. A white screen appears if device is connected with PC.
Then try "fastboot devices". If your device is displayed, you can flash with "fastboot flash" system image. Stock system.img download link can be found in AOSP thread, second post.

alohahe3000 said:
You have to boot into fastboot modus. When booting, push power and Volume down button. A white screen appears if device is connected with PC.
Then try "fastboot devices". If your device is displayed, you can flash with "fastboot flash" system image.
Click to expand...
Click to collapse
Exactly
alohahe3000 said:
Stock system.img download link can be found in AOSP thread, second post.
Click to expand...
Click to collapse
Or just use my link. I copied it from the AOSP Thread

I managed to get my phone displayed when I entered fastboot devices.
And I managed to flash the img!! Hurra !!
Thank you very very much to everyone here helping me ...
I thought that nothing would work because when I typed "abd devices" nothing happened. But when I typed "fastboot devices" the phone was there.

mark_at said:
I managed to get my phone displayed when I entered fastboot devices.
And I managed to flash the img!! Hurra !!
Thank you very very much to everyone here helping me ...
I thought that nothing would work because when I typed "abd devices" nothing happened. But when I typed "fastboot devices" the phone was there.
Click to expand...
Click to collapse
It wasn't so difficult.
Viel Spaß mit dem Smartphone!!!

one more thing I have to add:
after flashing the system.img from the link above .... I have FRP lock .... that was not before.
does it mean I have to relock my bootloader and then unlock it once again? In some other thread I found that information.

mark_at said:
one more thing I have to add:
after flashing the system.img from the link above .... I have FRP lock .... that was not before.
does it mean I have to relock my bootloader and then unlock it once again? In some other thread I found that information.
Click to expand...
Click to collapse
and now I relocked bootloader .... and guess what? bootloop again ... and I can not unlock it again, because I did not think about enable OEM unlock! It says necessary to unlock FRP before.
I am terribly sorry for being such an idiot!!

mark_at said:
and now I relocked bootloader .... and guess what? bootloop again ... and I can not unlock it again, because I did not think about enable OEM unlock! It says necessary to unlock FRP before.
I am terribly sorry for being such an idiot!!
Click to expand...
Click to collapse
Never ever relock bootloader untill you have a backup plan. We have dload method till emui 7 buut not sure on EMUI 8 so can't suggest you anything at the moment. Someone played with EMUI 8 can guide you through it.

I understand that I was not allowed to relock bootloader! I feel awful and stupid about it ... believe me!

I was able to erase FRP with HCU client from DC Phoenix.
After that I was in phone again
And afterwards I could open the bootloader again.
Halleluja!!
Thanks for everyone's help here ...

Fastboot not working

Hi everyone,
after a whole day spent try to fix my oneplus 6, now the roblem is that the fastboot is not working anymore. it gets stuck at the starting point with the oneplus logo and the writing Fastboot Mode.
Just to explain better, i rooted my phone but, trying to fix an audio problem, i did something wrong (probavly wiping all datas with twrp) and the phone got stuck at the Fastboot mode (opposite problem that i have now). After i fixed this (flashing manually every partitions) the phone is working again, but i realised that, by mistake, i used the oxygen 9.0.11 for oneplus 6T. So i tried to go to the Fastboot Mode but it gets stuck at that point. I also see that the phone is not rooted anymore.
I installed again Adb and fastboot but it doesn't fix the problem.
Just to give other random informations, the boot loader is still unlocked and i can't lock it.
As you can see i'm totally not an expert. I just wanted to root my oneplus 6 to increase the volume of the headphones.
Anyone that can help me?
Thanks

Pipp8888 said:
Hi everyone,
after a whole day spent try to fix my oneplus 6, now the roblem is that the fastboot is not working anymore. it gets stuck at the starting point with the oneplus logo and the writing Fastboot Mode.
Just to explain better, i rooted my phone but, trying to fix an audio problem, i did something wrong (probavly wiping all datas with twrp) and the phone got stuck at the Fastboot mode (opposite problem that i have now). After i fixed this (flashing manually every partitions) the phone is working again, but i realised that, by mistake, i used the oxygen 9.0.11 for oneplus 6T. So i tried to go to the Fastboot Mode but it gets stuck at that point. I also see that the phone is not rooted anymore.
I installed again Adb and fastboot but it doesn't fix the problem.
Just to give other random informations, the boot loader is still unlocked and i can't lock it.
As you can see i'm totally not an expert. I just wanted to root my oneplus 6 to increase the volume of the headphones.
Anyone that can help me?
Thanks
Click to expand...
Click to collapse
Try: https://forum.xda-developers.com/oneplus-6/how-to/guide-mega-unbrick-guide-hard-bricked-t3796051
The idea is to boot it in download mode. You'll need the Qualcomm drivers, msm download tool, and oos full rom. Run the tool as administrator.

Pipp8888 said:
Hi everyone,
after a whole day spent try to fix my oneplus 6, now the roblem is that the fastboot is not working anymore. it gets stuck at the starting point with the oneplus logo and the writing Fastboot Mode.
Just to explain better, i rooted my phone but, trying to fix an audio problem, i did something wrong (probavly wiping all datas with twrp) and the phone got stuck at the Fastboot mode (opposite problem that i have now). After i fixed this (flashing manually every partitions) the phone is working again, but i realised that, by mistake, i used the oxygen 9.0.11 for oneplus 6T. So i tried to go to the Fastboot Mode but it gets stuck at that point. I also see that the phone is not rooted anymore.
I installed again Adb and fastboot but it doesn't fix the problem.
Just to give other random informations, the boot loader is still unlocked and i can't lock it.
As you can see i'm totally not an expert. I just wanted to root my oneplus 6 to increase the volume of the headphones.
Anyone that can help me?
Thanks
Click to expand...
Click to collapse
Fastboot require Android SDK(Software Development Kit) and different USB drivers for windows computer may be that's the reason why your Fastboot is not working.
To Root your oneplus 6 :
https://www.theandroidsoul.com/oneplus-6-root/

msm download tool doesn't recognise my phone, and i tried to install the quualcom drivers but my pc whem i try to install it, it says that my phone already has the best drivers.

Pipp8888 said:
msm download tool doesn't recognise my phone, and i tried to install the quualcom drivers but my pc whem i try to install it, it says that my phone already has the best drivers.
Click to expand...
Click to collapse
Maybe uninstall those drivers, reboot pc and reinstall the New ones.

thejase said:
Maybe uninstall those drivers, reboot pc and reinstall the New ones.
Click to expand...
Click to collapse
How can I uninstall the old drivers? Thanks

Pipp8888 said:
How can I uninstall the old drivers? Thanks
Click to expand...
Click to collapse
https://www.drivethelife.com/window...remove-driver-on-windows-10-8-7-xp-vista.html

i unistalled all drivers with Driver Takent. The only driver detected is ADB whem i connect the phone. The Device Manager still recognise my phone in the Usb Devices section as "OnePlus" and still doesn't let me upgrade to the qualcomm drivers.

FINALLY PROBLEM SOLVED with qualcomm drivers!!!! Thank you gus for the big help.
Last question: should i keep useing now the qualcomm drivers? thanks

Pipp8888 said:
FINALLY PROBLEM SOLVED with qualcomm drivers!!!! Thank you gus for the big help.
Last question: should i keep useing now the qualcomm drivers? thanks
Click to expand...
Click to collapse
If it works, yes ofc.