Related
Hello,
I have HTC Desire S. I did HTCDev.com unlock, but again and again there are problems to root this device. I can't flash recovery via fastboot, hangs on sending files etc. Went through many guides and nothing:
http://forum.xda-developers.com/showthread.php?t=1194488
http://forum.xda-developers.com/showthread.php?t=1318919
http://forum.xda-developers.com/sho...m.xda-developers.com/showthread.php?t=1399331
Always there is something like adb shell /data/local/tmp/zergRush > Cannot copy boomsh: Permission diened etc. problems.
I am totally lost. can you give me few hints how to or downgrade to 0.98.00000 or whatever to install custom recovery. Please! :s
Can you please help me root this device, install clockwork recovery and rom to MIUI? I have rooted another, my old HTC Desire before, but there anything went fine.
***Unlocked***
SAGA PVT SHIP S-ON RL
HBOOT-2.00.0002
RADIO-3822.10.08.04_M
eMMC-boot
Aug 22 2011, 15:22:13
Guys, really need your help, please! Will pay dollars for help.
This is such a huge pain in the ass! Sorry for 2xpost.
I have followed this guide: http://forum.xda-developers.com/showthread.php?t=1399331
I really managed to get to this point with success:
5. now type
adb shell /data/local/tmp/misc_version -s 1.27.405.6
--> this will change your version information
Click to expand...
Click to collapse
and problem starts on:
6. now you can doubleclick on the privous downloaded RUU and follow the steps. it may tell you from going down from version 2.xx to 1.xx but it is possible.
7. phone reboots and when it is up again you should have android 2.3.3 hboot 0.98.0000 S-ON
8. now just download revolutionary from http://revolutionary.io and create a beta key and start programm
Click to expand...
Click to collapse
RUU installer simply freezes on "Sending" data to phone. I am stuck there, sometimes it gives error [171], sometime shows that ''battery less than 30% remaining''. What the heck is going on? (I have locked bootloader before RUU install, because I have read that it should be like that.) (HTC Sync installed before RUU install)
You need to relock the bootloader with the command "fastboot oem lock"
So boot the phone into fastboot, then in cmd run above command, then re try the RUU.
Already did that, but with no success. Still the same problem. RUU installer freezes on "Sending".
---
As I enter bootloader ***Unlocked*** on the top is changed to ***Relocked***, so command "fastboot oem lock" did the job.
Try extracting the rom.zip file from the RUU, then renaming it to PG88IMG.zip then place that file on your SDcard root then apply the update in hboot.
I have dowloaded RUU file which is .exe, is there any RUU what you would recommend for me? (phone is not branded, Europe: Latvia) Maybe I am using wrong RUU also?
And as I will put PG88IMG.zip in to SD card, how should I apply the update in hboot, by running some command in cmd?
@Forwox
To get the ROM.zip from the RUU and to install via PG88IMG.zip
Start the RUU and once at the main page go to Start>Run and type in %temp%
Next find the newest folder and in there will be file called rom.zip. Copy this file to the desktop and rename it to PG88IMG.zip
Now copy this file to your SD card and start the phone in HBOOT (turn it on whilst holding volume down). It will find the file and start the update.
If that fails please run this fastboot command "fastboot getvar all" and post its results and the RUU you are trying to install.
Well, I got that rom.zip from %temp%, newest folder found rom.zip (rom.zip date modified is 2011.03.15) , put it into SD card, then entered HBOOT and it gave me:
SD Checking...
Loading... [PG88DIAG.zip]
No image!
Loading... [PG88DIAG.nbh]
No image or wrong image!
Loading...[PG88IMG.zip]
No image!
Loading... [PG88IMG.nbh]
No image or wrong image!
As I enter into cmd and run "fastboot getvar all" it gives me:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.00.0002
(bootloader) version-baseband: 3822.10.08.04_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.27.405.68
(bootloader) serialno: SH17CTJ03677
(bootloader) imei: 356708045855945
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG8810000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4177mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ebd3df7d
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.016s
Click to expand...
Click to collapse
I am trying to install RUU_Saga_HTC_Europe_1.28.401.1_Radio_20.28b.30.0805U_38.03.02.11_M_release_177977_signed
When I tried this: http://forum.xda-developers.com/showthread.php?t=1399331 method before, I went so far and got stuck with RUU...exe installing: (see attachemen 1.)
EDIT!!!
I have managed to flash RUU by copying it to SD card (writing .zip was the problem), flashed via HBOOT, but nothing have changed!)
(see attachement 2. when flashing 3., 4. when RUU is flashed)
Try to install the 1.47... (dont remember the exact number) using the installer... I've downgraded it with that version following the same tut as u did. Dont know if it makes a difference but give it a try... or maybe there's someone else who could help u (im not really a pro ^^)
Sent from my HTC Desire S
Forwox said:
Guys, really need your help, please! Will pay dollars for help.
This is such a huge pain in the ass! Sorry for 2xpost.
I have followed this guide: http://forum.xda-developers.com/showthread.php?t=1399331
I really managed to get to this point with success:
and problem starts on:
RUU installer simply freezes on "Sending" data to phone. I am stuck there, sometimes it gives error [171], sometime shows that ''battery less than 30% remaining''. What the heck is going on? (I have locked bootloader before RUU install, because I have read that it should be like that.) (HTC Sync installed before RUU install)
Click to expand...
Click to collapse
are u'r phone already have firmware version 1.27.405.6, if that..u can try uninstall HTCsync first and leave the driver..n now u can try run RUU upgrade again..n see..
i hope this help u..
YESSSS, FINALLY DID IT!!!
What were my problems? RUU was the incorrect versions, few problems with PC drivers, that's why fastboot recovery flashing didn't worked and the only way to go was Revolutionary, but it does not work on 2.00.xxxx HBOOT version, that's why downgrade was needed.
My HTC Desire S now:
-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
Click to expand...
Click to collapse
Before:
***LOCKED***
SAGA PVT SHIP S-ON RL
HBOOT-2.00.0002
RADIO-3822.10.08.04_M
eMMC-boot
Aug 22 2011, 15:22:13
Click to expand...
Click to collapse
What have I done:
*HTCDev.com Unlock and then Relock, downgrade from HBOOT-2.00.0002 to HBOOT- 0.98.0002 is done, RUU installed, S-OFF made via revolutionary, MIUI ROM installed.*
Here is a little walkthrough from *pain in the ass* to total success how it was in my case :
------------
1. Installed all necessary android related drivers to PC.
2. In Desire S phone turned off "fastboot" option in Settings/power/fastboot. Turned on USB debugging Settings/Applications/Development/USB debugging
3. Switched on and connected phone to PC (Charge only).
3.1 If your HTC Desire S in HBOOT shows pink ***LOCKED*** go to HTCDev.com and unlock it.
4. Downloaded files from this topic: http://forum.xda-developers.com/showthread.php?t=1399331 (zergRush and misc_version ONLY!!!)
Unziped the downloaded files in a folder (e.g. c:/Users/yourName/Downloads)
5. In Windows went to Start>Run and typed cmd. Now you needed to relock the bootloader with the, so typeed command "fastboot oem lock" in terminal just just I opened. "I recommend to restart the phone and after that connect to Charge only again as before."
3. Run the Terminal again and changed into the folder where I unzipped files before (change folder with 'cd')
4. Now typed to the terminal (every line is one command!)
adb push zergRush /data/local/tmp
adb push misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/zergRush
adb shell chmod 777 /data/local/tmp/misc_version
adb shell
(IF THERE IS ANY PROBLEM WITH zergRush or BOOMSH, and only $ shows up, type this):
4.1 rm /data/local/tmp/boomsh
4.2 rm /data/local/tmp/sh
4.3 cd /data/local/tmp/
IF NO PROBLEM EXPLAINED ABOVE, THEN KEEP TYPING AFTER PREVIOUS adb shell THIS:
cd /data/local/tmp/
./zergRush
5. Then typed
adb shell /data/local/tmp/misc_version -s 1.27.405.6
"This will change your version information, but you need the same RUU version!"(don't type this in cmd, of course)
6. Now found appropriate RUU for device. I used RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199410_signed and it worked like a charm!!! I have tried two other with no success on downgrade. My Desire S is non-branded!
7. Run that downloaded RUU .exe file, went to Start>Run and typed in %temp% Now clicked "Date modified" and found the newest folder and in there will be file called rom.zip. Copied this file to the desktop and renamed it to PG88IMG (adding .zip extension was the trouble maker for me! But you can try)
8. Copied this file to my SD card and start the phone in HBOOT (turn it on whilst holding volume down). The phone found the file and started the update.
9. Phone restarted and you I saw HBOOT- 0.98.0002 instead of HBOOT-2.00.0002 as it was before. If it is like that, then you have successfully downgraded your HTC Desire!
8. Now just download revolutionary from http://revolutionary.io and create a beta key and start programm. It will do S-OFF on your device.
DONE!
Now you can install any ROM by your choice.
Good luck and don't give up! It took me 3 days, but I didn't gave up.
I hope this report somehow helps users like me, who faces the same problems and storyline.
Many thanks to foX2delta and SuperKid who helped, and topics in this forum.
Glad it worked out, never heard of a RUU not working in this way (want main version, wasnt CID related). Only thing I can think of is maybe the RUU's (v1.28/1.47) each respond differently to the later versions (v2.10) or luck of the gods or a bad download of the RUU.
As foX2delta said
foX2delta said:
or a bad download of the RUU.
Click to expand...
Click to collapse
So remember always checking md5 sums, even if it was not necessarily because of that.
Sent from my HTC Desire S
This worked for me too. If you've unlocked the bootloader though htcdev though, you HAVE to relock it, otherwise flashing the older RUU will give an error message. This makes me wonder if unlocking it is even needed at all.
You know what??? you're a life saver!
I followed your steps and managed to make it .... phew!!
I used the RUU directly though, it worked fine once the bootloader is locked again
Thanks!
ahmedsalahais said:
You know what??? you're a life saver!
I followed your steps and managed to make it .... phew!!
I used the RUU directly though, it worked fine once the bootloader is locked again
Thanks!
Click to expand...
Click to collapse
At least, glad this worked for you. Enjoy it.
HELP! ok i unlocked my desire s using HTCdev.
and i download both zergRush and misc_version and unzip it on c:\users\user\downloads
so i go to cmd and type in those commands but i got this
c:\Users\user\Downloads>adb push zergRush /data/local/tmp
'adb' is not recognized as an internal or external command,
operable program or batch file.
need to downgrade it from 2.00.0002.
*latest update. now it says
c:\Android>adb push zergRush /data/local/tmp
error: device not found
**latest update.
C:\Users\user>cd c:\Android
c:\Android>adb push zergRush /data/local/tmp
1152 KB/s (14157 bytes in 0.012s)
c:\Android>adb push misc_version /data/local/tmp
644 KB/s (15837 bytes in 0.024s)
c:\Android>adb shell chmod 777 /data/local/tmp/zergRush
c:\Android>adb shell chmod 777 /data/local/tmp/misc_version
c:\Android>adb shell /data/local/tmp/zergRush
/data/local/tmp/zergRush: /acct: permission denied
acct: permission denied
acct: permission denied
acct: permission denied
acct: permission denied
/data/local/tmp/zergRush: 6: Syntax error: "(" unexpected
--------------------solve---------------
No htcdev needed?
I'm a newbie, but I think you do not need to unlock then relock bootloader via htcdev. Doing this is basically telling HTC you are voiding your warranty. I am trying this method tonight and will report if HTC unlock is needed.
I had unlocked bootloader via htcdev.com and installed a custom rom. now i need to go back to stock rom so i downloaded old RUU
I tried the steps above and iam getting the following message.
/system/bin/sh: 4.3: not found
C:\Android>adb push zergRush /data/local/tmp
351 KB/s (23060 bytes in 0.064s)
C:\Android>adb push misc_version /data/local/tmp
694 KB/s (589849 bytes in 0.829s)
C:\Android>adb shell chmod 777 /data/local/tmp/zergRush
C:\Android>adb shell chmod 777 /data/local/tmp/misc_version
C:\Android>
C:\Android>adb shell
[email protected]:/ $ 4.1 rm /data/local/tmp/boomsh
4.2 rm /data/local/tmp/sh
4.3 cd /data/local/tmp/4.1 rm /data/local/tmp/boomsh
/system/bin/sh: 4.1: not found
127|[email protected]:/ $ 4.2 rm /data/local/tmp/sh
/system/bin/sh: 4.2: not found
127|[email protected]:/ $ adb shell /data/local/tmp/misc_version -s 1.27.405.6
hell /data/local/tmp/misc_version -s 1.27.405.6
/system/bin/sh: 4.3: not found
127|[email protected]:/ $
Pls help
Leave the 4.1, 4.2 and 4.3 aside. In case you didn't put attention - they're just step numbers, and aren't part of the commands.
You're making an awful mess.
hi,
so i wasn't confident enough to root my own device so i gave it to an aquaintance to do it. when i got it back i installed super user and tried to install titanium backup but it gave me:
could not aquire root privileges, etc.
so i ran root checker and this is the result:
Super User Applications Status:
Superuser application - version 3.1.3 - is installed!
SuperSU application - is NOT installed.
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Standard Location
Check Command: ls -l /system/xbin/su:
Result: /system/xbin/su: No such file or directory
Analysis: File /system/xbin/su does not exist.
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Root User ID and Group ID Status:
SU binary not found or not operating properly
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1
i'm not quite sure what he's done but i think all he's done it to unblock it (?) maybe, therefore i don't know where i should pick it up to finish the rooting process. i've been reading around but i'm just getting more confused. please give me a step-by-step guide to finish this off.
oh, and i don't know how to determine the hboot version since Revolutionary couldn't detect my device anymore.
thank you
Hi, tried to install a new rom on my HTC One X ATT without success..
Specs : HTC ONE X Evita PVT Ship S-On RL
Hboot- 1.140002
Current status : ******TAMPERED******
******UNLOCKED******
I currently have TWRP 2.2.0 but I am unable to install any rom, also I have by mistake formatted my drive so my phone doesn't have any operating system atm. I changed the SCid to 1111111 but can't get from S-On to S-Off. I tried using a method on this forum and I keep getting
C:\.................>adb push soffbin3 /data/local/tmp/
error: device not found
Same for the next 3 lines, I am guessing maybe because those folders don't exist anymore on my drive....
Would really appreciate any help on what step to take next to have it back n working... The latest of Pac Man Rom was what I tried to install....
Sam
You couldn't install any aosp ROMs because you don't have the correct firmware, you would need to upgrade via the 3.18 RUU to update your phone to the 2.14 firmware. First thing you need to do is use the mount menu in TWRP and copy a Sense 4+ Android 4.1 ROM to the phone from your PC. Once you've installed a Sense 4+ ROM just use the Rumrunner method to get s-off, you'll find it here. Once you have s-off you can run the 3.18 RUU, then you can flash TWRP again, then you can install current aosp ROMs.
Sent from my Evita
Thanks
Thanks will do right away but got 1 more question, sorry I am new at this, but you said "Sense 4+ Android 4.1 ROM to the phone from your PC"
Is there a specific version I should install or could you give me a name of one I could look up to download and install ? I just read that some I can't install because my Hboot is only 1.14.... Is there a website I can go to download a sense 4+ rom ?
You don't ever need to go anywhere except XDA for information and software for your phone. Specifically you need to stay within this forum you're posting in now. Here's the main page for our device:
http://forum.xda-developers.com/one-x-att
And here's our two development sections:
http://forum.xda-developers.com/one-x-att/development (Sense ROMs)
http://forum.xda-developers.com/one-x-att/orig-development (aosp ROMs)
You'll find what you need there, any Sense 4 ROM will be fine.
Sent from my Evita
S-Off
So I installed Rage XL Evita V2.1 rom and it works... Next I tried to use the Rumrunner method to S-off but here's what I get...
==================== rumrunner S-OFF 0.5.0 ==============================
rumrunner S-OFF comes with NO WARRANTY (express or implied)
and NO GUARANTEE OF FITNESS for any particular task.
We have made every effort we can to make this a safe process for users
however the authors disclaim any liability for damage to your phone
or other materials or devices used during this process.
The entire risk of running rumrunner S-OFF lies with you, the user.
By using this software you acknowledge and accept that the authors
are not liable for any loss, material or otherwise howsoever caused.
Do you understand the implications of this warning?
(Yes/No)
Yes
Dear User: We will expect that YOU:
(1) Know how to use ADB and FASTBOOT binaries
---- [Yes, use these tools to test USB connection BEFORE running rumrunner] ----
(2) Realize that rumrunner S-OFF cannot support every CUSTOM rom in this world
(3) Understand that irc support IS NOT A GENERAL HELPDESK
(4) Are able to identify and download the CORRECT package for YOUR device
(5) Know how to enable USB-debugging on YOUR device (Yes, do that now)
(6) Understand that you may NOT repack or redistribute rumrunner S-OFF
Ok?
(Yes/No)
Yes
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (9/120)
Waiting
Test 2: Booting device
Waiting for ADB (37/120)
must ferment longer...
must sanitize, skunky rum is nasty
hold please..............................................
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (9/120)
FATAL: Download updated package at rumrunner.us
Press ENTER to exit
Any idea on the problem ? I did follow instructions and use the Universal HTC Download 0.5.0....
It might be an incompatibility issue with the Rage XL ROM, you could try the Facepalm s-off method instead. You'll find it here.
Sent from my Evita
NVM
Sorry please ignore previous post, finally got it to work. Hboot 1.14, S-Off and RageXL Evita V 2.1 atm, I am currently downloading the 3.18 RUU.. Thanks a lot for the help will let you know if I have any more questions....
Cool, glad it worked. Yell out if you have any further issues.
Sent from my Evita
error Device Not found
Thanks, current status is
*****UNLOCKED******
EVITA PVT SHIP S-OFF RL
CID- 11111111
HBOOT- 2.14.0000
Radio- 0.24p.32.09.06
So I ran and updated the RUU, unfortunately after it did it somehow deleted my twrp I had installed so i cant mount and flash/ install other roms, I tried to re flash TWRP 2.6 for evita but it keeps telling me thers an error and device not found.. So I reinstalled the drivers, and when I check in my device manager I can see my HTC with it's driver installed, I even get a sign at the right bottom of my screen telling me the device is ready to be used but when I run fastboot flash openrecovery....., once again device not found... Any suggestions on what to do next ?
Can't Root
I tried rooting like I did before but couldn't, heres what I get..
Rooting...
Start Rooting...
failed on '/data/local/tmp' - Permission denied
link failed File exists
reboot #1 - DO NOT DISCONNECT YOUR DEVICE!
/system/bin/sh: can't create /data/local.prop: Permission denied
reboot #2 - DO NOT DISCONNECT YOUR DEVICE!
remount failed: Operation not permitted
failed to copy 'su' to '/system/bin/su': Read-only file system
Unable to chown /system/bin/su: No such file or directory
Unable to chmod /system/bin/su: No such file or directory
rm failed for /system/xbin/su, No such file or directory
link failed Read-only file system
failed to copy 'Superuser.apk' to '/system/app/./Superuser.apk': Read-only file
system
rm failed for /data/local.prop, No such file or directory
rm failed for /data/local/tmp, Permission denied
failed on '/data/local/tmp.bak' - No such file or directory
1102 KB/s (1075144 bytes in 0.952s)
mount: permission denied (are you root?)
/system/xbin/busybox: cannot open for write: Read-only file system
Unable to chown /system/xbin/busybox: No such file or directory
Unable to chmod /system/xbin/busybox: No such file or directory
/system/bin/sh: /system/xbin/busybox: not found
rebooting
I am guessing this is why I can't flash twrp, tried also to flash through android ( Recovery Tools ) I get that my phone isn't rooted...
Another fail
I tried another method still not rooted....
C:\Users\Sam.Sam-PC\Downloads\OneXRootOneClick>adb devices
List of devices attached
HT24YW310539 device
C:\Users\Sam.Sam-PC\Downloads\OneXRootOneClick>adb push oneXchopper /data/local/
tmp/xpwn
2329 KB/s (1283460 bytes in 0.538s)
C:\Users\Sam.Sam-PC\Downloads\OneXRootOneClick>adb push busybox /data/local/tmp/
busybox
2445 KB/s (811432 bytes in 0.324s)
C:\Users\Sam.Sam-PC\Downloads\OneXRootOneClick>adb push ownage /data/local/tmp/p
hase1.sh
57 KB/s (296 bytes in 0.005s)
C:\Users\Sam.Sam-PC\Downloads\OneXRootOneClick>adb shell chmod 755 /data/local/t
mp/xpwn /data/local/tmp/busybox
C:\Users\Sam.Sam-PC\Downloads\OneXRootOneClick>adb shell ln -s /data/local/tmp/b
usybox /data/local/tmp/sed
link failed File exists
C:\Users\Sam.Sam-PC\Downloads\OneXRootOneClick>adb shell "/data/local/tmp/xpwn"
[+] This may take a few minutes.
[-] Failure.
ysfsam said:
Thanks, current status is
*****UNLOCKED******
EVITA PVT SHIP S-OFF RL
CID- 11111111
HBOOT- 2.14.0000
Radio- 0.24p.32.09.06
So I ran and updated the RUU, unfortunately after it did it somehow deleted my twrp I had installed so i cant mount and flash/ install other roms, I tried to re flash TWRP 2.6 for evita but it keeps telling me thers an error and device not found.. So I reinstalled the drivers, and when I check in my device manager I can see my HTC with it's driver installed, I even get a sign at the right bottom of my screen telling me the device is ready to be used but when I run fastboot flash openrecovery....., once again device not found... Any suggestions on what to do next ?
Click to expand...
Click to collapse
Of course it deleted TWRP, it returns your phone to a stock state. I did mention you'd have to flash TWRP again after the RUU.
Sent from my Evita
---------- Post added at 05:26 AM ---------- Previous post was at 05:23 AM ----------
ysfsam said:
I tried rooting like I did before but couldn't, heres what I get..
Rooting...
Start Rooting...
failed on '/data/local/tmp' - Permission denied
link failed File exists
reboot #1 - DO NOT DISCONNECT YOUR DEVICE!
/system/bin/sh: can't create /data/local.prop: Permission denied
reboot #2 - DO NOT DISCONNECT YOUR DEVICE!
remount failed: Operation not permitted
failed to copy 'su' to '/system/bin/su': Read-only file system
Unable to chown /system/bin/su: No such file or directory
Unable to chmod /system/bin/su: No such file or directory
rm failed for /system/xbin/su, No such file or directory
link failed Read-only file system
failed to copy 'Superuser.apk' to '/system/app/./Superuser.apk': Read-only file
system
rm failed for /data/local.prop, No such file or directory
rm failed for /data/local/tmp, Permission denied
failed on '/data/local/tmp.bak' - No such file or directory
1102 KB/s (1075144 bytes in 0.952s)
mount: permission denied (are you root?)
/system/xbin/busybox: cannot open for write: Read-only file system
Unable to chown /system/xbin/busybox: No such file or directory
Unable to chmod /system/xbin/busybox: No such file or directory
/system/bin/sh: /system/xbin/busybox: not found
rebooting
I am guessing this is why I can't flash twrp, tried also to flash through android ( Recovery Tools ) I get that my phone isn't rooted...
Click to expand...
Click to collapse
I'm not sure why you're doing that again, that process doesn't root your phone, it gives you SuperCID which you already have. There's no point in trying that again. No your phone isn't rooted, in order for it to be rooted you need TWRP installed first so you can install root or a rooted ROM. You just need to work out why fastboot isn't working and you'll be good to go.
This may seem like a stupid question but I have to ask it, is the phone in fastboot mode when you're trying the fastboot commands? If it is and you're still having problems, try uninstalling your drivers, then download HTC Sync Manager from HTC.com, once that's installed connect your phone while booted into Android and it'll make sure the right drivers are installed.
Sent from my Evita
READ THIIS!
*this thread is for E8. it will NOT work on m7,or any older device. please check the general forum for your particular device for a similar thread.
_____________________________________________________________________________________________________________________
this thread is for the folks who wish tochage their MID in order to fully convert a device and recieve OTA updates. the method described here is not the only way to skin the cat,but as long as your careful the risk is very minimal, its quick and easy and doesnt require any hboot downgrades,eng hboot install,data loss,or having to run an ruu.
please note that s-off is required!
credits:
-beaups for schooling me on the echo command protocol
-kdj67f for dumping partitions from his java card s-offed phone
-davehasninjas for dumping rumrunner s offed partitions
-andybones for testing on a vzw device
*i dont have E8. ian.anindya and a couple others have tested and provided dumps. please let me know and ill add you to the credits. also if someone wants to provide a copy of there cmd window doing the process,ill update that as well
standard disclaimer: use this information at your own risk. it has been tested,but copying the command incorrectly could have consequences. if you melt your phone into a smoldering little pile of aluminum goo, its not my fault.
secondary disclaimer: please use caution what mids you try and change. some devices may NOT be capable of being covertable to other devices due to available radio bands. in these cases,conversion may result in a bricked,or non-finctional device and may not be recoverable. i dont have the knowledge of E8 to say whats safe and whats not.
reference: http://forum.xda-developers.com/one-e8/help/htc-one-e8-mid-cid-ruu-ota-twrp-t2903210 make sure to hit the thanks button for @ian.anindya
IF you are an advanced user with adb/fastboot set up and some basic knowlede of the cmd window,you can skip to #2
1)set up adb(windows 7 and older)
-download this file
-install drivers: if you have htc sync installed,you should allready have drivers. if not,you can install htc sync,or install these modified htc drivers from revolutionary (driver mirror)
-unzip your miniadb_v1031.zip file. this is native funtionality in windows 7. you otherwise may need a utility such as "7-zip" to extract,or unzip it. place the unzipped folder onto the root of your C drive on your PC. root means the top level,not inside any folders. so just copy and paste,or drag and drop the folder onto C with everything else that is there. you may want to rename it to "miniadb_m7" since youll be putting some device specific files in here.
-open a command window. on windows 7,click the start bubble in the lower left and type "command" in the search box. xp i believe is similar or the same. doing this should open a small black command window.
-change to your miniadb_m7 directory. type the following at the prompt in your cmd window:
cd c:\miniadb_m7
your command promt should change to "c:miniadb_m7>" provided you: 1)unzipped the miniadb_v1031 zip file,and 2)put the folder on your c drive,and 3)entered the name of the folder correctly ("miniadb_m7" in this case)
-now make sure usb debugging is checked in developer options(you will need to turn it on first),and plug your phone into your PC with a usb cable
-make sure your phone is being recognized- type:
adb devices
if your drivers are installed correctly,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.
if you get your serial number back,then enter this command:
adb reboot bootloader
this should take your phone to the "fastboot" screen,wich is white with colored letters. this is one mode of your bootloaders interactive modes. at the top youll see fastboot devices as confirmation youre in fastboot.
now enter:
fastboot devices
again,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.
if you get your serial number back,you can enter the following to boot back to the phones OS:
fastboot reboot
and now,youve installed adb/fastboot and tested youre phones drivers. if at either spot,you have trouble and dont get your serial number back,there is some sort of connection issue. use these steps to troubleshoot:
troubleshooting connectivity issues:
-try a reboot of the PC
-try different usb cables and ports
-dont use a usb hub
-dont use usb 3.0
-make sure nothing capable of comunicating with the phone is enabled and running. htc sync,pdanet,easy tether,and even itunes have all been known to cause issues.
-windows 8 has been known to have issues. try a windows 7 or older machine
failing the above,
-i use these drivers for fastboot and adb(donwload and run as admin): http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe (mirror)
failing that,try manually updating the drivers in the following manner:
-put the phone in fastboot mode(select fastboot from the hboot menu)
-open device manager on the PC
-plug in phone,watch for it to pop up in device manager.
-update drivers with device manager,pointing the wizard to the extracted
driver download folder from above
note that you can check the connectivity of the phone,and make sure drivers are working by in the following manner:
-open cmd window. change to directory containing adb/fastboot utilities
-adb with the phone in the booted OS,usb debug enabled,enter:
adb devices in a cmd window
-fastboot with phone in fastboot,enter:
fastboot devices in cmd window
in either case,a properly connected phone with working drivers installed should report back the phones serial number.
Click to expand...
Click to collapse
this process,in your cmd window,should look something(but not exactly) like this:
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Scott>[COLOR="red"]cd c:\miniadb_m7[/COLOR]
c:\miniadb_m7>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
FAxxxxxxxxxx device
c:\miniadb_m7>[COLOR="red"]adb reboot bootloader[/COLOR]
c:\miniadb_m7>[COLOR="red"]fastboot devices[/COLOR]
FAxxxxxxxxxx fastboot
c:\miniadb_m7>[COLOR="red"]fastboot reboot[/COLOR]
rebooting...
finished. total time: 0.037s
c:\miniadb_m7>
2)change your MID
warning: *do not try and type the command. please copy and paste it
-0PAJ10000:
enter the following:
adb shell
su (if needed to get a # prompt)
Code:
[B]echo -ne '\x30\x00\x50\x00\x41\x00\x4A\x00\x31\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384[/B]
(the above is one big long command. make sure you copy it all,and dont get extra spaces when you paste it.)
exit
adb reboot bootloader
fastboot getvar mid (or getvar all)
verify 0PAJ10000 for modelid
fastboot reboot
________________________________________________________________________________________
your command window should look something(but not exactly) like this:
Code:
c:\miniadb_m7>[COLOR="red"]adb shell[/COLOR]
[email protected]:/ # [COLOR="Red"]echo -ne '\x50\x00\x4e\x00\x30\x00\x37\x00\x33\x00\x31\x00\x30\x00\x
30\x00\x30' | dd of=/dev/block/mmcblk0p6 bs=1 seek=16384[/COLOR]
00\x30' | dd of=/dev/block/mmcblk0p6 bs=1 seek=16384 <
17+0 records in
17+0 records out
17 bytes transferred in 0.009 secs (1888 bytes/sec)
[email protected]:/ # [COLOR="red"]exit[/COLOR]
exit
c:\miniadb_m7>[COLOR="red"]adb reboot bootloader[/COLOR]
c:\miniadb_m7>[COLOR="red"]fastboot getvar all[/COLOR]
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.17.3250.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.27.531.8
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HTxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000 [COLOR="Blue"]<-looky[/COLOR]
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4175mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-f188f379dbbfee373cd551f7bc62b8435
getvar:all FAILED (unknown status code)
finished. total time: 0.092s
c:\miniadb_m7>[COLOR="Red"]fastboot reboot[/COLOR]
rebooting...
(bootloader) hbootpreupdate: 11
finished. total time: 7.288s
some other useful links:
remove tampered banner: http://forum.xda-developers.com/one-e8/general/how-to-remove-tampered-banner-t3019164
change lock status flag(lock/unlock bootloader):
other mids
0PAJ20000
Code:
echo -ne '\x30\x00\x50\x00\x41\x00\x4A\x00\x32\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
____________________________________________________________________________________________________________________________
0PAJ21000
Code:
echo -ne '\x30\x00\x50\x00\x41\x00\x4A\x00\x32\x00\x31\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
_______________________________________________________________________________________________________________________
0PAJ30000
Code:
echo -ne '\x30\x00\x50\x00\x41\x00\x4A\x00\x33\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
_______________________________________________________________________________________________________________________
0PAJ31000
Code:
echo -ne '\x30\x00\x50\x00\x41\x00\x4A\x00\x33\x00\x31\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
_______________________________________________________________________________________________________________________
0PAJ40000
Code:
echo -ne '\x30\x00\x50\x00\x41\x00\x4A\x00\x34\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
_______________________________________________________________________________________________________________________
0PAJ50000
Code:
echo -ne '\x30\x00\x50\x00\x41\x00\x4A\x00\x35\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
_______________________________________________________________________________________________________________________
also mine!
Worked fine here.... Tnx
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.30306251.17_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid:
(bootloader) product: mec_dugl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0PAJ21000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 87bcfea0
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Can we change:
product: mec_dugl
to
product: mec_dwgl
DutchDanny said:
Can we change:
product: mec_dugl
to
product: mec_dwgl
Click to expand...
Click to collapse
I haven't looked in to that,and for the most part it does not seem to be needed. I've converted m7_u to m7_ul variants without changing the product id and ruus, otas,etc work fine.
However... Just because you can,does not mean that you should. Folks have found that's its not a good idea to try and convert cdma world phones to gsm variants. For example m7_wlv to m7_ul.
So use caution in the conversions that you attempt
Sent from my HTC One max
I only changed MID and am on stock mec_dwgl.... Let's see what happens when ota arrives
Sent from my HTC One_E8 dual sim using Tapatalk
DutchDanny said:
I only changed MID and am on stock mec_dwgl.... Let's see what happens when ota arrives
Sent from my HTC One_E8 dual sim using Tapatalk
Click to expand...
Click to collapse
Hi DutchDanny,
Would be grateful if you could help me with a query. I would like to change my Indian M8Sd (mec_dwgl, HTC__038, 0PAJ40000) to change into EU M8Sw (mec_dugl, HTC__001, 0PAJ21000) so that I can flash the latest EU OTA. I have done CID/MID mod before and tried chinese RUU (this was not much of a success as the phone kept rebooting).
I am using the phone in the UK and desperately trying to get 4g/LTE. What do you think the prospects of success?
Many thanks.
parthasd said:
Hi DutchDanny,
Would be grateful if you could help me with a query. I would like to change my Indian M8Sd (mec_dwgl, HTC__038, 0PAJ40000) to change into EU M8Sw (mec_dugl, HTC__001, 0PAJ21000) so that I can flash the latest EU OTA. I have done CID/MID mod before and tried chinese RUU (this was not much of a success as the phone kept rebooting).
I am using the phone in the UK and desperately trying to get 4g/LTE. What do you think the prospects of success?
Many thanks.
Click to expand...
Click to collapse
converting to another variants firmware/software will NOT let you have different radio bands. this is mainly to run different stock software,and recieve stock OTA updates.
radio bands are at a much deeper level within the phone,and not accessible. youll pick up the same bands after a conversion as you do before.
as ive mentioned,be extremely careful what you do. trying to install gsm softare and firmware on a cdma,or cdma/gsm "world phone" or vice versa can cause irreversable damage and even hard bricks in some scenarios.
my advice would be if you cannot use your device as is,sell it and obtain a device intended for the region/carrier that you want to use it in.
parthasd said:
Hi DutchDanny,
Would be grateful if you could help me with a query. I would like to change my Indian M8Sd (mec_dwgl, HTC__038, 0PAJ40000) to change into EU M8Sw (mec_dugl, HTC__001, 0PAJ21000) so that I can flash the latest EU OTA. I have done CID/MID mod before and tried chinese RUU (this was not much of a success as the phone kept rebooting).
I am using the phone in the UK and desperately trying to get 4g/LTE. What do you think the prospects of success?
Many thanks.
Click to expand...
Click to collapse
I did change my M8sw China model successful to M8sw EU
You can read how I did this and try it at your own risk HERE
help to s-off
can anyone help me to s-off. I'm using M8sd OPAJ400 Indian dual sim
scotty1223 said:
0PAJ20000
Code:
echo -ne '\x30\x00\x50\x00\x41\x00\x4A\x00\x32\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
____________________________________________________________________________________________________________________________
0PAJ21000
Code:
echo -ne '\x30\x00\x50\x00\x41\x00\x4A\x00\x32\x00\x31\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
_______________________________________________________________________________________________________________________
0PAJ30000
Code:
echo -ne '\x30\x00\x50\x00\x41\x00\x4A\x00\x33\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
_______________________________________________________________________________________________________________________
0PAJ31000
Code:
echo -ne '\x30\x00\x50\x00\x41\x00\x4A\x00\x33\x00\x31\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
_______________________________________________________________________________________________________________________
0PAJ40000
Code:
echo -ne '\x30\x00\x50\x00\x41\x00\x4A\x00\x34\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
_______________________________________________________________________________________________________________________
0PAJ50000
Code:
echo -ne '\x30\x00\x50\x00\x41\x00\x4A\x00\x35\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
_______________________________________________________________________________________________________________________
Click to expand...
Click to collapse
thanks for this great post, can you please share the command for m8sy taiwan mec dual opaj 22000. cant seem to find it any where since i bought this device but the meid was modified
sherazshery said:
thanks for this great post, can you please share the command for m8sy taiwan mec dual opaj 22000. cant seem to find it any where since i bought this device but the meid was modified
Click to expand...
Click to collapse
Code:
echo -ne '\x30\x00\x50\x00\x41\x00\x4A\x00\x32\x00\x32\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
assuming your mid is in the same place. i am not familiar with that model(and this is the E8 forum)
scotty1223 said:
Code:
echo -ne '\x30\x00\x50\x00\x41\x00\x4A\x00\x32\x00\x32\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
assuming your mid is in the same place. i am not familiar with that model(and this is the E8 forum)
Click to expand...
Click to collapse
Thanks for the quick reply
Complete model no. Is
HTC E8 Dual Sim(blue color) MEC_DUGL M8SY OPAJ22000
The command u shared is for this model?
scotty1223 said:
Code:
echo -ne '\x30\x00\x50\x00\x41\x00\x4A\x00\x32\x00\x32\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
assuming your mid is in the same place. i am not familiar with that model(and this is the E8 forum)
Click to expand...
Click to collapse
thanks for your great post....is this for 0PAJ22000 ?????
when i input this text , adb dont give me any reaction ...are you know reason ???
my phone is s-off and supercid and unlock
HTC one E9 change MID
Hello friends !
I'm new one to xda.
please give me a code for this mid.
MID = 0PL312000
DutchDanny said:
Can we change:
product: mec_dugl
to
product: mec_dwgl
Click to expand...
Click to collapse
I got error "Permission Denied" plz help i need to change Chinese version to EU
Alizpk said:
I got error "Permission Denied" plz help i need to change Chinese version to EU
Click to expand...
Click to collapse
I don't have al the information anymore.
But are you s-off & supercid?
Yes I'm s off and super cid
DutchDanny said:
I don't have al the information anymore.
But are you s-off & supercid?
Click to expand...
Click to collapse
Yes S-off and supercid
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.