• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Anyone help me get MIUI (S-on, latest FB)

TheDirectorFur

TheDirectorFur

Well-Known Member
So I'm running meanbean just fine after unlocking bootloader via HTCdev and flashing Meanbean, but I continuously try to flash MIUI to no success. I flash the Rom (twrp), go to bootloader from recovery after that, click fastboot, and push the boot.img via cmd prompt. But I reboot the phone, and I get a "process.android has failed" and then I get "sim toolkit default message yes/no. Every 2 seconds. Am I not doing the correct s-on installation of this Rom? Would really appreciate help on this
Thanks
 
TheDirectorFur said:
So I'm running meanbean just fine after unlocking bootloader via HTCdev and flashing Meanbean, but I continuously try to flash MIUI to no success. I flash the Rom (twrp), go to bootloader from recovery after that, click fastboot, and push the boot.img via cmd prompt. But I reboot the phone, and I get a "process.android has failed" and then I get "sim toolkit default message yes/no. Every 2 seconds. Am I not doing the correct s-on installation of this Rom? Would really appreciate help on this
Thanks
Click to expand...

what are you wiping before you flash the rom? you should wipe dalvik cache, cache, and factory reset, and system in twrp.
 
Okay, I tried that. So I'm just going to go S-Off
I'm about to relock bootloader and run RUU Will Ruu return TWRP to Stock rec.?
 
ocnbrze said:
yes the ruu on the Team Unlimited website will return the phone back to stock.
Click to expand...

Okay so I tried to flash RUU, this is what I got

writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOchecking main version...
FAILED (remote: 43 main version check fail)

What does that mean?
 
TheDirectorFur said:
Okay so I tried to flash RUU, this is what I got

writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOchecking main version...
FAILED (remote: 43 main version check fail)

What does that mean?
Click to expand...

what is your hboot and radio? you can find this in the bootloader menu at the top.

and the reason is because you flashed the wrong ruu for your phone. the ruu will depend on what your hboot is.
 
ocnbrze said:
what is your hboot and radio? you can find this in the bootloader menu at the top.

and the reason is because you flashed the wrong ruu for your phone. the ruu will depend on what your hboot is.
Click to expand...

Hboot-2.09.0000
Radio 1.12.11.1119

So I have to find a different RUU?
 
TheDirectorFur said:
Hboot-2.09.0000
Radio 1.12.11.1119

So I have to find a different RUU?
Click to expand...

ok unfortunately you can't get s-off with your hboot. you have the latest ota and all you can do is unlock the bootloader. you will have to wait for the devs to figure out a way to get s-off with hboot 2.09. how long of a wait? not really sure. the devs usually will keep those kinds of things quiet, until they find one.

but you can still flash things with an unlocked bootloader, so all is not lost.
 
Thanks for all your help. Lastly, I read somewhere that if you flash a ROM via ADB,because fastboot is part of the boot/partition, the kernel will stick and won't require a seperate flash. Is this true? and if so what would be the command to flash the ROM?
 
TheDirectorFur said:
Thanks for all your help. Lastly, I read somewhere that if you flash a ROM via ADB,because fastboot is part of the boot/partition, the kernel will stick and won't require a seperate flash. Is this true? and if so what would be the command to flash the ROM?
Click to expand...

you can't flash roms per se via adb. you can push the rom file and then command recovery to do it via adb. not sure if that is what you are talking about.

you can flash roms with s-on but the boot.img(this is where the kernel lies) does not get flashed. you can however use fastboot command to flash the the boot.img to get the kernel. but it will depend if you are coming from aosp to sense or sense to aosp.

also check the rom's op. the devs have found a way to flash the kernel with s-on. if the rom has a s-on kernel installer then you do not need to fastboot the boot.img. it will automatically flash the kernel when you flash the rom just like normal.

hope that makes sense.
 
You must log in or register to reply here.
Back
Top Bottom