I was attempting to unlock my bootloader and managed to fat finger one of the critical pieces. When typing fastboot -i 0x1949 erase aboot, I typed in fastboot -i 0x1949 erase boot. Which erased by boot partition. Now my device dutifully sits at the grey Kindle Fire logo, but never boots. I haven't otherwise done anything to this device, and it was running on a fresh installation of 4.5.5.3.
I can still access fastboot via a fastboot cable. I attempted to fix the issue by loading the boot partition with the boot.img found in the latest Amazon update files, but it didn't seem to have any effect.
I also attempted to boot into bulk mode, but issuing the command to erase the aboot partition returns a message that there is no aboot partition?
Is this a recoverable situation?
leeharrison1984 said:
I was attempting to unlock my bootloader and managed to fat finger one of the critical pieces. When typing fastboot -i 0x1949 erase aboot, I typed in fastboot -i 0x1949 erase boot. Which erased by boot partition. Now my device dutifully sits at the grey Kindle Fire logo, but never boots. I haven't otherwise done anything to this device, and it was running on a fresh installation of 4.5.5.3.
I can still access fastboot via a fastboot cable. I attempted to fix the issue by loading the boot partition with the boot.img found in the latest Amazon update files, but it didn't seem to have any effect.
I also attempted to boot into bulk mode, but issuing the command to erase the aboot partition returns a message that there is no aboot partition?
Is this a recoverable situation?
Click to expand...
Click to collapse
@draxie - thoughts?
I managed to get back in to TWRP by manually installing it via fastboot.
dl.twrp.me/soho/
However, my real problem was I was using my Soho KF, not a Thor/Apollo variant.
I managed to get things sorted and unbricked the Soho, thanks for showing up though!
Related
So I relocked my bootloader after upgrading to marshmallow and forgot that I did that..... I tried to flash a stock boot img so I could utilize the ota, and it sort of bricked my tablet. Being a total dumbass I didn't realize that was the problem. Having had a similar issue before on my galaxy s4 where I follow a similar solution. I already have twrp installed, and it was asking for encryption for which there was none. So I wiped data and formatted to get past the encryption. On my s4 I was then able to reinstall the stock firmware and software. However when I tried to push the bootloader to my nexus I got this weird error.. can someone pleeeeeeease spare me and help me out. This tablet is my lifeline for college...
Don't get me in trouble for posting this image please lol, I just don't have enough posts. http ://i67.tinypic.com/v80vwl.jpg[/B][/B]
I figured it out, I was just being dumb. I just needed to use the fastboot commands and not try to use twrp
tdct12 said:
So I relocked my bootloader after upgrading to marshmallow and forgot that I did that..... I tried to flash a stock boot img so I could utilize the ota, and it sort of bricked my tablet. Being a total dumbass I didn't realize that was the problem. Having had a similar issue before on my galaxy s4 where I follow a similar solution. I already have twrp installed, and it was asking for encryption for which there was none. So I wiped data and formatted to get past the encryption. On my s4 I was then able to reinstall the stock firmware and software. However when I tried to push the bootloader to my nexus I got this weird error.. can someone pleeeeeeease spare me and help me out. This tablet is my lifeline for college...
Don't get me in trouble for posting this image please lol, I just don't have enough posts. http ://i67.tinypic.com/v80vwl.jpg[/B][/B]
I figured it out, I was just being dumb. I just needed to use the fastboot commands and not try to use twrp
Click to expand...
Click to collapse
If your able to access the bootloader menu or the fastboot menu, you could flash the stock and would fix the brick,soft brick or boot-loop.
Head to Google developer nexus image. Download the factory image of your devices on your devices. Extract all the files and copy paste the fastboot and adb files. Head to your devices and open the fastboot menu.
Type the following commends to restore your devices if the flashall did not work.
Fastboot oem unlock
Fastboot flash bootloader bootloader....
Fastboot reboot-bootloader
Fastboot erase boot
Fastboot flash boot boot.img
Fastboot erase recovery
Fastboot flash recovery recovery.img
Fastboot erase system
Fastboot flash system system.img (this could take up to 15 minutes, don't do anything to stop the process you can make your devices and a worst state)
Fastboot erase cache
Fastboot flash cache cache.img
Fastboot erase vendor
Fastboot flash vendor vendor.img
Fastboot reboot
This should fix your devices. I did not and it save each time I broke my device or anything similar.
If you want after all that. You can enter the following commends to relock your devices but don't make the same mistake you did before. If you want to avoid that same mistake just don't enter the commends.
What the guy above me said, also pro tip, some times not all the files will extract just keep extracting till all the image files are there.
I have flashed whole firmware in fastboot mode with the help of fastboot tool. First i flash preloader. i use this command "fastboot flash preloader preloader.img" after this i flashed boot, recovery and other factory images. but when i m going to flash pgpt.img or gpt.img commad ended up with "PGPT : No partition table found" after this wiped user data and relock the bootloader with this command "fastboot oem lock". when i enter fastboot reboot and hit enter. It ain't gonna boot no recovery & no fastboot. only charging lead blinks and nothing more.
i never flash pgpt.img like this "fastboot flash partition pgpt.img.
I have flashed whole firmware in fastboot mode with the help of fastboot tool. First i flash preloader. i use this command "fastboot flash preloader preloader.img" after this i flashed boot, recovery and other factory images. but when i m going to flash pgpt.img or gpt.img commad ended up with "PGPT : No partition table found" after this wiped user data and relock the bootloader with this command "fastboot oem lock". when i enter fastboot reboot and hit enter. It ain't gonna boot no recovery & no fastboot. only charging lead blinks and nothing more.
i never flash pgpt.img like this "fastboot flash partition pgpt.img.
Hello,
i have a TF303k Asus tablet.
It worked fine (rooted with Kingo) until i ran Magisk.
Since then, the tablet only boots into fastboot mode, when i switch it on.
However, when i do a:
Code:
fastbooot boot boot.img
with the boot.img of the firmware.zip, the tablet starts and i can use it.
Trying to make booting permanent does not seem to work:
Doint a
Code:
fastboot flash boot boot.img
ends with success, but the tablet again goes to fastboot mode.
There are some additional images in the firmware: bootloader.[aboot, rpm, bl2, sbl3,tz].img but none of these is bootable.
I'm not able to boot into recovery, i always end up in fastboot mode.
Any tips or does anyone have a recovery.img ?
Thanks, Je\/eR
Hello,
I just received this weird phone I never heard or seen before and I need to root it. I'm afraid to start doing anything because I don't know if I will be able to flash back stock image (let alone find it) if anything goes south. Has anyone successfully tinkered their phone?
Yes. Managed to unlock and root mine yesterday, but with some caveats.
Some of the commands are different.
fastboot oem nubia_unlock NUBIA_NX619J
Is the command to start the bootloader unlock in Fastboot mode.
Then you can do
fastboot flashing unlock
To fully unlock the bootloader.
It appears you have to do the fastboot flashing unlock part each time in fastboot mode.
I flashed the boot.img modified with Magisk, had to reboot into fastboot again and redo flashing unlock before I could boot with my modified boot image. Everything since worked as expected.
One benefit to the Red Magic Mars is that it has an actual recovery partition and does not use the A/B slot partitioning system that so complicates other devices. So as long as you leave the recovery partition alone, you will be able to restore to stock using a USB C thumbdrive with the image file on it.