Develop Bugs

[q] emergency help needed kernel tar or stock tar

Hi guys so I've been messing with kernels and BinDroid. Well it seems that the stock kernel provided by BinDroid has an invalid md5 and if the md5 is removed and I attempt to flash anyway it hangs in odin and won't flash. I cannot boot into TWRP to flash my zip files. I can't find any freaking tar back to stock. PLEASE HELP my tablet is currently UNUSABLE.
EDIT:
Tried to flash a stock md5 from SamMobile in odin 3.09. It came back fail during flashing system.img. Now it won't turn on dear god any ideas?
EDIT ITS NOT DEAD!!!!
It now comes to a screen saying Firmware upgrade encountered an issue please select recovery mode in Kies and try again. PLEASE PLEASE HELP
From emergency recovery screen I reflashed the image my device is now booting again!!! Huzzah!!!

S4 Mini issues

I once tried to "Unroot" my phone by factory restoring it then flashing a stock rom and original firmware through Odin. Flashing the stock rom worked however when I tried to flash the firmware through Odin I got an "ext4 image fail" error. I am now stuck with a phone that does not boot. It is just stuck on a "Connect to Kies for emergency recovery" screen - but my phone is never detected in Kies. I cannot boot into recovery mode: I tried and I get the Samsung logo with the blue "RECOVERY BOOTING" text at the top for a split second, but then the screen goes black and I get this message at the top of the screen:
"image size too large!! W:1000, H:1920
display image fail
SECURE FAIL: KERNEL"
Basically, I had 4.2.2 Jellybean installed but wanted Kitkat (this was much earlier this year) and so I found a method of installing KitKat which also gave root access. Can't remember what I did to install it.
I have now successfully flashed CWM recovery through Odin but I have absolutely no idea what to do next. All the guides I have read talk about installing something through an SD card via the recovery menu, which I obviously cannot do because I can't reach the recovery menu.
Anyone know the steps to take?

SoulWithin said:
I once tried to "Unroot" my phone by factory restoring it then flashing a stock rom and original firmware through Odin. Flashing the stock rom worked however when I tried to flash the firmware through Odin I got an "ext4 image fail" error. I am now stuck with a phone that does not boot. It is just stuck on a "Connect to Kies for emergency recovery" screen - but my phone is never detected in Kies. I cannot boot into recovery mode: I tried and I get the Samsung logo with the blue "RECOVERY BOOTING" text at the top for a split second, but then the screen goes black and I get this message at the top of the screen:
"image size too large!! W:1000, H:1920
display image fail
SECURE FAIL: KERNEL"
Basically, I had 4.2.2 Jellybean installed but wanted Kitkat (this was much earlier this year) and so I found a method of installing KitKat which also gave root access. Can't remember what I did to install it.
I have now successfully flashed CWM recovery through Odin but I have absolutely no idea what to do next. All the guides I have read talk about installing something through an SD card via the recovery menu, which I obviously cannot do because I can't reach the recovery menu.
Anyone know the steps to take?
Click to expand...
Click to collapse
Not quite sure what you mean by flashing rom & firmware as it's the same thing, I guess you mean you flashed multipart rom files as separate items. Or did you flash "extra" files, by which I mean flash a full stock rom plus some duplicates eg csc, bootloader etc at the same time? Not sure if this would just overwrite or cause issues. Is there a procedure you followed? Eactly what files did you flash?
Anyhow, I think your first problem is that your cwm recovery has not installed properly. CWM is not maintained anymore The first thing I would do is try to flash a stable TWRP for our phone (see ne0zone75's TWRP thread) as this is maintained. If after flashing TWRP you still can only access download mode then you should flash a full stock rom (1 file with 4 files inside) as others have done to solve "image size too large" problem (try different Odin version if fails). If you can boot into recovery thin you can flash a zip file (though I think it would be a good idea to flash a full stock rom so you at least starting with a known configuration , then flash a custom rom or root it)

bootloop issue when tried to rollback

i tried rollback from Oreo to Nought. after flashing .img files through TWRP i got error like.......,
Error
Func no: 10 (boot image)
error no: 2 (load failed)
please help. suggest the Oreo stock boot.img link
thanks in advance
if same post already exist pls link me through
i searched xda i didn't find a solution.
i've unlocked bootloader !

babu.123 said:
i tried rollback from Oreo to Nought. after flashing .img files through TWRP i got error like.......,
Error
Func no: 10 (boot image)
error no: 2 (load failed)
please help. suggest the Oreo stock boot.img link
thanks in advance
if same post already exist pls link me through
i searched xda i didn't find a solution.
i've unlocked bootloader !
Click to expand...
Click to collapse
Roll-back is possible, but not like that.
To help or suggestions what you I can try. Will need to know what you flashed, where you flashed it, what was any message after or during flashing.
Also need to know if twrp also gives this type of message, or if it boots.
As far as link to Oreo stock images. Need to know what model and build number. (You know there are almost 10 model/region combo's and each has at least 3 builds)

mrmazak said:
Roll-back is possible, but not like that.
To help or suggestions what you I can try. Will need to know what you flashed, where you flashed it, what was any message after or during flashing.
Also need to know if twrp also gives this type of message, or if it boots.
As far as link to Oreo stock images. Need to know what model and build number. (You know there are almost 10 model/region combo's and each has at least 3 builds)
Click to expand...
Click to collapse
Model : BND-al10
Got oreo as beta tester.
From firware finder app download roll back full ota package. And extracted that update.app and flashed boot, system, and stock recovery.
After that try to reboot the device. Stucked at bootloop.
Twrp is working. When i try to restore (i had backup the system, ext. Data) restore process success but error ahows as
Alert
Update the system again
Error
Func no: 10 (boot)
Error no: 2 ( load failed).
I tried another zip files to flash through memory card but zip loading failed in twrp.

babu.123 said:
Model : BND-al10
Got oreo as beta tester.
From firware finder app download roll back full ota package. And extracted that update.app and flashed boot, system, and stock recovery.
After that try to reboot the device. Stucked at bootloop.
Twrp is working. When i try to restore (i had backup the system, ext. Data) restore process success but error ahows as
Alert
Update the system again
Error
Func no: 10 (boot)
Error no: 2 ( load failed).
I tried another zip files to flash through memory card but zip loading failed in twrp.
Click to expand...
Click to collapse
Should have used hwota or hurupdater to flash the fullota, not extract the images, but too late for that.
Wow, what a mess.
For starters, to explain some of what seems to have happened.
Nougat and oreo have different partitions. Not only in name but also location.
Twrp cannot create any partition.
That being said, Oreo does not have a boot or recovery partition, so where did you flash the boot.img and recovery.img
It is obvious the stock recovery flash was not to "recovery_ramdisk" because twrp still working.
Not quite sure what parts were in you backup that you tried. And the " other zip " is a mystery.
I would think, since twrp is loading that using hurupdater might still be an option.

Thanks for your advice. Get back to system with oreo with the help of hurupdater.
1st i have no idea what is hurupdater is. But i Google for it. And now i am able use my mobile.
Thanks a lot

mrmazak said:
Should have used hwota or hurupdater to flash the fullota, not extract the images, but too late for that.
Wow, what a mess.
For starters, to explain some of what seems to have happened.
Nougat and oreo have different partitions. Not only in name but also location.
Twrp cannot create any partition.
That being said, Oreo does not have a boot or recovery partition, so where did you flash the boot.img and recovery.img
It is obvious the stock recovery flash was not to "recovery_ramdisk" because twrp still working.
Not quite sure what parts were in you backup that you tried. And the " other zip " is a mystery.
I would think, since twrp is loading that using hurupdater might still be an option.
Click to expand...
Click to collapse
Thanks for that idea. It worked. Now my mobile is working.
Using hurupdater flashed stock rom of full ota. Thanks a lot

Not able to flash stock firmware.

Hi,
My device is rooted with Pixel Experience ROM-Android Pie. I am not able to flash stock firmware on it.
Below are the errors :
Zip Treble Compatibility Error
Invalid Zip File Format
Error installing zip file
Right now I can only start up in TWRP recovery mode. Already formatted data,system,cache.
Please help.

Just use the latest dumplingfor OOS 9.0.8(from the forums) and flash it

Make sure you have the latest recovery installed. If you still can't flash it then use the unbrick tool to go full stock. That's guaranteed to work imo.

{GUIDE} - fix for being stuck at samsung boot screen due to rollback protection

Hi all I have been tinkering away and destrying my setup left right and centre to sort this process out but if you're unable to run the latest TWRP for your note from Ian and get stuck at SAMSUNG screen on boot then this process will fix that if followed correctly. This is due to the device's roll back protection.
This process will reset everything back to current date and get everything working on the new Oneui 2.1 base
Process for getting round SAMSUNG screen issue - please read through first and get the files you need before starting. I did this on my N976B but in theory it should work for other 10-range devices, notes indeed!
UNLESS YOUR RUNNING CRUEL KERNEL OR A SPIN OFF, YOU'LL NEED VOL UP AND POWER TO ACTIVATE MAGISK ON EACH BOOT
Needed:
Stock firnware
Magisk app
Twrp image
Pc and odin also patience and a brain lol
-Return to stock by flashing AP/BL/CP&CSC in odin
-Reboot and confirm oem unlocking greyed out, install magisk app and patch twrp image from Ian, also patch your ap file.
-reboot to download, meanwhile get the magisk_patched.tar and insert TWRP renamed as recovery.img in place of the stock patched recovery (keep this one for later)
-In download mode and with auto reboot off in odin, flash BL, Magisk_patched.tar(with the TWRP from Ian in), CP & HOMECSC.
-When flashing is complete exit download mode and immediately hold power and vol up and hold until on TWRP slider screen. swipe to allow modifications, format internal storage and flash multidisabler.
-Reboot TWRP and backup your current patched stock rom. FLASH THE STOCK PATCHED RECOVERY YOU SAVED EARLIER AND THEN FLASH MULTIDISABLER (THIS IS IMPORTANT AS YOU WILL THEN BE ABLE TO INSTALL TWRP VIA THE APP WITHOUT HAVING TO REFORMAT INTERNAL)
-Reboot straight to stock recovery (reboot from TWRP and hold Vol up and power until in stock recovery) and factory reset then reboot.
-You should now boot up as normal, setup your device, in particular have TWRP app and Magisk set up and running.
-Flash the Unpatched TWRP for your device in the TWRP app - reboot TWRP and check the box to kill that annoying swipe to allow modifications and then you are good to flash whatever rom or kernel you want for your device!

Flash the stock patch recovery as boot??

orbital_71 said:
Flash the stock patch recovery as boot??
Click to expand...
Click to collapse
yes then immediately flash multidisabler before you reboot to set up

i have just helped someone through this on TG so it defo works :good::good::good:

It can also confirm this is working. Just followed this guide on my Note 10+ (N975F with CTD1) and happy flashing now.

drexxie1962 said:
It can also confirm this is working. Just followed this guide on my Note 10+ and happy flashing now.
Click to expand...
Click to collapse
Excellent, thanks for testing!!!!!!!

@askmydas
you may find this useful - follow this to get your sec date reset then follow the process spelt out in the thread of the rom you want to use as you may need a different TWRP depending on what sec date the chef of your chosen rom uses.

Hey, when I get to " FLASH THE STOCK PATCHED RECOVERY YOU SAVED EARLIER" I try to do this and it tells me I don't have enough space. Any ideas?

KiwiNote+ said:
Hey, when I get to " FLASH THE STOCK PATCHED RECOVERY YOU SAVED EARLIER" I try to do this and it tells me I don't have enough space. Any ideas?
Click to expand...
Click to collapse
I worked it out, I was trying to install "recovery.img" to boot partition, "recovery.img" needs to be installed to RECOVERY partition. Silly me. Fixed it now, but have a new issue:
After I flash unpatched twrp image through the app, now my phone will only boot into TWRP. I don't even boot with recovery button presses, but it will still boot into TWRP only. Any ideas?

I know this is an old thread, but it may be that my solution could help someone who is locked on the outside of the device (softbrick)
TD,DR: If you have softbrick and you can't boot the device at all, try flashing via Odin the BL, CP, CSC from a stock rom and the AP of another completely different stock rom.
I had an IMEI 0000 issue on my Galaxy Note 8 (SM-N950F), using Hades Rom (custom), and I needed to install the stock rom. As I was on the F(15) binary, there were only two roms (SamMobile and Stockrom.net) available for my country (Brazil) with this binary:
N950FXXUFDUD6_N950FOXMFDUD6_ZTO
stockrom.net_N950FXXUFDUG5_N950FOXMFDUG4_ZTO
And a via Frija:
SM-N950F_1_20210717024140_0wmgsx8iwf_fac
And no Combination Rom for that binary
After flashing these roms several times, I was always stuck on the “Powered by Google” screen, even doing cache wipe and factory reset through stock recovery several times. So I flashed the N950FOXMFDUD6, flashed the CF-Auto-Root and was able to boot the device. Once inside I noticed that it didn't solve the problem of IMEI 0000. I tried a few more procedures, ended up restarting to install TWRP, and the OEM is closed!!! (OEM OFF, Prenormal). I start getting the message “only official binaries are allowed to be flashed(recovery)”. I flash the stock rom, but it gets stuck on “Powered by Google” again. I tryed to install CF-Auto-Root and I get the message “only official binaries…” I can't log into the device anymore. So after four days of desperation, trying every technique possible, trying to create the Combination Rom by unzipping the AP file from the stock Rom and modifying the files inside, without success, I finally try a procedure I haven't seen anywhere else: I go to the modified Odin: Odin3_v3.14.1_3B_PatcheD, I selected the BL, CP, CSC files from the N950FOXMFDUD6 rom and the AP file from the rom SM-N950F_1_20210717024140_0wmgsx8iwf_fac
And it worked! I can boot the device