Related
OKay,
Philz/Advanced CWM build for;
SM-T230/NU/31 Philz 6.59 and Aromafm [Marvell]
https://www.androidfilehost.com/?w=files&flid=28382
SM-T237p Philz 6.59 [QCOM/MSM] Thanks @hookem2oo7 for testing.
https://www.androidfilehost.com/?fid=95916177934549969
SM-T230nt Philz 6.59 [QCOM/MSM] Thanks @Erus Tyrannus for testing.
https://www.androidfilehost.com/?fid=23991606952612934
SM-T330/NU/31 Philz 6.58.9
https://www.androidfilehost.com/?w=files&flid=23544
SM-T530NU/31/35 Philz 6.58.9
https://www.androidfilehost.com/?w=files&flid=23537
SM-T533 Philz 6.58.9 <-this is a temporary test build - no noobs.
https://www.androidfilehost.com/?fid=24336189125296272
After usage you may need to reflash the stock LP 5.1 releases recovery.
https://www.androidfilehost.com/?fid=24338798368260119 <-This zip is recovery flashable.
Click to expand...
Click to collapse
NOTE remove .md5 extension if Odin complains -- 64gig sdcards must be formatted exfat
As soon as i get reorganized i will get device trees reconstructed and posted.
My hard drive failed and i lost most of what i had.
the source code for Philz recovery is here https://github.com/PhilZ-cwm6/philz_touch_cwm6
----------------------------------------------------------------------------------
Thanks to the following for support and testing
Huge thanks to @g_ding84 for testing the SM-T230/NU31 process
A special thanks to @Aben314 for supporting me in my efforts.
On the SM-T33XX- @Rusell - the main man , primary tester @pre4speed initial tester and moral support @Flashalot device tree and moral support
On the SM-T53XX thanks to @tgalal @sub77 for their previous work and @mariojuniorjp for testing on the sm-t531
-----------------------------------------------------------------------------------
These are the tools you need if you don't have them already - Odin and Samsung USB Drivers
https://www.androidfilehost.com/?w=files&flid=25040
----------------------------------------------------------------------------------
For builders, this is the default.prop of the sm-t330nu recovery, to make sure your rom assert entries will be correct
Code:
# PHILZ SM-T330NU-MB74
#
persist.security.ams.enforcing=0
ro.adb.secure=0
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.sys.usb.config=adb
persist.sys.root_access=1
ro.build.product=milletwifi[COLOR="Red"]ue[/COLOR]
ro.product.device=milletwifi[COLOR="Red"]ue[/COLOR]
ro.product.model=SM-T330NU
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=US
ro.board.platform=msm8226
Sources
Device Trees Per Build
MOD EDIT: LINKS REMOVED
dev host link does not work for me.
rsktkr1 said:
dev host link does not work for me.
Click to expand...
Click to collapse
Did you read the OP completely?
If so, my apologies. Sometimes devhost goes down for inexplicable reasons.
Try again later.
m
UPDATE; see OP
SM-T330NU Philz/ADV CWM recovery
corrected storages, sdcard1 , usb-otg
TODO - orient to landscape, adjust/optimize read/write speeds
I now have the sm-t330nu so, hopefully, things will pick up.
m
EDIT- Okay, new version, storages corrected, no landscape orientation yet.
YOU MUST MAKE A NEW BACKUP AFTER INSTALL !
Backups made with previous version encounter selinux context/permission problem
and result in bootloop.
Double-checking file info for Odin
Does the sm-t330nu-philz-recovery-D-3.tar file for Odin contain the same update as the zip? I'm still new to Odin, but I've gleaned from searching that it can't use flashable zip files, they must be tar or tar.md5. Want to make sure I get the correct file before giving this a go. Thanks for a small bit of hand-holding.
K,
hi, no, odin flash d-3 first then flash the update in recovery.
i'm working on final build, so once that's done the current odin flashable file and the update zip
will be replaced, read the update post as well as the OP and be aware of the selinux issue ,
i believe i've corrected that issue in the current/final build i'm working on and should hopefully
have it up soon
thanks.
m.
Final Build Uploaded
Okay,
see OP for link, will be moving things over to android file host soon [mirror], will add link to OP
Final Build, orientation will remain in portrait, from what i've been reading, i would need to modify
kernel source to achieve landscape, which i won't be doing until after i get a rom [successful] to build through, sorry.
I tried increasing font size but, in portrait the text becomes jumbled and looks sloppy, [ yuck ! ]
The virtual keys will come in handy
Storages and selinux issue corrected, sdcard1 :good: usb-otg :good:
As a precaution, make a brand new backup, especially to preserve your full stock rom !
When/if i get landscape orientation and font sizes done i will release a really final version,
provided someone else doesn't do it first.
Sorry for the goofs and delays.
m
Thank you all!!!!
I'm getting a MD5 error when attempting to flash this Recovery to my T330NU Galaxy tab 4 8.0 Via ODIN
I tried redownloading it several times and got the same results.. I tried to flash this over the TWRP recovery port, its not mounting Cache so I can't flash the Zip..
Zaphodspeaks said:
I'm getting a MD5 error when attempting to flash this Recovery to my T330NU Galaxy tab 4 8.0 Via ODIN
I tried redownloading it several times and got the same results.. I tried to flash this over the TWRP recovery port, its not mounting Cache so I can't flash the Zip..
Click to expand...
Click to collapse
Z,
hi,
the .md5 extension can be removed, meaning, rename blah.recovery.tar.md5 to blah.recovery.tar
i scripted the odin packing process for my recovery builds a while back so, the md5 gets added as a matter of course.
the recovery will flash, as a step to defeat the automatic restoration of the stock recovery by the rom,
uncheck auto restart/reboot in odin and perform your flash, wait for the RES OK message, give it a second or two longer,
then disconnect your tab and use the three button combo to force boot to recovery, home,volume-up,power
from recovery reboot as normal.
m
moonbutt74 said:
Z,
hi,
the .md5 extension can be removed, meaning, rename blah.recovery.tar.md5 to blah.recovery.tar
i scripted the odin packing process for my recovery builds a while back so, the md5 gets added as a matter of course.
the recovery will flash, as a step to defeat the automatic restoration of the stock recovery by the rom,
uncheck auto restart/reboot in odin and perform your flash, wait for the RES OK message, give it a second or two longer,
then disconnect your tab and use the three button combo to force boot to recovery, home,volume-up,power
from recovery reboot as normal.
m
Click to expand...
Click to collapse
Ill do just that.. While I was sleeping, that idea did occur to me
Edit, yup that worked! Thanx..
Edit: Like the TWRP recovery, this recovery won't mount Cache..?
deleted, no longer relevant.
Pulling this conversation into the right thread.
I have the milletwifiUE SM-T330NU. This recovery wouldn't flash on it. The title is misleading b/c this recovery isn't for all of the SM-T330NU devices. Since it wouldn't flash, there isn't any harm done, but having read almost every other thread in the Tab 4 forum, I'd suggest pointing out the code name of each device is important in the OP. There are differences between the SM-T330NUs apparently.
Still, M, thank you for your work on the device. If you can link me to directions on how to pull a recovery.log or boot.img or whatever you may need to include the milletwifiue, I'd be glad to. If you've already posted those directions and I missed them, point me to the post.
Can you make one for smt331
Dewang rocky said:
Can you make one for smt331
Click to expand...
Click to collapse
D,
hi, try this version, flash via odin. http://d-h.st/de2u click the download now button.
the name of the file is sm-t331-Philz-6_58_9-recovery-round1.tar
m
xnatex21 said:
Pulling this conversation into the right thread.
I have the milletwifiUE SM-T330NU. This recovery wouldn't flash on it. The title is misleading b/c this recovery isn't for all of the SM-T330NU devices. Since it wouldn't flash, there isn't any harm done, but having read almost every other thread in the Tab 4 forum, I'd suggest pointing out the code name of each device is important in the OP. There are differences between the SM-T330NUs apparently.
Still, M, thank you for your work on the device. If you can link me to directions on how to pull a recovery.log or boot.img or whatever you may need to include the milletwifiue, I'd be glad to. If you've already posted those directions and I missed them, point me to the post.
Click to expand...
Click to collapse
The recovery is for the milletwifi sm-t330nu, again if you read the op you will see the codename clearly stated in the posted default.prop.
If i understand your issue, you either attempted to flash this recovery's .zip installation from another recovery, or you attempted to flash
a modified repackaged "stock" rom in which, during the process, the assert in the updater-script determined your device to be incorrect.
In which case your custom rom and/or previous custom recovery are in error.
I say this bluntly yet, without malice, I have done this before and have a fairly good handle on it. I would certainly modify a version for you
if you provide me with the actual original stock boot or recovery image for your device. Images from custom/modded roms will not do.
m
moonbutt74 said:
The recovery is for the milletwifi sm-t330nu, again if you read the op you will see the codename clearly stated in the posted default.prop.
If i understand your issue, you either attempted to flash this recovery's .zip installation from another recovery, or you attempted to flash
a modified repackaged "stock" rom in which, during the process, the assert in the updater-script determined your device to be incorrect.
In which case your custom rom and/or previous custom recovery are in error.
I say this bluntly yet, without malice, I have done this before and have a fairly good handle on it. I would certainly modify a version for you
if you provide me with the actual original stock boot or recovery image for your device. Images from custom/modded roms will not do.
m
Click to expand...
Click to collapse
If I'm one of the only people that would benefit from it, lets not worry about it. At this point I don't have the stock recovery b/c I flashed twrp first and then tried to flash this.
I see you did post the code name in the OP but I think it would help to point out that there are sm-t330nu variants, like mine. Coming from years of flashing, I know most people here are used to checking model #s that are posted in the title. Its very unusual to get a model with different code names and not a different carrier, in this case wifi (as opposed to Verizon ot Sprint etc).
Edit: typos
X,
hi,
the ue thing is weird, , i am wondering if my tab might have been a refurbished device.
this should do you, it the same recovery adjusted to milletwifiue
Derp on me, sorry https://www.androidfilehost.com/?fid=95887005526787734
the name of the file is sm-t330nu-Philz-6_58_9-milletwifiue-recovery.zip
I'll add it to OP and make an edit. Let me know if you have an issue.
m
moonbutt74 said:
X,
hi,
the ue thing is weird, , i am wondering if my tab might have been a refurbished device.
this should do you, it the same recovery adjusted to milletwifiue
https://www.androidfilehost.com/?fid=95887005526787126
I'll add it to OP and make an edit. Let me know if you have an issue.
m
Click to expand...
Click to collapse
M,
I flashed it in twrp .3 and it failed. It didn't give me the wrong device error though.
My device is a refurb too. I pulled this from bug report, not sure if it helps:
milletwifiue-user 4.4.2 KOT49H T330NUUEU1ANCA
Only should work on Android 10 based ROMs
External wifi adapters need custom kernel compiling
I've suffered to get the Kali Nethunter working on custom ROMs
U need free storage available (not sure cuz I've formated data then installed and it's been a while but ig not less than 15 gbytes)
Here are the steps :
1.download the file from offensive security website
(Not sure if external links are allowed but here it is ) : https://www.offensive-security.com/kali-linux-nethunter-download/
(Just look for miui davinci file)
2.Download it and extract on whatever device u want the copy the extracted folder to the roo of the storage (of course not the "/" folder the "storage/emulated/0" one
3. Go into extractedFolder/data/app/
And make sure every app there is installed especially the nethunter.apk
4.copy the "kalifs-arm64-full.tar.xz" file to the root
"storage/emulated/0"
5.Open the Nethunter app and go into chroot manager and install chroot
5.Browse for the file location which you copied into the root "storage/emulated/0" and it will start installing it will take up too 10 to 15 minutes
6.You are done now but HID attacks aren't working
7.Go to USB arsenal and change "reset" into anything that has " hid" untill you see a successful toast message then save config to database
Done.
If it helped you hit the thanks button (your choice)
I'll be available asap if anyone has a question
how about monitor mode on wifi dongle? have you tested it?
yaro666 said:
how about monitor mode on wifi dongle? have you tested it?
Click to expand...
Click to collapse
Monitor mode works by default using the internal card
For external I don't have one to test it now
But I am sure it will work as long as it has a supported chip
batman957 said:
I've suffered to get the Kali Nethunter working on custom ROMs
U need free storage available (not sure cuz I've formated data then installed and it's been a while but ig not less than 15 gbytes)
Here are the steps :
1.download the file from offensive security website
(Not sure if external links are allowed but here it is ) :
(Just look for miui davinci file)
2.Download it and extract on whatever device u want the copy the extracted folder to the roo of the storage (of course not the "/" folder the "storage/emulated/0" one
3. Go into extractedFolder/data/app/
And make sure every app there is installed especially the nethunter.apk
4.copy the "kalifs-arm64-full.tar.xz" file to the root
"storage/emulated/0"
5.Open the Nethunter app and go into chroot manager and install chroot
5.Browse for the file location which you copied into the root "storage/emulated/0" and it will start installing it will take up too 10 to 15 minutes
6.You are done now but HID attacks aren't working
7.Go to USB arsenal and change "reset" into anything that has " hid" untill you see a successful toast message then save config to database
Done.
If it helped you hit the thanks button (your choice)
I'll be available asap if anyone has a question
Click to expand...
Click to collapse
i have a mi 9t with unlocked bootloader twrp also rooted using magisk, i flashed my nethunter kernel, but it gets stuck at the nethunter boot logo, how do i fix this, do i need a specific force encryption or something? ive restored the system couple times using mi flash, ive been trying for a couple days now, if you have any solutions please lmk a step by step guide, also is there a way i can do this without flashing it, but also get all the tools working?
Niksa2 said:
i have a mi 9t with unlocked bootloader twrp also rooted using magisk, i flashed my nethunter kernel, but it gets stuck at the nethunter boot logo, how do i fix this, do i need a specific force encryption or something? ive restored the system couple times using mi flash, ive been trying for a couple days now, if you have any solutions please lmk a step by step guide, also is there a way i can do this without flashing it, but also get all the tools working?
Click to expand...
Click to collapse
Sorry I wish I was able to help
But the tag says [CUSTOM ROM]
SO I HAVE No Idea
Maybe try this
Don't flash any thing just follow the procedure listed above and It may work
Just don't flash anything
It won't work, cuz you need kernel for monitoring for example wifi - stock kernels can't put wlan1 (internal or external) wifi to monitor mode, so you won't be able to pentest routers
batman957 said:
Sorry I wish I was able to help
But the tag says [CUSTOM ROM]
SO I HAVE No Idea
Maybe try this
Don't flash any thing just follow the procedure listed above and It may work
Just don't flash anything
Click to expand...
Click to collapse
Which custom ROM? Is it possible with AOSP based (I am on havoc 3.6 now)
hruaiapunte said:
Which custom ROM? Is it possible with AOSP based (I am on havoc 3.6 now)
Click to expand...
Click to collapse
Any whatever you want
I tested on evoX and titanium os
Niksa2 said:
i have a mi 9t with unlocked bootloader twrp also rooted using magisk, i flashed my nethunter kernel, but it gets stuck at the nethunter boot logo, how do i fix this, do i need a specific force encryption or something? ive restored the system couple times using mi flash, ive been trying for a couple days now, if you have any solutions please lmk a step by step guide, also is there a way i can do this without flashing it, but also get all the tools working?
Click to expand...
Click to collapse
Are you trying to install Nethunter onto stock miui rom?
If so, take a look at
https://forums.kali.org/showthread.php?48308-Xiaomi-Mi-9t-Not-Work-Hid-Monitor-Bad-USB
This worked for me
I'm running full Nethunter on Mi9t stock MiUi Global 11.0.4 rooted with Magisk.zip (via TWRP) and everything just works like a charm. No problems capturing packets, injection support is doing fine and HID seems to work (never tested it but NH App shows its working)
All i had to do was root the Mi9t with Magisk (flashed the zip via TWRP), after checking that everything went well ive booted back into TWRP and flashed the nethunter-2020.2-pre3-davinci-miui-ten-kalifs-full.zip downloaded at https://www.offensive-security.com/kali-linux-nethunter-download/
After that i had to reflash Magisk.zip again (directly after flashing the nethunter.zip without rebooting the device!) and thats it.
As the pre-build images you get at offensive-security allready come with the tweaked kernel u need for injection and monitor mode, theres no need to flash a 'nethunter kernel' afterwards...it works 'out of the box'
Flashing another nethunter kernel afterwards will most probably result in a bootloop... (tried myself a few times with hasty nethunter kernel)
Ive only tried this with the officiall pre-built images on a stock MiUi ROM.
If you want to flash NH on a Costum ROM, you should probably go with the Guide from OP
Happy Hunting
hello, after so many tests they managed like this:
1. twrp orange fox
2.format and wipe
3.flash: fw "miui_DAVINCIGlobal_V11.0.5.0.QFJMIXM_aaab5b40c7_1 0.0.zip" flash "AOSiP-10-Quiche-davinci-20200526-gapps.zip" flash "Magisk-v19.3.zip" flash "Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip"
4.reboot
5.inizializza and upgrade Magisk (download update Magisk to phone)
6.download Busybox module (Magisk)
7.poweroff
8.twrp flash "nethunter-2020.2-davinci-miui-ten-kalifs-full.zip" flash (Magisk downloaded to phone) flash "Disable_Dm-rity_ForceEncrypt_03.04.2020.zip"
9.reboot
HardcodedString said:
Are you trying to install Nethunter onto stock miui rom?
If so, take a look at
https://forums.kali.org/showthread.php?48308-Xiaomi-Mi-9t-Not-Work-Hid-Monitor-Bad-USB
This worked for me
I'm running full Nethunter on Mi9t stock MiUi Global 11.0.4 rooted with Magisk.zip (via TWRP) and everything just works like a charm. No problems capturing packets, injection support is doing fine and HID seems to work (never tested it but NH App shows its working)
All i had to do was root the Mi9t with Magisk (flashed the zip via TWRP), after checking that everything went well ive booted back into TWRP and flashed the nethunter-2020.2-pre3-davinci-miui-ten-kalifs-full.zip downloaded at https://www.offensive-security.com/kali-linux-nethunter-download/
After that i had to reflash Magisk.zip again (directly after flashing the nethunter.zip without rebooting the device!) and thats it.
As the pre-build images you get at offensive-security allready come with the tweaked kernel u need for injection and monitor mode, theres no need to flash a 'nethunter kernel' afterwards...it works 'out of the box'
Flashing another nethunter kernel afterwards will most probably result in a bootloop... (tried myself a few times with hasty nethunter kernel)
Ive only tried this with the officiall pre-built images on a stock MiUi ROM.
If you want to flash NH on a Costum ROM, you should probably go with the Guide from OP
Happy Hunting
Click to expand...
Click to collapse
henghst69 said:
1. twrp orange fox
2.format and wipe
3.flash: fw "miui_DAVINCIGlobal_V11.0.5.0.QFJMIXM_aaab5b40c7_1 0.0.zip" flash "AOSiP-10-Quiche-davinci-20200526-gapps.zip" flash "Magisk-v19.3.zip" flash "Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip"
4.reboot
5.inizializza and upgrade Magisk (download update Magisk to phone)
6.download Busybox module (Magisk)
7.poweroff
8.twrp flash "nethunter-2020.2-davinci-miui-ten-kalifs-full.zip" flash (Magisk downloaded to phone) flash "Disable_Dm-rity_ForceEncrypt_03.04.2020.zip"
9.reboot
Click to expand...
Click to collapse
Does Kali work with QFJEUXM 11.0.5?
By following the cited guide
https://forums.kali.org/showthread.php?48308-Xiaomi-Mi-9t-Not-Work-Hid-Monitor-Bad-USB
I don't see anything about:
- Format Data and wipe
Is it necessary?
-"AOSiP-10-Quiche-davinci-20200526-gapps.zip
Is it necessary to flash, maybe Kali breaks the stock built-in GApps?
-"Disable_Dm-rity_ForceEncrypt_03.04.2020.zip"
Is it also necessary to flash, Magisk cannot make it pass SafetyNet without?
Also, does installing Kali affect:
- Widevine L1 (dropping to L3)
- 4G/4G+ (by disabling some bands or carrier aggregation)?
One more question, what would be a procedure to go back to stock?
Manually updating to the stock Recovery/ZIP firmware from System update/Choose update package would be enough or flashing Fastboot/TGZ firmware by Mi Flash Tool will be needed?
zgfg said:
Does Kali work with QFJEUXM 11.0.5?
By following the cited guide
https://forums.kali.org/showthread.php?48308-Xiaomi-Mi-9t-Not-Work-Hid-Monitor-Bad-USB
I don't see anything about:
- Format Data and wipe
Is it necessary?
-"AOSiP-10-Quiche-davinci-20200526-gapps.zip
Is it necessary to flash, maybe Kali breaks the stock built-in GApps?
-"Disable_Dm-rity_ForceEncrypt_03.04.2020.zip"
Is it also necessary to flash, Magisk cannot make it pass SafetyNet without?
Also, does installing Kali affect:
- Widevine L1 (dropping to L3)
- 4G/4G+ (by disabling some bands or carrier aggregation)?
One more question, what would be a procedure to go back to stock?
Manually updating to the stock Recovery/ZIP firmware from System update/Choose update package would be enough or flashing Fastboot/TGZ firmware by Mi Flash Tool will be needed?
Click to expand...
Click to collapse
-Does Kali work with QFJEUXM 11.0.5?
Well, somewhere i've read that it should work with 11.0.5 too but dont remember where...would have to search for it again to provide a link to you...
- Format Data and wipe
Not sure if its necessary, but i did so. Its always a good thing to do before flashing any ROM.
Just try it without that step and you'll see...you can always reflash to stock if you get any errors, so just give it a shot mate
-"AOSiP-10-Quiche-davinci-20200526-gapps.zip
Nope, thats not necessary for sure. I'm using it with the stock built gapps and its working fine
-Disable_Dm-rity_ForceEncrypt_03.04.2020.zip
Thats pretty strange with that ForceEncrypt step, some say they had to others not. I did not flash it to be honest and everythings okay so far. But theres a Chance that you will have to! Maybe it belongs to which ROM you are using (global,eu,chinese) but cant tell for sure...
So this one you will have to figure out yourself, sry.
-4G and LTE is working good for me, so i'd say kali isnt affecting it
-About Widefine, well i dont know to be honest...im watching Prime and Sky Go on the Phone sometimes but for the Quality Prime just says 'optimal' and Sky Go 'HD'...it looks great for sure but i cant tell the exact Quality....if theres a way to check that, let me know and i'll be happy to do that for you
-One more question, what would be a procedure to go back to stock?
I would just do a wipe/format and flash the stock MiUI image or better, your backup via TWRP (or any other custom Recovery)
For me, Fastboot by MiFlashTool is always the last option. If nothing else works, Fastboot is a Livesaver but thats just 'my way' of doing it, there are probably many others who say otherwise!
Sometimes it needs a lot of testing to figure out the best way for your specific device, so always do a backup and flash a custom recovery before flashing Nethunter. That way, its always posible to get back to Stock if you encounter any bootloops/problems after the installation.
Its like always while playing around with any OS...if it wont work, you just have to "Try Harder"
Im happy to help anyway, if you got any more Questions just shout out mate
HardcodedString said:
-Does Kali work with QFJEUXM 11.0.5?
Well, somewhere i've read that it should work with 11.0.5 too but dont remember where...would have to search for it again to provide a link to you...
- Format Data and wipe
Not sure if its necessary, but i did so. Its always a good thing to do before flashing any ROM.
Just try it without that step and you'll see...you can always reflash to stock if you get any errors, so just give it a shot mate
-"AOSiP-10-Quiche-davinci-20200526-gapps.zip
Nope, thats not necessary for sure. I'm using it with the stock built gapps and its working fine
-Disable_Dm-rity_ForceEncrypt_03.04.2020.zip
Thats pretty strange with that ForceEncrypt step, some say they had to others not. I did not flash it to be honest and everythings okay so far. But theres a Chance that you will have to! Maybe it belongs to which ROM you are using (global,eu,chinese) but cant tell for sure...
So this one you will have to figure out yourself, sry.
-4G and LTE is working good for me, so i'd say kali isnt affecting it
-About Widefine, well i dont know to be honest...im watching Prime and Sky Go on the Phone sometimes but for the Quality Prime just says 'optimal' and Sky Go 'HD'...it looks great for sure but i cant tell the exact Quality....if theres a way to check that, let me know and i'll be happy to do that for you
-One more question, what would be a procedure to go back to stock?
I would just do a wipe/format and flash the stock MiUI image or better, your backup via TWRP (or any other custom Recovery)
For me, Fastboot by MiFlashTool is always the last option. If nothing else works, Fastboot is a Livesaver but thats just 'my way' of doing it, there are probably many others who say otherwise!
Sometimes it needs a lot of testing to figure out the best way for your specific device, so always do a backup and flash a custom recovery before flashing Nethunter. That way, its always posible to get back to Stock if you encounter any bootloops/problems after the installation.
Its like always while playing around with any OS...if it wont work, you just have to "Try Harder"
Im happy to help anyway, if you got any more Questions just shout out mate
Click to expand...
Click to collapse
Thank you a lot for your answer.
Btw, few days ago I upgraded to QFJEUXM v11.0.6 (so no more 11.0.5), which is newer than the Kali pre-built image, but according to v11.0.6 Changelog only Security patch was updated
I'm still tempting to try Kali (currently having new official TWRP v3.4.0, Magisk Canary 20416 and Hasty kernel)...
You can check your Widevine Security level (still interested if you have L1) by
https://play.google.com/store/apps/details?id=flar2.devcheck
https://play.google.com/store/apps/details?id=com.androidfung.drminfo
By going back to stock you said flashing MIUI. - so you mean flashing ZIP/Recovery firmware through TWRP?
zgfg said:
Thank you a lot for your answer.
Btw, few days ago I upgraded to QFJEUXM v11.0.6 (so no more 11.0.5), which is newer than the Kali pre-built image, but according to v11.0.6 Changelog only Security patch was updated
I'm still tempting to try Kali (currently having new official TWRP v3.4.0, Magisk Canary 20416 and Hasty kernel)...
You can check your Widevine Security level (still interested if you have L1) by
https://play.google.com/store/apps/details?id=flar2.devcheck
https://play.google.com/store/apps/details?id=com.androidfung.drminfo
By going back to stock you said flashing MIUI. - so you mean flashing ZIP/Recovery firmware through TWRP?
Click to expand...
Click to collapse
No problem, i'm happy to help wherever i can :good:
-Btw, few days ago I upgraded to QFJEUXM v11.0.6...
Yeah, im not surprised bout that...sorry for the late answer :/
Thank you for pointing out these two Apps mate!
I've checked my Widevine Security Level and both Apps showing Widefine L1 (Screenshots attached) so no downgrade after flashing Nethunter
Yes thats correct, to get back to stock you would have to flash the ZIP/Recovery firmware through TWRP.Only if that doesnt work you'd have to do it through Fastboot.
If you did a full backup (i.e. through TWRP) of your system before flashing Nethunter, you would be able to restore it by flashing the recovery,dtbo,boot and system images one by one through TWRP/Fastboot (not sure but i think it should be enough to just reflash the system.img, boot.img and dtbo.img to get your pre-Nethunter Setup/Specs back (English isnt my native Language so in case you dont get what im trying to explain...that means your stock 11.0.6 with TWRP v3.4.0, Magisk Canary 20416 and the Hasty kernel including all your Settings and Stuff)
You wouldnt have to flash a 'naked stock rom' if Nethunter doesnt work
If you're still not comfortable enough to install Nethunter onto your Device, just wait a few more Days.
I will try to get Nethunter running on the 11.0.6 ROM myself as soon as i have some more time!Will also try it with your Specs/Setup by then
Hi, i cant install chroot.
image transparente png
sinanlenfom said:
Hi, i cant install chroot.
image transparente png
Click to expand...
Click to collapse
Obviously you set the wrong Folder Name...just choose one of the three options from Screenshot 1!?
But to be honest, and i really dont want to offend you, if you couldnt figure that one out yourself you shouldnt install Nethunter at all...
@zgfg
Sorry mate, wasnt able to try it so far.....very busy at work atm! Will do the next few Days
HardcodedString said:
@zgfg
Sorry mate, wasnt able to try it so far.....very busy at work atm! Will do the next few Days
Click to expand...
Click to collapse
Thanks
HardcodedString said:
Sorry mate, wasnt able to try it so far.....very busy at work atm! Will do the next few Days
Click to expand...
Click to collapse
Ok, I installed NetHunter zip image for Davinci over QFJEUXM v11.0.6.0 and re-rooted with Magisk Canary v20419.
Ran NetHunter app and chroot.
I think it looks ok - screenshots attached
Btw, tried yesterday Wifite to 'break' three WPA WLANs (Private, not Enterprise) for whom I actually know passwords - their passwords are weak like vesna1970 or 136923457
Wifite was running for two or three hours, trying Pixie-Dust, NULL PIN, PIN Attack, Handshake capture but eventually failed for all three connections
I will set up a WEP AP at home next week to test again, but who nowadays still uses WEP. Almost everybody would be using WPA, and with stronger passwords than above
If so, I doubt it is of big (educational) use and I am suspect about YT movies where they successfully break WPA in 30 minutes (or more)
Receiving a notification to update NetHunter from Installed 2020.2 to 2020.2?!
But the Update fails with Error -110 - on screenshots
Btw, I have successfully updated (couple of times) packages from NetHunter app, currently there is nothing to update there
Edit:
Fixed the NH app update notification: open NetHunter Store, Settings, Expert mode and untick Privilege Extention.
Let it update the NetHunter app
Hello, I'm a noob in modding a phone, but I want to try
Some years ago a friend of mine bought a redmi5plus in China and brought it in Europe; he put on it a global MIUI and registered it with a MI account.
Now he sold me his phone, and correctly disassociated it from his account.
What it would be nice to do is to remove the MIUI global, and put a stock android OS, like android 8.1 (with google apps), because I want to give it to my father, and he's a bit old, he learned the standard android and can't fit with the MIUI one (he still asks "where the hack is the menu button with all my apps?" and similar).
So, a pure OS, no MIUI, no non-google-basic apps.
Since I'm quite a noob (ok, I have a computer science degree but I've never touched a phone), could you please help me on learning how to do this?
(or if there's a guide on how to do that, what are the OS list i can mount on it, no problem, just link me)
edit: specs are:
- model: redmi 5 plus
- android version: 7.1.2 N2G47H
- MIUI version: MIUI global 9.2 | stabile 9.2.6.0(NEGMIEK)
- band base: 953_GEN_PACK-1.129634.1.131253.1
- kernel version: 3.18.31-perf-g439dbb6
Thanks!
First you must unlock the bootloader with waiting
https://en.miui.com/unlock/download_en.html
The unlock tool will tell u how long.
Then u need a recovery like
https://forum.xda-developers.com/re...t/recovery-orangefox-recovery-xiaomi-t4054193
This work for orangefox too
https://www.xda-developers.com/how-to-install-twrp/
After you flash over ADB, you must flash again the orangefox.zip in recovery.
And roms look in the right section
You can find many guides at xda
joke19 said:
First you must unlock the bootloader with waiting
https://en.miui.com/unlock/download_en.html
The unlock tool will tell u how long.
Then u need a recovery like
https://forum.xda-developers.com/re...t/recovery-orangefox-recovery-xiaomi-t4054193
This work for orangefox too
https://www.xda-developers.com/how-to-install-twrp/
After you flash over ADB, you must flash again the orangefox.zip in recovery.
And roms look in the right section
You can find many guides at xda
Click to expand...
Click to collapse
Thanks so much man, at least now I know the right steps to do!
Hope everything will be good, tomorrow I'll try.
p.s.: is it necessary orangefox or just TWRP is enough?
tiec7 said:
Thanks so much man, at least now I know the right steps to do!
Hope everything will be good, tomorrow I'll try.
p.s.: is it necessary orangefox or just TWRP is enough?
Click to expand...
Click to collapse
Is your choice what recovery u use, I like orangefox.
joke19 said:
Is your choice what recovery u use, I like orangefox.
Click to expand...
Click to collapse
ah i see I think I need a lightweight one, because this phone will be used by my father
Do you think it's possible to install a standard android 8.1 ? does it exist as a rom?
tiec7 said:
ah i see I think I need a lightweight one, because this phone will be used by my father
Do you think it's possible to install a standard android 8.1 ? does it exist as a rom?
Click to expand...
Click to collapse
No, but you can make miui that it look like stock with a theme and a customer launcher.
Maybe you can use the Xiaomi eu rom.
Google it. It's nice
Sent from my Mi Note 10 using XDA Labs
joke19 said:
No, but you can make miui that it look like stock with a theme and a customer launcher.
Maybe you can use the Xiaomi eu rom.
Google it. It's nice
Sent from my Mi Note 10 using XDA Labs
Click to expand...
Click to collapse
mmm i had a look but i think i'll try evolutionX ( the one in this post: https://forum.xda-developers.com/redmi-note-5/development/evolution-x-4-4-redmi-5-plus-t4122467 )
is there a small guide on how to do the steps to install it? =)
Until now I just disassociated this phone from the old account (was my friend account who gave this phone to me) and I just looked into developer settings and i saw that is already unlocked (don't exactly know what does it means but is it, if there's some explanation of those things in some guide...)
ok, i tried to install it without success, the phone now goes in black screen and stays there.
I installed TWRP with
fastboot devices
fastboot flash recovery twrp.img
boot twrp.img
this step was ok, if i do it from a command line connecting my phone in fastboot mode to the pc, it starts.
then i went on "install" and installed the zip file
EvolutionX_4.5_vince-10.0-20200714-0943-OFFICIAL.zip
from here
https://forum.xda-developers.com/redmi-note-5/development/evolution-x-4-4-redmi-5-plus-t4122467
after that, i rebooted the redmi 5 plus and boom, black screen after some seconds of "mi" screen.
can anyone help me?
ok, i've managed it: i followed these guides: https://forum.xda-developers.com/android/general/how-to-fix-unable-to-mount-data-t3830897
now, I installed havocOS but I just realized there's no camera app. why? how can i do to have it?
edit: no wifi and no mobile connection!! without any of the roms I tried!
someone has any idea?
duplicate
tiec7 said:
ok, i've managed it: i followed these guides: https://forum.xda-developers.com/android/general/how-to-fix-unable-to-mount-data-t3830897
now, I installed havocOS but I just realized there's no camera app. why? how can i do to have it?
edit: no wifi and no mobile connection!! without any of the roms I tried!
someone has any idea?
Click to expand...
Click to collapse
Flash orangefox, install the last global firmware, reboot to the recovery, format not wipe the data partition, reboot again and then your rom
https://xiaomifirmwareupdater.com/firmware/vince/
Sent from my Mi Note 10 using XDA
joke19 said:
Flash orangefox, install the last global firmware, reboot to the recovery, format not wipe the data partition, reboot again and then your rom
https://xiaomifirmwareupdater.com/firmware/vince/
Sent from my Mi Note 10 using XDA
Click to expand...
Click to collapse
the problem with no SIM and no WIFI was exactly the firmware. I didn't even know a phone had a firmware!!
Thanks!!
Now it works with EvolutionX; absolutely no chance of working with
- crDroid
- MSM Xtended
- coltOS
- resurrection remix
- HavocOS
with all of these it gives me a misterious "error 7" during install. Do you know what is this error?
Ok, i solved.
I was absolutely CERTAIN that the ROM I wanted to install was the one made for my redmi 5 plus,
(filename is Havoc-OS-v3.7-20200726-vince-Official-GApps.zip )
so what i did was
- I went to META-INF\com\google\android inside the zip file with winrar
- unzipped to desktop the updater-script file
- since my phone is TOTALLY EMPTY, i changed those lines:
* removed line
Code:
run_program("/tmp/install/bin/backuptool.sh", "backup", "/dev/block/bootdevice/by-name/system", "ext4");
* removed line
Code:
run_program("/tmp/install/bin/backuptool.sh", "restore", "/dev/block/bootdevice/by-name/system", "ext4");
* then, since I read a lot about that but no one ever posted the result, i tried changing this line
Code:
block_image_update("/dev/block/bootdevice/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat.br", "system.patch.dat") ||
abort("E1001: Failed to update system image.");
with this line:
Code:
block_image_update("/dev/block/bootdevice/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat.br", "system.patch.dat");
and i re-inserted this file draggin and droppin it in the winrar window, where the old file was; DO NOT CHANGE THE NAME OF THE ZIP or it will be thrown an error on the zip name;
- wiped system, dalvik, cache, data (if it gives some errors, reboot and retry; if still errors, i formatted data in ext2 then re-formatted in ext4 )
- installed the modded zip
everything went ok.
I am anyway really disappointed by this community, not a single help in 3 days, just "follow guides". Just thanks to joke19 who at least tried to help me giving me some basic info.
tiec7 said:
Ok, i solved.
I was absolutely CERTAIN that the ROM I wanted to install was the one made for my redmi 5 plus,
(filename is Havoc-OS-v3.7-20200726-vince-Official-GApps.zip )
so what i did was
- I went to META-INF\com\google\android inside the zip file with winrar
- unzipped to desktop the updater-script file
- since my phone is TOTALLY EMPTY, i changed those lines:
* removed line
* removed line
* then, since I read a lot about that but no one ever posted the result, i tried changing this line
with this line:
and i re-inserted this file draggin and droppin it in the winrar window, where the old file was; DO NOT CHANGE THE NAME OF THE ZIP or it will be thrown an error on the zip name;
- wiped system, dalvik, cache, data (if it gives some errors, reboot and retry; if still errors, i formatted data in ext2 then re-formatted in ext4 )
- installed the modded zip
everything went ok.
I am anyway really disappointed by this community, not a single help in 3 days, just "follow guides". Just thanks to joke19 who at least tried to help me giving me some basic info.
Click to expand...
Click to collapse
Me too. Nobody push the thanks button in this thread.
Sent from my Mi Note 10 using XDA Labs
Hello developers,
I bought a Huawei P20 lite a few days ago after verifing, that lineage is possible to install on those phones.
Now, after struggling for 3 days to install lineage, I decided to post here.
First some information about my phone:
Device: Huawei P20 lite dual SIM, 4GB RAM, 64GB internal (ANE-L21, i guess?)
Fastboot Info (I ran those commands when creating this post):
fastboot oem get-build-number: ANE-LX1 9.1.0.257(C432E6R1P7) (from what I understood, ANE-LX1 and ANE-L21 Firmwares are the same?)
fastboot oem get-product-model : ANE-LX1
fastboot getvar version: FALED, Command not allowed
fastboot getvar vendorcountry: HW/EU
When I got the phone, I got my bootloader unlock code first.
I then successfully updated the phone to the newest version (the official Huawei approach, using HiSuite).
After that, I unlocked the bootloader with no problems and flashed TWRP.
I needed to try a few versions to find one that's working as the official ones for that phone kept freezing, I finally found one by Pretorian08 that's working).
Then I formatted to get rid of encryption, did the wipe procedure, cleared the cache, data and system partition and installed the newest lineage build and GAPPS.
After rebooting, the Phone showed me the usual "your device has been unlocked and can't be trusted"- dialog, and tried to boot then.
From here on, nothing happened.
I tried every build I could find, including the most actual one from tonight (lineage-16.0-20201214-nightly-anne-signed.zip).
Some builds would reboot after some time and show the shortened warning message, then boot directly into Recovery.
I totally bricked my phone somewhere on the way (multiple times I think), but could unbrick it by flashing rescue_recovery_kernel, rescue_recovery_ramdisk and rescue_recovery_vendor with appropriate img files extracted from a "Anne-L01 Anne-L21 9.1.0.132(C432E5R1P7T8)" - Firmware and then going back to zero by installing a stockrom via dload and unlocking the bootloader again.
I then tried several other custom Roms, but the outcome is always the same: The phone just freezes with the warning message still visible while trying to boot up, or it boots into TWRP.
ROMs I've tried (I'll write the filenames to provide more info):
- Havoc OS-v3.2-20200215-ARM64AB-GSI.img
- Resurrection Remix ARM64_AB_20191205.img (this is the only custom ROM that will do ANYTHING at all: It will show the Red RessurectionMix Bootlogo, but sadly it won't boot past that point)
- Treble AOSP losq-v224-201017-arm64-bvN.img
With the above 3, installing GAPPS is not possible because "not enough free space in system partition"
- Every possible lineage build for that phone
As stated before, I'm struggling with the phone for 3 days now, so I followed a whole bunch of threads and advices, flashed multiple firmware files using different methods and tried like 7 different TWRP versions. With other words: I did a lot of things, which yould possibly mess up the phone and maybe I did something wrong at some point.
Maybe, I flashed a wrong Firmware while trying to unbrick or something like that. Can you guys help me understand what I'm doing wrong?
I don't like it if people post questions in a forum and then don't share what they figured out, so I'll post 's a little update after 6 days:
Here's a serious advice, if you're considering to buy this phone because there are lineage builds available: forget it.
I mean in most cases it seems to work somehow (from what I read), but from my experience I can say now, that there are phones where it apparently just doesn't work.
I've wasted over one week of my holiday working nonstop on that phone, I've downloaded about 50GB of different firmware files, recoveries, patches and custom Roms and flashed my firmware like 40 times. Best thing I could archieve is an indefinitely looping bootlogo in AOSP, lineage won't even get to that point.
I've tried every lineage build available, i've tried EMUI versions from 9.1.0.0X up to 9.1.0.200 (it is stated multiple times that the .200 will definitely work), no chance. I even tried a rollback to EMUI 8 via Hisuite and using old lineag builds in the end.
The fact that I didn't get any advice in this forum leads me to the conclusion, that no one has an Idea on what the problem is here either.
As I don't feel good with using a phone that still has original google stuff and huawei spy/bloatware installed, the only option that is left to me is just throwing it away and using some old phone. That's sad and a real waste of material and time, as the phone is brand new, but using the stockrom is no option to me. I really don't know what went wrong, I've already successully installed lineage (and cyanogenmod before) on more than 8 other devices, always without any problems.
So even if you (think you) know what you're doing, I can't recommend buying this device with the intention of using lineage.
user_name_duplicate said:
So even if you (think you) know what you're doing, I can't recommend buying this device with the intention of using lineage.
Click to expand...
Click to collapse
P20 lite is not so bad, maybe you are doing something wrong...
I've installed without problems Havoc, LOS 16.0, LOS 17.1unofficial, AOSP 10, losq-v224-201017 etc. etc...
P.S.: If you "hate" Google and Google's bloatware (like me ) only, you can simply rebrand your phone to chinese Nova 3e.
Or, choose Custom ROM based on Stock with KangVip settings , stable enough to be used as your daily driver." ( e.g. https://forum.xda-developers.com/hu...m-emui-8-0-kangvip-p20-lite-catuva21-t3813564
https://forum.xda-developers.com/hu...-emui-8-0-0-huawei-p20-lite-dual-sim-t3813604) . Using KangVip settings you can disable completely GAPPs .
(My primary phone is at the moment Mate 10 lite rebranded to chinese Maimang 6 (to get away from GAPPS ) . Among other things, better battery life, lower data consumption (using FUT) etc.)
Hi -Alf-, thank you for replying.
-Alf- said:
P20 lite is not so bad, maybe you are doing something wrong...
Click to expand...
Click to collapse
You're right, it's not the phone, it's me. I guess I am doing something wrong, but I don't have the slightest clue what that is.
Any suggestions?
I've already invested a lot of time and have more or less resignated, but thanks to covid lockdown I'm basically trapped inside the house and might aswell give it another try.
Rebranding is an option, you're right. I already have downloaded a nova 3e Firmware, if nothing else works, I might try that.
Also, I'll have a look at the KangVip Roms, haven't heard of them before.
But to be honest, I think I wouldn't be satisfied with those options, at least not for a long time.
Getting lineage running on that phone is a task, the problem solver inside me is really commited to accomplish, because that was the intention I bought the phone with. Also, not being able to accomplish something that hundreds of other people already have done and that is proven to work is driving me nuts. I wouldn't have bothered trying to get it working for 10 days otherwise.
Unfortunately, availability of custom ROMs for Kirin devices is scarce.
Try Havoc 2.9 (requires EMUI 8)
Havoc 2.9
Hi -Alf-,
-Alf- said:
Try Havoc 2.9 (requires EMUI 8)
Click to expand...
Click to collapse
Tried that now, after downgrading to EMUI 8 via HiSuite, I did exactly what you wrote in that thread. The outcome is the same as with every other ROM I've tried: I see the "your device has been unlocked and can't be trusted" screen, then after a while it tells me that "my device is booting now" and just does nothing except rebooting every 10 or so minutes.
Luckily those devices seem to be fairly indestructible, as long as the Bootloader is open and FRP is disabled, so I'll give it some more tries.
-Alf- said:
Unfortunately, availability of custom ROMs for Kirin devices is scarce.
Click to expand...
Click to collapse
I bought the phone because I thought it was officially supported:
LineageOS Downloads
download.lineageos.org
Was that assumption wrong, is there some hint or exception, that I'm not seeing?
The phone was delivered some weeks late because the seller was out of stock. I guess it came directly from china. Is it possible, that I got a new hardware revision, which is not yet supported?
user_name_duplicate said:
I guess it came directly from china. Is it possible, that I got a new hardware revision, which is not yet supported?
Click to expand...
Click to collapse
It may be a fake, try to verify the authenticity on linked website
imei24
user_name_duplicate said:
I guess it came directly from china
Click to expand...
Click to collapse
Exactly, I saw for example Huawei P20 Pro with MediaTek proc.
Btw., I have installed this Havoc 2.9 three times without problem, so it's really very strange...
In fastboot mode run commands :
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
fastboot oem get-build-number
fastboot getvar vendorcountry
fastboot oem get-product-model
fastboot getvar rescue_version
and post the results please.
Some might fail, so don't worry about it.
You can also download "Device Info HW" apk and check your SoC (Kirin 659) Vendor (HiSilicon), ABI (arm64-v8a) etc.
On imei24, the device is listed as "Huawei P20 Lite" for both imeis, blacklist status is "clean". Recognized Serial is the same for both Imei numbers.
Only thing that's not clear to me is the warranty status:
Warranty start: 2018/7/23
Warranty end: 2018/8/6
So it can't be that new, at least not factory new, right?
I bought it on real.de, so I have no further information where it comes from. China was just my assumption because they where out of stock and delivered 2 or 3 weeks late. I can't really imagine that real is selling fake phones (on purpose). That really wouldn't help their image if people found out.
I ran the commands you provided:
fastboot oem oeminforead-CUSTOM_VERSION: FAILED
fastboot oem oeminforead-SYSTEM_VERSION : ANE-LX1 8.0.0.180(C432)
fastboot oem get-build-number : ANE-LX1 8.0.0.180(C432)
fastboot getvar vendorcountry: hw/eu
fastboot oem get-product-model: ANE-LX1
fastboot getvar rescue_version: rescue0.6
I will download the Device Info apk as soon as my device boots again (I will reflash the stock image once again).
Edit: Device Info HW is telling me I'm using a Kirin 659 SOC.
Okay, most of custom ROMs require lower build number, that's why I wrote that I tested Havoc 2.9 on .126. If you are running latest build number, it may cause your problems.
IMO it is time to clean your phone, extract from Oreo firmware (it doesn't matter which build number) ramdisk.img , kernel.img, recovery_ramdisk.img and erecovery_ramdisk.img and transfer to the SD card.
Download .126 Service ROM
8.0.126
unpack it and transfer dload file to the SD Card (without unpacking it)
Install
TWRP
over eRecovery, boot into TWRP, select Flash image and flash 4 files. Go back to main TWRP's panel > Reboot > Power Off.
Use three button combo to flash the ROM. This process will erase all your data and lock the bootloader again!!!
Unlock BL and try Havoc 2.9 . It must work!
Good luck.
Edit: I found on my MEGA :
https://mega.nz/#!o8FUVR6T!-1fl6TviRtgGbssuG9LgyssCJg4dwxa84luJmrnvSCg
https://mega.nz/#!gkdgnLBa!O8LVZF4J0NiEB78c9z4_FxASN0vWx3rOAIQdmhApAOQ
https://mega.nz/#!xpViTTSC!Q_5ieeEL0gpKROj35cvjc_TRddmkFTMsIxvOT6lS23Y
https://mega.nz/#!EhM2lZqK!yphxvKNUQueIryop44DmPflp7Iwi9c8ExeaCRqA-iY4
Hello Alf, thanks for your last reply!
Downgrading worked, that was the last thing I've tried before christmas.
I wanted to continue today, but found this thread you've posted in.
I thought I'd give it a try and now I'm running on lineage (which is what I initially wanted), sadly only the 15.1 version, but I don't need the newest version.
WiFi is working and, until now, it's running stable. I've installed 8.1. nano gapps (might try pico in the future) and magisk v21.
Maybe I'm lucky and in the next few weeks or months I'll find a working build of an android pie lineage.
I think with installed TWRP it should now be possible, to do a complete backup, mess around with the system (i.e. upgrade Android/Flash ROMs) and then restore it to my now working state, is that correct?
If that's the case, I'll try some other ROMs, including the havok ROM I've already downloaded.
Which partitions must be included in my backup to perform such operations?
For anyone else encountering my problem, here is what finally did the trick:
Code:
- downgrade to .126, following alfs procedure
- Flash TWRP by pretoriano80 (on recovery_ramdisk partition)
- do a wipe (format data to get rid of encryption, then via advanced wipe format cache partitions and system)
- install lineage 15 (link), last build is from 2020-10-27, so it's not an abandoned build
- install GAPPS 8.1
- install magisk v21
- wipe cache/Dalvik
- boot to system
Booting for the first time took a few minutes, but since then, it's running smooth and without any problems.
The only thing that's still an enigma to me is, why the LOS builds I initially tried (with EMUI 9.0.0.200) didn't work, even though other people don't seem to have a problem with ANE-LX1 and LOS16. If anyone is reading this and has an answer to that question, please post!
For now, I'm happy with LOS 15. Thank you many many times, Alf! Greetings to Melmac!
user_name_duplicate said:
Thank you many many times, Alf!
Click to expand...
Click to collapse
No problem...
user_name_duplicate said:
Greetings to Melmac!
Click to expand...
Click to collapse
I'm currently struggling with the same issue. Tried every combination of TWRP with lineage 16 and gapps. Some roms I can get to boot but then not enough space for h gapps. I have tried to wipe system, data and cache to resize system partition which ends up in phone booting directly to TWRP. Other times I get to warning screen and end up with boot - loop. So I'm well a are off your frustration. However I have decided that I'm not gonna settle for version 15. I'm trying for 17 but much have to settle with lineage is 16..
Hi
Quite bored of Oneplus updates for my Nord 2 5G that transforms more and more the phone in publicity support for OnePlus CEO messages, and adding features I don't care at all, I'm looking to flash it with an alternative ROM.
What is most stable and operational ROM for that device currently ? The version of the device I have is DN2103 (bought in Switzerland).
Thanks for your advices,
Vincèn
Tried them all. Evolution X is the most often updated and works the best for me.
Hey there!
I also need some much needed insight in how to continue with this device (DN2103 bought in NL, Europe; just updated from 11.A.14 to 11.A.21). I suspect I will probably need the same answer as OP is looking for.
This is my second OnePlus, I was using a OnePlus X before running my first and only ROM, Lineage OS, to be able to move on to Android 10. Then screen broke for the second time after I had already fixed up the whole phone myself before that using brand new parts (Screen, frame, backplate) except for the motherboard still original. So I decided it was time for a new device.
Really love the DN2103 itself, except for the whole rooting / OTA update process, although it was a good training in getting to know all the technicalities. I had been running rooted 11.A.14 since it came out till yesterday, because I was avoiding dealing with the whole process again.
Anyway I kicked myself under my butt and got myself to 11.A.21 now. I was planning to just continue updating OOS till the latest 11.C.10 / 11.C.13, because after all this effort, I'm too curious to not check out the new Android.
But I just happened to read some thread where people were saying that somewhere after 11.C.4 it's not possible anymore to get into fastboot / BROM mode and thus no means to get TWRP?? That sounds horrible, one mistake rooting and it would be a big mess, having to downgrade to OOS 11 again and bla bla bla, why the f...?
So, I just need to hear this from someone, is this correct? I'm too tired to investigate now myself after a 20h OTA/rooting session behind me and just 3h sleep.
And how is everyone dealing with it that wants root? Has everyone moved on to other ROMs for Android 12 / 13, because of this?
In the update process yesterday for some reason my phone did a complete wipe without asking / warning. So I really need to get to a stage in this update process where I can restore all my ****. I've been at this for 24h right now and was happy to do so as I was making steps. but now I suddenly got hit in the face by this news.
tl;dr PLEASE confirm/deny this news (underlined part above) and help me decide if the only comfortable way is to ditch OOS for a custom ROM to get Android 12 / 13 with root & TWRP. I've thrown 24 hours into OTA updating OOS 11, now got to 11.A.21, but phone somehow got wiped in process, so now I really need to finish upgrading and restore data, because I'm without all the apps / accounts etc. I depend on for daily life.
I do really enjoy the road but now I HATE being lost along the way. Show me the light and, if ROM, same question as OP
Sorry if a bit off-topic + long post...
Yes, you need to have android 11 to enter fastboot. I had 12 and had to downgrade. Trust me, this is the most fuked up thing.
wuttehhell said:
Yes, you need to have android 11 to enter fastboot. I had 12 and had to downgrade. Trust me, this is the most fuked up thing.
Click to expand...
Click to collapse
Stop waiting for oneplus. There are great roms on android 13 that work very nice. What i am using is Evolution X. Tried them all and this is the one i stick to. Found no bugs, very consistent updates and the team as i see work very fast on every bug people find.
Btw, u dont need root to change rom, only if you want. I personally dont use root and works great.
wuttehhell said:
Tried them all. Evolution X is the most often updated and works the best for me.
Click to expand...
Click to collapse
Thanks for the info, and noticed too in forum that it looks to be the most up-to-date and maintained ROM for DN2103 and it looks to have no more any blocking bugs such as Wifi or Bluetooth not working, or random reboots/crashes. I'm running right now version DN2103_11_C.12 with Android 12. Is it ok to upgrade to Evolution X straight ? as I see people speaking about downgrade first to Android 11 :/
wuttehhell said:
Stop waiting for oneplus. There are great roms on android 13 that work very nice. What i am using is Evolution X. Tried them all and this is the one i stick to. Found no bugs, very consistent updates and the team as i see work very fast on every bug people find.
Click to expand...
Click to collapse
Thanks a lot for confirming! I'd already read the thread and indeed Evolution looks like the best option, so that's decided then. Wish me luck flashing the ROM
And about root, I really have some essential mods that need root. For example Advanced Charge Controller (I use it with the GUI app ACCA for convenience, else it's only terminal). I limit my charging by default to 80%, which translates in about a 4x increase in lifetime of the battery. On normal days I don't need any more than that, and it always has the option to charge to 100% if you know you're gonna have a long day without charging capabilities.
vincebay said:
Thanks for the info, and noticed too in forum that it looks to be the most up-to-date and maintained ROM for DN2103 and it looks to have no more any blocking bugs such as Wifi or Bluetooth not working, or random reboots/crashes. I'm running right now version DN2103_11_C.12 with Android 12. Is it ok to upgrade to Evolution X straight ? as I see people speaking about downgrade first to Android 11 :/
Click to expand...
Click to collapse
As I understand, and as @wuttehhell just confirmed in this thread, once you update OxygenOS beyond Android 11, fastboot and BROM mode don't work anymore. This means you can't install a custom recovery like TWRP to flash a new ROM, neither can you flash it using fastboot.
This means you have to rollback to Android 11 first. Fortunately OnePlus has official rollback packages, which is just a .ZIP archive like any other update, except it will downgrade to a previous version. Warning: a rollback package will WIPE ALL DATA. So make sure to backup anything you need to keep before downgrading. The upside is you can do a clean flash of the ROM (flashing method where device gets wiped), which is the most stable method and gives you a fresh OS that will use less battery and such.
I think the process of downgrading itself is very simple though. If you get stuck let us know, there's many knowledgeable people here lucky for us so keep a positive attitude and with a little luck we'll both be running Evolution X in the coming days!
Releece said:
As I understand, and as @wuttehhell just confirmed in this thread, once you update OxygenOS beyond Android 11, fastboot and BROM mode don't work anymore. This means you can't install a custom recovery like TWRP to flash a new ROM, neither can you flash it using fastboot.
This means you have to rollback to Android 11 first. Fortunately OnePlus has official rollback packages, which is just a .ZIP archive like any other update, except it will downgrade to a previous version. Warning: a rollback package will WIPE ALL DATA. So make sure to backup anything you need to keep before downgrading. The upside is you can do a clean flash of the ROM (flashing method where device gets wiped), which is the most stable method and gives you a fresh OS that will use less battery and such.
I think the process of downgrading itself is very simple though. If you get stuck let us know, there's many knowledgeable people here lucky for us so keep a positive attitude and with a little luck we'll both be running Evolution X in the coming days!
Click to expand...
Click to collapse
@Releece thanks for the details and so if I have well understood the whole process:
backup datas
Downgrade to Android 11 using the OTA downgrade package and procedure from oneplus (which implies a full reset of device)
Reboot at least one tine in Android 11
Flash TWRP
Reboot in TWRP (be careful not to boot Android or I'll have to reflash TWRP)
Flash Evolution X zip
Boot normally and enjoy Evolution X
Am I correct ? I have seen also that the phone has the same annoying double "bank" when you flash it that I had on previous OnePlus phones. Does it imply I have to do each flashing process on both banks ?
Thanks
vincebay said:
@Releece thanks for the details and so if I have well understood the whole process:
backup datas
Downgrade to Android 11 using the OTA downgrade package and procedure from oneplus (which implies a full reset of device)
Reboot at least one tine in Android 11
Flash TWRP
Reboot in TWRP (be careful not to boot Android or I'll have to reflash TWRP)
Flash Evolution X zip
Boot normally and enjoy Evolution X
Am I correct ? I have seen also that the phone has the same annoying double "bank" when you flash it that I had on previous OnePlus phones. Does it imply I have to do each flashing process on both banks ?
Thanks
Click to expand...
Click to collapse
Yep that should do it, looks like you did your research and understand the process.
I had the same question earlier. Strangely I found that the Nord 2 does not have A / B partitioning. I can only detect an A-partition with apps designed to test it. I didn't have to do anything extra / another way while rooting with Magisk, OTA updates or flashing ROM. I thought A/B was enforced on all phones since Android 10 or sth, but apparently not all.
I would add one extra step, after you reboot into TWRP (before flashing the ROM) make a backup of all the individual partitions one by one (so you can restore any single partition in the future), even the tiniest ones.
Some contain calibration data for e.g. Bluetooth and fingerprint sensor that are specific to your device. Now this whole process should leave them untouched, but if anything ever happens to them, the only way to get your phone working again is to send your phone to a service centre, so it's a good idea to have everything backed up.
They will be stored in the TWRP folder in /sdcard/, which is the folder you can see on your PC. So after backing them all up, you can just copy them to your PC.
I successfully flashed Evolution yesterday, and all went well Initially the new Android 13 UI was a bit of a shock from what I was used to, but I'm starting to like it already, especially after going over the settings. And it works smooooth like butter. The only thing that annoyed me was the haptic feedback, which feels very mushy instead of snappy. But putting vibration strength to low helps a lot. Maybe I can find a way to modify it later.
I had one little hickup: Evolution install instructions say this for TWRP before flashing ROM:
"3. Tap [Wipe] , then [Format data]. type "yes" and Enter"
But when I did this, it removed the media folder at /data/media/ instead of just emptying it. I remember it gave me a pop-up saying something like, for /data/media/ to get populated I would probably need to boot to system. But if I would've done that stock would overwrite recovery.
I don't have a lot of knowledge about this, but this folder gets mounted to /sdcard/ and is where your internal storage is mounted to. So after the wipe I wanted to copy the ROM .zip to my phone using the file manager. Windows did recognize my phone as having internal storage, and I could open it, but it didn't see any file/folder/free space and I couldn't copy anything to it.
I solved it by renaming ROM to sth simple like evolution.zip, placing it inside platform-tools folder, and then using ADB push command, so it looked like:
ADB push C:/platform-tools/evolution.zip /data/
It doesn't give any feedback while copying and I didn't even see much disk usage on Windows task manager, so I was about to get nervous and close the terminal, but then it suddenly completed successfully and I could see the evolution.zip in TWRP file manager. After that flashing took just a few minutes and everything went perfect.
Now I don't know if it's maybe a typo in the instructions or if TWRP had a bug, but I don't think so as it specifically gave me a prompt about it. I think it's better to just tap [Wipe] and then do the usual factory reset slider, with data, dalvik and cache selected. Think I'll make a post later in the Evolution thread to ask.
Good luck!
Hi, I don´t like the colors on Oxygen OS. I don't know if it's cause by our screen or is something related with the ROM. In Samsung or Xiaomi colors are more brilliant and saturated. In Evolution ROM, can you modify this issue?
So I have been able to dowgrade my DN2103 to 11_A20 running Android 11 but I'm stuck there !
Each time I try to flash twrp or load it in device I get that:
[email protected]:~/Bureau$ fastboot boot twrp.img
Sending 'boot.img' (131072 KB) OKAY [ 3.310s]
Booting FAILED (remote: 'not allowed in locked state')
fastboot: error: Command failed
[email protected]:~/Bureau$ fastboot flash recovery twrp.img
Sending 'recovery' (131072 KB) OKAY [ 3.371s]
Writing 'recovery' FAILED (remote: 'not allowed in locked state')
fastboot: error: Command failed
I have unlocked OEM protection into it and allow USB debug. Any ideas what's the problem ?
damn was a long time I had not done Android flashing so was a little more complicated but made it (well it looks to be so far Will see if it boots after initial setup and now hanging on the Phone initial preparation but should go very soon I think
Thanks