Database Info

[Q]stuck in bootloader,no recovery

Hi to everybody,my friend has a problem with his desire S.
his phone is turned off itself vibrating.now he can boot only in bootloader mode,and the recovery is gone.
here some spec.
-Revolutionary-
SAGA PVT SHIP S-OFF RL
HBOOT-6.98.1002
radio-3805.06.02.03_M
eMMC-boot
Mar 10 2011,14:58:38
( bootloader ) version: 0.5
(bootloader) version-bootloader: 6.98.1002
(bootloader) [email protected] baseband : 3805.06.02.03_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.47.401.4
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG8810000
(bootloader) cidnum: HTC__405
(bootloader) battery-status: good
(bootloader) battery-voltage: 3653mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 361a7ba6
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
tried this http://forum.xda-developers.com/showthread.php?t=1488672 but no luck.when starts to flash the recovery,the vertical progress bar stops and the phone begins to vibrate.
He also tried to flash the eng hboot to run a RUU,but seems he can't flash the hboot (hangs on "writing hboot").
thanks for any help.

Did your friend happen to pull his battery anytime before all this started?
Recovery doesn't just "disappear" - he must have done something prior to that...
Anyway, the first thing is to rule out (or in) a fried eMMC
So do this:
Set up adb/fastboot and connect your phone (link in my sig)
Then connect your device to the PC, enter recovery, open cmd (command prompt) on the PC and type:
adb shell
dmesg | grep mmc0
For further details, consult this excellent guide by amidabuddha:
http://forum.xda-developers.com/showthread.php?t=1284196

thanks for the quick reply.when I have the output of the dmesg | grep mmc0 ,I'll post here.I haven't the phone with me,so I have to wait for my friend.

the phone,does not appear to be recognized by adb
C:\android-sdk-windows\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
but through fastboot devices the output is mb139tj10369 fastboot.
any ideas?

NeTvAmPiRe70 said:
the phone,does not appear to be recognized by adb
C:\android-sdk-windows\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
but through fastboot devices the output is mb139tj10369 fastboot.
any ideas?
Click to expand...
Click to collapse
Well, since you can get to fastboot, try this anyway.
Also, see if flashing recovery again gets you up and running.
Boot into fastboot on the phone, and using the cmd terminal, push a new recovery to the phone. I'm attaching 4EXT recovery. Just download it, extract recovery.img from the zip file, put it into your adb/fastboot folder and issue the following command:
fastboot flash recovery recovery.img
Then try to boot into recovery and tell me what you see...
DOWNLOAD : 4EXT Recovery

enigmaamit said:
Well, since you can get to fastboot, try this anyway.
Also, see if flashing recovery again gets you up and running.
Boot into fastboot on the phone, and using the cmd terminal, push a new recovery to the phone. I'm attaching 4EXT recovery. Just download it, extract recovery.img from the zip file, put it into your adb/fastboot folder and issue the following command:
fastboot flash recovery recovery.img
Then try to boot into recovery and tell me what you see...
DOWNLOAD : 4EXT Recovery
Click to expand...
Click to collapse
...no luck hangs on "writing recovery".

NeTvAmPiRe70 said:
...no luck hangs on "writing recovery".
Click to expand...
Click to collapse
Okay, i'm attaching 4EXT recovery in PG88IMG.zip format. Just place this on your sd card root, and boot into bootloader... it will try to flash this recovery on its own the moment it detects it. Let's see what happens...
DOWNLOAD HERE

enigmaamit said:
Okay, i'm attaching 4EXT recovery in PG88IMG.zip format. Just place this on your sd card root, and boot into bootloader... it will try to flash this recovery on its own the moment it detects it. Let's see what happens...
Click to expand...
Click to collapse
this is not the same thing but with a different recovery?
however,I'll give it a try.
NeTvAmPiRe70 said:
tried this http://forum.xda-developers.com/showthread.php?t=1488672 but no luck.when starts to flash the recovery,the vertical progress bar stops and the phone begins to vibrate.
Click to expand...
Click to collapse

NeTvAmPiRe70 said:
this is not the same thing but with a different recovery?
however,I'll give it a try.
Click to expand...
Click to collapse
I don't know what was there in that file... so i sent you mine.
But if fastboot wasn't working, the possibility of an eMMC brick is looming larger...
Just try the commands i asked you to type in my first post... I mean boot into bootloader, then see if these commands cough up a report... if it doesn't work, boot into fastboot and try again. You must have some kind of recovery man...
Also, you didn't say what happens when you select Recovery option from the bootloader... what happens?

enigmaamit said:
Okay, i'm attaching 4EXT recovery in PG88IMG.zip format. Just place this on your sd card root, and boot into bootloader... it will try to flash this recovery on its own the moment it detects it. Let's see what happens...
DOWNLOAD HERE
Click to expand...
Click to collapse
...same as before,when starts to flash the recovery,the vertical progress bar stops and the phone hangs on "do not power off the device".
tried the dmesg | grep mmc0 both from bootloader and from fastboot but the phone,does not appear to be recognized by adb.
when he select recovery from the bootloader,appears the white screen with the htc logo,then the phone turns off itself vibrating.

NeTvAmPiRe70 said:
...same as before,when starts to flash the recovery,the vertical progress bar stops and the phone hangs on "do not power off the device".
tried the dmesg | grep mmc0 both from bootloader and from fastboot but the phone,does not appear to be recognized by adb.
when he select recovery from the bootloader,appears the white screen with the htc logo,then the phone turns off itself vibrating.
Click to expand...
Click to collapse
Then i think your friend might have fried his eMMC.
Last resort is to call in the expert : Send a PM to amidabuddha, the guy whose guide i linked in my first post. I haven't found anyone more knowledgeable in these matters. If anyone can help you, its him.
I hope you can salvage the device...but its not looking very good....

thanks for your help,I'lll contact the expert

...and the expert has decreed:fried eMMC

NeTvAmPiRe70 said:
...and the expert has decreed:fried eMMC
Click to expand...
Click to collapse
That's what i thought too... just didn't want to mouth off such a grave judgement without being doubly sure.
Very sorry - unable to help any further. Hope your friend takes the news well, and wish him/her better luck for the next device!

[Q] Stuck on HTC boot screen after sudden restart

Hello Everyone,
My Desire S was running Fallout 4.0 ROM. I had a couple sudden restarts in the last week and a half, but they seem to have been graphic related and because I didn't have the time to re-install, I just lived with it (not a big deal) for the time being.
However, yesterday when I picked up my phone I have noticed that it is stuck on the HTC boot screen. I thought that this is just another one of those restarts, but when the boot operation didn't progress I figured that something is wrong. I booted into recovery (CWM 5.0.2.0) and then got the infamous errors of can't mount Cache/System/Data.
This when my troubles have began because I cannot seem to be able to solve this issue.
1) From within the "mounts and storage" menu I cannot mount nor format the partitions (I get an error such as "Error mounting /cache!" and "Error formatting /cache! The latter takes also a long while in which the format is being attempted but in the end the error appears)
2) When I choose the wipe option (restore factory defaults) it takes a very long time (30-40 minutes) to wipe the data and cache partitions. Sometimes it gives an error message and some time it says complete, but with not effect whatsoever from what I can tell.
3) Attempt to restore my Nandroid backup fails (both of the original stick ROM that came with the phone and the more recent Fallout backup). An error message says that it cannot be completed.
4) I tried to flash several ROMs. The first two failed (including the original Fallout ROM that I have used). I think that I have managed to flash CM7 and RunnyDroid. I say think, because the process seem to be completed without an error, but nothing has changed otherwise, the system doesn't boot.
5) I checked my eMMC by booting into Fastboot and running the command
Code:
adb shell
dmesg | grep mmc0
from adb.
The output is
Code:
dmesg | grep mmc0
<3>[6.953796] mmc0: No card detect facilities available
<6>[6.954345] mmc0: Qualcomm MSM SDCC at 0x00000000a0500000 irq 98,
<6>[6.954589] mmc0: Platform slot type: MMC
<6>[6.954711] mmc0: 4 bit data mode disabled
<6>[6.954925] mmc0: 8 bit data mode enabled
<6>[6.955078] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 96000000
<6>[6.955291] mmc0: Slot eject status = 0
<6>[6.955413] mmc0: Power save feature enable = 1
<6>[6.955566] mmc0: DM non-cached buffer at ffa0f000, dma_addr 0x0c
<6>[6.955780] mmc0: DM cmd busaddr 0x0c36e000, cmdptr busaddr 0x0c3
<6>[7.109436] mmc0: new high speed MMC card at address 0001
<6>[7.111297] mmcblk0: mmc0:0001 M4G2DE 2.10 GiB
~ #
To my best understanding it means that the eMMC is not necessarily fried.
4) Because I cannot boot into the system I tried to re-flash recovery (actually 4EXT) via fastboot and adb, but it fails with the error
FAILED (remote: not allowed)
Click to expand...
Click to collapse
. The same happened when I tried to flash the boot.img from a ROM.
5. I read about installing a RUU. well, I think that I have found a version that fits my phone but all the download links are broken and a web search didn't find the version that I (think that I) need elsewhere. Also, those are EXE file, that to my best of understanding requires the Android system to be booted up in order the installation process to work, which I cannot accomplish at this point.
General details of my phone as appear in the HBOOT screen:
SAGA PVT SHIP S-OFF RL
HBOOT-0.98.0000
RADIO-38.03.02.15_M
eMMC-boot
Mar 10 2011.14:58:38
Click to expand...
Click to collapse
Genreal details as received from running the commend
Code:
fastboot getvar all
in adb:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 0.98.0000
(bootloader) version-baseband: 38.03.02.15_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.28.401.1
(bootloader) serialno: HTXXXXXXXX
(bootloader) imei: XXXXXXXXXX
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG88*****
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4196mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 361a7ba6
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.033s
Additional notes:
1) I took caution not to pull the battery, I know that it can have very negative effects. When I had to, before pulling the battery I have used the Volume up and down + Power combination to restart the phone and pulled the battery in that 2-3 seconds window before it restarts. I also didn't reconnect the battery immediately but waited about a minute.
3) I formatted my memory card (8GB) to FAT32, just in case the file system is corrupt (I have backed up everything first). This doesn't seem to have an effect.
4) I didn't root or S-OFF the phone myself. At the time of buying it I wasn't even aware of all of this and didn't plan to replace ROMs, etc., so I don't have much information about how the S-OFF and Root were achieved, this is how the phone was provided to me.
I would appreciate any input and advice. Is it a faulty eMMC? Is there anything else that I can do (I am far from being an expert in this field)?
Thank you very much.

Please try to be simple. I don't think that all these informations are necessary. This is a question Doesn't Have to be so long. The responders will ask you for additional info if needed.

Thank you for your reply, but I don't see the point in posting a vague and general question that will then require people to ask for information and suggest measures that one might already has taken.
From my experience in other forums (in which I'm more on the "helping" side) it is very frustrating to read vague and general questions and repeatedly ask for the same basic information over and over (and over) again just to get started. It is a waste of time and energy for all parties involved. In my opinion posting the relevant technical information, issue summary and steps already taken with their results is the way to go.
Update: I contacted the lab of the store from which I purchased the device. They tested it and told me that the board is (most probably) faulty, something to do with the electrical components. Because the device is still under warranty they will send it to be replaced.
Hopefully, the fact that I have flashed a custom ROM in the past won't be an obstacle in light of the nature of the fault.
Thank you.

You're right about the information. It does help to just provide it all and the information given is useful. Hope it all works out mate
Sent from my Desire S using Tapatalk 2

The Story of my lost and recovery IMEI = 0 into GOOD

FIRST AT ALL, BE SURE WHAT YOU DO, I AM NOT RESPONSIBLE FOR ANY DAMAGE, ETC... AT YOUR OWN RISK, THIS IS MY EXPERIENCE, IT CAN BUT IT MUST NOT WORK ON YOUR PHONE, YOU HAVE BEEN WARNED BERFORE DOING ANY ACTION​
Guys, this is a story of a 3 year odyssey to get my IMEI on this phone back and at the end, YES!!! it works again. 100% full signal came back.
Now let's get into in....
First, tools you need to recovery your IMEI again.
- phone must be unlocked
- phone must be root
- phone should be on original stock 5.1
- TWRP Recovery ROM (use twrp-3.0.2-0-xt1032)
- from PlayStore download "Partitions Backup"
- from PlayStore download "Root Browser"
- XPOSED Framework and XPOSED Installer
- IMEI CHANGER (XPOSED MODULE)
- .IMG (use attached)
The story:
A friend of mine bought 2013 a Moto G (1st Gen) and wanted to root by himself. Root doesen't work, so he kept up. He decided to put an other rom on his phone, what he doesen't know, he erased all with command everything before (DICKHEAD): Fastboot erase all and Fastboot erase recovery <-- KILLER
From this moment.. after rebooting his phone the was no signal anymore. Serveral ROM and MODEMS tried out. Nothing just WIFI works. He gave the phone to me. 3 years later i wanted to re-awake this wonderful phone back to life.
Now, here comes the steps, you should do, to re-gain your phone...
01. choose and use a stock 5.1 rom of your country and flash it by fastboot command as always...
02. after rom installation and after reboot, install TWRP recovery rom with fastboot
03. reboot into recovery and install root in TWRP (use: UPDATE-SuperSU-v2.46)
04. reboot and download from PlayStore "Partitions Backup" and "Root Browser" and "IMEI Changer"
05. download XPOSED Framework (zip) and XPOSED Installer (apk)
06. reboot into TWRP install XPOSED Framework
07. reboot and install the XPOSED Installer APK with Root Browser and install IMEI Changer Module in XPOSED
08. reboot system, go into IMEI Changer and change your IMEI (under the back cover of your phone)
09. reboot and type in phone *#06#, you should see right now your IMEI, but the signal is already lost right? Okay, let's go ahead...
10. now return into Root Browser and see if there is a folder on your SDCARD "PartitionsBackups", if not, start the App and return
11. copy all three .img (attached) into it, start the App "Partitions Backup" again. Navigate to 3 dotted menu and and check "Restore a Partition"
12. navigate with "Root Browser" to the folder "PartitionsBackups" on SDCARD and use the first one, if successful, restore also the both other partitions. Forget the dd commands in terminal or cmd (doesent work), use the APP on top.
13. if it's done, reboot and pray... GOOD LUCK
14. Congrats, your signal should be back.
15. use Partitions Backup to backup all your partitions (as .img) and store them elsewhere.
16. set IMEI Changer as inactive and reboot, check with *#06#, otherwise let it active
17. !!! GIVE ME A THANKS, IF YOU ARE HAPPY WITH THIS !!!​

NOTE!
YOUR IMEI WILL NOT SHOWN IN FASTBOOT!
(bootloader) version: 0.5
(bootloader) version-bootloader: 411A
(bootloader) product: falcon
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x1
(bootloader) emmc: 16GB Toshiba REV=06 PRV=01 TYPE=17
(bootloader) ram: 1024MB Hynix S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: TA8900FI4F
(bootloader) cid: 0x0007
(bootloader) channelid: 0x00
(bootloader) uid: 28F911020F000000000000000000
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Aug 19 23:46:25 UTC 2015"
(bootloader) ro.build.fingerprint[0]: motorola/falcon_retde/falcon_umts:
(bootloader) ro.build.fingerprint[1]: 5.1/LPB23.13-56/56:user/release-ke
(bootloader) ro.build.fingerprint[2]: ys
(bootloader) ro.build.version.full[0]: Blur_Version.221.21.56.falcon_umt
(bootloader) ro.build.version.full[1]: s.Retail.en.DE
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.045
(bootloader) version-baseband: MSM8626BP_1032.3116.98.00y EMEA_CUST
(bootloader) kernel.version[0]: Linux version 3.4.42-g89906d6 ([email protected]
(bootloader) kernel.version[1]: ilclbld34) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Mon Aug 17 19:06:25 CDT 2015
(bootloader) sdi.git: git=MBM-NG-V41.1A-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V41.1A-0-g199f3c5
(bootloader) rpm.git: git=MBM-NG-V41.1A-0-g8b7736e
(bootloader) tz.git: git=MBM-NG-V41.1A-0-g99c1a7c
(bootloader) aboot.git: git=MBM-NG-V41.1A-0-g80481ae
(bootloader) qe: qe 1/1
(bootloader) ro.carrier: unknown
all: listed above
finished. total time: 0.104s

Reserved #2

Reserved #3

Can it work on Moto E dual sim 2014 indian version
Jerome-X said:
FIRST AT ALL, BE SURE WHAT YOU DO, I AM NOT RESPONSIBLE FOR ANY DAMAGE, ETC... AT YOUR OWN RISK, THIS IS MY EXPERIENCE, IT CAN BUT IT MUST NOT WORK ON YOUR PHONE, YOU HAVE BEEN WARNED BERFORE DOING ANY ACTION​
Guys, this is a story of a 3 year odyssey to get my IMEI on this phone back and at the end, YES!!! it works again. 100% full signal came back.
Now let's get into in....
First, tools you need to recovery your IMEI again.
- phone must be unlocked
- phone must be root
- phone should be on original stock 5.1
- TWRP Recovery ROM (use twrp-3.0.2-0-xt1032)
- from PlayStore download "Partitions Backup"
- from PlayStore download "Root Browser"
- XPOSED Framework and XPOSED Installer
- IMEI CHANGER (XPOSED MODULE)
- .IMG (use attached)
The story:
A friend of mine bought 2013 a Moto G (1st Gen) and wanted to root by himself. Root doesen't work, so he kept up. He decided to put an other rom on his phone, what he doesen't know, he erased all with command everything before (DICKHEAD): Fastboot erase all and Fastboot erase recovery <-- KILLER
From this moment.. after rebooting his phone the was no signal anymore. Serveral ROM and MODEMS tried out. Nothing just WIFI works. He gave the phone to me. 3 years later i wanted to re-awake this wonderful phone back to life.
Now, here comes the steps, you should do, to re-gain your phone...
01. choose and use a stock 5.1 rom of your country and flash it by fastboot command as always...
02. after rom installation and after reboot, install TWRP recovery rom with fastboot
03. reboot into recovery and install root in TWRP (use: UPDATE-SuperSU-v2.46)
04. reboot and download from PlayStore "Partitions Backup" and "Root Browser" and "IMEI Changer"
05. download XPOSED Framework (zip) and XPOSED Installer (apk)
06. reboot into TWRP install XPOSED Framework
07. reboot and install the XPOSED Installer APK with Root Browser and install IMEI Changer Module in XPOSED
08. reboot system, go into IMEI Changer and change your IMEI (under the back cover of your phone)
09. reboot and type in phone *#06#, you should see right now your IMEI, but the signal is already lost right? Okay, let's go ahead...
10. now return into Root Browser and see if there is a folder on your SDCARD "PartitionsBackups", if not, start the App and return
11. copy all three .img (attached) into it, start the App "Partitions Backup" again. Navigate to 3 dotted menu and and check "Restore a Partition"
12. navigate with "Root Browser" to the folder "PartitionsBackups" on SDCARD and use the first one, if successful, restore also the both other partitions. Forget the dd commands in terminal or cmd (doesent work), use the APP on top.
13. if it's done, reboot and pray... GOOD LUCK
14. Congrats, your signal should be back.
15. use Partitions Backup to backup all your partitions (as .img) and store them elsewhere.
16. set IMEI Changer as inactive and reboot, check with *#06#, otherwise let it active
17. !!! GIVE ME A THANKS, IF YOU ARE HAPPY WITH THIS !!!​
Click to expand...
Click to collapse
Bro, I also lost my imei number for moto e, it shows imei: 0, but in fastboot getvarall, it shows imei number.I think the img file you have attached will be different for moto e. I am ready to do anything, please guide. Thanks and regards

Im not an expert, but this method seems dangerous. The partitions you have attached are unique to your device, and flashing them on another device could cause serious permanent problems. I would suggest you remove these instructions until it is known what is contained within the hob, dhob and fsc partitions, unless someone can correct me.

Its up to the user to doing any action. This is my story, and my very own solution here, i wrote.
Gesendet von meinem SM-A310F mit Tapatalk

Professor Gibbins said:
Im not an expert, but this method seems dangerous. The partitions you have attached are unique to your device, and flashing them on another device could cause serious permanent problems. I would suggest you remove these instructions until it is known what is contained within the hob, dhob and fsc partitions, unless someone can correct me.
Click to expand...
Click to collapse
What problems? Even if they are the same IMEI still there is little chance that 2 users to be in the same country same network and same city. Anyway there are a lot of people who used the command and are screwed so it's great tutorial to revive the device
Sent from Samsung Galaxy S7

Jerome-X said:
Its up to the user to doing any action. This is my story, and my very own solution here, i wrote.
Click to expand...
Click to collapse
Exactly, this could mean that an inexperienced user might follow these instructions without understanding the implications. And when you say this is your very own solution, it's literal. This solution only applies to your specific device.
Eurofighter_ty said:
What problems? Even if they are the same IMEI still there is little chance that 2 users to be in the same country same network and same city. Anyway there are a lot of people who used the command and are screwed so it's great tutorial to revive the device
Click to expand...
Click to collapse
The IMEI duplication was only an example. There could be many other irreversible issues that the user doesn't even immediately realise.
Essentially, these partitions should never be overwritten without first taking a backup.

Yes of course, u re right
Gesendet von meinem SM-A310F mit Tapatalk

Haha, I'm not fussed with being right - just wanting to point out/give my opinion on the possible risks.
By all means keep your tutorial, but could I suggest adding a step where the 3 partitions are backed up before they are overwritten, just in case they need those partitions in the future.

Thank you so much for this really useful guide, I was hopeless and finally after 3 years was able to make my phone work.

Up Volume button not working when trying to unlock Bootloader

I am able to connect my phone (BLU STUDIO 6.0 HD) to my computer and use ADB, then type in fastboot oem unlock. However, when I try to use my Volume Up button in order to select to unlock the bootloader, it wont work. Only the Volume Down button is working, which cancels the command. I am doing this in order to get a custom recovery and in turn get CyanogenMod working. I've been working on this all day and have found no solution. :crying: I would appreciate any help.

volume up not working in bootloader
I am able to connect my phone (lenovo vibe c2 k10a40) to my computer and use ADB, then type in fastboot oem unlock. However, when I try to use my Volume Up button in order to select to unlock the bootloader, it wont work. Only the Volume Down button is working, which cancels the command. I am doing this in order to get a custom recovery and in turn get CyanogenMod working. I've been working on this all day and have found no solution. I would appreciate any help.
I'm sorry for my English, I'm brazilian

same here im on a figo gravity x55l i sent in a ticket to figo support and they just ignored it but anyway
i tried
fastboot oem unlock
fastboot oem unlock-go
and also activating oem unlock in dev settings and doing fastboot methods again...nothing
i looked up that a phone unlocks its bootloader by enableing oem unlock in dev settings and doing a format and still nothing
---------- Post added at 03:15 PM ---------- Previous post was at 02:56 PM ----------
has anyone tried with a headset with volume buttons? i know it is crazy but i dont have a pair to try lol

GREAT NEWS I MANAGED TO GET ROOT WITHOUT UNLOCKING THE BOOTLOADER ALL YOU NEED IS TO
1.download your firmware and extract it
2.extract the boot.img from the firmware and put it on your phone REMEMBER WHERE YOU PUT IT SINCE YOU WILL NEED THIS!
3download magiskmanager install it and open it.
4click install and choose the boot.img it will install magisk into it
5.put it back in your firmware folder on your pc
6 look for a file that says Checksum_gen and run it
7 once that completes use spflash tool and load your scatterfile and flash JUST THE BOOT.IMG wait for the reboot and you have root!
THANK YOU DEVELOPERS OF MAGISKMANAGER!
Click like if this helped to get the word out...I think that's how it works

SP6RK said:
GREAT NEWS I MANAGED TO GET ROOT WITHOUT UNLOCKING THE BOOTLOADER ALL YOU NEED IS TO
1.download your firmware and extract it
2.extract the boot.img from the firmware and put it on your phone REMEMBER WHERE YOU PUT IT SINCE YOU WILL NEED THIS!
3download magiskmanager install it and open it.
4click install and choose the boot.img it will install magisk into it
5.put it back in your firmware folder on your pc
6 look for a file that says Checksum_gen and run it
7 once that completes use spflash tool and load your scatterfile and flash JUST THE BOOT.IMG wait for the reboot and you have root!
THANK YOU DEVELOPERS OF MAGISKMANAGER!
Click to expand...
Click to collapse
I'm new to mediatek and I have the same problem volume up won't unlock bootloader. I had the same idea you did and hopefully you can help.
First off I'm not sure I have the right firmware I have a Blu studio m5 plus is what the box says. The stock recovery calls it Blu dash xl when I look up firmware for Blu studio m5 plus it has one from need rom and you need to pay for an account to download. If you look up the dash xl firmware I was able to find it free and its specs match my phone I think it's the right firmware. If I patch the boot img from magisk. I need help with flashing with sp flash tool. Did you replace the actual boot img from the firmware with the new patched boot img or did you just load the new boot img from another folder. See I don't know what the Android scatter file really does. Does the boot img have to be in the same folder as firmware to flash because the scatter file finds that folder or not? And help with the checksum gen I'm unfamiliar how do I use it? What does it do? How do I use it to verify?

SP6RK said:
GREAT NEWS I MANAGED TO GET ROOT WITHOUT UNLOCKING THE BOOTLOADER ALL YOU NEED IS TO
1.download your firmware and extract it
2.extract the boot.img from the firmware and put it on your phone REMEMBER WHERE YOU PUT IT SINCE YOU WILL NEED THIS!
3download magiskmanager install it and open it.
4click install and choose the boot.img it will install magisk into it
5.put it back in your firmware folder on your pc
6 look for a file that says Checksum_gen and run it
7 once that completes use spflash tool and load your scatterfile and flash JUST THE BOOT.IMG wait for the reboot and you have root!
THANK YOU DEVELOPERS OF MAGISKMANAGER!
Click to expand...
Click to collapse
You need to try twrp porter from hovatek YouTube channel you can flash twrp without unlocking the bootloader.
https://forum.hovatek.com/thread-21839.html
I first made a backup with Wwr tool from hovatek without having root or unlocking bootloader then I patched my bootimg with magisk. Copied the boot img and scater file that Wwr tool also makes into a folder flashed the patched boot Img with S P flash tool rebooted was rooted with magisk. Then I used twrp booter and it takes like 3 minutes to make you a twrp out of your backup you get from Wwr tool. Without any work I just hit 6 enter puts out twrp recovery and I flashed that with s p flash tool rebooted directly into twrp recovery from phone off and it works great. With a locked bootloader.

SP6RK said:
GREAT NEWS I MANAGED TO GET ROOT WITHOUT UNLOCKING THE BOOTLOADER ALL YOU NEED IS TO
1.download your firmware and extract it
2.extract the boot.img from the firmware and put it on your phone REMEMBER WHERE YOU PUT IT SINCE YOU WILL NEED THIS!
3download magiskmanager install it and open it.
4click install and choose the boot.img it will install magisk into it
5.put it back in your firmware folder on your pc
6 look for a file that says Checksum_gen and run it
7 once that completes use spflash tool and load your scatterfile and flash JUST THE BOOT.IMG wait for the reboot and you have root!
THANK YOU DEVELOPERS OF MAGISKMANAGER!
Click to expand...
Click to collapse
Thank you so much for this guide, really worked like a charm. Been having troubles with flashing from fastboot mode due to button trouble.
Many thanks!!!

This method is interesting, does it really work? I am trying to get ROOT on this BLU Studio 6.0 HD D651 terminal, but it is useless, I cannot pass the bootloader security sector, I CANNOT flash the Recovery Partition, I am also trying to create the TWRP for a BLU Studio 6.0 HD D651 with this Hovatek program, but I can't conclude the flashing of this file
"ERROR in partition size", read Fastboot mode with Advenger Box and everything is fine, except the protected sector of the computer, bootloader locked ON. I leave here the Registry to see if you can help me. I also tried SP Flash Tools and it is the same, the Flash concludes well (GOOD / OK) but I restart in Recovery and it is the same Recovery Stock.
I also asked the people of Hovatek and they say that it is necessary to unlock the bootloader of the terminal, so what the partner says above I do not understand how I manage to circumvent security!
Posd. On the TWRP Team page the file “TWRP Custom Recovery 2.8 for BLU Studio 6.0 HD” was deleted! (Can anyone share it?)
Fastboot Reading phone info Avengers Box 0.6.2
max-download-size: 134217728
partition-size: userdata: 32000000
partition-type: userdata: ext4
partition-size: cache: 7e00000
partition-type: cache: ext4
partition-size: system: 3e800000
partition-type: system: ext4
partition-size: expdb: a00000
partition-type: expdb: raw data
partition-size: logo: 300000
partition-type: logo: raw data
partition-size: misc: 80000
partition-type: misc: raw data
partition-size: sec_ro: 600000
partition-type: sec_ro: ext4
partition-size: recovery: 1000000
partition-type: recovery: raw data
partition-size: boot: 1000000
partition-type: boot: raw data
partition-size: uboot: 60000
partition-type: uboot: raw data
partition-size: seccfg: 20000
partition-type: seccfg: raw data
partition-size: protect_s : a00000
partition-type: protect_s : ext4
partition-size: protect_f: a00000
partition-type: protect_f: ext4
partition-size: nvram: 500000
partition-type: nvram: raw data
partition-size: pro_info: 300000
partition-type: pro_info: raw data
partition-size: ebr1: 80000
partition-type: ebr1: raw data
partition-size: mbr: 80000
partition-type: mbr: raw data
partition-size: preloader: 1400000
partition-type: preloader: raw data
off-mode-charge: 1
warranty: yes
unlocked: no
secure: yes
kernel: lk
product: J805B_BLU
version: 0.5
Capture CMD ERROR:

EngelP said:
This method is interesting, does it really work? I am trying to get ROOT on this BLU Studio 6.0 HD D651 terminal, but it is useless, I cannot pass the bootloader security sector, I CANNOT flash the Recovery Partition, I am also trying to create the TWRP for a BLU Studio 6.0 HD D651 with this Hovatek program, but I can't conclude the flashing of this file
"ERROR in partition size", read Fastboot mode with Advenger Box and everything is fine, except the protected sector of the computer, bootloader locked ON. I leave here the Registry to see if you can help me. I also tried SP Flash Tools and it is the same, the Flash concludes well (GOOD / OK) but I restart in Recovery and it is the same Recovery Stock.
I also asked the people of Hovatek and they say that it is necessary to unlock the bootloader of the terminal, so what the partner says above I do not understand how I manage to circumvent security!
Posd. On the TWRP Team page the file “TWRP Custom Recovery 2.8 for BLU Studio 6.0 HD” was deleted! (Can anyone share it?)
Fastboot Reading phone info Avengers Box 0.6.2
max-download-size: 134217728
partition-size: userdata: 32000000
partition-type: userdata: ext4
partition-size: cache: 7e00000
partition-type: cache: ext4
partition-size: system: 3e800000
partition-type: system: ext4
partition-size: expdb: a00000
partition-type: expdb: raw data
partition-size: logo: 300000
partition-type: logo: raw data
partition-size: misc: 80000
partition-type: misc: raw data
partition-size: sec_ro: 600000
partition-type: sec_ro: ext4
partition-size: recovery: 1000000
partition-type: recovery: raw data
partition-size: boot: 1000000
partition-type: boot: raw data
partition-size: uboot: 60000
partition-type: uboot: raw data
partition-size: seccfg: 20000
partition-type: seccfg: raw data
partition-size: protect_s : a00000
partition-type: protect_s : ext4
partition-size: protect_f: a00000
partition-type: protect_f: ext4
partition-size: nvram: 500000
partition-type: nvram: raw data
partition-size: pro_info: 300000
partition-type: pro_info: raw data
partition-size: ebr1: 80000
partition-type: ebr1: raw data
partition-size: mbr: 80000
partition-type: mbr: raw data
partition-size: preloader: 1400000
partition-type: preloader: raw data
off-mode-charge: 1
warranty: yes
unlocked: no
secure: yes
kernel: lk
product: J805B_BLU
version: 0.5
Capture CMD ERROR:
Click to expand...
Click to collapse
Yeah it works try it but remember your bootloader is still locked so installing twrp might softbrick your device...find a way to unlock your bootloader

SP6RK said:
GREAT NEWS I MANAGED TO GET ROOT WITHOUT UNLOCKING THE BOOTLOADER ALL YOU NEED IS TO
1.download your firmware and extract it
2.extract the boot.img from the firmware and put it on your phone REMEMBER WHERE YOU PUT IT SINCE YOU WILL NEED THIS!
3download magiskmanager install it and open it.
4click install and choose the boot.img it will install magisk into it
5.put it back in your firmware folder on your pc
6 look for a file that says Checksum_gen and run it
7 once that completes use spflash tool and load your scatterfile and flash JUST THE BOOT.IMG wait for the reboot and you have root!
THANK YOU DEVELOPERS OF MAGISKMANAGER!
Click to expand...
Click to collapse
I tried this and it worked !
I've been trying to Flash-Root MTK 6580 Blu studio G2 HD,
Volume Up wasn't working to Unlock Bootloader . (I had to unlock it)
Flashed the patched boot.img with Spflash and it worked, i rooted my phone without unlocking bootloader.
Someone in the above comments said to Unlock Bootloader somehow, Flashing anything with TWRP or anyother software may brick phone.
(I think you shouldn't unlock bootloader unless you absolutely need it)

Volume up button
I was having the same trouble.
Check if you have any software update .
Update them and try again i hope it will work.
It works for me samsung a10s

Techguy777 said:
You need to try twrp porter from hovatek YouTube channel you can flash twrp without unlocking the bootloader.
https://forum.hovatek.com/thread-21839.html
I first made a backup with Wwr tool from hovatek without having root or unlocking bootloader then I patched my bootimg with magisk. Copied the boot img and scater file that Wwr tool also makes into a folder flashed the patched boot Img with S P flash tool rebooted was rooted with magisk. Then I used twrp booter and it takes like 3 minutes to make you a twrp out of your backup you get from Wwr tool. Without any work I just hit 6 enter puts out twrp recovery and I flashed that with s p flash tool rebooted directly into twrp recovery from phone off and it works great. With a locked bootloader.
Click to expand...
Click to collapse
Thanks SO much Techguy777!! I can absolutely confirm that after MANY, MANY days day of trying to get my MTK6582 device rooted , this process worked perfectly without unlocking the bootloader. I already had the Magisk patched boot image file and all the SP Flash tool set but didn't know how to use them correctly. I followed the step-by-step guide here:
SP Flash Tool - Basic User Guide
Install Mediatek Drivers Extract the Mediatek_USB_Driver_Auto-Installer zip file. Run the installer file that is extracted from zip by right clicking the .exe file and click on "Run as Administrator". ( the exe file that comes out of zip = Mediatek_Driver_Auto-Installer.exe ) Click on "Install"...
gpdcentral.com
Enjoy!

SP6RK said:
GREAT NEWS I MANAGED TO GET ROOT WITHOUT UNLOCKING THE BOOTLOADER ALL YOU NEED IS TO
1.download your firmware and extract it
2.extract the boot.img from the firmware and put it on your phone REMEMBER WHERE YOU PUT IT SINCE YOU WILL NEED THIS!
3download magiskmanager install it and open it.
4click install and choose the boot.img it will install magisk into it
5.put it back in your firmware folder on your pc
6 look for a file that says Checksum_gen and run it
7 once that completes use spflash tool and load your scatterfile and flash JUST THE BOOT.IMG wait for the reboot and you have root!
THANK YOU DEVELOPERS OF MAGISKMANAGER!
Click to expand...
Click to collapse
Thank you. This really works to get magisk so easily installed without having to unlock bootloader. No need to even install TWRP recovery.

SP6RK said:
GREAT NEWS I MANAGED TO GET ROOT WITHOUT UNLOCKING THE BOOTLOADER ALL YOU NEED IS TO
1.download your firmware and extract it
2.extract the boot.img from the firmware and put it on your phone REMEMBER WHERE YOU PUT IT SINCE YOU WILL NEED THIS!
3download magiskmanager install it and open it.
4click install and choose the boot.img it will install magisk into it
5.put it back in your firmware folder on your pc
6 look for a file that says Checksum_gen and run it
7 once that completes use spflash tool and load your scatterfile and flash JUST THE BOOT.IMG wait for the reboot and you have root!
THANK YOU DEVELOPERS OF MAGISKMANAGER!
Click like if this helped to get the word out...I think that's how it works
Click to expand...
Click to collapse
What is Checksum_gen file? I can't find it in firmware folder

lyehengfoo said:
Thank you. This really works to get magisk so easily installed without having to unlock bootloader. No need to even install TWRP recovery.
Click to expand...
Click to collapse
Please guide me too. What is Checksum_gen file? I can't find it in firmware folder

360 N6 Lite (QIKU): help is needed: 1)to root the device 2)to cope with AVB

Device: 360 N6 Lite by QIKU, Snapdragon 630
Device is running stock ROM based on android 8.1, no mods, no tweaks, just a stock android. I've never ever messed with any system files/partitions.
Stock ROM was re-flashed a few days ago after this thread was posted - to satisfy request of some person who thought I had ROM tampered with.
I can re-flash ROM as many times as would be needed, upon request if anybody is really keen to help.
Addtional info about my device:
1. fastboot has limited functionality: it cannot flash any partiton. Therefore, if I have to flash certain partition, like booot/recovery/system I only can do it with QFIL flashing software.
2. I can patch stock boot.img by Magisk alright. However, after I flash patched boot phone goes to Red State (or bootloop if phone is connected to PC), so Magisk is not an option here. Or I'm just so stupid I do not see how to benefit from Magisk. Log of Magisk patching the stock boot is attached here.
I thought I might have a chance with superSU though.
3. bootloader is unlocked if I can trust the info below:
(bootloader) unlocked:yes
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:3975
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) variant:SDM EMMC
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x1F400000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5EBBFBE00
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xE0000000
(bootloader) secure:yes
(bootloader) serialno:********
(bootloader) product:QK1713-A01
(bootloader) max-download-size:536870912
(bootloader) kernel:uefi
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
Phone is apparently not rooted as shown on attached pics. However, when I run <adb shell> command, it appears as if there is a root already installed as I see # prompt, not $.
This phone really makes me crazy. I cannot flash custom recovery, I cannot flash any partition using fastboot, I cannot flash any zip-package and I cannot figure out how to properly install SU-binary.
Any help is much appreciated!

In the thread linked to above one can see BusyBox is installed on phone. BusyBox by default comes with the SU-binary. Check this.

jwoegerbauer said:
Check this.
Click to expand...
Click to collapse
Sure. Could you please share details what exactly to be checked: files/locations/permissions/what?
Just in case:
1|QK1713:/ # ls /system/bin/su
ls: /system/bin/su: No such file or directory
1|QK1713:/ # ls /system/xbin/su
ls: /system/xbin/su: No such file or directory
1|QK1713:/ #
QK1713:/ # find /system -name "su"
QK1713:/ #
QK1713:/ # find /data -name "su"
QK1713:/ #
QK1713:/ # find /system -name "busy*"
/system/bin/busybox
QK1713:/ #

Regarding AVB: the goal is to deactivate AVB 1.0 in order to be able to flash custom recovery (TWRP).
In Magisk log it is said 'Boot image is signed with AVB 1.0'
As mentioned here: AVB 1.0 there is no VBMETA partitions on devices with AVB 1.0. This is almost correct statement re my device. To be more precise: there is such a partition, list of partitions is attached. But VBMETA is filled with all zeroes. File mmcblk0p57 (dd-ed from device) is also attached, it consists of zeroes
Also, VBMETA partition is not supposed to be flashed when flashing stock ROM. Here's what is there in rawprogram0.xml:
Code:
<program SECTOR_SIZE_IN_BYTES="512" file_sector_offset="0" filename="" label="vbmeta" ...
<program SECTOR_SIZE_IN_BYTES="512" file_sector_offset="0" filename="" label="vbmetabak" ...
So, I conclude it should be useless for me to try anything like:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Question is: is there any way how to deactivate AVB 1.0 so that I could flash boot.img patched by Magisk? Image of stock boot is attached herewith.
Or, almost the same question: what needs to be done with stock boot in order for my device does not reject custom recovery?

Does your QFil tool allow you to add additional options when flashing an image?
I know you don't believe that your phone uses vbmeta, but we can't rule it out unless you can flash it properly.
I still find it really hard to believe that they removed the ability to flash from fastboot. It makes me think it is more likely that the syntax of the command is different. That's just my gut feeling and of course I may be wrong.
Do you know if your device uses A/B partitioning?
What happens if you use TWRP and try:
fastboot boot recovery.img

Bondyuk said:
Does your QFil tool allow you to add additional options when flashing an image?
Click to expand...
Click to collapse
QFIL - Qualcomm Flash Image Loader. It can flash any partition I want to but it does not support command line parameters: it is ran as a separate program, not from command line if it is what you mean.
Bondyuk said:
I know you don't believe that your phone uses vbmeta, but we can't rule it out unless you can flash it properly.
Click to expand...
Click to collapse
Well, as I mentioned: VBMETA is filled with all zeroes. Do you think all zeroes can effectively prevent me from using customized images?
Bondyuk said:
Do you know if your device uses A/B partitioning?
Click to expand...
Click to collapse
It certainly does not.
Bondyuk said:
What happens if you use TWRP and try:
Click to expand...
Click to collapse
I cannot use TWRP because TWRP is a customized (changed) recovery. My ugly device does NOT allow using amended partition. It relates to both boot and recovery.

vp1117 said:
Device: 360 N6 Lite by QIKU, Snapdragon 630
Device is running stock ROM based on android 8.1, no mods, no tweaks, just a stock android. I've never ever messed with any system files/partitions.
Addtional info about my device:
1. fastboot has limited functionality: it cannot flash any partiton, therefore the only way I can flash anything is by QFIL
2. I can patch stock boot.img by Magisk alright. However, when I flash patched boot phone goes to Red State (or bootloop if phone is connected to PC), so Magisk is not an option here. Or I'm just so stupid I do not see how to benefit from Magisk. I hope I might have a chance with superSU though.
Log of Magisk patching the stock boot is attached here.
3. bootloader is unlocked:
(bootloader) unlocked:yes
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:3975
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) variant:SDM EMMC
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x1F400000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5EBBFBE00
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xE0000000
(bootloader) secure:yes
(bootloader) serialno:********
(bootloader) product:QK1713-A01
(bootloader) max-download-size:536870912
(bootloader) kernel:uefi
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
Phone is apparently not rooted as shown on attached pics. However, when I run <adb shell> command, it appears as if there is a root already installed: https://forum.xda-developers.com/t/i-need-help-rooting-my-zte-quest-5.4276715/post-85018813
This phone really bothers me. I cannot flash custom recovery, I cannot flash any partition using fastboot and I cannot figure out how to properly install SU-binary.
Any help is much appreciated!
Click to expand...
Click to collapse
What's your android version I see that you're using SuperSU just to let u know SuperSU only works on Android Nougat and below this means if you're running android Oreo and above SuperSU will no longer work for Android Oreo and above I recommend u to use magisk

Austinredstoner said:
What's your android version I see that you're using SuperSU just to let u know SuperSU only works on Android Nougat and below this means if you're running android Oreo and above SuperSU will no longer work for Android Oreo and above I recommend u to use magisk
Click to expand...
Click to collapse
I'm not using superSU. I only wanted to explore if it would be possible to use superSU on my device.
Stock ROM is based on Oreo.
I cannot use Magisk.

vp1117 said:
I'm not using superSU. I only wanted to explore if it would be possible to use superSU on my device.
Stock ROM is based on Oreo.
I cannot use Magisk.
Click to expand...
Click to collapse
Why can't u use magisk did u flash magisk.zip file in via twrp recovery or some other recovery like orangefox

vp1117 said:
I'm not using superSU. I only wanted to explore if it would be possible to use superSU on my device.
Click to expand...
Click to collapse
What do you really want to have: SuperSU or SU ( read: Switch User )? SuperSU is a Superuser access management tool ( authored by Chainfire ), whereas SU is a binary ( ported from Linux distros ) that allows to perform actions on Android with Superuser privileges similar to the Administrator privileges on Windows OS.

jwoegerbauer said:
What do you really want to have: SuperSU or SU ( read: Switch User )? SuperSU is a Superuser access management tool, whereas SU is a binary that allows to perform actions on Android with Superuser privileges similar to the Administrator privileges on Windows OS.
Click to expand...
Click to collapse
Thank you. You are right: probably, I'm not clear in stating of my goal. I need to be able to run file managers like Root Explorer with root privileges, i.e. to access and amend files in system areas.

Austinredstoner said:
Why can't u use magisk did u flash magisk.zip file in via twrp recovery or some other recovery like orangefox
Click to expand...
Click to collapse
Because I cannot use any custom recoveries.
All I can do with Magisk is to patch stock boo.img and try to flash it to the phone. Just to get Red State as a result.
It all was written in my 1st post in this thread...

vp1117 said:
Sure. Could you please share details what exactly to be checked: files/locations/permissions/what?
Just in case:
1|QK1713:/ # ls /system/bin/su
ls: /system/bin/su: No such file or directory
1|QK1713:/ # ls /system/xbin/su
ls: /system/xbin/su: No such file or directory
1|QK1713:/ #
QK1713:/ # find /system -name "su"
QK1713:/ #
QK1713:/ # find /data -name "su"
QK1713:/ #
QK1713:/ # find /system -name "busy*"
/system/bin/busybox
QK1713:/ #
Click to expand...
Click to collapse
This screenshot of Android's terminal window shows that phone's Android must be somehow rooted because of # is shown instead of $ in front of each line
Run either on computer
Code:
adb devices
adb shell "mount -t auto -o rw,remount /system"
or in Android terminal
Code:
mount -t auto -o rw,remount /system
Is it giving you a 'not permitted' error - or similar?

jwoegerbauer said:
This screenshot of Android's terminal window shows that phone's Android must be somehow rooted because of # is shown instead of $ in front of each line
Run either on computer
Code:
adb devices
adb shell "mount -t auto -o rw,remount /system"
or in Android terminal
Code:
mount -t auto -o rw,remount /system
Is it giving you a 'not permitted' error - or similar?
Click to expand...
Click to collapse
From PC's command prompt:
Z:\android\adb>adb devices
List of devices attached
b839ca58 device
Z:\android\adb>adb shell "mount -t auto -o rw,remount /system"
Z:\android\adb>
At the same time, from android terminal application:

@vp1117
The screenshot shows that Android Terminal app is launched as normal user, not as superuser as former screenshots provided here by you show it.
I have come to the conclusion that your phone is no longer in its state of delivery, as initially claimed by you: there are simply too many things that do not fit together.
Hence my recommendation: Do a Factory Reset, then re-flash phone's Stock ROM to get rid off of all mods you applied so far, wipe phone's Cache partition, and afterwards restart your attempts to root it from the scratch - of course having the appropriate knowledge how to do it.
My last 2 cents here:
To re-flash phone's Stock ROM you use YGDP tool
DL: https://droidfilehost.com/download/download-ygdp-tool-version/

Have done it.
For ROM re-flashing I used QIKU vendor's utility, not YGDP. Screenhots of re-flashing are attached.
Next, the only thing I did was to install Material Terminal and Root Explorer applications.
Here are results of same commands executing:
And Root Explorer denying device having been tooted:

... and here's info about my attempts to find su and busybox on freshly re-flashed device:

Once you run "adb shell" and you get greeted with a # prompt then you can perform commands in "adb shell" without having to run su. BTW: This is because of in your phone's Android properties ro.secure by default is set to 0.
Be happy!
You can try to add the su applet ( what is missing in your pre-installed no-root version of BusyBox ) to Android at your own - what requires both the phone's bootloader got unlocked and the Android's SELinux got disabled before:
Code:
adb devices
adb shell "mkdir -p /data/local/tmp"
adb push <location-of-su-applet-on-pc-here> /data/local/tmp
adb shell
chmod 0777 /data/local/tmp/su
chown root:root /data/local/tmp/su
chcon /data/local/tmp/su u:object_r:su_exec:s0
mount -t auto -o rw,remount /system
mv -f /data/local/tmp/su /system/bin/su
mount -t auto -o ro,remount /system
exit
adb reboot
The matching su applet you fetch from SuperSU.zip.

jwoegerbauer said:
Once you run "adb shell" and you get greeted with a # prompt then you can perform commands in "adb shell" without having to run su. BTW: This is because of in your phone's Android properties ro.secure by default is set to 0.
Click to expand...
Click to collapse
Thank you for guiding me.
There is a lot of information in your last post that I have to digest and understand being at zero-knowledge level.
Let me start with this:
ro.secure - is it defined in default.prop stored in boot.img?

@vp1117
It's the file build.prop located in /system directory what is the file of interest, not the "default.prop" file.
Build.prop contains all those final settings / commands that make an Android device run smoothly.
I'm pretty sure build.prop on your phone contains the lines
ro.secure=0
ro.debuggable=1
persist.service.adb.enable=1
FYI: If ro.secure=0 then adbd runs as root.
BTW:
I no longer participate this thread: It just doesn't make sense to me anymore.