Made this for myself, but you guys can use it to. It's stock VS995 Magisk patched (aka rooted) Oreo
Download: https://drive.google.com/file/d/129CRgvyjtc1fF01l-_fi6kLReE3oXD_L/view?usp=sharing
Ignore the "NO OS INSTALLED" prompt in TWRP if you get one after installation. It's a TWRP bug.
Anyone know if this will work on US996 on the Verizon Network?
baldybill said:
Anyone know if this will work on US996 on the Verizon Network?
Click to expand...
Click to collapse
He just posted it why don't you try it and find out if it works.
Sent from my LG-H910 using XDA Labs
This is amazing, how did you build this zip?
Can I install it on H910?
Rooted Oreo vs995 has working data?
Cause for other dirty Santa versions like h910/h915 Oreo, using it with magisk patched boot, keeping eng aboot and recovery, the Oreo modem won't work properly. The rest of the phone will be fine.
Thank you for the rom...got it on verizon dirty flash over alpharom it work...call and 4g work fine!! Waiting for kernel to fix static
Thanks you for the job.
cnjax said:
He just posted it why don't you try it and find out if it works.
Sent from my LG-H910 using XDA Labs
Click to expand...
Click to collapse
This is intentionally bad advice. If you attempt to do this, my advice is make sure you have a KDZ to recover to and delete all files in /images EXCEPT system.bin and boot.bin. Cross-flashing bootloader partitions is a bad idea.
darkknight200 said:
Rooted Oreo vs995 has working data?
Cause for other dirty Santa versions like h910/h915 Oreo, using it with magisk patched boot, keeping eng aboot and recovery, the Oreo modem won't work properly. The rest of the phone will be fine.
Click to expand...
Click to collapse
Yes, everything works as intended except static on boot. I recommend enabling secure startup and toggling your screen before entering the startup pin so you can very quickly get rid of it.
NotYetADev said:
Yes, everything works as intended except static on boot. I recommend enabling secure startup and toggling your screen before entering the startup pin so you can very quickly get rid of it.
Click to expand...
Click to collapse
So that means you still have twrp recovery?
darkknight200 said:
So that means you still have twrp recovery?
Click to expand...
Click to collapse
You have to go into fastboot and re-flash it. I'd wait until you have gotten past setup wizard to do so, though.
NotYetADev said:
You have to go into fastboot and re-flash it. I'd wait until you have gotten past setup wizard to do so, though.
Click to expand...
Click to collapse
To clarify, the phone doesn't have dirty Santa engineer aboot anymore after flashing the zip because it gets replaced with stock aboot? But u can still flash twrp thru fastboot still?
darkknight200 said:
To clarify, the phone doesn't have dirty Santa engineer aboot anymore after flashing the zip because it gets replaced with stock aboot? But u can still flash twrp thru fastboot still?
Click to expand...
Click to collapse
It still has the engineering aboot, so you still have fastboot.
NotYetADev said:
It still has the engineering aboot, so you still have fastboot.
Click to expand...
Click to collapse
hm ok. So the vs995 oreo is the first variant that has working data with eng aboot then.
edit: @askermk2000 for vs995 oreo mk2000 kernel.
Thank you so much!
So once we get the phone going again, just go into the bootloader and do "fastboot flash recovery twrp.img"? (with the right filename) and we get a working TWRP back?
Thank you!!!!
Buzzy42 said:
So once we get the phone going again, just go into the bootloader and do "fastboot flash recovery twrp.img"? (with the right filename) and we get a working TWRP back?
Thank you!!!!
Click to expand...
Click to collapse
I try to that it does flash twrp but when I try get in twrp mode it only flash a logo then boot I also try to delete recovery.bin in the zip but not work so...also tryna debloat app througt root uninstall but some how system folder doesn't mount...
darkknight200 said:
edit: @askermk2000 for vs995 oreo mk2000 kernel.
Click to expand...
Click to collapse
I am building kernel now.
Could someone on this ROM do:
Code:
cat /proc/cmdline
I just want to check something before my kernel is installed.
askermk2000 said:
I am building kernel now.
Could someone on this ROM do:
Code:
cat /proc/cmdline
I just want to check something before my kernel is installed.
Click to expand...
Click to collapse
elsa:/ # cat /proc/cmdline
sched_enable_hmp=1 sched_enable_power_aware=1 app_setting.use_32bit_app_setting=1 kpti=1 console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 user_debug=31 msm_rtb.filter=0x237 ehci-hcd.park=3 lpm_levels.sleep_disabled=1 [email protected] androidboot.hardware=elsa buildvariant=user slub_debug=FZPU lge.rev=rev_10 model.name=LG-US996 lge.bootreason=0x8f58a242 cc_mode=0 kswitch lge.bootreasoncode=0x8f58a242 bootcable.type=NO_INIT lge.battid=SW3800_VC0 androidboot.dlcomplete=0 androidboot.ddr_size=4294967296 androidboot.ddr_info=0x6 lge.crash_handler=on lge.hreset=off boot_cpus=0-3 androidboot.revision=12 androidboot.verifiedbootstate=red androidboot.veritymode=enforcing androidboot.rpmb_state=1 androidboot.bootdevice=624000.ufshc androidboot.serialno=LGUS996e04caf92 lge.signed_image=true androidboot.baseband=msm mdss_mdp.panel=1:dsi:0:qcom,mdss_dsi_sw49407_dsc_qhd_cmd:config1:1:none:cfg:single_dsi
elsa:/ #
Related
So I'm on a VP and am BL unlocked, twrp'd and rooted on 7.1 and want to update to 7.1.1. I want to flash the stock boot.img so I can take the OTA and update. Problem is I keep trying to extra the boot.img but can't get it to flash.
Not sure if I'm doing it wrong or have the wrong img but it's driving me nuts.
I've read through the forums and I know I'll get flamed for asking but I just need a bit of help with this.
Thx
mpetruzz said:
So I'm on a VP and am BL unlocked, twrp'd and rooted on 7.1 and want to update to 7.1.1. I want to flash the stock boot.img so I can take the OTA and update. Problem is I keep trying to extra the boot.img but can't get it to flash.
Not sure if I'm doing it wrong or have the wrong img but it's driving me nuts.
I've read through the forums and I know I'll get flamed for asking but I just need a bit of help with this.
Thx
Click to expand...
Click to collapse
fastboot flash boot_a /path/to/boot.img
fastboot flash boot_b /path/to/boot.img
Or, just flash the whole image with flash-all command. 7.1.1 (NMF26O, Dec 2016) is the one you want and its found here https://developers.google.com/android/images. You can edit the script and remove the -w and it'll keep the user data in tact. For me, it was better to start from scratch.
Droid1019 said:
fastboot flash boot_a /path/to/boot.img
fastboot flash boot_b /path/to/boot.img
Click to expand...
Click to collapse
Ok thanks! I had a few people give me the wrong command line that's prolly why it wasn't working. I'll give this a shot later!!
Droid1019 said:
fastboot flash boot_a /path/to/boot.img
fastboot flash boot_b /path/to/boot.img
Or, just flash the whole image with flash-all command. 7.1.1 (NMF26O, Dec 2016) is the one you want and its found here https://developers.google.com/android/images. You can edit the script and remove the -w and it'll keep the user data in tact. For me, it was better to start from scratch.
Click to expand...
Click to collapse
OK, so now I'm using those commands and still am getting the error message cannot load path/to/boot.img.
I can give the flash all a try, how to I edit the script to remove the -w??
mpetruzz said:
OK, so now I'm using those commands and still am getting the error message cannot load path/to/boot.img.
I can give the flash all a try, how to I edit the script to remove the -w??
Click to expand...
Click to collapse
If you get that error message it sounds like you don't have the right path for it to find that file. With the phone in bootloader mode I type in the command then drag the bit image into the terminal window and execute. I use a Mac so I don't know if you can drag the file in on a Windows machine. You'll have the same issue with the flash all if you don't have the right path.
mpetruzz said:
So I'm on a VP and am BL unlocked, twrp'd and rooted on 7.1 and want to update to 7.1.1. I want to flash the stock boot.img so I can take the OTA and update. Problem is I keep trying to extra the boot.img but can't get it to flash.
Not sure if I'm doing it wrong or have the wrong img but it's driving me nuts.
I've read through the forums and I know I'll get flamed for asking but I just need a bit of help with this.
Thx
Click to expand...
Click to collapse
Can't you just flash stock recovery and sideload the OTA? Seems a lot easier and safer.
bobby janow said:
Can't you just flash stock recovery and sideload the OTA? Seems a lot easier and safer.[/QUOTE
Yeah that does sound better!!. Honestly I might just leave it on 7.1 til some Roms come out.
Click to expand...
Click to collapse
mpetruzz said:
bobby janow said:
Can't you just flash stock recovery and sideload the OTA? Seems a lot easier and safer.[/QUOTE
Yeah that does sound better!!. Honestly I might just leave it on 7.1 til some Roms come out.
Click to expand...
Click to collapse
7.1.1 is worth it. Not sure when roms are coming out but with the OTA it's about a 10 minute install and reboot. You'll need to just fastboot flash recovery recovery.img for the stock, go directly into recovery with the vol keys / power key and then adb sideload the ota file after entering the recovery menu.
Did you flash another kernel? Is that why you want to replace the boot.img? If so you can probably just flash the OTA without changing anything other than recovery since it will overwrite the boot.img anyway.
Click to expand...
Click to collapse
bobby janow said:
mpetruzz said:
7.1.1 is worth it. Not sure when roms are coming out but with the OTA it's about a 10 minute install and reboot. You'll need to just fastboot flash recovery recovery.img for the stock, go directly into recovery with the vol keys / power key and then adb sideload the ota file after entering the recovery menu.
Did you flash another kernel? Is that why you want to replace the boot.img? If so you can probably just flash the OTA without changing anything other than recovery since it will overwrite the boot.img anyway.
Click to expand...
Click to collapse
Right now I'm only BL unlocked, twrp'd and rooted. No kernel modifications.
Where do I get the recovery.img from?
I was told by others here I need to flash the stock boot image in order to take the OTA. Jeez I'm getting so confused cause I keep getting different info
Click to expand...
Click to collapse
mpetruzz said:
bobby janow said:
Right now I'm only BL unlocked, twrp'd and rooted. No kernel modifications.
Where do I get the recovery.img from?
I was told by others here I need to flash the stock boot image in order to take the OTA. Jeez I'm getting so confused cause I keep getting different info
Click to expand...
Click to collapse
Stock recovery is in the image file from Google. Download it and extract it and flash it in bl. You might need things to "take" the OTA but I don't believe you need anything to flash the OTA (adb sideload) That will overwrite any kernel (boot.img) changes you made. But you said you made no kernel changes so why would you need to flash a boot.img?
Click to expand...
Click to collapse
bobby janow said:
mpetruzz said:
Stock recovery is in the image file from Google. Download it and extract it and flash it in bl. You might need things to "take" the OTA but I don't believe you need anything to flash the OTA (adb sideload) That will overwrite any kernel (boot.img) changes you made. But you said you made no kernel changes so why would you need to flash a boot.img?
Click to expand...
Click to collapse
OK so i'm in the system image file for 7.1 and am not seeing the recovery.img. Must be doing something wrong, but it's def not there. Anywhere else I can grab it from?
Also once I get it what would the adb command line be to flash it?
Click to expand...
Click to collapse
bobby janow said:
mpetruzz said:
Stock recovery is in the image file from Google. Download it and extract it and flash it in bl. You might need things to "take" the OTA but I don't believe you need anything to flash the OTA (adb sideload) That will overwrite any kernel (boot.img) changes you made. But you said you made no kernel changes so why would you need to flash a boot.img?
Click to expand...
Click to collapse
I got it and am all set!! Used the skipsoft tool to flash the stock recovery, then sideloaded the OTA!!
Thanks brother for all the help!!!!
Click to expand...
Click to collapse
Hey I'm pretty new to this but is there a way I can update without a computer, I dont mind losing root as long as I'm still unlocked... I'm using a Verizon phone on at&t if that matters... If not I can always to it tomorrow when I can get to a computer..
bobby janow said:
mpetruzz said:
7.1.1 is worth it. Not sure when roms are coming out but with the OTA it's about a 10 minute install and reboot. You'll need to just fastboot flash recovery recovery.img for the stock, go directly into recovery with the vol keys / power key and then adb sideload the ota file after entering the recovery menu.
Did you flash another kernel? Is that why you want to replace the boot.img? If so you can probably just flash the OTA without changing anything other than recovery since it will overwrite the boot.img anyway.
Click to expand...
Click to collapse
OK maybe i spoke too soon. I sideloaded the OTA and was able to install TWRP, but now when I flash the su zip I don't have the SuperSu app and can't get root. I've tried it twice and it looks like it's flashed but then when I reboot it's not there.
What am I not doing to get this too work??
Click to expand...
Click to collapse
mpetruzz said:
bobby janow said:
OK maybe i spoke too soon. I sideloaded the OTA and was able to install TWRP, but now when I flash the su zip I don't have the SuperSu app and can't get root. I've tried it twice and it looks like it's flashed but then when I reboot it's not there.
What am I not doing to get this too work??
Click to expand...
Click to collapse
http://forum.xda-developers.com/pixel-xl/development/root-supersu-t3490156
This is where you'll need to go at this point. Lots to read but you have to do it in order to get it working correctly. Good luck, you'll get it.
Click to expand...
Click to collapse
bobby janow said:
mpetruzz said:
http://forum.xda-developers.com/pixel-xl/development/root-supersu-t3490156
This is where you'll need to go at this point. Lots to read but you have to do it in order to get it working correctly. Good luck, you'll get it.
Click to expand...
Click to collapse
Got it, man this pixel is crazy different than what I'm used too. Thanks all for the help!
Click to expand...
Click to collapse
Hi Guys,
Note : By doing this, you know that you're gonna do a modification to your phone, and im not in any way, responsible for what happen after. Escape Route for if something wrong happen is provided, but YOU DO THIS ON YOUR OWN RISK
since this phone is fairly new, at this moment a clear rooting method haven't established yet. This is what this thread for.
Based on information gathered from P20 Lite Forum (the rooting guide for that device even already up - here), it seems the old trick of rooting (from Mate 10 Pro) using Patched Boot Method is working fine. And Magisk is working
Basically this method need few pre-requisites :
1. Unlocked Bootloader (by getting the code here ) - and if you not sure how to do it, go here for the guide
2. Stock Boot (or RAMDISK to be precise for this phone) - I managed to extract it from 8.1.0.106 ROM version for CLT-L29 (download here)
3. Magisk Manager 5.5.4 (from Magisk Thread) to patch the .img above, or
4. Patched RAMDISK image (i patched it) from here
5. and of course computer with ADB & Fastboot installed (make sure you have latest SDK to prevent something not working)
Now, to Root it, all you need to do is,
1. Boot into bootloader
2. Type
Code:
fastboot flash ramdisk patched_boot.img
(patched_boot.img is the file you download from prerequisites number 4, placed it in the same directory with your adb & fastboot - i assume you know that already)
3. Reboot
4. You now should have root access, download Magisk Manager to manage modules and superuser
(you might need to flash this module if you failed to pass safetynet)
In case something go wrong, flash back the stock RAMDISK from pre-requistes number 2 above using same method as what u did to flash the patched one.
That way worked. Thanks.
Edit:
Just as a hint. To get magisk work as it should..
After boot into the system and installed Magisk Manager, install Magisk from there again, so you dont get any /data/magisk problems.
SafteyNet passed then.
Fingers crossed twrp is possible soon
Works on CLT-L09
I have a German single Sim from Vodafone tested the root yesterday and works very well
Would this method work on CLT-L09 model? Thanks
danifilth4king said:
Would this method work on CLT-L09 model? Thanks
Click to expand...
Click to collapse
The post before you just confirmed yourbquestion, LoL
Yes it does
This is awesome, thanks for sharing! I thought I could live without root but after only half a day, I've decided I can't!
Before I do this, I was wondering where you managed to get the stock rom (quote below)?
otonieru said:
2. Stock Boot (or RAMDISK to be precise for this phone) - I managed to extract it from 8.1.0.106 ROM version for CLT-L29 (download here)
Click to expand...
Click to collapse
fl4r3 said:
This is awesome, thanks for sharing! I thought I could live without root but after only half a day, I've decided I can't!
Before I do this, I was wondering where you managed to get the stock rom (quote below)?
Click to expand...
Click to collapse
It's from www.allrom.ir (its in persian) and there's another site, rusian one if am not mistaken, but i forget the exact address
Great, thanks for that! I managed to find it on allrom.ir
Hey guys, I need some help please! I unlocked bootloader through Huawei website which went fine and then when I flashed the patched boot.img through fastboot and tried to reboot my phone has told me there was a critical error while booting. It won't boot to system and just loops a few times and then boots to Huawei eRecovery. This is my first Huawei device and I'm clueless as to how to recover
Any ideas would be much appreciated! Thanks
**EDIT*** false alarm! I managed to boot to fastboot and restore the ramdisk from the first post
danifilth4king said:
Hey guys, I need some help please! I unlocked bootloader through Huawei website which went fine and then when I flashed the patched boot.img through fastboot and tried to reboot my phone has told me there was a critical error while booting. It won't boot to system and just loops a few times and then boots to Huawei eRecovery. This is my first Huawei device and I'm clueless as to how to recover
Any ideas would be much appreciated! Thanks
**EDIT*** false alarm! I managed to boot to fastboot and restore the ramdisk from the first post
Click to expand...
Click to collapse
What is your phone model ? CLT-L29 or L09 ? And what is your ROM version ?
otonieru said:
What is your phone model ? CLT-L29 or L09 ? And what is your ROM version ?
Click to expand...
Click to collapse
It's CLT-L09, build number 8.1.0.103(C782)
It's and EE UK handset. Any ideas why it wouldn't have worked? Thanks
danifilth4king said:
It's CLT-L09, build number 8.1.0.103(C782)
It's and EE UK handset. Any ideas why it wouldn't have worked? Thanks
Click to expand...
Click to collapse
The ramdisk.img was taken from .106 ROM, so its actually newer than what installed on your phone. That might become issue,
But, do you managed to revive the phone using the stock ramdisk from first post ?
otonieru said:
The ramdisk.img was taken from .106 ROM, so its actually newer than what installed on your phone. That might become issue,
But, do you managed to revive the phone using the stock ramdisk from first post ?
Click to expand...
Click to collapse
Yes thank you, the stock ramdisk from the first post allowed my phone to boot normally again. Do you think if I use magisk manager app to patch the stock ramdisk it will work for me? Or is that the same as what you did to make the patched boot.img anyway?
danifilth4king said:
Yes thank you, the stock ramdisk from the first post allowed my phone to boot normally again. Do you think if I use magisk manager app to patch the stock ramdisk it will work for me? Or is that the same as what you did to make the patched boot.img anyway?
Click to expand...
Click to collapse
If you have the 103 rom, and able to extract the ramdisk yourself, you can try patch it yourself.
Have you tried to flash the patch ramdisk one more time ? In case it just a bad flash.
Because if you manage to boot using stock one. It means your system has no problem using .106 boot image and the patched one should work as well
otonieru said:
If you have the 103 rom, and able to extract the ramdisk yourself, you can try patch it yourself.
Have you tried to flash the patch ramdisk one more time ? In case it just a bad flash.
Because if you manage to boot using stock one. It means your system has no problem using .106 boot image and the patched one should work as well
Click to expand...
Click to collapse
Ok I will try again and report back. How do you boot into fastboot from device off state by the way? I had difficulty doing it earlier. Thanks again!
danifilth4king said:
Ok I will try again and report back. How do you boot into fastboot from device off state by the way? I had difficulty doing it earlier. Thanks again!
Click to expand...
Click to collapse
Its better to do it from ON state, and use adb reboot bootloader command
otonieru said:
Its better to do it from ON state, and use adb reboot bootloader command
Click to expand...
Click to collapse
I mean if the patched boot.img still doesn't work again and the device won't boot to system? I did it before when I flashed back to stock ramdisk, but I don't know how I entered fastboot exactly lol
danifilth4king said:
I mean if the patched boot.img still doesn't work again and the device won't boot to system? I did it before when I flashed back to stock ramdisk, but I don't know how I entered fastboot exactly lol
Click to expand...
Click to collapse
Put the device off and hold power button and volume down. You should come directly into the rescue mode.
danifilth4king said:
I mean if the patched boot.img still doesn't work again and the device won't boot to system? I did it before when I flashed back to stock ramdisk, but I don't know how I entered fastboot exactly lol
Click to expand...
Click to collapse
Ah, sorry, i got it wrong. Yes, its power n volume down.
Does anyone happen to have this? I used the 9.5.3 img for the TWRP with working decrypt, and it booted fine once, however now it keeps booting back to TWRP despite selecting "reboot system." I think someone mentioned they had it, but I can't find it for the life of me. Thanks so much!
No, don't think there are any full zips for T-Mo yet.
Bradl79 said:
No, don't think there are any full zips for T-Mo yet.
Click to expand...
Click to collapse
Thanks for the heads-up I actually got it to boot again by flashing SkyDragon kernel and Magisk!
sabrdawg said:
Thanks for the heads-up I actually got it to boot again by flashing SkyDragon kernel and Magisk!
Click to expand...
Click to collapse
How did this fix the boot image? How did your flash TWRP? The one with decryption or no?
photolarry said:
How did this fix the boot image? How did your flash TWRP? The one with decryption or no?
Click to expand...
Click to collapse
I flashed the TWRP with working decrypt. The only problem is, is that I just tried restoring a backup with it, and now I can't get out of fastboot mode. Downloading MSM Tool now :/
MSM Tool?
sabrdawg said:
I flashed the TWRP with working decrypt. The only problem is, is that I just tried restoring a backup with it, and now I can't get out of fastboot mode. Downloading MSM Tool now :/
Click to expand...
Click to collapse
Where is it? They said it is not out yet.
Here you go
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
In case you still need it, I'm fairly certain this is the boot image for GM31CB 9.5.5. I extracted it from my own device when I was flashing the international firmware. I will be honest, it might have the Chinese TWRP patched in. I doubt it though since it I can't find any of the TWRP files in the decompiled image.
https://drive.google.com/open?id=1nla0OCUpFL01CnVM5vm0G4aQ1gZ6cupI
bmg1001 said:
In case you still need it, I'm fairly certain this is the boot image for GM31CB 9.5.5. I extracted it from my own device when I was flashing the international firmware. I will be honest, it might have the Chinese TWRP patched in. I doubt it though since it I can't find any of the TWRP files in the decompiled image.
https://drive.google.com/open?id=1nla0OCUpFL01CnVM5vm0G4aQ1gZ6cupI
Click to expand...
Click to collapse
Thank you!
bmg1001 said:
In case you still need it, I'm fairly certain this is the boot image for GM31CB 9.5.5. I extracted it from my own device when I was flashing the international firmware. I will be honest, it might have the Chinese TWRP patched in. I doubt it though since it I can't find any of the TWRP files in the decompiled image.
https://drive.google.com/open?id=1nla0OCUpFL01CnVM5vm0G4aQ1gZ6cupI
Click to expand...
Click to collapse
You had to root in order to extract boot IMG correct?
Nekromantik said:
You had to root in order to extract boot IMG correct?
Click to expand...
Click to collapse
No, I flashed TWRP to the opposite partition and extracted it there.
bmg1001 said:
No, I flashed TWRP to the opposite partition and extracted it there.
Click to expand...
Click to collapse
hmm
the instructions for installing twrp mentions having stock boot.img in order to install it
how did you flash to second slot without a stock boot.img?
Nekromantik said:
hmm
the instructions for installing twrp mentions having stock boot.img in order to install it
how did you flash to second slot without a stock boot.img?
Click to expand...
Click to collapse
I didn't use the guide. I flashed TWRP (the TWRP image that is provided in that same thread) to the opposite partition.
bmg1001 said:
I didn't use the guide. I flashed TWRP (the TWRP image that is provided in that same thread) to the opposite partition.
Click to expand...
Click to collapse
ah ok
not sure I wanna risk anything as no msmtool guaranteed for the 5g version.
I followed the guide here: https://forum.xda-developers.com/mate-8/general/oreo-nxt-l09-l29-t3844267
And managed to install openkirin Omnirom Pie, and it runs great. WiFi, bluetooth, fingerprint reader, and camera are all working perfectly, BUT I have absolutely no signal.
The phone recognizes the sim and and reads the data, but it displays no network connection, showing 0 bars. I've been going crazy trying to figure this out and fix it. Any help would be greatly appreciated.
In the Phone Status tab it shows the following.
Device Name: unknown
Model & hardware: unknown
Build number: unknown
SELinux status: Enforcing
I tried flashing the modem file for the NXT-L09 through fastboot, but if failed with "command not allow." The bootloader is unlocked.
Rename local.prop to local.prop.bak in /cust/all/cn/prop it might work
mahrtayyab said:
Rename local.prop to local.prop.bak in /cust/all/cn/prop it might work
Click to expand...
Click to collapse
I can't mount the cust partition. It appears to be empty? This is the first time I've encountered a phone with encryption activated in the recovery.
Try using root explorer
mahrtayyab said:
Try using root explorer
Click to expand...
Click to collapse
I'll give it a shot and report back. Thanks!
mahrtayyab said:
Try using root explorer
Click to expand...
Click to collapse
Root Explorer doesn't show a cust folder. There is a single cust file, though it appears empty when I try to open it.
So it means your cust is messed try flashing cust.img using fastboot then rename
mahrtayyab said:
So it means your cust is messed try flashing cust.img using fastboot then rename
Click to expand...
Click to collapse
I've already tried it. I keep getting "remote:Command Not Allowed" which apparently means the bootloader is locked. But it displays unlocked in Fastboot mode. To be honest, I feel completely lost here. Chinese phones have so many weird layers of security and encryption it's really confusing.
TheMaddestMax said:
I've already tried it. I keep getting "remote:Command Not Allowed" which apparently means the bootloader is locked. But it displays unlocked in Fastboot mode. To be honest, I feel completely lost here. Chinese phones have so many weird layers of security and encryption it's really confusing.
Click to expand...
Click to collapse
could you solve?
TheMaddestMax said:
I've already tried it. I keep getting "remote:Command Not Allowed" which apparently means the bootloader is locked. But it displays unlocked in Fastboot mode. To be honest, I feel completely lost here. Chinese phones have so many weird layers of security and encryption it's really confusing.
Click to expand...
Click to collapse
Flash cust using twrp otherwise flash stock rom.
mahrtayyab said:
Flash cust using twrp otherwise flash stock rom.
Click to expand...
Click to collapse
How do I do that? Do I need a special zip?
elcoya06 said:
could you solve?
Click to expand...
Click to collapse
No. I've been fighting with this phone for about a month now, and I'm not making much progress.
TheMaddestMax said:
How do I do that? Do I need a special zip?
Click to expand...
Click to collapse
You can try dload but it fails most of the time so use can twrp and hurupdater to flash stock rom
TheMaddestMax said:
No. I've been fighting with this phone for about a month now, and I'm not making much progress.
Click to expand...
Click to collapse
flash stock 8.0 raise signal with magick after flashing onmirom do hard reset take out decryption with twrp and restart
elcoya06 said:
flash stock 8.0 raise signal with magick after flashing onmirom do hard reset take out decryption with twrp and restart
Click to expand...
Click to collapse
I'm away from the house right now, but I'll give it a try as soon as I get back, and let you know. Thanks for the help.
mahrtayyab said:
You can try dload but it fails most of the time so use can twrp and hurupdater to flash stock rom
Click to expand...
Click to collapse
I'll give this a shot if I can't flash through Dload. Thanks.
Hi
I have extracted stock recovery from latest OTA 10.0.7 EU for our OP7T and enabled adb shell, so now i am putting this one up here to come handy for those soft bricked using some wonky magisk modules. But also for other needs.
open terminal while in bootloader and type:
Code:
fastboot flash recovery recovery_op7t_adb_10.0.0.7_by_Killswitch.img
reboot into recovery u can use as well:
Code:
fastboot reboot recovery
you can follow this guide on how to remove magisk modules
Download: GDrive
Enjoy and good luck!
I am assuming it will work on other versions as well like OOS 10.3.0 India.
Sent from my OnePlus7T using XDA Labs
I have a quation. If I have last rom 1.0.0.7, I do not have stock recovery on my telephone?
zioloiso said:
I have a quation. If I have last rom 1.0.0.7, I do not have stock recovery on my telephone?
Click to expand...
Click to collapse
Yes, this here is that stock recovery WITH ADB ENABLED.
iruiz2 said:
Yes, this here is that stock recovery WITH ADB ENABLED.
Click to expand...
Click to collapse
default recovery is without ADB Enabled?
zioloiso said:
default recovery is without ADB Enabled?
Click to expand...
Click to collapse
no stock recovery does not come with module enabled...you can try it yourself just boot to recovery and try adb shell
thats why i did it.
parag60288 said:
I am assuming it will work on other versions as well like OOS 10.3.0 India.
Sent from my OnePlus7T using XDA Labs
Click to expand...
Click to collapse
believe it should its just a recovery, i believe the ROM localization is where the real difference is...the stock recovery eitherway comes in some chinese and english...no indian language.. and in the end you can still reflash stock if you need to do anything there with it. Eventhou i am flashing only through bootloader...never really used it except adb shell
killswitx said:
Hi
I have extracted stock recovery from latest OTA 10.0.7 EU for our OP7T and enabled adb shell, so now i am putting this one up here to come handy for those soft bricked using some wonky magisk modules. But also for other needs.
open terminal while in bootloader and type:
Code:
fastboot flash recovery recovery_op7t_adb_10.0.0.7_by_Killswitch.img
reboot into recovery u can use as well:
Code:
fastboot reboot recovery
you can follow this guide on how to remove magisk modules
Download: GDrive
Enjoy and good luck!
Click to expand...
Click to collapse
Man, this is a great post. Thank you. May I ask what you did to enable ADB shell? Did you modify default.prop in the ramdisk?
bynarie said:
Hi
I have extracted stock recovery from latest OTA 10.0.7 EU for our OP7T and enabled adb shell, so now i am putting this one up here to come handy for those soft bricked using some wonky magisk modules. But also for other needs.
open terminal while in bootloader and type:
reboot into recovery u can use as well:
Man, this is a great post. Thank you. May I ask what you did to enable ADB shell? Did you modify default.prop in the ramdisk?
Click to expand...
Click to collapse
https://forum.xda-developers.com/7t...n-os-stock-recovery-adb-t3991865/post80866897
Sent from my OnePlus7TPro using XDA Labs
In theory, we should be able to make a backup of our own boot.img with this?
qbanlinxx said:
In theory, we should be able to make a backup of our own boot.img with this?
Click to expand...
Click to collapse
Yea im trying it right now..
Is this the right path?
/dev/block/bootdevice/by-name/boot_a
/dev/block/bootdevice/by-name/boot_b
Edit:
Yea its the right path. The img can be patched with Magisk and you can root the device by flashing the boot.img
qbanlinxx said:
In theory, we should be able to make a backup of our own boot.img with this?
Click to expand...
Click to collapse
I just DD'd boot.img. This seemed to work for backing up partitions.
Recovery images don't differ across variant models do they?
This would work on global version for instance?
shorty1993 said:
Recovery images don't differ across variant models do they?
This would work on global version for instance?
Click to expand...
Click to collapse
If it doesn't work, I have a Global insecure 1.0.0.7 recovery image I could share.
grandpajiver said:
If it doesn't work, I have a Global insecure 1.0.0.7 recovery image I could share.
Click to expand...
Click to collapse
Please do. Would rather use the global if possible.
shorty1993 said:
Please do. Would rather use the global if possible.
Click to expand...
Click to collapse
Hi,
Here's a link to Google Drive for 1.0.0.7 Global ADB-enabled stock recovery:
https://drive.google.com/open?id=1e59CRQKJ9ymBKui2mtCrnbLhZ06ukvYe
Reboot your phone to fastboot (bootloader).
fastboot reboot fastboot to get to FastbootB or whatever its called. It'll look like stock recovery.
Fastboot flash recovery insecure_recovery_GLO_1007.img
Reboot.
Profit.
grandpajiver said:
Hi,
Here's a link to Google Drive for 1.0.0.7 Global ADB-enabled stock recovery:
https://drive.google.com/open?id=1e59CRQKJ9ymBKui2mtCrnbLhZ06ukvYe
Reboot your phone to fastboot (bootloader).
fastboot reboot fastboot to get to FastbootB or whatever its called. It'll look like stock recovery.
Fastboot flash recovery insecure_recovery_GLO_1007.img
Reboot.
Profit.
Click to expand...
Click to collapse
Are there differences between the Global and EU recoveries?
iruiz2 said:
Are there differences between the Global and EU recoveries?
Click to expand...
Click to collapse
wouldn't say there ist much difference.. its just recovery
Sent from my [device_name] using XDA-Developers Legacy app
obol2 said:
Yea im trying it right now..
Is this the right path?
/dev/block/bootdevice/by-name/boot_a
/dev/block/bootdevice/by-name/boot_b
Edit:
Yea its the right path. The img can be patched with Magisk and you can root the device by flashing the boot.img
Click to expand...
Click to collapse
Can you please explain me how you did it ?
samyhaff said:
Can you please explain me how you did it ?
Click to expand...
Click to collapse
Boot into recovery, go in cmd and type adb.
type
dd if=/dev/block/bootdevice/by-name/boot_a of =/data/media/0/nameoffile.img
dd if=/dev/block/bootdevice/by-name/boot_b of =/data/media/0/nameoffile.img
patch one of them in magisk manager, fastboot boot patched img, direct install magisk in magisk manager