Hi, hope someone can help me.
I have a Samsung Galaxy S4 (GT-I9500), it was on Android 4.3 and I upgraded to Andorid 4.4.2 via Kies.
This was a legitimate provider update.
Immediately on the first boot the Samsung Logo was blocky and pixelated, so was the Samsung animation.
This blocky-ness persists on the desktop and any app I open.
UNTIL I lock the screen and unlock it. Then everything becomes clear again.
I since then I installed a new 4.4.2 ROM via Odin, but no luck.
I have ClockWorkMod installed too. The strange thing is that when I boot into recovery mode (into ClockMod) the resolution is fine.
Any ideas?
Help would be greatly appreciated.
Thorfell said:
Hi, hope someone can help me.
I have a Samsung Galaxy S4 (GT-I9500), it was on Android 4.3 and I upgraded to Andorid 4.4.2 via Kies.
This was a legitimate provider update.
Immediately on the first boot the Samsung Logo was blocky and pixelated, so was the Samsung animation.
This blocky-ness persists on the desktop and any app I open.
UNTIL I lock the screen and unlock it. Then everything becomes clear again.
I since then I installed a new 4.4.2 ROM via Odin, but no luck.
I have ClockWorkMod installed too. The strange thing is that when I boot into recovery mode (into ClockMod) the resolution is fine.
Any ideas?
Help would be greatly appreciated.
Click to expand...
Click to collapse
can you give us a pic?
Trozzul said:
can you give us a pic?
Click to expand...
Click to collapse
Here you go.
I find out something else.
If I enable the lock screen pattern the the display stays blocky.
Thorfell said:
Here you go.
I find out something else.
If I enable the lock screen pattern the the display stays blocky.
Click to expand...
Click to collapse
I think it's got to be config or software related beacause if I turn the lock screen back to swipe, restart and then lock it's fine again.
I just took a look at the screenshots I attached.
They look fine!
that's very odd. What would cause the screen to display the images badly but save the screenshots as normal?
Thorfell said:
I just took a look at the screenshots I attached.
They look fine!
that's very odd. What would cause the screen to display the images badly but save the screenshots as normal?
Click to expand...
Click to collapse
well if CWM looks fine, try flashing twrp and see if twrp is pixely, if not get back to stock 4.2.2 or 4.3 and see whats up. maybe you had a bad install on 4.4?
Trozzul said:
well if CWM looks fine, try flashing twrp and see if twrp is pixely, if not get back to stock 4.2.2 or 4.3 and see whats up. maybe you had a bad install on 4.4?
Click to expand...
Click to collapse
I tried flashing back to 4.3, but Odin Failed.
I am trying to get a different 4.4.2 ROM now.
Once I download the new ROM (my bandwidth is terrible), do you think it's worthwhile to re-partition in Odin as well to fix the blocky issue?
Do you think it could be boot loader related?
Thorfell said:
I tried flashing back to 4.3, but Odin Failed.
I am trying to get a different 4.4.2 ROM now.
Once I download the new ROM (my bandwidth is terrible), do you think it's worthwhile to re-partition in Odin as well to fix the blocky issue?
Do you think it could be boot loader related?
Click to expand...
Click to collapse
thats up to you for the re partitioning, you know what it does right? as for Odin, did you get your firmware from here Sammobile.com? is download mode the same way as well?
Trozzul said:
thats up to you for the re partitioning, you know what it does right? as for Odin, did you get your firmware from here Sammobile.com? is download mode the same way as well?
Click to expand...
Click to collapse
I fugure if the pixelation is config related or a corruption then a repartition would fix it.
I will put a 4.3 XFA rom from sammobile and see if the problem goes away. It will have to be on after the easter weekend though
Thorfell said:
I fugure if the pixelation is config related or a corruption then a repartition would fix it.
I will put a 4.3 XFA rom from sammobile and see if the problem goes away. It will have to be on after the easter weekend though
Click to expand...
Click to collapse
No matter what I do, I can't get a 4.3 ROM on my galaxy.
I have flashed back to an official Samsung 4.4.2 for my region but the blocky-ness is still there.
I'm going to take the device to a Samsung store and see what they say.
Thanks for the advice.
Thorfell said:
No matter what I do, I can't get a 4.3 ROM on my galaxy.
I have flashed back to an official Samsung 4.4.2 for my region but the blocky-ness is still there.
I'm going to take the device to a Samsung store and see what they say.
Thanks for the advice.
Click to expand...
Click to collapse
Latest update: The Samsung Service centre is not particularly helpful.
I left my phone there yesterday and explained the problem.
Got the phone back and all they had done was wipe the data and reinstall Android. It has not fixed the pixelated problem.
I explained the problem again in excruciating detail and have left the phone with them once again.
let's see what happens.
Can anyone tell me what actually kicks off the graphics processing as soon as the phone boots?
As in when the very first image is displayed on boot (the Samsung logo with device model number).
Is it the bootloader? If so any ideas on what I can do to reinstall the standard samsung one?
Problem solved.
So after all of that Samsung replaced my screen and it sorted the problem out!
Still, it's very odd that it failed immediately after the 4.4.2 update.
Related
I have a Galaxy S 4G Rooted and Unlocked. I tried to install a special lock screen tweak, and all of the sudden upon booting, the Android System imemdiately force closes. The screen stays totally black after the T-Mobile splash screen and Galaxy S logo come up.
I've erased all my data, but what i really need to do is flash the phone (i think...)
What should i do?
Thanks.
danstheman7 said:
I have a Galaxy S 4G Rooted and Unlocked. I tried to install a special lock screen tweak, and all of the sudden upon booting, the Android System imemdiately force closes. The screen stays totally black after the T-Mobile splash screen and Galaxy S logo come up.
I've erased all my data, but what i really need to do is flash the phone (i think...)
What should i do?
Thanks.
Click to expand...
Click to collapse
If your phone appears to be bricked what you may have to do is flash your phone with one of the three or four Stock Roms that can be found on the DEV site. Check here to see how to use ODEN. For flashing Roms ODEN is the process that is being used on the SGS4G until CWM is working. There may be another way to fix your issue, but if you can get into download mode ODEN should work to get you back to working order. Just make sure you don’t check Partition when using ODEN.
danstheman7 said:
What should i do?
Thanks.
Click to expand...
Click to collapse
You are in luck!!! Check Here http://forum.xda-developers.com/showthread.php?t=1061093
Samsung just released an update using Kies Mini. It's just bug fixes, but it addresses your blank screen. Kies Mini Updates your system Over The Air (OTA). read up on it before you do it. It can be done with the data connection from your phone, but you may want to have a WiFi backup to download the ROM. You don't want it to get interupted during the download process.
nwpro3 said:
You are in luck!!! Check Here http://forum.xda-developers.com/showthread.php?t=1061093
Samsung just released an update using Kies Mini. It's just bug fixes, but it addresses your blank screen. Kies Mini Updates your system Over The Air (OTA). read up on it before you do it. It can be done with the data connection from your phone, but you may want to have a WiFi backup to download the ROM. You don't want it to get interupted during the download process.
Click to expand...
Click to collapse
I ended up using ODEN like you said, and installed 2.2.1 FROYO KC1.
Phone works fine now, thank you
Oh, and I tried clicking "Software Update" and it says "No Firmware"....
Maybe because i'm unlocked on AT&T?
danstheman7 said:
I ended up using ODEN like you said, and installed 2.2.1 FROYO KC1.
Phone works fine now, thank you
Oh, and I tried clicking "Software Update" and it says "No Firmware"....
Maybe because i'm unlocked on AT&T?
Click to expand...
Click to collapse
I don't think Kies recognizes the KC1 firmware since it was never an official release. Hopefully someone will get a firmware dump so that Whitehawk can give us a Deodexed version soon.
danstheman7 said:
I ended up using ODEN like you said, and installed 2.2.1 FROYO KC1.
Phone works fine now, thank you
Oh, and I tried clicking "Software Update" and it says "No Firmware"....
Maybe because i'm unlocked on AT&T?
Click to expand...
Click to collapse
Good to hear you got your phone back up and working. Whether you use KC1 or the new KD1 that was just released won’t make all that much difference. When you clicked on Update Software it is looking for the Over The Air Update firmware. That update is selectively distributed to phones from TMO as the bandwidth allows. Your phone hasn’t received the OTA update yet. That is why you got the No Firmware message. The other way you can download the KD1 firmware is by using Keis Mini software from Samsung. I did that update last night and now have the KD1 Firmware. If you are on AT&T you would have to get the OTA update from them if you are on that network. That is if they decide to send it out.
Ah, great.
Well either way I removed the bloatware apps on my phone with TitaniumBackup, so no OTA for me anyway, correct?
danstheman7 said:
Ah, great.
Well either way I removed the bloatware apps on my phone with TitaniumBackup, so no OTA for me anyway, correct?
Click to expand...
Click to collapse
Tmo is in the process of scheduling OTA updates. If you are on ATT, the update will have to come from them if they are sending them out. You can also use the Kies Mini application to get the KD1 update from Samsung Here Check the OP. There is also a Deodexed version On the Dev page. http://forum.xda-developers.com/showthread.php?t=1063696. Note: The Deodexed version needs to be flashed using ODEN or Heimdall.
Yeah just follow the steps in this guide http://forum.xda-developers.com/showthread.php?t=1001759
to flash the deodexed rom in the post above me.
I recently flashed the 4.4.2 OTA onto my phone, then downgraded to JB to flash Carbon but was not pleased so I reformatted the phone, put 4.4.3 back and then restored a nandroid from before I downgraded.
Now, when I unlock the phone, the screen flashes blue, not just parts of it, the whole thing, almost like the display is going bad. If i open a game, it stops and wont do it again until i relock the screen.
Just curious of anyone else has had this happen.
braneed said:
I recently flashed the 4.4.3 OTA onto my phone, then downgraded to JB to flash Carbon but was not pleased so I reformatted the phone, put 4.4.3 back and then restored a nandroid from before I downgraded.
Now, when I unlock the phone, the screen flashes blue, not just parts of it, the whole thing, almost like the display is going bad. If i open a game, it stops and wont do it again until i relock the screen.
Just curious of anyone else has had this happen.
Click to expand...
Click to collapse
I apologize for not being able to help you with your issue, but where did you get a 4.4.3 file for the RAZR HD?
LifeAsADroid said:
I apologize for not being able to help you with your issue, but where did you get a 4.4.3 file for the RAZR HD?
Click to expand...
Click to collapse
I have the same issue after OTA to 4.4.2. Usually happens to me when in YouTube or MX Player.
I see others with the same issue over in the Motorola forums.
Looking forward to hearing from others who have had this issue and found a solution.
My apologies, I meant 4.4.2
braneed said:
I recently flashed the 4.4.2 OTA onto my phone, then downgraded to JB to flash Carbon but was not pleased so I reformatted the phone, put 4.4.3 back and then restored a nandroid from before I downgraded.
Now, when I unlock the phone, the screen flashes blue, not just parts of it, the whole thing, almost like the display is going bad. If i open a game, it stops and wont do it again until i relock the screen.
Just curious of anyone else has had this happen.
Click to expand...
Click to collapse
I have the same issue after OTA to 4.4.2. Usually happens to me when in YouTube or MX Player.
I see others with the same issue over in the Motorola forums.
Looking forward to hearing from others who have had this issue and found a solution
braneed said:
I recently flashed the 4.4.2 OTA onto my phone, then downgraded to JB to flash Carbon but was not pleased so I reformatted the phone, put 4.4.3 back and then restored a nandroid from before I downgraded.
Now, when I unlock the phone, the screen flashes blue, not just parts of it, the whole thing, almost like the display is going bad. If i open a game, it stops and wont do it again until i relock the screen.
Just curious of anyone else has had this happen.
Click to expand...
Click to collapse
I also have had this problem with my droid razr maxx HD. I also have 4.4.2 and haven't flashed anything to it, but it is unlocked and rooted. It usually happens to me when im in portrait on the twitch.tv app. it stops after a bit, but I have no idea what is happening. it also stops if I go to landscape mode.
Balls Hurricane said:
I also have had this problem with my droid razr maxx HD. I also have 4.4.2 and haven't flashed anything to it, but it is unlocked and rooted. It usually happens to me when im in portrait on the twitch.tv app. it stops after a bit, but I have no idea what is happening. it also stops if I go to landscape mode.
Click to expand...
Click to collapse
ditto
Now that I see others affected I should probably expand on my original post above.
Initially I took the 4.2.2 OTA update with an unlocked bootloader. After the update, phone stuck in splash screen with the "Locked Bootloader" message.
I then rebooted into recovery and re-installed the 4.4.2 AOSP using RSD.
I too see the blue flash most frequently while watching video and occasionally while in Touchdown exchange.
dunroven said:
Now that I see others affected I should probably expand on my original post above.
Initially I took the 4.2.2 OTA update with an unlocked bootloader. After the update, phone stuck in splash screen with the "Locked Bootloader" message.
I then rebooted into recovery and re-installed the 4.4.2 AOSP using RSD.
I too see the blue flash most frequently while watching video and occasionally while in Touchdown exchange.
Click to expand...
Click to collapse
I was completely stock jellybean when I took the OTA, not rooted or unlocked or anything. I only recently unlocked and rooted mine. I'm pretty sure I had the problem before I did all that.
Two days ago my Galaxy Note 10.1 gt-n8010 got stuck at the initial screen (Samsung Galaxy Note 10.1)
It was working normally, and it was last successfully upgraded to a custom rom and CWM 6.0.3.6 a month ago.
The custom rom was (to my best knowledge Android Revolution HD 11.2 - 4.1.2)
Booting into recovery and download modes works.
CWM recovery works partially. Erasing Cache en resetting to factory works, and sometimes results in getting to the second splash screen of the boot process where it again gets stuck (Samsung animation keeps glowing), but more it keeps getting stuck at he first boot screen.
Erasing Dalvic cache leads to immediate reboot.
CWM log files cant be opened / external sd card can't be reached/mounted.
So CWM is only working for a small part.
I've attached images of the CWM screens including a log-screen that shows that files and folders cannot be found.
Using ODIN, to flash a new CWM or custom/original ROM result in a FAIL message.
Tried different ODIN version, two original Samsung data cables and two computers. Alle the same result. FAIL.
I'm hesitant to continue now without some help. I might do more harm and destroy all chances there are to recover this tablet.
I've flashed all my phones and tablets before. I'm not an expert, but never had a mishap, because I triple read the instructions. The situation that arises now is not a result of a failed upgrade/flash, but suddenly appeared one morning.
On the last days i thought i had also broken my tablet and i had more or less the same problem. If i were you i would directly download an official 4.4.2 and flash it via odin. Then if you everything works i would try whatever you want to flash
Try changing recovery. Give TWRP a try. Had it happen with a phone and switching recoveries solved it.
Sent from my SM-N900T using XDA Free mobile app
Well I had the same problem due to toooo many consecutive reboots
I was on gnabo then wid twrp
then I reflashed 4.4.2 update via odin and everything was a breeze after that
and one more thing
be sure to change the recovery cause the same one might not work again
well at least it didn't do worth me
I use philz now
Can't flash anything
Tried everything I could find but nothing works. I'm using windows 7 and cannot flash anything using Odin.
Download mode and CWM recovery still boot.
Are there other ways to communicate and reprogram the galaxy note 10.1?
Deadbeef said:
Tried everything I could find but nothing works. I'm using windows 7 and cannot flash anything using Odin.
Download mode and CWM recovery still boot.
Are there other ways to communicate and reprogram the galaxy note 10.1?
Click to expand...
Click to collapse
are you sure you do not have a bad cable
I've used two different original Samsung cables. Same result.
Brick?
Change a Odin version like odin 3.07 http://forum.xda-developers.com/showthread.php?t=1837605?
your odin shows your device is Samsung I9505 Galaxy S4
Where does Odin show the device is a i9505? It's a n8010.
reCAPTCHA
I am having similar issues (Galaxy Note 10.1 N8010 Gnabo ROM) - stuck on the samsung logo (never managed to get past it though) boots into recovery but can't mount sd card OR internal storage. Can't flash anything using Odin, always gets a Complete(Write) operation failed. Any suggestions ?
Looks like we're both in the same sinking boat.
Sorry for late reply
Deadbeef said:
Where does Odin show the device is a i9505? It's a n8010.
Click to expand...
Click to collapse
Sorry for late reply
Your Odin Screen Shot Say i9505 as your device
Deadbeef said:
Looks like we're both in the same sinking boat.
Click to expand...
Click to collapse
I join u guys as well....
also was on gnabo rom and suddenly stuck on Samsung screen... however what's different from you is that I have a N8000 and Odin flashing shows "PASS". But whatever I flash doesn't boot... I think I need to open a thread about it.
georgesmh said:
I join u guys as well....
also was on gnabo rom and suddenly stuck on Samsung screen... however what's different from you is that I have a N8000 and Odin flashing shows "PASS". But whatever I flash doesn't boot... I think I need to open a thread about it.
Click to expand...
Click to collapse
Same here with Ganbo v7 since ysterday....
Just get stuck on Samsung logo and nothing works, even reverting to older backup image
Agyar said:
Same here with Ganbo v7 since ysterday....
Just get stuck on Samsung logo and nothing works, even reverting to older backup image
Click to expand...
Click to collapse
guys did any of you solve the problem??
georgesmh said:
guys did any of you solve the problem??
Click to expand...
Click to collapse
Nothing yet.... I've tried one old backup of v5 I've had and that won't boot now as well...
Really strange. I'm hoping to get it working somehow over the weekend latest, since I'll be on business trip next week and would like to have operating device on airplanes.
Agyar said:
Nothing yet.... I've tried one old backup of v5 I've had and that won't boot now as well...
Really strange. I'm hoping to get it working somehow over the weekend latest, since I'll be on business trip next week and would like to have operating device on airplanes.
Click to expand...
Click to collapse
maybe it's a problem from Gnabo ROM itself??? What's really sad is nobody on the threads knows how to help us
Uni starts next week!
georgesmh said:
maybe it's a problem from Gnabo ROM itself??? What's really sad is nobody on the threads knows how to help us
Uni starts next week!
Click to expand...
Click to collapse
I've seen few other occurrences of this on different roms on various forums, so probably not Gnabo issue. also, nobody nowhere had a fix for it
I had similar problem last November with a stock 4.4.2 ROM. Fortunately it was still in warranty (2 years in the UK) and Samsung took it in and replaced both battery and main board. They did not explain what was wrong, only that they were seeing quite a few with this issue. Could it be flash failure?
dmarchant said:
I had similar problem last November with a stock 4.4.2 ROM. Fortunately it was still in warranty (2 years in the UK) and Samsung took it in and replaced both battery and main board. They did not explain what was wrong, only that they were seeing quite a few with this issue. Could it be flash failure?
Click to expand...
Click to collapse
I don't think it was flash failure, at least not in my case, since device worked without any issue for quite a while after last flashing... what was different now is that my battery was drained out for the first time i quite a while...
I've updated my Note Edge (italian, 100% stock) to Lollipop few days ago, but i really don't like it, i think it's the worst android version i ever used (i hate, a lot, how the lockscreen works now).
Is there any safe (and maybe easy) way to reinstall Kitkat 4.4.4?
i've found this guide searching with Google:
http://androidsigma.com/how-to-downgrade-samsung-note-edge-from-android-lollipop-to-kitkat/
is it ok?
thanks in advance
Goofy-Goober said:
i've found this guide searching with Google:
http://androidsigma.com/how-to-downgrade-samsung-note-edge-from-android-lollipop-to-kitkat/
is it ok?
thanks in advance
Click to expand...
Click to collapse
I did it just the way the guide says, download your official Rom for you phone from sammobile, then use odin, its pretty straight forward, if you get into a bootloop, just wipe cache and it should boot.
MHeat said:
I did it just the way the guide says, download your official Rom for you phone from sammobile, then use odin, its pretty straight forward, if you get into a bootloop, just wipe cache and it should boot.
Click to expand...
Click to collapse
ok, thanks for the reply.
you did the downgrade starting from an original Lollipop rom?
because my phone is non-rooted and 100% stock now, with the Lollipop rom that i received via KIES update.
Goofy-Goober said:
ok, thanks for the reply.
you did the downgrade starting from an original Lollipop rom?
because my phone is non-rooted and 100% stock now, with the Lollipop rom that i received via KIES update.
Click to expand...
Click to collapse
I have the SM-N915T the version from tmobile, but when i bought it from a third party (brand new and unlocked) it did not come with the tmobile rom, it was the one from trinidad and tobago kitkat 4.4.4)
so i downloaded the lollipop Rom for Tmobile, and it worked fine, but i did not like all the bloatware from Tmobile so i decided to go back to kitkat, so i downloaded the kitkat version i had before, downloaded it from sammobile
checked usb debugging in developers settings, then put the phone in download mode, opened odin, click on PDA and selected the kitkat rom i had downloaded from sammobile, everything went fine, after everything completed, remember to wait for the PASS message fro odin, do not disconnect the phone unless it says PASS, after that the phone just boot looped, samsung logo, then samsung logo. So i booted to recovery and cleared cache, after that the phone booted just fine. So basically that is what i did, no problems at all, just make sure you download the Rom for yous specific Edge Model.
i've succesfully downgraded my phone
after the flash with Odin the phone was bootlooping, but with a full wipe (data and cache) everything was ok
now i've disabled automatic firware updates and i'll stick to KK 4.4.4 till Google new updates to Lollipop and the awful head-ups notification system.
thank you very much!
Goofy-Goober said:
i've succesfully downgraded my phone
after the flash with Odin the phone was bootlooping, but with a full wipe (data and cache) everything was ok
now i've disabled automatic firware updates and i'll stick to KK 4.4.4 till Google new updates to Lollipop and the awful head-ups notification system.
thank you very much!
Click to expand...
Click to collapse
Cool man, glad everything went fine.
Hi,
I am having bootloop issue even after I clear with cache and dalvik from the recovery. I flashed with ODIN(N915GXXU1ANK4_N915GOLB1ANK4_MM1.zip) from Lollipop 5.0.1 as mine is Singapore unit. Anyone care to share their experience on how to recover from this.....
yltan said:
Hi,
I am having bootloop issue even after I clear with cache and dalvik from the recovery. I flashed with ODIN(N915GXXU1ANK4_N915GOLB1ANK4_MM1.zip) from Lollipop 5.0.1 as mine is Singapore unit. Anyone care to share their experience on how to recover from this.....
Click to expand...
Click to collapse
This is how i did from lollipop rollback to kitkat CWM > wipe data/factory reset > wipe cache partition > advance > wipe dalvik cache > turn off phone go to download mode > odin start to flash kitkat (SM-N915G Singapore)
The way I recovered this is factory reset instead of clearing the cache. Now running Kit Kat and very much happier...
yltan said:
The way I recovered this is factory reset instead of clearing the cache. Now running Kit Kat and very much happier...
Click to expand...
Click to collapse
Thanks for the suggestion. It worked as I went from Lollipop to Kit Kat. Much happier, especially considering the camera button on the edge panel for both selfie and normal mode. makes life a whole lot easier
I have a Verizon edge but everytime I try to flash back to kitkat with odin, it says it fails. I've tried 2 different files but neither seem to work. Are there any other methods or any other place to get the file from other than sammobile? Lollipop has killed my love for this phone. Maybe I'm doing something wrong. Who knows.
blayzejlm said:
I have a Verizon edge but everytime I try to flash back to kitkat with odin, it says it fails. I've tried 2 different files but neither seem to work. Are there any other methods or any other place to get the file from other than sammobile? Lollipop has killed my love for this phone. Maybe I'm doing something wrong. Who knows.
Click to expand...
Click to collapse
If you know the baseband number of the verizon 4.4.4 Stock ROM, my T Mobile one is N915TUVU1ANK3, you can search for it on https://www.androidfilehost.com/
Downloads much faster with none of that stupid gimmicky pricing.
This phone really shines on Kit Kat. if only Samsung put just a little more effort in maintaining the features of Kit Kat on Lollipop. I really do like the face lift of Lollipop but I'll take the ergonomic Kit Kat that takes full advantage of the Edge any day.
hi guys, im using note edge, sprint N915P, with 5.1.1 but my fingerprint have problem. I would like to downgrade to 4.4.4, is that ok or any suggestion i need to pay attention? I heard that the phone will be null, lost imei if we try to downgrade, is that real? Thanks all
phognle said:
hi guys, im using note edge, sprint N915P, with 5.1.1 but my fingerprint have problem. I would like to downgrade to 4.4.4, is that ok or any suggestion i need to pay attention? I heard that the phone will be null, lost imei if we try to downgrade, is that real? Thanks all
Click to expand...
Click to collapse
Never heard the IMEI thing before. Doesn't even make sense to me. Just download the stock 4.4.4 ROM for sprint via Odin.
Read the above directions In the thread.
edo101 said:
Never heard the IMEI thing before. Doesn't even make sense to me. Just download the stock 4.4.4 ROM for sprint via Odin.
Read the above directions In the thread.
Click to expand...
Click to collapse
Thanks, im dowloading the 4.4.4 Rom and wait for the good result, this is my first time, so nervous.
phognle said:
Thanks, im dowloading the 4.4.4 Rom and wait for the good result, this is my first time, so nervous.
Click to expand...
Click to collapse
i tried but it said fail, my baseband is N915PVPU4COG1, and i downloaded the firmware "N915PVPU1ANK1_N915PSPT1ANK1_XAS" from sammobile. Did i download the correct firmware? Please support. Thanks a lot.
What was the fail message? was it aboot.mbn????
Thanx
Yes thats the failed message I got. I tried the file from 2 different sites.
blayzejlm said:
Yes thats the failed message I got. I tried the file from 2 different sites.
Click to expand...
Click to collapse
Yeah I got the same error message attempting to move from the firmware for SM-N915P (5.1.1.) to SM-N915FY(5.0.1.) though I've seen a few people talk about the fact that you can't go backwards now.
SM-G930F
TWRP 3.62_9-0
Last Known ROM: [TeamExyKings][S7_S7Edge_G930_G935_F_FD][Pie_9.0][15-January-2020][Note_FE_Port][v20]LightROM
I'm trying to get my S7 to stock. I have no idea where it's going wrong. This all started when I went to get my phone off the charger and it looked like it took a hard crash. Im not sure why either. I can get into DOWNLOAD MODE, and I can reflash my TWRP with ODIN. Whenever I go to flash a ROM in TWRP, it freezes on install, and I have to hard reset it. Anyways, my end goal is to get my S7 back to stock. Thank you so much in advance.
I've managed to get a rom(LightROM) in.. but I am stuck on a BLUE LED and a Black Screen? Anyone got the possible solution to get back to a stock rom? I am actually having a hard time finding a stock rom as well.
RowtronX said:
SM-G930F
TWRP 3.62_9-0
Last Known ROM: [TeamExyKings][S7_S7Edge_G930_G935_F_FD][Pie_9.0][15-January-2020][Note_FE_Port][v20]LightROM
I'm trying to get my S7 to stock. I have no idea where it's going wrong. This all started when I went to get my phone off the charger and it looked like it took a hard crash. Im not sure why either. I can get into DOWNLOAD MODE, and I can reflash my TWRP with ODIN. Whenever I go to flash a ROM in TWRP, it freezes on install, and I have to hard reset it. Anyways, my end goal is to get my S7 back to stock. Thank you so much in advance.
I've managed to get a rom(LightROM) in.. but I am stuck on a BLUE LED and a Black Screen? Anyone got the possible solution to get back to a stock rom? I am actually having a hard time finding a stock rom as well.
Click to expand...
Click to collapse
Going back to stock is probably the best option, download the firmware from here selecting your country and carrier
Download Samsung Galaxy S7 SM-G930F firmware
Download the latest Samsung firmware for Galaxy S7 with model code SM-G930F. Check out our free download or super fast premium options.
www.sammobile.com
you will have two csc files the csc file wipes the phone whereas the home csc upgrades the software, you would use home if you had a working rom say Android 7 and wanted to upgrade to 8. You want to wipe the phone.
Not_Rich said:
Going back to stock is probably the best option, download the firmware from here selecting your country and carrier
Download Samsung Galaxy S7 SM-G930F firmware
Download the latest Samsung firmware for Galaxy S7 with model code SM-G930F. Check out our free download or super fast premium options.
www.sammobile.com
you will have two csc files the csc file wipes the phone whereas the home csc upgrades the software, you would use home if you had a working rom say Android 7 and wanted to upgrade to 8. You want to wipe the phone.
Click to expand...
Click to collapse
well i went in TWRP and formatted/wiped everything. Would i still need a rom? I feel like something is mad corrupted. Maybe a Kernel? I haven't been successful of flash a room or getting into the OS yet. I just need to get into the phone and have it turn on.