Related
I am really needing some advise. I was having a funny pop up a couple of days ago on my OPO saying that google music has stopped. I am running the 33 update at this time rooted with twrp. So, I froze the app with titanium back up. I went to flash MAHDI rom right now and when I wiped the phone red lettering popped up saying E.error opening:/data/data/com.google.android.music:I/O error
But it said it wiped successfully. So I flashed MAHDI and gapps and when I booted I got this message unfortanutley the process android system has stopped, and under that was another message that said, system UIDs inconsistent you need to wipe your data partition or your device will be unstable
So I wiped everything again and still got the red lettering pop up. I tried restoring a previous back up and it fails. Now I am back in twrp but I am lost on what to do.
Is there a way just to flash back to stock? Is there a fix that anyone knows about? I highly appreciate any help. Thanks again!
I don't clearly understand your problem 100%, maybe its because its 3:05 AM and I have not gone to sleep yet.
1. Use TWRP -> Wipe -> Swipe
2. Flash Mahdi ROM, Gapps, Kernel (if you use one)
3. Reboot
4. You'll have a clean scratch.
You shouldn't be having any errors with a clean scratch. You probably didn't wipe correctly. You don't need to change any mount or wipe, the defaults will wipe it. But since you changed it, you need to reset it back.
Worst comes to worst if you really want to flash back to stock. Then look up on XDA about fastbooting back to stock.You can find the 33R Images https://cyngn.com/products/oneplusone/
zephiK said:
I don't clearly understand your problem 100%, maybe its because its 3:05 AM and I have not gone to sleep yet.
1. Use TWRP -> Wipe -> Swipe
2. Flash Mahdi ROM, Gapps, Kernel (if you use one)
3. Reboot
4. You'll have a clean scratch.
You shouldn't be having any errors with a clean scratch. You probably didn't wipe correctly. You don't need to change any mount or wipe, the defaults will wipe it. But since you changed it, you need to reset it back.
Worst comes to worst if you really want to flash back to stock. Then look up on XDA about fastbooting back to stock.You can find the 33R Images https://cyngn.com/products/oneplusone/
Click to expand...
Click to collapse
Thank you for your response! I tried doing the above by wiping but it would never boot up correctly. Always kept crashing on boot. I now wiped the whole phone and I am still in twrp but now everything is gone, including my nandroids, and all roms along with Mahdi. So, it looks like I will have to flash back to stock using fastboot mode.
I highly appreciate your help and I am glad to donate something. I don't mind buying lunch :good:
Are the images in a flashable zip or called a snapshot?
rayandreas said:
Thank you for your response! I tried doing the above by wiping but it would never boot up correctly. Always kept crashing on boot. I now wiped the whole phone and I am still in twrp but now everything is gone, including my nandroids, and all roms along with Mahdi. So, it looks like I will have to flash back to stock using fastboot mode.
I highly appreciate your help and I am glad to donate something. I don't mind buying lunch :good:
Are the images in a flashable zip or called a snapshot?
Click to expand...
Click to collapse
You don't need to go back to stock, alternatively, you can use adb sideload which will push the zip onto your phone and then proceed with a flash.
ADB Sideload is very easy to use, you go into recovery and plug your phone into your computer. Have adb environment set up (if you were going to fastboot, you'd need fastboot which would come with adb anyways) and then adb sideload the .zip over to your phone.
The images are in a flashable zip but thats for 25R which you will need to get yourself back up to 33R or you can fastboot flash 33R or flash a custom ROM of your choice.
zephiK said:
You don't need to go back to stock, alternatively, you can use adb sideload which will push the zip onto your phone and then proceed with a flash.
ADB Sideload is very easy to use, you go into recovery and plug your phone into your computer. Have adb environment set up (if you were going to fastboot, you'd need fastboot which would come with adb anyways) and then adb sideload the .zip over to your phone.
The images are in a flashable zip but thats for 25R which you will need to get yourself back up to 33R or you can fastboot flash 33R or flash a custom ROM of your choice.
Click to expand...
Click to collapse
Thank you very much for taking time to help me. Here is just a little something to show my appreciation. Confirmation number: 1JL24849R60212845
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.
Hi everyone, i've got my OPO when CM12 still wasn't a thing, and it always did his job wonderfully, i've updated to CM12 when it first came out, then updated it every time a new stable version was out, YNG1TAS2I3 version included (with root access and TWRP). A few days ago, while i was listening to some music with Google Play Music, the phone started to reboot itself for no apparent reason, and after around 10 reboots with random timings, i found out there was a problem with google play services, so i blocked them with Titanium Backup, deleted updates, updated them again, reactivated, and everything went fine.
Yesterday, my phone once again rebooted by itself, but every time it was rebooting, while showing the boot logo, it rebooted again without actually loading android. I first tried to wipe cache, then dalvik cache, then data and system partitions, factory reset, but it kept rebooting no matter what, until i tried to flash CM11S on it. After a few tries and total wipes, CM11S was running with no reboots, and it worked flawlessly, no root, no custom recovery, everything stock flashed from official fastboot images zip.
After that, i tried to update via OTA to the more recent versions of CM11S, no problems so far, but as soon as i updated to CM12 via OTA once again, the phone started to reboot itself after the update, it says "Upgrading Android" like when you wipe the dalvik-cache, and then it freezes for a second, then reboots.
Things i've tried so far:
full wipe and factory reset from TWRP
erase and flash again all partitions
erase and flash again persist partition
flash colorOS and then flash CM12
After flashing the persist partition it managed to work for a minute on CM12, but then it started rebooting itself again, and i've managed to save the last part of logat log , but i'm not sure if it's worth anything to find out the problem! (i can't post it on forum because of the new user link restriction, but if you want to have a look at it, let me know)
So, basically, my phone works only on android 4.x and not on 5.x, I would think some app on it can make it crash, but even after a full wipe it still behaves like this, what could be the reason and how can i try to fix it? thanks in advice!
I recommend you to flash fastboot images of CMOS12 without skipping any file
Steps to flash >> http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
xKylesx said:
Hi everyone, i've got my OPO when CM12 still wasn't a thing, and it always did his job wonderfully, i've updated to CM12 when it first came out, then updated it every time a new stable version was out, YNG1TAS2I3 version included (with root access and TWRP). A few days ago, while i was listening to some music with Google Play Music, the phone started to reboot itself for no apparent reason, and after around 10 reboots with random timings, i found out there was a problem with google play services, so i blocked them with Titanium Backup, deleted updates, updated them again, reactivated, and everything went fine.
Yesterday, my phone once again rebooted by itself, but every time it was rebooting, while showing the boot logo, it rebooted again without actually loading android. I first tried to wipe cache, then dalvik cache, then data and system partitions, factory reset, but it kept rebooting no matter what, until i tried to flash CM11S on it. After a few tries and total wipes, CM11S was running with no reboots, and it worked flawlessly, no root, no custom recovery, everything stock flashed from official fastboot images zip.
After that, i tried to update via OTA to the more recent versions of CM11S, no problems so far, but as soon as i updated to CM12 via OTA once again, the phone started to reboot itself after the update, it says "Upgrading Android" like when you wipe the dalvik-cache, and then it freezes for a second, then reboots.
Things i've tried so far:
full wipe and factory reset from TWRP
erase and flash again all partitions
erase and flash again persist partition
flash colorOS and then flash CM12
After flashing the persist partition it managed to work for a minute on CM12, but then it started rebooting itself again, and i've managed to save the last part of logat log , but i'm not sure if it's worth anything to find out the problem! (i can't post it on forum because of the new user link restriction, but if you want to have a look at it, let me know)
So, basically, my phone works only on android 4.x and not on 5.x, I would think some app on it can make it crash, but even after a full wipe it still behaves like this, what could be the reason and how can i try to fix it? thanks in advice!
Click to expand...
Click to collapse
1)Are u tried cm 12.1
after u flashing cm 12 then reboot and again go back to recovery and flash cm 12.1
2) try to use different kernels supporting to cm 12 like boeffla /AK etc
3) try to flash cm 12 firmware via fastboot flash installation process
Hi there, first post on here!
I've bought a nexus 5 off of eBay from some person who tried to root it and failed, thinking it would be an easy matter of restoring it.
However, the standard stock recovery process did not work, and I've encountered a number of issues:
When the device gets to erasing 'cache', it stays there for upwards of half an hour with no results.
With stock recovery flashed, pressing power + volUp immediately makes it erase /data, with no other options given.
It also does not show the stock recovery icon, instead a standing up android figure with a spinning poly in front of it.
Flashing TWRP and booting into recovery, it says 'e' is locked and goes into a boot loop.
Also no options in CWM recovery
I thought I would ask on here because it's out of my league now, I've tried on both windows and mac with no luck and I'm not sure what to try next, maybe just leave it until cache finally erases?
Thanks in advance!
You need to read read and read some more.
Start here:
http://forum.xda-developers.com/google-nexus-5/general/resource-guides-info-threads-linked-read-t2784527
It sounds like the bootloader is locked.
It's almost impossible to brick a nexus.
I've managed to get a version of CWM loaded.
Performing factory reset gives the error that /data cannot be mounted for wiping.
Bootloader is definitely open.
M1kesky said:
I've managed to get a version of CWM loaded.
Performing factory reset gives the error that /data cannot be mounted for wiping.
Bootloader is definitely open.
Click to expand...
Click to collapse
Ok :good:. That means you can install TWRP 3.0.
Try this: flash back to a completely stock MM or LP ROM by manually flashing each partition, inlcuding the userdata.img file. When you have finished flashing all partitions, boot directly to recovery from fastboot mode, perform a factory wipe, and reboot.
I've tried doing that but it just results in the standing up android icon, with power+up leading to it trying to wipe data again. no option to do a factory wipe.
I put TWRP 3.0.0 on just to test and ended up in a worse bootloop, which failed to load TWRP but occasionally got into it and displayed this:
imgur.com/RKyZIJf
Sorry as I am a new user it doesn't let me use links
audit13 said:
Try this: flash back to a completely stock MM or LP ROM by manually flashing each partition, inlcuding the userdata.img file. When you have finished flashing all partitions, boot directly to recovery from fastboot mode, perform a factory wipe, and reboot.
Click to expand...
Click to collapse
Thanks, I gave it another try and did the recovery partition last, and made sure I manually put it into recovery mode from bootloader.
The red triangle and recovery menu are back, I can't thank you enough!
Glad you got it to work. I suggest using TWRP 2.8.7.1. For some reason version 3.0 does not work properly with all N5 phones.
It's still happening.
I've been away for a few days so only had the chance to respond now.
I got into the ususal recovery screen as mentioned previously and tried to do a factory reset, but it had problems with /data again.
I left it the entire night while I slept and it was still saying formatting /data in the morning, nothing had changed.
Anybody got any more suggestions? It's also back to the android with the rotating poly instead of the android with the exclamation mark.
EDIT: when flashing userdata, no matter what version of android I try, it always hangs.
It started on 6.0.1 if that helps.
The userdata.img file is included with each stock rom. I advise against mixing userdata.img files from different stock ROMs.
Sorry, I mean that I've flashed completely whole different versions of android and the result is the same across all of them, not that I've used different userdata img's on the same version of android.
Could be an emmc problem which would require a motherboard swap.
Is that likely to happen when the previous owner said it was fine before they tried to root?
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?