Hey everyone, so I saw that there was a new update for MIUI Developer ROM (9.3.28) and I decided to download it. After I downloaded it, i opened twrp and flashed it with lazyflasher as I always do. After the phone boots normally, i realised that the phone had been upgraded to android pie, so I went to check google camera to see if it was working still, but it didnt. So I went back to TWRP to try to enable HAL3 via adb shell, but when i opened TWRP i saw a strange message. It asked for a password in order to decrypt my data. this was the first time i saw it and after searching a bit I tried to use my phones password, but it didnt work. I decided to ignore the message and just open adb shell and enable HAL3. The thing is that when I tried to open it said device not found, which is really strange ( im using the same computer as i was before, adb is installed of course ). I had no choice but to downgrade to stable, so I tried to downgrade to stable rom. Downloaded the rom, but when i chose "choose package" it wouldnt let me install the stable one because it was an older version of android....
So long story short, Android Pie has left me with a non-working Google Camera, TWRP and no ability to downgrade or flash and ROMs.
Any help would be appreciated
https://www.youtube.com/watch?v=bsbZ3kG88Dw
Same problem with me. I tried everything but no luck and now I am unable to use camera2api. So i thought to root my phone and edit build prop manually but when I flashed magisk my phone stuck at boot logo. I lost all my data and I had to flash with mi flash tool. Luckily my bootloader was unlocked.
After flashing Pie, you have to flash a TWRP recover for MIUI Pie. This will allow to decrypt your device (data will be erased).
If you want to rollback to stable (as I did), download fastboot ROM via MIUI official site, boot to bootloader and flash it via flash_all.bat file included in the ROM (assuming you have fastboot on your PC).
Related
i tried installing the lastest ota update while i had twrp installed, i have tried everything to get out of this loop.
tried flashing the updated rom off the oneplus website and if gave me errors
just looked at my phone and now it wont turn on what so every getting really stressed please help
[SOLVED]
went back to stock recovery and side loaded the full 1.4 gb rom i will leave a link for tutorial that i used, i wanted to get back to complete stock and this was the one use
"https://forums.oneplus.net/threads/guide-how-to-unroot-your-oneplus-3-and-go-back-completely-to-stock.456232/"
When you have TWRP you have to install full zip, not simply the eval OTA zip
bob_cheeseman5 said:
i tried installing the lastest ota update while i had twrp installed, i have tried everything to get out of this loop.
tried flashing the updated rom off the oneplus website and if gave me errors
just looked at my phone and now it wont turn on what so every getting really stressed please help
Click to expand...
Click to collapse
Flash the stock recovery.
Get stock recovery from downloads.oneplus.net
I cant seem to flash the stock recovery. The device is not visible in adb devices or fastboot devices. im facing the same issue.
If you are using TWRP 3.0.4-0 - try a hard boot...hold down the power button for 20s...wait 20s, power it back on.
bob_cheeseman5 said:
i tried installing the lastest ota update while i had twrp installed, i have tried everything to get out of this loop.
tried flashing the updated rom off the oneplus website and if gave me errors
just looked at my phone and now it wont turn on what so every getting really stressed please help
Click to expand...
Click to collapse
easy solution. Boot into fastboot
download this tool.
https://forum.xda-developers.com/oneplus-3/development/toolkit-oneplus-3-toolkit-unlock-t3398799
if newest version isnt working, download an older version with older twrp
than unzip the tool and run the .bat file and install twrp.
Thats it
There are many posts on Nougat not working with official TWRP (based on 6.0 build). Try booting into stock recovery. performing a system settings reset, then booting into fastboot and run the adb command, <fastboot boot TWRP-3.0.2-1.28.img>. From there you can do virtually anything you need to do. I recommend at least using a modified version of TWRP (such as 1.28). This has been posted many times before, please try and do a search for the answers first, it will help tremendously. Thanks
recovery
i had the same problem on my rooted OP3 when i used TWRP 3.0.2-1 , it worked to flash the full 4.0.1 rom but failed for everything else, flashing latest verion of twrp fixed it for me
Got the same problem (unrooted phone + device state locked, cannot access recover, but can access fastboot) with an added "benefit", USB debugging mode was off before it all went crashing and burning.
How to access my phone via PC? (all the guides I've found assume I had USB debugging mode on before the phone got soft-bricked, but as a normal phone user who never installed anything custom, I've never figured it is A MUST BE ON function).
Or simpler question - what tool to use to turn on the USB debugging mode? (if that is at all possible?)
Aislandas said:
Got the same problem (unrooted phone + device state locked, cannot access recover, but can access fastboot) with an added "benefit", USB debugging mode was off before it all went crashing and burning.
How to access my phone via PC? (all the guides I've found assume I had USB debugging mode on before the phone got soft-bricked, but as a normal phone user who never installed anything custom, I've never figured it is A MUST BE ON function).
Or simpler question - what tool to use to turn on the USB debugging mode? (if that is at all possible?)
Click to expand...
Click to collapse
I have tried doing the installing of the newer twrp but cant find a newer version of it, i am on 3.0.2-1. i have the same problem as you that my USB debugging isnt on i dont think so when trying to use the op3 tool kit i can get it to pick up fast boot but nothing else.
have you found a solution to your problem yet?
bob_cheeseman5 said:
I have tried doing the installing of the newer twrp but cant find a newer version of it, i am on 3.0.2-1. i have the same problem as you that my USB debugging isnt on i dont think so when trying to use the op3 tool kit i can get it to pick up fast boot but nothing else.
have you found a solution to your problem yet?
Click to expand...
Click to collapse
Noted that you solved your issue, but this post is about the new version of TWRP. Version 3.0.3 is available on twrp.me and it works with Nougat.
bob_cheeseman5 said:
I have tried doing the installing of the newer twrp but cant find a newer version of it, i am on 3.0.2-1. i have the same problem as you that my USB debugging isnt on i dont think so when trying to use the op3 tool kit i can get it to pick up fast boot but nothing else.
have you found a solution to your problem yet?
Click to expand...
Click to collapse
Gave up trying and booked a session with OP technicians Will see how it goes in a week.
Hello members of XDA,
The issue I'm having is pretty rare and found few or non threads about it, so I will try to be the most precise possible.
Yesterday I decided to change the ROM of my LG G4 H815, I was previously on LineageOS, since LineageOS on H815 wasn't developped anymore. So I asked myself why not trying Android Oreo with CypherOS. Before any changes I was with the latest version of LineageOS for H815 and I had TWRP with the version 3.0.2.1. Bootloader was obviously unlocked.
So I starded to download all the required material to switch to CypherOS 5.3.1, while the download I've made a backup of my actual lineageOS installation on my internal storage. Once every thing was downloaded I tried to install CypherOS I had an error 7 in TWRP install box, so I was pretty worried, scouted XDA threads about the error but i was redirected to the solution where you modify the update binary with txt but still didnt worked. I've found a thread talking about updating firmware of the H815 ( https://forum.xda-developers.com/g4/development/v5-8-5-n7-1-2-resurrection-remix-t3704450) While panicking I've done a wipe of everything (dalvik, data,cache and system) .I applied thge firmware update but I also re-read the thread of CypherOS and figured that I needed a newer version of TWRP, installed it so. THen magically CypherOS installed without any issue.
After installing the Gapps (Arm64 8.1 Nano) I rebooted and the first weird thing appears, after seeing the LG screen while the boot I have another screen telling me that the bootloader has been locked and that i should visit g.co/ABH for more information, then CypherOS initialise, CypherOS worked like a charm. So I wanted to go to my TWRP and make a backup in case. I launched ADB and use the command adb reboot recovery, the phone restarted and had the following events : LG logo, warning message about the bootloader, LG logo again and then a black screen. However I was in recovery mode since adb found me with the command fastboot devices. I had no TWRP logo or anything linked to it. Few minutes later, I had the basic recovery mode where you move yourself with the volume buttons and select with power where the functions are pretty limited.
Then I rebooted the phone with adb (fastboot reboot), CypherOS still working perfectly. Thaught that it was the bootloader which back to scratch when he was blocked, I figured out that he was still unlocked, I used the command "fastboot getvar unlocked" through ADB. THen I thaught i had to install back TWRP, tried through the fastboot mode but I had an error
Code:
FAILED (remote: unkown command)
since i tried everything i could even in the basic recovery mode, the only working command in the recovery is "fastboot flash recovery twrp.img" but still does nothing.
I mean it's not that terrible since I can use my phone and i'm about to change phone in 2 months for a Oneplus but i would really like to be able to install magisk on the phone to grant root access and be able to use TWRP on it like I used to. By the way the backup of lineageOS has been deleted while performing unecessary wipes.
Bennou said:
Hello members of XDA,
The issue I'm having is pretty rare and found few or non threads about it, so I will try to be the most precise possible.
Yesterday I decided to change the ROM of my LG G4 H815, I was previously on LineageOS, since LineageOS on H815 wasn't developped anymore. So I asked myself why not trying Android Oreo with CypherOS. Before any changes I was with the latest version of LineageOS for H815 and I had TWRP with the version 3.0.2.1. Bootloader was obviously unlocked.
So I starded to download all the required material to switch to CypherOS 5.3.1, while the download I've made a backup of my actual lineageOS installation on my internal storage. Once every thing was downloaded I tried to install CypherOS I had an error 7 in TWRP install box, so I was pretty worried, scouted XDA threads about the error but i was redirected to the solution where you modify the update binary with txt but still didnt worked. I've found a thread talking about updating firmware of the H815 ( https://forum.xda-developers.com/g4/development/v5-8-5-n7-1-2-resurrection-remix-t3704450) While panicking I've done a wipe of everything (dalvik, data,cache and system) .I applied thge firmware update but I also re-read the thread of CypherOS and figured that I needed a newer version of TWRP, installed it so. THen magically CypherOS installed without any issue.
After installing the Gapps (Arm64 8.1 Nano) I rebooted and the first weird thing appears, after seeing the LG screen while the boot I have another screen telling me that the bootloader has been locked and that i should visit g.co/ABH for more information, then CypherOS initialise, CypherOS worked like a charm. So I wanted to go to my TWRP and make a backup in case. I launched ADB and use the command adb reboot recovery, the phone restarted and had the following events : LG logo, warning message about the bootloader, LG logo again and then a black screen. However I was in recovery mode since adb found me with the command fastboot devices. I had no TWRP logo or anything linked to it. Few minutes later, I had the basic recovery mode where you move yourself with the volume buttons and select with power where the functions are pretty limited.
Then I rebooted the phone with adb (fastboot reboot), CypherOS still working perfectly. Thaught that it was the bootloader which back to scratch when he was blocked, I figured out that he was still unlocked, I used the command "fastboot getvar unlocked" through ADB. THen I thaught i had to install back TWRP, tried through the fastboot mode but I had an error since i tried everything i could even in the basic recovery mode, the only working command in the recovery is "fastboot flash recovery twrp.img" but still does nothing.
I mean it's not that terrible since I can use my phone and i'm about to change phone in 2 months for a Oneplus but i would really like to be able to install magisk on the phone to grant root access and be able to use TWRP on it like I used to. By the way the backup of lineageOS has been deleted while performing unecessary wipes.
Click to expand...
Click to collapse
It's clearly written on the official website and in the official TWRP support thread for the g4 what you have to do when on Nougat bootloader and want to flash TWRP... and keeping it.
Sent from my LG-H815 using XDA Labs
Yet, this still doesnt help me to solve my issue. Do you think there is a way to fix it or no ? If not, I'll just deal with it for the few months lasting.
Bennou said:
Yet, this still doesnt help me to solve my issue. Do you think there is a way to fix it or no ? If not, I'll just deal with it for the few months lasting.
Click to expand...
Click to collapse
Okay if it doesn't work for you you must do something wrong. It works 100%. If you really want help you should explain in detail exactly which steps you took as otherwise it's all just guessing what you're doing.
Sent from my LG-H815 using XDA Labs
Indeed, I didn't followed the procedure exactly, didn't do the step after flashing TWRP (removing battery and boot manually to recovery). Well thank you, was my bad on that.
Should I do a clean new install of cypheros or should I keep it like that, what would be your advice ? Knowing that at the moment CypherOS works like a charm. I also plan to install Magisk on it to root it.
To help others newbie like me, solution can be found here : https://forum.xda-developers.com/g4/development/recovery-twrp-3-touch-recovery-t3442424
So two days before Android Oreo update released (RETEU channel). I tried to flash Magisk cause i needed root access but then i realized that the Bootloader was locked and i unlocked it. Everything was ok until i tried to flash a custom recovery (TWRP) but after that everything was way too complicated. I flashed TWRP but everytime i was trying to restart my phone and get there it was replaced with the stock recovery. I tried to find something online and i did here in XDA. Everything was working and i said that is time to flash Magisk, i rebooted my phone in recovery mode and after that i flashed Magisk, but after that my ROM was destroyed and i didnt even had a backup (yes i know i should have done that, but i totally forgot about it). I said ok, the phone was released almost a year ago and there should be a Stock or Custom ROM online, i did find a couple of them but everytime i tried to flash them i was getting an error, i found the problem, my TWRP was a 32bit version and i changed that to a 64bit, but no other ROM except Lineage 15.1 was working. After flashing Lineage Os I found out that my fingerprint sensor wasn't working, my flashlight too and the camera was awful. I went back online and tried to find a stock ROM but i couldn't find anything, i tried a stock 7.1.1 and stock 8.0 but none of them was working. The last thing that i did was trying to flash it with ADB and after that my phone was working for 10 min until i got a security update that after the installation my phone didnt even boot again, i cant boot it, it isnt showing anything, no vibration, no sound, nothing Please help!
Hi Guys,
I hope every one is doing well. I have been on the latest Paranoid Android Sapphire Beta 1 build for the last few days. I have been liking the rom so far but I would need to go back to stock OOS for now. Aside from using MSM tool is there another way to flash back stock OOS zips via recovery? I tried sideloading via AOSPA's recovery but it failed (no worries, as I am still able to boot to AOSPA just fine).
Kind regards!
You can try this,,https://www.droidwin.com/unbrick-oneplus-9-pro-fastboot-commands/
Salilsarkar said:
You can try this,,https://www.droidwin.com/unbrick-oneplus-9-pro-fastboot-commands/
Click to expand...
Click to collapse
Many thanks! I was having issues downloading the stock firmware files needed for the MSM tool. I do have the downgrade zip and ota signed zip for my model, but extracting with payload dumper gives me only 7 image files so I think it's incomplete, and I would still need to download the full firmware files to be able to flash via fastboot.
If you try using fastboot to downgrade, you're very likely going to brick and have to use the MSM anyway.
blitzkriegger said:
Hi Guys,
I hope every one is doing well. I have been on the latest Paranoid Android Sapphire Beta 1 build for the last few days. I have been liking the rom so far but I would need to go back to stock OOS for now. Aside from using MSM tool is there another way to flash back stock OOS zips via recovery? I tried sideloading via AOSPA's recovery but it failed (no worries, as I am still able to boot to AOSPA just fine).
Kind regards!
Click to expand...
Click to collapse
I was able to flash to oos11 using twrp. Well, I was on crdroid and there are custom ROMs that require oos12 before It will work. So I went crdroid 8.6 to oos11 to oos 12 and then lineage 19
Well it was a ride for me lol. Took me a few hours to realize I can gain fastboot access via long pressing power button+volume up and volume down altogether. I was then able to reflash the modded magisk boot image to regain access to AOSPA.
The fun part came after trying to flash back to stock via MSM. First I figured out that instead of using the "vol up+vol- button approach then connect usb" way of trying to get MSM tool to connect to the EDL mode of the phone, an easier method is to use "ADB reboot edl" command.
Now as I previously used global stock OOS, I mistakenly used the MSM tool for the global region. However, this got me in a SHA-256 mismatch in the flashing process, causing a flash error which got me back to getting stuck at the bootloader again. Turns out the global MSM tool does not work for LE2120 model.
So at this point I had 2 options - either find a MSM tool that works, or try flashing back to stock via fastboot. The fastboot way would have worked but I ran into a problem - you have to flash to .img files partly via fastboot, then partly via fastbootd. And when on fastbootd my phone is not recognized by the PC (this is why trying to flash back AOSPA also failed, it can't continue the fastbootd part of the install as for some reason my pc loses connection with the phone on fastbootd).
My saving grace was I found out that for LE2120, the EU version of the MSM tool works. So long-story short I got back to stock OOS 12 again. It was a fun yet nerve wracking experience, and I learned a lot.
So the lesson of the story is, for anyone tinkering with this device, to learn the basics, from knowing your correct model number, knowing the proper button combinations to boot to fastboot/edl/recovery, knowing which tools to use, to knowing how to setup/troubleshoot your pc to ensure the phone communicates properly at every step!
I tried for like 3 hours to find a boot.img and i had root on my phone, but without wifi and sound.
a quick google search showed me that it was because i had a wrong version of the boot.img, afterwards i found another one and now after i have tried installing twrp, booting and flashing using adb (stock and modified versions of boot.img) but it just keeps bootlooping. in twrp i cant wipe, make a backup, see any files in /storage/ and i have no clue what to do next.
What model 7T do you have? HD1907? What was the rom that you were using before you installed TWRP on? OOS12 does not support TWRP. Custom rom A13 does not support TWRP. Only a few custom rom A12 and OOS11 support TWRP.
Idk but I'm just wondering if flashing the last working rom image (dirty flash)? That would eliminate TWRP(?) and eliminate Magisk(?) while hopefully keeping the device from being wiped possibly?
*** Hopefully someone could/would verify this before you attempt... ***
i was on android 11 but i cant remember the version, i have HD1903 (EU ver). i THINK i had the one from the oneplus website(https://service.oneplus.com/us/search/search-detail?id=2096229) but idk anymore
I JUST RANDOMLY TRIED BOOTING MY PHONE AGAIN AND IT WORKED imma check if everything works and will regardless still look at this thread bc it can prob break easily
nah wifi and sound still dont work, but im not in bootloop anymore
MimKA22 said:
I JUST RANDOMLY TRIED BOOTING MY PHONE AGAIN AND IT WORKED imma check if everything works and will regardless still look at this thread bc it can prob break easily
nah wifi and sound still dont work, but im not in bootloop anymore
Click to expand...
Click to collapse
Msmtool back to oos11
can you describe how to use it or send a link to tutorial or smth thx man <3
MimKA22 said:
can you describe how to use it or send a link to tutorial or smth thx man <3
Click to expand...
Click to collapse
[OP7T][OOS 11.0.5.1 HD65AA/BA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
i cant find the file for my current version and it doesnt work if i try it with the only version that is android 11
and i cant turn my phone back on
and after i installed the drivers i had to restart my pc and now there is this thing at the bottom right:
testmode
windows 10 pro
...
i waited until my phone had no more battery charge and now im bootlooping again :/
nvm it just booted
im downgrading it now and i dont get the error "smth communication smth" in msmtool anymore
alr it worked my phone is wiped again but i can turn on wifi and sound
but how do i root my phone now? I have an Idea, im gonna write step by step what i think gets me a rooted phone please confirm if that would not break my phone ^^' (bootloader already unlocked)
1. enable usb debugging and allow my pc
2. download and install the latest magisk version from the github
3. download magisk patched boot.img for ver 11.0.5.1BA BUT since i cant find anything on the internet im gonna have to use the zip file from the unbrick tool thing (https://onepluscommunityserver.com/list/Unbrick_Tools/OnePlus_7T/EU_HD65BA/R/) and then patch the boot.img using magisk myself
4. then use platform tools and type following commands: "adb reboot fastboot", "fastboot flash boot {the patched boot image file}"
5. then use magisk to direct install the root thing
i just realisized the unbrick thing that i wanted to use instead of a boot.img doesnt have a boot.img in it... WHERE CAN I FIND A BOOT.IMG brooo androidfilehost.com doesnt have it the unbrick tool doesnt have it
omg i realized i could update my phone to 11.0.9.1 then download the same version from official website and use the dumper to get the boot.img **** meee
wait it sais its 11.0.9.1HD65 AA and not BA **** me
k nvm i just changed the site settings to germany and now its BA
i just went for it and now my phone is rooted thank you very much for your help i would've prob tried to revert back to stock for like 2 weeks and then cry that i cant root my phone thank you so much xd