Related
So I forgot to backup my stock kernel before flashing franco R23. Can I just extract the boot.img from the update.zip? I'm on LMY47M. Thanks!
chrisbo4 said:
So I forgot to backup my stock kernel before flashing franco R23. Can I just extract the boot.img from the update.zip? I'm on LMY47M. Thanks!
Click to expand...
Click to collapse
yes, assuming that's the build your are running.
flash using fastboot:
fastboot flash boot boot.img
you'll have to root again after, if desired.
PhilDX said:
yes, assuming that's the build your are running.
flash using fastboot:
fastboot flash boot boot.img
you'll have to root again after, if desired.
Click to expand...
Click to collapse
Thanks! I'll give that a try.
It depends what you mean bybuodste.zip. if you mean OTA then no but you can normally get it from the factory images but there isn't one for M so you'll need to find the rooted ROM.zip and extract it from there.
rootSU said:
It depends what you mean bybuodste.zip. if you mean OTA then no but you can normally get it from the factory images but there isn't one for M so you'll need to find the rooted ROM.zip and extract it from there.
Click to expand...
Click to collapse
^^^ this guy is right, I read the OP too quickly and missed the part about update.zip, I just assumed that we were talking about factory images.
I don't think the boot.img changed after D (including E, M and I), but a little digging around should verify that.
factory images are here:
https://developers.google.com/android/nexus/images
whatever you do, do not attempt to relock your boot loader (should you want to for some reason) until everything is working properly.
PhilDX said:
I don't think the boot.img changed after D (including E, M and I), but a little digging around should verify that.
Click to expand...
Click to collapse
Good point.
Could download the OTA files and run an md5sum on all the boot patches. If they match in each, they're patching kernel identically and the factory image version for any 5.1 would be appropriate.
Hi,
i'm trying to customize the system.img for my own purpose and flash it via Odin.
i'm running Ubuntu 14.04 TLS.
i did some tests and non of them worked, the flash was succeeded but i get soft brick (bootloop)
so, what is did?
these steps, please correct me if i did something wrong.
1)simg2img on the extracted system.img from the stock tar.
2)mount ext4 type the converted system.raw using the following command: mount -t ext4 -o loop img.raw /mnt/
now i want to repack it without making changes (for tests), using the following commands:
1)make_ext4fs -s -l 3145728000 -a system system_nonbloat.img /mnt
2)sgs4ext4fs --bloat system_nonbloat.img system.img
the sizes are not equals. (~30mb less than the original system image).
someone know's what i'm doing wrong?
thanks!
Try it without the - a system variable.
ashyx said:
Try it without the - a system variable.
Click to expand...
Click to collapse
Thanks for your quick reply,
i just tried this, and now i have only few mb missing,
system_out.img -> 2611942608
system_original.img -> 2644169200
can you explain why the sizes are not equals?
and still, not working.
Amit Abitbul said:
Thanks for your quick reply,
i just tried this, and now i have only few mb missing,
system_out.img -> 2611942608
system_original.img -> 2644169200
can you explain why the sizes are not equals?
and still, not working.
Click to expand...
Click to collapse
Where did you get make_ext4fs from?
ashyx said:
Where did you get make_ext4fs from?
Click to expand...
Click to collapse
I compiled the tools from this git
github.com /ASdev/android_img_repack_tools/tree/android-5.0.2
Amit Abitbul said:
I compiled the tools from this git
github.com /ASdev/android_img_repack_tools/tree/android-5.0.2
Click to expand...
Click to collapse
Compile from branch 5.1.1 and try again.
ashyx said:
Compile from branch 5.1.1 and try again.
Click to expand...
Click to collapse
i have the same result.
still missing few megabytes.
Amit Abitbul said:
i have the same result.
still missing few megabytes.
Click to expand...
Click to collapse
I wouldn't worry about the packed size difference. Convert your output image to raw and see if the size matches the original raw image.
Also you probably need to patch the boot.img to remove dm-verity.
Supersu can do this for you.
ashyx said:
I wouldn't worry about the packed size difference. Convert your output image to raw and see if the size matches the original raw image.
Also you probably need to patch the boot.img to remove dm-verity.
Supersu can do this for you.
Click to expand...
Click to collapse
Yes, the raw image is the same,
What do you mean about the boot.img and dm-verity?
I'm kind of new in this world.
If I repack without making any change I need to do something with the boot image?
Amit Abitbul said:
Yes, the raw image is the same,
What do you mean about the boot.img and dm-verity?
I'm kind of new in this world.
If I repack without making any change I need to do something with the boot image?
Click to expand...
Click to collapse
Dm-verity is part of a chain of trust which does an integrity check on the system partition.
If it is modified the device won't boot.
This is why supersu patches the boot.img to disable it.
Try installing the latest supersu it should disable dm-verity then see if it boots.
ashyx said:
Dm-verity is part of a chain of trust which does an integrity check on the system partition.
If it is modified the device won't boot.
This is why supersu patches the boot.img to disable it.
Try installing the latest supersu it should disable dm-verity then see if it boots.
Click to expand...
Click to collapse
And if I don't want to root the device, what I need to do?
I really appreciate your help, thank you!
Amit Abitbul said:
And if I don't want to root the device, what I need to do?
I really appreciate your help, thank you!
Click to expand...
Click to collapse
If you've already modified the system partition what difference does it make?
Flash this zip in twrp
https://www.androidfilehost.com/?fid=24459283995297893
Sent from my SM-T280 using XDA-Developers mobile app
ashyx said:
If you've already modified the system partition what difference does it make?
Flash this zip in twrp
https://www.androidfilehost.com/?fid=24459283995297893
Sent from my SM-T280 using XDA-Developers mobile app
Click to expand...
Click to collapse
I will flash it in users tablets, I don't want them to have root access,
And i dont want to disable knox.
Amit Abitbul said:
I will flash it in users tablets, I don't want them to have root access,
And i dont want to disable knox.
Click to expand...
Click to collapse
Which version of TAB S2?
Sent from my SM-T280 using XDA-Developers mobile app
ashyx said:
Which version of TAB S2?
Sent from my SM-T280 using XDA-Developers mobile app
Click to expand...
Click to collapse
SM-T810 WiFi Version.
Running android 5.0.2.
Amit Abitbul said:
SM-T810 WiFi Version.
Running android 5.0.2.
Click to expand...
Click to collapse
The problem is to patch the boot.img and disable dm-verity you need to unpack the boot.img make the modifications then repack.
This leaves you with an unsigned image that may trip knox.
Sent from my SM-T280 using XDA-Developers mobile app
ashyx said:
The problem is to patch the boot.img and disable dm-verity you need to unpack the boot.img make the modifications then repack.
This leaves you with an unsigned image that may trip knox.
Sent from my SM-T280 using XDA-Developers mobile app
Click to expand...
Click to collapse
boot.img modifications? what i need to do there? maybe unpack and repack without making changes?
ashyx said:
The problem is to patch the boot.img and disable dm-verity you need to unpack the boot.img make the modifications then repack.
This leaves you with an unsigned image that may trip knox.
Sent from my SM-T280 using XDA-Developers mobile app
Click to expand...
Click to collapse
do you have a tutorial how to build my own based stock rom?
And how to make the final file, so I can flash it?
I don't know what I missing here, and it still not working.
Stuck on "Samsung Tab S2"
Amit Abitbul said:
do you have a tutorial how to build my own based stock rom?
And how to make the final file, so I can flash it?
I don't know what I missing here, and it still not working.
Stuck on "Samsung Tab S2"
Click to expand...
Click to collapse
None of it going to work unless you're prepared to patch the boot.img and remove dm-verity.
ashyx said:
None of it going to work unless you're prepared to patch the boot.img and remove dm-verity.
Click to expand...
Click to collapse
I flashed your zip file and the cf auto root via twrp,
And still... Nothing, what I need to do to boot.img?
Here are stock Mate 9 boot images that are modified to not force encryption. You can flash these in fastboot or TWRP, just select Image in TWRP then flash. An insecure boot image lets you use adb remount, and adb push or adb pull etc. to /system and its contents. Basically it's using ADB as root. I'll modify more upon request provided you link me to the boot you want modified.
ALL VERSIONS:
https://www.androidfilehost.com/?w=files&flid=152685
*To remove encryption after flashing to stock , boot into TWRP, format data, reboot recovery then flash a decrypted boot.img. If you're running a stock modified kernel, formatting data alone will not remove encryption. The idea is to always be decrypted. Never boot the system with a stock unmodified boot.img or it will encrypt your internal storage. So if you're fastboot flashing back to stock from another rom, flash a modified boot.img instead of the stock one*
In the full root thread it was advised to format data first and then flash modified boot image. In this OP it says to flash modified boot image and then format data. Does the order matter or can you do it both ways? Thanks
Sent from my MHA-L09 using XDA-Developers Legacy app
JATCHUHAN said:
In the full root thread it was advised to format data first and then flash modified boot image. In this OP it says to flash modified boot image and then format data. Does the order matter or can you do it both ways? Thanks
Sent from my MHA-L09 using XDA-Developers Legacy app
Click to expand...
Click to collapse
The order doesn't matter as long as you Format Data and have the Decrypted boot.img installed you're good. I updated the OP with the same directions as the full root thread so there is no confusion. Thanks for pointing this out.
Ok thanks
Sent from my MHA-L09 using XDA-Developers Legacy app
JATCHUHAN said:
Ok thanks
Sent from my MHA-L09 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Just to clarify. After you Format Data your data partition gets decrypted until first boot.
That's why you have to flash the decrypted boot.img before booting.
ante0 said:
Just to clarify. After you Format Data your data partition gets decrypted until first boot.
That's why you have to flash the decrypted boot.img before booting.
Click to expand...
Click to collapse
Yes I format data and flash decrypted boot before booting the phone. All is OK
Also aj could you decrypt the boot for L09C432B156 please, the link is below
https://drive.google.com/file/d/0B-qepxzncI0DSVpQN1RMTGZOX00/view?usp=drivesdk
Many thanks
Sent from my MHA-L09 using XDA-Developers Legacy app
Do you think in next days it will be possibile to get boot images also for Pro/ PD Mate 9? Thanks.
lukemo said:
Do you think in next days it will be possibile to get boot images also for Pro/ PD Mate 9? Thanks.
Click to expand...
Click to collapse
What's your full build number (Settings-About)?
ante0 said:
What's your full build number (Settings-About)?
Click to expand...
Click to collapse
LON-L29C721B138...is the last firmware for porsche design mate 9...
lukemo said:
LON-L29C721B138...is the last firmware for porsche design mate 9...
Click to expand...
Click to collapse
I can decrypt when I get home in 2 hourish.
lukemo said:
Do you think in next days it will be possibile to get boot images also for Pro/ PD Mate 9? Thanks.
Click to expand...
Click to collapse
Just send me a link to the boot image you need done
ajsmsg78 said:
Just send me a link to the boot image you need done
Click to expand...
Click to collapse
Thanks a lot. Tomorrow I'll be back to Milan and I'll download the ROM and extract the boot.img file.
ajsmsg78 said:
Just send me a link to the boot image you need done
Click to expand...
Click to collapse
Here you can find the boot.img for Porsche Design B138. Thanks.
https://www.dropbox.com/s/45adneap6dduab5/BOOT.img?dl=0
lukemo said:
Here you can find the boot.img for Porsche Design B138. Thanks.
https://www.dropbox.com/s/45adneap6dduab5/BOOT.img?dl=0
Click to expand...
Click to collapse
https://www.dropbox.com/s/tgfdprba4ikuaah/decrypted-boot-MHA-L29C721B138.img?dl=0
And sorry, totally forgot it yesterday
ante0 said:
https://www.dropbox.com/s/tgfdprba4ikuaah/decrypted-boot-MHA-L29C721B138.img?dl=0
And sorry, totally forgot it yesterday
Click to expand...
Click to collapse
Why to be sorry? You're so kind, thanks, I'll try it in the next few days. Only a question: you called the decrypted boot MHA-L29, obviously it's my LON-L29C721B138 decrypted I think...
lukemo said:
Why to be sorry? You're so kind, thanks, I'll try it in the next few days. Only a question: you called the decrypted boot MHA-L29, obviously it's my LON-L29C721B138 decrypted I think...
Click to expand...
Click to collapse
Oh, the filename is just incorrect. It's the same Boot you posted
https://www.dropbox.com/s/tgfdprba4ikuaah/decrypted-boot-LON-L29C721B138.img?dl=0
Updated file name.
How come there's no US C567 decrypted boot image?
posydon1 said:
How come there's no US C567 decrypted boot image?
Click to expand...
Click to collapse
Was wondering the same thing, haven't seen anything for it. I just want adb to free up wifi hotspot on my unlimited plan
posydon1 said:
How come there's no US C567 decrypted boot image?
Click to expand...
Click to collapse
erikclaw said:
Was wondering the same thing, haven't seen anything for it. I just want adb to free up wifi hotspot on my unlimited plan
Click to expand...
Click to collapse
Because there is no Firmware update for it yet.
If you have TWRP, please backup boot and post here
ante0 said:
Because there is no Firmware update for it yet.
If you have TWRP, please backup boot and post here
Click to expand...
Click to collapse
I can do that
Edited: https://db.tt/ke4c3m3tr1
TWRP from TWRP Builder builded for Nokia 7 Plus....
I still don't know if working (as i write in another thread), so that it does not fit, i write separate thread about it...
Small story:
I unpacked B2N-132E-0-00WW-B07.nb0 using nbd tools, although is not complete unpacked, "B2N-0-132G-00WW-boot.img" is here...
Unpack using unmkbootimg and get kernel(zImage) and ramdisk(ramdisk.cpio.gz)...
In unpacked ramdisk is binary "recovery", "init.recovery.qcom.rc" and "recovery.fstab" which is used/imported by default "init.rc"...
Then i think this is recovery, using TWRP Builder APK installed on N7+ i upload this image...
After some days i receive message that TWRP for Nokia 7 Plus is builded OK
Of course flashing this need Unlocked bootloader, then all who need it, PLEASE do participate in petition about Unlocking bootloader:
https://forum.xda-developers.com/nokia-7-plus/how-to/petition-possibility-to-unlock-t3788953
(after write comment, please also click too on "Do you have this question as well?")
Download: TWRP_onyx_00ww-08051830.img
Won't boot (tried to boot into it via fastboot (I don't want to flash it yet), and it just hanged on the android one text. Maybe going to properly flash it in few days.
Ranpe said:
Won't boot (tried to boot into it via fastboot (I don't want to flash it yet), and it just hanged on the android one text. Maybe going to properly flash it in few days.
Click to expand...
Click to collapse
thanks for testing, flashing is sure not need and not safe, boot via fastboot i think must work(if twrp working)...
anyway if you can boot then you have unlocked bootloader right?
can you try boot via fastboot original in nb0 boot/recovery from twrp is builded? file B2N-0-132G-00WW-boot.img
maybe problem is that this is "hybrid" boot+recovery in one, and is need some hotkey or magic durring boot?
k3dar7 said:
thanks for testing, flashing is sure not need and not safe, boot via fastboot i think must work(if twrp working)...
anyway if you can boot then you have unlocked bootloader right?
can you try boot via fastboot original in nb0 boot/recovery from twrp is builded? file B2N-0-132G-00WW-boot.img
maybe problem is that this is "hybrid" boot+recovery in one, and is need some hotkey or magic durring boot?
Click to expand...
Click to collapse
Yeah, I have unlocked bootloader on my 7+. Looks like the boot.img (which's used in that build of TWRP) is from older rom than the one I'm on at the moment. (B2N-213B-0-00WW-boot.img) May it be the reason for it to not boot? Anyway, I'll try to build a newer version soon.
Ranpe said:
Yeah, I have unlocked bootloader on my 7+. Looks like the boot.img (which's used in that build of TWRP) is from older rom than the one I'm on at the moment. (B2N-213B-0-00WW-boot.img) May it be the reason for it to not boot? Anyway, I'll try to build a newer version soon.
Click to expand...
Click to collapse
How did you get it open? Bootloader
DroiDMester said:
How did you get it open? Bootloader
Click to expand...
Click to collapse
https://forum.xda-developers.com/nokia-6/how-to/guide-how-to-unlock-bootloader-qualcomm-t3769930/
Ranpe said:
Yeah, I have unlocked bootloader on my 7+. Looks like the boot.img (which's used in that build of TWRP) is from older rom than the one I'm on at the moment. (B2N-213B-0-00WW-boot.img) May it be the reason for it to not boot? Anyway, I'll try to build a newer version soon.
Click to expand...
Click to collapse
yes, TWRP in #0 is builded from *boot.img from 8.0, i not find newer version, you have B2N-213B-0-00WW-boot.img ? if yes, then please try upload it via TWRP Builder, i not this do because not have newer file and too not posible to upload more that 1x from one device...
unlocking bootloader you do via NTool?
k3dar7 said:
yes, TWRP in #0 is builded from *boot.img from 8.0, i not find newer version, you have B2N-213B-0-00WW-boot.img ? if yes, then please try upload it via TWRP Builder, i not this do because not have newer file and too not posible to upload more that 1x from one device...
unlocking bootloader you do via NTool?
Click to expand...
Click to collapse
I've submitted the newer boot.img to them already, we'll see if they update it. Yeah, unlocked via ntool (by a guy I know).
Ranpe said:
I've submitted the newer boot.img to them already, we'll see if they update it. Yeah, unlocked via ntool (by a guy I know).
Click to expand...
Click to collapse
strange, i not see it in complete, queue, running or rejected don't show after upload you some error like "for this device is already builded"? i don't know if is posible rebuild for same device model from another device with another/newer boot.img...
I thought too about NTool, but i not find any seller od setool2 credit with small amount of credit (<=10), only 30 and for me message no answer... also authot of NTool write me only "not help you"... then try wait what Nokia do with many question about posibility of unlocking bootloader officialy...
try to get stock recovery img, porting should be easier.
SkaboXD said:
try to get stock recovery img, porting should be easier.
Click to expand...
Click to collapse
as i say in #0 TWRP is builded from srock recovery from 8.0 NB0 for N7p, i think problem is that N7p not use separate recovery but is inside normal boot, then need some magic to switch to recovery part of this "hybrid" boot, and because N7p need to recovery via powering cable and hold VolUp+Power then i think is same need with booting TWRP from #0, but who know if this is possible with not flashed booting via fastboot...
edit: anyway if my thoughts are true, then with hybrid boot+recovery flashed to device, is really need twrp based on exact boot image for current rootfs on device... (as Rampe too say if is possible evoce recovery from image booted via fastboot without flashing, then is not need exact version...
SkaboXD said:
try to get stock recovery img, porting should be easier.
Click to expand...
Click to collapse
The recovery is in the boot.img, and we have the images already.
Ranpe said:
The recovery is in the boot.img, and we have the images already.
Click to expand...
Click to collapse
oh i get it, so you need to make twrp for every Android version because of changed boot.img?
SkaboXD said:
oh i get it, so you need to make twrp for every Android version because of changed boot.img?
Click to expand...
Click to collapse
Not 100% sure of it, but unfortunately it may be so.
SkaboXD said:
oh i get it, so you need to make twrp for every Android version because of changed boot.img?
Click to expand...
Click to collapse
if changed kernel version/config (or binary, script, key in boot.img) then yes... if update use same files in boot.img as previous then no...
if i look at version in Settings/About for 8.1 v2.13 and 8.1 v2.22 then kernel version i same 4.4.78, but builded date is other (17.3. and 20.4.), not know if changes config, source etc, or is only same kernel rebuilded with full build proces again... i not have whole boot.img for 2.13 or 2.22 only for 8.0 v1.23
edit: FW for camera/touch/baseband/nothing not in boot.img (if not compile inside kernel(which i do not expect))
@Ranpe you have boot.img for 2.13 and/or 2.22 ? can you please upload it somewhere?
k3dar7 said:
@Ranpe you have boot.img for 2.13 and/or 2.22 ? can you please upload it somewhere?
Click to expand...
Click to collapse
Yeah, I have the boot.img for 2.13, but not (yet) for 2.22 (Need to get python working properly so I could dump inside of the payload.bin in the new OTA-update). You can download the 2.13 boot.img (and some other stuff) from here.
dotsaredots said:
Yeah, I have the boot.img for 2.13, but not (yet) for 2.22 (Need to get python working properly so I could dump inside of the payload.bin in the new OTA-update). You can download the 2.13 boot.img (and some other stuff) from here.
Click to expand...
Click to collapse
thanks for uploading, i now too have extracted 2.13 using payload_dumper.py (link from here), but for unpack payload.bin from 2.22 i think do not help any python "propertly working" because 2.22 is incremental update and this is not supported by payload_dumper.py...
btw: now i'm sure that N7p have really hybrid recovery_in_boot, what is used for any Phone that use new A/B method of updating on running system and simply switch to new update after reboot...
https://source.android.com/devices/tech/ota/ab/ab_implement
first of all you need to edit recovery.fstab in vendor partion it won`t boot because of encrypted data
The Moto X4 (payton) too has a hybrid recovery and they managed to make twrp. Might contact @mightysween or the official maintainers at twrp for hints?
Broadcasted from Zeta Reticuli
Gravemind2015 said:
The Moto X4 (payton) too has a hybrid recovery and they managed to make twrp. Might contact @mightysween or the official maintainers at twrp for hints?
Broadcasted from Zeta Reticuli
Click to expand...
Click to collapse
X4, Pixel2 and other A/B devices use a bootable recovery image (fastboot boot twrp.img) and then install a .ZIP package that patches the boot.img with TWRP recovery.
There have been other issues on the various devices with encryption, with bootcontrol partition switching, and with handling of empty "B" partitions. So proceed with caution, especially with flashing roms from TWRP before you have a way to populate the B partition.
Hello guys.
How can I root my device Oppo Reno?
Have you tried kingroot APK ?
Doesn't work
Possible root method
Anyone got a copy of boot.img for snapdragon 710 version as I have found a way to root
Do share with us.
Root
If someone has boot.img I can use magisk to root the IMG then flash it . Some tried on oppo find x and it worked
I have it.
SjDU said:
I have it.
Click to expand...
Click to collapse
pm it to @jsmith20094
Boot.img
SjDU said:
I have it.
Click to expand...
Click to collapse
Has anyone got a copy of boot.img for oppo Reno PCAM00 A.14 ?
THANKS
jsmith20094 said:
Has anyone got a copy of boot.img for oppo Reno PCAM00 A.14 ?
THANKS
Click to expand...
Click to collapse
you have PM
jsmith20094 said:
If someone has boot.img I can use magisk to root the IMG then flash it . Some tried on oppo find x and it worked
Click to expand...
Click to collapse
Isn't the bootloader locked and fastboot disabled? How would we be able to flash the new boot file?
wolfgart said:
you have PM
Click to expand...
Click to collapse
I have patched the boot.img but I can't go into fastboot mode it just reboots the OS any ideas I have already enabled oem unlock in dev settings ?
jsmith20094 said:
I have patched the boot.img but I can't go into fastboot mode it just reboots the OS any ideas I have already enabled oem unlock in dev settings ?
Click to expand...
Click to collapse
You were saying that in the same method someone gain root on Find X ?
Should be the same here
They did but I don't know how to unlock bootloader
jsmith20094 said:
They did but I don't know how to unlock bootloader
Click to expand...
Click to collapse
It seems that OPPO will release Deep Test for Reno too after 3 Months starting selling it in China ...
I don’t know what starts in the recovery. When you tap “Ver 1.2” for about 5 times. A pop up appears it say something like “ Test Case 1 .. it will cost about an hour”
Stock boot.img and patched magisk boot.img
Here I have provided the boot.img and Patched Magisk boot.img
Stock boot.img
https://drive.google.com/file/d/1-1suHaaCT-Sc3pSOb7Lh6_pRRXEnGlC7/view?usp=drivesdk
Magisk patched boot.img
https://drive.google.com/file/d/1-0Spo-IriS9PmMF82EkVA0vqyyBjfjSG/view?usp=drivesdk
jsmith20094 said:
Here I have provided the boot.img and Patched Magisk boot.img
Stock boot.img
https://drive.google.com/file/d/1-1suHaaCT-Sc3pSOb7Lh6_pRRXEnGlC7/view?usp=drivesdk
Magisk patched boot.img
https://drive.google.com/file/d/1-0Spo-IriS9PmMF82EkVA0vqyyBjfjSG/view?usp=drivesdk
Click to expand...
Click to collapse
do you have tested that ?
@jsmith20094
How to flash with locked bootloader as for now it's impossible to unlock? Thanks
At the moment we cant flash it but as soon as oppo launch the deep program for it you simply install there APK and it allows you to unlock fast boot . As soon as it launches I will post APK with instructions