*removed*
Is there a way to to this with the boot, system, product and vbmeta images from custom roms?
Ljrouse5 said:
Is there a way to to this with the boot, system, product and vbmeta images from custom roms?
Click to expand...
Click to collapse
Yes, see this post for how to make a custom super image:
https://forum.xda-developers.com/showpost.php?p=83706419&postcount=152
You can use the attachment in this op as an example/template to make your own flashable package.
Check out the updater-script; very simple syntax for writing images.
Updated the OP with link to SAFE fastboot flashable that does NOT write gpt and bootloader, so it is safe to flash on any Sofia variant. Flashing the bootloader zip is DANGEROUS, and should be flashed only over the SAME or OLDER gpt and bootloader.
Now if you have TWRP installed, you can flash back and forth among stock and custom roms, without the need for a pc and fastboot.
Where's the file?
Related
Since pepole have no knolege of what they are doing and kind of blame me for it i will not provide the images anymore.
Please lock this thread.
First, woohoo!
Flashing now, thanks bud!
EDIT: Hey Bunny, maybe I'm missing something. Where are those bootloader images available?
@bunny0007 is this pre-rooted, or stock ?
All the bootloader files are in the ota file.
Yes this is stock system partition with root.
bunny0007 said:
All the bootloader files are in the ota file.
Yes this is stock system partition with root.
Click to expand...
Click to collapse
So then this point is moot then?
"...Since the 5.0.2 update contains new bootloader and stuff, you might have to flash those if neccesary...." it happens automatically when you do the single system flash?
---------- Post added at 06:24 PM ---------- Previous post was at 06:18 PM ----------
Is there a mirror link? Dev-Host seems to have been jacked by some crazy redirect malware...or maybe its just me...
Moe5508 said:
So then this point is moot then?
"...Since the 5.0.2 update contains new bootloader and stuff, you might have to flash those if neccesary...." it happens automatically when you do the single system flash?
---------- Post added at 06:24 PM ---------- Previous post was at 06:18 PM ----------
Is there a mirror link? Dev-Host seems to have been jacked by some crazy redirect malware...or maybe its just me...
Click to expand...
Click to collapse
I flashed the ota file before i made the system dump.
Im not sure if the new bootloader an stuff are required for this update, but the ota are not a new rom, just patched files, no new boot image or recovery image.
Am stuck in fastboot mode and can't get into ADB mode anymore to be able to do a sideload...any idea how to flash that OTA zip file in fastboot? Anyone got the boot and recovery images extracted?
Moe5508 said:
Am stuck in fastboot mode and can't get into ADB mode anymore to be able to do a sideload...any idea how to flash that OTA zip file in fastboot? Anyone got the boot and recovery images extracted?
Click to expand...
Click to collapse
The only way to flash the ota file are from stock non rooted 5.0.1 via sideload from recovery.
You might fastboot flash stock 5.0.1 system, boot and recovery, then you shuld be able to flash the ota from recovery.
bunny0007 said:
Here is a stock lollipop 5.0.2 system image that can be flashed in fastboot.
Flash with
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system-rooted.img
Stock 5.0.2 boot partition dump download (sorry for the partiton size): http://www68.zippyshare.com/v/4v4NAT5J/file.html
Stock 5.0.2 recovery partition dump download (sorry for the partiton size): http://www3.zippyshare.com/v/hpeV5W22/file.html
Stock 5.0.2 System rooted: http://d-h.st/IGov
Smaller 5.0.2 boot.img and recovery.img might fe found here http://forum.xda-developers.com/g-watch-r/development/stock-boot-recovery-g-watch-r-t2956964
Since the 5.0.2 update contains new bootloader and stuff, you might have to flash those if nessesary.
Extract the files and use the flash cmd file from windows cmd, or flash the files manually with fastboot.
bootloader.aboot.img
bootloader.imgdata.img
bootloader.rpm.img
bootloader.sbl1.img
bootloader.sdi.img
bootloader.tz.img
Download Bootloader Stuff : http://d-h.st/bDXl
Click to expand...
Click to collapse
Thanks for the bootloader stuff.But in flash.cmd.It should "fastboot flash sbl1 bootloader.sbl1.img"rather than "sb11".you can change it.then everyone can flash the newest sbl1
akaHardison said:
Thanks for the bootloader stuff.But in flash.cmd.It should "fastboot flash sbl1 bootloader.sbl1.img"rather than "sb11".you can change it.then everyone can flash the newest sbl1
Click to expand...
Click to collapse
I just caught that, too. sb11 should read "sbl1" (SBL1) in the commands list when flashing the "bootloader stuff", otherwise you'll get an error that sb11 partition does not exist.
fronc said:
I just caught that, too. sb11 should read "sbl1" (SBL1) in the commands list when flashing the "bootloader stuff", otherwise you'll get an error that sb11 partition does not exist.
Click to expand...
Click to collapse
yep have changed the error in new zip
@bunny0007 can you please post a step by step guide for how to flash this?
I am on rooted 5.0.1 and do not understand the order, or not even which imgs are necessary to flash?
you reboot to bootloader mode, flash boot/system/recovery and also dl his bootloader stuff and flash all of those (he included a .cmd with all the fastboot commands)
bunny0007 said:
Here is a stock lollipop 5.0.2 system image that can be flashed in fastboot.
Flash with
fastboot flash system system-rooted.img
Stock 5.0.2 System rooted: http://d-h.st/IGov
Click to expand...
Click to collapse
When I go to the devHost to download this system, I hit the "download" button and it takes me to spam where it asks me to download a 1-MB file that is called system-rooted.img.zip.exe.
Is the link bad, or am I just being a noob? I'm expecting a 256 MB img file with the stock 5.02 system rooted, not a 1 MB executable file with a deceptive name.
Any assistance appreciated.
Cheers,
B.D.
BostonDan said:
When I go to the devHost to download this system, I hit the "download" button and it takes me to spam where it asks me to download a 1-MB file that is called system-rooted.img.zip.exe.
Is the link bad, or am I just being a noob? I'm expecting a 256 MB img file with the stock 5.02 system rooted, not a 1 MB executable file with a deceptive name.
Any assistance appreciated.
Cheers,
B.D.
Click to expand...
Click to collapse
Just uncheck the "Download with Dev-Host Download Manager" box.
Spleeno said:
you reboot to bootloader mode, flash boot/system/recovery and also dl his bootloader stuff and flash all of those (he included a .cmd with all the fastboot commands)
Click to expand...
Click to collapse
hey, so boot then system and then recovery, followed by the bootloader stuff, in this order, right?
b0gd4n said:
hey, so boot then system and then recovery, followed by the bootloader stuff, in this order, right?
Click to expand...
Click to collapse
Boot into fastboot, then make sure you can use fastboot from windows in cmd shell.
Then use this to flash
1. Unzip and flash bootloader stuff with cmd file.
2. Flash system with "fastboot flash system filename.img"
3. Flash boot with "fastboot flash boot boot.img"
4. Flash Stock 5.0.2 recovery with "fastboot flash recovery recovery.img"
5. Reboot the watch
Is there coming a stock rooted 5.1.1?
TimV_ said:
Is there coming a stock rooted 5.1.1?
Click to expand...
Click to collapse
Yep here http://forum.xda-developers.com/g-watch-r/development/rom-stock-rooted-5-1-1-t3124921
How do you come around to get the watch listed in adb (adb devices command). I installed several drivers for my lg g watch r, tried both in win10 test and non test mode, but the watch is not recognized. DEvice manager lists it as "unknown usb device descriptor request failed".
I appreciate any type of suggestion. Thanks in advance!
Requirements:
you need to have a pc with adb working
a stock firmware on your device (any)
unlocked bootloader
a working backup just in case
Pro:
you will not lose your data / application
Cons:
you will lose all system modification (root, busybox, custom kernel...)
you'll take all the risk of operation (I've tested on my device)
Guide:
some file names changes depending on version so please complete the {version_here} placeholder with the file you download
* prepend "sudo" on command line if you are on a Linux machine
download last version for your device here (if you want to root download the zip file in the section below to speed up the operations)
extract
extract image-{device_here}-{version_here}.zip in the same folder (no subdir)
command line* (or reboot device with vol down pressed):
Code:
adb reboot bootloader
command line*:
Code:
cd {your_path_here}
command line*:
Code:
fastboot flash bootloader bootloader-{device_here}-{version_here}.img
command line*:
Code:
fastboot reboot-bootloader
command line*:
Code:
fastboot flash radio radio-{device_here}-{version_here}.img
command line*:
Code:
fastboot flash system system.img
command line*:
Code:
fastboot flash boot boot.img
ONLY IF YOU FOUND A VENDOR.IMG IN THE ZIP command line*:
Code:
fastboot flash vendor vendor.img
command line*:
Code:
fastboot flash cache cache.img
command line*:
Code:
fastboot reboot
Now you have the lastest stock image and all your data.
Change recovery (TWRP) and root:
Note that we haven't flash the stock recovery, but during every boot of an unmodified system there's a script that do that (supersu usually deactive this behavior during install).
If you had TWRP installed and the SuperSU zip on your device, at the end of the above procedure you can boot directly from bootloader to recovery and go directly to last step:
download: TWRP image (twrp-{version_here}-{device_here}.img) for your device
download: chainfire SuperSU 2.71 on your device
command line*:
Code:
fastboot flash recovery twrp-{version_here}-{device_here}.img
alternatively you can keep the original recovery and use TWRP one time with
Code:
fastboot boot twrp-{version_here}-{device_here}.img
boot in recovery and flash supersu zip
working fine for me, all correct, thanks
Just tried with flash_all.bat. I'm getting the message "Can not generate image". How can I solve this, please?
Thank you, works like a charm!
Same here, cant flash system
There's not flash-all.bat in my steps (that delete you data!), can't give help about it sorry
i've gone your way, but i tried also the flash-all.bat with the -w switch, didnt work.
Tnx mate. Helped a lot
Cant flash the system.img manually. All the other img are working. I get this error message :
Code:
target reported max download size of 1073741824 bytes
error: cannot load 'system.img'
The old system.img from lrx22c works also.
Someone know whats going on?
Sp0KI said:
Cant flash the system.img manually. All the other img are working. I get this error message :
Code:
target reported max download size of 1073741824 bytes
error: cannot load 'system.img'
The old system.img from lrx22c works also.
Someone know whats going on?
Click to expand...
Click to collapse
I think that all who has flashed the developer preview got an broken filesystem or the partitions missmatch.
Before i used the preview the -w update flag worked well to rebuild the partitions, now it didnt work anymore, tried all factory images don to 4.4
c3k said:
Requirements:
you need to have a pc with adb working
a stock firmware on your device (any)
a working backup just in case
Click to expand...
Click to collapse
so if i have twrp, before i have to return stock 5.0.1??
or i flash directly 5.1 over twrp?
tnx
chikess said:
I think that all who has flashed the developer preview got an broken filesystem or the partitions missmatch.
Before i used the preview the -w update flag worked well to rebuild the partitions, now it didnt work anymore, tried all factory images don to 4.4
Click to expand...
Click to collapse
I didn't flash the preview.
Sp0KI said:
I didn't flash the preview.
Click to expand...
Click to collapse
Hmm ok, but u got the same problems. So, in this way we had to wait for a flashable zip or maybe ota.
@c3k why do you mention to flash twrp while in steps above stock recovery is not included to flash... ? Doesn't that mean that custom recovery (twrp) is still on device?
Doesn't this require an unlocked bootloader, and not necessarily root, or am I confused?
Sp0KI said:
Cant flash the system.img manually. All the other img are working. I get this error message :
Code:
target reported max download size of 1073741824 bytes
error: cannot load 'system.img'
The old system.img from lrx22c works also.
Someone know whats going on?
Click to expand...
Click to collapse
Are you using the latest version for the fastboot.exe file?
foosion said:
Doesn't this require an unlocked bootloader, and not necessarily root, or am I confused?
Click to expand...
Click to collapse
This requires an unlocked bootloader. But, there are users like us who have rooted the stock ROM.
This guide is meant for the users who has unlocked bootloader with rooted stock ROM.
This guide will also work for phones with unlocked bootloaders with STOCK ROM(rooted or un-rooted).
efrant said:
Are you using the latest version for the fastboot.exe file?
Click to expand...
Click to collapse
I had faced the same issue while flashing LRX22C. It got fixed by rebooting the phone and switching the cable to a different USB port. Might work for him too.
PS: I have flashed the images from Linux.
In my case I guess all the issues are from a previous attempt to flash OptiPop ROM. The flashing process it's a little tricky to understand (with that F2FS file system). I remember that after flashed OptiPop and the phone didn't boot, I tried to restore to stock ROM and it was a lot of errors until it worked fine again.
efrant said:
Are you using the latest version for the fastboot.exe file?
Click to expand...
Click to collapse
I'm using the newest Minimal ADB.
The strange thing is, that i can flash the LRX22C system.img and all other new lmy47d files but not the lmy47d system.img.
I guess i'll wait for the OTA update and hope it works then.
Tried rebooting and switching port and usb cabel..
You actually don't need to manually install supersu or root. Flash the 5.1 images and then (after the first full boot) flash twrp.
Once you boot into twrp and exit out of it, you will be promoted with a message that your phone is not rooted, and you're asked if you want to install supersu. It's built into twrp.
Current: Unlocked, Rooted, TWRP, Custom Rom 5.0.1, Custom Kernel, Encrypted
Goal: Unlocked, Rooted, TWRP, Factory 5.1.0, Custom Kernel, Decrypted
How do I go from my current state to my goal?
Would the following steps be correct and shortest?
1) Flash factory image - Flash All
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
2) Disable encryption - Flash kernel, disable + wipe
http://forum.xda-developers.com/nexus-6/development/disable-forced-encryption-gain-root-t2946715
3) Install Root - SuperSU
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
4) Install TWRP
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
5) Install Custom Kernel
Is step 2 in the correct order? Do I perform the install and disable to eliminate all traces of decryption?
Step 5, do I flash the kernel via TWRP or use the kernel's app from the Google Store?
Bump
I was Stock 5.01. except rooted and decrypted.
Copied SuperSU.zip to my Nexus 6.
had all the .img files extracted and in the same folder as my fastboot.exe from the Android SDK (make sure you are at the latest).
Boot to bootloader.
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.08.img
fastboot reboot-bootloader
fastboot flash radio radio-shamu-d4.0-9625-02.95.img
fastboot reboot-bootloader
Using a decrypted flagged 5.1 boot.img
fastboot flash boot de-cryptedboot.img
fastboot flash system system.img
fastboot flash cache cache.img
I reflashed twrp as well...couldn't remember if I had left it on or had flash to stock recovery after rooting.
fastboot flash recovery twrp-2.8.5.0.img
When that finished flashing I used the volume keys to move to "boot recovery" and pressed power.
Team Win Recovery came up and I installed SuperSU.zip
Rebooted...done. 5.1, unencrypted, rooted and kept all my data.
Where did you get the decrypted boot img from?
From this thread.
http://forum.xda-developers.com/showthread.php?t=2946715
does the ota zip file contain all the .img files.............
it looks like it does, but there not all named in the normal fashion..........
can this be clarified.......
what files are what?
They are all there. Bootloader and the radio are in the main zip file and the rest are in the zip that is inside the main zip file. Extract both zip files.
tcrews said:
They are all there. Bootloader and the radio are in the main zip file and the rest are in the zip that is inside the main zip file. Extract both zip files.
Click to expand...
Click to collapse
after seeing this post I realize your talking about the factory image (tgz) and not the OTA zip.........
I have now downloaded the image but I am sure this post was referring to the 5.1 ota zip.......
Hi Guys..
So I've followed a guide, wherein it will walk you through on how to flash TWRP on your phone on your non-active partition.
I would want to revert my non-active partition to stock, any thoughts?
Any help is much appreciated!
Extract the stock boot.img from stock and boot into fastboot
fastboot flash boot_(a or b) boot.img
kishd said:
Extract the stock boot.img from stock and boot into fastboot
fastboot flash boot_(a or b) boot.img
Click to expand...
Click to collapse
Is this rooting? I would want to revert everything back to stock, man
What's the easiest way to return to the stock kernel? I keep reading to flash dtbo.img and the stock boot.img, but wouldn't doing that kill magisk?
Edit: I'm dumb. Easiest way for future magisk users: just re-patch the stock boot image and flash it in fastboot
Shayded said:
What's the easiest way to return to the stock kernel? I keep reading to flash dtbo.img and the stock boot.img, but wouldn't doing that kill magisk?
Click to expand...
Click to collapse
Yes, flashing those stock images will kill Magisk. So what you would want to do is flash the factory dtbo.img, and then you can just flash a pre-patched Magisk boot.img to revert to stock kernel with Magisk.
If you're already on the Apr 2020 firmware (specifically QQ2A.200405.005), here are the files you need to flash. I uploaded the QQ2A.200405.005 factory dtbo.img for you for your convenience. If you're on a different region / firmware, don't flash these lol.
coral-qq2a.200405.005-factory-dtbo.img: https://www.androidfilehost.com/?fid=4349826312261767171
coral-qq2a.200405.005-magisk_patched-20.4.img: https://www.androidfilehost.com/?fid=4349826312261763705
boot into bootloader,
fastboot flash dtbo coral-qq2a.200405.005-factory-dtbo.img
fastboot flash boot coral-qq2a.200405.005-magisk_patched-20.4.img
reboot phone
edit: i see you already edited your post. just in case the kernel you were using modified the dtbo partition, i would also recommend flashing the stock dtbo image as well.
Shayded said:
just re-patch the stock boot image and flash it in fastboot
Click to expand...
Click to collapse
Flash boot and dtbo too just to avoid potential issues