Ok bought a telus mega SGH-I527M with a broken screen,bought a screen on ebay (seller swears it is origional)but I think he is lieing as it has a black back to it instead of my beige origional screen and doesnt even have the numbers sticker on it,but anyhow worked great for an evening and I unlocked useing a code for rogers,it downloaded an update on its own and asked me if I wanted to install,so I did the update and when it rebooted the screen wouldnt unlock with a swipe any more so I factory restored it now can not press next at the start,can I go back to old firmware?stock rom for rogers instead of telus?and how?or any other ideas?thanks.
[email protected] said:
Ok bought a telus mega SGH-I527M with a broken screen,bought a screen on ebay (seller swears it is origional)but I think he is lieing as it has a black back to it instead of my beige origional screen and doesnt even have the numbers sticker on it,but anyhow worked great for an evening and I unlocked useing a code for rogers,it downloaded an update on its own and asked me if I wanted to install,so I did the update and when it rebooted the screen wouldnt unlock with a swipe any more so I factory restored it now can not press next at the start,can I go back to old firmware?stock rom for rogers instead of telus?and how?or any other ideas?thanks.
Click to expand...
Click to collapse
Why buy a **** touchscreen ? -.-
??Thank Me Up If I Helped You ??
also dont know if the previous owner had rooted,he said it was only 3mnths old
If you updated to the official kk which would be NE5 and this would be the most likely cause of the touchscreen not responding as phones with still the original screens has not responded after the NE5 update on other i527m mega..so your screen is not at fault.
Samsung should have tested the new kk update better before releasing the update.
Sent from my SGH-I527M using XDA Free mobile app
[email protected] said:
Ok bought a telus mega SGH-I527M with a broken screen,bought a screen on ebay (seller swears it is origional)but I think he is lieing as it has a black back to it instead of my beige origional screen and doesnt even have the numbers sticker on it,but anyhow worked great for an evening and I unlocked useing a code for rogers,it downloaded an update on its own and asked me if I wanted to install,so I did the update and when it rebooted the screen wouldnt unlock with a swipe any more so I factory restored it now can not press next at the start,can I go back to old firmware?stock rom for rogers instead of telus?and how?or any other ideas?thanks.
Click to expand...
Click to collapse
Try flashing this rom from my post here and see if it will help you out and you must unpack it first and then flash with odin..and i believe this rom was made with the rogers rom, but if you did receive the new KK NE5 update then this will not likely work, but it will not harm the phone..worth a try as i use this rom in certain situations also to get back and it works great.
starmaster10 said:
Try flashing this rom from my post here and see if it will help you out and you must unpack it first and then flash with odin..and i believe this rom was made with the rogers rom, but if you did receive the new KK NE5 update then this will not likely work, but it will not harm the phone..worth a try as i use this rom in certain situations also to get back and it works great.
Click to expand...
Click to collapse
couldnt go to your link,browser said forbidden?
can I root this?or custom rom?any way to be useable again?thanks(also I am new to all of this so a guide would be good)
found this?
If the downgrade was from the leaked 4.4.2,then this is probably because this repackaged and leaked firmware did not have a locked bootloader.
The officially released India 4.4.2 may cause more problems with downgrading - but we will have to wait and see if it contains a locked bootloader.
I didn't downgrade from leaked 4.4.2... My downgrade from official 4.4.2 DBT was also successfully in spite of new BL. I mean, didn't change BL with downgrade, just the firmware via Odin. And luckily the new BL from 4.4.2 works fine with firmware 4.1.2... that's what I wanted to inform about, because many think that it will not work, but it does! (At least in 3 oder 4 cases with german firmware.)
There is always a risk, yes, but maybe, somebody doesn't like 4.4.2 just as me and needs an idea to go back without root, so that's the answer I want to give.
[email protected] said:
couldnt go to your link,browser said forbidden?
can I root this?or custom rom?any way to be useable again?thanks(also I am new to all of this so a guide would be good)
Click to expand...
Click to collapse
Ooops..sorry about the link as somehow it was set to private, i have now corrected it and will put link here also
ROOT_JDQ39.I527MVLUBNA3.tar
And check my post here as it will help you in the flashing using odin and all .tar files are flashed this way, the only difference when flashing a recovery is you uncheck the reboot box and with other .tar files for roms etc. you check that reboot box, but everytime odin is restarted the reboot box will be checked already..let me know how this all goes with that rom above that i put a link to and the other stuff as all the custom roms in this mega section by @Silesh.Nair can be flashed and these are all the custom roms i tested so far that work on the i527m mega, but they all work even the newer ones and the custom roms i tried can be seen in this thread
starmaster10 said:
Ooops..sorry about the link as somehow it was set to private, i have now corrected it and will put link here also
ROOT_JDQ39.I527MVLUBNA3.tar
And check my post here as it will help you in the flashing using odin and all .tar files are flashed this way, the only difference when flashing a recovery is you uncheck the reboot box and with other .tar files for roms etc. you check that reboot box, but everytime odin is restarted the reboot box will be checked already..let me know how this all goes with that rom above that i put a link to and the other stuff as all the custom roms in this mega section by @Silesh.Nair can be flashed and these are all the custom roms i tested so far that work on the i527m mega, but they all work even the newer ones and the custom roms i tried can be seen in this thread
Click to expand...
Click to collapse
thank you verry much for the help,will try that and the link is good!!!!!
now seem to be stuck at the samsung flashing screen with no start?
[email protected] said:
now seem to be stuck at the samsung flashing screen with no start?
Click to expand...
Click to collapse
ok did a restore and on 2.2 now,thw screen is working again but have no sound no wi-fi and no rogers network?
?
[email protected] said:
ok did a restore and on 2.2 now,thw screen is working again but have no sound no wi-fi and no rogers network?
?
Click to expand...
Click to collapse
also no bluetooth,ran the supersu on phone and it said that it disabled knox?so rooted I think,wouldnt mind a custom rom that is stable but with all the crap samsung puts in removed,also it was koodo and still has koodo apps would like a rogers 16gb version and thanks for your help earlier.
i have this same problem with my i9200 idk what to do
[email protected] said:
also no bluetooth,ran the supersu on phone and it said that it disabled knox?so rooted I think,wouldnt mind a custom rom that is stable but with all the crap samsung puts in removed,also it was koodo and still has koodo apps would like a rogers 16gb version and thanks for your help earlier.
Click to expand...
Click to collapse
I cant get into the mode where I can use the sdcard anymore,says could not do normal boot?still works with odin but dont know what to try next?thanks.
ok,can boot from sd now useing phils recovery and flashed CM11 but still have no wi-fi or sound or bluetooth?Knox?
Related
Hello!
After flashing many custom ROMs and leaks my phone was acting a little funky, so I decided to go back to factory stock. I fired up kies on my pc and went to "Emergency recovery" It asked me for my serial number (I thought this was for getting the right stock firmware) After everything was done the phone booted up normally but I ended up with a "La'Fleur" boot logo
All I wanted was my stock firmware (Without having to look for the firmware, modem,etc myself) I though kies would do a better job than me :silly:
Sigh...
Any of you experienced this before?
Same problem here
Dont know how this happens...
Sent from my GT-I9300 using Tapatalk
Kies gives you the firmware that matches your serial number. So, your phone originally has this firmware, or an earlier version of it, i.e. your phone was branded.
If you don't like it get the latest unbranded firmware for your region from sammobile.com and flash with odin.
wangdaning said:
Kies gives you the firmware that matches your serial number. So, your phone originally has this firmware, or an earlier version of it, i.e. your phone was branded.
If you don't like it get the latest unbranded firmware for your region from sammobile.com and flash with odin.
Click to expand...
Click to collapse
Well it's suposed to work like that... but my phone is the plain gray international version. That's why it's so funny to me. I created this thread to see if some other people were having this issue as well and it seems so.
Anyway, it worked for me because it restored the stock modem and cleaned the whole nand. As soon as I saw that "La'Fleur" logo, I wiped it and threw CM 10.1 at it. Working great so far.
My point is, Samsung should do better (as usual, with everything) at keeping their records.
Well, none of us know what happend. Could be the carrier originally planned to carry this model, bought it from Samsung, and later changed their mind and sold it to a third party.
Nothing to show Samsung's records are wrong.
Sent from my GT-I9300 using xda app-developers app
wangdaning said:
Well, none of us know what happend. Could be the carrier originally planned to carry this model, bought it from Samsung, and later changed their mind and sold it to a third party.
Nothing to show Samsung's records are wrong.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Well, I bought mine at a retail store, unlocked and without any carrier bloatware. Just to point out "La'Fleur" is a special edition of galaxy devices featuring a special 'floral' design paint coat, that Samsung released for valentines; with ROM customization to match the design. As with mine being the plain grey version and using the 'official' method to get the stock ROM, I think I'm pretty safe to say that there's something wrong going somewhere at Samsung.
This is exactly what I was trying to avoid downloading the firmware, modem, etc and flashing it myself, getting something different than the one that came when I first took it out of the box... And this is exactly what I got using Samsung's method. LOL :laugh:
Kudos at Samsung! /s
Zealhybrid said:
Well, I bought mine at a retail store, unlocked and without any carrier bloatware. Just to point out "La'Fleur" is a special edition of galaxy devices featuring a special 'floral' design paint coat, that Samsung released for valentines; with ROM customization to match the design. As with mine being the plain grey version and using the 'official' method to get the stock ROM, I think I'm pretty safe to say that there's something wrong going somewhere at Samsung.
This is exactly what I was trying to avoid downloading the firmware, modem, etc and flashing it myself, getting something different than the one that came when I first took it out of the box... And this is exactly what I got using Samsung's method. LOL :laugh:
Kudos at Samsung! /s
Click to expand...
Click to collapse
Ah, got it. Still, never know where the mix up came from, but I am more clear about your issue.
Zealhybrid said:
Well, I bought mine at a retail store, unlocked and without any carrier bloatware. Just to point out "La'Fleur" is a special edition of galaxy devices featuring a special 'floral' design paint coat, that Samsung released for valentines; with ROM customization to match the design. As with mine being the plain grey version and using the 'official' method to get the stock ROM, I think I'm pretty safe to say that there's something wrong going somewhere at Samsung.
This is exactly what I was trying to avoid downloading the firmware, modem, etc and flashing it myself, getting something different than the one that came when I first took it out of the box... And this is exactly what I got using Samsung's method. LOL :laugh:
Kudos at Samsung! /s
Click to expand...
Click to collapse
Also Got the plain Grey version...
And Also Got lafleur firmware after kies recover
Sent from my GT-I9300 using Tapatalk
After flashing is the answer .
The hdswver codes that are presented to Kies match that firmware release and that's what you get .
http://forum.xda-developers.com/showthread.php?t=1978840
jje
same problem, what is the fix?
dli7319 said:
same problem, what is the fix?
Click to expand...
Click to collapse
Find the correct ROM on sammobile.com and flash it yourself using Odin.
There are guides here (In General) to help with this
rootSU said:
Find the correct ROM on sammobile.com and flash it yourself using Odin.
There are guides here (In General) to help with this
Click to expand...
Click to collapse
The problem is that, it is the same rom -.-
Edit: Oh, there are 2 different roms and lafleur is newer so kies selected that one, got it
flashed the other one and all is good
dli7319 said:
The problem is that, it is the same rom -.-
Click to expand...
Click to collapse
Find an unbranded ROM for your region on sammobile.com and flash it yourself using Odin.
There are guides here (In General) to help with this
EDIT> You don't even have a regional version?! Flash ANY unbranded ROM
got la flour too... but then instal custom room like imperium hd or other, my imei is ruined... problems in modem but nothing helps... cyanogen works...
xenixas said:
got la flour too... but then instal custom room like imperium hd or other, my imei is ruined... problems in modem but nothing helps... cyanogen works...
Click to expand...
Click to collapse
I got that too. Before you do anything to your phone, make sure yo do a Nandroid backup, also make a backup for your EFS partition as there is where your IMEI and radio paramaters are stored.
I had to send my phone to Samsung, and they replaced the motherboard.
Sorry to hear this happened to you
Zealhybrid said:
I got that too. Before you do anything to your phone, make sure yo do a Nandroid backup, also make a backup for your EFS partition as there is where your IMEI and radio paramaters are stored.
I had to send my phone to Samsung, and they replaced the motherboard.
Sorry to hear this happened to you
Click to expand...
Click to collapse
but does no one knows hot to fix it I read about modem version its about EFS partition format like new one from samsung, its readable by samsung firmware but not custom rooms I'll tried to flash custom and I need to chose modem version witch could read EFS partinion. My phone originaly is SEB it's baltic, I have 4.1.1 XEO instaled no imei... kies updated to xeo 4.1.2 and now it says software is changed cant update lol somthing bad is going with samsung
On the same boat i9305
xenixas said:
but does no one knows hot to fix it I read about modem version its about EFS partition format like new one from samsung, its readable by samsung firmware but not custom rooms I'll tried to flash custom and I need to chose modem version witch could read EFS partinion. My phone originaly is SEB it's baltic, I have 4.1.1 XEO instaled no imei... kies updated to xeo 4.1.2 and now it says software is changed cant update lol somthing bad is going with samsung
Click to expand...
Click to collapse
Sad to learn that I am not the only one. Mine is i9305, bought from Samsung's authorized retail shop, International edition grey. firmware changed to la fleur edition after emergency FW recovery. embarrassing to use it in front of others. Need to change lock screen. Has anyone tried to get help from Samsung? thanks
I know im stupid beacuse i cannot see the device in the forum where i choose to download the recovery now when i flash it, the device cant go through boot logo the Samsung Galaxy Mega and the screen turn to be screw up and black, i can still get to Download mode, i allready flash the stock and correct recovery for SGM but i cant get through the recovery (flashed with odin). Please help me
FIX: Flashed Stock Firmware
Nottezio said:
I know im stupid beacuse i cannot see the device in the forum where i choose to download the recovery now when i flash it, the device cant go through boot logo the Samsung Galaxy Mega and the screen turn to be screw up and black, i can still get to Download mode, i allready flash the stock and correct recovery for SGM but i cant get through the recovery (flashed with odin). Please help me
Click to expand...
Click to collapse
You need to re flash the entire stock rom thru Odon to reconfigure the other partitions and framework. Go to live . Samsung updates or sammobile and download a stock rom to your pic then run it thru Odin... This should bring you back to life man. And make sure you get the proper rom as there is the i9205 lte and i9200 non lte. Good luck
Mega
megalomanic14 said:
You need to re flash the entire stock rom thru Odon to reconfigure the other partitions and framework. Go to live . Samsung updates or sammobile and download a stock rom to your pic then run it thru Odin... This should bring you back to life man. And make sure you get the proper rom as there is the i9205 lte and i9200 non lte. Good luck
Mega
Click to expand...
Click to collapse
Yeah man, i allready think for that earlier, now the file just finished downloading, and.... i dont know how to flash firmware with Odin, can you help me?
Nottezio said:
Yeah man, i allready think for that earlier, now the file just finished downloading, and.... i dont know how to flash firmware with Odin, can you help me?
Click to expand...
Click to collapse
Sure man...get your mega into download mode, open up Odin, connect the mega and Odin will show added in a colored box...Click on the pda slot, find the tar file you've finished downloading, let it process for a few minutes, then you'll see the file appear in the pda slot...and the scroll box on bottom left will stop initializing then just click start and let it do its thing....will take about 10 minutes total....you'll be back stock.
let me know if you need any help.
Mega
Hi..see if this post i made will help you out http://forum.xda-developers.com/showpost.php?p=48385485&postcount=2 and use the .tar.md5 or just .tar file in the PDA window of odin as mentioned by megalomanic14
megalomanic14 said:
Sure man...get your mega into download mode, open up Odin, connect the mega and Odin will show added in a colored box...Click on the pda slot, find the tar file you've finished downloading, let it process for a few minutes, then you'll see the file appear in the pda slot...and the scroll box on bottom left will stop initializing then just click start and let it do its thing....will take about 10 minutes total....you'll be back stock.
let me know if you need any help.
Mega
Click to expand...
Click to collapse
God damn it thanks it worked now my device showing Android Is Upgrading pop up, while my device unroot? I think now i should see every detail of .tar i download
Nottezio said:
God damn it thanks it worked now my device showing Android Is Upgrading pop up, while my device unroot? I think now i should see every detail of .tar i download
Click to expand...
Click to collapse
Sure man no problem...Def yes double check anything you ever flash on your phone, especially as some things are for the mega 5.8 or i9205 vs i9200...yes you'll be unrooted...just let it boot and get back running... then go over to mega development forum and look for the root and cwm for the mega...you'll run both the exact same way in pda slot on Odin. If you need any help flashing root or cwm just pm me. Glad you got her back upand running man.
Mega
megalomanic14 said:
Sure man no problem...Def yes double check anything you ever flash on your phone, especially as some things are for the mega 5.8 or i9205 vs i9200...yes you'll be unrooted...just let it boot and get back running... then go over to mega development forum and look for the root and cwm for the mega...you'll run both the exact same way in pda slot on Odin. If you need any help flashing root or cwm just pm me. Glad you got her back upand running man.
Mega
Click to expand...
Click to collapse
Now i have the latest firmware 4.2.2 that just posted in 2014 and i used the old root method which flashing rooted kernel, the question is this method work for latest fimware but still at 4.2.2, i tested the root method on October 08 2013 4.2.2 Firmware and it work does it work on 2014 4.2.2 firmware
Nottezio said:
Now i have the latest firmware 4.2.2 that just posted in 2014 and i used the old root method which flashing rooted kernel, the question is this method work for latest fimware but still at 4.2.2, i tested the root method on October 08 2013 4.2.2 Firmware and it work does it work on 2014 4.2.2 firmware
Click to expand...
Click to collapse
All the mega firmwares are 4.2.2...go into settings, scroll down to about phone and send me the build number of your mega...i can tell you if it's ml1 then no they do not work, but i have developed a method of getting you back to stock rooted mj2 if so...send me that build number and well go from there.
Mega
megalomanic14 said:
All the mega firmwares are 4.2.2...go into settings, scroll down to about phone and send me the build number of your mega...i can tell you if it's ml1 then no they do not work, but i have developed a method of getting you back to stock rooted mj2 if so...send me that build number and well go from there.
Mega
Click to expand...
Click to collapse
JDQ39.I9152XWUAML3
GT-I9152 yeah SGM 5.8
do you have any suggested root method?
Nottezio said:
JDQ39.I9152XWUAML3
GT-I9152 yeah SGM 5.8
do you have any suggested root method?
Click to expand...
Click to collapse
Ahh is see...no as I have the mega i9205...you need to go to the development forum and look for one that's for thr i9152 specifically. The other issue is that if the latest rom for the 5.8 is anything like the newset 6.3 rom, where you see the knox 00 knox warranty flag ect in the boot screen and download mode, then there isnt a root for it yet due to the bootloader. Idk for your model as i dont have that mega...id highly suggest you go to the dev section thi and look around you shoukd be able to find out in there. Good luck and always double check everything before modding your mega man.
If you need any other help just hit me up and I'll try and help you out.
Mega
---------- Post added at 04:42 AM ---------- Previous post was at 04:36 AM ----------
http://forhttp://forum.xda-develope...php?t=2329275QUOTE=megalomanic14;49296915]Ahh is see...no as I have the mega i9205...you need to go to the development forum and look for one that's for thr i9152 specifically. The other issue is that if the latest rom for the 5.8 is anything like the newset 6.3 rom, where you see the knox 00 knox warranty flag ect in the boot screen and download mode, then there isnt a root for it yet due to the bootloader. Idk for your model as i dont have that mega...id highly suggest you go to the dev section thi and look around you shoukd be able to find out in there. Good luck and always double check everything before modding your mega man.
If you need any other help just hit me up and I'll try and help you out.
Mega[/QUOTE]
Here's prolly your best bet...read thru this carefully an read the other posts by people, maybe someone has rooted that firmware.
good luck..
http://forum.xda-developers.com/showthread.php?t=2329275
Mega
megalomanic14 said:
Ahh is see...no as I have the mega i9205...you need to go to the development forum and look for one that's for thr i9152 specifically. The other issue is that if the latest rom for the 5.8 is anything like the newset 6.3 rom, where you see the knox 00 knox warranty flag ect in the boot screen and download mode, then there isnt a root for it yet due to the bootloader. Idk for your model as i dont have that mega...id highly suggest you go to the dev section thi and look around you shoukd be able to find out in there. Good luck and always double check everything before modding your mega man.
If you need any other help just hit me up and I'll try and help you out.
Mega
---------- Post added at 04:42 AM ---------- Previous post was at 04:36 AM ----------
http://forhttp://forum.xda-develope...php?t=2329275QUOTE=megalomanic14;49296915]Ahh is see...no as I have the mega i9205...you need to go to the development forum and look for one that's for thr i9152 specifically. The other issue is that if the latest rom for the 5.8 is anything like the newset 6.3 rom, where you see the knox 00 knox warranty flag ect in the boot screen and download mode, then there isnt a root for it yet due to the bootloader. Idk for your model as i dont have that mega...id highly suggest you go to the dev section thi and look around you shoukd be able to find out in there. Good luck and always double check everything before modding your mega man.
If you need any other help just hit me up and I'll try and help you out.
Mega
Click to expand...
Click to collapse
umm, when we gets KitKat update (maybe) do i need to find root method for 4.4 or i can still use old method? which is flashing kernel?
I'm planing not to root until get KitKat which 'they' say will coming soon on feb (?)
Nottezio said:
Here's prolly your best bet...read thru this carefully an read the other posts by people, maybe someone has rooted that firmware.
good luck..
http://forum.xda-developers.com/showthread.php?t=2329275
Mega
Click to expand...
Click to collapse
umm, when we gets KitKat update (maybe) do i need to find root method for 4.4 or i can still use old method? which is flashing kernel?
I'm planing not to root until get KitKat which 'they' say will coming soon on feb (?)[/QUOTE]
Just a word of advice...don't listen to "theys" about updates, because no body ever knows anything until an updates on their device. Lol. But yes you'll almost definitely need a new root pack for 4.3 or 4.4 whatever comes first. But the downside is that it would seem that Knox and selinux will be included in all future updates, so while root may be possible once Knox kernel fuse and Knox warranty flash are included in new bootloader, it complicates things dramatically. You may want to look into reverting to an older build of 4.2.2 if possible or a custom rom vs waiting for an update that may or may not come.
Mega
Well I think my sgm allready factory unlocked
Sent from my GT-I9152 using xda app-developers app
Hello xda people,
i have the galaxy mega gt-i9200 with 4.2.2 software (no knox included)
ive tried every 4.4.2 kitkat update firmware from sammobile and everytime i end up with the same result.
Problem is when i flash the firmware , it boots up and my touchscreen and softkeys are disbaled/dont work.
i have no clue what the problem is, custom roms seem to work, and 4.2.2 official stock works.
can someone help me out? please.
Ntech02 said:
Hello xda people,
i have the galaxy mega gt-i9200 with 4.2.2 software (no knox included)
ive tried every 4.4.2 kitkat update firmware from sammobile and everytime i end up with the same result.
Problem is when i flash the firmware , it boots up and my touchscreen and softkeys are disbaled/dont work.
i have no clue what the problem is, custom roms seem to work, and 4.2.2 official stock works.
can someone help me out? please.
Click to expand...
Click to collapse
Maybe nobody has had this same issue. JIMMBOB offered a suggestion in one of your other threads.
You have 3 different threads.....are they 3 different problems. I only ask cause they are worded differently.
When you flash, are you flashing clean?
I am trying to offer some assistance. It sounds as if your having same problem across the board. Just have to start with basic responses so dont get upset. Try to walk through your process of flashing. Maybe you missed something. We all can.
Folks are reading, again maybe others just havent come across this issue.
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
Ntech02 said:
Hello xda people,
i have the galaxy mega gt-i9200 with 4.2.2 software (no knox included)
ive tried every 4.4.2 kitkat update firmware from sammobile and everytime i end up with the same result.
Problem is when i flash the firmware , it boots up and my touchscreen and softkeys are disbaled/dont work.
i have no clue what the problem is, custom roms seem to work, and 4.2.2 official stock works.
can someone help me out? please.
Click to expand...
Click to collapse
Ntech02 said:
I flashed this stock rom here http://forum.xda-developers.com/showthread.php?p=53767196 for my GT-i9200 Mega
coming from silentnight's flashable stock rom & another time from C-ROM 4.4.3,
each time i flash the stock rom (http://forum.xda-developers.com/showthread.php?p=53767196) it completes, reboots just fine, and when it starts up my screen doesnt respond anymore ive tried factory resets and full wipes & reflashed multiple times, idk what to do to make it work.
i can still go back to custom roms and my screen works fine on those. ive even tried going to 4.2.2 official stock but that doesnt work either.
someone please help =(
Click to expand...
Click to collapse
Ntech02 said:
Hello xda,
ive been having an issue for sometime but idk what it is,
when i boot my phone i cant see the logo that says "GALAXY MEGA i9200" it just stays black until the samsung boot animation appears.
in addition i cant see the DOWNLOAD mode screen either, although i can still enter download mode by using the button combination or just hitting reboot to DOWNLOAD mode.
does anybody know how to fix this?
Click to expand...
Click to collapse
Ntech02 said:
i have asked multiple times and im getting no response which is why i took my question here. if u werent gonna help me figure out something u didnt have to reply. and i can say its a stock rom because thats what it is. Stock Russian 4.4.2 kitkat Update for the GT-I9200. the only thing is this developer removed knox & the recovery. ive tried both versions of the rom and ended in the same result.
Click to expand...
Click to collapse
@Ntech02
Are you sure you are flashing the correct Official Firmware? I show many but you stated Russian above so I show two for your phone on KitKat. Also, if you were not made aware or didn't read up on the forums, once you upgrade to the "NE4 Bootloader" (Or KITKAT) and above you can not revert back to the previous ( JellyBean ) "Bootloaders". If you manage to flash back to them you will more than likely brick your phone.
Flashing a Custom Rom via Custom Recovery being from NF2, NE4, NA2, and MJ2 Roms for your Mega is still okay. Just remember not to Flash/Odin the Official Firmware from prior NE4 as the Firmwares include the Bootloader in them that one can not downgrade to.
All except for one of these Official Firmware is Flashable via Kies as well:
GT-I9200 Ukraine (Kyivstar)......2014 June ........4.4.2 ........I9200XXUDNF1 ........I9200OXEDNF1
GT-I9200 Kazakhstan...............2014 June ........4.4.2 ........I9200XXUDNF1 ........I9200OXEDNF1
GT-I9200 Uzbekistan ...............2014 June ........4.4.2 ........I9200XXUDNF1 ........I9200OXEDNF1
GT-I9200 Russia .....................2014 June ........4.4.2 ........I9200XXUDNF1 ........I9200SERDNF2
GT-I9200 Brazil .......................2014 June ........4.4.2 ........I9200UBUDNE2 ........I9200ZTODNE2
GT-I9200 Russia .....................2014 May .........4.4.2 ........I9200XXUDNE4 ........I9200SERDNE4
I know it has been mentioned / suggested before in other sections of the forum but updating your profile to reflect at least the Country and a Carrier for your phone would be helpful to provide some assistance.
captemo said:
Maybe nobody has had this same issue. JIMMBOB offered a suggestion in one of your other threads.
You have 3 different threads.....are they 3 different problems. I only ask cause they are worded differently.
When you flash, are you flashing clean?
I am trying to offer some assistance. It sounds as if your having same problem across the board. Just have to start with basic responses so dont get upset. Try to walk through your process of flashing. Maybe you missed something. We all can.
Folks are reading, again maybe others just havent come across this issue.
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
Click to expand...
Click to collapse
Yes i understand i have 3 threads but someone could've at least attempted to help me out like you & dark angle is doing now, so i thank you guys for taking the time to reply.
its the same issue regarding the screen, im not gonna get upset with u lol
but ive followed all the instructions correctly, and yes ive flashed clean.
im on philz cwm recovery as it is.
i would erase my data b4 installing the kitkat stock update.
used odin3 3.09 & 3.04
the firmware flashes fine.
it boots up like its supposed to, but the screen is just unresponsive .
ive done factory resets from stock recovery
ive even left it on over night to see if maybe something didnt load. but nothing works maybe its a driver issue?
DarkAngel said:
@Ntech02
Are you sure you are flashing the correct Official Firmware? I show many but you stated Russian above so I show two for your phone on KitKat. Also, if you were not made aware or didn't read up on the forums, once you upgrade to the "NE4 Bootloader" (Or KITKAT) and above you can not revert back to the previous ( JellyBean ) "Bootloaders". If you manage to flash back to them you will more than likely brick your phone.
Flashing a Custom Rom via Custom Recovery being from NF2, NE4, NA2, and MJ2 Roms for your Mega is still okay. Just remember not to Flash/Odin the Official Firmware from prior NE4 as the Firmwares include the Bootloader in them that one can not downgrade to.
All except for one of these Official Firmware is Flashable via Kies as well:
GT-I9200 Ukraine (Kyivstar)......2014 June ........4.4.2 ........I9200XXUDNF1 ........I9200OXEDNF1
GT-I9200 Kazakhstan...............2014 June ........4.4.2 ........I9200XXUDNF1 ........I9200OXEDNF1
GT-I9200 Uzbekistan ...............2014 June ........4.4.2 ........I9200XXUDNF1 ........I9200OXEDNF1
GT-I9200 Russia .....................2014 June ........4.4.2 ........I9200XXUDNF1 ........I9200SERDNF2
GT-I9200 Brazil .......................2014 June ........4.4.2 ........I9200UBUDNE2 ........I9200ZTODNE2
GT-I9200 Russia .....................2014 May .........4.4.2 ........I9200XXUDNE4 ........I9200SERDNE4
I know it has been mentioned / suggested before in other sections of the forum but updating your profile to reflect at least the Country and a Carrier for your phone would be helpful to provide some assistance.
Click to expand...
Click to collapse
hey darkangel thank you both for trying to help me out,
my i9200 is unlocked and on tmobile, i am in the USA but my firmware is the Russian 4.2.2
i actually am on the NE4 (kitkat) bootloader but im still running Russian 4.2.2 jellybean,
i did a nandroid backup from Philz CWM recovery b4 i flashed the Russian official kitkat update
as stated above anything i tried just didnt work. the screen is unresponsive and so are the softkeys
so i just flashed philz recovery again and restored my jellybean stock which is how im still running on JB.
ive had no issues as far as bricking my phone im pretty savy when it comes to android i think im having a bad day lol
Ntech02 said:
hey darkangel thank you both for trying to help me out,
my i9200 is unlocked and on tmobile, i am in the USA but my firmware is the Russian 4.2.2
i actually am on the NE4 (kitkat) bootloader but im still running Russian 4.2.2 jellybean,
i did a nandroid backup from Philz CWM recovery b4 i flashed the Russian official kitkat update
as stated above anything i tried just didnt work. the screen is unresponsive and so are the softkeys
so i just flashed philz recovery again and restored my jellybean stock which is how im still running on JB.
ive had no issues as far as bricking my phone im pretty savy when it comes to android i think im having a bad day lol
Click to expand...
Click to collapse
This is more than likely going to sound like a stupid noob answer.
Did you buy your phone new or used?
I noticed when I was looking at buying a Mega with a broken screen, if you use a cheap replacement screen, you need to plug in the factory screen and boot and then plug in the aftermarket screen. I wonder if maybe you got it used and it was repaired and the stock OS is seeing as not being an OEM screen? Maybe Custom ROMs don't check these things?
@Ntech02 try flashing this rom via recovery http://forum.xda-developers.com/showthread.php?t=2608110
Sent from my GT-I9200 using XDA Premium 4 mobile app
nitromuscle said:
This is more than likely going to sound like a stupid noob answer.
Did you buy your phone new or used?
I noticed when I was looking at buying a Mega with a broken screen, if you use a cheap replacement screen, you need to plug in the factory screen and boot and then plug in the aftermarket screen. I wonder if maybe you got it used and it was repaired and the stock OS is seeing as not being an OEM screen? Maybe Custom ROMs don't check these things?
Click to expand...
Click to collapse
I Bought it New from NewEgg.com but the screen did break b4, and i bought a replacement 70$ screen and fixed it myself, idk if thats cheap but thats how much they typically cost on amazon.com . all custom roms work, and the 4.2.2 jelly bean official software works fine.
you maybe right about the OEM screen
alexischino said:
@Ntech02 try flashing this rom via recovery http://forum.xda-developers.com/showthread.php?t=2608110
Sent from my GT-I9200 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
is this kitkat?
@Ntech02 No is jellybean 4.2.2 but if you are on kitkat you can flash this rom via recovery i'm using the russia 4.4.2 kk and i have flash the v10 and the v11 you can use them to go back to jellybean.
Sent from my GT-I9200 using XDA Premium 4 mobile app
alexischino said:
@Ntech02 No is jellybean 4.2.2 but if you are on kitkat you can flash this rom via recovery i'm using the russia 4.4.2 kk and i have flash the v10 and the v11 you can use them to go back to jellybean.
Sent from my GT-I9200 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
ohhh no no no lol ive been saying all along that im already on JB 4.2.2 official stock.
im still on the kitkat boot loader though.
You should be fine running JB on kitkat bootloader as long as you do not try and Odin a firmware with the JB bootloader and try to go back to the 4.2.2 bootloader. It will not let you go back to it. Flashing ROM's for your phone is all good as long as you do not touch the bootloader.
But if you really want to have KitKat then you need to try and reflash one of the KitKat official Firmwares I had mentioned above for your phone. You can only flash Firmwares via Odin from KitKat and above now because of the KitKat Bootloader.
i have been trying all day to unlock this phone. on a website, i saw that the best way to unlock a Galaxy Mega was to flash an unlocked rom via ODIN, but that seems to be my problem. i found one, flashed it, and then i had the logo, and then nothing, only black. then, i looked furthermore and found the reason why i have that is that i flashed the wrong rom.
my cellphone was bought from Bell, so its BMC! i flashed the BMC rom, and now, i have :
Image size too large ! ! W:1080, H:1920
display image fail
SECURE FAIL: Kernel
plz help, fast!
st-ban said:
i have been trying all day to unlock this phone. on a website, i saw that the best way to unlock a Galaxy Mega was to flash an unlocked rom via ODIN, but that seems to be my problem. i found one, flashed it, and then i had the logo, and then nothing, only black. then, i looked furthermore and found the reason why i have that is that i flashed the wrong rom.
my cellphone was bought from Bell, so its BMC! i flashed the BMC rom, and now, i have :
Image size too large ! ! W:1080, H:1920
display image fail
SECURE FAIL: Kernel
plz help, fast!
Click to expand...
Click to collapse
The same thing happened to me and a bunch of other people. You have to flash the pit file and modem/tz file from this thread with Odin. The files are posted on page 24. Then you can install a custom ROM like Beanstalk. It runs perfectly on my Mega.
http://forum.xda-developers.com/showthread.php?t=2461203&page=24
I give you a tip...
Next time buy a normal unlocked model and not form a carrier like att or whatever
The i9205 in europe works 100% no problems man.
Only fact is that the galaxy mega is so bad supported by custom roms...
Sent from my GT-I9205 using XDA Free mobile app
st-ban said:
i have been trying all day to unlock this phone. on a website, i saw that the best way to unlock a Galaxy Mega was to flash an unlocked rom via ODIN, but that seems to be my problem. i found one, flashed it, and then i had the logo, and then nothing, only black. then, i looked furthermore and found the reason why i have that is that i flashed the wrong rom.
my cellphone was bought from Bell, so its BMC! i flashed the BMC rom, and now, i have :
Image size too large ! ! W:1080, H:1920
display image fail
SECURE FAIL: Kernel
plz help, fast!
Click to expand...
Click to collapse
Hi..check my post here and download the ROOT_JDQ39.I527MVLUBNA3.tar rom which is rooted already and is a rogers rom and is a NA3 based rom which i believe your phone is on now, but it will still work as if you are on bell just remove any rogers stuff from the rom which is only a couple of items anyway and you should be up and running again..make sure to unpack the file first after you have downloaded it to get the .tar file inside and then just flash with odin.
See if this rom will help you out as it should i believe. :good:
lets try starmaster10's now....
starmaster10 said:
Hi..check my post here and download the ROOT_JDQ39.I527MVLUBNA3.tar rom which is rooted already and is a rogers rom and is a NA3 based rom which i believe your phone is on now, but it will still work as if you are on bell just remove any rogers stuff from the rom which is only a couple of items anyway and you should be up and running again..make sure to unpack the file first after you have downloaded it to get the .tar file inside and then just flash with odin.
See if this rom will help you out as it should i believe. :good:
Click to expand...
Click to collapse
Thanks, Dave_N. Your steps removed the SECURE FAIL KERNEL error. Now, I can use the cellphone regular recovery. Then I install CWM, and then I tried to install BeanStalk, but it froze a few seconds after. Same thing with CW11. So I redid your steps again, and got the original recovery, without CWM. Now, ill try starmaster10's.
I'll keep you posted...
starmaster10 said:
Hi..check my post here and download the ROOT_JDQ39.I527MVLUBNA3.tar rom which is rooted already and is a rogers rom and is a NA3 based rom which i believe your phone is on now, but it will still work as if you are on bell just remove any rogers stuff from the rom which is only a couple of items anyway and you should be up and running again..make sure to unpack the file first after you have downloaded it to get the .tar file inside and then just flash with odin.
See if this rom will help you out as it should i believe. :good:
Click to expand...
Click to collapse
OK, so i tried your pack, it worked, i can turn the phone ON now...
I just cant turn Wi-Fi on, and my gf's Rogers simcard does not work either.......
st-ban said:
OK, so i tried your pack, it worked, i can turn the phone ON now...
I just cant turn Wi-Fi on, and my gf's Rogers simcard does not work either.......
Click to expand...
Click to collapse
Can you let me know what your baseband version is it is in settings>more tab>about device and the baseband version should be near the botton..maybe about 4 up from the bottom of the page.
Sent from my SGH-I527M using XDA Free mobile app
UNKNOWN???
starmaster10 said:
Can you let me know what your baseband version is it is in settings>more tab>about device and the baseband version should be near the botton..maybe about 4 up from the bottom of the page.
Sent from my SGH-I527M using XDA Free mobile app
Click to expand...
Click to collapse
'unknown'..... it literally says 'unknown'
i have :
Kernel version :
3.4.0-2416192
[email protected] -06 #1
Thu Jan 9 22:39:55
Build number :
JD139.I527MVLUBNA3
SE for Android status :
Enforcing
Secure boot status :
Type : Samsung
st-ban said:
'unknown'..... it literally says 'unknown'
i have :
Kernel version :
3.4.0-2416192
[email protected] -06 #1
Thu Jan 9 22:39:55
Build number :
JD139.I527MVLUBNA3
SE for Android status :
Enforcing
Secure boot status :
Type : Samsung
Click to expand...
Click to collapse
You mean your baseband version says unknown actually as this could indicate that you might have updated to the newer kitkit rom which would be NE5 at the end of the baseband version..is this baseband you posted was it at NA3 before flashing..as we just need the last 3 characters from the baseband version like NA3 or NE5 or the original firmware would have been MH1...let me know if you basevand is showing unknown at this time now.
Sent from my SGH-I527M using XDA Free mobile app
hmmmmm.....
starmaster10 said:
You mean your baseband version says unknown actually as this could indicate that you might have updated to the newer kitkit rom which would be NE5 at the end of the baseband version..is this baseband you posted was it at NA3 before flashing..as we just need the last 3 characters from the baseband version like NA3 or NE5 or the original firmware would have been MH1...let me know if you basevand is showing unknown at this time now.
Sent from my SGH-I527M using XDA Free mobile app
Click to expand...
Click to collapse
it says Baseband version : UNKNOWN.
---
in the meantime, i used Kies / Tools / Firmware upgrade and initialization, i entered my phone model (SGH-I527M) and my serial number and this is what I have :
Initialized version : PDA:NE5 / PHONE:NE5 / CSC:NE5 (BMC)
st-ban said:
it says Baseband version : UNKNOWN.
---
in the meantime, i used Kies / Tools / Firmware upgrade and initialization, i entered my phone model (SGH-I527M) and my serial number and this is what I have :
Initialized version : PDA:NE5 / PHONE:NE5 / CSC:NE5 (BMC)
Click to expand...
Click to collapse
Then this means that the phone must of had a OTA update to NE5 which is the newer kitkat and once you update to this you cannot go back to NA3 based rom or the MH1 based rom due to knox security has locked the bootloader from letting a person going back..if you can get kies ti work to put the NE5 based rom onto your ohone then it will operate normally again..the rom I gave you a link to will not work then it will boot the phone and all..but there is no network..wifi..and sound..I am trying at this time to get a NE5 dump of the system files but I am having problems with that at this time..if kies will not fix it then there is no fix at this time.
Sorry that I cannot help in this situation further as I cannot even update to the NE5 KK rom as my device status is custom and I cannot get it to officiak due to this knox crap..sorry about this..but I will keep looking to get this NE5 system dump files so I can make a flashable odin file out of them to help in this situation that quite a few people are in.
Sent from my SGH-I527M using XDA Free mobile app
actually to be precize... this is what i found out and tested on my s3mini... i had it rooted and official stock and there was an update avialable for it trough odin and ota, in that time i had a virus on the pc i use (oops downloaded the first stupid link for odin 3.09) so i got stuck, and then i was tbinking something. i searched for the official stock recovery from samsung and downloaded it for my device and then i got into SuperSU and completly removed root. when done i got into my current recovery and flashed the stock recovery amd after that my system said it was official and was able to pull it ota
i dont know if it helps you just wanted to mention and share. you may not find a stock recovery so maybe pull it out of somewhere like the official firmware and download and then pull it out with a root file explorer.
Sent from my GT-I9205 using XDA Free mobile app
I have tried that also..I had it to official status in both spots on the download page but that know warranty would always stay at 0xffffffff or something like and it still says my device is custom and you cannot get any updates and then I get that image size to big thing .but as soon as I get it to like 0x1 it works but I cannot get the update and there is no update for the kk on my carrier which is sasktel..been doing this stuff for quite a while but this newer kitkat update is sure throwing a monkey wrench into things.
But thanks for the info.
Sent from my SGH-I527M using XDA Free mobile app
starmaster10 said:
I have tried that also..I had it to official status in both spots on the download page but that know warranty would always stay at 0xffffffff or something like and it still says my device is custom and you cannot get any updates and then I get that image size to big thing .but as soon as I get it to like 0x1 it works but I cannot get the update and there is no update for the kk on my carrier which is sasktel..been doing this stuff for quite a while but this newer kitkat update is sure throwing a monkey wrench into things.
But thanks for the info.
Sent from my SGH-I527M using XDA Free mobile app
Click to expand...
Click to collapse
Well dude your not the only guy with problems... Guys that have a metro pcs galaxy mega cant get kitkat either.... Should have not buyed from a carrier buddy .
Im happy that i got one from europe
Sent from my GT-I9205 using XDA Free mobile app
its the peanut said:
Well dude your not the only guy with problems... Guys that have a metro pcs galaxy mega cant get kitkat either.... Should have not buyed from a carrier buddy .
Im happy that i got one from europe
Sent from my GT-I9205 using XDA Free mobile app
Click to expand...
Click to collapse
No problem on that part as i do not really want the kk update as i just wanted it to get a system image out of it and make it odin flashable..but the rooting would be the problem on the oifficial kk..but the custom rom here on the site i can use all of them for the mega 6.3 and still have kk that way.
starmaster10 said:
No problem on that part as i do not really want the kk update as i just wanted it to get a system image out of it and make it odin flashable..but the rooting would be the problem on the oifficial kk..but the custom rom here on the site i can use all of them for the mega 6.3 and still have kk that way.
Click to expand...
Click to collapse
Oops dont mind me i accidently posted on the from thread lol. I removed the comment.
In my attempts to root this device my boot was damaged. I can get into stock recovery and download mod but of course I can not find any roms including the stock for this device. Can someone PLEASE send me there boot.img. If you have the full stock rom for this model SM-G360T1, that would be awesome too. THX!
Boom Shocka Locka
Jedijaded said:
In my attempts to root this device my boot was damaged. I can get into stock recovery and download mod but of course I can not find any roms including the stock for this device. Can someone PLEASE send me there boot.img. If you have the full stock rom for this model SM-G360T1, that would be awesome too. THX!
Click to expand...
Click to collapse
Ok so I should have more faith in myself. So by the end of my nightmare I messed up my boot AND my recovery and could only get into download mode. On a hunch I got ahold of the stock rom for the SM-G360T which is the T-Mobile version of this phone and being as they run on the same network(Same company now) the boot.img and recovery.img WORK ON THIS MODEL. Im back in my phone and everything is running perfect. So for those out there that know WAY more about making roots and roms you might be able to use this stock rom to finally root this monster. Or at least if you soft brick your device you can use these files to get back into your phone until we are able to get the stock rom for this phone. The link to the stock rom for the SM-G360T is below. Hope we get a root for this phone soon. THX!
Im a noob poster on Xda so I cant link it but just go to sammobile.com and search for SM-G360T and make sure you sign up and activate ur account its free you just have to do that or the download link is broke. Have fun.
Did you have to do any unlocking?
im currently downloading the tmobile sm-g360t image( i also have the metro sm-ge360t1) which i had soft bricked by flashing a root for the h* model. I just wanted to know after odin the tmobile imagine were you just able to pop in you're metro im and go? thanx
subun1t said:
im currently downloading the tmobile sm-g360t image( i also have the metro sm-ge360t1) which i had soft bricked by flashing a root for the h* model. I just wanted to know after odin the tmobile imagine were you just able to pop in you're metro im and go? thanx
Click to expand...
Click to collapse
Ya bro I did the extact same thing with the H root. Just put the boot.img in a tar and flash it like u did the H and it will fix it. You might get a security message after but u can just go to Kies and update back to stock if you dont mind losing all your data. Cheers.
The whole rom isn't tested
subun1t said:
im currently downloading the tmobile sm-g360t image( i also have the metro sm-ge360t1) which i had soft bricked by flashing a root for the h* model. I just wanted to know after odin the tmobile imagine were you just able to pop in you're metro im and go? thanx
Click to expand...
Click to collapse
I extracted just the boot.img and made my own tar to flash just the kernel, which was the problem. Flashing the whole rom isn't what you need to do in this case. Just make a mental note that you can you use the boot.img and recovery.img to get back into android.
Hello this is androidadmirer
i recently bought a samsung galaxy core prime from metro pcs
out of the box lolipop 5.1.1
i have an idea how to break this phone loose
but i need some input from you all to see if i'm wrong or if this is possible
so my plan is to use odin to flash the samsung core sm-360hu version firmware and they have a working twrp recovery
then make a rom with the t mobile firmware and insert su in bin and xbin (the t mobile firmware works perfect because it's the same network and same android 5.1.1 o.s
this sounds really good in theory but i don't know if i am totally right
can someone chime in on this please
any help will be very appriciated
Let me know
androidadmirer said:
Hello this is androidadmirer
i recently bought a samsung galaxy core prime from metro pcs
out of the box lolipop 5.1.1
i have an idea how to break this phone loose
but i need some input from you all to see if i'm wrong or if this is possible
so my plan is to use odin to flash the samsung core sm-360hu version firmware and they have a working twrp recovery
then make a rom with the t mobile firmware and insert su in bin and xbin (the t mobile firmware works perfect because it's the same network and same android 5.1.1 o.s
this sounds really good in theory but i don't know if i am totally right
can someone chime in on this please
any help will be very appriciated
Click to expand...
Click to collapse
Let me know if that custom recovery works if not u can use the sm-g360t (t-mobile) to get back though if I remember right the phone has to be rooted for twrp to work right not sure....also you should be able to get the stock rom from smart switch if you force the update that way you have the rom that was made for it as a base...I will try and get the rom and post it I was just checking and there is an update. Let me know
Jedijaded said:
Let me know if that custom recovery works if not u can use the sm-g360t (t-mobile) to get back though if I remember right the phone has to be rooted for twrp to work right not sure....also you should be able to get the stock rom from smart switch if you force the update that way you have the rom that was made for it as a base...I will try and get the rom and post it I was just checking and there is an update. Let me know
Click to expand...
Click to collapse
im gonna try and flash the galaxy grand prime rom and then use odin to flash a recovery on it because its only 4.4.4 so my thought was to flash the "downgraded 4.4.4" then flash the twrp and then make a rom from the t mobile odin firmware
where is the link? thanks
Jedijaded said:
Ok so I should have more faith in myself. So by the end of my nightmare I messed up my boot AND my recovery and could only get into download mode. On a hunch I got ahold of the stock rom for the SM-G360T which is the T-Mobile version of this phone and being as they run on the same network(Same company now) the boot.img and recovery.img WORK ON THIS MODEL. Im back in my phone and everything is running perfect. So for those out there that know WAY more about making roots and roms you might be able to use this stock rom to finally root this monster. Or at least if you soft brick your device you can use these files to get back into your phone until we are able to get the stock rom for this phone. The link to the stock rom for the SM-G360T is below. Hope we get a root for this phone soon. THX!
Im a noob poster on Xda so I cant link it but just go to sammobile.com and search for SM-G360T and make sure you sign up and activate ur account its free you just have to do that or the download link is broke. Have fun.
Click to expand...
Click to collapse
Hi. Can you post the link to download the firmware ? Thanks
SM-G360T1 "boot.img" And "recovery.img" Files
I just uploaded the "boot.img" and "recovery.img" from the latest stock update for the SM-G360T1 on this thread here if anyone needs it in the future.
http://forum.xda-developers.com/showpost.php?p=62457159&postcount=42
EDIT: Updated this post today with ODIN flashable boot and recovery files. Be sure to read the whole post before flashing. Thanks!
I tried the F, H, & "lte" versions firmware, still no positive results, I keep having to flash back to the stock boot.img and recovery.img that bogarty has just linked above.... we need to find a way to unlock this bootloader on this devicez firmware... TWRP seems so close to working.
Huh?
TEFjLONjDON said:
Ok so Unlocking the Phone for use on other carriers is not the same as unlocking the bootloader. thank fully our bootloader is not locked... But it is always a good idea to completely free your device.. SO
As long as you own your device out-right and it was purchased >90 days ago, then Metro cant say no.
This post is just for those that don't already know, (make sure you do this first before you flash a recovery or try a root method)
The Samsung Galaxy Core Prime comes locked from Metropcs by default. But after you buy it and its yours..
just call them @ (+1-888-8METRO8) or (1-888-863-8768)
1. Ask for tech support
2. Ask for the unlock code,
3. Tell them you leaving the carrier.. or the country.. and they will give you the unlock codes (plural 2 codes one for the Device and the other for the Sim card if you say your leaving the country).
4. Put in the code and your good to go..
PS... Its your device.. Bought and payed for...... They really can't say NO..........
Click to expand...
Click to collapse
Thx for the random post that has nothing to do with what we are talking about.
Something new to play with...
OK so i got a TWRP recovery to flash but when I get in there my screen is disable. Maybe you guys can play with it and see what u get here is the link
dl.twrp.me/coreprimelte/
P.S. Two more posts and I can post real links sry....lol
Happy rooting..* Root has been achieved for our device check it out herehttp://forum.xda-developers.com/showthread.php?p=62859013 on the other thread.
Sent from my SM-G900T using Tapatalk
Have you been checking the other posts? Root is here!
Anyone have a custom rom for this device yet?
Jedijaded said:
Thx for the random post that has nothing to do with what we are talking about.
Click to expand...
Click to collapse
so i did the root on my phone.... Can i still unlock my phone?
send from hdx 7 using tapatalk
I didnt found a way to unlock my sm-g360t1, i made the root and tryed several boxes that told me "device unlocked" but wasnt true. Have to pay 24 bucks online to whitelist imei and unlock it trought the device unlock app. I flashed the stock rom from sammobile before but maybe works with the rooted phone too. Problem solved for me
so i got the frp message. odin flashed stock recovery and boot now it gets stuck on the metro pcs screen..... FML can anyone help me fix this problem ?
I had to flash the stock from sammobile SM-G360T1 is what you have to search for then start over but make sure the oem unlock is switched to in that causes the frp (factory reset protection)
---------- Post added at 10:49 PM ---------- Previous post was at 10:36 PM ----------
Or just wait If I remember correctly it took my phone several minutes to boot after flashing stock
Sent from my SM-G360T1 using Tapatalk