Hi sorry to ask but this tutorial wont work. To create a combination firmware to bypass Google FRP I'll summarize it for you all. First rename the AP and BL files to .zip next extract them using 7zip to their own folders. Copy only certain files to a folder, zip it back up, and install it with Odin.
Now the problem is It seems Samsung has messed with these images since 2020. The BL (once extracted) has had all the images just broke into smaller parts so you cant tell what is what anymore. No more 3 files now its a giant mess and the data that holds the FRP info must be in there.
The AP has also changed but the file is just named super.img.lz4 instead of system.img.lz4 so nothing much.
Any path two lead me in the right way would be greatly appreciated. Thanks and have a great summer everyone.
Related
in order to create a flashable bootloader.zip we need to be able to extract the bootloader-flo-flo.4.04.img file all the img utilities I tried to unpack that file give a bunch or errors
can anyone see if they are able to unpack that file with imgtool or imgRePackerRK or other?
If anyone can try and unpack the bootloader-flo-flo.4.04.img file I am not sure why I keep getting bad file descriptor errors when trying to unpack it using imgtool
with that unpacked it should be easy to make a flashable bootloader, and there are a bunch of people all over that need this that either do not have access to a machine or like myself the USB port is not working at all on the device.
I second this!
Please!
Pleeeeeease!!!!
OPO Yeauh!!!
Agreed! I currently donr have a computer so i cant update rhe bootloader
The recovery flashable bootloader can now be downloaded from the link posted in this thread http://forum.xda-developers.com/nex...shable-factory-image-zips-android-5-t2939599/
Be sure to thank @eksasol I bugged him so much I feel really bad now, awesome work!
Hi all, having a strange issue with a signed update zip file.
i have an update i need to modify, i made the changes and signed it properly, but update failed.
to make sure, i just unzipped the original file and zipped it again (no changes and all signatures shouldn't change) - update failed AGAIN.
(BTW i also tried to sign after zipping, that didn't help as well).
the original zip and the new one aren't the same size, but when extracted all files are identical.
would appreciate any direction here..
some specific info - i'm trying to modify a connected car (FlyAudio) update file, the recovery is proprietary so there's little info on why it fails.
bigfoot2047 said:
Hi all, having a strange issue with a signed update zip file. i have an update i need to modify, i made the changes and signed it properly, but update failed. to make sure, i just unzipped the original file and zipped it again (no changes and all signatures shouldn't change) - update failed AGAIN. (BTW i also tried to sign after zipping, that didn't help as well). the original zip and the new one aren't the same size, but when extracted all files are identical. would appreciate any direction here.. some specific info - i'm trying to modify a connected car (FlyAudio) update file, the recovery is proprietary so there's little info on why it fails.
Click to expand...
Click to collapse
Typically, update.zip files are recovery flash files and ODIN doesn't flash zip files in that manner.
***Please Note: As always, I welcome any member to help with further valuable information/clarification for any of my posts.
Sent via Communicator [d2vzw] from the Bridge of the U.S.S. Enterprise.
ok, so the problem is that the update.zip (it has a different name but it's an 'update.zip' file) wasn't signed.
after extracting, zipping, signing i'm getting a file that's ~1K smaller than the original and identical up to that point.
the tool i'm using to sign uses test keys so i assume it's a keys issue.
--------------------------
update - needed to sign with -w (signapk option) that added the required footer.
thanks all
Good day all,
I am hoping someone can help me out and explain what I am not doing correct or point me in the right direction.
I have been reading the forums for quiet some time and have learned alot and want to thank everyone for their posts.
My question is I have taken apart the combination file and have been able re create the tar ball and successfully push it back onto the phone. ( I know some of these eng boot and combination files are digitally signed and I have not figured out how to confirm this). The issue is when I push this file with odin it wipes the user data which is the issue.
I then began digging deeper into the img files and located within the cache.img/recovery/command:
--carry_out=csc_factory
--wipe_data
Which will wipe the data. I have tried removing this along with changing the csc_home which would not wipe the user data if I understand this correctly. Once I modify the file I change the permissions back to read only and convert the cache.img to an android sparse file and create the tar-ball. I am now going through the system.img and boot.img to see if I can possibly modify these to bypass mounting the cache.img.
I am not sure if any of this will work and not sure why its not working so any advice would be very helpful.
Thanks,
San
hi, trying to flash PL1 onto my note 5 but in all downloads the BL file was corrupt, droidvoider has kindly supplied the files in another post on here, but they were all separate files, can anyone tell me how to pack the individual files to make the BL file please?
thank you in advance for your help
Hello Guys,
i opened the thread in the Question&Answer Forum but somehow i have an different approach now that i learned how to rollback an firmware version with an locked bootloader. i dont know if it is possible, i more want to open like a discussion about it if this would be an thing someone could possibly do (and thats the reason im opening another thread for it, since it is not the same question anymore as in the other thread).
well, you can flash an image like EML-L29 8.1.0.129 to the device via the dload method. this image installs just fine, great. but now.. in my understanding the interesting part is this update.app. this update.app as far as my knowledge goes contains all this img files. you know, kernel system boot recovery etc.. wouldnt it be possible to simply replace the recovery.img with an twrp recovery.img, put the update.app back together, zip it in the necessary update_sdcard file and try to install it? i read about the tool "HuaweiUpdateExtractor", and this handy nice tool is showing the files.
another thought of me is: the installer is *verifying* the update.app somehow. but if it is verifying this file, there must be like a crc-file, some way of telling "this file is original" or "this file is okay". so maybe this is another part of the problem that i would have to take care of. but still i would need to know a lot more about the way the eRecovery works.
my ultimate goal is to solve the bootloader code problem since tackling it with dc-unlock and hcu wont work cause the security patch level seems already too high in the first versions of this phone. im basically search now ways around it - i know, there is actually no way to do it, but this is the reason why im opening this thread in hope to get some clues or ideas - and telling my own. oh and im pretty sorry if this is maybe annoying, i surely dont have any intention of spam the forums or stress too much on this topic (but it got me very interested).
Edit: i read in another board that it is nearly Impossible to switch the img files because they are encrypted. I guess it is not possible with this method so basically.. just ignore this thread. I guess there is really no way.
Also I think they have to do some checksum when flashing, so it's really impossible to just switch files...
About dload, i'm on 9.0.0.293 on EML-L29C432
I try the dload method to rollback to android 8.1, no success
i use an usb otg, created dload folder to root and place update.app extracted zip in dload folder
Also i created an "EML-L29_hw_eu" folder inside dload with again extracted from the hw zip file
When i use the dialer method, phone recognize the update.app file and reboot
after reboot to recovery, i have an error and i can't downgrade
What i did wrong ?
thanks
bender8125 said:
About dload, i'm on 9.0.0.293 on EML-L29C432
I try the dload method to rollback to android 8.1, no success
i use an usb otg, created dload folder to root and place update.app extracted zip in dload folder
Also i created an "EML-L29_hw_eu" folder inside dload with again extracted from the hw zip file
When i use the dialer method, phone recognize the update.app file and reboot
after reboot to recovery, i have an error and i can't downgrade
What i did wrong ?
thanks
Click to expand...
Click to collapse
well the biggest problem may be the image itself that you are trying to flash. if you take it from firmwarefinder, you will get most likely absolutely no success. you need to take one from androidhost.ru, the ones there worked for me. there you just put everything in the dload folder on your USB-Stick. oh and better use an full-OTA, not just an simple ota update, because that wont work (you cant just update a few files when you are already on EMUI 9). and on top of that: backup your phone first, because it is possible that after your downgrade you lose all data on your phone.
oh and another thing if you just want to get back to EMUI 8.1 (not a specific version you wish for), just use hisuite, because they are allowing the downgrade even more easily. the method i mentioned above is if you try to flash a specific version like i did with 8.1.0.120