Database Develop

Flashed Germany 4.3 Stuck on Samsung Screen

Hello Guys i flashed the Germany Version of 4.3 lte last night and in doing so i have Temporarily killed my Phone.
I have tried all the Recoveries processes via Kies and Odin and i am having no luck.
I think the reason why it won't flash is because the Germany 4.3 is a Newer Version than the Stock 4.1.2.
When i'm in Odin i get sboot.bin Fail when trying to Flash the Latest Stock rom. I am able to Flash the Germany 4.3 again and that flashes but then the Phone Stays on the Samsung Flash Screen.
Could someone please Help? I have been on with this for Hours now. I think what i need is a 4.3 Version of any rom in Odin .tar format so i can at least get the phone to boot up and then maybe i can get CWM Recovery on there and flash a Stock rom that way.
Thanks in Advance

You have to remove sboot.bin and tz.bin when downgrading. Be careful, downgrading will give you Knox warranty void 0x1!
Sent from my GT-I9305 using xda app-developers app

.NetRolller 3D said:
You have to remove sboot.bin and tz.bin when downgrading. Be careful, downgrading will give you Knox warranty void 0x1!
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse
I have already seen that Message in Tiny Writing. What does that mean if i get that and how do you remove sboot.bin and TZ.bin
Do i remove them from the Stock 4.1.2 or the Germany 4.3?
My head is well and truely done in. I was up till 5am trying to fix it and then when i woke i went straight back to it and i still havn't got it working.
Thanks for your help in advance.

marti4578 said:
I have already seen that Message in Tiny Writing. What does that mean if i get that and how do you remove sboot.bin and TZ.bin
Do i remove them from the Stock 4.1.2 or the Germany 4.3?
My head is well and truely done in. I was up till 5am trying to fix it and then when i woke i went straight back to it and i still havn't got it working.
Thanks for your help in advance.
Click to expand...
Click to collapse
I am in the same boat if u found a solution help me also
Currently i flashed philz recovery upon which i have flashed tgp 11.30 but have no imei baseband.

marti4578 said:
I have already seen that Message in Tiny Writing. What does that mean if i get that.
= warranty void and no way so far to remove the count .
Click to expand...
Click to collapse

AMoizK said:
I am in the same boat if u found a solution help me also
Currently i flashed philz recovery upon which i have flashed tgp 11.30 but have no imei baseband.
Click to expand...
Click to collapse
Have you got any efs backup made by yourself? Or have you ever used boeffla kernel or any other that backups efs partition?

Hbohd said:
Have you got any efs backup made by yourself? Or have you ever used boeffla kernel or any other that backups efs partition?
Click to expand...
Click to collapse
Hello I don't have any EFS Backups done by Myself and i have never used Boeffla Kernel or any other Backup. I am so at my Witts end it unreal.
I have tried to do Kies recovery and i am back at the Firmware Upgrade Encountered an Issue. Please select recovery mode in Kies and Try again.
I have no idea which way to go or what to do. I know it will be fixed but i have little Faith at the Moment.
Thanks for your help in advance.

marti4578 said:
Hello I don't have any EFS Backups done by Myself and i have never used Boeffla Kernel or any other Backup. I am so at my Witts end it unreal.
I have tried to do Kies recovery and i am back at the Firmware Upgrade Encountered an Issue. Please select recovery mode in Kies and Try again.
I have no idea which way to go or what to do. I know it will be fixed but i have little Faith at the Moment.
Thanks for your help in advance.
Click to expand...
Click to collapse
THE kies frimware intilition doesnt work as you have 4.3 bootloader and knox blocks older boot loader
dont worry when 4.3 becomes available in your area it wont have to downgrade and ultimately this method will work but still things are looking pretty bad dor the intermediatory days.
PS is ther anyway to restore baseband imei without any backup

AMoizK said:
THE kies frimware intilition doesnt work as you have 4.3 bootloader and knox blocks older boot loader
dont worry when 4.3 becomes available in your area it wont have to downgrade and ultimately this method will work but still things are looking pretty bad dor the intermediatory days.
PS is ther anyway to restore baseband imei without any backup
Click to expand...
Click to collapse
What if i download the Germany Version again and try flashing. I thought it would of worked? I am now in this situation surely the Country it comes from wouldn't make a difference? Could someone take the Germany 4.3 and make it a Working Version .tar file to flash with Odin3?

marti4578 said:
What if i download the Germany Version again and try flashing. I thought it would of worked? I am now in this situation surely the Country it comes from wouldn't make a difference? Could someone take the Germany 4.3 and make it a Working Version .tar file to flash with Odin3?
Click to expand...
Click to collapse
I ment through kies.

Hello Guys i have Fantastic News!!
I have no idea what i did different, However i have reflashed the German 4.3 on my GT-I9305 and this time to my Total Surprise it worked!!
I wish i could say what i did and it worked but i have absolutely no idea what was done differently.
Thanks all for your Help.
I will say i installed the drivers manually and just on the off chance i flashed it again with the file i downloaded last Night. I also flashed a recover trying to get it to load a recover so i could flash a zip file.

marti4578 said:
Hello Guys i have Fantastic News!!
I have no idea what i did different, However i have reflashed the German 4.3 on my GT-I9305 and this time to my Total Surprise it worked!!
I wish i could say what i did and it worked but i have absolutely no idea what was done differently.
Thanks all for your Help.
I will say i installed the drivers manually and just on the off chance i flashed it again with the file i downloaded last Night. I also flashed a recover trying to get it to load a recover so i could flash a zip file.
Click to expand...
Click to collapse
Which file can u specify pls and also which recovery also is wifi and data working

AMoizK said:
Which file can u specify pls and also which recovery also is wifi and data working
Click to expand...
Click to collapse
which file????:crying:

AMoizK said:
which file????:crying:
Click to expand...
Click to collapse
Please read the rules .

JJEgan said:
Please read the rules .
Click to expand...
Click to collapse
Can u point me to the rules

AMoizK said:
Can u point me to the rules
Click to expand...
Click to collapse
http://forum.xda-developers.com/announcement.php?f=256
5. Create a thread or post a message only once.
As a large forum, we don't need unnecessary clutter. You're free to edit your message as you like, so if you do not receive an answer, revisit your message and see if you can describe your problem better. Not everyone is online at the same time so it might take a while before you receive an answer. (Also refer to Rule 16)

Finally
I am so feeling sucessful right now although i didnt got 4.3 but i was sucessful in getting my imei and baseband and network back.:good:

Sorry for the late response but when you get stuck on the Samsung boot screen all you have to do is boot into Recovery and do a Factory Reset and Wipe Cache.
Another thing to remember is to flash the modem for your country otherwise you might accidently disable some frequencies and enable other useless ones.

xkwizt said:
Sorry for the late response but when you get stuck on the Samsung boot screen all you have to do is boot into Recovery and do a Factory Reset and Wipe Cache.
Another thing to remember is to flash the modem for your country otherwise you might accidently disable some frequencies and enable other useless ones.
Click to expand...
Click to collapse
Doesn't work I will syill be stuck at boot screen

AMoizK said:
Doesn't work I will syill be stuck at boot screen
Click to expand...
Click to collapse
Which 4.3 update did you flash? I used the DBT German one.
Did you flash the right modem too? It worked for me and i was using a i9305T. All i did was flash the latest modem (from the brand of phone i have which is Telstra) and did a wipe data and wipe cache.

[SOLVED] Bricked i9305? - No Recovery - "Get PIT for mapping" stuck - sboot.bin FAIL

[SOLVED] Bricked i9305? - No Recovery - "Get PIT for mapping" stuck - sboot.bin FAIL
Yo.
Basically been using this phone for ages, having random freezing issues for a while, so I decided to /****it and re-stock everything because it is likely that I have been an idiot with kernels/messing around with stuff once.
This freezing has persisted through stable, unstable, nightly CM 10.2/10.3/11 ROM's as well as pure stock and unrooted, so I figured it was something deeper down - the kernel, and I got a stock kernel for i9305 (attached). Everything basically went to ****, the phone got stuck bootlooping on the initial Samsung logo, doing the button-combo to get into recovery just stucks it on that logo. I can enter Download mode.
No biggie, I'll just ODIN it up (3.0.7) and flash the stock firmware, except now (this did not happen before the kernel flash) it simply fails with "sboot.bin FAIL", which people claim to be a PIT error (Kies not open btw, no KiesTrayAgent either, it's on the PC though), so I grab a i9305 stock PIT that I try and flash with the stock firmware, except now it gets stuck at "Get PIT for mapping" and never moves onwards from there.
So I'm essentially stuck with a problem that can probably be fixed by a stock firmware ODIN flash, and a problem that prevents me from fixing the PIT stuff to get the stock firmware through.
I have tried ODIN-flashing CWM recovery as well as stock recovery (also attached), but I'm still stuck on the logo regardless.
Any help here? Kinda lost ATM.
EDIT: Can't link/attach the .rar with the files. :S

Just re-install your back up

Raistlin1158 said:
Just re-install your back up
Click to expand...
Click to collapse
Retarded answer.
@OP
We need more data... first, which kernel did you flash ? If you can't attach it, link to it.
Second, what stock rom did you try to flash ?
Third, are you knoxed?

Hey guys.
Cheers for the answers, I just figured it out though actually. The sboot.bin error was caused by some bootloader-stuff-thingy I could hardly explain if I got a book on it. I got ahold of another stock ROM which flashed fine, I cleaned up and all that (NAND erase all did the job), back to CM11 as TouchWiz didn't fix my problems.
To answer your questions (others might have the problem and find this thread):
http://forum.xda-developers.com/galaxy-s3/development-i9305/recovery-odin-flashable-tar-t1971265 <- kernel
I tried to flash an "XXBMD1" stock ROM from SamMobile, it had worked previously.
I am Knoxed and have "tripeed the fuse" (trying to fix the crashing issues I went back to stock ROM, then it prompted for the 4.3 TouchWiz update which brings KNOX), so I'm without warranty (ODIN returns "KNOX Warranty Void: 1), but I guess I can consider this a learning experience as everything turned out good enough in the end.

There you go:
Based on JellyBean 4.1.2_XXBMD1 <--- You can't flash 4.1.2 because of the knox bootloader.
Had you tried a stick 4.3 you might have been sucessfull

daedric said:
Retarded answer.
Click to expand...
Click to collapse
Hello...
Don't you do irony in your country,
only a moron would play about with his phone without making a back up first, but the point seems to have gone over your head as well... Durrr

Raistlin1158 said:
Hello...
Don't you do irony in your country,
only a moron would play about with his phone without making a back up first, but the point seems to have gone over your head as well... Durrr
Click to expand...
Click to collapse
soft bricks aren't fixed by restoring nandroids.

Update odin and change usb cable and port.

Raistlin1158 said:
Hello...
Don't you do irony in your country,
only a moron would play about with his phone without making a back up first, but the point seems to have gone over your head as well... Durrr
Click to expand...
Click to collapse
Apologies for not detecting the irony on your post.
Yet, what you wrote means you didn't even bother to read the OP. What good would a nandbackup do, if he cannot even get to recovery?
I take back the retarded and replace it with lazy.
chongc1996 said:
soft bricks aren't fixed by restoring nandroids.
Click to expand...
Click to collapse
A nandroid wouldn't do any harm as soon as he got a recovery working
Raistlin1158 said:
Update odin and change usb cable and port.
Click to expand...
Click to collapse
Again, OP second post not read. His issue was probably originating in a attempt to flash a stock 4.1 (with 4.1 bootloader) over a 4.3 bootloader. Knox won't allow it.
Add stubbornness to laziness.
@ OP: please change the [Q] in the op to [SOLVED]

daedric said:
Apologies for not detecting the irony on your post.
Yet, what you wrote means you didn't even bother to read the OP. What good would a nandbackup do, if he cannot even get to recovery?
I take back the retarded and replace it with lazy.
A nandroid wouldn't do any harm as soon as he got a recovery working
Again, OP second post not read. His issue was probably originating in a attempt to flash a stock 4.1 (with 4.1 bootloader) over a 4.3 bootloader. Knox won't allow it.
Add stubbornness to laziness.
@ OP: please change the [Q] in the op to [SOLVED]
Click to expand...
Click to collapse
heh, last time i soft bricked, i could access recovery like op, but nandroid didn't help. some other problem that flashing stock rom solved

.... the phone got stuck bootlooping on the initial Samsung logo, doing the button-combo to get into recovery just stucks it on that logo. I can enter Download mode.
Click to expand...
Click to collapse
chongc1996 said:
heh, last time i soft bricked, i could access recovery like op, but nandroid didn't help. some other problem that flashing stock rom solved
Click to expand...
Click to collapse
As you can see, OP could NOT get to recovery, only download. His fault was attempting to flash 4.1 with OLD BOOTLOADER on top of a 4.3 NEW BOOTLOADER.

daedric said:
As you can see, OP could NOT get to recovery, only download. His fault was attempting to flash 4.1 with OLD BOOTLOADER on top of a 4.3 NEW BOOTLOADER.
Click to expand...
Click to collapse
ok sir, you are right, calm down, I'm out of here.

Cheers for the helpful as well as not-so-helpful responses, all back up and running now.

HELP!! SM-T810 Not Booting

Hey,
Recently I tried to root my Tab S2 and I don't know where I screwed up.
I need help resetting my device back to stock, I cannot flash the stock roms/images. :crying:
It keeps failing, there is also a 'Kernal is not SEAndroid Enforcing' text in red on the boot screen and it stays stuck.
When I flash a stock rom, it says "SW Rev Check Fail Device : 2 Binary: 1"
If you need more information. just comment.
Hopefully you can help!

Well first of all you need to stop panicking and explain what state the device is in and what you did that caused the issue.
Also screenshots say a thousand words.

So, I tried rooting my device using this, http://forum.xda-developers.com/tab-s2/development/root-cf-autoroot-tab-s2-sm-t3187202
and it put my device into a boot loop. Then I think I flashed it with the http://forum.xda-developers.com/tab-s2/development/kernel-permissive-lollipop-5-1-1-kernel-t3205831 but I can't remember.
Now since it has ran out of battery it looks like this:
blob:https%3A//drive.google.com/5dd4cf24-c9b9-4a91-b27a-e2d280356b9c
and I can only enter 'Download Mode' and it no longer boots past this screen. After I did those 2 things I tried to look for some fixes like using the Stock Roms for it, and Samsung Kies but it didn't work.

You need to fix the Google link, not working.
Which device do you have is it running 5.1.1?
Did you flash the correct permissive kernel first then cf_autoroot?

It's running 5.0.2 and it's the SM-T810.
I think that may have been the problem flashing the 5.1.1 kernel by mistake. Is there a way to fix it. I don't think I can get it repaired as the warranty is probably voided.

SaiyanShivvy said:
It's running 5.0.2 and it's the SM-T810.
I think that may have been the problem flashing the 5.1.1 kernel by mistake. Is there a way to fix it. I don't think I can get it repaired as the warranty is probably voided.
Click to expand...
Click to collapse
Sorry can't post the link as I'm A new member so it won't let me until I make 10 posts

SaiyanShivvy said:
It's running 5.0.2 and it's the SM-T810.
I think that may have been the problem flashing the 5.1.1 kernel by mistake. Is there a way to fix it. I don't think I can get it repaired as the warranty is probably voided.
Click to expand...
Click to collapse
Here is this link, it might help did not read thru out the whole way through, just try to relax there is a way to fix it, if in the end if you cannot fix it just warranty it and play dumb it's worked for me more than once. http://forum.xda-developers.com/showthread.php?p=64137334

dislplin01 said:
Here is this link, it might help did not read thru out the whole way through, just try to relax there is a way to fix it, if in the end if you cannot fix it just warranty it and play dumb it's worked for me more than once. http://forum.xda-developers.com/showthread.php?p=64137334
Click to expand...
Click to collapse
Thanks for the help, I'll let you know of it works ! ???

At the end of the day this is completely fixable. All you need do is simply download the stock firmware for your device and region from SamMobile and flash with odin.
Don't wipe anything just flash.

ashyx said:
At the end of the day this is completely fixable. All you need do is simply download the stock firmware for your device and region from SamMobile and flash with odin.
Don't wipe anything just flash.
Click to expand...
Click to collapse
Yeah, Thanks, I will see if I can, if I can't then I will send it for repairs.

SaiyanShivvy said:
Yeah, Thanks, I will see if I can, if I can't then I will send it for repairs.
Click to expand...
Click to collapse
I promise you, you don't need to send it for repair.
You have several options to fix this.
The reason you get that error in Odin is simply because you are flashing the wrong firmware for your device.
Tell me the region you bought this device and I'll point you to the correct firmware.

ashyx said:
I promise you, you don't need to send it for repair.
You have several options to fix this.
The reason you get that error in Odin is simply because you are flashing the wrong firmware for your device.
Tell me the region you bought this device and I'll point you to the correct firmware.
Click to expand...
Click to collapse
I live in New Zealand, so the region would be Oceania I guess?

SaiyanShivvy said:
I live in New Zealand, so the region would be Oceania I guess?
Click to expand...
Click to collapse
Actually I think your region comes under Australia region XSA.
http://www.sammobile.com/firmwares/database/SM-T810/XSA/

dm verity boot error cb9 fixed..

I found simple fix.
just flash CB 7 firmware and modem throuth twrp.
https://www.androidfilehost.com/?fid=457095661767116249

First flash this file and then Rom. That's right?? Or its other way around

karan khara said:
First flash this file and then Rom. That's right?? Or its other way around
Click to expand...
Click to collapse
If u have dm verity error on boot. Just flash it..

Wouldn't this procedure downgrade some performance on the device?

Giocarro said:
Wouldn't this procedure downgrade some performance on the device?
Click to expand...
Click to collapse
No..

Can I flash CB 7 firmware and modem through USB-otg using twrp....I'm on CB9...my phone is encrypted

Nitesh13 said:
Can I flash CB 7 firmware and modem through USB-otg using twrp....I'm on CB9...my phone is encrypted
Click to expand...
Click to collapse
Yes u can..

Firmware is MM-based, can you flash this after you installed beta 9, because this is N-based?

cool.boy said:
I found simple fix.
just flash CB 7 firmware and modem throuth twrp.
https://www.androidfilehost.com/?fid=457095661767116249
Click to expand...
Click to collapse
Nice but what do you fix. If it is only a message that is displayed at boot but has no negative effects what is the point of fixing.
In my opinion using firmware and modem from mm for n can't be a good match or let's say better.

I have no DM verity error and I have cb9 firmware and rooted
Sent from my OnePlus 3 using XDA Labs

Why would you want to flash old firmware and modem, not made for this ROM, just to get rid of a pointless message?
Especially when there are other methods to fix this so called issue ...
Sent from my OnePlus 3 using Tapatalk

puschkin said:
Firmware is MM-based, can you flash this after you installed beta 9, because this is N-based?
Click to expand...
Click to collapse
Yes..

snippem said:
Nice but what do you fix. If it is only a message that is displayed at boot but has no negative effects what is the point of fixing.
In my opinion using firmware and modem from mm for n can't be a good match or let's say better.
Click to expand...
Click to collapse
Its a bug related cb9 firmware. U can use cb7 firmaware to fix it..

This makes sense. I was on open beta 8 for a few days
When I stumble across open beta 8 firmware + modem, I flashed it. Phone was working without issues prior to that, so I dont know what possessed me to do that because after that I began receiving dmverity message right after bootloader warning. I immediately knew it had to be the updated firmware/modem. Unfortunately I was unable to access twrp anymore. I ended up bricking my phone trying to revert this issue lol all is good now. I suggest you do not update to any firmware/moden newer than cb 7.

cool.boy said:
Its a bug related cb9 firmware. U can use cb7 firmaware to fix it..
Click to expand...
Click to collapse
it's not a bug…just another warning for modified partitions.
No need to be "fixed" and don't think using mm firmware to replace n's is a good choice

cool.boy said:
Its a bug related cb9 firmware. U can use cb7 firmaware to fix it..
Click to expand...
Click to collapse
cesar.mk4 said:
This makes sense. I was on open beta 8 for a few days
When I stumble across open beta 8 firmware + modem, I flashed it. Phone was working without issues prior to that, so I dont know what possessed me to do that because after that I began receiving dmverity message right after bootloader warning. I immediately knew it had to be the updated firmware/modem. Unfortunately I was unable to access twrp anymore. I ended up bricking my phone trying to revert this issue lol all is good now. I suggest you do not update to any firmware/moden newer than cb 7.
Click to expand...
Click to collapse
dlhxr said:
it's not a bug…just another warning for modified partitions.
No need to be "fixed" and don't think using mm firmware to replace n's is a good choice
Click to expand...
Click to collapse
Exactly I believe there is no point in flashing old firmware only if you can't wait for 5 sec.
If this was a bug oneplus would have pushed a patch out by now.

snippem said:
Exactly I believe there is no point in flashing old firmware only if you can't wait for 5 sec.
If this was a bug oneplus would have pushed a patch out by now.
Click to expand...
Click to collapse
I absolutely agree. 5 seconds more isnt a big deal. But why was I unable to access twrp?

cesar.mk4 said:
I absolutely agree. 5 seconds more isnt a big deal. But why was I unable to access twrp?
Click to expand...
Click to collapse
I never had that till now only after flash does not reboot.
In my opinion it is more a twrp incompatibility that will be resolved when N sources are out by oneplus

snippem said:
Exactly I believe there is no point in flashing old firmware only if you can't wait for 5 sec.
If this was a bug oneplus would have pushed a patch out by now.
Click to expand...
Click to collapse
Don't even need to wait, just press the power button to skip it (same applies to first bootloader unlocked message).
Sent from my OnePlus 3 using Tapatalk

it's easily avoidable (but the phone will be decrypted)
after flashing ob9 successfully and booting to system, reboot to TWRP (.28) and wipe convert data to f2fs then wipe it, then wipe internal storage (back up your data to your pc 1st)...and that's it, if you want root, reboot back to TWRP and flash root, then roboot to system, dmverity will be gone, and the phone decrypted,
(this will work if you started with a clean ob9 install like sideloading, and you ended with a full stock ob9)

Bootloop after flashing any kernel

Good time of the day, I need help with resolving the issue mentioned in title. No matter which kernels I flash, bootloop consistently occurs. I flashed them using TWRP and cleared all caches as required, but to no avail. Neither on a clean system nor on a rooted one do they work

Did you recently upgrade to May1 Security Patched Firmware upgrade?

OldNoobOne said:
Did you recently upgrade to May1 Security Patched Firmware upgrade?
Click to expand...
Click to collapse
Yes, I did

VerySorryFor said:
Yes, I did
Click to expand...
Click to collapse
ok I thought so, atleast flashing disable-dmverity makes the GSI boot to rom logo but nothing beyond that, it just refuses to boot anything but the latest Stock ROM, I think its time to throw away this device (SM-M215G) into the garbage bin. Man Shamshung ruined my device, now stuck on 1UI5.1!
#Edit: You can try to contact a dev called Fredin, he might be able to help if there is any hope at all, you can find him on TGram & M21 Threads btw, all the best

VerySorryFor said:
Yes, I did
Click to expand...
Click to collapse
Have you tried flashing Kernel through Terminal or ADB sideload? Try finding out if A13 Stock ROM is R/O-System?