help! can't boot and twrp asking for pword - Nexus 5 Q&A, Help & Troubleshooting

so i have been using multirom and reflashed a rom to my internal rom. then i rebooted it and it is stick with a blank screen after the "google" logo and stuck there. when i go to twrp, it prompts me for a password that i have not set. I have read that this happens if you dont reboot after unlocking but i did that when i first unlocked the bootloader and have never ran into any problems flashing many roms till now. any ideas???

onecrzyasian said:
so i have been using multirom and reflashed a rom to my internal rom. then i rebooted it and it is stick with a blank screen after the "google" logo and stuck there. when i go to twrp, it prompts me for a password that i have not set. I have read that this happens if you dont reboot after unlocking but i did that when i first unlocked the bootloader and have never ran into any problems flashing many roms till now. any ideas???
Click to expand...
Click to collapse
Did u try to wipe "format data" as explained by Dess_Troy?

This happened to me too when I flashed a kernel without making sure it was correct for the rom I was running. I just forced it to reboot into recovery and it turned out fine. Have you tried that?
Sent from my Nexus 5 using Tapatalk

If you have just used fastboot oem unlock, you should let the device boot up normally first before trying to install TWRP. If you boot TWRP first before booting normally, you will be prompted for a password. Hit cancel and got to Wipe -> Format Data. Type yes at the prompt and hit the "enter" key. Hit the home button at the bottom and Reboot -> Recovery. Unlocking the device will cause you to lose all userdata, apps, pictures, downloads, etc.
Click to expand...
Click to collapse
Source: http://www.teamw.in/project/twrp2/205
It'll be ok

This has happened to me a couple times, all I had to do was hit cancel and it went into recovery, no password needed. Just needed to reflash Multirom.

hmm wonder if i could have reflashed the multirom. cuz when i tried to reflash roms or try to flash another roms or anything, it wouldn't work. said the files were all encrypted. under the file manager, there was no accessible or viewable files. completely locked out. I ended up doing a back up by going into bootloader and pulling files to my desktop then did a stock flash.
as for the reformatting, i've shouldn't/wouldn't want to do that because i have already unlocked the bootloader, did the fastboot reboot and flashed countless roms and kernels. I think there was some sort of corruption that screwed with something. And i really didn't want to lose all my data be reformatting it.
only booting into recovery and clicking cancel when prompted password made me completely locked out. said that everything was encrypted so i was out of luck.

Related

[Q] Why won't my NS4G boot into recovery but boots fine into System?

My apologies if this post is not in the correct formatting or location.
A couple of days ago I flashed the Euroskank release of CM10 (10-20120816-UNOFFICIAL-crespo4g, to be exact) and after that, I have not been able to boot into recovery either from the power button's reboot menu or booting into the bootloader then recovery.
When I tried with both methods, I was presented with a completely blank screen and lit up, unresponsive capacitive keys. This state ususally persists for two minutes before shutting down and booting, normally, into the system where everything works as it should. Another forum post suggested using strong ambient lighting to see the standard onscreen options but my screen is completely blank.
I tried to reinstall the recovery with Rom Manager, which yielded the same result, and with fastboot, both flashing the recovery over the existing one and erasing the recovery partition and then flashing it.
I then thought to flash TWRP as it might have been a problem with CWM recovery. Once I flashed TWRP and booted into recovery, I was shown the standard TWRp splash screen for two minutes before the phone rebooted into the system.
I'm thinking there might be a problem with the unlocked state of my phone, even though it is OEM unlocked and there hasn't been any problems before.
I don't know how to fix this. Any help would be greatly appreciated!
[SOLVED]
It appears that the only way to fix this problem is to relock the device using fastboot and then to unlock it using the same method.
First of all backup everything you need.
1st method: try flashing a different rom, especially a stock one would be great, probably that does the trick.
If the first one doesnt help ypu can lock and unlock your phone again, since the unlocking procedure sets everything to default parameters.
Please report back, I'm curious.
miklosbard said:
First of all backup everything you need.
1st method: try flashing a different rom, especially a stock one would be great, probably that does the trick.
If the first one doesnt help ypu can lock and unlock your phone again, since the unlocking procedure sets everything to default parameters.
Please report back, I'm curious.
Click to expand...
Click to collapse
Thanks for the response!
Unfortunately, I'm unable to make a nandroid backup, as well as flashing any roms, since recovery is completely inaccessible. I am forced to rely entirely on Titanium backups and SMS backup. However I will relock and unlock in a bit once I'm sure no one is going to contact me.
Have you tried booting into recovery through ROM manager?
Sent from my Nexus S using Tapatalk 2

Phone Won't Turn On; Soft Keys Flashing When Buttons Are Pressed

Hi all,
So, last night I successfully rooted and unlocked my One X on AT&T. Today, I tried putting a ROM on it. I flashed the boot.img first, then tried to install the ROM (Jelly Bean Sense). It failed for some reason, so I wiped and rebooted my phone.
Instead of going back to the stock ROM, the phone now will not turn on, is not recognized on both laptops I tried, and does not recognize even being charged. The only thing that happens is when I press down the power button, all of the soft keys illuminate and flash until I stop holding it. I've managed to get into the bootloader screen once, but the phone reset itself before I could do anything.
The only screen I can get to with the Vol Down+Power combo is the HTC Screen, but it's the one that shows before my custom recovery, with some warning from HTC in red letters at the bottom.
At this point, I just want a phone that works. This is a lot more complex [for me] than rooting and flashing a ROM to the Inspire I had for some reason. I fly out for vacation in two days for a few weeks, so I'd like to be able to avoid having to send this thing back to HTC or AT&T if possible.
ANY help is greatly appreciated.
If it's easier, feel free to Skype chat me.
Thanks!
Im confused.. it won't come on, but you can get to recovery? If you can manually boot into twrp you'll be fine.. may I ask which Rom you flashed? Did you flash the boot.img first? Or after you flashed Rom? Alot of guys will say flash boot.img first.. I don't have that funky hboot but I have to do my cousins alot and his will only boot correctly if I flash Rom first, then boot into bootloader and fastboot the boot.img.
Try that and let me know how it goes
Also... Let go of all the buttons when you see the white screen lol. That means you found bootloader
Sent from my HTC One XL using Tapatalk 2
InflatedTitan said:
Im confused.. it won't come on, but you can get to recovery? If you can manually boot into twrp you'll be fine.. may I ask which Rom you flashed? Did you flash the boot.img first? Or after you flashed Rom? Alot of guys will say flash boot.img first.. I don't have that funky hboot but I have to do my cousins alot and his will only boot correctly if I flash Rom first, then boot into bootloader and fastboot the boot.img.
Try that and let me know how it goes
Also... Let go of all the buttons when you see the white screen lol. That means you found bootloader
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
I can get it to boot into the Bootloader screen and the TWRP now just fine, but that's as far as it will go. The internal SD will not mount with TWRP either now.
Here's the ROM I tried to flash: http://forum.xda-developers.com/showthread.php?t=2055490
I put it on my SD card, then extracted the boot.img to the folder I have my dab/fastboot files in, then flashed the boot.img, then tried to flash the ROM.
If I can get it working again, I'll try to do it in reverse order next time and see if that works. Still trying to find a way to get a ROM on here with my Mac, and to make my SD card work again. Everything on it is backed up so it's ok if I need to wipe it.
If you can get to bootloader, you're not bricked. It's just a matter of flashing the right stuff in the right order.
It could be that your sdcard is corrupted. Factory reset from bootloader will do it, but fixing it just a matter of formatting it again. Can you mount it on your computer? What happens when you plug into your PC?
Your sdcard is corrupt. No big deal but you'll lose everything. Plug it in into computer and locate the storage and try to find a way to format it. Sorry, I have no clue with a mac I swore off apple products :thumbup:
Anyway, you seem to know the ropes for the most part. If you can format, drag Rom onto SD. Wipe everything in twrp. Cache, dalvick, factory reset, system. Flash Rom.. immediately boot into bootloader and fastboot the boot.img. choose reboot from bootloader. Good luck!
Sent from my HTC One XL using Tapatalk 2
Yep, I also suggest doing a factory reset from the bootloader ( which will erase your internal storage) but at least you'll be able to mount your SD card, put a ROM on it and flash it. I would highly recommended you to flash viper 3.0.0, you don't need to flash the boot.img and its pretty much stock JB with some tweaks.
Sent from my HTC One XL using Tapatalk 2
I am having this same problem (minus the custom screen).
My phone will boot into TWRP and all, but it won't mount (PC says the disk needs to be formatted before it can be used). When I go to reboot or anything from TWRP, it tells me there is no OS installed and am I sure.
Can anyone help?
That's good news!
I tried doing a factory reset from bootloader, but nothing happened. Maybe because the SD card won't mount?
I only have a Mac, with no PC in sight. It doesn't show up at all on here. Fastboot USB, or when I mount it as USB in TWRP. It does however show up as a device in recovery in terminal. But nothing on the desktop. Apple+Android do not mix well!
I'm ok with losing my data, what I'm not OK with is having to use this pink Razr while my nice phone is broken :'(
Thanks for all the help so far!
I do a factory reset from bootloader, it takes me into TWRP. Now is the only time it will even remotely show up on my laptop, and even then it's only via terminal when I do adb devices. Since it can't mount for some reason, is there a way to reformat via Terminal, and maybe even push the ROM to my phone from there? That's something I'm not familiar with.
elijahpr said:
I do a factory reset from bootloader, it takes me into TWRP. Now is the only time it will even remotely show up on my laptop, and even then it's only via terminal when I do adb devices. Since it can't mount for some reason, is there a way to reformat via Terminal, and maybe even push the ROM to my phone from there? That's something I'm not familiar with.
Click to expand...
Click to collapse
Format your sd..drag Rom..wipe..flash..enjoy
omario8484 said:
Format your sd..drag Rom..wipe..flash..enjoy
Click to expand...
Click to collapse
I can't format because it doesn't show up on my computer, and doing so in bootloader takes me to TWRP.
emylibef said:
I am having this same problem (minus the custom screen).
My phone will boot into TWRP and all, but it won't mount (PC says the disk needs to be formatted before it can be used). When I go to reboot or anything from TWRP, it tells me there is no OS installed and am I sure.
Can anyone help?
Click to expand...
Click to collapse
Hey dude, I followed their advice (dug out my XP machine) and now my SD card is re-formatted.
Get into the bootloader screen, hit factory reset. (When I did this on mine, it took me right to TWRP)
From there, I mounted as USB and it showed up as needing to be reformatted on my XP machine. Took a few minutes to do on this dinosaur, but it worked, cause everything is gone!
Right now I'm in the process of zipping up the Viper XL ROM (thanks for the recommendation barondebxl, it looks awesome!), which I'll put onto my SD card and wipe/flash from there. (on my Mac now).
Hopefully it works!
I'm unable to flash ROMs for some reason. It doesn't give an error, just says that it failed. Any ideas?
elijahpr said:
Get into the bootloader screen, hit factory reset.
Click to expand...
Click to collapse
No no no. This is what is corrupting your sdcard. Only do a factory reset in TWRP or once booted up. Start over and format again. Then copy over your rom.
When you and a few others mentioned doing it, what were you referring to?
I've tried three different ROMs now, and each fails without saying why in TWRP.
Problem solved! Got the stock RUU back on there and it works perfectly. Just re-rooted and unlocked again. Round two..

Root = bootloop on 5.0.1

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.

XT1033 - Something that i haven't seen in forever.

Hi, guys.
I picked this xt1033 and it had the microusb input damaged, so i replaced it, but since then, it got stucked on motorola logo.
I guessed that the system got corrupted and then i uploaded some new system. It went through nicely, but when it rebooted got stucked again. So, i'ved unlocked it bootloader (to start from zero) and re-locked it, putting a new system from the ground and apparently it ended well, but it got stucked again on logo (and later i've founded that it didn't lock). I've begin to put TWRP to install a custom rom on it (to see if i've could pass throgh that) and founded that my files was still there (EVEN AFTER I'VE UNLOCKED THE BOOTLOADER, who would've erased everything from inside), system, images and even whatsapp files. MTP Service give-me a taste of what was inside and everything was there, nothing corrupt.
So i'ved erased it and put a new rom, TWRP said it did it and was asking for reboot, so i did.
And it got stucked again and nothing was erased.
So the thing is, it's internal storage is freezed and i can't do anything with it.
Could you guys help me? Thanks in advance.
i may be wrong here... but i dont remember unlocking bootloader erased my data.... but it was long time ago...
coming back to your problem.. have you tried using repair option in twrp?
also try wiping all partitions and do a recovery reboot to see if it works
access_unlimited said:
i may be wrong here... but i dont remember unlocking bootloader erased my data.... but it was long time ago...
coming back to your problem.. have you tried using repair option in twrp?
also try wiping all partitions and do a recovery reboot to see if it works
Click to expand...
Click to collapse
Already done.
I could only enter TWRP by boot it on bootloader, not flashing ('cuz was impossible to write on memory and was saying that the flash was successful).
TWRP said it wipe it completely without any error, but it's was there.
And by ordering to reboot on Recovery Mode, it went back to original recovery and trying to erase from there do the same thing (said that was complete, but everything is still there).
Same problem here, this is a problem with emmc bricked

BLN-L24 - Noob friendly guide for upgrading to EMUI 8/rooting/OpenKirin rom install?

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?

Categories

Resources