Related
Hello,
I've tried before, and was unsuccessful. I am on a small regional carrier and when flashing MIUI, my 3g or 1x data connection does not work and reception is very very poor due to being on a verizon radio. I have accuired my carreirs ODIN files, but running linux I use Heimdall. However, I've extracted the files and have the modem.bin file. When I flash this over my MIUI ROM, and try to reboot, I get some wiered error where MIUI wont even boot up. I don't remember the error and am at work currently(which is the reason for the spelling errors also, sorry).
My proccess is:
1. Install MIUI from stock
2. Boot and install Glitch V12
3. Flash new modem.bin through Heimdall using Atlas 2.2.1 pit file(a pit file is required correct?)
Am I doing something wrong? Is the correct way
1. Flash Phone to stock with carriers radio
2. Install MIUI
3. Yada Yada
Everything works currently but data, I have to connect to WIFI. Any suggestions for me?
I'm not positive because i'm on Verizon and have never had to do this but I believe using the pit file when you flash the modem is your problem..try doing everything you said in the same order but when it comes to the part about flashing the modem do not use the pit file that is used only when you repartition, so no needed for that
Sent from my SCH-I500 using XDA App
Correct me if I'm wrong(probably am), but don't you have to populate the .pit file portion in order for odin to flash?
Sent me alink to the modem.bin i will prepare a cwm flashable zip for you.
That would be awsome demetris, it'll be about 2 hours before I will be able to do that as I am currently at work. I'll post it up here soon. Thank you
kyleco said:
Correct me if I'm wrong(probably am), but don't you have to populate the .pit file portion in order for odin to flash?
Click to expand...
Click to collapse
nope you don't have to populate the pit section to flash..you just need to use the pda button only, (never the phone button) if you were using an official VZW rom.tar and you wanted to repartition, then you would use the pit section but unless your repartitioning, it's not a requirement for Odin to flash, and would actually cause problems using a pit file with out an official VZW.tar...which is why I think you were having the issues trying to flash a modem with a pit file.
Edit: i'm sorry I just realized the instructions I just gave were for Odin and you're using heimdal...or wait...are you using Odin or heimdal?? I would wait for the previous posters cwm zip, because i'm unsure of heimdal's exact instructions, unless you are using Odin? but I still think your problems stems from using the pit with the modem
Sent from my SCH-I500 using XDA App
I am using Heimdall, and now that I am at my laptop, you do have to load a .pit file in order to add a partion portion(such as a modem) here is the modem.bin file demetris. I really appreciate the .zip file man! I'm hoping this helps me. Now I just need to find a way to push my carriers prl file to my phone so it stops pushing to verizon update.
Demetris, if you know how to make a .zip for a prl file, here is the .prl for my also.
I owe you one for this,
Thanks everyone!
What fascinate you got there, it seems modem is bigger than galaxy s family,
i think is the verizon cdma and i need to know where that modem lies in the partition.
Anyway i made one with the stantard bml12 partition that all galaxy s modems are i hope is the same on cdma
Here it is:
http://www.multiupload.com/AL7IBCDKMB
Flash it with CWM.
If you need an odin one just ask
I've got the version version of the fascinate. I500. I'll give this zip a try. Thanks again
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 .
Does anyone have the pit file for this phone? Need to repartition. Found it for the n7000 but not the i717. Thanks in advance.
Oh sure. Lots of people have it.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
If you go to samfirware.com you will see which Pit's go with each firmware, 512 is the most common, dont risk it...check!
I'm pretty sure they are available there as well...
and do not !!!...change the file names inside the tarballs....= instant brick...IMHO
And I did a little searching for you...see if this helps as well....g
http://forum.xda-developers.com/showthread.php?t=999097
ntellegence said:
Does anyone have the pit file for this phone? Need to repartition. Found it for the n7000 but not the i717. Thanks in advance.
Click to expand...
Click to collapse
Did you ever get this? I'm currently unable to mount my internal SD or move apps to it even though its practically empty. I think I need to re-partition and from what I've read the past few hours you need a PIT file to do it.
Need PIT file i717 AT&T
Please help guys!
Don't search in all internet resources, pit file 16Gb to Odin for my Samsung Galaxy Note 16Gb AT&T.Everybody search this file?Please give me to my e-mail ([email protected],[email protected])
Big thank you!!!
Sorry on my Engllish!)
Pit file is found with the stock firmware image.
Samfirmware.com will have what you need ...g
Not found
gregsarg said:
Pit file is found with the stock firmware image.
Samfirmware.com will have what you need ...g
Click to expand...
Click to collapse
I'm not found for AT&T model i717 : (Only firmware download & flashguide (not worked download,file deleted)
Please tell us the problems you are having.
You should be able to Odin push a stock firmware image to the device using Odin3, version 1.85.
This will correct your partition issue....g
Problem
gregsarg said:
Please tell us the problems you are having.
You should be able to Odin push a stock firmware image to the device using Odin3, version 1.85.
This will correct your partition issue....g
Click to expand...
Click to collapse
My memory devicee is a small, not 16GB and 3GB for using.
Thanks, I solved the problem by using the official program update KIES and pit file is not needed.
My mobile is worked!10,63Gb for using)))
Began to work better.
but do not give up on the presence of a pit file if anyone has it.([email protected])
____________________
(Google translator,sorry!)
As stated ....Odin and Kies will manage the partitions for you.
I'm glad you are up and going again ...g
i just DLed the lastest firmware from samfirmware and went through the Odin process BUT my phone is stuck at the white screen with the ATT world logo amd wont go anywhere.
any help would be greatly appreciated, thank you
Teufel Hunden said:
i just DLed the lastest firmware from samfirmware and went through the Odin process BUT my phone is stuck at the white screen with the ATT world logo amd wont go anywhere.
any help would be greatly appreciated, thank you
Click to expand...
Click to collapse
boot into stock recovery and do a factory reset, forgot what its called exactly but you get what i mean. its takes a while to boot and may even go through the boot cycle twice so give it some time.
dzee206 said:
boot into stock recovery and do a factory reset, forgot what its called exactly but you get what i mean. its takes a while to boot and may even go through the boot cycle twice so give it some time.
Click to expand...
Click to collapse
I'll give it a try
---------- Post added at 10:37 PM ---------- Previous post was at 10:20 PM ----------
dzee206 said:
boot into stock recovery and do a factory reset, forgot what its called exactly but you get what i mean. its takes a while to boot and may even go through the boot cycle twice so give it some time.
Click to expand...
Click to collapse
It worked ! thanks man?
Sorry guys for bump old thread, but did anyone already has the .pit file for this phone?
thanks
kendokar said:
Sorry guys for bump old thread, but did anyone already has the .pit file for this phone?
thanks
Click to expand...
Click to collapse
Same request. Didn't find any traces of it over the whole internet.
Here we go! Zipped original .pit file is in attachment. Pulled it out of my phone.
blazingcherub said:
Here we go! Zipped original .pit file is in attachment. Pulled it out of my phone.
Click to expand...
Click to collapse
Will this PIt file work on i717d ?
Here we go:
I was trying to install a custom rom today (done it about 20 times before on different devices including this one).
Had rooted stock & CWM custom bootloader (unlocked using Casual months ago I think).
Flashed custom rom and (unfortunately) downloaded and flashed a file for the international version (GT-N7100).
Basically, I accidentally flashed the MJ5 custom bootloader by accident (again, it's for international version, which I have SCH-i605).
It's from here under the SPECIAL INSTRUCTIONS FOR 3.6 AND ABOVE heading
(don't ask why, I'm an idiot. Was trying to install this rom and just totally blew past the fact it was for international version)
I've tried using odin to flash "KIES_HOME_I605VRAMC3_I605VZWAMC3_1098177_REV04_user_low_ship.tar.md5" (stock rom) and "sch-i605-16gb.pit" as outlined in the countless 'Restore to stock rom/bootloader from bricked state' articles out there on the webs but it keeps failing. (Part 1b from here)
Current symptoms:
Boot loop almost instant at samsung logo with new N7100 line. Will not boot into bootloader but I can get it into odin download mode.
Using Odin3 v 3.07 (on multiple computers with the right drivers I'm pretty sure) I go into download mode and this is listed:
ODIN MODE
PRODUCT NAME: GT-N7100
CUSTOM BINARY DOWNLOAD: NO
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
WARRANTY BIT: 0
Odin hangs at 'Get PIT for mapping' if re-partition is checked, outputs the following if re-partition is unchecked (only auto-reboot and F. Reset Time checked)
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> boot.img
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
After this point, it's like the phone stops responding to odin, because if I try to flash again or flash something else, odin just outputs:
<OSM> All threads completed. (succeed 0 / failed 0)
I've been at it for about 8 hours now and I know I'm getting desperate, so I'm hoping you all can help me out before I resort to new phone/sending in for factory reset
Thanks!
- John
Which stock rom are you trying to put back
Sent from my SCH-I605 using XDA Premium 4 mobile app
---------- Post added at 10:35 AM ---------- Previous post was at 10:33 AM ----------
Is the Samsung logo Blickling or is stable
thanks,
chat/email : [email protected]
Sorry to say John but that's not a soft brick. Flashing a bootloader for another device causes a hard brick which willl require a JTAG.
nikhil.kdhand said:
Which stock rom are you trying to put back
Sent from my SCH-I605 using XDA Premium 4 mobile app
---------- Post added at 10:35 AM ---------- Previous post was at 10:33 AM ----------
Is the Samsung logo Blickling or is stable
thanks,
chat/email : [email protected]
Click to expand...
Click to collapse
Everything you ask is in the op.
Samsung logo not stable.
Stock rom he's trying to flash is vramc3 4.1.2
Sent from my SCH-I605 using Tapatalk
Re: JTAG
Hälftebyte said:
Sorry to say John but that's not a soft brick. Flashing a bootloader for another device causes a hard brick which willl require a JTAG.
Everything you ask is in the op.
Samsung logo not stable.
Stock rom he's trying to flash is vramc3 4.1.2
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
Ah, thanks for clearing that up. Guess it's JTAG repair time. I went ahead and purchased a JTAG repair from mobiletechvideos[dot]mybigcommerce[dot]com (Sorry, I haven't posted enough on my account to put outside links in)
For $50, I think it'll be worth having my baby back.
Thanks for your help!
- John Miller
he1calledbubba said:
Ah, thanks for clearing that up. Guess it's JTAG repair time. I went ahead and purchased a JTAG repair from mobiletechvideos[dot]mybigcommerce[dot]com (Sorry, I haven't posted enough on my account to put outside links in)
For $50, I think it'll be worth having my baby back.
Thanks for your help!
- John Miller
Click to expand...
Click to collapse
Yeah many people use him. He's also here on XDA.
Let us know how it turns out. :good:
I actually did the exact thing you did. I can flash other roms, but can't get the radio back or flash AOSP roms. Can you let me know how the JTAG goes? I need to do it, too. It's either that or upgrade to a note 3.
Could you guys give me a recommendation on the one I should choose?
Also. I don't mean to sound like a "noob" or anything, but would it be possible to just flash the i605 bootloader back?
Numzi said:
I actually did the exact thing you did. I can flash other roms, but can't get the radio back or flash AOSP roms. Can you let me know how the JTAG goes? I need to do it, too. It's either that or upgrade to a note 3.
Could you guys give me a recommendation on the one I should choose?
Also. I don't mean to sound like a "noob" or anything, but would it be possible to just flash the i605 bootloader back?
Click to expand...
Click to collapse
Sounds like you have a different issue. Have you tried reverting to stock? If you can flash roms fine then you should be able to go back to stock which would return you to i605 radio and bootloader. If you go back to stock and still have no radio then you probably borked your efs
Sent from my SCH-I605 using Tapatalk
Hälftebyte said:
Sounds like you have a different issue. Have you tried reverting to stock? If you can flash roms fine then you should be able to go back to stock which would return you to i605 radio and bootloader. If you go back to stock and still have no radio then you probably borked your efs
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
I have tried doing that, but Odin gets stuck on different things. I cant even repartition with the i605 pit file. But it lets me repartition with the N7100 one. Also, I cant flash the stock rom as it gets stuck on sboot, but if I use 66root one, it goes through, but doesn't run properly. (Odin also allows me to flash the N7100 stock file.)
The bootloader baseline file also gets stuck on tz.img. (Unless I'm using the wrong one, but I'm sure I'm not)
I kind of lost hope in restoring my phone to normal. if I flash a 4.3 TW Rom, it works fine, but the radio doesnt read. If I flash a 4.1.2 Rom, it works fine and I might or might not get signal, but data doesnt work and my internal memory reads 0/0. Any ideas?
Sent from my SCH-I605 using xda app-developers app
Numzi said:
I have tried doing that, but Odin gets stuck on different things. I cant even repartition with the i605 pit file. But it lets me repartition with the N7100 one. Also, I cant flash the stock rom as it gets stuck on sboot, but if I use 66root one, it goes through, but doesn't run properly. (Odin also allows me to flash the N7100 stock file.)
The bootloader baseline file also gets stuck on tz.img. (Unless I'm using the wrong one, but I'm sure I'm not)
I kind of lost hope in restoring my phone to normal. if I flash a 4.3 TW Rom, it works fine, but the radio doesnt read. If I flash a 4.1.2 Rom, it works fine and I might or might not get signal, but data doesnt work and my internal memory reads 0/0. Any ideas?
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
Most likely you're going to need JTAG if you really want to be back to original. If not there are a few things I would try.
Anyway, from what I'm reading you're on an N7100 bootloader so that's why you're able to repartition with the N7100 pit file. You're pretty lucky you're even able to repartition to be honest.
What happens when you flash the N7100 stock rom? Are you able to boot?
Are you using your phone on the Verizon network?
Btw, the reason root66 works is because it only contains the system partition. There's no sboot, boot, modem etc in there to conflict with the N7100 bootloader you currently have. But of course it will have issues since the i605 system image won't jell well with N7100 boot, etc.
Sent from my SCH-I605 using Tapatalk
Hälftebyte said:
Most likely you're going to need JTAG if you really want to be back to original. If not there are a few things I would try.
Anyway, from what I'm reading you're on an N7100 bootloader so that's why you're able to repartition with the N7100 pit file. You're pretty lucky you're even able to repartition to be honest.
What happens when you flash the N7100 stock rom? Are you able to boot?
Are you using your phone on the Verizon network?
Btw, the reason root66 works is because it only contains the system partition. There's no sboot, boot, modem etc in there to conflict with the N7100 bootloader you currently have. But of course it will have issues since the i605 system image won't jell well with N7100 boot, etc.
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
If I could avoid JTagging it would be preferred haha. I don't care about going back to complete original (stock) if that's what you mean. I just want to get my Radio to read while being able to access my storage and data because I'm pretty happy with the 4.3 Touchwiz Rom (at least for now).
When I flash the N7100 stock rom, I can boot. It boot loops until I go into recovery and format data/cache and after that it works fine, with no radio service. Also, I have always been using my phone on the H2O Wireless network with APN settings. But now, the radio doesn't read at all and shows no imei and what not. However if I go back to Jedi X 19 (was my daily 4.1.2 TW driver), the radio reads and I have my imei, but I can't get data and it says my memory is full (can't open gallery and my internal SD says 0/0 bytes).
I know about root66, but what I don't understand is why I was able to flash to the N7100 bootloader and now can't flash back to the i605 one. Is there a specific reason for that?
Btw, Thanks for trying to help me right now. Really appreciated.
Numzi said:
If I could avoid JTagging it would be preferred haha. I don't care about going back to complete original (stock) if that's what you mean. I just want to get my Radio to read while being able to access my storage and data because I'm pretty happy with the 4.3 Touchwiz Rom (at least for now).
When I flash the N7100 stock rom, I can boot. It boot loops until I go into recovery and format data/cache and after that it works fine, with no radio service. Also, I have always been using my phone on the H2O Wireless network with APN settings. But now, the radio doesn't read at all and shows no imei and what not. However if I go back to Jedi X 19 (was my daily 4.1.2 TW driver), the radio reads and I have my imei, but I can't get data and it says my memory is full (can't open gallery and my internal SD says 0/0 bytes).
I know about root66, but what I don't understand is why I was able to flash to the N7100 bootloader and now can't flash back to the i605 one. Is there a specific reason for that?
Btw, Thanks for trying to help me right now. Really appreciated.
Click to expand...
Click to collapse
Okay, I doubt what I was thinking of is going to work then. I was thinking you should flash the N7105 modem while you're on the N7100 rom. Maybe you can try that or maybe try flashing the i605 modem there's always the risk of fully bricking it though.
If that doesn't work I would try using Heimdall to flash the I605 pit file and sboot.bin.
Heimdall sometimes works in cases where Odin fails (according to a JTAG guy a spoke to once)
I have no problem helping. I have three motherboards myself, two of which i experiment with. One is bricked, one is water damaged and semi bricked (no efs, imei, internal memory only works on 4.3 TW) and one is fully functional :laugh:
Hälftebyte said:
Okay, I doubt what I was thinking of is going to work then. I was thinking you should flash the N7105 modem while you're on the N7100 rom. Maybe you can try that or maybe try flashing the i605 modem there's always the risk of fully bricking it though.
If that doesn't work I would try using Heimdall to flash the I605 pit file and sboot.bin.
Heimdall sometimes works in cases where Odin fails (according to a JTAG guy a spoke to once)
I have no problem helping. I have three motherboards myself, two of which i experiment with. One is bricked, one is water damaged and semi bricked (no efs, imei, internal memory only works on 4.3 TW) and one is fully functional :laugh:
Click to expand...
Click to collapse
Well at this point, I was already ready to send it for JTag repair so I'll try anything. Would you mind letting me know which N7105 modem I should flash? I've already tried i605 modems (not through Odin though) and they haven't worked.
I'm a bit confused with how to use Heimdall and where to find sboot for i605. I have it and wanted to try it, but was lost haha.
Oh that's great lolol. Mine is like yours for internal memory right now. I have a back up of my efs folder, but when I restore it, it doesn't read it.
Numzi said:
Well at this point, I was already ready to send it for JTag repair so I'll try anything. Would you mind letting me know which N7105 modem I should flash? I've already tried i605 modems (not through Odin though) and they haven't worked.
I'm a bit confused with how to use Heimdall and where to find sboot for i605. I have it and wanted to try it, but was lost haha.
Oh that's great lolol. Mine is like yours for internal memory right now. I have a back up of my efs folder, but when I restore it, it doesn't read it.
Click to expand...
Click to collapse
If you have CWM or TWRP you could try one of these flashable modems from here http://forum.xda-developers.com/showthread.php?t=2031575
As I said this might brick you fully
Heimdall is pretty easy after you get the hang of it. After download you will need to setup the drivers with the zadig.exe installer. I would use a different usb port from the one you currently use for Odin so you don't have to reinstall samsung drivers whenever you want to use Odin. You should find a tutorial easily to get started. If you need more help I can go into a bit more detail.
To access the files that Heimdall will need (sboot.bin, boot, tz, system, param, modem.bin etc ), make a copy of the tar.md5 rom file you have. Remove the .md5 at the end and use 7z to extract the contents. You will see all the separate files needed for each partition.
The fact that you can actually repartition sounds good though. I feel like if you can get the I605 sboot.bin (bootloader) flashed, you can then partition with the I605 PIT. This is all speculation though :fingers-crossed:
Hälftebyte said:
If you have CWM or TWRP you could try one of these flashable modems from here http://forum.xda-developers.com/showthread.php?t=2031575
As I said this might brick you fully
Heimdall is pretty easy after you get the hang of it. After download you will need to setup the drivers with the zadig.exe installer. I would use a different usb port from the one you currently use for Odin so you don't have to reinstall samsung drivers whenever you want to use Odin. You should find a tutorial easily to get started. If you need more help I can go into a bit more detail.
To access the files that Heimdall will need (sboot.bin, boot, tz, system, param, modem.bin etc ), make a copy of the tar.md5 rom file you have. Remove the .md5 at the end and use 7z to extract the contents. You will see all the separate files needed for each partition.
The fact that you can actually repartition sounds good though. I feel like if you can get the I605 sboot.bin (bootloader) flashed, you can then partition with the I605 PIT. This is all speculation though :fingers-crossed:
Click to expand...
Click to collapse
I got it. Alright then I will try this tomorrow when I finish classes (It's 3am right now and I have to wake up in 4 hours). I'll post here with the result! This is a new suggestion for this, so I'm kind of nervous/excited about the result. haha.
Just think of it as another experiment for you. Fingers crossed. I'll let you know and thanks so much.
Numzi said:
I got it. Alright then I will try this tomorrow when I finish classes (It's 3am right now and I have to wake up in 4 hours). I'll post here with the result! This is a new suggestion for this, so I'm kind of nervous/excited about the result. haha.
Just think of it as another experiment for you. Fingers crossed. I'll let you know and thanks so much.
Click to expand...
Click to collapse
Also in case you didn't realize, since everything except internal storage works in JediX19, when installing Jedi you can install the swap script, FAT32 script (no need to format external sd card). Then you will have 'internal storage' and a signal. Not the best solution but a workaround. Not many roms have the swap script option so I guess you'd be stuck on Jedi if you choose this route.
Hälftebyte said:
Also in case you didn't realize, since everything except internal storage works in JediX19, when installing Jedi you can install the swap script, FAT32 script (no need to format external sd card). Then you will have 'internal storage' and a signal. Not the best solution but a workaround. Not many roms have the swap script option so I guess you'd be stuck on Jedi if you choose this route.
Click to expand...
Click to collapse
So Heimdall didn't work - it failed repartitioning and when I tried unchecking that, failed at bootloader, then at cache, etc. Do you think it's wiser for me to first try flashing the modem then do the SD Swap? or to just do the SD Swap thing on Jedi?
EDIT: I just did the FAT32 script and the internal storage (which is actually my ext SD card), still says 0/0 bytes...
Numzi said:
...
EDIT: I just did the FAT32 script and the internal storage (which is actually my ext SD card), still says 0/0 bytes...
Click to expand...
Click to collapse
Strange it works for me. Otherwise I only have internal memory when I'm on TW 4.3
I guess there's not much more experimenting to do
Hälftebyte said:
Strange it works for me. Otherwise I only have internal memory when I'm on TW 4.3
I guess there's not much more experimenting to do
Click to expand...
Click to collapse
I'll keep trying to see if the Swap could work eventually. I'll just stick with Jedi or the 4.3 rom until I JTag repair in 2 weeks. Thanks for your help. I really appreciate it.
Numzi said:
I'll keep trying to see if the Swap could work eventually. I'll just stick with Jedi or the 4.3 rom until I JTag repair in 2 weeks. Thanks for your help. I really appreciate it.
Click to expand...
Click to collapse
No prob. Good luck. It looked so hopeful with you being able to partition. :good:
Hälftebyte said:
No prob. Good luck. It looked so hopeful with you being able to partition. :good:
Click to expand...
Click to collapse
I decided to just get the JTag service now and just paid for it. I'll let you know if it really goes back to perfect.
I was flashing a rom onto my galaxy s4 and I've noticed that it couldn't receive OTA updates before but I never updated so it didn't affect me much until today when I tried flashing a rom and the code turned red and it says SW REV. Check FAIL: fused:5. Binary: 3, I also tried using odin downloader to flash VRAUME7 back onto it but said it encountered a error in line 27. After I tried using Kies downloader to update the software but it says firmware upgrade encountered an issue please select recovery mode in Kies but when I used recovery mode in keis it says it encountered a problem while updating, I'm out of ideas could someone please help
af_nm said:
I was flashing a rom onto my galaxy s4 and I've noticed that it couldn't receive OTA updates before but I never updated so it didn't affect me much until today when I tried flashing a rom and the code turned red and it says SW REV. Check FAIL: fused:5. Binary: 3, I also tried using odin downloader to flash VRAUME7 back onto it but said it encountered a error in line 27. After I tried using Kies downloader to update the software but it says firmware upgrade encountered an issue please select recovery mode in Kies but when I used recovery mode in keis it says it encountered a problem while updating, I'm out of ideas could someone please help
Click to expand...
Click to collapse
Fused 5 means you need to flash either mj7 or mk2 .
I'd do the full wipe at this point. If one doesn't work right at first... Try the other. Do you recall which your phone was on prior to this?
Sent From My Verizon S4
af_nm said:
I was flashing a rom onto my galaxy s4 and I've noticed that it couldn't receive OTA updates before but I never updated so it didn't affect me much until today when I tried flashing a rom and the code turned red and it says SW REV. Check FAIL: fused:5. Binary: 3, I also tried using odin downloader to flash VRAUME7 back onto it but said it encountered a error in line 27. After I tried using Kies downloader to update the software but it says firmware upgrade encountered an issue please select recovery mode in Kies but when I used recovery mode in keis it says it encountered a problem while updating, I'm out of ideas could someone please help
Click to expand...
Click to collapse
so what is your base build number?
what rom were you trying to flash
are you loki'd or safestrap?
decaturbob said:
so what is your base build number?
what rom were you trying to flash
are you loki'd or safestrap?
Click to expand...
Click to collapse
Yea I don't know either.. I just saw that Odin error then I saw me7. Figured op tried flashing the wrong one. It is a bit confusing though with no actual info to go on.
Sent From My Verizon S4
decaturbob said:
so what is your base build number?
what rom were you trying to flash
are you loki'd or safestrap?
Click to expand...
Click to collapse
Verizon SCH-I545
a rom called premium but I didn't even get to download it before the red code started
and lastly I rooted using loki'd, sorry for the lack of info
af_nm said:
Verizon SCH-I545
a rom called premium but I didn't even get to download it before the red code started
and lastly I rooted using loki'd, sorry for the lack of info
Click to expand...
Click to collapse
OK well if you can get back into download mode then flash the MDK tar . I'm not really sure if you were flashing a rom in Odin or a custom recovery but in any case if all else fails.... Odin mdk
Sent From My Verizon S4
With the new knox security trying to flash a prior firmware will trip the flag so it's advised to be careful when flashing images via Odin. Flash an earlier version that doesn't take and you'll lose the warranty on your phone.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
would reinstalling the pit files work?
odin mdk
Mistertac said:
OK well if you can get back into download mode then flash the MDK tar . I'm not really sure if you were flashing a rom in Odin or a custom recovery but in any case if all else fails.... Odin mdk
Sent From My Verizon S4
Click to expand...
Click to collapse
I ended up trying to flash using odin mdk and even that refused to work is there anything else I can try
af_nm said:
I ended up trying to flash using odin mdk and even that refused to work is there anything else I can try
Click to expand...
Click to collapse
I have to admit, I am really confused by your posts. I have no idea what you were, or are, trying to do. Are you SURE you were on MDK? If you weren't on MDK, you need to Odin back to the build you were on.
Sent from my NCC-1701 using Tapatalk 4
riker147 said:
I have to admit, I am really confused by your posts. I have no idea what you were, or are, trying to do. Are you SURE you were on MDK? If you weren't on MDK, you need to Odin back to the build you were on.
Sent from my NCC-1701 using Tapatalk 4
Click to expand...
Click to collapse
same here, I'm not sure what he has or what he has done........
decaturbob said:
same here, I'm not sure what he has or what he has done........
Click to expand...
Click to collapse
I know it... It we can know exactly where you were before. Like did you have this s4 since new when they shipped with mdk? Did u root it yourself then Loki? Install cwm or twrp? Things are kinda confusing. Just figured you were on mdk but I've seen stranger posts on here when in the end the op actually didn't have mdk or wasn't even on e Verizon s4.
Sent From My Verizon S4
Mistertac said:
I know it... It we can know exactly where you were before. Like did you have this s4 since new when they shipped with mdk? Did u root it yourself then Loki? Install cwm or twrp? Things are kinda confusing. Just figured you were on mdk but I've seen stranger posts on here when in the end the op actually didn't have mdk or wasn't even on e Verizon s4.
Sent From My Verizon S4
Click to expand...
Click to collapse
The OP says that it said "Fused:5" means he is on MJ7 or MK2. It may have been on MDK and Loki'd at one point, but it's now MJ7/MK2 and needs to be recovered using one of those ROM images - NOT MDK.
k1mu said:
The OP says that it said "Fused:5" means he is on MJ7 or MK2. It may have been on MDK and Loki'd at one point, but it's now MJ7/MK2 and needs to be recovered using one of those ROM images - NOT MDK.
Click to expand...
Click to collapse
Yea good call I think I was actually confusing posts when I was responding earlier. Forgot about the fused 5. Thanks .
Sent From My Verizon S4
riker147 said:
I have to admit, I am really confused by your posts. I have no idea what you were, or are, trying to do. Are you SURE you were on MDK? If you weren't on MDK, you need to Odin back to the build you were on.
Sent from my NCC-1701 using Tapatalk 4
Click to expand...
Click to collapse
No it was shipped with vruame7 and I was never able to update after I rooted so it's always been on vraume7 I used loki'd when I rooted. Ive tried using mj7 and mk2 and used this http://forum.xda-developers.com/showthread.php?t=2507253. when I ran it in odin it ran until it stopped at system.img.ext4 followed by complete(Write) operation failed and on the top left of my phone it says START [224,1440] and BAR [240,1440]
af_nm said:
No it was shipped with vruame7 and I was never able to update after I rooted so it's always been on vraume7 I used loki'd when I rooted. Ive tried using mj7 and mk2 as well but I can't find one that will work
Click to expand...
Click to collapse
If it came with VRUAME7 then you didnt use the Loki method to root. If you want help you should post more logs/info. Like your last sentence "Ive tried using mj7 and mk2 as well but I can't find one that will work" can you elaborate on that? Saying you cant find one that works suggests you've found ones that dont work. But what does "don't work" consist of? It could be "write error", md5 mismatch, "PIT partition not found", "SW Rev check fail..", wrong file etc.
Check that the Odin tar file name says "VRUEMJ7" or "VRUEMK2" in it and ends in tar.md5 and make sure the md5 matches. If that fails then post back with logs/info that will actually assist us in helping you troubleshoot
Sent from my SCH-I545 using XDA Premium 4 mobile app
Surge1223 said:
If it came with VRUAME7 then you didnt use the Loki method to root. If you want help you should post more logs/info. Like your last sentence "Ive tried using mj7 and mk2 as well but I can't find one that will work" can you elaborate on that? Saying you cant find one that works suggests you've found ones that dont work. But what does "don't work" consist of? It could be "write error", md5 mismatch, "PIT partition not found", "SW Rev check fail..", wrong file etc.
Check that the Odin tar file name says "VRUEMJ7" or "VRUEMK2" in it and ends in tar.md5 and make sure the md5 matches. If that fails then post back with logs/info that will actually assist us in helping you troubleshoot
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No I converted my SD card to EXFAT and downloaded the root onto the rom so I was mistaken I didn't use loki sorry. I just ran this factory image which is for mj7 http://forum.xda-developers.com/showthread.php?t=2507253. I confirmed it was for mj7 after the MD5 file downloaded and ran it using odin, it went fine until it got to system.img.ext4 followed by complete(Write) operation failed and on the top left of my phone it says START [224,1440] and BAR [240,1440] in red and the flash failed. I hope this is more helpful
af_nm said:
No I converted my SD card to EXFAT and downloaded the root onto the rom so I was mistaken I didn't use loki sorry. I just ran this factory image which is for mj7 http://forum.xda-developers.com/showthread.php?t=2507253. I confirmed it was for mj7 after the MD5 file downloaded and ran it using odin, it went fine until it got to system.img.ext4 followed by complete(Write) operation failed and on the top left of my phone it says START [224,1440] and BAR [240,1440] in red and the flash failed. I hope this is more helpful
Click to expand...
Click to collapse
Yes thats much better, gives a lot more info that we can use to help Follow the directions I give here and download and use the pit file I uploaded in this thread, you can find it towards the bottom under the "Full-wipe" directions. Post back and let us know if it worked or if you need more help. Hope this helps.
Surge1223 said:
Yes thats much better, gives a lot more info that we can use to help Follow the directions I give here and download and use the pit file I uploaded in this thread, you can find it towards the bottom under the "Full-wipe" directions. Post back and let us know if it worked or if you need more help. Hope this helps.
Click to expand...
Click to collapse
So I followed the directions to flash the system.img.ext4 file and I already extracted it and am uploading it using heimdall. I have the pit file ready and I put the system.img.ext4 in under SYSTEM, added then removed it but it won't let me flash once it's removed and if I do flash with it on there it says ERROR: Failed to access device. libusb error: -12. I have deleted kies and reinstalled Samsung drivers, any ideas
af_nm said:
So I followed the directions to flash the system.img.ext4 file and I already extracted it and am uploading it using heimdall. I have the pit file ready and I put the system.img.ext4 in under SYSTEM, added then removed it but it won't let me flash once it's removed and if I do flash with it on there it says ERROR: Failed to access device. libusb error: -12. I have deleted kies and reinstalled Samsung drivers, any ideas
Click to expand...
Click to collapse
Driver issue 99% of the time make sure you've uninstalled all Samsung drivers. Use windows' control panel option to uninstall programs and make sure all kies, samsung, and verizon related stuff is uninstalled. Then reboot the pc, let your phone install the drivers for your pc, and try using a different usb port with the stock oem cable. Also make sure adb isn't running in the background
Sent from my SCH-I545 using XDA Premium 4 mobile app