Related
Hey,
Sorry for the noob question - but I wasn't able to find anything on this. Everyone seems to take this as it is, but I simply want to know why boot.img is flashed in order to get root and how it affects the phone.
I followed this tutorial to get my Rogers Magic rooted.
What did the boot.img do in this case and can I use Amon_RA's RAv1.1.2 ION Recovery or do I need to flash another boot image in order to use a different recovery.img.
Basically, I just want to know why I do the steps that I do.
vladkor said:
Hey,
Sorry for the noob question - but I wasn't able to find anything on this. Everyone seems to take this as it is, but I simply want to know why boot.img is flashed in order to get root and how it affects the phone.
I followed this tutorial to get my Rogers Magic rooted.
What did the boot.img do in this case and can I use Amon_RA's RAv1.1.2 ION Recovery or do I need to flash another boot image in order to use a different recovery.img.
Basically, I just want to know why I do the steps that I do.
Click to expand...
Click to collapse
boot.img contains
the actual linux kernel for the phone
small ramdrive to start the system
system.img contains
android os, libraries,system settings and applications
userdata.img contains apps, and user settings
br
jerpelea said:
boot.img contains
the actual linux kernel for the phone
small ramdrive to start the system
system.img contains
android os, libraries,system settings and applications
userdata.img contains apps, and user settings
br
Click to expand...
Click to collapse
Thanks for the reply! I'm still lost though on the whole 'fastboot flash boot boot.img' part.
Is there a specific/best/newest boot.img that I should be using with the Rogers Magic? Are there different ones out there or is it just one standard one?
Hi there,
A while ago I got a OnePlus One which came with ColorOS loaded. I of course googled my way to get the Cyanogenmod and followed these instructions.
http://www.youtube.com/watch?v=QDKOEtN9pbo
I'm currently on the 25R firmware and I know there are some updates after that but the phone doesnt detect any update release. I would like to know why the OTA updates are not being picked up from the phone. Was it simply the easy method mentioned above?
I also thought of reflashing it properly and found some instructions on the web.
Code:
Install Android tools (and drivers if you use Windows-crap). You need the fastboot and adb tools
Get http://dist01.slc.cy...ed-fastboot.zip and unpack it
Enable USB debugging on the phone
Run adb reboot-bootloader
Once bootloader started run: fastboot oem unlock
After automatic reboot, do steps 3 & 4 again
In the directory where you unpacked it, run in a console
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata_64g.img (or userdata.img for 16G version)
fastboot oem lock
fastboot reboot
These instructions will somehow get the OTA updates working, am I right to assume that this method would rewrite everything and I would lose the recovery software of the ColorOS? Also are the Android tools these?
http://developer.android.com/sdk/index.html
Fastboot and ADB, I can use this one right?
http://forum.xda-developers.com/showthread.php?t=2588979
I appreciate the help and a few explanations.
Cheers.
Just download this
http://builds.cyngn.com/fota/incremental/bacon/cm-bacon-ac1ccf7921-to-5fa8c79c0b-signed.zip
Sent from my A0001 using XDA Premium 4 mobile app
scabbie1980 said:
Just download this
http://builds.cyngn.com/fota/incremental/bacon/cm-bacon-ac1ccf7921-to-5fa8c79c0b-signed.zip
Sent from my A0001 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hi scabbie, from the looks of the file its an incremental update. Do I just run it from the OPO with Cyanogenmod? If this is a long tedious method, I would rather do a fresh install and get the OTA updates to work. Also part of the reason I want a clean install is because the phone is acting up and my screen goes black when I call someone and then when I want to hang up the screen is still black and I cant hang up. and physical buttons dont respond either.
I dont know if this incremental update will fix this kind of problem, so hence my option to do some clean install.
Cheers
dude777 said:
Hi scabbie, from the looks of the file its an incremental update. Do I just run it from the OPO with Cyanogenmod? If this is a long tedious method, I would rather do a fresh install and get the OTA updates to work. Also part of the reason I want a clean install is because the phone is acting up and my screen goes black when I call someone and then when I want to hang up the screen is still black and I cant hang up. and physical buttons dont respond either.
I dont know if this incremental update will fix this kind of problem, so hence my option to do some clean install.
Cheers
Click to expand...
Click to collapse
If you're looking for a completely fresh install, just go to my guide thread (link in signature) and follow section 8.
Transmitted via Bacon
OK, for a clean download you need to download this in fastboot mood
https://www.copy.com/s/hMXtmkJAbDhjxQyC
Sent from my A0001 using XDA Premium 4 mobile app
---------- Post added at 02:01 PM ---------- Previous post was at 01:56 PM ----------
scabbie1980 said:
OK, for a clean download you need to download this in fastboot mood.
https://www.copy.com/s/hMXtmkJAbDhjxQyC
Look on YouTube on how to use this toolbox and it will completely wipe your phone then flash clean.
Sent from my A0001 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sent from my A0001 using XDA Premium 4 mobile app
scabbie1980 said:
OK, for a clean download you need to download this in fastboot mood
https://www.copy.com/s/hMXtmkJAbDhjxQyC
Sent from my A0001 using XDA Premium 4 mobile app
---------- Post added at 02:01 PM ---------- Previous post was at 01:56 PM ----------
Sent from my A0001 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
A toolbox is completely unnecessary, and they're more trouble than they're worth. Plus, nobody learns anything even using a toolbox, and that knowledge is crucial for when things go wrong.
Transmitted via Bacon
DON'T use a toolbox please
Learn as you go by doing things properly, I speak from my own experience. These skills and knowledge that you gain will help if you ever run into any issues
Go here to install the adb drivers computer wide so you can flash from any folder on your computer, it makes your life so much easier
http://forum.xda-developers.com/showthread.php?t=2588979
Then follow timmaaa guide on how to start fresh with a complete 44s ROM
Sent from my A0001 using XDA Free mobile app
Thanks guys for the effort here, really like your guides timmaaa very clear and non confusing. Yes I would like to avoid shortcuts as I took the easy route and now the phone goes in hiatus moment when calling. I'll get around this in the weekend and see how that goes.
Cheers.
@ timmaaa
Love the guide you put up, I was having a read through this and I'm slightly confused on your comments. http://forum.xda-developers.com/one...-to-guides-t2839471/post56731494#post56731494
You mentioned just go straight to Section 8, but in the link above you mentioned go through 1-4 then go to 8. I dont think I need to root on section 4 but for 1, 2 and 3, I would like to know, particularly in section 2 and 3 if you can explain to a novice like me. As I'm understanding this, I think the ColorOS phone has some recovery software, thats how I did the easy flashing method thing, so for section 2 your instructions will overwrite the ColorOS one?
For Section 3 the nandroid backup seems like a snapshot of the phone (which includes recovery, phone OS and other things) before installing custom rom?
Please let me know if my interpretation is correct and correct me along the way, I am here to learn what I can, so that I can successfully flash the OPO phone.
Cheers.
dude777 said:
@ timmaaa
Love the guide you put up, I was having a read through this and I'm slightly confused on your comments. http://forum.xda-developers.com/one...-to-guides-t2839471/post56731494#post56731494
You mentioned just go straight to Section 8, but in the link above you mentioned go through 1-4 then go to 8. I dont think I need to root on section 4 but for 1, 2 and 3, I would like to know, particularly in section 2 and 3 if you can explain to a novice like me. As I'm understanding this, I think the ColorOS phone has some recovery software, thats how I did the easy flashing method thing, so for section 2 your instructions will overwrite the ColorOS one?
For Section 3 the nandroid backup seems like a snapshot of the phone (which includes recovery, phone OS and other things) before installing custom rom?
Please let me know if my interpretation is correct and correct me along the way, I am here to learn what I can, so that I can successfully flash the OPO phone.
Cheers.
Click to expand...
Click to collapse
I was assuming that because you're on the 25R build of CM11S that you've already unlocked your bootloader and installed TWRP recovery, if this isn't the case then you will need to follow sections 1, 2, and 3 before moving on to section 8.
The phone definitely already has some kind of recovery on it (every phone does), but you do need to install a custom recovery in order to make a backup of your current ROM. It will overwrite the existing recovery when you install it, and then later on when you flash the fastboot images (in section 8) the stock recovery will overwrite the custom recovery. So why bother flashing the custom recovery if it'll just be overwritten? Because insurance. It'll allow you to make a nandroid backup of your current setup to fall back on just in case something goes wrong.
A nandroid is like a snapshot of the phone, but it doesn't include your recovery partition, it includes the /system partition (where the os resides), the /data partition (where your apps and settings reside), and the /boot partition (the kernel). You should always have at least one nandroid on your phone at all times. Personally, I make one before I flash anything, that way if I don't like whatever I'm flashing or if something goes wrong, I can just restore my backup and boot the phone up, and it's exactly how I left it.
After you've made your backup make sure you transfer it to your PC (and anything else important on the phone), because flashing the fastboot images is going to wipe your whole phone, including all of your user data.
If you have any other questions please don't hesitate to ask.
Transmitted via Bacon
timmaaa said:
I was assuming that because you're on the 25R build of CM11S that you've already unlocked your bootloader and installed TWRP recovery, if this isn't the case then you will need to follow sections 1, 2, and 3 before moving on to section 8.
The phone definitely already has some kind of recovery on it (every phone does), but you do need to install a custom recovery in order to make a backup of your current ROM. It will overwrite the existing recovery when you install it, and then later on when you flash the fastboot images (in section 8) the stock recovery will overwrite the custom recovery. So why bother flashing the custom recovery if it'll just be overwritten? Because insurance. It'll allow you to make a nandroid backup of your current setup to fall back on just in case something goes wrong.
A nandroid is like a snapshot of the phone, but it doesn't include your recovery partition, it includes the /system partition (where the os resides), the /data partition (where your apps and settings reside), and the /boot partition (the kernel). You should always have at least one nandroid on your phone at all times. Personally, I make one before I flash anything, that way if I don't like whatever I'm flashing or if something goes wrong, I can just restore my backup and boot the phone up, and it's exactly how I left it.
After you've made your backup make sure you transfer it to your PC (and anything else important on the phone), because flashing the fastboot images is going to wipe your whole phone, including all of your user data.
If you have any other questions please don't hesitate to ask.
Transmitted via Bacon
Click to expand...
Click to collapse
I see, so even if my phone doesnt have much inside it should still be recommended, because of the listed above are operational and if something were to happen on the newly flashed phone, I have no way of retracing my steps.
So in a hypothetical situation I unlocked the bootloader and proceed to section 2. The recovery software provided when I first got the phone will be overwritten by the TWRP recovery and I will have lost the old one. I will then perform a nandroid backup where I can preserve a last known working configuration as an insurance, if future flashes fail. I assume you restore nandroid backup through the TWRP recovery? Also the nandroid backup is made on the phone? so I will need to transfer that to my PC before flashing?
At this stage all I changed is the bootloader and recovery partition with custom recovery. When I jump to section 8 it should be smooth sailing, provided I follow them clearly and the drivers work on the PC.
I apologise for being a pain in the butt! I just like to clarify before I do something horrible and have no idea what to do next.
Cheers
dude777 said:
I see, so even if my phone doesnt have much inside it should still be recommended, because of the listed above are operational and if something were to happen on the newly flashed phone, I have no way of retracing my steps.
So in a hypothetical situation I unlocked the bootloader and proceed to section 2. The recovery software provided when I first got the phone will be overwritten by the TWRP recovery and I will have lost the old one. I will then perform a nandroid backup where I can preserve a last known working configuration as an insurance, if future flashes fail. I assume you restore nandroid backup through the TWRP recovery? Also the nandroid backup is made on the phone? so I will need to transfer that to my PC before flashing?
At this stage all I changed is the bootloader and recovery partition with custom recovery. When I jump to section 8 it should be smooth sailing, provided I follow them clearly and the drivers work on the PC.
I apologise for being a pain in the butt! I just like to clarify before I do something horrible and have no idea what to do next.
Cheers
Click to expand...
Click to collapse
You do indeed restore a nandroid backup with the recovery that you made the backup with. And yes it is saved on the phone so you will need to transfer it to your PC. You're not being a pain in the butt, you're doing the right thing and researching before attempting something.
Transmitted via Bacon
Yeah I agree users like you that research crap before attempting something are much preferred over users that blindly use a toolbox then come complaining cuz they messed something up but dunno how to fix it. I always do my research before flashing just like you are doing. Just make sure you install the drivers I linked to computer wide on your windows computer and you should have no problems, no need to install separate SDK for android and copy the files you're flashing into a special folder, etc
info update
Hey guys, noob here. I wanted to update to the most recent version and I am running version: XNPH25R atm.
Anyone could be so kind to tell me what's the easiest way to to this? I have a 64gb chinese version.
If you follow timmaaa's guide you should be good to go. I'm a noob myself and just did it over the weekend and its a blast. Good luck
Cheers
maeishoj said:
Hey guys, noob here. I wanted to update to the most recent version and I am running version: XNPH25R atm.
Anyone could be so kind to tell me what's the easiest way to to this? I have a 64gb chinese version.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2839471
Transmitted via Bacon
maeishoj said:
Hey guys, noob here. I wanted to update to the most recent version and I am running version: XNPH25R atm.
Anyone could be so kind to tell me what's the easiest way to to this? I have a 64gb chinese version.
Click to expand...
Click to collapse
Lol really? Did u completely ignore reading the thread that you just posted in??
[emoji15] [emoji58]
Moto G7 river xt1962-1 firmware 29.114-16-5
firmware_moto-g7_river_xt1962-1_29.114-16-5_copyparts
will be needed for custom roms
firmware_moto-g7_river_xt1962-1_29.114-16-5_full
is all partitions, not required for custom roms, just for curious developers
windows users will need to make their own .bat files I don't use windows
two things:
1. working on twrp for river
2. working on lineageos 16 for river based on payton... errors with some vendor files
actually errors all over
please help I have two newborns and only get a few minutes to myself each night
good luck on building lineage, the g6 never had any development so i dont anticipate the g7 will get much either. if i was you id concentrate on twrp so we can at least flash gsi based roms.
Is this the original factory signed rom? (I.e. is it possible to fully flash and relock bootloader?)
Also wondering if anyone has the latest full rom (29.114-16-7).
Thanks in advance!
ptn107 said:
Moto G7 river xt1962-1 firmware 29.114-16-5
firmware_moto-g7_river_xt1962-1_29.114-16-5_copyparts
will be needed for custom roms
firmware_moto-g7_river_xt1962-1_29.114-16-5_full
is all partitions, not required for custom roms, just for curious developers
windows users will need to make their own .bat files I don't use windows
two things:
1. working on twrp for river
2. working on lineageos 16 for river based on payton... errors with some vendor files
actually errors all over
please help I have two newborns and only get a few minutes to myself each night
Click to expand...
Click to collapse
Confirmed that at least boot.img is correctly signed. You rock ptn107!! However I did confirm (from the version number displayed in recovery) that this is 29.114.16 and not 29.114.16-5.
How were you able to extract the partitions? Specifically boot.img. If I can learn that, then it would be easy to unroot, take OTA updates, copy and save boot.img, and patch with Magisk. Thanks in advance!!!
smokinu said:
Confirmed that at least boot.img is correctly signed. You rock ptn107!! However I did confirm (from the version number displayed in recovery) that this is 29.114.16 and not 29.114.16-5.
How were you able to extract the partitions? Specifically boot.img. If I can learn that, then it would be easy to unroot, take OTA updates, copy and save boot.img, and patch with Magisk. Thanks in advance!!!
Click to expand...
Click to collapse
The boot image version does not change with every little update. For every version of 29.114.16-* released it will be the same boot.img. 29.114.16-7 is getting around and most likely uses the exact same boot.img as ours.
As for extracting the .img files I use a linux shell script I wrote here. Makes doing this quick with each new firmware image.
It needs to be placed in /sdcard on your device (root is required to work):
Code:
adb push mkimg.sh /sdcard/
adb shell
cd /sdcard/
su -c sh ./mkimg.sh
I do this in Linux. Not much of a Windows user anymore.
Output files go into /sdcard/firmware-images but you can change that with the 'outfolder' variable if you wish.
Long story short it takes the list of partitions from /dev/block/bootdevice/by-name/ and uses 'dd' to create the .img.
If you are looking to just get a boot.img from our device and nothing else the command would be as follows (needs root):
Code:
su dd if=/dev/block/mmcblk0p41 of=/sdcard/boot.img > /dev/null 2>&1
ptn107,
Thanks for the write-up. I'm familiar with a similar approach using TWRP (booted, but not installed) and dd copying the individual partitions. I will give your script a try. Should save a lot of time!
Is there a way to copy partitions without root? My biggest concern is taking on an OTA update (currently 16-7), without having the original signed images to revert back to stock and relock the bootloader. Motorola has historically been bad at providing factory roms. If there is a clever way to unroot, take an OTA, save original, and re-root....I'd be a happy camper!
/dev is user root and group root so root is necessary.
Is there a clever way to take an OTA update and get a copy of the new boot.img? From what i understand, you have to unroot to take an OTA update.
BTW...good luck with the newborns!! Mine is now 3 and is still as much of a handful as when he was a newborn.
ptn107 said:
The boot image version does not change with every little update. For every version of 29.114.16-* released it will be the same boot.img. 29.114.16-7 is getting around and most likely uses the exact same boot.img as ours.
As for extracting the .img files I use a linux shell script I wrote here. Makes doing this quick with each new firmware image.
It needs to be placed in /sdcard on your device (root is required to work):
Code:
adb push mkimg.sh /sdcard/
adb shell
cd /sdcard/
su -c sh ./mkimg.sh
I do this in Linux. Not much of a Windows user anymore.
Output files go into /sdcard/firmware-images but you can change that with the 'outfolder' variable if you wish.
Long story short it takes the list of partitions from /dev/block/bootdevice/by-name/ and uses 'dd' to create the .img.
If you are looking to just get a boot.img from our device and nothing else the command would be as follows (needs root):
Code:
su dd if=/dev/block/mmcblk0p41 of=/sdcard/boot.img > /dev/null 2>&1
Click to expand...
Click to collapse
Boot img sometimes changes, you never know. I bricked a g6 by flashing a boot img that the last number in the version was 2 instead of 4. Flashed, and got stuck in a bootloop. Had to completely reflash stock firmware, then took an OTA that bricked it.
clcombs262 said:
Boot img sometimes changes, you never know. I bricked a g6 by flashing a boot img that the last number in the version was 2 instead of 4. Flashed, and got stuck in a bootloop. Had to completely reflash stock firmware, then took an OTA that bricked it.
Click to expand...
Click to collapse
I did confirm that the boot.img between 16 and 16-5 is different. The recovery mode displays the correct version for each of the boot.imgs, and MD5 checksums are different, although same file size.
That being said, flashing a 16 boot.img on a 16-5 device will mearly result in bootloop until the correct version is flashed. People should keep track of which slot they loaded the boot.img into (A/B).
smokinu said:
I did confirm that the boot.img between 16 and 16-5 is different. The recovery mode displays the correct version for each of the boot.imgs, and MD5 checksums are different, although same file size.
That being said, flashing a 16 boot.img on a 16-5 device will mearly result in bootloop until the correct version is flashed. People should keep track of which slot they loaded the boot.img into (A/B).
Click to expand...
Click to collapse
Code:
fastboot oem lock
doesn't work with PPO29.114-16-5
says boot.img is not signed
update: same for PPO29.114-16 and PPO29.80-61
ptn107 said:
Code:
fastboot oem lock
doesn't work with PPO29.114-16-5
says boot.img is not signed
update: same for PPO29.114-16 and PPO29.80-61
Click to expand...
Click to collapse
I saw the same thing on my end at first. Found this to work repeatedly....
fastboot oem lock (enter this a few times until i says something to the effect of...."you still need to flash a signed boot.img")
fastboot flash boot boot.img (this will now flash fine without saying the image is not signed)
fastboot oem lock (if you prefer to re-lock. You'll need the unlock key again if you plan to unlock).
smokinu said:
I saw the same thing on my end at first. Found this to work repeatedly....
fastboot oem lock (enter this a few times until i says something to the effect of...."you still need to flash a signed boot.img")
fastboot flash boot boot.img (this will now flash fine without saying the image is not signed)
fastboot oem lock (if you prefer to re-lock. You'll need the unlock key again if you plan to unlock).
Click to expand...
Click to collapse
Wow. That actually worked. I had to do both commands like 6 times one after the other but it worked.
Thank you!
No problem! Glad I could help. Found that one by accident.
smokinu said:
No problem! Glad I could help. Found that one by accident.
Click to expand...
Click to collapse
I would have never found that out.
fastboot without root
I have been foolish and used twrp to wipe my G7. I am trying to use twrp to flash or fastboot update provided in this thread but neither approach works.
error is invalid zip file.
I was running -7 not -5
as in my title, there is no root. and because of my stupidity, no OS either! I am happy to give any details
Any help would be amazing. Thanks in advance!
Mr_navillus said:
I have been foolish and used twrp to wipe my G7. I am trying to use twrp to flash or fastboot update provided in this thread but neither approach works.
error is invalid zip file.
I was running -7 not -5
as in my title, there is no root. and because of my stupidity, no OS either! I am happy to give any details
Any help would be amazing. Thanks in advance!
Click to expand...
Click to collapse
The zip file itself cannot be flashed as it's not in proper update format. You'll have to extract and flash the contents via fastboot. To get to fastboot, power off the device then hold power and volume down until you see the bootloader screen, and then connect it via USB to a pc
Follow the instructions here to get back to stock
Mr_navillus said:
I have been foolish and used twrp to wipe my G7. I am trying to use twrp to flash or fastboot update provided in this thread but neither approach works.
error is invalid zip file.
I was running -7 not -5
as in my title, there is no root. and because of my stupidity, no OS either! I am happy to give any details
Any help would be amazing. Thanks in advance!
Click to expand...
Click to collapse
Sounds like you wiped the system partition then tried to flash the unflashable zip file (hence, no system)
First, always make backups.
Second, you can still get into fastboot and manually update/restore
You can also use the moto software to recover the device.
Get it into fastboot, start from there. It is 100% an easy recovery process
warBeard_actual said:
You can also use the moto software to recover the device.
Click to expand...
Click to collapse
This fixed it in a jiffy. Making backups from now on!
Question to the experts:
Unlocking the bootloader and rooting a phone is stressful times for those of us who (like me) only do this once every few years when we buy a new phone. On some phones, after attempts at routing, I've been stuck for days without a phone till some distant helpful person helped me back to a working rooted phone. Other times it was very simple. But the experience leaves you scared.
Yes I know it's my own (and similar other uneducated) fault because we did something wrong that would be obvious to any expert. But it happens to the rest of us no matter how many threads we read.
So my question is, if the phone becomes non functional following erroneous commands or files (my own unintentional error), will this same 'moto recovery' restore things?
Where do I find out more 'how' to use this Moto software and where this 'Moto software recovery' is to be found?
Thank you.
Edit
Just to clarify things, this is my first Moto phone which is why I don't know what the Moto software recovery is. Is it what you get by pressing Power-volume down?
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.