Flashed TWRP, but no OS is working - Xiaomi Redmi 8 Questions & Answers

Redmi Note 8, I've successfully installed TWRP, then without taking backup attempted to wipe everything (including vendor & system).
Wiping of data failed.
Tried installing Pixel OS (non Plus version using ADB side loading), the OS started with the Google logo then it rebooted to TWRP.
Then I formatted data using Ext2 then using Ext4 then tried to wipe everything again and it worked (wiping everything system, data and vendor).
Tried installing Pixel OS again, but this time not even the Google logo appeared, just Redmi and then it reboots to TWRP.
I tried installing Pixel OS Plus, same.
I tried installing stock Mi ROM Global, this time it is stuck on the MIUI logo without doing anything, I have to reboot into recovery manually.
Now the only thing working on this piece of metal is TWRP, what to do?
Oh, and one more thing, even though now TWRP doesn't show red error lines and writes successful after OS installation, there is only one line that bothers me on the screen saying: init_user0_failed, but it's not in red.

Now I tried Potato OS, startup logo indefinitely.

One more question, is there a PC software for Xiaomi just like iTunes for Apple where I can restore my phone just like the day I bought it?

Logs from TWRP (compressed in 7z format): https://drive.google.com/file/d/1sfgYId00k-VRpzQ5VVC2mpP0rBRP1StB/view?usp=sharing

asaeles said:
Redmi Note 8, I've successfully installed TWRP, then without taking backup attempted to wipe everything (including vendor & system).
Wiping of data failed.
Tried installing Pixel OS (non Plus version using ADB side loading), the OS started with the Google logo then it rebooted to TWRP.
Then I formatted data using Ext2 then using Ext4 then tried to wipe everything again and it worked (wiping everything system, data and vendor).
Tried installing Pixel OS again, but this time not even the Google logo appeared, just Redmi and then it reboots to TWRP.
I tried installing Pixel OS Plus, same.
I tried installing stock Mi ROM Global, this time it is stuck on the MIUI logo without doing anything, I have to reboot into recovery manually.
Now the only thing working on this piece of metal is TWRP, what to do?
Oh, and one more thing, even though now TWRP doesn't show red error lines and writes successful after OS installation, there is only one line that bothers me on the screen saying: init_user0_failed, but it's not in red.
Click to expand...
Click to collapse
You should ask this at Redmi Note 8 forum. This place is for Redmi 8.

Related

Disable encryption on MiMax2 after Dot OS Install

Hello All,
I was on Stock MIUI 9 Global ROM (rooted with TWRP 3.2.1.0 OFFICAL) which was getting slower by the day. One day all of a sudden, I started getting ads on my lockscreen which was the final straw. So I installed dot OS 7.1.1 for Mi Max2. When setting up dot OS, I setup the lock screen pattern without knowing that it was turning ENCRYPTION ON.
I got bad sound in dot OS 7.1.1 ROM (tinny sound with echo), I was not happy so I did a full wipe of all partitions EXCEPT internal storage. and then installed Xiaomi EU ROM 9.5 Stable.
The issue:
TWRP and Normal Android BootUp on Xioami EU asks me for entering pattern every single boot. It asks for: Enter pattern to start android. On TWRP recovery boot: TWRP asks me to enter pattern and then decrypts phone.
How can I DISABLE Encryption without doing a full wipe + format of data partion?
Just to confirm: I remember the pattern, my phone works perfectly in Xiaomi EU ROM, I just want to disable encryption without doing a full WIPE+FORMAT+SETUP of my phone.
Thanks.
sk280 said:
Hello All,
I was on Stock MIUI 9 Global ROM (rooted with TWRP 3.2.1.0 OFFICAL) which was getting slower by the day. One day all of a sudden, I started getting ads on my lockscreen which was the final straw. So I installed dot OS 7.1.1 for Mi Max2. When setting up dot OS, I setup the lock screen pattern without knowing that it was turning ENCRYPTION ON.
I got bad sound in dot OS 7.1.1 ROM (tinny sound with echo), I was not happy so I did a full wipe of all partitions EXCEPT internal storage. and then installed Xiaomi EU ROM 9.5 Stable.
The issue:
TWRP and Normal Android BootUp on Xioami EU asks me for entering pattern every single boot. It asks for: Enter pattern to start android. On TWRP recovery boot: TWRP asks me to enter pattern and then decrypts phone.
How can I DISABLE Encryption without doing a full wipe + format of data partion?
Just to confirm: I remember the pattern, my phone works perfectly in Xiaomi EU ROM, I just want to disable encryption without doing a full WIPE+FORMAT+SETUP of my phone.
Thanks.
Click to expand...
Click to collapse
Honestly I didn't find any OTHER WAY without a Full Wipe!
TBH.. I'm kinda glad that someone else had this scenario.. :cyclops:
(Cause I had)
Here's how I overcame this issue..
1. First I Cleared everything on my phone using twrp and wiped everything **literally everything**
2. Then using fastboot on my PC I did this:
fastboot boot -recovery-( fastboot boot twrp.img)
[This will temporarily boot into TWRP]
3. And I wiped everything all over again
[Don't ask me why I did that but it worked for me]:silly:
4. Installed TWRP again using fastboot
5. Flashed a new ROM!
Hope this helps you!
Cheers mate!:fingers-crossed:
Thanks for that. I do NOT want to do a full wipe as I don't have access to Windows PC to do this (I'm on a MAC and don't have adb and drivers for MI MAX2).
TBH, the pattern is very annoying especially on restart as I have to wait for it and then wait some more for restart.
Worse case scenario, I'll a full backup of /data internal storage to an SD CARD, WIPE ALL Parittions and try again.
I'm almost tempted to reinstall dotOS and then NOT select a pattern when setting it up, you think that'll work?
the_phantom_97 said:
Honestly I didn't find any OTHER WAY without a Full Wipe!
TBH.. I'm kinda glad that someone else had this scenario.. :cyclops:
(Cause I had)
Here's how I overcame this issue..
1. First I Cleared everything on my phone using twrp and wiped everything **literally everything**
2. Then using fastboot on my PC I did this:
fastboot boot -recovery-( fastboot boot twrp.img)
[This will temporarily boot into TWRP]
3. And I wiped everything all over again
[Don't ask me why I did that but it worked for me]:silly:
4. Installed TWRP again using fastboot
5. Flashed a new ROM!
Hope this helps you!
Cheers mate!:fingers-crossed:
Click to expand...
Click to collapse
the_phantom_97 said:
Honestly I didn't find any OTHER WAY without a Full Wipe!
TBH.. I'm kinda glad that someone else had this scenario.. :cyclops:
(Cause I had)
Here's how I overcame this issue..
1. First I Cleared everything on my phone using twrp and wiped everything **literally everything**
2. Then using fastboot on my PC I did this:
fastboot boot -recovery-( fastboot boot twrp.img)
[This will temporarily boot into TWRP]
3. And I wiped everything all over again
[Don't ask me why I did that but it worked for me]:silly:
4. Installed TWRP again using fastboot
5. Flashed a new ROM!
Hope this helps you!
Cheers mate!:fingers-crossed:
Click to expand...
Click to collapse
Thanks a lot!
I was having a problem installing couple of ROMs with hanging on logo screen.
I was wiping everything and nothing was helping until I formatted data partition in twrp, it is not only wipe, it is format where you have to confirm writing 'yes' if you really want to.
Then everything started to work!
Thanks again!

xiaomi mi 8 bootloop

Hello,
I bought a mi8 with open bootloader and tried to install xiamoi.eu rom. Now I'm stuck in the 'powered by android' boot screen.
How I installed the rom:
1. installed TWRP_dipper via fastboot
2. wiped the phone
3. Copied this 'xiaomi.eu_multi_MI8_V10.2.2.0.PEACNXM_v10-9.zp' to the internal storage
4. Installed the rom
I can't access the TWRP menu anymore. If i try to start it, I get to the 'powered by android' bootloop screen. I've already tried flashing twrp again.
**Edit: I installed a newer twrp version and can now start it***
***Edit 2: Had to "format data" not just wipe, and confirm format with "yes".***
thanks for help.
Hope I have no Brick now

Custom Rom flashing problem.

Okay. Am currently on MIUI 11.0.3 (the latest one available for RaphaelIN)
So, the problem am facing is that, when i flash a custom rom, my phone gets rebooted to recovery and sometimes to fastboot(this happens occasionally) and i just simply cant get the rom to load.
Sometimes my phone gets into a state which resembles hardbrick (none of the buttons work, even holding the power button for 10secs doesn't) and after sometimes, usually 15 to 20 mins it restarts itself. This has happened thrice till date and all while booting to system.
The Roms i have tried-
-Pixel experience (unofficial) (android Q)
- Lineage OS 17 (unofficial)
- Havoc OS (both official and unofficial) (both pie and Q versions)
-MIUI (European rom)
I have also tried flashing the chinese, indian and global vendor (all done separately) thinking it was a vendor issue, but it also doesn't work.
Recovery is TWRP latest version, have also used orange fox recovery
Bootloader unlocking was done through the official method and the official app.
Any solutions for this problem and has anyone faced these problems or is it only me?
Astrek said:
Okay. Am currently on MIUI 11.0.3 (the latest one available for RaphaelIN)
So, the problem am facing is that, when i flash a custom rom, my phone gets rebooted to recovery and sometimes to fastboot(this happens occasionally) and i just simply cant get the rom to load.
Sometimes my phone gets into a state which resembles hardbrick (none of the buttons work, even holding the power button for 10secs doesn't) and after sometimes, usually 15 to 20 mins it restarts itself. This has happened thrice till date and all while booting to system.
The Roms i have tried-
-Pixel experience (unofficial) (android Q)
- Lineage OS 17 (unofficial)
- Havoc OS (both official and unofficial) (both pie and Q versions)
-MIUI (European rom)
I have also tried flashing the chinese, indian and global vendor (all done separately) thinking it was a vendor issue, but it also doesn't work.
Recovery is TWRP latest version, have also used orange fox recovery
Bootloader unlocking was done through the official method and the official app.
Any solutions for this problem and has anyone faced these problems or is it only me?
Click to expand...
Click to collapse
Consider this an overkill solution that always works for me if I run into issues with other methods. It will wipe everything so backup your data and apps.
Download the latest fastboot Indian MIUI ROM (for anyone else reading this download the ROM that is the same region as your phone)
Fully extract the ROM and flash it - make sure, if you use the Mi Flash Tool, that you change the flash option to 'clean all'
Boot into MIUI once, you don't need to actually go through the set-up, just let it fully load.
Boot the phone into fastboot and install TWRP - I recommend the latest mauronofrio TWRP.
After installing TWRP boot immediately into TWRP.
Format the data partition - don't skip this step.
Wipe cache and dakvik - don't wipe anything else.
In TWRP goto the mount menu and unmount the data partition then mount it again - others would suggested rebooting back into TWRP, either way works, you just need to make sure the data partition is properly mounted after formatting it.
Install the ROM of your choice - either have the ROM on a USB OTG stick, or copy it onto the phone from a PC whilst still in TWRP.
If your ROM doesn't include Google apps and services and you want Google, then install GApps - at the time of writing this Android 10 GApps is still in beta and packages bigger than nano may cause issues, so stick with pico or nano, assuming your installing an Android 10 ROM.
Boot into the ROM.
If you want Magisk, once the ROM has loaded, boot back into TWRP and flash the latest Magisk installer - it is possible to flash Magisk without booting into the ROM first and you'll probably be OK, but occasionally it can cause problems, I can't remember the details, but for the sake of 30 seconds I now boot into the ROM before flashing, just to be on the safe side.
At the time of writing this people have recently reported issues flashing GApps immediately after flashing Havoc 3.0 and recommend booting Havoc before flashing GApps. Although others say they've not had any problems. So if you choose to install Havoc you 'might' have problems if you install GApps without booting into Havoc at least once first.
I've never had problems when following this method.
You didn't format data that's why your rom doesn't boot. Follow Robbos nice guide and you are good to go.:good:
Robbo.5000 said:
Consider this an overkill solution that always works for me if I run into issues with other methods. It will wipe everything so backup your data and apps.
Download the latest fastboot Indian MIUI ROM (for anyone else reading this download the ROM that is the same region as your phone)
Fully extract the ROM and flash it - make sure, if you use the Mi Flash Tool, that you change the flash option to 'clean all'
Boot into MIUI once, you don't need to actually go through the set-up, just let it fully load.
Boot the phone into fastboot and install TWRP - I recommend the latest mauronofrio TWRP.
After installing TWRP boot immediately into TWRP.
Format the data partition - don't skip this step.
Wipe cache and dakvik - don't wipe anything else.
In TWRP goto the mount menu and unmount the data partition then mount it again - others would suggested rebooting back into TWRP, either way works, you just need to make sure the data partition is properly mounted after formatting it.
Install the ROM of your choice - either have the ROM on a USB OTG stick, or copy it onto the phone from a PC whilst still in TWRP.
If your ROM doesn't include Google apps and services and you want Google, then install GApps - at the time of writing this Android 10 GApps is still in beta and packages bigger than nano may cause issues, so stick with pico or nano, assuming your installing an Android 10 ROM.
Boot into the ROM.
If you want Magisk, once the ROM has loaded, boot back into TWRP and flash the latest Magisk installer - it is possible to flash Magisk without booting into the ROM first and you'll probably be OK, but occasionally it can cause problems, I can't remember the details, but for the sake of 30 seconds I now boot into the ROM before flashing, just to be on the safe side.
At the time of writing this people have recently reported issues flashing GApps immediately after flashing Havoc 3.0 and recommend booting Havoc before flashing GApps. Although others say they've not had any problems. So if you choose to install Havoc you 'might' have problems if you install GApps without booting into Havoc at least once first.
I've never had problems when following this method.
Click to expand...
Click to collapse
Thnx for the guide. i will do this within a day or two and update you if it worked or not.
Kollachi said:
You didn't format data that's why your rom doesn't boot. Follow Robbos nice guide and you are good to go.:good:
Click to expand...
Click to collapse
I did format the data partition coz that's one thing I and my friends always do when flashing new rom. I don't exactly remember but i think, the pseudo hardbrick thingy started after i formatted the system, data, cache & internal storage.
I will follow Robbos guide adn keep you guys updated on what happened.
Astrek said:
I did format the data partition coz that's one thing I and my friends always do when flashing new rom. I don't exactly remember but i think, the pseudo hardbrick thingy started after i formatted the system, data, cache & internal storage.
I will follow Robbos guide adn keep you guys updated on what happened.
Click to expand...
Click to collapse
Format data = (you will need to type in "yes")
Note: Format data or wipe data isn't the same thing.
Robbo.5000 said:
Consider this an overkill solution that always works for me if I run into issues with other methods. It will wipe everything so backup your data and apps.
Download the latest fastboot Indian MIUI ROM (for anyone else reading this download the ROM that is the same region as your phone)
Fully extract the ROM and flash it - make sure, if you use the Mi Flash Tool, that you change the flash option to 'clean all'
Boot into MIUI once, you don't need to actually go through the set-up, just let it fully load.
Boot the phone into fastboot and install TWRP - I recommend the latest mauronofrio TWRP.
After installing TWRP boot immediately into TWRP.
Format the data partition - don't skip this step.
Wipe cache and dakvik - don't wipe anything else.
In TWRP goto the mount menu and unmount the data partition then mount it again - others would suggested rebooting back into TWRP, either way works, you just need to make sure the data partition is properly mounted after formatting it.
Install the ROM of your choice - either have the ROM on a USB OTG stick, or copy it onto the phone from a PC whilst still in TWRP.
If your ROM doesn't include Google apps and services and you want Google, then install GApps - at the time of writing this Android 10 GApps is still in beta and packages bigger than nano may cause issues, so stick with pico or nano, assuming your installing an Android 10 ROM.
Boot into the ROM.
If you want Magisk, once the ROM has loaded, boot back into TWRP and flash the latest Magisk installer - it is possible to flash Magisk without booting into the ROM first and you'll probably be OK, but occasionally it can cause problems, I can't remember the details, but for the sake of 30 seconds I now boot into the ROM before flashing, just to be on the safe side.
At the time of writing this people have recently reported issues flashing GApps immediately after flashing Havoc 3.0 and recommend booting Havoc before flashing GApps. Although others say they've not had any problems. So if you choose to install Havoc you 'might' have problems if you install GApps without booting into Havoc at least once first.
I've never had problems when following this method.
Click to expand...
Click to collapse
Ohhh *****...!!!! It ****ing worked!!!! Though i made some mistakes like clean all and lock in first step, but was able to unlock bootloader almost instantly, no idea why but i can almost instantly unlock certain mi phone's bootloader instantly. But a lot of thanx for taking your time and writing this up... You really saved me from being stuck in MIUI forever!
A lot of thnx.... and also happy new year... 1st day of 2020 went quite well for me all thnx to you and i hope yours goes well too.!
Robbo.5000 said:
Consider this an overkill solution that always works for me if I run into issues with other methods. It will wipe everything so backup your data and apps.
Download the latest fastboot Indian MIUI ROM (for anyone else reading this download the ROM that is the same region as your phone)
Fully extract the ROM and flash it - make sure, if you use the Mi Flash Tool, that you change the flash option to 'clean all'
Boot into MIUI once, you don't need to actually go through the set-up, just let it fully load.
Boot the phone into fastboot and install TWRP - I recommend the latest mauronofrio TWRP.
After installing TWRP boot immediately into TWRP.
Format the data partition - don't skip this step.
Wipe cache and dakvik - don't wipe anything else.
In TWRP goto the mount menu and unmount the data partition then mount it again - others would suggested rebooting back into TWRP, either way works, you just need to make sure the data partition is properly mounted after formatting it.
Install the ROM of your choice - either have the ROM on a USB OTG stick, or copy it onto the phone from a PC whilst still in TWRP.
If your ROM doesn't include Google apps and services and you want Google, then install GApps - at the time of writing this Android 10 GApps is still in beta and packages bigger than nano may cause issues, so stick with pico or nano, assuming your installing an Android 10 ROM.
Boot into the ROM.
If you want Magisk, once the ROM has loaded, boot back into TWRP and flash the latest Magisk installer - it is possible to flash Magisk without booting into the ROM first and you'll probably be OK, but occasionally it can cause problems, I can't remember the details, but for the sake of 30 seconds I now boot into the ROM before flashing, just to be on the safe side.
At the time of writing this people have recently reported issues flashing GApps immediately after flashing Havoc 3.0 and recommend booting Havoc before flashing GApps. Although others say they've not had any problems. So if you choose to install Havoc you 'might' have problems if you install GApps without booting into Havoc at least once first.
I've never had problems when following this method.
Click to expand...
Click to collapse
thanks for help
but no work for me
after flash rom and reboot booting to twrp auto..
Kollachi said:
Format data = (you will need to type in "yes")
Note: Format data or wipe data isn't the same thing.
Click to expand...
Click to collapse
many times the tiniest msg has the greatest significance. thanks mate!!!
Guys i need your help,, i flashed my phones custom Rom tecno 7cs using sp flashing tool.
That worked and it showed the tick icon on my pc.
The problem is that it does nothing to my phone because the software issues are still there
my phone keeps restarting itself almost all the time and sometimes won't even boot it takes longer to boot,,, apps keep on crushing and many more.AM tired am going to break it and throw it if i don't get solutions asap!
So the flashing process only wiped data on the phone nothing else whatsoever.
tecno 7cs p121 Bi safaricom ke 20151111

Can I custom rom brand phones?

Hi.
I have a Zenfone 5 (ZE620KL, X00QD). It is a brand phone (Vivo Brand, which is a mobile operator in Brazil).
I'm trying to flash custom roms but it seems they simply don't work.
I already bootloaded and rooted the phone. It has TWRP 3.3.1-0 installed now. When I rooted, I used Magisk with the original stock rom boot.img from Vivo Brand firmware to generate the rooted boot.img. It worked as intended and the phone was rooted.
I tried to install many roms. All of them, I wiped the folders (Dalvik, cache, Data, vendor, system) and even formated data (and rebooted the phone after each procedure) before trying to install the roms.
I also downloaded the roms from XDA respective topics. The list of each rom I tried and the errors are:
CRDroid and dotOS: do install, but enter in bootloop. I tried to wait for a few boots. I entered twrp again and wiped cache, data, dalvik and vendor). But still bootloop.
HavocOS and Pixel Experience: installed and no bootloop, but it doesn't quit from the initial screen loading (I waited for 2 hours). I also tried to reboot and nothing. Then, I wiped the folders again and nothing.
NezukoOS: close one. It installs and even gets to a screen where it asks for a password. When I enter the password it says the password is correct, but decryption uncessful. It asks to erase data. I did it (tried just wipe cache, data, Dalvik, but not the system folder this time! I also tried to format data). But no good ending. It says again about the decryption problem.
LineageOS 16.1 and Viper OS: they give me an "error installing zip file" message in TWRP. This is odd, because the zip file is not corrupted. I can open and extract it on my PC. But, I also downloaded again and tried a second time and nothing.
Is it because the phone is brand vivo? Or any sugestions?
I also tried the above procedures with adb sideload. The problems were the same.
Sorry if the term "brand vivo" is incorrect or about my English.

Stuck in boot loop

Hi, I got a situation here. I had to reinstall the rom in my Note 7 Pro after nearly 2 years from teh last time I had to do it.
Unfortunately, I had no idea that the new Magisk version can't be flashed by custom recoveries anymore. I simply flashed my rom using Orange Fox, restarted to the system, used the cell for 2 days, installed everything I needed, and yesterday I downloaded the latest 24310 Magisk version, flashed it using my custom recovery, and restarted in the system again.
Magisk greeted me with a message that it needed extra setup to be fully functional. I restarted in recovery, nothing happened, restarted to system, Maghisk still stuck in the need extra setup to be functional. I resolved to uninstall it using the app, got an error message in the console, tried restoring images, another error. Tried to reboot to recovery to try to reflash magisk, no more recovey, gone. Used adb to reflash recovery, rebooted to it, now I have a message that says Error opening: 'data/adb/magisk' (operation not permitted). Tried to use the Orange Fox option to remove Magisk, got some error messages Error opening: 'data/adb/magisk' (operation not permitted), but it said it was done. Tried to reboot, stuck in boot loop, back in recovery, dirty flashed my actual ROM, still stuck in boot load.
Any way to delete this locked magisk folder to try to completely remove magisk and try to reinstall it the correct way now? Or the only solution is a complete reinstallation of the ROM formatting all partitions? I haven't tried it yet because after 2 years of doing this procedure I barely remember how to do a clean install correctly.
Blackdragonbird said:
Hi, I got a situation here. I had to reinstall the rom in my Note 7 Pro after nearly 2 years from teh last time I had to do it.
Unfortunately, I had no idea that the new Magisk version can't be flashed by custom recoveries anymore. I simply flashed my rom using Orange Fox, restarted to the system, used the cell for 2 days, installed everything I needed, and yesterday I downloaded the latest 24310 Magisk version, flashed it using my custom recovery, and restarted in the system again.
Magisk greeted me with a message that it needed extra setup to be fully functional. I restarted in recovery, nothing happened, restarted to system, Maghisk still stuck in the need extra setup to be functional. I resolved to uninstall it using the app, got an error message in the console, tried restoring images, another error. Tried to reboot to recovery to try to reflash magisk, no more recovey, gone. Used adb to reflash recovery, rebooted to it, now I have a message that says Error opening: 'data/adb/magisk' (operation not permitted). Tried to use the Orange Fox option to remove Magisk, got some error messages Error opening: 'data/adb/magisk' (operation not permitted), but it said it was done. Tried to reboot, stuck in boot loop, back in recovery, dirty flashed my actual ROM, still stuck in boot load.
Any way to delete this locked magisk folder to try to completely remove magisk and try to reinstall it the correct way now? Or the only solution is a complete reinstallation of the ROM formatting all partitions? I haven't tried it yet because after 2 years of doing this procedure I barely remember how to do a clean install correctly.
Click to expand...
Click to collapse
Reflash the stock unrooted boot.img of your room in bootloader. Use adb
Fastboot flash boot boot.img
Similar problem here...
I tried reflashing stock recovery and stock boot.img - now whenever I reboot it just boots into recovery! I don't seem to be able to boot into system any more...
Any ideas?
I'm running AOSIP on a Xiami Mix Mi 3 - I hadn't updated to the latest Magisk in quite some time (since before the app could do it automatically). I have to use the recovery method.
Steps I took are:
Get recovery.zip from my ROM, patched it through the app, then flashed through fastboot. I rebooted while holding down the up arrow to reboot into recovery, then released for the phone to boot.
I got an error after booting that said "there's an internal error with your device" - and it was super buggy, couldn't tap the screen, super slow to load stuff, etc.... I figured it was a magisk issue, so tried to reflash recovery and boot... Not I'm stuck booting into recovery!
Help.
Edit: so - I think it turns out I have one of those RARE xiaomi devices that DOES have ramdisk even though the app doesn't detect it... Go figure. A clean install of the ROM, followed by patching the BOOT image rather than the recovery image - and we're up and running.

Categories

Resources