I know others have looked as well but can anyone *please* dump the rom of their AT&T 4.2.2 stock image for the good of all us AT&T S4 Zoom owners who are stuck in a logo reboot loop or have other problems that require a restore? There are currently no images available on any of the usual places (Samsung firmware, updates etc.)
Thanks very very much in advance!
If you not found any stock rom for C105A At&t... & Your Phone is In Boot loop Stuck on Samsung Logo... Then Just Flash C105A Mexico C105AUBUAND1, 4.2.2 System And Cache Separately in Odin...
This will not work because the AT&T variant of the phone is bootloader locked. You are not able to flash firmware variants unless they are for the AT&T version of the phone. Hence why so many people need a firmware image for AT&T. If anyone has or can make a DD.Image it would help a lot of people.
moomoo said:
This will not work because the AT&T variant of the phone is bootloader locked. You are not able to flash firmware variants unless they are for the AT&T version of the phone. Hence why so many people need a firmware image for AT&T. If anyone has or can make a DD.Image it would help a lot of people.
Click to expand...
Click to collapse
i am try this Method personally.. Every Thing working Fine
Download SM-C105A Mexico (Telcel) Android 4.2.2 firmware, from SamMobile,
Extract Whole Firmware Select only System Image & Cache file & Make it odin flashable Tar. using (tar-Tool_Odin3-v3.07_by_mkh.mourad)
Flash System & Then Cache In Odin Ap.. Thats It..
Try Only If Your Phone Is Soft Brick or In Boot loop State... Thanks
http://forum.xda-developers.com/picture.php?albumid=13143&pictureid=53644
http://forum.xda-developers.com/picture.php?albumid=13143&pictureid=53643
I'd like to help. I've extracted system.img and cache.img from an AT&T sm-c105a (4.2.2). Unfortunately I didn't read the above instructions very well and placed them both in an odin flashable tar.md5 file. I guess if you want to follow the above proceedure you will need to flash them separately. On the other hand, if you have a brick already anyway, you could just try it out. Any problems with the file post here. Mediafire was being dodgy and I wouldn't be surprised if it was damaged. Anyway here is the link, or as close a facsimile as my noobness will allow: http www mediafire com /download /xbdxb8gun1niwg9 /sm_c105a.zip
So, I assume from the deafening silence that this did not work? I'm not surprised since a dd of a mounted partion (system) can't be a good idea. I have been experimenting with Adebar which is also supposed to make a system backup. Doesn't seem to fully support the phone, or, doesn't create the full backup. I'm open to other ideas....
More files
Boot and recovery images, plus pit file all from stock sm-c105a AT&T JB 4.2.2. www . mediafire . com/ download/ 3df255lt8unnh24/ Boot_Recovery.tar.gz
Faisalkhan.007 said:
i am try this Method personally.. Every Thing working Fine But 3G Is Not Working..
Download SM-C105A Mexico (Telcel) Android 4.2.2 firmware, from SamMobile,
Extract Whole Firmware Select only System Image & Cache file & Make it odin flashable Tar. using (tar-Tool_Odin3-v3.07_by_mkh.mourad)
Flash System & Then Cache In Odin Ap.. Thats It..
Try Only If Your Phone Is Soft Brick or In Boot loop State... Thanks
{
"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"
}
Click to expand...
Click to collapse
Don t work to me.
Here are a cache and system image from the AT&T variant of the phone. @awwar can you be more specific. You are in a boot loop? No recovery?? Device recognized by Odin/Heimdall??? I am VERY interested in providing a way to unbrick our phones but am unwilling to brick my only device. If you want to try something post here and I will provide what support I can.
My CM-C105A is in Kies recovery mod mode. I can flash only system and cash tar files. Kies show error when i am traing to recover my phone.
Have you tried the pit file? Sometimes that might help?? Also, I have a boot.img download further up the page. If your bootloader is bad you could get similar symptoms? Kies doesn't like my boot/recovery images? Can you post the specific error? Thanks for replying. c_p
capt_planit said:
Here are a cache and system image from the AT&T variant of the phone. @awwar can you be more specific. You are in a boot loop? No recovery?? Device recognized by Odin/Heimdall??? I am VERY interested in providing a way to unbrick our phones but am unwilling to brick my only device. If you want to try something post here and I will provide what support I can.
Click to expand...
Click to collapse
have you pit -file to AT&T firmware?
awwar said:
have you pit -file to AT&T firmware?
Click to expand...
Click to collapse
@awwar Here are recovery and boot images and pit file from AT&T version of phone Build # JDQ39.C105AUCUAMJ2. Kies may not be able to restore if you have a damaged bootloader source. But, on a plus note, "I haven't run into anyone yet who couldn't undo soft brick from Odin" source
capt_planit said:
@awwar Here are recovery and boot images and pit file from AT&T version of phone Build # JDQ39.C105AUCUAMJ2. Kies may not be able to restore if you have a damaged bootloader source. But, on a plus note, "I haven't run into anyone yet who couldn't undo soft brick from Odin" source
Click to expand...
Click to collapse
Nothing changed, I flashed whith this firmwares but error. This firmware is too large.
@awwar Ok man, thanks for testing. I hope your skills extend further than the average windows user. You have to extract the files and then repackage them for odin as tar.md5. I think you can do it in windows but I can only talk you through it if you are using linux. I am not sure which image to flash first but Faisalkhan.007 in the first page suggests doing it one file/partition at a time. I would flash my recovery and on reboot try using volume up and home to get to the newly flashed recovery. I think you are getting file too large because you've got more than one file in your flash package. Restore the pit file as a last attempt after trying to flash each partition. I'd love to figure out how to pass you the bootloader only but I've got another project ahead of this. Did you look at some of those links? Try this (search for download mode on the page) if you are having trouble getting to download mode. And this is for osX but might help too. The errors you are getting don't sound like the one I get. I upload an entire file then fail at 100% for an unknown reason. The Heimdall guys say that is due to the locked bootloader. TLDR: Split files, flash singly, reboot and try stuff in between. c_p
Well I Really Don't Know , But Its Working For Me,
http://forum.xda-developers.com/picture.php?albumid=13143&pictureid=53644
http://forum.xda-developers.com/picture.php?albumid=13143&pictureid=53643
awwar said:
Nothing changed, I flashed whith this firmwares but error. This firmware is too large.
Click to expand...
Click to collapse
Okay Wait I Am Gonna Upload Flash able Tar System & Cache files On Cloud When its Done, i will send You Link, :good:
awwar said:
Don t work to me.
Click to expand...
Click to collapse
https://mega.nz/#F!SFhCnIIb!D7QIX-Xmkd8aZBfU_-2PIg
Try It
I have *three (3)* SM-C105A S4 Zoom Camera phones by Samsun and enjoy them. I have upgraded firmware on 2 so that I can use Remote ... uh, is it Viewfinder? And it works. Not to the point. What I *lost* was compatibility with *ooooooold* Photo Elements. Which, at age 57 I like to use and don't want to relearn. I run it on a virtual XP. What makes this post relevant is that *third* S4. It *hasn't* upgraded. Cracked screen, disused, but I crammed.. well, a bit of fibrous matter...OK , a ciggy-butt, in the battery door, with a rubber-band, to hold a fresh battery in place, ... and it's booting now. So, please give me a month to extract the firmware, yes it is AT&T and also upload Photo Elements, firmware from old and upgraded, to continue the discussions, or not, and to try cloning the two to restore my ability to post process nudies shot with my camera phones. And other pics. I wrote an AI MathCAD program to postprocess nudies (it's fine art fer heaven's sake) that actually simualted the artist's brush strokes. More on all this in I hope a month.
DGoncz
---------- Post added at 01:39 PM ---------- Previous post was at 01:22 PM ----------
No, back when, I must have applied, not the most recent upgrade, but the intermediate of the three versions.....and all hope is lost. Photos from the oldest S4 I have do *not* open in Photo Elements. None of my cameras produce photos that open in Photo Elements any longer...but they did. I opened an older photo just now.
Dang these upgrades. The message says the JPG file is missing a segment. Phooey.
I have a business account with Samsung and will open a support ticket.
I will not pursue the hack angle for now.
Samsung may help me.
Cheers,
DGoncz
DGoncz said:
I have *three (3)* SM-C105A S4 Zoom Camera phones by Samsun and enjoy them. I have upgraded firmware on 2 so that I can use Remote ... uh, is it Viewfinder? And it works. Not to the point. What I *lost* was compatibility with *ooooooold* Photo Elements. Which, at age 57 I like to use and don't want to relearn. I run it on a virtual XP. What makes this post relevant is that *third* S4. It *hasn't* upgraded. Cracked screen, disused, but I crammed.. well, a bit of fibrous matter...OK , a ciggy-butt, in the battery door, with a rubber-band, to hold a fresh battery in place, ... and it's booting now. So, please give me a month to extract the firmware, yes it is AT&T and also upload Photo Elements, firmware from old and upgraded, to continue the discussions, or not, and to try cloning the two to restore my ability to post process nudies shot with my camera phones. And other pics. I wrote an AI MathCAD program to postprocess nudies (it's fine art fer heaven's sake) that actually simualted the artist's brush strokes. More on all this in I hope a month.
DGoncz
Click to expand...
Click to collapse
@DGoncz You could do that, or, you could just do a complete wipe/reset. Should be 4.2.2 after that. You may also be able to use a hex editor to set the start of the jpeg file to whatever your proggie wants to see. Good luck c_p
Related
Hi,
I am looking into getting a European ROM running on the sgs3 I bought here in China.
I tried downloading the official Samsung rom from UK, but I failed during installation of the modem part. It rendered my phone useless, and it took hours getting it back up with the kies and the official Chinese rom.
I used the software called Odin i believe, to attempt the update.
To me, it seems as if it is not that easy, maybe due to the modem thing, but can anyone verify that this will never work?
The main reason for applying a different rom is, that it seems that none of the Google apps are going to work. I can't install them, but they won't run. The apps seem to load, put with no message, it closes and the phone returns to the previous screen.
Anyone with any input on this?
{
"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"
}
Sent from my GT-I9300 using Tapatalk 2
Samething
Same problem with me, how you solved your problem?
Hi,
I never solved the problem.
I must say, I have not been working on it either.
I have been searching and searching but have not been successful in finding a solution.
Sent from my GT-I9300 using Tapatalk 2
Huum, but you were able to install Google Play? I already installed twice but the app keeps crashing everytime that I try to open it.
And I must say; I was frustrated to realize that my SGS3 didn't came with a SD card on it.
Hi,
I was able to install it yes, but have the same problem as you. It starts to load, and suddenly it just disappears.
No cash message, no nothing. That is why I think this is a limitation that is put there on purpose.
Sent from my GT-I9300 using Tapatalk 2
Sort of fixed
Hi,
Just for an update.
I was looking into getting a european rom on to my phone, but ended up doing a ROOT instead, and then install Google Apps.
Everything is just the way I like them now
To root and install CWM (Needed to install the Google Apps), i followed this guide:
*Can't link to the guide due to forum policies. PM me, and I will give you the link
After having downloaded the software neccesary, it took about 30 seconds for my phone to be ready.
I then did more or less as this guide *Can't link to the guide due to forum policies. PM me, and I will give you the link says.
With the only exception, that I copied the Google Apps zip-file to the SD card from Windows explorer, and bootet into recovery mode by holding the HOME, VOLUME UP and POWER button at the same time, after having powered off my phone.
Now, all the apps are working as I have been used to.
To solve your Problem and install official rom from Samsung to your phone you need to buy Odin Mobile.
For Chinese phone, when you use computer with odin, there is something that is blocked on the Phone so you cannot install any firmware from odin using the pc.
With odin Mobile u can flash >>>> personnally i flashed the one of Samsung GS3 HK because i still want to have some chinese stuff in my phone as i like to have.. And work perfectly !
Hope it will help you ! cordially!
Sunsenista said:
To solve your Problem and install official rom from Samsung to your phone you need to buy Odin Mobile.
For Chinese phone, when you use computer with odin, there is something that is blocked on the Phone so you cannot install any firmware from odin using the pc.
With odin Mobile u can flash >>>> personnally i flashed the one of Samsung GS3 HK because i still want to have some chinese stuff in my phone as i like to have.. And work perfectly !
Hope it will help you ! cordially!
Click to expand...
Click to collapse
I am not sure what you mean by
For Chinese phone, when you use computer with odin, there is something that is blocked on the Phone so you cannot install any firmware from odin using the pc.
Click to expand...
Click to collapse
But what I have done, is to find the modem-file for installation, and I am now using a rom called Omega, currently a version 19.
http://forum.xda-developers.com/showthread.php?t=1663656
First off, I install the ROM, and afterwards, I install the modem.
Everything seems to be working just fine.
The Omega rom, is the official Samsung rom, with some "hacks" - during installation you are for instance asked if you want the complete thing, or if you want to leave out all bloatware.
Official Samsung will no longer be available OTA, as the updating process detects, that the phone has been altered.
I live in China and own a SGS3 bought here in china. What you have to do is flash a kernel that is compatible with TRIANGLE AWAY to reset to zero the flash counter on the phone. Then you should be able to flash any original Samsung ROM made for the SGS3. If it doesn't work, you might also have to flash the stock XLH1 modem. Then it should work.
same problem
stallemanden said:
Hi,
Just for an update.
I was looking into getting a european rom on to my phone, but ended up doing a ROOT instead, and then install Google Apps.
Everything is just the way I like them now
To root and install CWM (Needed to install the Google Apps), i followed this guide:
*Can't link to the guide due to forum policies. PM me, and I will give you the link
After having downloaded the software neccesary, it took about 30 seconds for my phone to be ready.
I then did more or less as this guide *Can't link to the guide due to forum policies. PM me, and I will give you the link says.
With the only exception, that I copied the Google Apps zip-file to the SD card from Windows explorer, and bootet into recovery mode by holding the HOME, VOLUME UP and POWER button at the same time, after having powered off my phone.
Now, all the apps are working as I have been used to.
Click to expand...
Click to collapse
sorry, i'm new and i dont know how to send a PM. Can you send me the whole manual, because i worry to need the Samsung service again to repair my phone. Thank you
---------- Post added at 02:51 PM ---------- Previous post was at 02:46 PM ----------
Kremata said:
I live in China and own a SGS3 bought here in china. What you have to do is flash a kernel that is compatible with TRIANGLE AWAY to reset to zero the flash counter on the phone. Then you should be able to flash any original Samsung ROM made for the SGS3. If it doesn't work, you might also have to flash the stock XLH1 modem. Then it should work.
Click to expand...
Click to collapse
Hello thank's for your support. Are you sure that it will work with a Unicom brandet S3? I tried to flash it before, after this it doesn't work anymore. So i had to go to Samsung service point and pay to recover it. Thanks'
solution
Hello all,
i found the solution. The Chinese S3 has another boot sector, so it can't be flashed by Odin with any other firmware.
I found in a Chinese forum how to make it.
First you have to root, this was no problem.
You have to install mobile odin, because mobile doesn't flash the boot image.
Now you can copy any firmware to sd card and flash.
Best Regards
Congratulation to all who's been waiting for this!
First things first! Be careful, I'm not to blame if you brick your device.
WARNING - See the second post for reported problems
This ROMs are for the North American aka US devices (YP-GI1CB), if you have an international device (YP-GI1CW), you should go to this thread which was created by our good friend zebluk. Also there is a wonderful tutorial how to flash the rooted image in that thread, so you can follow it (but use the image from this thread). All credits to zebluk!
So..
-------------
When downloading from the mirrors, be warned, I have not checked them, you should check their integrity by calculating their sha1 hashes and comparing with ones I am providing for each file.
Here is the PIT file.
Here is the STOCK FACTORYFS ROM (size: ~260 MiB, sha1: 709ea3a1594fe4776065308a198e120129652b38)
Mirrors:
Mirror by ECLK09 (password: XDA-DEV)
Here is the STOCK KERNEL (size ~5.2 MiB): sha1: 25235a0ed6ad42cab1743b8f1c141248efb25647)
Mirrors:
Mirror by ECLK09 (password: XDA-DEV)
-------------
And here is the ROOTED STOCK ROM (size: ~260 MiB, sha1: 64ec57e6254b3c24ad7740b0c2bcad3a6e4bd26c)
Mirrors:
Mirror by ECLK09 (password: XDA-DEV)
-------------
Password for all the 7zip archives: XDA-DEV
First you should un-7zip your downloaded file, there you will have directoriy with a descriptive name and a tarball archive inside.
You can flash these tarball (without extracting) using Odin v3.04 (Attached) or extract the image file from the tarball archive and flash using Heimdall v1.3.1 (don't use the 1.3.2 version). I've personally tried flashing only with Heimdall under Linux, but Odin should work too.
If you are using Windows and you don't have device drivers, download them from here.
@Good Guy User:
DepositFiles is not the best filesharing service but works well for me, feel free to create mirrors and share links in PM, I'll post them here.
Greetz to: Entropy512 for showing the correct road, zebluk for help and advices, baruch6132 for flashing my untested rooted kernel and dumping the factoryfs, zaclimon and baladev for helping, Benjamin Dobell and Glass Echidna for Heimdall, jazzor for ext4_utils, William Enck for split_bootimg.pl, ECLK09 for providing mirrors for uploaded files, Green Day for being awesome, all who have helped or held breath for this, and to you!
Possible problems and workarounds
There are reported cases when the wi-fi stopped working after flashing the rooted factoryfs. And there are two reported solutions:
1. Backup the contents of /system/etc/wifi before flashing to restore them after flashing if you experinece the wi-fi problem. (This is the recommended way)
2. Flash the kernel.
---------------------------------
Added:
As it turned out in the International version (YP-GI1CW) thread, the highly possible reason for this is that there are slightly different versions of the devices. The full code of my device is YP-GI1CB/XAA. If your version is not the XAA (there is, for example, YP-GI1CB/XEG), just backup the contents of your /system/etc/wifi directory before flashing, then rewrite them back if you lose wifi after rooting.
Apologies if this is a dumb question, but I'm having trouble figuring out which version to use. I bought my device in the US from a retail store, so I'm assuming it's the US version, but my model number (both under the battery and in the "About Device" section) just says "YP-GI1". The android version is 2.3.6, and kernel is 2.6.35.7-CL1. Any ideas on how to find out if this is a CB or CW device?
Thanks a ton
direwolf1 said:
Apologies if this is a dumb question, but I'm having trouble figuring out which version to use. I bought my device in the US from a retail store, so I'm assuming it's the US version, but my model number (both under the battery and in the "About Device" section) just says "YP-GI1". The android version is 2.3.6, and kernel is 2.6.35.7-CL1. Any ideas on how to find out if this is a CB or CW device?
Thanks a ton
Click to expand...
Click to collapse
I'm pretty sure that it's the US version YP-GI1CB.
There are two reported cases when the wifi stopped working after flashing the rooted factosyfs.
Please report if you have successfully flashed and rooted without problems, so we can know if those two cases were exceptions due to some still unknown reason or there is a real problem. Thank you.
I'm an idiot--found the model number and it is indeed a US device. I'd like to download this and root it, but now I'm worried about the wifi issue. Any new reports?
Root successful, everything works fine
This is the first time I have rooted using Odin. I followed the instructions on the 4.2 Int. rooting page linked in the top (this is the US version, and I did use the files on this thread). Everything works great, wifi included. I installed AdAway and removed all of the Samsung bloat. Sorry about the pic quality, my nexus 7 vga camera is all that I have near me lol.
{
"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"
}
Hi, could you help me please! This is the firs time for my rooting a SGP 4.2. Can I root it using windows 7? I'm now downloading all the files attached by alice, but (here's the problem) I don't know what I should do with its.
AngelBoutto said:
Hi, could you help me please! This is the firs time for my rooting a SGP 4.2. Can I root it using windows 7? I'm now downloading all the files attached by alice, but (here's the problem) I don't know what I should do with its.
Click to expand...
Click to collapse
Follow the tutorial here (but use the ROM in this thread). It's how I did it. This was my first time using this method as well. The only file you need is the modified (aka rooted) ROM. Works great.
EDIT: NM I still had a nexus 7 tar in the same directory that I confused. Please ignore and thanks to all who got this root to work. Cant wait to we have kernels and such that support voodoo sound.
The second post (problems and solutions) has updated.
Users who have experienced the wifi problem after rooting, can you please write here you full device code (e.g. mine is YP-GI1CB/XAA) so we can know whether the problem is the existence of slightly different versions of the same device.
To find out your revision, enter in terminal getprop ril.product_code.
alice90 said:
The second post (problems and solutions) has updated.
Users who have experienced the wifi problem after rooting, can you please write here you full device code (e.g. mine is YP-GI1CB/XAA) so we can know whether the problem is the existence of slightly different versions of the same device.
To find out your revision, enter in terminal getprop ril.product_code.
Click to expand...
Click to collapse
My model is: YP-GI1CB/XEG
Think you know how I solved my wifi Problem. Kernel Flash and usb jigg
I rooted it using these instructions and it worked like a charm. Wifi is working great. Only issue I had was that my device seemed a little finicky when I was trying to get it into download mode, but I figured it out eventually. Thanks so much for this!
sedelman said:
Follow the tutorial here (but use the ROM in this thread). It's how I did it. This was my first time using this method as well. The only file you need is the modified (aka rooted) ROM. Works great.
Click to expand...
Click to collapse
I finish to install the rom rooted, but I think doesn't work for me. all in my device is the same, and and check with a rooted checker and said your device isn't rooted.
AngelBoutto said:
I finish to install the rom rooted, but I think doesn't work for me. all in my device is the same, and and check with a rooted checker and said your device isn't rooted.
Click to expand...
Click to collapse
Find the SuperSU app in the menu (it should be there if you flashed successfully) and open it, it will ask a question about replacing the su, confirm it.
Then try to install something that requires root and check whether it works.
Many thanks.
Complete success with Odin 3.04.
I was confused initially with Heimdall and mistakenly tried to load factoryfs.img as a Heimdall package which returned an error about a missing factoryfs.xml file. "factoryfs.img" is not a Heimdall package. If you want to use Heimdall simply to flash the factoryfs.img, I recommend using the command line.
heimdall flash --factoryfs factoryfs.img
No problems with WiFi after the upgrade as my device is YP-GI1CB/XAA, although I backed up my /system/etc/wifi folder just in case.
Thanks.
Finally!!! I did! But, now my problem is the RAM! in a few minutes the level of RAM is on the top! And my device start to be frozen for period of time... Could someone help me with that? Someone of you know if we can find ROM's modified?
AngelBoutto said:
Finally!!! I did! But, now my problem is the RAM! in a few minutes the level of RAM is on the top! And my device start to be frozen for period of time... Could someone help me with that? Someone of you know if we can find ROM's modified?
Click to expand...
Click to collapse
Try rebooting.I had the same problem as you then i rebooted and the problem went away.
kvn7918 said:
Try rebooting.I had the same problem as you then i rebooted and the problem went away.
Click to expand...
Click to collapse
I restart my device almost 5 times a day! The RAM runaway! When I open Skype, well in 30 second my device start to restart automatically.
i have a problem i use this rom the root rom, now my player the home button dont work any one have same problem please let me know model numbe yp-gi1
I've compiled the stock firmware for the Developer edition of the Galaxy S4. Specifically the 1545OYUAMDK variant that shares similarities to our beloved MDK. I got the partitions from users who had made backups prior to gaining root and/or other means to have the least modified version of the stock firmware. As far as the bootloader goes, I have the entire firmware and I edited the partitions to account for the padded zeroes and offsets. Below is a table of partitions, the green are those that I or dev edition owners were able to successfully flash with Heimdall/Odin and are signed, the red are ones that I am unable to flash probably because I incorrectly edited them to be consistent with the sha1 checksums of partitions verifying it immediately before or after or haven’t been tested by someone with a dev device.
I should note that I only tested this on a stock root ME7 build, therefore some partitions that I couldn't flash, the Dev edition of the Gs4 might be able to. I did confirm that users on OYUAMDK were able to flash certain parts of the firmware but no one has tried to completely go back to stock. As expected, I could flash all but recovery, boot, and aboot, djrbliss mentions that the difference between consumer and dev builds comes down to how aboot checks boot and recovery in his blog...so my findings are consistent with his research. I confirmed that the partitions that I did flash were actually flashed because I compared the hexdump of the files before and after (since the file sizes are mostly the same after cutting out the padded zeroes and other indicators). If you have a developer device and you absolutely need to flash stock firmware, this is probably as close as you will get, but more work needs to be done to refine this. Note, take precautionary measures and especially be careful when flashing aboot. Feel free to criticize these, and let me know if any changes need to be made. Use at your own risk and remember this is somewhat a work in progress.
Edit: One user on a dev build brick claims to have flashed aboot.mbn successfully. Status changed to yellow! (Need one more confirmation before I feel confident to give it the green light, pun intended)
Instructions:
Note that this is more meant for a emergency rather than convenience, also the purpose of this post was both to help the owners of development edition gs4 and to make the process better in the future, this can brick your device
If you do decide to dance with the devil, post your findings. The file is in tar.md5.gz format so odin will extract it to a tar.md5 for you or you can just flash it in heimdall. I have left the firmware.xml and pit file in the tar, you can remove them and edit them as needed.
Using Odin: Odin doesn’t play well with this. I’ve had varied results. Use Heimdall. But if you insist..have the latest Samsung drivers, try Odin versions 3.07+, make sure to run as administrator and select/click PDA then select the tar.md5.gz file. Also make sure that only "Auto Reboot" and "F. Reset Time" are checked before finally clicking start.
Using Heimdall: Load the package using frontend running as root. If you use Heimdall in the command line, then you probably already know what you're doing.
RECOMBINATION_I545OYUAMDK_562219_STOCK_RESTORE.tar.md5
MD5:b238ac352255f3b26593dffa6d7aa72f
Download
Download Mirror
Size: File/Partition:
2597816 RECOMBINATION_I545OYUAMDK_562219_STOCK_RESTORE.tar.md5
8 SGR.pit
2518320 system.img.ext4
9000 NON-HLOS.bin
9488 recovery.img
208 tz.mbn
1200 aboot.mbn
50856 modem.bin
268 sbl3.mbn
152 rpm.mbn
96 sbl1.mbn
4 firmware.xml
8072 boot.img
152 sbl2.mbn
Before I get asked "What happens when people on MDK or ME7 try to flash this"?
I'll tell you my results, from numerous flashes in odin/heimdall. My baseband and build type are both now OYUAMDK as shown below and my phone doesn't show a custom screen nor does my phone think its modified. However this doesn't change the fact that we cannot downgrade to a older kernel. This will not unlock your device if you're on MDK or ME7 and flashing this carries a high risk of bricking your device. When flashing the stock MDK restore, ME7 users usually get a "SW REV. CHECK FAIL: FUSED: 3, Binary: 1" message, however with flashing this on ME7 users will receive a "SECURE CHECK FAIL: aboot" message instead either way its a fail.
{
"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"
}
**
Changelog
10/14/2013 - Initial release
10/19/2013 - Confirmed boot.img and recovery.img flash succesfully - status changed to green
11/09/2013 - User claims to have flashed aboot.mbn succesfully on dev build - status changed to yellow!
Awesome Surge! Now somebody with a Dev ed device on me7 like sound-mind should try it and see if they could restore their device to developer...
Sent from my SCH-I545 Dev Edition using XDA Premium 4 mobile app
I am new to Heimdall. I am running it on a Windows 8 64 bit machine. Heimdall does not see the tar.md5.gz file....it seems to be looking for a tar.gz file. What am I doing wrong or what do I need to do. Thanks. This is a great resource to have,
Skeetch79 said:
I am new to Heimdall. I am running it on a Windows 8 64 bit machine. Heimdall does not see the tar.md5.gz file....it seems to be looking for a tar.gz file. What am I doing wrong or what do I need to do. Thanks. This is a great resource to have,
Click to expand...
Click to collapse
Download 7-zip or winrar. Then extract the tar.md5.gz so it leave you with just a tar.md5. Then either:
1. Rename it to a tar, extract the files, and customize the package you want to flash using heimdall then heimdall will make a tar.gz for you
or
2. Rename the tar.md5 to tar, then using 7-zip in the right click menu or from the 7zip file manager menu select "add to archive" and under archive format select gzip.
Alternatively you can use the tar.md5 with odin, but I highly suggest using heimdall instead. I've had odin flash the file for me, but more often then not it fails for this particular odin tar.
Great! Thanks!
Sent from my SCH-I545 using Tapatalk
Extraordinary progress and dedication and effort. Thank you so much!
So the file includes everything a stock Dev ed official Odin image would right? The red partitions are there even though you could not manage to flash them..
Sent from my SCH-I545 Dev Edition using XDA Premium 4 mobile app
Roland_D said:
So the file includes everything a stock Dev ed official Odin image would right? The red partitions are there even though you could not manage to flash them..
Sent from my SCH-I545 Dev Edition using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes the red partitions are still there. But as to whether it includes everything? Technically no, the cache.img.ext4, persdata.img.ext4, and hidden.img.ext4 arent there yet. Im going to have to look more into hidden.img.ext4 because Id include it but. As far as cache.img.ext4 and persdata.img.ext4 I haven't come across a clean copy of either yet. I thought about just usings MDK's but ill look into it more before I include any more partitions.
Upon opening Heimdall I notice that I have the options to Load Package, Flash and Utilities but "Create Package" is greyed out. How does that become enabled?
Skeetch79 said:
Upon opening Heimdall I notice that I have the options to Load Package, Flash and Utilities but "Create Package" is greyed out. How does that become enabled?
Click to expand...
Click to collapse
I haven't used Heimdall in Windows but in linux you have to go to utilities, click detect device, then select save as and save the .pit file. Im not sure if the Windows version of Heimdall has a command line either but if it does you could also type the equivalent of this:
sudo heimdall download-pit --output dev-SCH1545.pit
Click to expand...
Click to collapse
Then go to the Flash tab and under pit click browse and open the pit file you just downloaded. Then click add-->select a partition name-->click browse and navigate the the selected partition file-->Then click add. Now you should be able to use the Create Package option.
Surge1223 said:
Yes the red partitions are still there. But as to whether it includes everything? Technically no, the cache.img.ext4, persdata.img.ext4, and hidden.img.ext4 arent there yet. Im going to have to look more into hidden.img.ext4 because Id include it but. As far as cache.img.ext4 and persdata.img.ext4 I haven't come across a clean copy of either yet. I thought about just usings MDK's but ill look into it more before I include any more partitions.
Click to expand...
Click to collapse
My Dev edition has no modifications, not sure if that helps or not. I'm willing to post what you need as long as it doesn't contain any personal info.
I'm unable to download due to dropbox temp disabled
equake said:
I'm unable to download due to dropbox temp disabled
Click to expand...
Click to collapse
Yeah im in the process of changing file hosts, ill put up a temp mirrror though
Sent from my SCH-I545 using xda app-developers app
This is a great resource and compilation for Dev S4 owners. Have you made anymore progress with this or found anything more? Thanks again for all your hard work and dedication
Well I haven't heard from anyone regarding where heimdall is failing. I also haven't confirmed if people on Dev s4s that took the ME7 update were able to downgrade back to OYUAMDK or not. So far the radio and kernel along with sbl1-3, rpm and tz have been proven to work. I know recovery should work, as I'm able to take it apart successfully, and the build.prop says OYUAMDK. I'm hoping aboot works, aboot is the partition I'm waiting for results on.
Sent from my TouchPad using xda app-developers app
I thought
I was pretty much stock with root (stock recovery and boot images from Bait-Fish and yourself in the other thread) but I constantly had the custom and open lock icon screen when booting the phone. I was reluctant to load ROMS at this point without any sort of safety net (I did make a nandroid early on in case) - even though it is a developer phone and that is what you are supposed to do
I wanted to try the package you put together so I played it safe and just created a Heimdall package to flash the Boot and Recovery only. Flashing went great and now when I boot the phone I get the Samsung S4 boot screen along with the word "official" under about phone->status in the system settings. (if flashing boot and recovery did not work then i would have went as far as flashing the system.img.ext4 - so now I don't have to)
As I said, I flashed both the boot and recovery images posted by Bait-Fish and yourself in the other thread and stayed on a custom status but somehow these boot and recovery images did the trick.
Thanks again.
If you need me to test anything out please let me know.
It would be nice though if the S4 Developer Phone could received OTA's and/or have KIES recognize the phone. Being on MDK we are two builds behind the consumer version with no official way to upgrade and catch up. could I flash the consumer ME7 or MI1 build without worrying about locking the bootloader and my dev phone? If so, then could I always ODIN or Heimdall back down to MDK if I wanted to?
Edit: the recovery and boot images I downloaded from bait-fish were identical in size... does that make sense or should they be different?
Skeetch79 said:
I thought
I was pretty much stock with root (stock recovery and boot images from Bait-Fish and yourself in the other thread) but I constantly had the custom and open lock icon screen when booting the phone. I was reluctant to load ROMS at this point without any sort of safety net (I did make a nandroid early on in case) - even though it is a developer phone and that is what you are supposed to do
I wanted to try the package you put together so I played it safe and just created a Heimdall package to flash the Boot and Recovery only. Flashing went great and now when I boot the phone I get the Samsung S4 boot screen along with the word "official" under about phone->status in the system settings. (if flashing boot and recovery did not work then i would have went as far as flashing the system.img.ext4 - so now I don't have to)
As I said, I flashed both the boot and recovery images posted by Bait-Fish and yourself in the other thread and stayed on a custom status but somehow these boot and recovery images did the trick.
Thanks again.
If you need me to test anything out please let me know.
It would be nice though if the S4 Developer Phone could received OTA's and/or have KIES recognize the phone. Being on MDK we are two builds behind the consumer version with no official way to upgrade and catch up. could I flash the consumer ME7 or MI1 build without worrying about locking the bootloader and my dev phone? If so, then could I always ODIN or Heimdall back down to MDK if I wanted to?
Edit: the recovery and boot images I downloaded from bait-fish were identical in size... does that make sense or should they be different?
Click to expand...
Click to collapse
I can think of no circumstances where I would want my Dev Edition S4 to receive OTA Downloads. I want to avoid those. That is why I bought a developer device to start with. When the Devs have had a chance to see the updates features and incorporate them into new ROM releases that is soon enough for me. If indeed the OTA could be had without locking down the bootloader, I still would not want to accept it. So much goodness in custom roms. I don't consider myself behind at all if I wait for the latest updates to be incorporated into the Roms.
But TEHO, I guess.
Sent from my Hyperdriven Dev Edition Vzw SCH-I545 with KT kernel using Tapatalk 4
wtherrell said:
I can think of no circumstances where I would want my Dev Edition S4 to receive OTA Downloads. I want to avoid those. That is why I bought a developer device to start with. When the Devs have had a chance to see the updates features and incorporate them into new ROM releases that is soon enough for me. If indeed the OTA could be had without locking down the bootloader, I still would not want to accept it. So much goodness in custom roms. I don't consider myself behind at all if I wait for the latest updates to be incorporated into the Roms.
But TEHO, I guess.
Sent from my Hyperdriven Dev Edition Vzw SCH-I545 with KT kernel using Tapatalk 4
Click to expand...
Click to collapse
I hear you! What ROMS are you running and usually how do you go about installing them? (i.e. install custom recovery then flash the ROM as a zip?) I am pretty new to having a developer device and navigating around it. Does Hashcode's SafeStrap work for our dev device? if so, which version? Sorry I am asking so many questions, I am still a n00b, still green, getting my feet wet, I want to make the right decisions and do the right things without royally screwing anything up.
Skeetch79 said:
I hear you! What ROMS are you running and usually how do you go about installing them? (i.e. install custom recovery then flash the ROM as a zip?) I am pretty new to having a developer device and navigating around it. Does Hashcode's SafeStrap work for our dev device? if so, which version? Sorry I am asking so many questions, I am still a n00b, still green, getting my feet wet, I want to make the right decisions and do the right things without royally screwing anything up.
Click to expand...
Click to collapse
In regards to your question about installing ME7 or MI1 I would highly advise against it. We're currently trying to see if someone who already took the ME7 update on their dev phone is willing to test and see if this package will take them back to OYUAMDK, specifically if it will allow them to flash an older aboot. It does not work on consumer ME7 devices, but until we have confirmation from someone who is already on an ME7 build on their dev device, id hold off. As far as custom recovery...I believe you guys have the ability of using loki and/or just regular non loki'd twrp and cwm right? Id use those before I would use Safestrap at this point; more compatibility. Also if you wanted to be on the latest build why not install a ME7 rom? VRUAME7 stock root deodex is already up. I was working on the MI1 stock root deodex rom, but got side tracked lol. Its pretty much done, just cant get wifi to work all time yet. Oh and about the recovery and boot imgs and different sizes, they should be identical the only difference is I trimmed the padded areas, basically the same as you would get from an official Odin image.
{
"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"
}
"Full Firmware" is firmware 4 file or 5 file (BL_ , AP_ , CP_ , CSC_ , EFS_ ,...), sometimes is a single file (All_...) and include the standard PIT files. When you flash "Full Firmware" & PIT files, all devices partitions will be repair, re-fomat and factory reset devices.
When do need "Full Firmware" ?
Soft brick
Failed to mount a partition: efs, data, system,...
Failed flash firmware via Odin (stop at a partition: HIDDEN, CACHE,...)
Bootloop
Factory reset
Mod Edit: * * * IT IS YOUR RESPONSIBILITY TO VERIFY WHAT YOU ARE FLASHING TO YOUR DEVICE IS SAFE AND FOR YOUR DEVICE * * *
Mod Edit
1. Samsung Galaxy Note 8 (SM-N950F)
VietNam: N950FXXU1AQI1_N950FOXM1AQHF_XXV_7.1.1_FULL.zip (3,6G)
UK: N950FXXU1AQI1_N950FOXM1AQHF_BTU_7.1.1_FULL.zip (3,6G)
2. Samsung Galaxy Note 8 (SM-N950N)
S: N950NKSU1AQI2_N950NOKR1AQI2_SKC_7.1.1_FULL.zip (3,1G)
L: N950NKSU1AQI2_N950NOKR1AQI2_LUC_7.1.1_FULL.zip (3,1G)
K: N950NKSU1AQI2_N950NOKR1AQI2_KTC_7.1.1_FULL.zip (3,1G)
3. Samsung Galaxy Note 8 (SM-N950U)
USA: N950USQU1AQI9_N950UOYN1AQI9_USC_7.1.1_FULL.zip (3,5G)
Verizon: N950USQU1AQI5_N950UOYN1AQI5_VZW_7.1.1_FULL.zip (3,6G)
T-Mobile: N950USQU1AQI5_N950UOYN1AQI5_TMB_7.1.1_FULL.zip (3,4G)
Sprint: N950USQU1AQH7_N950UOYN1AQH7_SPR_7.1.1_FULL.zip (3,5G)
4. Samsung Galaxy Note 8 (SM-N950U1)
AT&T: N950U1UEU1AQI5_N950U1OYM1AQI5_ATT_7.1.1_FULL.zip (3,0G)
5. Samsung Galaxy Note 8 (SM-N950W)
Canada: N950WVLU1AQI5_N950WOYV1AQI5_XAC_7.1.1_FULL.zip (3,6G)
6. Samsung Galaxy Note 8 (SM-N950X)
Updating…
Mod Edit
Hi Thank you for hosting the firmware
I have tried this N950U1UEU1AQI5_N950U1OYM1AQI5_ATT_7.1.1_FULL.zip (3,0G) but you posted that as ATT. (there is no ATT bloatware at all)
I figured it out by N950U1 = No Carrier and N950U is carrier like verzon/ATT/TMB
this is Unlocked US version Note 8 like SM-N950UZKAXAA and sold by Samsung Direct or best buy so far .
kt.thegioiso said:
"Full Firmware" is firmware 4 file or 5 file (BL_ , AP_ , CP_ , CSC_ , EFS_ ,...), sometimes is a single file (All_...) and include the standard PIT files. When you flash "Full Firmware" & PIT files, all devices partitions will be repair, re-fomat and factory reset devices.
When do need "Full Firmware" ?
Click to expand...
Click to collapse
There's already a thread for the SM-N950F/DS Model:
https://forum.xda-developers.com/galaxy-note-8/how-to/official-stock-firmware-update-odin-t3677072
The correct unlocked (SM-N950U1) version can be found here:
https://forum.xda-developers.com/ga...covery-odin-recovery-software-t3671615/page22
The carrier versions of the Unlocked (SM-N950U1) "aqh9"...only differ by including the product activation information that the SIM provides during provisioning. Flashing the XAA unlocked firmware and inserting SIM is the same as flashing any of the SM-N950U1 brand labeled firmware like SPR AQH9...
---------- Post added at 05:38 AM ---------- Previous post was at 05:33 AM ----------
car2carl said:
Hi Thank you for hosting the firmware
I have tried this N950U1UEU1AQI5_N950U1OYM1AQI5_ATT_7.1.1_FULL.zip (3,0G) but you posted that as ATT. (there is no ATT bloatware at all)
I figured it out by N950U1 = No Carrier and N950U1 is carrier like verzon/ATT/TMB
this is Unlocked US version Note 8 like SM-N950UZKAXAA and sold by Samsung Direct or best buy so far .
Click to expand...
Click to collapse
...
Canada firmware link points to AT&T firmware. Could someone please update that link? I will be sending my phone in for refund (to get the N950F), and want to completely reset it.
Side note, anyone know how they check airtime usage to determine return eligibility? I'm well under 30 minutes, but I'm curious regardless.
https://www.sammobile.com/firmwares/SM-N950F/SWC/download/N950FXXU1AQI1/189026/
Is it possible that anyone can download this for me?
Edit: obsolet, retourned to shop with light bleeding on the hole left side.
I keep getting failed message when trying to flash the verizon firmware. any ideas.
thunderbread said:
I keep getting failed message when trying to flash the verizon firmware. any ideas.
Click to expand...
Click to collapse
Edit config file for UMS/patch from 0 to 1...and if regular Odin fails...use Prince Comsy's Odin...if still fail download firmware again...if still fail, boot to recovery and perform factory reset then flash again
Could I flash SM-N950F firmware on SM-N950N device? I need to change csc from Korea to Vietnam
Can someone help me? I installed a firmware con my Note8 and my storage decreased from 128 gb to 32 gb.
D_Gabe said:
Can someone help me? I installed a firmware con my Note8 and my storage decreased from 128 gb to 32 gb.
Click to expand...
Click to collapse
Sounds like you might not have re-partitioned it properly?
seandop said:
Sounds like you might not have re-partitioned it properly?
Click to expand...
Click to collapse
Nope. Apparently, when I installed the Unlocked firmware, it automatically partitioned my device. I had to do a factory reset to recover my 128gb storage.
It actually worked. Thanks anyway. I'm actually learning a lot. First time customizing an Android device (just changed from an iPhone 6 Plus).
D_Gabe said:
Nope. Apparently, when I installed the Unlocked firmware, it automatically partitioned my device. I had to do a factory reset to recover my 128gb storage.
It actually worked. Thanks anyway. I'm actually learning a lot. First time customizing an Android device (just changed from an iPhone 6 Plus).
Click to expand...
Click to collapse
Glad you figured it out! Welcome to Android.
So, would I be able to use this process to load the Verizon firmware to my Unlocked Note 8? I bought an unlocked version from Samsung, but there are several features that seem to be unavailable (visual voicemail, accessing internet when on phone, etc.). Would loading the Verizon firmware fix that issue for me?
Verizon tech support has not been of much use trying to get these features working on my unlocked phone, so I'm hoping that if it "magically" becomes a Verizon phone, the features would start working.
Note that I have tried Shortcut Master to get around these limitations, but no luck so far.
Croq360 said:
So, would I be able to use this process to load the Verizon firmware to my Unlocked Note 8? I bought an unlocked version from Samsung, but there are several features that seem to be unavailable (visual voicemail, accessing internet when on phone, etc.). Would loading the Verizon firmware fix that issue for me?
Verizon tech support has not been of much use trying to get these features working on my unlocked phone, so I'm hoping that if it "magically" becomes a Verizon phone, the features would start working.
Note that I have tried Shortcut Master to get around these limitations, but no luck so far.
Click to expand...
Click to collapse
Yes, download and flash the latest VZW firmware in Odin (all four files) and all will be well.
Deleted.
I can't get back to stock as I used the first method of samfail and now my bootloader reflects aqh8 and my system/baseband reflects aq15. I tried using Odin and get device mismatch errors I tried using kies it doesn't recognize my phone even in emergency mode. Any ideas how to get back to complete stock aq15 or at least on how to get bootloader to match system as aq15?
See how bl reflects aqh8? Is there a way to get it to match the rest at aq15? Or does everyone who used samfail root method look this way? How would I go back to Stock since I'm getting device mismatches in odin.
Please any help would be greatly appreciated
See mismatch
kirschdog1 said:
I can't get back to stock as I used the first method of samfail and now my bootloader reflects aqh8 and my system/baseband reflects aq15. I tried using Odin and get device mismatch errors I tried using kies it doesn't recognize my phone even in emergency mode. Any ideas how to get back to complete stock aq15 or at least on how to get bootloader to match system as aq15?
See how bl reflects aqh8? Is there a way to get it to match the rest at aq15? Or does everyone who used samfail root method look this way? How would I go back to Stock since I'm getting device mismatches in odin.
Please any help would be greatly appreciated
Click to expand...
Click to collapse
Use Prince Comsey Odin. You won't get the device mismatch errors.
sprint sm-N950USQU1AQI5 flashing to use on another carrier
I tried flashing with the zip file. But, I see invalid sim when I insert different carrier. Detailed desc would help me.
Or, is there any alternative to flash the sprint note 8(N950USQU1AQI5) to use different carrier.
Thanks in advance.
I have the variant of this phone by boost Mobile. There is so far as I can tell no way to do a normal bootloader unlock procedure on this device. So I have been trying to experiment trying to break or disable verity. Before I get any more excited, let me make sure I understand correctly. None of the partitions for example system, or boot or recovery cannot be flashed while verity is enabled, most certainly if you don't have root access on the device.
Well somehow, and I have yet to be able to repeat this, I was able to flash a system image in Odin, but the device would not boot because I successfully flashed it but because the other binaries did not match the signature of the "custom system". While doing this I was also able to downgrade from binary 8 to binary 7 (android 10 to 9). So I guess my question is, if I am able to repeat this process then how good is it that I am able to flash a system image and How likely would I be able to continue flashing the other partitions? Before I get into detail on how I managed or how I think I managed to do this I want to make sure that this can actually go anywhere before I waste my time.
Okay I I'm not sure if this is what happened that caused the custom system. Inside the AP tar file of the firmware for this device, is a zip file called 'fota'.for a minute it was useless because in order to extract any of the files from it or modify it you need a password, and chain fire just so happen to figure it out a while back and it still works. So with the password I can essentially delete any number of the files I want inside that zip, and it will still flash to the device successfully. Inside that file are various other files like ADBD, sbin and other various interesting files and bin files. I guess I have to experiment more but wouldn't I just be able to modify the fstab, also inside that zip file, to remove verification from the various partitions (verity)? I guess the question is would it still flash. And there's no way to find out without trying because magisk does not touch that folder.
i rooted 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"
}
Well it is a successful root, but it doesn't hold. Something stops it from taking fully. It will last for a minute or so before disappearing. So I looked at a logcat briefly and saw a few lines every so often mentioning something about the kernel and relocking it. I'm not at my PC right now so I can't post the logs.
DragonFire1024 said:
Well it is a successful root, but it doesn't hold. Something stops it from taking fully. It will last for a minute or so before disappearing. So I looked at a logcat briefly and saw a few lines every so often mentioning something about the kernel and relocking it. I'm not at my PC right now so I can't post the logs.
Click to expand...
Click to collapse
What files did you flash through odin?
sikkinixx said:
What files did you flash through odin?
Click to expand...
Click to collapse
only the ones I am able. Still haven't figured out how i downgraded from 10 to 9. I flashed the stock firmware (AIO firmware. apparently all carrier stock firmware can be flashed, regardless if its Boost Mobile [BST]). I however did flash the modem (CP) with modem.bin and modem_debug.bin from a combination firmware that's supposed to be factory binaries (which I can't flash any others from that combination because it tells me to get permission to flash them lol).
Im glad someone is trying this I just frp unlocked a galaxy s7 and im feeling confident about rooting this sm-a102u but its what i am using for my every internet access but Im cheering for you DragonFire1 You Got this !
majored said:
Im glad someone is trying this I just frp unlocked a galaxy s7 and im feeling confident about rooting this sm-a102u but its what i am using for my every internet access but Im cheering for you DragonFire1 You Got this !
Click to expand...
Click to collapse
I'm quite sure I don't. I've been able to mimic what I've been able to flash to the device. But regardless it doesn't matter because no matter what way I do or what I flash it fails all kinds of check sums. A lot of things do flash, but a bunch of red text comes across the screen that tells me about binary checks sum errors.but the images do flash to the device but until you restore the firmware that was previously on there it will never work again. I really do hate boost Mobile.
DragonFire1024 said:
I'm quite sure I don't. I've been able to mimic what I've been able to flash to the device. But regardless it doesn't matter because no matter what way I do or what I flash it fails all kinds of check sums. A lot of things do flash, but a bunch of red text comes across the screen that tells me about binary checks sum errors.but the images do flash to the device but until you restore the firmware that was previously on there it will never work again. I really do hate boost Mobile.
Click to expand...
Click to collapse
interesting well now that you mention that if you flash similar firmware cant you essentially add whats misssing i mean ive flashed over an install and still had wifi password saved and some apps im confusing myself now but im pretty sure thats how it went
majored said:
interesting well now that you mention that if you flash similar firmware cant you essentially add whats misssing i mean ive flashed over an install and still had wifi password saved and some apps im confusing myself now but im pretty sure thats how it went
Click to expand...
Click to collapse
It depends. So far I have only been able to use a different modem image and nothing else. Even if I flash the images that do match the flashed files that fail checksum, it still fails secure check. What i am confused about is how I am able to flash anything and even get a check sum failure. I was under the impression that images that fail anything, check sum or secure check, won't flash. So my question is how is it I am able to do so? If something is flashing there has to be a way to flash the files it needs.
So I have successfully made kingroot device owner. Not that it does any good because it doesn't seem to give me root. But using one of my favorite apps to seek the activity
Code:
com.kingroot.kinguser/.receiver.DeviceOwnerReceiver
I used dpm to set-device-owner. I did this from the most recent available firmware for this device on a fresh factory reset with no accounts attached.
Before that I also was able to make icebox apps freezer device owner and disable knox apps.
If anybody knows any other tricks I can use for device owner or something that can escalate privileges from here...
I love icebox apps freezer. You can set it as device owner and have the ability to freeze all applications Including system apps. I have been doing so one by one and as I do, some of Samsung's UI disappears and stock Android fills in. This is probably as close to root as I'll get for a while.
DragonFire, which files did you change in order to obtain root? I want to try this out for myself. Please respond
Nothing in the thread mentioning what files he flashed?
for anyone who needs to test code on this type device i have a sm-a102u1 unlocked running android 9 i wont send it off but i will test anybodys wierd root code maybe this exploit could work https://github.com/grant-h/qu1ckr00t let's make history guys i will be the dude who doesn't know what hes doing somebody compile this and tinker with it all you want and send it off to me to test i think CVE-2019-2215 will be our best bet of pwning this sucker i got a laptop running windows 10 for all your needs so if you like just wanna help but dont have the device or dont wanna brick yours be my guest
and even if you have almost 0 coding knowlage feel free to send your abomnation of a rooting software to just get it tested no matter how bad it is
even if you don't have the device
DragonFire1024 said:
Okay I I'm not sure if this is what happened that caused the custom system. Inside the AP tar file of the firmware for this device, is a zip file called 'fota'.for a minute it was useless because in order to extract any of the files from it or modify it you need a password, and chain fire just so happen to figure it out a while back and it still works. So with the password I can essentially delete any number of the files I want inside that zip, and it will still flash to the device successfully. Inside that file are various other files like ADBD, sbin and other various interesting files and bin files. I guess I have to experiment more but wouldn't I just be able to modify the fstab, also inside that zip file, to remove verification from the various partitions (verity)? I guess the question is would it still flash. And there's no way to find out without trying because magisk does not touch that folder.
Click to expand...
Click to collapse
DragonFire1024 said:
Well it is a successful root, but it doesn't hold. Something stops it from taking fully. It will last for a minute or so before disappearing. So I looked at a logcat briefly and saw a few lines every so often mentioning something about the kernel and relocking it. I'm not at my PC right now so I can't post the logs.
Click to expand...
Click to collapse
Sounds like debugging level needs set to Mid or High from the stock setting of low. This can be done and allow the root to stick until a user reboot.
Applying that whole method After, setting debug level, might actually work. It did for the Note5.
At that point, once root is achieved, it really comes down to making sure all partitions are mounted with the same options.
You can't just remount system as read/write only, if that partition normally has "noatime, etc" mounting options. That automatically triggers a verity panic reboot
You got to do the profit work, as well as, get every letter down to the T as far as copying stock fw. File names in Odin, CB, QL, Date fingerprints, file size to the byte (almost).
It's possible to spoof ALL Day, but most don't think (aka Over Think) all the possible checks and balances that would deviate from a standard stock download/flash.
DragonFire1024 said:
Well somehow, and I have yet to be able to repeat this, I was able to flash a system image in Odin, but the device would not boot because I successfully flashed it but because the other binaries did not match the signature of the "custom system". While doing this I was also able to downgrade from binary 8 to binary 7 (android 10 to 9).
Click to expand...
Click to collapse
Plenty of stock firmware packages in revision 8 ship as Android 9. So really it might not have downgraded as much as you think then.
And going from revision 8 to 7....which part of the firmware downgraded? Just the system image? Do you know this for sure if it couldn't boot?
The old samFAIL method would work something similar to that but you would've had to modify the system image you flashed first.
DragonFire1024 said:
Okay I I'm not sure if this is what happened that caused the custom system. Inside the AP tar file of the firmware for this device, is a zip file called 'fota'.for a minute it was useless because in order to extract any of the files from it or modify it you need a password, and chain fire just so happen to figure it out a while back and it still works. So with the password I can essentially delete any number of the files I want inside that zip, and it will still flash to the device successfully. Inside that file are various other files like ADBD, sbin and other various interesting files and bin files. I guess I have to experiment more but wouldn't I just be able to modify the fstab, also inside that zip file, to remove verification from the various partitions (verity)? I guess the question is would it still flash. And there's no way to find out without trying because magisk does not touch that folder.
Click to expand...
Click to collapse
But will flash successfully like you state or are you asking that question without modifying the otacerts first? Because normally the fota.zip contains a lot of data for most of those things you're saying is failing the checks.
So I'm just not sure about the entire story now....
Delgoth said:
Plenty of stock firmware packages in revision 8 ship as Android 9. So really it might not have downgraded as much as you think then.
And going from revision 8 to 7....which part of the firmware downgraded? Just the system image? Do you know this for sure if it couldn't boot?
The old samFAIL method would work something similar to that but you would've had to modify the system image you flashed first.
But will flash successfully like you state or are you asking that question without modifying the otacerts first? Because normally the fota.zip contains a lot of data for most of those things you're saying is failing the checks.
So I'm just not sure about the entire story now....
Click to expand...
Click to collapse
strange how he didnt post anything on how he did it
timba123 said:
If we pay $50 to $75 for a flash token, maybe factory combo could be flashed then root figured out from there but its not worth it to me to spend that for this pos. So stuck with adb debloat I guess. Oh well
Click to expand...
Click to collapse
I mean, after upgrading, yeah the A10e is a bit dated. BUT WAIT...
The A10e is still a device using an Exynos octa-core SoC. Not a snapdragon or mtk chipset. With full command line access and root privileges the hardware itself is actually still quite capable with its 2gb of RAM.