Related
please if some one knows how to flash a zimage kernel with adb shell????
kaokollaa said:
please if some one knows how to flash a zimage kernel with adb shell????
Click to expand...
Click to collapse
You can't do it with adb. The only way is to use fastboot from the android sdk (same folder that adb is located in) and use:
Code:
fastboot flash zimage zImage (where the second zImage is the filename)
kaokollaa said:
please if some one knows how to flash a zimage kernel with adb shell????
Click to expand...
Click to collapse
To flash a zImage:
1. Place the zImage you want to flash inside your AndroidSDK\tools folder
2. Reboot your phone into FASTBOOT/bootloader mode
3. Run the following commands (from your AndroidSDK\tools PATH):
Code:
fastboot devices -- Should pull up serial #
Code:
fastboot boot zImage -- Your phone will automatically reboot
The command above will only temporarily boot the new zImage, meaning you can test and do whatever you want, but after you reboot your phone again -- your previous zImage will be reloaded, removing the current one you were testing (Recommended method for testing, until you're sure you want to permanently flash).
If you want to make the new zImage you're trying to flash permanent, enter this command instead:
Code:
fastboot flash zimage zImage
Fastboot might hang so just turn the power off on your Evo then put it back into “fastboot” mode by pressing on the Power button WHILE holding down the Volume down button. Then press Power button once more to enter “fastboot” mode. You should see the image flashing now. Just reboot after that.
I'm trying to flash a zImage and I first got this error with the 0.97 bootloader
Code:
writing 'zImage'... FAILED (remote: not allowed)
And with the eng bootloader the error says
Code:
writing 'zImage'... FAILED (remote: unknown fail)
Anybody have any ideas to fix this? I searched for a while and turned up nothing.
do you have eng .76 bootloader? it is the one needed for clockworkmod. also, instead of the second zimage, type the name of your file. are you on a mac or a pc? if you are on a mac, you will need the mac fastboot file. pm me if you need it.
dkdude36 said:
do you have eng .76 bootloader? it is the one needed for clockworkmod. also, instead of the second zimage, type the name of your file. are you on a mac or a pc? if you are on a mac, you will need the mac fastboot file. pm me if you need it.
Click to expand...
Click to collapse
I flashed the eng bootloader and that's when I started getting the "remote: unknown fail" error when trying to flashe the zimage.
The file IS named zImage so that's right.
Plot thickens- now it will only boot into fastboot. I tried restoring my nandroid and it will still only boot into fastboot. I can get into the bootloader and recovery no problem but the phone reboots into fastboot every time.
I tried to flash a stock PC36IMG file and during the install process next to boot it says Fail-PU.
Now it says "Partition update fail!"
Please tell me I didn't just brick my phone.
EDIT: Ok, I flashed the PC36IMG file again and now it's booting again. My question is this- is the kernel stored on the boot partition? Would wiping the boot partiton and then flashing the zImage work? What commands would I use to do that?
http://tinypic.com/r/2q9ifir/7
dont know what to do...
Replay
MishXT said:
****tinypic****/r/2q9ifir/7
dont know what to do...
Click to expand...
Click to collapse
I am a ubuntu user,
but you need root permissions,
Try what you get when you type : fastboot devices
When you get an error with no permissions. Get root acces (in ubuntu sudo -s)
try export the fastboot directory path and run fastboot devices again.
Then when that is working, try your thing again. There will be no errors
Murakuchi said:
I am a ubuntu user,
but you need root permissions,
Try what you get when you type : fastboot devices
When you get an error with no permissions. Get root acces (in ubuntu sudo -s)
try export the fastboot directory path and run fastboot devices again.
Then when that is working, try your thing again. There will be no errors
Click to expand...
Click to collapse
I'm pretty sure he figured this out already as his question is close to 2 years old.
Evilone69tmg said:
I'm pretty sure he figured this out already as his question is close to 2 years old.
Click to expand...
Click to collapse
+1 lolz
HipKat said:
+1 lolz
Click to expand...
Click to collapse
haha bless him he actually thought he was helping rofl hehe xx
KernelDev101 said:
haha bless him he actually thought he was helping rofl hehe xx
Click to expand...
Click to collapse
Hello, another post added to a year old thread.
I am getting trouble trying to flash a custom compiled HTC amaze x715e. (unbranded, S-off, unlocked, SuperCID)
I cross-compiled the kernel source and now have the zImage in my /arch/arm/boot folder.
fastboot flash zimage zImage
results in 'FAILED (remote: not allowed)'
fastboot boot zImage
results in 'FAILED (remote: reproduce boot image with on-flash ramdisk error)'
How am I suppose to flash this?
Is there a thread for this?
Thanks in advance.
Disclaimer :
Code:
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Your warranty will be void if you tamper with any part of your device / software.
Download :
OnePlus7TOxygen_14.I.05_OTA_fastboot
Code:
ro.vendor.build.date=Wed Sep 25 21:54:29 CST 2019
ro.vendor.build.date.utc=1569419669
ro.vendor.build.fingerprint=OnePlus/OnePlus7T/OnePlus7T:10/QKQ1.190716.003/1909250940:user/release-keys
ro.vendor.build.id=QKQ1.190716.003
ro.vendor.build.tags=release-keys
ro.vendor.build.type=user
ro.vendor.build.version.incremental=1909250940
ro.vendor.build.version.release=10
ro.vendor.build.version.sdk=29
ro.product.vendor.brand=OnePlus
ro.product.vendor.device=OnePlus7T
ro.product.vendor.manufacturer=OnePlus
ro.product.vendor.name=OnePlus7T
Fastboot Commands :
Code:
fastboot flash aop_a aop.img
fastboot flash aop_b aop.img
fastboot flash bluetooth_a bluetooth.img
fastboot flash bluetooth_b bluetooth.img
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash dsp_a dsp.img
fastboot flash dsp_b dsp.img
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
fastboot flash logo_a logo.img
fastboot flash logo_b logo.img
fastboot flash modem_a modem.img
fastboot flash modem_b modem.img
fastboot flash oem_stanvbk oem_stanvbk.img
fastboot flash qupfw_a qupfw.img
fastboot flash qupfw_b qupfw.img
fastboot flash storsec_a storsec.img
fastboot flash storsec_b storsec.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
Credits :
jamflux
Regards,
acervenky
reserved
Thanks very much for this.
.
Is there any solution for root ?
I am not able to root using magisk patched boot.img
.
Magisk beta stucking at bootloader warning info at boot.
Magisk canary giving Qualcomm crash dump error on boot.
RohanAJoshi said:
Thanks very much for this.
.
Is there any solution for root ?
I am not able to root using magisk patched boot.img
.
Magisk beta stucking at bootloader warning info at boot.
Magisk canary giving Qualcomm crash dump error on boot.
Click to expand...
Click to collapse
Download the attachment, and flash it using this command :
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
This should help you with the image patched using beta.
Regards,
acervenky
acervenky said:
Download the attachment, and flash it using this command :
This should help you with the image patched using beta.
Regards,
acervenky
Click to expand...
Click to collapse
OK, I will try this and report you back soon.
acervenky said:
Download the attachment, and flash it using this command :
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
This should help you with the image patched using beta.
Regards,
acervenky
Click to expand...
Click to collapse
tried this, not working.
same as before, with magisk beta patched, phone stuck at bootloader unlock warning.
.
steps i did
flashed vbmeta as you said.
flashed patched boot.
reboot.
.
my doubt is :
in your fist post, for plashing vbmeta, you used _a & _b
but in this command, its only vbemeta, not a or b
RohanAJoshi said:
tried this, not working.
same as before, with magisk beta patched, phone stuck at bootloader unlock warning.
.
steps i did
flashed vbmeta as you said.
flashed patched boot.
reboot.
.
my doubt is :
in your fist post, for plashing vbmeta, you used _a & _b
but in this command, its only vbemeta, not a or b
Click to expand...
Click to collapse
Managed to compile a kernel with avb flag disabled and vbmeta removed, download it from this link, please note that they're unpatched and there may be bugs if oneplus messed up something in the source code.
Please patch it with beta and canary, report if it works!
Regards,
acervenky
acervenky said:
Managed to compile a kernel with avb flag disabled and vbmeta removed, download it from this link, please note that they're unpatched and there may be bugs if oneplus messed up something in the source code.
Please patch it with beta and canary, report if it works!
Regards,
acervenky
Click to expand...
Click to collapse
which file should i dowload ?
stock or mod ?
RohanAJoshi said:
which file should i dowload ?
stock or mod ?
Click to expand...
Click to collapse
Mod, I've uploaded the stock incase you face any problems and need to revert!
Regards,
acervenky
acervenky said:
Mod, I've uploaded the stock incase you face any problems and need to revert!
Regards,
acervenky
Click to expand...
Click to collapse
that mod.img is going through bootloader warning screen, its boot looping further on boot animation.
did not tried patched magisk of mod file.
I thought 1st try plain if it booting or not, if not booting clean file, magisk mod wont boot.
RohanAJoshi said:
that mod.img is going through bootloader warning screen, its boot looping further on boot animation.
did not tried patched magisk of mod file.
I thought 1st try plain if it booting or not, if not booting clean file, magisk mod wont boot.
Click to expand...
Click to collapse
Same issue here, the mod.img file bootloops after warning of bootloader. Please help! The stock image brings me back to the qualcomm crashdump mode.
Another issue, while flashing the fastboot images initially, for system and vendor files, the following was displayed.
“Invalid sparse file format at header magi
sending sparse system_a (775469 KB)...
OKAY [ 17.955s]
writing ‘system_a’...
FAILED (remote: Partition not found)
finished. total time: 17.971s”
The same displays for system_b, vendor_a and vendor_b. I’ve tried SYSTEM_a, System_a, System_A, SYSTEM_A but to no avail. Do you think this might be the cause of the Qualcomm crash dump mode?
How2Kritin said:
Same issue here, the mod.img file bootloops after warning of bootloader. Please help! The stock image brings me back to the qualcomm crashdump mode.
Another issue, while flashing the fastboot images initially, for system and vendor files, the following was displayed.
“Invalid sparse file format at header magi
sending sparse system_a (775469 KB)...
OKAY [ 17.955s]
writing ‘system_a’...
FAILED (remote: Partition not found)
finished. total time: 17.971s”
The same displays for system_b, vendor_a and vendor_b. I’ve tried SYSTEM_a, System_a, System_A, SYSTEM_A but to no avail. Do you think this might be the cause of the Qualcomm crash dump mode?
Click to expand...
Click to collapse
It's not possible to flash it properly
Read the following reply from @mauronofrio
"actually is not possible, the oneplus 7t is using the new /super partition and on op7t is not possible to flash a full stock rom from fastboot, but you can flash all partitions except system, vendor, product (The 3 partitions that contains the rom), he should boot in twrp to try to restore his device, maybe i can help a bit, but it's something really new and i think the oneplus 7t is the first one that is supporting this"
cultofluna said:
It's not possible to flash it properly
Read the following reply from @mauronofrio
"actually is not possible, the oneplus 7t is using the new /super partition and on op7t is not possible to flash a full stock rom from fastboot, but you can flash all partitions except system, vendor, product (The 3 partitions that contains the rom), he should boot in twrp to try to restore his device, maybe i can help a bit, but it's something really new and i think the oneplus 7t is the first one that is supporting this"
Click to expand...
Click to collapse
Interesting! So the backup and restore vendor, system won't work via twrp?
Anyone tried manually flashing Magisk via twrp?
Regards,
acervenky
acervenky said:
Interesting! So the backup and restore vendor, system won't work via twrp?
Anyone tried manually flashing Magisk via twrp?
Regards,
acervenky
Click to expand...
Click to collapse
I did, initially but it said that the /system, /vendor and /product partitions couldn’t be mounted. When I tried to restore I got stuck in the fastboot mode. After that, I’ve used your file and got stuck with the qualcomm crashdump mode.
FIXED
Final update: Mauronofrio has helped me out and fixed everything for me, a huge thanks to him. My device is in perfect condition now. Thanks a lot to everyone who tried to help too!
I wonder, if a T-Mobile 7T is unlocked can we use this method to install the international firmware on it?
Is this for EU Model?
Hot-Proton said:
Is this for EU Model?
Click to expand...
Click to collapse
No, Global!
Regards,
acervenky
Ok that is bad. Wait for EU Version.
for T-Mobile no, I messed up mine, it boots but no wifi and data. I did a remote session with oneplus but they can't fix it, they don't have the firmware for the tmobile version, unless if someone has already patched the MSM, but sadly nothing yet
---------- Post added at 07:50 AM ---------- Previous post was at 07:48 AM ----------
How2Kritin said:
Final update: Mauronofrio has helped me out and fixed everything for me, a huge thanks to him. My device is in perfect condition now. Thanks a lot to everyone who tried to help too!
Click to expand...
Click to collapse
how did you reach out to him, just wanna know if there's a fix for my wifi and data no connections, T-Mobile unlock bootloader, tried flashing the modem from here but no effect and when I tried deleting it, sim card cannot be detected
This step work on my devices firmware version RMX2180_11_A_85
file boot.img and vbmeta.img inthis post
how to ubl
instal IndepthTest-C11-C12-C15 and open
click start and wait for it to appear start in the depth test and click
on fastboot mode open cmd
fastboot flashing unlock (enter)
fastboot reboot (enter) press vol up or down for unlock bootloader
how to root
click install in magisk manager select patch file point to the original boot file
the boot patch file is in the download folder
copy file boot patch & vbmeta img to folder flatfrom adb
go to fastboot mode
adb reboot bootloader (enter)
fastboot flash boot magisk_patched.img (enter)
fastboot -–disable-verity -–disable-verification flash vbmeta vbmeta.img (enter)
fastboot reboot (enter)
Work at my c12 l, but use platform tool
rudiyansahreder said:
Work at my c12 l, but use platform tool
Click to expand...
Click to collapse
Thanks for report ,,work UBl and root ,,
mine doesnt say magisk_patched.img when i install magisk into the boot.img what will i do?
wakohoxi said:
mine doesnt say magisk_patched.img when i install magisk into the boot.img what will i do?
Click to expand...
Click to collapse
Check in the download folder to the patch img file
Thanks
bass_deso said:
copy file boot patch & vbmeta img to folder flatfrom adb
Click to expand...
Click to collapse
that "flatfrom" is i.е. "root folder", right?..
Does this really work on realme c15? I have installed the in-deph test application but the application always exits
Maaf sebelumnya.
cara mendapatkan stock boot.img gmn? Lupa back up.. terus udh ganti costom rom.. bootloop
apps dont work on c15, crashes each load
Baik sekali
Minta rooter
hello i have big problem.
i unlocked bootloader with command fastboot flashing unlock / the show me unlock bootloader / Write YES
unlocked done, after unlock bootloader wipe data.
Then i try install custom TWRP..i download latest TWRP,then restart mobile to fastboot ..fastboot devices show me device,and i try
fastboot flash recovery recovery.img (show mi Failed remote: (recovery_a) No such partition
so next i try next commands:
fastboot getvar current-slot
fastboot set_active other
fastboot flash boot recovery.img /done
everithing see normally done without any problems.
Reboot phone and there its,,reboot in to fastboot. Mobile not starting im stuck in fastboot.
Can you help me please?
Merlousek said:
hello i have big problem.
i unlocked bootloader with command fastboot flashing unlock / the show me unlock bootloader / Write YES
unlocked done, after unlock bootloader wipe data.
Then i try install custom TWRP..i download latest TWRP,then restart mobile to fastboot ..fastboot devices show me device,and i try
fastboot flash recovery recovery.img (show mi Failed remote: (recovery_a) No such partition
so next i try next commands:
fastboot getvar current-slot
fastboot set_active other
fastboot flash boot recovery.img /done
everithing see normally done without any problems.
Reboot phone and there its,,reboot in to fastboot. Mobile not starting im stuck in fastboot.
Can you help me please?
Click to expand...
Click to collapse
In other Treble (a/b slots) based phones, the recovery is built into the boot rom. Likely you will need to re-flash the boot.img. That's what I would try first.
numbawon said:
In other Treble (a/b slots) based phones, the recovery is built into the boot rom. Likely you will need to re-flash the boot.img. That's what I would try first.
Click to expand...
Click to collapse
so what can i do? i dont have stock recovery,and twrp recovery dont start, what fastboot command can i try to repair? only what i have its global rom downloaded from nubia homepage but i dont now how to flash stock rom and repair all this i try miflash tool,but mi flash tool not support zip formats
You are going to need extract the global rom
Follow these instructions
Extract Android OTA Payload.bin File using Payload Dumper Tool
Learn how to dump and extract Android OTA Payload.bin file to get the boot.img (for rooting with Magisk), vendor.img, and other other partition images.
www.thecustomdroid.com
Once extracted, you should then be able to fastboot flash boot_(a or b) boot.img
numbawon said:
You are going to need extract the global rom
Follow these instructions
Extract Android OTA Payload.bin File using Payload Dumper Tool
Learn how to dump and extract Android OTA Payload.bin file to get the boot.img (for rooting with Magisk), vendor.img, and other other partition images.
www.thecustomdroid.com
Once extracted, you should then be able to fastboot flash boot_(a or b) boot.img
Click to expand...
Click to collapse
okey,,its look so verry hard for me so only way for me its wait for nubia unbrick tool for Red magic 6 like unbrick tool for red magic 5.
Merlousek said:
okey,,its look so verry hard for me so only way for me its wait for nubia unbrick tool for Red magic 6 like unbrick tool for red magic 5.
Click to expand...
Click to collapse
Several of us are in the waiting game for the unbrick tool at this point.
i try bumper what you send me but another im stuck here
Merlousek said:
i try bumper what you send me but another im stuck here
Click to expand...
Click to collapse
I'll see if I can get it all extracted for you and post it someplace. I've not done it myself, I just knew where the information was.
can do for me anybody download official rom V312 https://help.redmagic.gg/hc/en-us/articles/900006829463-RedMagic-6
and extract payload.bin via payload bumper all files and reupload for me please?
i need it for flash stock room via MIflash
Thanks for help.
Merlousek said:
can do for me anybody download official rom V312 https://help.redmagic.gg/hc/en-us/articles/900006829463-RedMagic-6
and extract payload.bin via payload bumper all files and reupload for me please?
i need it for flash stock room via MIflash
Thanks for help.
Click to expand...
Click to collapse
RedMagic6-6pro - Google Drive
drive.google.com
I've extracted both versions of the rom. The "output" folder in their respective paths contains all the extracted img files. All files are included for completeness.
numbawon said:
RedMagic6-6pro - Google Drive
drive.google.com
I've extracted both versions of the rom. The "output" folder in their respective paths contains all the extracted img files. All files are included for completeness.
Click to expand...
Click to collapse
thank you so much,and i have last question,,i try flash it with miflash,,boot on edl,i see device but mi flash say couldnt find flash script,, so what program use for flashing all files?
Merlousek said:
thank you so much,and i have last question,,i try flash it with miflash,,boot on edl,i see device but mi flash say couldnt find flash script,, so what program use for flashing all files?
Click to expand...
Click to collapse
Just use fastboot. Forget mi tool.
bs3pro said:
Just use fastboot. Forget mi tool.
Click to expand...
Click to collapse
what? fastboot? i have extracted all files from phyton like boot.img , system.img ... and what fastboot do you means?
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
you mean this fastboot commands?
and flash all files from stock recovery in fastboot?
bs3pro said:
Just use fastboot. Forget mi tool.
Click to expand...
Click to collapse
what? fastboot? i have extracted all files from phyton like boot.img , system.img ... and what fastboot do youmeans?
fastboot flash system system.img
fastboot flash recovery recovery.img
like that?
another error when i try flash all files from fastboot
Thanks..i try this commands on screenshot in previous reply sometimes error but fastboot flash boot boot.img works and my nubia red magic 6 its on ALIVE..Thanks all for help, You are best.
Merlousek said:
Thanks..i try this commands on screenshot in previous reply sometimes error but fastboot flash boot boot.img works and my nubia red magic 6 its on ALIVE..Thanks all for help, You are best.
Click to expand...
Click to collapse
Nice job!
Merlousek said:
hello i have big problem.
i unlocked bootloader with command fastboot flashing unlock / the show me unlock bootloader / Write YES
unlocked done, after unlock bootloader wipe data.
Then i try install custom TWRP..i download latest TWRP,then restart mobile to fastboot ..fastboot devices show me device,and i try
fastboot flash recovery recovery.img (show mi Failed remote: (recovery_a) No such partition
so next i try next commands:
fastboot getvar current-slot
fastboot set_active other
fastboot flash boot recovery.img /done
everithing see normally done without any problems.
Reboot phone and there its,,reboot in to fastboot. Mobile not starting im stuck in fastboot.
Can you help me please?
Click to expand...
Click to collapse
What TWRP did you install? Make sure you're downloading a TWRP that's available for this device. So far, to my knowledge, there isn't a TWRP recovery for this device yet.
Hello there, how did u just unlock bootloader by fastboot command? didn't use OEM unlock option on dev setting?
Btw can you share me your twrp that you used?
I need it so badly my rom bugged stuck at google account setup
I was rooted with Magisk 25.2 fine. I followed the OTA update intructions (uninstall, update, install to the other partition etc). When Magisk rebooted my phone I got a messae that says
QUALCOM CrashDump Mode
-------------------------------
dm-verity device corrupted
verity_ctr
I can reboot back into my other partition, and I have a version of the OS that's pre-OTA, but I've lost root there. I can switch between partitions and go from the Qualcom CrashDump to my working non-rooted OS.
How do I get from either of these places to a rooted version of the OTA update?
I'd suggest waiting for the next OTA and do it again.
However, I don't understand why you did the uninstall, update, install to the other partition etc part. I usually just do the following steps:
Install OTA (do NOT reboot yet)
Install Magisk in the other partition
Reboot
So far it has worked for me for each update.
Ecna said:
I was rooted with Magisk 25.2 fine. I followed the OTA update intructions (uninstall, update, install to the other partition etc). When Magisk rebooted my phone I got a messae that says
QUALCOM CrashDump Mode
-------------------------------
dm-verity device corrupted
verity_ctr
I can reboot back into my other partition, and I have a version of the OS that's pre-OTA, but I've lost root there. I can switch between partitions and go from the Qualcom CrashDump to my working non-rooted OS.
How do I get from either of these places to a rooted version of the OTA update?
Click to expand...
Click to collapse
You may be able to copy your good partitions (a or b, whichever works) to the other one. So they'll both be loaded with working stock firmware. Then take the OTA and drop in a magisk patched boot image after OTA is good
Appreciative said:
You may be able to copy your good partitions (a or b, whichever works) to the other one. So they'll both be loaded with working stock firmware. Then take the OTA and drop in a magisk patched boot image after OTA is good
Click to expand...
Click to collapse
How would I copy my good partition to the broken one?
viktak said:
I'd suggest waiting for the next OTA and do it again.
Click to expand...
Click to collapse
The current OTA is still pending, and I don't have root anymore, so waiting won't get me anywhere.
However, I don't understand why you did the uninstall, update, install to the other partition etc part.
Click to expand...
Click to collapse
I just followed the Magisk instructions here:
https://topjohnwu.github.io/Magisk/ota.html
Ecna said:
How would I copy my good partition to the broken one?
Click to expand...
Click to collapse
While on Slot_A Flash copypartitions.zip??
Sorry for the noob question but how do I do "While on Slot_A Flash copypartitions.zip" I cant find the copypartitions.zip please help thanks
forum.xda-developers.com
[SLOT A/B devices] Universal A/B-cloner
I DO NOT TAKE RESPONSIBILITY FOR YOUR DEVICE BREAKING THIS /WILL/ COPY YOUR BOOTLOADER FROM ONE SLOT TO ANOTHER IF YOU DO THAT WITH A BOOTLOADER THAT IS OLDER THAN THE SLOT YOURE OVERWRITING YOUR DEVICE MIGHT BRICK Ok, thats over with INFO...
forum.xda-developers.com
Something like these, or manually. Be sure to figure out which partition (a or b) is currently good and working so you don't copy the wrong way. If you do copy the wrong direction, you may have to msm
Appreciative said:
While on Slot_A Flash copypartitions.zip??
Sorry for the noob question but how do I do "While on Slot_A Flash copypartitions.zip" I cant find the copypartitions.zip please help thanks
forum.xda-developers.com
[SLOT A/B devices] Universal A/B-cloner
I DO NOT TAKE RESPONSIBILITY FOR YOUR DEVICE BREAKING THIS /WILL/ COPY YOUR BOOTLOADER FROM ONE SLOT TO ANOTHER IF YOU DO THAT WITH A BOOTLOADER THAT IS OLDER THAN THE SLOT YOURE OVERWRITING YOUR DEVICE MIGHT BRICK Ok, thats over with INFO...
forum.xda-developers.com
Something like these, or manually. Be sure to figure out which partition (a or b) is currently good and working so you don't copy the wrong way. If you do copy the wrong direction, you may have to msm
Click to expand...
Click to collapse
Thank you, I'll dig into these links!
I got similar problem, solved by disabling dm-verify manually. You can try extract vbmeta.img from rom package using payload_dumper, then use fastboot to disable dm-verify.
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
I'm having this same problem, but to fix it I need to switch back to the "good" slot and boot my phone normally to fix it. However after booting my phone into fastboot, I'm unable to run the appropriate command:
Code:
fastboot --set-active=a
fastboot: unknown option -- set-active=a
Do I have the wrong version of fastboot installed on my PC? How can the rest of fastboot work but not this specific command?
sumfahg said:
I'm having this same problem, but to fix it I need to switch back to the "good" slot and boot my phone normally to fix it. However after booting my phone into fastboot, I'm unable to run the appropriate command:
Code:
fastboot --set-active=a
fastboot: unknown option -- set-active=a
Do I have the wrong version of fastboot installed on my PC? How can the rest of fastboot work but not this specific command?
Click to expand...
Click to collapse
Make sure you have the latest full platform tools and not the minimum platform tools, or if you are on a windows PC try the fastboot enhanced version
TheGhost1951 said:
Make sure you have the latest full platform tools and not the minimum platform tools, or if you are on a windows PC try the fastboot enhanced version
Click to expand...
Click to collapse
I am on Windows, where can I download fastboot enhanced?
sumfahg said:
I am on Windows, where can I download fastboot enhanced?
Click to expand...
Click to collapse
There is an xda threads on it. Just search xda forums for fastboot enhanced.
sumfahg said:
I am on Windows, where can I download fastboot enhanced?
Click to expand...
Click to collapse
You could try:
fastboot set_active other
Or
fastboot set_active a
Or
fastboot -a (this is in the documentation but I have never tried it, nor see it online often)
zjhjack123 said:
I got similar problem, solved by disabling dm-verify manually. You can try extract vbmeta.img from rom package using payload_dumper, then use fastboot to disable dm-verify.
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
Spent some time trying to do this. fastboot said Rewriting, Sending, writing, Finished. All OKAY. No error messages in there. But when I rebooted into the other partition I got the same dm-verity crash dump.
Ecna said:
Spent some time trying to do this. fastboot said Rewriting, Sending, writing, Finished. All OKAY. No error messages in there. But when I rebooted into the other partition I got the same dm-verity crash dump.
Click to expand...
Click to collapse
I dug a bit further and tried these as well:
Code:
fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system_a vbmeta_system.img
fastboot --disable-verity --disable-verification flash vbmeta_vendor_a vbmeta_vendor.img
Whenever I try to boot to the a partition, I just loop back into fastboot mode. The b partition still works though.
Appreciative said:
You could try:
fastboot set_active other
Or
fastboot set_active a
Or
fastboot -a (this is in the documentation but I have never tried it, nor see it online often)
Click to expand...
Click to collapse
Fastboot --set-active=a or b which ever you need in bootloader mode
Ecna said:
I dug a bit further and tried these as well:
Code:
fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system_a vbmeta_system.img
fastboot --disable-verity --disable-verification flash vbmeta_vendor_a vbmeta_vendor.img
Whenever I try to boot to the a partition, I just loop back into fastboot mode. The b partition still works though.
Click to expand...
Click to collapse
Maybe you could try set-active a (if a slot is the bad rom) first, reboot into fastboot again and then use fastboot to flash vbmeta with disable verity parameter.
Or you could try to boot into good rom, and flash full update package using local update instead of ota, then see if it can boot into updated rom.
zjhjack123 said:
Maybe you could try set-active a (if a slot is the bad rom) first, reboot into fastboot again and then use fastboot to flash vbmeta with disable verity parameter.
Or you could try to boot into good rom, and flash full update package using local update instead of ota, then see if it can boot into updated rom.
Click to expand...
Click to collapse
I did switch the active slot to a, just cause that seemed like a good idea.
How do I only flash the update package to the A slot? I thought it went to both by default?
Ecna said:
I did switch the active slot to a, just cause that seemed like a good idea.
How do I only flash the update package to the A slot? I thought it went to both by default?
Click to expand...
Click to collapse
When you flash tom in the system, it only update the firmware in another slot. So if your current good rom is in slot b, you can just boot into slot b and apply system update via local update, the updated rom will be in slot a.
Ecna said:
I did switch the active slot to a, just cause that seemed like a good idea.
How do I only flash the update package to the A slot? I thought it went to both by default?
Click to expand...
Click to collapse
If you have the images:
fastboot flash system_a system_a.img
fastboot flash system_b system_b.img
it's also possible to pull the whole partitions down with msm tool (press f8, select partitions and readback, files go to c:\) or using dd.
If not, #19 above