Develop Bugs

[25.01.2011] WARNING! Do not flash JM*,KA*... README! [Patch released, L/N supported]

DO NOT USE THIS ON THE GINGERBREAD RELEASES ! THE SAMSUNG GINGERBREAD RELEASES DO HAVE SIGNED BOOTLOADERS, BUT THEY ARE NOT LOCKED. In other words, you can still flash custom kernels and such, and the bootloader patch will only break things, not fix them.
To read the history of this problem, see the 2nd post of this thread (scroll down).
A number of new firmwares for the Samsung Galaxy Tab come with "signed / protected" bootloaders. These new bootloaders prevent you from flashing custom or otherwise unsigned kernels on the device. Trying to do so anyway will result in errors and usually requires you to reflash your ROM completely.
I hope everybody here has learned the lesson not to just flash anything that SamFirmware releases
The patch
After a great many hours of researching, testing and coding, myself (Chainfire) and Rotohammer have come up with a patch that works on most devices (currently all known GSM Tab variants), and flashes back unprotected JJ4 (T-Mobile ?) bootloaders, or the original P1000N bootloaders for the Latin models. The app only patches when it finds protected bootloaders, and you have to press a button for that, so the app can also be used to look at your current status.
The patch has been tested repeatedly and with success on (0 bricks so far):
- GT-P1000 Euro/International/Unbranded Galaxy Tab
- SGH-I987 AT&T Galaxy Tab
- SGH-I987 Rogers Galaxy Tab
- SGH-T849 T-Mobile Galaxy Tab
- GT-P1000L Latin Galaxy Tab (use LATIN version!)
- GT-P1000N Latin Galaxy Tab (use LATIN version!)
Additional thanks to: koush, neldar, richardtrip, AColwill, farahbolsey, deezid, wgery, tmaurice, rmanaudio, crisvillani, alterbridge86, ivannw, themartinohana, luisfer691 (in no particular order!)
Please note that even though there have not been any bricks so far, replacing bootloaders is a very dangerous operation that may BRICK your device, and you should think twice before using the patch. Using the patch is completely AT YOUR OWN RISK!
Instructions
Download the attached APK, install it on your device, and run it. It will show you a status screen, and if your device is compatible and you have protected bootloaders, the bottom entry "Patch bootloaders" will become available. Tapping it will start the patch procedure.
Note that the patch requires root !
Mini-FAQ
--- After the fix, my "zImage" still shows signed ! Is this a problem ?
No, this is perfectly fine! What matters is that "PBL", "SBL" and "SBL_Backup" are not signed. If "zImage" is signed, it means this ROM can be flashed onto a device that has signed bootloaders. UNsigned "zImage"s can NOT be flashed on signed bootloaders. This is the origin of the problem, because custom kernels are always UNsigned "zImage"s !
--- Can I now flash any ROM and just use this application to fix the bootloaders ?
Technically yes. But it would be stupid to do so. Flashing bootloaders (what this app does) is VERY dangerous, it is the only way to really brick a Tab. If you want to flash a new ROM, make sure it DOES NOT contain bootloaders. Remove them yourself, or wait for somebody else (like Rotohammer) to remove the bootloaders and post the "safe" ROM. Even though this patch is available, if at all possible, you should always try to avoid having to use it.
CDMA tabs
There is currently no support for CDMA Galaxy Tabs, nor do we know if support is needed at this time.
LINKING
You are expressly forbidden to repost the APK elsewhere. If you post about this, post a link to this thread, not to the download (or a repost of the download).
Download
Don't forget to donate and/or press the thanks button!
For non-XDA members who cannot access the attachment, here are multiupload links:
Euro / International / Unbranded / AT&T / Rogers / T-Mo: http://www.multiupload.com/EMOCU1S0V2
Latin (P1000L and P1000N): http://www.multiupload.com/3TJ3YWMWJR
MAKE SURE TO SELECT THE RIGHT DOWNLOAD!

WARNING! Do not flash JM6/9/A/C/D/E/F... Before reading this !
THIS POST, #2 OF THIS THREAD, IS HISTORICAL AND LEFT HERE "FOR THE RECORD". SEE THE FIRST POST FOR WHAT IS CURRENT!
BREAKING NEWS / JAN 15: A fix has been found ! See this post. Also see the bounty thread: http://forum.xda-developers.com/showthread.php?t=906464.
This really applies to other ROMs as well, but the "new" JM6/9/A/C/D/E/F ROMs specifically.
Some of these ROMs include new bootloaders. These bootloaders check checksums/signatures in various parts of the firmwares. The "normal" Samsung ROMs, nor custom ROMs and kernels, have these checksums.
The result is that once flashed, you cannot revert to older/official/custom Samsung ROMs, and you are pretty much stuck using one of these four ROMs, as they are the only ones containing the right checksums.
At least TRIPLE CHECK if you want to flash one of these ROMs, that what you are flashing DOES NOT include the new bootloaders ( boot.bin and sbl.bin ). I know from the CF-Root thread that a fair number of you are already too late, but I thought to warn new users anyways. Some modders (like rotohammer) already usually remove these parts, but still triple check everything to make sure.
There is no known fix. I know, I've tried all of them some people suggested in other threads. None of them really works. Sure, with some effort, you can get a different firmware to somewhat run, but you'll still be using the "checksum" bootloaders and the kernel will not be modified. You will still be running the kernel from the "checksum" firmware you loaded earlier. You will not be able to do full flashes, nor will KIES updates work.
Hopefully somebody will find a real solution for this issue for those already affected. If so, please post it in this thread.
Are you affected ?
NEW DEC 28: See SGTBootloaderCheck script below!
It is hard to say for sure without actually trying to flash a non-JM6/A/C/D kernel without the correct checksum. Here's a screenshot of the error you'll get:
If you still have the original files for the ROM you flashed, but do not want to try flashing a non-Samsung-stock kernel, there are some indicators:
- Rename all .tar.md5 files to .tar
- Extract all the .tar files with WinRAR
- Look at the resulting files:
--- Includes "boot.bin" (primary bootloader)
--- Includes "sbl.bin" (secondary bootloader)
If one or both are present, this indicates new bootloaders are being flashed. That does not make it certain if they are "protected" or not, though. But if a large zImage is also present (see the next item), it is very likely they are.
- Look at the resulting files:
--- "zImage" (kernel)
If zImage is about 7800 kb (as opposed to 4000 - 5500 kb that is normal), it is very likely this kernel includes a checksum. If you want to be 100% sure, open zImage in a hex editor, and go all the way to the end. There will be a few mb of 0's, followed by 128 bytes checksum - the very last 128 bytes in the file.
Such a zImage can be flashed both on "original" and the new "protected" bootloaders. The "protected" bootloaders can only flash these zImage, not the smaller variants.
If you have boot.bin, sbl.bin and a 7800 kb zImage, it is 99% likely flashing this ROM will give you a "protected" bootloader.
Some tech
Once these ROMs are flashed, it is required updates to "boot", "sbl", "zImage" have a 128-byte checksum/signature. In boot.bin and sbl.bin these are near the end, in zImage (7800 kb files) they are the very last 128 bytes. Only firmwares with a zImage that have this signature will be flashable (which at the time of this writing are only JM6/A/C/D).
I have no idea how this signature is generated as of yet, so "faking it" is also not an option. If somebody figures that out, please post it in this thread. Then we could just insert the signatures in the older bootloaders and flash them back (still a dangerous effort by itself).
I think, and possible others will correct me on this, the verification goes as follows, on a running device:
- PBL ( boot.bin ) checks SBL ( sbl.bin ) signature
- SBL checks kernel ( zImage ) signature
While flashing, I think it's the SBL that verifies the PBL/SBL/kernel flash, and refuses to write if the signature isn't correct.
Possible solutions
Flashing back "unprotected" bootloaders from older ROMs through either Odin or Heimdall does not work. These older bootloaders do not have the required signatures/checksums and thus the flash will fail.
A possible solution would be rooting the device, using Koush' bmlunlock, and dd'ing back bml1 and bml4 from backups, complete bypassing the flash checks. This is a very very dangerous to be trying out though, and unless you really know what you are doing, I wouldn't attempt it. Maybe someone has Samsung repair center contacts or a JTAG unit close by ?
Personal note
I have tried to flash back older bootloaders and kernels several times and in several ways (from for example JJ4) but this fails. Odin said it succeeded the very last time I tried, however it really didn't, as my device is now a full (user-wise) brick. It doesn't even turn on to show me the "phone --- | --- pc" error screen. So I guess I need to make a trip to the nearest Samsung repair center (200 miles away). Too bad my car also broke down today Guess it'll be some time (and money) before I have a working Tab again. Note that the brick was a problem with Odin, probably, not directly caused by the protected bootloaders themselves.
Update: Tab is back and working Replaced mobo, so I no longer have the signed bootloaders myself.
NEW DEC. 28: SGTBootloaderCheck
Attached is also SGTBootloaderCheck. This is a script run on your Windows PC through ADB to check your bootloaders. It requires root, SuperUser, and a working ADB connection.
Just unzip the archive to a new folder, and double-click "check.bat". That should dump your bootloaders and kernel, copy them to your computer, check the content for signatures, and let you know the result.
I can't guarantee it works, but it should
Attached
An archive with some relevant files for those who want to do some research. DON'T FLASH THESE FILES !!!
( 467, 909 )

I'm sorry about your Tab man.

After flashing JM6, I have "zImage" and "Sbl.bin" but no "boot.bin" in my internal SD. Am I affected?
Also, is it safe to delete these files from my internal SD? I'm guessing they were put there temporarily and are now stored somewhere else already?

hey chainfire,
i'm sorry about the brick :/
my english seems to be very bad... could u explain me why ur tab is bricked now?
i think i understood why its not possible to flash to another firmware but why ur tab is bricked now? yesterday i flashed to jm6 from an old arabic fw (i think it was JJ1) with pit p1 and code, modem and csc file with re-part. on. so is anything there i have to look out now?

codewisp said:
After flashing JM6, I have "zImage" and "Sbl.bin" but no "boot.bin" in my internal SD. Am I affected?
Also, is it safe to delete these files from my internal SD? I'm guessing they were put there temporarily and are now stored somewhere else already?
Click to expand...
Click to collapse
You could be affected, I can't say for sure. The only way to be sure is trying to flash a custom kernel and see if Odin gives an error. See the CF-Root thread for screenshots of the error that is produced if you are affected. If there's no error and it boots, you have probably not been affected. Note that you can flash back the original JM6 kernel with both the "protected" as well as the "original" bootloaders.
I'll update the first post to add a bit more information.
Also yes, those files on your internal SD are temporary, you can delete them.
DubZyy said:
hey chainfire,
i'm sorry about the brick :/
my english seems to be very bad... could u explain me why ur tab is bricked now?
i think i understood why its not possible to flash to another firmware but why ur tab is bricked now? yesterday i flashed to jm6 from an old arabic fw (i think it was JJ1) with pit p1 and code, modem and csc file with re-part. on. so is anything there i have to look out now?
Click to expand...
Click to collapse
The brick is a result of a bad bootloader flash... it's not something any of you are likely to encounter (unless you are trying to fix this issue).
If you successfully flashed to JJ1 - Odin did not produce any errors - you are probably safe!

Thanks for the information, but a little bit late for me --> bricked
My luck: Next samsung repair center is 5 kilometers away.
But I don't know what i should tell him.
The truth?

@chainfire
Have your tried hexediting the version of the SBL to a "fake" newer version? or does the check only care about the checksum ? on older phone we used to be able to do this....
I'm unpacking my dev. tab as we speak so I hope to have some time to play between x-mas dinners

chinchen said:
Thanks for the information, but a little bit late for me --> bricked
My luck: Next samsung repair center is 5 kilometers away.
But I don't know what i should tell him.
The truth?
Click to expand...
Click to collapse
Damned lucky the repair center is close!
You wouldn't happen to be living near me and I just never heard of this service center, would ya ?
How exactly is it a brick ? It's only a brick if it doesn't turn on at all anymore (like mine). If you can get anything on screen, you can bring it back to life (although maybe with protected bootloaders).
Jesterz said:
@chainfire
Have your tried hexediting the version of the SBL to a "fake" newer version? or does the check only care about the checksum ? on older phone we used to be able to do this....
I'm unpacking my dev. tab as we speak so I hope to have some time to play between x-mas dinners
Click to expand...
Click to collapse
As far as I have been able to deduce (I have not done a full decompile yet, and not sure if I'm going to) it's only the checksum that matters. But I could be wrong there.
I'll upload some files for you in a minute, so you can look at them yourself as well.

chinchen said:
Thanks for the information, but a little bit late for me --> bricked
My luck: Next samsung repair center is 5 kilometers away.
But I don't know what i should tell him.
The truth?
Click to expand...
Click to collapse
Anything besides truth - tell them that you turn off Tab at evevning, and at the morning he doesnt start... they believe
Chainfire - my condolence... i also cannot flash CF-Root on JMC so i think i have new bootloader - im waiting for next steps when yours Galaxy Tab alive
sorry for my english

@Jesterz:
Some files you might want to look at attached to first post.

Is there any way to check what version of bootloader i have installed? I cannot install CF-Root on JMC -its enough to say i upgrade bootloader in my Tab?

faust86 said:
Is tehere any way to check what version of bootloader i have installed? I cannot install CF-Root on JMC -its enough to say i upgrade bootloader in my Tab?
Click to expand...
Click to collapse
If you get the same error as in the screenshot linked to in the first post, yes, you have the protected bootloaders.

good to know i am not effected. and for people who has effected roms i think as we know the reason there will be a quick solution for this.

Chainfire said:
If you get the same error as in the screenshot linked to in the first post, yes, you have the protected bootloaders.
Click to expand...
Click to collapse
So i install this *** bootloader... maybe i brick my Tab and take it to service point... i have 100 meters :>

Me too
Chainfire said:
If you get the same error as in the screenshot linked to in the first post, yes, you have the protected bootloaders.
Click to expand...
Click to collapse
I have the error and I cant change ROM (a part from switching between JM6, JMA and JMC)... Hope someone soon find a fix!
My tab some ago was in a similar state (complete black and didnt show in ODIN).
My luck was that it was stuck in some kind of download mode. Leaving it connected to the computer has made a miracle: after more than 15 minutes it has appeared as connected in ODIN and was possible to flash back a ROM).

patomas said:
I have the error and I cant change ROM (a part from switching between JM6, JMA and JMC)... Hope someone soon find a fix!
My tab some ago was in a similar state (complete black and didnt show in ODIN).
My luck was that it was stuck in some kind of download mode. Leaving it connected to the computer has made a miracle: after more than 15 minutes it has appeared as connected in ODIN and was possible to flash back a ROM).
Click to expand...
Click to collapse
I'll just try that. I have no hope of it working, but hey, it's not like I'm using the Tab for anything else right now

patomas said:
My tab some ago was in a similar state (complete black and didnt show in ODIN).
My luck was that it was stuck in some kind of download mode. Leaving it connected to the computer has made a miracle: after more than 15 minutes it has appeared as connected in ODIN and was possible to flash back a ROM).
Click to expand...
Click to collapse
While the Tab was at a black screen, did you ever press the power button or did you just leave it alone for Odin to eventually find it?

rotohammer said:
While the Tab was at a black screen, did you ever press the power button or did you just leave it alone for Odin to eventually find it?
Click to expand...
Click to collapse
While you're here... any chance of both STL and BML dumps of your (hopefully proper) PBL and SBL ?

Chainfire said:
While you're here... any chance of both STL and BML dumps of your (hopefully proper) PBL and SBL ?
Click to expand...
Click to collapse
Of course. I have dumps of everything. I'm just about to run some diffs to make sure my current bootloaders are ok, I can't remember what Ive flashed

Telstra Stock Firmware

Before flashing a custom rom on my new tab I decided to make a Roto Backup for myself and to share for anyone else with a Telstra tab who might need to go back to stock.
Please note this is not an official rom, for more information please see Roto's thread
http://forum.xda-developers.com/showthread.php?t=850359
I followed his instructions exactly, including generating the tar for flashing with Odin which is what I'm posting here.
I have a Desire but doing this sort of thing with Samsung devices is new to me, however I have successfully flashed this on my Tab with Odin, once saving me after trying to flash a bad download of the MCR kernel.
I factory reset beforehand so it's clean except for superuser & root Z4Root worked straight up on this so I imagine it should unroot just as easy.
If you have converted your filesystem then you will need to re-partition with Odin, I don't think this rom will work with ext4. I originally attached my backup pit but it doesn't seem to work, I've attached the pit from Roto-JME-Full-v4.
http://www.multiupload.com/KQF09AELMR
Tar MD5SUM - A75722008429EF469568E96F6F81F40A
Telstra modem.bin
http://www.multiupload.com/T04FXM8R5B
Bin MD5SUM - D1857CF262EFB929F73533C79D6B71AC
All thanks to rotohammer!

Thank you very much for your sharing!!!!
I'm using Galaxy Tab P-1000T Telstra, too.

Thank you - tucked away safely

thank you kind sir!

Many thanks for this - have used it several times now as I was too lazy to make an initial backup. Works just fine, and prerooted too!
Sent from my GT-P1000T using XDA Premium App

legand
I am on telstra also.

first of all, thank you.
my question here is how do i restore the stock firmware? i have a desire and restoring it to stock is just running the RUU provided but with GT, i'm clueless.

I was able to restore this with Odin happily. Just use it with the 'PDA' option.

BeauGiles said:
I was able to restore this with Odin happily. Just use it with the 'PDA' option.
Click to expand...
Click to collapse
Hi BeauGiles, will you be able to provide some simple instructions? what version of odin you are using? i found 2 version on the xda (odin3_1.70 and 1.31)
thank you.

I suggest having a look at the installation guide for the Overcome ROM, specifically the "Re-stocking" section as it has photos and things for Odin which makes it pretty clear. It's attached to the first post here
http://forum.xda-developers.com/showthread.php?t=932082
The process is basically the same, use the pit file and re-partition and select the telstra rom under PDA, you won't need to add the modem separately as it's already inside the telstra rom tar.
If any apps or settings carry over just do a factory reset.

Sarsippius said:
The process is basically the same, use the pit file and re-partition and select the telstra rom under PDA, you won't need to add the modem separately as it's already inside the telstra rom tar.
Click to expand...
Click to collapse
thank you.

Hi Sarsippius,
Thank you for the TELSTRA ROM.
I have a problem here, everytime i press the power button, my tab reboots, and also when the tab autolock. It also doesn't load the recovery mode when i press the power + up button(and then release the power button). Does anyone here having the same problem? Please share the solution.
Thank you again!

You hold the volume up button until the samsung logo appears, I personally hold it in until the recovery mode appears. Up to you...

Sarsippius said:
it's clean except for superuser & root
Click to expand...
Click to collapse
So how did you root it and how do I unroot it?
Only asking cause I suspect that not removing z4root is what baffed my official gingerbread update.

z4root is an app you can use to root certain Samsung devices, it worked on early Tab firmwares like those on the Telstra tab, it doesn't work on more recent firmwares but I haven't really looked at it lately.
Anyway, you open the app, hit the root button and it roots the tablet, it will also unroot although I never tested this. Give that a go otherwise do a search as there are instructions on this forum to manually unroot.

All good and sorry for the dumb question. was tired and late when I posted .
I assumed having z4root still kicking around when I let the official GB upgrade install was what was stopping me root using Doomlords method
Turns out samsungs use/abuse of the system directory was the issue and using the instructions later in the post Post 208sorted things out.
FYI: If anyone uses the above the code sample goes into the bat file after...
"@echo --- remounting /system
@files\adb shell "/data/local/tmp/busybox mount -o remount,rw /system"

do you think this would work on an australian optus tablet providing I change the modem to suit..?

I don't know of any reason why it wouldn't work but I'm not sure why you would want to do that.

ahh because i want the "stock" ROM so I can sell it.
I forgot to take a backup before I put Overcome then CM7 on it

senectus said:
do you think this would work on an australian optus tablet providing I change the modem to suit..?
Click to expand...
Click to collapse
Remembering that you'll have the stock Telstra bloat.. Er, apps on there such as Foxtel, BigPond, etc.
---
I am here: http://maps.google.com/maps?ll=-33.897667,151.175675

i9192 hard bricked

My i9192 s4 mini got hard bricked while charging I don't know how or why it happened..
I found this somewhere in the forum.. can anyone make me a dump file for i9192 because I don't know anyone who has the same phone as me so I'm asking for help. I tried to bring it to a programmer but they said they have to j-tag it for 3days up to a week. but I don't want to leave my phone on other people's hand so I'd rather fix this myself.
help would be really really appreciated. TIA
initial situation:
- we have a brick with killed bootloader after unsuccessful flashing, not turning on, no reaction on buttons, no any mode available (recovery, download).
What is needed:
- any Linux, like Ubuntu, but more convinient is PartedMagic of any version;
- MicroSD card;
- working phone of the same model or dump of its first 139008 blocks (about 70MB).
How to make a dump:
- on rooted device download from Google Play app "TerminalEmulator" and run it;
- Enter su, appears "[email protected]:/ #", enter "dd if=dev/block/mmcblk0 of=sdcard/mmcblk0uptop7.img count=139008";
- after completion copy file "mmcblk0uptop7.img" from the phone to PC, for example to drive C:/.
How to revive the phone:
- insert MicroSD into PC and launch "PartedMagic";
- copy dump to MicroSD, for this open Terminal, we see "[email protected]:~#", enter "dd if=/media/WIN7/mmcblck0uptop7.img of=/dev/mmcblk0", where "/media/WIN7/" - it's your drive C:/, where stored a dump, and "/dev/mmcblk0mmcblk0" - your MicroSD in PartedMagic;
- wait for completion, remove MicroSD;
- put MicroSD to non-working phone, connect the phone to PC using USB;
- if all steps are done correctly, phone will boot by pressing the keys, using bootloader from external MicroSD;
- now it is possible to re-flash internal eMMC using Odin, to make a possibility to remove external card;
- that's all, phone completely revived.
Supported devices:
- tested on i9190, will work on i9192/i9195, should work on smartphones of other brands with new Qualcomm chips.
Technical details:
- details are too big to write. If you are interested - read about MSM8930 boot architecture and etc.
Some conclusions:
- Qualcomm has made a good modern chip, with a lot of feasibility, but not placing many information to open sources;
- Samsung - trying to complicate life of users by integrating of its own digital signature, what is leading to immediate bricking of devices when trying to modify bootloader. Be careful.
Click to expand...
Click to collapse
Update:
Please try to send me an unbrick.img file from a stock i9192 that came from Saudi.. but if not from Saudi at least a stock ones..
If someone could send me a full or even half image file from a i9192 stock device
thank you.

I just need the "make a dump" part.

Bcoz of knox m not rooting my phone but I really want to help you
Is there any othet way to make dump file without a rooted device?

NafeesTyagi said:
Bcoz of knox m not rooting my phone but I really want to help you
Is there any othet way to make dump file without a rooted device?
Click to expand...
Click to collapse
I don't know if there's another way tho. but thanks anyway. even my phone is not rooted. I'll bring it to a service center today but I doubt they can get it fixed because the warranty of my phone is in another country and I'm in the Philippines right now. probably I will have to pay for it if they try to fix it but it's gonna be expensive.. I just want to save some bucks and try to fix it myself but unfortunately I don't have another phone like this one to do that, neither my friends.
EDIT:
Unfortunately they keep refusing to J-TAG my unit.. they said that they don't have software to j-tag i9192.

I'll upload mine when I get to the office
Sent from my GT-I9192 using Tapatalk

fburgos said:
I'll upload mine when I get to the office
Sent from my GT-I9192 using Tapatalk
Click to expand...
Click to collapse
Thanks!! I hope I can fix my phone.. it's been a month since I last used it.

here you go, its from a the latest firmware
https://www.dropbox.com/s/89yodahtvig6lhc/debrick.img

fburgos said:
here you go, its from a the latest firmware
https www . dropbox . com s 89yodahtvig6lhc debrick.img
Click to expand...
Click to collapse
Thank you bro! is that from i9192?.. gonna update if I fixed my phone so ppl who has same problem will be able to use this thread.
EDIT: IT has some improvements its vibrating now when I plug it in my PC but the problem is ODIN won't detect my phone. Hmm

Hi I have some improvements but I could not flash my phone.. it keeps failing on ODIN, sorry im just a newbie on this kind of stuff and still learning.. I used the stockfirmware which is the md5 file that is 1.4gb for my phone is that the right one for the bootloader?
its like this
BOOT RECOVERY MODE
CHECK BOOT PARTITIONS
COPY FROM T-FLASH
BOOT RECOVERY
WRITE 139008 SECTORS
FLASH WRITE FAILURE
ddi : mmc_read failed
ODIN MODE
PRODUCT NAME: GT-I9192
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enabled

now that you have a debrick image follow this guide , hope it helps.
http://forum.xda-developers.com/showthread.php?t=2600869
btw you don't need to follow step 2.2 of that guide

dovakinn said:
now that you have a debrick image follow this guide , hope it helps.
http://forum.xda-developers.com/showthread.php?t=2600869
btw you don't need to follow step 2.2 of that guide
Click to expand...
Click to collapse
same thing happened still on that root recovery mode.. the problem is I'm stuck at flashing my phone.. probably the problem is the version of the firmware @jburgos gave me.. I need to know what version is his firmware and where it came from so I can download the stock firmware for that version.

can you get into download mode ?? a quick glance a jburgos proflie shows he is most likely using a Latin American firmware , though i really doubt that it will make diffrence, if you can get into download mode you can try flashing it again with your stock firmware.
by mistake i had deleted my image file and right now i am on a really bad connection uploading another image will tale me 3 days

dovakinn said:
can you get into download mode ?? a quick glance a jburgos proflie shows he is most likely using a Latin American firmware , though i really doubt that it will make diffrence, if you can get into download mode you can try flashing it again with your stock firmware.
by mistake i had deleted my image file and right now i am on a really bad connection uploading another image will tale me 3 days
Click to expand...
Click to collapse
I can't get into download mode.. btw mine is the Saudi Arabia version..
Its not download mode and I took a picture of it so you guys can see:
BOOT RECOVERY MODE
CHECK BOOT PARTITIONS
COPY FROM T-FLASH
BOOT RECOVERY
WRITE 139008 SECTORS
FLASH WRITE FAILURE
ddi : mmc_read failed
ODIN MODE
PRODUCT NAME: GT-I9192
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enabled
Man I'm stuck.. I thought I had it but its not flashing through root recovery mode

I wonder if I need the exact same phone as dump, or I need a longer address on dump, anymore opinion guys I'm kinda getting annoyed on my phone. idk what is root recovery mode either..
I'm currently stuck on Boot Recovery Mode that has no android logo.. can't go to download mode.
If someone could send me a full or even half image file from a i9192 stock device it would be very helpful.

this is the rom i used for the image, http://forum.xda-developers.com/showthread.php?t=2620621
i have another image from a past firmware but its at home and i dont the firmware version

fburgos said:
this is the rom i used for the image, http://forum.xda-developers.com/showthread.php?t=2620621
i have another image from a past firmware but its at home and i dont the firmware version
Click to expand...
Click to collapse
which model did u use tho?
I'm stuck at boot recovery mode I can't go to download mode.. I hope someone who has stock rom will share their .img file.. but still I'm going to download that custom rom and try to flash it.

jhetz09 said:
which model did u use tho?
I'm stuck at boot recovery mode I can't go to download mode.. I hope someone who has stock rom will share their .img file.. but still I'm going to download that custom rom and try to flash it.
Click to expand...
Click to collapse
mi device its a i9192 from panama
sorry to hear didnt work, i use this guide to get the debrick.img,
[HARD BRICK ?] - I919x - Make your debrick.img and have it on extSdCard by security http://forum.xda-developers.com/showthread.php?t=2625628
i have another .img but not with me, broke my screen, next week ill upload when i get my phone back, i think the other firmware was from ubmh1 odin firmware but im not shure wich firmware but im shure it was a stock samsung that came without knox
do you remember wich firmware was in your device, was a knox one?

fburgos said:
mi device its a i9192 from panama
sorry to hear didnt work, i use this guide to get the debrick.img,
[HARD BRICK ?] - I919x - Make your debrick.img and have it on extSdCard by security http://forum.xda-developers.com/showthread.php?t=2625628
i have another .img but not with me, broke my screen, next week ill upload when i get my phone back, i think the other firmware was from ubmh1 odin firmware but im not shure wich firmware but im shure it was a stock samsung that came without knox
do you remember wich firmware was in your device, was a knox one?
Click to expand...
Click to collapse
my device model is either
KSA-I9192XXUAMH3
KSA-I9192XXUBNB1
I dont think my phone is with knox

well finally i was on stable connection , here is the my debrick image this also made from the guide http://forum.xda-developers.com/showthread.php?t=2625628 suggest you use this to write to your SD http://forum.xda-developers.com/showthread.php?t=2600869 and if your cell boots try go imd into download mode and flash your stock rom ,
this from firmware I9192DDU1BML1 , btw this img was created after i had deleted knox and other bloat ware from the rom , hope it helps.
https://www.dropbox.com/s/i6ul61hisnvrjog/debrick.img

dovakinn said:
well finally i was on stable connection , here is the my debrick image this also made from the guide http://forum.xda-developers.com/showthread.php?t=2625628 suggest you use this to write to your SD http://forum.xda-developers.com/showthread.php?t=2600869 and if your cell boots try go imd into download mode and flash your stock rom ,
this from firmware I9192DDU1BML1 , btw this img was created after i had deleted knox and other bloat ware from the rom , hope it helps.
https://www.dropbox.com/s/i6ul61hisnvrjog/debrick.img
Click to expand...
Click to collapse
gonna try it.. thanks for sharing. gonna post if there's an improvement..
I'll consider this as my last resort.. ill send it to the seller since I still have warranty for this phone.. I never flashed or rooted this phone. but if I send it back it'll take a month to get it back.. but better than nothing.

[ROOT][Samsung Galaxy Tab E][sm-t377p/sm-t560nu]

WHATS THIS?
This is my port of CF-AUTOROOT for the Samsung Galaxy TAB E.
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SAMMOBILE or a TWRP backup in case of problems. This will trip the knox counter.
Flash with ODIN 3.10.7 in the AP slot.
Load the respective file below into the AP slot and hit start.
cfautoroot_sm-t377p.tar
cfautoroot_sm-t560nu.tar
NOTE: ON SOME 5.1.1 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
STOCK TWRP IMAGE FOR SM-T377P
This is a link to the stock system, boot, modem image for the T377P in case anyone needs it. Needs to be restored with twrp.
Thanks to @shawn1976 for providing this.
https://www.dropbox.com/s/skuwsbzm2zigd83/sm-T377PVPU1AOJ5-boot-system-modem-only.zip?dl=0
Credits: Chainfire and my testers - Phrozen99 and nates730
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
.

FRP lock
Any suggestions on getting pass an FRP lock? My niece tried to root it but didn't turn on the enable OEM unlock. I just literally got it so don't have a back up and stock rom is no where I can find online even tried the Samsung Switch software and the T377P is not an option.

Jasn7766 said:
Any suggestions on getting pass an FRP lock? My niece tried to root it but didn't turn on the enable OEM unlock. I just literally got it so don't have a back up and stock rom is no where I can find online even tried the Samsung Switch software and the T377P is not an option.
Click to expand...
Click to collapse
Isn't there a recovery mode in the SS software that allows the firmware to be reflashed?

ashyx said:
Isn't there a recovery mode in the SS software that allows the firmware to be reflashed?
Click to expand...
Click to collapse
That was my plan ...however they do not support this model number yet so its not available to be reflashed. I checked sammobile as well figuring I could download firmware and use Odin to reflash and same situation.

There's a chance the sm-t377R4 firmware may flash as it's practically identical to the sprint firmware just a different csc.

Okay....will try and find that one.

Hi, I had a question. The Samsung Tab E is my first android device (I am a IOS user, so i know how to Jailbreak, but I don't know how to root!). My friend told me to root it, but I don't really know how to do it. Can you post a step by step tutorial. Also, after i rooted can i update my device to a newer version or do i have to remove the root. Lastly, how do you back up your device? Thank you! I appreciate your hard work!

Badob said:
Hi, I had a question. The Samsung Tab E is my first android device (I am a IOS user, so i know how to Jailbreak, but I don't know how to root!). My friend told me to root it, but I don't really know how to do it. Can you post a step by step tutorial. Also, after i rooted can i update my device to a newer version or do i have to remove the root. Lastly, how do you back up your device? Thank you! I appreciate your hard work!
Click to expand...
Click to collapse
You can follow the tutorial below, it's for the Tab A but the procedure is identical.
Obviously don't use the cf_autoroot file in the tutorial use the one here. Also note the PDA button in Odin is now called AP.
http://techchomps.com/how-to-root-the-samsung-galaxy-tab-a-9-7/

ashyx said:
You can follow the tutorial below, it's for the Tab A but the procedure is identical.
Obviously don't use the cf_autoroot file in the tutorial use the one here. Also note the PDA button in Odin is now called AP.
Click to expand...
Click to collapse
Thanks Man!!! Had some last questions: Can i update my device to a newer version (if available) or do i have to remove the root and how do you back up your device? Thank you again!

Badob said:
Thanks Man!!! Had some last questions: Can i update my device to a newer version (if available) or do i have to remove the root and how do you back up your device? Thank you again!
Click to expand...
Click to collapse
You can update your device with odin anytime you want but not via ota.
To back up you device you need to install TWRP.
Search Google for info on using TWRP.

ashyx said:
You can update your device with odin anytime you want but not via ota.
To back up you device you need to install TWRP.
Search Google for info on using TWRP.
Click to expand...
Click to collapse
Thanks For the help!

Where do I get TWRP for Tab E T560, and how do I install it?
Thank you.
Edit: Found the answer.

ashyx said:
There's a chance the sm-t377R4 firmware may flash as it's practically identical to the sprint firmware just a different csc.
Click to expand...
Click to collapse
I tried the t377R4 firmware that didn't work. Any idea on where I could track down a copy of the t377p? Odd I can't even use the Samsung Smart Switch or even Kies as it doesn't recognize the model number. Or if anyone has a backup available they can share please let me know.

I have a US Cellular Samsung Tab E SM-T377R4 and I rooted it using the procedure below. The root process went fine and everything is working well except Recovery Mode does not work. It just boots to a black blank screen when I try to go to Recovery Mode. But that's no big deal to me.
ashyx said:
You can follow the tutorial below, it's for the Tab A but the procedure is identical.
Obviously don't use the cf_autoroot file in the tutorial use the one here. Also note the PDA button in Odin is now called AP.
http://techchomps.com/how-to-root-the-samsung-galaxy-tab-a-9-7/
Click to expand...
Click to collapse

Stevenwsmith said:
I have a US Cellular Samsung Tab E SM-T377R4 and I rooted it using the procedure below. The root process went fine and everything is working well except Recovery Mode does not work. It just boots to a black blank screen when I try to go to Recovery Mode. But that's no big deal to me.
Click to expand...
Click to collapse
Surprised recovery doesn't work, considering the 2 devices are identical specs.
Try installing Twrp, you'll probably find that works OK.

Jasn7766 said:
I tried the t377R4 firmware that didn't work. Any idea on where I could track down a copy of the t377p? Odd I can't even use the Samsung Smart Switch or even Kies as it doesn't recognize the model number. Or if anyone has a backup available they can share please let me know.
Click to expand...
Click to collapse
Same problem here... I've been looking all over for a copy of the SM-T377P stock ROM. Anyone that happens to have a copy/link for it please share.

JohnICon said:
Same problem here... I've been looking all over for a copy of the SM-T377P stock ROM. Anyone that happens to have a copy/link for it please share.
Click to expand...
Click to collapse
What's the issue?

Rooting gone bad... Rooted my SM-T377P with KingRoot and there is an FRP Lock that comes up a week later. All of the custom ROM versions I have keep getting rejected by ODIN every time I try to flash them. The only other way I can think of doing this is to flash the stock ROM for the device.

JohnICon said:
Rooting gone bad... Rooted my SM-T377P with KingRoot and there is an FRP Lock that comes up a week later. All of the custom ROM versions I have keep getting rejected by ODIN every time I try to flash them. The only other way I can think of doing this is to flash the stock ROM for the device.
Click to expand...
Click to collapse
You realise you can't flash a custom rom with odin?
Also when you flash the stock t377r4 firmware what part fails?

The aboot fails every time I try to flash it

[ROM] SM-A105F Stock/Combination Firmware

Stock Firmware:
A105FDDU1ASC2
Combination Firmware:
FA90 A105FXXU1ASB6
Extract the firmware with 7zip
Use odin to flash it as per normal

Cool... Thanks man...

what is a combination firmware

How about A105g/ds?

Root/recovery
hello guys, is there any way to root and install custom recovery (TWRP) on galaxy A10 (A105F) or any one working on it ?
i've been searching the web for last two days and i found nothing really work
thank u guys

brahimlagdem said:
hello guys, is there any way to root and install custom recovery (TWRP) on galaxy A10 (A105F) or any one working on it ?
i've been searching the web for last two days and i found nothing really work
thank u guys
Click to expand...
Click to collapse
Did you find a twrp file to flash SM-A105F device ?

Any news about developping/availability of SM-A105F twrp file ? I hope Someone will be able to help with this (growing number of user as noticed on the internet)

Hh

timba123 said:
Hi. I have the metro pcs variant 10e. Our oem unlocking in developer options has been hidden/disabled/missing. Is the a10f the same as far as my metro variant? Also when trying to get into bootloader mode the phone vibrated and a little yellow exclamation ! symbol appeared at bottom of my screen right above the charging port. What was that exactly? This is my 1st A series device
Click to expand...
Click to collapse
even if its the same you cant unlock the bl or root as its a usa variant and its not allowed.
the yellow symbol you see is normal.. its an indicator for the charging i believe to indicate slow charging for example

deadman96385 said:
Stock Firmware:
A105FDDU1ASC2
Combination Firmware:
FA90 A105FXXU1ASB6
Extract the firmware with 7zip
Use odin to flash it as per normal
Click to expand...
Click to collapse
you do know flashing combo firmware now requires factory approval in the form of a token right?

elliwigy said:
you do know flashing combo firmware now requires factory approval in the form of a token right?
Click to expand...
Click to collapse
I don't really follow Samsung much anymore, when this was posted the phone was new and I had access to both and both firmwares weren't available anywhere so I posted it in case it would help someone.

timba123 said:
I have metro ASK4 firmware currently on phone. I found official ASK1 4 file firmware . When trying to downgrade I get SHA256 error. So locked bootloader prevents it? Cant even downgrade. What can I look into as far as changing property values sys.oem_unlock_allowed 1 temporarily if anything? I do apologize if my questions annoy the more experienced members. I used adb shell setprop and it added it but theres 2. One with 0 and one with 1
Click to expand...
Click to collapse
That's because you spelled it wrong bro lol.. it also doesn't do anything unfortunately and reverts after you reboot the device.
You cannot downgrade.. most time even on unlocked bl's downgrading is not allowed.
If you mean you found a lower firmware on same rev that's a different story. You get sha error because you need a modified odin that has the sha checks disabled.. or you can use something like chimera tool

timba123 said:
Lol I see my spelling error now. I think I was really burned out trying to learn and figure out stuff. Is there any decent links on how to patch SHA256? I tried many web searches and little results
Click to expand...
Click to collapse
huh? thats not useful at all lol.. theres already pstched odins all over the internet.. it doesnt patch the firmware, it patches odin software so it ignores the sha256 altogether

timba123 said:
Yes there are many patched Odin's but not a patched 3.14 version. My device will not work with any odin lower than 3.14
Click to expand...
Click to collapse
i forgot lol.. i also have an a10e but i use chimera tool and it works fine and no sha checks if u select that ootion
Sent from my SM-G977P using Tapatalk

timba123 said:
Unfortunately I cant afford any tool like that. I've tried crack versions that dont require box or card but none of them are current cracks.
Click to expand...
Click to collapse
crack talk is also not allowed on xda lol
Sent from my SM-G977P using Tapatalk

timba123 said:
Thanks. I downloaded official version. Pay day I'm going to try a starter license. I'm a little excited lol. Do you know if it flashes combo on a10e?
Click to expand...
Click to collapse
it does/doesnrt.. u cant just flash combo firm to the device, it also has nothing to do with odin or chimera.. samsung implemented security so combo firm cannot b flashed unless you have a token for it.. without it u can only flash stock firmware.. if u got acombo token tho then yes, chimera at that point could flash combo no problem