Hello!
I've recently got into a big problem while doing stuff I don't know much about (and probably in the wrong way, because of that...). So, let's get to the problem, shall we?!
Well, I wanted to root my Moto G4 Plus (XT1640) but I had never done anything like it, so my phone was basically the way it came out of the factory. Before all of this, my phone was using Nougat 7.0.1 (I do OTA updates). I installed TWRP and followed the steps (even some from this forum). However, at that point my phone was boot-looping in the screen "Your bootloader has been unlocked, your device can't be trusted. Your phone will boot in 5 seconds.". Despite the warning, my phone didn't boot. After a while, screen got black and the only way I could use the phone was while in the bootloader. Then, I've made wipes through the Recovery, hopeful that it'd help, but it didn't. Finally, I surrendered and went looking for an original stock ROM I could flash and maybe get things working again. Found SOME ROM that's probably the right one ("XT1640_ATHENE-RETBR_MPJ24.139-50_cid50_subsidy-DEFAULT_CFC.xml.zip") (I'm from Brazil, btw). Great, downloaded, followed steps in the forum to flash it, great, it boots again! Can login to Google, default settings stuff, etc... HOWEVER.
Then, with my phone working again, I wanted to get rid of the nasty boot screen that said my device can't be trusted, etc. So I looked it up and tried to reflash the same stock ROM as above, but now doing it so I could re-lock the bootloader. To do that, I repeated the flashing commands but added the command "mfastboot oem lock" at the end (also used "mfastboot oem lock begin" as the 1st command). Then the CMD said I had to retype the command to apply. Did that, but then the following message showed: "Waiting for signed boot.img, enter the command again" or something like that (didn't printscreen, sorry). Then I reentered the command a 3rd time and then it said "Please flash a signed ROM" or something. So, basically, it failed. After that, repeating the command just showed the last message again. Unhappy, but hopeful, I entered "mfastboot reboot" to reboot my phone. So, got back into the phone (still with the nasty "Your bootloader has been unlocked" warning) and then I basically gave up. I'm now trying to install an OTA update (for Nougat, since the ROM I installed is 6.0.1) but the WiFi download is REALLY slow (and the problem is not my internet, since I've tried downloading a couple of files in my PC to test it).
So my biggest fear is that I have a ROM that's not REALLY meant for my phone (despite looking EVERYWHERE for it) and that's causing problems with the WiFi. Maybe the OTA update is just slow in the server-side, but I'd like to know. Is there a way to get the ROM I got when I bought the phone (that EXACT SAME ONE)?! I wonder if there's a problem because of Motorola/Lenovo regional things. Otherwise, the phone works (gets 4G signal, making calls and downloading Play store updates is as far as I've tested for now). And I would also like to know if there's a way to relock the bootloader in my case(since when I tried those errors I've mentioned above happened)? What I seemed to have done is downgrade a version (since I was in Nougat and then installed a stock ROM that's 6.0.1) and I don't know where to go from here. Thanks a lot, guys! Sorry for the long post, I just wanted to describe the events in order.
There is no official source for you to get a rom. This is not a nexus. I wonder why people always want to relock bootloaders! (it seems in your case only for the 5 seconds warning). As far as i know only modem can differ but roms...
Do you still have TWRP?
if so: if you are on an N modem right now try to flash an N custom rom. If you are on an M modem flash an M custom rom.
KEEP YOU BOOTLOADER UNLOCKED and also:KEEP "OEM UNLOCKING" in developers options ENABLED AT ALL TIMES! (the last step will prevent you from a 72 hours lockout from your Google account.)
There are other ways to get rid of the bootloader warning. (flash a custom logo.bin)
I already opened an RMA for the phone but they have no stock so I figured I'll take another shot at it.
The short version is that my gf messed up and updated the system while transferring her data from her old phone with the tapNgo thing.
I've done multiple facory resets, downloaded the rom from ZTE support, put it on SD, flashed it from recovery and deleted cache and nothing helps.
I don't have the exact error log anymore since I don't have the phone with me now but it reads something along the lines of
loading /proc/devices/audio/sound------ cannot find file/directory.
I looked it up and after a lot of Googling it seems like the symlink to the actual driver folder is missing and I have no idea why.
Does anyone know if i can fix this with an ADB shell?
Alternatively, I tried to follow some of the many guides out there to put the phone in EDL mode and relfash it with XiamiFlash utility but after trying 3-4 downloads and 900 versions of misflash all I ever get is "reading hello packet... unable to communicate to com4"
Haaaalp please?
*edit* this is pretty much exactly the same as what I'm getting: https://forum.xda-developers.com/android/help/sound-card-detected-t3379736
The problem with the phone is it makes no sounds?
gpz1100 said:
The problem with the phone is it makes no sounds?
Click to expand...
Click to collapse
the sound drivers for the OS is missing completely, no sound no microphone.
The syslog looks like this(this is from another phone its its the exact same problem):
AudioDaemon: Opening sound card state : /proc/asound/card---/state
AudioDaemon: Open /proc/asound/card---/state failed : No such file or directory
AudioDaemon: Sleeping for 100 ms
Strange issue indeed. Which model do you have? Which specific firmware file are you flashing to it?
I would think flashing the full unmodified factory firmware using the stock recovery will wipe the phone completely, including the /data partition.
Everything worked before? Help me understand the order of events. What is tapngo?
While in the midst of transferring information to or from the phone, a software update appeared and she accepted/installed it?
Its the A2017U model.
I had tried the 1.1.0 B15 firmware from SD card as well as the 1.0.0 B29 older firmware.
Right now its on B17 Nougat 7.1.1, the phone runs and works perfectly just has no audio hardware.
I wasn't there for the exact procedure but basically she powered it on, it asked for sim, she inserted that, tapped the "transfer my data" and then held the two phones together to get the NFC process started. That starts the bluetooth transfer process and it takes a really long time where it transfers all data and apps from the old phone.
At this point the phone still made sounds when adjusting the volume etc.
Somewhere in that process the "update available" notification came up and she pressed the option to install it.
After I got home I tried to figure out what is wrong, first i thought the phone wasn't registered on the cellphone network but then after a bit i figured out the audio is the issue, then i did a factory reset both from the phone UI and tried again from recovery mode, both times chose the "erase all data" option but neither time did it help at all.
I don't really know enough about phones but i think its the bootloader/something very early on thats messed up. Either that or the audio chip really just did fry.
My hope was to get the full factory image for everything that you need to install with the EDL mode thing but I can't find any good reliable guides for that.
It's the first thread in the development section.. Stickied even.
https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
Get this package - B15-NEW_FULL (Nougat)
I really don't understand zte's numbering scheme. Newer versions get lower numbers. Makes no sense. That's the full firmware except for the fastboot which passes commands. At this point it's a non issue given the issue you're having.
So I don't need to load TWRP on it, I can still keep it just stock with unlocked bootloader?
I tried that miflash thing before, i had it connected un usb download mode but nothing worked for me, I'll try doing this guide when i get home step by step again.
Their firmware numbers is based on numbers and letters 1.0a-z and then 1.1a-z so 1.0z1 is less that 1.1a1
Ok I have an update
Did miflash, nothing changed.
Ulocked bootloader and miflashed the bootloader from the sticky thread.
The phone made the startup sound and audio worked for a few seconds after android started up and then stopped again
*edit*
ok so after it showed signs of life i re-locked the bootloader, and did the OTA updates to 7.1.1 and the audio seems to be working for good now!!
Conclusion seems to be the bootloader was the key to get it working again. Hope this helps others if it comes to it.
I have had my Essential Phone for almost two years now and one day last week when I turned the phone on I saw the following error message.
You device is corrupt. It can't be trusted and may not work property.
Visit this link on another device:
gc.o/ABH
Press Power Key to Continue
There is a red exclamation point at the top that looks like this <!>. I contacted Essential Support and they told me the only way that message gets displayed is when someone has unlocked the bootloader at some point. I have never connected my phone to a USB cable for anything other then charging it with a power outlet and I have certainly never heard of ADB before this error occurred.
I would like to know how this error has happened if all I do is install a few apps from the Play Store and install OS updates when the are officially available OTA. Essential Support has said its my fault and will not help.
I tried to reset the phone back to factory settings several times. I have used the reset from within the Settings, I have used ADB to side-load the latest OTA OS from Essentials website and I have also tried some kind of flashing reset but no matter what I did I could not get this error to go away. These methods are described on the Essential site linked below.
Here is the link to Essentials website that I used. Since this is my first XDA post it will not let me post the whole URL. (essential.com/developer/current-builds)
I eventually ran the following command which did remove the error.
Code:
adb reboot "dm-verity enforcing"
From what I can tell this just prevents the error message from being displayed, correct? If the reason for the error is still there then what are my options? Should I worry about this error? Is it possible for me to reset the phone in someway to get this error message to go away and put the phone back into a secure and safe state? I don't care about any user data on the phone. The whole thing can be erased, which I think I have done sever times already trying to fix this.
Any suggestions would be greatly appreciated because beyond trying to fix this error I have no experience with ADB or modifying a phone in anyway.
Thanks,
-eric
Is there anyone who can offer help?
EricAndroid said:
Is there anyone who can offer help?
Click to expand...
Click to collapse
You can unlock your bootloader and unlock critical partitions than flash the latest bts (back to stock) from the link below. Make sure to read the directions and use a quality type c USB 3.0 or 3.1. you basically download the zip and unzip it, then run the flash-all-wipe.bat from fastboot mode. This will fix the actual problem. Good luck and make sure to ask in that thread if you get stuck.
Almost forgot, make sure to download the Essential Window's drivers(from thread below as well). You don't need to worry about setting up adb and fastboot because it's Automatic when you run the commands from the zip you download. Also make sure you first uninstall any instance of adb or fastboot that may already be on your computer.
https://forum.xda-developers.com/es...ment/stock-7-1-1-nmj20d-t3701681/post74437484
Hello,
Here is my problem.
2 days ago, I wanted to root my phone to get rid of any Google stuff (at this point I didn't know the existence of ADB commands :crying: ).
I followed a step by step youtube tutorial (youtube.com/watch?v=ZD-5twDm6XI), which works with TWRP, magisk and Odin (factory reset is needed).
Once everything is finished, my phone is finally rooted, and I grant superuser rights to Titanium app to uninstall google, and only SOME apps uninstalled totally (maps, chrome, facebook) BUT google play services won't uninstall. So, I try with System App Removal to uninstall google play stuff, and the same happens.
I reboot my phone, and it seems that everything disappeared... Not so sure... Indeed, the play store reinstall all applications as soon as I connect to the WiFi! and I have a persistent message "google play services stopped" that prevents me from browsing for example.
At this point, I use ADB commands, to remove anything which contains "com.blahblah.google.blahblah" and the play store (com.android.vending) with -k command. And it worked totally fine !!!!! I disconnect my phone, ready to backup my data. Idkw, i wanted to uninstall system app removal. IMPOSSIBLE from the phone, which says : "samsung One UI stopped" (I was in safe boot mode). My phone doesn't answer, so I reboot it.
Once it has booted, the TWRP menu screen appears. Ok, isn't that weird ? I swipe to allow changes, then I go to system to boot "normally" my phone.
A warning says : NO OS INSTALLED !!!! I don't understand, I panic, but finally boots my phone. Black charging screen. Forever.
I started first to flash an "official" Samsung ROM from Sammobile. TWRP indicates it is an invalid .zip, adb too. Odin doesn't manage to boot from the ROM too. I take a deep breathe and cry. Then I download the /e/ ROM which works fine !! but it has become impossible to backup my data from my samsung account....
So, I came to ask you a few things. WHY did it happen ? How can I be sure that there is no trace of TWRP anymore ? However, my phone storage is 64 GB and there is only 53,5 Gb free of internal storage !? Do you think the original firmware could be "hidden" in my files (e ROM is about 800Mos compressed) ?
It is stupid, but after my mistakes, I miss google...
I will do my best to reply asap.
Thank you for your help !
PS: -I'm a newbie in informatic, don't make things too complicated
-sorry for bad English, not my mother language
Google writes and distributes android.
There are many things in android that you cannot remove and still have a viable system.
imho you will have to flash a rom but we need your phones information (found in settings/system/about phone) model, version baseband, etc. etc
Others more knowledgeable can step in and help.
also read:
https://www.androidcentral.com/factory-reset-protection-what-you-need-know
KrisM22 said:
Google writes and distributes android.
There are many things in android that you cannot remove and still have a viable system.
imho you will have to flash a rom but we need your phones information (found in settings/system/about phone) model, version baseband, etc. etc
Others more knowledgeable can step in and help.
also read:
Click to expand...
Click to collapse
Thank you for your reply ! I've read your article about FRP but I'm afraid it's not my problem...
Here are some of my phone specifications :
model : SM-G950F
version baseband : G950FXXS8DTC1
OS : /e/ version 0.9-p-dev-dreamlte (LineageOS API : Ilama 9)
Android 9
I've been digging the web for ROMs but each time I feel unsecure about it (virus, etc...) so I hope maybe you have something trustworthy
[UPDATE]
S8recovery said:
Hello,
Here is my problem.
2 days ago, I wanted to root my phone to get rid of any Google stuff (at this point I didn't know the existence of ADB commands :crying: ).
I followed a step by step youtube tutorial (youtube.com/watch?v=ZD-5twDm6XI), which works with TWRP, magisk and Odin (factory reset is needed).
Once everything is finished, my phone is finally rooted, and I grant superuser rights to Titanium app to uninstall google, and only SOME apps uninstalled totally (maps, chrome, facebook) BUT google play services won't uninstall. So, I try with System App Removal to uninstall google play stuff, and the same happens.
I reboot my phone, and it seems that everything disappeared... Not so sure... Indeed, the play store reinstall all applications as soon as I connect to the WiFi! and I have a persistent message "google play services stopped" that prevents me from browsing for example.
At this point, I use ADB commands, to remove anything which contains "com.blahblah.google.blahblah" and the play store (com.android.vending) with -k command. And it worked totally fine !!!!! I disconnect my phone, ready to backup my data. Idkw, i wanted to uninstall system app removal. IMPOSSIBLE from the phone, which says : "samsung One UI stopped" (I was in safe boot mode). My phone doesn't answer, so I reboot it.
Once it has booted, the TWRP menu screen appears. Ok, isn't that weird ? I swipe to allow changes, then I go to system to boot "normally" my phone.
A warning says : NO OS INSTALLED !!!! I don't understand, I panic, but finally boots my phone. Black charging screen. Forever.
I started first to flash an "official" Samsung ROM from Sammobile. TWRP indicates it is an invalid .zip, adb too. Odin doesn't manage to boot from the ROM too. I take a deep breathe and cry. Then I download the /e/ ROM which works fine !! but it has become impossible to backup my data from my samsung account....
So, I came to ask you a few things. WHY did it happen ? How can I be sure that there is no trace of TWRP anymore ? However, my phone storage is 64 GB and there is only 53,5 Gb free of internal storage !? Do you think the original firmware could be "hidden" in my files (e ROM is about 800Mos compressed) ?
It is stupid, but after my mistakes, I miss google...
I will do my best to reply asap.
Thank you for your help !
PS: -I'm a newbie in informatic, don't make things too complicated
-sorry for bad English, not my mother language
Click to expand...
Click to collapse
I've been browsing through my root files and folders ( / ) ...
So :
/system is occupied with 2.33 GB
/vendor with 577 MB
/mnt with 9.01 GB
/proc with ... 236.9GB but every under-folder is empty... (explanations welcome !)
/storage is empty
If anyone could check on his device (S8 Exynos with android 9.0 Pie and One UI) if the files' sizes approximately matched, it would be great !
The one I just received is G950FXXS8DTC6 / G950FOXM8DTC1 / G950FXXS8DTC1 (after it took the Apr 1 update) so probably identical - a Yateley GU46 6GG UK phone. I am running it on ATT Prepaid(US) , which gave me the Apr 1 update. I don't know its history but it hasn't been modified - knox=0.
What you would need to do is get that zip and flash it with odin, but having no experience flashing the S8 myself, or any idea where to get that zip, I can be of no help to you. (I just came off a moto x4 which I ruined by flashing a couple custom rom's to try to help others on that forum - the blessings of Pie on that device!)(plus, taking the Apr 1 update on that phone requires a factory reset/wipe.) I needed a dependable phone here and in Europe on vacation.
Keep posting and ask someone to help you re-flash it.
EDIT: I wonder what a settings/general management/factory reset would do. But don't do one until someone here much more experienced with the S8 suggests it.
EDIT: WARNING WARNING WARNING -> Before flashing, ACTIVATE PIN in "Secure startup" (You'll be asked for it AFTER flashing!)
lockscreen and security / secure startup / require pin
I also see a note to delete your google account before doing this. Don't know if necessary.
EDIT: I believe I have found the rom - see pic This is from the SamFirm exe. 0.3.7 I put VOD for the region.
Remember: don't do anything with this until someone experienced in S8 tells you to!
Hi KrisM22,
I've already flashed with Odin, and I have talked about this on different forums, seen tutos on websites,... I hope this time it will work
I have the ROM required, selected activate pin, followed step by step the recommendations, and if I figured it out I will keep you up to date !
KrisM22 said:
The one I just received is G950FXXS8DTC6 / G950FOXM8DTC1 / G950FXXS8DTC1 (after it took the Apr 1 update) so probably identical - a Yateley GU46 6GG UK phone. I am running it on ATT Prepaid(US) , which gave me the Apr 1 update. I don't know its history but it hasn't been modified - knox=0.
What you would need to do is get that zip and flash it with odin, but having no experience flashing the S8 myself, or any idea where to get that zip, I can be of no help to you. (I just came off a moto x4 which I ruined by flashing a couple custom rom's to try to help others on that forum - the blessings of Pie on that device!)(plus, taking the Apr 1 update on that phone requires a factory reset/wipe.) I needed a dependable phone here and in Europe on vacation.
Keep posting and ask someone to help you re-flash it.
EDIT: I wonder what a settings/general management/factory reset would do. But don't do one until someone here much more experienced with the S8 suggests it.
EDIT: WARNING WARNING WARNING -> Before flashing, ACTIVATE PIN in "Secure startup" (You'll be asked for it AFTER flashing!)
lockscreen and security / secure startup / require pin
I also see a note to delete your google account before doing this. Don't know if necessary.
EDIT: I believe I have found the rom - see pic This is from the SamFirm exe. 0.3.7 I put VOD for the region.
Remember: don't do anything with this until someone experienced in S8 tells you to!
Click to expand...
Click to collapse
The flashing WORKED :victory: !!! It frightens me right now to check if TWRP has disappeared... But thank you anyway !z
S8recovery said:
The flashing WORKED :victory: !!! It frightens me right now to check if TWRP has disappeared... But thank you anyway !z
Click to expand...
Click to collapse
Excellent! What ROM did you flash it with?
KrisM22 said:
Excellent! What ROM did you flash it with?
Click to expand...
Click to collapse
I flashed a ROM from https://www.imei.info/download-firmware/samsung/samsung-g950f-galaxy-s8/SM-G950F/ , then I just followed the steps and flashed with Odin. TWRP has disappeared (the classic recovery menu came back). I think I have found my issue with the "no OS installed" bug : it could be because I deleted the essential API com.google.android.packageinstaller, what may have prevented the phone from booting and launching the OS and its apps .
I should have read this excellent post before...
*I ran antivirus analysis with virustotal and Bitdefender, which both declared the extracted files were safe : I didn't notice anything different by my phone compared to the original OS too, so...
EDIT: I close this thread. A Member tried to help, but seems like the partition was unrecoverable damaged and the data are lost now. Thanks to everyone that put time and efford in reading and helping.
_____________________________________________
Hello,
my name is Robert and i'm trying to save the data (pictures/videos) of the crashed Samsung A40 of a friend.
What happened? She started a recommended Android system update before going to sleep and in the morning the phone welcomed her with an error message (picture 1). I was able to start the recovery system (picture 2) but except for wipe data / factory reset (what i did not try just yet) nothing seems to work.
I'm a J2EE developer with some experience, but i never tried to repair a crashed Android OS so far. So maybe I missed something that would solve the problem more simple, than what i've tried ... which is:
> Apply an Update via Odin / SD Card / ADB
Odin (installed to my desktop PC) isn't able to see the device / port ... most likely because i'm unable to open the debug port via dev-tools (android os is not starting).
I've also tried to put the latest OS version including updates (A405FNXXS3BTI3_A405FNODX3BTF4_DTM) to an SD card and install it from there. I'm able to mount it, but (after all i have been reading) the error i get when i execute the install command, seems to indicate that KNOX denies it.
I'm also able to connect the device to my desktop PC. Command "ADB devices" lists the phone with a (port?) number and allows me to execute "ADB sideload" ... but i dont know what to do with it :/
> Apply some TWRP magic
Obviously i can't install the app via app store so i have to do it manually. The TWRP howto section for the A40 phone says i've to root the device first using magisk. The magisk howto section for the A40 phone says: in order to root my phone i will have to wipe data at least once before i can put magisk to good use. Well ... thats exactly what i do NOT want to do :/
So, am i missing something here? Or did i misunderstood some part of any solution i looked up so far? Or is it simply impossible to get back the data at this point?
I appreciate any hint you can give me.
Thanks in advance!
Robert