I have a rooted HTC one M9. I saw the HTCU tag so the device bootloader is also unlocked. Android version is 5.0.2
I compiled a custom kernel and updated it using abootimage.
I then tried:
Code:
adb reboot bootloader
fastboot boot boot.img
adb wait-for-device shell
I could use also
Code:
fastboot flash boot boot.img
but i want for the begining the boot.img to be lost on reboot.
The device is waiting in fastboot Menu with following options:
Reboot
Reboot to bootloader
Boot to download mode
Boot to recovery mode
Power down
When i give command:
Code:
fastboot devices
I get no device (empty list).
How can i update the kernel?
Is there a problem with fastboot?
The title of the thread is a bit misleading since you are asking a question and not explaining what needs to be done to flash a kernel.
The M9 has no Fastboot Mode like the ones you may know from older HTC devices. You need to boot to Download Mode if you want to use fastboot commands. Besides I think I read somewhere here on xda that fastboot boot commands do not work with the M9 due to new security features. But I can't find that specific post right now so my memories might be wrong...
Related
After initially trying the Android Revolution HD rom after rooting few days ago, I realized I wanted to go back to stock. I downloaded "https://dl.google.com/dl/android/aosp/mysid-icl53f-factory-65895fa8.tgz" off of http://groups.google.com/group/android-building/msg/2cd2b16ed56a7e84 for my Verizon LTE GN variant...
I extracted "image-mysid-icl53f.zip" and flashed it the usually way with CWM, ended up going into a boot loop. Luckily I had a Nandroid backup of my phone just after rooting so I was able to use that to restore back to stock...
Was there any reason that "image-mysid-icl53f.zip" didn't work? I read another unrelated (if I remember correctly) post on here about flashing the image with a modified script from Google, do I need to use the flash-all.sh or something when flashing this zip? Do I need the other files (bootloader-toro..., radio-cdma..., and radio-toro...)? Or did I just get unlucky and a reflash probably would have fixed it?
Thanks
You don't flash the zip with cwm. You need to do fastboot -w update blah.,ip command with it.
Search for the "convert yawuwhatever to yawublah" thread for the directions
Sent from my Galaxy Nexus
s1977 said:
Resetting the phone by taking out the battery shouldn't be a problem if you havent started flashing the new rom. I would try again after confirming that the fastboot and usb drivers can see the device before proceeding any further.
You can use fastboot devices to list attached devices. Only progress further once you can see your phone using the above command.
I did the same today a few hours ago and in my case, I started the phone in bootloader mode via Volume up + down + power button or via adb reboot bootloader. Then with fastboot, issue the fastboot oem unlock command to unlock the bootloader first. Once done, then you can flash the stock image (bootloader, radio and rom) with the following commands.
fastboot flash bootloader <bootloader image>
fastboot reboot-bootloader
fastboot flash radio <radio image>
fastboot reboot-bootloader
fastboot -w update <rom image>
Don't forget to lock the bootloader once done using fastboot oem lock
Just to clarify, depending on the version of the OS on your client PC/Mac/Linux, there are variants of fastboot. I use fastboot-mac from my mac.
Click to expand...
Click to collapse
Also try checking out this thread: How to? Change from yakjuxw to yakju
Pretty easy root. This is based off the N5206EX_23_141129 boot.img. All it really does is give you root via adb though.
Sucks we don't have kernel source yet...but this should get us started.
Download this boot.img:
http://www.invisiblek.org/n3/N5206EX_23_141129_rooted_boot.img
md5sum: 416978b586b932e0dbe5d18b74332ad8
Make sure to enable Developer Settings (tap the build number in about a bunch of times), then enable adb debugging in developer options.
Destructions:
Code:
adb reboot bootloader
fastboot oem unlock
fastboot flash boot N5206EX_23_141129_rooted_boot.img
fastboot reboot
Here's an unofficial twrp also, I opt'd not to start a new thread for it as Dees_Troy is planning to release it soon anyway:
http://www.invisiblek.org/n3/TWRP_2.8.3.0_UNOFFICIAL_n3.img
md5sum: 9905f2017dc12584cc4f071b349a10bf
Destructions:
Code:
adb reboot bootloader
fastboot oem unlock (if you have't already)
fastboot flash recovery TWRP_2.8.3.0_UNOFFICIAL_n3.img
fastboot reboot
After you get adb again:
Code:
adb reboot recovery
Looks like the official TWRP is now out, slightly newer version
http://teamw.in/project/twrp2/282
hi
does anyone has a simply way to root with a common 'step'
i left samsung and will come this phone
thanks'
HI... thanks but, the link for the image is broken... can you post it again... Thanks.¡¡¡
can this work on n5207 or do u know where i can root my version please!!!
What link recovery
Godell famz said:
What link recovery
Click to expand...
Click to collapse
https://eu.dl.twrp.me/n3/
Ok so from this thread : http://forum.xda-developers.com/zenfone2/help/how-to-upgrade-cn-version-to-ww-t3101556
I saw this : fastboot flash fastboot droidboot.img - droidboot.img is fastboot, and if you somehow will flash corrupted image, you won't be able to boot to fastboot anymore. Thanks to sorg
Is there ANY way to fix that ? Mine is broken and I CAN NOT : root/update recovery/enter bootloader
Basically i am STUCK on the firmware I have and CAN NOT do anything on this phone other than factory reset it but thats just about it.
Search for flash_image. I used it to flash recovery from running system. I suppose it can be used to flash fastboot too.
maciek90 said:
Search for flash_image. I used it to flash recovery from running system. I suppose it can be used to flash fastboot too.
Click to expand...
Click to collapse
The phone HAS RECOVERY does NOT HAVE BOOTLOADER
Read entire message. I wrote that this tool probably can be used to flash fastboot too.
You can also try "dd" command from busybox. Check sticky section in Zenfone General forum how to use it.
xRanker said:
Ok so from this thread : http://forum.xda-developers.com/zenfone2/help/how-to-upgrade-cn-version-to-ww-t3101556
I saw this : fastboot flash fastboot droidboot.img - droidboot.img is fastboot, and if you somehow will flash corrupted image, you won't be able to boot to fastboot anymore. Thanks to sorg
Is there ANY way to fix that ? Mine is broken and I CAN NOT : root/update recovery/enter bootloader
Basically i am STUCK on the firmware I have and CAN NOT do anything on this phone other than factory reset it but thats just about it.
Click to expand...
Click to collapse
You shouldn't mess with stuff you don't understand
If you have recovery, can you get to recovery menu?
Droid on back with error underneath and where you have to hold power then up volume to get to recovery menu.
Ok, here is link to flash_image tool.
http://forum.xda-developers.com/showthread.php?t=902493
I used it to flash recovery on HTC Sensation, but it should work with fastboot on Zenfone too. The command should be "flash_image fastboot /path/to/droidboot.img"
I'm not sure if it will work, but you already have messed up fastboot so this shouldn't make it worse
The second option is "dd if=/path/to/droidboot.img of=/dev/block/by-name/fastboot" or "dd if=/path/to/droidboot.img of=/dev/block/mmcblk0p3" as fastboot is the third partition. You can execute this even in terminal emulator on phone. Of course I haven't check it, but it's listed in general section to flash recovery (fastboot is just another partition, so it should work too).
About going to recovery maybe you can type " reboot recovery" in terminal emulator or from pc "adb reboot recovery". I'm not sure if it uses fastboot to boot into recovery but it's worth trying.
xRanker said:
Ok so from this thread : http://forum.xda-developers.com/zenfone2/help/how-to-upgrade-cn-version-to-ww-t3101556
I saw this : fastboot flash fastboot droidboot.img - droidboot.img is fastboot, and if you somehow will flash corrupted image, you won't be able to boot to fastboot anymore. Thanks to sorg
Is there ANY way to fix that ? Mine is broken and I CAN NOT : root/update recovery/enter bootloader
Basically i am STUCK on the firmware I have and CAN NOT do anything on this phone other than factory reset it but thats just about it.
Click to expand...
Click to collapse
Find Your Solution Here
Tried fixing my oppo find 7
Did all those Fastboot wipe .
Fastboot flash recovery and flash LOGO and stuffs
but im still stuck on logo ... WHUT
kevzwenhao said:
Tried fixing my oppo find 7
Did all those Fastboot wipe .
Fastboot flash recovery and flash LOGO and stuffs
but im still stuck on logo ... WHUT
Click to expand...
Click to collapse
Did you unlock bootloader?
1. Connect the device to the computer through USB.
2. From a terminal on a computer, type the following to boot the device into fastboot mode (or restart pressing power+vol up):
Code:
adb reboot bootloader
3. Once the device is in fastboot mode, verify your PC sees the device by typing:
Code:
fastboot devices
4. From the same terminal, type the following command to unlock the bootloader:
Code:
fastboot oem unlock
If the device doesn't automatically reboot, reboot it from the menu. It should now be unlocked.
5. Then you can flash the recovery what you want. In fastboot mode, type in terminal:
Code:
fastboot devices
6. And flash the recovery. Type:
Code:
fastboot flash recovery your_recovery_image.img
Good luck
roi_xordo said:
Did you unlock bootloader?
1. Connect the device to the computer through USB.
2. From a terminal on a computer, type the following to boot the device into fastboot mode (or restart pressing power+vol up):
Code:
adb reboot bootloader
3. Once the device is in fastboot mode, verify your PC sees the device by typing:
Code:
fastboot devices
4. From the same terminal, type the following command to unlock the bootloader:
Code:
fastboot oem unlock
If the device doesn't automatically reboot, reboot it from the menu. It should now be unlocked.
5. Then you can flash the recovery what you want. In fastboot mode, type in terminal:
Code:
fastboot devices
6. And flash the recovery. Type:
Code:
fastboot flash recovery your_recovery_image.img
Good luck
Click to expand...
Click to collapse
Hi, is it wrong to wipe the system partition before flashing a custom rom? Coming from stock ColorOS, I've wiped all dalvik cache, cache, system, and data, then flash a custom rom but it ended up getting endless bootanimation unable to boot into the custom rom.
I did unlock the bootloader with the adb code, flashing a temporary recovery was a success but endless bootanimation happened after flashing a custom rom. The custom rom was successfully installed according to TWRP's log.
Pls advice, thanks in advanced
P.s: I was referring to my friend's device X9076
Hi, i tried in the past some roms than not works, phone stuck in boot animation. The roms wich works for me and my x9076 with r63419 are:
Omnirom (6 or 5) THE BEST
Project Spectrum
Cyanogen 13 (modified version for new panel: http://community.oppo.com/en/forum.php?mod=viewthread&tid=44907&extra=)
Miui
If you install CM13, you need to flash unified partition script for CM13 (you can find it in the same post from the forum Oppo Community)
For the other roms i dont need to flash anything else than rom and gapps.
Now i give a chance to CM13, but i think that i will get back to Omni if developers dont fix the mobile radio issue.
Cheers
Can anyone guide me please, 1st time i bought MTK phone Oppo F7, its update automatically but suddenly dead like stuck on logo and restarting again and again, i didnt ever flash MTK phone, neither i have any android tool like MRT dongle or any other flash USB or Box... Kindly guide me step by step how to flash with which tool only USB cable and PC... Thanks in advance
Method 1:-
Download Custom Recovery for armani in your pc and rename it to recovery.img
and download root zip and paste it in your sdcard
Download 15 seconds adb & fast drivers and follow the instructions....
In pc type the following commands by opening cmd from shift+right click and open command prompt here after connecting the device to pc
Code:
adb devices
after successful install of drivers you will see the device listed in that
Code:
adb reboot bootloader
After rebooting into fastboot mode type the following commands
Code:
fastboot flash recovery recovery.img
after successful flashing of recovery then type this
Code:
fastboot reboot recovery
Flash SuperSU/Koush superuser in your TWRP/CWM/Philz recovery
Method 2:- Download Kingo ROOT and root
Method 3:- Download Kingo ROOT pc version in your pc and load it and connect your device to pc and root....
Method 4:- Download KingRoot and click to root....if it fails in first attempt, try atleast 5 times...
Yes these are indeed the best methods to root this phone.
Also, note that Magisk will not work for the stock MIUI because the phone has Android 4.4 and Magisk probably requires 5.0+. So, Magisk should be used for newer custom ROMs.
HemanthJabalpuri said:
I want to root my MIUI 9 armani in 2018.....
I don't have PC
Click to expand...
Click to collapse
Also, like you had said earlier, if you don't have a PC due to some reason, you can use another phone or tablet for that purpose (to flash the custom recovery). I've read somewhere that most Android devices having 5.0 and below came preloaded with adb fastboot binaries (for newer Android phones, you can easily obtain the binaries online and add them into the /system/bin folder if it is rooted) and hence you can connect your Redmi to this other device using an OTG cable and use the shell (any terminal app) to issue the commands. The only important thing to be considered in this approach is that the other (host) device should have a big enough battery to be able to provide sufficient current to the Redmi phone such that it should not get disconnected during the process.
This method is usually ignored by people, but it really works.
Reserved
Reserved
Code:
$ fastboot reboot recovery
fastboot: usage: unknown reboot target recovery
Cannot issue the last command.
When I flash TWRP and reboot nothing happens. Same Mi Recovery is present.
I am on MIUI 9. Not rooted. I am trying to get a custom recovery but I fail. Please help.
blazzer12 said:
Code:
$ fastboot reboot recovery
fastboot: usage: unknown reboot target recovery
Click to expand...
Click to collapse
Are you sure recovery was flashed properly?
Try this while in fastboot mode :-
Code:
fastboot devices
Make sure that your device is listed properly.
Try this
Code:
fastboot erase recovery
fastboot flash recovery <path to recovery img>
Then reboot using
Code:
fastboot reboot recovery
If still doesn't work out, try to directly boot into recovery image
Code:
fastboot boot <path to recovery img>
If still doesn't work out, then there might be a problem with the fastboot binary on the PC, try to reinstall the latest version of it on the PC and try again.
---------- Post added at 22:03 ---------- Previous post was at 21:55 ----------
blazzer12 said:
When I flash TWRP and reboot nothing happens. Same Mi Recovery is present.
Click to expand...
Click to collapse
If the issue is specific to TWRP Recovery, try to flash other recoveries. For example, older version of TWRP or maybe try Philz Touch recovery as well.
Yes, the fastboot devices is being listed. Still #2 didn't work. But #3 worked perfectly.
So for me flashing recovery didn't work. I had to temporarily boot into the recovery and then again flash the recovery from there.
Thank you for the help. :good:
Now we can root with Magisk too...
https://forum.xda-developers.com/ap...v7-universal-systemless-t3473445/post78829088
Note:- Magisk v22.1 is the last version to support Android 4.4.2