Hi Guys,
I really need help here. I am using Huawei P9 EVA-L19.
I once unlocked bootloader, installed TWRP and rooted my phone. After 1 day I using it, I tried to flash to unofficial emui 5 which is follow the instruction from here; https://forum.xda-developers.com/p9/how-to/huawei-p9-eva-l19-android-7-0-nougat-t3532649
However, after I done flash it. I found out that there's a lot of application I can't access including my camera ( which totally gone from my phone ). I decided to flash back to emui 4.1.
The issue that I'm facing right now is, I can't even access to TWRP. I tried a lot of ways to install TWRP and try to boot. Nothing happen. I've tried to use Dload, I tried using CMD it seems never success.
Now, I really need someone to help me on this issue. I know there's a lot of people who facing the same issue that I'm facing right now. Or someone who already solve this issue please assist me. I'm already give up on this.
Thanks in advance.
Here's an attempted TLR of what has happened
Tried installing LineageOS. Got Error 7. Tried a bunch of things to make it work like editing the updater-script and things like that but it didn't work.
Then I simply wanted my phone to work again. Installed Clean Stock ROM + Stock Recovery straight out of OnePlus webpage. Now I have permanent dm-verity error (tried going back to 4.0.2, disabling dm-verity via fastboot commands and restoring 4.0.3) and still appears.
So yeah, basically that.
I messed up like a month ago too, bricked the OP3T and managed to revive it with a chinese program.
Any ideas on why I can never manage to install LineageOS?
EDIT: After the last factory reset, the phone wouldn't find any wifi network. After an hour or so, it found my wifi and got a 92mb update that fixed the dm-verity error
What firmware are you running and what's your Android version? If you're running 7.1.1 on 4.1.0 you should be good to go just by flashing all the latest LOS files
sakumaxp said:
What firmware are you running and what's your Android version? If you're running 7.1.1 on 4.1.0 you should be good to go just by flashing all the latest LOS files
Click to expand...
Click to collapse
I just received the 4.1.0, going to try again tonight. Hope it works
Okay.
So I have a Note 5 N920G. I'm 99% sure this is what the phone I have is, I bought this phone from Amazon India, pretty sure when I looked it up way back when, this was the one.
First ROM I ever installed was a Dr. Ketan Rom , Lollipop V8. I don't ever remember installing a BL/Modem for the same way back then.
Later I moved on to a Sick as Hell V3 Rom and I managed to get that installed just fine without getting a BL/Modem for the same as well.
**TODAY**
I have now tried to install the latest version of Dr Ketan's ROM N10 for my Note 5. It mentioned to install/upgrade the BL/Modem so I chose the one that is required for me phone, viz. the N920G BL/Modem.
Proceed to install. Rom installs just fine.
Proceed to reset/reboot. Get NOTHING. Stuck on an infinite loading screen.
Reboot phone, still nothing.
Get frustrated try to move to another ROM for the same phone in the same sub forum.
This one also has a Kernel and a CSC something that needs to be installed in order to try and boot this ROM. Proceed with everything and in order, no luck still....
NOW, even when I try to install the other ROMs, including Dr Ketan Roms or my previous Sick as Hell Rom that I was using earlier I am facing the error labelled :-
"set_metadata_recursive: some changes failed"
I just upgraded from TWRP 3.0.0.2 to the latest 3.1.1.X version that's out right now between these two installs (previous installation worked out just fine from what I can remember.)
I ALSO installed a new kernel since I was trying to install another rom when this one failed, and that rom required a kernel to be installed :-
https://forum.xda-developers.com/note5/development/7-0-khongloi-nougat-rom-aod-edge-t3580620
Now since flashing this kernel (I assume that is what is giving me all these issues) NO ROM is installing without giving me the error above of set metadata.
A quick google search says that I should update my recovery to the latest... But it IS! I upgraded to the current latest 3.1.1.X that I am supposed to have, that I found from their website.
I am so beyond frustrated at this point in time. Can someone please help me figure this out?
Honestly I am so ****ing done right now, I would Paypal you my appreciation if you can get me to install a new ROM after getting out of this mess.
Hey,
I have question about a problem I have.
So I tried to install the latest open beta version (beta 17) on my OnePlus 3T through TWRP.
This didn't worked because of ERROR: 7.
I found some solutions to fix ERROR 7 but it doesn't worked with this OS.
I tried some things like updating TWRP and installing the Oxygen recovery. I messed some things up. I deleted my OS from my device accidentally.
I solved the problem and was able to install the latest stable OS without problems.
Then I tried to install ResurrectionRemix-N for OP3T and I got the ERROR 7 again. but it said:
E3004: This package is for device: OnePlus3T, oneplus3t; this device is Oneplus3.
The thing is, it is an OnePlus 3T.
I don't know why and how it changed. The TWRP is for OP3T.
In the settings it says that the Build-Number is: ONEPLUS A3003_28_171012.
So I don't know. The default device name was OnePlus 3T.
Later I got an automatic email from Google because I logged in on an "new" device. But here they say that it is an OP3.
I would like to change it, but I don't know how.
I thought I can just change someting in the build.prop, but I didn't tried it yet.
Hopefully someone can help me.
-Fun4Jan
Okay so, I went in the build.prop and this is what I found:
ro.build.product=OnePlus3
ro.build.user=OnePlus
ro.build.flavor=OnePlus3-user
ro.build.description=OnePlus3-user 7.1.1 NMF26F 136 dev-keys
ro.common.soft=OnePlus3
ro.display.series=OnePlus 3T
ro.build.oemfingerprint=7.1.1/NMF26F/10122113:user/release-keys
[...]
ro.build.ota.versionname=OnePlus3TOxygen_28_1710122300
ro.build.version.ota=OnePlus3TOxygen_28.A.57_GLO_057_1710122300
So do you think I can just change it in the build.prop?
Yes, you can change it in the build.prop.
please try changing it and report us back.
akash.galaxy07 said:
Yes, you can change it in the build.prop.
please try changing it and report us back.
Click to expand...
Click to collapse
So I changed it and tried to install it but failed. It tells me that it is an OP3
Try the Qualcomm MSM Tool and try resetting your device completely as instructed on the Unbrick guide. Looks like you installed a corrupted Open Beta package, and something from Bootloader configuration went completely haywire. You can backup your Internal Storage since you have TWRP access.
Good Luck!
Have you tried using TWRP version 3.1.1-0?
Fun4Jan said:
So I changed it and tried to install it but failed. It tells me that it is an OP3
Click to expand...
Click to collapse
With oreo use this TWRP https://forum.xda-developers.com/devdb/project/dl/?id=27068
after flash again beta 17
przemcio510 said:
Have you tried using TWRP version 3.1.1-0?
Click to expand...
Click to collapse
I tried it with TWRP 3.1.1-2 for the OnePlus 3t
thes3usa said:
Try the Qualcomm MSM Tool and try resetting your device completely as instructed on the Unbrick guide. Looks like you installed a corrupted Open Beta package, and something from Bootloader configuration went completely haywire. You can backup your Internal Storage since you have TWRP access.
Good Luck!
Click to expand...
Click to collapse
Okay, I will try it. I hope it works
kob72 said:
With oreo use this TWRP https://forum.xda-developers.com/devdb/project/dl/?id=27068
after flash again beta 17
Click to expand...
Click to collapse
Can you Explain it to me a bit detailed please.
Fun4Jan said:
Okay, I will try it. I hope it works
Click to expand...
Click to collapse
So I tried it with this instruction: http://www.androidbrick.com/oneplus-one-two-3-3t-5-mega-unbrick-guide-twrp-flashing/
I did it like it says but some things were different and I think it was because my phone worked and wasn't bricked.
Now I have my phone and got the oldest OOS 3.5.1. My changeable Phonename is OnePlus 3T but I got a mail again where it says that I logged in with a OnePlus 3.
I will try to install TWRP and the latest OOS version.
So I finally solved it.
I was a bit confused with the TWRP version, so I thought that I can install the latest OOS with the Oxygen Recovery and I saw, that I used the wrong Recovery for my phone.
I used the right TWRP version for my phone but not the right Oxygen Recovery when I tried it with it.
I thank all you guys for the help.
Fun4Jan said:
So I finally solved it.
I was a bit confused with the TWRP version, so I thought that I can install the latest OOS with the Oxygen Recovery and I saw, that I used the wrong Recovery for my phone.
I used the right TWRP version for my phone but not the right Oxygen Recovery when I tried it with it.
I thank all you guys for the help.
Click to expand...
Click to collapse
No problem, would you mind adding [SOLVED] to the title, so other users with the same or similar problem will read this post to fix their devices too?
Thanks, and happy flashing!
Fun4Jan said:
I tried it with TWRP 3.1.1-2 for the OnePlus 3t
Click to expand...
Click to collapse
Then try with the older version, the newest one is known to cause problems with proper device detection.
Edit: nevermind, just saw it's fixed.
Hello, every Developer...
So I own a OnePlus 3t (A3000). I rooted it using TWRP 3.2.3-1 & Magisk 16.7.
Everything was going fine until I upgraded Magisk with the Direct Install. My phone got into what forums say Bootloop.
I found many solutions but mostly had that Flash Magisk Un-installer and further. But whenever I was trying to Flash it said Error occurred installing.
So I thought that Installing Original ROM from OnePlus site would help but now its stuck on Circle Spinning.
I'm totally dead. Don't know what to do.
Please help me.
I would really appreciate a step by step guide as I am not good in understanding things like others here on this firm.
Root-1001 said:
Hello, every Developer...
So I own a OnePlus 3t (A3000). I rooted it using TWRP 3.2.3-1 & Magisk 16.7.
Everything was going fine until I upgraded Magisk with the Direct Install. My phone got into what forums say Bootloop.
I found many solutions but mostly had that Flash Magisk Un-installer and further. But whenever I was trying to Flash it said Error occurred installing.
So I thought that Installing Original ROM from OnePlus site would help but now its stuck on Circle Spinning.
I'm totally dead. Don't know what to do.
Please help me.
I would really appreciate a step by step guide as I am not good in understanding things like others here on this firm.
Click to expand...
Click to collapse
See this post https://forum.xda-developers.com/on...genos-5-0-1-android-8-0-t3728119/post78381819
And use TWRP 3.2.3-0 not -1
Sent from my OnePlus3T using XDA Labs