Related
Hi all,
So I'm far from a noob at at all of this (doing the custom android thing for years). But I'm not exactly constantly fiddling with my phone all the time anymore either. Basically I get a set-up that works for me, and I stick with it.
I've patiently been waiting to update to Lollipop. And today I did it. I did it by flashing the required factory images with fastboot.
AND IT WORKS. No problem. It boots. I go through the initial set-up. I can let it restore all my apps and passwords from the google servers, etc. So far so good.
My problem is that I cannot root. After I try, it bootloops (stuck at the Google splash, with my unlocked icon).
I tried to root before my first boot. I tried after the initial boot (before set-up and signing in). I tried rooting after setting it all up, and singing in, and letting google restore all of my apps. No matter which sequence I try, it will reboot a couple times at the first Google splash, and then fall back to Recovery.
(So, I'm on back on my rooted 4.4.4 nandroid, I think it's Mahdi Rom-- I forget)
Vital Stats:
Trying to install factory images of 5.0.1, all stock (system, boot (kernel), radio, bootloader)
Factory reset
(the above works fine)
TWRP 2.8.1.0
SuperSU-v2.40 (flashed via recovery)
Any ideas? Thanks for any help.
No, but could you try the previous version of SuperSU? Just to rule out the new version that I haven't tested please?
I updated to 5.0.1 earlier
Flashed all the img files exact userdata and then booted in to Android.
I then flashed TWRP 2.8.1.0 and used that to flash SuperSU 2.37
All that worked fine.. I then did a play update and SuperSU updated to 2.40
All working fine as far as I can tell. Apps needing root are working!
iowabeakster said:
Hi all,
So I'm far from a noob at at all of this (doing the custom android thing for years). But I'm not exactly constantly fiddling with my phone all the time anymore either. Basically I get a set-up that works for me, and I stick with it.
I've patiently been waiting to update to Lollipop. And today I did it. I did it by flashing the required factory images with fastboot.
AND IT WORKS. No problem. It boots. I go through the initial set-up. I can let it restore all my apps and passwords from the google servers, etc. So far so good.
My problem is that I cannot root. After I try, it bootloops (stuck at the Google splash, with my unlocked icon).
I tried to root before my first boot. I tried after the initial boot (before set-up and signing in). I tried rooting after setting it all up, and singing in, and letting google restore all of my apps. No matter which sequence I try, it will reboot a couple times at the first Google splash, and then fall back to Recovery.
(So, I'm on back on my rooted 4.4.4 nandroid, I think it's Mahdi Rom-- I forget)
Vital Stats:
Trying to install factory images of 5.0.1, all stock (system, boot (kernel), radio, bootloader)
Factory reset
(the above works fine)
TWRP 2.8.1.0
SuperSU-v2.40 (flashed via recovery)
Any ideas? Thanks for any help.
Click to expand...
Click to collapse
Try not doing that? When you go through the initial configuration, choose "Set up as a new device". Maybe the restore is somehow corrupting SuperSU?
BirchBarlow said:
Try not doing that? When you go through the initial configuration, choose "Set up as a new device". Maybe the restore is somehow corrupting SuperSU?
Click to expand...
Click to collapse
It happens even if I try to root before setting anything up at all.
albert_htc,
Are you saying: I should also flash the stock recovery first. Then boot for the first time. Then re-flash TWRP. Then flash SuperSU.
I never flashed the stock recovery. TWRP was on already on it.
Thanks guys. I'll give it another rip (doing stock recovery, then flashing back to TWRP) sometime soon.
iowabeakster said:
It happens even if I try to root before setting anything up at all.
albert_htc,
Are you saying: I should also flash the stock recovery first. Then boot for the first time. Then re-flash TWRP. Then flash SuperSU.
I never flashed the stock recovery. TWRP was on already on it.
Thanks guys. I'll give it another rip (doing stock recovery, then flashing back to TWRP) sometime soon.
Click to expand...
Click to collapse
Yes, flash the factory image using the batch file so every partition gets re-flashed. Now I'm thinking maybe your recovery is corrupt.
Run flash-all.bat and when your device reboots, go through all of the initial configuration and download all of the Gapps updates. Once that's all completed, go ahead and route using TWRP. If you find yourself still having the same problem, try live booting TWRP to flash SuperSU.
BirchBarlow said:
Yes, flash the factory image using the batch file so every partition gets re-flashed. Now I'm thinking maybe your recovery is corrupt.
Run flash-all.bat and when your device reboots, go through all of the initial configuration and download all of the Gapps updates. Once that's all completed, go ahead and route using TWRP. If you find yourself still having the same problem, try live booting TWRP to flash SuperSU.
Click to expand...
Click to collapse
I'm not going to flash over my user data, nandroids, app back-ups, etc. I'll stay with kit kat forever on my nexus 5 before I do that. Version numbers aren't that important. Hours wasted getting things set-up again are.
My recovery works fine. Both on kit kat and lollipop. My only problem is a boot loop when I flash SuperSU (via TWRP), on lollipop. I will try flashing stock recovery, though and then reflashing TWRP.
iowabeakster said:
I'm not going to flash over my user data, nandroids, app back-ups, etc. I'll stay with kit kat forever on my nexus 5 before I do that. Version numbers aren't that important. Hours wasted getting things set-up again are.
My recovery works fine. Both on kit kat and lollipop. My only problem is a boot loop when I flash SuperSU (via TWRP), on lollipop. I will try flashing stock recovery, though and then reflashing TWRP.
Click to expand...
Click to collapse
It's a tedious process, but it really isn't all that hard to back everything up to a computer, and you can do it easily with fastboot and a single command line.
Or what I'd recommend doing is just booting up, backing up all folders to a PC and then resetting and restoring later, backup apps with Titanium Backup (what I always do). A lot of us flashed factory images when Lollipop came out, so it isn't that bad once you start on the road.
Have you tried rooting from the bootloader via Chainfire's cf-auto root? I know I've read that sometimes rooting from recovery doesn't work properly, and that only certain zips will work. I've used the auto root each time (from stock fastboot flashing 5.0 & 5.0.1) with lollipop and it works fine. Link
Unzip and run batch file in bootloader. It will wipe everything if you haven't already unlocked bootloader (fastboot oem unlock). If you are already unlocked it won't wipe anything.
snappycg1996 said:
It's a tedious process, but it really isn't all that hard to back everything up to a computer, and you can do it easily with fastboot and a single command line.
Or what I'd recommend doing is just booting up, backing up all folders to a PC and then resetting and restoring later, backup apps with Titanium Backup (what I always do). A lot of us flashed factory images when Lollipop came out, so it isn't that bad once you start on the road.
Click to expand...
Click to collapse
I just backed the /sdcard, to my PC. I just re-ran titanium.
I can deal with "/sdcard issues" from updating to lollipop easy enough. That's a 30 second fix. I can deal with setting up my email accounts to my email client app. I can deal with launcher settings, and all the other apps, widgets, etc. Those are things that I can slowly get back to where I want. They aren't critical. But yeah, very tedious.
I think "starting over" may be much more tedious for me than most people though. I run ssh servers and clients on all PCs, servers, and phones (disabling passwords and using rsa encryption keys for security). It's very nice, once I get it all set up in that I can access everything (from anything) very easily. I do need root for that though also.
But if I can't just hit a "restore" to get it all my ssh addresses, keys, fingerprits, etc back to where it was and then I have to: reverify new fingerprints, generate new keys, re-enable passwords to transmit new keys for everything, then disable passwords (for all machines) ... well... I just get very very grumpy.
anactoraaron said:
Have you tried rooting from the bootloader via Chainfire's cf-auto root? I know I've read that sometimes rooting from recovery doesn't work properly, and that only certain zips will work. I've used the auto root each time (from stock fastboot flashing 5.0 & 5.0.1) with lollipop and it works fine. Link
Unzip and run batch file in bootloader. It will wipe everything if you haven't already unlocked bootloader (fastboot oem unlock). If you are already unlocked it won't wipe anything.
Click to expand...
Click to collapse
I'll check that out. Thanks.
Hello everyone.
I had a problem flashing TWRP on my Google Nexus 5, or better the problem comes when I try to enter the recovery.
I followed this pattern from stock android 6.0.1 with august security patch:
1) unlock bootloader
2) downloaded lastest TWRP (3.0.2 hammerhead) recovery from the official website
3) flash it with "fastboot flash recovery recovery.img"
Until this point everything's alright but then when I unplug my phone from the laptop and click on enter recovery something strange happens.
I can see the TWRP boot image but as soon as I go in I see tons of errors related to "cannot mount ..." and some partitions name like /data, /cache, and then starts the bootloop without let me any chance to do something. Sorry but I can't see every error beacuse this happen too fast.
Any idea on what is going on?
I've tried the TWRP 3.0.1 but is the same shuold I go down or maybe I have to change it beacuse of compatibily issues with the monthly patches?
Thank you for your help, I hope I explained my problem clearly.
After unlocking the bootloader, phone wipe all data? Did you reboot after unlocking bootloader?
audit13 said:
After unlocking the bootloader, phone wipe all data? Did you reboot after unlocking bootloader?
Click to expand...
Click to collapse
No I've just unlocked and then tryied to flash the recovery without wipe.
But data is already wiped by unlocking the bootloader isn't it?
Anyway thanks for your reply as soon as I can I'll try what you have written.
Yes, the data should be automatically wiped. Try TWRP 2.87. If the phone still doesn't boot into TWRP, reflash stock recovery, flash userdata.img, immediately boot into stock recovery using the button combo without rebooting, perform a factory wipe, reboot into fastboot, and flash TWRP again.
audit13 said:
Yes, the data should be automatically wiped. Try TWRP 2.87. If the phone still doesn't boot into TWRP, reflash stock recovery, flash userdata.img, immediately boot into stock recovery using the button combo without rebooting, perform a factory wipe, reboot into fastboot, and flash TWRP again.
Click to expand...
Click to collapse
Thank you so much for telling me to flash the 2.8.7, i've choosen the 2.8.7.1 without success (it did't flash i don't know why) but then after another wipe all I've flashed the 2.8.7.0 and it seems to work.
The only thing I would like to ask now is: I'm going to flash superSU and elementalX over stock AOSP (I don't want custom ROM for now) and can this recovery cause problem because of it is not the last update?
Thank you again for the answer!
I have not tried 2.87 with Elemental X. The only way to determine whether it will work would be to try it. I recommend creating a nandroid backup before flashing Elemental so you can restore if something goes wrong.
TWRP Restore problem
Hi, I have an issue with the resotre of TWRP...
Here's what I did:
-Downloaded the latest OTA image https://developers.google.com/android/nexus/ota
-Downloaded latest SuperSU http://download.chainfire.eu/supersu-stable
-Downloaded latest ElementalX http://elementalx.org/devices/nexus-5/
-reboot to TWRP
Choose OTA, then SuperSU, then ElementalX
Luunch the restore..
And my screen is "blocked" from 5 hours on Install Zip 1 of 3.
"blocked" means doesn't move to the Zip2 but the clock is moving... the screen is locking itself after few seconds and I am able to unlock it...
Any idea how to exit properly ?
I have rebooted...deleted all my music... (I think that the issue may come from insufficient disk space) and relaunched...
Will see...
download Nexus Root Toolkit-type in google Nexus Root Toolkit - and watch from yuotoube how it work's
good luck
hunter-dz said:
download Nexus Root Toolkit-type in google Nexus Root Toolkit - and watch from yuotoube how it work's
good luck
Click to expand...
Click to collapse
My N5 was already rooted... and it's the second time that I update the OTA using directly TWRP... and for the August patch it has worked fine.
I don't know what's happen now...
kevtuning said:
My N5 was already rooted... and it's the second time that I update the OTA using directly TWRP... and for the August patch it has worked fine.
I don't know what's happen now...
Click to expand...
Click to collapse
Download thé nrt and i Will teach how to root ur n5
And type in Google nrt n5 xda
audit13 said:
I have not tried 2.87 with Elemental X. The only way to determine whether it will work would be to try it. I recommend creating a nandroid backup before flashing Elemental so you can restore if something goes wrong.
Click to expand...
Click to collapse
Now I can confirm that I was able to flash the lastest SuperSU and ElementalX with TWRP 2.8.7.0 without any problem, so thank you again for your help.
kevtuning said:
Hi, I have an issue with the resotre of TWRP...
Here's what I did:
-Downloaded the latest OTA image https://developers.google.com/android/nexus/ota
-Downloaded latest SuperSU http://download.chainfire.eu/supersu-stable
-Downloaded latest ElementalX http://elementalx.org/devices/nexus-5/
-reboot to TWRP
Choose OTA, then SuperSU, then ElementalX
Luunch the restore..
And my screen is "blocked" from 5 hours on Install Zip 1 of 3.
"blocked" means doesn't move to the Zip2 but the clock is moving... the screen is locking itself after few seconds and I am able to unlock it...
Any idea how to exit properly ?
Click to expand...
Click to collapse
Hi, I've have successfully installed the last OTA update but not with zip file, instead I downloaded the factory image and flashed with fastboot boot.img and system.img (also vendor.img if you have one) then rebooted into TWRP and installed the lastest ElementalX and SuperSU.
I'm not sure but I think that factory image zip file are not installable via recovery but only with the flash-all that comes with them. This script use fastboot to flash everything you need of the factory image
You can find this procedure on the ElementalX website, here is the link hope it can help out: http://elementalx.org/how-to-install-android-monthly-security-updates/
Finally... I installed CM13 and ElementalX... in some minutes ...
I suppose the the problem was in my zip file...
Hey guys. I'm in a hell of a bind and could use some help.
My Galaxy Note 5 (N920T, rooted) was running fine on this ROM: https://forum.xda-developers.com/tm...m-qc6-lite-rom-bloated-knoxed-odexed-t3598686 ; however, I had disabled OEM unlock at one point to try and fix a random app I was playing with. The battery died not long after, causing the phone to reboot. On power, it failed to boot due to custom binary block from FRP, so I decided to try and run the usual troubleshooting of flashing a stock ROM via Odin. Stock images will flash (tried 5.1.1, 6.1, and 7); however, when they try to install I get the error for no DRK. Sometimes I'll also get a dm-verity error as well... So I then tried to flash TWRP or any recovery via Odin to let me fix this issue; however, any custom recoveries I try to flash are being blocked by FRP.
So, I'm in a loop. I can't use my initial ROM because FRP, however I also can't install a stock ROM because of missing DRK, AND I can't fix the DRK or verity errors because I can't install a recovery capable of doing so because of FRP.
IMEI is intact when I look into Download mode, but I can't seem to get anything to work. I've tried the FRP Tool and crack, but that gives me FRP blocks as well (USERDATA).
Am I boned?
B U M P
Anyone?
same situation, going to try flashing it to stock. Can we just flash a stock bootloader or do we need to start over?
Got it working by flashing stock rom with odin so maybe not exact same situation as you. Hard to find a filehosting site with good download speeds and spent all day trying to get latest stock note 5 firmware. Well good for now.. All started because of a wrong flip of a switch *bangs head on desk*
You need to do a few things. First you need to wipe everything in TWRP including format data, so love your files to some other storage. In Odin go to options and turn off auto reboot. Turn on f reset time, phone bootloader update and Nand Erase All. You need to know that this doesn't always work, if you can't unlock it this way try disabling encryption after flashing stock and TWRP and flash Magisk. Let me know how it goes.
Metabolic12 said:
You need to do a few things. First you need to wipe everything in TWRP including format data, so love your files to some other storage. In Odin go to options and turn off auto reboot. Turn on f reset time, phone bootloader update and Nand Erase All. You need to know that this doesn't always work, if you can't unlock it this way try disabling encryption after flashing stock and TWRP and flash Magisk. Let me know how it goes.
Click to expand...
Click to collapse
Got as far as getting the firmware flashed via Odin, but when I first boot I get "Device does not have DRK" error. I cannot install TWRP or any custom recovery through Odin due to FRP lock.
x24veggie said:
Got as far as getting the firmware flashed via Odin, but when I first boot I get "Device does not have DRK" error. I cannot install TWRP or any custom recovery through Odin due to FRP lock.
Click to expand...
Click to collapse
if all you are getting is frp lock just flash back to stock like I did and start over rooting etc.
craig198 said:
if all you are getting is frp lock just flash back to stock like I did and start over rooting etc.
Click to expand...
Click to collapse
That's not all. Basically, it goes,
Flash back to stock
Reboot
Can't finish ROM install because DRK is unavailable
Can't install anything in locked, stock android recovery
TWRP, autoroot, etc. is blocked from Odin by FRP
craig198 said:
same situation, going to try flashing it to stock. Can we just flash a stock bootloader or do we need to start over?
Got it working by flashing stock rom with odin so maybe not exact same situation as you. Hard to find a filehosting site with good download speeds and spent all day trying to get latest stock note 5 firmware. Well good for now.. All started because of a wrong flip of a switch *bangs head on desk*
Click to expand...
Click to collapse
No. It started because you didn't back up your phone properly with twrp before going flash crazy
---------- Post added at 08:52 AM ---------- Previous post was at 08:47 AM ----------
x24veggie said:
That's not all. Basically, it goes,
Flash back to stock
Reboot
Can't finish ROM install because DRK is unavailable
Can't install anything in locked, stock android recovery
TWRP, autoroot, etc. is blocked from Odin by FRP
Click to expand...
Click to collapse
https://www.google.ca/amp/s/forum.x...to-solve-dm-verity-verification-t3293306/amp/ have you tried this? If we can figure this out please don't ever play with oem or have a stock recovery ? that's your security blanket
US BLN-L24 on straight talk here. I've spent months trying to figure out a painless way to get this thing upgraded, rooted, and rom'd but 100 different threads explain 100 different processes and none of them are particularly easy to follow. Surely someone has taken the time to write up an updated, easy to follow guide for this specific model of 6x? Does this still require debranding?
Model number = BLN-L24
EMUI Version = 5.0.4
Build Number = BLN-L24C567B377
Android version = 7.0
Thanks.
johnnyrichter said:
US BLN-L24 on straight talk here. I've spent months trying to figure out a painless way to get this thing upgraded, rooted, and rom'd but 100 different threads explain 100 different processes and none of them are particularly easy to follow. Surely someone has taken the time to write up an updated, easy to follow guide for this specific model of 6x? Does this still require debranding?
Model number = BLN-L24
EMUI Version = 5.0.4
Build Number = BLN-L24C567B377
Android version = 7.0
Thanks.
Click to expand...
Click to collapse
There is. But yeah I agree. Anyway to debrand and update to EMUI 8 you need to follow a few steps.
You need an Unlocked Bootloader. If yours isn't unlocked, unlock it via Ministry of Solutions or DC Phoenix. Both are paid.
You need an SD card with at least 8 GB size.
First of all download Firmware Finder from Play Store. Search for model BLN-AL20 and download the 8.0.0.536 Full-OTA. Download the following three archives:
Update.zip
Update_data_full_public.zip
And the last one should be the one with BLN-AL20 in the name.
After you download the three files, go ahead and search for HWOTA for Honor 6X on XDA and download it. Extract it to /C. Once extracted, rename the files you downloaded before to:
Update.zip -> Don't rename
Update_data_full_public.zip -> update_data_public.zil
And the last file to -> update_all_hw.zip
Transfer the three files to update folder inside HWOTA 7. Now, you need an unlocked Bootloader. Now boot phone into Fastboot and connect phone to PC. And now run update.bat once it asks you to boot into TWRP unplug your phone. Now hold power button. When it boots up and you see three options menu, hold volume up to enter into TWRP. once in TWRP reconnect USB cable. Now press Enter twice. Wait patiently. Once it finishes, reboot phone and when you see three options menu, again hold volume up to boot into eRecovery. Perform a Factory reset. Once that complete, Format Cache and reboot. First boot will take several minutes. On first boot it will be an incomplete flash. You won't have any signal. To fix that, download Hurupdater. Search for it. Once it's download transfer it and the same three files you used before to your SD card inside the same folder. Next download TWRP from link:
https://mega.nz/#!a81EDZAR!2-9yPFh3reghkGcfSl3nRIJhHGkP8fqDsgUG66ewjkk
Once TWRP is downloaded, again reboot to Bootloader and flash TWRP by command:
fastboot flash recovery_ramdisk RECOVERY-V2.img
Then reboot with fastboot reboot.
Once phone reboots, power it off. Next turn on by holding Power and Volume Up simultaneously till you boot into TWRP. Once in TWRP head over to
Wipe -> Format Data -> YES -> hit Enter
Once that finishes, press back twice. Now:
Advanced Wipe -> Mark Dalvik/ART Cache, Cache, Data, Internal and System. Swipe to Wipe.
Once wipe finishes head over to install, select SD card and navigate to folder with the Hurupdater files. Select only Hurupdater to flash. Press Volume Down when prompted. It will take at least 10 mins. So be patient. Once it finishes, Wipe Cache/Dalvik. After that, Reboot System Now. When it's booting and you see these options menu again hold into eRecovery and wipe Data/Factory Reset. Once that finishes again Format Cache and then Reboot System Now.
First boot will take at least 10 minutes. So be patient and don't panic. When your phone first boots you won't have any signal. Finish setup. Then turn off phone. Plug USB into computer and the other end into phone while holding Volume Down when it's powered off. Once you boot into Bootloader reflash TWRP as you did before. Next flash latest Magisk. Install Magisk Manager and ES File Explorer and Grant SU rights of ES File Explorer. Then using root Explorer navigate to
/cust/all/cn/prop/local.prop
And edit the line
ro.config.full_network_support=true
Change true to false. Save and reboot. Now you have Network. If this works then I'll help you flash a Custom ROM.
I saved my PID and unlock code from last year when I first tried to unlock/root/rom the phone, so no need to pay for bootloader unlock.
I just unlocked my bootloader and it factory reset my phone, now waiting for phone to boot so I can go to play store and continue with your instructions. Will report back soon, hopefully. I made sure all my photos and contacts were saved to external SD before unlock so no data lost.
Edit1: Downloaded/installed firmware finder, retrieving those 3 files now, then will move them to pc. Getting hwota extracted to C:\ right now.
Got stuck near the end of your guide;
Code:
C:\Users\John>fastboot flash recovery_ramdisk RECOVERY-V2.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (9100 KB)...
OKAY [ 0.222s]
writing 'recovery_ramdisk'...
FAILED (remote: Command not allowed)
finished. total time: 0.232s
I put the recovery-v2.img file in C:\users\john\ directory, assuming it needed to be there since that's my working directory in cmd prompt when I submit that command.
I figured I would have to unlock bootloader again since it relocked from earlier, so I did that and went back to fastboot and ran fastboot flash recovery_ramdisk RECOVERY-V2.img again. Now I get this error,
Code:
c:\Users\John>fastboot flash recovery_ramdisk RECOVERY-V2.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (9100 KB)...
OKAY [ 0.221s]
writing 'recovery_ramdisk'...
FAILED (remote: partition length get error)
finished. total time: 0.231s
Not sure what to do now?
Rebooted to recovery and had TWRP, noticed the update.bat window was still up waiting for me to hit enter once booted in to TWRP so I tried that. Flashed the three files I saved earlier, rebooted, now doing update install so it looks like I'm back on track and not finished yet.
Edit1: Performed factory reset, then wiped cache and rebooted. Phone is now booting. At this point it *Should* boot normally, no signal, then I can reboot to fastboot and continue with flashing twrp and last few steps.
Edit2: fastboot flash recovery_ramdisk RECOVERY-V2.img appears to have worked after booting in to fastboot. Then ran fastboot reboot, booting now.
Edit3: On this part my phone appears to be stuck on chinese language?
First boot will take at least 10 minutes. So be patient and don't panic. When your phone first boots you won't have any signal. Finish setup. Then turn off phone.
Click to expand...
Click to collapse
I'm trying to figure out how to get it to english so i can finish setup, shut down, get in tyo fastboot, flash twrp again, then boot in to that to flash magisk. Also do I get magisk manager and es file explorer in play store?
Edit4: Got it to english, finished setup, shut down, fastboot, reflashed twrp, reboot, shut down, enter twrp with volume up + power, sd card not showing up on computer to copy latest magisk so had to reboot system and put that file on sd(showing BLN-AL20 and EMUI 8!!!), shut down, enter twrp again, flashed latest magisk, rebooted to EMUI8, launched Magisk Manager(already present) and it downloaded/installed update and Magisk now shows latest version installed. Installed ES File Explorer from xda labs page via hisuite, shows installed but when launching it just goes to white screen so currently trying to figure that out so I can edit that file and restore cell service.
Edit5: Removed ES File Explorer since it's not working and went with MiXplorer, edited that file and saved, rebooted, now have service. Now ready for new rom!
Now that phone is unlocked, rooted, and on EMUI8 how do I go about flashing one of the official openkirin roms at https://openkirin.net/download/? Which one is most stable for daily use?
Edit: Also no google apps, so I'm very limited in using my phone until I can get one of the OpenKirin roms installed.
johnnyrichter said:
Now that phone is unlocked, rooted, and on EMUI8 how do I go about flashing one of the official openkirin roms at https://openkirin.net/download/? Which one is most stable for daily use?
Edit: Also no google apps, so I'm very limited in using my phone until I can get one of the OpenKirin roms installed.
Click to expand...
Click to collapse
I used RROS and it was pretty stable with no major bugs. 99% daily driver. But you can see ignorable force closes here and there.
It's simple to flash all OpenKirin Roms. Just download the desired one, put it into your adb folder, boot your phone to bootloader/fastboot, type command:
fastboot flash system (filename).img
Regarding GAPPS if you're on Stock Chinese Oreo B536, just download the playstore apk from apkpure or any other source and install. It will work and you can then disable AppGallery.
OpenKirin Roms have everything included, Gapps too.
Edit: https://openkirin.net/user_guide/openkirin-rom-installation-instructions/
The detailed guide to flashing OpenKirin roms.
Went with LineageOS since I've always loved their roms, figured I'd try that one first. At step 15 I choose wipe data/factory reset, it reboots, I don't touch anything, and it loads to the black/red TWRP. It did this twice so the second time I did factory reset from TWRP and reboot system.
It then went to LOS boot, then "to start android, enter password" screen. Looked around on google, some people said clearing cache fixed that, rebooted to stock recovery, said data partition corrupted, factory reset again, rebooted, again went to that TWRP for some reason, factory reset in there, wipe dalvik/art and cache, reboot system, LOS boot logo, phone said it was encrypting, rebooted, LOS boot logo, encryption unsuccessful screen and option to reset phone, keep clicking RESET PHONE button and nothing happens. Was able to do a power button restart since LOS is partially working, same encryption unsuccessful screen with non-working RESET PHONE button.
How do I fix this? I think the problem is factory reset in factory recovery is not working, because when it reboots to start factory reset it instead loads to TWRP and factory reset never happens. Can't use phone at all at the moment.
Trying RROS next to see if that helps, but I did notice FRP UNLOCK wasn't on fastboot screen...not sure why? Maybe that is my problem? Bootloader is unlocked.
Edit: Flashed RROS, tried a factory reset from erecovery, rebooted in to twrp again. Tried to factory reset there and reboot, RROS loading screen, encrypting again, reboot, I'm now in rom setup wizard so maybe it's working now? Not sure if I'm still rooted, though or why fastboot stopped saying FRP unlock.
johnnyrichter said:
Trying RROS next to see if that helps, but I did notice FRP UNLOCK wasn't on fastboot screen...not sure why? Maybe that is my problem? Bootloader is unlocked.
Click to expand...
Click to collapse
No frp on chinese oreo due to partial Gapps presence/support. That's not an issue.
Now the Wipe Data option.
Wiping data through TWRP decrypts data partition and wiping with stock one encrypts it. OS works with encrypted one. So after installing any OpenKirin Rom, do factory reset with stock recovery right after flashing the rom.
Now follow the instructions of flashing rom, after that flash and go to stock recovery, wipe/factory reset. Restart and it should work
goldenevil47 said:
No frp on chinese oreo due to partial Gapps presence/support. That's not an issue.
Now the Wipe Data option.
Wiping data through TWRP decrypts data partition and wiping with stock one encrypts it. OS works with encrypted one. So after installing any OpenKirin Rom, do factory reset with stock recovery right after flashing the rom.
Now follow the instructions of flashing rom, after that flash and go to stock recovery, wipe/factory reset. Restart and it should work
Click to expand...
Click to collapse
That's the part that is broken for me, stock recovery factory reset. I click the button, type yes and hit the button, phone reboots but instead of booting to the factory reset process it reboots to twrp each time.
Right now I'm officially loaded in to RROS I'm assuming, but not sure if I should expect any issues since I never did do a factory reset from what I've seen so far.
johnnyrichter said:
That's the part that is broken for me, stock recovery factory reset. I click the button, type yes and hit the button, phone reboots but instead of booting to the factory reset process it reboots to twrp each time.
Right now I'm officially loaded in to RROS I'm assuming, but not sure if I should expect any issues since I never did do a factory reset from what I've seen so far.
Click to expand...
Click to collapse
I am SO sorry. I wrote the guide and went to sleep. Glad to know everything worked for you. Here Is the stock Recovery. Flash it in the same way you flashed TWRP. And then factory reset. I was writing instructions but look like someone beat me to them. Again, Sorry.
https://mega.nz/#!xiR2TYAB!kmt60JDRh4_7u37W56CEJZUuhcZvv6AefJiuadF1e9s
And if you want a Pie ROM just ask. I know a really good and stable one. I will help with that.
Right now everything seems to be working fine, RROS is working with no issues so far, getting all my apps/settings back in place. Unfortunately I can only add my work exchange email account(office365) to gmail on this rom, can't do exchange in the android e-mail app which sucks.
I know TWRP is still there on the "ramdisk" hiding, but I've done several shutdowns and restarts and it hasn't come back up so I think I'll leave it be. If it becomes a problem I can always flash the stock recovery again.
johnnyrichter said:
Right now everything seems to be working fine, RROS is working with no issues so far, getting all my apps/settings back in place. Unfortunately I can only add my work exchange email account(office365) to gmail on this rom, can't do exchange in the android e-mail app which sucks.
I know TWRP is still there on the "ramdisk" hiding, but I've done several shutdowns and restarts and it hasn't come back up so I think I'll leave it be. If it becomes a problem I can always flash the stock recovery again.
Click to expand...
Click to collapse
Again. I am SO SORRY. I shouldn't have been this careless. But if you want to be sure, just boot into fastboot, flash stock Recovery, reboot. Again boot to fastboot, flash ROM like you did before, this time boot into Stock Recovery and Factory Reset. Reboot and profit. And if you want Root, then flash TWRP like you did before, followed by latest Magisk.
Mannan Qamar said:
Again. I am SO SORRY. I shouldn't have been this careless. But if you want to be sure, just boot into fastboot, flash stock Recovery, reboot. Again boot to fastboot, flash ROM like you did before, this time boot into Stock Recovery and Factory Reset. Reboot and profit. And if you want Root, then flash TWRP like you did before, followed by latest Magisk.
Click to expand...
Click to collapse
No problem at all, worst case scenario I would have just gone back to stock firmware since I still have the files from last year when I tried rooting/romming and failed.
Everything seems to be working great though. RROS is real smooth and very customizable which I like. Just can't seem to figure out how to get the stock email app to allow exchange account, and how to customize the notification light.
Magisk Manager was present when I first loaded in to RROS, upon opening it did its updates/installs. Just ran a root checker and phone is rooted...so somehow it maintained root from when I did the EMUI 8 install. Should I have busybox installed? Will xposed work for me?
Thanks to the both of you for all the help. I'm so happy to finally have a good ROM on my 6x. :good:
Phone is all configured and running great, sorted out the fb messenger light issue, busybox running.
Is xposed compatible with this version of android yet? And if I wanted to try one of the other OpenKirin roms, what is involved in switching? Just flash the other rom and perform a stock recovery wipe/reset, or do I need to wipe data before flashing new rom?
johnnyrichter said:
Phone is all configured and running great, sorted out the fb messenger light issue, busybox running.
Is xposed compatible with this version of android yet? And if I wanted to try one of the other OpenKirin roms, what is involved in switching? Just flash the other rom and perform a stock recovery wipe/reset, or do I need to wipe data before flashing new rom?
Click to expand...
Click to collapse
No. No Xposed. And to switch ROMs, flash the new one via fastboot followed by a factory reset in stock recovery and you're Golden
Mannan Qamar said:
No. No Xposed. And to switch ROMs, flash the new one via fastboot followed by a factory reset in stock recovery and you're Golden
Click to expand...
Click to collapse
Awesome. I might give LOS a try tonight, depends on how attached I am to RROS by then. I've been playing with my phone all day at the office tweaking and change stuff in RROS getting everything working just the way I like it. I'm so thrilled to have the phone rooted/rom'd!
Thank you again for all your help!
I want to revert back too. Will report.
soweic said:
I want to revert back too. Will report.
Click to expand...
Click to collapse
What do you mean?
Today I tried to finally update to the latest version of crDroid, but ended up having a bunch of issues doing so, and after a lot of troubleshooting and trying to fix it, I ended up putting it into a bootloop of some sort instead.
I'm pretty sure the last thing I tried was installing a different version of TWRP to see if that version would let me properly install the rom, and stop my phone from always rebooting into recovery mode.
Trying to turn it on normally or boot into TWRP leaves it hanging on the "Redmi" boot screen, it can boot into fastboot mode though.
I'm guessing that the only way to recover my phone at this point is to flash the Official MIUI rom back onto the phone, but that also involves wiping Data and losing pretty much everything I've put on the phone.
I was smart enough to make a TWRP of the Data folder, but while making the backup, the console said it doesn't include all personal files or something.
How much of my personal data and files can I rescue from the phone in this state, and how can I do that before it gets wiped when fixing it?
Also, I think I really need some help in actually restoring my phone and flashing the custom rom properly.
No matter how much effort I put into figuring out how to do this stuff, unexpected issues always seem to happen, and turns something that initially seemed so simple into multiple hours of troubleshooting.
The only way I think i've gotten rom flashing to work at all was by wiping everything and installing the official MIUI rom, but I don't want to be losing my data every month when an update comes out.
So, could someone please help me get my phone working again?
Edit: I ended up fixing my own issue by ADB flashing on a different release of TWRP, and then installing fcrypt disabler after the rom but before everything else.
Sanarise said:
Today I tried to finally update to the latest version of crDroid, but ended up having a bunch of issues doing so, and after a lot of troubleshooting and trying to fix it, I ended up putting it into a bootloop of some sort instead.
I'm pretty sure the last thing I tried was installing a different version of TWRP to see if that version would let me properly install the rom, and stop my phone from always rebooting into recovery mode.
Trying to turn it on normally or boot into TWRP leaves it hanging on the "Redmi" boot screen, it can boot into fastboot mode though.
I'm guessing that the only way to recover my phone at this point is to flash the Official MIUI rom back onto the phone, but that also involves wiping Data and losing pretty much everything I've put on the phone.
I was smart enough to make a TWRP of the Data folder, but while making the backup, the console said it doesn't include all personal files or something.
How much of my personal data and files can I rescue from the phone in this state, and how can I do that before it gets wiped when fixing it?
Also, I think I really need some help in actually restoring my phone and flashing the custom rom properly.
No matter how much effort I put into figuring out how to do this stuff, unexpected issues always seem to happen, and turns something that initially seemed so simple into multiple hours of troubleshooting.
The only way I think i've gotten rom flashing to work at all was by wiping everything and installing the official MIUI rom, but I don't want to be losing my data every month when an update comes out.
So, could someone please help me get my phone working again?
Click to expand...
Click to collapse
can u boot into twrp?
if u can boot, while in twrp, connect your phone via usb cable to pc. u can copy everything on pc
Simoom Sadik said:
can u boot into twrp?
if u can boot, while in twrp, connect your phone via usb cable to pc. u can copy everything on pc
Click to expand...
Click to collapse
Unfortunately, I can't.
Trying to boot into TWRP just gets stuck on the 'Redmi' boot logo.
I just remembered that you can install TWRP over ADB, and that Peter's one says it works even when the system partition is empty, so maybe the issue is the TWRP I installed and could possibly undo this part of the issue over ADB.
It won't fix the issue preventing my from updating my rom, but recovery only is still better than a soft brick.
Edit: That worked, i've put Peter's TWRP back on, and it's launching into recovery mode/TWRP again now
twrp not boot after successfully flash in this rom
Sanarise said:
Unfortunately, I can't.
Trying to boot into TWRP just gets stuck on the 'Redmi' boot logo.
I just remembered that you can install TWRP over ADB, and that Peter's one says it works even when the system partition is empty, so maybe the issue is the TWRP I installed and could possibly undo this part of the issue over ADB.
It won't fix the issue preventing my from updating my rom, but recovery only is still better than a soft brick.
Edit: That worked, i've put Peter's TWRP back on, and it's launching into recovery mode/TWRP again now
Click to expand...
Click to collapse
flash latest twrp download from github, install twrpbuilder img twrp ,it boot fine and you will copy your data to pc and then install any other twrp img which u want , dont wipe anything from phone before phone boot.flash only original twrp builder 3.2.3.1 official,it boot only on latest updates.
Why nobody use orangefox?
is your issue solve or not tell,
Simoom Sadik said:
can u boot into twrp?
if u can boot, while in twrp, connect your phone via usb cable to pc. u can copy everything on pc
Click to expand...
Click to collapse
if your problem is not solve then tell me you need to flash a fastboot rom first with save user data.bat file and when it installed then you can install twrp builder 3.2.1. and then boot to twrp this methods working fine,if you recently flashed any android 10 rom then first you need to flash a miui fastboot rom,or flash it via command mode direct only 3 files
first click on extract a fastboot rom and copy boot system and vender file with flash.all bat file and make a new folder then click on flash.bat save user data file to flash these images
or you can do this manually
fastboot flash system system.img
fastboot flash vender vender.img
fastboot flash boot boot.img
then reboot device to fastboot again
now flash latest official twrp builder 3.2.3.1 img twrp and take all your data backup,
in fastboot flash latest miui do not downgrade direct otherwise you lost your data,
after this if you sucess then you can flash your old rom which is running before issue of boot loop of redmi logo
it will deincrypt your data safely and then root device and boot normally, if you lost anything then contact me with mail or whatsapp i will help you,7009197673 india
and this twrp work on all version from chines to global beta stable and indian stable
joke19 said:
Why nobody use orangefox?
Click to expand...
Click to collapse
In the end, I did try orangefox, and it might have been part of why it worked.
However, the crDroid installation instructions specifically mentions using Peter's TWRP, so I initially used that one.
anmoltinder said:
if your problem is not solve then tell me you need to flash a fastboot rom first with save user data.bat file and when it installed then you can install twrp builder 3.2.1. and then boot to twrp this methods working fine,if you recently flashed any android 10 rom then first you need to flash a miui fastboot rom,or flash it via command mode direct only 3 files
Click to expand...
Click to collapse
Thank you for the effort you put into typing up a guide to help me, but I ended up fixing my own problem.
I was able to use fastboot to flash on a better TWRP release, and then get the rom to install properly by installing fcrypt-disabler just after it.
Sanarise said:
Today I tried to finally update to the latest version of crDroid, but ended up having a bunch of issues doing so, and after a lot of troubleshooting and trying to fix it, I ended up putting it into a bootloop of some sort instead.
I'm pretty sure the last thing I tried was installing a different version of TWRP to see if that version would let me properly install the rom, and stop my phone from always rebooting into recovery mode.
Trying to turn it on normally or boot into TWRP leaves it hanging on the "Redmi" boot screen, it can boot into fastboot mode though.
I'm guessing that the only way to recover my phone at this point is to flash the Official MIUI rom back onto the phone, but that also involves wiping Data and losing pretty much everything I've put on the phone.
I was smart enough to make a TWRP of the Data folder, but while making the backup, the console said it doesn't include all personal files or something.
How much of my personal data and files can I rescue from the phone in this state, and how can I do that before it gets wiped when fixing it?
Also, I think I really need some help in actually restoring my phone and flashing the custom rom properly.
No matter how much effort I put into figuring out how to do this stuff, unexpected issues always seem to happen, and turns something that initially seemed so simple into multiple hours of troubleshooting.
The only way I think i've gotten rom flashing to work at all was by wiping everything and installing the official MIUI rom, but I don't want to be losing my data every month when an update comes out.
So, could someone please help me get my phone working again?
Edit: I ended up fixing my own issue by ADB flashing on a different release of TWRP, and then installing fcrypt disabler after the rom but before everything else.
Click to expand...
Click to collapse
help.I woke up yesterday and I turned on my phone and it is stuck on the Mi logo.All i can do is get it to fastboot thing.It seems like you and I have the same problem and I would love to have some help from you
Fcsubxrhi said:
help.I woke up yesterday and I turned on my phone and it is stuck on the Mi logo.All i can do is get it to fastboot thing.It seems like you and I have the same problem and I would love to have some help from you
Click to expand...
Click to collapse
If you can access fastboot, then flash TWRP.... Enter recovery, wipe your system partitions and then flash the Stock MIUI ROM or use the MiFlash tool. Make sure you aren't flashing an older version of the ROM than the onle already installed.
CongestedHangman said:
can u boot into twrp?
if u can boot, while in twrp, connect your phone via usb cable to pc. u can copy everything on pc
Click to expand...
Click to collapse
I have the same problem that stated after installing the update for derpfest and I can boot into twrp. Any solution for me?