I've seen that this is possible on several phones but it seems that the way of doing it is not very consistent.
So I was wondering if this is possible for the Note 3 and if so how. Also if there is the risk of hard bricking the device by trying this.
I read several times that you could flash boot logos with the fastboot command
Code:
fastboot flash splash splash1.img
or
Code:
fastboot flash logo logo.img
, though I can't even access the bootloader as it seems.
Doing
Code:
adb reboot-bootloader
Paulske said:
I've seen that this is possible on several phones but it seems that the way of doing it is not very consistent.
So I was wondering if this is possible for the Note 3 and if so how. Also if there is the risk of hard bricking the device by trying this.
I read several times that you could flash boot logos with the fastboot command
Code:
fastboot flash splash splash1.img
or
Code:
fastboot flash logo logo.img
, though I can't even access the bootloader as it seems.
Doing
Code:
adb reboot-bootloader
Click to expand...
Click to collapse
Yes, the boot splash is in the bootloader and yes, there's a definite and high risk of a hard brick trying to do this. The Samdung bootloader isn't the most friendly when it comes to modification.
I see. Thanks for the heads up, I guess its not worth the risk in that case.
I wonder if anyone managed to do this successfully over the years. Happy the Note 3 is still capable of running one of the latest ROMs.
Related
ok, so i wanted to try Cyanogenmod 7.
i followed the steps:
1- rooted the device
2- downgraded to Froyo firmware
3- installed Cyanogenmod 7.20.
all worked fine for almost one week until i updated rom manager from the market.
since the the device led flickers in green and orange. I can get into clockworkmod recovery menu but it lasts for a few seconds and disappears. it appears again and so on.
adb devices returns:
List of devices attached
SH0BHRT09137 recovery
but because it's not stable the same command doesn't return any devices few seconds later.
what shall i do now ?
steps one and two i assume are switched around, try booting into fastboot
if your hboot is still stable you may have more luck here
fastboot works in similar ways as adb - so fastboot devices
if you see yours
then wipe and flash a new recovery via fastboot
fastboot -w
fastboot flash recovery recovery.img
fastboot reboot
(replace recovery.img with whatever name you give that recovery image)
demkantor said:
steps one and two i assume are switched around, try booting into fastboot
if your hboot is still stable you may have more luck here
fastboot works in similar ways as adb - so fastboot devices
if you see yours
then wipe and flash a new recovery via fastboot
fastboot -w
fastboot flash recovery recovery.img
fastboot reboot
(replace recovery.img with whatever name you give that recovery image)
Click to expand...
Click to collapse
Thanks for the info. after i installed fastboot and ran "fastboot devices" i don't get any devices.
are you in fastboot mode within hboot? does your phone say fastboot usb?
write down everything on your phone when you boot into bootloader
demkantor said:
are you in fastboot mode within hboot? does your phone say fastboot usb?
write down everything on your phone when you boot into bootloader
Click to expand...
Click to collapse
strange enough "adb reboot" go the device working ! not sure why it was stuck at ClockMod.
hope this thread help somebody later.
so i tried flashing the 4.3 stock image i downloaded from the google website for the grouper. i had already bricked this tablet before by accidentally unplugging it while it was flashing the boot loader. I just paid 30 dollars and received a new motherboard from eBay last week, and started playing with my nexus 7 again. This time, I made sure to not touch the boot loader as I noticed that the bootlaoder on my grouper and the one in the image archive were both 4.23. So first I issued the commands
Code:
fastboot oem unlock
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
i went ahead by issuing the command
Code:
fastboot -w update image-nakasi-jwr66y.zip
it started flashing, but my annoying brother came in and closed the screen of my macbook. When I opened it again, the fast boot mode was still showing on my nexus, but the flashing on terminal had stopped. i quit terminal and opened it again. i typed:
Code:
fastboot devices
and my tablet showed up as normal. However, when I tried to issue any command, terminal would just display a blank space. I then selected reboot boot loader on my nexus, but the device just turned into a black screen, exactly the way it appeared last time i bricked it. I'm so frustrated and confused. Why is the device refusing to go into the boot loader using power-volume down if I didn't even touch the boot loader? At the most my device should only be soft bricked. I checked the contents of image-nakasi-jwr66y.zip and the contents were
Code:
android-info.txt
boot.img
recovery.img
system.img
userdata.img
I don't think these have anything to do with the boot loader?
the flash log didn't show any evidence of touching the bootloader except the check part where it checked the boot loader version, which was reported as 4.23.
If someone could provide me with assistance it would be greatly appreciated!
Hi friends,zenfone 3 bootloder opened the lock.Now I want to close .Relock bootloader.
Ive tried asking this before for my Ze520kl, someone said it isn't possible to relock the bootloader
I would like to know if someone has an update about that...
When I tried to root my phone (ZE552KL Androïd 7.0) I installed an app to unlock the bootloader of my phone (ZE552KL_SIGNED_Android_M_UnlockTool_2016_0715). I used it and ever since, when I turn on my device, I get a warning screen saying "Your device software cannot be checked for corruption. Please lock the bootloader." It sends me to this link for information. The notification disappear after 10 seconds and androïd starts.
I was quite stupid to do that because I do not have to knowledge to properly root my device. So I give up, but I would like to get back my device without that security warning.
I have already flashed it from the recovery menu, with an sd card, wiping data and cache. But it didn't work.
Any advice?
my69 said:
Hi friends,zenfone 3 bootloder opened the lock.Now I want to close .Relock bootloader.
Click to expand...
Click to collapse
I found this on the bootloader source:
Code:
fastboot oem unlock
fastboot oem unlock-go
fastboot oem lock
fastboot flashing unlock
fastboot flashing lock
fastboot flashing lock_critical
fastboot flashing unlock_critical
fastboot flashing get_unlock_ability
but they're all untested, trying them would make you take the risk of
killing your phone
OR
locking the bootloader
keep in mind that Asus also keeps track of system mounts as read write changes, so if you're trying to fool them, locking the bootloader won't be enough
Commands do not work.
gkillershots said:
I found this on the bootloader source:
Code:
fastboot oem unlock
fastboot oem unlock-go
fastboot oem lock
fastboot flashing unlock
fastboot flashing lock
fastboot flashing lock_critical
fastboot flashing unlock_critical
fastboot flashing get_unlock_ability
but they're all untested, trying them would make you take the risk of
killing your phone
OR
locking the bootloader
keep in mind that Asus also keeps track of system mounts as read write changes, so if you're trying to fool them, locking the bootloader won't be enough
Click to expand...
Click to collapse
Commands do not work.
myheartloves said:
Commands do not work.
Click to expand...
Click to collapse
well, I think Asus disabled thoose ones
sorry
I wanted to make this post about my adventure with my old Pixel 2. I was getting non-stop red lines out of the log in TWRP. Many times I would have problems mounting system and vendor partitions as well as vendor partitions needing "to be cleaned".
This led me to believe that I may have a corrupted partition, so I did some research into how the partitions are organized, and what happens when you flash a lot of ROMs. Perhaps you want to go back to the stock firmware? Perhaps - like in my case - you want to install a ROM such as GrapheneOS that's meant to lock the bootloader afterwards, and act more like the stock ROM.
What I didn't understand up until recently is how exactly the A and B slots of phones like the Pixel 2 work. They work because the firmware allows updating OTA to the opposite slot of what's active. That way - in the worst case scenario - you can actually boot into the opposite slot and regain access to your phone. I'm not an expert on this, but that's my basic understanding.
So now that that's covered, another important aspect is flashing ROMs. If you are like me and like testing many different ROMs, you may end up running into issues such as the one I stated above with TWRP.
The only way I was able to avoid these types of issues is to run some commands through fastboot.
One such command is
Code:
fastboot format system
This command will format the system partition and make it easier to install ROMs without running into issues.
Another command is
Code:
fastboot format vendor
This command was very important in my case, because the vendor partition was actually unusable for my slot A. Doing this command finally fixed that issue.
Another thing to note is ROMs can be installed in both slots. A lot of people don't do this, because they leave their bootloader unlocked and probably just run the ROM for half a day, and flash another. In my case, I needed to flash both slots in order to lock the bootloader in GrapheneOS, and allow the OS to update OTA. If you don't flash both slots, that won't work.
Just to clarify further, these are the commands (at the bootloader) I ran (from a command prompt in Windows) in order from start to finish when I was flashing a ROM I wanted to keep:
Code:
fastboot --set-active=a
fastboot format system
fastboot format vendor
fastboot reboot bootloader
fastboot --set-active=b
fastboot format system
fastboot format vendor
fastboot reboot bootloader
fastboot flash bootloader bootloader.img
fastboot reboot bootloader
fastboot flash radio radio.img
fastboot reboot bootloader
fastboot update rom.zip
// Let the phone reboot into the new ROM, let it sit for a minute,
// then reboot into bootloader manually and then continue with fastboot:
fastboot --set-active=a
fastboot flash bootloader bootloader.img
fastboot reboot bootloader
fastboot flash radio radio.img
fastboot reboot bootloader
fastboot update rom.zip
Once I've done this, and can confirm it successfully loads into the ROM I've installed, I can now say that I have a clean, fresh install in BOTH slots A and B.
I'll update this thread if I can think of anything else that can help newbies like me.
Cheers!
HCFL said:
I wanted to make this post about my adventure with my old Pixel 2. I was getting non-stop red lines out of the log in TWRP. Many times I would have problems mounting system and vendor partitions as well as vendor partitions needing "to be cleaned".
This led me to believe that I may have a corrupted partition, so I did some research into how the partitions are organized, and what happens when you flash a lot of ROMs. Perhaps you want to go back to the stock firmware? Perhaps - like in my case - you want to install a ROM such as GrapheneOS that's meant to lock the bootloader afterwards, and act more like the stock ROM.
What I didn't understand up until recently is how exactly the A and B slots of phones like the Pixel 2 work. They work because the firmware allows updating OTA to the opposite slot of what's active. That way - in the worst case scenario - you can actually boot into the opposite slot and regain access to your phone. I'm not an expert on this, but that's my basic understanding.
So now that that's covered, another important aspect is flashing ROMs. If you are like me and like testing many different ROMs, you may end up running into issues such as the one I stated above with TWRP.
The only way I was able to avoid these types of issues is to run some commands through fastboot.
One such command is
Code:
fastboot format system
This command will format the system partition and make it easier to install ROMs without running into issues.
Another command is
Code:
fastboot format vendor
This command was very important in my case, because the vendor partition was actually unusable for my slot A. Doing this command finally fixed that issue.
Another thing to note is ROMs can be installed in both slots. A lot of people don't do this, because they leave their bootloader unlocked and probably just run the ROM for half a day, and flash another. In my case, I needed to flash both slots in order to lock the bootloader in GrapheneOS, and allow the OS to update OTA. If you don't flash both slots, that won't work.
Just to clarify further, these are the commands (at the bootloader) I ran (from a command prompt in Windows) in order from start to finish when I was flashing a ROM I wanted to keep:
Code:
fastboot --set-active=a
fastboot format system
fastboot format vendor
fastboot reboot bootloader
fastboot --set-active=b
fastboot format system
fastboot format vendor
fastboot reboot bootloader
fastboot flash bootloader bootloader.img
fastboot reboot bootloader
fastboot flash radio radio.img
fastboot reboot bootloader
fastboot update rom.zip
// Let the phone reboot into the new ROM, let it sit for a minute,
// then reboot into bootloader manually and then continue with fastboot:
fastboot --set-active=a
fastboot flash bootloader bootloader.img
fastboot reboot bootloader
fastboot flash radio radio.img
fastboot reboot bootloader
fastboot update rom.zip
Once I've done this, and can confirm it successfully loads into the ROM I've installed, I can now say that I have a clean, fresh install in BOTH slots A and B.
I'll update this thread if I can think of anything else that can help newbies like me.
Cheers!
Click to expand...
Click to collapse
Would this help in bootloop as well? I have a pixel 1st gen that does. I have flashed and or tried to anyways factory images...OTA and even was able to boot twrp and get lineage to flash, only to get a random reboot and bootloop. I would need to flash the factory image in order to get this phone operable. Should I flash a factory image and then do your steps or should I do the steps first and then flash the factory image?
Nope. Did not work. Seems as if the stock recovery is fubar
Hello, I am trying to flash TWRP to my zenfone, I managed to do it once by some miracle with the exact same setup as I have now.
by typing fastboot devices I get K6AXB7616289*** fastboot
but if I try to flash anything with the phone connected I get no output at all.
If I try to flash with the phone disconnected I get <waiting for any device> and no change when I connect it.
In both of these cases when I disconnect the phone I get:
Sending 'recovery' (31332 KB) FAILED (Write to device failed (No such device))
fastboot: error: Command failed
It is overall wonky and seems to change depending on nothing. Sometimes while writing sudo fastboot reboot bootloader I get to the bootloader as expected, but sometimes I get an error but still manage to get to the bootloader and other times it boots up normally.
I am running ParrotOS from a USB
I also posted in here as my problem is very similar but I hope this post resurrects this particular topic: https://forum.xda-developers.com/t/...but-fastboot-devices-is-working-fine.4295449/
What commands are you using?
Fastboot flash boot boot.img?
The boot.img could be the twrp.img renamed to boot. Img but it should be to recovery I believe.
Fastboot flash recovery twrp.img
Yeah im writing fastboot flash recovery and then the path to my twrp.img. I managed to flash it once after a lot of struggle but now I can't do it again.
After posting I saw that I'm using a USB 3 port and my laptop doesn't have a usb 2 one so I think that might be the issue.
Considering I can get three different outputs from the same command in the span of a couple seconds I think that the problem might be hardware related. I can update once I get my hands on a USB 2 port.
Kaynejulian said:
What commands are you using?
Fastboot flash boot boot.img?
The boot.img could be the twrp.img renamed to boot. Img but it should be to recovery I believe.
Fastboot flash recovery twrp.img
Click to expand...
Click to collapse
I have now tried with a USB 2 port and there is no change.
I have had issue when the phones in fastboot and I'm able to flash via his method. Using platform tools I copy all my IMg's into the folder then open a command prompt window in that folder and fastboot reboot bootloader or fastboot reboot fastboot. Which I learned the hardway is fastbootd mode and then and only then did it actually flash. I also learned the hardway that you boot directly from in fastboot mode or it all just cycles back.
Fastboot reboot.
What version zenfone model and what is system is it running?
If your device is running android 10 or newer then is a different process as you'll need to flash the super.img rather than individual imgs like system vendor product ect
Tue shore image also means it matters where you flash the img
Get a fastboot getvar all printout to me and I'll do what I can to help u get it running again