[Q] Flashing Custom Roms Problem - Samsung Galaxy Fit GT 5670

Hey,
I have been having many problems with flashing custom roms on my fit. Let me describe it to you.
After flashing the custom rom and following the instruction (wipe data etc), when I reboot my device it doesn't boot up (in stock based roms), sometimes it displays a black screen with android written on the side (in cyanogen-mod 7 based roms). The only custom rom that has worked for me till now is 'RazoDroid' (I'm not trying to advertise or anything).
Please help me, I have downloaded more than 15 custom roms and none of them work.
Thank You.

UltimateWater said:
Hey,
I have been having many problems with flashing custom roms on my fit. Let me describe it to you.
After flashing the custom rom and following the instruction (wipe data etc), when I reboot my device it doesn't boot up (in stock based roms), sometimes it displays a black screen with android written on the side (in cyanogen-mod 7 based roms). The only custom rom that has worked for me till now is 'RazoDroid' (I'm not trying to advertise or anything).
Please help me, I have downloaded more than 15 custom roms and none of them work.
Thank You.
Click to expand...
Click to collapse
how long did you wait before deciding that the rom doesnt boot.
wait atleast 5 min for the bootanimation to come.
then the total boot time can be as long as 20min .
so dont be desperate and wait do something else till then.
If still problem persists make a boot logcat i.e. start a logcat boot the device wait the prescribed 20 min and close the logcat and post it here.
also do the above mentioned thing for cm7 official and let me know.:good:

Thanks for your reply,
I have waited for as long as an hour.
I finally got it working.
1) For Cm based roms, I had to format /system.
2) I don't actually know how it worked on stock based roms this time, I tried the instructions given by a.cid not the Rom's instruction provided in their respective threads.
Thank You to a.cid for your beginner's guide. Press the thanks button on his thread here, if he helped you too.

Related

[Q] Newbieee in need of HELPPPP ASAP!! lol

Ok first off I have to say that this site is great I have found alot of helpfull and some confusing topics here lol. the other day I downloaded the cyanogen mod 7 and everything is working perfectly on my htc evo sprint
my only problem I noticed is that I dont know how to revert back to The HTC Sense ui. My other question is that I noticed alot of different roms on here and some I have tried installing but some wont work for me and some freeze when i attempt to reboot. Can anyone help me out please!!!
To revert back to Sense from Cyanogen, you'll have to reflash the ROM that came stock on your device. You should be able to find this in the forum for your device (EVO).
There are many different ROMs available here, some will work for you and some you may experience difficulty with. Most Devs usually post step-by-step instructions for installing their ROMs in the Opening Post (OP) of the thread. If you follow these you'll usually be fine, and you can always flash back to stock and start again if you get into trouble.
Good luck, and welcome to XDA
Did you do a nandroid backup first? If not, you should always do one before flashing. If you did, just restore through your recovery & you'll be back where you were before.
If CM7 is functional but you just don't like it, I would go ahead and do a nandroid backup anyway, so if anything messes up you'll at least have something working you can restore.
If you want something like stock, I would suggest the Sprint Lover's Rom. Myn's Warm 2.2 would also be good, or you could try out Warm Z which is the new version of Sense. I'm assuming you like Sense as a UI & as a launcher?
I've heard great things about Mikfroyo as well. If you're new to rooting/flashing, I would suggest using a stable Rom instead of an experimental one - at least until you get the hang of it.
If you're having trouble flashing ROMs, try switching to Amon Ra recovery (I assume you're using clockwork) and try flashing again. You can do this through ROM Manager (it came with CM7). Just choose "flash alternate recovery".
Before rooting, modifying, and flashing ROMs, you're supposed to have a clear understanding of it all. I suggest reading the stickies in the Evo forums & any guides you can find. Read everything. Seriously.
I have an Evo as well, so if you need anything, I'm here. Just ask. If you need some guidance & handholding, send me a pm & I'll walk you through everything. Just be sure to educate yourself. There's no such thing as knowing too much when it comes to modifying your phone.
EDIT: If the phone gets stuck on the splash screen after flashing a Rom, it's most likely because you didn't wipe properly. Be sure to wipe data/factory reset, wipe cache & dalvik cache.
Thank u kindly
Both of you were helpful I will take my time and read and explore the forums in hopes of understanding clearly yes i am running clockwork is this ananran better? if so how can i use it ?

[Q] Custom ROM always bricking

Hi there, I have been trying for countless hours to make a custom ROM work on my P920 with no results, always some issues. I've managed to brick my phone in different ways a billion times now, then spent billion hours unbricking it and in the end I'm always back to where I started. I would really love some help please.
My phone is P920.
The android version I'm running is: 2.3.5
Kernel version: 2.6.35.7+
Software version: V21E
Rooting method: megatron
Now I would like a ROM that uses Android 4 and that can still use the 3D features such as 3D camera, the ROM calledthe Darkroom International would be an example I imagine.
While that's one of the ROMs that I would want, I've tried many, and always encountering issues, let me clarify.
First of all my device has to be rooted and since SuperOneClick doesn't work for me as it gets stuck on step 7, I use megatron which works well. I even double check if my phone is rooted with the Root Checker from the Android store. Now according to the guides I've read I need a custom recovery system, so I install Clockworkmod. I then place the ROM on the SD card, in the recovery menu I delete cache, that other cache, format it, format system, data, everything those guides tell me to. Afterwards, I install the ROM by selecting the zip and then I reboot. I've tried like 3 different ROMs, jellybem, cyanogenmod and some other. Yes I know none of them support 3D features - I didn't know at the time. Anyway, the issue was always the same, right after the LG logo there would be a screen with some weird colors showing the display of what happened before the phone crashed. Before it crashed? Yes, the phone would actually boot into the ROM but only for a few minutes, crashing afterwards. The next time I would boot, it would show that weird screen with those fancy colors with what happened just before it crashed. So I followed some steps and I got back to the original 2.3.5 ROM, everything back to normal.
I tried doing some more research and I came across the Darkroom Intentional ROM which had a bit different instructions. It asked me to install TWRP recovery with a bootloader, so I did, successfully, then did all the clean cache etc, installed ROM, bam, wouldn't boot at all. Oh boy have I had issues here, I couldn't even get it back to the default 2.3.5 stock ROM because my phone wasn't even recognized in the device manager. So I did some more research, found a solution, managed to flash back to 2.3.5 stock and I'm back to square one.
Now, could someone please help and explain to me what exactly have I done wrong and how I can make it right? I've spent countless hours now trying to install a custom ROM with no success. Sorry about the long read. If you need me to supply some more information please let me know. Thank you.
First of all if u want to use an ICS ROM then u need to update to ICS FIRST u can't flash it directly from 2.3.5 u can use xbsalls thread to update......
Next if cm based Roms are crashing then u need to flash bootloaders which means u should use os_hacking tool to flash ICS bootladers if u wanna update
Or flash GB bootloaders
So first update if u want
Root
Flash bootloaders
Flash recovery
Flash Roms
Sent from my Nexus 4 using xda app-developers app

[Q] How to reflash a new rom?

Hi!
I flashed pac-rom but it keeps my phone awake 24hrs even when i am sleeping therefore 70% battery consumption when i am sleeping and everyday i have been posting in that thread for help or update but dev has left,and this was a stable version with never ending problems for me.So i want to remove this and see if the other rom also behaves like this or not.
I want to remove this rom and gapps as well but i am a newbie and never did this before.I will be really grateful if someone guide me step by step in this.
Please reply soon coz i am not able to live a normal life as battery is creating problems for me.Thanks a lot in advance
LG P500 rooted,pac-rom,aokp 4.2.2,stock kernel
Read the sticky thread!
Here it is.. http://forum.xda-developers.com/showthread.php?t=1152306
Sent from my LG-P500 using xda premium
I know that dear
kunnaliskinng said:
Read the sticky thread!
Here it is.. http://forum.xda-developers.com/showthread.php?t=1152306
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
As i said i am newbie things are not clear to me and what i asked in the question is not mentioned clearly and exactly.And since 7 days i am stuck in this esp last three days coz either the rom is a problem or need to be reflashed.And how to remove gapps etc that is not clear dear.Anyone who has a helping nature would write few lines or steps if he wants to help.My head is screwed up with this rom,nothing is working properly and all the time i am busy with my phone.Can't even open my eyes now as i have been continously looking at small screen.
Do not know if i have to reset the phone again or what,how to remove gapps as i do not have google store,gmail and maps in that. I always try to help a newbie coz i know he will not understand things clearly and can screw up,and in my case an experience person can tell if it is some thing else i should do along with that i.e if he would be concerned.
You are the king man so you would not know these small petty things.
Anyway thanks for whatever best you could do.
@kitu34: The procedure for flashing a new ROM is always the same:
1. Download the ROM, put it on your SD card (I recommend creating a folder in your SD card for your ROMs, kernels, etc., so that they're all in one place, but that's just a suggestion, not a requirement. Optional: Download the recommended GAPPS package for the ROM (if the ROM comes with built-in GAPPS, no need to download this).
2. Boot into recovery. You should be able to reboot into recovery simply by pressing power button > reboot > recovery. If not, then shutdown the phone and press & hold power+volume down+home.
3. In recovery, perform a factory reset (wipe data & cache), wipe dalvik-cache, and wipe system.
4. In recovery, flash the zip of the ROM you want to install (the procedure for this depends on your custom recovery; just browse around the menus for the option to flash a zip). If the ROM has a separate GAPPS package, you can also flash it here. Note: Always flash the GAPPS after you flash the ROM, not before.
5. Reboot system.
Flashing a custom kernel uses the same procedure, except you only wipe cache & dalvik-cache in step 3.
____________________
Sent from the moon.
____________________Sent from the moon.[/QUOTE]
Thanks.Ok it is exactly the same.And what if i just have to update the rom,in case i need?
(Two times thanks due to moon from a man just living on earth hhehehe)
Flashing a custom kernel uses the same procedure, except you only wipe cache & dalvik-cache in step 3.
____________________
Sent from the moon.[/QUOTE]
Just confused whether to reflash pac rom or flash either rashed's 10.1 or Jenkin's.Maybe first flashing went wrong coz i am having lots of problems and the phone is awake 24hrs.I want a good rom but battery friendly
kitu34 said:
Thanks.Ok it is exactly the same.And what if i just have to update the rom,in case i need?
(Two times thanks due to moon from a man just living on earth hhehehe)
Click to expand...
Click to collapse
Update the ROM? Do you mean flashing a newer version of the same ROM? Some ROMs can be updated by simply wiping cache, dalvik, & system (no need to wipe data), then flashing the new version. Personally, I advise doing a clean install every time when installing a new ROM, even if it's just an update. That means a full wipe: data, cache, dalvik-cache, & system. A clean install helps you avoid potential errors.
____________________
Sent from the moon.
Syd_M said:
Update the ROM? Do you mean flashing a newer version of the same ROM? Some ROMs can be updated by simply wiping cache, dalvik, & system (no need to wipe data), then flashing the new version. Personally, I advise doing a clean install every time when installing a new ROM, even if it's just an update. That means a full wipe: data, cache, dalvik-cache, & system. A clean install helps you avoid potential errors.
____________________
Sent from the moon.
Click to expand...
Click to collapse
Thanks a lot, but any advise on those three roms? and i need a stable one
kitu34 said:
Thanks a lot, but any advise on those three roms? and i need a stable one
Click to expand...
Click to collapse
If you want good battery life, then I suggest staying away from Jelly Bean ROMs for now -- the battery drain is huge. If you want to try a stable JB ROM, then the latest Jenkins build is good, as long as you don't mind battery drain and a couple of relatively major bugs (those being bluetooth A2DP not working and wifi hotspot reboot).
If you want a relatively more stable, but still high-end, ROM, then stick with ICS. Hephappy's CM9 is good (check the thread in the General LG-P500 forum), or if you want a tweaked & modded ICS, then get neko95's ICySNAP.
That said, the king of battery life still is Gingerbread. I'm personally using the latest unofficial CM7.2 build by FitAmp; it's stable and with good battery life, better than ICS or JB.
____________________
Sent from the moon.
Syd_M said:
If you want good battery life, then I suggest staying away from Jelly Bean ROMs for now -- the battery drain is huge. If you want to try a stable JB ROM, then the latest Jenkins build is good, as long as you don't mind battery drain and a couple of relatively major bugs (those being bluetooth A2DP not working and wifi hotspot reboot).
If you want a relatively more stable, but still high-end, ROM, then stick with ICS. Hephappy's CM9 is good (check the thread in the General LG-P500 forum), or if you want a tweaked & modded ICS, then get neko95's ICySNAP.
That said, the king of battery life still is Gingerbread. I'm personally using the latest unofficial CM7.2 build by FitAmp; it's stable and with good battery life, better than ICS or JB.
____________________
Sent from the moon.
Click to expand...
Click to collapse
ok then for now i will try jenkin's coz that was the first rom i downloaded on my pc but did not flash.actually i have serious battery and other issues that is why i am just getting rid of this now and then read about the roms you mentioned.after fashing i will tell you how it goes and if that also has a battery issue then the next...so kind of you to help as there are very few people here who really want to help.(the other day grgtm from cebu really helped me when my phone went in fastboot,cebu guys are damn good hehe)thanks a lot
4. In recovery, flash the zip of the ROM you want to install (the procedure for this depends on your custom recovery; just browse around the menus for the option to flash a zip). If the ROM has a separate GAPPS package, you can also flash it here. Note: Always flash the GAPPS after you flash the ROM, not before.
I am doing with jenkins as i already have but it does not have gapps as i am not flashing the very last update which has gapps with it.\So is it ok to use rashed's cm10's mini gapps?
kitu34 said:
I am doing with jenkins as i already have but it does not have gapps as i am not flashing the very last update which has gapps with it.\So is it ok to use rashed's cm10's mini gapps?
Click to expand...
Click to collapse
Yes, Rashed's mini gapps is for all cm10.x roms, including the Jenkins builds.
Edit: By the way, grgtm is from Romania, not Cebu (Philippines). You probably got him mixed up with someone else.
____________________
Sent from the moon.
Syd_M said:
Yes, Rashed's mini gapps is for all cm10.x roms, including the Jenkins builds.
Edit: By the way, grgtm is from Romania, not Cebu (Philippines). You probably got him mixed up with someone else.
____________________
Sent from the moon.
Click to expand...
Click to collapse
Hahaha you are right it was you who is from cebu and i was asking him if it is night time in phillipines then he told me he is from Romania.My mistake.
Ok listen i did that and just wanted to check but the home button is not responding,any ideas? Thanks
BUT WHEN SCREEN IS OFF I CAN WAKE UP WITH THE HOME BUTTON AND I DOWNLOADED WHATSAPP BUT THE USUAL NOTIFICATION IN THE NOTIFICATION BAR DID NOT COME.I think have to reflash again
kitu34 said:
Hahaha you are right it was you who is from cebu and i was asking him if it is night time in phillipines then he told me he is from Romania.My mistake.
Ok listen i did that and just wanted to check but the home button is not responding,any ideas? Thanks
BUT WHEN SCREEN IS OFF I CAN WAKE UP WITH THE HOME BUTTON AND I DOWNLOADED WHATSAPP BUT THE USUAL NOTIFICATION IN THE NOTIFICATION BAR DID NOT COME.I think have to reflash again
Click to expand...
Click to collapse
The home button not working is a result of a GAPPS error when the system partition is too full. You'll need to trim the ROM prior to flashing (search the cm10 thread; it's too complicated for me to explain here) or download the version of cm10.1 with built-in GAPPS. The fact of the matter is, our phones has a very small system partition, hence why we have to go to all this trouble when using JB.
____________________
Sent from the moon.
Syd_M said:
The home button not working is a result of a GAPPS error when the system partition is too full. You'll need to trim the ROM prior to flashing (search the cm10 thread; it's too complicated for me to explain here) or download the version of cm10.1 with built-in GAPPS. The fact of the matter is, our phones has a very small system partition, hence why we have to go to all this trouble when using JB.
____________________
Sent from the moon.
Click to expand...
Click to collapse
Thanks,but first i am trying to reflash coz in the first time i wiped even cache partition and now i will try without that coz i did not yet get an answer to how to trim
You're seriously going to need to learn how to help yourself, @kitu34. Instead of asking for step-by-step instructions all the time, try looking for them yourself; simply using the "search this thread" function and running a search for "trim" in Rashed's thread would give you what you need. In fact, here's the link to the program used to trim ROMs: http://forum.xda-developers.com/showpost.php?p=33349661 -- that link was in the first post of Rashed's thread, labeled (and in very big letters) CLICK ME. The instructions for using the program is also in the thread, and the program's interface is so simple that simply browsing around should tell you what to do.
____________________
Sent from the moon.
Syd_M said:
You're seriously going to need to learn how to help yourself, @kitu34. Instead of asking for step-by-step instructions all the time, try looking for them yourself; simply using the "search this thread" function and running a search for "trim" in Rashed's thread would give you what you need. In fact, here's the link to the program used to trim ROMs: http://forum.xda-developers.com/showpost.php?p=33349661 -- that link was in the first post of Rashed's thread, labeled (and in very big letters) CLICK ME. The instructions for using the program is also in the thread, and the program's interface is so simple that simply browsing around should tell you what to do.
____________________
Sent from the moon.
Click to expand...
Click to collapse
Thanks,i did search the thread by the relevant keywords but was not clear that i simply have to remove apps after flashing or before or what and the link you gave did not strike me would be for trimming.Now i know as someone told me to use titanium but the link i have not read fully but it is helpfull and will read now.Thanks again
Just for your info
kitu34 said:
Thanks,i did search the thread by the relevant keywords but was not clear that i simply have to remove apps after flashing or before or what and the link you gave did not strike me would be for trimming.Now i know as someone told me to use titanium but the link i have not read fully but it is helpfull and will read now.Thanks again
Click to expand...
Click to collapse
That link to the website is closed,i mean the website is closed.Bye
I tried Jenkins with rashed's mini gapps and worked perfectly(except battery drain), instead using an tool for rom editing, use an app like root uninstaller to get read of unnecessary apps to free some space on internal memory or use an d2ext script(but it got some strange behavior from my phone, you need a really fast sd card, an class 10 for that, and a reliable brand, mine is class 4, so in the final, sd card will worth half price of the phone)
grigtm said:
I tried Jenkins with rashed's mini gapps and worked perfectly(except battery drain), instead using an tool for rom editing, use an app like root uninstaller to get read of unnecessary apps to free some space on internal memory or use an d2ext script(but it got some strange behavior from my phone, you need a really fast sd card, an class 10 for that, and a reliable brand, mine is class 4, so in the final, sd card will worth half price of the phone)
Click to expand...
Click to collapse
Thanks,i have both titanium and es explorer,can i do with that by simply uninstalling system app? Actually someone told me not to this way and instead trim the rom.Even i am confused what is the difference.Either it creates problems or the amount of space we get by uninstalling with titanium is less compared to trimming the rom.
I will later what i did later.

Ambient display keeps screen backlight on

Hello.
My problem is that sometimes, when I receive a notification, ambient display turns screen on to show it (as it should do normally), but then, when it is supposed to turn screen off again, it only goes black, but the backlight is still on. It's hard to notice, but I don't want the backlight on, using battery, when I think it's off.
The only way to turn it off is by activating ambient display again (moving the phone, waving in front of proximity sensor, pressing power button), and then it would show my normal lock screen and then turn off, until "something" makes it leave the backlight on again.
Anyone have/had/knows this issue? I've used Mokee ROM, now I'm on RR and it happened on both, I don't remember if it happened in CM. Could it be something app related?
Thanks.
Yeah same happened with cm 12.1 latest nightly too.....just checked it now...
The Answer
Hi there !
When you have installed the custom rom, you have probably flashed directly from another custom rom , is this correct?
If so, it may be your phones drivers slightly messed up at the moment seeing as it has different parts from other roms, depending on how you flashed it.
My solution would be to flash the stock firmware , which can easily be found in the forums, and then flash twrp, then your rom of choice. If that doesn't work, its likely a bug in that specific build of the rom you are installing , seeing as another person who has replied has had the same problem .
therealduff1 said:
Hi there !
When you have installed the custom rom, you have probably flashed directly from another custom rom , is this correct?
If so, it may be your phones drivers slightly messed up at the moment seeing as it has different parts from other roms, depending on how you flashed it.
My solution would be to flash the stock firmware , which can easily be found in the forums, and then flash twrp, then your rom of choice. If that doesn't work, its likely a bug in that specific build of the rom you are installing , seeing as another person who has replied has had the same problem .
Click to expand...
Click to collapse
That's strange! I guess it may be something like the drivers you said, because just one user said that have the same problem, but I'll have to wait until I have some free time to flash stock and root and flash CM and restore all apps and that again... I hate that part of installing another ROM.
therealduff1 said:
Hi there !
When you have installed the custom rom, you have probably flashed directly from another custom rom , is this correct?
If so, it may be your phones drivers slightly messed up at the moment seeing as it has different parts from other roms, depending on how you flashed it.
My solution would be to flash the stock firmware , which can easily be found in the forums, and then flash twrp, then your rom of choice. If that doesn't work, its likely a bug in that specific build of the rom you are installing , seeing as another person who has replied has had the same problem .
Click to expand...
Click to collapse
I flashed stock using fastboot and then RR but the problem persists... Any other ideas??
Secuential said:
I flashed stock using fastboot and then RR but the problem persists... Any other ideas??
Click to expand...
Click to collapse
Ok, I have spent some time thinking about this one for you, as I really want you to get this one fixed!
Although I need abit more information.
1) Does the issue occur on stock rom?
2)Are you sure it is not a problem with the build you are running?
3)What exact steps did you use to flash the rom?
To show that you appreciate my help so far, please click thanks
therealduff1 said:
Ok, I have spent some time thinking about this one for you, as I really want you to get this one fixed!
Although I need abit more information.
1) Does the issue occur on stock rom?
2)Are you sure it is not a problem with the build you are running?
3)What exact steps did you use to flash the rom?
To show that you appreciate my help so far, please click thanks
Click to expand...
Click to collapse
Thanks!
1)I can't tell if it occurs on stock, because on stock I use moto display (which doesn't have this issue).
2) I'm almost sure, because I've used 2 ROMs and both do the same. Maybe I'll have to try with CM nightlies?
3)I followed the guide in "general" section to flash stock using fastboot and android sdk. After that, I booted on stock, then rebooted to bootloader, flashed TWRP, entered to recovery, wiped data and then flashed RR ROM with it's gapps and then flashed moto camera and gallery. After that, wipe dalvik and cache and rebooted to system.
Right , ok. I recommend trying one of the cm12 nightly builds, seeing as they worked on my phone fine in terms of ambient display
therealduff1 said:
Right , ok. I recommend trying one of the cm12 nightly builds, seeing as they worked on my phone fine in terms of ambient display
Click to expand...
Click to collapse
Well, the other user that commented on this post was also using latest CM nightly, so I'm not very positive about it, but I may try it when I have time.
Well , looking at all of the information In this post , I think it is safe to say ambient display is not fully working on many roms :/
I installed a new build of cm12 earlier, and I found that sometimes the backlight will stay on , but other times it is fine.
If you want to work on this together, email me at [email protected] , and then we can look into it abit further ?
I will take a thorough look into the forums to see if others are recieving any problems as well .
therealduff1 said:
Well , looking at all of the information In this post , I think it is safe to say ambient display is not fully working on many roms :/
I installed a new build of cm12 earlier, and I found that sometimes the backlight will stay on , but other times it is fine.
If you want to work on this together, email me at [email protected] , and then we can look into it abit further ?
I will take a thorough look into the forums to see if others are recieving any problems as well .
Click to expand...
Click to collapse
Thanks! I have a lot of work right now, so I can't work with this now, but I'll email you when I have more free time!

[Completed] Galaxy Fame s6810L - Stuck in CWM after flashing a custom ROM

Hey!
First of all, this post will be too hard to write because of my English.
I had decided to improve the performance of my Fame a long time ago (I have to clarify that I'm a noob at flashing roms and doing related stuff). So I flashed Galaxy Fame - Stock deodexed and it worked perfect.
After a while my cell phone became slow again so I installed Cyanogenmod 12.1. I didn't like that rom due to the bugs and performance.
So I wiped the data/cache/dalvik and re-flashed the previous deodexed rom again.
What's the problem? It boots and stays in the "s6810L" screen for a few seconds, then reboots and stays in that screen again for a few seconds and THEN it shows the CWM recovery menu.
I haven't tried another rom yet, but I want to know why it didn't work this time... I really like the deodexed rom because it's so smooth and fast.
What am I doing wrong?
I'm sorry for my english again, thanks in advance, and regards!
Edit #1: I'm using this CWM
Hi !
When flashing roms a factory reset is recommended especially when flashing between 2 totally different based roms , cyanogen / stock
My advice is to use odin and revert to stock , don`t flash via recovery
Also , I can move this thread to the designated location if you continue to have problems and the solution I suggested doesn`t work , there may be more users with the same device.
Use the same thread you have linked above to get the firmware
Good luck and let me know !

Categories

Resources