Develop Bugs

Extracted ramdisk from boot.img inside RUU_Supersonic_1.32.651.1_Radio_1.39.00.04.26

I've extracted the ramdisk from the boot.img which was posted by Football in the RUU_Supersonic_1.32.651.1_Radio_1.39.00.04.26 file.
This contains all the bootable files which are executed once the kernel loads...
to extract all the files from the ramdisk
normally, these are the commands:
mkdir ramdisk
cd ramdisk
gzip -dc ../boot.img-ramdisk.gz | cpio -i
BUT for some reason between my uploading and the host, the .gz gets corrupted. i put all the files into a .tar
tar -xvf EVO-stock-ROM-ramdisk.tar
http://www.joeyconway.com/evo/kernel/EVO-stock-ROM-ramdisk.tar
this is the directory listing from the ramdisk (yea im using my moment dev environment...)
[email protected]:~/evo/updates/dst/boot/ramdisk$ ls -l
total 168
-rw-r--r-- 1 moment moment 216 2010-05-22 16:23 bootcomplete.supersonic.rc
drwxrwx--x 2 moment moment 4096 2010-05-22 16:23 data
-rw-r--r-- 1 moment moment 118 2010-05-22 16:23 default.prop
drwxr-xr-x 2 moment moment 4096 2010-05-22 16:23 dev
-rwxr-x--- 1 moment moment 103548 2010-05-22 16:23 init
-rwxr-x--- 1 moment moment 1677 2010-05-22 16:23 init.goldfish.rc
-rwxr-x--- 1 moment moment 14403 2010-05-22 16:23 init.rc
-rwxr-x--- 1 moment moment 4840 2010-05-22 16:23 init.supersonic.rc
drwxr-xr-x 2 moment moment 4096 2010-05-22 16:23 proc
drwxr-x--- 2 moment moment 4096 2010-05-22 16:23 sbin
-rw-r--r-- 1 moment moment 75 2010-05-22 16:23 shutdown.supersonic.rc
drwxr-xr-x 2 moment moment 4096 2010-05-22 16:23 sys
drwxr-xr-x 2 moment moment 4096 2010-05-22 16:23 system
Edit: To flash kernels on the EVO, I created a simple app: FlashImageGUI - http://forum.xda-developers.com/showthread.php?t=1083260

i can't download this, it give me a error saying file is damaged

super-6-1 said:
i can't download this, it give me a error saying file is damaged
Click to expand...
Click to collapse
wow, good catch. im not sure why its being corrupted so i made all the files and directory into a .tar!
thanks for the feedback!

there are a few scripts to do what uve done here. 1) extract-ramdisk.pl and 2) split-bootimg.pl. there are a few others but these are the two i choose to use. anyhow it looks like a normal ramdisk from a snapdragon device.

toastcfh said:
there are a few scripts to do what uve done here. 1) extract-ramdisk.pl and 2) split-bootimg.pl. there are a few others but these are the two i choose to use. anyhow it looks like a normal ramdisk from a snapdragon device.
Click to expand...
Click to collapse
sweet, i used split-bootimg.pl, worked great. im new to all this so im very glad we're on the same page!
what kind of tools do we have to put a modified boot.img back onto the EVO?

Could we update the boot.img by utilizing the ROM Update Utility functionality--by flashing an updated .nbh to the phone?

joeykrim said:
sweet, i used split-bootimg.pl, worked great. im new to all this so im very glad we're on the same page!
what kind of tools do we have to put a modified boot.img back onto the EVO?
Click to expand...
Click to collapse
google "rom cooking lox" and ull find all u need to know about it

toastcfh said:
google "rom cooking lox" and ull find all u need to know about it
Click to expand...
Click to collapse
thanks! i googled it and found this thread
http://htcpedia.com/forum/showthread.php?t=1404
and then a thread of yours linking back to that thread.
from what i've read in that thread and other threads, using the recovery on the phone to apply an update.zip which we create and sign, seems to be the most common method to update the phone with our own ROM.
i have one question. will the stock recovery on the EVO apply the update.zip i build and sign? or do we need a custom recovery before we can apply our update.zip files we've built and signed?
also for anybody with an EVO, feel like testing? im willing to work and create a custom update.zip which I think should give us root, I have a few different methods in mind from my last rooting experience of an Android phone,the samsung moment android 2.1 upgrade, a few weeks ago...but its really hard for me to know never having used or seen the HTC android platform and not having the EVO until the 4th...
i wish i had an EVO to test with...!

joeykrim said:
thanks! i googled it and found this thread
and then a thread of yours linking back to that thread.
from what i've read in that thread and other threads, using the recovery on the phone to apply an update.zip which we create and sign, seems to be the most common method to update the phone with our own ROM.
i have one question. will the stock recovery on the EVO apply the update.zip i build and sign? or do we need a custom recovery before we can apply our update.zip files we've built and signed?
also for anybody with an EVO, feel like testing? im willing to work and create a custom update.zip which I think should give us root, I have a few different methods in mind from my last rooting experience of an Android phone,the samsung moment android 2.1 upgrade, a few weeks ago...but its really hard for me to know never having used or seen the HTC android platform and not having the EVO until the 4th...
i wish i had an EVO to test with...!
Click to expand...
Click to collapse
I believe that the current SPL will only run signed HTC updates, and that the common attack vector is to find a way to overwrite the default SPL with a custom widget in order to disable checks for signed updates and other annoyances. (please correct me if I'm wrong!)
My question I'm trying to figure out now is how does HTC sign the ROMs?

andrew500 said:
I believe that the current SPL will only run signed HTC updates, and that the common attack vector is to find a way to overwrite the default SPL with a custom widget in order to disable checks for signed updates and other annoyances. (please correct me if I'm wrong!)
My question I'm trying to figure out now is how does HTC sign the ROMs?
Click to expand...
Click to collapse
They take their private key and sign it...

This is mindboggling, nonetheless.
Oh the joy.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

[Hack][Root] SIM Unlock for FREE - Info required

Hi,
I am currently residing on the One S forums (don't have a One V), and have found (in conjunction with jh787) a working method of SIM unlocking the One S for free.
The method may also be applicable to the One V.
Part of the trick is obtaining an UN_Lock-code stored on the phone. On the One S this is found as follows:
1) You need root
2) You need Terminal Emulator (free from the market)
Open the Terminal Emulator app and type:
su [enter]
strings -n 8 /dev/block/mmcblk0p6 [enter] (or maybe mmcblk0p7 on the One V)
It will output several lines of data.
One the One S, towards the bottom are 2 lines. One contains your IMEI number, the other reads UN_Lock_code=063312345 (for example)
This is NOT the SIM unlock code - don't use it!
I believe that the One V uses a different partition structure, so the correct data may not be in the mmcblk0p6 block.
If anyone can tell be the correct block for the One V, I will test the hack on your device and, if possible, provide a free sim unlock hack for the One V.

For One S, what is this mmcblk0p6 referring to ?
Below is One V partition structure:
mmcblk0p17: misc
mmcblk0p21: recovery
mmcblk0p22: boot
mmcblk0p25: system
mmcblk0p28: cache
mmcblk0p26: userdata
mmcblk0p29: devlog
mmcblk0p31: pdata
mmcblk0p30: extra
mmcblk0p32: fat
mmcblk0p27: swap

ckpv5 said:
For One S, what is this mmcblk0p6 referring to ?
Click to expand...
Click to collapse
Good question - I have absolutely no idea!!

I found the IMEI number in block mmcblk0p7 but I didn't find the UN_Lock_code string. Maybe thats because mine is not SIM locked.

hlavicka82 said:
I found the IMEI number in block mmcblk0p7 but I didn't find the UN_Lock_code string. Maybe thats because mine is not SIM locked.
Click to expand...
Click to collapse
That may well be the case. Have added a note in the OP. Can other users try mmcblk0p7 and report..
Here is my TE output from that block which shows what you are looking for.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
From other reports, I believe that the code may not exist in a factory-unlocked phone (only a carrier-locked one).
This method may help to search for the right string.

if the code is not under or above the ime code , its suposed to have a date instead, that means that the unlock code is not in the device

any news? i really need it!

this is good idea of a thread! i was about to pay for this, if someone can crack it i will donate him the payment i ment to pay for it

I have a partially locked one v (it is locked on Orange carrier - but it is confirmed as working with a Cosmote AND Vodafone carrier). Is this method working? I want to know because I want to root the thing and if I don't find a good method to unlock it I may as well go with it to service center. It's only 1 day old. Cheers

Tested, it doesn't work. Here's why:
"sh: strings: not found".
Cheers!
This is on stock version. So i guess I need to push the 'strings' in /system/bin

1ceb0x said:
I have a partially locked one v (it is locked on Orange carrier - but it is confirmed as working with a Cosmote AND Vodafone carrier). Is this method working? I want to know because I want to root the thing and if I don't find a good method to unlock it I may as well go with it to service center. It's only 1 day old. Cheers
Click to expand...
Click to collapse
This method is not yet working on the One V. We still do not know where the UN_Lock_code resides (If it is there at all - it is not on the mmcblk0p6 block). If your phone works with 3 different sim cards, however, it is not SIM-locked!
1ceb0x said:
Tested, it doesn't work. Here's why:
"sh: strings: not found".
Cheers!
This is on stock version. So i guess I need to push the 'strings' in /system/bin
Click to expand...
Click to collapse
The strings command seems to work only if you have busybox installed. It will work on most custom ROMs but not on stock unless you have installed busybox manually.

I have busybox installed. I've pushed strings to /system/bin and now I'll run the command. I don't know if this works or not because no one with an unlocked sim has tried it and said it was good or not.

i found this
mmcblk0p7
ORANGB10
00000168
3518160590368500
QCT_UMTS_RADIO_VER=1
HSDPACat=10
HSUPACat=6
QCT_UMTS_RADIO_END=1
&<2jz12F
wi5zz/z 0^
09/46i_6
574908040
00000006
574908040
&<2jz12F
wi5zz/z 0^
09/46i_6
""##$%&(*+-0368;
!"#$%&(*,/26:>CG
&!&2&D&U&g&x&
7$H$Z$k$}$
&0&H&S&d&v&
!"#$%&(*,/26:>CG
,.037;AGNV`lz
[email protected]:/ #

did anyone made some progress or found any other way for software based unlocking?
I was wondering how does this unlocking sites get their codes anyway,i am sure they dont have a deal with carriers or HTC of any sort,so there must be a way to find out the codes by our selves...adb,or some tool perhaps,idk
Reason i am posting this question is that i got no means to pay anything through internet due to not having a paypal system where i live and dont have a credit card too.
Also i would like to bring some DEVELOPERS attention to this.
If i find a way i am going to post it here for sure,if someone can help,please do PM me or answer in this thread.
Thanks.

Here is my output:
I've loceted the IMEI, but nothing seems like the "unlock".
[email protected]:/ # strings -n 8 /dev/block/mmcblk0p7
strings -n 8 /dev/block/mmcblk0p7
HTC__032
00000168
(IMEI removed)
QCT_UMTS_RADIO_VER=1
HSDPACat=10
HSUPACat=6
QCT_UMTS_RADIO_END=1
fnq!` Z!
[email protected]
[email protected]|]ze
574908040
00000001
574908040
fnq!` Z!
[email protected]
[email protected]|]ze
""##$%&(*+-0368;
!"#$%&(*,/26:>CG
&!&2&D&U&g&x&
7$H$Z$k$}$
&0&H&S&d&v&
!"#$%&(*,/26:>CG
,.037;AGNV`lz

found this on mmcblk0p18, but I don't know if it belongs to bootloader or simlock. (my phone has no simlock)
Code:
strings -n 8 /dev/block/mmcblk0p18 | grep -i unlock
unlocktoken
INFOunlock token check successfully
FAILunlock token check failed
*** UNLOCKED ***
[SIMLOCK_ERR] Unlock SIM card by smart card fail!!!
Unlock SIM card by smart card fail!!!
UnlockCode=[%s]
unlock memory
clearsimlocktype: UnlockSimLockbySmartCard failed
clearsimlocktype: UnlockSimLockbySmartCard success!!!
Device was already unlocked!
[RADIO_ERR] UnLockcode length %d error!
[RADIO_ERR] Unlock SimLock by SmartCard NG
setunlock_status
setunlock_unlock
setunlock_lock
setunlock_relock

TechnoLover said:
found this on mmcblk0p18, but I don't know if it belongs to bootloader or simlock. (my phone has no simlock)
Click to expand...
Click to collapse
I guess this should be useful. Can anyone with a sim locked try this in block 18 and see if it gives you different output?

my mouse wont let me select stuff so here's a screenie of my output simlocked

Lloir said:
my mouse wont let me select stuff so here's a screenie of my output simlocked
Click to expand...
Click to collapse
same here (output)
from the string sytax, I think that adr.18 is a string container for the bootloader
Have tried the tool from here but nothing looks like the unlock code from the partitions of the script.
Seems like form the One series only the S can be unlocked this way as of now. Nor the X, XL, threads says anything new.

Ken-Shi_Kun said:
same here
Click to expand...
Click to collapse
oh no mine's broken broken left click is damaged

[DEPRECATED][GUIDE][ROOT] Smartwatch 3 KNX01V

I removed download link due to this method not working on lollipop.
This guide is deprecated, please use TWRP Recovery from this thread to install root
DISCLAMER and WARNING: I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or the current economic crisis. Please do some research if you have any concerns about this app.
Click to expand...
Click to collapse
You have been warned!
Links:
Sony PC Companion
Download link removed while I will test for compatibility with 5.x, md5 summ: e2c34b07faa415a6cbb95943649c7eba
Step 1:
Code:
[URL="source.android.com/source/building-devices.html#unlocking-the-bootloader"]Unlocked bootloader[/URL]
1. Enable adb debug
2. adb reboot bootloader
3. fastboot oem unlock (twice if requested)
4. fastboot format cache
5. fastboot format userdata
6. fastboot getvar all (and verify that it is)
7. fastboot reboot
Step 2:
Code:
Updated to the latest KNX01V
[URL="http://www.sonymobile.com/us/tools/pc-companion/"]Install Sony PC Companion[/URL] and use Supports Zone -> Accessories software update -> Smartwatch 3
Step 3:
Code:
Have Flashboot (Sony s1 flash) drivers installed just in case (Install Sony PC Companion and do update as indicated in previous step)
Step 4:
Code:
[COLOR="red"]BOOT [/COLOR][COLOR="Red"](DO NOT EVER FLASH IT!!!)[/COLOR] rooting boot.img
1. Download rooting kernel image (SWR50-rootboot.img)
2. Reboot into bootloader (adb reboot bootloader)
3. fastboot boot SWR50-rootboot.img
4. Wait till device reboots or sits in black screen for a while (1 min+ then reboot it by holding power 10+sec)
Step 5:
Code:
Verify by:
1. adb shell
2. su
3. you should see [email protected]:/ #
Step 6:
Code:
1. Let me know!
2. Use it, dive into GPS investigation or customizations, etc.....
Special thanks:
1. Justin Case for LG G Watch rooting method using LGGW-rootboot.img
2. osm0sis for Android Image Kitchen
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

reserved

How it works:
1. Each boot.img packs zImage (real kernel) and ramdisk (special files for kernel use)
2. This one has all modifications from LGGW rootboot by Justin Case:
a. Adds su binary, superuser.sh install script, modified install-recovery.sh and additional step into init.rc file to invoke superuser.sh install script. Also modifications to mount system as rw and some disabled security.
3. So basically it mount system as rw and does following (cut from superuser.sh install script):
Code:
#!/system/bin/sh
/system/bin/mount -o remount,rw /system
/system/bin/sleep 2
/system/bin/cat /sbin/su > /system/xbin/su
/system/bin/cat /sbin/su > /system/xbin/daemonsu
/system/bin/cat /sbin/install-recovery.sh > /system/etc/install-recovery.sh
/system/bin/chown 0.0 /system/xbin/su
/system/bin/chown 0.0 /system/xbin/daemonsu
/system/bin/chown 0.0 /system/etc/install-recovery.sh
/system/bin/chmod 06755 /system/xbin/su
/system/bin/chmod 06755 /system/xbin/daemonsu
/system/bin/chmod 755 /system/etc/install-recovery.sh
/system/bin/sync
/system/bin/sleep 3
/system/bin/reboot

I have dumped the rom from my debug/test version and was wondering if you were able to give me a guide on how i could try and flash it with a retail version? I presume this root guide probably won't work for me

Well, if hardware and partitions are the same - I do not see why it will not work. However, it will not help to flash.
I might try to compile twrp, but will have to carefully read its docs first.

thanks @XorZone confirmed as working and a nice easy process too (I was already unlocked).
Out of curiosity, modded LGGW rootboot or just renamed?

iBuzman said:
thanks @XorZone confirmed as working and a nice easy process too (I was already unlocked).
Out of curiosity, modded LGGW rootboot or just renamed?
Click to expand...
Click to collapse
Thanks for letting me know!
I reverse engineered changes in LGGW by unpacking and comparing ramdisks from both rootboot and original lg kernel and then applied the same changes to our kernel extracted from PC Companion files.

great thinking and good job ?
btw, that pic confirmed su access to watch over bluetooth debug connection ?

really great tutorial. I am planning to buy this watch, but I think currently there is NO app that requires Root. so I wonder how can we get benefit of this ?

Kurotsuchi said:
really great tutorial. I am planning to buy this watch, but I think currently there is NO app that requires Root. so I wonder how can we get benefit of this ?
Click to expand...
Click to collapse
There is at least Wear Control app: https://play.google.com/store/apps/details?id=octathorp.wearcontrol
I plan to code density changer that will require access to adb, so either from rooted phone or rooted wear.

Kurotsuchi said:
really great tutorial. I am planning to buy this watch, but I think currently there is NO app that requires Root. so I wonder how can we get benefit of this ?
Click to expand...
Click to collapse
how to benefit?
root apps of course!!
(sry for bad pic, unlocked bootloader z3 in low light [emoji12]

XorZone said:
There is at least Wear Control app: https://play.google.com/store/apps/details?id=octathorp.wearcontrol
I plan to code density changer that will require access to adb, so either from rooted phone or rooted wear.
Click to expand...
Click to collapse
that's awesome man! will purchase mine next week, can't wait to root it. thanks for the answer.

Thanks for the root, XorZone. For anyone wondering, here's the dmesg of the watch
A few small observations from digging:
The main chipset seems to be the BCM23550
The CPU has 4 cores, 2 are disabled in software. Should be easy enough to reenable if you please
It definitely has WiFi hardware, but the firmware is currently missing from the image. If you mange to get a hold of compatible firmware and nvram, it should be simple enough to get WiFi up and running
The WiFi firmware message mentions a "43341". Which is odd because apparently the main chipset does have WiFi support built in. Searching for a Broadcom 43341 gives you this, but this might just be a red herring.

cb22 said:
Thanks for the root, XorZone. For anyone wondering, here's the dmesg of the watch
A few small observations from digging:
The main chipset seems to be the BCM23550
The CPU has 4 cores, 2 are disabled in software. Should be easy enough to reenable if you please
It definitely has WiFi hardware, but the firmware is currently missing from the image. If you mange to get a hold of compatible firmware and nvram, it should be simple enough to get WiFi up and running
The WiFi firmware message mentions a "43341". Which is odd because apparently the main chipset does have WiFi support built in. Searching for a Broadcom 43341 gives you this, but this might just be a red herring.
Click to expand...
Click to collapse
Yeah, I noticed the same about WiFi chip, it might be that they packed bcm43341 as part of the BCM23550 soc, like Invensense MPU9250 chip packs mpu6500 inside.
For the 43341 I'm finding it in the configs here: https://android.googlesource.com/kernel/tegra/+/bdde9f16131a5ac2039062d5ce22e3e153acbe68^!/
Looks like BCM43341 is BCM4334 + NFC chip, so we could try S3 I9300 files as per http://redmine.replicant.us/projects/replicant/wiki/GalaxyS3I9300Firmwares

how can i grant superuser permission to an app? i install es file explorer with sideload but i can't get superuser permission. the procedure is ok

Sorry admins for not putting in correct location....
Moved to Correct Area!

cdrshm said:
Sorry admins for not putting in correct location....
I can not get my device to show up in adb devices and its driving me crazy. Tried windows 7/8/server 2012R2 ..lol
Now I have done my fair share of custom roms and bootloaders.
OG Droid
Nexus
Nexus 10
Asus Memo Pad (came from alarm company, and could only load one app...now its a full running tablet)
I am sure its a silly thing I have done or am missing...
Thoughts....ideas?..need more info?
Click to expand...
Click to collapse
As usual, check if adb enabled in settings-about-developer options, if there are no developer options - it is as usual 7 times click on build number in about screen.

And please use Q&A thread for such questions

I've confirmed root survives the Lollipop update

Wow, I was out whole weekend, will have to catch up with the update

[DISCOVERY] Looking for info to try to support recovery on International honor 5X

If you're in the USA, TWRP and root are available for you here - but only if you have the KIW-L24 model:
[TWRP] for KIW-L24 USA (kiwi)
^^ That recovery is not recommended or tested for any version other than KIW-L24 as of February 10, 2016.
So here's the situation:
We may be able to support other versions for international users
We make no promises
We are providing a tool and instructions for you to give us the information we need about your version
We make no promises
You MUST give the information exactly as we request
No personal information is being gathered - none
We've made it as easy as possible, you don't have to be an expert
We may have to come back and ask you for more information
We make no promises
But we are willing to try if you want to help
Instructions:
Download the attached zip file and unzip it on your phone - ES File Explorer or equivalent is fine
Run the script: find-honor.sh
Copy the contents of /sdcard/found-honor.txt to http://hastebin.com
Post the link to your hastebin here in the thread
DO NOT post the output here - we're not going to manage to that - only post your hastebin.com link, ok
You may run the script however you like:
adb shell or Terminal Emulator
or just use SH Script Runner (instructions on that will come later in the thread)
Shell/terminal instructions:
cd to the folder where you unzipped the script
Execute the following command:
source find-honor.txt
How to upload:
Go to the found-honor.txt file in your file browser
/sdcard, /storage/emulated/0 and Internal Storage all mean the same thing on your phone
Open, select all, copy
Paste and save to hastebin.com
Pictures follow, in my example I use the built-in Files app
Go to the internal storage, tap on find-honor.txt
OK to open Just Once with HTMLViewer
Long press any word to get menu on bottom
Select all, then copy
Goto http://hastebin.com and paste
Find the disk image in the upper right corner to save
Post the link
Your output will look similar to http://hastebin.com/norufikubu.avrasm
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
SH Script Runner Instructions:
Load the file as shown in the pictures
Run it with the little run button next to the name in the top bar
Post results to hastebin using instructions above
DOWNLOAD SCRIPT HERE:
View attachment find-honor.sh.zip

If you're curious to see the how the information is being gathered:
Code:
#!/system/bin/sh
#
# Find honor 5X properties for recovery exploration
# EarlyMon 2016/02/08
TARG=/sdcard/found-honor.txt
getprop | grep -i ro.build.product > $TARG
echo "" >> $TARG
grep -i msm /system/build.prop >> $TARG
echo "" >> $TARG
cat /proc/meminfo | grep -i memtotal >> $TARG
echo "" >> $TARG
cat /proc/partitions >> $TARG
echo "" >> $TARG
cd /sys/dev/block
for i in 179:*
do
cat $i/uevent | grep NAME >> $TARG
echo "" >> $TARG
done
cd - > /dev/null
df >> $TARG 2> /dev/null
echo "" >> $TARG
cat /proc/self/mountinfo >> $TARG
echo "" >> $TARG
cat /system/build.prop >> $TARG
echo ""
echo "Copy the contents of"
echo ""
echo "$TARG"
echo ""
echo "to hastebin.com"
echo ""
echo "Post the hastebin.com link in the thread."
Remember -
ONLY POST YOUR DATA LINK, LIKE THIS:
http://hastebin.com/norufikubu.avrasm
You can see from my sample link that nothing personal is being gathered.

Happy to help
Hope this helps:
/eqokatoboh.md
If this is against the rules, then delete it.
Have a nice day
Widos

WidosFTW said:
Hope this helps:
/eqokatoboh.md
If this is against the rules, then delete it.
Have a nice day
Widos
Click to expand...
Click to collapse
http://hastebin.com/eqokatoboh.md
That works, thanks.
That's a 2/16 KIW-L21

Run Script with SH Script Runner
hastebin. com / ujotesawow.md
Im a new user so i cant post links

racing2410 said:
Run Script with SH Script Runner
hastebin. com / ujotesawow.md
Im a new user so i cant post links
Click to expand...
Click to collapse
Welcome to the forums.
http://hastebin.com/ujotesawow.md
Another 2/16 KIW-L21 - thanks!

@WidosFTW or @racing2410
Per suggestions from the team (shm and Ncypt3d) after reviewing your data, we've decided to update the script because we don't want to take the chance relying on the honor website specs.
Please refer to the following picture from the app CPU-X in the Play Store:
The top of yours ought to be similar and say MSM 8939 HUAWEI KIW-L21 (where mine says L23).
If there is any doubt, please erase the old find-honor.sh on your phone, get the new copy from the OP, and repeat the process for us.
Many thanks!

ok lets see
hastebin /ereyaronoh.avrasm

Done it @EarlyMon
/oqiqemojer.avrasm

http://hastebin.com/ereyaronoh.avrasm
http://hastebin.com/oqiqemojer.avrasm
Perfect, just what we expected, thanks!

I'm on the US version but still appreciate that you're working on our international brothers and sisters 5xs. So I must say....this sounds "very promising "! Sorry I couldn't help it.

WidosFTW said:
Done it @EarlyMon
/oqiqemojer.avrasm
Click to expand...
Click to collapse
racing2410 said:
ok lets see
hastebin /ereyaronoh.avrasm
Click to expand...
Click to collapse
From what i can tell from the info provided the L24 twrp recovery should work on L21.
Here is the official L24 twrp:
https://dl.twrp.me/kiwi/twrp-3.0.0-0-kiwi.img.html
Stock L21 recovery encase it does not work:
https://www.androidfilehost.com/?fid=24411628330025737
If there is a error please put as much info as you can get and pictures if possible. Also attach a recovery.log so we can double check everything is working.

ok i will try to flash the recovery after work. first i have to unlock my bootloader :angel:

deadman96385 said:
From what i can tell from the info provided the L24 twrp recovery should work on the L21.
If there is a error please put as much info as you can get and pictures if possible. Also attach a recovery.log so we can double check everything is working.
Click to expand...
Click to collapse
The installation works fine and it also starts the twrp but you cant use it properly because you get the touchscreen error, which was already described in the US Thread. I dont know where the recovery.log is so I cant post it here. I somehow managed to install root but I would consider this unusable.
Edit:
Found the log, it is in the attachments.

Can confirm. Installing TWRP was fine, but it can't be used (touchscreen does not recognize input)

LordKelsier said:
Can confirm. Installing TWRP was fine, but it can't be used (touchscreen does not recognize input)
Click to expand...
Click to collapse
You mentioned that you were able to use the debloat method on your KIW-L21.
Did something change on the touchscreen usability or can you elaborate for the benefit of us and others?

EarlyMon said:
You mentioned that you were able to use the debloat method on your KIW-L21.
Did something change on the touchscreen usability or can you elaborate for the benefit of us and others?
Click to expand...
Click to collapse
Someone in the main thread posted that you have to tap the screen extremely fast and that the issue is most likely a bug in the TWRP software (not waiting long enough for user input or something). It worked this way but is extremely luck based. Like I had to try and flash the zip file 10 times before I was able to slide the slider while not having the archive validation checkbox checked.
Selecting the "install" button and the archive itself also took a few minutes. Basically you'll have to hammer your screen at 5 touches per second or something for it recognize

Same with me it took me about an hour to get it working.

We've been discussing the touchscreen among ourselves and your feedback may help - thanks!
Sent from my KIW-L24 using XDA Free mobile app

Do you still need ppl to run the script for the L21?

How to Root | Degoogle (enable Sig Spoofing) on Galaxy S20FE (Qualcomm)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hello Guys/Girls/Non-Binary this should just be some Tutorial because I didn't find a lot about this on xda.
I have Twrp installed check out this thread on how to do it: TWRP FOR S20 FE EXYNOS
TWRP KEY COMBO: Power + VolUP
I will give you the download-link of the right version of the Twrp if you have the SM-G780G because i feel no one has it and searching comments is kinda bothering.
Twrp for SM-G780G (dunno if it works on others but should) is in attached Files on This Post.
This Version of Twrp has a small "bug" or a kinda non see able feature because it doesn't give you a GUI thing for enable Write-Rights in "/system_root" if you are a n00b don't worry explain later.
First of all you need adb and linux is kinda good because i don't know on how to do some zip things in Windows (and it kinda sucks anyway but don't cry )
So the real tutorial starts here (you HAVE TWRP and a boootable system right now) if not check the link i gave you.
First of all you root the phone (You can skip this step if you don't want root rights):
Download Magisk-Zip : Magisk Zip
Connect the Phone and your PC and put the magisk.zip on your phone. -> In Twrp go to install -> Click Magisk.zip.
Wait and some mad voodo magic from your Lord and Savior topjohnwu: https://forum.xda-developers.com/m/topjohnwu.4470081/
appears and you're rooted.
So this is the more complicated part of the tutorial (because we only have android 11 on this phone we need to kinda manually deodex you're services.jar I did a tutorial on that here:
Sig Spoofing on Android 11
You can use the exact same steps!!
short description: download haystack11-attempt, dexpatcher, the zip you need to rename, - pull and deodex your services.jar - flash the zip in Magisk!!
After that boot in system install fdroid (put the apk from your PC to the phone install via Samsung-files or some other app) download signature-spoof checker from fdroid and give the permission if that works youre good to go.
Go in Magisk -> Reboot to Recovery (Or Reboot in Twrp with Key-Combo)
Now we are debloating (the de-bloat in /system_root is necessary the pm uninstall commands and i will add them later forgot to write down and I'am always high(so i forgot them) also they are optional) for real you could de-bloat a lot more here but I doesn't wanna ruin camera app and things real Samsung boys will know what i talk about. but if you have better de-bloating options go and comment!
System_root de-bloat necessary:
adb shell
# Samsung ****
rm /system_root/system/app/ARZone/ARZone.apk
rm /system_root/system/app/BixbyWakeup/BixbyWakeup.apk
rm /system_root/system/app/FBAppManager_NS/FBAppManager_NS.apk
rm /system_root/system/app/Facebook_stub/Facebook_stub.apk
rm /system_root/system/app/YouTube/YouTube.apk
rm /system_root/system/priv-app/Bixby/Bixby.apk
rm /system_root/system/priv-app/BixbyAgentStub/BixbyAgentStub.apk
rm /system_root/system/priv-app/BixbyService/BixbyService.apk
rm /system_root/system/priv-app/GalaxyAppsWidget_Phone_Dream/GalaxyAppsWidget_Phone_Dream.apk
rm /system_root/system/priv-app/GalaxyApps_OPEN/GalaxyApps_OPEN.apk
rm /system_root/system/priv-app/GameHome/GameHome.apk
rm /system_root/system/priv-app/FBInstaller_NS/FBInstaller_NS.apk
rm /system_root/system/priv-app/FBServices/FBServices.apk
rm /system_root/system/priv-app/EasySetup/EasySetup.apk
rm /system_root/system/priv-app/OneDrive_Samsung_v3/OneDrive_Samsung_v3.apk
rm /system_root/system/priv-app/Tips/Tips.apk # stupid Samsung Tips popups
rm /system_root/system/priv-app/DeXonPC/DeXonPC.apk
rm /system_root/system/priv-app/CocktailBarService_v3.2/CocktailBarService_v3.2.apk # Edge panel top right floats
# Google ****
rm /system_root/system/app/Chrome/Chrome.apk
rm /system_root/system/app/ChromeCustomizations/ChromeCustomizations.apk
rm /system_root/system/app/Gmail2/Gmail2.apk
rm /system_root/system/app/GoogleCalendarSyncAdapter/GoogleCalendarSyncAdapter.apk
rm /system_root/system/app/GoogleContactsSyncAdapter/GoogleContactsSyncAdapter.apk
rm /system_root/system/app/GoogleLocationHistory/GoogleLocationHistory.apk
rm /system_root/system/priv-app/SetupWizard/SetupWizard.apk # Without removal never passes initial setup
# Stuff replaced by MicroG aka NSA eyes
rm /system_root/system/priv-app/GmsCore/GmsCore.apk
rm /system_root/system/priv-app/GoogleServicesFramework/GoogleServicesFramework.apk
rm /system_root/system/priv-app/Phonesky/Phonesky.apk
rm /system_root/system/priv-app/Velvet/Velvet.apk
In Twrp -> Mount System
Now open Terminal on Your PC (in use of ADB) and try to do one of the delete commands in /system_root if you're getting a rights error don't worry I explain how you get it working.
The command is:
mount -o rw,remount /system_root
Go try a delete command in /system_root again. everything should be fine now.
Go through all the de-bloat commands after that download the microG flash-able zip of your linking here: (Or use Nanolux)
https://github.com/FriendlyNeighborhoodShane/MinMicroG_releases/releases/tag/2021.04.28
Put it on your phone and flash it throuh twrp.
Boot and Boom OneUI 3.1 with MicroG and low bloat this Exynos now runs like a beast.
Sorry this my second post on this thread so don't kill me for my bad English or some dumb mistakes!
Credits to all the beautiful guys on xda! This stuff would never happen without those Legends!!

Exynos is SM-G780F any owners of the G i.e. the snapdragon 4G version following your link will have a bad time.

3mel said:
Exynos is SM-G780F any owners of the G i.e. the snapdragon 4G version following your link will have a bad time.
Click to expand...
Click to collapse
My Tutorial says Exynos only like 3 Times

Hello. So happy to see some posts like these about s20 fe Exynos version. Really appreciate your work. Im more than a noob, i can't follow all these steps as they are a bit complicated as i used to root and install twrp, custom roms on my beloved Galaxy S5! But yeah pleasing to see the forum moving abit

Kingslayer9988 said:
My Tutorial says Exynos only like 3 Times
Click to expand...
Click to collapse
not everyone who might want root knows about SoCs.
it wasn't a dig at you.

Hello, How to do safetynet, I tried universal fix riru and it does not work And a few other ways

pepcio03 said:
Hello, How to do safetynet, I tried universal fix riru and it does not work And a few other ways
Click to expand...
Click to collapse
You can't pass safetnet with microg installed, it has been an issue for a while
SafetyNet API · Issue #181 · microg/GmsCore
As of version 0.37 Pokemon Go uses GMS's safetynet feature and I for one can't get past login. What is the implementation status on safetynet, is this out of scope for microg?
github.com
If you want to pass safetynet you'll have to remove microg and reinstall google play services to able to pass it.

Hello, does this microG degoogle work with the S 20 FE Snapdragon
(G781B/DS) ?​