Related
Hey there,
Tldr bottom
While trying to apply unlock bootloader, root, and custom rom my phone, I encountered a few problems. I bought this phone in china and this gave me so many headaches. Firstoff no gapps so that's why I'm doing all this, but twrp and firmware is a pain in the ass. I unlocked the bootloader and installed twrp. But I couldn't get my phone to boot into twrp, it would only go to erecovery.
I have tried installing twrp and not booting but going straight to twrp, as to avoid the overwrite. It did not work. I tried many many flashes with different twrp, none worked. Not even the Chinese ones. So I figured it might be because I'm running emui 5 on Nougat.
I tried to downgrade, which was a hassle. Dload did not work and finnaly I found that the pc huawei suite had downgrade avaliable. So I tried that but got stuck at the screen in the attachment. I encountered this before so I went to fastboot and flashed twrp and booted up.
Still cant boot into twrp, only erecovery. I Thought I had downgraded, but when booting up I saw it was the old UI and in the 'about phone' it still said emui 5, android 7. So I did it all again. But this time I first locked my bootloader. So I locked my bootloader and tried to downgrade... This time it booted up without problems but it was still emui5 android 7. Odd.
So unlocked my bootloader again and now I'm stuck at this screen. It won't let me boot recovery or fastboot. It does not even respond to vol up+vol down + power. Force update. Nothing works. It boots to this screen everytime.
imgur.com/gallery/gOJ9E
Tldr: unlocked bootloader for second time after failed downgrade. Now its bricked.
Rommco05 said:
You be able enter to fastboot? Turn off phone, plug phone to pc/usb and turn on with holding vol-
Click to expand...
Click to collapse
Nope, I can't enter Fastboot, nor recovery, nor force a dload update. I get the 'honor' welcome screen followed by the screenshot in my main post.
(Your device has been unlocked and can't be trusted.
To learn more, visit: ....................
Your device is rebooting now)
Thanks for replying, hope you can still help me.
iloos said:
Nope, I can't enter Fastboot, nor recovery, nor force a dload update. I get the 'honor' welcome screen followed by the screenshot in my main post.
(Your device has been unlocked and can't be trusted.
To learn more, visit: ....................
Your device is rebooting now)
Thanks for replying, hope you can still help me.
Click to expand...
Click to collapse
It takes sometime to enter fastboot mode when your phone is powered off. Try again.
Switch off the phone
Press volume down button
While pressing it plug your phone
Keep the volume down button pressed.
It takes around 10-15 seconds to show up. Sometimes it takes even more time but eventually you'll be able to enter
iloos said:
Nope, I can't enter Fastboot, nor recovery, nor force a dload update. I get the 'honor' welcome screen followed by the screenshot in my main post.
(Your device has been unlocked and can't be trusted.
To learn more, visit: ....................
Your device is rebooting now)
Thanks for replying, hope you can still help me.
Click to expand...
Click to collapse
Can you boot to erecovery?
suhel28 said:
It takes sometime to enter fastboot mode when your phone is powered off. Try again.
Switch off the phone
Press volume down button
While pressing it plug your phone
Keep the volume down button pressed.
It takes around 10-15 seconds to show up. Sometimes it takes even more time but eventually you'll be able to enter
Click to expand...
Click to collapse
I will keep trying but I have already done this many times without success.
adriansticoid said:
Can you boot to erecovery?
Click to expand...
Click to collapse
Nope
iloos said:
Nope
Click to expand...
Click to collapse
Just to clarify, I was pertaining to the Erecovery, not TWRP recovery. You can't boot to that?
adriansticoid said:
Just to clarify, I was pertaining to the Erecovery, not TWRP recovery. You can't boot to that?
Click to expand...
Click to collapse
Indeed, I can noy boot to erecovery. I can also not boot to fastboot. I only ger the honor loadong screen and then the screenshot from above.
iloos said:
Indeed, I can noy boot to erecovery. I can also not boot to fastboot. I only ger the honor loadong screen and then the screenshot from above.
Click to expand...
Click to collapse
How about HiSuite? You tried that?
Sent from my Honor 8 using XDA Labs
Yeah man, it won't work. Sorry for the late reply.
adriansticoid said:
How about HiSuite? You tried that?
Sent from my Honor 8 using XDA Labs
Click to expand...
Click to collapse
iloos said:
Yeah man, it won't work. Sorry for the late reply.
Click to expand...
Click to collapse
Have you fixed it now?
Sent from my Honor 8 using XDA Labs
adriansticoid said:
Have you fixed it now?
Sent from my Honor 8 using XDA Labs
Click to expand...
Click to collapse
Nope, Still stuck at the screenshot in the first post. whatever I do. Plugged in, not plugged in. Holding up, down, or up and down. Tried everything. (I think)
iloos said:
Nope, Still stuck at the screenshot in the first post. whatever I do. Plugged in, not plugged in. Holding up, down, or up and down. Tried everything. (I think)
Click to expand...
Click to collapse
How about the service center?
Sent from my Honor 8 using XDA Labs
Take it to customer service
PalakMi said:
Take it to customer service
Click to expand...
Click to collapse
adriansticoid said:
How about the service center?
Click to expand...
Click to collapse
Yeah I guess that'll be my last option. Maybe the only one.
iloos said:
Yeah I guess that'll be my last option. Maybe the only one.
Click to expand...
Click to collapse
Let's hope for the best
iloos said:
Yeah I guess that'll be my last option. Maybe the only one.
Click to expand...
Click to collapse
Let us know what happens.
Sent from my Honor 8 using XDA Labs
Make sure you post about the results after
can anyone help me. my phone wont boot, itried to go from emui 8 india to emui 8 china. but when it asked for bootloader unlock code, i entered and it said password wrong. so i manually tried to unlock bootloader. it ewas succesful but now phonw wont boot. it stuck in phone is now booting screen. cant enter fastboot, recovery or dload. i tried to change location in hwota 8. someone please help me.
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.
I've spent hours searching and cannot find a definite answer to my question. I see others have asked HOW to fix this issue, I just want to know if it is possible.
Is it possible to factory reset my device or not?
Bootloader is NOT UNLOCKED, and I am stuck on bootloader screen.
"Bootlinux Failed: Not started" when trying recovery mode.
"Slot Unbootable: Load Error" when trying to start.
My device is obviously not found under adb devices as it is locked, but does show up in fastboot devices.
My computer does recognize the android device as well.
Is it possible to factory reset my device or not?
Is there any way to flash a custom ROM and get it operational?
I'd say you're out of luck, I've had the slot unbootable error/ authload error and both usually require re flashing the bootloader, radio, boot.img or a full factory image restore via flash-all to restore via an unlocked BL. I haven't seen any other methods available for the walleye with a locked bootloader I can offer either.
junglism93 said:
I'd say you're out of luck, I've had the slot unbootable error/ authload error and both usually require re flashing the bootloader, radio, boot.img or a full factory image restore via flash-all to restore via an unlocked BL. I haven't seen any other methods available for the walleye with a locked bootloader I can offer either.
Click to expand...
Click to collapse
Thanks for your reply,
Surely Google or some super nerd would know how? But I think I am also out of luck.
Thanks though.
Hi! I don't know if could helps, but did you try to sideload full OTA through recovery mode? This should be go with locked BL too, but I am not sure if you have to have enable usb debuging...
somin.n said:
Hi! I don't know if could helps, but did you try to sideload full OTA through recovery mode? This should be go with locked BL too, but I am not sure if you have to have enable usb debuging...
Click to expand...
Click to collapse
Hey Somin,
I haven't fully looked into that option yet, started to give up. But I can't access recovery mode or even get out of bootloader, and usb debugging is not enabled, oem is locked.
If you have any further information or ideas I would be really keen to hear.
Thanks,
Alex
OilyBigMac said:
Hey Somin,
I haven't fully looked into that option yet, started to give up. But I can't access recovery mode or even get out of bootloader, and usb debugging is not enabled, oem is locked.
If you have any further information or ideas I would be really keen to hear.
Thanks,
Alex
Click to expand...
Click to collapse
Did you tried to get to recovery from bootloader screen or with key combination too?
somin.n said:
Hi! I don't know if could helps, but did you try to sideload full OTA through recovery mode? This should be go with locked BL too, but I am not sure if you have to have enable usb debuging...
Click to expand...
Click to collapse
Hey Somin,
I haven't fully looked into that option yet, started to give up. But I can't access recovery mode or even get out of bootloader, and usb debugging is not enabled, oem is locked.
If you have any further information or ideas I would be really keen to hear.
Thanks,
Alex
somin.n said:
Did you tried to get to recovery from bootloader screen or with key combination too?
Click to expand...
Click to collapse
I do appreciate your help, but as I just mentioned, I am stuck in bootloader screen and get errors when trying to access recovery, download, start or any other option. Obviously using the hard reset only brings me to bootloader where I am stuck.
Is this what you're referring to with key combination?
OilyBigMac said:
Is this what you're referring to with key combination?
Click to expand...
Click to collapse
Hi! No Shut down your phone and try "the game" with power button and vol+ btn... I didn't find any tutorial and it is slightly lottery, but you could get directly to recovery mode if you will press this btns in correct way:
- try to hold them for long time
- try to hold power btn and quick pushing vol+
If you will get to "no command" screen, press again pwr+vol up and you should be in recovery mode. Good luck
somin.n said:
Hi! No Shut down your phone and try "the game" with power button and vol+ btn... I didn't find any tutorial and it is slightly lottery, but you could get directly to recovery mode if you will press this btns in correct way:
- try to hold them for long time
- try to hold power btn and quick pushing vol+
If you will get to "no command" screen, press again pwr+vol up and you should be in recovery mode. Good luck
Click to expand...
Click to collapse
Interesting, I get the same error message as I do when I try to enter Download Mode. So this is different than the power and volume down, and different than just restarting it.
So far I just keep getting back to bootloader screen saying operation denied. But might keep trying it here and there haha.
Thanks for your help.
I had the same problem. I was able to solve it by selecting the download mode in the bootloader. There was an error message. Then I fastboot flashing unlock on the console. Then the bootloader is unlocked. No idea why this worked.
Maybe this will help someone who encountered the same problem.
Hello There,
Recently, I had brought an OnePlus Nord 2T, Indian Variant specifically. I was trying to root the device by installing TWRP but the TWRP wasn't having any access to the storage because I had wiped the Internal Storage in TWRP before I could do that, which didn't give me any access to the storage of the device. Even if I connected my PC.... Or Disabling/Re-Enabling MTP.
Long story short, I eventually gave up and decided to try again sometime later and proceeded to lock the bootloader. But after relocking the BL the phone would boot and show the error
"The current image(boot/recovery) have been destroyed". I have tried everything to get it to boot into Fastboot but it just won't boot into it.
Pressing Volume Down + Volume Up + Power Button will only display the same error with a small "Recovery Mode" at the bottom left of the screen! I could have tried booting from Recovery but it just doesn't works cause I think that there is no stock recovery because the phone hadn't booted to the OOS yet. Any help as to how can i get it to boot into fastboot mode???? Please!!!!!!!!
Please anybody respond!
The current image(boot/recovery) have been destroyed!
I recently tried to unroot my Oneplus Nord 2T and after locking the bootloader the phone entered this state. There is no connection between my phone and pc. Pressing Volume Down+Power Button brings back to same page. Urgent need help. Edit: The...
forum.xda-developers.com
PattasuBalu said:
The current image(boot/recovery) have been destroyed!
I recently tried to unroot my Oneplus Nord 2T and after locking the bootloader the phone entered this state. There is no connection between my phone and pc. Pressing Volume Down+Power Button brings back to same page. Urgent need help. Edit: The...
forum.xda-developers.com
Click to expand...
Click to collapse
There is no MSM tool for the device! I don't know how can I fix it
ArmashOnXDA said:
There is no MSM tool for the device! I don't know how can I fix it
Click to expand...
Click to collapse
There is no fix currently for this problem. The only way to fix it now is to give it to a oneplus repair shop.
PattasuBalu said:
There is no fix currently for this problem. The only way to fix it now is to give it to a oneplus repair shop.
Click to expand...
Click to collapse
Ahhhhhhhhh- That sucks. OnePlus isn't the same as it once used to be. Is OnePlus ever even gonna release the blessed keys to the public to help thelucky one's who managed to brick their device?
ArmashOnXDA said:
Hello There,
Recently, I had brought an OnePlus Nord 2T, Indian Variant specifically. I was trying to root the device by installing TWRP but the TWRP wasn't having any access to the storage because I had wiped the Internal Storage in TWRP before I could do that, which didn't give me any access to the storage of the device. Even if I connected my PC.... Or Disabling/Re-Enabling MTP.
Long story short, I eventually gave up and decided to try again sometime later and proceeded to lock the bootloader. But after relocking the BL the phone would boot and show the error
"The current image(boot/recovery) have been destroyed". I have tried everything to get it to boot into Fastboot but it just won't boot into it.
Pressing Volume Down + Volume Up + Power Button will only display the same error with a small "Recovery Mode" at the bottom left of the screen! I could have tried booting from Recovery but it just doesn't works cause I think that there is no stock recovery because the phone hadn't booted to the OOS yet. Any help as to how can i get it to boot into fastboot mode???? Please!!!!!!!!
Click to expand...
Click to collapse
What you need to do if you have a data Cable is connect to the computer that way you can install adv and boot into fastboot
791853 said:
What you need to do if you have a data Cable is connect to the computer that way you can install adv and boot into fastboot
Click to expand...
Click to collapse
Could you explain it more in detail? Like giving me the exact instructions as to what i have to do.
Also, What do you mean by "adv"?
791853 said:
What you need to do if you have a data Cable is connect to the computer that way you can install adv and boot into fastboot
Click to expand...
Click to collapse
This will not work if you have a bad boot partition. There was a way to flash boot.img via brom mode but it is patched now. So only now is to give it to Oneplus service center.
PattasuBalu said:
This will not work if you have a bad boot partition. There was a way to flash boot.img via brom mode but it is patched now. So only now is to give it to Oneplus service center.
Click to expand...
Click to collapse
How long does the service center take to fix the device? Hours? Days? Months?
It usually takes 1-2 days. If you are lucky you get it fixed on the spot.
I had the same issue. Got a new device from my provider in exchange.
Maybe brom mode could work in your case.
Your build has to be A.14 or lower as A.15 received the patch.
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).