You all probably noticed that if the Settings->Power->Fastboot setting is enabled, Power+Vol_down will not work and the phone will do a standard boot. Is there anyway to force booting the phone into hboot? If not, this is a possible way to get bricked in case your ROM is messed up and the phone's last mode was to Fastboot.
netboy3 said:
You all probably noticed that if the Settings->Power->Fastboot setting is enabled, Power+Vol_down will not work and the phone will do a standard boot. Is there anyway to force booting the phone into hboot? If not, this is a possible way to get bricked in case your ROM is messed up and the phone's last mode was to Fastboot.
Click to expand...
Click to collapse
That's exactly why we leave fastboot off in the settings
Maybe I don't understand the question. Could you not just use:
adb reboot bootloader
or
adb reboot recovery
cntryby429 said:
Maybe I don't understand the question. Could you not just use:
adb reboot bootloader
or
adb reboot recovery
Click to expand...
Click to collapse
You can only use those if adbd is running which means you either were successful in booting into recovery (and you can't do it as power+vol_down doesn't work), or you have a working ROM (see the OP).
xRogerxC said:
That's exactly why we leave fastboot off in the settings
Click to expand...
Click to collapse
I wish it was that simple. The ability to get to the menu seems to be related to the bootloader's ability to access /data. If the bootloader can't get to /data it looks to defaulting to NOT showing the hboot menu. I've noticed this on my phone. I have my phone encrypted which doesn't allow access to /data until you decrypt it. If you cancel out of the decrypt prompt then reboot the phone, you will not be able to power+vol_down (though I never changed the fastboot setting).
netboy3 said:
You all probably noticed that if the Settings->Power->Fastboot setting is enabled, Power+Vol_down will not work and the phone will do a standard boot. Is there anyway to force booting the phone into hboot? If not, this is a possible way to get bricked in case your ROM is messed up and the phone's last mode was to Fastboot.
Click to expand...
Click to collapse
If you are rooted you can use the app quick boot to reboot to hboot without having to do the shutdown but.
Sent from my HTC6525LVW using Tapatalk
dottat said:
If you are rooted you can use the app quick boot to reboot to hboot without having to do the shutdown but.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
See the OP. Assuming your ROM is messed up and is not booting (happens a lot when your'e a flashoholic), you can't run any apps or even get to adb. I've never seen a phone that will not allow you to always be able to cold-boot into the bootloader. This is a serious problem for folks that plan to experiment with lots of ROM flashing.
netboy3 said:
See the OP. Assuming your ROM is messed up and is not booting (happens a lot when your'e a flashoholic), you can't run any apps or even get to adb. I've never seen a phone that will not allow you to always be able to cold-boot into the bootloader. This is a serious problem for folks that plan to experiment with lots of ROM flashing.
Click to expand...
Click to collapse
In that case you hold power and volume buttons until the phone tells you it's going to restart or vibrates or you see the screen flash. Depending on what mode you are in it will do different things. At this point you can release power and move to only volume down.
If timed correctly you will land in hboot. Practice makes perfect.
Sent from my HTC6525LVW using Tapatalk
dottat said:
In that case you hold power and volume buttons until the phone tells you it's going to restart or vibrates or you see the screen flash. Depending on what mode you are in it will do different things. At this point you can release power and move to only volume down.
If timed correctly you will land in hboot. Practice makes perfect.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
dottat, thank you for your post. You are correct. This requires quite a bit of proper timing to succeed. To recap: In case you are in fast-boot power mode and/or have your phone encrypted and power+vol_down doesn't get you into hboot:
1. Power down the phone.
2. Hold volume_up and power.
3. Keep holding the above, you should see the animated HTC splash show up.
4. Keep holding the above, the screen will go dark.
5. Once the screen goes dark, quickly release power and volume_up and press volume_down.
6. If timed perfectly, you should land in hboot menu.
Thanks again to dottat for pointing it out.
Related
okay guys so surprisingly i havent seen anything on here about the button combo to get into bootloader on your one x (or recovery)
i think its just volume down and power ? but a lot of the time it just boots up like normal.
anything specific i can do to get it to work better?
also once i re lock my bootloader, there is no way for me to get the phone to boot up normally, like no matter what i do it just reboots into the bootloader what should i do?
(basically im trying to get from clean rom on 1.82.5 base , back to offical stock 1.73.5)
The_Zodiac said:
okay guys so surprisingly i havent seen anything on here about the button combo to get into bootloader on your one x (or recovery)
i think its just volume down and power ? but a lot of the time it just boots up like normal.
anything specific i can do to get it to work better?
also once i re lock my bootloader, there is no way for me to get the phone to boot up normally, like no matter what i do it just reboots into the bootloader what should i do?
(basically im trying to get from clean rom on 1.82.5 base , back to offical stock 1.73.5)
Click to expand...
Click to collapse
You have to hold vol down the entire time until it gets to the bootloader. Also, turn fastboot off.
Or you can always "adb reboot recovery" if you're at a computer
The_Zodiac said:
okay guys so surprisingly i havent seen anything on here about the button combo to get into bootloader on your one x (or recovery)
i think its just volume down and power ? but a lot of the time it just boots up like normal.
anything specific i can do to get it to work better?
also once i re lock my bootloader, there is no way for me to get the phone to boot up normally, like no matter what i do it just reboots into the bootloader what should i do?
(basically im trying to get from clean rom on 1.82.5 base , back to offical stock 1.73.5)
Click to expand...
Click to collapse
I've found that if you lock the bootloader while on a rom that uses an insecure boot.img like cleanrom does you'll see "security warning" on the bootloader screen and the phone won't boot to anything except the bootloader. It's ok though because you can install the ruu from there.
stnguyen09 said:
You have to hold vol down the entire time until it gets to the bootloader. Also, turn fastboot off.
Or you can always "adb reboot recovery" if you're at a computer
Click to expand...
Click to collapse
gunnyman said:
I've found that if you lock the bootloader while on a rom that uses an insecure boot.img like cleanrom does you'll see "security warning" on the bootloader screen and the phone won't boot to anything except the bootloader. It's ok though because you can install the ruu from there.
Click to expand...
Click to collapse
how do you disable fastboot? (or you mean while the phone is running normally in settings?)
i tried running the ruu from the bootloader and it wouldnt work though
is there a different rom i could flash, then be able to lock and flash back to stock 1.7?
The_Zodiac said:
how do you disable fastboot? (or you mean while the phone is running normally in settings?)
i tried running the ruu from the bootloader and it wouldnt work though
is there a different rom i could flash, then be able to lock and flash back to stock 1.7?
Click to expand...
Click to collapse
from the bootloader screen choose fastboot and you should be able to install the RUU
This method of getting into the bootloader always works for me.
It involves counting so read it through first as you need to act quickly:
Hold down the power button untill you see the capacitive buttons start flashing.
After a few seconds they will stop flashing.
Hold the volume down button immediately.
Then hold the power button for around 3 seconds and release it, while still holding the volume up button.
Hold it until you boot into the bootloader screen.
rohan32 said:
This method of getting into the bootloader always works for me.
It involves counting so read it through first as you need to act quickly:
Hold down the power button untill you see the capacitive buttons start flashing.
After a few seconds they will stop flashing.
Hold the volume down button immediately.
Then hold the power button for around 3 seconds and release it, while still holding the volume up button.
Hold it until you boot into the bootloader screen.
Click to expand...
Click to collapse
ill have to give this a shot, at what point do you start holding the volume up button?
Hi,
My Nexus S was working great and suddenly the power button stopped working, now when I try to flash anything via fastboot it freezes at the bootloader screen, the volume keys don't work just there.
I wanted to flash stock ICS bootloader, radio and ROM but I guess there's no way to flash without fastboot? adb works though.
Thanks for your help!
ibr4him said:
Hi,
My Nexus S was working great and suddenly the power button stopped working, now when I try to flash anything via fastboot it freezes at the bootloader screen, the volume keys don't work just there.
I wanted to flash stock ICS bootloader, radio and ROM but I guess there's no way to flash without fastboot? adb works though.
Thanks for your help!
Click to expand...
Click to collapse
Is your power button failing by any chance? If the power button fails and stay in a clicked position, you will not be able to scroll.
No, the power button, physically, is perfect, just as it was before. it just doesn't 'function' anymore.
ibr4him said:
No, the power button, physically, is perfect, just as it was before. it just doesn't 'function' anymore.
Click to expand...
Click to collapse
So it works or it doesn't work? That's what I mean by failing, when it stops working, you will not be able to scroll in fastboot mode because it's stuck as clicked in. In fastboot you cannot send 2 keystrokes at the same time, so as long as the power button is stuck you're out of luck.
Sometimes playing with the power button will make it unstuck, sometimes it will not. It's a very common problem with the Nexus S. Some people had decent luck opening up their Nexus and cleaning the power button while others sent their phone to repair.
No, it does not function. BUT, what I'm thinking is, if i the power button was CLICKED then the first option is "Restart Bootloader" and it would have been auto-selected resulting in a reboot-loop, but I do see the bootloader screen and it doesn't disappear until I remove the battery and restart.
ibr4him said:
No, it does not function. BUT, what I'm thinking is, if i the power button was CLICKED then the first option is "Restart Bootloader" and it would have been auto-selected resulting in a reboot-loop, but I do see the bootloader screen and it doesn't disappear until I remove the battery and restart.
Click to expand...
Click to collapse
That's not how it works though. It's constantly clicked, not as clicking only once the bootloader appears. I know it's strange, but it's really a well known issue.
If you remove the battery and put it back in, does your phone start automatically? That's also a sign the power button is stuck.
No, If I remove the battery and reinsert, it does NOT autostart unless its also connected to the PC via USB.
ibr4him said:
No, If I remove the battery and reinsert, it does NOT autostart unless its also connected to the PC via USB.
Click to expand...
Click to collapse
Alright. Does not necessarily mean the button isn't stuck though.
Do you have a custom recovery? If you use Clockworkmod or TWRP, you can flash nearly anything from there, rom, radio and so on as long as they're zipped in a way one of these recovery will understand.
If you are still able to boot your rom and it's rooted, but you don't have a custom recovery, you can flash one from within Android.
Oh, I thought you could only flash bootloader, radio and ROM via fastboot, atleast thats how I did so far. I download factory images and they come as .img files, is there anywhere I can find a flashable stock ICS .zip?
Yes, I can boot into the stock JB rom, and yes I can even access clockwork recovery.
ibr4him said:
Oh, I thought you could only flash bootloader, radio and ROM via fastboot, atleast thats how I did so far. I download factory images and they come as .img files, is there anywhere I can find a flashable stock ICS .zip?
Yes, I can boot into the stock JB rom, and yes I can even access clockwork recovery.
Click to expand...
Click to collapse
You were doing it the good way though, fastboot is a very strong utility.
Here's one flashable with CWM.
http://forum.xda-developers.com/showthread.php?t=1569509&highlight=rom
ONLY for GSM Nexus S. Not for 4G. This is really important.
One more way I was able to confirm that the phone indeed freezes on bootloader is that adb commands are accepted on the home screen or on CWM (./adb reboot bootloader for example), but neither adb nor fastboot works on the bootloader (error: device not found).
I opened the phone to clean the power button as you suggested, but its already quite clean, there's nothing to do there. However, I broke my sim tray in the process! :'(
Now, no power button and no network!
ibr4him said:
I opened the phone to clean the power button as you suggested, but its already quite clean, there's nothing to do there. However, I broke my sim tray in the process! :'(
Now, no power button and no network!
Click to expand...
Click to collapse
Ouch! That's not good at all. :|
Some people blast the button with compressed air or clean it with isopropyl alcohol.
Ok.. I'm about to lose hope, please any creative ideas will be much appreciated..
I think i did a big mistake trying to update to the latest nightly release of CM 10.2 using the auto-update feature of cm 10.1...
The end result is a bootloop, gets up to the CM rotating animation for a few seconds and reboots.
on top of that:
unable to get into bootloader using pwr+vol up nor vol down
unable to access device using adb nor fastboot - shows no device connected
the PC does not recognize the device though there are drivers installed, the charging LED lights up but no PC activity
all of the solutions i've seen assume either the recover/bootloader is available or the phone is accessed via fastboot/adb.
in this case neither are correct....
for some time i wanted to upgrade to htc one but not yet....
please help
Press and hold power until the phone shuts off.
Then let go of power and press and hold volume down until bootloader comes up.
Sent from my One X using xda app-developers app
exad said:
Press and hold power until the phone shuts off.
Then let go of power and press and hold volume down until bootloader comes up.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
tried it again several time, but as I said it doesn't work.
I get a black screen (not the CM animation) and than reboot all over again.
You could try letting it drain completely. Then charge a bit and try again.
Is your phone plugged in while your trying? My phone will not enter bootloader while its plugged in.
Sent from my One X using xda app-developers app
spitfireatz said:
tried it again several time, but as I said it doesn't work.
I get a black screen (not the CM animation) and than reboot all over again.
Click to expand...
Click to collapse
You are mostly likely not performing the button combo correctly. If there were no bootloader (hboot), the screen would not be coming on at all. Not getting into bootloader is almost always a case of not doing the button combo correctly. The one possible exception, is if your volume rocker has failed (and simply not registering the vol down being pressed).
Make sure you hold vol down, and do not let go until the while bootloader screen comes up.
Recovery is a different story, as you can indeed not have recovery installed, and the phone will still function. But hboot and recovery are 2 different things.
redpoint73 said:
You are mostly likely not performing the button combo correctly. If there were no bootloader (hboot), the screen would not be coming on at all. Not getting into bootloader is almost always a case of not doing the button combo correctly. The one possible exception, is if your volume rocker has failed (and simply not registering the vol down being pressed).
Make sure you hold vol down, and do not let go until the while bootloader screen comes up.
Recovery is a different story, as you can indeed not have recovery installed, and the phone will still function. But hboot and recovery are 2 different things.
Click to expand...
Click to collapse
I wish it was the case,
when i try to go into hboot the device instead of going into another boot until animation cycle, goes into black screen boot cycle. which means most likely that the action (PWR+Vol) does have an effect otherwise it would have continued to go into same boot cycle through the CM animation..
besides there is a recovery installed, or at least was...
is there anyway to re-install the hboot part without the hboot/fastboot availability?
spitfireatz said:
is there anyway to re-install the hboot part without the hboot/fastboot availability?
Click to expand...
Click to collapse
If you are s-off, try running the RUU.
I bricked my htc one m8. Dont even know how, all i had was cyanogenmod 11 installed and it and my phone just boots into black screen after initial splash screen. I can get the charging indicator to show at low or full battery and i get vibration feedback when i hard reboot. I cant get into recovery or bootloader and my computer doesn't recognize it. What do!!
piisceiss said:
I bricked my htc one m8. Dont even know how, all i had was cyanogenmod 11 installed and it and my phone just boots into black screen after initial splash screen. I can get the charging indicator to show at low or full battery and i get vibration feedback when i hard reboot. I cant get into recovery or bootloader and my computer doesn't recognize it. What do!!
Click to expand...
Click to collapse
if your phone boots into a black screen its not hardbricked, hardbricked means it wont turn on at all and you have no indicators
piisceiss said:
I bricked my htc one m8. Dont even know how, all i had was cyanogenmod 11 installed and it and my phone just boots into black screen after initial splash screen. I can get the charging indicator to show at low or full battery and i get vibration feedback when i hard reboot. I cant get into recovery or bootloader and my computer doesn't recognize it. What do!!
Click to expand...
Click to collapse
Does ADB recognize the device?
piisceiss said:
I bricked my htc one m8. Dont even know how, all i had was cyanogenmod 11 installed and it and my phone just boots into black screen after initial splash screen. I can get the charging indicator to show at low or full battery and i get vibration feedback when i hard reboot. I cant get into recovery or bootloader and my computer doesn't recognize it. What do!!
Click to expand...
Click to collapse
Unplug your phone and hold volume up and power for 30
seconds. Do not have it plugged in while doing this.
Bierce22 said:
if your phone boots into a black screen its not hardbricked, hardbricked means it wont turn on at all and you have no indicators
Click to expand...
Click to collapse
Ok so thats good to know
DizDroid said:
Does ADB recognize the device?
Click to expand...
Click to collapse
No but i could be doing aomething wrong. Ill give it another go
piisceiss said:
No but i could be doing aomething wrong. Ill give it another go
Click to expand...
Click to collapse
You may need to uncheck usb debugging in developer options then reboot and go in and check usb debugging again then try adb tools using adb devices and see if it works then. Some m8's can be a real pain that way you just need to keep trying.
M9guy said:
You may need to uncheck usb debugging in developer options then reboot and go in and check usb debugging again then try adb tools using adb devices and see if it works then. Some m8's can be a real pain that way you just need to keep trying.
Click to expand...
Click to collapse
I cant boot into the os, it only goes to a black screen. It still vibrates though when i try doing any form of reset
piisceiss said:
I cant boot into the os, it only goes to a black screen. It still vibrates though when i try doing any form of reset
Click to expand...
Click to collapse
I would run the newest ruu that dottat has posted in the android development section for this phone, put it on your sd card using your computer, then put it back in your phone and boot to fastboot and let it pick it up and hit I believe it is yes and it will restore your phone. You are on 4.4.4 right ? If you are having problems getting to fastboot hold power and volume up until you see the lights change and or it vibrate then quickly switch to power and volume down and it should take you to fastboot, it may take you multiple tries to get it there. This sounds like the screen of death issues people have had on viperone which the fix for that so far has been to reverse the 4g handoff fix as most people that have the sod they had used the 4g handoff fix but if you cant get past the black screen then you cant do the fix for that. Have you tried leaving your phone sit for a while to see if it comes out of it ? Also most people only had that issue in weak signal areas so a good signal area could get your screen working again if you had done the 4g handoff fix. If you did some have said that the change can stick even through a ruu, but I cannot verify that either way.
Can I say I'm having an almost same problem.
I wiped my phone in prep of loading a new rom.
RUU the firmware for 4.4.4
Loaded twrp
and then it rebooted to the htc screen.
Now I can't get past that screen. I can hard reboot but it only comes back to that screen. and if I try to access it through the computer it can't load the driver so that I can sideload.
Help please
rcbarrieault said:
Can I say I'm having an almost same problem.
I wiped my phone in prep of loading a new rom.
RUU the firmware for 4.4.4
Loaded twrp
and then it rebooted to the htc screen.
Now I can't get past that screen. I can hard reboot but it only comes back to that screen. and if I try to access it through the computer it can't load the driver so that I can sideload.
Help please
Click to expand...
Click to collapse
it's tricky to get it back to hboot... but you can with practice. Hold power a both volume buttons until you think it finally has rebooted. Switch to only holding vol down to enter hboot. Timing and practice makes perfect.
It took about an hour of trying. But I did it. Plus I had to do a few other things to get things remounted.
rcbarrieault said:
It took about an hour of trying. But I did it. Plus I had to do a few other things to get things remounted.
Click to expand...
Click to collapse
I will have to try this. What other things did you do?
Once I was back in recovery I reformatted before rebooting and then from recovery I installed the rom.
dottat said:
it's tricky to get it back to hboot... but you can with practice. Hold power a both volume buttons until you think it finally has rebooted. Switch to only holding vol down to enter hboot. Timing and practice makes perfect.
Click to expand...
Click to collapse
I did this and we're all fixed, thank you for all the replies
dottat said:
it's tricky to get it back to hboot... but you can with practice. Hold power a both volume buttons until you think it finally has rebooted. Switch to only holding vol down to enter hboot. Timing and practice makes perfect.
Click to expand...
Click to collapse
I agree with Dottat, faced the same issue when trying to flash ARHD 22.1 on my Verizon M8. I think I sprayed some **** in my pants with that loud fart .
After trying several times I got the trick and could get into Hboot. The issue I think was I was holding Power + Volume up & down for more than required time and it Rebooted. We need to Switch Off the device by Holding Power + Volume UP & Down button for about 8-10 secs and then just remove the finger from Volume UP button. It takes you to Hboot mode..
Hello,
I've rooted my Pixel 3 as described here in the forum.
Everything went well and I was booting in TWRP without any problems; Bootloader is still unlocked. I didn't installed a custom ROM or anything else. After I've selcted "restore backup" my backup (which I've made before with TWRP) my phone is now messed up:
It's starting in Bootloader (Warning Screen for unlocked Bootloader) and than is switching on an white screen with Google logo for ca. 3-4 sec. and than it's jumping back into the Bootloader in an endless Loop.
Any idea what I can do to rescue my phone?
Thanks, Mags
MMoes said:
Hello,
I've rooted my Pixel 3 as described here in the forum.
Everything went well and I was booting in TWRP without any problems; Bootloader is still unlocked. I didn't installed a custom ROM or anything else. After I've selcted "restore backup" my backup (which I've made before with TWRP) my phone is now messed up:
It's starting in Bootloader (Warning Screen for unlocked Bootloader) and than is switching on an white screen with Google logo for ca. 3-4 sec. and than it's jumping back into the Bootloader in an endless Loop.
Any idea what I can do to rescue my phone?
Thanks, Mags
Click to expand...
Click to collapse
In bootloader mode can you get your computer to recognize the phone. If so, download the latest update from Google website and install using adb. This will wipe the phone but will get it restored. I've had to do this in my pixel 2 before. I don't have the pixel 3 yet as I just ordered it today.
MMoes said:
Hello,
I've rooted my Pixel 3 as described here in the forum.
Everything went well and I was booting in TWRP without any problems; Bootloader is still unlocked. I didn't installed a custom ROM or anything else. After I've selcted "restore backup" my backup (which I've made before with TWRP) my phone is now messed up:
It's starting in Bootloader (Warning Screen for unlocked Bootloader) and than is switching on an white screen with Google logo for ca. 3-4 sec. and than it's jumping back into the Bootloader in an endless Loop.
Any idea what I can do to rescue my phone?
Thanks, Mags
Click to expand...
Click to collapse
FilthyFord said:
In bootloader mode can you get your computer to recognize the phone. If so, download the latest update from Google website and install using adb. This will wipe the phone but will get it restored. I've had to do this in my pixel 2 before. I don't have the pixel 3 yet as I just ordered it today.
Click to expand...
Click to collapse
You can also edit the flash-all file to remove the -w and not completely wipe your phone. This way, your data will remain and it still resets the important factory stuff.
FilthyFord said:
In bootloader mode can you get your computer to recognize the phone. If so, download the latest update from Google website and install using adb. This will wipe the phone but will get it restored. I've had to do this in my pixel 2 before. I don't have the pixel 3 yet as I just ordered it today.
Click to expand...
Click to collapse
Thanks, I‘ve tried with adb devices & no device found. So obviously my computer doesn‘t recognize the Pixel
sliding_billy said:
You can also edit the flash-all file to remove the -w and not completely wipe your phone. This way, your data will remain and it still resets the important factory stuff.
Click to expand...
Click to collapse
Thanks. Loosing my data isn‘t the Problem. Actually I‘m even not able to connect to the phone and flash anything.
MMoes said:
Thanks. Loosing my data isn‘t the Problem. Actually I‘m even not able to connect to the phone and flash anything.
Click to expand...
Click to collapse
Have you hard powered the device down and then rebooted to BL with key combo to check connectivity?
sliding_billy said:
Have you hard powered the device down and then rebooted to BL with key combo to check connectivity?
Click to expand...
Click to collapse
No, could you please descripe the process what to do exactly. Would love to give it a try. Thank you
MMoes said:
No, could you please descripe the process what to do exactly. Would love to give it a try. Thank you
Click to expand...
Click to collapse
Hold down the power button until the phone completely shuts off. Hold power while holding the volume down button (start by holding the volume down and then immediately start holding the power button - it's is technically holding both at the same time but starting with volume down just a moment before keeps you from pressing power first). That should get you to fastboot.
MMoes said:
Thanks, I‘ve tried with adb devices & no device found. So obviously my computer doesn‘t recognize the Pixel
Click to expand...
Click to collapse
ADB doesn't work when booted to the bootloader. It only works when you're booted to the OS. To see if the computer recognizes the phone when in the bootloader, use fastboot devices instead of adb devices.
sliding_billy said:
Hold down the power button until the phone completely shuts off. Hold power while holding the volume down button (start by holding the volume down and then immediately start holding the power button - it's is technically holding both at the same time but starting with volume down just a moment before keeps you from pressing power first). That should get you to fastboot.
Click to expand...
Click to collapse
Holding the power button didn't had any effect, but holding volume - and holding power button at the same time was starting the bootloader and so I was now able to start TWRP Manager.
So if you could help me from here to fix the OS would be great, e.g. is there any chance to copy the original OS from Google or an custom ROM from my computer (e.g. I wotk on MAC and is there a way to copy via Terminal?) or does TWRP offers any way to reset/ reinstall?
robocuff said:
ADB doesn't work when booted to the bootloader. It only works when you're booted to the OS. To see if the computer recognizes the phone when in the bootloader, use fastboot devices instead of adb devices.
Click to expand...
Click to collapse
Yes, the computer recognizes the phone (via Terminal on my MAC)
MMoes said:
Holding the power button didn't had any effect, but holding volume - and holding power button at the same time was starting the bootloader and so I was now able to start TWRP Manager.
So if you could help me from here to fix the OS would be great, e.g. is there any chance to copy the original OS from Google or an custom ROM from my computer (e.g. I wotk on MAC and is there a way to copy via Terminal?) or does TWRP offers any way to reset/ reinstall?
Click to expand...
Click to collapse
Sorry, but I do not know the Mac commands, but if you are in Fastboot and the device shows/connects it is just a matter of running the flash-all and resetting. If you are not connecting in Fastboot but can get into TWRP, I would start with a reset in TWRP.
sliding_billy said:
Sorry, but I do not know the Mac commands, but if you are in Fastboot and the device shows/connects it is just a matter of running the flash-all and resetting. If you are not connecting in Fastboot but can get into TWRP, I would start with a reset in TWRP.
Click to expand...
Click to collapse
The commands on the MAC are almost the same and with your flash-all (flash.all.sh Mac Command) it worked very well with the factory image from google. Now I'm back in the race and my P3 is running again.
Thank you all guys!
MMoes said:
The commands on the MAC are almost the same and with your flash-all (flash.all.sh Mac Command) it worked very well with the factory image from google. Now I'm back in the race and my P3 is running again.
Thank you all guys!
Click to expand...
Click to collapse
Excellent news. On another note... if all you need from TWRP is to install Magisk to root, you do not need to permanently install TWRP. Just fastboot boot the [twrp].img file, install the Magisk .zip and keep stock recovery.
From messing around, it seems that trying to restore system from twrp is messed up. Data backup works fine. The only other way I got bootlooped was by messing with boot, vbmata, and vendor partitions. Out of those three, I think boot is the most likely to get messed up by normal users. I know this is sorted now, but in the future try to just reflash boot.img and see if it boots.
-The vbmeta and vendor thing is specific because I need to get the radio to work here.