Related
[ROOT][UNLOCKED] Wiko Ride - bootloader unlocked, mtk-su'able, & $35 at wally world
Just found this phone on the list of mtk-su'able devices and grabbed one, and to my surprise the bootloader is unlocked as well. Comes with Pie. I haven't been able to build a TWRP that runs on it, but I just dd'ed the boot partition and patched it offline with Magisk and dd'ed it back. It's only a 2GB/16GB phone but worth the price to have a real rooted phone again vs having to deal with temproots.
rlrevell said:
Just found this phone on the list of mtk-su'able devices and grabbed one, and to my surprise the bootloader is unlocked as well. Comes with Pie. I haven't been able to build a TWRP that runs on it, but I just dd'ed the boot partition and patched it offline with Magisk and dd'ed it back. It's only a 2GB/16GB phone but worth the price to have a real rooted phone again vs having to deal with temproots.
Click to expand...
Click to collapse
I was just thinking about picking one of these up today! They have them in stock at a local walmart. I found an article on getandroidtips that links to a GSI ROM.
Do you think the GSI ROM will actually work on the Wiko Ride without TWRP? Do you just flash the zip using the stock recovery?
columbustalley said:
I was just thinking about picking one of these up today! They have them in stock at a local walmart. I found an article on getandroidtips that links to a GSI ROM.
Do you think the GSI ROM will actually work on the Wiko Ride without TWRP? Do you just flash the zip using the stock recovery?
Click to expand...
Click to collapse
Yeah, I've since given the phone away but IIRC you don't even need the mtk-su, you just unlock the bootloader and flash whatever you want. I flashed with fastboot, not having a working TWRP. @tecknight managed to build a TWRP that almost worked before I kinda lost interest. You do have to sign the images using the AVB process, but IIRC it doesn't care who signed them, just that they're signed. I can look through my notes for more details. You'll definitely learn a lot about how AVB works if nothing else, and the phone seems very hard to accidentally brick.
I *think* I have dd dumps of every partition from before I changed anything saved somewhere.
rlrevell said:
Yeah, I've since given the phone away but IIRC you don't even need the mtk-su, you just unlock the bootloader and flash whatever you want. I flashed with fastboot, not having a working TWRP. @tecknight managed to build a TWRP that almost worked before I kinda lost interest. You do have to sign the images using the AVB process, but IIRC it doesn't care who signed them, just that they're signed. I can look through my notes for more details. You'll definitely learn a lot about how AVB works if nothing else, and the phone seems very hard to accidentally brick.
I *think* I have dd dumps of every partition from before I changed anything saved somewhere.
Click to expand...
Click to collapse
That's great! So I just grab the zip for the GSI ROM... sign it with AVB... then I can flash it with fastboot? I think I'll pick one up tomorrow and give it a go. I'll backup all my partitions before I do anything. If I get stuck I'll let you know thanks for the great info!
I got it working! Got root using the mtk-su then backed up all the partitions using a script on github. Enabled bootloader unlock in settings then from PC did fastboot flashing unlock. Flashed the vbmeta.img using fastboot to disable AVB checks. Wiped system then flashed the arm64 Android 10 GSI a/b ROM to system using fastboot. Everything working as expected so far!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
back up all partitions with script on github
columbustalley said:
I got it working! Got root using the mtk-su then backed up all the partitions using a script on github.
Click to expand...
Click to collapse
which github script is that ? I am trying to do the same thing ! :highfive:
s4goa said:
which github script is that ? I am trying to do the same thing ! :highfive:
Click to expand...
Click to collapse
I used the project called dump-android-partitions. It worked in Cygwin on Windows 10 for me. It requires root on your device as well.
partn BAK sh script
columbustalley said:
It requires root on your device as well.
Click to expand...
Click to collapse
https://codeload.github.com/for2ando/dump-android-partitions/zip/master
looks like a good option for
adb shell
columbustalley said:
I got it working! Got root using the mtk-su then backed up all the partitions using a script on github. Enabled bootloader unlock in settings then from PC did fastboot flashing unlock. Flashed the vbmeta.img using fastboot to disable AVB checks. Wiped system then flashed the arm64 Android 10 GSI a/b ROM to system using fastboot. Everything working as expected so far!
Click to expand...
Click to collapse
So I also got lineage 17.1 up and running pretty well. Did you have any luck getting open gapps installed? No amount of searching produced a twrp for Wiko ride and I even started down the rabbit hole of maybe making my own twrp device tree and compiling from source but then I noticed the android 10 branch of twrp is still wip so that sounds like a bad idea. Maybe manual install through adb and temp root?
aroganone said:
So I also got lineage 17.1 up and running pretty well. Did you have any luck getting open gapps installed? No amount of searching produced a twrp for Wiko ride and I even started down the rabbit hole of maybe making my own twrp device tree and compiling from source but then I noticed the android 10 branch of twrp is still wip so that sounds like a bad idea. Maybe manual install through adb and temp root?
Click to expand...
Click to collapse
I actually use this phone without any google play services. I use F-Droid and Aurora for managing apps. Sorry about that mate!
There might be an easy solution though. If you use a GSI ROM that comes with gapps pre-installed everything should work fine in theory right?
Search google for this image and give it a try. It's the gapps version of the ROM that I currently use.
Havoc-OS-v3.7-20200709-Official-GApps-a64-ab.img.xz
This is absolutely incredible! Normally Pie Bootloader's are locked (as well as Android 8+). To see this is absolutely amazing! If anyone needs custom tools made I can provide a link as well as the source code to build the tools
TheExploitedOne said:
This is absolutely incredible! Normally Pie Bootloader's are licked (as well as Android 8+). To see this is absolutely amazing! If anyone needs custom tools made I can provide a link as well as the source code to build the tools
Click to expand...
Click to collapse
It is pretty great to see an "unlicked" ; ) bootloader on such a cheap device. Unfortunately they are now out of stock in all of the stores in my area and I don't see it listed on the Walmart website anymore. Hopefully they ship another batch!
Thanks for all the info. I’ll definitely check out havoc. I’m completely new to android and the custom rom scene so this has been a great learning experience. So far it’s a fantastic little retroarch emulation device for the money.
aroganone said:
Thanks for all the info. I’ll definitely check out havoc. I’m completely new to android and the custom rom scene so this has been a great learning experience. So far it’s a fantastic little retroarch emulation device for the money.
Click to expand...
Click to collapse
You'll absolutely love the journey too I started at a young age (14 and I'm 22 now) in the hacking scene. It's been absolutely incredible with what I've learned about Android as well as getting to build a custom rim from the sources with my own modifications
---------- Post added at 08:32 PM ---------- Previous post was at 08:32 PM ----------
columbustalley said:
It is pretty great to see an "unlicked" ; ) bootloader on such a cheap device. Unfortunately they are now out of stock in all of the stores in my area and I don't see it listed on the Walmart website anymore. Hopefully they ship another batch!
Click to expand...
Click to collapse
I meant locked lol
Try checking out Amazon they usually have them
columbustalley said:
I actually use this phone without any google play services. I use F-Droid and Aurora for managing apps. Sorry about that mate!
There might be an easy solution though. If you use a GSI ROM that comes with gapps pre-installed everything should work fine in theory right?
Search google for this image and give it a try. It's the gapps version of the ROM that I currently use.
Havoc-OS-v3.7-20200709-Official-GApps-a64-ab.img.xz
Click to expand...
Click to collapse
So I ended up trying (arm64 boots, a64 doesn't):
Havoc-OS-v3.7-20200709-Official-GApps-arm64-ab.img.xz
I get all the way to the every end of setting up all the google account and setting and it hangs on: All Set. "Swipe up to get started". Eventually it just goes to sleep.
Rebooting it loads for a while and then hangs on the havoc logo. Any ideas or any other images with gapps cooked in that I can try? I've wiped data and cache.
Some screen shots:
aroganone said:
So I ended up trying (arm64 boots, a64 doesn't):
Havoc-OS-v3.7-20200709-Official-GApps-arm64-ab.img.xz
I get all the way to the every end of setting up all the google account and setting and it hangs on: All Set. "Swipe up to get started". Eventually it just goes to sleep.
Rebooting it loads for a while and then hangs on the havoc logo. Any ideas or any other images with gapps cooked in that I can try? I've wiped data and cache.
Some screen shots:
Click to expand...
Click to collapse
I've actually had a similar issue but I assumed it was because of some mistake I made during the process. I got a second Wiko Ride on Ebay and ran through the steps again and discovered that you need to do a full wipe with the SP Flash Tool. Be very careful though because you could lose your MEID and MAC. Make sure to back up all partitions before using the "Format all + download" function. After I did the full format with SP Flash Tool I restored the nvram and nvdata partitions from my backup. You need to edit an XML to accomplish this there are guides on Youtube. Here are some other notes that I made during the process mind you it's not comprehensive as it doesn't even have the SP Flash Tools steps but it may help you.
Unlock bootloader in developer options
Boot into fastboot
#fastboot flashing unlock
Install mtk-easy-su and magisk
#adb install mtk-easy-su.apk
#adb install magisk.apk
Set magisk to "auto"
Backup nvram and nvdata partitions using cygwin and dump-android-partitions.sh
#./dump-android-partitions.sh -s SERIALNUMBER nvram
#./dump-android-partitions.sh -s SERIALNUMBER nvdata
Unlock SIM using Miracle Thunder
Boot into fastboot
#fastboot --disable-verification flash vbmeta vbmeta.img
#fastboot erase system
#fastboot flash system .\Havoc-OS-v3.7-20200709-Official-arm64-ab.img
#fastboot -w
#fastboot reboot
0
columbustalley said:
I've actually had a similar issue but I assumed it was because of some mistake I made during the process. I got a second Wiko Ride on Ebay and ran through the steps again and discovered that you need to do a full wipe with the SP Flash Tool. Be very careful though because you could lose your MEID and MAC. Make sure to back up all partitions before using the "Format all + download" function. After I did the full format with SP Flash Tool I restored the nvram and nvdata partitions from my backup. You need to edit an XML to accomplish this there are guides on Youtube. Here are some other notes that I made during the process mind you it's not comprehensive as it doesn't even have the SP Flash Tools steps but it may help you.
Unlock bootloader in developer options
Boot into fastboot
#fastboot flashing unlock
Install mtk-easy-su and magisk
#adb install mtk-easy-su.apk
#adb install magisk.apk
Set magisk to "auto"
Backup nvram and nvdata partitions using cygwin and dump-android-partitions.sh
#./dump-android-partitions.sh -s SERIALNUMBER nvram
#./dump-android-partitions.sh -s SERIALNUMBER nvdata
Unlock SIM using Miracle Thunder
Boot into fastboot
#fastboot --disable-verification flash vbmeta vbmeta.img
#fastboot erase system
#fastboot flash system .\Havoc-OS-v3.7-20200709-Official-arm64-ab.img
#fastboot -w
#fastboot reboot
Click to expand...
Click to collapse
So I need a nudge in the right direction. Where do I get/extract/create the scatter file? I've backed up every partition manually but I'm a bit stuck on the part where you need to load the scatter file for SP Flash Tool.
aroganone said:
So I need a nudge in the right direction. Where do I get/extract/create the scatter file? I've backed up every partition manually but I'm a bit stuck on the part where you need to load the scatter file for SP Flash Tool.
Click to expand...
Click to collapse
If you've got the MT65xx use MTK Droid Tools
TheExploitedOne said:
If you've got the MT65xx use MTK Droid Tools
Click to expand...
Click to collapse
tried it but MTK Droid Tools apparently doesn't support newer chips. It pulled the following data but didn't generate the block data.
Hardware : MT6761V/CAB
Model : W-U300
Build number : treble_arm64_bvN-userdebug 10 QQ3A.200705.002 eng.crossg.20200713.132209 test-keys
Build date UTC : 20200713-132131
Android v : 10
Baseband v: MOLY.LR12A.R3.MP.V31.3.P39
Kernel v : 4.9.117+ ([email protected]) (Android (4691093 based on r316199) clang version 6.0.2 (https://android.googlesource.com/toolchain/clang 183abd29fc496f55536e7d904e0abae47888fc7f) (https://android.googlesource.com/toolchain/llvm 34361f192e41ed6e4e8f9aca80a4ea7e9856f327) (based on LLVM 6.0.2svn)) #2 SMP Fri Nov 1 14:21:38 CST 2019
I found stock firmware with the scatter file here but not sure how much I trust it:
https://romprovider.com/wiko-u300-firmware/
I also was looking at a newer tool : Wwr MTK
but haven't tried it yet.
Hello, has anybody tried some GSI roms? Maybe the havoc os? I've heard that they should work with any Snapdragon powered device. I need to wait 6 days until my bootloader is unlocked and maybe somebody tested some roms already. Thanks in advance and stay healthy
I'm currently running phh's gsi with gcam as a daily driver ?
bigyin said:
I'm currently running phh's gsi with gcam as a daily driver ?
Click to expand...
Click to collapse
Okay nice. Are there any major bugs or do you use it as a daily driver?
Effzeh1948 said:
Okay nice. Are there any major bugs or do you use it as a daily driver?
Click to expand...
Click to collapse
For me I'm running it as a daily, there are a few bugs ie finger print scanner doesn't work but I just use pin for security anyway.
I was quite surprised how well it actually runs and very fast compared to miui, great battery etc.
bigyin said:
For me I'm running it as a daily, there are a few bugs ie finger print scanner doesn't work but I just use pin for security anyway.
I was quite surprised how well it actually runs and very fast compared to miui, great battery etc.
Click to expand...
Click to collapse
And 90hz display also works? If yes I will try it out once my bootloader is unlocked
Effzeh1948 said:
And 90hz display also works? If yes I will try it out once my bootloader is unlocked
Click to expand...
Click to collapse
No sorry just 60hz just now but tbh I've not actually missed 90hz.
There's an aosp Rom in the works at the moment for our device, so this is a good substitute until it's out for me personally.
Okay and is there anything I have to do special when I want to flash it?
bigyin said:
For me I'm running it as a daily, there are a few bugs ie finger print scanner doesn't work but I just use pin for security anyway.
I was quite surprised how well it actually runs and very fast compared to miui, great battery etc.
Click to expand...
Click to collapse
Does VoLTE work in this ROM?My SIM is Jio.
pnsdhrn said:
Does VoLTE work in this ROM?My SIM is Jio.
Click to expand...
Click to collapse
No not for me sorry.
---------- Post added at 12:48 PM ---------- Previous post was at 12:46 PM ----------
Effzeh1948 said:
Okay and is there anything I have to do special when I want to flash it?
Click to expand...
Click to collapse
For starters you must have "stock recovery" and not twrp as it won't work.
Are you good with fastboot etc?
Effzeh1948 said:
Hello, has anybody tried some GSI roms? Maybe the havoc os? I've heard that they should work with any Snapdragon powered device. I need to wait 6 days until my bootloader is unlocked and maybe somebody tested some roms already. Thanks in advance and stay healthy
Click to expand...
Click to collapse
So I can speak to using Phh's GSI ROM as I tried out the v222 patch not too long ago. They do infact work, but they are missing a couple of features - Fingerprint does not work at all, 90Hz is not working (stuck at 60Hz) even with forcing it with ADB refresh rate command, VoLTE / Wifi Calling does not work, but the core functionality works at least. The problem I had with using the GSI, is that I bought a Xiaomi Mi 10 because it was in the premium segment of smartphones... missing all these key features with something as simple as a in-screen fingerprint or 90Hz placed it below the premium device I originally purchased. That's just my personal opinion of course, it depends how much you value your freedom over your device as the GSI/project treble images allow you to do that. There is an entry on the Phh's list for our device for what works and what doesnt. Can't link due to posting verification. Nothing has changed in terms of me testing the v222 patch.
To get to the point of fastboot if you are not experienced with debugging shell scripting, this will be incredibly tricky. Some issues are not apparent unless you see them. For example, the instructions listed on the Phh table is the following:
$ fastboot flash recovery stock-recovery.img (using official miui recovery)
$ fastboot reboot fastboot
$ fastboot flash system system-quack-arm64-ab-gapps.img
$ fastboot -w (wipe userdata)
$ fastboot reboot
I can tell you these have a LOT of caveats. For example, do you know how to enable USB debugging on your device and have the correct fastboot for your OS? If you don't, you need to know how to. Secondly, inorder to reference the "stock recovery img" file, you must point it to the directory of the image file.. if you dont know how to do any of that youre going to have a seriously tough time. Lastly, one other protip I can give you is that during the fastbootd phase, ENSURE you have fastboot connectivity by doing "fastboot devices" ! That tripped me because I had the correct drivers for ADB and fastboot, but fastbootd is another implementation after android 10. So you must have the correct drivers if you dont see your device listed under fastboot devices during fastbootd. you can grab them by googling, they come from XIaomi cn website and enabling it through Windows device manager if you use Windows. They are not signed, so you will have to bypass signature verification on bootup setting for Windows. Good luck let me know if you go through with installing it, I'd like to see how Havok performs!
xda-jimjongs said:
So I can speak to using Phh's GSI ROM as I tried out the v222 patch not too long ago. They do infact work, but they are missing a couple of features - Fingerprint does not work at all, 90Hz is not working (stuck at 60Hz) even with forcing it with ADB refresh rate command, VoLTE / Wifi Calling does not work, but the core functionality works at least. The problem I had with using the GSI, is that I bought a Xiaomi Mi 10 because it was in the premium segment of smartphones... missing all these key features with something as simple as a in-screen fingerprint or 90Hz placed it below the premium device I originally purchased. That's just my personal opinion of course, it depends how much you value your freedom over your device as the GSI/project treble images allow you to do that. There is an entry on the Phh's list for our device for what works and what doesnt. Can't link due to posting verification. Nothing has changed in terms of me testing the v222 patch.
To get to the point of fastboot if you are not experienced with debugging shell scripting, this will be incredibly tricky. Some issues are not apparent unless you see them. For example, the instructions listed on the Phh table is the following:
$ fastboot flash recovery stock-recovery.img (using official miui recovery)
$ fastboot reboot fastboot
$ fastboot flash system system-quack-arm64-ab-gapps.img
$ fastboot -w (wipe userdata)
$ fastboot reboot
I can tell you these have a LOT of caveats. For example, do you know how to enable USB debugging on your device and have the correct fastboot for your OS? If you don't, you need to know how to. Secondly, inorder to reference the "stock recovery img" file, you must point it to the directory of the image file.. if you dont know how to do any of that youre going to have a seriously tough time. Lastly, one other protip I can give you is that during the fastbootd phase, ENSURE you have fastboot connectivity by doing "fastboot devices" ! That tripped me because I had the correct drivers for ADB and fastboot, but fastbootd is another implementation after android 10. So you must have the correct drivers if you dont see your device listed under fastboot devices during fastbootd. you can grab them by googling, they come from XIaomi cn website and enabling it through Windows device manager if you use Windows. They are not signed, so you will have to bypass signature verification on bootup setting for Windows. Good luck let me know if you go through with installing it, I'd like to see how Havok performs!
Click to expand...
Click to collapse
Which android 10 rom my phone need to be in (cn or global or it does not matter?) before I can flash GSI rom. Thanks for the answer.
[email protected] said:
Which android 10 rom my phone need to be in (cn or global or it does not matter?) before I can flash GSI rom. Thanks for the answer.
Click to expand...
Click to collapse
It doesn't particularly matter because you'll be replacing the system.img and recovery.img. Ensure you dont have TWRP and you're using stock recovery. You just need an unlocked bootloader and the necessary tools. Let us know how it goes.
Bluetooth audio dont works!
xda-jimjongs said:
So I can speak to using Phh's GSI ROM as I tried out the v222 patch not too long ago. They do infact work, but they are missing a couple of features - Fingerprint does not work at all, 90Hz is not working (stuck at 60Hz) even with forcing it with ADB refresh rate command, VoLTE / Wifi Calling does not work, but the core functionality works at least. The problem I had with using the GSI, is that I bought a Xiaomi Mi 10 because it was in the premium segment of smartphones... missing all these key features with something as simple as a in-screen fingerprint or 90Hz placed it below the premium device I originally purchased. That's just my personal opinion of course, it depends how much you value your freedom over your device as the GSI/project treble images allow you to do that. There is an entry on the Phh's list for our device for what works and what doesnt. Can't link due to posting verification. Nothing has changed in terms of me testing the v222 patch.
To get to the point of fastboot if you are not experienced with debugging shell scripting, this will be incredibly tricky. Some issues are not apparent unless you see them. For example, the instructions listed on the Phh table is the following:
$ fastboot flash recovery stock-recovery.img (using official miui recovery)
$ fastboot reboot fastboot
$ fastboot flash system system-quack-arm64-ab-gapps.img
$ fastboot -w (wipe userdata)
$ fastboot reboot
I can tell you these have a LOT of caveats. For example, do you know how to enable USB debugging on your device and have the correct fastboot for your OS? If you don't, you need to know how to. Secondly, inorder to reference the "stock recovery img" file, you must point it to the directory of the image file.. if you dont know how to do any of that youre going to have a seriously tough time. Lastly, one other protip I can give you is that during the fastbootd phase, ENSURE you have fastboot connectivity by doing "fastboot devices" ! That tripped me because I had the correct drivers for ADB and fastboot, but fastbootd is another implementation after android 10. So you must have the correct drivers if you dont see your device listed under fastboot devices during fastbootd. you can grab them by googling, they come from XIaomi cn website and enabling it through Windows device manager if you use Windows. They are not signed, so you will have to bypass signature verification on bootup setting for Windows. Good luck let me know if you go through with installing it, I'd like to see how Havok performs!
Click to expand...
Click to collapse
When I try to flash something to the system partition it says that there is no system partition. All I can flash to is the super partition.
i using Phh's GSI ROM but I have a problem with the bluetooth headphones are detected but I can't hear anything
Kabanoska said:
i using Phh's GSI ROM but I have a problem with the bluetooth headphones are detected but I can't hear anything
Click to expand...
Click to collapse
Unfortunately known issue.. You can use a USB C cable but it requires an additional fix: enable "using alternate audio policy" in phh setting->qualcomm feauture Fix for Media sound-> Fixed by enable "disable audio effects" in phh setting -> misc features
Basecatcherz said:
When I try to flash something to the system partition it says that there is no system partition. All I can flash to is the super partition.
Click to expand...
Click to collapse
Ensure you are on fastbootd not regular fastboot! It will be a different logo, like yellow/orange on your phone instead of blue. That is probably causing the error, you can get there by doing the command fastboot reboot fastboot.
is there any other gsi system will run on mi 10?
Kabanoska said:
is there any other gsi system will run on mi 10?
Click to expand...
Click to collapse
Probably most of them as they're GSIs
xda-jimjongs said:
Unfortunately known issue.. You can use a USB C cable but it requires an additional fix: enable "using alternate audio policy" in phh setting->qualcomm feauture Fix for Media sound-> Fixed by enable "disable audio effects" in phh setting -> misc features
Ensure you are on fastbootd not regular fastboot! It will be a different logo, like yellow/orange on your phone instead of blue. That is probably causing the error, you can get there by doing the command fastboot reboot fastboot.
Click to expand...
Click to collapse
Fastbootd is the fastboot user space, right? I got it in LR Team TWRP but fastboot doesnt recognize it.
How to enter the right one?
Mackay53 said:
Probably most of them as they're GSIs
Click to expand...
Click to collapse
I tried more than 10 none on mi10 did not start
I can't restore android in my tab s7 T-875 4G to old version
please help me
Almgrm2008 said:
I can't restore android in my tab s7 T-875 4G to old version
please help me
Click to expand...
Click to collapse
You won't be able to downgrade the normal way (via Odin) if you have upgraded to BUC1 or later.
Samsung incremented rollback protection at that point.
EDIT: The actual version number varies depending on model. It's the March security update, which I think for S7 (non-plus) would be BUC6.
LSS4181 said:
You won't be able to downgrade the normal way (via Odin) if you have upgraded to BUC1 or later.
Samsung incremented rollback protection at that point.
EDIT: The actual version number varies depending on model. It's the March security update, which I think for S7 (non-plus) would be BUC6.
Click to expand...
Click to collapse
Is it possible that there is no way to go back to an older version
Almgrm2008 said:
Is it possible that there is no way to go back to an older version
Click to expand...
Click to collapse
If you're not rooted, well, there really is no way back without voiding your warranty.
If you're rooted (warranty already voided), you might be able to dd the individual partitions inside super (after extracting them using lpunpack), if you use Ian's TWRP. I only did this for getting GSI to work, and I did not test if it's possible to boot an earlier stock image this way post-increment.
LSS4181 said:
If you're not rooted, well, there really is no way back without voiding your warranty.
If you're rooted (warranty already voided), you might be able to dd the individual partitions inside super (after extracting them using lpunpack), if you use Ian's TWRP. I only did this for getting GSI to work, and I did not test if it's possible to boot an earlier stock image this way post-increment.
Click to expand...
Click to collapse
Where can I find the Ian TWRP file for my device?
Almgrm2008 said:
Where can I find the Ian TWRP file for my device?
Click to expand...
Click to collapse
You may have to check the thread. Actually it's mainly for the S7 Plus (T976B).
From what I remember, back then there were few testers for the non-Plus S7 (T875) so the progress was limited at that time.
At present, it was reported to be working on T875, but the display were corrupted so you can only use the adb shell. I don't know how to make nandroid backups entirely from command line but for flashing the individual partitions via dd, the adb shell should be enough.
LSS4181 said:
You may have to check the thread. Actually it's mainly for the S7 Plus (T976B).
From what I remember, back then there were few testers for the non-Plus S7 (T875) so the progress was limited at that time.
At present, it was reported to be working on T875, but the display were corrupted so you can only use the adb shell. I don't know how to make nandroid backups entirely from command line but for flashing the individual partitions via dd, the adb shell should be enough.
Click to expand...
Click to collapse
Did you explain to me how?
Almgrm2008 said:
Did you explain to me how?
Click to expand...
Click to collapse
For TWRP I think you can just ask in the Telegram group (in Ian's TWRP thread).
I don't recommend flashing the stock Android 10 using the dd method, as I cannot assess what would be needed to get old Android 10 system working in your current state. In case there are some other rollback protections aside from the bootloader (I don't know), you risk bricking your device for good.
I've a thread in the guide section on how to flash GSI (credits to everyone who helped me getting everything working), and you can find how to use dd to flash system and vendor there. Again, it's only for GSI and I don't really think it's a good idea to flash older stock FW this way.
Will a previous version of Android backup TWRP work to restore on Target tab S6 currently running Android 12 4.1
but why do you want to down grade is there any performance problem i want to know because I am running the older version and I was considering to update .
Hello,
I found a firmware file for the Nord N20 5g. However, it is CPH2459_11_A.06, while my phone says it is GN2200_11_A.06. Would it still be possible to do a local update to pull the boot image, or must the CPH and GN match? I have the T-Mobile version, bootloader unlocked, and network unlocked , along with the July security patch.
Thanks!
Take a full-backup of your firmware and find out.. lol.
DrScrad said:
Take a full-backup of your firmware and find out.. lol
Click to expand...
Click to collapse
I'm unfortunately not that brave
Rogo00 said:
I'm unfortunately not that brave
Click to expand...
Click to collapse
Want me to give it a go?
DrScrad said:
Want me to give it a go?
Click to expand...
Click to collapse
It would be awesome just to see if it works, but I don't know if it would harm your phone or not, and I would feel terrible if it did.
i would try flashing to inactive slot then switch over and maintain your functional system
PsYk0n4uT said:
i would try flashing to inactive slot then switch over and maintain your functional system
Click to expand...
Click to collapse
I'm still too new to rooting to do this successfully, I'm afraid
cph2459 is the unlocked version of the N20 5G correct? could you link the firmware please?
It is the unlocked version. I have the TMO version but it is network unlocked. The firmware can be found here: https://mega.nz/file/MXckFawK#IZ1ypD5Ftqw5Oz3oaeHLahqfUeaD6DlTzHCjeR3oseg
Also, this one is GN2200, but it is 11_A.05. Would it downgrade with the current patch? https://mega.nz/file/lX1H3Z5C#hUVmdbWUFI0bt0WQZVfaenTfVwoOqlfn2oexY5uC-Hs
If the OTA contains patches for all the required images then it SHOULD. But don't take my word on that.
What exactly are you trying to accomplish? Do you simply need a backup? It would probably be best to load a prerooter gsi with DSU sideloader and just use Partitions Backup and Restore app from playstore and backup all your partitions then just add them all to a single archive to make it easier to manage. You can select in options to save as raw (.img) and then just compress them all into a single archive and that would make it even easier to retrieve the needed partition images if you happen to need to restore anything.
PsYk0n4uT said:
If the OTA contains patches for all the required images then it SHOULD. But don't take my word on that.
What exactly are you trying to accomplish? Do you simply need a backup? It would probably be best to load a prerooter gsi with DSU sideloader and just use Partitions Backup and Restore app from playstore and backup all your partitions then just add them all to a single archive to make it easier to manage. You can select in options to save as raw (.img) and then just compress them all into a single archive and that would make it even easier to retrieve the needed partition images if you happen to need to restore anything.
Click to expand...
Click to collapse
I see. Basically I'm just trying to obtain root access. You mentioned prerooted gsi? I will need to read up more on this. Man this would be a lot easier with TWRP lol
waiting to hear from someone about a twrp that has been in the works. we tried one yesterday that didnt work. a different device tree is needed from the one that was used.
using DSU loader you can temporarily load a prerooted gsi and back everything up and move it to your pc and then move the boot.img to your internal storage where you can easily find it with the magisk app. install and load the magisk app and patch the boot.img then move the patched boot image to your pc and flash it in fastboot. that will give you a permanent root unless you prefer to stick with the gsi you sideloaded. but keep in mind any gsi you load with DSU Sideloader will be gone when you reboot the phone and your back to your regular system. you can use the sticky command if you want to keep the gsi installed but be sure to allocate plenty of space for your gsi if you plan on using it long term
if your on the may or july security patch you should be able to just download the patched boot.img from my other thread. i posted the stock images too in case you need to go back to stock or have issues booting. that being said. its best to just make your own backups. the july patch is GN2200_11_A.06
PsYk0n4uT said:
if your on the may or july security patch you should be able to just download the patched boot.img from my other thread. i posted the stock images too in case you need to go back to stock or have issues booting. that being said. its best to just make your own backups. the july patch is GN2200_11_A.06
Click to expand...
Click to collapse
I didn't know you did the July patch as well. I will check it out now
Also if and when you do flash the magisk patched boot images, do this command before and/or after flashing the boot.img:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Someone else has tried this and lost radios..... Can maybe get everything working again by reflashing the FULL BACKUP you took before cross flashing.... This would be an experiment though so don't attempt if your not ready to spend some time researching and unbricking your device should it be necessary
I tried it. I'm bootlooped
bricklife4me said:
I tried it. I'm bootlooped
Click to expand...
Click to collapse
I was just about to ask if you had two different devices because remember me telling you to be careful and not get your flashes mixed up?
DrScrad said:
I was just about to ask if you had two different devices because remember me telling you to be careful and not get your flashes mixed up?
Click to expand...
Click to collapse
I have a samsung a02, pixel 7 pro, moto g 5 g , oneplus n20 , iphone 12, iphone 6 , 4 tablets, and two LG
Trying to follow the various guides to move from A12 DE2118 back to A11 DE2117 (and then on to Lineage or Libre). I'm passing everything through to a Windows VM, but the tools dont see the phone in EDL mode, and neither the google or oneplus drivers seem to help.
I'd really like to just flash this whole puppy with Linux, but I'm getting stuck on a few points. Do I "need" to us MSM? Seems like the answer is no as there is a non-MSM guide here, but it's still windows related. Where are all these image files coming from in the various guides? When I download the images from the mirrors, or OnePlus directly they have a payload.bin, but not the 30+ named .img files I see listed in some of the guides.
Feeling confused, and I know I'm capable of getting this done, I just need someone to help fill in the blanks for me. I "was" able to unlock the bootloader, that's how far I am now. Thanks!
lurkio said:
Where are all these image files coming from in the various guides? When I download the images from the mirrors, or OnePlus directly they have a payload.bin, but not the 30+ named .img files I see listed in some of the guides.
Click to expand...
Click to collapse
https://github.com/ssut/payload-dumper-go will extract .img files for you from a payload.bin. Also supports zip packages that contain payload.bin.
A linux guide is sorely lacking. Would be great if you could document your steps for others.
blueberry.sky said:
https://github.com/ssut/payload-dumper-go will extract .img files for you from a payload.bin. Also supports zip packages that contain payload.bin.
A linux guide is sorely lacking. Would be great if you could document your steps for others.
Click to expand...
Click to collapse
Thanks. And definitely have been along the way.
I'm working through this as well, so feel free to ask questions if you need help along the way, @lurkio. I have lots of linux experience, and like you, this device has been a little confusing for me.
My goal is to go from stock A12 on DE2118 --> LOS19 on DE2117
For this device specifically, all the info we need is here -- it's just a bit hard for me to piece it all together for myself.
Try the drivers I've attached here. I think one of them worked for me for QDL in windows.
Here's some of what I found here on the forums:
justauserthatusesaphone said:
Note: if you're on T-Mo OOS 12, then you have to go back to OOS 11 via MSM tools in order to do this.
Click to expand...
Click to collapse
Looks like the downgrade comes first, then the conversion.
Successful conversion of N200 5G from T-Mo to OEM without MSM tool! (Credit to Summersofar)
Click to expand...
Click to collapse
The conversion process in this post worked beautifully for me last year. I was on one of the later stock A11 builds, and carefully followed the guide in the first post.
blueberry.sky said:
https://github.com/ssut/payload-dumper-go will extract .img files for you from a payload.bin. Also supports zip packages that contain payload.bin.
Click to expand...
Click to collapse
+1 for payload-dumper-go. That tool makes it so easy to get the images, and it looks really cool doing it. (And for the Arch crowd like me, it's in the AUR!)
Also, check that you're running the latest ADB/Fastboot. I found a lot of small issues magically disappeared once I was up-to-date. Here are the links to the latest and greatest.
https://dl.google.com/android/repository/platform-tools-latest-LINUX.zip
https://dl.google.com/android/repository/platform-tools-latest-WINDOWS.zip
Downgrade US OEM (DE2117) Android 12 firmware to Android 11 BEFORE installing Lineage!
Click to expand...
Click to collapse
I haven't tried to downgrade yet, but this guide looks promising. Sideload an APK to device instead of (I'm guessing?) MSM.
---rrryannn--- said:
I haven't tried to downgrade yet, but this guide looks promising. Sideload an APK to device instead of (I'm guessing?) MSM.
Click to expand...
Click to collapse
Let me know if that tool works for you, I get the failed verification on the official OnePlus image or the A11 image that was posted.
I have a separate post about it, but I get stuck at fastbootd. I just didnt have enough luck in linux so I used a VM to get the MSM tool to flash A11 on the device, and that worked. So currently I'm on A11 DE2118, and I need to get to DE2117 to get to Lineage.
If I watch dmesg or the journal I see the phone constantly connecting and disconnecting in fastbootd mode, it's fine in fastboot mode, and all other modes. I might just have to spin up windows on another PC to get this moving. Stuck!