• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[CLOSED]HaHaHack Dis: No Magisk REQUIRED!!!!

Status
Not open for further replies.
Search This thread

Pachacouti

Senior Member
Jul 8, 2020
232
44
52
The Capital above the Lower one...
  • Like
Reactions: MastNi

Pachacouti

Senior Member
Jul 8, 2020
232
44
52
The Capital above the Lower one...
Not your usual tut... it's more a bit of advice. Respect.

When I first tried to flash a rooted recovery, it all failed until I read of vbmeta. I jump through the vbmeta route, then I realise something VERY important.

When you flash a blank vbmeta, you wipe the structure of much of your fone. You never were supposed to WIPE your vbmeta structure.

Magisk needs YOU to do this. YOU dont.

A test resulting in Proof:

How many do this?

fastboot flash vbmeta blank_vbmeta.img
fastboot flash boot boot.img
fastboot flash recovery twrp_recovery.img

Or

fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot --disable-verity --disable-verification flash boot boot.img
fastboot --disable-verity --disable-verification flash recovery twrp_recovery.img

Both are wrong. What if: dm-1,2,3 cant mount?

Where are they if you wiped vbmeta? Does your fone know?

You WILL need vbmeta after this.

fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img 2>nul >nul
fastboot flash boot boot-debug.img

-allowed me to then do what I want?

How to add su to fone.

Follow the busybox link I posted. Do it manually in twrp.

Flash back to stock boot/recovery

Discover $ and # mean nothing

Discover I got full access with no app's adapted for such use...

Ask why they still use pie..

It's the only tutorial you'll need with a boot-debug.img

Let this be a warning.

It is the ONLY warning you'll get...

with your vbmeta blank'd you will be constantly trying to bypass safetynet

Warning time is up...

Flash back to stock after getting su to work with $ instead of #

su is no longer true root, so $

(system_as_root IS root, su comes AFTER, and so goes from # to $ in the structure of things.)

su is no longer used in # it's a role reversal. # is now $ if u get me.

in my fone...


$ su --context u:r:system_app:s0 -c "pm uninstall --user 0 com.google.android.apps.wellbeing" < /dev/null
$ success
$ su --context u:r:system_app:s0 -c "pm uninstall --user 0 com.android.emergency" < /dev/null
$ success
$

That's why I posted adb logs, proof is in the order of what you see... notice I started with

fastboot --disable-verity --disable-verification flash whatever

and as I progressed I no longer used anything other than

fastboot flash boot whatever.

fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img 2>nul >nul is HOW to disable vbmeta without WIPING it in a variant=user build

Wipe it if you want. I dont. Magisk wants you to when it is un-neccessary.

Because when removing the boot-debug and flashing stock back, my fone pass's safety.net, after re-locking bootloader, even with an unorthodox method produced by su when it is supposed to crash android 10 is it not? Magisk kills su by commandeering it's location, not android 10.


I'm not saying DONT use magisk using this method, it wont work. Side effects of magisk installed, with this is dead adb period Nada!

I'm saying by installing magisk, which takes over (patches) your vbmeta, the boot-debug.img becomes useless, just another boot with no vbmeta structure to follow...

Now one of you need to separate my notes from my commands, keep commands in order, and SEE.

Cause I rooted my fone. Here.#

Ps, at no point in this post did I use a blank vbmeta.

To properly disable verity, load boot-debug.img, reboot, type:

adb root
adb disable verity
adb reboot

That's it! it stay's across boot flashing etc... so bang goes --disable-verity, not needed after.

This is where you'r all going WRONG.

As aquarian, I swim where the fish sink... through their dead bodies that are not of the sea, I raise us all to immortality, by simply producing all 3 in me, jesus, lucifer, and the monkey.

It never was physical ;)
 
Last edited:

Pachacouti

Senior Member
Jul 8, 2020
232
44
52
The Capital above the Lower one...
Ok, yeah, I likadagringo... it's bad enough finding out your everyones god wether they believe or not lol... so I try to keep busy...

The following link proves I have root, and by design. Mine is the FIRST fone to offer the root as boot-debug.img.


Thanks for the insult's.

Now instead of insults, if someone would like to point me in the direction of a use-debug version I can load into my fone, I can do tests...

Aside's from that, I'm vindicated.

It took the monkey king (height of mans intelligence) to show you who knew better..

The customer.
 
Last edited:

munjeni

Senior Member
Jun 2, 2011
9,445
22,041
Thats something very wrong in that phone model software, security hole. Are you getting su work while on stock boot.img or you getting it work only while having boot debug img installed? Where you have put su binary? You do not have bootloop while keeping su installed (to the system?) after relocking bootloader?
 
Last edited:
  • Like
Reactions: lebigmac

Pachacouti

Senior Member
Jul 8, 2020
232
44
52
The Capital above the Lower one...
Thats something very wrong in that phone model software, security hole. Are you getting su work while on stock boot.img or you getting it work only while having boot debug img installed? Where you have put su binary? You do not have bootloop while keeping su installed (to the system?) after relocking bootloader?
Well, while you were typing your msg, I was doing this:

(warning, my adb log... read each line...)

Armor_X5_Q:/ # exit
Armor_X5_Q:/ # exit
Armor_X5_Q:/ # ^C
130|Armor_X5_Q:/ # exit

D:\0\AdbStation>so the order is
'so' is not recognized as an internal or external command,
operable program or batch file.

D:\0\AdbStation>adb shell
Armor_X5_Q:/ # exit

D:\0\AdbStation>adb su
adb.exe: unknown command su

D:\0\AdbStation>adb shell su
^C
D:\0\AdbStation>had to escape freeze
'had' is not recognized as an internal or external command,
operable program or batch file.

D:\0\AdbStation>adb shell
Armor_X5_Q:/ # su whoami
Armor_X5_Q:/ # su --help
SuperSU v2.82 (ndk:arm64-v8a) - Copyright (C) 2012-2017 - Chainfire & CCMT

Usage: su [options] [--] [-] [LOGIN] [--] [args...]

Options:
-c, --command COMMAND pass COMMAND to the invoked shell
-cn, --context CONTEXT switch to SELinux CONTEXT before invoking
-h, --help display this help message and exit
-, -l, --login pretend the shell to be a login shell
-m, -p,
-mm, --mount-master connect to a shell that can manipulate the
master mount namespace - requires su to be
running as daemon, must be first parameter
-mns, --mount-namespace PID enter mount namespace used by PID
--preserve-environment do not change environment variables
-s, --shell SHELL use SHELL instead of the default detected shell
-v, --version display public version and exit
-V display internal version and exit

Usage#2: su LOGIN COMMAND...

Usage#3: su {-d|--daemon|-ad|--auto-daemon|-r|--reload}
auto version starts daemon only on SDK >= 18 or
if SELinux is set to enforcing
(call only from a root session)

Usage#4: su {-i|--install|-u|--uninstall}
perform post-install / pre-uninstall maintenance
(call only from a root session)

Usage#5: su --id pid
identify eldest parent of pid
(call only from a root session)
Armor_X5_Q:/ # so su is actually working with boot-debug.img
sh: so: inaccessible or not found
127|Armor_X5_Q:/ # so now reflash stock boot ok?
sh: so: inaccessible or not found
127|Armor_X5_Q:/ # ok?
sh: ok?: inaccessible or not found
127|Armor_X5_Q:/ # ^C
130|Armor_X5_Q:/ # exit
130|Armor_X5_Q:/ # exit

D:\0\AdbStation>notice how i exit, twice in 2 seperate search's
'notice' is not recognized as an internal or external command,
operable program or batch file.

D:\0\AdbStation>adb shell exit

D:\0\AdbStation>adb shell
Armor_X5_Q:/ # exit

D:\0\AdbStation>but if I type su
'but' is not recognized as an internal or external command,
operable program or batch file.

D:\0\AdbStation>adb shell
Armor_X5_Q:/ # su
Armor_X5_Q:/ # exit
Armor_X5_Q:/ # cant exit
/system/bin/sh: cant: inaccessible or not found
127|Armor_X5_Q:/ # su
Armor_X5_Q:/ # ^C
130|Armor_X5_Q:/ #
130|Armor_X5_Q:/ # exit
130|Armor_X5_Q:/ # exit

D:\0\AdbStation>unless I type exit twice after ctrl/c
'unless' is not recognized as an internal or external command,
operable program or batch file.

D:\0\AdbStation>so stock boot time, r u ready
'so' is not recognized as an internal or external command,
operable program or batch file.

D:\0\AdbStation>adb reboot bootloader

D:\0\AdbStation>fastboot flash boot boot.img
Sending 'boot' (32768 KB) OKAY [ 0.780s]
Writing 'boot' OKAY [ 0.515s]
Finished. Total time: 1.435s

D:\0\AdbStation>fastboot flash recovery recovery.bin
fastboot: error: cannot load 'recovery.bin': No such file or directory

D:\0\AdbStation>fastboot flash recovery recovery.img
Sending 'recovery' (20646 KB) OKAY [ 0.671s]
Writing 'recovery' OKAY [ 0.328s]
Finished. Total time: 0.998s

D:\0\AdbStation>ok, so now I'm stock, vbmeta bein legit kicks in
'ok' is not recognized as an internal or external command,
operable program or batch file.

D:\0\AdbStation>fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.016s

D:\0\AdbStation>boot into gui
'boot' is not recognized as an internal or external command,
operable program or batch file.

D:\0\AdbStation>adb shell
adb.exe: no devices/emulators found

D:\0\AdbStation>need to regrant keys etc
'need' is not recognized as an internal or external command,
operable program or batch file.

D:\0\AdbStation>adb shell
Armor_X5_Q:/ $ su
1|Armor_X5_Q:/ $ see?
/system/bin/sh: see?: inaccessible or not found
127|Armor_X5_Q:/ $ su whoami
1|Armor_X5_Q:/ $ su --help
SuperSU v2.82 (ndk:arm64-v8a) - Copyright (C) 2012-2017 - Chainfire & CCMT

Usage: su [options] [--] [-] [LOGIN] [--] [args...]

Options:
-c, --command COMMAND pass COMMAND to the invoked shell
-cn, --context CONTEXT switch to SELinux CONTEXT before invoking
-h, --help display this help message and exit
-, -l, --login pretend the shell to be a login shell
-m, -p,
-mm, --mount-master connect to a shell that can manipulate the
master mount namespace - requires su to be
running as daemon, must be first parameter
-mns, --mount-namespace PID enter mount namespace used by PID
--preserve-environment do not change environment variables
-s, --shell SHELL use SHELL instead of the default detected shell
-v, --version display public version and exit
-V display internal version and exit

Usage#2: su LOGIN COMMAND...

Usage#3: su {-d|--daemon|-ad|--auto-daemon|-r|--reload}
auto version starts daemon only on SDK >= 18 or
if SELinux is set to enforcing
(call only from a root session)

Usage#4: su {-i|--install|-u|--uninstall}
perform post-install / pre-uninstall maintenance
(call only from a root session)

Usage#5: su --id pid
identify eldest parent of pid
(call only from a root session)
Armor_X5_Q:/ $ yeah, su in effect ;)
/system/bin/sh: syntax error: unexpected ')'
1|Armor_X5_Q:/ $
1|Armor_X5_Q:/ $
1|Armor_X5_Q:/ $
1|Armor_X5_Q:/ $
1|Armor_X5_Q:/ $
1|Armor_X5_Q:/ $ su
1|Armor_X5_Q:/ $
1|Armor_X5_Q:/ $
1|Armor_X5_Q:/ $
1|Armor_X5_Q:/ $ su
1|Armor_X5_Q:/ $ ^C
130|Armor_X5_Q:/ $
130|Armor_X5_Q:/ $ exit

D:\0\AdbStation>see? only one exit this time...
'see?' is not recognized as an internal or external command,
operable program or batch file.

D:\0\AdbStation>adb shell su --help
SuperSU v2.82 (ndk:arm64-v8a) - Copyright (C) 2012-2017 - Chainfire & CCMT

Usage: su [options] [--] [-] [LOGIN] [--] [args...]

Options:
-c, --command COMMAND pass COMMAND to the invoked shell
-cn, --context CONTEXT switch to SELinux CONTEXT before invoking
-h, --help display this help message and exit
-, -l, --login pretend the shell to be a login shell
-m, -p,
-mm, --mount-master connect to a shell that can manipulate the
master mount namespace - requires su to be
running as daemon, must be first parameter
-mns, --mount-namespace PID enter mount namespace used by PID
--preserve-environment do not change environment variables
-s, --shell SHELL use SHELL instead of the default detected shell
-v, --version display public version and exit
-V display internal version and exit

Usage#2: su LOGIN COMMAND...

Usage#3: su {-d|--daemon|-ad|--auto-daemon|-r|--reload}
auto version starts daemon only on SDK >= 18 or
if SELinux is set to enforcing
(call only from a root session)

Usage#4: su {-i|--install|-u|--uninstall}
perform post-install / pre-uninstall maintenance
(call only from a root session)

Usage#5: su --id pid
identify eldest parent of pid
(call only from a root session)

D:\0\AdbStation>adb shell su -c mount -o rw,remount /

D:\0\AdbStation>bingo
'bingo' is not recognized as an internal or external command,
operable program or batch file.

D:\0\AdbStation>see?
'see?' is not recognized as an internal or external command,
operable program or batch file.

D:\0\AdbStation>adb shell su -c mount -o rw,remount /system_root

D:\0\AdbStation>weird, huh?
'weird' is not recognized as an internal or external command,
operable program or batch file.

D:\0\AdbStation>no root app installed
'no' is not recognized as an internal or external command,
operable program or batch file.

D:\0\AdbStation>adb shell
Armor_X5_Q:/ $ cd system
Armor_X5_Q:/system $ cd xbin
Armor_X5_Q:/system/xbin $ ls
chromeos libsupol.so su suinit sukernel supolicy trace
Armor_X5_Q:/system/xbin $ su
1|Armor_X5_Q:/system/xbin $ suinit --help
1|Armor_X5_Q:/system/xbin $ cant get hash, dont need it...
/system/bin/sh: cant: inaccessible or not found
127|Armor_X5_Q:/system/xbin $ #
127|Armor_X5_Q:/system/xbin $ sudo su
/system/bin/sh: sudo: inaccessible or not found
127|Armor_X5_Q:/system/xbin $ su sudo
1|Armor_X5_Q:/system/xbin $ cd /
Armor_X5_Q:/ $ exit

D:\0\AdbStation>adb root
adbd cannot run as root in production builds

D:\0\AdbStation>pardon?
'pardon?' is not recognized as an internal or external command,
operable program or batch file.

D:\0\AdbStation>adb shell su -c whoami

D:\0\AdbStation>adb shell
Armor_X5_Q:/ $ adb shell su -c whoami
/system/bin/sh: adb: inaccessible or not found
127|Armor_X5_Q:/ $ su -c whoami
1|Armor_X5_Q:/ $ su -c mount -o rw,remount rootfs /
1|Armor_X5_Q:/ $ su -c mount -o rw,remount vendor
1|Armor_X5_Q:/ $ how do I...
/system/bin/sh: how: inaccessible or not found
127|Armor_X5_Q:/ $ no complaints from fone or su.
/system/bin/sh: no: inaccessible or not found
127|Armor_X5_Q:/ $
127|Armor_X5_Q:/ $
127|Armor_X5_Q:/ $
127|Armor_X5_Q:/ $
127|Armor_X5_Q:/ $
127|Armor_X5_Q:/ $ exit

D:\0\AdbStation>adb disable-verity
disable-verity only works for userdebug builds
verity cannot be disabled/enabled - USER build

D:\0\AdbStation>adb shell su -c disable-verity

D:\0\AdbStation>lol
'lol' is not recognized as an internal or external command,
operable program or batch file.

D:\0\AdbStation>
 

optimumpro

Senior Member
Jan 18, 2013
6,754
14,234
Thats something very wrong in that phone model software, security hole. Are you getting su work while on stock boot.img or you getting it work only while having boot debug img installed? Where you have put su binary? You do not have bootloop while keeping su installed (to the system?) after relocking bootloader?
It's joke. A good sign of a hoaxer is when he immediately jumps to effing everybody who questions his nonsense. That's a red flag that is all over this thread. {Mod edit}

Apart from that, {Mod edit}, there is no difference between ADB root and root. In reality, debug_boot.img does not provide full root access, it only provides root access for adb commands, and even that requires system_debug image, which you will never get on stock: to have a stock system_debug, one must recompile from sources with that flag. Show me an OEM who provides sources for anything other than kernel.

His other claim about passing Safetynet on stock with bootimage-debug is abracadabra. No phone with unlocked bootloader will pass Safetynet without modifications in framework and kernel: the frameworks usually contain the names of services and applications and kernel has the 'fooling' flags. Yeah, he can modify kernel, if he has sources, but would never be able to modify frameworks.

{Mod edit - Regards Oswald Boelcke}
 
Last edited by a moderator:

Pachacouti

Senior Member
Jul 8, 2020
232
44
52
The Capital above the Lower one...
{Mod edit}

The docs clearly state vbmeta resets when going from boot-img to stock.. from upper to lower whichever way... I dont wipe my vbmeta... I dont need to. The docs state why.

But with 2 =null as written, vbmeta can be disabled, but being legit, registers as such, even though disabled.

{Mod edit}

But read my proof, and deny it, {Mod edit - Disrespect removed! Oswald Boelcke}
 
Last edited by a moderator:

Pachacouti

Senior Member
Jul 8, 2020
232
44
52
The Capital above the Lower one...
Any dev wanna give me commands I can use in adb in order to copy n paste what you need to see my fone do, feel free, am up for testing, and being an android noob, I dont actually know what to look for, never mind post.

Ask away, keep it real, and see what I can do...

Commands please?
 

Pachacouti

Senior Member
Jul 8, 2020
232
44
52
The Capital above the Lower one...
Truth of the matter is reader's, yeah, I've a few followers in the midst of it all... I bought a fone I went mad at for a year before I figured this out... it's crazy if you actually read where I stopped writing in the firestick section, see, amazon caught up with ME, and we all got hit. They patched it quick because I found it, no-one else.. I stopped before the hit. Knowing it was coming. No more firestick for me. No more amazon. but before this decision, I bought the armor x5 pro, it clearly stated unlocked, as in shell access. But I could not find it. It was there all that time, and look at how many threads I attempted. No one really showed interest. Then I discover boot-debug.img, and well...

After reading so many dis-heartening thread's saying my fone was android 9 got me. I could not load any twrp, now I know why. I could not use magisk Now I know why. I never did dis magisk, I simply stated it wont work, and magisk is finito as stated by john wu sa.

I believe him. Because I now know why.

I tried everything to get root. No joy. Because I trusted software, Ultracompare stated the boot.img and boot-debug.img were identical. Yeah, the encryption is. The encryption disguises the fact boot-debug is actually variant=eng.

Ultracompare or hexedit show variant=user in both bootloaders, so yeah, my fone lies.

But why when I solve my problem, my own way, does everyone get upset?

Ah, because it shows 2 things.

Root with no magisk

That magisk kills.

Now that I cant explain.

It's just an old app I guess... fit for the fones google will deem eol shortly...
 

optimumpro

Senior Member
Jan 18, 2013
6,754
14,234
This is if I understand correctly manufacturer mistake with leaked (signed?) boot debug image.
No. It's not manufacturer's signed. He probably compiled it from manufacturer's sources with 'debug' flag, but that won't give you root, it will only give you adb_debug root, as most custom roms do. His boot.img won't boot on locked bootloader. Nor would it pass Safetynet. It actually achieves nothing. As I said, every custom user_debug rom has adb_root feature, but not root.
 

Dileas

Member
Feb 25, 2013
43
5
Did you know....

A few years back, when alcohol 120% came out, I downloaded a dvd that turned out to be corrupt. The image supplied by Alcohol 120% always came with an mdf file, and the disk image itself. Mdf is actually the md5 hash of the dvd.

When attempting to burn disk, I accidently chose the mdf, (md5 hash) instead of the actual disk image, and it turned out that the mdf hash reproduced the disk image byte for byte.

In otherwords, the 4.7gig dvd image was never necessary. That's 4.7gig reproducable from an md5 hash of say 100kb in size.

Now imagine this in fones. Dont store the file, store it's hash.

The CIA hate me now...

{Mod edit: Disrespectful part removed - Regards Oswald Boelcke}


You should have just started with that, so that everyone would know to ignore the rest of your comments.
 
Last edited by a moderator:
  • Like
Reactions: allenrb2

Pachacouti

Senior Member
Jul 8, 2020
232
44
52
The Capital above the Lower one...
{Mod edit} stock boot-debug = adb root... no mistake... patched with su thus:

Manually install meefiks su.apk, dont attempt to install it, instead, top right, save flashable x64.zip, then into twrp to flash it, after mounting /system_root/, reboot, su-pro to update, flash magisk'd boot to grant su permissions, in gui, uninstall magisk, install busybox, reboot bootloader to reflash back to debug-boot. njoi knowing I dont have magisk, and thanks to systemrw, can reflash stock and recovery back and the su root works.

{Mod edit}

It's a genuine stock rom.

{Mod edit}

Think I'll make a hybrid bootloader...
 
Last edited by a moderator:
Moderator Announcement

Thread has been cleaned! First, I've to apologise that my actions last longer than originally expected but I've to admit that for a non-native English tongue like me it was partially difficult to read or understand the provided information. Second, I'd like to mention that my actions were solely driven and guided by the XDA Forum Rules and completely unaffected by my personal opinion about the thread's subject.

While we encourage lively and vivid discussions, exchanges of opinions, experiences, knowledge and news, we always expect that this occurs within the left and right arc of the forum rules especially regarding member conduct. Just by the topic of the thread, such a spirited discussion could be expected, and it proved to become true. Unfortunately, the exchange of arguments was too often (and just once is one time too much) accompanied by statements of disrespect and profanity in argumentative and self-righteous posts. Whenever possible, I've partially edited posts but I couldn't also avoid to delete a very few ones.
My intention is not to stop any discussion of this subject but please share your opinions without personal attacks and in the most objective manner! Some of the things I've read make me to remind everybody that you're fully responsible for your posts and we don't grant any insanity defense if you post under the influence of alcohol or other drugs.

So, briefly a reminder what we expect: No profanity, sexually explicit language or other offensive content toward members or their work, which includes general statements about developers. XDA is and will always remain a website by developers for developers in first priority. Flaming or posting with a lack of respect is unacceptable. Same applies to posts in a demanding, argumentative, disrespectful or self-righteous manner. Zero tolerance to personal attacks, racial, political and/or religious discussions.

2. Member conduct.

2.1
Language: XDA is a worldwide community. As a result, what may be OK to say in your part of the world, may not be OK elsewhere. Please don't direct profanity, sexually explicit language or other offensive content toward Members or their work. Conversely, while reading posts from other members, remember that the word you find offensive may not be offensive to the writer. Tolerance is a two-way street.

2.2 Nudity: XDA is used by people of all ages, including minors. It is unacceptable to post nude or pornographic imagery, which includes the exposure of male or female genitalia and / or female breasts.

2.3 Flaming / Lack of respect: XDA is about sharing and this does not involve virtual yelling (flaming) or rudeness. Flaming or posting with a lack of respect is unacceptable. Treat new members in the manner in which you would like to have been treated when you were a new member. When dealing with any member, provide them with guidance, advice and instructions when you can, showing them respect and courtesy. Never post in a demanding, argumentative, disrespectful or self-righteous manner.

2.4 Personal attacks, racial, political and / or religious discussions: XDA is a discussion forum about certain mobile phones. Mobile phones are not racial, political, religious or personally offensive and therefore, none of these types of discussions are permitted on XDA.

2.5 All members are expected to read and adhere to the XDA rules.
Thanks very much for your cooperation and understanding! I've now subscribed to this thread, and in future I'm going to directly approach any member if moderator action is warranted. I remain available for your questions and/or comments via PM (do not reply in-thread), or you can reach us through the report system.

Respectfully
Oswald Boelcke
Senior Moderator
 

munjeni

Senior Member
Jun 2, 2011
9,445
22,041
Did you know....

A few years back, when alcohol 120% came out,
Alcohol is come out almost or more than 15 years ago!

That's 4.7gig reproducable from an md5 hash of say 100kb in size.
Poor levels of knowledge. You can't produce file from md5 hash thats not possible! Its possible bruteforcing something small but nobody use md5 for that purpose. Mdf is something diferent than md5.

Now imagine this in fones. Dont store the file, store it's hash.
Do you realy think why would there be compression algorithms in archivers, audio files, video files... etc if you think it can be done with a hash? You messed something. Hashes is something diferent! I can suggest you to read this -> https://en.wikipedia.org/wiki/Cryptographic_hash_function

Think I'll make a hybrid bootloader...
boot.img or boot-debug.img IS NOT bootloader.

This topic is bragging and nothing else.
 
Last edited:
  • Like
Reactions: Full House

Pachacouti

Senior Member
Jul 8, 2020
232
44
52
The Capital above the Lower one...
Moderator Announcement

Thread has been cleaned! First, I've to apologise that my actions last longer than originally expected but I've to admit that for a non-native English tongue like me it was partially difficult to read or understand the provided information. Second, I'd like to mention that my actions were solely driven and guided by the XDA Forum Rules and completely unaffected by my personal opinion about the thread's subject.

While we encourage lively and vivid discussions, exchanges of opinions, experiences, knowledge and news, we always expect that this occurs within the left and right arc of the forum rules especially regarding member conduct. Just by the topic of the thread, such a spirited discussion could be expected, and it proved to become true. Unfortunately, the exchange of arguments was too often (and just once is one time too much) accompanied by statements of disrespect and profanity in argumentative and self-righteous posts. Whenever possible, I've partially edited posts but I couldn't also avoid to delete a very few ones.
My intention is not to stop any discussion of this subject but please share your opinions without personal attacks and in the most objective manner! Some of the things I've read make me to remind everybody that you're fully responsible for your posts and we don't grant any insanity defense if you post under the influence of alcohol or other drugs.

So, briefly a reminder what we expect: No profanity, sexually explicit language or other offensive content toward members or their work, which includes general statements about developers. XDA is and will always remain a website by developers for developers in first priority. Flaming or posting with a lack of respect is unacceptable. Same applies to posts in a demanding, argumentative, disrespectful or self-righteous manner. Zero tolerance to personal attacks, racial, political and/or religious discussions.

2. Member conduct.

2.1
Language: XDA is a worldwide community. As a result, what may be OK to say in your part of the world, may not be OK elsewhere. Please don't direct profanity, sexually explicit language or other offensive content toward Members or their work. Conversely, while reading posts from other members, remember that the word you find offensive may not be offensive to the writer. Tolerance is a two-way street.

2.2 Nudity: XDA is used by people of all ages, including minors. It is unacceptable to post nude or pornographic imagery, which includes the exposure of male or female genitalia and / or female breasts.

2.3 Flaming / Lack of respect: XDA is about sharing and this does not involve virtual yelling (flaming) or rudeness. Flaming or posting with a lack of respect is unacceptable. Treat new members in the manner in which you would like to have been treated when you were a new member. When dealing with any member, provide them with guidance, advice and instructions when you can, showing them respect and courtesy. Never post in a demanding, argumentative, disrespectful or self-righteous manner.

2.4 Personal attacks, racial, political and / or religious discussions: XDA is a discussion forum about certain mobile phones. Mobile phones are not racial, political, religious or personally offensive and therefore, none of these types of discussions are permitted on XDA.

2.5 All members are expected to read and adhere to the XDA rules.
Thanks very much for your cooperation and understanding! I've now subscribed to this thread, and in future I'm going to directly approach any member if moderator action is warranted. I remain available for your questions and/or comments via PM (do not reply in-thread), or you can reach us through the report system.

Respectfully
Oswald Boelcke
Senior Moderator
Soz, for my wording with some, got no time for stupid people who dont check proof before making sad statement's.. then the rest who just dont do positive... I do get carried away, thank you for keepin it clean, and real ;)
 
Status
Not open for further replies.

Top Liked Posts

  • There are no posts matching your filters.
  • 4
    Pachacouti your boot-debug.img not work for Xiaomi devices. How to make it work on other devices? Please provide universal solution so that everybody can enjoy your new discovery. Not everyone has ulefone...
    Thanks!
    Just build a boot image for your device with the userdebug buildtype set. Plenty of info on how to do that all over the interweb...

    Many custom ROMs come with it by default even.
    3
    Moderator Announcement

    Thread has been cleaned! First, I've to apologise that my actions last longer than originally expected but I've to admit that for a non-native English tongue like me it was partially difficult to read or understand the provided information. Second, I'd like to mention that my actions were solely driven and guided by the XDA Forum Rules and completely unaffected by my personal opinion about the thread's subject.

    While we encourage lively and vivid discussions, exchanges of opinions, experiences, knowledge and news, we always expect that this occurs within the left and right arc of the forum rules especially regarding member conduct. Just by the topic of the thread, such a spirited discussion could be expected, and it proved to become true. Unfortunately, the exchange of arguments was too often (and just once is one time too much) accompanied by statements of disrespect and profanity in argumentative and self-righteous posts. Whenever possible, I've partially edited posts but I couldn't also avoid to delete a very few ones.
    My intention is not to stop any discussion of this subject but please share your opinions without personal attacks and in the most objective manner! Some of the things I've read make me to remind everybody that you're fully responsible for your posts and we don't grant any insanity defense if you post under the influence of alcohol or other drugs.

    So, briefly a reminder what we expect: No profanity, sexually explicit language or other offensive content toward members or their work, which includes general statements about developers. XDA is and will always remain a website by developers for developers in first priority. Flaming or posting with a lack of respect is unacceptable. Same applies to posts in a demanding, argumentative, disrespectful or self-righteous manner. Zero tolerance to personal attacks, racial, political and/or religious discussions.

    2. Member conduct.

    2.1
    Language: XDA is a worldwide community. As a result, what may be OK to say in your part of the world, may not be OK elsewhere. Please don't direct profanity, sexually explicit language or other offensive content toward Members or their work. Conversely, while reading posts from other members, remember that the word you find offensive may not be offensive to the writer. Tolerance is a two-way street.

    2.2 Nudity: XDA is used by people of all ages, including minors. It is unacceptable to post nude or pornographic imagery, which includes the exposure of male or female genitalia and / or female breasts.

    2.3 Flaming / Lack of respect: XDA is about sharing and this does not involve virtual yelling (flaming) or rudeness. Flaming or posting with a lack of respect is unacceptable. Treat new members in the manner in which you would like to have been treated when you were a new member. When dealing with any member, provide them with guidance, advice and instructions when you can, showing them respect and courtesy. Never post in a demanding, argumentative, disrespectful or self-righteous manner.

    2.4 Personal attacks, racial, political and / or religious discussions: XDA is a discussion forum about certain mobile phones. Mobile phones are not racial, political, religious or personally offensive and therefore, none of these types of discussions are permitted on XDA.

    2.5 All members are expected to read and adhere to the XDA rules.
    Thanks very much for your cooperation and understanding! I've now subscribed to this thread, and in future I'm going to directly approach any member if moderator action is warranted. I remain available for your questions and/or comments via PM (do not reply in-thread), or you can reach us through the report system.

    Respectfully
    Oswald Boelcke
    Senior Moderator
    3
    Thats something very wrong in that phone model software, security hole. Are you getting su work while on stock boot.img or you getting it work only while having boot debug img installed? Where you have put su binary? You do not have bootloop while keeping su installed (to the system?) after relocking bootloader?
    It's joke. A good sign of a hoaxer is when he immediately jumps to effing everybody who questions his nonsense. That's a red flag that is all over this thread. {Mod edit}

    Apart from that, {Mod edit}, there is no difference between ADB root and root. In reality, debug_boot.img does not provide full root access, it only provides root access for adb commands, and even that requires system_debug image, which you will never get on stock: to have a stock system_debug, one must recompile from sources with that flag. Show me an OEM who provides sources for anything other than kernel.

    His other claim about passing Safetynet on stock with bootimage-debug is abracadabra. No phone with unlocked bootloader will pass Safetynet without modifications in framework and kernel: the frameworks usually contain the names of services and applications and kernel has the 'fooling' flags. Yeah, he can modify kernel, if he has sources, but would never be able to modify frameworks.

    {Mod edit - Regards Oswald Boelcke}
    3
    I read the docs regarding it
    Got a link? Would love to read it myself.
    3
    Moderator Announcement: Thread provisionally closed!
  • 8
    Magisk is no more...

    I present a new fool proof method of flashing su to Android 10_Q and above!!

    I ranted and ranted about variant=user/user-debug/eng builds that I got no-where... people thinkin am dissin john wu, nah, I respect what I've learnt from his app forcing me to connect online, I want su without connecting, in order to secure my own fone.

    Introducing proof!!

    Simple. Instead of flashing boot.img

    Flash boot-debug.img from stock.

    This address's the lack of adb root.

    Logs:


    D:\0\AdbStation>fastboot --disable-verity --disable-verification flash vbmeta vb
    lankmeta.img
    Rewriting vbmeta struct at offset: 0
    Sending 'vbmeta' (4 KB) OKAY [ 0.000s]
    Writing 'vbmeta' OKAY [ 0.000s]
    Finished. Total time: 0.016s

    D:\0\AdbStation>fastboot --disable-verity --disable-verification flash boot boot
    -debug.img
    Sending 'boot' (32768 KB) OKAY [ 0.764s]
    Writing 'boot' OKAY [ 0.515s]
    Finished. Total time: 1.404s

    D:\0\AdbStation>fastboot --disable-verity --disable-verification flash recovery
    MyTwrp.img
    Sending 'recovery' (26086 KB) OKAY [ 0.718s]
    Writing 'recovery' OKAY [ 0.406s]
    Finished. Total time: 1.139s

    D:\0\AdbStation>fastboot reboot-recovery
    Rebooting into recovery OKAY [ 0.000s]
    Finished. Total time: 0.000s

    D:\0\AdbStation>adb root
    adbd is already running as root

    D:\0\AdbStation>adb root
    restarting adbd as root

    D:\0\AdbStation>adb shell
    Armor_X5_Q:/ # mount -o remount,rw /system_root
    mount: '/system_root' not in /proc/mounts
    1|Armor_X5_Q:/ # mount -o remount,rw /system
    mount: '/system' not in /proc/mounts
    1|Armor_X5_Q:/ # mount -o remount,rw /
    '/dev/block/dm-1' is read-only
    Armor_X5_Q:/ # su
    /system/bin/sh: su: inaccessible or not found
    127|Armor_X5_Q:/ # ls
    acct d init.environ.rc metadata sbin
    apex data init.rc mnt sdcard
    bin debug_ramdisk init.usb.configfs.rc odm storage
    bugreports default.prop init.usb.rc oem sys
    cache dev init.zygote32.rc proc system
    charger etc init.zygote64_32.rc product ueventd.rc
    config init lost+found product_services vendor
    Armor_X5_Q:/ # cd apex
    Armor_X5_Q:/apex # ls
    com.android.apex.cts.shim [email protected]
    [email protected] com.android.resolv
    com.android.conscrypt [email protected]
    [email protected] com.android.runtime
    com.android.media [email protected]
    com.android.media.swcodec com.android.tzdata
    [email protected] [email protected]
    Armor_X5_Q:/apex # exit

    D:\0\AdbStation>adb reboot bootloader

    D:\0\AdbStation>fastboot --disable-verity --disable-verification flash recovery
    recovery.img
    Sending 'recovery' (20646 KB) OKAY [ 0.577s]
    Writing 'recovery' OKAY [ 0.312s]
    Finished. Total time: 0.889s

    D:\0\AdbStation>fastboot reboot
    Rebooting OKAY [ 0.000s]
    Finished. Total time: 0.000s

    D:\0\AdbStation>adb root
    restarting adbd as root

    D:\0\AdbStation>adb shell
    Armor_X5_Q:/ # exit

    ------------------------

    Pay attention, the first part above, I flashed a twrp...

    Below, I flash stock images... without closing adb window.
    --------------------------------------------------------------

    D:\0\AdbStation>adb reboot bootloader

    D:\0\AdbStation>fastboot --disable-verity --disable-verification flash boot boot
    -debug.img
    Sending 'boot' (32768 KB) OKAY [ 0.764s]
    Writing 'boot' OKAY [ 0.499s]
    Finished. Total time: 1.373s

    D:\0\AdbStation>fastboot --disable-verity --disable-verification flash recovery
    recovery.img
    Sending 'recovery' (20646 KB) OKAY [ 0.484s]
    Writing 'recovery' OKAY [ 0.328s]
    Finished. Total time: 0.811s

    D:\0\AdbStation>fastboot reboot
    Rebooting OKAY [ 0.000s]
    Finished. Total time: 0.000s

    D:\0\AdbStation>adb root
    restarting adbd as root

    D:\0\AdbStation>adb shell
    Armor_X5_Q:/ # su
    /system/bin/sh: su: inaccessible or not found
    127|Armor_X5_Q:/ # exit

    D:\0\AdbStation>adb shell
    Armor_X5_Q:/ # cd /system
    Armor_X5_Q:/system # cd bin
    Armor_X5_Q:/system/bin # ls

    Edit'd not relevant.. too long the things we can do list pissed one off...

    Armor_X5_Q:/system/bin #

    No MORE MAGISK!!!

    It'a a feature of Android 10 and over lol... says so in the android docs....

    who needs su when you have root?

    SYSTEM_AS_ROOT

    Voila...

    it's in the understanding.

    YouRoot
    4
    Pachacouti your boot-debug.img not work for Xiaomi devices. How to make it work on other devices? Please provide universal solution so that everybody can enjoy your new discovery. Not everyone has ulefone...
    Thanks!
    Just build a boot image for your device with the userdebug buildtype set. Plenty of info on how to do that all over the interweb...

    Many custom ROMs come with it by default even.
    3
    Moderator Announcement: Thread provisionally closed!
    3
    I read the docs regarding it
    Got a link? Would love to read it myself.
    3
    Thats something very wrong in that phone model software, security hole. Are you getting su work while on stock boot.img or you getting it work only while having boot debug img installed? Where you have put su binary? You do not have bootloop while keeping su installed (to the system?) after relocking bootloader?
    It's joke. A good sign of a hoaxer is when he immediately jumps to effing everybody who questions his nonsense. That's a red flag that is all over this thread. {Mod edit}

    Apart from that, {Mod edit}, there is no difference between ADB root and root. In reality, debug_boot.img does not provide full root access, it only provides root access for adb commands, and even that requires system_debug image, which you will never get on stock: to have a stock system_debug, one must recompile from sources with that flag. Show me an OEM who provides sources for anything other than kernel.

    His other claim about passing Safetynet on stock with bootimage-debug is abracadabra. No phone with unlocked bootloader will pass Safetynet without modifications in framework and kernel: the frameworks usually contain the names of services and applications and kernel has the 'fooling' flags. Yeah, he can modify kernel, if he has sources, but would never be able to modify frameworks.

    {Mod edit - Regards Oswald Boelcke}