Hi, someone had acces to my phone and installed some crazy spyware that went into phones firmware. I flashed Havoc OS and different stock roms and it didnt change anything, as soon as i connect to the internet it starts downloading from Google Play bypassed No Root Firewall (didnt ask for permission or anything) and he starts messing with my phone (plays notifications sounds from messenger that i dont have installed, freezing/closing apps, drains battery etc). My guess is that there are some scripts in secondary and third bootloader or something idk, what im sure is that its definitley in firmware.
What can i do? I searched for Qualcomm Snapdragon 439 firmware, manufacturer doesnt post it and i cant find it. Chimera tool has an option for update but the license costs 120 euro and i dont know if its gonna work, im thinking it will only go away if i flash the entire thing.
Can anyone help me pls?
up
Run Logcat at Phone Boot Time
Hello, I'm trying to troubleshoot why some kernels result in bootloops on my phone and others work just fine. (For example, KingxKernel CFS #8 would work, but not #9-#11) I read somewhere about running a logcat during boot, but I have no idea...
forum.xda-developers.com
I dont know what to look for can u help me?
Hes still messing with my phone now i cant open wifi and i can't see it when i connect it to pc with usb.
Uploaded log here
https://raw.githubusercontent.com/pulshar18/mylog/main/mylog.txt
Theres some weird text at the very end
02-08 13:20:22.505 698 1733 D : readbrightness,out1:1231ÉÙÖc,‰®pœË±Ï.
up
upppppppp
You can download your Fastboot System Image here (source) and flash it with MI Flash using EDL mode (boot in Fastboot mode and run fastboot oem edl).
After the procedure is done, try running fastboot -w to wipe your userdata partitions. Ensure your bootloader is locked after this entire process.
If this doesn't fix your issue, a simple app is being used to troll you.
dgadelha said:
You can download your Fastboot System Image here (source) and flash it with MI Flash using EDL mode (boot in Fastboot mode and run fastboot oem edl).
After the procedure is done, try running fastboot -w to wipe your userdata partitions. Ensure your bootloader is locked after this entire process.
If this doesn't fix your issue, a simple app is being used to troll you.
Click to expand...
Click to collapse
Vett all apps especially side loaded ones. Disable auto downloads/install unknown apps.
Use only a cloud email app like gmail and download nothing from it.
dgadelha said:
You can download your Fastboot System Image here (source) and flash it with MI Flash using EDL mode (boot in Fastboot mode and run fastboot oem edl).
After the procedure is done, try running fastboot -w to wipe your userdata partitions. Ensure your bootloader is locked after this entire process.
If this doesn't fix your issue, a simple app is being used to troll you.
Click to expand...
Click to collapse
Its like windows bios malware, i flashed probably more than 10 stock roms and Havoc OS. I tried a couple of times with MI flash tool aswell, i doubt edl mode is gonna change anything. I wiped everything i can (cache, data, dalvik, system... whatever you can wipe in twrp).
blackhawk said:
Vett all apps especially side loaded ones. Disable auto downloads/install unknown apps.
Use only a cloud email app like gmail and download nothing from it.
Click to expand...
Click to collapse
Staff from Malwarebytes scanned my "apps report", its somewhere deeper.
up
pulshar18 said:
Staff from Malwarebytes scanned my "apps report", its somewhere deeper.
Click to expand...
Click to collapse
If it's in your data base you need to find it now.
If you have archived copies of it do not connect them to anything potentially infected.
Archive only to physically/electronically isolated hdds, etc.
When in doubt, zero fill the OS hdd* and reload the OS on the PC. If you keep a clone copy this shouldn't be a big deal (I keep at least 2 clone copies). Start with a known clean PC.
On the device, nuke it to the ground and use only known good firmware to reflash. Download it again to the known good PC.
Try adding the data base to the PC only after the phone is reloaded and known to be malware free, then to the phone.
If you can't find a good archived copy of the database you'll need to really think this through carefully. You risk lossing if not your whole data base, a lot of your time.
OS's are expendable, data bases are not.
Protect critical assets at all times and put a plan into effect to do so, now.
As soon as an infection or malware is recognized, it needs to be dealt with decisively, asap.
I'm ready to factory reset at any time, anywhere.
I don't care... I'll nuke it if needed.
One reason a stay stock is to avoid situations like this. Dirty firmware can really be too much fun.
*always use a physical dual drive setup whenever possible; a dedicated OS/programs drive and a data drive.
Related
I need to get my phone back to the original stock Android since Cyanogenmod wrecked it by disabling the phone dialing keys, but I can't because fastboot isn't working. What do I do? Apart from the number keys not working, everything else on the phone is fine.
I've spent 15 hours on this so far and if it doesn't get solved I have to throw my phone in the trash. I've read every word and gone through every step of the how-tos linked below, over and over and over and over.
In the command prompt my commands and responses are:
fastboot devices -> 'fastboot' is not recognized as an internal or external command, operable program or batch file
fastboot-windows devices -> nothing happens
fastboot-windows oem unlock -> <waiting for device>
http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
http://forum.xda-developers.com/nexus-4/general/tutorial-nexus-4-update-to-4-4-kitkat-t2534160
http://forums.androidcentral.com/ne...s-4-factory-image-restore-13.html#post3938684
Nexus 4
CyanogenMod 11.0 installer xnpq32p
Android 4.4.4
Do you HAVE fastboot on your computer and are in the correct directory to run the commands? Are you in the right mode on the phone? Check the Device Manager for driver errors?
But why not just update CM? There's obviously something that went wrong there because certainly CM doesn't usually have issues with the Dialer. Or just flash a stock rom in recovery.
es0tericcha0s said:
Do you HAVE fastboot on your computer and are in the correct directory to run the commands? Are you in the right mode on the phone? Check the Device Manager for driver errors?
But why not just update CM? There's obviously something that went wrong there because certainly CM doesn't usually have issues with the Dialer. Or just flash a stock rom in recovery.
Click to expand...
Click to collapse
Yes I had the tool.
Took half a day but I finally found Minimal ADB and Fastboot tool. Fortunately I sensed that everything must to be saved and extracted into one single folder, and the tool installed there - which the step-by-step guides either omit to mention or are vague about.
The dialer problem happened immediately upon installing CM, for the first time, the other day. So that was the latest version. Others have reported the same problem in the past and no one at CM replied. I'm leaving the country on a long trip and can't play with this any longer. I need a completely 100% working phone immediately.
If I had known that a so-called 'factory reset' does nothing of the kind, and getting back to stock is a such massive undertaking, I never would have considered messing with this.
fbtsrg said:
Yes I had the tool.
Took half a day but I finally found Minimal ADB and Fastboot tool. Fortunately I sensed that everything must to be saved and extracted into one single folder, and the tool installed there - which the step-by-step guides either omit to mention or are vague about.
The dialer problem happened immediately upon installing CM, for the first time, the other day. So that was the latest version. Others have reported the same problem in the past and no one at CM replied. I'm leaving the country on a long trip and can't play with this any longer. I need a completely 100% working phone immediately.
If I had known that a so-called 'factory reset' does nothing of the kind, and getting back to stock is a such massive undertaking, I never would have considered messing with this.
Click to expand...
Click to collapse
It's a factory DATA reset, not a restore your operating system option. It works exactly as it should, by removing user data and settings.
But for future reference, this is why you do a backup in recovery - so you can switch back in time of want or need.
times usbeae
es0tericcha0s said:
But for future reference, this is why you do a backup in recovery - so you can switch back in time of want or need.
Click to expand...
Click to collapse
- What do you mean by "backup in recovery"? What is that, and where is it?
- What do you mean by "switch back"? Switch back to what? The original state precisely as it was when I opened the box? Because ideally - if I ever root again - that is what I would like to be able to do in a simpler way than removing a bunch of drivers then installing new ones then enabling and disabling and re-enabling USB debugging then running ADB and fastboot and typing commands.
I guess I'm not clear on how it's possible to install Cynanogenmod by downloading an installer, click on two or three things, bam you're done - whereas removing it is an order of magnitude more complicated.
fbtsrg said:
- What do you mean by "backup in recovery"? What is that, and where is it?
- What do you mean by "switch back"? Switch back to what? The original state precisely as it was when I opened the box? Because ideally - if I ever root again - that is what I would like to be able to do in a simpler way than removing a bunch of drivers then installing new ones then enabling and disabling and re-enabling USB debugging then running ADB and fastboot and typing commands.
I guess I'm not clear on how it's possible to install Cynanogenmod by downloading an installer, click on two or three things, bam you're done - whereas removing it is an order of magnitude more complicated.
Click to expand...
Click to collapse
Well I would never have reason to use an installer (I prefer the "old school" manual methods) but CM couldn't install without a custom recovery, so not really sure how you don't know about that...? You can get to recovery from the bootloader screen accessed while off from Power + Vol Down for a few seconds. In recovery you can flash another rom or a stock based one. If you are S-On, you still need to fastboot flash the boot.img though. Have you checked your Device Manager for driver errors? I never have luck with this vintage of HTCs in fastboot on my Win 8.1 PC. I never have issues in Win 7 though. I actually keep a POS WIn 7 PC around just to work on HTCs.
So yea, the installer is helpful in making it simple to install, however, since you went the "easy" route, it seems like you missed out on a lot of reason to read through some threads and get some idea on what exactly you're doing and what's been done to the phone. It's best to walk before you run.
This thread may help you with your fastboot issues
http://forum.xda-developers.com/showthread.php?t=2277112
I was trying to figure out how to install a larger GApps package on my tablet, and I used GNU parted to do repartition. I've resized the system partition to 3GB and still can't install the full package.
Anyway I didn't do anything disastrous except that I accidentally deleted misc partition, I made a new partition and name it as misc and thought it was all good.
I didn't realize what I've done until I tried to reboot, my tablet is now completely a brick, the screen doesn't turn on no matter what I do
What can I do now? Is there any possible solution?
Nathaniel_Wu said:
I was trying to figure out how to install a larger GApps package on my tablet, and I used GNU parted to do repartition. I've resized the system partition to 3GB and still can't install the full package.
Anyway I didn't do anything disastrous except that I accidentally deleted misc partition, I made a new partition and name it as misc and thought it was all good.
I didn't realize what I've done until I tried to reboot, my tablet is now completely a brick, the screen doesn't turn on no matter what I do
What can I do now? Is there any possible solution?
Click to expand...
Click to collapse
If you can't see/access device in fastboot nothing can be done short of board replacement (factory/fastboot cables won't work). Even if it does respond in fastboot only a few have been successful in reviving the device after a repartitioning which is BAD idea on this device. I lack the necessary experience so will not be able to guide you further. Assumes an unlocked bootloader; you're done if device is still locked.
Davey126 said:
If you can't see/access device in fastboot nothing can be done short of board replacement (factory/fastboot cables won't work). Even if it does respond in fastboot only a few have been successful in reviving the device after a repartitioning which is BAD idea on this device. I lack the necessary experience so will not be able to guide you further. Assumes an unlocked bootloader; you're done if device is still locked.
Click to expand...
Click to collapse
Fastboot device list doesn't show anything… My bootloader is unlocked, but that doesn't matter now I guess…:crying:
hello i think minse one is break or so, was serving in internet it hang over, now it only starts in fastboot mode, wantet to flash twrp there but comes error: fash write failure, what can i do?
brill_e said:
hello i think minse one is break or so, was serving in internet it hang over, now it only starts in fastboot mode, wantet to flash twrp there but comes error: fash write failure, what can i do?
Click to expand...
Click to collapse
Can't flash or boot TWRP on this device. Consult index or other threads for info on reloading FireOS via stock recovery.
I have been through hell and high water today with this Nord N200 5G today. Soft Brick after Soft Brick. iI only flashed TWRP and try to boot into OS after exiting TWRP but i get No OS you sure you want to reboot?. I also can't figure out how to get my internal storage viewed in TWRP. I've read multiple guides and still can't figure it out. I"m pretty new to this so . and they try to flash Magisk for root as well as super su during on adventure fiasco after fiasco today. The Bootloader and OEM unlock was simple straight forward. Most Guides though are not in LAMENS terms and have abbreviations that new people do not understand. i have had to reflash my phone 20+ today with factory due to the NO OS problem with TWRP and can't get it so i can view my internal data from twrp even though i've followed several guides and the ones that says to do the wipe thing i always get the error about it can't mount the data or it has encountered and error 255 and by got try looking things up for those and you you get sent all over the place. So If there is Anyone Out There That would like to help an old geezer out to be able to get a stable TWRP and a Stable root going on please Respond. Sorry Had to Vent......
Oh yea and not to mention Unable to install 3.6.2
TWRP is not officially launched for this phone. In my opinion lineage is the best option for this phone as of now. It has a custom recovery and is easily rooted as well. https://forum.xda-developers.com/t/rom-official-dre-12l-lineageos-19.4473129/
weirdfate said:
TWRP is not officially launched for this phone. In my opinion lineage is the best option for this phone as of now. It has a custom recovery and is easily rooted as well. https://forum.xda-developers.com/t/rom-official-dre-12l-lineageos-19.4473129/
Click to expand...
Click to collapse
A couple of questions before I jump into that.
How are updates handled? Does the OS do auto-updates?
How is the camera?
I don't know a lot about this phone, but previous phones I've owned had proprietary camera/software, and any custom ROM not based on the stock OS lost camera quality because it couldn't use the proprietary software..
jova33 said:
A couple of questions before I jump into that.
How are updates handled? Does the OS do auto-updates?
How is the camera?
I don't know a lot about this phone, but previous phones I've owned had proprietary camera/software, and any custom ROM not based on the stock OS lost camera quality because it couldn't use the proprietary software..
Click to expand...
Click to collapse
Obviously not who you were asking but I just updated to Lineage and it was fairly straightforward following the directions, just make sure you're on Android 11. Updates can be done through settings menu, I just actually applied an update and it worked fine. It can check for updates every day, week, month if you choose I don't know if it will automatically update it though. Camera I have not tried as I don't use it as an everyday phone but generally from what I've seen it's common to have quality go down using software other than stock but I could be wrong.
I can't speak on the difference in camera quality because I dont use it much. There is some loss of function between the stock camera app and the aftermarket rom camera app
This phone has no official twrp so it has tons of decrypting issues which explains almost all of your problems.
What worked for me is to avoid touching the phone if at all possible while in TWRP. It's very unstable and if you click something it will try to mount partitions and somehow brick you in the process. While booted into TWRP I did almost everything via ADB command from my computer instead of through the TWRP menus, including reboot.
I Pushed my magisk package to /tmp instead which worked. I'm just going to go the lineage route later though. I don't think it's worth messing with TWRP on this device.
Update: Phone Complete Bricked. Says something like The Image(boot/recovery) has been destroyed please flash the correct image or call customer service to fix it. on top of this....Unable to flash anything. everything no matter what it is, i even tried to follow a guide to get back to factory and it say that no such partition or volume full. Oh and it's an A/B partition phone
swee08315 said:
What worked for me is to avoid touching the phone if at all possible while in TWRP. It's very unstable and if you click something it will try to mount partitions and somehow brick you in the process. While booted into TWRP I did almost everything via ADB command from my computer instead of through the TWRP menus, including reboot.
I Pushed my magisk package to /tmp instead which worked. I'm just going to go the lineage route later though. I don't think it's worth messing with TWRP on this device.
Click to expand...
Click to collapse
how do you push? ive tried the adb push and to no avail... it just keeps saying it's unable to. oh and when i did have twrp installed it wouldn't boot into the os unless i fastboot boot twrp.img then it would reset and finally boot into regular os
MiniNinja2024 said:
how do you push? ive tried the adb push and to no avail... it just keeps saying it's unable to. oh and when i did have twrp installed it wouldn't boot into the os unless i fastboot boot twrp.img then it would reset and finally boot into regular os
Click to expand...
Click to collapse
I believe it was just "adb push boot.img /tmp/boot.img"
And then in TWRP when selecting a file to flash you have to click on the top level option to go up a directory and find /tmp while not clicking anything else. I pushed to tmp to avoid mounting any partitions since the phone bricked everytime that happened.
swee08315 said:
I believe it was just "adb push boot.img /tmp/boot.img"
And then in TWRP when selecting a file to flash you have to click on the top level option to go up a directory and find /tmp while not clicking anything else. I pushed to tmp to avoid mounting any partitions since the phone bricked everytime that happened.
Click to expand...
Click to collapse
how do i get the phone completely unbricked cause it's saying something like The Image[boot,recovery] has been destroyed please flash correct image or contact customer service to fix it
I forgot to mention that I can no long get into recovery it won't even flash a recovery anymore. it will say it completed successfully but i got to boot recovery and it just boot right back into bootloadre/fastboot mode. i even tried to do fastboot --set-active=a and fastboot --set-active=b tried booting into each of them and nothing. when i do fastboot getvar all it says that boot_a and boot_b are unbootable. any idea how to fix this?
Will be trying again in a week when i get my new unlock token. just took the phone to the store, said that the bricking of the phone happend during an update. They didn't have any Nord N200's in stock so they ordered one and said they would have it in the store in a day or two. onto the next phone til then. any ideas on a TCL A509DL Trac Phone?
MiniNinja2024 said:
I forgot to mention that I can no long get into recovery it won't even flash a recovery anymore. it will say it completed successfully but i got to boot recovery and it just boot right back into bootloadre/fastboot mode. i even tried to do fastboot --set-active=a and fastboot --set-active=b tried booting into each of them and nothing. when i do fastboot getvar all it says that boot_a and boot_b are unbootable. any idea how to fix this?
Click to expand...
Click to collapse
You need to use MSM tools to unbrick. It'll restore your device to stock and relock your bootloader.
swee08315 said:
You need to use MSM tools to unbrick. It'll restore your device to stock and relock your bootloader.
Click to expand...
Click to collapse
Having problems getting msm running on deb linux. Have the firmware and files needed but can't get msm to run on MX linux And can't get VMware to run either to try it through that on windows 10
MiniNinja2024 said:
Having problems getting msm running on deb linux. Have the firmware and files needed but can't get msm to run on MX linux And can't get VMware to run either to try it through that on windows 10
Click to expand...
Click to collapse
i'm not sure if you can even get the devices to connect to the unbrick tools in a virtual machine. to save some time, use a physical computer running windows 10+ and use a virtual machine as a last resort or if you don't have another computer.
by the way, make sure you have the drivers.
justauserthatusesaphone said:
i'm not sure if you can even get the devices to connect to the unbrick tools in a virtual machine. to save some time, use a physical computer running windows 10+ and use a virtual machine as a last resort or if you don't have another computer.
by the way, make sure you have the drivers.
Click to expand...
Click to collapse
i don't have another machine only the one i'm using running MX linux. and with all the Distro's of linux i have installed and used there is no need to install drivers for phones for every phone, 3 that i have connected to my computer it' has recognized all 3 phones and runs adb and fastboot commands fine on them. Lol, Took me a minute to read your name but Love the Name.
Haha, don't flash it. Boot it. I ended up stop using it and am now using the Lineage OS Recovery. SUPER stable. I am in the works making a new TWRP as well... This unofficial variant just isn't working for me either. So, I figured since im making it doe myself, might as well release it
justauserthatusesaphone said:
i'm not sure if you can even get the devices to connect to the unbrick tools in a virtual machine. to save some time, use a physical computer running windows 10+ and use a virtual machine as a last resort or if you don't have another computer.
by the way, make sure you have the drivers.
Click to expand...
Click to collapse
You can. Use virtualbox. I wouldn't bother with qemu.
swee08315 said:
You need to use MSM tools to unbrick. It'll restore your device to stock and relock your bootloader.
Click to expand...
Click to collapse
There is a command line alternative for Linux. It is originally made for flashing android boards, but works with phones as well.
Springles2 said:
You can. Use virtualbox. I wouldn't bother with qemu.
Click to expand...
Click to collapse
Interesting, that's actually useful to know. Thanks.
MiniNinja2024 said:
Update: Phone Complete Bricked. Says something like The Image(boot/recovery) has been destroyed please flash the correct image or call customer service to fix it. on top of this....Unable to flash anything. everything no matter what it is, i even tried to follow a guide to get back to factory and it say that no such partition or volume full. Oh and it's an A/B partition phone
how do you push? ive tried the adb push and to no avail... it just keeps saying it's unable to. oh and when i did have twrp installed it wouldn't boot into the os unless i fastboot boot twrp.img then it would reset and finally boot into regular os
Click to expand...
Click to collapse
I do adb push (File) partition
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.
So,
This may seem mundane to some of you, and I apologize. But I'm hitting a wall with this Pixel. I cannot use Fastboot normally because I can't get access to any of the internal partitions. I have a list of them that I looked up, but fastboot will not allow me to use any fastboot flash or flashing commands that I need to flash a new ROM.
I've unlocked bootloader - Duh - (been doing this a little while)
Rebooted
Reenabled ADB - #adb reboot bootloader (works fine)
Sending files --> ADB and fastboot both will serve the image or file to the phone, but the phone fails on "partition does not exist" on every time.
I have tried re-flashing this device with the android flashing tool through Google (works fine and I'm currently running the 13 Beta T3B3). Would straight flashing from a zip file help?
I want to be running LoS but I cannot get even the vendor_boot or boot image to flash. Everything seems to be software/firmware locked and I've tried the fastboot commands to unlock certain partitions and things like that from what I can tell in the changes to fastboot. So my question is:
What am I missing? I have even got it to boot into LoS and things worked, but you could tell something was very wrong with the flash and major app/gapp issues. This was accomplished with the flash tool flashing the partitions "boot" and "vendor_boot" and "dtbo" for me to get me into the LoS recovery. From there I reset and installed via sideload like normal, flashed the rest of the partitions listed with LoS and I cannot get a working build without major app issues and major stability issues. CLI will also not give me any info on why these can't be flashed, of course, but that's not how this should work. I know it should be more stable than it is just because it's a Pixel (one would think - has been in the past) It's a Global model GB7N6 and I don't understand what the hold up is.
Any help or suggestions would be greatly appreciated! Thanks!
You need to flash the regular factory image first, not the beta!!
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
See instructions
To be fair, I just flashed the beta as a last ditch. Every try I've done was with production software.
I will absolutely try this though. Anything to straighten this mess out.
XGX5309 said:
To be fair, I just flashed the beta as a last ditch. Every try I've done was with production software.
I will absolutely try this though. Anything to straighten this mess out.
Click to expand...
Click to collapse
Hi friend
If prior attempts to fix the problem in GetSimple CMS failed, it could be worthwhile to try the beta version as a last resort. A alternative strategy can occasionally assist in solving the issue Free Fire