Hi, I just joined this forum and I'm hoping you guys can help me with my problem:
I have an S9+ with the FRP Lock on, a guy on Reddit told me that there is a way to unlock it. The phone in question is a SM-G9650 made in Argentina. And the other number that appears on the recovery menu when you do the Bixby + Vol Up + Power button is G9650ZHS6CSK4.
I've downloaded the correct firmware (I think that version was Android 9.0) for that number up there, and when I try to flash the phone with Odin, everything goes great, I first flash the AP file and the phone reboots, but it doesn't boot into "Factory Binary Mode" it just goes straight to the normal phone setup and in Odin I get no errors as you will see in the screenshots below:
{
"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"
}
So, what am I doing wrong? If I'm missing the combination ROM does anybody know where to find it? Please if any of you can help me I would be grateful!
Have a nice day!
Flameon266 said:
Hi, I just joined this forum and I'm hoping you guys can help me with my problem:
I have an S9+ with the FRP Lock on, a guy on Reddit told me that there is a way to unlock it. The phone in question is a SM-G9650 made in Argentina. And the other number that appears on the recovery menu when you do the Bixby + Vol Up + Power button is G9650ZHS6CSK4.
I've downloaded the correct firmware (I think that version was Android 9.0) for that number up there, and when I try to flash the phone with Odin, everything goes great, I first flash the AP file and the phone reboots, but it doesn't boot into "Factory Binary Mode" it just goes straight to the normal phone setup and in Odin I get no errors as you will see in the screenshots below:
So, what am I doing wrong? If I'm missing the combination ROM does anybody know where to find it? Please if any of you can help me I would be grateful!
Have a nice day!
Click to expand...
Click to collapse
YOU have a great day!!!!! Stop telling people what to do!! (totally joking)
all joking aside, yes, the combination file is the way to get past FRP. I have not looked at your file to make sure its the combination file needed in order to get past FRP, but that is indeed the process. You flash the combo firmware (not called a ROM) and then the phones actual firmware you need and the phone shouldnt ask for the google account info anymore.
Reddit is a good place to have quick conversations about how to address issues, but youll find that 99% of the people over there just refer back to XDA. Wonder why! LoL Anyways, ill look at the file you posted, but i am at work so some of my research will be limited due to the vile creature called Citrix.
here is a link that Citrix wouldnt let me get to due to the net nanny configured within the evil bastard Citrix.
https://combinationfirmware.com/combination-samsung-galaxy-s9-plus/
i cannot verify that link due tho the aforementioned evil gremlin Citrix, more so the netnanny, but you get my point
Thanks! I'll get started
Youdoofus said:
YOU have a great day!!!!! Stop telling people what to do!! (totally joking)
all joking aside, yes, the combination file is the way to get past FRP. I have not looked at your file to make sure its the combination file needed in order to get past FRP, but that is indeed the process. You flash the combo firmware (not called a ROM) and then the phones actual firmware you need and the phone shouldnt ask for the google account info anymore.
Reddit is a good place to have quick conversations about how to address issues, but youll find that 99% of the people over there just refer back to XDA. Wonder why! LoL Anyways, ill look at the file you posted, but i am at work so some of my research will be limited due to the vile creature called Citrix.
here is a link that Citrix wouldnt let me get to due to the net nanny configured within the evil bastard Citrix.
i cannot verify that link due tho the aforementioned evil gremlin Citrix, more so the netnanny, but you get my point
Click to expand...
Click to collapse
Thanks! I'll get started with that link, I'm not near my PC right now so I can't check the link comfortably, anyways from what I saw I didn't see the specific one that matches this code *G9650ZHS6CSK4* completely, does it has to be the EXACT same?
Flameon266 said:
Thanks! I'll get started with that link, I'm not near my PC right now so I can't check the link comfortably, anyways from what I saw I didn't see the specific one that matches this code *G9650ZHS6CSK4* completely, does it has to be the EXACT same?
Click to expand...
Click to collapse
no, it doesnt have to be the exact same, but certain parts are important. G9650 phone model #ZHS6 bootloader versionCSK4 build version
Youdoofus said:
no, it doesnt have to be the exact same, but certain parts are important. G9650 phone model #ZHS6 bootloader versionCSK4 build version
Click to expand...
Click to collapse
So, technically can I just use any combination firmware with the G9650 part in this case? I've been googling earlier but I haven't found one that completely matches that code, most likely I'm not looking on the right places
Flameon266 said:
So, technically can I just use any combination ROM with the G9650 part in this case? I've been googling earlier but I haven't found one that completely matches that code, most likely I'm not looking on the right places
Click to expand...
Click to collapse
model number and bootloader revision are the only really important parts as far as getting the phone to boot and/or not brick, the rest is mostly to determine which security update its on and what carrier its for
also the images in the OP dont show even on my daily driver home computer. I could check on one of the others too, but i dont think thats necessary.
Youdoofus said:
model number and bootloader revision are the only really important parts as far as getting the phone to boot and/or not brick, the rest is mostly to determine which security update its on and what carrier its for
also the images in the OP dont show even on my daily driver home computer. I could check on one of the others too, but i dont think thats necessary.
Click to expand...
Click to collapse
Hi again, I started looking for a combination firmware that matches the model number and bootloader but I haven't found any, can you help me out?
Flameon266 said:
Hi again, I started looking for a combination firmware that matches the model number and bootloader but I haven't found any, can you help me out?
Click to expand...
Click to collapse
hello, please excuse the sarcasm in my reply, but here ya go
https://bit.ly/2TPgiPU
sorry, couldnt help myself
Youdoofus said:
hello, please excuse the sarcasm in my reply, but here ya go
https://bit.ly/2TPgiPU
sorry, couldnt help myself
Click to expand...
Click to collapse
So, let me see if I understood correctly, even though my phone's version is G9650Z, the G965U will work just fine? I get the joke but at the same time, what I meant is that I couldn't find any combo firmware that has the G9650ZHS6 in the name
Flameon266 said:
So, let me see if I understood correctly, even though my phone's version is G9650Z, the G965U will work just fine? I get the joke but at the same time, what I meant is that I couldn't find any combo firmware that has the G9650ZHS6 in the name
Click to expand...
Click to collapse
im glad the art of humor isnt entirely lost here these days!! honest to god
G9650ZHS6 is the first part of your devices firmware, but the firmware combination file you want doesnt need to exactly match the first part tho. From what you have here, its telling you that the G9650 is the model number, the HS6 part is the bootloader, but in the US models, there are 2 characters following the model number representing the country code but this one only has one before the bootloader version. So, as long as the combination file is the same model number and the same bootloader version, it should be just fine. Odin will fail if you try to flash a BL revision lower than what is currently on the phone and i wouldnt recommend going higher if avoidable as you cant go back to a previous BL version once youve installed a newer one.
Youdoofus said:
im glad the art of humor isnt entirely lost here these days!! honest to god
G9650ZHS6 is the first part of your devices firmware, but the firmware combination file you want doesnt need to exactly match the first part tho. From what you have here, its telling you that the G9650 is the model number, the HS6 part is the bootloader, but in the US models, there are 2 characters following the model number representing the country code but this one only has one before the bootloader version. So, as long as the combination file is the same model number and the same bootloader version, it should be just fine. Odin will fail if you try to flash a BL revision lower than what is currently on the phone and i wouldnt recommend going higher if avoidable as you cant go back to a previous BL version once youve installed a newer one.
Click to expand...
Click to collapse
So, in this case, I already have the model number which is G6950, now, I need to find one that has the "S6" in it, being that, the bootloader version I'm looking for right?
Youdoofus said:
im glad the art of humor isnt entirely lost here these days!! honest to god
G9650ZHS6 is the first part of your devices firmware, but the firmware combination file you want doesnt need to exactly match the first part tho. From what you have here, its telling you that the G9650 is the model number, the HS6 part is the bootloader, but in the US models, there are 2 characters following the model number representing the country code but this one only has one before the bootloader version. So, as long as the combination file is the same model number and the same bootloader version, it should be just fine. Odin will fail if you try to flash a BL revision lower than what is currently on the phone and i wouldnt recommend going higher if avoidable as you cant go back to a previous BL version once youve installed a newer one.
Click to expand...
Click to collapse
I found this combo file G9650ZCU6ASJ2 , will it work? One more thing, the phone right now is on Android 9.0 and the combo I downloaded has "FA80" on the name, which, according to what I've read, it's Android 8.0, do I need to downgrade the phone to 8.0? Can I just flash the 8.0 firmware into it and then continue?
Flameon266 said:
I found this combo file G9650ZCU6ASJ2 , will it work? One more thing, the phone right now is on Android 9.0 and the combo I downloaded has "FA80" on the name, which, according to what I've read, it's Android 8.0, do I need to downgrade the phone to 8.0? Can I just flash the 8.0 firmware into it and then continue?
Click to expand...
Click to collapse
the android version doesnt really matter too much (outside of the requirement of factory resetting when going between versions usually). I am not 100% that the file you listed will work, but as long as it is for your device and is the correct bootloader version, it wont harm it.
Youdoofus said:
the android version doesnt really matter too much (outside of the requirement of factory resetting when going between versions usually). I am not 100% that the file you listed will work, but as long as it is for your device and is the correct bootloader version, it wont harm it.
Click to expand...
Click to collapse
And now I have another problem, when I flash it with the combination firmware, it starts and then immediately after Odin says "Fail" and the phone shows this:
FRP is enabled, ignore PIT download.
FRP is enabled, not allowed to download non-FRP abl binary.
What could it be?
Flameon266 said:
And now I have another problem, when I flash it with the combination firmware, it starts and then immediately after Odin says "Fail" and the phone shows this:
FRP is enabled, ignore PIT download.
FRP is enabled, not allowed to download non-FRP abl binary.
What could it be?
Click to expand...
Click to collapse
are you using patched Odin?
Youdoofus said:
are you using patched Odin?
Click to expand...
Click to collapse
Hmmmmm, no? I've downloaded the latest available version from the Odin site
Flameon266 said:
Hmmmmm, no? I've downloaded the latest available version from the Odin site
Click to expand...
Click to collapse
get this version and give it a try
https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
Youdoofus said:
get this version and give it a try
https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
Click to expand...
Click to collapse
Tried both patched versions attached in the post, none of them worked. Same issue.
Related
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
Sorry I posted this in the wrong area earlier and as you can probably guess I am very new to this. I have looked around on different sites and tried a few things with no success. I have an S4 Galaxy SCH-I545 v.I545VRSGPL1 and I want to upgrade it from it's present status of 5.0.1 to 7.1.2 or better and I have a few questions. 1) Does the phone have to rooted in order to do this and if so what do I use. From what I've read (and I hope I'm wrong) this particular phone from Verizon seems to be a difficult one. 2.) What would be the best performing upgrade for the phones hardware. Thanks to all for their help.
87lwrdr said:
Sorry I posted this in the wrong area earlier and as you can probably guess I am very new to this. I have looked around on different sites and tried a few things with no success. I have an S4 Galaxy SCH-I545 v.I545VRSGPL1 and I want to upgrade it from it's present status of 5.0.1 to 7.1.2 or better and I have a few questions. 1) Does the phone have to rooted in order to do this and if so what do I use. From what I've read (and I hope I'm wrong) this particular phone from Verizon seems to be a difficult one. 2.) What would be the best performing upgrade for the phones hardware. Thanks to all for their help.
Click to expand...
Click to collapse
1) This phone has a locked bootloader and has to remain on Touchwiz. Rooting methods are posted in the General section. You're stuck on Lollipop with this device, however you can flash other ROMs with Flashfire.
2. That would be software. Hardware is things such as the speaker, Home button, or the device itself.
{
"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"
}
Again, being new to this, what can I actually do to this phone? You say I'm stuck on Lollipop for the OS and Touchwiz for an interface what can I use to increase it's functionality and performance ability? I read where Marshmallow doesn't have as many significant changes from Lollipop as the changes were from KitKat to Lollipop but I always thought having the most current OS would aid you in using programs and security designed for newer OS's, just like with computers. What about security and update issues, will they stop supporting Lollipop leaving vulnerable? Or is that the idea, forcing you into buying a newer phone.
87lwrdr said:
Again, being new to this, what can I actually do to this phone? You say I'm stuck on Lollipop for the OS and Touchwiz for an interface what can I use to increase it's functionality and performance ability? I read where Marshmallow doesn't have as many significant changes from Lollipop as the changes were from KitKat to Lollipop but I always thought having the most current OS would aid you in using programs and security designed for newer OS's, just like with computers. What about security and update issues, will they stop supporting Lollipop leaving vulnerable? Or is that the idea, forcing you into buying a newer phone.
Click to expand...
Click to collapse
Pretty much, after 18-24 months companies just stop putting out new software (to get you to buy a new phone), that's part of the reason for using custom ROMs. This device is much older than that and has a locked bootloader, keeping you from doing a lot of things, like using a ROM with an unofficial kernel, so the latest software is not possible. The Sprint and TMo versions of this phone do not have locked bootloaders and are able to use Marshmallow and Nougat, etc. So root the phone using the one methods outlined in the General section (you need to use one that uses SuperSU to use Flashfire) of this forum and then use Flashfire to flash a custom ROM in the Android Development. New features and better functionality. I also recommend removing apps you don't use to decrease RAM consumption and increase performance.
Are you saying I can root this version of my S4 (Galaxy S4 SCH-I545 v.I545VRSGPL1) and then install a custom rom to it using either SuperSU or Flashfire, right? For this version of phone are there any custom roms you would suggest using that are designed more for it? Sorry for all the questions, I just don't want to do something I'll be sorry for or can't reverse or fix.
Again, thanks for all your help and guidance.
87lwrdr said:
Are you saying I can root this version of my S4 (Galaxy S4 SCH-I545 v.I545VRSGPL1) and then install a custom rom to it using either SuperSU or Flashfire, right? For this version of phone are there any custom roms you would suggest using that are designed more for it? Sorry for all the questions, I just don't want to do something I'll be sorry for or can't reverse or fix.
Again, thanks for all your help and guidance.
Click to expand...
Click to collapse
SuperSU is required to use Flashfire, but yes. I would Odin OF1 first or WiFi won't work, I would suggest Stanglitre's ROM it was the most stable I tried for the short time I had this device.
What do I use on build LRX22C.I545VRSGPL1?
I have seen other roms on the site but how do I know if they will work for my build of phone? I try to read as much as I can but the way some people talk and explain things in some of the posts it might as well be in a foreign language. lol. I hope in time I'll be able to understand all the meanings, but right it's a little tough and I don't want to mess things up because I wasn't sure of something. Are the roms made for specific builds or can any be used?
87lwrdr said:
I have seen other roms on the site but how do I know if they will work for my build of phone? I try to read as much as I can but the way some people talk and explain things in some of the posts it might as well be in a foreign language. lol. I hope in time I'll be able to understand all the meanings, but right it's a little tough and I don't want to mess things up because I wasn't sure of something. Are the roms made for specific builds or can any be used?
Click to expand...
Click to collapse
Yes they are for specific builds. You really picked one of the worst phones to start with. Do you have a PC?
Yes, I have a PC. I didn't know anything about this phone when I got it much less the problems I'm facing with it now. I just don't like these phone companies or anyone else backing you into a corner and forcing you to buy something newer because they quit taking care of that product when it's only a couple years old.
87lwrdr said:
Yes, I have a PC. I didn't know anything about this phone when I got it much less the problems I'm facing with it now. I just don't like these phone companies or anyone else backing you into a corner and forcing you to buy something newer because they quit taking care of that product when it's only a couple years old.
Click to expand...
Click to collapse
This device is more than a couple years old... But I would recommend downloading the OF1 firmware from wwe.sammobile.com and using the Odin program to flash it. Then you can use a few of the ROMs on here.
I believe I've flashed the phone successfully. The Baseband Version was - I545VRSGPL1 and now it is - I545VRUGOF1 The Android Version is still 5.0.1 At this point what can I do with or to it now? Thanks
87lwrdr said:
I believe I've flashed the phone successfully. The Baseband Version was - I545VRSGPL1 and now it is - I545VRUGOF1 The Android Version is still 5.0.1 At this point what can I do with or to it now? Thanks
Click to expand...
Click to collapse
You can now root it and flash a ROM. Just follow the rupturing instructions in the General section of the forum.
Not sure what happened but here goes. I flashed the phone to OF1 and then tried to root it so I could put on a new rom. I used kingoroot to root the phone and it showed rooted but could not load flashfire. tried a couple times but kept getting a message that the bianary was occupied and after that when I tried to boot it the phone would freeze on the verizon red boot logo. I tried to re-flash OF1 and now it's stuck on "software update failed" with a yellow triangle and under that it says " your device didn't update successfully". I'm gonna guess that all of this isn't a good thing and hope there is a possible fix for this. Any insight and help would be greatly appreciated.
87lwrdr said:
Not sure what happened but here goes. I flashed the phone to OF1 and then tried to root it so I could put on a new rom. I used kingoroot to root the phone and it showed rooted but could not load flashfire. tried a couple times but kept getting a message that the bianary was occupied and after that when I tried to boot it the phone would freeze on the verizon red boot logo. I tried to re-flash OF1 and now it's stuck on "software update failed" with a yellow triangle and under that it says " your device didn't update successfully". I'm gonna guess that all of this isn't a good thing and hope there is a possible fix for this. Any insight and help would be greatly appreciated.
Click to expand...
Click to collapse
Reflash OF1 with Odin and start over. I told you SuperSU was needed for Flashfire to work right. You need to use a root method that uses SuperSU. There is a couple guides in the General section of this forum.
It won't re-flash. I can boot the phone to d/l mode, then start odin, load the of1 file, it checks it successfully and when I hit start it starts working and stops in about ten seconds while trying to load "system.img.ext4" and shows FAILED
87lwrdr said:
It won't re-flash. I can boot the phone to d/l mode, then start odin, load the of1 file, it checks it successfully and when I hit start it starts working and stops in about ten seconds while trying to load "system.img.ext4" and shows FAILED
Click to expand...
Click to collapse
Try OC1 tar instead.
After numerous times of trying and using different cables and com ports it finally took the OF1 firmware successfully. I don't know if it was using a different port or cable or just a combination of all, but it worked. I used a root checker and it says it's not rooted. Now, do I root with SuperSU then use FlashFire to install the new rom?
87lwrdr said:
After numerous times of trying and using different cables and com ports it finally took the OF1 firmware successfully. I don't know if it was using a different port or cable or just a combination of all, but it worked. I used a root checker and it says it's not rooted. Now, do I root with SuperSU then use FlashFire to install the new rom?
Click to expand...
Click to collapse
Yes
Hi tell us how it was please...I am with the same trouble can not pass from lollipop don't have any rom mod nothing
Avoid and pass by a fool and a madman
Great effort! thank you very much.
can you update the boot extractor from your previous post? i don't understand how to change the code u said here. thanks
jaygan93 said:
can you update the boot extractor from your previous post? i don't understand how to change the code u said here. thanks
Click to expand...
Click to collapse
It seems that many suffered from the payload_dumper, including me, and I'm thinking of a new extractor, something like that it's a standalone executable, containing all needed runtime libraries inside it so you don't need to install python/vc++, based on latest android sources, automatically detects many things, could be used universally on any ota for any brand, any version, and if it can't, it shows an warning and needed info if possible, at least.
Big problems to do this is that android build environment doesn't support windows (linux or macOS only and I don't use them), I can't spend much time on this, some phones such as black shark uses different their own codes and hide/never reveal those... etc...., so it requires a huge effort/time and I'm just thinking....
However, I will update the extractor or build a new extractor in any ways better, even though it takes some time.
wga0 said:
It seems that many suffered from the payload_dumper, including me, and I'm thinking of a new extractor, something like that it's a standalone executable, containing all needed runtime libraries inside it so you don't need to install python/vc++, based on latest android sources, automatically detects many things, could be used universally on any ota for any brand, any version, and if it can't, it shows an warning and needed info if possible, at least.
Big problems to do this is that android build environment doesn't support windows (linux or macOS only and I don't use them), I can't spend much time on this, some phones such as black shark uses different their own codes and hide/never reveal those... etc...., so it requires a huge effort/time and I'm just thinking....
However, I will update the extractor or build a new extractor in any ways better, even though it takes some time.
Click to expand...
Click to collapse
Yeah, actually i found out there is some payload dumper without instal phyton or something else and just an exe to extract the full ota payload.bin like in this post https://forum.xda-developers.com/mi-a2/how-to/guide-install-payload-bin-twrp-t3865319 i did try to extract the full ota an it did extracted all the img like boot, vendor, system etc. but i'm not sure that the system.img extracted from this payload dumper is useable or faulty one, so i'm not dare to flash it. Btw, thanks for the response i appreciate it. i hope you can find the best solution for us too.
It will get an unlock when it produces the firmware in a complex way. When it will flash the system partition and get lock again when the system is booting.
This is not necessary.
jaygan93 said:
Yeah, actually i found out there is some payload dumper without instal phyton or something else and just an exe to extract the full ota payload.bin like in this post https://forum.xda-developers.com/mi-a2/how-to/guide-install-payload-bin-twrp-t3865319 i did try to extract the full ota an it did extracted all the img like boot, vendor, system etc. but i'm not sure that the system.img extracted from this payload dumper is useable or faulty one, so i'm not dare to flash it. Btw, thanks for the response i appreciate it. i hope you can find the best solution for us too.
Click to expand...
Click to collapse
I'd tried them also, and they also generated some images corrupted when using on Black shark ota. I tried almost payload_dumper I could find at internet, only one, payload_dumper-master for incremental has the needed operation for full payload, and no one worked for incremental.
MCT_ said:
It will get an unlock when it produces the firmware in a complex way. When it will flash the system partition and get lock again when the system is booting.
This is not necessary.
Click to expand...
Click to collapse
I can't understand your word exactly, but the system never do lock/unlock during update. And... why are you talking that here? It has nothing to do with 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"
}
com.blackshark.ota/com.blackshark.ota.ui.TestActivity
MCT_ said:
View attachment 5008907
com.blackshark.ota/com.blackshark.ota.ui.TestActivity
Click to expand...
Click to collapse
It seems that you're sending wrong letter to worng address... This thread is for image_extractor/payload_dumper
wga0 said:
It seems that you're sending wrong letter to worng address... This thread is for image_extractor/payload_dumper
Click to expand...
Click to collapse
I don't see any problems with it, other than checking the signature.
And I don't see any posts about how happy everyone is to use TWRP on their device.
MCT_ said:
I don't see any problems with it, other than checking the signature.
And I don't see any posts about how happy everyone is to use TWRP on their device.
Click to expand...
Click to collapse
then use it yourself and don't disturb others. This is not for TWRP, not for update as you did. No relation at all! If you want to help others, do it right way in right place. I will not answer you again sorry...
wga0 said:
then use it yourself and don't disturb others. This is not for TWRP, not for update as you did. No relation at all! If you want to help others, do it right way in right place. I will not answer you again sorry...
Click to expand...
Click to collapse
First you guys talked about how to break the integrity of the system, then began to flash twpr recovery, now take the topic to the section of how you are going to install the update despite the modems. All you are on is trying to install an update. You have disabled a lot of devices, but there is not a single img backup in the discussion topic to restore it. It feels like you're deliberately stalling.
MCT_ said:
First you guys talked about how to break the integrity of the system, then began to flash twpr recovery, now take the topic to the section of how you are going to install the update despite the modems. All you are on is trying to install an update. You have disabled a lot of devices, but there is not a single img backup in the discussion topic to restore it. It feels like you're deliberately stalling.
Click to expand...
Click to collapse
You are totally wrong. All of it. Where I say to use the TWRP?
It's you who ask how to flash it and you're wrong again because BS2 has no recovery partition. I disagree or ask extremely careful when need it for reasons many times in this forum. Search it. The other guys also never said 'flash'! It's only you who saying that and making problems. Your writings for fastboot is also wrong, you can see the difference between your wrings yourself. You can use any side of slot. Such as set_active or current_slot is only a environment variables used when boot. Your words about 'SELinux' or other thins also are all wrong from your misunderstanding.
Here're many people who can't update because they never receive the update OTA, can't receive any services because it never released officially at their country, already bricked because of those who don't know the things exactly (like you).... There're many people who needs help. My own is also still at MP4 and the distributer/reseller never think about update. It's even officially released version!!
All of this, such as analyzing the payload.bin, making images from them, and more.... is to help those people at least by SW method. Those people who can't get services can do these method to revive their phone, to cover their deficient hw/sw with other sw, if root is needed to do so, then rooting it in most safest way...
What am I doing this meaningless.... what a waste of time...
plz search all it again, and think it again. Plz don't screw up other people with wrong knowledge. See what other people ask us... even doing these things is short in time... I or other guys never need to do this. Just enjoy myself is more easy, pleasant. I start this because many people suffered from fakers, who ask money for a deficient rooting and many lost their important stock images, money, updates... warranty and times. Now you're doing that. read all those and plz stop the verbal diarrhea...
wga0 said:
You are totally wrong. All of it. Where I say to use the TWRP?
It's you who ask how to flash it and you're wrong again because BS2 has no recovery partition. I disagree or ask extremely careful when need it for reasons many times in this forum. Search it. The other guys also never said 'flash'! It's only you who saying that and making problems. Your writings for fastboot is also wrong, you can see the difference between your wrings yourself. You can use any side of slot. Such as set_active or current_slot is only a environment variables used when boot. Your words about 'SELinux' or other thins also are all wrong from your misunderstanding.
Here're many people who can't update because they never receive the update OTA, can't receive any services because it never released officially at their country, already bricked because of those who don't know the things exactly (like you).... There're many people who needs help. My own is also still at MP4 and the distributer/reseller never think about update. It's even officially released version!!
All of this, such as analyzing the payload.bin, making images from them, and more.... is to help those people at least by SW method. Those people who can't get services can do these method to revive their phone, to cover their deficient hw/sw with other sw, if root is needed to do so, then rooting it in most safest way...
What am I doing this meaningless.... what a waste of time...
plz search all it again, and think it again. Plz don't screw up other people with wrong knowledge. See what other people ask us... even doing these things is short in time... I or other guys never need to do this. Just enjoy myself is more easy, pleasant. I start this because many people suffered from fakers, who ask money for a deficient rooting and many lost their important stock images, money, updates... warranty and times. Now you're doing that. read all those and plz stop the verbal diarrhea...
Click to expand...
Click to collapse
This code is just a ".cmd " project and some draft entries from the "one-click" flashing engine using ADB.
wga0 said:
You are totally wrong. All of it. Where I say to use the TWRP?
It's you who ask how to flash it and you're wrong again because BS2 has no recovery partition. I disagree or ask extremely careful when need it for reasons many times in this forum. Search it. The other guys also never said 'flash'! It's only you who saying that and making problems. Your writings for fastboot is also wrong, you can see the difference between your wrings yourself. You can use any side of slot. Such as set_active or current_slot is only a environment variables used when boot. Your words about 'SELinux' or other thins also are all wrong from your misunderstanding.
Here're many people who can't update because they never receive the update OTA, can't receive any services because it never released officially at their country, already bricked because of those who don't know the things exactly (like you).... There're many people who needs help. My own is also still at MP4 and the distributer/reseller never think about update. It's even officially released version!!
All of this, such as analyzing the payload.bin, making images from them, and more.... is to help those people at least by SW method. Those people who can't get services can do these method to revive their phone, to cover their deficient hw/sw with other sw, if root is needed to do so, then rooting it in most safest way...
What am I doing this meaningless.... what a waste of time...
plz search all it again, and think it again. Plz don't screw up other people with wrong knowledge. See what other people ask us... even doing these things is short in time... I or other guys never need to do this. Just enjoy myself is more easy, pleasant. I start this because many people suffered from fakers, who ask money for a deficient rooting and many lost their important stock images, money, updates... warranty and times. Now you're doing that. read all those and plz stop the verbal diarrhea...
Click to expand...
Click to collapse
This guy seems to be high lol. he is actually accusing us of bricking his phone and many others deliberately. I never said flash TWRP but I guess he doesn't know the difference between flashing TWRP and booting it.
Anyways, just ignore him he is talking meaningless and talk about non related things in different threads.
KM7 said:
This guy seems to be high lol. he is actually accusing us of bricking his phone and many others deliberately. I never said flash TWRP but I guess he doesn't know the difference between flashing TWRP and booting it.
Anyways, just ignore him he is talking meaningless and talk about non related things in different threads.
Click to expand...
Click to collapse
When you get root, via /data/media/... there is a dependency of the partition with internal storage, but you do not mention this and suggest using flash in its various variations. :good:
I don't even have a development section:
My bootloader is closed, I'm waiting for an update.
I've tried everything here, from bs2pro firmware on bs2 to payload_dumper and update.
With Google's floating code, this won't work, or you'll end up in the stone age.
Code is constantly moving.
You must obtain superuser rights legally, via the server.
Why do you need ROOT if you don't have a BootLoader, Recovery and ROM ?
What would delete installation APKs from system/app without disabling services ?
You made a copy of the system in img format for two months, with ROOT license on Board.
wga0 said:
EDIT: I found that more images in the full Android 10 OTA are corrupted when extracted with the payload_dumper, even including the boot image and modem.img, which is critically related to boot. I write this urgently... and will update soon... (Plz use with REPLACE part, or with below modified code)
Please be careful when you use the payload_dumper for full payload.
I found the payload_dumper doesn't have all the operations needed. It supports only two operations, REPLACE_XZ(lzma compression), REPLACE_BZ(bz2 compression), but BlackShark full OTA requires REPLACE(no compression, bsdiff or other format) also, and it generates some images incorrectly. It doesn't show you an error or any sign of malfunction also.
It seems that using it for the boot image only is okay, but images such as vendor.img, system.img are not correctly generated and it can brick your phone.
You can use payload_dumper-master instead. It supports the REPLACE operation for full payload, although it requires the vc++14.0 to compile the bsdiff library. I think easy way is to copy the REPLACE part in payload_dumper-master to payload_dumper, and use that.
Or you can modify the boot_extractor I uploaded to extract all files. Just delete the search part (comparing partition name), then it will extract all images.
oh... you need to change one more part...
Code:
#SOURCE_BSDIFF for Black Shark
elif op.type == op.REPLACE:
if pat[:3] == b'BSD':
odata = bytes()
for ext in op.src_extents:
ofile.seek(ext.start_block*block_size)
odata += ofile.read(ext.num_blocks*block_size)
pat = bsdiff4.patch(odata,pat)
ndata = io.BytesIO(pat)
for ext in op.dst_extents:
nfile.seek(ext.start_block*block_size)
nfile.write( ndata.read(ext.num_blocks*block_size) )
This will work for all images, all OTA for other phones (universally), and for both full, incremental of course.
Click to expand...
Click to collapse
i wish i saw this before hard breaking my black shark 2 pro now it is stuck in EDL i bought it before 6 days and now i think i will throw it into the trash
abd96iq said:
i wish i saw this before hard breaking my black shark 2 pro now it is stuck in EDL i bought it before 6 days and now i think i will throw it into the trash
Click to expand...
Click to collapse
Salam bro, try to hold down volume down button + power button while you are in EDL mode "this might take upto 60 seconds". If this doesn’t work, then try holding volume down when your phone reboot. This should take you to fastboot, from there you can run my full restore Black Shark 2 Pro batch, which you can get it from here.
Hope this works for you, goodluck.
KM7 said:
Salam bro, try to hold down volume down button + power button while you are in EDL mode "this might take upto 60 seconds". If this doesn’t work, then try holding volume down when your phone reboot. This should take you to fastboot, from there you can run my full restore Black Shark 2 Pro batch, which you can get it from here.
Hope this works for you, goodluck.
Click to expand...
Click to collapse
I tried but unfortunately doesn't work bro
I have even contacted s-unlock team but to avail
I think i will throw it in trash .
I am really sad
Thank you bro
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.
{
"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"
}
My s8+ had UAE firmware on it, settings showed FD version but all other apps like HW info and antutu, Samsung members said F only.
Moving forward I tried to flash a custom official noble rom, and I clicked install twrp too. Fast forward after installation my phone only is stuck in downloading screen, and holding down volume down and power button keeps taking me back to download mode, and it won’t even boot or do anything else. It’s just stuck. I tried to flash official firmware from Odin, i wasn’t sure what my csc was so I flashed and tried every single rom of UAE and I could not flash a single one. It keeps failing. My sister has exams, and I’m being held responsible, I’m poor and my mom can’t buy her a new phone let alone fix this from a shop. I beg any kind soul to please help me out of this.
shafin123 said:
View attachment 5894253My s8+ had UAE firmware on it, settings showed FD version but all other apps like HW info and antutu, Samsung members said F only.
Moving forward I tried to flash a custom official noble rom, and I clicked install twrp too. Fast forward after installation my phone only is stuck in downloading screen, and holding down volume down and power button keeps taking me back to download mode, and it won’t even boot or do anything else. It’s just stuck. I tried to flash official firmware from Odin, i wasn’t sure what my csc was so I flashed and tried every single rom of UAE and I could not flash a single one. It keeps failing. My sister has exams, and I’m being held responsible, I’m poor and my mom can’t buy her a new phone let alone fix this from a shop. I beg any kind soul to please help me out of this.
Click to expand...
Click to collapse
Alright, lets fix this. Looking at what firmware is available for your phone. Can you please give me your CSC? Dial *#1234#" to figure out what you're current CSC code is.
shafin123 said:
View attachment 5894253My s8+ had UAE firmware on it, settings showed FD version but all other apps like HW info and antutu, Samsung members said F only.
Moving forward I tried to flash a custom official noble rom, and I clicked install twrp too. Fast forward after installation my phone only is stuck in downloading screen, and holding down volume down and power button keeps taking me back to download mode, and it won’t even boot or do anything else. It’s just stuck. I tried to flash official firmware from Odin, i wasn’t sure what my csc was so I flashed and tried every single rom of UAE and I could not flash a single one. It keeps failing. My sister has exams, and I’m being held responsible, I’m poor and my mom can’t buy her a new phone let alone fix this from a shop. I beg any kind soul to please help me out of this.
Click to expand...
Click to collapse
Wait...you can't dial. Well, what country are you in?
ethical_haquer said:
Alright, lets fix this. Looking at what firmware is available for your phone. Can you please give me your CSC? Dial *#1234#" to figure out what you're current CSC code is.
Click to expand...
Click to collapse
Sir, the phone does not do anything but go in download mode, this is a screen shot I kept before starting the flashing process
ethical_haquer said:
Wait...you can't dial. Well, what country are you in?
Click to expand...
Click to collapse
I am in Bangladesh, this is a second hand phone and I’m not sure but I sense that this used to be a single sim phone and the previous owner put a dual SIM card tray and installed firmware for FD model, and somehow both sims did use to work just fine.
I’ll tell you where everything went wrong and what was the state of the device so that you can make a better judgement of where I ****ed up.
1. I used adb fast boot from cmd to reboot the phone into fastboot.
2. I installed linageos 19.1 android 12 version and the phone was working perfectly. The custom rom was installed.
3. Then I wanted to tweak the phone to increase battery life, stop over heating and screen flicker so I did some research and downloaded hadesRom v12.0 Pie S8/S8+/Note8 and stored it in my phone memory and flashed it in the similar way as linage OS. I also went ahead and tried to install a2n kernel. When trying to install, I received a message saying that I’m trying to install a wrong kernel where my g955 is “N” and not “F” which indicates that it’s a Korean variant but this contradicts everything I’ve done before, anyway that didn’t create a problem but I did this without even rebooting after the hades rom. Ever since then, I’ve been booted back to download mode and I’ve tried flashing official firmwares but nothing helped. It failed every time I’ve been up all night since yesterday and my mother is on the verge of kicking me out, I’m pulling my own hair to find out what is actually wrong but I can’t find anything.
All details of what has been done to the device***
ll tell you where everything went wrong and what was the state of the device so that you can make a better judgement of where I fvkd up.
1. I used adb fast boot from cmd to reboot the phone into fastboot.
2. I installed linageos 19.1 android 12 version and the phone was working perfectly. The custom rom was installed.
3. Then I wanted to tweak the phone to increase battery life, stop over heating and screen flicker so I did some research and downloaded hadesRom v12.0 Pie S8/S8+/Note8 and stored it in my phone memory and flashed it in the similar way as linage OS. I also went ahead and tried to install a2n kernel. When trying to install, I received a message saying that I’m trying to install a wrong kernel where my g955 is “N” and not “F” which indicates that it’s a Korean variant but this contradicts everything I’ve done before, anyway that didn’t create a problem but I did this without even rebooting after the hades rom. Ever since then, I’ve been booted back to download mode and I’ve tried flashing official firmwares but nothing helped. It failed every time I’ve been up all night since yesterday and my mother is on the verge of kicking me out, I’m pulling my own hair to find out what is actually wrong but I can’t find anything
shafin123 said:
it keeps failing.
Click to expand...
Click to collapse
How?
Also, what version of Android did you have with stock? - Right now it looks like I can only download A9 for your device.
ethical_haquer said:
How?
Click to expand...
Click to collapse
Secure check fail: (pit)
And then if I reboot the phone into download mode, and reset and start the process from scratch again, it fails and the error this time is write operation failed
ethical_haquer said:
Also, what version of Android did you have with stock?
Click to expand...
Click to collapse
Android 9 on stock, then installed linageOS with android 12 then flashed hades ported android 9 and that’s where it went wrong
I
shafin123 said:
Secure check fail: (pit)
And then if I reboot the phone into download mode, and start Odin, fails and the error is write operation failed
Click to expand...
Click to collapse
I’ve even tried multiple csc in both Odin 1.3 and the latest one. I haven’t left any stone unturned from my knowledge. All adb drivers and Samsung drivers are installed as well
shafin123 said:
Android 9 on stock, then installed linageOS with android 12 then flashed hades ported android 9 and that’s where it went wrong
Click to expand...
Click to collapse
So do you want to go back to stock A9 or LOS19, both are an option.
shafin123 said:
I’ve even tried multiple csc in both Odin 1.3 and the latest one. I haven’t left any stone unturned from my knowledge. All adb drivers and Samsung drivers are installed as well
Click to expand...
Click to collapse
Is this with F, or FD as the end of the model firmware?
It sounds like the PIT error happens when the firmware isn't the right version.
Also, do you want the BNG (Bangladesh) firmware or something else?
ethical_haquer said:
So do you want to go back to stock A9 or LOS19, both are an option.
Is this with F, or FD as the end of the model firmware?
It sounds like the PIT error happens when the firmware isn't the right version.
Also, do you want the BNG (Bangladesh) firmware or something else?
Click to expand...
Click to collapse
BNG firmware is fine, I don’t know if I should flash F or FD, as I’ve tried both and both have failed. I’d rather go back to A9 and then work my way around. And I have all the firmwares downloaded. I think I’ve messed up my boot loader somehow.
ethical_haquer said:
So do you want to go back to stock A9 or LOS19, both are an option.
Is this with F, or FD as the end of the model firmware?
It sounds like the PIT error happens when the firmware isn't the right version.
Also, do you want the BNG (Bangladesh) firmware or something else?
Click to expand...
Click to collapse
Beggars can’t be choosers, I just want the phone to work again, and somehow get out of the download mode
shafin123 said:
Beggars can’t be choosers, I just want the phone to work again, and somehow get out of the download mode
Click to expand...
Click to collapse
So, what exactly happens when you flash the firmware, a PID error?
Secure check fail: (pit)
And alternatively
Write operation failed, this is after I get pit fail and try again
shafin123 said:
Secure check fail: (pit)
And alternatively
Write operation failed, this is after I get pit fail and try again
Click to expand...
Click to collapse
Look at this tutorial. I've followed it before. Just make sure that you're flashing it properly with Odin, as you need to make sure you wipe the device:
As you can see, flashing the CSC file will wipe, whereas the HOME_CSC will not.
ethical_haquer said:
Look at this tutorial. I've followed it before. Just make sure that you're flashing it properly with Odin, as you need to make sure you wipe the device:
As you can see, flashing the CSC file will wipe, whereas the HOME_CSC will not.
Click to expand...
Click to collapse
Yes I’m aware and only using the CSC file not home.
shafin123 said:
Yes I’m aware and only using the CSC file not home.
Click to expand...
Click to collapse
Try looking at these solutions. Let me know if it still doesn't work.