Related
Please dont reply harshly or bump me, I just got this account to ask for help here so i dont know all the rules and im not that tech savvy, anyways: So I had the newest oxygen os, then I rooted, installed twrp, unlocked bootloader, flashed Hydrogen Os all successfully. Then it became a hassle and I wanted to unroot and revert to 100% stock. So, I downloaded the stock firmware for Oxygen Os, Then I unrooted through Superuser, then went into recovery, wiped cache/dalvik/data, then flashed stock firmware. HERE'S WHERE THE PROBLEM STARTS, it first went into a bootloop, so I restarted it, then it booted successfully and i set it all up with a pin and fingerprint. Anyways, so once I got in, I wanted to relock the bootloader so i went into the settings, disabled the "oem unlock option", turned off my phone, went into fastboot, then typed "fastboot oem lock" and relocked the bootloader. THE REAL PROBLEM IS HERE: When I turned on my phone again and it booted, an all black screen came up that said "To start android please enter your password" so I entered the pin I set earlier, and it was wrong. No matter what i entered it said I was wrong. So, I shut off my phone and tried to go into recovery, and instead the OnePlus logo flashed then the phone turned off. So I went into fastboot and tried to wipe the data but it said partition erase is not allowed, then I tried to flash the stock and twrp and both times it said it failed too saying partition flashing is not allowed. So 1. I can't flash anything or wipe anything because its not allowed. 2. I cant get into android because it says my password is wrong. 3. I cant get into recovery because the Oneplus logo just flashes then phone turns off. PLEASE HELP ME THIS IS THE ONLY PHONE I HAVE!!!!
You should try Fastboot EDL. search Google. Good luck
scottwitha5 said:
Please dont reply harshly or bump me, I just got this account to ask for help here so i dont know all the rules and im not that tech savvy, anyways: So I had the newest oxygen os, then I rooted, installed twrp, unlocked bootloader, flashed Hydrogen Os all successfully. Then it became a hassle and I wanted to unroot and revert to 100% stock. So, I downloaded the stock firmware for Oxygen Os, Then I unrooted through Superuser, then went into recovery, wiped cache/dalvik/data, then flashed stock firmware. HERE'S WHERE THE PROBLEM STARTS, it first went into a bootloop, so I restarted it, then it booted successfully and i set it all up with a pin and fingerprint. Anyways, so once I got in, I wanted to relock the bootloader so i went into the settings, disabled the "oem unlock option", turned off my phone, went into fastboot, then typed "fastboot oem lock" and relocked the bootloader. THE REAL PROBLEM IS HERE: When I turned on my phone again and it booted, an all black screen came up that said "To start android please enter your password" so I entered the pin I set earlier, and it was wrong. No matter what i entered it said I was wrong. So, I shut off my phone and tried to go into recovery, and instead the OnePlus logo flashed then the phone turned off. So I went into fastboot and tried to wipe the data but it said partition erase is not allowed, then I tried to flash the stock and twrp and both times it said it failed too saying partition flashing is not allowed. So 1. I can't flash anything or wipe anything because its not allowed. 2. I cant get into android because it says my password is wrong. 3. I cant get into recovery because the Oneplus logo just flashes then phone turns off. PLEASE HELP ME THIS IS THE ONLY PHONE I HAVE!!!!
Click to expand...
Click to collapse
Give this thread a read.
http://forum.xda-developers.com/showthread.php?t=3405700
Several people have had success reviving their OP3. Also, there is an option to contact OnePlus support and have a remote session with their tech support. They will send you an email with files to download and will walk you thru what you need to do for them to unbrick your device.
Sent from my Nexus 6 using XDA-Developers mobile app
Try reflashing stock firmware with fastboot.
fast69mopar said:
Give this thread a read.
http://forum.xda-developers.com/showthread.php?t=3405700
Several people have had success reviving their OP3. Also, there is an option to contact OnePlus support and have a remote session with their tech support. They will send you an email with files to download and will walk you thru what you need to do for them to unbrick your device.
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Windows wont install the drivers on the thread so i cant proceed and the next available date for Oneplus tech is July 24th this is so urgent....any other options?
Nv1dia said:
Try reflashing stock firmware with fastboot.
Click to expand...
Click to collapse
I cant because says flashing isnt allowed
scottwitha5 said:
Please dont reply harshly or bump me, I just got this account to ask for help here so i dont know all the rules and im not that tech savvy, anyways: So I had the newest oxygen os, then I rooted, installed twrp, unlocked bootloader, flashed Hydrogen Os all successfully. Then it became a hassle and I wanted to unroot and revert to 100% stock. So, I downloaded the stock firmware for Oxygen Os, Then I unrooted through Superuser, then went into recovery, wiped cache/dalvik/data, then flashed stock firmware. HERE'S WHERE THE PROBLEM STARTS, it first went into a bootloop, so I restarted it, then it booted successfully and i set it all up with a pin and fingerprint. Anyways, so once I got in, I wanted to relock the bootloader so i went into the settings, disabled the "oem unlock option", turned off my phone, went into fastboot, then typed "fastboot oem lock" and relocked the bootloader. THE REAL PROBLEM IS HERE: When I turned on my phone again and it booted, an all black screen came up that said "To start android please enter your password" so I entered the pin I set earlier, and it was wrong. No matter what i entered it said I was wrong. So, I shut off my phone and tried to go into recovery, and instead the OnePlus logo flashed then the phone turned off. So I went into fastboot and tried to wipe the data but it said partition erase is not allowed, then I tried to flash the stock and twrp and both times it said it failed too saying partition flashing is not allowed. So 1. I can't flash anything or wipe anything because its not allowed. 2. I cant get into android because it says my password is wrong. 3. I cant get into recovery because the Oneplus logo just flashes then phone turns off. PLEASE HELP ME THIS IS THE ONLY PHONE I HAVE!!!!
Click to expand...
Click to collapse
Anybody?? Please help
scottwitha5 said:
Anybody?? Please help
Click to expand...
Click to collapse
Update: I followed the Mega Unbrick Guide for a hard bricked Oneplus 3, and now instead of even starting android, this appears, and I cant get into recovery or flash anything because it isnt allowed....please help me
I think your error was to relock the bootloader because if it was still unlocked, you could still reflash the boot.img (but your relocked your bootloader)
Solving it.
Don't worry I shall help you.
This happened to me too.
http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
To get the drivers and adb along with twrp and root use this toolkit.
http://forum.xda-developers.com/oneplus-3/development/toolkit-oneplus-3-toolkit-unlock-t3398799
Get the Oneplus drivers through this too.
It's not very complicated but ask me for any help.
Use the Method 2 in the Mega UnBrick Guide and download the stock image on to it.
You will lose data all of it.!
Make it boot.
Then tick OEM unlocking
Unlock bootloader through the toolkit.
flash twrp and root done..!!.
You messed up when you ticked off OEM unlocking and fastbooting it.
I purchased a 5x for my wife so she can get on Project Fi. They said it was stuck boot looping, thinking I could solve the problem.
Here are the basics.
-Yes, I can get into boot loader (the menu of start, recovery, etc), but I can't get into TWRP. Tried flashing TWRP a few times and nothing. SkipSoft recognizes that its installed though.
-After bootlooping for awhile, it will load normally and work fine. However it wants to update to the newest version of android. I run the ota and back to bootlooping. It will show the android dude and say "error". Will eventually start bootlooping and then boot normally.
-I have flashed different stock versions. I tried the newest, the second to newest and the last M available. All will flash but continue the bootlooping.
Bootlooping can be anywhere from 1 minute to 10+.
The device will also first display something like, "Your device software can't be checked for corruptions. Please lock the bootloader"
But it'll show up whether the bootloader is locked or not.
The phone will freeze at some point. Whether right away or after 5 minutes. It freezes and then restarts and goes through the bootloop again.
So what else can/should I do? I've never dealt with Kernels but wondering if the last owner did something to them. Is there a way to flash stock kernels just incase or is this done when I flash a Google Factory Stock Image?
Would flashing a non-stock rom be a good idea?
Thanks
So I tried sideloading. I was able to get into the stock recovery. I tried wiping cache and data, then tried installing the newest stock rom.
Everything seemed to work. Then I had to restart. A message popped up after the same "Your device software can't be checked for corruptions. Please lock the bootloader". It had the title in blue stating "Encryption unsuccessful".
Then said, "Encryption was interrupted and can't complete. As a result, the data on your phone is no longer accessible. To resume using your phone you need to perform a factory reset. When you set up your phone after the reset, you'll have an opportunity to restore any data that was backed up to your Google Account."
Then there is a single button that says, "Reset Phone".
Problem still persists.
Help please...
Why did you bought a bootlooped phone?
Sin Stalker said:
I purchased a 5x for my wife so she can get on Project Fi. They said it was stuck boot looping, thinking I could solve the problem.
Here are the basics.
-Yes, I can get into boot loader (the menu of start, recovery, etc), but I can't get into TWRP. Tried flashing TWRP a few times and nothing. SkipSoft recognizes that its installed though.
-After bootlooping for awhile, it will load normally and work fine. However it wants to update to the newest version of android. I run the ota and back to bootlooping. It will show the android dude and say "error". Will eventually start bootlooping and then boot normally.
-I have flashed different stock versions. I tried the newest, the second to newest and the last M available. All will flash but continue the bootlooping.
Bootlooping can be anywhere from 1 minute to 10+.
The device will also first display something like, "Your device software can't be checked for corruptions. Please lock the bootloader"
But it'll show up whether the bootloader is locked or not.
The phone will freeze at some point. Whether right away or after 5 minutes. It freezes and then restarts and goes through the bootloop again.
So what else can/should I do? I've never dealt with Kernels but wondering if the last owner did something to them. Is there a way to flash stock kernels just incase or is this done when I flash a Google Factory Stock Image?
Would flashing a non-stock rom be a good idea?
Thanks
Click to expand...
Click to collapse
When my Nexus 5x got into bootloop, I sent it to LG and they had to change the whole circuit. So yeah.
When you flash Google Factory Image, it flash the stock kernel.
If you have warranty, then send it to Google/LG. If you haven't got, then you're in problem. New motherboard needed, but it's expensive.
See the following thread for more info.
https://forum.xda-developers.com/nexus-5x/help/5x-bootloop-cause-fix-t3476794/
khalifakk said:
Why did you bought a bootlooped phone?
Click to expand...
Click to collapse
Cause its cheaper.
Sin Stalker said:
Cause its cheaper.
Click to expand...
Click to collapse
Then face the consequences...
khalifakk said:
Then face the consequences...
Click to expand...
Click to collapse
What consequences?
Hardware bootloop can't be fix by software.
Duckscreen said:
Hardware bootloop can't be fix by software.
Click to expand...
Click to collapse
Exactly. Everyone has either been able to get a replacement under warranty or was pretty much screwed if it was out of warranty.
Sent from my Nexus 5X using Tapatalk
Sin Stalker said:
What consequences?
Click to expand...
Click to collapse
A bootlooped phone for ever....
I recommend you will install kernel adiutor app after try rooting
I recommend you will install kernel adiutor app after try rooting
Almost I got no bootloop even no random reboot nexus 5x's state
I'm trying to prevent having to use the warranty if I don't have to as this was just a mistake on my part.
I've tried going completely back to stock removing TWRP and everything and I'm in the stock recovery right now with the error that says:
"Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory reset and erase all user data stored on this device."
Which I've done twice now (since going back to stock bootloader) and nothing happens.
These are the steps I took-
downloaded factory ota image.
flashed flash-all.bat
moved boot.img to adb directory and flashed boot image on both a & b slots
ran flash-all.bat again (just in case)
start up & get the loading G screen that either never stops loading or refreshes to this screen with the error above.
I tried locking the bootloader and that just caused a "no os" error. So I unlocked it, re-ran flash-all.bat and now I'm back with this error. I mean at least I can get into the bootloader & recovery?
I'm going to try pressing the 'try again' about 20 times in a row. I saw something online that said pressing try again that many times it randomly worked. I'm still searching and trying to figure this out but that is going to be my next step while I search.
I posted this on reddit about an hour ago but still no responses so I wanted to reach out here as well.
Just for more information: I am able to get into stock recovery & bootloader just fine. It is just the OS that doesn't want to load. I have factory reset this thing more times than I can count. I've tried flashing the images google has up. I did the very first one and the 8.1.0.
Neither are working & I don't understand why. The ones that are listed here.
Just for kicks here is a screenshot of the whole window and what happens during the flashing in the flash-all.bat. Here they are.
HELP?
While I was doing those screenshots I fixed it! I downloaded 8.1.0 (OPM1.171019.011, Dec 2017) just for the heck of it since the others weren't working. Figured it wouldn't hurt anything, would just cause the same error to appear and it took longer to install, which I figured was good, AND NOW I WAS ABLE TO GET INTO THE STARTUP SCREEN! WOO!
DudeThatsErin said:
I'm trying to prevent having to use the warranty if I don't have to as this was just a mistake on my part.
I've tried going completely back to stock removing TWRP and everything and I'm in the stock recovery right now with the error that says:
"Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory reset and erase all user data stored on this device."
Which I've done twice now (since going back to stock bootloader) and nothing happens.
These are the steps I took-
downloaded factory ota image.
flashed flash-all.bat
moved boot.img to adb directory and flashed boot image on both a & b slots
ran flash-all.bat again (just in case)
start up & get the loading G screen that either never stops loading or refreshes to this screen with the error above.
I tried locking the bootloader and that just caused a "no os" error. So I unlocked it, re-ran flash-all.bat and now I'm back with this error. I mean at least I can get into the bootloader & recovery?
I'm going to try pressing the 'try again' about 20 times in a row. I saw something online that said pressing try again that many times it randomly worked. I'm still searching and trying to figure this out but that is going to be my next step while I search.
I posted this on reddit about an hour ago but still no responses so I wanted to reach out here as well.
Just for more information: I am able to get into stock recovery & bootloader just fine. It is just the OS that doesn't want to load. I have factory reset this thing more times than I can count. I've tried flashing the images google has up. I did the very first one and the 8.1.0.
Neither are working & I don't understand why. The ones that are listed here.
Just for kicks here is a screenshot of the whole window and what happens during the flashing in the flash-all.bat. Here they are.
HELP?
While I was doing those screenshots I fixed it! I downloaded 8.1.0 (OPM1.171019.011, Dec 2017) just for the heck of it since the others weren't working. Figured it wouldn't hurt anything, would just cause the same error to appear and it took longer to install, which I figured was good, AND NOW I WAS ABLE TO GET INTO THE STARTUP SCREEN! WOO!
Click to expand...
Click to collapse
You tried fastbooting the "factory OTA image" Well, that mistake number one. Just use the stock factory image, not the OTA.
Never mind.?
Congrats on fixing it.
For future reference, and if you ever reset your phone again, you should perform: fastboot flashing unlock_critical <--this will wipe your phone!
As you can see in your screenshots, that failed, each time. This was the cause of your failure(s): FAILED (remote: Flashing is not allowed for Critical Partitions)
The last one worked because it flashed the proper bootloader (TMZ12a). Had you not used that image, it still would have failed.
What was your fix?
@DudeThatsErin -As mentioned by uicnren, you still need to unlock_critical or your phone will not upgrade properly, and you won't be able to flash full factory images. When you unlocked your bootloader, there were two steps but you only completed the first one. See the sticky by Nathan for step-by-step instructions. Unlocking critical will wipe the phone again, but then you will be set.
I've had Google phones for years now, including previous Pixel, but I just got an XL 2 yesterday and I'm regretting it.
It's Google unlocked and running June's latest image. I've experienced various app crashing on stock, and random reboots.
Then there's the rooting and flashing. I unlocked the bootloader and installed the most recent, twrp (the one verified to work on xda for roms) but can't flash anything.
My twrp either hangs on the twrp start screen, or when it does load, the touch screen doesn't work. When I can get it going, every rom I flash gives me an error on the second step. I'm flashing on slot B by the way, that's what boots up when I boot to twrp.
Lastly, I am unlocked both for flashing and flashing_critical thru adb, so I'm at a loss and seriously confused.
When I FIRST unlocked everything, I was able to flash Nitrogen rom but I got stuck at the rom splash screen.
Tldr:
-What is the Correct install method/sequence for roms?
-do the slots matter?
-is random reboots and app crashing on stock a sign of a hardware issue?
I haven't installed a custom ROM on my P2XL, so I'm running rooted stock. Anyway, for rooted stock, this is what I did.
Entered bootloader mode.
Booted into recovery using the command "fastboot boot recovery.img", where "recovery.img" is the TWRP recovery iteslf. In my case, I renamed it "taimen.img".
Flashed the TWRP installer zip needed for the P2XL (Required if intending to replace the stock recovery).
Rebooted into recovery.
Flashed a custom kernel (Recommended - resolves touch issues in TWRP).
Flashed Magisk.
6. Rebooted.
If installing a custom ROM, flash it prior to the custom kernel. Slots only matter if running stock. Random reboots and app crashes are not signs of a hardware issue.
stevew84 said:
I've had Google phones for years now, including previous Pixel, but I just got an XL 2 yesterday and I'm regretting it.
It's Google unlocked and running June's latest image. I've experienced various app crashing on stock, and random reboots.
Then there's the rooting and flashing. I unlocked the bootloader and installed the most recent, twrp (the one verified to work on xda for roms) but can't flash anything.
My twrp either hangs on the twrp start screen, or when it does load, the touch screen doesn't work. When I can get it going, every rom I flash gives me an error on the second step. I'm flashing on slot B by the way, that's what boots up when I boot to twrp.
Lastly, I am unlocked both for flashing and flashing_critical thru adb, so I'm at a loss and seriously confused.
When I FIRST unlocked everything, I was able to flash Nitrogen rom but I got stuck at the rom splash screen.
Tldr:
-What is the Correct install method/sequence for roms?
-do the slots matter?
-is random reboots and app crashing on stock a sign of a hardware issue?
Click to expand...
Click to collapse
Ya know my friend, after our conversation yesterday, and your questions in the nitrogen thread, and now random reboots and app crashes, I think it's time to consider a factory reset. You shouldn't be having those problems on a stock setup. If that's not successful, then I would definitely consider an RMA. Just my 2 cents worth :good:
I agree. I got it used tho which is an issue.
Badger50 said:
Ya know my friend, after our conversation yesterday, and your questions in the nitrogen thread, and now random reboots and app crashes, I think it's time to consider a factory reset. You shouldn't be having those problems on a stock setup. If that's not successful, then I would definitely consider an RMA. Just my 2 cents worth :good:
Click to expand...
Click to collapse
Just so you know, I got the rom to flash finally, but it's stuck at the rom splash screen during first boot. I'm going to leave it and hope it eventually boots up.
stevew84 said:
Just so you know, I got the rom to flash finally, but it's stuck at the rom splash screen during first boot. I'm going to leave it and hope it eventually boots up.
Click to expand...
Click to collapse
If it doesn't after 5 minutes, do a hard restart with the power button. If that doesn't work, then reboot to twrp and flash the rom and twrp installer zip again.
Ok cool thanks. I relocked bootloader last night and went back to stock. Unlocked it all this morning from my work computer and different unlock app. So here's hoping.
Badger50 said:
If it doesn't after 5 minutes, do a hard restart with the power button. If that doesn't work, then reboot to twrp and flash the rom and twrp installer zip again.
Click to expand...
Click to collapse
I finally got everything to work. My vendor image is a mismatch but I could just flash junes and be done with it, right?
stevew84 said:
I finally got everything to work. My vendor image is a mismatch but I could just flash junes and be done with it, right?
Click to expand...
Click to collapse
What did you do to get it to work? You could just flash the June vendor.img to both slots. If you keep getting a vendor mismatch, probably nothing to worry about according to the Dev of nitrogen.
Different machine, cable and unlocking tool.
But I went to bone stock with locked bootloader, then flashed the newest twrp with the newest all in one tool. Was on slot A so wiped everything and flashed rom plus twrp again. I rebooted system to slot B, but then it just hung at the rom splash screen.
So I did it all over on slot A, ignored the "no os installed" message and booted anyway. Then it fired up. Rebooting into twrp from there took me to B, which is where I need to be for an image file or root.
So yea, thanks for the help.
I'm having this issue also. I tried flashing nitrogen, it hung. I tried to go back with factory reset Img and nothing happens in adb. Flashed the may img and it wouldn't boot all the way up. Now I'm stuck in bootloader trying to figure this all out. Seems like nothing in doing is working. I can get recovery to boot, but no files inside so idk. Tried to sideloadb nitrogen, but it said adb out of date for device when sdk is fully updated.
MatthewRobinson said:
I'm having this issue also. I tried flashing nitrogen, it hung. I tried to go back with factory reset Img and nothing happens in adb. Flashed the may img and it wouldn't boot all the way up. Now I'm stuck in bootloader trying to figure this all out. Seems like nothing in doing is working. I can get recovery to boot, but no files inside so idk. Tried to sideloadb nitrogen, but it said adb out of date for device when sdk is fully updated.
Click to expand...
Click to collapse
You didn't mention the out of date message in your other post, but uninstall SDK and then download the stand-alone adb/fastboot binaries from May of this year. Dump that in a folder (eg. c:\adb) and put that folder in your path statement. Manually flash the full factory image without modifying flash-all.bat. Post your screeen if you have any errors. :good:
stevew84 said:
I agree. I got it used tho which is an issue.
Click to expand...
Click to collapse
Google knows the date the phone was purchased based on imei number and honors their warranty by date, not owner. Unless it was blacklisted.
smartymcfly said:
Google knows the date the phone was purchased based on imei number and honors their warranty based on that.
Click to expand...
Click to collapse
Thanks. I might try to take advantage.
So, being the stupid person I am I broke my Mate SE one day after purchase ._. I'm posting my entire process just in case anything helps.
I started off by updating to the latest ROM and then unlocking the bootloader, which went fairly well, then flashed TWRP. A lot of versions I found didn't work(Bootloader says Func NO: 11 (recovery image) and Error NO: 2 (load failed!)), but I got a working version here: https://forum.xda-developers.com/honor-7x/development/oreo-twrp-complete-backup-t3764500 .
After that, I installed Magisk, which went well, then Xposed framework inside Magisk, which put my phone in a bootloop. I didn't know what to do, so I went with a factory reset[terrible idea]. Now, my phone has the FRP lock on, and the android setup is stuck on a "just a sec" page, right after selecting language and wifi, so I can't login to my google account to disable the FRP lock.
I tried flashing, but apparently the FRP lock stops me from being able to flash anything inside the bootloader. I do still have my TWRP recovery and a backup of the kernel and ramdisk(sadly nothing else useful, although I do also have dts, dfx, vendor_image, oeminfo and secure_storage) but restoring them or wiping the system again has no effect(still stuck on "just a sec").
After some google searching someone in a thread said that I should use stock recovery to wipe factory data(by restoring the stock recovery in TWRP), and I would be able to get past the "just a sec" problem, but I am reluctant because if it doesn't work, I would permanently lose my TWRP recovery with no way to flash it back(because of that FRP lock). I also tried installing update.app and other stock ROMs from various sources using TWRP, but all of them had a "check_write_data_to_partition, write data error" error. I'm not sure if it's related to FRP.
I think my next course of action is to either a) disable FRP in recovery, b) bypass the setup screen or c) install some ROM on it and somehow bypassing the check_write_data_to_partition error, but I'm not sure how to do any of these. Any ideas or suggestions? Thanks.
rkevin_arch said:
So, being the stupid person I am I broke my Mate SE one day after purchase ._. I'm posting my entire process just in case anything helps.
I started off by updating to the latest ROM and then unlocking the bootloader, which went fairly well, then flashed TWRP. A lot of versions I found didn't work(Bootloader says Func NO: 11 (recovery image) and Error NO: 2 (load failed!)), but I got a working version here: https://forum.xda-developers.com/honor-7x/development/oreo-twrp-complete-backup-t3764500 .
After that, I installed Magisk, which went well, then Xposed framework inside Magisk, which put my phone in a bootloop. I didn't know what to do, so I went with a factory reset[terrible idea]. Now, my phone has the FRP lock on, and the android setup is stuck on a "just a sec" page, right after selecting language and wifi, so I can't login to my google account to disable the FRP lock.
I tried flashing, but apparently the FRP lock stops me from being able to flash anything inside the bootloader. I do still have my TWRP recovery and a backup of the kernel and ramdisk(sadly nothing else useful, although I do also have dts, dfx, vendor_image, oeminfo and secure_storage) but restoring them or wiping the system again has no effect(still stuck on "just a sec").
After some google searching someone in a thread said that I should use stock recovery to wipe factory data(by restoring the stock recovery in TWRP), and I would be able to get past the "just a sec" problem, but I am reluctant because if it doesn't work, I would permanently lose my TWRP recovery with no way to flash it back(because of that FRP lock). I also tried installing update.app and other stock ROMs from various sources using TWRP, but all of them had a "check_write_data_to_partition, write data error" error. I'm not sure if it's related to FRP.
I think my next course of action is to either a) disable FRP in recovery, b) bypass the setup screen or c) install some ROM on it and somehow bypassing the check_write_data_to_partition error, but I'm not sure how to do any of these. Any ideas or suggestions? Thanks.
Click to expand...
Click to collapse
There is an unlock frp patch by a dev in another that works with the 7x. It should work for you too.
I will find link when I get off the road
mrmazak said:
There is an unlock frp patch by a dev in another that works with the 7x. It should work for you too.
I will find link when I get off the road
Click to expand...
Click to collapse
Link to frp unlock
https://mega.nz/#!nw0wAYoA!hYtf78s0AjwRCpPo_NQ2F4LYclngNBNurJNETypSNKQ
Posted many places. But I found it on the bottom of post 2.
Here.
https://forum.xda-developers.com/showpost.php?p=76398556&postcount=2
mrmazak said:
Link to frp unlock
https://mega.nz/#!nw0wAYoA!hYtf78s0AjwRCpPo_NQ2F4LYclngNBNurJNETypSNKQ
Posted many places. But I found it on the bottom of post 2.
Here.
https://forum.xda-developers.com/showpost.php?p=76398556&postcount=2
Click to expand...
Click to collapse
Thanks for the help! It worked, and the bootloader says FRP unlocked. It didn't help the "just a sec" issue, but since I can use fastboot flash, I might be able to flash a new rom in it and just ditch EMUI[probably]. I'll play around with it a bit. Again, thanks a lot for your help!
I got everything working now! Just in case anyone had the same "just a sec" issue: it was fixed by flashing stock recovery then doing a factory reset there(I'm not sure how that's different from wiping dalvik/cache/data/internal storage in twrp, but it makes a difference apparantly). Just flashing custom ROMs didn't solve the problem. After that I installed magisk, and then installed this version of xposed: https://forum.xda-developers.com/showpost.php?p=76582399&postcount=11 . I installed the v90-beta3 version before which caused the bootloop, but it is fixed in the next version. Magisk has some issues so the magisk manager can't start with internet(adb logcat says there's a NullPointerException in com.topjohnwu.magisk.database.RepoDatabaseHelper.removeRepo) but frankly I don't need to open it with internet anyways. Now I have everything I need on my new phone! Thanks to mrmazak for pointing me to the right direction.