Database Users

May i Install KK Bootloader after having flashed Lollipop update?

Hi people. As you may imagine, i've been trying to update to Lollipop since it was released for my device like a month ago (i have a SM-G530M, LTE version in Argentina), but i'm experiencing, like some people, a weird problem whenever i try to flash the last firmware through ODIN ( G530MUBU1BPH2_G530MUUB1BPH2_G530MUBU1BPG1_HOME.tar.md5 ).
>>I'll give details about my issue to make myself clear
The thing is that, Odin shows me the "Passed" message, and when the phone should reboot and make a fresh start (i made sure to wipe /data, /cache and dalvik), it shows the initial "Samsung Galaxy Grand Prime - Powered by Android" screen (which i must tell..., shows up for many seconds, and then, the screens turns gray with many bars, so after a couple of minutes, it restarts again.
In this scenario, i can't access the recovery mode, though i can still fortunately get into download mode, so i had to stick in kitkat searching for a solution.
After some googling, i came across with this:
htcmania. com/showthread .php?t= 1067200
Effectively, the problem is caused by owning a NON-original touchscreen replacement, and to make sure, i asked for help to my friend to disconnect the screen while trying to boot into Lollipop. The idea behind this was to wait for the typical startup sound since the system didn't even show the boot animation during the failure (and the phone would get warm too). So, with the display and digitalizer disconnected, we could hear the startup sound! and the heat was gone. So my problem is that i have the touchscreen of another Grand Prime variant, made for the G530H "Duos". It works ok, but only in Kitkat.
I tried to get the original replacement specifically for my variant (G530M), but i can't get it even on the internet.
In the meanwhile, i thought about installing lollipop and then, restoring/installing the previous Kitkat bootloader over, but i suspect this may be dangerous.
Would this brick my device? I'm aware that Lollipop brought changes to the bootloader so the problem is to make the system boot in the first place.
Just that, thanks a lot in advance!

alpha-ro said:
Hi people. As you may imagine, i've been trying to update to Lollipop since it was released for my device like a month ago (i have a SM-G530M, LTE version in Argentina), but i'm experiencing, like some people, a weird problem whenever i try to flash the last firmware through ODIN ( G530MUBU1BPH2_G530MUUB1BPH2_G530MUBU1BPG1_HOME.tar.md5 ).
>>I'll give details about my issue to make myself clear
The thing is that, Odin shows me the "Passed" message, and when the phone should reboot and make a fresh start (i made sure to wipe /data, /cache and dalvik), it shows the initial "Samsung Galaxy Grand Prime - Powered by Android" screen (which i must tell..., shows up for many seconds, and then, the screens turns gray with many bars, so after a couple of minutes, it restarts again.
In this scenario, i can't access the recovery mode, though i can still fortunately get into download mode, so i had to stick in kitkat searching for a solution.
After some googling, i came across with this:
htcmania. com/showthread .php?t= 1067200
Effectively, the problem is caused by owning a NON-original touchscreen replacement, and to make sure, i asked for help to my friend to disconnect the screen while trying to boot into Lollipop. The idea behind this was to wait for the typical startup sound since the system didn't even show the boot animation during the failure (and the phone would get warm too). So, with the display and digitalizer disconnected, we could hear the startup sound! and the heat was gone. So my problem is that i have the touchscreen of another Grand Prime variant, made for the G530H "Duos". It works ok, but only in Kitkat.
I tried to get the original replacement specifically for my variant (G530M), but i can't get it even on the internet.
In the meanwhile, i thought about installing lollipop and then, restoring/installing the previous Kitkat bootloader over, but i suspect this may be dangerous.
Would this brick my device? I'm aware that Lollipop brought changes to the bootloader so the problem is to make the system boot in the first place.
Just that, thanks a lot in advance!
Click to expand...
Click to collapse
Did you ever try to buy it at Samsung Store? They maybe have it

I didn't consider that, i'll see if i can contact them directly, hopefully i can get the replacement i need. Thanks friend!

Audio drivers went missing during update

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.

Boot help Galaxy S7 Edge

Folks I initially tried to root my phone *SM-G935F* using Odin and a CF hero2lte file. The flashing was all good to go with a green pass. Then upon rebooting the phone got stuck on the Samsung logo boot screen with red words at the top that said **Recovery Is Not Seandroid Enforcing**. This being the case all I was able to get into was (Download Mode). I tried to do the samething a few times and gave up after no successful attempts and the phone not being able to successfully reboot.
Fast forward to present I downloaded the phone's firmware which was a zip that contained 4 files (5 total actually because there was another CS file in the event that you wanted to preserve your data etc.). I loaded all of the files in Odin and made an attempt to flash the phone again however it got stuck on *System* and never go to Green *Pass*. So I figured I would try it a couple of more times in case Odin or something just got hung up on the first try. Any how that wasn't the case.
Now with the above being said what did change is when I would try to reboot into *Download Mode* again it said something along the lines of Emergency Smart Switch Recover. I downloaded Smart Switch onto my computer and went through the specific steps to try to Recover the phone using Smart Switch. Now after it was all done I got to the blue screen with the Android and it said *Erasing...* then the phone booted up and its now stuck at the Samsung animation screen. This being said as of current I can now access *Download Mode* and also boot into the black screen or *Recovery Mode* I think its called where I can reboot the phone through a bootloader, power off, factory data wipe / reset, etc etc.
The above being said I have tried the factory reset / wipe. The reboot in bootloader, reboot phone, all with no success.
Also would like to add that before doing all of the above I forgot to tick *USB Debugging* in Developers Mode when the phone was in its normal state. I must also mention that all of this was a first for me and I looked at doing so to try and recover lost data on my phone. Also wanna add that I am not too familiar with ADB or twrp or how to mess with any of that stuff given the limited access I have to my device because it can no longer bootup like it normally would.
I'm currently at a lost of words as to what I can do next as I am out of ideas and could really use some help. I would also be more than happy to donate a little to anyone who is able to help me boot my phone back up and get things back to normal.
Any and all help would be greatly appreciated.

Folks please disregard my post above as I was finally able to figure things out and get my phone back to its factory state. Thanks.

Hydranize said:
Folks please disregard my post above as I was finally able to figure things out and get my phone back to its factory state. Thanks.
Click to expand...
Click to collapse
Bro would you tell pls , what you did to restore. Thanks

shah22 said:
Bro would you tell pls , what you did to restore. Thanks
Click to expand...
Click to collapse
After me not being successful with the root or with flashing the stock OEM firmware using Odin the phone would get hung up in download mode and the only difference when it would go into download mode it would say to use SmartSwitch Emergency Recover which is what was used and that fixed the issue and the phone rebooted completely fine.
However the above being said I honestly still feel the phone has some small minor issues that I did try to resolve all with no luck. First off when loading to my home screen the icons, and clock, etc etc take about 2 or 3 seconds longer for them to appear on screen than it used like when the phone was new out of the box.
Other thing to note is for some odd reason this issue was thought to be worked out by just booting into recovery mode and doing a factory reset from there, wiping the cache, etc etc. Well this also didn't solve the issue and for some odd reason when performing this the phone didn't reboot on its own.
Basically how it should be normally is after you select that you want to do a factory reset, wipe cache, etc etc, the phone should normally reboot and go through the entire process by itself, however this was not the case. The phone instead went back to the recovery screen and I had to select reboot rather than it normally rebooting on its own.
I've honestly given up on things and given that it is in working order with just a few small minor hiccups I've decided to give the phone to a family member which they plan to use as trade-in credit towards a new Galaxy Note 8.
That being said I will always have a soft spot for the S7 Edge being it was my first smartphone after I had bought a Sony Xperia Z during the same year but returned it the day after because what was to me being poor quality of the Sony phone.

Hmm, looks strange bro , your phone didnt worked after flashing stock rom with odin , and this is the last resort , but you said it was normal before you tried to root , so i guess it was still a software issue other than some hardware problem due to software , but anyways wish you good luck in future , another thing is that my s7 edge has also a very poor build quality , has front camera issues , paint peeling around usb port , wifi issue and high battery degradation , but that happens i guess with today's phones

The version of Odin I used was v3.10.6. I had tried the most current version and a few others, and from the get go for whatever reason this was the only version that would actually pickup the phone being added. Well wait hold on a second the other version would say added when the phone was in but when hitting start nothing would happen, even after waiting an extensive amount of time, also note that the com was highlighted that blue ish color indicating the phone was being recognized by Odin but once again for some odd reason it was only version v3.10.6 that carried out the process of my root attempt and also the attempt I made flashing the original firmware on it.
As for quality the phone had no paint chip or peeling, neither the silver aluminum frame around it either. The build quality was beautiful and up to par with mine. I had a soft spot for my S7 Edge also because it was in the white color which at the time of purchasing was a bit more scarce than the other colors. I purchased the phone from an Amazon.com seller, and during that time I also purchased 2 others from other Amazon sellers but returned those because they had carrier animations for them that were Band LTE or Brand LTE, whatever its called.
This one had no carrier animation upon boot and turned out to be a UK Nougat model. Haven't really seen or came across another one since that would be from a trusted seller or source. Nowadays you never know what you're getting both on eBay and Amazon from these third party sellers.

Yeah thats really strange with odin , its good that you dont have quality issues which struck heavily on me , but yes everyone should be quite careful when ordering online and only should do with trusted resellers

Hydranize said:
Folks please disregard my post above as I was finally able to figure things out and get my phone back to its factory state. Thanks.
Click to expand...
Click to collapse
I'm facing the same problem buddy. Could you pass me the process for the recovery that was used?

vini3237 said:
I'm facing the same problem buddy. Could you pass me the process for the recovery that was used?
Click to expand...
Click to collapse
What phone are you having the issue with and what are you using that caused the issue? I can possibly try to help you out if I know a little more about your situation and device.

Hydranize said:
What phone are you having the issue with and what are you using that caused the issue? I can possibly try to help you out if I know a little more about your situation and device.
Click to expand...
Click to collapse
Phone is SM-G935FD
I do not know what caused it, I already got the celuar so, in status it says Custom.
I already tried to blink for odin 3 different Stocks and the same thing continues.
When I got it it could not access the recovery mode, only the download mode was accessible, after flashing the Brazilian Stock 6.0.1 I was able to access recovery mode.
The phone turns on, and hangs at boot, Samsung logo, restarts and stays in infinite looping.
Can it be Hardware?

Try to flash the original Firmware for it, make sure the Firmware is the one specific to that model, download it and load all of the Firmware files into Odin.

Hydranize said:
Try to flash the original Firmware for it, make sure the Firmware is the one specific to that model, download it and load all of the Firmware files into Odin.
Click to expand...
Click to collapse
Ok now i think what was the problem , you didnt enabled usb debugging , and for flashing with odin its a must ! , for guys who want to flash firmware using odin .. please enable usb debugging in developer options or you will have much issues and may also brick your phone , so if you dont want to enable usb debugging or developer options , just use samsung smart switch on pc to flash your firmware.

Yeah that was my issue was I had OEM Unlock checked off and one other thing in Developer Options and forgot to enable USB Debugging leaving me stuck in the process when the phone couldn't reboot normally after the flash attempts. But yeah SmartSwitch Emergency Recovery should definitely be able to fix and resolve the issue if the phone can't reboot normally.

Nokia 6 TA-1000 Android Pie to international ROM flashing issue

First of all, forgive me for being cognitively impaired when it comes to things like this. I work in marketing and can't code or follow instructions very well.
Here's the deal:
I made the mistake of buying a Chinese Nokia 6 way back, and now I want to flash it with an international ROM before giving it to my niece. Which international ROM it gets doesn't really matter so long as it has Gapps. Since my niece is three years old, she won't care if the phone has Nougat, Oreo, or Pie as she's likely to be more interested in eating those pastries rather than having one as the firmware on her freebie phone.
First of all, I just updated to Android 9 before I began working on this little project. That might have been my first mistake.
Anyway.
I started by following this guide. I wasn't able to get OST LA to work so I gave up.
Then I started following this guide, as it seemed to involve less work.
I downloaded all the relevant files;
renamed them;
put them on my SD card;
went into recovery mode;
installed the update
rebooted the phone and;
installed the firmware.zip
However, after the installation, the phone never goes further than the Nokia-logo. I can reboot all I want, but it's stuck. I can't even get into recovery anymore. I believe this is a bootloop? The main issue here is that I am completely locked out of my phone, and that is really annoying.
Any tips or ideas on how to get away from this unpleasant conundrum would be greatly appreciated.

Ok, an update.
I was able to find a way to access the damn recovery menu after following the steps proposed by viennazar in this thread.
Similarly, I did a wipe as per his instructions, and rebooted the phone after that. Lo and behold, my phone was able to move past the Nokia-logo, and booted up as a TA-1003!
Now, my main issue is that I am unable to move past the initial setup as the phone is checking for updates from Google's servers. That means I am fresh out of luck since I have the great misfortune of residing in the PRC.
That's an entirely different issue though...

Can't actually fix the OS of my Moto G6

Hi.
First of all, I want to let you know I'm just new to this page, so I'm so sorry if I make any mistakes within creating the post.
As you've read in the title, I can't fix the OS of this phone. I bought it used, and apparently it didn't have any OS (I thought it was because there was a flashing attempt, which went wrong). One day, I just looked for Android 9 and I installed it. The phone started working, and so I started using it. There were some problems with the phone though. First of all, at random moments, it started lagging and just re-starting. The other problem I had was the bootloader message, saying that I didn't have an official OS.
Today, I tried to uninstall all of /system. I read a lot of information, I watched a lot of videos and I started doing so. Basically, what I wanted to do is delete all in /system so I could install a clean ROM from my computer. Problem is, I have "flashing_locked" flag. I also downgraded it to Android 8, and I think it made it worse. Now, I don't even have internet connection (or what is called /persist), which also means I'm stuck in the setup screen. There's no way I have now to enter developer mode, nor activating usb debugging. Just wondering, is there any tips I could get from you guys to fix all this problem?
Thanks a lot.
Edit: I also think there's some "residual" data from those flashing attempts, Android 8 and also Android 9. I'm not sure if that has something to do.
Edit 2: I also requested a Unique Key from the Motorola official page, which didn't lead me to anywhere. Although I used "fastboot oem unlock <key>", it didn't work to me.

s9kii_ said:
Problem is, I have "flashing_locked" flag.
Click to expand...
Click to collapse
I'm wondering how you managed to downgrade the device from Android 9 to 8 with a locked bootloader?? that's very strange... To fix the known issue of broken wifi/mobile connection (as a result of the downgrade) it's recommended to revert back to Android 9.
So, you did the downgrade from 9 to 8. But now you can't finish the setup wizard to activate OEM unlocking? Please tell me, at which point it has been deactivated?? It doesn't make any sense...
Try the Lenovo Motorola Smart Assistant tool. It'll fix the issue.
s9kii_ said:
I also think there's some "residual" data
Click to expand...
Click to collapse
I think not. Flashing a firmware means copying image files to a specific partition. Each image file got its own partition table. There will be no data left.