Related
Hey guys i got a phone that wont boot up, the inital issue was there was no baseband, so i tired to flash via ODIN the stock image onto the phone, it fails at the modem part. I've looked through a few threads and i think the PIT file might help me; but i cannot for the life of me find the pit file. Does anyone have the Note 2 pit file they can share?
thanks
eric303 said:
Hey guys i got a phone that wont boot up, the inital issue was there was no baseband, so i tired to flash via ODIN the stock image onto the phone, it fails at the modem part. I've looked through a few threads and i think the PIT file might help me; but i cannot for the life of me find the pit file. Does anyone have the Note 2 pit file they can share?
thanks
Click to expand...
Click to collapse
Does the phone boot and if so have you rooted. Have you tried flashing the modem thru recovery. http://forum.xda-developers.com/showthread.php?t=1916936 I couldn't get link to go to page 1 sorry... This wont help you personally but maybe someone with some time (more than me) could make a .pit for you. If not ill look at it tomorrow
Sent from my SGH-T889 using Tapatalk 4 Beta
deeznutz1977 said:
Does the phone boot and if so have you rooted. Have you tried flashing the modem thru recovery. http://forum.xda-developers.com/showthread.php?t=1916936 I couldn't get link to go to page 1 sorry... This wont help you personally but maybe someone with some time (more than me) could make a .pit for you. If not ill look at it tomorrow
Sent from my SGH-T889 using Tapatalk 4 Beta
Click to expand...
Click to collapse
the phone does not boot, and i do not have root. I have not tried flashing the modem through recovery as i dont have a custom recovery on there or a modem.zip
Update - so i was able to get the phone to boot up, installed root and TWRP, installed the note 2 modem but still baseband unknown. From i can understand so far is that its a Tmobile note2, my idiot friend tried to flash the n7100 SW on it, now its showing unknown baseband/IMEI. Is there a fix for this?
truwrxtacy said:
the phone does not boot, and i do not have root. I have not tried flashing the modem through recovery as i dont have a custom recovery on there or a modem.zip
Update - so i was able to get the phone to boot up, installed root and TWRP, installed the note 2 modem but still baseband unknown. From i can understand so far is that its a Tmobile note2, my idiot friend tried to flash the n7100 SW on it, now its showing unknown baseband/IMEI. Is there a fix for this?
Click to expand...
Click to collapse
try to flash via recovery some modems and do factory reset
someone has a thread with all modems
What version of ODIN were you using? Some earlier versions have issues w/ the modem part of newer phones... just a thought.
dwitherell said:
What version of ODIN were you using? Some earlier versions have issues w/ the modem part of newer phones... just a thought.
Click to expand...
Click to collapse
Good point dwith , i use 3.07
How did you?
truwrxtacy said:
the phone does not boot, and i do not have root. I have not tried flashing the modem through recovery as i dont have a custom recovery on there or a modem.zip
Update - so i was able to get the phone to boot up, installed root and TWRP, installed the note 2 modem but still baseband unknown. From i can understand so far is that its a Tmobile note2, my idiot friend tried to flash the n7100 SW on it, now its showing unknown baseband/IMEI. Is there a fix for this?
Click to expand...
Click to collapse
I have exact same error, but also mine wont enter recovery mode, only download mode.
Kind to share how you recovered your phone ?
dannyogolo said:
I have exact same error, but also mine wont enter recovery mode, only download mode.
Kind to share how you recovered your phone ?
Click to expand...
Click to collapse
Have you tried Kies? That has been reported to work for recovering from Loss of imei and partitioning by at least one person around here.
Hastily spouted for your befuddlement
wrong post sorry
hi may i know how to find a pit file for my note2
deeznutz1977 said:
Does the phone boot and if so have you rooted. Have you tried flashing the modem thru recovery. http://forum.xda-developers.com/showthread.php?t=1916936 I couldn't get link to go to page 1 sorry... This wont help you personally but maybe someone with some time (more than me) could make a .pit for you. If not ill look at it tomorrow
Sent from my SGH-T889 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I have note 2 but how to find the pit file, mine is active note2 korean version
hi guys,
I have a galaxy s3, in Canada, and cannot flash the newest AOKP (aokp_d2att_ota-eng-task650_7.20.2013b), I downloaded the I747MVLDLK4_aio.tar.md5 file and flashed it with odin as per instructions, then did a format,cache wipe/dalvik wipe, then try and write the new ROM, and all i get is error 7! ive tried it a few times! All i can say is im sure glad i did a NAND backup before i tried.
i dont understand whats wrong? i wasnt sure if i did the bootloader file right, but i followed directions, i put the phone in write mode, opened odin, clicked PDA, chose the file, and it wrote fine.no errors or anything. is there something i maybe missed?
can someone help me out?
TIA,
GINNZ
Maybe check to see if you have the latest recovery installed
Sent from my SGH-I747 using xda premium
ginnz said:
hi guys,
I have a galaxy s3, in Canada, and cannot flash the newest AOKP (aokp_d2att_ota-eng-task650_7.20.2013b), I downloaded the I747MVLDLK4_aio.tar.md5 file and flashed it with odin as per instructions, then did a format,cache wipe/dalvik wipe, then try and write the new ROM, and all i get is error 7! ive tried it a few times! All i can say is im sure glad i did a NAND backup before i tried.
i dont understand whats wrong? i wasnt sure if i did the bootloader file right, but i followed directions, i put the phone in write mode, opened odin, clicked PDA, chose the file, and it wrote fine.no errors or anything. is there something i maybe missed?
can someone help me out?
TIA,
GINNZ
Click to expand...
Click to collapse
If you're in Canada chances are you're running the d2can recovery that the phone wants. You need to flash either the d2att recovery Odin from the twrp website or do a quick search for the latest tarp or cwm flashable zip files.
Status 7 can be
a) out of date bootloader
b) out of date recovery
or for Canadians
c) d2can recovery when the Roms are requiring d2att
Sent from my SGH-I747 using xda app-developers app
KorGuy123 said:
If you're in Canada chances are you're running the d2can recovery that the phone wants. You need to flash either the d2att recovery Odin from the twrp website or do a quick search for the latest tarp or cwm flashable zip files.
Status 7 can be
a) out of date bootloader
b) out of date recovery
or for Canadians
c) d2can recovery when the Roms are requiring d2att
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Ok, thanks, I had an older version of AOKP running, which was released in December or so, and the recovery flashed was "RecoveryGalaxyS3USCanada.tar", I thought the new I747M4LDLK4 file was all i needed to flash this newer rom?
What exactly do i need? Im sorry for so many questions, but this just isnt making sense to me.... I managed to root the phone initially last year, and havn't done anything with it since.
so what is the newer I747M4LDLK4 file that i flashed with Odin for? Is the recovery initially flashed not the right one? if not, which one is needed, and how do i flash it? Id imagine with Odin, if so, do i just flash it the same as the I747M4LDLK4 file (PDA)?
im almost there, i just need a small push in the right direction....
Thanks for all your help so far, and please bare with me. I was an Apple jailbreaker for years, so this stuff is pretty foreign to me still.
---edit---
ok, so i went to twrp and found 2 recovery's, one is "openrecovery-twrp-2.6.0.0-d2att.tar" and one is "openrecovery-twrp-2.6.0.0-d2can.tar", this is where im confused, should i flash the "d2att", or the "d2can"? I mean, im in Canada, on MTS, and flashed the I747M4LDLK4, which was meant for Canada already....
also, can someone please clarify what the I747M4LDLK4 file is? it clearly states that canadian users MUST flash this before flashing the new AOKP, as it wont wont flash without it.... I did that, and still get Error7, now im looking at a new "recovery" as well, as i hope this will fix my error 7 issue. No where in the massive AOKP thread did it say that a different recovery would be needed as well, only the new I747M4LDLK4_aio.tar.md5 file!
so, anyways, if i flash a new recovery, (all i need to know is which one at this point), then i should be able to flash the new (AOKP) rom? i really dont wanna brick this thing, and i wish there wasnt so much confusion with the d2att/d2can files. it would seem completely logical that i would need the d2can file, but who knows, .... there was some sort of error on my phone when i tried to flash the ROM last night and d2att was in it somewhere......
im assuming the I747M4LDLK4_aio.tar.md5 is the bootloader, if so, i have the most recent one flashed now, so i must be getting the error because my recovery is out of date? i think im almost there, all i need is to know which recovery to flash, and i should be golden! the original recovery that is on the phone now from my first AOKP flash is "RecoverygalaxyS3USCanada.tar"
Ginnz.
ginnz said:
Ok, thanks, I had an older version of AOKP running, which was released in December or so, and the recovery flashed was "RecoveryGalaxyS3USCanada.tar", I thought the new I747M4LDLK4 file was all i needed to flash this newer rom?
What exactly do i need? Im sorry for so many questions, but this just isnt making sense to me.... I managed to root the phone initially last year, and havn't done anything with it since.
so what is the newer I747M4LDLK4 file that i flashed with Odin for? Is the recovery initially flashed not the right one? if not, which one is needed, and how do i flash it? Id imagine with Odin, if so, do i just flash it the same as the I747M4LDLK4 file (PDA)?
im almost there, i just need a small push in the right direction....
Thanks for all your help so far, and please bare with me. I was an Apple jailbreaker for years, so this stuff is pretty foreign to me still.
---edit---
ok, so i went to twrp and found 2 recovery's, one is "openrecovery-twrp-2.6.0.0-d2att.tar" and one is "openrecovery-twrp-2.6.0.0-d2can.tar", this is where im confused, should i flash the "d2att", or the "d2can"? I mean, im in Canada, on MTS, and flashed the I747M4LDLK4, which was meant for Canada already....
also, can someone please clarify what the I747M4LDLK4 file is? it clearly states that canadian users MUST flash this before flashing the new AOKP, as it wont wont flash without it.... I did that, and still get Error7, now im looking at a new "recovery" as well, as i hope this will fix my error 7 issue. No where in the massive AOKP thread did it say that a different recovery would be needed as well, only the new I747M4LDLK4_aio.tar.md5 file!
so, anyways, if i flash a new recovery, (all i need to know is which one at this point), then i should be able to flash the new (AOKP) rom? i really dont wanna brick this thing, and i wish there wasnt so much confusion with the d2att/d2can files. it would seem completely logical that i would need the d2can file, but who knows, .... there was some sort of error on my phone when i tried to flash the ROM last night and d2att was in it somewhere......
im assuming the I747M4LDLK4_aio.tar.md5 is the bootloader, if so, i have the most recent one flashed now, so i must be getting the error because my recovery is out of date? i think im almost there, all i need is to know which recovery to flash, and i should be golden! the original recovery that is on the phone now from my first AOKP flash is "RecoverygalaxyS3USCanada.tar"
Ginnz.
Click to expand...
Click to collapse
Okay, first thing first. You are reading WAY TOO MUCH into this, You need to slow down and do some reading on what is what for your phone.
There is no confusion about d2can and d2att in here. Here it is as simple as I can explain.
You live in Canada (as do I) our phones are SGH-I747M when you install a custom recovery (Clockworkmod or TWRP) The phone is registered as a Canadian model. The developers on this forum build ROMS for d2att only. They just happen to work on our phones as they are identical. To be able to flash these ROMS on our Canadian phones you have to flash the d2att recovery (Clockworkmod or TWRP)
So my suggestion was to make sure you have flashed the d2att recovery to your phone. You can get the Odin files from the websites or a quick search here would get you the flashable .zip files you would flash in recovery like a ROM (no wiping needed though)
Anything on THIS FORUM ONLY will not brick your device. Anything labelled under anything outside this forum ie. i9300 (International S3) or the other carriers will cause harm to your phone and you'll be a sad panda.
I747M4LDLK4 is your bootloader.
What Is A Bootloader?
In literal terms, bootloader is code that is executed before any Operating System starts to run. The concept of bootloaders is universal to virtually all Operating systems that inculcates operating systems on your PC, laptop, smartphones, and other such devices. Bootloaders basically package the instructions to boot operating system kernel and most of them also have their own debugging or modification environment. As the bootloader kicks off before any piece of software on your device, it makes it extremely processor specific and every motherboard has it’s own bootloader. This is one reason that all Android phones have different Custom ROMS developed due to high variance of processing hardware present on the device.
Click to expand...
Click to collapse
If you were to flash a US bootloader on your phone you'll be a sad panda.
The newer ROMS are requiring an updated bootloader to work properly. The newest Canadian bootloader MF1 still won't work for most of these ROMS so don't update it that far.
I don't know what else to suggest.
There are 2 main reasons for status 7 (3 if you're on a Canadian carrier which you are)
@KorGuy123
Nice job on the explanations. Many Users (none of which are obviously in this section of course ) would see that he was running a version of Task's ROM from December and jumped all over him. Keep up the good work.
OP ~ KorGuy123's last post points out to what a Status 7 recovery error is. Most of the times Status 7's are mainly due to Recovery issues. Bootloader issues will usually throw a [getprop ro.bootloader] error instead of a Status 7 just for future reference.
KorGuy123 said:
If you're in Canada chances are you're running the d2can recovery that the phone wants. You need to flash either the d2att recovery Odin from the twrp website or do a quick search for the latest tarp or cwm flashable zip files.
Status 7 can be
a) out of date bootloader
b) out of date recovery
or for Canadians
c) d2can recovery when the Roms are requiring d2att
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Thanks for bearing with me guys!!! I got it. as was stated, i was overthinking the whole thing! i flashed a new recovery .d2att, and all went fine!
you guys are awesome!
ginnz.
ginnz said:
Thanks for bearing with me guys!!! I got it. as was stated, i was overthinking the whole thing! i flashed a new recovery .d2att, and all went fine!
you guys are awesome!
ginnz.
Click to expand...
Click to collapse
Glad it worked out for you. Enjoy!
Sent from my SGH-I747 using xda app-developers app
CWM flashable bootloader safety concern.
I have recently seen users here flashing bootloader with CWM, here is my just head up for safety concern of CWM flashble bootloader
Here is link to post by well known X-Note ROM developer @soloilmeglio regarding forcing bootloader with CWM
http://forum.xda-developers.com/showthread.php?t=2609561
even chances are less than a 1% it will be huge for terms of breaking device. We rarely rare seen any reported brick device by bad method of flashing on XDA.
Irrespective of this another concern is MD5 check. I strongly recommend to flash bootloader with MD5 check only. Once on CWM flashable format hardly any newbies doing md5 check before every flashing (even Philz have included built in). Any corrupted bootloader download flashing will high possibly end with brick. Bootloader best to be flashed with Odin with tar.md5 format so any corrupt download will auto fail bootloader flashig even one have not checked it.
Hope this will be enough to understand
Regards
PS : Anyone requires safe ND3 Kitkat bootloader with tar.md5 it is here.-flash using Odin for bootloader tab.
dr.ketan said:
CWM flashable bootloader safety concern.
I have recently seen users here flashing bootloader with CWM, here is my just head up for safety concern of CWM flashble bootloader
Here is link to post by well known X-Note ROM developer @soloilmeglio regarding forcing bootloader with CWM
http://forum.xda-developers.com/showthread.php?t=2609561
even chances are less than a 1% it will be huge for terms of breaking device. We rarely rare seen any reported brick device by bad method of flashing on XDA.
Irrespective of this another concern is MD5 check. I strongly recommend to flash bootloader with MD5 check only. Once on CWM flashable format hardly any newbies doing md5 check before every flashing (even Philz have included built in). Any corrupted bootloader download flashing will high possibly end with brick. Bootloader best to be flashed with Odin with tar.md5 format so any corrupt download will auto fail bootloader flashig even one have not checked it.
Hope this will be enough to understand
Regards
PS : Anyone requires safe ND3 Kitkat bootloader with tar.md5 it is here.
Click to expand...
Click to collapse
Good Info today morning i've flashed with TWRP but went on successful I am happy it did not Brick, But here on in Future will keep this in mind, Any possibilities now that the device is working fine are there any chances of bricking in future.
If bootloader is flashable through cwm zip then its possible to flash it via a full custom rom zip too then ? logical ?
theres a dev in Note 2 community who included the bootloader in his 4.3 rom ...i make sure I look at the skeleton of the zip after downloading. i never went to his thread again.
at that time everyone said bootloader doesnt get flashed through cwm. but whatever the case all devs have a moral responsibility to inform from before in changelog or instructions if bootloader is included in his rom zip whether it gets flashed or not. It should not be done surreptiously.
anyway good post, important discussions, should be made sticky :good:
Thank you DR.KETAN for this very important advice.
I have flashed by odin but about to flash by CWM last night.
Who have successfully flashed have nothing to worry or nothing needs to do now.
If it includes in cwm plain or including rom risk remains same.
I can even make simple utility with which you can flash bootloader with simple application on device by just keeping bootloader file on SD card. But I will never do that.
Sent from my SM-N900 using xda premium
dr.ketan said:
Who have successfully flashed have nothing to worry or nothing needs to do now.
If it includes in cwm plain or including rom risk remains same.
I can even make simple utility with which you can flash bootloader with simple application on device by just keeping bootloader file on SD card. But I will never do that.
Sent from my SM-N900 using xda premium
Click to expand...
Click to collapse
So bootloader= odin. End of story
Bootloader.tar.md5 = odin.
Sent from my SM-N900 using xda premium
dr.ketan said:
Bootloader.tar.md5 = odin.
Sent from my SM-N900 using xda premium
Click to expand...
Click to collapse
You mean to say that if we flash it through CWM or through any simple utility like you mentioned then there are chances of the bootloader going to the wrong partitions? Is that what you are trying to say?
I am thinking is there any way to find out which is the correct partition for the bootloader then?
Sent From My New Galaxy S5 GT-N7100
dr.ketan said:
Bootloader.tar.md5 = odin.
Sent from my SM-N900 using xda premium
Click to expand...
Click to collapse
Hi Doc this bootloader.tar.md5 file should be put in which option in Odin?
PDA
Phone
Bootloader
I think its the bootloader but want to be 100% sure.:laugh:
Bootloader will flash to partition on which cwm script have mentioned. But look thread in op where partition was defined correctly even though it was bricked also we don't have complete mechanism and information about knox stuff and how Samsung have managed it.
When you flash with odin Samsung have already coded file where and how to flash and it will go correctly. Another big issue is cwm itself can't stop flashing if file is corrupted. Only concern here is bootloader, if you flashed corrupted recovery /modem/kernel chances of brick is almost nil and your device can be survived by correcting it. But when you flash wrong bootloader /corrupt bootloader there may not have any combo key working so you will be helpless. It may or may not rescued by jtag box.
So always wise decision is use only tar.md5 format with odin to make safest land.
Just remember if anything most dangerous in terms of flashing it's bootloader.
Sent from my SM-N900 using xda premium
palace35mm said:
Hi Doc this bootloader.tar.md5 file should be put in which option in Odin?
PDA
Phone
Bootloader
I think its the bootloader but want to be 100% sure.:laugh:
Click to expand...
Click to collapse
Bootloader or pda any.
I recommend bootloader.
Sent from my SM-N900 using xda premium
dr.ketan said:
Bootloader will flash to partition on which cwm script have mentioned. But look thread in op where partition was defined correctly even though it was bricked also we don't have complete mechanism and information about knox stuff and how Samsung have managed it.
When you flash with odin Samsung have already coded file where and how to flash and it will go correctly. Another big issue is cwm itself can't stop flashing if file is corrupted. Only concern here is bootloader, if you flashed corrupted recovery /modem/kernel chances of brick is almost nil and your device can be survived by correcting it. But when you flash wrong bootloader /corrupt bootloader there may not have any combo key working so you will be helpless. It may or may not rescued by jtag box.
So always wise decision is use only tar.md5 format with odin to make safest land.
Just remember if anything most dangerous in terms of flashing it's bootloader.
Sent from my SM-N900 using xda premium
Click to expand...
Click to collapse
Yeah that is the most important thing of all.
And it's better to be safe with the bootloader. I don't think we have a hard unbrick method like the note 3 through sdcard.
So it's better to be safe [emoji106]
Sent From My New Galaxy S5 GT-N7100
dr.ketan said:
CWM flashable bootloader safety concern.
I have recently seen users here flashing bootloader with CWM, here is my just head up for safety concern of CWM flashble bootloader
Here is link to post by well known X-Note ROM developer @soloilmeglio regarding forcing bootloader with CWM
http://forum.xda-developers.com/showthread.php?t=2609561
even chances are less than a 1% it will be huge for terms of breaking device. We rarely rare seen any reported brick device by bad method of flashing on XDA.
Irrespective of this another concern is MD5 check. I strongly recommend to flash bootloader with MD5 check only. Once on CWM flashable format hardly any newbies doing md5 check before every flashing (even Philz have included built in). Any corrupted bootloader download flashing will high possibly end with brick. Bootloader best to be flashed with Odin with tar.md5 format so any corrupt download will auto fail bootloader flashig even one have not checked it.
Hope this will be enough to understand
Regards
PS : Anyone requires safe ND3 Kitkat bootloader with tar.md5 it is here.-flash using Odin for bootloader tab.
Click to expand...
Click to collapse
I repeat--many thanks for the warning---I will take notice--might even re-flash with ODIN--since you say that the original zip was not correct?
dr.ketan said:
CWM flashable bootloader safety concern.
PS : Anyone requires safe ND3 Kitkat bootloader with tar.md5 it is here.
Click to expand...
Click to collapse
Thanks @dr.ketan for all your wonderful works, insight and knowledge:thumbup:
My concern is can we flash the above bootloader on DN3 rc2 rom provided by the great E-team?
Sent from my GT-N7100 using XDA Premium 4 mobile app
Bootloader is not rom dependent. You can flash on any kitkat based ROM.
Sent from my SM-N900 using xda premium
haybill said:
I repeat--many thanks for the warning---I will take notice--might even re-flash with ODIN--since you say that the original zip was not correct?
Click to expand...
Click to collapse
No you need not to Reflash if your bootloader information is correct.
I didn't get you about original zip. Can you point me exactly?
Sent from my SM-N900 using xda premium
Can we change bootloader frequently ?
Like I am on kitkat now then go to jellybean MJ5 then again kitkat ? No issue?
justkiddinghere said:
Can we change bootloader frequently ?
Like I am on kitkat now then go to jellybean MJ5 then again kitkat ? No issue?
Click to expand...
Click to collapse
No you can't downgrade your bootloader because of Knox security implemented
Sent From My New Galaxy S5 GT-N7100
---------- Post added at 11:24 AM ---------- Previous post was at 11:20 AM ----------
@dr.ketan
I was just wondering if we could remove the Knox security or Knox part of the code from the bootloader files I mean sboot.bin,param.bin and tz.img so that we can get a Knox free kitkat bootloader. I know that won't work for people who already flashed MK4 and later. But it would really be helpful for people on MJ5 as they can retain warranty and be Knox free.
Is this possible?
Sent From My New Galaxy S5 GT-N7100
i vote for no tinkering with official BL....for personal experiments fine but for community...no
ive come across many expert users who havent been able to use their wifi even with mj5 bl or later, reverting to stock hasnt helped either.
justkiddinghere said:
Can we change bootloader frequently ?
Like I am on kitkat now then go to jellybean MJ5 then again kitkat ? No issue?
Click to expand...
Click to collapse
No.
Probably this one is last for Note2, you may not need to flash bootloader in future. (I don't think Note2 will get 5.0 ever)
but No it's requires only when there is major OS change and once you have 4.3 OR 4.4 bootloader, you can't downgrade but still can use 4.3 by flashin ROM with CWM OR Odin without having bootloader in it.
smeet.somaiya said:
@dr.ketan
I was just wondering if we could remove the Knox security or Knox part of the code from the bootloader files I mean sboot.bin,param.bin and tz.img so that we can get a Knox free kitkat bootloader. I know that won't work for people who already flashed MK4 and later. But it would really be helpful for people on MJ5 as they can retain warranty and be Knox free.
Is this possible?
Sent From My New Galaxy S5 GT-N7100
Click to expand...
Click to collapse
I am too small to do it.
Please help me out... I somehow ended up softbricking my device. An I cant find any working links so i can flash using odin..
What bootloader version is on the phone? I recommend not flashing anything that tries to change the bootloader or modem until you confirm at least the bootloader version.
I was on 4.2.2 if this helps then i rooted and flashed to pac-mans latest nightly
I really need help with the file to flash... none of the links are working.. I need help bad guys... An another if I ever do get this file Am I going to have to repartion or flash in pit?
Im ready to throw this phone out.. This shouldnt have to be this hard. Who would of thought If you messed up and soft brick your phone. There would be no way of undoing this cuz theres no ****ing working links anywhere or people just dont want to help. This is a joke.
This is my only phone.. It just sucks i cant find anyworking links. What did you guys do when you softbrick with no links? An when I do flash this file if I ever get it... I just put it in pda then flash in odin?
TTT
Sos..................help............................sos....................help
Ok look just go to sammobile.com or samsung-updates then download rom from there then install it through odin pc
Sent from my SM-G925F using Tapatalk
face palm... Are you sure it will work? an are they safe to flash if i was running 4.2.2
Let me Fill you guys in on the con-****ery that I did. Got phone rooted 4.2.2 firmware I then flashed cwm lawlz before roming.. I then romed the pca-man 5.1 nightly i believe.. So everything was going great Rom booted up fine no promblems... I go to mess with my performance settings... Boom no root... I concluded it was from when i factory reset before i flashed that pacman rom... next time ill be sure just to wipe it re i stand... manually so I dont lose my root just cache and dalvik cache?
So what did I do I ended up trying to reflash the root again via odin like a big idiot! Now Im bootlooped an tthis is wherne please help me THANKS ALOT stand.. So can someo
Re flash rom again with supersu zip through cwm
Anyway as i remember S3 got 4.3 so try it mate
Sent from my SM-G925F using Tapatalk
cwm is out of the picture my whole phone is wiped except for my recovery and download mode and also the pacman bootloader/loop soft brick i need to flash using odin... Im not sure if this is going to work.. Anyone have anything?
Fixed see link if you have the same problem http://forum.xda-developers.com/showthread.php?t=2549068&page=73 or message me if ANYONE needs any help. Your ATT unbricking boss!!
Unbricking is not required if you can get into download mode.
In download mode, just flash TWRP or Philz Touch, boot to recovery, and flash a custom ROM. Flash supersu from recovery for root access.
Everythings taken care of already, thanks though// =]
Was your phone hard bricked?
audit13 said:
Was your phone hard bricked?
Click to expand...
Click to collapse
No i was just really happy that it worked philz mod saved my phone.. Clockworkmod twrp didn't flash anymore so that's what the panic was.. Thanks for your time.
Just hyped I fixed it. Thanks for your help and everything in s3 forums!
From the Moderator
Remember to be polite when posting .......... to answer the TWRP Question ....... going forward TWRP is really the only stable recovery program for 4.XX the CWM has issues on many devices in Jellybean forward....... FYI
2nd thing most of the comments helping you are correct. The worst case scenario is in a hard brick you would need a Jtag to get into download mode ..... but if you can without it there is always a fix .......
One other thing .....going from JB to KK the bootloader is different framework so, there is a special flash for upgrading to that the 1st time be informed...... FYI
Be Kind Be Respectful/ Civil when posting ~~~ oka1
Hello , i got a new phone Note 4 ( Sorry wrong title . it is n910F not H)
it was on kitkat 4.4.2 and it was working well so i wanted to upgrade to 6.0.1
when i go to bootloader , i saw N910P but inside firmware and under battery it is N910F
I was confused so i flashed n910F but it fails to flash so i tried n910p , it worked but i lost imei and network. i took it a repair store and he wrote a new cert file . now i got new imie but still i dont have network. if i want to search manually , it always say error
He made downgrade to 5.1.1 and make unlock via programing tools but the same.
i didnt make any back ups foe efs.
can some one help me with this?
Thanx in advance
Sobaro said:
Hello , i got a new phone Note 4
it was on kitkat 4.4.2 and it was working well so i wanted to upgrade to 6.0.1
when i go to bootloader , i saw N910P but inside firmware and under battery it is N910H
I was confused so i flashed n910h but it fails to flash so i tried n910p , it worked but i lost imei and network. i took it a repair store and he wrote a new cert file . now i got new imie but still i dont have network. if i want to search manually , it always say error
He made downgrade to 5.1.1 and make unlock via programing tools but the same.
i didnt make any back ups foe efs.
can some one help me with this?
Thanx in advance
Click to expand...
Click to collapse
You should always always backup every partition. Especially efs.
Anyhow, what service are you trying to use? GSM or CDMA?
If your using it with GSM, and If this phone is truly a sprint phone, it probably got sim locked when he fixed it. I ain't no expert but it probably needs unlocked if this is the case.
Edit: I just understood what you wrote, that he already unlocked it. Sorry for misunderstanding.
But if your using it with sprint, maybe it just needs activation updated. I don't use sprint or CDMA so I don't know a lot about that.
But main thing you need to do before anything else. Is make a full back up of your partitions. I always make backup in two.( Which is mainly all you need)
But also there are programs that (I can't remember there names,) make backups of all your hidden partitions, just in case.
I understand I didn't provide you with a definite answer to your problem but hope it can help.
aaron74 said:
You should always always backup every partition. Especially efs.
Anyhow, what service are you trying to use? GSM or CDMA?
If your using it with GSM, and If this phone is truly a sprint phone, it probably got sim locked when he fixed it. I ain't no expert but it probably needs unlocked if this is the case.
Edit: I just understood what you wrote, that he already unlocked it. Sorry for misunderstanding.
But if your using it with sprint, maybe it just needs activation updated. I don't use sprint or CDMA so I don't know a lot about that.
But main thing you need to do before anything else. Is make a full back up of your partitions. I always make backup in two.( Which is mainly all you need)
But also there are programs that (I can't remember there names,) make backups of all your hidden partitions, just in case.
I understand I didn't provide you with a definite answer to your problem but hope it can help.
Click to expand...
Click to collapse
nah, i am not using it with sprint and yes i am using GSM network.
I tried every solution available but no success .
Sobaro said:
nah, i am not using it with sprint and yes i am using GSM network.
I tried every solution available but no success .
Click to expand...
Click to collapse
Can to send me a copy of your build.prop
Edit. Are you using sprint stock ROM? What version? Are you sure it's unlocked? If yes, I might be able to help. But I have to gather some info. And get to my PC. Cause I'm testing a ROM right now and am lagging
I have faced the same problem and, managed to solve it. Here is the solution..
1. Download any kk or lp firmware of n910p. Extract the .tar file, get the ' modem.bin' and flash it using Odin. Do it twice, yes, twice. Before flashing the modem, make sure you have unchecked 'auto boot' option in Odin. To turn off the phone after the first flesh, just take off the battery.
2. Download twrp 3.0.1.0 for n910f. Yes.. TWRP recovery for N910F ( or the model specified under the battery). Flash it using Odin.
3. Download any stock based custom ROM which is based on the modem you have flashed. For example, BOB7, COG5 , COK1( these are the last 4 characters of the stock firmware/modem)
4. Flash the custom ROM using twrp, flash gasps, and smile.
If you face bootloop, just try different kernel. I'm using BOB7 modem, emotion kernel, vision x custom ROM.
z.a.shimon said:
I have faced the same problem and, managed to solve it. Here is the solution..
1. Download any kk or lp firmware of n910p. Extract the .tar file, get the ' modem.bin' and flash it using Odin. Do it twice, yes, twice. Before flashing the modem, make sure you have unchecked 'auto boot' option in Odin. To turn off the phone after the first flesh, just take off the battery.
2. Download twrp 3.0.1.0 for n910f. Yes.. TWRP recovery for N910F ( or the model specified under the battery). Flash it using Odin.
3. Download any stock based custom ROM which is based on the modem you have flashed. For example, BOB7, COG5 , COK1( these are the last 4 characters of the stock firmware/modem)
4. Flash the custom ROM using twrp, flash gasps, and smile.
If you face bootloop, just try different kernel. I'm using BOB7 modem, emotion kernel, vision x custom ROM.
Click to expand...
Click to collapse
Thank you, i will try and get back to u soon . Much appreciated !
aaron74 said:
Can to send me a copy of your build.prop
Edit. Are you using sprint stock ROM? What version? Are you sure it's unlocked? If yes, I might be able to help. But I have to gather some info. And get to my PC. Cause I'm testing a ROM right now and am lagging
Click to expand...
Click to collapse
yes i am sure phone is unlocked through Domestic Unlock ( z3x & octoplus Boxes)
also i am on Stock 5.1.1 lollipop
I think the only way u can help me is by sharing a good QCN and EFS for N910P ! (if the above solution from our friend doesnt work 4 me )
Also i am from another country so there is no harm for you if u share it with me in private.
Thanks in Advance !
Sobaro said:
yes i am sure phone is unlocked through Domestic Unlock ( z3x & octoplus Boxes)
also i am on Stock 5.1.1 lollipop
I think the only way u can help me is by sharing a good QCN and EFS for N910P ! (if the above solution from our friend doesnt work 4 me )
Also i am from another country so there is no harm for you if u share it with me in private.
Thanks in Advance !
Click to expand...
Click to collapse
Sounds like your on your way. Good luck.
z.a.shimon said:
I have faced the same problem and, managed to solve it. Here is the solution..
1. Download any kk or lp firmware of n910p. Extract the .tar file, get the ' modem.bin' and flash it using Odin. Do it twice, yes, twice. Before flashing the modem, make sure you have unchecked 'auto boot' option in Odin. To turn off the phone after the first flesh, just take off the battery.
2. Download twrp 3.0.1.0 for n910f. Yes.. TWRP recovery for N910F ( or the model specified under the battery). Flash it using Odin.
3. Download any stock based custom ROM which is based on the modem you have flashed. For example, BOB7, COG5 , COK1( these are the last 4 characters of the stock firmware/modem)
4. Flash the custom ROM using twrp, flash gasps, and smile.
If you face bootloop, just try different kernel. I'm using BOB7 modem, emotion kernel, vision x custom ROM.
Click to expand...
Click to collapse
I did exactly as u said but still dont have network. i think i messed up my efs folder .
Please any suggestions ?
Sobaro said:
I did exactly as u said but still dont have network. i think i messed up my efs folder .
Please any suggestions ?
Click to expand...
Click to collapse
Could you please check the IMEI? Is it null or "00"? Does your phone shows baseband number?
z.a.shimon said:
Could you please check the IMEI? Is it null or "00"? Does your phone shows baseband number?
Click to expand...
Click to collapse
My imei & baseband are OK
Any way i send it back to customer care , thank u very much.
same problem
i have the same problem you have i do not know what shall i do ?
please any help
did you try to flash stock sprint firmware lollipop 5.1.1?
Sobaro said:
My imei & baseband are OK
Any way i send it back to customer care , thank u very much.
Click to expand...
Click to collapse
Bro
Did you ever solved the problem?
I have a similar problem, but my phone makes emergen y calls, but will notnregiater to the network.