Q&A for [Firmware][unofficial]1545OYUAMDK ODIN TAR
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [Firmware][unofficial]1545OYUAMDK ODIN TAR. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Update links plox
Update links. . . please?
I locked my bootloader the same day I received my Dev S4 back in 2013 and have read and re-read every post on XDA that has info about returning the firmware back to stock, it looks like this ODIN TAR should work, but I can't find a working DL link for it anywhere on the web. Samsung is of no help whatsoever, they just flat out will not help me because I've "modified the device". If this actually does not work, or even if it will work if I have my original aboot file, it'd be awsome if you could let me know and I'll stop checking this thread every month Thanks in advance!
I prob have the link somewhere, but the thing is we learned later on that you can only re-unlock your bootloader if you still have the aboot that came with your dev edition backed up somewhere
Surge1223 said:
I prob have the link somewhere, but the thing is we learned later on that you can only re-unlock your bootloader if you still have the aboot that came with your dev edition backed up somewhere
Click to expand...
Click to collapse
I believe that I did a dd of all partitions, but I'm not 100% because I have 2 aboot.mbn files, the one that I thought was the original aboot is 2.00 MB (2,097,152 bytes) and the one that I believe is from the consumer TAR is only 1.18 MB (1,239,088 bytes). Would that help rule out whether or not I have the original? I've read your posts about using a hex editor, which I'm willing to learn and do if necessary, I was just really hoping this recombo tar would work. If the Dev aboot is larger than the consumer aboot, could I possibly get a bit of guidance on how to repackage it all up into an odin TAR? I'm in no hurry, It's been almost 2 years since I got my Dev S4 and I'm 99.9% sure that I went OYU to VRU the day I got it by following a rooting guide without reading enough. . . Needless to say, I'm a lot more educated now! Lol, either way, I appreciate you getting back to me so quickly!
jas84701 said:
I believe that I did a dd of all partitions, but I'm not 100% because I have 2 aboot.mbn files, the one that I thought was the original aboot is 2.00 MB (2,097,152 bytes) and the one that I believe is from the consumer TAR is only 1.18 MB (1,239,088 bytes). Would that help rule out whether or not I have the original? I've read your posts about using a hex editor, which I'm willing to learn and do if necessary, I was just really hoping this recombo tar would work. If the Dev aboot is larger than the consumer aboot, could I possibly get a bit of guidance on how to repackage it all up into an odin TAR? I'm in no hurry, It's been almost 2 years since I got my Dev S4 and I'm 99.9% sure that I went OYU to VRU the day I got it by following a rooting guide without reading enough. . . Needless to say, I'm a lot more educated now! Lol, either way, I appreciate you getting back to me so quickly!
Click to expand...
Click to collapse
The one that's 2mb is likely a dd backup with padded zeros (good sign) problem is you have to be sure or you'll hard brick. I'd need to see the file, and even if we confirmed it's a dev edition aboot you would have to be 100 percent sure it's one from your phone originally.
jas84701 said:
I believe that I did a dd of all partitions, but I'm not 100% because I have 2 aboot.mbn files, the one that I thought was the original aboot is 2.00 MB (2,097,152 bytes) and the one that I believe is from the consumer TAR is only 1.18 MB (1,239,088 bytes). Would that help rule out whether or not I have the original? I've read your posts about using a hex editor, which I'm willing to learn and do if necessary, I was just really hoping this recombo tar would work. If the Dev aboot is larger than the consumer aboot, could I possibly get a bit of guidance on how to repackage it all up into an odin TAR? I'm in no hurry, It's been almost 2 years since I got my Dev S4 and I'm 99.9% sure that I went OYU to VRU the day I got it by following a rooting guide without reading enough. . . Needless to say, I'm a lot more educated now! Lol, either way, I appreciate you getting back to me so quickly!
Click to expand...
Click to collapse
Send me the 2MB file. I'll make it flashable in Odin for you.
Related
Hello XDA!
I opened a new thread hopefully to open a discussion about improvements I think are beneficial, my experience over the last 24 hours that a couple sticky edits would have saved me (and others) time.
My Story:
Yesterday (5/3) I saw I had around a 250 mb OTA. Excited (hoping for 4.2, assuming was the 4.1.2 that VZW released recently) I kick on WiFi, download and watch as it reboots and appears to install successfully. Time for work to end, grabbed phone off charger as it appeared to be rebooting after successful install, and ran out to catch train home.
Downstairs, at train stop, take a look at phone and heart sinks as it is in a fast splash screen loop, blinking the VZW Galaxy Note 2 screen for about 1 second in endless loop. As I had never seen before was thinking firmware update bricked it and I was looking at least until Tuesday before I'd have a working phone. Luckily, I was able to quickly see that I could still get into download mode, so knew I was (likely) going to be ok.
Get home and a Quick Robin, to the Internetz! later I'm browsing XDA and following the t=t=2024207 walkthu to restore stock. FYI, my device prior to the failed OTA was unrooted stock. At this point I'm not sure if it's going to restore, so I'm trying to do the true stock, no unlocked bootloader in case it has to be RMA'd. I've downloaded all my files, waited patiently for the slow hosting service for the FXZ(?) to download and am grinding through it and of course it fails at the system.img. Luckily, blessedly the awesome community here had released the image that included the unlocked bootloader which I was (after waiting to download, etc etc again) able to successfully get installed via Odin, booted up and working successfully.
So, while the first post section regarding restore to stock does indicate users with latest firmware "L4 OTA Only" shouldn't be attempting to use the Official VRAL I didn't think it applied to me. I would say that a fair amount of individuals looking to take the drastic step of a full restore to stock might be in a scenario like mine, where something significant has happened and likely confirming what OS/firmware/etc you are on might not be feasible. In my case, I assumed never rooted/unlocked vanilla device should be about as receptacle to an "official" restore as any. In this scenario, where a 100% for all devices stock recovery ("alternative") works, 'I feel that it should have been pushed harder than the official or at least blurbed with if you don't know what you are on, use this' While I understand that it is the "official" image, it has requirements for it to work. A co-worker had an ASUS TF300T that tried pushing a recovery image for ICS after he had upgraded to JB and it hard bricked his tablet, with ASUS wanting to charge him about 60% cost of the tablet to replace motherboard. That's heartbreaking, and I am sure since a hard brick wasn't a likely scenario here, why it wasn't mentioned.
Also: The download link for the Alternate Restore lists the file as: I605_VRALJB_Restore.tar.md5.xz which requires that it be unpacked using 7zip AND also that once extracted, it needs to be renamed to kick of the extra extension md5 in order for ODIN to see it properly as a PDA image file. (I605_VRALJB_Restore.tar.md5 ) Neither step is mentioned in the original post, and I had to read through to I believe the 11th page or so before realizing that was the problem. I'm sure with most of the people that are daily users of this forum knew automatically that these steps were required, but I would counter that a thread explaining how to restore Stock is one of the few threads that is likely to reach a larger, inexperienced demographic who would need to know such details.
Lastly, since (I thought) I had an unlocked bootloader, but otherwsie working phone again (Thank you, thank you thank you!) might as well get it rooted, and grab a ODEX'd stripped ROM with the OS release because getting the Software Update nag and not being able to complete or even brick my phone makes my OCD gland flex mightily. Was delighted to see an on-device APK root option which threw me back to the ease of z4root a few years ago with my Droid X. APK installs, and it roots so easily, like it had the functionality out of the box. I grab goo.im manager and install TWRP. Go to boot into custom recovery so I can install my sexy updated OS ROM and enjoy my fun device without all the yucky bloatware I've just ignored/dealt with for the last 2 months and I get the dreaded and in my opinion illegal "VZW unauthorized software" software brick.
Back to the forums, see I need another stock 'alternative' restore to fix AND a little confused, but believe I need to run a "jailbreak" bootloader unlock (CASUAL ?t=2118348) Which I haven't done yet. I have all files downloaded, just paused to post my experiences here.
So, this was main reason for my post, as I can understand some of why walkthru is laid out the way it is above, but why not have this included as part of the stickied root walkthru? It's mentioned thusly:
section 1a is a old method and no longer needs to be used unless the end user wants root only. proceed to Adam Outler's "JAILBREAK" thread linked at the bottom of this section for rooting and unlocking bootloader so custom roms can be flashed!!!
Click to expand...
Click to collapse
I couldn't find the link it refers to at bottom of section? I ended up googling to find guide. ((t=202420)
if this is still a requirement for root, custom ROM/Recovery, I would have made this steps 1-x of the root guide. is it because another person authored it? It would be nice to be able to credit and quote, I know alot of what drives contributors is the 'Thanks" and Donations, be great if XDA admins could round table and find a solution that allows for a consolidated guide for each device and still give each contributor a way to get their +1's and plug donation/web/twitter handle url's
So, is my understanding incorrect of what is needed or do folks agree with me that current setup is not the most efficient way XDA community could be offering instructive guides on Root/Mods? It would be wonderful if XDA Mods upon announcement of devices, when creating the forum threads for device (Development, OG Development, General, etc etc) created a blank thread for the how to root et.al and then allowed it to be edited by the community as a Wiki. Or even if an individual created, allow that person to allow x amount of other community members to edit, add and adjust.
I see droidstyle created a thread about questions for softbrick, and I might have to look at the original sticky thread about how to stock restore, but it seems he/she might have better saturation if this info was included in the original post. The stickied How To recover stock is direct accessible from a google search. I doubt his Q&A thread is or definitely not going to be one of the highest page-ranked sites.
So, please let me know if I'm just out of my mind, off the mark. I will give myself a small escape clause based on the fact that I probably scored about 2 hours of sleep last night messing around trying to get the note running again. I am actually concerned that the instructions for Return to Stock/Root/Etc for the VZW i605 doesn't have the link to unlock bootloader via casual and am hoping that following that process before rooting/customrecovery/ROM is correct, and not going to be another BrickGate for me. I know as OS versions are updated and/or Big Red and Big Blue constantly push patches trying to lock people out of their phones that instructions change and methods break. As new directions are implemented it's easy to lose steps as edits occur on the fly.
Most importanly! I hope this thread comes across as constructive criticism/suggestions, I have nothing but the highest respect for this community and it's contributors. Even skewed, outdated and conflicting information is better than no information and I SUPER appreciate the hard work required to get it out to us. I am most definitely not expressing displeasure with my experience or the content, only using the threads I mentioned as examples of what I personally see as opportunity for improvements XDA could implement that would allow for easier dissemination of the information the community is sharing so unselfishly. I only open it for discussion, so that others like me can access the information quicker with less confusion. I read comments of disgust and exasperation as people are directed to search, rather than post, and they are right, the information is invariably there, and most often or not within the first 5 posts of a thread. But sometimes when a developer talks to another developer, the tiny and considered minor details are not mentioned because it's considered common knowledge, and thats where the noobs, soccer moms and Grandmas can get left scratching their heads trying to puzzle how you got from point a to b. (Stereotypes used for comedic effect, please take no offense) I believe it would save alot of people having to answer the same questions over and over again time and frustration and freeing them to focus their talents on making us the next epic ROM/Kernel/App
thanks for reading! Also, I'm not just drive-by b*tching, if anyone is interested, I would love to show a mock-up of the i605 guide these great contributors have created as I would compile it. I'm passionate about mobile technology and customization, sadly my talents don't lie in the creation of such, only the enjoyment of it. But I'm a hell of a document admin. I create wiki's and KB's/sharepoint admin for a living, and would love to contribute what I know in that way
Hello everyone,
I did the same mistake again by updating my S2 from GingerBread to IceCreamSandwitch without calibrating the horizontal accelerometere, and now my phone sensor is a bit off "to the left"
(when i play games like " Trial ", the phone is supposed to be in the "normal" position so the rider should not move at all but in my case he is always going back {like am rotating the phone to the left} so i have to rotate the phone about 15 degrees to the right in order to be "normal" )
Unless you have a better solution for this problem cause seriously, why on earth there is only a gyroscope calibration for a device that have more than that sensor >_< !??!
anyway
i would really appreciate if your link me to all the necessary files to downgrade from ICS to GB,
IMPORTANT:
i don't want to root my phone cause i will update to official ICS again
SOLVED
i just need the PDA file which i found my model here : http://www.androidfirmwares.net/
thank you
Maybe post in the dedicated forum for that device lol
You mean you did the same thing on your S2 as you did on your S Advance 6 weeks ago ? If so, go get the rom files you need from Samfirmware, flash with Odin following instructions in thread stickied near top of Q&A titled 'Flash Stock firmware'.
If you're still talking about your S Advance then yeah, you're obviously in the wrong place.
MistahBungle said:
You mean you did the same thing on your S2 as you did on your S Advance 6 weeks ago ? If so, go get the rom files you need from Samfirmware, flash with Odin following instructions in thread stickied near top of Q&A titled 'Flash Stock firmware'.
If you're still talking about your S Advance then yeah, you're obviously in the wrong place.
Click to expand...
Click to collapse
yes that's exactly what happened (am with S2 now) and i actually tried both Samsung-updates and samfirmwares but the search results contain Roms for 4.1.2, 4.0.3 and 4.0.4 i might be searching in the wrong place though so i would really appreciate it if you post a link for me
thank you very much
If you can't find GB firmware at those two places, you can try AndroidFirmwares.net, but they probably won't have what you want either. If they don't, you're probably SOOL; try Google searches or use something else (or do a bunch of XDA searches, you might get lucky & someone might have uploaded it somewhere & linked to it in a thread way back).
Edit - You need to use the pulldown boxes @ Samfirmware better, there's plenty of GB firmwares available. If there isn't one for your country/carrier, you're going to have to use something else.
MistahBungle said:
If you can't find GB firmware at those two places, you can try AndroidFirmwares.net, but they probably won't have what you want either. If they don't, you're probably SOOL; try Google searches or use something else (or do a bunch of XDA searches, you might get lucky & someone might have uploaded it somewhere & linked to it in a thread way back).
Edit - You need to use the pulldown boxes @ Samfirmware better, there's plenty of GB firmwares available. If there isn't one for your country/carrier, you're going to have to use something else.
Click to expand...
Click to collapse
thanx man i'll keep looking, but just a question, is it really impossible to recalibrate the accelerometer on Android 4.1.2 ?
i am 100% sure that it's not a hardware problem so why there is no way to fix that
No idea, never had a problem with it myself. Hopper8 had issues with it maybe 12 mths ago & searched high/low for a solution went really 'in depth' with it. Maybe search for his threads on that issue/from about that time.
MistahBungle said:
No idea, never had a problem with it myself. Hopper8 had issues with it maybe 12 mths ago & searched high/low for a solution went really 'in depth' with it. Maybe search for his threads on that issue/from about that time.
Click to expand...
Click to collapse
Thank you, i checked that but it seems that he is facing problem with the gyroscope mine is an accelerometer problem (i make casual mobile games for a living and i made a little accelerometer test, it is simple 18 degree "wrong" to the left)
anyway,
i found this website : AndroidFirmwares.net - News and am downloading this firmware the bad news is that i have no idea where to find the .pit file, cause as i remember with my S-Advance (and my old S too) i need a pit file to use with Odin right ? and it's always a very small size,
any help with that please ?
Don't touch a PIT file unless:-
A) You have a specific reason to.
B) You know what you're doing.
I've seen literally hundreds (and no doubt there has been many more I haven't seen) of people flashing PIT files when they absolutely didn't need to brick their phones on here over the past 2 & a bit yrs (almost always a case like yours of simply needing to flash a one part stock firmware to fix, but people have to over-complicate things).
Neither A nor B applies to you, so don't do it. If you think what I've said is overkill, I'm merely trying to save you from having to throw your phone in the bin.
MistahBungle said:
Don't touch a PIT file unless:-
A) You have a specific reason to.
B) You know what you're doing.
I've seen literally hundreds (and no doubt there has been many more I haven't seen) of people flashing PIT files when they absolutely didn't need to brick their phones on here over the past 2 & a bit yrs (almost always a case like yours of simply needing to flash a one part stock firmware to fix, but people have to over-complicate things).
Neither A nor B applies to you, so don't do it. If you think what I've said is overkill, I'm merely trying to save you from having to throw your phone in the bin.
Click to expand...
Click to collapse
Thank you,
so following what you said, i only need to select the downloaded firmware from the PDA button and press start ?
Remark :
i tried that and i got this error :
"Can't open the serial(COM) port."
Since kies is completely closed and am 100% that i have the USB direver installed (phone detected and i've done that before)
i am going to assume that my cable or my ports are the cause of the problem, if you have a better suggestion please illuminate me, otherwise i'll try with different cable/PC tonight and keep you updated, lastly i REALLY hope that an expert android developer or maybe someone that can spread this problem for more people cause it is VERY annoying to have to do this for such a minor problem just because the OS developers have forgot or didn't want to allow us to adjust all the phone sensors ...
Note that after this downgrade, i will have to upgrade again and restore all my previous data,setting, apps again... and that is a real painful waste of time >_< !!!
Hopper8's 'Odin troubleshooting' thread stickied in the General section has all the info/stuff you need to try in order to get a successful flash.
MistahBungle said:
Hopper8's 'Odin troubleshooting' thread stickied in the General section has all the info/stuff you need to try in order to get a successful flash.
Click to expand...
Click to collapse
Thank you very much, changing the cable solved this, the phone is back to stock again :victory:
just in case someone face this,
i got a SplashScreen loop (my SplashScreen is changed from TIM {italian operator} to the default samsung wich is another victory for me :highfive: )
anyway,
that was simply solved by booting into recovery mode and wipe all data
Edit :
Samsung Kies doesn't detect new update anymore, i think that is because i only used PDA in Odine ?
i'll have to update with Odine again (it take less time than kies anyway)
Hi all,
I installed CM11 onto my S5830i (GB) and managed to get it all working. I had to install S5360_XXMK1 modem and a newer version of CWM to prevent the "Status 7" error. Anyway, it all worked and I had CM11 up and running. Unfortunately, I had to remove it, I couldn't click any links in the browser and the browser was slow as all buggery even on a fast wifi connection. So I fired up Odin and tried to put the stock firmware on (i don't have an original state backup, the phone came with a custom rom on it already). I got these files
CSC_S5830i_BTUMD1.tar.md5
MODEM_S5830i_XXMD1.tar.md5
PDA_S5830i_XXMD1.tar.md5
But something's messing up, after Odin does its thing and the phone restarts, I notice something on the screen during restart saying it failed to format the /data partition. When I let the phone boot up normally it just stays on the "Samsung" startup animation forever. If I go into samsung recovery and try to do a factory reset, this is what I see
Code:
-- Wiping data...
Formatting /data...
E:format_volume: rfs format failed on /dev/stl11
Formatting /cache...
Data wipe complete.
Obviously, something's wrong there, can anyone tell me how to fix it pleeeeese, I'd be eternally grateful.
Thanks
NS
EDIT: I think the CM install may have messed around with my partitioning. I do not have a pit file for the phone (GB Version) and am reluctant to be using the re-partition option in Odin. I can find pit files online, but they're either not the correct version or the poster doesn't even say what version it is. I am just so lost and confused with all this.
@NicSure, Flashing wrong base band into your Ace-i is ill advised mate, go to CM11 discussion topic and read my comments . ( You will damage your EFS partition,thus device may become hard bricked in many cases)
As for troubleshooting : Already explained all of the instructions in details in many places, So I will provide links/hints for now. If your problem persisted, let us know
Here we go mate:
1. Official source for your stock firmware CSC/MODEM/PDA >> this page (sammobile.com)
2. Study this topic to get the hang of Wipe flash-able packages,,, How to produce them, Boot looder and pit files required for the process , etc etc,, all well instructed here
3. Read few last pages of this topic; my comments; for more insight into your problem. Please be advised you have already converted your partitions into MTD ,therefore formatting /data ( concerting back into RFS partitions ) might be failure through CWM/e3 recovery >> Odin process is required for"stl11" .
Hope I did help you
ehsanotaku said:
@NicSure, Flashing wrong base band into your Ace-i is ill advised mate, go to CM11 discussion topic and read my comments . ( You will damage your EFS partition,thus device may become hard bricked in many cases)
As for troubleshooting : Already explained all of the instructions in details in many places, So I will provide links/hints for now. If your problem persisted, let us know
Here we go mate:
1. Official source for your stock firmware CSC/MODEM/PDA >> this page (sammobile.com)
2. Study this topic to get the hang of Wipe flash-able packages,,, How to produce them, Boot looder and pit files required for the process , etc etc,, all well instructed here
3. Read few last pages of this topic; my comments; for more insight into your problem. Please be advised you have already converted your partitions into MTD ,therefore formatting /data ( concerting back into RFS partitions ) might be failure through CWM/e3 recovery >> Odin process is required for"stl11" .
Hope I did help you
Click to expand...
Click to collapse
Thanks but you were too technical. I have been to a lot of those pages you linked and it's not all obvious what's going on. You spoke about "base band", I have no idea what that is. I have no idea what RFS, MTD
are (file systems?), not do I know where to get a bootloader from. Sam mobile won't let me download anything without paying and/or signing up which I'm reluctant to do. I'll re-read the posts you linked to (I had already seen them) and see if something starts to make more sense.
For instance:
"Please be advised you have already converted your partitions into MTD ,therefore formatting /data ( concerting back into RFS partitions ) might be failure through CWM/e3 recovery >> Odin process is required for"stl11"
May as well have been in Klingon, I didn't understand a word of it.
EDIT:
I've reviewed those threads again. Seems I need to use split fus on the downloaded file from SamMobile (which I had to register to download, not happy about that) and use the "wipe" versions. I need a pit file, there's no info anywhere on how to get that. So I've just done a general google and hopefully I've downloaded one (more info on that is needed in the tuts). And the bootloader is attached to the unbrick thread, but, is that the ONLY bootloader? Do I need a specific one for my region? Do I need a specific pit file for my region? All this info is not supplied anywhere, Newcomers are not going to know this stuff and it needs to be made clear in the tutorials. Most of the tuts have broken links (split fus for instance), so I'm not sure if the stuff I googled is actually the same. Absolute nightmare.
NicSure said:
You spoke about "base band", I have no idea what that is.
Click to expand...
Click to collapse
Please read the link was provided for your convenient. ( Absolutely suitable for beginners).
NicSure said:
I have no idea what RFS, MTD
are (file systems?)
Click to expand...
Click to collapse
"Robust File System" is more or less equivalent to your FAT/FAT32 of your PC ( Samsung file system Format,, not going to add "Journalling system" to the mix, since you are not a sport ,,FYI : You are supposed to know common terms such as MTD , RFS when you are massing with CM11 mate >> Read the first page thoroughly, before start experimenting with Cyanogen stuff,,,
MTD (Memory Technology Device) supports YAFFS2 as a file system residing on it and is considered some type of of Partition Map.
NicSure said:
not do I know where to get a boot loader from. Sam mobile won't let me download anything without paying and/or signing up which I'm reluctant to do
Click to expand...
Click to collapse
Again actually start reading this topic ( quite self explanatory).
NicSure said:
Seems I need to use split fus on the downloaded file from SamMobile (which I had to register to download, not happy about that) and use the "wipe" versions.
Click to expand...
Click to collapse
This topic contains well made Wipe packages ( European version is compatible with your device, If you are reluctant to register though).
NicSure said:
I need a pit file, there's no info anywhere.
Click to expand...
Click to collapse
Again, Read the topic I mentioned above. You are on Cooperve device, so be aware of wrong file ( "cooperve_0623.pit" resided inside Odin3.v3.07.Cooperve folder) All of the related links already provided , Just take your time and read mate.
I'd already read the posts you linked to multiple times thank you. They may be "straight forward" to you, but I can assure you they are certainly not so for a newcomer. Too many things are vague, missing or not explained properly.
In any case, I managed to get the stock firmware back on after trawling the internet for a .pit file, downloading the firmware, splitting it, taking the wipe versions with the pit and the bootloader and using Odin to fully flash the phone back to stock firmware, Finally. The tuts here are indeed a lot of help, but so so so disjointed.
Also, why would changing the base band effect the file system? How could it cause physical damage to NAND memory. I'm confused. I assume you mean physical damage, because if not, why would it be ill-advised to change it if it could just be changed back with no ill-effects?
@NicSure, First of all Thanks button implanted here for a good reason and most likely you are the first person who was complaining about my assistance (How information is organized and distributed for new commers is not my responsibility nor distribution of step-by-step instructions ) . Second of all You were complaining about the technical terms and jargon, But know you are asking for technical reason in regard of the consequences of flashing Galaxy Y GT-S5360 inside your ACE-i device !
I did mention about EFS partition corruption, which renders your device mobile network communication useless and hard bricking of your device.which is a phone that shows no signs of power-on and will not access download mode with button combo. You did assume wrong mate.
Generally speaking, Carriers use different radio frequencies in our respective countries , Different Devices do contain different modem hardware inside, So you are not encouraged to do what you have done in the first place.
If you are not flashing the correct versions for your phone , or if the flash gets interrupted there’s a good chance you will Hard Brick your device, thus we may need hardwired access to modify/erase and rewrite chip's code ( Service is required).
When a phone is in a hard-bricked state it’s most likely that the bootloaders, which is the phones initial code to launch the phones ROM, becomes corrupted.
The only way to revive the phone is to rewrite the bootloader code, because the phone does not power on ., So you see so many things could go wrong :silly:
ehsanotaku said:
@NicSure, First of all Thanks button implanted here for a good reason and most likely you are the first person who was complaining about my assistance (How information is organized and distributed for new commers is not my responsibility nor distribution of step-by-step instructions ) . Second of all You were complaining about the technical terms and jargon, But know you are asking for technical reason in regard of the consequences of flashing Galaxy Y GT-S5360 inside your ACE-i device !
I did mention about EFS partition corruption, which renders your device mobile network communication useless and hard bricking of your device.which is a phone that shows no signs of power-on and will not access download mode with button combo. You did assume wrong mate.
Generally speaking, Carriers use different radio frequencies in our respective countries , Different Devices do contain different modem hardware inside, So you are not encouraged to do what you have done in the first place.
If you are not flashing the correct versions for your phone , or if the flash gets interrupted there’s a good chance you will Hard Brick your device, thus we may need hardwired access to modify/erase and rewrite chip's code ( Service is required).
When a phone is in a hard-bricked state it’s most likely that the bootloaders, which is the phones initial code to launch the phones ROM, becomes corrupted.
The only way to revive the phone is to rewrite the bootloader code, because the phone does not power on ., So you see so many things could go wrong :silly:
Click to expand...
Click to collapse
Firstly, I'm not complaining, I'm criticizing, there's a difference. I was critical of your language and terminology as it didn't match the links you posted. Also the level of technical talk you used toward a clear newbie who would obviously never understand it without clarification. If that offends you then I'm sorry, I'm just speaking my mind. Help offered, no matter how kindly or freely is useless if it cannot be understood. I generally take a very irritated approach to people who post links (with the implication that the information is freely available if you'd bother to look) in response to perfectly polite questions, especially when I'd already read ALL the posts you linked to before and had trouble with them, that is why I posted, to get a little more basic understanding, not be presented with links to material I'd already read and needed help with. Also, after some researching, with regard to the base-band, I think you're wrong, there's no way flashing a different base-band separately could effect the bootloader, no way at all. I seriously doubt it could even cause corruption, that's liek saying installing the incorrect driver for a graphics card on a PC could corrupt the file system, just no. So far I've flashed many many different MODEM types onto my phone to try to test this, in some caes the phone boots, in some cases it doesn't etc.. Not once has the phone failed to go into Odin flash mode, and if it can get to that, it can be restored. So based on research and some experimental evidence conducted to test your assertion, I'd have to say that my initial findings are that your assertion is probably incorrect.
Also I learn very quickly. My knowledge of the subject had increased dramatically from my first post to my second. I learned c++ in a day for example, and was posting similar newbie questions on programming forums to which I was later replying with a level of knowledge that wasn't consistent with my initial post. It's just me, sorry about that. And thanks for trying to help, but I got it myself.
NicSure said:
... I can assure you they are certainly not so for a newcomer. Too many things are vague, missing or not explained properly. In any case, I managed to get the stock firmware back on after trawling the internet for a .pit file, downloading the firmware, splitting it, taking the wipe versions with the pit and the bootloader and using Odin to fully flash the phone back to stock firmware, Finally. The tuts here are indeed a lot of help, but so so so disjointed.
Click to expand...
Click to collapse
Dear NicSure, I am in the same situation as yours, I was planning to "simply" (or maybe wrongly?) use Odin 3.09 and flash the Splitted files from here (http://forum.xda-developers.com/galaxy-ace/s5830i-develop/stock-rom-odin-flashable-firmware-t3002776).
But you mentioned that also the ".pit" file is needed. Could you guide me through the process you followed to have back a Stock from CM11 ROM?
Thank you in advance!
thePanz said:
I was planning to "simply" (or maybe wrongly?) use Odin 3.09 and flash the Splitted files from here (http://forum.xda-developers.com/galaxy-ace/s5830i-develop/stock-rom-odin-flashable-firmware-t3002776).
But you mentioned that also the ".pit" file is needed. Could you guide me through the process you followed to have back a Stock from CM11 ROM?
Thank you in advance!
Click to expand...
Click to collapse
Per your request/confirmation @ development section/twr topic i would resume troubleshooting .
What is your device variation (5830i/C/M/V/5839i ) ? Do you have any Nandroid back up left inside your SD card from your original stock firmware partitions ? Can you see your IMEI number , when you are dialing "*#06#" ? Your original stock CSC/PDA/MODEM you are coming from ? Your Region / Country / carrier you are staying with at the moment and please give me the Totoro Modem part you did flash to get into the CM11 ? and for addressing part of your primary queries , Odin 3.07 works very well with variation I mentioned above ( you could use 3.09 with no harm though , but not recommended ) . Pit file also must be relevant, otherwise you will hard brick your device in many cases I observed .
Would anyone be kind enough to share a good PIT file? I'm having a lot of really weird issues with my phone and I want to NAND erase the device and ODIN the .tar I got from SamMobile. Please don't share your unfounded fears of NAND erasing a device. I've done it at least two dozen times with my last three devices. Contrary to popular belief there is no danger here unless your phone is damaged with bad blocks. Please just share the PIT file if you have it. I am EXTREMELY comfortable here. Thank you.
I'm in need of this as well
I'd give it to you, but I don't know how to get the file you're after.
Hola. Sorry for late reply. I keep forgetting to check on the Sprint Edge page. There aren't many of us
I just created this pit file from my phone. I'm not sure if it matters, but I am running tx_dbs_tx's 4/28/15 stock, rooted, deodexed, KNOX-less 5.0.1 ROM.
https://www.dropbox.com/s/h9kmco32dnz5019/SM-N915-5.0.1 (Sprint).pit.zip?dl=0
Lemme know how it goes.
I wanted to make a thread to let everyone know how the port is coming. So here it is.
Right now we have an incomplete device tree, found here:
https://github.com/Azimoto9/android_device_samsung_cprimeltemtr
We're currently working on getting a recovery to build so that we can try to build cm.
But heres the thing,
its literally just two people actually working on the project, and we need some help. So if you're a developer or even want to become a developer and are willing to put time in, whether to learn or help us port cm, we need you.
A great resource for learning android development is XDA-University.com. Between that and the cyanogenmod wiki, it's how I am still learning what to do. Unfortunately there is no generic guide on how to port cm to a device (or at least not a complete one).
So if you would like to contribute in some way, head over to webchat.freenode.net and join the channel #G360T1 or message me on XDA. if webchat isnt working for you, you can use Hexchat for windows or a similar irc client.
So that was both an update on current progress and a plea to the community for help on this one. Thanks for reading.
Looking forward to this and willing to help any way I can!
People believe that if they manage to get Cyanogenmod for our Core Prime, is compatible with the g360m? Since we have this model in Latin America, and not stand lagwiz :v . Regards
fededelg said:
People believe that if they manage to get Cyanogenmod for our Core Prime, is compatible with the g360m? Since we have this model in Latin America, and not stand lagwiz :v . Regards
Click to expand...
Click to collapse
Maybe, but it may require some variant work.
I feel like I gotta say that it's so hard to know what's going on in IRC. I feel totally uninformed. At least with XDA we can look back and see what we missed and get caught up. I wish I could run IRC 24/7 to stay in the loop, but unfortunately I can't.
Sent from my SM-G360T1 using Tapatalk
bogarty said:
I feel like I gotta say that it's so hard to know what's going on in IRC. I feel totally uninformed. At least with XDA we can look back and see what we missed and get caught up. I wish I could run IRC 24/7 to stay in the loop, but unfortunately I can't.
Sent from my SM-G360T1 using Tapatalk
Click to expand...
Click to collapse
I might actually be able to help with that. I can try to make my bot output logs somehow, but it may require some work, so don't expect it instantly, lol.
This is great news. I'd like to take this as an opportunity to learn some new things but unfortunately I don't quite have much time to invest at the moment. I'll be keeping an eye on this and if free time opens up I'll be jumping in. I have some basic knowledge of the ins and outs of android and linux but I know I definitely need to learn a lot more.
We're getting closer... ?
Sent from my SM-G360T1 using Tapatalk
I ll contribute with this project but need some files from this device
Dreamstar said:
I ll contribute with this project but need some files from this device
Click to expand...
Click to collapse
Which files
Sent from my SM-G360T1 using Tapatalk
Boot.img , Recovery.img , and partition blocks
Dreamstar said:
Boot.img , Recovery.img , and partition blocks
Click to expand...
Click to collapse
How do I or where do I get the partition noob here
https://www.androidfilehost.com/?fid=24351979186683928
Or here is the rooted stock firmware if that helps
is this project still alive?
Yes, freenode #g360t1 is where you can find more regular updates. @galaxykeks
Sent from my SM-T350 using Tapatalk
Dreamstar said:
Boot.img , Recovery.img , and partition blocks
Click to expand...
Click to collapse
About partition blocks, would you want partition dumps? Or the listing of all of the partitions?
"Partition Blocks"...
Forgive me for speaking out of turn, but I'm guessing what was really being asked for was the partition image table (pit file). I find myself in need of the very same thing. even Odin requires one if you are repartitioning the phone -OR- just rewriting the table to repair incidental damage (believe it or not partition table damage does happen, really, lol). Heimdall wants one too. Somehow while trying to root my G360T1 I got TWRP to flash ok. I booted into it just once;; something was unstable, it rebooted randomly and disappeared. No matter what I try it just boots to the Samsung logo and hangs, kernel and/or recovery. The stock firmware has issues writing any one of the .mbn component firmware files, seemingly random in choice which one. the phone display reports "SECURE CHECK FAIL:" and the odin logfile shows "FAIL! (Auth)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed." I thought aboot.mbn was the only partition Samsung was locking....
Anyway, the problem is that I now have no access to the partition table so I can retrieve a copy. Download mode is all that works. A pit file for this beast is nowhere apparent no matter how diligently my browser search engines are applied to the problem. At least I could be sure the firmware gets written to at the proper locations (bricked an S3 that way:cyclops
That's all that's keeping me from offering to help with the port. I am/was a software engineer with spare cycles, a development environment including Ubuntu linux, as well as a keen interest in diving into deeper android waters (e.g. building the kernel).I'm pretty sure i'm ready and equal to the challenge. Maybe I wouldn't make as many bricks if I knew a bit more, lol. And hey, I've finally got my personal assistant with me 24/7 and I've got a multicore Linux computer in my pocket no matter where I go. I like it!
OK, I yield the thread...
riches2rags I will be happy to get you the PIT file when I get a free moment, hopefully within the next hour or so
Edit: Doing it now, sorry for the holdup
@riches2rags sorry again for the holdup. I generated this PIT file with the android emulator app, from a completely stock rooted firmware. I had made a lot of changes previously, so I wiped everything except external SD (including internal storage), used Odin to flash the official firmware, booted up the startup wizard, skipping everything but Wi-Fi settings, and rooted. Then I installed the android terminal app using the apk file and dd-ed the file I link to below (long story short, as stock as possible):
https://www.androidfilehost.com/?fid=24459283995298587
Thanks thisisapoorusernamechoice! I just d/l'd it. I'm tired & it's late so I won't get to try it for a few hours, but I'm stoked.
On a side note, I see Hartford as your location. As in Connecticut, right? Funny, I grew up across the river in Glastonbury and got my BSEE/BSCS degrees at UConn ('83). Small world
riches2rags said:
On a side note, I see Hartford as your location. As in Connecticut, right? Funny, I grew up across the river in Glastonbury and got my BSEE/BSCS degrees at UConn ('83). Small world
Click to expand...
Click to collapse
Wow it really is a small world, I grew up in Bolton, right next to Glastonbury, and I played soccer in Glastonbury all the time, they have really nice indoor and outdoor facilities. And I can't even count how many people I know who went to UConn, including both my paternal grandparents. Cool stuff :good: