I made a better way to flash GSIs
https://forum.xda-developers.com/nubia-red-magic-5g/development/swapper-generate-flashable-zips-img-t4133591
Go here and use that.
Nubia's bootloader and fastbootd is **** and both can't flash images to the logical partitions like the system partition and vendor partition.
So we need to build an image for the super partition to be flashed.
If you just wanted to flash a custom rom skip part 1 and download the super.img from the link (los or havoc, havoc recommended as los's brightness control is half broken)
Requirements: An unlocked RM5G booted into the bootloader (not fastbootd, if you don't know what that is, you probably are in bootloader), An A/B GSI image (yes we need a A/B image not an A-only image, from android 9 released devices all phones are systeam as root), A linux environment (I did it in WSL), the download file
BACKUP YOU'RE SUPER PARTITION BEFORE FLASHING AND SAVE IT SOMEWHERE SAFE BEFORE FLASHING
(Seriously, tho I figured this out while trying to unbrick my phone after ****ing up my super partition. Trust me, it will be a life saver. Doing this will also break flashing stock ota rom via recovery until you flash your backup)
Part 1: Building the super image
Download tools.7z and extract it
Place the GSI image in the same folder and rename it to system.img
Execute the lpmake.sh script in a linux environment (It will say invalid headers at magic, it's not an error so just ignore it)
When it is complete there will be a super.img file in the folder (takes about 1 min)
Part 2: Flashing the super image
Before we flash the super.img we have to disable verity.
flash vbmeta and vbmeta_system with
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img
(You don't have to flash these every time. Just once)
Now we can flash the super.img with
fastboot flash super super.img
You also have to wipe dalvik, cache, data
If you have twrp do it in twrp.
If you don't, you shouldn't be doing this, I told you to backup your super partition.
That's it.
Tested GSIs:
LOS 17.X : Boots, Wifi/Data/BT works, Brightness control is half broken (always at full brightness)
Android 11 DP3 : Doesn't boot
Havoc 3.4 : Boots, 3.5 doesn't work
Phh-Quack : Doesn't boot
Descendant X : Boots, same as LOS
Oh, and for people wondering about the fingerprint sensor. It doesn't work. The phone doesn't even know it has it under the display(Maybe a problem with all under display fingerprint sensor phones).
After more testing, found out slot count can be 1 instead of 2.
Link to files
https://drive.google.com/open?id=1DuQp2_uebwRr9mD5MQxibQGdPBQyPkHN
Wow amazing, so we can use any other gsi except the one forced by these guys
Sent from my NX659J using Tapatalk
---------- Post added at 09:55 AM ---------- Previous post was at 09:53 AM ----------
apersomany said:
https://drive.google.com/open?id=1DuQp2_uebwRr9mD5MQxibQGdPBQyPkHN
Click to expand...
Click to collapse
Also does everything work like the air triggers and the fan ect
Sent from my NX659J using Tapatalk
keep it up. the fingerprint sensor is a goodix sensor it was the problem on other devices too. we will need to ask nubia for the goodix sources to fix it.
is the fan, gaming triggers and 144hz working? also what about the slider any functionality?
gokhujee said:
Wow amazing, so we can use any other gsi except the one forced by these guys
Sent from my NX659J using Tapatalk
---------- Post added at 09:55 AM ---------- Previous post was at 09:53 AM ----------
Also does everything work like the air triggers and the fan ect
Sent from my NX659J using Tapatalk
Click to expand...
Click to collapse
Sadly air triggers, fans, 144hz, slider doesn't work (Maybe it'll work if we port the app to the rom)
For the fingerprint sensor I'm gonna try some things.
apersomany said:
Nubia's bootloader and fastbootd is **** and both can't flash images to the logical partitions like the system partition and vendor partition.
So we need to build an image for the super partition to be flashed.
If you just wanted to flash a custom rom skip part 1 and download the super.img from the link (los or havoc, havoc recommended as los's brightness control is half broken)
Requirements: An unlocked RM5G booted into the bootloader (not fastbootd, if you don't know what that is, you probably are in bootloader), An A/B GSI image (yes we need a A/B image not an A-only image, though the treble info app says that our device is A-only, it's not), A linux environment (I did it in WSL), the download file
BACKUP YOU'RE SUPER PARTITION BEFORE FLASHING AND SAVE IT SOMEWHERE SAFE BEFORE FLASHING
(Seriously, tho I figured this out while trying to unbrick my phone after ****ing up my super partition. Trust me, it will be a life saver. Doing this will also break flashing stock ota rom via recovery until you flash your backup)
Part 1: Building the super image
Download tools.7z and extract it
Place the GSI image in the same folder and rename it to system.img
Execute the lpmake.sh script in a linux environment (It will say invalid headers at magic, it's not an error so just ignore it)
When it is complete there will be a super.img file in the folder (takes about 1 min)
Part 2: Flashing the super image
Before we flash the super.img we have to disable verity.
flash vbmeta and vbmeta_system with
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img
(You don't have to flash these every time. Just once)
Now we can flash the super.img with
fastboot flash super super.img
You also have to wipe dalvik, cache, data
If you have twrp do it in twrp.
If you don't, you shouldn't be doing this, I told you to backup your super partition.
That's it.
Tested GSIs:
LOS 17.X : Boots, Wifi/Data/BT all works, Brightness control is half broken (always at full brightness)
Android 11 DP3 : Doesn't boot
Havoc 3.4 : Boots, So far everything works, Probably will stay on this
Oh, and for people wondering about the fingerprint sensor. It doesn't work. The phone doesn't even know it has it under the display(Maybe a problem with all under display fingerprint sensor phones).
Click to expand...
Click to collapse
So you got your phone working again! Nice Is volte calls working on havoc?
And it looks like you uploaded the converted gsi images? Thanks
NO WIFI for me on havoc
VZTech said:
So you got your phone working again! Nice Is volte calls working on havoc?
And it looks like you uploaded the converted gsi images? Thanks
NO WIFI for me on havoc
Click to expand...
Click to collapse
That's probably because you're boot.img is not from the same version as mine (2.46) try flashing the one I uploaded to google drive
apersomany said:
That's probably because you're boot.img is not from the same version as mine (2.46) try flashing the one I uploaded to google drive
Click to expand...
Click to collapse
Your not having issues? Mine is laggy, calls not working
VZTech said:
Your not having issues? Mine is laggy, calls not working
Click to expand...
Click to collapse
The lag goes away if you turn the screen on and off.
apersomany said:
The lag goes away if you turn the screen on and off.
Click to expand...
Click to collapse
Ouch, this isn't good
Thanks for the super img tools/instructions - this will actually come in handy on another device I'm working on.
MishaalRahman said:
Thanks for the super img tools/instructions - this will actually come in handy on another device I'm working on.
Click to expand...
Click to collapse
The script has a fixed partition size specified for the rm5g so you might wan't to change the partition size.
there seems to be a workaround to keep Fingerprint functionality while rooting and even with twrp installed. it seems it's even possible to lock the bootloader at the same time. will wait for xda guides to explain as i don't understand it yet. i saw video evidence and it's pretty easy. the guy even forgot oem unlock in dev options and it still worked for him.
only cn rom supported it seems. and it's a similar guide to the redmagic 3.
apersomany said:
The script has a fixed partition size specified for the rm5g so you might wan't to change the partition size.
Click to expand...
Click to collapse
Wondering if we could add the ims.apk to the image??? Its needed for volte. If its done on the os, the phone doesnt boot.
VZTech said:
Wondering if we could add the ims.apk to the image??? Its needed for volte. If its done on the os, the phone doesnt boot.
Click to expand...
Click to collapse
It's possible, but I would rather make a magisk module for it, it takes way less time.
apersomany said:
It's possible, but I would rather make a magisk module for it, it takes way less time.
Click to expand...
Click to collapse
I tried adding it. Didnt boot. Just a black screen. exactly which havoc did you use?
VZTech said:
I tried adding it. Didnt boot. Just a black screen. exactly which havoc did you use?
Click to expand...
Click to collapse
I used https://forum.xda-developers.com/pr...e-development/havoc-os-3-3-gsi-archs-t4076903 this one, specifically the Gapps Included ARM64 A/B version.
apersomany said:
I used https://forum.xda-developers.com/pr...e-development/havoc-os-3-3-gsi-archs-t4076903 this one, specifically the Gapps Included ARM64 A/B version.
Click to expand...
Click to collapse
Thanks. I used that ones too. I extracted the system image, added the file, repacked, then used the tool to convert to super, but it wouldnt boot.
VZTech said:
Wondering if we could add the ims.apk to the image??? Its needed for volte. If its done on the os, the phone doesnt boot.
Click to expand...
Click to collapse
VZTech said:
Thanks. I used that ones too. I extracted the system image, added the file, repacked, then used the tool to convert to super, but it wouldnt boot.
Click to expand...
Click to collapse
Hmm... That's weird.
Have you increased the size of the partition that you've added the file to in the script? (If it was added to the system img probably won't matter as I've set the value to something like 3gigs if I remember correctly)
So doing it without adding the file works, but if you add it it won't boot right?
nadejo said:
there seems to be a workaround to keep Fingerprint functionality while rooting and even with twrp installed. it seems it's even possible to lock the bootloader at the same time. will wait for xda guides to explain as i don't understand it yet. i saw video evidence and it's pretty easy. the guy even forgot oem unlock in dev options and it still worked for him.
only cn rom supported it seems. and it's a similar guide to the redmagic 3.
Click to expand...
Click to collapse
Yes in our forum in Telegram: ZTE Nubia Redmagic 5G Channel people are using the Chinese ROM and bypassing the bootloader unlock. I have not yet tried. We are perfecting the process ATM. We even got a guy to restore a TWRP backup of Global ROM. It isn't an easy process. You have to be very, very careful. There are a lot of wipes that go on in between. Will post once we have a 100% working solution. Under the Bootloader Unlock tutorial in XDA for this device.
Related
Hello y'all,
I've noticed that on the Pixel 2 and on many other A/B devices, there is a twrp zip available that can be flashed after flashing the twrp image to boot and booting into recovery and flashing the stock boot image (like we do on the Essential) which patches the ramdisk in the stock boot.img to add twrp to it so that twrp can be permanently installed on the device.
If I could make something like this myself, I would have a long time ago, but unfortunately, it's over my head. Just curious why something like this has never been made for the Essential. Also, but much less important, TWRP 3.2.3-0 is about to be released (code is on GitHub), yet the latest available to us is version 3.2.1-1.
I know one of you smart devs could make the zip to install twrp to the ramdisk (and possibly build the latest version of twrp also) probably in almost no time at all. I love my Essential, but having to connect it to a PC just to get into TWRP is very irritating.
When one of you guys have the time, could you give it a try? I'd be happy to test whatever you come up with.
Much thanks!
starcms said:
Hello y'all,
I've noticed that on the Pixel 2 and on many other A/B devices, there is a twrp zip available that can be flashed after flashing the twrp image to boot and booting into recovery and flashing the stock boot image (like we do on the Essential) which patches the ramdisk in the stock boot.img to add twrp to it so that twrp can be permanently installed on the device.
If I could make something like this myself, I would have a long time ago, but unfortunately, it's over my head. Just curious why something like this has never been made for the Essential. Also, but much less important, TWRP 3.2.3-0 is about to be released (code is on GitHub), yet the latest available to us is version 3.2.1-1.
I know one of you smart devs could make the zip to install twrp to the ramdisk (and possibly build the latest version of twrp also) probably in almost no time at all. I love my Essential, but having to connect it to a PC just to get into TWRP is very irritating.
When one of you guys have the time, could you give it a try? I'd be happy to test whatever you come up with.
Much thanks!
Click to expand...
Click to collapse
It's definitely possible but I don't know how many Devs would want to take this up. I'm all for the idea, I really miss having TWRP permanently, but you kinda get used to the whole PC flashing thang.
I don't know how different the Pixel 2 is in comparison to the Essential phone, but they both share A/B partitions, so it wouldn't be too outlandish if someone were able to port something like this over to our Mata's down the road.
?
starcms said:
Hello y'all,
I've noticed that on the Pixel 2 and on many other A/B devices, there is a twrp zip available that can be flashed after flashing the twrp image to boot and booting into recovery and flashing the stock boot image (like we do on the Essential) which patches the ramdisk in the stock boot.img to add twrp to it so that twrp can be permanently installed on the device.
If I could make something like this myself, I would have a long time ago, but unfortunately, it's over my head. Just curious why something like this has never been made for the Essential. Also, but much less important, TWRP 3.2.3-0 is about to be released (code is on GitHub), yet the latest available to us is version 3.2.1-1.
I know one of you smart devs could make the zip to install twrp to the ramdisk (and possibly build the latest version of twrp also) probably in almost no time at all. I love my Essential, but having to connect it to a PC just to get into TWRP is very irritating.
When one of you guys have the time, could you give it a try? I'd be happy to test whatever you come up with.
Much thanks!
Click to expand...
Click to collapse
MoistPicklez said:
It's definitely possible but I don't know how many Devs would want to take this up. I'm all for the idea, I really miss having TWRP permanently, but you kinda get used to the whole PC flashing thang.
I don't know how different the Pixel 2 is in comparison to the Essential phone, but they both share A/B partitions, so it wouldn't be too outlandish if someone were able to port something like this over to our Mata's down the road.
?
Click to expand...
Click to collapse
The problem lies in the way our touch driver is implemented. For lack of a better explanation, what good would it do to need to carry a type c mouse around to use twrp if touch doesn't work. Many many people have tried and failed getting touch to work on Oreo source, let alone P. That is why twrp resides on a nougat kernel meant for LOS. Someone I know even rewrote the driver in c, no go. It's gonna be tough sledding.
Does it have to be touch though? Could it be more old school clockworkmod recovery where you use the buttons or really like default recovery. I don't know enough about it but just a thought. You definitely get use to just downloading and flashing in twrp and it would be cool to find that with the PH-1.
Atleaset there is a way to use TWRP on the fly.
1) Root the phone the first time using the PC.
2) Copy the TWRP and boot.img(rooted) files to the Phone.
3) While booted and rooted, use apps like Rashr - Flash Tool or Flashify available on the playstore to flash TWRP and boot to it.
4) Once you are done using TWRP, flash the boot.img and boot to the phone.
Gundabolu SC said:
Atleaset there is a way to use TWRP on the fly.
1) Root the phone the first time using the PC.
2) Copy the TWRP and boot.img(rooted) files to the Phone.
3) While booted and rooted, use apps like Rashr - Flash Tool or Flashify available on the playstore to flash TWRP and boot to it.
4) Once you are done using TWRP, flash the boot.img and boot to the phone.
Click to expand...
Click to collapse
Been waiting for someone to share this for 6 months.. thanks lol
aer0zer0 said:
The problem lies in the way our touch driver is implemented. For lack of a better explanation, what good would it do to need to carry a type c mouse around to use twrp if touch doesn't work. Many many people have tried and failed getting touch to work on Oreo source, let alone P. That is why twrp resides on a nougat kernel meant for LOS. Someone I know even rewrote the driver in c, no go. It's gonna be tough sledding.
Click to expand...
Click to collapse
Thanks for the explanation. Now I understand why it hasn't been done before.
But why the issue with touch in TWRP with an Oreo kernel in the first place? What's so special/different/difficult about the touch driver that the Essential uses? And why does it work fine with TWRP with a Nougat kernel? No other devices (to my knowledge) have this issue.
Edit: I wonder if since TWRP worked with the touch driver from the Nougat kernel, if it could work with the P kernel? Maybe whatever was changed in Oreo that prevented it from working has been fixed?
starcms said:
Thanks for the explanation. Now I understand why it hasn't been done before.
But why the issue with touch in TWRP with an Oreo kernel in the first place? What's so special/different/difficult about the touch driver that the Essential uses? And why does it work fine with TWRP with a Nougat kernel? No other devices (to my knowledge) have this issue.
Click to expand...
Click to collapse
Hbtp_daemon (touchscreen) doesn't work in twrp on 8.x and newer sources.
Hbtp_daemon runs in userspace iirc, which is the problem. So an entire driver needs to be hogged together in order to get twrp to work. same process that worked on N doesn't work now.
aer0zer0 said:
Hbtp_daemon (touchscreen) doesn't work in twrp on 8.x and newer sources.
Hbtp_daemon runs in userspace iirc, which is the problem. So an entire driver needs to be hogged together in order to get twrp to work. same process that worked on N doesn't work now.
Click to expand...
Click to collapse
Not possible to use the driver in userspace after TWRP decrypts the device (userspace) using the default password (after any patterns or pins are removed from the lockscreen)?
Edit: And what the heck is the driver doing in userspace anyway? Shouldn't it be in /vendor? If the driver is in userspace, then how can the touchscreen work after a factory reset?
The new Lineage Recovery is not bad but I see no way to apply other zips like Magisk. Maybe it can be worked on and adapted. No touch , just button control.
galakanokis said:
The new Lineage Recovery is not bad but I see no way to apply other zips like Magisk. Maybe it can be worked on and adapted. No touch , just button control.
Click to expand...
Click to collapse
It doesn't after you lets say flash magisk and gapps they create a script in /system/addon....and when updatting lineage it runs the scripts in the addon folder which is how gapps and magisk get installed to the new updated system and boot.....first magisk and gapps have to be flashed in twrp....after that u shudnt need it on dirty flashes
galakanokis said:
The new Lineage Recovery is not bad but I see no way to apply other zips like Magisk. Maybe it can be worked on and adapted. No touch , just button control.
Click to expand...
Click to collapse
@aer0zer0
This seems like the easiest solution to getting TWRP working on the Oreo and P boot images and being able to keep it permanently installed in ramdisk. Make TWRP use the volume up/down keys for scrolling and the power key to select. If the touchscreen is soooo difficult to get working, forget it. If someone really wants to use the touchscreen, they can use the existing TWRP version built on the Nougat boot image.
galakanokis said:
The new Lineage Recovery is not bad but I see no way to apply other zips like Magisk. Maybe it can be worked on and adapted. No touch , just button control.
Click to expand...
Click to collapse
What can you do in Lineage recovery if you can't flash zips? Can you make backups? What else can you do? If you have it installed, could you attach a pic (assuming you have another phone/camera)?
Has anyone looked in the stock P kernel? I was poking around and noticed some twrp residual files. This was straight from the images zip from essential. I didn't touch it.Wth are they in there for? Could they have a better twrp on the back burner for kernel development purposes for Essential? It was in the ramdisk, ill look again tomorrow when I unpack the boot.img. it would make sense to have it in ramdisk, pixel 2 has it like that. Ill post screenshots after work. But, the conversation looks good folks, you are on to something. We could always bust out some phillz recovery, or clockwork mod.
starcms said:
What can you do in Lineage recovery if you can't flash zips? Can you make backups? What else can you do? If you have it installed, could you attach a pic (assuming you have another phone/camera)?
Click to expand...
Click to collapse
I would say it is more stock-ish as far as recoverys go. It's a stock LOS recovery. You can factory reset, flash or sideload update.zips or signed zips no regular custom ROM zips or magisk. It is meant to run on LOS, it only runs on LOS actually and not made for the flashaholics out there. It's a good start though.
Sorry, out right now and no other phone/camera handy.
Gundabolu SC said:
Atleaset there is a way to use TWRP on the fly.
1) Root the phone the first time using the PC.
2) Copy the TWRP and boot.img(rooted) files to the Phone.
3) While booted and rooted, use apps like Rashr - Flash Tool or Flashify available on the playstore to flash TWRP and boot to it.
4) Once you are done using TWRP, flash the boot.img and boot to the phone.
Click to expand...
Click to collapse
Just wanted to mention this works perfectly, tried it last night was able to get into TWRP and then back into my P Beta 3 with root, no issues. Thanks for this!
One could also theoretically copy a copy of the twrp boot. Img to the ex kernel manager backup file, and while booted into the system, hit restore kernel and since its in the boot partition it will flash it then reboot into recovery. Then from there flash your normal kernel and boot back to system/android.. i backup all my kernels after rooting them so after flashing otas, i can just flash my prerooted kernel and reboot without having to flash magisk
Edit. This works, i just did it, but u must make it reboot to bootloader to then tell it to reboot recovery. I dont know if flashify is the same
MoistPicklez said:
Just wanted to mention this works perfectly, tried it last night was able to get into TWRP and then back into my P Beta 3 with root, no issues. Thanks for this!
Click to expand...
Click to collapse
Hey, I'm just curious, before I try it, anyway when using flashify and selecting flash zip - does a recovery other than stock need to be present?
dirtyreturn said:
Hey, I'm just curious, before I try it, anyway when using flashify and selecting flash zip - does a recovery other than stock need to be present?
Click to expand...
Click to collapse
Not sure what you mean by that but to be honest all I did was take the TWRP11.img, and flashed it to boot (kernel) using Rashr, Flashify didn't load up oddly, then reboot to bootloader, select Recovery and bam, there was TWRP. Then to get back I just flashed my boot.img, and Magisk and all my modules and everything were all good to go. No issues at all. ?
Edit: as long as you have TWRP.img, your boot.img, and Magisk, you can easily get to TWRP and back, just make sure you have the img's you need and boom we all got TWRP on the fly.
Wish I had tried this sooner.
MoistPicklez said:
Not sure what you mean by that but to be honest all I did was take the TWRP11.img, and flashed it to boot (kernel) using Rashr, Flashify didn't load up oddly, then reboot to bootloader, select Recovery and bam, there was TWRP. Then to get back I just flashed my boot.img, and Magisk and all my modules and everything were all good to go. No issues at all. ?
Edit: as long as you have TWRP.img, your boot.img, and Magisk, you can easily get to TWRP and back, just make sure you have the img's you need and boom we all got TWRP on the fly.
Wish I had tried this sooner.
Click to expand...
Click to collapse
Hey, Rashr doesn't support this device(phone). I get a reboot to recovery option and if I tap cancel the app just closes. Did the app identify what it needed to?
In Flashify there are 3 options ,Flash - kernel,boot, and zip. What I'm curious about is , when choosing just the zip option - would twrp first need to be flashed to the boot partition?
Install Android 9.0 Pie AOSP GSI
Warning
You will loose all your data. Make sure to backup. You are doing this at your own risk. Neither me nor xda is responsible for any bricked devices.
Pre-Requisites
Please read carefully. Any questions which are already answered in OP will be ignored.
If you have a question, not answered in OP read last 2-3 pages. Any questions which are already answered in last 2-3 pages will also be ignored.
Not being rude, but people need to start reading.
Make sure you have unlocked the bootloader.
Text Guide
Install Android 9.0 Pie AOSP GSI
1. Download AB Arm64 GSI from link in downloads. Unzip it. Windows users can use Winrar. Mac users can use the Unarchiver.
2. Download and unzip adb & fastboot linked in downloads section.
3. Place the extracted system image (step 1) in platform-tools folder. Rename it to system-arm64.img.
4. Power off phone.
5. Press and hold volume down and power button at the same time. You will now boot into fastboot boot.
6. Connect phone to computer.
7. Windows users open command prompt. Mac/Linux users open Terminal. Navigate to the folder where you unzipped adb & fastboot.
Windows
Code:
fastboot devices
Mac & Linux
Code:
./fastboot devices
If your device shows up, drivers were installed correctly. If not, then drivers were not installed and you need to install them.
8. Erase System
Windows
Code:
fastboot erase system
Mac & Linux
Code:
./fastboot erase system
9. Flash Android Pie GSI
Windows
Code:
fastboot flash system system-arm64.img
Mac & Linux
Code:
./fastboot flash system system-arm64.img
10. Wipe/Factory Reset
Windows
Code:
fastboot -w
Mac & Linux
Code:
./fastboot -w
11. Reboot
Windows
Code:
fastboot reboot
Mac & Linux
Code:
./fastboot reboot
11. Profit. Android 9.0 Pie. Rooting might result in broken Wi-fi. So, flash back stock boot.img if your wifi is broken after rooting.
Video Guide
Downloads
MiUnlock Tool - http://xiaomi-miui-ota-3rdrom.ks3-c...1/3.3.525.23/miflash_unlock-en-3.3.525.23.zip
Latest ADB & Fastboot :- https://developer.android.com/studio/releases/platform-tools
Setup ADB and Fastboot (if above adb & fastboot do not work) - https://www.xda-developers.com/adb-fastboot-any-directory-windows-linux/
Android 9.0 Pie GSI Thread :- https://forum.xda-developers.com/pr...velopment/aosp-9-0-phh-treble-t3831915/page12
Android 9.0 Pie GSI Download Links :- https://github.com/phhusson/treble_experimentations/releases
Winrar (Windows) :- https://www.rarlab.com/
The Unarchiver (Mac):- https://theunarchiver.com/
@munchy_cool wow!!!, Thanks man. But sorry but i have to ask, did you try this on your A2 is it working fine without any issues?
crazykas said:
@munchy_cool wow!!!, Thanks man. But sorry but i have to ask, did you try this on your A2 is it working fine without any issues?
Click to expand...
Click to collapse
the A2 in the video is mine. I tried it for some time. Camera works, wifi works, sound works, charging works, couldnt check calls and lte as I am at work and cannot have my sim turned off for even a minute. But yes it works.
munchy_cool said:
the A2 in the video is mine. I tried it for some time. Camera works, wifi works, sound works, charging works, couldnt check calls and lte as I am at work and cannot have my sim turned off for even a minute. But yes it works.
Click to expand...
Click to collapse
much appreciated man!! Reason i asked this is i ****edup my phone before cause of that fastboot boot twrp > set active b slot thing. So my warranty covered me and gave a new phone. lol. BTW what do you mean by "cannot have my sim turned off for even a minute"? Finally it will be great if you can add how to flash back the stock rom as well.. Thanks mate :good:
crazykas said:
much appreciated man!! Reason i asked this is i ****edup my phone before cause of that fastboot boot twrp > set active b slot thing. So my warranty covered me and gave a new phone. lol. BTW what do you mean by "cannot have my sim turned off for even a minute"? Finally it will be great if you can add how to flash back the stock rom as well.. Thanks mate :good:
Click to expand...
Click to collapse
not sure how you bricked it but glad you got a new phone.
"cannot have my sim turned off"
So, I have only one sim which is in my work phone. to test LTE, data etc i will have to remove the sim from that phone and put it in the Mi A2. Now, I cannot do that as I cannot have my sim (phone number) turned off for even a minute due to work.
As for going back to stock. Download stock firmware, extract it and replace pie gsi img with system.img from factory firmware zip and you will be back to stock.
munchy_cool said:
not sure how you bricked it but glad you got a new phone.
"cannot have my sim turned off"
So, I have only one sim which is in my work phone. to test LTE, data etc i will have to remove the sim from that phone and put it in the Mi A2. Now, I cannot do that as I cannot have my sim (phone number) turned off for even a minute due to work.
As for going back to stock. Download stock firmware, extract it and replace pie gsi img with system.img from factory firmware zip and you will be back to stock.
Click to expand...
Click to collapse
How did i bricked my phone. Simple. First of all no desrepect for any dev, since i did this by my one. What i did was tried to flash unofficial twrp and fastboot set slot b did not worked. Once i reboot it got stuck on a bootloop. i couldn't flash xiaomi stock fastboot zip due to "critical partition flashing is not allowed" and before you asked yes my A2 was bootloader unlocked one. Unlock critical partition thing is not for our devices like for pixel series as far as i know. So simply i couldn't fix it, neither the software guy from my purchased center. That's why im afraid. I know you are besy, but highly appreciate if you can write down how to go back to stock guideline as well. Thanks again :good:
crazykas said:
How did i bricked my phone. Simple. First of all no desrepect for any dev, since i did this by my one. What i did was tried to flash unofficial twrp and fastboot set slot b did not worked. Once i reboot it got stuck on a bootloop. i couldn't flash xiaomi stock fastboot zip due to "critical partition flashing is not allowed" and before you asked yes my A2 was bootloader unlocked one. Unlock critical partition thing is not for our devices like for pixel series as far as i know. So simply i couldn't fix it, neither the software guy from my purchased center. That's why im afraid. I know you are besy, but highly appreciate if you can write down how to go back to stock guideline as well. Thanks again :good:
Click to expand...
Click to collapse
did you try fastboot set slot a, and then reboot? that should have fixed it.
As for a guide for going back to stock from Pie.
LIke i said.
dowload fastboot firmware from here.
https://forum.xda-developers.com/mi-a2/how-to/ota-v9-6-5-0-odimife-t3823445
extract the zip file. open images folder. grab system.img. put it in fasboot folder. and in step where we flash pie gsi image, flash the system.img you just pasted in fastboot folder.
munchy_cool said:
did you try fastboot set slot a, and then reboot? that should have fixed it.
As for a guide for going back to stock from Pie.
LIke i said.
dowload fastboot firmware from here.
https://forum.xda-developers.com/mi-a2/how-to/ota-v9-6-5-0-odimife-t3823445
extract the zip file. open images folder. grab system.img. put it in fasboot folder. and in step where we flash pie gsi image, flash the system.img you just pasted in fastboot folder.
Click to expand...
Click to collapse
Thanks man. Will try at night. Can't wait ????
MTP doesn't work.
Streect said:
MTP doesn't work.
Click to expand...
Click to collapse
It works. Enable it in Developer Tools.
Thank you very much for sharing, i will try it soon
---------- Post added at 10:02 AM ---------- Previous post was at 09:39 AM ----------
No problem on Linux? Simple adb /fastboot installed on Ubuntu
---------- Post added at 10:09 AM ---------- Previous post was at 10:02 AM ----------
Again: which one img do you choose, aonly or ab?
HTCDevil said:
Thank you very much for sharing, i will try it soon
---------- Post added at 10:02 AM ---------- Previous post was at 09:39 AM ----------
No problem on Linux? Simple adb /fastboot installed on Ubuntu
---------- Post added at 10:09 AM ---------- Previous post was at 10:02 AM ----------
Again: which one img do you choose, aonly or ab?
Click to expand...
Click to collapse
did you read the OP at all? it's mentioned step 1 which file you need.
How to install Gapps?
munchy_cool said:
[...]
Click to expand...
Click to collapse
Two things:
1) Thank you for the guide! You got yourself another subscriber on YouTube This is my first device that supports Treble. From your experience, how stable are GSI ROMs?
2) Update your signature
speedunderx said:
How to install Gapps?
Click to expand...
Click to collapse
i didnt get time to check that. may have to install some apks. maybe the same apks which are needed for amazon fire tablets to get play store working.
soulicro said:
Two things:
1) Thank you for the guide! You got yourself another subscriber on YouTube This is my first device that supports Treble. From your experience, how stable are GSI ROMs?
2) Update your signature
Click to expand...
Click to collapse
gsi's are pretty stable, check xda thread for bugs. will update signature soon
munchy_cool said:
did you read the OP at all? it's mentioned step 1 which file you need.
Click to expand...
Click to collapse
About my last question ok, i see on YouTube it is ab. Other question not answered yet. Thanks.
HTCDevil said:
About my last question ok, i see on YouTube it is ab. Other question not answered yet. Let him answer by itself. Thanks.
Click to expand...
Click to collapse
no problem on Linux.
munchy_cool said:
no problem on Linux.
Click to expand...
Click to collapse
Great, hope gapps work and camera is mostly Stable. Thank you
HTCDevil said:
Great, hope gapps work and camera is mostly Stable. Thank you
Click to expand...
Click to collapse
it does not have gapps. you may have to manually install some apks. try with apks needed for Play Store on amazon fire tablets.
if you figure those out, please let us know.
What is "vbmeta.img" and why it is needed? How it works? Does anybody knows?
Có ***g câu hỏi
---------- Post added at 02:48 PM ---------- Previous post was at 02:44 PM ----------
I have the same question in
Google it
I have a question regarding vbmeta: I flashed it when I was installing a rom (let's say unofficial los). If I install another rom that doesn't ask me to flash vbmeta (let's say xiaomi.eu), will it flash another vbmeta? Is vbmeta included in xiaomi.eu's .zip?
As far as i understood it, correct me if i'm wrong, it disables verified boot for e.g. installing a gsi rom.
kennyk09 said:
Google it
Click to expand...
Click to collapse
Funny... I just did that and here I am.
I would like to know what is vbmeta as well...
Sent from my MI 9 using Tapatalk
After Android 8 they implemented Verified Boot. That's why you need vbmeta.img for some tasks (mostly to disable verified boot). In some cases, TWRP will not install if Verified Boot is on. Read more Here
kennyk09 said:
Google it
Click to expand...
Click to collapse
This is the 2nd reply on google rofl, got any better ideas genius
Yahoo it
kennyk09 said:
Google it
Click to expand...
Click to collapse
What if I bing it, sir?
Google sent me here — it's the first result when searching "vbmeta.img". Looks like we've entered a recursive function here! Let's add an exit condition.
Further digging led me to the Android Verified Boot 2.0 Readme which by skimming through it answered most of my questions.
So to get this clear, my current understanding is that vbmeta is akin to SecureBoot on PC — it uses hashes for each stage of the boot process to ensure that the final operating environment hasn't been tampered with at any stage of the startup process. Now since vbmeta actually contains the hashes/keys for the boot, system, and vendor partitions, that does mean that every ROM build will need a unique vbmeta.img if we wanted AVB to verify successfully, right? Also, I still don't understand how a vbmeta.img can disable AVB... does it simply set the hashes to zeros? And if we wanted to disable AVB, then where would THAT vbmeta.img come from? I presume we would need an image that is specific for our device, or would a generic vbmeta.img work across multiple devices (maybe with the limitation of being for A-only or A/B devices)?
I've been away from the custom ROM scene for a long time, so I'm trying to catch up with all these new features (AVB, A/B partitions, SafetyNet, etc.).
AFAIK, you need to flash vbmeta.img if you are going from an Miui ROM to a custom ROM.
And there is only one version of it.
rossarnie said:
AFAIK, you need to flash vbmeta.img if you are going from an Miui ROM to a custom ROM.
And there is only one version of it.
Click to expand...
Click to collapse
your right, vbmeta is responsible for checking initial boot to enter into boot or in recovery mode. thats why make sure you flash or restore system with its own vbmeta or you will end up bootloop or stock on fastboot mode.
kennyk09 said:
Google it
Click to expand...
Click to collapse
TOP answer! Do you know what happens if I search for "vbmeta.img" in Google? I end up in this thread!
A forum would be pretty much useless if every question in every thread would be answered in this way. A kind of "master solution": Google it!
Thank you!!
So is the vbmeta.img the same file for all phones?
Or is it vendor specific?
Or is it phone specific?
Thank you!
Elmarigo said:
So is the vbmeta.img the same file for all phones?
Or is it vendor specific?
Or is it phone specific?
Thank you!
Click to expand...
Click to collapse
As a part of a custom ROM or your firmware images it must be unique for your device model. It's like a boot.img for example.
A vbmeta.img contains checksums of the most important partitions to verify them.
A checksum is a small-sized datum derived from a block of digital data for the purpose of detecting errors that may have been introduced during its transmission or storage. By themselves, checksums are often used to verify data integrity but are not relied upon to verify data authenticity. (Wikipedia)
vbmeta=
verified boot metadata
Thank you!
I know what a checksum is, but didn't know that the vbmeta image contained checksums - which arised more questions:
When every partition is checksummed against vbmeta, wouldn't the phone need a different vbmeta everytime, depeding on Magisk being installed, or TWRP, or both combined?
Elmarigo said:
Thank you!
I know what a checksum is, but didn't know that the vbmeta image contained checksums - which arised more questions:
When every partition is checksummed against vbmeta, wouldn't the phone need a different vbmeta everytime, depeding on Magisk being installed, or TWRP, or both combined?
Click to expand...
Click to collapse
1. Not every partition, only /system, /vendor and /boot in most cases. But this could vary depending on your manufacturer.
2. Magisk is a systemless root solution. Have a look at /sbin/.magisk and you will see, that /system and /vendor were mounted as mirrors with all modifications that are needed, e.g. Magisk modules.
Only TWRP does some changes on /system.
Wow
Kudos to the guy who said google it. You'd better duckduckgo it to break this cycle, because I also ended up here as the first result!
Elmarigo said:
So is the vbmeta.img the same file for all phones?
Or is it vendor specific?
Or is it phone specific?
Thank you!
Click to expand...
Click to collapse
that was already answered. only 1 version of vbmeta exists.
I tried rooting my OP6T on Android 10, and was up half the night. Recovered from a hard brick twice, using the Qualcomm serial flash tool thing. I was trying to flash Majisk, and read that it had to be done via a custom recovery like TWRP. All the guides said that it to boot TWRP, then basically flash TWRP using itself so that it says. Fastboot kept saying "Remote Unknown Command" when using "fastboot boot" like all the guides said. Then someone told me to run "fastboot flash boot twrp.img". This caused the first hard brick. I guess because I wrote the recovery over the boot partition. I then found a post somewhere where someone said that Oneplus Devs removed the boot command from Fastboot for some reason. No idea why!! But no one else in the OP6T TWRP thread reported issues. Maybe they were all installing TWRP on an Android 9.x build that diden't have this issue? Eventually after recovering and flashing several layers on OTA updates through the local upgrade option, I was back on A10 OB2. But I still wanted root and hadn't got TWRP working yet. Then I found a random post buried in a random thread somewhere saying that custom recoveries on A10 are useless at this point period because TWRP can't flash the system partition, as it's read only. Not sure if this only applies to OP devices?
I am now back to where I started. I would still like twrp for backups, but since it's not cooperating, I try the alternative option for Masisk, involving the patched boot.img file. I download the patched the patched boot file in this thread. Flashed it with "fastboot flash boot boot.img", and got my 2nd hard brick. It would get stuck at the bootloader warning screen and no fastboot.
Now i've lost my data, 6+ hour of time, and no closer than I was before.
I am going to take a break now, cause I need an operational phone this week. Word of advice: If you're not a developer that knows exactly what they are doing, don't even attempt to get root on an Android 10 build!
You can install Magisk,manager,extract the boot img from the OOS zip file using payload_dumper,copy that boot img. to your phone,patch the image with magisk,copy to your PC then fastboot the patched image to your phone .And yes,you cannot have twrp yet.
I'm on the open beta 2 of Android 10 and I have root and TWRP. It's possible.
It's not that hard, you don't even need twrp to install magisk. in android 10.
download open beta 2 Android 10. Extract payload.bin from it. Use payload_dumper to extract boot
install magisk apk, and patch boot.
go to fastboot use the
"Fastboot flash boot_a patched_boot.img "
and you are done.
Sh4d0wk1ng said:
It's not that hard, you don't even need twrp to install magisk. in android 10.
download open beta 2 Android 10. Extract payload.bin from it. Use payload_dumper to extract boot
install magisk apk, and patch boot.
go to fastboot use the
"Fastboot flash boot_a patched_boot.img "
and you are done.
Click to expand...
Click to collapse
I think I see what I did! I need to use "fastboot flash boot_a" (or b), and not just "fastboot flash boot". Not sure how you know whether to use a or b without a custom recovery though? Because AFAIK, the fastboot command for that is broken.
Not sure what payload dumper is, but I should be able to use the the same patched boot image that everyone else used since it's for that same ROM, now that I known exactly where to flash it to (besides A or B).
When I flashed to "boot" before, I must have overwritten some kind of low-level pre-bootloader, lol.
Thank you
Bhamilton0347 said:
I'm on the open beta 2 of Android 10 and I have root and TWRP. It's possible.
Click to expand...
Click to collapse
How did you achieve this? Do you have to start with A9 with TWRP, and then somehow upgrade to A10 without overwriting it with stock recovery?
I found this guide, but step 2 does not make sense to me. How could you flash TWRP inside of the Masisk Manager app?
I imagine you still can't flash system with TWRP, but everything else works?
Thank you
roman gabriel said:
You can install Magisk,manager,extract the boot img from the OOS zip file using payload_dumper,copy that boot img. to your phone,patch the image with magisk,copy to your PC then fastboot the patched image to your phone .And yes,you cannot have twrp yet.
Click to expand...
Click to collapse
I think the issue was that I flashed to the wrong place. See above. Thank you.
I'm feeling extremely lazy rn and I don't feel like explaining all of the trouble I went through to get it working, but you should be able to just fastboot flash these images to their respective partitions and you should have both TWRP and Magisk. It's got Magisk 20.1, the modified one so that EdXposed will work. But they're functionally the same.
https://drive.google.com/file/d/149TqVLqKr7Rc8xygMDoUyY_SLoATQrRq/view?usp=drivesdk
Let me know if it works.
Note: this is the boot.img for the second open beta of Android 10 for the OnePlus 6T. This may also work on the stable and first beta release as well as even on the 6, but I do not know. Also, your SIM card may not be showing up, but this problem disappeared for me a minute or two after boot.
Bhamilton0347 said:
I'm feeling extremely lazy rn and I don't feel like explaining all of the trouble I went through to get it working, but you should be able to just fastboot flash these images to their respective partitions and you should have both TWRP and Magisk. It's got Magisk 20.1, the modified one so that EdXposed will work. But they're functionally the same.
https://drive.google.com/file/d/149TqVLqKr7Rc8xygMDoUyY_SLoATQrRq/view?usp=drivesdk
Let me know if it works.
Note: this is the boot.img for the second open beta of Android 10 for the OnePlus 6T. This may also work on the stable and first beta release as well as even on the 6, but I do not know. Also, your SIM card may not be showing up, but this problem disappeared for me a minute or two after boot.
Click to expand...
Click to collapse
Thank you. I can't risk it right now. But i'll try sometime. Anyone wanna be the guinea pig?
If it works well, it should be very useful to the community.
I am brand new to Majisk by the way. It's been a couple years since I was rooted.
flyoffacliff said:
Thank you. I can't risk it right now. But i'll try sometime. Anyone wanna be the guinea pig?
If it works well, it should be very useful to the community.
I am brand new to Majisk by the way. It's been a couple years since I was rooted.
Click to expand...
Click to collapse
It's 100% safe and I can guarantee it'll boot as long as you're on an international OP6T on the Android 10 open beta 2. I reuploaded and included the stock boot.img as well so just in case you do have any problems, you can just fastboot flash it and you'll be able to boot right up (no hard brick or anything)
Bhamilton0347 said:
It's 100% safe and I can guarantee it'll boot as long as you're on an international OP6T on the Android 10 open beta 2. I reuploaded and included the stock boot.img as well so just in case you do have any problems, you can just fastboot flash it and you'll be able to boot right up (no hard brick or anything)
Click to expand...
Click to collapse
Great. Thank you. I might wait for the next stable build though. It just came out on H2OS, so shouldn't be too long now.
Man it just worked smooth for me. I was already on OB2 and I followed this below link. Half way down, I realised it was for OP6 and not 6T. However I had proper twrp and I just followed the procedure.
https://forum.xda-developers.com/oneplus-6/how-to/how-to-flash-twrp-magisk-android-10-t3988213
EDIT: I faced problems with wifi connectivity. So I had rebooted to TWRP and reflashed OB2, TWRP and Magisk again to get it working. An issue with
"fastboot flash boot" command I guess.
flyoffacliff said:
I think I see what I did! I need to use "fastboot flash boot_a" (or b), and not just "fastboot flash boot". Not sure how you know whether to use a or b without a custom recovery though? Because AFAIK, the fastboot command for that is broken.
Not sure what payload dumper is, but I should be able to use the the same patched boot image that everyone else used since it's for that same ROM, now that I known exactly where to flash it to (besides A or B).
When I flashed to "boot" before, I must have overwritten some kind of low-level pre-bootloader, lol.
Thank you
I wasn't sure either but I know that the boot on the oneplus 6t android 10 it has two partitions. I just flashed it on boot_a and it works. I could attempt to install twrp on the other partition but I don't really needed it. good luck and let us know how it went.
Click to expand...
Click to collapse
I had a bit more luck with the adventure this time! Successfully flashed TWRP and Magisk, but then Emojis were completely broken at the OS level. Apparently this is caused by a partition issue, but not sure how this happened. I tried a script to fix it that someone posted and it did not work. So I took this as an opportunity to flash the latest ROM to fix it.
I went into TWRP, ran the full update ZIP, then the TWRP installer, then the Magisk installer (all without rebooting). Apparently it does not switch slots automatically when you run it from recovery instead of the "local update" option? TWRP was fine after the update, but Masisk was not, despite me flashing the ZIP. No idea why! But I switched back to the other slot that was still rooted, used Magisk Manager to flash it to inactive slot, and switched slot back to one with new OS. Success! Funny how different methods work/fail with different people. Thanks for the help everyone. I just noticed 10.3.1 is no longer posted on the OnePlus website download page, hope it didn't get pulled again!
EDIT: Does each slot just have its own system and cache partition? Everything else is like data and modem is combined, right?
https://forum.xda-developers.com/oneplus-6t/how-to/root-oneplus-6t-loosing-data-android-10-t4041865
follow this guide.. work 100%. Tested.
For starters, there's no thread for this device and I wasn't sure where to put it.
Secondly, me and a friend have been tinkering around with the Cricket Dream 5G and have successfully unlocked the bootloader and obtained root access. Unlocking the bootloader was the easy part. Anyways we've made a full device backup before rooting. I have a magisk patched boot.img. Just unlock the bootloader, flash the patchedboot.img and install magisk. There you go, you have root
WARNING
DO NOT FLASH A MODIFIED SUPER.IMG IT WILL BRICK YOUR DEVICE You can, however modify your system, like removing or adding apps.
I bricked mine because I flashed a modified super img. It's stuck in preloader. Still learning this dynamic partition scheme, it's weird
Full backup on Google drive currently, gonna be moving to mega=>
https://mega.nz/folder/UARQCD6I#8CSNy43GWo6XjEKk_mlldw
Links below, all links are thru mega
Original boot=> https://mega.nz/file/JBAhHSTQ#Aw-GQQ6-StdNAhLsu0vdonNDXcBo4wXI8xEalQ99X2Y
Original boot is in bin format but magisk recognized it and patched it.
Patched boot.img=> https://mega.nz/file/hEJjlaxI#e2DdzvNkq1421uESaSQR4ZP_-CHvt6I_IDCEpyYDZqA
And an app for the magisk modules, not my work, only sharing=> https://mega.nz/file/VAQR0ARI#IUT42ycW5bbb8xVSDhDthREJzr1GEd5WHW0xZbkE8Ts
Also, relocking the bootloader after flashing the patched boot img, it will say there's no OS installed. It's still there. Just unlock it and it'll boot. Not sure why. I believe it's the secure boot being on
Just send a message on here if links are broken
If enough people are on this maybe we can get a working twrp
Update: twrp available here => https://forum.xda-developers.com/t/development-for-the-cricket-dream-5g.4414603/
If anyone uses gpay, unlocking the bootloader will break it. But I know a workaround if anyone wants it.
@Welkwo is behind the twrp process.
My post is just a guide, really.
Thank God! I have numerous phones but for some reason, I have my main number through a sim card thast's unfortunately tied into this phone.. I have been searching online for the stock firmware for this p;hone for a long time with no conclusive results, so upon my search for it this morning, I came acrfoss your post and I almost craped my pants. Thank God.. noot for the almost crapped pants, but for the efforts of you and your friend.. Thank you so much.
We are also working on a TWRP for the device. We can get it to boot but it doesn't recognize the partitions. I absolutely love the cricket dream 5g
Is it not completely slow as **** to you?! It's nowhere near what my OnePlus 5T , Redmi Note 8 nor Motorola Ace One can do nor did I expect it to be but God damn it's just super slow to me..
By the way should I flash boot_a and boot_b in fastboot because when I did the first time when I booted back up it kept making Google framework stop responding
Josephdbrewer25 said:
We are also working on a TWRP for the device. We can get it to boot but it doesn't recognize the partitions. I absolutely love the cricket dream 5g
Click to expand...
Click to collapse
Nevermind.. I retract m yprevious statement.. I just got root and I'm blown away at the sactual speed of this phone. It's such a night and day fgucking difference betweeen having root and not.
Sorry I've been absent. My work has me drained and I've bricked my dream 5g. I messed with my super partition and it is stuck in preloader.
Also I only flashed the boot for the current slot via fastboot
We need to create a scatter file, not quite sure how. Any help is appreciated
yooo... are you guys just needling the scatter to make a twrp recovery?
DrScrad said:
yooo... are you guys just needling the scatter to make a twrp recovery?
Click to expand...
Click to collapse
Honestly I'm not sure. My friend is behind the twrp process. We got one to boot but it don't recognize the partitions so it won't even boot to the os.
Do you have a scatter file? If so please share and I'll also attach it to the op if I have permission, lol
I've got me a new phone so I'll be experimenting again. Just don't flash a modified super img. I messed mine up when I did
Josephdbrewer25 said:
I've got me a new phone so I'll be experimenting again. Just don't flash a modified super img. I messed mine up when I did
Click to expand...
Click to collapse
Josephdbrewer25 said:
We are also working on a TWRP for the device. We can get it to boot but it doesn't recognize the partitions. I absolutely love the cricket dream 5g
Click to expand...
Click to collapse
TWRP for Cricket Dream 5G
Hi there, I have a Cricket Dream 5G and so far I have unlocked bootloader, root via magisk, full system image backup as well as GSI support with a TWRP device tree based on the boot.img. However, the system is A/B with dynamic super partition...
forum.xda-developers.com
lopestom said:
TWRP for Cricket Dream 5G
Hi there, I have a Cricket Dream 5G and so far I have unlocked bootloader, root via magisk, full system image backup as well as GSI support with a TWRP device tree based on the boot.img. However, the system is A/B with dynamic super partition...
forum.xda-developers.com
Click to expand...
Click to collapse
Yeah. Your point? That's the friend working on twrp
No TWRP file?
DragonPitbull said:
No TWRP file?
Click to expand...
Click to collapse
I'll get back with you. Currently at work. I think it's this file in the I've attached but I'm not sure
image-new.img
drive.google.com
Josephdbrewer25 said:
I'll get back with you. Currently at work. I think it's this file in the I've attached but I'm not sure
image-new.img
drive.google.com
Click to expand...
Click to collapse
I not need that. but anyone need permission access.
Josephdbrewer25 said:
Yeah. Your point? That's the friend working on twrp
Click to expand...
Click to collapse
Okay. But the DT in the github is your.
I need access of DT for help and if you or users need help about TWRP improvements. Looking my post about collaborator.....
UPD: I donwloaded your bot_a.bin (I need time for donwload super...img file) and I'm working with that to process informations & simple DT. I prefer collaborator than creating new DT in the github. But if I not receive any answer here so i go create new DT in the github and compiled TWRP file for anyone test.
The question now is: Who is the tester?
UPD1: super_backup_2022-03-10_02-34-47.img from MEGA is not good. 3 times trying donwloading file..... Can you put that as zip file in the GDrive?
UPD2: The super.img file was downloaded.
I need some informations from device. But at this point I'll write in the TWRP Cricket Dream 5G thread. .
If someone can put informations so answer in that thread.
Not sure if I should post here or at the TWRP thread but I think I've fixed the problem with being stuck at preloader after flashing modified super img. I got it to work by flashing the modified super img, locking bootloader and unlocking bootloader.
Can someone else also verify that this works?
Edit: Nvm I've been flashing the wrong super img
UPDATE: TWRP IS NOW AVAILABLE FOR THIS DEVICE.
See this post: https://forum.xda-developers.com/t/twrp-for-cricket-dream-5g.4418963/post-86858605
Kinda new to this, but I have a problem I am hoping someone knows about...I unlocked bootloader then i entered the fastboot flash command ...my phone died, as in shut off, power button does nothing, plugging it in to the computer does nothing, and charging does nothing. Thoughts? I'm assuming its dead? Thnx for listening lol
correction, i entered fastboot reboot fastboot
You know what? IT'S ALWAYS SOMETHIN'! I just got a Cricket Dream 5G for free (promo) and the bloody thing won't read a Micro SD card unless it's formatted to Fat32. Which means the largest card it'll use is a 32gb card. I mean WTH? I've never seen anything like this. If I put in a card formatted to exFat or NTFS it says it's corrupted. A Fat32 card is fine. Anyone else run across this? Just another X-File conspiracy against me.
so...no one knows anything??? anyway to fix this??? i noticed when plugged into computer it makes the connecting noise followed by disconnect noise a few minutes later, and button combos seem to change the timing of said noises but nothing shows up under adb or fastboot devices....help!!!!!