Tmobile firmware test build? - T-Mobile Samsung Galaxy S 5

I was told the only way to get my phone to be restored via Odin is to flash a "test build" of a firmware because it is the only kind that will truly fully delete everything when flashing, anyone know if this is available anywhere?
Thanks

Not that I have ever seen.
Who told you that?
I would think you should be able to use the reset option in ODIN when flashing.
What problems are you having that flashing the stock file in Odin isn't fixing?

TheArtiszan said:
Not that I have ever seen.
Who told you that?
I would think you should be able to use the reset option in ODIN when flashing.
What problems are you having that flashing the stock file in Odin isn't fixing?
Click to expand...
Click to collapse
keithross39 told me that.
I tried all the conventional ways of odin flashing to no avail, I posted detailed info here.
link

I would do a little research into if repartition or erase nand might help.
I think pit file is in those files so you might be able to try repartition.

TheArtiszan said:
I would do a little research into if repartition or erase nand might help.
I think pit file is in those files so you might be able to try repartition.
Click to expand...
Click to collapse
I flashed pit several and checked erase nand in odin several times with no success

The not seandroid enforcing is cause of the custom recovery. I ran into something similar awhile back and it was the kernel.

Related

brick the phone after flash with a wrong pit file

hi there,
i flash my phone with a wrong pit file, and i run into a problem. its already fixed again by my self, but i want to share my experience with you, maybe someone can use it too.
you can download stock- roms, odin and pit files for your phone on sammobile.com. i found a explanation on samdownloads.de with follow information's:
- pit file with 220 on the end is for 16gb version
- pit file with 322 is for 32bg version
- pit file with 329 is for 64gb version
HOLD ON! This information's are wrong for me, and that's why i ran into this problem.
so i download a rom, and i choose the 322 file for my device and start with the flash process. result from that was, that odin hangs on step, SET PARTITION, and that was it. before, i already deleted the other pit files, while i was thinking i didn't need it. so the first was, i investigate some times to find the pit files on the net again and i start to flash with all files, one after the other..
my phone hangs with 220 pit file, with 322 pit file but i get it successfully flashed with 329 file, which if i believe to samdownloads.de was the file for the 64gb version of the phone.
in my opinion and if i look on my experience right now, for international i9300 32bg version the right pit file was the 329. after flashing it again, my phone was again fully stock, everything was fine, my 25gb free space was there, so its fine.
maybe i can help someone with this information's..
m_adnan said:
hi there,
i flash my phone with a wrong pit file, and i run into a problem. its already fixed again by my self, but i want to share my experience with you, maybe someone can use it too.
you can download stock- roms, odin and pit files for your phone on sammobile.com. i found a explanation on samdownloads.de with follow information's:
- pit file with 220 on the end is for 16gb version
- pit file with 322 is for 32bg version
- pit file with 329 is for 64gb version
HOLD ON! This information's are wrong for me, and that's why i ran into this problem.
so i download a rom, and i choose the 322 file for my device and start with the flash process. result from that was, that odin hangs on step, SET PARTITION, and that was it. before, i already deleted the other pit files, while i was thinking i didn't need it. so the first was, i investigate some times to find the pit files on the net again and i start to flash with all files, one after the other..
my phone hangs with 220 pit file, with 322 pit file but i get it successfully flashed with 329 file, which if i believe to samdownloads.de was the file for the 64gb version of the phone.
in my opinion and if i look on my experience right now, for international i9300 32bg version the right pit file was the 329. after flashing it again, my phone was again fully stock, everything was fine, my 25gb free space was there, so its fine.
maybe i can help someone with this information's..
Click to expand...
Click to collapse
I've had my S3 since may 25th MAY and done tons of flashing of ROMS. Never have i ticked the pit as it was clearly mentioned in all the flashing tutorials. There is no need to do it and dont need to encourage others to do something which can hard brick their phones.
sak500 said:
I've had my S3 since may 25th MAY and done tons of flashing of ROMS. Never have i ticked the pit as it was clearly mentioned in all the flashing tutorials. There is no need to do it and dont need to encourage others to do something which can hard brick their phones.
Click to expand...
Click to collapse
100% agree stay away from PIT unless you really know what you are doing .
jje
sak500 said:
I've had my S3 since may 25th MAY and done tons of flashing of ROMS. Never have i ticked the pit as it was clearly mentioned in all the flashing tutorials. There is no need to do it and dont need to encourage others to do something which can hard brick their phones.
Click to expand...
Click to collapse
JJEgan said:
100% agree stay away from PIT unless you really know what you are doing .
jje
Click to expand...
Click to collapse
its only as a information, maybe somebody runs into the same problem..
It's true that's it's not advised to play with pit files, but I think it would be better if you explained to people why.
Pit files are to be used only when you need to restore partition layout on the phone. That means after you mess up partitions and not before. Bu some guys just ignore warnings like this.
PjotrFias said:
It's true that's it's not advised to play with pit files, but I think it would be better if you explained to people why.
Pit files are to be used only when you need to restore partition layout on the phone. That means after you mess up partitions and not before. Bu some guys just ignore warnings like this.
Click to expand...
Click to collapse
The why is generally that they use the wrong PIT files .
One of the stupid reasons why is going to forum xxxx downloading firmware from them then coming here to ask why has it broke my phone .
PIT mistakes for SG range are in the thousands not just the odd few .
jje
flashed a pit file and now my galaxy s2 is hard bricked
Hi
im new to xda. but having been trying to root my galaxy s2 I9100 through xda tutorials.
my problem started when i flashed a pit file with odin.and now i think its hard bricked. doesn't respond to anything, doesn't show on odin either. ive taken the battery out and have kept it like it for more than 6 hours, with no luck at all. but once i put in the battery to check it becomes hot. even bought a USB Jig and tried, nothing happened. please help as in my country we dont get warranty or we dont samsung service centers. I've tried so many ways to get my phone to life but have failed.. please help:crying:
Does the phone boot to download mode does Odin see the phone .
jje
JJEgan said:
Does the phone boot to download mode does Odin see the phone .
jje
Click to expand...
Click to collapse
nope nothing happens only gets hot..
boboschiyax said:
nope nothing happens only gets hot..
Click to expand...
Click to collapse
One source a USB Recovery Jig and try to enter download mode .Flash stock firmware .
That fails its a paid for service centre job .
jje
JJEgan said:
One source a USB Recovery Jig and try to enter download mode .Flash stock firmware .
That fails its a paid for service centre job .
jje
Click to expand...
Click to collapse
thanks but already did that. didn't work
boboschiyax said:
i think its hard bricked. doesn't respond to anything, doesn't show on odin either.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=32367917
pleaaaaaaaaaase help me !!
m_adnan said:
hi there,
i flash my phone with a wrong pit file, and i run into a problem. its already fixed again by my self, but i want to share my experience with you, maybe someone can use it too.
you can download stock- roms, odin and pit files for your phone on sammobile.com. i found a explanation on samdownloads.de with follow information's:
- pit file with 220 on the end is for 16gb version
- pit file with 322 is for 32bg version
- pit file with 329 is for 64gb version
HOLD ON! This information's are wrong for me, and that's why i ran into this problem.
so i download a rom, and i choose the 322 file for my device and start with the flash process. result from that was, that odin hangs on step, SET PARTITION, and that was it. before, i already deleted the other pit files, while i was thinking i didn't need it. so the first was, i investigate some times to find the pit files on the net again and i start to flash with all files, one after the other..
my phone hangs with 220 pit file, with 322 pit file but i get it successfully flashed with 329 file, which if i believe to samdownloads.de was the file for the 64gb version of the phone.
in my opinion and if i look on my experience right now, for international i9300 32bg version the right pit file was the 329. after flashing it again, my phone was again fully stock, everything was fine, my 25gb free space was there, so its fine.
maybe i can help someone with this information's..
Click to expand...
Click to collapse
i tried 4 pit files to repartition my samsung s3 i9300 but all the result is fault
my s3 now dead
please help me
i search google for all pit files of i9300 but no success
pleaaaaaaaaaaaaaaaaaaaaaaaaaaaaase can anybody help me!!
please help me i did the same thing i have note 3 of n9005 UAE version of 32gb and i flashed a wrong pit file (i.e i flashed N900A pit file in N9005 ) and i tried many pit files using Nand erase all in odin but its not working for me as it just erased the partion in my phone but its not repartioning i mean not replacing any pit file
and odin just showing me error all the time and flashing FAIL
Nothing you can do. If you flash a wrong pit file then your phone is broken. Hard bricked.
The only possibility for you is finding someone with a JTAG box. Try one of those phone repair shops. AFAIK, that's your only hope.
Flashing a wrong pit file is pretty much the worst possible thing you can do to your phone. How the hell did you manage to flash the wrong pit file? Didn't you double, triple, quadruple check that it was the correct file before flashing?
Please don't tell me that you knew that the file was meant for another phone? I've actually seen people do that... :facepalm:
Sent from my GT-I9300 using Tapatalk
NeilH1978 said:
Nothing you can do. If you flash a wrong pit file then your phone is broken. Hard bricked.
The only possibility for you is finding someone with a JTAG box. Try one of those phone repair shops. AFAIK, that's your only hope.
Flashing a wrong pit file is pretty much the worst possible thing you can do to your phone. How the hell did you manage to flash the wrong pit file? Didn't you double, triple, quadruple check that it was the correct file before flashing?
Please don't tell me that you knew that the file was meant for another phone? I've actually seen people do that... :facepalm:
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
It is possible because people usually think in terms of branding. Not aware different models may exist in different regions. Example the note gen1 has Korean and Chinese and US versions, each has a different model number.
XyRo7ec said:
please help me i did the same thing i have note 3 of n9005 UAE version of 32gb and i flashed a wrong pit file (i.e i flashed N900A pit file in N9005 ) and i tried many pit files using Nand erase all in odin but its not working for me as it just erased the partion in my phone but its not repartioning i mean not replacing any pit file
and odin just showing me error all the time and flashing FAIL
Click to expand...
Click to collapse
Here is the pit file for Note 3 SM-N9005 32gb varient.
HELP i think flashed the wrong .tar root file for my Galaxy J7 Pro
Hey man,
XDA doesn't trust me enough to let me make my own post and as I'm writing this I'm supposed to be studying for the 3 exams I will be having.
So,
I rooted my phone susing ODIN and the same root file a few months ago on Android 7.1 and it worked. I used it with TWRP recovery and everthing was fine.
Then the Android Oreo update was released for my phone, finally, and I hooked my phone up to my laptop and downloaded the firmware using Samsung's new Software called SmartThings.
Now I had stock ROM, but my device was recognized as rooted and modified, so couldn't use a few apps like Samsung Health and Pay. Then, without thinking, I put my phone in Download Mode and flashed the SAME .tar root file with ODIN, and now my phone won't boot to the pulsating Samsung logo and is stuck in the bootloader
wanted to say that Odin said PASS when .tar file was downloaded in the AP slot
In download mode,
Download Mode says:
Current Binary: Custom
System status: Official
FAP LOCK: OFF
OEM LOCK: OFF
Secure Download: Enabled
WARRANTY VOID: 1 (0x0303)
I have access to STOCK recovery and download mode, and I've already tried factory resetting phone and wiping cache. I don't want to take more rash steps without someone knowledgeable guiding me. and I cant find any other forum to post on because I'm not a high enough member.
I have fixed when up wrong file pit
My phone is samsung note9 128gb
When i try to up file pit on rom . I had loss my store from 128gb to 32gb
I don't find any solotion on web
And i have go to setting , open development setting. Choose lock OEM. After that my phone restart and recover to 128gb
Please share this solution . I hope it can help many people up wrong file pit and loss data store like me .
File up wrong pit file odin by Lock Oem
Recover Lost data store .

NAND Write Start stalls

First I read all the stickies and tried every installation to go back to stock but Odin just freezes up. Also tried different USB ports and and computers and same results. I can only go into download mode.
You may need to repartition. Not knowing the history of how your phone got to where it is now, I can't be sure. Can you give me a complete rundown of your issue?
creepyncrawly said:
You may need to repartition. Not knowing the history of how your phone got to where it is now, I can't be sure. Can you give me a complete rundown of your issue?
Click to expand...
Click to collapse
How would I go about repartitioning the phone? I full wipe and flashed the new Shostock3 and it was doing fine. The next day when I woke up my phone had the sleep of death. The Galaxy S2 logo was stuck and I tried to get into recovery and it only showed half of the screen and was frozen. Now the screen says Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
Go to the Download Repository. The link is in my sig.
First, try flashing full stock Gingerbread. Use the download under the heading I777UCKH7-CL503881 Stock Binaries. This is the full distribution which contains the bootloaders. It doesn't matter whether you use the one-click downloader, or the tar.md5 file with Odin stand alone. If this flash completes, then you're recovered. Follow the guides to root and install a custom Gingerbread kernel, then flash back to SHOstock3 or whatever firmware you want.
If this flash does not complete, then download the I777 UCKH7 PIT and use that in Odin stand alone with the above tar.md5 file. Insert the tar in the PDA slot, the pit in the PIT slot, and check repartition, then flash.
creepyncrawly said:
Go to the Download Repository. The link is in my sig.
First, try flashing full stock Gingerbread. Use the download under the heading I777UCKH7-CL503881 Stock Binaries. This is the full distribution which contains the bootloaders. It doesn't matter whether you use the one-click downloader, or the tar.md5 file with Odin stand alone. If this flash completes, then you're recovered. Follow the guides to root and install a custom Gingerbread kernel, then flash back to SHOstock3 or whatever firmware you want.
If this flash does not complete, then download the I777 UCKH7 PIT and use that in Odin stand alone with the above tar.md5 file. Insert the tar in the PDA slot, the pit in the PIT slot, and check repartition, then flash.
Click to expand...
Click to collapse
So I tried both the one-click downloader and flash doesn't not complete, same goes for odin and PIT file.
selw0nk said:
So I tried both the one-click downloader and flash doesn't not complete, same goes for odin and PIT file.
Click to expand...
Click to collapse
If you didn't try it already, now go back and flash just the tar.md5 file without the pit, again, and see if it will complete.
creepyncrawly said:
If you didn't try it already, now go back and flash just the tar.md5 file without the pit, again, and see if it will complete.
Click to expand...
Click to collapse
Just did and it is stuck at NAND Write Start!! My phone might have a hardware issue.
selw0nk said:
Just did and it is stuck at NAND Write Start!! My phone might have a hardware issue.
Click to expand...
Click to collapse
Yes, I was hoping that the problem is not hardware, but it was a thought from the beginning, given the sequence of failure. Is the phone by chance still under warranty?
Let's don't give up yet, though.
Things to try, then try to flash the full firmware in between.
1. Use Odin stand alone to flash just the I777 secondary bootloader.
2. Use Odin stand alone to flash just the param.lfs.
Try the instructions in this post.
creepyncrawly said:
Yes, I was hoping that the problem is not hardware, but it was a thought from the beginning, given the sequence of failure. Is the phone by chance still under warranty?
Let's don't give up yet, though.
Things to try, then try to flash the full firmware in between.
1. Use Odin stand alone to flash just the I777 secondary bootloader.
2. Use Odin stand alone to flash just the param.lfs.
Try the instructions in this post.
Click to expand...
Click to collapse
No it isn't anymore. My upgrade isn't until May. Do you think a usb jig will work?
Thanks I will try that and will let you know how it comes along.
selw0nk said:
Do you think a usb jig will work?
Click to expand...
Click to collapse
You can already get into download mode. I don't believe there is any difference in the download mode produced by a jig. A jig is really helpful if the wrong secondary bootloader was flashed by accident (or ignorance), and you can't get the phone into download mode any ohter way.
selw0nk said:
No it isn't anymore. My upgrade isn't until May. Do you think a usb jig will work?
Thanks I will try that and will let you know how it comes along.
Click to expand...
Click to collapse
Tried those these you mentioned and still stuck. I'm already losing hope and want to get a new phone or spare already. I think I have a few things saved in the phone too.
Update: My screen is stuck at the Samsung Galaxy S2 screen with the yellow triangle.
Same problem
selw0nk said:
Tried those these you mentioned and still stuck. I'm already losing hope and want to get a new phone or spare already. I think I have a few things saved in the phone too.
Update: My screen is stuck at the Samsung Galaxy S2 screen with the yellow triangle.
Click to expand...
Click to collapse
I am having the exact same problem and my update isn't until May too!! Is this a common hardware failure?
kunalm123 said:
I am having the exact same problem and my update isn't until May too!! Is this a common hardware failure?
Click to expand...
Click to collapse
What rom were you on if I may ask? I'm not sure, but I'm about ready to give on trying everything. I started using my old Nokia phone and have to manually add my contacts lol. Sad panda
selw0nk said:
What rom were you on if I may ask? I'm not sure, but I'm about ready to give on trying everything. I started using my old Nokia phone and have to manually add my contacts lol. Sad panda
Click to expand...
Click to collapse
I was using a stock unrooted SGS2. It just stop working out of the blue..back to nokia it is
So I think I am going to send my phone to Mobile Tech Videos and hope they can unbrick it. http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-ii-at-t-jtag-brick-repair/
selw0nk said:
So I think I am going to send my phone to Mobile Tech Videos and hope they can unbrick it. http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-ii-at-t-jtag-brick-repair/
Click to expand...
Click to collapse
I think I have a similar issue on my phone (stalls in odin, I haven't flashed any PIT files yet), were they able to unbrick it?
Same issue here, The phone's stuck on Nand flash in Odin. Had tried all recommendations suggested here... Any updates on the phone sent to mobiletech guys?

Flash back to stock... Failure. Help!

I was trying to flash back my I605 Note 2. I'm coming from CM11. Downloaded original 4.1.2 firmware and ran through Odin. Everything passed and worked through Odin, but when the phone restarted it was flashing the Galaxy Note 2 screen....... Any ideas? About to sell the phone. Really need some help. Any comments would be appreciated. Thank you.
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-note-2/
Worst case scenario Jtag brick repair $50. I would try everything thing 1st. Try to Odin root66. Try Odin again, maybe with the vram, or vrall down load. Can you get into recovery? Or download mode?
madmuthertrucker said:
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-note-2/
Worst case scenario Jtag brick repair $50. I would try everything thing 1st. Try to Odin root66. Try Odin again, maybe with the vram, or vrall down load. Can you get into recovery? Or download mode?
Click to expand...
Click to collapse
download mode yes. recovery no.
khipps16 said:
download mode yes. recovery no.
Click to expand...
Click to collapse
I think I've had this problem before. I flashed the root66 4.1.2 file and it got stuck. From there I put it in download mode and flashed TWRP through Odin. Then I went into recovery and flashed a ROM and from there I got it to boot. Since you're selling it, I would say flash creanrom and then flash sophisticated 4.3 to give them a stock experience.
- Your phone fitting in my phone's screen is nothing new to me.
After NAND write, Odin fails..... Now what?
khipps16 said:
After NAND write, Odin fails..... Now what?
Click to expand...
Click to collapse
Haven't seen that one. I did some research and the things I found are pretty bad. I read theres a problem where your phone storages are set to R/O rather than R/W and its not allowing it to write anything. The last thing I found to fix it was a fix for the VZN GS3, but I'm gonna guess the same will for the the Note 2. I would suggest using the unrooted stock firmware since root is unimportant right now. You can get that somewhere in another thread because I don't have the link handy. Get that, and get the pit file and load that into Odin with your phone in download mode. Go ahead and make sure repartition is checked as well and give that a try. Using the pit file should reset the data tables (or something like that) to the proper R/W permissions. Hope everything works out for you!
EDIT- Here's the thread you can use to get the firmware and pit file. All the files you should need are in section 1b. I know I said not to use the root66 file, go ahead and try it first because the firmware files are huge. If root66 doesn't work, go for the one that says it'll return it to "out of the box conditions." From here, hopefully it'll boot. If you run into the endless boot issue from here, go back to the first post I posted and do that.
Another Edit - I'm an idiot. Forgot to paste the link. http://forum.xda-developers.com/showthread.php?t=2024207
- Your phone fitting in my phone's screen is nothing new to me.

Stuck on getting Pit mapping

Hey guys i'm trying to fix a friend's i9300. He bought it from someone already in the current state.
It boots to the samsung logo but does nothing after that
Model: GT-I9300
FCC ID: A3LGTI9300A
SSN: I9300GSMH
I have tried to ODIN I9300ZNUBML1_I9300CHUBML1_CHU.zip onto it, but it says its missing pit partition, so i tried to load a pit onto it, I've tried GT-I9300_mx_20120329.pit but it gets stuck of getting pit mapping.
What am I doing wrong? I have no clue which country this phone is from either.
I have attached the *.PIT file I used to restore my phone. It is for the 16GB i9300. Remember in ODIN to include the ROM in the /PDA section, and the *.pit file in the section where it asks for it. Have the following boxes checked:
Re-Partition
Auto-Reboot
F. Reset Time.
Phone Bootloader Update
Flash the ROM, and let ODIN do it's thing. DO NOT UNPLUG YOUR DEVICE UNTIL IT IS DONE!! Doing this will completely wipe the phone, and return it to a factory state.
Flash the firmware and pit at the same time, or try the rescue firmware in general thread.
If it still fails then emmc chip is blown, new motherboard required.
Sent from my GT-I9300 using Tapatalk
thanks guys i'll give that a shot and report back.
eric303 said:
thanks guys i'll give that a shot and report back.
Click to expand...
Click to collapse
if you enter on recovery mode and you get this:
http://forum.xda-developers.com/galaxy-s3/help/emmc-problem-t2722684
its the same of my phone, report back if you solved, mine dont flash pit files
k-semler said:
I have attached the *.PIT file I used to restore my phone. It is for the 16GB i9300. Remember in ODIN to include the ROM in the /PDA section, and the *.pit file in the section where it asks for it. Have the following boxes checked:
Re-Partition
Auto-Reboot
F. Reset Time.
Phone Bootloader Update
Flash the ROM, and let ODIN do it's thing. DO NOT UNPLUG YOUR DEVICE UNTIL IT IS DONE!! Doing this will completely wipe the phone, and return it to a factory state.
Click to expand...
Click to collapse
I have a lot of PIT files, but with yours i can flash in heidmall, but return an error on 7%... i dont understand
sergio_f said:
I have a lot of PIT files, but with yours i can flash in heidmall, but return an error on 7%... i dont understand
Click to expand...
Click to collapse
Have you tried a different USB cable, and/or using a different USB port on your computer?
k-semler said:
Have you tried a different USB cable, and/or using a different USB port on your computer?
Click to expand...
Click to collapse
Yes, tried different computers also, i think it's the memory, it's corrupted, but it's funny because only with PIT file from this post i get something when try flash the stock Rom even with errors..

IMEI null BASEBAND null

hi, i flashed my galaxy s2 i777 to JB 4.1.2 with odin and when it restarted, it didnt recognize the sim card, then i checked and the IMEI an Baseband were gone, i have a screenshot with the IMEI it had, but i didnt backed EFS, i didnt even know that i had to, when flashing, its not the first time i flash, i had 4.0.3 then flashed to 4.1.2, and then i had a problem and flashed to 4.3 then it got stuck on rethink possible screen so i flashed back to 4.1.2, and now im without IMEI o BASEBAND, like this it doesnt recognize any sim card, please help, ive already searched in the forum but didnt find a working solution for me!
Thanks!
Did ya try to wipe data/factory reset in Recovery and then re Odin stock 4.1.2 firmware ?
Sent from my Nexus 5 using Tapatalk
4-2ndtwin said:
Did ya try to wipe data/factory reset in Recovery and then re Odin stock 4.1.2 firmware ?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
yes i did, twice, i used gsii repair too, it said that my phone was unlocked but nothing happened when restarted, i tried the method of erasing efs folder, copying, recopying, and all that, i use the command su chown 1001:radio /efs/.... but it says "no radio found". any idea why is that happening?, i need help with this!! and thanks.
PD: one question, i always see that everyone asks here to read the stickies, where are the stickies or what are they?, what i do is read the previous threads in search for an answer but i havent see the stickies.
juanf9224 said:
yes i did, twice, i used gsii repair too, it said that my phone was unlocked but nothing happened when restarted, i tried the method of erasing efs folder, copying, recopying, and all that, i use the command su chown 1001:radio /efs/.... but it says "no radio found". any idea why is that happening?, i need help with this!! and thanks.
Click to expand...
Click to collapse
Did you use a pit file and repartition during one of your flashes?
PD: one question, i always see that everyone asks here to read the stickies, where are the stickies or what are they?, what i do is read the previous threads in search for an answer but i havent see the stickies.
Click to expand...
Click to collapse
Sticky threads are at the top of each forum in the desktop version of the forum, and have a push pin icon on the left. On the mobile version of the forum, I think there is a separate tab for the sticky threads.
creepyncrawly said:
Did you use a pit file and repartition during one of your flashes?
Click to expand...
Click to collapse
i didnt, altough, i wanted to, because i saw that it was the solution to a problem i had when flashing, but no, i didnt use the pit file nor repartition.
creepyncrawly said:
Sticky threads are at the top of each forum in the desktop version of the forum, and have a push pin icon on the left. On the mobile version of the forum, I think there is a separate tab for the sticky threads.
Click to expand...
Click to collapse
ohhh, i see, thanks.
juanf9224 said:
i didnt, altough, i wanted to, because i saw that it was the solution to a problem i had when flashing, but no, i didnt use the pit file nor repartition.
Click to expand...
Click to collapse
Well, I don't know exactly what you did to mess with the imei/efs. Without a backup, it's going to be difficult to recover from that problem. Frankly, I don't know enough about it to be of any help. I think I've read that you can get the phone working with a generic IMEI but you can't get the original IMEI back. But again, it's just speculation on my part. Maybe someone else who knows more will jump in.
when I had this issue I flashed with odin back to JB 4.1.2 stock and that seemed to fix it, don't know if it will be work for you but its worth looking into
creepyncrawly said:
Well, I don't know exactly what you did to mess with the imei/efs. Without a backup, it's going to be difficult to recover from that problem. Frankly, I don't know enough about it to be of any help. I think I've read that you can get the phone working with a generic IMEI but you can't get the original IMEI back. But again, it's just speculation on my part. Maybe someone else who knows more will jump in.
Click to expand...
Click to collapse
i tried to downgrade to ics 4.0.3 but always fails with odin, i was looking into the version of the firmware by typing *#1234# and in it says:
PDA : 1777UCMD8
PHONE: Unknown
CSC: I777ATTMD8
is there any way to get the phone file, i see in odin that it has a phone option, so, i'd like to try and flash that file and see, any idea where to get it for JB 4.1.2?
micallan_17 said:
when I had this issue I flashed with odin back to JB 4.1.2 stock and that seemed to fix it, don't know if it will be work for you but its worth looking into
Click to expand...
Click to collapse
my actual firmware is JB 4.1.2 so i cant go back to it since that's the one i have, and i've tried to downgrade to 4.0.3 wich is the rom it had when i bought it, but it always fails on factoryfs.img dont know why.
juanf9224 said:
my actual firmware is JB 4.1.2 so i cant go back to it since that's the one i have, and i've tried to downgrade to 4.0.3 wich is the rom it had when i bought it, but it always fails on factoryfs.img dont know why.
Click to expand...
Click to collapse
yes but regardless of you currently being on 4.1.2 you can still reflash the stock jb 4.1.2 firmware via odin, you can try redownloading the image file since you might have a case of a corrupted image.
I agree that you should attempt to flash stock ucmd8 again after re-downloading the file. You should flash the .tar.md5 version. Odin will check the md5 sum of the file before flashing and only flash it if it is not corrupt. You can find a download for it in the Download Repository. It's the very last item at the bottom.
micallan_17 said:
yes but regardless of you currently being on 4.1.2 you can still reflash the stock jb 4.1.2 firmware via odin, you can try redownloading the image file since you might have a case of a corrupted image.
Click to expand...
Click to collapse
Yes, i've reflashed several times jb4.1.2 but the imei is still unkown as well as the baseband.
Where do i get the image file so i can flash it? Or you mean the firmware?
juanf9224 said:
Where do i get the image file so i can flash it? Or you mean the firmware?
Click to expand...
Click to collapse
By the image file, he means the firmware file. I put a link to the Download Repository in my last post, and it is also in my signature on every post. Did you download from there and try flashing that file? If not, please do that as your next step.
creepyncrawly said:
By the image file, he means the firmware file. I put a link to the Download Repository in my last post, and it is also in my signature on every post. Did you download from there and try flashing that file? If not, please do that as your next step.
Click to expand...
Click to collapse
i see, ill try now with that, thanks man, ill be back to let you know if it worked.
creepyncrawly said:
I agree that you should attempt to flash stock ucmd8 again after re-downloading the file. You should flash the .tar.md5 version. Odin will check the md5 sum of the file before flashing and only flash it if it is not corrupt. You can find a download for it in the Download Repository. It's the very last item at the bottom.
Click to expand...
Click to collapse
i flashed with that JB from the repository but nothing, same as always, the last thing i want to try is to downgrade, but when i try to downgrade to 4.0.3 it always fail on factoryfs.img, and i flashed 4.3 but it got stuck on rethink possible, do i need some specific way to downgrade?
juanf9224 said:
i flashed with that JB from the repository but nothing, same as always, the last thing i want to try is to downgrade, but when i try to downgrade to 4.0.3 it always fail on factoryfs.img, and i flashed 4.3 but it got stuck on rethink possible, do i need some specific way to downgrade?
Click to expand...
Click to collapse
At this point, downgrading to 4.0.3 is probably not a solution. From all the information that you have posted so far, it appears that your phone either has a firmware issue such as corrupt memory, or a hardware issue such as damaged eMMC memory. It is also possible that a necessary step is being skipped, such as performing a wipe data/factory reset from within recovery. Although both myself and 4-2ndtwin have mentioned that you should do that, you have never specifically stated in any of your three threads that you followed our advice.
So first things first, have you performed a wipe data/factory reset from within recovery? Have you included this step with every attempt to flash a firmware through Odin3?
creepyncrawly said:
At this point, downgrading to 4.0.3 is probably not a solution. From all the information that you have posted so far, it appears that your phone either has a firmware issue such as corrupt memory, or a hardware issue such as damaged eMMC memory. It is also possible that a necessary step is being skipped, such as performing a wipe data/factory reset from within recovery. Although both myself and 4-2ndtwin have mentioned that you should do that, you have never specifically stated in any of your three threads that you followed our advice.
So first things first, have you performed a wipe data/factory reset from within recovery? Have you included this step with every attempt to flash a firmware through Odin3?
Click to expand...
Click to collapse
i did, last night i flashed to ics 4.0.3 and perform a wipe data/factory reset before, but it got stuck on rethink possible screen, now ill flashed back to 4.1.2 , in case of corrupt memory, what could do?
creepyncrawly said:
At this point, downgrading to 4.0.3 is probably not a solution. From all the information that you have posted so far, it appears that your phone either has a firmware issue such as corrupt memory, or a hardware issue such as damaged eMMC memory. It is also possible that a necessary step is being skipped, such as performing a wipe data/factory reset from within recovery. Although both myself and 4-2ndtwin have mentioned that you should do that, you have never specifically stated in any of your three threads that you followed our advice.
So first things first, have you performed a wipe data/factory reset from within recovery? Have you included this step with every attempt to flash a firmware through Odin3?
Click to expand...
Click to collapse
i now flashed to 4.0.4 and got stuck on rethink possible screen too, im almost giving up ._. nothing seems to work x_x.
Don't give up just yet. Try going all the way back to i777uckh7 firmware. If it doesn't boot. Power off, reboot recovery, wipe data/factory reset, then reboot. If successful, save ur EFS folder 1st, back it up with an app or Root Explorer, etc. Save it in a few places, external sdcard, pc. Then u could proceed to update to JB or wherever u r wanting to go.
Sent from my Nexus 5 using Tapatalk
I agree with 4-2ndtwin. Don't give up, and follow his suggestion.
In fact proceed according to the following sequence. If Step 1 solves the issue, stop there, otherwise proceed to step 2, and then if necessary step 3.
Step 1) 4-2ndtwin's suggestion. Download "I777UCKH7-CL503881 FULL tar.md5" from the section titled I777UCKH7-CL503881 Stock Binaries. Flash with Odin3 v1.85 (preferred version). Perform wipe data/factory reset from within recovery.
Step 2) Download the Tar version of Siyah 2.6.14 Kernel. Flash it in PDA. Without ticking Re-Partitioning. Next repeat Step 1 above.
Step 3) Download the SBL Bootloader from the Download Repository. Flash it as PDA in ODIN, without ticking Re-Partitioning. (Please observe normal bootloader flashing caution.) Next repeat Step 2 above.
To recap the above for clarity:
Step 1 - I777UCKH7 full distribution --> wipe data/factory reset
Step 2 - SiyahKernel v2.6.14 --> I777UCKH7 full distribution --> wipe data/factory reset
Step 3 - Secondary Bootloader --> SiyahKernel v2.6.14 --> I777UCKH7 full distribution --> wipe data/factory reset

Categories

Resources