Database Users

Insecure boot.img for 4.4

I've been looking for an insecure stock boot.img for about two hours now and I can't find one. I also tried modifying the one included in the factory image by unpacking and setting the ro.secure value in default.prop to 0 but it doesn't seem to work.
So my question is really split in two:
1) Am I just bad at searching? If so, could you link me to a working insecure stock boot.img?
2) What am I missing? I found something about adbd binaries or so, saying that this method doesn't work since 4.2.2, but I didn't quite understand it to be honest... What more modifications do I need to make in order for it to work?
Basically, all I want to be able to do is use adb remount and adb push.
Huge thanks in advance! :good:

fritzhy said:
I've been looking for an insecure stock boot.img for about two hours now and I can't find one. I also tried modifying the one included in the factory image by unpacking and setting the ro.secure value in default.prop to 0 but it doesn't seem to work.
So my question is really split in two:
1) Am I just bad at searching? If so, could you link me to a working insecure stock boot.img?
2) What am I missing? I found something about adbd binaries or so, saying that this method doesn't work since 4.2.2, but I didn't quite understand it to be honest... What more modifications do I need to make in order for it to work?
Basically, all I want to be able to do is use adb remount and adb push.
Huge thanks in advance! :good:
Click to expand...
Click to collapse
as far i know to do adb remount / push u just need to unlock bootloader doing fastboot oem unlock(with phone in fastboot mode)those 2 command work here using that.

opssemnik said:
as far i know to do adb remount / push u just need to unlock bootloader doing fastboot oem unlock(with phone in fastboot mode)those 2 command work here using that.
Click to expand...
Click to collapse
My bootloader is unlocked alright, also I'm pretty sure that the only thing the bootloader has to do with it, is that it has to be unlocked if you want to be able to flash a new kernel (independent on if it's insecure or not).

fritzhy said:
My bootloader is unlocked alright, also I'm pretty sure that the only thing the bootloader has to do with it, is that it has to be unlocked if you want to be able to flash a new kernel (independent on if it's insecure or not).
Click to expand...
Click to collapse
weird, i have never seen security boot off even with custom, now im on stock 4.3 with google kernel and i can do those 2 commands, i just flashed ak now and still security boot on, franco is the same thing, so i guess there is not security boot off for n4.

[Q] How to install kernel with ADB

Hi Everyone!
My question is can you install kernel (that is boot.img) with ADB?
I don't want responses like use SGY Toolkit (I know it can flash kernel but it does not use ADB), or use chamatht kernel restore, Kernel Backup/Restore.
I want this to be done by ADB,
because I don't want to wear and tear hardware buttons in recovery.
I have a idea, but I don't know if this works. Can someone test this and tell me?
NOOBS DON'T TRY THIS. THIS IS NOT CHILDS PLAY.
Code:
adb push boot.img /sdcard/hnk
adb shell
$ su
# stop
# dd if=/sdcard/hnk/boot.img of=/dev/block/bml7
# reboot
Can someone tell me is this proper way? Or suggest any other new working way.
Thanks in advance.

hnkotnis said:
Hi Everyone!
My question is can you install kernel (that is boot.img) with ADB?
I don't want responses like use SGY Toolkit (I know it can flash kernel but it does not use ADB), or use chamatht kernel restore, Kernel Backup/Restore.
I want this to be done by ADB,
because I don't want to wear and tear hardware buttons in recovery.
I have a idea, but I don't know if this works. Can someone test this and tell me?
NOOBS DON'T TRY THIS. THIS IS NOT CHILDS PLAY.
Code:
adb push boot.img /sdcard/hnk
adb shell
$ su
# stop
# dd if=/sdcard/hnk/boot.img of=/dev/block/bml7
# reboot
Can someone tell me is this proper way? Or suggest any other new working way.
Thanks in advance.
Click to expand...
Click to collapse
why would someone recommed you using SGY TOOLKIT
WHEN IT HAS BEEN CREATED BY YOU
HAHAHA....

abhishekr700 said:
why would someone recommed you using SGY TOOLKIT
WHEN IT HAS BEEN CREATED BY YOU
HAHAHA....
Click to expand...
Click to collapse
Do you know why I typed it?
There are n00bs who suggest such things. They don't bother what they type.
(This has been previously happenedd to a Recognized Developer, who used to live near my place).
So I added it so I will not get stupid notifications suggesting my own toolkit to me.
Anyway please do not post unless you have answer.

hnkotnis said:
Do you know why I typed it?
There are n00bs who suggest such things. They don't bother what they type.
(This has been previously happenedd to a Recognized Developer, who used to live near my place).
So I added it so I will not get stupid notifications suggesting my own toolkit to me.
Anyway please do not post unless you have answer.
Click to expand...
Click to collapse
sorry for posting
well found this maybe it helpshttp://www.xoomforums.com/forum/motorola-xoom-development/3209-flashing-kernel-through-adb-lots-pics.html
and
http://sanamsxperia.blogspot.in/p/installing-stock-custom-kernels.html

abhishekr700 said:
sorry for posting
well found this maybe it helpshttp://www.xoomforums.com/forum/mot...09-flashing-kernel-through-adb-lots-pics.html
and
http://sanamsxperia.blogspot.in/p/installing-stock-custom-kernels.html
Click to expand...
Click to collapse
I appreciate your help.
But you have found wrong answer.
This has Fastboot.
Samsung phones are not compatible with fastboot.
In that method you need to go to bootloader menu (NOT AVAILABLE IN SAMSUNG)
In that method command is
Code:
fastboot flash [COLOR=red][U]boot[/U][/COLOR] boot.img
This flashes boot.img to boot partition (red coloured in above command)
But it is not for SGY.
Have you tried the code I have mentioned above? (OF COURSE AT YOUR OWN RISK)

hnkotnis said:
I appreciate your help.
But you have found wrong answer.
This has Fastboot.
Samsung phones are not compatible with fastboot.
In that method you need to go to bootloader menu (NOT AVAILABLE IN SAMSUNG)
In that method command is
Code:
fastboot flash [COLOR=red][U]boot[/U][/COLOR] boot.img
This flashes boot.img to boot partition (red coloured in above command)
But it is not for SGY.
Have you tried the code I have mentioned above? (OF COURSE AT YOUR OWN RISK)
Click to expand...
Click to collapse
maybe this is suitable
So your question was how to flash a kernel NOT how to flash a rom image, correct? The suggestions above are how to install a rom (update.zip or nandroid backup)
Here's how to flash just the kernel:
Assumptions:
- you have root
- you can use ADB
- flash_image binary is installed
- you have the kernel image you want to install on the phone already
Steps:
1). Boot phone into recovery
2). run "adb shell" to get a root shell
3). type "flash_image boot kernel.img" where kernel.img is the filename of the kernel image you want to flash
Note: you can ONLY do this via adb in recovery. Any other way will result in an error (permissions).
Click to expand...
Click to collapse

abhishekr700 said:
maybe this is suitable
Click to expand...
Click to collapse
I told you.
I have already searched shell and Android Debugging Bridge commands before asking a question in XDA Forum.
This does not work.
I think I will have to wait till someone tries my ADB commands set.

B29 bootloader unlocked message

I'd like to know if there's a way to remove the 5 second "Your device has been unlocker and can't be trusted" message that started coming up every time I boot when I unlocked the bootloader on my A2017U.
If I understand correctly, this was added in B29 and I just need to flash the B27 boot sequence and then unlock it. Just not sure exactly how to do that, and what specific files I need.
Thanks

I'll just get used to that Boot Message, for the whole reason of if you want BL unlock when N hits, you are going to have that message unless ZTE changed the way it boots.
Otherwise you can flash B20 aboot.img to remove such thing.

DrakenFX said:
I'll just get used to that Boot Message, for the whole reason of if you want BL unlock when N hits, you are going to have that message unless ZTE changed the way it boots.
Otherwise you can flash B20 aboot.img to remove such thing.
Click to expand...
Click to collapse
Hi,
I unlocked my A2017G using controllerboy's method. I didn't get this message then. But after flashing the B11 full rom from ZTE's webstite (using the update.zip from my SDCard) I now also have this message. Since I'm on a A2017G I can't flash the B20 boot.img i guess. Can I flash the boot.img from controllerboys thread or will that brick my device because of the B11 ROM?
Side note: I didn't get offered the update to Nougat (even without root) now I'm on B11. Not sure if I want to switch no Nougat yet without xposed, but if I wanted, how would I proceed?
Many thanks in advance,
Cheers,
/Cacti

The Boot message is not in the Boot.img. You habe to flash the old aboot to get rid of the message. I already did it and it is working fine.

Bomberus said:
The Boot message is not in the Boot.img. You habe to flash the old aboot to get rid of the message. I already did it and it is working fine.
Click to expand...
Click to collapse
Can you provide a quick tutorial for flashing aboot.img? Tried with fastboot flash and it failed.
Thanks!

Bomberus said:
The Boot message is not in the Boot.img. You habe to flash the old aboot to get rid of the message. I already did it and it is working fine.
Click to expand...
Click to collapse
Thanks! That worked flawlessly!!!
@shifuharris: Take a look here: https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379
You need step 1,6 and 13 of the B) Unlock the bootloader part
Worked for me.
Cheers,
/Cacti

le_cactus said:
Thanks! That worked flawlessly!!!
@shifuharris: Take a look here: https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379
You need step 1,6 and 13 of the B) Unlock the bootloader part
Worked for me.
Cheers,
/Cacti
Click to expand...
Click to collapse
Thanks for the help. However, I get a permission denied error when I try to execute step 13. Not sure why. Device is rooted. Any suggestions?
Thanks!

I had the same. I opened a terminal window, gave the su command and then did the dd commmand. Hope I make sense.
Cheers,
/Cacti
Sent from my ZTE A2017G using XDA-Developers Legacy app

Installation Procedure
To summarize the procedure:
First use adb to copy aboot and fbop (if you want to use the fastboot features) to your sdcard)
Then flash the aboot and fastboot(only needed if you want the fastboot lock/unlock options) images
Enjoy your unlocked phone
See B : https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379
Code:
#copy necessary files to internal sd card
adb push aboot.img /sdcard/
adb push fastboot_unlock.img /sdcard/
#make a backup to your internal sd of the partitions we are going to modify
adb shell dd if=/dev/block/bootdevice/by-name/fbop of=/sdcard/fbop_lock.img
adb shell dd if=/dev/block/bootdevice/by-name/aboot of=/sdcard/aboot_lock.img
#copy them to your pc
adb pull /sdcard/fbop_lock.img
adb pull /sdcard/aboot_lock.img
#flash the proper fastboot and aboot file
adb shell dd if=/sdcard/fastboot_unlock.img of=/dev/block/bootdevice/by-name/fbop
adb shell dd if=/sdcard/aboot.img of=/dev/block/bootdevice/by-name/aboot
I also added the old aboot and fastboot_unlock image. For me as a european user the fastboot unlock options was initally not available.

The bootloader message actually saved me from softbricks so I don't mind it being there

[DEV][ZS550KL][ZS570KL][ZS570KLPRO] Bootloader Unlock, Root & Busybox

Ladies & Gents, please buckle up for liftoff.
Code:
[COLOR="Red"][B]/* Disclaimer
* You are choosing to test this software as-is & accept full responsibility in case
* it will not work as expected. Or for WW3. Or dead kittens, whichever is worse.
*/[/B][/COLOR]
Instructions 1/2 = Bootloader Unlock:
Code:
[b]1: DOWNLOAD[/b] the [URL="https://drive.google.com/file/d/0B8rpJsF4EG0YUHh4UEo5ZExHWjg"]> prerequisites <[/URL]
[b]2: UNZIP[/b]
You will have 3 folders for zs550kl, zs570kl & zs570klpro containing:
UL-Z016-WW-4.12.40.9999-user.zip -> unlock-capable firmware update
UL-Z016_1-WW-4.12.40.9999-user.zip -> unlock-capable firmware update for the zs570kl PRO variant (in its own folder)
UnlockTool.apk -> unlock app, needed for the actual operation
PDF with Instructions in CN & EN (for zs570kl/pro only)
- bootroot.img - rooted boot image (bootrootn.img for ZS550KL Nougat)
- bootstock.img - stock boot image, if you want to return to stock or if something went wrong (bootstockn.img for ZS550KL Nougat)
- Superuser.apk - superuser app
[b]3: FACTORY RESET[/b] via Settings -> Backup & Reset
This usually solves the issue with not being able to unlock due to a "missing PIN"
Do through initial setup - no need to configure anything as the following factory reset will erase everything again.
Just click through the options to access the app drawer asap.
[b]4: COPY Files:[/b]
ZS570KL - Copy UL-Z016-WW-4.12.40.9999-user.zip to your internal storage
ZS570KLpro - Copy UL-Z016_1-WW-4.12.40.9999-user.zip to your internal storage
[COLOR="DarkOrchid"]ZS550KL - no files needed at this stage. Just ensure you are on the latest firmware: (Marshmallow: v12.40.108.29; Nougat: v22.40.26.43); update otherwise.
[URL="http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZS550KL/UL-Z018-WW-12.40.108.29-user.zip"]> latest MM firmware <[/URL] put it in the root of your internal storage.
[URL="http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZS550KL/UL-Z018-WW-22.40.26.43-user.zip"]> latest N firmware <[/URL] put it in the root of your internal storage.[/COLOR]
Copy & install UnlockTool.apk
[b]5: REBOOT[/b]; You should have a notification about a new firmware.
No notification for ZS550KL if you were already on the latest firmware.
Install & reboot again.
[b]6: Run the UNLOCK[/b] App
It should do another factory reset on success.
Instructions 2/2 = ROOTING:
Code:
[b]7:[/b] Copy/install Superuser.apk
[b]9:REBOOT into BOOTLOADER[/b]; either holding volume up + power from a powered down state or typing the following in a console (assuming you have ADB enabled in developer options)
adb reboot bootloader
[b]9: FLASH[/b] bootroot.img via fastboot
fastboot flash boot bootroot.img (you can also do a fastboot boot bootroot.img without flashing to check if the boot image works for you)
fastboot reboot
note: change the filename to bootrootn.img if you want to test the ZS550KL Nougat version.
[b]10:[/b] Check for root via adb shell; su or via any app requiring root, on device (terminal, titanium backup, etc...)
- in case something goes wrong, flash the stock boot via fastboot.
- report success/failure in this thread.
[b]11:[/b] BUSYBOX (Optional):
I've bundled busybox with the boot image; follow the commands below to install (in an adb shell or terminal session):
mount -o remount,rw /system
busybox --install -s /system/xbin/
[b]12: RECOVERY[/b] (Optional):
[URL="https://drive.google.com/file/d/0B8rpJsF4EG0YZ1FQSkUxRW9TdWs"]> stock dump <[/URL]
> twrp < / WIP

What it does mean to us? Can someone create some tutorial?
Wysłane z mojego ASUS_Z016D przy użyciu Tapatalka

squo_85 said:
What it does mean to us? Can someone create some tutorial?
Wysłane z mojego ASUS_Z016D przy użyciu Tapatalka
Click to expand...
Click to collapse
It means we have the bootloader unlock.
The tutorial/instructions are contained in a PDF in the zip.
English instructions at the end of the PDF.

Three is one more question?
Hot to root it?
Like for 520kl with changed according to 570kl files
Spoiler
https://youtu.be/hg77b8o8Jk4
Or just use universal tool e.g. Autoroot tool?
Spoiler
https://youtu.be/UYTCRhg0SCw

can confirm working on zs570kl/256GB (yes I knew it was dangerous, I used fastboot boot instead of fastboot flash - be wiser)

Chaosruler said:
can confirm working on zs570kl/256GB (yes I knew it was dangerous, I used fastboot boot instead of fastboot flash - be wiser)
Click to expand...
Click to collapse
Thanks for testing ;]
Were you thus able to achieve root from within an app on the system?

adwinp said:
Thanks for testing ;]
Were you thus able to achieve root from within an app on the system?
Click to expand...
Click to collapse
yeah, Titanium Backup (PRO)
thank you very much for your hard work, let the custom android era begin!

Chaosruler said:
yeah, Titanium Backup (PRO)
thank you very much for your hard work, let the custom android era begin!
Click to expand...
Click to collapse
Great, thank you for the confirmation & enjoy ;]
Let the fun begin ^^

Do you think I can flash with fastboot flash instead of running it with fastboot boot? The latter let's me have root until I restart my device( temp root)...
Maybe fastboot flash will perma root it

Chaosruler said:
can confirm working on zs570kl/256GB (yes I knew it was dangerous, I used fastboot boot instead of fastboot flash - be wiser)
Click to expand...
Click to collapse
Hey there,
How did you achieve root? How did you achieve unlocking bootloader. I have followed the instructions and all I have was my data erasing. How can I confirm if my bootloader is unlocked and what did you do to get root. OneClickRoot stated my phone could not be rooted.
I have the zs570kl/256gb phone too.

jmoricone said:
Hey there,
How did you achieve root? How did you achieve unlocking bootloader. I have followed the instructions and all I have was my data erasing. How can I confirm if my bootloader is unlocked and what did you do to get root. OneClickRoot stated my phone could not be rooted.
I have the zs570kl/256gb phone too.
Click to expand...
Click to collapse
bootloader unlock is not root... its what is required to root... to confirm your bootloader is unlocked use adb to get device info, it will say if its unlocked there
What I did to root is run fastboot boot bootroot.img to temporarily use the ops boot image

Chaosruler said:
bootloader unlock is not root... its what is required to root... to confirm your bootloader is unlocked use adb to get device info, it will say if its unlocked there
What I did to root is run fastboot boot bootroot.img to temporarily use the ops boot image
Click to expand...
Click to collapse
Wow, i guess i am a newbie here.. I have heard adb but dont remember what where or how i got it fo rmy zen2. can you provide instructions how how to check, access, use adb to confirm unlocked bootloader. Also can you provide instructions on to to run the boot image for rooting.
thanks

For some reason, i can't get to fastboot, i was able to get it before unlocking this device, now after unlocking, i can't get to fastboot, unless i'm missing something here. I can get to recover mode, but that all.
EDIT: Ok i got into boot loader, which my fastboot was able to detect the device, but the commands are unknown, search it up saying it;s locked, but i just did the installment above for updating it to make it unlock, am i missing something here? (I might do this over again later on tonight)
We may need screenshots of making sure to see the oem unlocking.

Darkdragontc said:
For some reason, i can't get to fastboot, i was able to get it before unlocking this device, now after unlocking, i can't get to fastboot, unless i'm missing something here. I can get to recover mode, but that all.
EDIT: Ok i got into boot loader, which my fastboot was able to detect the device, but the commands are unknown, search it up saying it;s locked, but i just did the installment above for updating it to make it unlock, am i missing something here? (I might do this over again later on tonight)
We may need screenshots of making sure to see the oem unlocking.
Click to expand...
Click to collapse
I updated post #1 with step by step instructions.
Follow.
I also went through the process myself, as described in OP & everything went fine.
Confirmed working.

adwinp said:
I updated post #1 with step by step instructions.
Follow.
I also went through the process myself, as described in OP & everything went fine.
Confirmed working.
Click to expand...
Click to collapse
Yup Confirmed Working, no more problems. Thank you! Now i hope we can make some custom roms and get twrp on here when we can. (820 that what i have)

Just to be clear, on the SD821 variant is this a permanent root or just a temp root?

ultramag69 said:
Just to be clear, on the SD821 variant is this a permanent root or just a temp root?
Click to expand...
Click to collapse
temp root if you use fastboot boot command
Perma root of you use fastboot flash boot command

Step 7 says the rooted image is only for the sd820 variant. It looks like people with the sd821 are having success so I guess it works for both?

pacattack81 said:
Step 7 says the rooted image is only for the sd820 variant. It looks like people with the sd821 are having success so I guess it works for both?
Click to expand...
Click to collapse
I can confirm it with my device...

pacattack81 said:
Step 7 says the rooted image is only for the sd820 variant. It looks like people with the sd821 are having success so I guess it works for both?
Click to expand...
Click to collapse
I used a SD820 boot image as base & don't have a SD821 variant to test on thus didn't want to mislead the community.
But @Chaosruler tested & it seems to work.

[OOS 11] Infinite boot animation following the installation of magisk module

Hello,
Yesterday I updated my OP8 Pro to OOS 11 by following this guide, everything was working fine and I kept the root.
I then updated one of my magisk modules (taichi) and after reboot I have an infinite boot animation.
Before, I went to the console in TWRP to uninstall the module, but there is no TWRP compatible with OOS 11.
So I don't know what to do.
Can someone help me please?
Thanks

zeldomar said:
Hello,
Yesterday I updated my OP8 Pro to OOS 11 by following this guide, everything was working fine and I kept the root.
I then updated one of my magisk modules (taichi) and after reboot I have an infinite boot animation.
Before, I went to the console in TWRP to uninstall the module, but there is no TWRP compatible with OOS 11.
So I don't know what to do.
Can someone help me please?
Thanks
Click to expand...
Click to collapse
You can try the following command whilst your device is on the boot logo:
adb wait-for-device shell magisk --remove-modules
If that does not work, take a patched boot.img for A11 and fastboot boot it first, if that works then remove the module and restart.
The latter worked for me when I had an issue earlier with a wonky magisk module.

Shredz98 said:
You can try the following command whilst your device is on the boot logo:
adb wait-for-device shell magisk --remove-modules
If that does not work, take a patched boot.img for A11 and fastboot boot it first, if that works then remove the module and restart.
The latter worked for me when I had an issue earlier with a wonky magisk module.
Click to expand...
Click to collapse
Thank you very much, it worked!
I used solution 2 with a boot.img extracted from the zip of OOS 11.

zeldomar said:
Thank you very much, it worked!
I used solution 2 with a boot.img extracted from the zip of OOS 11.
Click to expand...
Click to collapse
Glad it worked!

Shredz98 said:
Glad it worked!
Click to expand...
Click to collapse
By any chance, do you know how to uninstall a module in my case?
Because now that I am no longer root, and that Magisk is disabled, I no longer have access to the "modules" section in Magisk Manager.
Thank you!

zeldomar said:
By any chance, do you know how to uninstall a module in my case?
Click to expand...
Click to collapse
You can do so via ADB with a modded recovery, see here for more details

zeldomar said:
By any chance, do you know how to uninstall a module in my case?
Because now that I am no longer root, and that Magisk is disabled, I no longer have access to the "modules" section in Magisk Manager.
Thank you!
Click to expand...
Click to collapse
You can use Magisk Manager to path the boot.img you used and fastboot boot that to regain root and when you delete the module then fastboot flash the patched boot.img and voila root without the borked module
Or you can follow the patched recovery way which should work fine as well
Or just use the ADB commands while your phone is on

s3axel said:
You can do so via ADB with a modded recovery, see here for more details
Click to expand...
Click to collapse
Thanks, but there is no recovery for OOS 11
Shredz98 said:
You can use Magisk Manager to path the boot.img you used and fastboot boot that to regain root and when you delete the module then fastboot flash the patched boot.img and voila root without the borked module
Or you can follow the patched recovery way which should work fine as well
Or just use the ADB commands while your phone is on
Click to expand...
Click to collapse
Unfortunately, no solution works for the moment:
- if I boot (from fastboot) on a patched (so rooted) boot.img, I fall back on the infinite animation logo (I imagine that magisk is reactivated and that it tries to load the problematic module again)
- I can't find a patched OOS 11 recovery, do you have a link? what should I do with this recovery please?
- now that my phone is on, I can run the adb command "adb wait-for-device shell magisk --remove-modules", but I get the following error: "/ system / bin / sh: magisk: inaccessible or not found "
Thanks for your help.

Finally, the adb command during bootloop worked.
Thanks everyone!