• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[GUIDE] How to root Red Hydrogen One Aluminum (H1A1000)

Search This thread

AumAum

Member
Sep 18, 2021
7
1
View attachment 5478323
1. Fastboot reboot bootloader
2. open the file "flash_a2h_windows.bat"
3. WAIT FOR SCRIPT TO FINISH. DO NOT UNPLUG
4. Unplug the cable from phone.
5. Reboot the phone
6. Finish setup
7. ENJOY
Dear Klutch Apex,
Thank you for the instructions set. I followed them as told. Once the batch file finished flashing it said press any key to continue. I did that and then pressed the power button to start the phone but now getting another error. I have taken a screen shot of the same.

Also if I leave the phone at the error message idle it goes to fast boot mode. I tried the start fastboot, recovery mode, nothing seems works. Also the product name is now changed to:
Product name: msm8998

Am I missing anything here.
Please let me know. Thank you.
Kind regards,
AUM AUM
 

Attachments

  • IMG_20211209_101135~2.jpg
    IMG_20211209_101135~2.jpg
    1.5 MB · Views: 13

AumAum

Member
Sep 18, 2021
7
1
View attachment 5478323
1. Fastboot reboot bootloader
2. open the file "flash_a2h_windows.bat"
3. WAIT FOR SCRIPT TO FINISH. DO NOT UNPLUG
4. Unplug the cable from phone.
5. Reboot the phone
6. Finish setup
7. ENJOY
Also recovery mode no longer works. It just loops back to start fastboot and restart bootloader. Only power off seems to power off the phone. Just want to give as much information possible for you understand what's happening. Any help would be very much appreciated. Thank you.
 

Mohsin6643

Member
Nov 28, 2021
22
4
Galaxy Note Edge
Moto G5S Plus
Dear Klutch Apex,
I forgot to mention that I can't use ADB devices command in ADB since it is not recognising my devices. I can only run fastboot devices and it shows the phone connected to the pc.so only fastboot instructions can work in my case.
I thought I should clarify this so you can guide appropriately.
Once and thank you.
Please let me know your thoughts.
Kind regards,
AUM AUM
I couldn't reply to the right post but I am referencing the post with the bootloader warning. Such a warning appears when you haven't unlocked your bootloader. Rub fastboot OEM Unlock, let it wipe the phone, run fastboot flashing unlock, if it asks to wipe then wipe, the run fastboot flashing unlock_critical and wipe if it asks. After that, flash using the instructions given by KlutchApex.
 

AumAum

Member
Sep 18, 2021
7
1
I couldn't reply to the right post but I am referencing the post with the bootloader warning. Such a warning appears when you haven't unlocked your bootloader. Rub fastboot OEM Unlock, let it wipe the phone, run fastboot flashing unlock, if it asks to wipe then wipe, the run fastboot flashing unlock_critical and wipe if it asks. After that, flash using the instructions given by KlutchApex.
Dear Mohsin6643,
I would not have gone this far without doing the OEM unlocking my phone. The problem is with secure boot = true. There is no way of telling the device to make it false so it could load another boot file. I checked the Google link I got ( see pic). It talks about secure OS. Anyway unless anyone has an ADB command load any program or command to make secure boot = false, I think the good work and efforts of KluchApex cannot be enjoyed. Thank you for the suggestion but that did not help. I am still not able to boot.
Happy to try anything to get past secure boot so please keep the suggestions coming. Thank you.
 

Mohsin6643

Member
Nov 28, 2021
22
4
Galaxy Note Edge
Moto G5S Plus
Dear Mohsin6643,
I would not have gone this far without doing the OEM unlocking my phone. The problem is with secure boot = true. There is no way of telling the device to make it false so it could load another boot file. I checked the Google link I got ( see pic). It talks about secure OS. Anyway unless anyone has an ADB command load any program or command to make secure boot = false, I think the good work and efforts of KluchApex cannot be enjoyed. Thank you for the suggestion but that did not help. I am still not able to boot.
Happy to try anything to get past secure boot so please keep the suggestions coming. Thank you.
Have you tried changing boot partitions?
1. fastboot getvar all
2. Scroll down to where it mentions the current boot slot
3. fastboot --set-active=a or fastboot --set-active=b depending on your current boot slot.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 5
    Hi all,

    For those who don't know, I'm known for rooting HMD Nokia Android Phones.
    EAQR6w7XoAATnuW

    So after few hours testing, I finally found out how to root it.
    Note, I've only dumped stock ROM from Verizon Wireless Variant as it's the only variant I've obtained so far. For non-operator variant and AT&T variant, I need your help for firmware dumping in case you want to restore your phone back to factory original state or OTA update if possible.

    Known working build: H1A1000.010ho.01.01.01r.109

    Procedure is pretty regular.

    Step 1: Unlock the bootloader
    Unlike HMD Nokia Android Phones, bootloader unlock is straight forward.
    Just enable OEM unlocking in developer options, reboot your phone to Fastboot mode and unlock the bootloader with following command:
    Code:
    fastboot flashing unlock
    Then confirm unlock on the phone.
    As I've always recommended for HMD Nokia Phones, you should do critical unlock as well:
    Code:
    fastboot flashing unlock_critical
    Then confirm unlock on the phone.

    Strange enough, this phone doesn't have unlock warning after unlocked. Not sure about open market release or AT&T Variant.

    Step 2: Install Magisk Manager and allow storage permission
    You can download it from Magisk release topic or https://github.com/topjohnwu/magisk/releases

    Step 3: Reboot to fastboot mode and flash patched boot image
    You can download required patched boot image and representative stock boot image from here: https://www.androidfilehost.com/?w=files&flid=297410
    For Verizon Variant that available with build "H1A1000.010ho.01.01.01r.109" so far, download "H1A1000.010ho.01.01.01r.109-boot_magisk_patched_193.img". You can check software version yourself if correct.

    The command is straight forward too:
    Code:
    fastboot flash boot /path/to/H1A1000.010ho.01.01.01r.109-boot_magisk_patched_193.img

    If you use Platform tools from Google officially, you needn't to care about your current slot actually.

    Now reboot your phone:
    Code:
    fastboot reboot

    Step 4: Restore stock boot image and reinstall Magisk (For OTA update ability although no update for months)
    After your phone booted, enable USB debugging and copy the file "H1A1000.010ho.01.01.01r.109-boot.img" you downloaded along with patched boot image. I would assume you copied it to root directory of internal storage.
    So execute following ADB commands:
    Code:
    $ su
    (Confirm Root permission on the phone)
    # getprop ro.boot.slot_suffix
    If it returns a, you'll need to execute this command:
    Code:
    # dd if=/storage/emulated/0/H1A1000.010ho.01.01.01r.109-boot.img of=/dev/block/bootdevice/by-name/boot_a
    If it returns b, you'll need to execute this command:
    Code:
    # dd if=/storage/emulated/0/H1A1000.010ho.01.01.01r.109-boot.img of=/dev/block/bootdevice/by-name/boot_b

    Then open Magisk Manager on your phone, tap no thanks if it asks for extra modules, then tap "Install" at the right of Magisk version, choose "Direct Install", and wait for the procedure complete.
    If installed successfully, you can reboot your phone on Magisk Manager now.

    That's it!
    At least this phone will work with Treble GSI build, so you should have idea about how could I dump the phone.

    For Treble GSI report, read this: https://github.com/phhusson/treble_experimentations/wiki/Red-Hydrogen-One
    2
    For those who want to know how I dumped the phone:

    Well, I found the phone could support Treble GSI and received update before.
    So if your current slot is B, you definitely want to give it a try.

    1. Unlock the bootloader

    2. Download AOSP 8.1 Treble GSI from @phhusson 's repo:
    https://github.com/phhusson/treble_experimentations/releases

    In my case I chose system-arm64-ab-gapps-su.img.xz one

    3. Enter fastboot mode and flash the image
    Please check current slot as well
    Code:
    fastboot getvar current-slot
    I would assume your current slot is B in this case.

    Code:
    fastboot flash system /path/to/system-arm64-ab-gapps-su.img
    fastboot erase frp

    4. Use volume key to choose "Reboot to recovery" then press power key to confirm
    Press power key and volume up key to get the menu if "No command" appears, then choose "Wipe data/factory reset" to erase userdata storage.
    Then reboot the phone.

    5. After the phone booted, finish Setup Wizard.

    6. Dump the boot image
    Code:
    adb shell
    $ su
    (Confirm root permission on the phone)
    # dd if=/dev/block/bootdevice/by-name/boot_b of=/storage/emulated/0/stock_boot.img
    # exit
    $ exit
    adb pull /storage/emulated/0/stock_boot.img
    adb reboot bootloader

    7. Switch to previous version, do factory reset
    Code:
    fastboot --set-active=a
    Reboot to recovery and perform factory reset.

    8. Reboot to normal OS and accept OTA update.
    9. Use Magisk to patch the boot image you dumped, then root it with your patched boot image, or you can upload it if possible.
    10. You can dump other partitions as well if you want.
    1
    Hey guys I ****ed up pretty big. Red wants me to send in my phone to get reimaged.

    Can someone please dump their system.img for me.

    https://www.addictivetips.com/mobil...es-boot-recovery-and-system-partition-images/

    dump is here
    https://github.com/AndroidDumps/red_hydrogenone_dump
    1
    Thank you so so much dude.

    your welcome, hope it helps.