Hello all,
I'm just new, and sorry for my bad English. But i wanted to share this information/question with you guys.
Oke so i'm not a scripter or what so ever, but if I f**k things up i like to find out and research it myself. And the problem was when I got my s7 edge , ofc I wanted to rooted it. And I did make a backup, but I felt there was something wrong and I forgot to put the backup on my pc . So after a few weeks of reflashing rerooting etc to find out why my phone somehow managed to bypass all the rom and csc tweaks. But last night I saw a log flashing by it wasn't able to restore my boot.img and it was already patched. And allot started bugging. So after hours of searching I couldn't find any fix for my boot img. So I bissicly drag it out of the .tar.md5 file , and signed it with a tool i found on the internet.
So I flashed all kinds of ways in hoping I could fix it. (Not sure if I did it or not). Here it comes ussualy when I check the logs I only see some settings flying by , what my model firmware is etc etc etc.
But now I see a log with dev notes all over the place , explaining stuf. Hope you guys still can follow me.
If I read the logs and combine the logs, I can actually see partitions geting mounted for (rw?) but failed to unmount after due some weird check he can't do.
I see partitions getting mounted where he is storing his ro.boot ETC1 compressed files.
ro.boot.warranty_bit = 1
ro.warranty_bit=1
config_always_enforce - true; enforcing=1 old_enforcing=1
And allot others of those with <dev-notes>
So is this editable? Like I said I'm really new to this. I somehow have a feeling my bootloader is locked for a part. Because I can do oem unlock an I can do root and install xposed etc. . But tweaked csc items etc from custom roms, always get resetted.
So my phone is still open in this log for a hour, like I said I'm a noob in this stuf. Trying to figure out how to fix my boot.img back to normal.
Hope someone can clarify what these settings are and if they are editable, Thank you!
----Edit----
Some additional info why I also post this.
I reflashed the homemade images allot with odin, without auto reboot. I wanted to make sure it really did flash correctly. I also formatted everything in twrp before I started flashing. So at the final flash I ticked auto reboot, knowing it would say applying update and so on. But the figure went dead instantly and booted me into recovery. And saw those logs comming by.
Related
Hi everyone,
Before blasting away with comments as to why I would do this, here's my story,
I live in Canada and just brought home a i9508, a China variant of the S4. It belonged to my dad and he didn't want it so I just took it. The i9508 doesn't have Play Store, and it doesn't work on Canadian 3G network.
So to me, the phone is useless right off the start (don't intend on selling it either, who wants it?) So I had 2 options:
1) Leave the phone as it is, and probably use it once every 1-2 years when I visit HK
2) Flash custom roms on it fully aware of the risk it will have so that there's a possibility I can make it more usable
So in the end I went with option 2.
I followed a guide and flashed TWRP for i9505 using Odin onto the phone, and used TWRP to install chainfire SU, and it actually worked (but SU wouldn't open because some sort of security on the phone is blocking it)
Next step, I downloaded the CM version for i9505 and flashed onto the phone, and that worked too. Only problem I've encountered was that the phone would only boot after a fresh install. If I installed CM, turned the phone off after the initial start up, the phone wouldn't boot pass the Samsung logo.
Up until this point, I didn't make a backup, because of my arrogance, cause I have available a copy of the official firmware, in case anything happens.
So I figured at this point, maybe if I restore the original firmware, and try the whole process again, the custom rom would work. So I went into Odin, flash the firmware with PDA, and failed. It just wouldn't work. After retrying it a couple of times, and downloading different updates of the firmware, nothing worked. Only thing working right now is, I can get into Download mode, and I can get into TWRP recovery (but for some reason, I can't flash the zips that I've adb pushed onto the phone, zip can't open)
For me, if it can't be fixed, then it's really SOL. But if there's a way to fix it, I'm open to testing anything people have in mind, cause afterall, this phone is paper weight either way. I'm interested in seeing if I could enable 3G by flashing a i9505 radio, despite warnings, although, I've never actually came across a thread where someone had actually tried it before.
Either way, if someone has any idea on how to fix the phone, and wouldn't mind sharing it, that'll be greatly appreciated.
Working
I can get into Download mode, but Odin is failing (if you need the error please let me know and I'll post it)
I can get into TWRP recovery, but can't flash files
I can get into adb
This isnt the correct forum for your phone. XDA don't follow clones
Unfortunately a section for i9508 doesn't exist, so I figure the closest one would be i9505.
Anyhow, if someone has an idea of how to fix it, I'm more than happy to do testing on it, like flashing other roms or radios.
Hey guys. I know for sure there is another thread about a similar problem but the biggest problem I'm having is figuring out what to do next, or better yet, what did I even mess up?
I made a thread a couple days ago here asking about the LTE option on my phone and how there was none. It's an Intl' phone and therefore I guess doesn't work on Canadian LTE networks.
Before we start, I'm using TWRP 2.7.0.0 . My phone is the UAE version of the D802, which is the D80220C. My current custom rom is Liquidsmooth MS3.2 .
So I found a list of modems and flashed the one for Bell. It was for the D803, but the thread I was looking at said it was cross-compatible so I assumed that meant it's okay for me to flash it on my phone.
Even so, I backed up my EFS partitions just to be 100% sure. I even used the .zip file that automatically backs up the current modem files. So I thought there was definitely a way out if it didn't work.
I will give you the full story of what was done and maybe I can get some guidance on maybe something I did wrong.
1) I flashed the D803 Bell modem.
2) Reboot to system, LS3.2 hangs on start up. Tried a hard restart to see if it wasn't a fluke. Nothing. Still hanging.
3) Figured the EFS files were toast, so I ran the restore .zip for my EFS. Reboot, and still hanging.
4) Said WTF? and restored my first stable rooted stock rom. It booted into the rom fine, but when it got to the lock screen I saw the "Service Disabled" and the phone quickly crashed.
5) Didn't even attempt to restart on that rom. So I tried a couple terminal commands to copy the modems1.img and modemst2.img files to corresponding partitions. Copied both just fine, but no change. Still screwing up.
So, this is where I am so far. I am in the process of downloading the D80220C UAE .kdz file so I can try to flash that one first. If that doesn't work, I'm really at a loss.
When I read into this some more, all I see is people who have totally wiped their EFS files and having to spend a whole bunch of time using a bunch of different programs to get in an recover the IMEI number.
What do you guys think?
Some good news right off the bat. I found a KK baseband for D802 and flashed it. So now I was able to restore my LS3.2 rom and boot into it fine. I see my IMEI and MAC address and can get WiFi at last!
Mods, you can delete this thread if you wish.
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.
So I've been rooting me phone for a while and have managed to never f*** up, till now, and I sincerely hope you guys can help me.
After rooting my S7 a while back, I just recently noticed SuperUser telling me that I didn't have root anymore, so I decided to follow these instructions to re-root my phone:
https://forum.xda-developers.com/ve...-to-notes-root-install-xposed-unroot-t3411039
I successfully followed all the steps to get root, but when I opened Flashfire it told me I could install a new update while maintaining root, so since my android is at 6.0.1, I did that and it bricked my phone.
On boot it says "Startup Failed - Use the Verizon Software Repair Assistant . . . " and on top it also says "Custom binary blocked by SECURE BOOT." I have tried going into recovery mode and deleting the system cache, but that doesn't do it. So is there any way to get the phone to properly boot while not deleting my data? I was rooting my phone precisely so I could use Titanium Backup again, so I don't have any backups stored anywhere. I have heard that flashing a recovery image with Odin can work, but would that delete my files? Someone please lend me your expertise.
My phone is a Verizon S7.
Fixed
I am surprised that no one responded to me, but what's important is that, miraculously, I managed to un-brick the phone myself without losing any data! What I did was, as my last hope (since Odin wasn't able to flash the stock image, a la the traditional soft-brick fix), decide to follow the on-screen instructions my phone was giving me and to download and run something called the "Verizon Software Repair Assistant," which can be found in the top google results after searching for the quoted name (xda doesn't let me post the link).
After putting my phone into download mode, I plugged it in, ran the software and let it work overnight. Checking on it in the morning, I found my phone, not only completely functional and working, but updated to Android 7.0 (it was 6.0.1 previously before the failed Flashfire OTA update) and still holding all of my data intact.
So, the interesting thing that I learned is that flashing to stock via Odin to fix a soft-bricked phone should not be the default resolution for potentially most people, as the carrier's default (in my case, Verizon's) repair utility managed to completely fix my phone without any side effects or data loss.
Is there anyone who could chime in on why the Repair Utility did not wipe my phone's memory, even though it warned it would?
**Note**
Verizon links to the Windows version of the repair assistant on their site, but to get the Mac version (which I used), the only way you can get it is by changing the end of the url they mention within the thread from "Win" to "Mac."
Pleased you managed to fix it, and thanks for posting the method for others
As for replies, if you stick around XDA you'll see replies can take days sometimes, patience is the key here
*Detection* said:
Pleased you managed to fix it, and thanks for posting the method for others
As for replies, if you stick around XDA you'll see replies can take days sometimes, patience is the key here
Click to expand...
Click to collapse
I guess I am not acquainted with this forum enough then, thanks!
Most likely the cause of the fault would be updating via FlashFire and keeping root. When the update was flashed, it most likely flashed the stock kernel and patched it for root, which is not a compatible root for our devices. Flashing the root kernel with Odin probably would have made the phone boot normally.
Hi Guys
This is my first post on xda even after using these forums for years. But today I cant find a solution on here or anywhere for that fact, and was literally hoping that I've missed something somewhere.
So to start. I have a Samsung Galaxy J5 Prime (SM-G570F). The other day I was flashing a custom rom when something went wrong during the flashing process and left me with a bricked device. Now I did do a full backup before flashing as I've learned the hard way how important this is. During the flashing it also asked me for a full wipe and to backup the EFS. Even though I did do all the backups and wiped everything< I've ticked both boxes and proceeded with the installation. Everything seemed fine but on 99.9% it froze. Not wanting to do anything I left it until it rebooted the phone by itself, where I was greeted with the download/flash screen. Didn't even give the warning about installing custom software and asked to continue. It just booted straight to the download screen. Tried getting back into recovery only to be greeted with download screen. No matter what I did it just kept booting into download mode. So I then re-flashed TWRP. Getting into the recovery I was able to mount EFS, System, Data, etc. Bu all showed 0mb of 0mb available. I then went to restore everything only to find that the SD Card was also wiped by the process. Thinking that maybe the recovery isn't reading everything correctly, I found the SD Card empty in windows also. No call me names or whatever, (I know my own stupidity) but I never backed up my backups on my PC. So I just proceeded flashing stock firmware as to start from scratch. Everything went as planned until the device got reset by odin. I was greeted with a screen saying "installing system update", but as soon as it reach 32% it changes to "erasing" and then "error" with the "DRK Missing" error. Then it boots to recovery where an error message is saying "unable to mount: EFS (Device or Recourse busy). I cleared cache and did a factory reset and it booted the system (Though mount error still appears in recovery even in custom TWRP/CWM recoveries also). Now I have a 00000..... IMEI number and no network connection. I've spent the last week on the web trying to find a solution with no luck. I'm tired AF because I didn't sleep trying to solve this. I tried flashing stock and custom roms, recovery's, boot-loaders, modems. Tried different software's like Samsung Tool, IMEI repair tool, Strings of adb commands, xposed modules, apps, terminals, etc. I even flashed factory binaries with no luck as to how to change it back.
So in short.
My EFS got wiped.
I lost my IMEI.
I don't have any backups.
Been awake for a week searching for solutions with no luck.
So please if anyone knows of a way to change the IMEI, please help me. I know It's illegal to change IMEI (though not in my country). But I down't want to change it for all the wrong reasons. I just want to change it back to the original found on the back of the phone and on the box. This can't do any harm can it? Please I just want my phone back please!
Full phone info with current firmware:
Samsung Galaxy J5 Prime (SM-G570F)
Android version - Nougat 7.0
Baseband version - G570FXXU1BQI6
Stock Firmware
No Root
No custom recovery
(Basically I just flashed everything back to stock to start over and try solving this)
Please help guys
I am in the same problem
Did you able to overcome from this problem, if yes please tell me the solution please!
I also have same issue.plz tell me what to do.
P01Z0N-T0N1C said:
Hi Guys
This is my first post on xda even after using these forums for years. But today I cant find a solution on here or anywhere for that fact, and was literally hoping that I've missed something somewhere.
So to start. I have a Samsung Galaxy J5 Prime (SM-G570F). The other day I was flashing a custom rom when something went wrong during the flashing process and left me with a bricked device. Now I did do a full backup before flashing as I've learned the hard way how important this is. During the flashing it also asked me for a full wipe and to backup the EFS. Even though I did do all the backups and wiped everything< I've ticked both boxes and proceeded with the installation. Everything seemed fine but on 99.9% it froze. Not wanting to do anything I left it until it rebooted the phone by itself, where I was greeted with the download/flash screen. Didn't even give the warning about installing custom software and asked to continue. It just booted straight to the download screen. Tried getting back into recovery only to be greeted with download screen. No matter what I did it just kept booting into download mode. So I then re-flashed TWRP. Getting into the recovery I was able to mount EFS, System, Data, etc. Bu all showed 0mb of 0mb available. I then went to restore everything only to find that the SD Card was also wiped by the process. Thinking that maybe the recovery isn't reading everything correctly, I found the SD Card empty in windows also. No call me names or whatever, (I know my own stupidity) but I never backed up my backups on my PC. So I just proceeded flashing stock firmware as to start from scratch. Everything went as planned until the device got reset by odin. I was greeted with a screen saying "installing system update", but as soon as it reach 32% it changes to "erasing" and then "error" with the "DRK Missing" error. Then it boots to recovery where an error message is saying "unable to mount: EFS (Device or Recourse busy). I cleared cache and did a factory reset and it booted the system (Though mount error still appears in recovery even in custom TWRP/CWM recoveries also). Now I have a 00000..... IMEI number and no network connection. I've spent the last week on the web trying to find a solution with no luck. I'm tired AF because I didn't sleep trying to solve this. I tried flashing stock and custom roms, recovery's, boot-loaders, modems. Tried different software's like Samsung Tool, IMEI repair tool, Strings of adb commands, xposed modules, apps, terminals, etc. I even flashed factory binaries with no luck as to how to change it back.
So in short.
My EFS got wiped.
I lost my IMEI.
I don't have any backups.
Been awake for a week searching for solutions with no luck.
So please if anyone knows of a way to change the IMEI, please help me. I know It's illegal to change IMEI (though not in my country). But I down't want to change it for all the wrong reasons. I just want to change it back to the original found on the back of the phone and on the box. This can't do any harm can it? Please I just want my phone back please!
Full phone info with current firmware:
Samsung Galaxy J5 Prime (SM-G570F)
Android version - Nougat 7.0
Baseband version - G570FXXU1BQI6
Stock Firmware
No Root
No custom recovery
(Basically I just flashed everything back to stock to start over and try solving this)
Please help guys
Click to expand...
Click to collapse
If this problem is still open, then on Your Phone box is writen imei, or take battery out and under serial number there will be your imei, root your device and use IMEI changer grant root access and type your imei in it, after that reboot and your imei should pop up! I had same issue and this steps made my day! THIS WORKS ONLY ON YOUR IMEI, YOU CAN'T CRACK, STEAL IMEI By this method, don't believe those Dumb ****'s from YouTube!
May I help You!
P01Z0N-T0N1C said:
Hi Guys
This is my first post on xda even after using these forums for years. But today I cant find a solution on here or anywhere for that fact, and was literally hoping that I've missed something somewhere.
So to start. I have a Samsung Galaxy J5 Prime (SM-G570F). The other day I was flashing a custom rom when something went wrong during the flashing process and left me with a bricked device. Now I did do a full backup before flashing as I've learned the hard way how important this is. During the flashing it also asked me for a full wipe and to backup the EFS. Even though I did do all the backups and wiped everything< I've ticked both boxes and proceeded with the installation. Everything seemed fine but on 99.9% it froze. Not wanting to do anything I left it until it rebooted the phone by itself, where I was greeted with the download/flash screen. Didn't even give the warning about installing custom software and asked to continue. It just booted straight to the download screen. Tried getting back into recovery only to be greeted with download screen. No matter what I did it just kept booting into download mode. So I then re-flashed TWRP. Getting into the recovery I was able to mount EFS, System, Data, etc. Bu all showed 0mb of 0mb available. I then went to restore everything only to find that the SD Card was also wiped by the process. Thinking that maybe the recovery isn't reading everything correctly, I found the SD Card empty in windows also. No call me names or whatever, (I know my own stupidity) but I never backed up my backups on my PC. So I just proceeded flashing stock firmware as to start from scratch. Everything went as planned until the device got reset by odin. I was greeted with a screen saying "installing system update", but as soon as it reach 32% it changes to "erasing" and then "error" with the "DRK Missing" error. Then it boots to recovery where an error message is saying "unable to mount: EFS (Device or Recourse busy). I cleared cache and did a factory reset and it booted the system (Though mount error still appears in recovery even in custom TWRP/CWM recoveries also). Now I have a 00000..... IMEI number and no network connection. I've spent the last week on the web trying to find a solution with no luck. I'm tired AF because I didn't sleep trying to solve this. I tried flashing stock and custom roms, recovery's, boot-loaders, modems. Tried different software's like Samsung Tool, IMEI repair tool, Strings of adb commands, xposed modules, apps, terminals, etc. I even flashed factory binaries with no luck as to how to change it back.
So in short.
My EFS got wiped.
I lost my IMEI.
I don't have any backups.
Been awake for a week searching for solutions with no luck.
So please if anyone knows of a way to change the IMEI, please help me. I know It's illegal to change IMEI (though not in my country). But I down't want to change it for all the wrong reasons. I just want to change it back to the original found on the back of the phone and on the box. This can't do any harm can it? Please I just want my phone back please!
Full phone info with current firmware:
Samsung Galaxy J5 Prime (SM-G570F)
Android version - Nougat 7.0
Baseband version - G570FXXU1BQI6
Stock Firmware
No Root
No custom recovery
(Basically I just flashed everything back to stock to start over and try solving this)
Please help guys
Click to expand...
Click to collapse
As i Read Your Post
So I realized that You are Also facing a problem Like me and now Mine is Solved
Just dont upgrade Your Mobile and Downgrade to android 6.0.1
and try to flash someone else efs and then it wil give u ur own imei and u will be hapy
Thanks