I think i have a huge problem here. I flashed Paranoid and my phone now is stuck on boot logo, the problem is that i cant turn off the phone nor star fastboot cuz my volume down key is not working... is there any way to get into fastboot using commands or sommething? thanks in advance.
DualDark said:
I think i have a huge problem here. I flashed Paranoid and my phone now is stuck on boot logo, the problem is that i cant turn off the phone nor star fastboot cuz my volume down key is not working... is there any way to get into fastboot using commands or sommething? thanks in advance.
Click to expand...
Click to collapse
If you are stuck in bootloop you won't be able to enter bootloader directly by pushing Powe+VolDown.
Firstly you have to power off the device (Power+VolUp+VolDown) and, when the screen goes off, you will be able to enter bootloader again (VolDown+Power)
I hope it helps,
-Z-
skorpionvenom said:
If you are stuck in bootloop you won't be able to enter bootloader directly by pushing Powe+VolDown.
Firstly you have to power off the device (Power+VolUp+VolDown) and, when the screen goes off, you will be able to enter bootloader again (VolDown+Power)
I hope it helps,
-Z-
Click to expand...
Click to collapse
thank you, but the problem is that my voldown key is not working, it broke down a few days ago...
DualDark said:
thank you, but the problem is that my voldown key is not working, it broke down a few days ago...
Click to expand...
Click to collapse
Can you detect your phone via adb ?
--> adb devices
if the answer is yes, you can just type
--> adb reboot recovery (I hope that you have twrp because that's a touch recovery)
skorpionvenom said:
If you are stuck in bootloop you won't be able to enter bootloader directly by pushing Powe+VolDown.
Firstly you have to power off the device (Power+VolUp+VolDown) and, when the screen goes off, you will be able to enter bootloader again (VolDown+Power)
I hope it helps,
-Z-
Click to expand...
Click to collapse
skorpionvenom said:
Can you detect your phone via adb ?
--> adb devices
if the answer is yes, you can just type
--> adb reboot recovery (I hope that you have twrp because that's a touch recovery)
Click to expand...
Click to collapse
Tried... but when in bootlogo and type it, not any device is shown...
DualDark said:
Tried... but when in bootlogo and type it, not any device is shown...
Click to expand...
Click to collapse
you can always try fastboot, even if I don't know if it's gonna work:
--> fastboot reboot-bootloader
skorpionvenom said:
you can always try fastboot, even if I don't know if it's gonna work:
--> fastboot reboot-bootloader
Click to expand...
Click to collapse
didnt work either... it just said <waiting for device>... damn it... ¬¬
DualDark said:
didnt work either... it just said <waiting for device>... damn it... ¬¬
Click to expand...
Click to collapse
Some users reported that it may take a while before the phone gets detected... alternatively you can try to change USB port.
If you cannot physically enter bootloader and you do not have access to either adb or fastboot, I am afraid that I don't know how to help you :crying:
skorpionvenom said:
Some users reported that it may take a while before the phone gets detected... alternatively you can try to change USB port.
If you cannot physically enter bootloader and you do not have access to either adb or fastboot, I am afraid that I don't know how to help you :crying:
Click to expand...
Click to collapse
I let it detecting since my last post till' this one and nothing happens... imma try changing to another usb port... this must be the most stupid half brick ever ¬¬
DualDark said:
I let it detecting since my last post till' this one and nothing happens... imma try changing to another usb port... this must be the most stupid half brick ever ¬¬
Click to expand...
Click to collapse
I honestly do not believe that your device is bricked... it just sucks that you cannot use the physical VolDown... I am pretty sure that if you get that fixed than you'll be able to restore your phone
skorpionvenom said:
I honestly do not believe that your device is bricked... it just sucks that you cannot use the physical VolDown... I am pretty sure that if you get that fixed than you'll be able to restore your phone
Click to expand...
Click to collapse
well i think so, but it is a brick till' i get fixed it... the problem is that the people that repairs in my country is like "oh this is a very new model, it'll be expensive to fix it" ¬¬, and also i cant use the warranty, im pretty sure they wont realise that i unlocked the bootloader, but the custom bootlogo is gonna be the problem...
anyway thanks for your help, now im on my way to check it out how much will cost repair the button...
Related
Hating life right now. Broken power button, once I get into fastboot it says 'No boot or recovery img' and fastboot doesn't respond and doesn't show up as a device during adb. Any tips or am I royally ****ed?
http://forum.xda-developers.com/showthread.php?t=1524858
Kitch16 said:
Hating life right now. Broken power button, once I get into fastboot it says 'No boot or recovery img' and fastboot doesn't respond and doesn't show up as a device during adb. Any tips or am I royally ****ed?
Click to expand...
Click to collapse
Step 1:
Download the appropriate factory image from: https://developers.google.com/android/nexus/images#sojuimm76d and make sure you have a working fastboot tool on your computer.
The thing is. I can get to fastboot, but it just doesn't respond, I can't use the volume keys during it...
Kitch16 said:
The thing is. I can get to fastboot, but it just doesn't respond, I can't use the volume keys during it...
Click to expand...
Click to collapse
Pretty sure your screwed. Same thing happened to me and there is nothing to do.
Sent from my Nexus S using xda premium
xsteven77x said:
Pretty sure your screwed. Same thing happened to me and there is nothing to do.
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
I'll send it back to Samsung. Hope they give me a new one :') doubt it though
Hello there. This is the last chance to wake up my phone because I already made a big number of googling..
I have tried to change custom recovery, got error message that space (or memory) is not enough. Resterted the phone and it just turned off. Now I cannot boot it. Phone has no reaction to buttons pressed. I have tried to boot into hboot (volume down+power) but phone is dead, The only positive thing is that the phone recognizes the charging over the AC and USB.
Please could anyone suggest how I can boot the phone into hboot/bootloader/fastboot?..
AMKiss said:
Hello there. This is the last chance to wake up my phone because I already made a big number of googling..
I have tried to change custom recovery, got error message that space (or memory) is not enough. Resterted the phone and it just turned off. Now I cannot boot it. Phone has no reaction to buttons pressed. I have tried to boot into hboot (volume down+power) but phone is dead, The only positive thing is that the phone recognizes the charging over the AC and USB.
Please could anyone suggest how I can boot the phone into hboot/bootloader/fastboot?..
Click to expand...
Click to collapse
Might sound obvious but did u pull the battery out n put back in, then try boot into bootloader.
jmcclue said:
Might sound obvious but did u pull the battery out n put back in, then try boot into bootloader.
Click to expand...
Click to collapse
I did, sir...
AMKiss said:
I did, sir...
Click to expand...
Click to collapse
I have the exact same issue...were you able to fix it?
No, I weren't.. I have just sold it as a brick for parts..
AMKiss said:
No, I weren't.. I have just sold it as a brick for parts..
Click to expand...
Click to collapse
k...Thanks for the response...I Think this is the end for me too...Btw, just for the record, how exactly did you try to install the recovery? via ADB or terminal emulator or app?
antimage05 said:
k...Thanks for the response...I Think this is the end for me too...Btw, just for the record, how exactly did you try to install the recovery? via ADB or terminal emulator or app?
Click to expand...
Click to collapse
Terminal emulator
Hello
My Nexus 5 is all of a sudden stuck in a bootloop, see video at https://plus.google.com/+AlexanderSkwar/posts/YY6VieTVq7Z
I guess, the power button is broken, or something like this. Google will replace the device, but there's one file on the device, which I'd need access to — my Libra database…
Well, would anyone have an idea, how I could get access to it? When I connect USB cable (or use Qi charger), the system boots but then directly reboots. I cannot adb to it. I also get thrown out of the fastboot (power + volume down) menu right away.
Ideas? Anyone? :crying:
Thanks,
Alexander
Do you have a custom recovery installed? do you have adb and fastboot set up in your computer?
alexs77 said:
Hello
My Nexus 5 is all of a sudden stuck in a bootloop, see video at https://plus.google.com/+AlexanderSkwar/posts/YY6VieTVq7Z
I guess, the power button is broken, or something like this. Google will replace the device, but there's one file on the device, which I'd need access to — my Libra database…
Well, would anyone have an idea, how I could get access to it? When I connect USB cable (or use Qi charger), the system boots but then directly reboots. I cannot adb to it. I also get thrown out of the fastboot (power + volume down) menu right away.
Ideas? Anyone? :crying:
Thanks,
Alexander
Click to expand...
Click to collapse
Well maybe removing the power key or fixing it without replacing the motherboard would work, but if you that you will lose your warranty :
el_daYa said:
Do you have a custom recovery installed? do you have adb and fastboot set up in your computer?
Click to expand...
Click to collapse
Yes, I do have a custom recovery setup. Yes, I do have adb and fastboot setup on my computer.
No, I don't get into fastboot or the custom recovery. If I try to, it will reboot right away, as shown on the video. [emoji30]
bitdomo said:
Well maybe removing the power key or fixing it without replacing the motherboard would work, but if you that you will lose your warranty :
Click to expand...
Click to collapse
Uhm, well, losing my warranty is of course also something, I would not want [emoji26]
Try plugging the phone to the computer then run "adb devices" if it recognizes it try to from adb reboot into bootloader or tell it to reboot into recovery. dont know what else to do. It looks like you are going to learn some sleight of hands my friend.
el_daYa said:
Try plugging the phone to the computer then run "adb devices" if it recognizes it try to from adb reboot into bootloader or tell it to reboot into recovery. dont know what else to do. It looks like you are going to learn some sleight of hands my friend.
Click to expand...
Click to collapse
I do know my way around adb
adb devices will only show the device , if it is booted. It does not boot - what happens, is visible in the Google+ post, which contains a video.
I tried plugging it in and it is not shown. Also not with the fastboot command (ie. "sudo fastboot devices" shows nothing. Adb also does not find the device). That is, what I meant with "I cannot adb to the device".
Then I am afraid you'll need assistance from a higher level my friend, sorry I wasn't much help.
Hello,
At one point this tablet was working just fine. It sat for a while and now it boot loops. Shows the amazon logo and auto restarts.
I can hold the proper volume up or down key and it says "Recovery Mode" on the bottom left but never enters into it.
Oddly enough I wasn't screwing around trying to do something I shouldn't have, but for the life of me I can't figure out what the deal is. Have anything I can try to possibly recover it? or is it straight to the bin.
Thank you in advance.
Take care,
Try fastboot boot recovery.img with the help of PC, if it boots format data and install rom.
Shiva Kumar A said:
Try fastboot boot recovery.img with the help of PC, if it boots format data and install rom.
Click to expand...
Click to collapse
Yeah good idea I'll report back .. I mean I can't break it anymore heh. I'm going to blame gamma rays coming down from from space and flipping a single bit in my 6 year old tablet............... causing it to boot loop.
So thinking out
Shiva Kumar A said:
Try fastboot boot recovery.img with the help of PC, if it boots format data and install rom.
Click to expand...
Click to collapse
So thinking out loud.
How do I get the tablet in a spot to accept a fastboot via USB?
It doesn't start up correctly to booted android. It doesn't enter TWRP... it seems as if I am stuck right?
likwidchz said:
So thinking out
So thinking out loud.
How do I get the tablet in a spot to accept a fastboot via USB?
It doesn't start up correctly to booted android. It doesn't enter TWRP... it seems as if I am stuck right?
Click to expand...
Click to collapse
What's happening when you try to boot into fastboot mode? After entering fastboot mode in cmd "fastboot boot twrp.img" "(drag and drop twrp file after boot )" it'll boot into twrp.
Shiva Kumar A said:
What's happening when you try to boot into fastboot mode? After entering fastboot mode in cmd "fastboot boot twrp.img" "(drag and drop twrp file after boot )" it'll boot into twrp.
Click to expand...
Click to collapse
You will have to explain how I would boot it into fastboot mode if
1 The tablet doesn't fully boot up past the amazon logo.
2 I cant even enter TWRP.
What am I missing?
Thank you and cheers!
When the device is fully shutdown press volume down + power.or maybe volume up check your device's combination key
Shiva Kumar A said:
When the device is fully shutdown press volume down + power.or maybe volume up check your device's combination key
Click to expand...
Click to collapse
Right then what? I'm missing something here.
likwidchz said:
Right then what? I'm missing something here.
Click to expand...
Click to collapse
I can't understand you what you trying to ask?
Shiva Kumar A said:
I can't understand you what you trying to ask?
Click to expand...
Click to collapse
Hello apologies,
I'll try and be as verbose as possible this time
This executes
[email protected]:/usr/src/giza# ./boot-fastboot.sh
[2023-02-08 12:26:26.386801] Waiting for preloader
[2023-02-08 12:26:50.335150] Found port = /dev/ttyACM0
[2023-02-08 12:26:50.365886] Handshake
[2023-02-08 12:26:50.386040] Preloader ready, sending FACTFACT
*Holding the left volume button + power button for some time.
[email protected]:/usr/src/giza# fastboot flash recovery bin/recovery.img
< waiting for any device >
Ive had this execute once, but when it does it looks like it wiped out TWRP as I cant get the small text to appear on the bottom left hand corner of the tablet while it does a boot holding power and the volume button.
So I'm not quite sure what I can do now.
Is there a method to flash TWRP with fastboot? or is that what the recovery is?
Could you provide a detailed list of items to try out and some high level instructions.
I've been thumbing through https://forum.xda-developers.com/t/unlock-root-twrp-unbrick-fire-hd-8-2016-giza.4303443/ this guide, but realize I'm not sure which step I need to start from, so I have bene trying a bunch of things and kind of stumped.
Thank you Shiva,
likwidchz said:
Right then what? I'm missing something here.
Click to expand...
Click to collapse
Bootloops are definitely a hassle sometimes. On your device your can either play the button game , watching the device closely and holding the the right button combo when the device goes black in hope that the device will boot into recovery or fastboot when it starts the bootloop again. The easiest thing for me to do sometimes is wait for the battery to drain completely dead then plug the device into the computer while holding the button combination to enter fastboot or recovery. The crappy part is waiting for the battery to drain. I did do a google and learned that Giza uses vol down button and pwr button to enter recovery. But with a dead battery it's likely one will only need to hold vol down button while plugging in the device. If it's in a bootloop it's probably not necessary to hold power button as well, just need to hold the vol down button at the time. I will say with a fair amount of confidence that the device is not a loss cause. Good luck, hope you get it working.
jonpjingleheimler said:
Bootloops are definitely a hassle sometimes. On your device your can either play the button game , watching the device closely and holding the the right button combo when the device goes black in hope that the device will boot into recovery or fastboot when it starts the bootloop again. The easiest thing for me to do sometimes is wait for the battery to drain completely dead then plug the device into the computer while holding the button combination to enter fastboot or recovery. The crappy part is waiting for the battery to drain. I did do a google and learned that Giza uses vol down button and pwr button to enter recovery. But with a dead battery it's likely one will only need to hold vol down button while plugging in the device. If it's in a bootloop it's probably not necessary to hold power button as well, just need to hold the vol down button at the time. I will say with a fair amount of confidence that the device is not a loss cause. Good luck, hope you get it working.
Click to expand...
Click to collapse
I had a weird assumption that I had to wait for the battery to drain. Its just weird this thing happened when it was working just fine.. usually I know when I screw something up pretty good.
I'm more curious on what command I need to be running and constantly retry to load up TWRP via fastboot.
Thanks!
likwidchz said:
I had a weird assumption that I had to wait for the battery to drain. Its just weird this thing happened when it was working just fine.. usually I know when I screw something up pretty good.
I'm more curious on what command I need to be running and constantly retry to load up TWRP via fastboot.
Thanks!
Click to expand...
Click to collapse
From what you have described issuing any command from a computer to the device wouldn't be possible as the device is bootlooping. I could not find any info on button combination to enter fastboot only recovery. from recovery there is a reboot to bootloader or fastboot option. that is your best bet. I have messed with at least a few different kindles in my time but there is always someone out there that has done more and may have another option they can add.
likwidchz said:
Hello apologies,
I'll try and be as verbose as possible this time
This executes
[email protected]:/usr/src/giza# ./boot-fastboot.sh
[2023-02-08 12:26:26.386801] Waiting for preloader
[2023-02-08 12:26:50.335150] Found port = /dev/ttyACM0
[2023-02-08 12:26:50.365886] Handshake
[2023-02-08 12:26:50.386040] Preloader ready, sending FACTFACT
*Holding the left volume button + power button for some time.
[email protected]:/usr/src/giza# fastboot flash recovery bin/recovery.img
< waiting for any device >
Ive had this execute once, but when it does it looks like it wiped out TWRP as I cant get the small text to appear on the bottom left hand corner of the tablet while it does a boot holding power and the volume button.
So I'm not quite sure what I can do now.
Is there a method to flash TWRP with fastboot? or is that what the recovery is?
Could you provide a detailed list of items to try out and some high level instructions.
I've been thumbing through https://forum.xda-developers.com/t/unlock-root-twrp-unbrick-fire-hd-8-2016-giza.4303443/ this guide, but realize I'm not sure which step I need to start from, so I have bene trying a bunch of things and kind of stumped.
Thank you Shiva,
Click to expand...
Click to collapse
Message me on telegram brother @HeyShiva
Shiva Kumar A said:
Message me on telegram brother @HeyShiva
Click to expand...
Click to collapse
Whats wrong with this forum?
likwidchz said:
Whats wrong with this forum?
Click to expand...
Click to collapse
Nothing, I can guide you there flawlessly. If you concerned about privacy no problem.
Shiva Kumar A said:
Nothing, I can guide you there flawlessly. If you concerned about privacy no problem.
Click to expand...
Click to collapse
I don't think you are the best person to guide on this one. You don't even seem to know what an Amazon tablet is, considering you suggested to fastboot boot when that cmd was patched back then in 2015.
@likwidchz If you're able to access fastboot thru boot-fastboot, erase preloader with fastboot erase boot0, reboot and run bootrom-step.sh again.
Rortiz2 said:
I don't think you are the best person to guide on this one. You don't even seem to know what an Amazon tablet is, considering you suggested to fastboot boot when that cmd was patched back then in 2015.
@likwidchz If you're able to access fastboot thru boot-fastboot, erase preloader with fastboot erase boot0, reboot and run bootrom-step.sh again.
Click to expand...
Click to collapse
Yes I don't know about this tablet, I thought it was just like any other tablets sorry
Rortiz2 said:
I don't think you are the best person to guide on this one. You don't even seem to know what an Amazon tablet is, considering you suggested to fastboot boot when that cmd was patched back then in 2015.
@likwidchz If you're able to access fastboot thru boot-fastboot, erase preloader with fastboot erase boot0, reboot and run bootrom-step.sh again.
Click to expand...
Click to collapse
Would you happen to be on IRC or some discord group?
I have done about ~7 of these tablets Suez/Giza but when something goes south, its not clear to me which step I need to start back from. Having a side conversation might help. In the end of the tablet is done, I am not going to be too broken up about it. But it's not a lost cause yet.
Thank you for the assistance! Much love.
--Take care.
likwidchz said:
Would you happen to be on IRC or some discord group?
I have done about ~7 of these tablets Suez/Giza but when something goes south, its not clear to me which step I need to start back from. Having a side conversation might help. In the end of the tablet is done, I am not going to be too broken up about it. But it's not a lost cause yet.
Thank you for the assistance! Much love.
--Take care.
Click to expand...
Click to collapse
I don't use IRC, but I do have Discord (R0rt1z2#3415).
Hello, So I've recently tried flashing a specific custom ROM for my Poco x3 pro, but when I flashed it on twrp it said Failed To Mount Vendor, Failed To Mount Root and something else but I don't really remember, I watched a youtube tutorial to fix but when I booted into system it just showed the boot logo animation, it only goes off when it's out of charge, my volume buttons are broken too, I've went to several stores but they said they can't fix it, the thing is that when I connect my phone to the PC, it detects it in adb, but I'm unable to do anything because it's "unauthorized" should I just give up on the phone?
Jerjfo said:
Hello, So I've recently tried flashing a specific custom ROM for my Poco x3 pro, but when I flashed it on twrp it said Failed To Mount Vendor, Failed To Mount Root and something else but I don't really remember, I watched a youtube tutorial to fix but when I booted into system it just showed the boot logo animation, it only goes off when it's out of charge, my volume buttons are broken too, I've went to several stores but they said they can't fix it, the thing is that when I connect my phone to the PC, it detects it in adb, but I'm unable to do anything because it's "unauthorized" should I just give up on the phone?
Click to expand...
Click to collapse
What happens if you run "adb reboot recovery"?
DarthJabba9 said:
What happens if you run "adb reboot recovery"?
Click to expand...
Click to collapse
It says "error: device unauthorized. Please Check The confirmation dialog on your device." Even though im stuck on the logo
Jerjfo said:
It says "error: device unauthorized. Please Check The confirmation dialog on your device." Even though im stuck on the logo
Click to expand...
Click to collapse
Tried an older adb version and it now says "This adb server's $ADB_VENDOR_KEYS is not set Try 'adb kill-server' if that seems wrong. Otherwise check for a confirmation dialog on your device.
Jerjfo said:
It says "error: device unauthorized. Please Check The confirmation dialog on your device." Even though im stuck on the logo
Click to expand...
Click to collapse
Unfortunately, if you can't use adb commands and your volume buttons are not functional, then you are out of options. Your priority should be to get the volume buttons fixed. If it is not possible to get them fixed, then you are stuck.
What about earphone volume buttons? That works.
DarthJabba9 said:
Unfortunately, if you can't use adb commands and your volume buttons are not functional, then you are out of options. Your priority should be to get the volume buttons fixed. If it is not possible to get them fixed, then you are stuck
Click to expand...
Click to collapse
Did you unlock the bootloader first? Sorry if this seems like a dumb question but you didn't indicate that you did.
@immortalwon exactly that was what i thought at the first reading this threat yesterday...
immortalwon said:
Did you unlock the bootloader first? Sorry if this seems like a dumb question but you didn't indicate that you did.
Click to expand...
Click to collapse
Yes, my bootloader is unlocked with twrp on it, I flashed the wrong rom for my phone [Oxygen OS Port] And it got stuck on logo
Jerjfo said:
Yes, my bootloader is unlocked with twrp on it, I flashed the wrong rom for my phone [Oxygen OS Port] And it got stuck on logo
Click to expand...
Click to collapse
I know exactly what happened. Because you flashed the wrong rom, it replaced also your custom recovery so now you are full bricked. I am not sure if there is official unbrick tools from Xiaomi, but you prob need to find someone who can do remote flash repairs.
I would try this before anything: Hold all volume buttons and power button until screen turns off. If it does turn off, hold volume down and power button and try to get into fastboot menu.
This link may also help: https://new.c.mi.com/global/miuidownload/detail/guide/1
immortalwon said:
I know exactly what happened. Because you flashed the wrong rom, it replaced also your custom recovery so now you are full bricked. I am not sure if there is official unbrick tools from Xiaomi, but you prob need to find someone who can do remote flash repairs.
I would try this before anything: Hold all volume buttons and power button until screen turns off. If it does turn off, hold volume down and power button and try to get into fastboot menu.
This link may also help: https://new.c.mi.com/global/miuidownload/detail/guide/1
Click to expand...
Click to collapse
The thing is that my volume buttons are broken, I might fix them but I think fastboot got erased along with the recovery (not sure)
Jerjfo said:
The thing is that my volume buttons are broken, I might fix them but I think fastboot got erased along with the recovery (not sure)
Click to expand...
Click to collapse
Why would you even bother to flash stuff with broken volume buttons? That's asking for big trouble, which occurred to you. I would suggest fixing or getting a new phone
Jerjfo said:
fastboot got erased along with the recovery (not sure)
Click to expand...
Click to collapse
Fastboot can't get erased.
No worries there.