I know about logcat, but fit seems to be a shell command, and it does not seem to be working when I am in recovery mode. I also know the recovery.log. But I still like to see what is happening in real time with my own two eyes. Is there some way of activating logcat while you are in recovery? It seems like I can shell into my device. I get this error
Code:
/sbin/sh: exec: line 1: logcat: not found
when I try to issue
Code:
./adb logcat
command. I created an image with Android Kitchen which seems to be installed waaaay too fast. i.e. I get a successful confirmation from TWRP, but when I try to reboot the device I get an error stating that there is no OS installed.
sansari123 said:
I know about logcat, but fit seems to be a shell command, and it does not seem to be working when I am in recovery mode. I also know the recovery.log. But I still like to see what is happening in real time with my own two eyes. Is there some way of activating logcat while you are in recovery? It seems like I can shell into my device. I get this error
Code:
/sbin/sh: exec: line 1: logcat: not found
when I try to issue
Code:
./adb logcat
command. I created an image with Android Kitchen which seems to be installed waaaay too fast. i.e. I get a successful confirmation from TWRP, but when I try to reboot the device I get an error stating that there is no OS installed.
Click to expand...
Click to collapse
I may be way off, but you tried Galaxy Tool by idone. Here is the link http://forum.xda-developers.com/not.../app-one-click-hotspot-enabler-menus-t2816159 it has the ability to access logcats and sys dumps, might be worth a try ?
jimzweb1 said:
I may be way off, but you tried Galaxy Tool by idone. Here is the link http://forum.xda-developers.com/not.../app-one-click-hotspot-enabler-menus-t2816159 it has the ability to access logcats and sys dumps, might be worth a try ?
Click to expand...
Click to collapse
Hey thanks. I'll have a look at it. I got some stuff with ./adb logcat. I had to reinitialize the tool a few times but TWRP is worth it's weight in gold. I have not had the opportunity to try some of the other recoveries out there. But that is because TWRP does all the things I need to do.
sansari123 said:
Hey thanks. I'll have a look at it. I got some stuff with ./adb logcat. I had to reinitialize the tool a few times but TWRP is worth it's weight in gold. I have not had the opportunity to try some of the other recoveries out there. But that is because TWRP does all the things I need to do.
Click to expand...
Click to collapse
No problem, I have used both TWRP and CWM. In the past I was not possible to switch, and use the backups from one to the other. Now that's changed and they are basically compatible making the choice between them just a personal preference. Let me know if the Galaxy Tool Hidden menu app helped ?
Hi all,
I have been through douzens of threads and forums looking for a solution to this.
I followed some instructions to modify the build.prop file on my Huawei G535-L11 to disable Huawei theme manager in order to get Xsposed working fully (changed ro.config.hwtheme: 0). I did a backup of my original build.prop before hand, and my phone was rooted and unlocked but running the stock rom.
Unfortunately, it rebooted but won't go past the first 'EE' splash screen (just turns off again).
I can inconsistently get in to both fastboot and Android recovery, so I have been trying to use adb to push the original build.prop to /system/ on the phone.
However, this fails as /system/ is apparently RO. I have now discovered that I can't get SU permissions despite my phone being rooted.
If I try:
adb shell
$ su
nothing happens and it goes back to a $ prompt.
If I try:
adb root
I get the message (paraphrased):
adb cannot run as root in production builds.
So I can't push or do any adb method of restoring the build.prop file?! I don't understand why it is acting as if it is not rooted. I had Link2sd, Gravity Box, No Frills Cpu Controller all set up and working before, so I'm fairly sure I did truly have root.
I have also tried flashing a TWRP recovery, which apparently is successful, but when I go in to recovery it is still the Android Recovery.
Does anyone have any ideas what I could do to get my phone working again please?! This is my last gasp before the phone gets filed under 'B' in the cylindrical cabinet in the corner of the room!
Any assistance greatly appreciated!
Some systems are very finicky with modded build.props, or you didn't set the file's permissions correctly. I'm afraid without being able to boot or a working custom recovery, then adb won't work, much less root enabled adb functions. adb works in some stock recoveries, but only for sideloading files directly signed by the manufacturer. In regards to TWRP, is the bootloader unlocked? If not, that would explain why it didn't work. Other than that, I don't believe you'll have any other options besides reloading the stock firmware.
Hi,
Thanks for the reply. Yes, the bootloader was / is unlocked.
Unfortunately, there isn't any stock firmware available anywhere. Unless someone out there has a backed up rom image from the EE Kestrel?
This is supposed to be a working TWRP for your device http://forum.xda-developers.com/showpost.php?p=58522448&postcount=117 - if you get it loaded, there might be a chance to push the working build.prop back to the phone. I would read that thread too and see if there isn't more useful info there or another member with your phone that could make a backup for you. Good luck.
Thanks.
Unfortunately, I'm pretty sure that is the TWRP I've tried. I'll double check when I'm on my PC.
I might try requesting a rom image on that thread, but the community for this phone seems to be pretty dead :/
I've just gone and ordered a new phone anyway, but it seems like a waste of a good phone just for the sake of one line of bad code!
Thanks for your help. I'll post again if I have any success.
Is there any way to get root access on OPX while the boot loader remains locked? Running stock firmware (Oxygen 2.2.3, Android v5.1.1).
I would like to export all my saved WiFi network settings, for importing onto another OPX (running AOSIP 8.1). Without root, the /etc/wifi/wpa_supplicant.conf file is basically empty (and has a timestamp of 6/10/2015). Is that even the correct location for the live wpa_supplicant file on OPX?
I don't think the boot loader can be unlocked without wiping the data? Which is obviously not going to help me in this situation. And I don't think Magisk or SuperSU can be installed without unlocking the bootloader?
I've tried Kingroot, but that won't even install. Is there a DirtyCow temporal root tool for OPX? I've not come across one. The only solution that looks like a possibility is the One Plus Engineering Mode root procedure: https://gist.github.com/aldur/b785257ac26d23bce648cad3ce2f6dc8. Does that work on OPX? It certainly seems to have the engineering mode tools on mine. And I think the ROM is old enough that it won't have been patched/removed?
Can I just ADB this command:
Code:
adb shell am start -n com.android.engineeringmode/.qualcomm.DiagEnabled --es "code" "angela"
and then start shell to try and access/transfer the proper wpa_supplicant.conf file? And then after, can I dial *#8011# to close root?
Is it possible that this will work without tripping SafetyNet, or is that inevitable? I'd rather not bork my stock phone by making it fail SafetyNet, avoiding all the Magisk rigmarole if possible.
Title says it all. I haven't gotten past root because every rooter I try fails. Tried rooting on 4.5.5.1 and .2, hoping .3 would solve any issues but it didn't. Really hoping to get a custom ROM on this thing, if anyone could help, much appreciated..
WSADKeysGaming said:
Title says it all. I haven't gotten past root because every rooter I try fails. Tried rooting on 4.5.5.1 and .2, hoping .3 would solve any issues but it didn't. Really hoping to get a custom ROM on this thing, if anyone could help, much appreciated..
Click to expand...
Click to collapse
No need to pre-root. Go for one of the bootloader unlock methods and profit.
https://forum.xda-developers.com/kindle-fire-hdx/general/thor-unlocking-bootloader-firmware-t3463982
https://forum.xda-developers.com/kindle-fire-hdx/general/multi-platform-1-click-bootloader-t3241014
Davey126 said:
No need to pre-root. Go for one of the bootloader unlock methods and profit.
https://forum.xda-developers.com/kindle-fire-hdx/general/thor-unlocking-bootloader-firmware-t3463982
https://forum.xda-developers.com/kindle-fire-hdx/general/multi-platform-1-click-bootloader-t3241014
Click to expand...
Click to collapse
Your first link shows root as a pre-requisite? Is it still not necessary?
WSADKeysGaming said:
Your first link shows root as a pre-requisite? Is it still not necessary?
Click to expand...
Click to collapse
It is not. This post offers nice summary of the necessary steps including required files.
Davey126 said:
It is not. This post offers nice summary of the necessary steps including required files.
Click to expand...
Click to collapse
I get this error when I run get_code.bat even though running 'adb devices' shows my hdx.
* daemon not running; starting now at tcp:5037
* daemon started successfully
adb: error: failed to copy 'cuber' to '/data/local/tmp/cuber': couldn't read from device
cuber: 0 files pushed. 0.1 MB/s (506072 bytes in 5.020s)
error: no devices/emulators found
error: no devices/emulators found
adb: error: failed to get feature set: no devices/emulators found
error: no devices/emulators found
Press any key to continue . . .
WSADKeysGaming said:
I get this error when I run get_code.bat even though running 'adb devices' shows my hdx.
* daemon not running; starting now at tcp:5037
* daemon started successfully
adb: error: failed to copy 'cuber' to '/data/local/tmp/cuber': couldn't read from device
cuber: 0 files pushed. 0.1 MB/s (506072 bytes in 5.020s)
error: no devices/emulators found
error: no devices/emulators found
adb: error: failed to get feature set: no devices/emulators found
error: no devices/emulators found
Press any key to continue . . .
Click to expand...
Click to collapse
Choices:
- do some basic troubleshooting to resolve the issue (first line offers a clue)
- use the 1-click method
Although preferable you do not need to execute get_code.bar prior to flashing the vulnerable bootloader (aboot) which is where the real magic lies. That said, a mistake at this stage can result in a black screen 'soft-brick' that is difficult to recover. Probably best to stick with 1-click.
Davey126 said:
Choices:
- do some basic troubleshooting to resolve the issue (first line offers a clue)
- use the 1-click method
Although preferable you do not need to execute get_code.bar prior to flashing the vulnerable bootloader (aboot) which is where the real magic lies. That said, a mistake at this stage can result in a black screen 'soft-brick' that is difficult to recover. Probably best to stick with 1-click.
Click to expand...
Click to collapse
Called in sick to work to spend the rest of the day googling my way thru this process and got it to 7.1.2
Sorry guys. I have exactly the same issue as in post #5 above. I do not want a one click type of solution. I would like to understand what the problem is and how to get the right drivers to fix the damn thing. I tried a dozen different drivers, installed correctly, with full reboots, etc, and nothing gets into that device. I use Windows 10. Thank you for any positive thought and solution.
[Thor][Apollo] Unlocking bootloader with any firmware
Hello. At first, I did not invent anything new, just checked some my guess on a other motherboard. All thanks and credits to our great developers. As always, all at your own risk. It does not work on the Fire HDX 8.9 (Saturn)! All steps in this...
forum.xda-developers.com
Reichmann aka realm mann, had the easiest guide imo.
Got a apollo unlocked and twrp'd in 30 minutes.
But take note you are expected to rename aboot file to "aboot_vuln.mbn"
And twrp to whatever the guide prints for the dd command. (I dont recall but just rename your twrp file to whatever that dd command references.)
Doesnt matter what windows. Or at least worked a treat on win7 for me. Reichmann used 10.
Make sure your key code file is generated or if you continue might be bricked judgjng from other posts.
Make sure you typed the commands exactly. Wmic commands are easy to mess up and could be confusing.
If you get an error double check every character of text.
Your disk index result number from wmic command replaces the X after Harddisk in dd command.
But if you dont get the same disk index result from all 3 wmic command or an error? Probably mistyped. Like "partiton".
Just double check and proof read.
Doesnt matter if you do mistype it as long as you retype it correctly eventually.
Yesterday, decided to remove bloatware(mostly Google) on my Huawei p8 lite using ADB. And somehow removed this.
:/ $ pm uninstall -k --user 0 com.android.location.fused
Restarted.
Boot Loop.
Before I rebooted my phone usb debugging was on.
Phone boots into eRecovery with 4 options
1)Download latest version and recovery(usuless gives my an "Getting package info failed")
2)Wipe data/factory reset
3)Reboot
4)Shutdown
When I'm connected to pc I allways get a message "Unable to open MTP device".
I don't have the root privalage so I can't folow these steps in this guide below.
Bootloop after removing com.android.location.fused [SOLVED]My questions is:
1. Any method of saving data on bootloop phone without root?
2. Should I try factory reset?
I don't understand what you want, but you can't root in boot loop.
But I hear you will root, it's really easy to root Huawei!
Guide.
1. Get your firmware, with hisuite, after install downgrade or update, will firmware file be saved in document folder on PC.
2. Extract files inside the firmware file, and find the boot.img, system.img or boot.img and opened it and modified, some you will and repack it again.
3. Update hash's for partition controller.
4. Make a form of server and port forward your device to think this is the server there get updating from and see request some your phone ask for or read source of Huaweis update.apk.
4. Configure your server, with coding and upload the firmware to your server.
5. Now just install your update and you have custom os
JonasHS said:
But I hear you will root, it's really easy to root Huawei!
Click to expand...
Click to collapse
This guide is missing most important predecessor step: unlocking bootloader (and therefore useless)
JonasHS said:
I don't understand what you want, but you can't root in boot loop.
Click to expand...
Click to collapse
Thanks for reply. Sorry that I not spicified. My problem is that I unistalled com.android.location.fused witch resulted in boot loop. My phone is not rooted and I don't know what to do next. Only think I can is factory reset, becouse eRecovery gives me an error. I just looking right now for any way to save my data. I found a similar problem solved, but person rooted phone before boot loop. So I guess I only have 1 option then?
You can try to start you Huawei in back up mode,
JonasHS said:
You can try to start you Huawei in back up mode,
Click to expand...
Click to collapse
Yes my phone in recovery mode. Should I try "Wipe data/factory reset"? Because "Download latest version and recovery" option gives me an error"Getting package info failed".
You don't need to unlock bootloader for edit system, i making my own exploit and do it.
O just look at this:
We say you can't edit Any software file on your device, because you don't has permission, like Linux nonroot user.
There are only 1 way to get this permission, it's unlocking bootloader and add your code to software.
NOT TRUE.
if we put this together with a door that's locked and you don't have the key, what do you do?
I will find another way to open the door.
so to show what i mean: update.apk ask server for download the update and send it back too your phone, and your phone will install. Inside an update package, where are boot.img and system.img, what if we edit this file before update, and put a code some will give your user on system the highest privilege. But we can't edit this file, because they are saved on folder, we don't has permission too?
For do this, can we manipulate the data server send back too us.
Prot forwarding.
JonasHS said:
You don't need to unlock bootloader for edit system, i making my own exploit and do it.
Click to expand...
Click to collapse
So you're a hacker and found method to properly sign system.img with huawei's private oem key? you're a genius!
https://android.googlesource.com/platform/external/avb/+/master/README.md#The-VBMeta-struct
Unfortunately the repair has to be done in /data/system/users/0/package-restrictions.xml and requires root access. Furthermore /data is encrypted therefore that modification can't be done offline, it requires booted android to stage where we can enter screen unlock pin (or at least to stage where /data/system is decrypted)
JonasHS said:
You don't need to unlock bootloader for edit system, i making my own exploit and do it.
O just look at this:
We say you can't edit Any software file on your device, because you don't has permission, like Linux nonroot user.
There are only 1 way to get this permission, it's unlocking bootloader and add your code to software.
NOT TRUE.
if we put this together with a door that's locked and you don't have the key, what do you do?
I will find another way to open the door.
so to show what i mean: update.apk ask server for download the update and send it back too your phone, and your phone will install. Inside an update package, where are boot.img and system.img, what if we edit this file before update, and put a code some will give your user on system the highest privilege. But we can't edit this file, because they are saved on folder, we don't has permission too?
For do this, can we manipulate the data server send back too us.
Prot forwarding.
Click to expand...
Click to collapse
That sounds awesome. I guess we can try.
aIecxs said:
So you're a hacker and found method to properly sign system.img with huawei's private oem key? you're a genius!
https://android.googlesource.com/platform/external/avb/+/master/README.md#The-VBMeta-struct
Unfortunately the repair has to be done in /data/system/users/0/package-restrictions.xml and requires root access. Furthermore /data is encrypted therefore that modification can't be done offline, it requires booted android to stage where we can enter screen unlock pin (or at least to stage where /data/system is decrypted)
Click to expand...
Click to collapse
Dahm.
The easiest way to fix bootloop is factory reset. There is no way to safe userdata without fixing bootloop, sorry. it's a hen and egg dilemma.
aIecxs said:
The easiest way to fix bootloop is factory reset. There is no way to safe userdata without fixing bootloop, sorry. it's a hen and egg dilemma.
Click to expand...
Click to collapse
I agree.
Just reset its easiest.
Think about this here: your PC has SSD or HDD and you can take it off and take it into new pc, and edit everythiny on the disk without admin and make a backup.
The true is, you can do the same with a phones chip, but it's hard to do
Next time, before playing with packages, do a backup of your pictures.
Btw you can unlock bootloader with PotatoNV and root with Magisk. rooted devices you can backup with Migrate or TWRP.
New to said:
Yes
Huawei don't store theres OEM keys on devices chip, so they will never could control if i replaced it with my own, and avb will still work in offline mode, so I can just read vbmeta.img with avbtool.py and generate the same vbmeta.img with different size or hash of partitions, some is benn modified.
Click to expand...
Click to collapse
You could me a hacker, i am not a hacker, i have just a good kwoning of code and dissembling
JonasHS said:
Just reset its easiest.
Think about this here: your PC has SSD or HDD and you can take it off and take it into new pc, and edit everythiny on the disk without admin and make a backup.
The true is, you can do the same with a phones chip, but it's hard to do
Click to expand...
Click to collapse
aIecxs said:
Next time, before playing with packages, do a backup of your pictures.
Btw you can unlock bootloader with PotatoNV and root with Magisk. rooted devices you can backup with Migrate or TWRP.
Click to expand...
Click to collapse
Thanks for replys(they gived me alot of ideas what I can learn about phone and hacking).I will be more careful about deleting packages in future.
I just did Factory reset and my phone is working fine again.
JonasHS said:
Huawei don't store theres OEM keys on devices chip, so they will never could control if i replaced it with my own, and avb will still work in offline mode, so I can just read vbmeta.img with avbtool.py and generate the same vbmeta.img with different size or hash of partitions, some is benn modified.
Click to expand...
Click to collapse
Of course they don't. No, you can't flash own vbmeta.img on locked bootloader as the bootloader verifies the hash of vbmeta which is oem signed (you don't have key).
If you know about any flash tool for HiSilicon Kirin exist (IDT?) it would probably easier to flash magisk patched (properly avb signed) ramdisk.img to get root access and adb (osm0sis AIK is capable of signing AVBv2) instead of modifying system.
Nevertheless this won't fix bootloop therefore it's pointless, as the culprit lies in package-restrictions.xml. it's impossible to decrypt userdata partition offline, so there is no hope sorry.
Who has told you this here, i am developer and has readers the source code, yes you can make your own sign keys with openssl
yes, that is called user-settable root of trust and requires you to compile own complete ROM, for example LineageOS. In any case that is impossible with stock EMUI as again you can't cheat Android Verified Boot chain of trust per design. That's the whole purpose of locked bootloader.