Related
Hi to all, guys, I need your help in this situation: I try to install CWM on S5830i thru flashing zip from SD, after flashing my phone take reboot, after this I got black screen. I wait approx 10 minutes, and then try to enter recovery mode (power+home+vol up) - nothing, I got black screen again. I try to enter ODIN mode (power+BOTH volume keys), with sucsess, so I understood that the only way to rise up my phone is USB flashing. I download all needed drivers and ODIN v1.85 (also I try to connect them with ODIN 4.38, but he cant se phone even with manually writing COM port). So, I download stock firmware S5830iXXKK5.tar, put tis file on PDA and begin flashing. I got this:
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003>
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
It was surprised me, because I read that there is no needed PID file for stock firmware. I try google PID for my phone, but with no result.
If you have any ideas how rise up this dead phone to ANY firmware, please help. Thanks a lot.
i´m not really sure about what difference between generic gt-s5830 and gt-s5830i, but did u use correct ops file? i mean the cooper.ops file.
the ops file define correct partition layout, and if u use incompatible ops that will result in a whole lot mess including bricking.
So you need Odin 1.85,drivers and here's the PDA file for Odin.
http://www.4shared.com/file/Ls2CAsHv/PDA.html
an0nym0us_ said:
i´m not really sure about what difference between generic gt-s5830 and gt-s5830i, but did u use correct ops file? i mean the cooper.ops file.
the ops file define correct partition layout, and if u use incompatible ops that will result in a whole lot mess including bricking.
Click to expand...
Click to collapse
i-series have other processor and video accelerator. http://forum.xda-developers.com/showthread.php?t=1459479
ickyyy said:
So you need Odin 1.85,drivers and here's the PDA file for Odin.
Click to expand...
Click to collapse
I try your PDA file, but have the same error, could you pls see screenshot?
varvsn said:
I try your PDA file, but have the same error, could you pls see screenshot?
Click to expand...
Click to collapse
why u use that odin? does gt-s5830i really need to use that odin?
afaik odin v3.xx or v4.xx that we regularly use doesnt have that pit tabs, intead we use ops.
moreover if u really need to use that odin, why is the pit tabs empty? its obvious by the pit error in the log that it cannot find pit file. lol
an0nym0us_ said:
why u use that odin? does gt-s5830i really need to use that odin?
afaik odin v3.xx or v4.xx that we regularly use doesnt have that pit tabs, intead we use ops.
moreover if u really need to use that odin, why is the pit tabs empty? its obvious by the pit error in the log that it cannot find pit file. lol
Click to expand...
Click to collapse
If you read again my first post:
(also I try to connect them with ODIN 4.38, but he cant see phone even with manually writing COM port)
So if you explain, why older version is working fine instead of 4.38, or take me some ideas, how I can use "right" ODIN, it will be great.
PIT = where you should place your .ops probably
varvsn said:
If you read again my first post:
(also I try to connect them with ODIN 4.38, but he cant see phone even with manually writing COM port)
So if you explain, why older version is working fine instead of 4.38, or take me some ideas, how I can use "right" ODIN, it will be great.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=23460922&postcount=9
EmoBoiix3 said:
PIT = where you should place your .ops probably
Click to expand...
Click to collapse
no pit's are not same as ops if i am not wrong.. other sammy devices do use pit..high end ones.
madman_amit said:
http://forum.xda-developers.com/showpost.php?p=23460922&postcount=9
no pit's are not same as ops if i am not wrong.. other sammy devices do use pit..high end ones.
Click to expand...
Click to collapse
.pit = All those with custom binary counter
.ops = All those with no custom counter
EmoBoiix3 said:
.pit = All those with custom binary counter
.ops = All those with no custom counter
Click to expand...
Click to collapse
cool ..
thats why sammy makes them locked down
madman_amit said:
http://forum.xda-developers.com/showpost.php?p=23460922&postcount=9
no pit's are not same as ops if i am not wrong.. other sammy devices do use pit..high end ones.
Click to expand...
Click to collapse
Great.. Is it mean, that my phone becomes useless break?
varvsn said:
Great.. Is it mean, that my phone becomes useless break?
Click to expand...
Click to collapse
someone will have to make pit file for your device thats the thing..
Can someone do this, guys?
Hello everyone...
I have a Galaxy SII HD LTE (SHV-E120L).
History:
The phone worked fine for 1 day, except a minor issue with sending sms. I am a total noob, however I decided to flash the TL 1.3 firmware to solve that issue. Someting went wrong in that process so, stupid as I usualy am, I started to play with the checkboxes of Odin. Result: a hard bricked 1/2 month salary worth phone
I found a JTAG shop who manage to "repair" the phone. all works fine except I cant connect to a mobile network. I did a firmware upgrade via Kies and received an error with the baseband upgrade.
The emergency recovery also ends in an error after 97% upload.
All the different firmware I try to flash via Odin gets an error when flashing the amss.bin (Complete(Write) operation failed. (see picture).
Here's the Odin error:
<ID:0/013> Odin v.3 engine (ID:13)..
<ID:0/013> File analysis..
<ID:0/013> SetupConnection..
<ID:0/013> Initialzation..
<ID:0/013> Get PIT for mapping..
<ID:0/013> Firmware update start..
<ID:0/013> boot.img
<ID:0/013> NAND Write Start!!
<ID:0/013> recovery.img
<ID:0/013> system.img.ext4
<ID:0/013> amss.bin
<ID:0/013>
<ID:0/013> Complete(Write) operation failed.
So the problem I have is:
- I can' connect to a mobile network.
- I can't flash other firmware
Am I right to say that I have a corrupt Modem - Radio - Baseband in the phone?
I know a little bit of Linux so I checked the filesystem with ADB Shell.
Can I delete certain files or change permissions or upload files from another phone to repair it?
What would you do in my place? I realy need someone to point me in the right direction. Thanks
---------------------------------------------------------------------------
The versions installed are:
Baseband: E120L.EL21.O843.LT
Kernel: 2.6.35.11-E120L.FB05.0938.CL939741
Build: GINGERBREEAD.FB05
---------------------------------------------------------------------------
No one can help me?
gs2 hd lte
did you try to flash other TL firmwares like the ics version or the GDphone one..? & make sure to find the right version for your phone E120L, not E120K or E120S; remembre that.
yakie47 said:
did you try to flash other TL firmwares like the ics version or the GDphone one..? & make sure to find the right version for your phone E120L, not E120K or E120S; remembre that.
Click to expand...
Click to collapse
Thanks for the reaction, yakie47...
I tried several firmwares beside TL (LGU+ HOME_E120L.FB05.0938_CL939741_REV00_user_low_ship, HOME_E120L.EL07.0011_CL718581_REV00_user_low_ship). Everytime Odin reaches amss.bin to flash, I get the - "Complete(Write) operation failed" - error.
I will now try the GDphone firmware and hope things will be better. I'll let you know later.
vdbergh, it seems that the problem for you is not firmware-related, but lies somewhere in the flashing process.
There're some point you may want to get before you flash the firmware, f.e.:
Do you use USB cable from the phone package?
Do you use USB port on motherboard rather than some external one?
Do you have any antivirus/firewall/any other security software disabled before flashing?
Additionally, you can try another USB port to connect the phone with.
rxulan said:
vdbergh, it seems that the problem for you is not firmware-related, but lies somewhere in the flashing process.
There're some point you may want to get before you flash the firmware, f.e.:
Do you use USB cable from the phone package?
Do you use USB port on motherboard rather than some external one?
Do you have any antivirus/firewall/any other security software disabled before flashing?
Additionally, you can try another USB port to connect the phone with.
Click to expand...
Click to collapse
Thank you for the sugestions Rxulan....
you are right that my problem is not firmware-related.
It is obvious now that it's related to the modem or baseband software, because I can flash everything except the amss.bin. What is amss.bin actually?
The phone is rooted, so is there anything I could check in the efs-directory or somewhere else?
Sould I send it back to Samsung for repair?
amss.bin is a part of modem software along with mdm.bin.
You can try ones from some stock firmware, just leave only those 2 files in the tar archive and flash the tar via PDA field.
You can download the latest firmware using Check Fus Downloader.
rxulan said:
amss.bin is a part of modem software along with mdm.bin.
You can try ones from some stock firmware, just leave only those 2 files in the tar archive and flash the tar via PDA field.
You can download the latest firmware using Check Fus Downloader.
Click to expand...
Click to collapse
I downloaded the latest stock firmware with Check Fus and left nlamss.bin and mdm.bin files in the tar. Flashing this with Odin gives the same error:
<ID:0/014> File analysis..
<ID:0/014> SetupConnection..
<ID:0/014> Initialzation..
<ID:0/014> Get PIT for mapping..
<ID:0/014> Firmware update start..
<ID:0/014> amss.bin
<ID:0/014> NAND Write Start!!
<ID:0/014>
<ID:0/014> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Help! 2 months later and still nowhere.
I can flash the boot.img, recovery.img, system.img.ext4, but not the amss.bin.
Conclusion: It's impossible to flash the modem software (amss.bin) into this phone.
Why?
What to do now?
That's weird really.
Conclusion: It's impossible to flash the modem software (amss.bin) into this phone.
Click to expand...
Click to collapse
It's definitely possible since I flashed FD03 modem onto FB05 official ROM myself.
rxulan said:
That's weird really.
It's definitely possible since I flashed FD03 modem onto FB05 official ROM myself.
Click to expand...
Click to collapse
Hi rxulan...
I've been digging a bit deeper... and have a little theory about my problem. I'm not sure but would like to have your opinion...
The modem software in my phone is corrupt.
All the firmwares I checked seem to have the same mdm.bin and amss.bin files.
Now I think that the mdm.bin file in all these firmwares are corrupt!
Why? When I try to extract the files from mdm.bin, all are ok except the amss.mbn file. Extracting that file gives me a "file is broken" error. And this happens with every firmware i tried.
Maybe you could see if you can extract the amss.mbn file from mdm.bin from your firmware?
So I think that if you're phone doesn't have a modem problem like mine, it doesn't extract the mdm.bin file from mdm.bin when flashing new firmware.
Does all this makes sence to you?
vdbergh
Well, that makes sense actually.
Try to download tar with FD03 modem software from here.
It's in russian, but it's ok, just resolve the captcha and click the green button.
EDIT: this tar can be flashed as is, no need to extract anything.
rxulan said:
vdbergh
Well, that makes sense actually.
Try to download tar with FD03 modem software from here.
It's in russian, but it's ok, just resolve the captcha and click the green button.
EDIT: this tar can be flashed as is, no need to extract anything.
Click to expand...
Click to collapse
Thanks for your help rxulan... I really appreciate this.
I downloaded the file, but flashing gives the same error as before.
When I look inside the mdm.bin file, the AMSS.MBN file is the same as in other firmware, and has the same problem of not beening able to be extracted.
(see pic)
Try for yourself and you will see that you can extract every file from amss.bin and mdm.bin except the AMSS.MBN file in mdm.bin.
That amss.bin is not needed really. It's probably just some 7zip issue with the bin package. What you need is amss.bin from the ROM directly, no need to extract anything from bin files.
So, you you did try to flash the tar given itself, without any modification, and it failed? That's really weird it can't flash amss.bin only.
No clue what can be the cause for now then. Are you sure it's not some antivirus software/etc?
Probably, it makes sense to try flashing from another computer?
rxulan said:
That amss.bin is not needed really. It's probably just some 7zip issue with the bin package. What you need is amss.bin from the ROM directly, no need to extract anything from bin files.
So, you you did try to flash the tar given itself, without any modification, and it failed? That's really weird it can't flash amss.bin only.
No clue what can be the cause for now then. Are you sure it's not some antivirus software/etc?
Probably, it makes sense to try flashing from another computer?
Click to expand...
Click to collapse
I know that I don't need to extract the .bin files, but flashing any firmware always results in error in amss.bin. I tried everything: reinstall drivers, other usb cables, other usb ports, other computer, all without result.
I am a total newbe in this but as far as I could learn, amss.bin has to do with the modem. And this is exactly the problem with my phone... I can't connect to a wireless network after JTAG hard brick recovery.
When I googled futher then I found that the AMSS.MBN file has to do with the Qualcomm baseband chip.
Now, it could be a coincidence, but I find it very strange that it's exactly this file (AMSS.MBN) that is impossible to extract. All other files in the .bin file are ok.
So I know that it's strange but I think that the amss.mbn file of all the firmwares are equal and corrupt.
The only thing I see that I can still try is to take the amss.mbn (/system/etc/firmware/amss.mbn) file from another E120L and copy it into mine.
Would you be so kind to send me this file from your phone?
No problem, here it is.
rxulan said:
No problem, here it is.
Click to expand...
Click to collapse
Thank you so much rxulan....
This file came form your phone and not from a firmware file?
It was the last thing I could come up with, but it doesn't solve my problem. I don't know anymore what to do.
Yes, this file is right from the phone.
Probably, try to update firmware with Kies? Will emergency firmware recovery work?
rxulan said:
Yes, this file is right from the phone.
Probably, try to update firmware with Kies? Will emergency firmware recovery work?
Click to expand...
Click to collapse
I tried Kies before, but that doesn't work. In firmware information I have "Your device does not support software upgrade via Kies"
Try the following. If your phone is rooted, you must have Root explorer installed.
Run Root explorer, then go to /system folder. Choose R/W permissions for the folder (see the appropriate Root explorer button in header). Long tap on build.pro file, then scroll menu down and choose to open the file in the text editor.
then change the FB05 part of ro.build.PDA value to EL22. Then tap on the phone menu button and choose save and exit. Reboot the phone and connect to Kies.
You should have firmware upgrade option available now.
rxulan said:
Try the following. If your phone is rooted, you must have Root explorer installed.
Run Root explorer, then go to /system folder. Choose R/W permissions for the folder (see the appropriate Root explorer button in header). Long tap on build.pro file, then scroll menu down and choose to open the file in the text editor.
then change the FB05 part of ro.build.PDA value to EL22. Then tap on the phone menu button and choose save and exit. Reboot the phone and connect to Kies.
You should have firmware upgrade option available now.
Click to expand...
Click to collapse
Thanks again!
I did as you explained and it worked. Kies started the upgrade but ended with an error (pic1). The emergency upgrade also ended with an error (pic2).
I have the feeling that the error is generated the moment the modem is flashed.
What could be the reason that this phone doesn't accept any updates? Could some files have the wrong permission (ro)?
I have an AT&T Branded i717 Note. And I screwed up.
I checked out the Super Everything thread (which is great!) but stupidly downloaded the Rogers stock ODIN (which seems to be a full flash - PIT, Bootloader, PDA, PHONE, and CSC).
Thank you djkid for providing it in this thread: forum.xda-developers.com/showthread.php?t=1657262
But anyway... I'm stupid because I flashed it (I know, I know, I was too eager and in a rush to flash something). Phone boots ok and everything, but it complains about the USB Storage being blank (or in an unsupported format), even though nothing is connected to it. If I put a MicroSD card in, it constantly shows "safe to remove SDCard".
I assume the partitions have been set incorrectly? I've been looking all over for an AT&T stock ODIN (that is full like the Rogers one mentioned above) but no luck. I downloaded and tried a few of the regular AT&T stock ODINs in the forum (thank you for those posts), but they only contain certain parts and they don't solve the USB / MicroSD issue I'm having.
Can anyone help?
Just go back and get rhe correct Odin3 files, put phone in download mode, start Odin, connect phone, and flash. I put the Rogers rom and modem on my phone last week (very laggy).
LaZiODROID said:
I have an AT&T Branded i717 Note. And I screwed up.
I checked out the Super Everything thread (which is great!) but stupidly downloaded the Rogers stock ODIN (which seems to be a full flash - PIT, Bootloader, PDA, PHONE, and CSC).
Thank you djkid for providing it in this thread: forum.xda-developers.com/showthread.php?t=1657262
But anyway... I'm stupid because I flashed it (I know, I know, I was too eager and in a rush to flash something). Phone boots ok and everything, but it complains about the USB Storage being blank (or in an unsupported format), even though nothing is connected to it. If I put a MicroSD card in, it constantly shows "safe to remove SDCard".
I assume the partitions have been set incorrectly? I've been looking all over for an AT&T stock ODIN (that is full like the Rogers one mentioned above) but no luck. I downloaded and tried a few of the regular AT&T stock ODINs in the forum (thank you for those posts), but they only contain certain parts and they don't solve the USB / MicroSD issue I'm having.
Can anyone help?
Click to expand...
Click to collapse
Well we all screw up once in a while. I had to return my Galaxy note to stock last night that what I would suggest you try first. if you cant connect use the usb try Airdriod to transfer the files. i used the stock att files from http://rootgalaxynote.com/ but if you cant find them let me know Ill send you what I have.
LaZiODROID said:
I downloaded and tried a few of the regular AT&T stock ODINs in the forum (thank you for those posts), but they only contain certain parts and they don't solve the USB / MicroSD issue I'm having.
Click to expand...
Click to collapse
I have flashed stock AT&T roms via Odin, but the USB Storage / MicroSD issue remains.
Is it because the stock AT&T roms I am trying only come with certain parts?
i.e. the Rogers one I flashed (found in the forum) had a few files... the PIT file, CDC file, along with the system/modem etc. None of these AT&T stock roms I have downloaded have these kinds of parts (though that isn't stopping me from trying them out of desperation)
rangercaptain said:
Just go back and get rhe correct Odin3 files, put phone in download mode, start Odin, connect phone, and flash. I put the Rogers rom and modem on my phone last week (very laggy).
Click to expand...
Click to collapse
Ditto......in my quest to unlock the RAT....g
---------- Post added at 12:38 PM ---------- Previous post was at 12:36 PM ----------
LaZiODROID said:
I have flashed stock AT&T roms via Odin, but the USB Storage / MicroSD issue remains.
Is it because the stock AT&T roms I am trying only come with certain parts?
i.e. the Rogers one I flashed (found in the forum) had a few files... the PIT file, CDC file, along with the system/modem etc. None of these AT&T stock roms I have downloaded have these kinds of parts (though that isn't stopping me from trying them out of desperation)
Click to expand...
Click to collapse
I'm quite certain that the ATT stock odin .tar file is complete...I've used it numerous times.
It has to be another issue...IMHO
And you are pulling the stock odin .tar from the everything thread ??
this is the one I'm talking about...and have used many times....g
http://forum.xda-developers.com/showthread.php?t=1506330
With all this said, do we need to add something to the Super Page? I have the off ICS odin, totally bloated by ATT , (only 1gb in size) which is on my server profile, just never push it out or added it to the Super Page. Do or should we list it...on the Super Page ?
LaZiODROID said:
I have an AT&T Branded i717 Note. And I screwed up.
I checked out the Super Everything thread (which is great!) but stupidly downloaded the Rogers stock ODIN (which seems to be a full flash - PIT, Bootloader, PDA, PHONE, and CSC).
Thank you djkid for providing it in this thread: forum.xda-developers.com/showthread.php?t=1657262
But anyway... I'm stupid because I flashed it (I know, I know, I was too eager and in a rush to flash something). Phone boots ok and everything, but it complains about the USB Storage being blank (or in an unsupported format), even though nothing is connected to it. If I put a MicroSD card in, it constantly shows "safe to remove SDCard".
I assume the partitions have been set incorrectly? I've been looking all over for an AT&T stock ODIN (that is full like the Rogers one mentioned above) but no luck. I downloaded and tried a few of the regular AT&T stock ODINs in the forum (thank you for those posts), but they only contain certain parts and they don't solve the USB / MicroSD issue I'm having.
Can anyone help?
Click to expand...
Click to collapse
gregsarg said:
Ditto......in my quest to unlock the RAT....g
---------- Post added at 12:38 PM ---------- Previous post was at 12:36 PM ----------
I'm quite certain that the ATT stock odin .tar file is complete...I've used it numerous times.
It has to be another issue...IMHO
And you are pulling the stock odin .tar from the everything thread ??
Click to expand...
Click to collapse
ladyhaylin said:
Well we all screw up once in a while. I had to return my Galaxy note to stock last night that what I would suggest you try first. if you cant connect use the usb try Airdriod to transfer the files. i used the stock att files from http://rootgalaxynote.com/ but if you cant find them let me know Ill send you what I have.
Click to expand...
Click to collapse
BTW very nice Sig Logo Picture....since BStar is my DD, LOL
gregsarg said:
this is the one I'm talking about...and have used many times....g
http://forum.xda-developers.com/showthread.php?t=1506330
Click to expand...
Click to collapse
Yes - the big RAR.
I will try it again then. I will do whatever it takes to get this thing back to normal. When flashing this one, should I check "re-partition"? or just leave all check boxes as they come....
Thanks everyone for jumping in
LaZiODROID said:
Yes - the big RAR.
I will try it again then. I will do whatever it takes to get this thing back to normal. When flashing this one, should I check "re-partition"? or just leave all check boxes as they come....
Thanks everyone for jumping in
Click to expand...
Click to collapse
Instead of having to go back all the way to gingerbread, use this odin file and flash official stock ICS which it has recovery, modem, kernel and ROM.
http://forum.xda-developers.com/showthread.php?p=28525924
Posted by 1timerlgk
RoloRacer Paranoid on JellyBean
LaZiODROID said:
Yes - the big RAR.
I will try it again then. I will do whatever it takes to get this thing back to normal. When flashing this one, should I check "re-partition"? or just leave all check boxes as they come....
Thanks everyone for jumping in
Click to expand...
Click to collapse
Simply run it ....don't re-partition ....let Odin do that ..
And GB or ICS is your choice ...but the original device partitions are GB ...not that it matters entirely, but if you want box stock ...it's the GB ...g
bigjoe2675 said:
With all this said, do we need to add something to the Super Page? I have the off ICS odin, totally bloated by ATT , (only 1gb in size) which is on my server profile, just never push it out or added it to the Super Page. Do or should we list it...on the Super Page ?
BTW very nice Sig Logo Picture....since BStar is my DD, LOL
Click to expand...
Click to collapse
I would Joe.....
we have the brick .tar,( GB) and It would be good to add the ICS .tar next to it I think....g
gregsarg said:
Simply run it ....don't re-partition ....let Odin do that ..
And GB or ICS is your choice ...but the original device partitions are GB ...not that it matters entirely, but if you want box stock ...it's the GB ...g
Click to expand...
Click to collapse
Alright. Loaded up Odin 1.85 (from the Super Everything thread), and grabbed the ICS stock recommended above (filename:
I717UCLF6_I717ATTLF6_I717UCLF6_HOME.tar.md5)
Flashing looked like it was going well!
Until it died at amss. Here is the log:
Code:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I717UCLF6_I717ATTLF6_I717UCLF6_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> recovery.img
<ID:0/006> system.img.ext4
<ID:0/006> amss.bin
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Since the majority of the flash finished, I thought I'd reboot the phone. Booted up OK (into what looks like the initial AT&T setups), but the USB issue remains. In the pic below, there is no USB anything attached to the phone, and there is a 1gig MicroSD card in the slot. (It offers to format the USB storage, which does nothing, and the internal sd storage doesn't seem to be recognized, and the external sd storage always says it is safe to remove it)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I await your wisdom. Thanks for the help so far guys.
Try and flash back to the stock ROM, I'm telling you go to rootgalaxynote.com use their step by step picture process.
If you want I have the stock PDA I'll send you it
sent from in the closet
ladyhaylin said:
Try and flash back to the stock ROM, I'm telling you go to rootgalaxynote.com use their step by step picture process.
If you want I have the stock PDA I'll send you it
sent from in the closet
Click to expand...
Click to collapse
I would appreciate that if you can. All I'm seeing on rootgalaxynote is ICS roms, ICS leaked roms and ones that look like custom roms.
The ROM I just flashed ( I717UCLF6_I717ATTLF6_I717UCLF6_HOME.tar.md5 ) -- is it not stock? Or is it that since it's ICS, it's too new for me to flash to get back to basics....
Thanks lady
Pm your email
http://rootgalaxynote.com/galaxy-no...brick-att-galaxy-note-sgh-i717-android-2-3-6/
(unroot and unbrick)
Root
http://rootgalaxynote.com/galaxy-note-root/how-to-root-att-galaxy-note-sgh-i717attrogerstelusbell/
Sent from my SAMSUNG-SGH-I717 using xda premium
ladyhaylin said:
Pm your email
http://rootgalaxynote.com/galaxy-no...brick-att-galaxy-note-sgh-i717-android-2-3-6/
(unroot and unbrick)
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
Alright. Downloaded and flashed attstockrom.tar (stock gingerbread AT&T) via Odin, but it didn't seem to help. It still has the USB Storage icon in the notification bar, saying it has an unsupported file system. Attempt to format it results in nothing... notification stays.
For this flash, I removed the MicroSD card. Flash was successful, and booted into the system. Below is a screenshot of the Storage area of Settings.
I'm thinking that the Rogers flash I originally did (to start this whole mess) maybe set the partitions wrong (or just different from this AT&T model phone)... is this possible? I don't know much about Samsung flashes (yet!). Also - I notice that the Odin 1.85 I grabbed (from the Super Everything thread) came with a PIT file (named u1_02_20110310_emmc_EXT4.pit) - but I don't want to flash it without knowing what it is exactly for. Any ideas on this? High brick risk?
Brick risk? Hell no. The pit file tells Odin how to partition the phone. Use it and see if your results are at all different.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
LaZiODROID said:
Alright. Downloaded and flashed attstockrom.tar (stock gingerbread AT&T) via Odin, but it didn't seem to help. It still has the USB Storage icon in the notification bar, saying it has an unsupported file system. Attempt to format it results in nothing... notification stays.
For this flash, I removed the MicroSD card. Flash was successful, and booted into the system. Below is a screenshot of the Storage area of Settings.
I'm thinking that the Rogers flash I originally did (to start this whole mess) maybe set the partitions wrong (or just different from this AT&T model phone)... is this possible? I don't know much about Samsung flashes (yet!). Also - I notice that the Odin 1.85 I grabbed (from the Super Everything thread) came with a PIT file (named u1_02_20110310_emmc_EXT4.pit) - but I don't want to flash it without knowing what it is exactly for. Any ideas on this? High brick risk?
Click to expand...
Click to collapse
can you format the card on with your computer?
kinghorsey said:
Brick risk? Hell no. The pit file tells Odin how to partition the phone. Use it and see if your results are at all different.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Click to expand...
Click to collapse
Crap. Loading the PIT file (u1_02_20110310_emmc_EXT4.pit) along with the stock AT&T GB wouldn't get the flashing started. It failed at the PIT check part (and I notice on the phones screen it says "SECURE CHECK FAIL : PIT"
I also tried using the above PIT with the stock AT&T ICS (to see if it would be different.. same result).
Code:
<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> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006>
<ID:0/006> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
LaZiODROID said:
Crap. Loading the PIT file (u1_02_20110310_emmc_EXT4.pit) along with the stock AT&T GB wouldn't get the flashing started. It failed at the PIT check part (and I notice on the phones screen it says "SECURE CHECK FAIL : PIT"
I also tried using the above PIT with the stock AT&T ICS (to see if it would be different.. same result).
Code:
<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> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006>
<ID:0/006> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
LORD HAVE MERCY :/ okay darling
what are you trying to do exactly?
ladyhaylin said:
LORD HAVE MERCY :/ okay darling
what are you trying to do exactly?
Click to expand...
Click to collapse
Thanks for sticking with me
I just want this USB Storage / MicroSD problem to be fixed. This is an AT&T i717. It all started when I flashed a stock Rogers ROM. The stock Rogers rom had a file for each field in ODIN (PIT, BOOTLOADER, PDA, PHONE, and CSC). I think that it re-partitioned the phone (in some foreign way that the AT&T phone no longer sees the MicroSD. It also no longer sees the internal storage. Also, the notification bar complains that USB Storage is on, and whatever is attached to the phone is in an unsupported format.). There is no USB anything attached to the phone. It is confused (and so am I).
Re-flashing the AT&T stock roms (that you guys kindly pointed me to) flash OK, but they don't solve the issue. My guess is this - do I need an AT&T specific PIT file to repartition this thing back to normal?
A friend of mine over at a Swedish forum is having problems with his SGS3 i9300. His phone just died, completely random, and refused to boot. he can only boot to download mode, nothing else.
He tried flashing a stock nordic ROM, which failed since ODIN threw him a "there is no pit partition" message. He tried flashing various PIT files, but it all stops with "there is not PIT partition" He did not do anything to his device for this to happen, it just died on him and that's where it all started.
Shot in the dark, but has his NAND memory somehow crashed, which caused the error of not booting/not accepting PIT files?
Theshawty said:
A friend of mine over at a Swedish forum is having problems with his SGS3 i9300. His phone just died, completely random, and refused to boot. he can only boot to download mode, nothing else.
He tried flashing a stock nordic ROM, which failed since ODIN threw him a "there is no pit partition" message. He tried flashing various PIT files, but it all stops with "there is not PIT partition" He did not do anything to his device for this to happen, it just died on him and that's where it all started.
Shot in the dark, but has his NAND memory somehow crashed, which caused the error of not booting/not accepting PIT files?
Click to expand...
Click to collapse
Hi! It just happened to me today! In the morning I was using the phone - calling someone.
Then put it into my pocket, went to work, and there it was already at the boot page, and staying there when resetting.
Tried to flash with odin, and I get the same error message as your friend.
I had a stock 4.0.4 rom, never touched anything on the phone yet.....
Any idea from someone?
edit:
as i9000 has linked to newer firmware with everything in post bellow, so just use that.
http://forum.xda-developers.com/show....php?t=1825272
niches said:
Hi! It just happened to me today! In the morning I was using the phone - calling someone.
Then put it into my pocket, went to work, and there it was already at the boot page, and staying there when resetting.
Tried to flash with odin, and I get the same error message as your friend.
I had a stock 4.0.4 rom, never touched anything on the phone yet.....
Any idea from someone?
Click to expand...
Click to collapse
Return under warranty .
jje
JJEgan said:
Return under warranty .
jje
Click to expand...
Click to collapse
yeah, problem is I bought it from amazon.de so I have to send it then via Post :S
tumult said:
full firmware flash with pit, bootloader, tz, etc..
hooe the link still works, if not i can make mirror tomorrow
also check in Odias thread in original android development if pit for 16 & 32 is same, but as far as i remember it is.
ps. i have flashed this firmware (without pit, but it is safe to download , no viruses, etc).
hope it helps
Click to expand...
Click to collapse
Thanks, I'll try it when I arrive home from celebrating the 253rd birtday of Mr. Guiness
Theshawty said:
A friend of mine over at a Swedish forum is having problems with his SGS3 i9300. His phone just died, completely random, and refused to boot. he can only boot to download mode, nothing else.
He tried flashing a stock nordic ROM, which failed since ODIN threw him a "there is no pit partition" message. He tried flashing various PIT files, but it all stops with "there is not PIT partition" He did not do anything to his device for this to happen, it just died on him and that's where it all started.
Shot in the dark, but has his NAND memory somehow crashed, which caused the error of not booting/not accepting PIT files?
Click to expand...
Click to collapse
All ROMs have full set images of partitions and may be flash with pit and repartition, pit - attached...
http://forum.xda-developers.com/showthread.php?t=1825272
as i9000 said:
All ROMs have full set images of partitions and may be flash with pit and repartition, pit - attached...
http://forum.xda-developers.com/showthread.php?t=1825272
Click to expand...
Click to collapse
edit: i was wrong, all partitions are there.
when you say full partition, you mean sboot.bin and tz.img also? sorry, don't think so , but if so good to know.
that's why i posted link above, that was only full firmware I could find.. but maybe it's just me.
tumult said:
when you say full partition, you mean sboot.bin and tz.img also? sorry, don't think so , but if so good to know.
that's why i posted link above, that was only full firmware I could find.. but maybe it's just me.
Click to expand...
Click to collapse
You can watch attached screen, 9 images:
sboot.bin
param.bin
tz.img
boot.img
recovery.img
system.img
cache.img
hidden.img
modem.bin...
You upload link of ROM full service ROM for Russia...
Why swedish man csc ser, russian location?
all the more so very old...
as i9000 said:
You can watch attached screen, 9 images:
sboot.bin
param.bin
tz.img
boot.img
recovery.img
system.img
cache.img
hidden.img
modem.bin...
You upload link of ROM full service ROM for Russia...
Why swedish man csc ser, russian location?
all the more so very old...
Click to expand...
Click to collapse
and i said sorry if i missed it .. anyway, i will delete my link then as yours are uptodate.
tumult said:
and i said sorry if i missed it .. anyway, i will delete my link then as yours are uptodate.
Click to expand...
Click to collapse
should not be deleted link, and the Russian people attend the xda forum ...
tumult said:
edit:
as i9000 has linked to newer firmware with everything in post bellow, so just use that.
http://forum.xda-developers.com/show....php?t=1825272
Click to expand...
Click to collapse
this is all great, but I think that does not work, I have met with this diagnosis: "there is no pit partition"
INTERNAL MMC IS DEAD... ((((
I'm having a similar problem. Except mine is a GT-I9300. Odin gives me this error.
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006>
<ID:0/006> There is no PIT partition.
<ID:0/006> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
TinyGrasshopper said:
I'm having a similar problem. Except mine is a GT-I9300. Odin gives me this error.
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006>
<ID:0/006> There is no PIT partition.
<ID:0/006> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Hey all, I have exactly the same error message. Running cm10 and my phone just froze, after re-boot i'm stuck on boot screen, no recovery and can only enter download mode....HELP!!!!
Someone reported that they had success with flashing the CF-Root to gain CWM recovery back and then flashing DarkyROM from it. But I don't know if that is even true.
PjotrFias said:
Someone reported that they had success with flashing the CF-Root to gain CWM recovery back and then flashing DarkyROM from it. But I don't know if that is even true.
Click to expand...
Click to collapse
thanks for the reply, i tried it but to no avail :crying:
Where did it stop? The first part?
PjotrFias said:
Where did it stop? The first part?
Click to expand...
Click to collapse
yeah i got the no pit message, tried flashing the pit file but won't do it...
I've just received this error on my phone too, Has there been any progress on solutions to this?
Another problem is that I can get into download mode and my system status is "Custom", How will this effect a return to manufacturer?
alot of replies with this errors lately...u guys used any custom FW ?
I was asked to make this one-click to help simplify the process of restoring a stock factory build for our Note 8.0 users. At this time neither myself or @garwynn are planning on releasing a rooted One-Click.
This Odin One-Click.exe contains the Stock GT-N5110 XXDNE1 Bootloader, Kernel, Modem and ROM for the Samsung Galaxy Note 8 16GB Wi-Fi edition (GT-N5110). Yes, that means this comes with the full Knox Bootloader.
There has been no change to the ROM from the initial build released by Samsung.
This will NOT trigger the Yellow Triangle NOR will it increment the Odin flash count.
This one-click resets your whole device to the stock XXDNE1 experience, similar to a factory restore and it may wipe all data. It also contains the full bootloader and Knox.
Instructions:
1: Backup anything important and Disable any PINs.
During this process your device's software will be returned to the Stock setup. All system data will be lost. To be safe, it is best to archive your backup off your device, ie on your PC or Dropbox.
2: Install Samsung USB/Android drivers (if necessary).
Samsung Drivers Download Link
3: Download the XXDNE1 Stock ROM One-Click.
GT-N5110 XXDNE1 Full Restore Unrooted (Compressed Archive).exe (Resets user data)
4: Unzip One-Click ROM using 7zip (this package is a self-extracting exe you should just be able to double-click on it after download and it will do the rest).
5: Start the Odin One-Click.
Navigate to the location where the "GT-N5110 XXDNE1 Full Restore Unrooted.exe" was saved upon extract from the 7Zip archive.
Double-click on "GT-N5110 XXDNE1 Full Restore Unrooted.exe". *On Vista or newer, you may need to right-click on the file and Run as Administrator.
6: Place device in Download Mode.
- Power device completely off.
- Press and hold Volume Down, Home and Power buttons, all at the same time.
- Release the buttons only when the ‘Warning!!’ message appears.
- Press [Volume Up] to enter Download mode.
7: Connect USB cable to PC and device.
Odin should show a yellow COM port in the second column. If you do not see a yellow COM port, you may need to run the Odin One-Click as Administrator and/or unplug/plugin the USB cable after starting Odin One-Click.
8: Start Odin flash process.
Press [Start].
9: Complete - PASS!
Status should change to green PASS! At this point your device should automatically reboot.
The boot process will take slightly longer than usual during which time you'll see the Samsung logo screen.
Congratulations! You've flashed the Factory Restore XXDNE1 build!
XDA:DevDB Information
[ROM][ODIN] GT-N5110 XXDNE1 (Modem/Kernel/Bootloader/ROM - Full Restore - Unrooted), ROM for the Samsung Galaxy Note 8.0
Contributors
rwilco12
ROM OS Version: 4.4.x KitKat
Version Information
Status: Stable
Created 2015-02-09
Last Updated 2015-02-09
Download Link: rwilco12.com/forum/showthread.php?tid=762
n5100
Having trouble loading 4.4.2 bootlader through odin onto my n5100 would it be ok to flash this, then root it and then install the custom n5100 rom of my choice or would I be on tne wrong bootlader and mess my tab up TIA
johnnyk75 said:
Having trouble loading 4.4.2 bootlader through odin onto my n5100 would it be ok to flash this, then root it and then install the custom n5100 rom of my choice or would I be on tne wrong bootlader and mess my tab up TIA
Click to expand...
Click to collapse
I believe it would mess up your bootloader but I don't have a way to verify as I don't have the n5100. Sorry!
Sent from my SPH-L900 using Tapatalk
triangle away
Will this reset the flash counter and allow ota updates? Or do you need to reset flash counter before you do this?
capitoldach said:
Will this reset the flash counter and allow ota updates? Or do you need to reset flash counter before you do this?
Click to expand...
Click to collapse
This won't reset the counter but it won't increment it either. This is a 100% stock unrooted ROM so you'll be able to take OTA's again after flashing.
Can I side load this with ADB? I am currently bricked and looking to start over if I can get my N5110 to install another ROM.
Sent from my SGH-I317 using XDA Premium 4 mobile app
addison892 said:
Can I side load this with ADB? I am currently bricked and looking to start over if I can get my N5110 to install another ROM.
Sent from my SGH-I317 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If you're bricked, how do you intend to use ADB?
styles420 said:
If you're bricked, how do you intend to use ADB?
Click to expand...
Click to collapse
I have full access to recovery and download modes.
I am unable to Odin and flash because of partition errors. I plan on using TWRP and the ADB option with Android SDk. Do you think this will work?
I have not been able to Odin . Pit files successfully and re-partition. I am hoping ADB will allow me to put the rom inside the current partitions and use TWRP to flash.
Just a thought. I really don't know what I am doing or how to fix it. But if I have download mode and recovery, I should be able to find a way.
I am currently in a bootloop to recovery.
Thanks for your response and any suggestions you may have.
Sent from my SGH-I317 using XDA Premium 4 mobile app
---------- Post added at 09:57 PM ---------- Previous post was at 09:48 PM ----------
I have followed the instructions posted here to the letter, but keep getting a FAIL! at the sboot.bin point shortly after starting one-click.
Sent from my SGH-I317 using XDA Premium 4 mobile app
addison892 said:
I have full access to recovery and download modes.
I am unable to Odin and flash because of partition errors. I plan on using TWRP and the ADB option with Android SDk. Do you think this will work?
I have not been able to Odin . Pit files successfully and re-partition. I am hoping ADB will allow me to put the rom inside the current partitions and use TWRP to flash.
Just a thought. I really don't know what I am doing or how to fix it. But if I have download mode and recovery, I should be able to find a way.
I am currently in a bootloop to recovery.
Thanks for your response and any suggestions you may have.
Sent from my SGH-I317 using XDA Premium 4 mobile app
---------- Post added at 09:57 PM ---------- Previous post was at 09:48 PM ----------
I have followed the instructions posted here to the letter, but keep getting a FAIL! at the sboot.bin point shortly after starting one-click.
Sent from my SGH-I317 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Unfortunately I don't know that this will work for you at this time. Essentially the one-click is a repackaged TAR. The TAR itself contains image files that correspond to specific partitions on your device. If the partitions on the device don't match up Odin is supposed to throw up a flag and stop the flash in order to prevent bricking the device.
I can't be 100% certain but given the fact it is stopping on sboot.bin, my guess is that the issues you are experiencing probably come from flashing a ZIP bootloader or ROM for another device. If that's the case we might be able to backtrack and undo what you've done so far but this won't work unless you have the right partition structures already in place.
I have spent hours trying to re-partition. The furthest I have gotten is where I am now... Stuck on Get PIT for mapping..
.. In ODIN. I am using the only PIT file for N5110 available on the entire World Wide Web!
☺
Sent from my SGH-I317 using XDA Premium 4 mobile app
hello, could someone please point me in the right direction. I've been trying to use this tool, I have access to stock recovery, when I factory reset it says it can't mount the /system. I tried this tool to reinstall every thing, but it fails at sboot.bin. all the research I've done leads me to believe this has something to do with the bootloader being locked, but I can't find anything about it, I keep getting lead back to this post. If anyone could point me where I need to be to figure this out I would really appreciate it.
Edit: I'm not sure what my problem was, but I eventually downloaded the stock 4.4.2 firmware and was able to flash through Odin and get up and running.
bookofjoshua said:
hello, could someone please point me in the right direction. I've been trying to use this tool, I have access to stock recovery, when I factory reset it says it can't mount the /system. I tried this tool to reinstall every thing, but it fails at sboot.bin. all the research I've done leads me to believe this has something to do with the bootloader being locked, but I can't find anything about it, I keep getting lead back to this post. If anyone could point me where I need to be to figure this out I would really appreciate it.
Edit: I'm not sure what my problem was, but I eventually downloaded the stock 4.4.2 firmware and was able to flash through Odin and get up and running.
Click to expand...
Click to collapse
can you point me in the direction of where you found stock 4.4.2 firmware, looked everywhere for odin flash file
redman2770 said:
can you point me in the direction of where you found stock 4.4.2 firmware, looked everywhere for odin flash file
Click to expand...
Click to collapse
For some reason they post the US version under Cellular South. You'll need to create a free account to download. It took about am hour for me to download with the free account.
http://www.sammobile.com/firmwares/download/30487/N5110UEU2CNE2_N5110XAR2CNE2_XAR.zip/
Does this clean up all the crap left over from many flashes & nandroid backups & restores? I find I have a lot of bits like old directories from previous meddling (mine) & would like to a real clean up back to pristine stock (so I can start meddling again, sort of from scratch so to speak.
Going to run it anyway (meddling again) to see what comes out the other end but was curious 'is all.
Error
This fails for me - on the tablet it says: sw rev. check fail. device:2, binary:1
Trying to flash back to stock after CM12
I've ran the app as administrator, see that is shows in the yellow box: 0:[COM4]
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> sboot.bin
<ID:0/004>
<ID:0/004>
<OSM> All threads completed. (succeed 0 / failed 1)
I've got the SAME thing goin on as KJarlin does. I'm having to go through Parallels on my Mac as I do not have a Winblows machine. That shouldn't make any difference though. Does anyone have solution???
kjarlin said:
I've ran the app as administrator, see that is shows in the yellow box: 0:[COM4]
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> sboot.bin
<ID:0/004>
<ID:0/004>
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
thewinelover said:
I've got the SAME thing goin on as KJarlin does. I'm having to go through Parallels on my Mac as I do not have a Winblows machine. That shouldn't make any difference though. Does anyone have solution???
Click to expand...
Click to collapse
Still no solution?
dopeismarcus said:
Still no solution?
Click to expand...
Click to collapse
+1
Same error.
Regards
kjarlin said:
This fails for me - on the tablet it says: sw rev. check fail. device:2, binary:1
Trying to flash back to stock after CM12
I've ran the app as administrator, see that is shows in the yellow box: 0:[COM4]
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> sboot.bin
<ID:0/004>
<ID:0/004>
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
thewinelover said:
I've got the SAME thing goin on as KJarlin does. I'm having to go through Parallels on my Mac as I do not have a Winblows machine. That shouldn't make any difference though. Does anyone have solution???
Click to expand...
Click to collapse
dopeismarcus said:
Still no solution?
Click to expand...
Click to collapse
mcpterra said:
+1
Same error.
Regards
Click to expand...
Click to collapse
Not able to verify as I no longer have the Note 8 but if I remember correctly the error you are getting is due to your device having a newer bootloader than the one-click. Most of the time a new bootloader locks out flashing of older bootloaders.
Sent from my Nexus 5X using Tapatalk