Does anyone happen to have the stock ColorOS recovery.img for this device?
Thanks!
Jaernyx said:
Does anyone happen to have the stock ColorOS recovery.img for this device?
Thanks!
Click to expand...
Click to collapse
I've been looking for it also. I couldn't find it in the ozip OTA files.
I have the Chinese variant and want to test the Chinese TWRP, but need the stock recovery just in case...
it's all inside the file system.new.dat.br I'm also trying with the global version
Kratong said:
it's all inside the file system.new.dat.br I'm also trying with the global version
Click to expand...
Click to collapse
I extracted that file. There are a lot of folders. Not sure where to look. Any idea?
with which program? I can't do it I need a fastboot rom
I'll take a look in the system file as well when I get off work.
Smart of you to back your stuff up before diving in. I was trying to see if I could create a rom for my device but I believe I borked my partitions up.
The twrp from wzsx150 in the other thread doesn't boot on my device so I'm hoping the stock recovery image will get me on the right path. I was able to make a bootable twrp but the system partition doesn't mount correctly so I can't flash with it.
I'm pretty new to this stuff but learning more every time I work on it, haha. Should have taken correct precautions though.
Jaernyx said:
I'll take a look in the system file as well when I get off work.
Smart of you to back your stuff up before diving in. I was trying to see if I could create a rom for my device but I believe I borked my partitions up.
The twrp from wzsx150 in the other thread doesn't boot on my device so I'm hoping the stock recovery image will get me on the right path. I was able to make a bootable twrp but the system partition doesn't mount correctly so I can't flash with it.
I'm pretty new to this stuff but learning more every time I work on it, haha. Should have taken correct precautions though.
Click to expand...
Click to collapse
I can't fastboot boot that recovery either and I have the Chinese variant.
Did you do the disable verity etc before trying to boot until your TWRP? Or it could be encryption that's preventing you from viewing the system partition? Might need to format data?
None of these things I'm willing to try without a backup stock recovery though
anandlal said:
I can't fastboot boot that recovery either and I have the Chinese variant.
Did you do the disable verity etc before trying to boot until your TWRP? Or it could be encryption that's preventing you from viewing the system partition? Might need to format data?
None of these things I'm willing to try without a backup stock recovery though
Click to expand...
Click to collapse
I poked around all the dat.br files in the OTA update except the numbered version files and wasn't able to find any recovery.
Unfortunately, I've already fully wiped and it still wont' mount. It kind of seems like my system partition got completely nuked, although tbh I'm not entirely sure how I did that
That being said, I tried directly mounting /system, but I get the error that a block device is required. I checked the fstab files on what I have available and it seems to point to a file that isn't on my device. RIP, haha.
I'll continue to see what I can figure out though. Happy to know it doesn't boot for you actually, as I thought it not booting was due to me gunking up something. Oh yeah, I have a Chinese variant too.
Jaernyx said:
I poked around all the dat.br files in the OTA update except the numbered version files and wasn't able to find any recovery.
Unfortunately, I've already fully wiped and it still wont' mount. It kind of seems like my system partition got completely nuked, although tbh I'm not entirely sure how I did that
That being said, I tried directly mounting /system, but I get the error that a block device is required. I checked the fstab files on what I have available and it seems to point to a file that isn't on my device. RIP, haha.
I'll continue to see what I can figure out though. Happy to know it doesn't boot for you actually, as I thought it not booting was due to me gunking up something. Oh yeah, I have a Chinese variant too.
Click to expand...
Click to collapse
Damn... That's insane! So I guess you have to wait for the stock recovery to be available before you can go back to the stock rom.
What I do like about the stock recovery is that your have the option to go online and install the stock rom.
Kratong said:
with which program? I can't do it I need a fastboot rom
Click to expand...
Click to collapse
Convert system.dat.br to system.dat (brotli)
Convert system.dat to RAW system.img (sdat2img)
Extract system.img (imgextractor)
I installed the twrp chinese version on the global version now i am rom china I wanted to go back but I can't go back to global
Kratong said:
I installed the twrp chinese version on the global version now i am rom china I wanted to go back but I can't go back to global
Click to expand...
Click to collapse
You were actually able to install the CN ROM in the Global variant?!
Yes
---------- Post added at 11:35 AM ---------- Previous post was at 11:25 AM ----------
I need a specific twrp for my model or a fastboot rom to go back to global
Kratong said:
Yes
---------- Post added at 11:35 AM ---------- Previous post was at 11:25 AM ----------
I need a specific twrp for my model or a fastboot rom to go back to global
Click to expand...
Click to collapse
What was the steps you took to go from EU to CN?
I was actually considering going from CN to EU but thought I'd was not possible due to the different partition sizes for system etc..
I can't convert system.img to raw system.img for flash with fastboot can someone post it already converted? for rmx2076.thanks
Kratong said:
I can't convert system.img to raw system.img for flash with fastboot can someone post it already converted? for rmx2076.thanks
Click to expand...
Click to collapse
this link system.img for rmx2076
https://bit.ly/2Yse5ue
i flashed system.img with fastboot reports this error invalid sparse file at header magi. what should i do?
Kratong said:
Yes
---------- Post added at 11:35 AM ---------- Previous post was at 11:25 AM ----------
I need a specific twrp for my model or a fastboot rom to go back to global
Click to expand...
Click to collapse
They just released a flash tool. Let me know if this works for you.
https://www.realmebbs.com/post-deta...subForumId=1156882636577189888&language=zh-CN
thanks later I look at it but is it ok for the global version too? my situation is now this I managed to install the Chinese rom on rmx 2076 involuntarily but the modem part doesn't work everything else works
Kratong said:
thanks later I look at it but is it ok for the global version too? my situation is now this I managed to install the Chinese rom on rmx 2076 involuntarily but the modem part doesn't work everything else works
Click to expand...
Click to collapse
From the looks of it. You just need to have your phone in fastboot mode and select the file you want to flash. So you can try selecting the Global ozip and see if that would bring you back to stock.
Related
I've been in the samsung family for so long that I didn't realize how different flashing can be. I broke my phone so I bought a Moto G. Rooted it right away with only a little trouble. I installed a Lollipop ROM afterward and couldn't get my phone to boot. Guess who forgot to do a backup of the stock ROM? Yay me... but anyway, I found a stock file and went through all the steps in the screenshot. Each time, I got the okay to move on and I assumed I had the stock file flashed. Upon rebooting, I stay at the "warning, bootloader is unlocked" and phone doesn't go any further. I'm not booting up at all and custom recovery is gone now.
Can anyone help? I'm at my wit's end.
Thanks in advance.
http://forum.xda-developers.com/showthread.php?t=2542219
Follow this step by step. I did it twice. If your phone boots, it is more than likely recoverable. Once you get everything sorted out and are ready to flash a custom ROM, I recommend Carbon ROM (personal preference).
The lollipop ones are still shaky. I would try em out but they truly aren't daily drivers yet
---------- Post added at 11:19 AM ---------- Previous post was at 11:01 AM ----------
Another thought. You have your bootloader unlocked. You can flash the TWRP image through fastboot. Then you can flash the "flashable zip" stock firmware
BBobby said:
http://forum.xda-developers.com/showthread.php?t=2542219
Follow this step by step. I did it twice. If your phone boots, it is more than likely recoverable. Once you get everything sorted out and are ready to flash a custom ROM, I recommend Carbon ROM (personal preference).
The lollipop ones are still shaky. I would try em out but they truly aren't daily drivers yet
---------- Post added at 11:19 AM ---------- Previous post was at 11:01 AM ----------
Another thought. You have your bootloader unlocked. You can flash the TWRP image through fastboot. Then you can flash the "flashable zip" stock firmware
Click to expand...
Click to collapse
That's actually the instructions I used to try to flash back to stock. But when it reboots, it never gets past the warning about bootloader. I can get the TWRP recovery back but from there is there another way to flash the "flashable zip"? With Samsung I could always use ODIN but I don't think it works with Moto G. I can't get the zip to internal storage to flash it.
Thanks for the reply by the way I'm going to try it one more time I think....
http://forum.xda-developers.com/showthread.php?t=2854688
Flashable stock zips. I don't have a PC to do a full reset. But with TWRP and the flashable stock zip I have had absolutely no problem.
If all else fails I would give it a shot
I have the xt 1032 cricket/aio. I am using stock "us retail" and it works just fine. If you have radio issues etc there is also a repository of flashable radio images
BBobby said:
http://forum.xda-developers.com/showthread.php?t=2854688
Flashable stock zips. I don't have a PC to do a full reset. But with TWRP and the flashable stock zip I have had absolutely no problem.
If all else fails I would give it a shot
I have the xt 1032 cricket/aio. I am using stock "us retail" and it works just fine. If you have radio issues etc there is also a repository of flashable radio images
Click to expand...
Click to collapse
I hate sounding dumb... but how will I flash the zip if I can't get it on my phone?
Get back TWRP custom recovery by booting your phone into bootloader and flash via fastboot. You can get the .IMG file for the falcon from their website latest version is 2.8.5.0
http://teamw.in/project/twrp2/233
Then simply install the corresponding stock flashable zip
BBobby said:
Get back TWRP custom recovery by booting your phone into bootloader and flash via fastboot. You can get the .IMG file for the falcon from their website latest version is 2.8.5.0
http://teamw.in/project/twrp2/233
Then simply install the corresponding stock flashable zip
Click to expand...
Click to collapse
Thank you for all your help. I'll give that a shot.
BBobby said:
Get back TWRP custom recovery by booting your phone into bootloader and flash via fastboot. You can get the .IMG file for the falcon from their website latest version is 2.8.5.0
http://teamw.in/project/twrp2/233
Then simply install the corresponding stock flashable zip
Click to expand...
Click to collapse
Quick question. When I go into recovery to flash the zip, do I go to 'advanced' and then ' terminal command'? and go from there? I feel like a noob and I've flashed dozens of roms...
To flash a zip, choose the install option, find the name of the zip, select it, swipe to install it.
audit13 said:
To flash a zip, choose the install option, find the name of the zip, select it, swipe to install it.
Click to expand...
Click to collapse
The problem is that I didn't make a backup. When I tried flashing back to stock using fastboot everything was wiped. I don't even have the original custom ROM that started the whole mess. The stock file flashed but phone won't boot. I never get passed the boot loader warning screen. I did everything to the tee (following the directions that BBobby posted above. Actually did it twice. Isn't there an ODIN type deal for this phone. Brand new and I've broke it dangit.
Oh and I can't get into the phone to enable us debugging.
There is rsd lite but it may not help. Odin doesn't help if you can't enter download mode too. Usb debugging isn't require to flash a rom or install recovery.
It sounds like your phone is not booting because of the bootloade or the data partition is messed up.
I can get into bootloader and I have TWRP installed and can boot into it. I'm starting to think it's a lost cause. Thanks though y'all.
stacalicious said:
I can get into bootloader and I have TWRP installed and can boot into it. I'm starting to think it's a lost cause. Thanks though y'all.
Click to expand...
Click to collapse
I also got similar problem as yours. I have xt1033 dual sim phone and i had flashed lollipop 5.0.2 soak version. When official update was released for xt1033 i got back to kitkat 4.4.4 to download ota. But when i flashed kitkat through fastboot it got stuck on unlocked bootloader screen. Only solution i got still is converting to gpe. Only Gpe firmware boots. Im still finding solution for bootloop
You can get into TWRP? What happens when you use it to flash a custom ROM?
BBobby said:
http://forum.xda-developers.com/showthread.php?t=2542219
Follow this step by step. I did it twice. If your phone boots, it is more than likely recoverable. Once you get everything sorted out and are ready to flash a custom ROM, I recommend Carbon ROM (personal preference).
The lollipop ones are still shaky. I would try em out but they truly aren't daily drivers yet
---------- Post added at 11:19 AM ---------- Previous post was at 11:01 AM ----------
Another thought. You have your bootloader unlocked. You can flash the TWRP image through fastboot. Then you can flash the "flashable zip" stock firmware
Click to expand...
Click to collapse
audit13 said:
You can get into TWRP? What happens when you use it to flash a custom ROM?
Click to expand...
Click to collapse
I originally flashed a custom ROM but it never would get past the loading screen. I went through all the steps to flash back to stock and now all my data is gone. The ROM I had in my download folder is gone as is all my other info. So I get into TWRP but there's nothing in my phone I can flash.
audit13 said:
You can get into TWRP? What happens when you use it to flash a custom ROM?
Click to expand...
Click to collapse
I've flashed dozens, probably hundreds of ROMs in the past and never ran into such an issue. Custom ROM seemed to take, but got stuck. So I used fastboot and followed the directions to the tee in this link http://forum.xda-developers.com/showthread.php?t=2542219
When the ROM is finished flashing (stock that is) it never gets past the bootloader warning screen. If I could just get a zip onto the phone, I could flash through TWRP but I have no idea how to or if it's even possible.
Cwm have a option "sdcard mount" via usb. I dont remember the specific option but you can mount your device and connect it to a computer.
esd316 said:
Cwm have a option "sdcard mount" via usb. I dont remember the specific option but you can mount your device and connect it to a computer.
Click to expand...
Click to collapse
So I got into cwm. I can't mount usb storage, but I have an option to use adb sideload? Can I flash stock from there?
http://teamw.in/project/twrp2/233
Instructions on how to flash via fastboot are there in the same download page
---------- Post added at 02:47 AM ---------- Previous post was at 02:43 AM ----------
stacalicious said:
Quick question. When I go into recovery to flash the zip, do I go to 'advanced' and then ' terminal command'? and go from there? I feel like a noob and I've flashed dozens of roms...
Click to expand...
Click to collapse
The moto g just needs to do a wipe. Advanced wipe is not necessary. Then install the zip from the folder. By the way you can flash from USB otg (USB storage device such as a flash drive)
I fixed it!!!
stacalicious said:
I originally flashed a custom ROM but it never would get past the loading screen. I went through all the steps to flash back to stock and now all my data is gone. The ROM I had in my download folder is gone as is all my other info. So I get into TWRP but there's nothing in my phone I can flash.
Click to expand...
Click to collapse
esd316 said:
Cwm have a option "sdcard mount" via usb. I dont remember the specific option but you can mount your device and connect it to a computer.
Click to expand...
Click to collapse
I'd hug your neck right now if I could get to you!!! I flashed cwm, went to adb sideload and installed a stock rom. My phone is back up and money isn't going to be pissed into the wind because I made a mistake. Thanks to everyone for your help.
The stock ROM has a feature called verity, which ensures that the system partition is not modified. It uses a cryptographic signature to verify each sector on the partition. If any sector is modified, it is treated as corrupt.
In other words, any changes to the system partition will render it unbootable. This includes mounting /system read-write in recovery, even once.
In order to modify your system partition or recover from accidentally mounting your system partition read-write, you must download and flash the correct boot image using tuliptool.
You can find stock boot images with verity removed here:
US model, version 7.1.1 b12
md5=71428e4957763858f47bc9540e848d5e
US model, version 7.1.1 b14
md5=c6a67411e81f27d798eea035ddf4261e
EU model, version 7.1.1 b09
md5=ba210d332d3527b81f652dd0d2ce962e
i tried to see what would happen if i adb sideload supersu and my results came out that the went to zte screen and went into a bootloop didnt boot up but i have root priv in twrp....hmm. so i re-edl boot to after that i was able to boot back in to my android without root or supersu and twrp went back to normal aswell i was in the mood to test thankfully i was able to fix what ever had any issues
What would we need to provide for you to make one for v1.0.0B06?
I can make one for any firmware version. I just need the following:
* any relevant regional or model info.
* firmware version (including android version).
* the backup boot image, eg. from tuliptool.
parawizard said:
What would we need to provide for you to make one for v1.0.0B06?
Click to expand...
Click to collapse
So if I were to want to stay on the current ZTE rom (for now) would I need to flash this in order to root or currently root is only supported on the incomplete rom you are working on?
Depends how you root. I don't run stock so someone else should answer with details.
fallen00sniper said:
So if I were to want to stay on the current ZTE rom (for now) would I need to flash this in order to root or currently root is only supported on the incomplete rom you are working on?
Click to expand...
Click to collapse
tdm said:
Depends how you root. I don't run stock so someone else should answer with details.
Click to expand...
Click to collapse
i'm not a fan of the stock image, i do like to keep features which the stock seems devoid other than atmos which used to be hit or miss lol
i am sure someone out there likes the stock look, i used nova launcher and made things smaller, neater and tried to make it look a little better.
Done some experiments with SuperSU 2.82 (unsuccessfully, got bootloop).
In other words, any changes to the system partition will render it unbootable. This includes mounting /system read-write in recovery, even once.
Click to expand...
Click to collapse
And was able restore phone to work only with this EU boot.
Thanks, for making and publishing it!
Hi tdm, my 7 mini is USA hardware version but with European 6.0.1 firmware (build number ZTE B2017G V1.0.0B12). I tried to go back to USA Nougat firmware but unsuccessfully. Basically my phone was turned into P852A11 from P852A12. Do I need a new boot image with verity removed so that I can flash USA firmware? If I have to use Tuliptool, can you build a Windows32 version? Thanks in advance.
Sure thing, I'll make a firmware package. Please get me your partition checksums as in this post:
https://forum.xda-developers.com/showpost.php?p=74134639&postcount=52
I'll look into a win32 version of tuliptool.
bao_gg said:
Hi tdm, my 7 mini is USA hardware version but with European 6.0.1 firmware (build number ZTE B2017G V1.0.0B12). I tried to go back to USA Nougat firmware but unsuccessfully. Basically my phone was turned into P852A11 from P852A12. Do I need a new boot image with verity removed so that I can flash USA firmware? If I have to use Tuliptool, can you build a Windows32 version? Thanks in advance.
Click to expand...
Click to collapse
tdm said:
Sure thing, I'll make a firmware package. Please get me your partition checksums as in this post:
https://forum.xda-developers.com/showpost.php?p=74134639&postcount=52
I'll look into a win32 version of tuliptool.
Click to expand...
Click to collapse
Thank you tdm. You are awsome. I will provide you the checksums tomorrow.
Hey @tdm
Wanted to ask if you just removed the "verify" option in the fstab file to strip the dm verity checks? I might have read something like this before
Yes that's exactly it.
TheSSJ said:
Hey @tdm
Wanted to ask if you just removed the "verify" option in the fstab file to strip the dm verity checks? I might have read something like this before
Click to expand...
Click to collapse
I had finally gotten around to unlocking the bootloader and flashing TWRP.
Would flashing one of your custom ROMs without flashing the verity-free boot images affect anything?
I would suggest flashing the no verity boot just to avoid the headache
The stock boot images are only for running stock. Custom ROMs all include their own boot images.
JoeGatto said:
I had finally gotten around to unlocking the bootloader and flashing TWRP.
Would flashing one of your custom ROMs without flashing the verity-free boot images affect anything?
Click to expand...
Click to collapse
tdm said:
The stock boot images are only for running stock. Custom ROMs all include their own boot images.
Click to expand...
Click to collapse
Great. Looks like I'll be trying AOKP soon.
JoeGatto said:
Great. Looks like I'll be trying AOKP soon.
Click to expand...
Click to collapse
I've been running it for a couple of days and so far its great. No issues here
MrWhite0429 said:
I've been running it for a couple of days and so far its great. No issues here
Click to expand...
Click to collapse
You weren't kidding. Feels much faster than ZTE's ROM, and so refreshing as long as I've been looking at that MiFavor UI.
EDIT: Battery drain during standby.
tdm said:
Sure thing, I'll make a firmware package. Please get me your partition checksums as in this post:
https://forum.xda-developers.com/showpost.php?p=74134639&postcount=52
I'll look into a win32 version of tuliptool.
Click to expand...
Click to collapse
Hi tdm, my adb can not recognize the mini. And in order to get the partition info, I need to "boot into twrp" as the instruction says. But my recovery is STOCK not TWRP.
Anyway, if you can make a win32 Tuliptool, I can unlock the bootloader and flash the TWRP in. After that, I can flash any firmware that I want. Is it correct?
Rooted Verizon Pixel 2: "There's an internal problem with your device. Contact ..."
I rooted my Verizon Pixel 2 running 8.1 and whenever I boot it up and I'm on the lock screen, I get this error: ""There's an internal problem with your device. Contact your manufacturer for details" Anyone know how to get rid of it?
I found this for a Nexus6p, but I'm not sure it'd work for a Google Pixel 2 (Verizon): https://forum.xda-developers.com/showpost.php?p=64289509&postcount=8
You have to re flash the stock boot image and dtbo image.
enzyne said:
You have to re flash the stock boot image and dtbo image.
Click to expand...
Click to collapse
On both slots.
enzyne said:
You have to re flash the stock boot image and dtbo image.
Click to expand...
Click to collapse
What was said but do everything here otherwise it will keep happening.
https://www.google.co.uk/amp/s/foru...ix-dtbo-message-theres-internal-t3715620/amp/
---------- Post added at 01:30 AM ---------- Previous post was at 01:21 AM ----------
iamnotreallyhere said:
What was said but do everything here otherwise it will keep happening.
https://www.google.co.uk/amp/s/foru...ix-dtbo-message-theres-internal-t3715620/amp/
Click to expand...
Click to collapse
Also you may not have to reflash the stock boot image just dtbo. If you are using a custom kernel make sure to flash that dtbo.
Ok. I have a few questions...
1. I did find this thread (and commented in it), but was concerned it'd be different for my Verizon Pixel 2. I now assume no as you linked it.
2. That thread didn't specify how to get the dtbo.img. I know how to get the stock image from Google, but not the dtbo.img. What I did was download the Google stock image, unzipped, then found the dtbo.img within the "taimen-opm1.171019.011-factory-2df1c1cb" folder. Is that correct?
3. Lastly, in no way can brick my phone/make me lose my unlocked phone...right?
EDIT: I just went ahead and did it. Looks like everything is working!
Lightn1ng said:
On both slots.
Click to expand...
Click to collapse
I did this. Curious though.. @Shadow/Walker doesn't mention doing it...is it important?
I downgraded to Magisk 15.1 because of this issue. 15.2 doesn't bring this error.
upperbladez said:
Ok. I have a few questions...
1. I did find this thread (and commented in it), but was concerned it'd be different for my Verizon Pixel 2. I now assume no as you linked it.
2. That thread didn't specify how to get the dtbo.img. I know how to get the stock image from Google, but not the dtbo.img. What I did was download the Google stock image, unzipped, then found the dtbo.img within the "taimen-opm1.171019.011-factory-2df1c1cb" folder. Is that correct?
3. Lastly, in no way can brick my phone/make me lose my unlocked phone...right?
EDIT: I just went ahead and did it. Looks like everything is working!
Click to expand...
Click to collapse
Glad you figured it out! I was going to say it's in the second zip file within the first zip file. Also I don't think there is a way to brick unless you lock your boot loader. As long as you can fastboot and have an unlocked bootloader you should be able to recover from anything. Never ever ever lock your bootloader ever again
Just ignore the message, it's just a security warning because of what Magisk is patching to enable systemless mods on the vendor partition. I doesn't affect anything.
I notice the full ROM has separate recovery image.
Is there any way to develop TWRP from the recovery?
I never have knowledge to make one unfortunately
mingkee said:
I notice the full ROM has separate recovery image.
Is there any way to develop TWRP from the recovery?
I never have knowledge to make one unfortunately
Click to expand...
Click to collapse
Because of dynamic partitions, TWRP is useless actually. You can boot it but that's all, you can't flash anything.
Running the same issue on Pixel 4XL. Any device that boots on 10 or higher at the moment. No update since October 2019...
vache said:
Because of dynamic partitions, TWRP is useless actually. You can boot it but that's all, you can't flash anything.
Click to expand...
Click to collapse
Any further news on this?
Would love to make a backup before attempting to root with Magisk
jharkness316 said:
Any further news on this?
Would love to make a backup before attempting to root with Magisk
Click to expand...
Click to collapse
There's an easy way to revert
Download a full ROM and extract boot.img and patch one and keep another ad backup
mingkee said:
There's an easy way to revert
Download a full ROM and extract boot.img and patch one and keep another ad backup
Click to expand...
Click to collapse
How can I extract the boot.img and patch it before I flash it to the phone?
Finally how can I flash the boot.img to the phone?
Sorry to sound like an idiot. I have rooted a phone before ( Moto X Pure )
and it worked well.
This phone tho is newer and uncharted territory for me. There were programs and such for the X Pure
when i did it. This seems to be a command (adb) process only.
Finally, is there a different logo.img I can use ( I assume this is the boot animation file)
jharkness316 said:
How can I extract the boot.img and patch it before I flash it to the phone?
Finally how can I flash the boot.img to the phone?
Sorry to sound like an idiot. I have rooted a phone before ( Moto X Pure )
and it worked well.
This phone tho is newer and uncharted territory for me. There were programs and such for the X Pure
when i did it. This seems to be a command (adb) process only.
Finally, is there a different logo.img I can use ( I assume this is the boot animation file)
Click to expand...
Click to collapse
ROM is zip format
You need to get the lastest ADB for windows to have fastbootd support
adb reboot fastboot
fastboot reboot fastboot
Fastbootd is like recovery and flashing command is same
Found the TWRP has support for One Action, Vision, and Zoom
Are these mainly the same phone with camera and battery changes as well as some software changes?
Can one of these not be used for Hyper?
If things go awry, can a factory flash from stock rom fix issues?
---------- Post added at 08:01 AM ---------- Previous post was at 08:01 AM ----------
Found the TWRP has support for One Action, Vision, and Zoom
Are these mainly the same phone with camera and battery changes as well as some software changes?
Can one of these not be used for Hyper?
If things go awry, can a factory flash from stock rom fix issues?
Vache, the only dev we have, made a port today. It's in the roms section...
Hello!
I tried the search function but my search-fu isn't strong today. I got a Vortex V22 phone from Standup Wireless. I must have been half asleep, because when i flashed what I assumed was the correct boot.img, I got stuck in a boot loop.
On further investigation, I had flashed the boot for another device called Vortex. I am having incredible difficulty in finding the right boot image. The info I have from the side of the box is:
Vortex V22 4G LTE
Color: Graphite Blue
ROM 32GB
RAM 3GB
OS Android 11
FCC ID 2ADLJ-V22
I deeply appreciate any and all help. Thanks so much!
i was trying to find a phone case for the phone what model number is yours ?
If you're still searching I can try to make a rom dump, I have this phone as well brand new untouched or registered.
I'd just need a tutorial on the proper way to dump and extract the files so I can upload the boot.img
_
I've never used it cause I put the StandUp Wireless sim in my T-Mo InSeeGo 5G HotSpot and prefer to use my Galaxy S8 with Keyboard Cover Case and Unihertz Titan Pocket
Just dumping the firmware from mine, using SP Flash Tool. Used this guide: https://www.hovatek.com/forum/thread-12719.html
Will remove userdata & cache, but there is a LOT of gbs of system data. This phone is appearently Treble-enabled with VNDK ver 30, so yes, you can flash a GSI on there. Will provide a custom recovery necessary.
Edit: if you were wondering, this phone has a MT6761 with a eMMC flash.
PicelBoi said:
Just dumping the firmware from mine, using SP Flash Tool. Used this guide: https://www.hovatek.com/forum/thread-12719.html
Will remove userdata & cache, but there is a LOT of gbs of system data. This phone is appearently Treble-enabled with VNDK ver 30, so yes, you can flash a GSI on there. Will provide a custom recovery necessary.
Edit: if you were wondering, this phone has a MT6761 with a eMMC flash.
Click to expand...
Click to collapse
Hi PicelBoi,
I have the V22. I've unlocked the BL and trying to install a custom rom via ADB or Fastboot but have had no luck. I try to erase or flash and I get errors saying partitions don't exist. Can you please help out with a recovery file?
I tried the hovatek guide but didn't have any luck, but I tried it before the BL was unlocked. Would that be an issue with the sp flash tool? I was told it shouldn't matter.
In fastboot not fastboot d do
Fastboot flash unlocking
And it'll ask ya if u agree bs....
& Click yes.
Mtkclient unlocks bootloader as well
defcondoc said:
Hi PicelBoi,
I have the V22. I've unlocked the BL and trying to install a custom rom via ADB or Fastboot but have had no luck. I try to erase or flash and I get errors saying partitions don't exist. Can you please help out with a recovery file?
I tried the hovatek guide but didn't have any luck, but I tried it before the BL was unlocked. Would that be an issue with the sp flash tool? I was told it shouldn't matter.
Click to expand...
Click to collapse
Sorry for waiting so long! Yeah, I got the firmware! Also follow previous guys post! Do you want my boot.img? Make sure you disable Android Verified Boot too!
PicelBoi said:
Sorry for waiting so long! Yeah, I got the firmware! Also follow previous guys post! Do you want my boot.img? Make sure you disable Android Verified Boot too!
Click to expand...
Click to collapse
No worries. Yes! Do you have the entire rom? The boot.img would definitiely be great as well.
mee too
defcondoc said:
No worries. Yes! Do you have the entire rom? The boot.img would definitiely be great as well.
Click to expand...
Click to collapse
Yea, will post it later this day! Do you need anything else like my super partition?
PicelBoi said:
Yea, will post it later this day!
Click to expand...
Click to collapse
Also this is a GSI image that works with this device - https://github.com/phhusson/treble_experimentations/releases/tag/v313 - newer versions might not work unfortunately.
defcondoc said:
Hi PicelBoi,
I have the V22. I've unlocked the BL and trying to install a custom rom via ADB or Fastboot but have had no luck. I try to erase or flash and I get errors saying partitions don't exist. Can you please help out with a recovery file?
I tried the hovatek guide but didn't have any luck, but I tried it before the BL was unlocked. Would that be an issue with the sp flash tool? I was told it shouldn't matter.
Click to expand...
Click to collapse
You need to reboot to userland fastboot, which you could do by rebooting to normal fastboot then telling fastboot to reboot to fastboot by typing in fastboot reboot fastboot. You will see a new screen, and now you could flash a GSI to the phone.
PicelBoi said:
Also this is a GSI image that works with this device - https://github.com/phhusson/treble_experimentations/releases/tag/v313 - newer versions might not work unfortunately.
Click to expand...
Click to collapse
I was able to get a bunch of GSI's that work with it, including the phone you posted, but I was looking to get root and found a couple pre-rooted GSI's that work as well. Newer ones do work as well I has 13 rooted and working. However, I liked the Pixel ROMs the best and would prefer to install those instead and then root. So I need the firmware for that so I can patch a modified boot.img.
PicelBoi said:
You need to reboot to userland fastboot, which you could do by rebooting to normal fastboot then telling fastboot to reboot to fastboot by typing in fastboot reboot fastboot. You will see a new screen, and now you could flash a GSI to the phone.
Click to expand...
Click to collapse
Thank you. I understand and have a lot of experience with this. However, I still never understood why there is two Fastboot's.
I can't get it to boot in one I flash the super that I backed up that don't get it to boot maybe I could use a good super. What about vbmeta?
atsalchenberg said:
I can't get it to boot in one I flash the super that I backed up that don't get it to boot maybe I could use a good super. What about vbmeta?
Click to expand...
Click to collapse
Are you looking for a good GSI ROM?
As of right now I'm just trying to get it booted up with any room. I got it rooted and then something I ****ed up when I tried to flash a GSI. And I started messing with the boot a boot b vbMeta from system and blank. And I don't have the firmware an the super that I backed up won't boot when I flash it.
But yes I am indeed looking for a good running a12 rom
atsalchenberg said:
As of right now I'm just trying to get it booted up with any room. I got it rooted and then something I ****ed up when I tried to flash a GSI. And I started messing with the boot a boot b vbMeta from system and blank. And I don't have the firmware an the super that I backed up won't boot when I flash it.
Click to expand...
Click to collapse
I completely messed up one messing with partitions and it took many tries trying to get to was able to still get to the bootloader fastboot and then recovery to fastbootD. You should be able to get it booted into fastbootd and flash as it seems you can.
Try the one below. you should be able to find it with a google search. If you can't let me know and I will try to look and see where I downloaded it from as I cannot remember where I found it.
I've tried many GSI ROM's Some boot fully, some only boot to the boot screen and some won't boot at all.
I'm using 13 rooted LineageOS GSI version 20-20230324-UNOFFICIAL-arm64_bvS
It is vanilla. I can't remember if there is a GAPPS version or not. But you can load it all after with magisk. But its rooted.
I still would like if picelboi could share the stock rom, so we can have a boot.img. I would like to try other ROM's that are not PRE-Rooted.
atsalchenberg said:
But yes I am indeed looking for a good running a12 rom
Click to expand...
Click to collapse
I can't remember which A12 I had working but I was looking for root and the one A12 that was prerooted I had issues with so I went to A13.
This is an A13. LineageOS GSI version 20-20230324-UNOFFICIAL-arm64_bvS
There may be a newer version of it now.
Also, these phones seem have that internet connect issue with some GSI ROMS and this is one of them I think, they connect to wifi but they won't actually connect to internet, but there is a easy fix for it.