I was trying to update my firmware in the hope of using one of the custom roms available, and my M8 is now stuck on the boot screen and will not go further. Here is what I did:
Currently have a GPE M8. It is S-Off, SuperCID, Unlocked, and converted to T-Mobile (Sense) stock rom.
Was on 1.54.401.5 firmware attempting to update to a 2.22.xxx firmware.
The exact process I used was:
Boot into fastboot
fastboot oem rebootRUU
fastboot flash zip firmware.zip twice (successful after 2nd time)
fastboot reboot
After this, it will not go past the default boot screen.
I then tried to revert back to 1.54.401.5 firmware using the same process. This time, it will reboot once after the stock boot screen and go into recovery. Still unable to get back to the OS.
What am I doing wrong and how do I get out of it? :crying:
[edit] I tried to install a newer firmware again, as well as a couple of different roms. No luck, still getting stuck at the boot screen or automatically rebooting into recovery. Had to resort to using the T-Mobile RUU to get back a working phone. I still don't know what went wrong with my attempt at trying to install a new firmware or rom. [/edit]
The firmware includes an incompatible kernel, just flash a different kernel or re-install the rom and you should be alright
thom109 said:
The firmware includes an incompatible kernel, just flash a different kernel or re-install the rom and you should be alright
Click to expand...
Click to collapse
I did try to install a couple different roms after installing the firmware, but either the rom fails to install, or even if it appears to install, it still gets stuck at the white boot screen.
I also don't understand how the kernal can be incompatible. In all the threads I've gone through of the custom roms (mainly ARHD), it's always the same story. "Just flash the 2.22.xxxx firmware and you'll be fine". In the threads specifically related to the updated roms, it's the same thing, just flash and go, regardless if you are on stock and some other rom. I, and only a few others, seem to have no luck actually flashing the 2.22.xxxx firmware.
Mpegger said:
I did try to install a could different roms after installing the firmware, but either the rom fails to install, or even if it appears to install, it still gets stuck at the white boot screen.
I also don't understand how the kernal can be incompatible. In all the threads I've gone through of the custom roms (mainly ARHD), it's always the same story. "Just flash the 2.22.xxxx firmware and you'll be fine". In the threads specifically related to the updated roms, it's the same thing, just flash and go, regardless if you are on stock and some other rom. I, and only a few others, seem to have no luck actually flashing the 2.22.xxxx firmware.
Click to expand...
Click to collapse
hmm weird, I have no idea what's going on here ... I had some issues after flashing firmware but new kernel and it worked just fine.
Maybe something in this thread could help you? http://forum.xda-developers.com/htc-one-m8/development/firmware-flashing-panic-attacks-t2824048
thom109 said:
hmm weird, I have no idea what's going on here ... I had some issues after flashing firmware but new kernel and it worked just fine.
Maybe something in this thread could help you? http://forum.xda-developers.com/htc-one-m8/development/firmware-flashing-panic-attacks-t2824048
Click to expand...
Click to collapse
Tried that too, same issue. Tried with the phone locked and unlocked, manually with fastboot and automatically via external SDcard (as in that thread), installed SkyDragon, ARHD, and stock after installing the firmware, and it still fails with the same issue. Even trying to revert back to the current firmware after trying to install 2.22.xxx results in the same problem, and the only way to fix it is with the RUU.
I think what I'll try next is to install the rom first, then try to install the firmware. Maybe in that order it will work. But it still doesn't make much sense that I can't install the newer firmware when so many others have had no problems.
Mpegger said:
Tried that too, same issue. Tried with the phone locked and unlocked, manually with fastboot and automatically via external SDcard (as in that thread), installed SkyDragon, ARHD, and stock after installing the firmware, and it still fails with the same issue. Even trying to revert back to the current firmware after trying to install 2.22.xxx results in the same problem, and the only way to fix it is with the RUU.
I think what I'll try next is to install the rom first, then try to install the firmware. Maybe in that order it will work. But it still doesn't make much sense that I can't install the newer firmware when so many others have had no problems.
Click to expand...
Click to collapse
always install rom first then firmware
Related
Hey guys, short background, upgraded to the HTC one at my brothers urging (showed me how sweet the phone can be after rooting and installing custom ROMs) and I absolutely love the phone. I bought the phone this last Sunday (Mar 2) and unlocked it with s-OFF, and installed the Viper 5.0 rom without too much trouble (had my brothers help). Since then I have come to learn that when making phone calls the only way for them to work properly is by using a headset with a mic built in. If I have the headset unplugged the call will go through (either receiving or making) but once it is picked up on either end there is no sound at all, even with speakerphone active. When someone calls me, my phone will ring, but again, no sound on either end.
I also never used the phone to make any calls before I rooted the phone, but I have ran a recovery back to stock ROM and still nothing. I have spent a lot of time on google searching the issue and everything I came across basically said get a new phone. Although it is annoying as hell, I would like to explore every option of fixing it before I take it back, and I think you guys can help!
Some friends have suggested updating radio's, and trying different ROM's, but to be honest I'm not sure I fully understand how to flash/run other ROM's on my own (my bro did most of the work while I watched) . I did reinstall the kernel I was using (ElementalX something) and reset all my power settings back to stock, but that didn't help any. Sorry for the wall of text but any help will be appreciated. Also, feel free to dumb it down for a HTC noob here
Thanks in advance!
p.s. using the HTC one 5.0 Viper ROM ElementalX kernel
Do you know if your brother ever updated it to the kitkat firmware? Running a kitkat rom with jellybean firmware is known to cause call issues. I would update the firmware using fastboot. You will need a pc with adb setup, and this file http://vzw1files.dyndns.org/FIRMWARE/3.11.605.1_firmware.zip If you feel up to trying it your self i can tell you how to do it.
Awesome man, that was it. Had to update the firmware/radio and now it works like a charm! Thanks very much!
Ok, so what I thought worked initially is no longer working . After I updated firmware/radio here http://forum.xda-developers.com/showthread.php?t=2485319 my phone started working correctly. After that I went on to download a HTC one color theme, and thats when problems started happening!
After I downloaded the theme and got my phone set up just the way I wanted it, it started freezing on me at the HTC splash screen. So after much deliberation I wiped everything back to the stock ROM and proceeded to reinstall my Viper 5.0 ROM and ElementalX kernel. During this process my phone went back to it's original problem of not wanting to give me any sound during phone calls. So I re-updated the firmware/radio again using the same zip file and steps that I had before from the link above ^^^ and my phone started restarting itself on its own, over and over. After I got into the recovery and yet again restored it back to stock roms and settings, the phone sound worked again. So, again, I installed the Viper 5.0 rom and elementalX kernel and checked to see if the phone was working properly, which everything was except for the phone sound (yet again). After another installation of the above firmware/radio update my phone decided to start restarting on its own again!!!
So currently I have wiped the ROM back to stock settings, and have not touched a thing! From what I understand there is not a problem with the ROM or the kernel (my brother is using the same files from my computer on his HTC one without any problems) but in my firmware/radio files. I have looked up a few firmware updates on my own but am hesitant to install them because I don't know if they're compatible with my phone/viper ROM. Again any help would be awesome, and I thank you in advance!!!!!!
-at wits end here
JMink10 said:
Ok, so what I thought worked initially is no longer working . After I updated firmware/radio here http://forum.xda-developers.com/showthread.php?t=2485319 my phone started working correctly. After that I went on to download a HTC one color theme, and thats when problems started happening!
After I downloaded the theme and got my phone set up just the way I wanted it, it started freezing on me at the HTC splash screen. So after much deliberation I wiped everything back to the stock ROM and proceeded to reinstall my Viper 5.0 ROM and ElementalX kernel. During this process my phone went back to it's original problem of not wanting to give me any sound during phone calls. So I re-updated the firmware/radio again using the same zip file and steps that I had before from the link above ^^^ and my phone started restarting itself on its own, over and over. After I got into the recovery and yet again restored it back to stock roms and settings, the phone sound worked again. So, again, I installed the Viper 5.0 rom and elementalX kernel and checked to see if the phone was working properly, which everything was except for the phone sound (yet again). After another installation of the above firmware/radio update my phone decided to start restarting on its own again!!!
So currently I have wiped the ROM back to stock settings, and have not touched a thing! From what I understand there is not a problem with the ROM or the kernel (my brother is using the same files from my computer on his HTC one without any problems) but in my firmware/radio files. I have looked up a few firmware updates on my own but am hesitant to install them because I don't know if they're compatible with my phone/viper ROM. Again any help would be awesome, and I thank you in advance!!!!!!
-at wits end here
Click to expand...
Click to collapse
You only need to flash the firmware/radios one time.
If you read the firmware radio install instructions in my thread, you should be using the one without the Boot.img/kernel.
The stock kernel is not gonna work on Viper apparently.
So you either flash the firmware which includes the stock Boot.img and then flash your choice of custom rom, or flash custom rom and then flash the firmware without the Boot.img that I posted.
If you are getting the files from my thread, that's where the instructions and proper files are located.
But once you have flashed the firmware it doesn't change until you flash new firmware again, no point in doing it over and over.
Flash firmware then Viper or use the one I posted without the stock kernel(boot.img)
So if you have no sound after updating firmware, flashing Viper and then a custom kernel, the issue is your kernel/rom combo.
You can flash any of the firmwares here http://vzw1files.dyndns.org/FIRMWARE/, or the ones from post 2 of santods stock rom thread in development. But it is recomended to match the firmware with the rom. So kk rom kk firmware, jb rom jb firmware. To me it sounds like a rom issue, a kernel issue, or a incompatibility between the two. But you said your bro is using it just fine so i dont know.
Does viper come with its own custom kernel built in, or does it just use the stock one?
santod040 said:
You only need to flash the firmware/radios one time.
If you read the firmware radio install instructions in my thread, you should be using the one without the Boot.img/kernel.
The stock kernel is not gonna work on Viper apparently.
So you either flash the firmware which includes the stock Boot.img and then flash your choice of custom rom, or flash custom rom and then flash the firmware without the Boot.img that I posted.
If you are getting the files from my thread, that's where the instructions and proper files are located.
But once you have flashed the firmware it doesn't change until you flash new firmware again, no point in doing it over and over.
Flash firmware then Viper or use the one I posted without the stock kernel(boot.img)
So if you have no sound after updating firmware, flashing Viper and then a custom kernel, the issue is your kernel/rom combo.
Click to expand...
Click to collapse
Thanks Santod, so far that appeared to have done the trick. Stayed up well into the AM last night to get this phone figured out. I downloaded your firmware without the Boot.img, flashed the custom rom, and then flashed the firmware and everything has been working so far.
If I could ask you two more quick questions, What is the significance of having the Boot.img or not having the Boot.img? And if down the road I install a new ROM and factory reset the phone, wont I have to update the firmware again?
JMink10 said:
Thanks Santod, so far that appeared to have done the trick. Stayed up well into the AM last night to get this phone figured out. I downloaded your firmware without the Boot.img, flashed the custom rom, and then flashed the firmware and everything has been working so far.
If I could ask you two more quick questions, What is the significance of having the Boot.img or not having the Boot.img? And if down the road I install a new ROM and factory reset the phone, wont I have to update the firmware again?
Click to expand...
Click to collapse
The Boot.img is basically the kernel and the files that initiate it(ramdisk).
If you are on a custom rom, you do not need nor want the stock kernel.
Most custom roms have a nice custom kernel included that is known to work on their rom.
If you simply wanted a stock rom and full stock firmware, then you would be using the stock kernel/boot.img.
As I stated above, the firmware doesn't change until you flash new firmware.
Flashing a new rom is not gonna overwrite the firmware, as it's done in fastboot, not in Recovery.
So if you flash a new rom, your firmware will not change and does not need to be flashed again until a newer one is posted.
A factory reset just resets your current rom to fresh install state, it doesn't effect firmware at all.
Before I get to the point let me explain what happened. I attempted to root my S3. It did work up until I got to the point where I was ready to flash a ROM and it didn't work. I received the "status 7" error on CWM and I receive an error on TWRP that means the same thing. So what I did since I couldn't restore from a backup that I would get bootloops from, I attempted to install a ROM that was .tar or md5.tar through ODIN which only worked for original firmware (given in the screenshot). I have managed to install this ROM on my phone through TWRP but unfortunately it is for TMobile and somehow my AT&T service works on it. Here is a screenshot of the phone. I have tried flashing "aokp_task650_d2lte_kitkat_6.3.2014" that is made for the AT&T S3 but no matter what I try to flash it will not flash. I have already tried doing the "ASSERTS" method but it did not work. Can someone please help me fix this issue??? :/
dreammaster252 said:
Before I get to the point let me explain what happened. I attempted to root my S3. It did work up until I got to the point where I was ready to flash a ROM and it didn't work. I received the "status 7" error on CWM and I receive an error on TWRP that means the same thing. So what I did since I couldn't restore from a backup that I would get bootloops from, I attempted to install a ROM that was .tar or md5.tar through ODIN which only worked for original firmware (given in the screenshot). I have managed to install this ROM on my phone through TWRP but unfortunately it is for TMobile and somehow my AT&T service works on it. Here is a screenshot of the phone. I have tried flashing "aokp_task650_d2lte_kitkat_6.3.2014" that is made for the AT&T S3 but no matter what I try to flash it will not flash. I have already tried doing the "ASSERTS" method but it did not work. Can someone please help me fix this issue??? :/
Click to expand...
Click to collapse
The hybrid firmware thing shouldn't really happen but for some reason, cross flashing between T999 (T-Mobile) & i747 (AT&T) sometimes happens without necessarily causing a brick. I would suggest you do a complete stock restore to AT&T 4.3JB firmware (UCUEMJB). Thereafter, you can go back to flashing your preferred custom ROM. Since you appear to be able to get to TWRP, you can first, from custom recovery, remove all existing firmware including OS and then reinstall the stock firmware. It appears the bootloader is still UCUEMJB so flashing AT&T stock firmware shouldn't be a problem. Please see the thread below for 4.3 stock restore...
http://forum.xda-developers.com/showthread.php?t=2658486
Larry2999 said:
The hybrid firmware thing shouldn't really happen but for some reason, cross flashing between T999 (T-Mobile) & i747 (AT&T) sometimes happens without necessarily causing a brick. I would suggest you do a complete stock restore to AT&T 4.3JB firmware (UCUEMJB). Thereafter, you can go back to flashing your preferred custom ROM. Since you appear to be able to get to TWRP, you can first, from custom recovery, remove all existing firmware including OS and then reinstall the stock firmware. It appears the bootloader is still UCUEMJB so flashing AT&T stock firmware shouldn't be a problem. Please see the thread below for 4.3 stock restore...
http://forum.xda-developers.com/showthread.php?t=2658486
Click to expand...
Click to collapse
So in this case, I just flash everything that it gives me correct? Is the stock ROM still rooted? If it is not then what rooting process do you suggest I go through? If it is a rooted ROM. Then do you recommend I unroot it and root it again or take some other alternative method? I really appreciate your help
dreammaster252 said:
So in this case, I just flash everything that it gives me correct? Is the stock ROM still rooted? If it is not then what rooting process do you suggest I go through? If it is a rooted ROM. Then do you recommend I unroot it and root it again or take some other alternative method? I really appreciate your help
Click to expand...
Click to collapse
It's a complete stock image which will take you to as near factory condition as you can get. This means it is unrooted. You would need to re-root after (successful) firmware installation. Prior to flashing the firmware, please remember to use custom recovery to remove all existing firmware including OS. Once you've restored the firmware, there are several ways to root but my preferred method is SafeRoot. You can find the download links and instructions to SafeRoot in the thread below ...
http://forum.xda-developers.com/showthread.php?t=2565758
You can also try Option 2 in the thread below ...
http://forum.xda-developers.com/showthread.php?t=2538991
Larry2999 said:
It's a complete stock image which will take you to as near factory condition as you can get. This means it is unrooted. You would need to re-root after (successful) firmware installation. Prior to flashing the firmware, please remember to use custom recovery to remove all existing firmware including OS. Once you've restored the firmware, there are several ways to root but my preferred method is SafeRoot. You can find the download links and instructions to SafeRoot in the thread below ...
http://forum.xda-developers.com/showthread.php?t=2565758
You can also try Option 2 in the thread below ...
http://forum.xda-developers.com/showthread.php?t=2538991
Click to expand...
Click to collapse
I am running 4.4.2 on my S3 (AOKP Task650) but unfortunately I am receiving some battery drain. Is there a Kernel I could use to prevent this and save more battery? Which Kernel do you recommend most? Also I am having issues with my Data. I get "E" for edge in a 4G LTE area? Is there a radio that I can flash or APN for this to fix that problem?
dreammaster252 said:
I am running 4.4.2 on my S3 (AOKP Task650) but unfortunately I am receiving some battery drain. Is there a Kernel I could use to prevent this and save more battery? Which Kernel do you recommend most? Also I am having issues with my Data. I get "E" for edge in a 4G LTE area? Is there a radio that I can flash or APN for this to fix that problem?
Click to expand...
Click to collapse
just to confirm, you re on ucuemjb bootloader, and installed/running Task650 4.4.4 rom 7.21.2014 (at this writing thats the latest update for the rom)
right?
sorry last time i tried to flash task650 rom, i got errors concerning the bootloader, went back to CM11 which has been my go-to-go rom and everything works fine, after you respond i will flash and get back to you on the network issues
thanks
Hey there,
recently, I pulled a really noob move - I flashed an i-9505 kernel (stock, plus recovery) on an i-9195 phone.
I had just flashed both phones a few days apart from each other and obviously,
something with the folders on my PC (or in my head^^) went wrong...
So, in short I have a phone right now, which wouldnt start and could not be flashed either by Odin
or via recovery. I have flashed serranoltexx recovery, Odin says "Pass", but I couldnt start it,
the screen says something about Image size being too large and shows "Secure Fail:Kernel".
Download mode does work, though.
Does anybody have a stock kernel for the 9195 variant? Since I couldnt flash via recovery,
I would prefer a tar.md5 file.
Or are there any other solutions to my problem?
AtzeOnAcid said:
Hey there,
recently, I pulled a really noob move - I flashed an i-9505 kernel (stock, plus recovery) on an i-9195 phone.
I had just flashed both phones a few days apart from each other and obviously,
something with the folders on my PC (or in my head^^) went wrong...
So, in short I have a phone right now, which wouldnt start and could not be flashed either by Odin
or via recovery. I have flashed serranoltexx recovery, Odin says "Pass", but I couldnt start it,
the screen says something about Image size being too large and shows "Secure Fail:Kernel".
Download mode does work, though.
Does anybody have a stock kernel for the 9195 variant? Since I couldnt flash via recovery,
I would prefer a tar.md5 file.
Or are there any other solutions to my problem?
Click to expand...
Click to collapse
What version of rom u have now ?
KitKat or JB ?
If Kitkat try this and see
If not just try to flash a full firmware from sammobile.
From error u got, Knox is active and tripped on your phone
And u also need a new recovery U can flash Phillz touch
Both files u can flash with Odin
SilviuMik said:
What version of rom u have now ?
KitKat or JB ?
If Kitkat try this and see
If not just try to flash a full firmware from sammobile.
From error u got, Knox is active and tripped on your phone
And u also need a new recovery U can flash Phillz touch
Both files u can flash with Odin
Click to expand...
Click to collapse
Thanks for the quick reply.
I will have a look into it this evening and report then...
So, I flashed the kernel and recovery and had no success so far.
Odin shows pass, though.
I was originally on 4.2.2 but decided then to flash some CM -
I am not sure anymore if it was 11, since I acted mostly in time pressure and out of desparation -
which worked quite fine. Since my friend, who wants to buy the phone, didnt want any modifications,
I tried to get back to stock.
After some different (and quite frankly useless) attempts, I read something about being on
KitKat and never going to return to lower versions. Too late for me...Could this be a problem?
So, no success with the KitKat kernel, is there the necessity to try a stock firmware?
I have tried so many before...
AtzeOnAcid said:
So, I flashed the kernel and recovery and had no success so far.
Odin shows pass, though.
I was originally on 4.2.2 but decided then to flash some CM -
I am not sure anymore if it was 11, since I acted mostly in time pressure and out of desparation -
which worked quite fine. Since my friend, who wants to buy the phone, didnt want any modifications,
I tried to get back to stock.
After some different (and quite frankly useless) attempts, I read something about being on
KitKat and never going to return to lower versions. Too late for me...Could this be a problem?
So, no success with the KitKat kernel, is there the necessity to try a stock firmware?
I have tried so many before...
Click to expand...
Click to collapse
I think your only bet is to try a stock kitkat rom unmodified ...
SilviuMik said:
I think your only bet is to try a stock kitkat rom unmodified ...
Click to expand...
Click to collapse
Will do...
Thank you so much man, it worked!
Phone is back to stock now, so my friend gotta deal with having an unrooted phone with KitKat
Thanks again and have a nice one!
my work requires encryption. i was on slimkatv22 at the time and had to encrypt. as encryption kept failing, i went back to stock. way back to stock.
so i'm running
JZO54K.I317UCAMH3 ROM
TEAMWIN Recovery
I317UCUCNE5 Bootloader
with Root and Busybox installed.
everytime i try to update via device update, it downloads, reboots and runs TWRP, I decrypt using password, reboots and the update fails with "Update Interrupted" message.
Is there a way to update ROM and keep encryption?
You can't OTA stock ROMs without stock recovery.
xBkKx said:
You can't OTA stock ROMs without stock recovery.
Click to expand...
Click to collapse
Thanks for your response. I tried updating ROM via ODIN and was not successful. Always got stuck in boot logo after i flashed new ROM.
Is there a stock recovery I should flash over TWRP to try?
Thanks for your help.
I have never used encryption so I can't really help if there are specifics around that. What exactly are you trying to install through Odin? If it's the firmware such as THIS it should overwrite the custom recovery with the stock one. If the stock ROM isn't booting you might have to boot into recovery and factory reset/wipe dalvik cache. This is my first Samsung phone so if nothing helps someone else who'd like to offer their assistance would probably be more knowledgeable.
I was going back to stock, which I guess, was mostly successful. however, I've not been able to install new ROM, namely 4.4.2 I317UCUCNE5. so if I install from your link, that should overwrite custom recovery and allow me to upgrade to 4.4.2 ROM either OTA or via Odin?
Maybe? Using the OTA always tells me there isn't an update (cause I'm on T-Mobile I guess?) and I haven't seen any files to update to Kitkat firmware through Odin
http://forum.xda-developers.com/showthread.php?t=2618447
i'm going to try this.
thanks,
miserly said:
http://forum.xda-developers.com/showthread.php?t=2618447
i'm going to try this.
thanks,
Click to expand...
Click to collapse
haven't had time to try. tbutbut i noticed that foxfi doesn't work even though i'm rooted. i searched for tether and doesn't seem to be a working solution for a free app.
SOLVED
finally got around to following the directions from dicksteele and voila! i'm on 4.4.2!
thanks all!
m
Good Morning
passage through the forum to see if someone can help me with a problem I have since I started with custom roms. My problem is that the cell is left without sound when I have headphones on and the cell is hot. the strange thing is that the sound is full, even if I unplug the headphones. I have to reboot the phone and wait for the temperature to normalize again to plug headphones and the sound is heard.
Another fact is that my cell phone can be on fire and the sound will be perfect as long as you do not have headphones plugged
Does anyone know why this happens and how to fix it?:crying:
Unfortunately it sounds like you have a rather unique problem there. I've never encountered it anyway.
Have you tried other roms or kernels? If not, I think that would be the first thing to try. What rom and kernel are you currently using? Try flashing a stock based rom, factory reset, and see if it still occurs.
If the problem persists on different roms and kernels, it will likely be a hardware issue.
Have you also tried different headphones?
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
Unfortunately it sounds like you have a rather unique problem there. I've never encountered it anyway.
Have you tried other roms or kernels? If not, I think that would be the first thing to try. What rom and kernel are you currently using? Try flashing a stock based rom, factory reset, and see if it still occurs.
If the problem persists on different roms and kernels, it will likely be a hardware issue.
Have you also tried different headphones?
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
ow it is the cyanogenmod 12.1, before used the slimkat and both have had that problem. I have not tried with stock rom because when I try to flash it with Odin leaves me in soft brick. and I find the rom that works. and hardware problem not think it's, as you never give me problems, unless the cell phone is hot
frank461 said:
ow it is the cyanogenmod 12.1, before used the slimkat and both have had that problem. I have not tried with stock rom because when I try to flash it with Odin leaves me in soft brick. and I find the rom that works. and hardware problem not think it's, as you never give me problems, unless the cell phone is hot
Click to expand...
Click to collapse
One reason Odin could be causing problems is if you are attempting to flash software with bootloader and modem that is older than what is on the phone. You have had CM12.1 on the phone, but what is your current bootloader and modem? You can use these commands in Terminal Emulator to find out:
Code:
getprop ro.bootloader
getprop | grep version.baseband
I may have missed it, but do you have the i747 or the i747M? Both will work with the same roms, however they use different bootloaders and modems. Odin should stop you from loading ROMs from the wrong device, most times anyway.
dawgdoc said:
One reason Odin could be causing problems is if you are attempting to flash software with bootloader and modem that is older than what is on the phone. You have had CM12.1 on the phone, but what is your current bootloader and modem? You can use these commands in Terminal Emulator to find out:
Code:
getprop ro.bootloader
getprop | grep version.baseband
I may have missed it, but do you have the i747 or the i747M? Both will work with the same roms, however they use different bootloaders and modems. Odin should stop you from loading ROMs from the wrong device, most times anyway.
Click to expand...
Click to collapse
Well my baseband AMD modem is I747mvlufne6 I for this model as I was going down the roms
frank461 said:
Well my baseband AMD modem is I747mvlufne6 I for this model as I was going down the roms
Click to expand...
Click to collapse
NE6 would indicate the i747M. The soft brick could be a factor of returning to stock KitKat after having been on Lollipop, either CM or AOSP and their derivatives. If you want to try a stock 4.4.2 ROM, the fix for the soft brick is either:
1) Flash the stock ROM from your custom recovery, then flash the stock recovery before rebooting, boot into the stock recovery and do a factory reset. OR -
2) Place the stock ROM on an external sdcard, boot into your custom recovery, format the internal sdcard, flash the stock ROM, reboot.
Needless to say, you will lose everything you have not backed up. Of course, I don't know that the stock ROM will fix your sound and overheating issues.
Ok i trying this and leter i tell you what happen
Thanks
If I'm not mistaken, the i747m firmware is available from http://sammobile.com/firmwares
So you can just flash NE6 full firmware (or newer), boot recovery and factory reset.
(Might be a little more straightforward that way...eliminates some extra steps)
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
If I'm not mistaken, the i747m firmware is available from http://sammobile.com/firmwares
So you can just flash NE6 full firmware (or newer), boot recovery and factory reset.
(Might be a little more straightforward that way...eliminates some extra steps)
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
You are correct, it is on sammobile and it would eliminate some steps. I think he would lose root, but it would be easy enough to afterwards flash a custom recovery and then root with the supersu.zip.
I probably suggest the two steps I do because they are the same for the i747M and the i747. With the i747 there is no 4.4.2 stock from sammobile to flash, so that third option isn't present.
good to fix the sound problem may work because i was investigated and found that the kernel could be problems because it was not compatible with Android 4.4 or newer. So I wanted to try to return to rom stock and see if it is true.
Now I'm downloading the rom is SamMobile (after a few problems of my own) and later, say if the sound repair
dawgdoc said:
You are correct, it is on sammobile and it would eliminate some steps. I think he would lose root, but it would be easy enough to afterwards flash a custom recovery and then root with the supersu.zip.
I probably suggest the two steps I do because they are the same for the i747M and the i747. With the i747 there is no 4.4.2 stock from sammobile to flash, so that third option isn't present.
Click to expand...
Click to collapse
I downloaded the firmware file SamMobile but it Odin file is not to flash in recovery what do to work in recovery?
frank461 said:
I downloaded the firmware file SamMobile but it Odin file is not to flash in recovery what do to work in recovery?
Click to expand...
Click to collapse
@DocHoliday77 would it be safe for him to flash one of the At&T stock 4.4.2 ROMs made available by @enewman17 as long as he was very careful to not flash the bootloader and modem? I'm thinking it would, but I prefer hearing another voice confirm this.
frank461 said:
I downloaded the firmware file SamMobile but it Odin file is not to flash in recovery what do to work in recovery?
Click to expand...
Click to collapse
You have to be in Download Mode to flash with Odin, not recovery. (Same buttons but volume down instead of up.)
dawgdoc said:
@DocHoliday77 would it be safe for him to flash one of the At&T stock 4.4.2 ROMs made available by @enewman17 as long as he was very careful to not flash the bootloader and modem? I'm thinking it would, but I prefer hearing another voice confirm this.
Click to expand...
Click to collapse
That would be safe to do. The main reason I still suggest flashing the full official firmware though is in case something currently on the device got corrupted somehow. Plus if he flashes the NE4 system and it still isn't fixed, the next step would be to flash full official stock anyway. Imo, it's the only true way to know if you have a hardware or a software issue.
That said though, I have a feeling things would end up working with either one of those solutions.
Sent from my SGH-T999 using Tapatalk
Sorry for the delay, I have already flashed the official ROM and as the sound problem is arrangement. however I have one more question, I'm from mexico but to flash the rom NE6 cell did not recognize the Spanish language. it is the only detail, as I pass the phone to Spanish without rooting the phone
As I said everything works fine, signal, wifi, everything. I guess because it is released. But I would like this in Spanish.
for now thank everyone who attended my problem.