Hi guys
I've just bricked my tab. I flashed ICS to try it then I did a Factory reset and the tab was bricked.
I can access the Download mode, but when I put any firmware into Odin PDA the flashing process get stuck shortly after " NAND Write Start!! " at the beganing of "factoryfs.img" !
Long story short, my tab is totally bricked is there anything I can do ?? Please help me as this tab is imported and I have no warranty.
Thank you very much, really appreciate the community here.
Coolman4now said:
Hi guys
I've just bricked my tab. I flashed ICS to try it then I did a Factory reset and the tab was bricked.
I can access the Download mode, but when I put any firmware into Odin PDA the flashing process get stuck shortly after " NAND Write Start!! " at the beganing of "factoryfs.img" !
Long story short, my tab is totally bricked is there anything I can do ?? Please help me as this tab is imported and I have no warranty.
Thank you very much, really appreciate the community here.
Click to expand...
Click to collapse
As long as you can access the Download mode, you are not hard bricked, just download the rom that your device came with and install through odin, this will be the only image that your tab will accept.
The problem is, the flashing starts normally and as soon as it starts to write the NAND the progress stops then a big red fail appears after a long time.
Thank you for your reply, I'm so desperate right now.
Can you tell us what model and firmware, etc you used to flash? I think you are the first case
maybe ur firmware is corrupt?try downloading a new one...as long u can acces download mode it is softbrick
Luckily I have a screenshot of the previous firmware
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I downloaded lots of firmware an none gets past the factoryFS
Did you do the factory reset while you were on ICS? Did you have CWM or root at all previously and/or after installation of ICS?
Hmmm...Curious. Any flashing program to be tried, other than Odin? If everything else fails, probably the flash ROM chip has gone bad like it did on my Xperia x10. Send it in for warranty, if possible, and tell them.you left it charging.overnight and it didn't wake in the morning...
Sent from my LG-P920 using xda app-developers app
I had root before on HC but I did a factory reset before installing ICS, then I flased the Austria ICS build. Then I did a factory reset from recovery and boom the tab can't boot nor can it be flashed ! always gets stuck at Writing NAND.
GRudolf94 said:
Hmmm...Curious. Any flashing program to be tried, other than Odin? If everything else fails, probably the flash ROM chip has gone bad like it did on my Xperia x10. Send it in for warranty, if possible, and tell them.you left it charging.overnight and it didn't wake in the morning...
Sent from my LG-P920 using xda app-developers app
Click to expand...
Click to collapse
To add insult to the injury, it's imported and I have no warranty. :good:
what you need to do is
You have super brick and not hard brick.what you need to do re partition using .pit file and then flash the room again. I had thus same issue and repartition worked for m e. How it helps
Well, you should contact service support anyway. Samsung generally doesn't care too much if the product was bought in another country...And a friend of had his Brazilian Tab 10.1 repaired in the UK, touchscreen problem, replaced by new unit free of charge... But, try another flashing solution first.
Sent from my LG-P920 using xda app-developers app
This looks like it is probably the super brick that people experienced on the note. We are luckier than the note because we have a dedicated recovery partition, so you can avoid the super brick by using a different recovery (such as the honeycomb recovery or CWM) and still use stock ICS as your rom.
As long as you don't use the stock ICS recovery for wiping/factory reset, you will be fine.
om0 said:
You have super brick and not hard brick.what you need to do re partition using .pit file and then flash the room again. I had thus same issue and repartition worked for m e. How it helps
Click to expand...
Click to collapse
How did you flash the pit file? Do you still have it?
Instructions please!
My battery actually died too - how can you charge it? D=
locerra said:
This looks like it is probably the super brick that people experienced on the note. We are luckier than the note because we have a dedicated recovery partition, so you can avoid the super brick by using a different recovery (such as the honeycomb recovery or CWM) and still use stock ICS as your rom.
As long as you don't use the stock ICS recovery for wiping/factory reset, you will be fine.
Click to expand...
Click to collapse
I guess that's not the case. Odin would overwrite all the partitions, including recovery...So device should act like factory new. However, flashing programs are often troublesome...
Sent from my LG-P920 using xda app-developers app
why not trying to let the battery run out first?
GRudolf94 said:
I guess that's not the case. Odin would overwrite all the partitions, including recovery...So device should act like factory new. However, flashing programs are often troublesome...
Click to expand...
Click to collapse
The initial post said that he did a factory reset, and then used Odin. The super brick is caused by using factory reset/wiping on recovery's built on un-safegarded kernels (the bug is actually in the firmware, but you can work around the bug by disabling a setting in the kernel). My guess is that the stock recovery with the ICS is built on an un-safegarded kernel.
I would seriously recommend that people go read up on the super brick, it affects our many (most?) of the Tab 7.7s out there. If you experience it, you better hope that Samsung support likes you.
I have tried the pit file lots of times, the flashing stops as soon as writing NAND starts.
Coolman4now said:
I have tried the pit file lots of times, the flashing stops as soon as writing NAND starts.
Click to expand...
Click to collapse
It looks like your NAND is cooked.
Have a look at ths http://forum.xda-developers.com/showthread.php?t=1682444
So Im blessed with a fried NAND Nice
Does anyone have the correct PIT file please ?
Related
Introduction
This package will totally reset your Captivate to UCKB2. This is the current version pushed out on new Captivate devices today. This package is intended for use on AT&T, however it will work with the Rogers SGH-i896 if you reset APN.
Note: this is stock rooted, I will put up a non-rooted version soon.
This package includes:
Repartitioning: Repartition to stock KB2
Reloading: IBL/PBL, PARAM, SBL, SBL2, Kernel, Recovery, FactoryFS and modem
formatting:Cache and DBdata
This package does not wipe:
EFS(Where your serial number and carrier information is stored)
Data(where your market apps are stored)
SDCard (where your pictures are stored)
You may use this code to reformat the Data and SDCard *2767*3855# There is no way to do this from Download Mode. The code will leave the EFS untouched.
Download:
Total Stock:
Download AT&T Samsung Captivate Total Stock UCKB2
http://files.teamkomin.com/Captivate/SamsungCaptivate-SGHi897-UCKB2-NoRoot-One-Click.jar
Total Stock Rooted:
Download AT&T Samsung Captivate Total Stock UCKB2 "Rooted Version"
http://files.teamkomin.com/Captivate/SamsungCaptivate-SGHi897-UCKB2-Rooted-One-Click.jar
Instructions:
Get the latest version of java here: http://java.com/en/download/installed.jsp
Put your phone into "Download Mode"
Run the program once, and if it does not work, then check the "Flash Bootloaders" checkbox and flash again
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Your device will end up as it came from the factory:
How I created this package:
I obtained the stock 2.1/2.2 bootloader which Trae uploaded
The stock Captivate part.pit came from my device using Heimdall(Download Pit option)
Uploaded the KB2 firmware to my device with bootloaders from nerz
Performed "wipe data" in recovery mode
Exploited the root prompt at the battery charge sequence using UART and grabbed the stock, wiped dbdata/cache partitions and params.lfs partition
Created a Heimdall tar.gz package using Heimdall 1.3
Finally, I used my Heimdall One-Click *BETA* packager to generate this one-click
This procedure can be reproduced for any custom ROM in the future.
Credits:
nerz- kb2 firmware: http://forum.xda-developers.com/showthread.php?t=1263379
Trae32566- 2.1/2.2 bootloaders: http://forum.xda-developers.com/showthread.php?t=1095067
Partition problems have been fixed.
Please use a good USB cable so that we don't clutter this thread with "this dosn't work"
Nice work!
Trying this out now on Win7 from Pinnacle 1.2 (RFS) will let you know results. I have been waiting to try UCKB2, thanks Adam!
Just wanting to be sure before I try and brick my phone lol.
When coming down from gigglebread, we need to use the froyo bootloaders i assume.
I dont know if its from running this in windows, but the flash bootloaders check box is greyed out for me. i clicked the details box and i am able to change the true false values for the flash column.
can i assume that i need to have the bootloaders set to true as they are set to false by default? also should i just true them all?
madmattco said:
Just wanting to be sure before I try and brick my phone lol.
When coming down from gigglebread, we need to use the froyo bootloaders i assume.
I dont know if its from running this in windows, but the flash bootloaders check box is greyed out for me. i clicked the details box and i am able to change the true false values for the flash column.
can i assume that i need to have the bootloaders set to true as they are set to false by default? also should i just true them all?
Click to expand...
Click to collapse
You wont brick your device if you don't flash bootloaders. Follow the instructions. If it wont boot, then flash again with bootloaders. This is a safety feature. If your device wont boot after flashing, then check flash bootloaders and flash it again.
Thanks for the quick reply Adam. Worked like a charm. Always a god job from you.
Adam... this is EXACTLY what i've been looking for. My wifes captivate hates every rom I've tried and I wanted to get her back to stock.
THANK YOU!
Adam,
Can I use this to go back to stock from CM7?
If you see this message:
Code:
Local and device PIT files don't match and repartition wasn't specified!
then your partitions are changed and it won't work and do not try it on Windows or Mac. On Linux, you can use this to correct the repartitioning problem and flash it. http://forum.xda-developers.com/showpost.php?p=17485056&postcount=23
Thanks for putting this together. I saw a need for this, but lacked the skills to completethis complicated task. Any chance of putting together an Odin package for it?
Edit
Can I dl your files and use the Odin 1 click creator to make an Odin flashable?
mrhaley30705 said:
Thanks for putting this together. I saw a need for this, but lacked the skills to completethis complicated task. Any chance of putting together an Odin package for it?
Edit
Can I dl your files and use the Odin 1 click creator to make an Odin flashable?
Click to expand...
Click to collapse
Hell no. Odin is closed source. It also uses closed source drivers. I don't support that at all.
You edited .. sure. If you want. I will have no part of Odin until the source is opened.
FOSS ....
Sent from my SAMSUNG-SGH-I897 using XDA App
c0ldburn3r said:
Adam... this is EXACTLY what i've been looking for. My wifes captivate hates every rom I've tried and I wanted to get her back to stock.
THANK YOU!
Click to expand...
Click to collapse
I know right LOL...
Sent from innerspace on my hacked telly...
i own an unlocked cappy.....
if i use this, will it lock my device again?????/
syanz87 said:
i own an unlocked cappy.....
if i use this, will it lock my device again?????/
Click to expand...
Click to collapse
No. Once unlocked, always unlocked.
Sent from my Inspire 4G
Worked well via Win 7 64bit, XP although it slowed up a bit (ran it live) and on Ubuntu 11.04. Switched back to pinnacle and all is right.
c0ldburn3r said:
Adam... this is EXACTLY what i've been looking for. My wifes captivate hates every rom I've tried and I wanted to get her back to stock.
THANK YOU!
Click to expand...
Click to collapse
Are you sure it is not simply an EBKAC error? I have to check my wife's every couple of Weeks. Simple uninstall of crap she downloaded and used for two mins plus delete cache seems to solve the problem.
Sent from my SAMSUNG-SGH-I897
Sent from my SAMSUNG-SGH-I897
Great job adam been waiting on something to be done like this with heimdall. Its a great utility and most of all open source. I've noticed less bad flashes with heimdall also and altogether less frustration.
Sent from my i897 w/Andromeda 3, Suckerpunch kernel, & 1.3Ghz OC using Tegrak.
This package worked great on both of my Captivate phones. You and Ben have done a great job along with all others who have supported the project. It will be awesome once your able to get the re-partitioning to work properly on Mac's along with Windows.
Great work. I didn't think it would work because one click unbrick didn't recognize my phone. But I opened the file, plugged in and it detected my phone. I didn't actually flash it, but I figure if it sees my phone, it should flash with no problem.
mrhaley30705 said:
Great work. I didn't think it would work because one click unbrick didn't recognize my phone. But I opened the file, plugged in and it detected my phone. I didn't actually flash it, but I figure if it sees my phone, it should flash with no problem.
Click to expand...
Click to collapse
If you have the phone ! Computer screen and heimdall recognizes your phone...hit start cause that's basically download mode
Sent from my SAMSUNG-SGH-I897 using XDA App
i just make repack of dxlp9 with simg2img and ext4_utils..
Just unpacking factoryfs insert su and superuser with proper permission and then repack with mkuserimg.sh..
Tar with ustar..and then md5
When flashing im on stock gingerbread dxla1
All progress working well and odin say pass with the green sign..
After reboot an icon android robot make a progress bar like flashing..but it stuck for a long time.
I turn out the device and go to download mode again.. Try to flashing the stock odin dxlp9 but the result is same..
I try with the third. ..... And odin stuck at factoryfs.img.. Until 15 menit..
Last try.. Im use odin with stock gingerbread but still stuck at factoryfs.img...
Just wanna share all of this..
I will go to samsung center and will make a claim about it...
SO becarefull with ALL ICS release..
Im the unlucky one.. Isnt it?
another brick story
the bugs seem to be exist in every ics release at the same batch after all. thanks for bringing this up bud. good luck for the warranty claim!
Sad news... But this ics bug is so annoying... Hope you get the warranty.
bejoanakmami said:
the bugs seem to be exist in every ics release at the same batch after all. thanks for bringing this up bud. good luck for the warranty claim!
Click to expand...
Click to collapse
vivek2701 said:
Sad news... But this ics bug is so annoying... Hope you get the warranty.
Click to expand...
Click to collapse
Just another bugs.. I dont know.. This is really superbrick like PSA said or another bug..
by looking at the symptoms it definitely is a superbrick.
suwandiapr said:
i just make repack of dxlp9 with simg2img and ext4_utils..
Just unpacking factoryfs insert su and superuser with proper permission and then repack with mkuserimg.sh..
Tar with ustar..and then md5
When flashing im on stock gingerbread dxla1
All progress working well and odin say pass with the green sign..
After reboot an icon android robot make a progress bar like flashing..but it stuck for a long time.
I turn out the device and go to download mode again.. Try to flashing the stock odin dxlp9 but the result is same..
I try with the third. ..... And odin stuck at factoryfs.img.. Until 15 menit..
Last try.. Im use odin with stock gingerbread but still stuck at factoryfs.img...
Just wanna share all of this..
I will go to samsung center and will make a claim about it...
SO becarefull with ALL ICS release..
Im the unlucky one.. Isnt it?
Click to expand...
Click to collapse
how about if you try to flash new ics bootloader
http://forum.xda-developers.com/showthread.php?t=1658967
Got you om suwandi...sorry to hear that anyway...
Sent from my GT-N7000 using Tapatalk 2
kalkanisvec said:
how about if you try to flash new ics bootloader
http://forum.xda-developers.com/showthread.php?t=1658967
Click to expand...
Click to collapse
No i couldnt.. There is no progress bar while flashing in download mode..
I can enter download mode but flashing stuck...no recovery..
Please try this one
1. In download mode through PC odin just Flash the single PIT file with ICS LPF stock rom (Yes you heard right) with repartition checked no other file just a single pit...
2. On success remove your battery go to download mode again and flash the whole LPF...once again with all the files (PIT, bootloader, pda csc and modem) again check repartion...It should boot with LPF.
Please confirm if it works.....
last Friday i tried to install the lpf version via PC Odin... i was on rooted lpy
it was going ok but before the end it hang at factoryfs.img & gave a message"fail!" with red color..
maybe i waited 30 seconds then i tried to restart the phone & i got screen of death "if i'm not mistaken... see the pic"
but i was lucky because i was able to enter the download mode
after that i tried to install official LPY again... failed
tried to install official LA4... failed
after that i made a fast panic searching to solve the problem...
anyways the solution was by flashing a n7000 GB bootloader & official LA4 after taking the battery out for some time...
so if u are in the same situation try it out... maybe it will help
better to wait a confirmation from an expert...
good luck...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
something like this...
This doesn't sound like the bug everyone is talking about because you odin from gb or something I am not understanding
Sent from my GT-N7000 using Tapatalk 2
kalkanisvec said:
how about if you try to flash new ics bootloader
http://forum.xda-developers.com/showthread.php?t=1658967
Click to expand...
Click to collapse
And the bootloader is going to help how?
kalkanisvec said:
how about if you try to flash new ics bootloader
http://forum.xda-developers.com/showthread.php?t=1658967
Click to expand...
Click to collapse
rajendrakumardbg said:
Please try this one
1. In download mode through PC odin just Flash the single PIT file with ICS LPF stock rom (Yes you heard right) with repartition checked no other file just a single pit...
2. On success remove your battery go to download mode again and flash the whole LPF...once again with all the files (PIT, bootloader, pda csc and modem) again check repartion...It should boot with LPF.
Please confirm if it works.....
Click to expand...
Click to collapse
Oke ill try soon..
nandihno said:
This doesn't sound like the bug everyone is talking about because you odin from gb or something I am not understanding
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Yes.. Im flashing for gingerbread.. But stuck happen after odin success write all ICS files to device...
This is what odin do when you flashing..
First they will write all necessary file to their partition..
After the flashing success, tab will reboot into recovery for format the /system and copying the files for CSC files...and reboot again..
SO the rest of operation its from ICS kernel..
Correct me if im wrong..
chasmodo said:
And the bootloader is going to help how?
Click to expand...
Click to collapse
I think not..coz flashing will stuck, whatever file i choose..
it is safe if we flash LP9 together with LPF bootloader ?
thehackersz said:
it is safe if we flash LP9 together with LPF bootloader ?
Click to expand...
Click to collapse
Im Not sure.. but probability still same..
I have some friend with lpf bootloader and flashing the lp9 without issues..
but im not suggest you to do that..
suwandiapr said:
Im Not sure.. but probability still same..
I have some friend with lpf bootloader and flashing the lp9 without issues..
but im not suggest you to do that..
Click to expand...
Click to collapse
sad to see official ICS for our country effected with this annoying bug.
i even saw people do saying that the build date LPF rom is newer compared to LP9. Even though LP9 just released by Samsung.
JTAG not work..
I've always had this problem since Gingerbread when using Odin to flash fw downloaded from XDA.
My solution is shut down the phone, restart by inserting the USB Jig (enter flashing mode) and flash the kernel that I separately downloaded for rooting purposes.
It works every single time I hit such error.
maybe this can help
hey, while browsing through threads I found this
http://forum.xda-developers.com/showpost.php?p=26285877&postcount=12
maybe this will help you?
Im a total noob, hope some pro can give you better advice.
Good luck.
suwandiapr said:
i just make repack of dxlp9 with simg2img and ext4_utils..
Just unpacking factoryfs insert su and superuser with proper permission and then repack with mkuserimg.sh..
Tar with ustar..and then md5
When flashing im on stock gingerbread dxla1
All progress working well and odin say pass with the green sign..
After reboot an icon android robot make a progress bar like flashing..but it stuck for a long time.
I turn out the device and go to download mode again.. Try to flashing the stock odin dxlp9 but the result is same..
I try with the third. ..... And odin stuck at factoryfs.img.. Until 15 menit..
Last try.. Im use odin with stock gingerbread but still stuck at factoryfs.img...
Just wanna share all of this..
I will go to samsung center and will make a claim about it...
SO becarefull with ALL ICS release..
Im the unlucky one.. Isnt it?
Click to expand...
Click to collapse
for someone with the experience to repack their own ROM ,you certainly surprise me by completely missing the stickies and tens of threads posted about how dangerous ICS is.
you flashed a with a wipe ROM? and even if not a wipe ROM ,every ROM will do it's own formatting of cache and flashing some stuff from recovery on first boot
that's the bar you saw when you flashed .
any wipe or flash from ICS kernels has a good chance of locking up the emmc of your device ,thus giving you a brick.
I'd try my luck with the warranty claim if I were you ,just make sure to reset the flash counter first.
good luck
To start with, I'm flash addict and always trying to flash new roms/firmwares. However after flashing one of the newest samsung firmware i got this little red exlamation mark:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have tried to reset flash counter in a lot of ways but it always stayed at number "1" (After you reset with triangle away latest, opening app again shows 0 flash counter but after reboot it increases to 1). Even if my flash counter was 5, after reset it was staying with 1. Seems that samsung introduced some security improvements against reseting flash counter for galaxy s3.
But one xda member InsteadWoolf published solution to reset flash counter:
1- Reset via Triangle Away
2- Turn off phone and go to download mode.
3- Then flash via odin pc the stock firmware you want.
After this method flash counter is 0. However if you go for custom rom or not stock kernel, that red exlamation mark comes back and flash counter increases to 1.
BIG CREDITS TO InsteadWoolf
So what firmware are you claiming Samsung has hacked as i have yet to see this on any build .
jje
JJEgan said:
So what firmware are you claiming Samsung has hacked as i have yet to see this on any build .
jje
Click to expand...
Click to collapse
i cant say exactly because didnt notice when i got it but i think with the latest BLH3 one ics. Never had this problem before, was flashing a lot via pc odin and reseting to 0 easily. And before i had even flash counter 5 and there wasnt any red exlamation mark like in the picture.
Thanks for noticing.
But, damn but what greasy screen! You should clean it more often.
Theshawty said:
Thanks for noticing.
But, damn but what greasy screen! You should clean it more often.
Click to expand...
Click to collapse
it is with crap screen protector
Are you sure that has something to do with the flash counter?
Phew......
.....so glad that that **** didn't show up after flashing Jelly Bean over Odin!! :victory:
Something to look out for? What do you guys think?
// Ohamn
I had the same issue after flashing a miui rom i had to reset with triangle away and go into download mode straight away without letting the phone boot up then flash full stock ics via odin and it reset. It took me ages to work it out i nearly gave up.
Sent from my GT-I9300 using XDA Premium HD app
azcamm27 said:
I had the same issue after flashing a miui rom i had to reset with triangle away and go into download mode straight away without letting the phone boot up then flash full stock ics via odin and it reset. It took me ages to work it out i nearly gave up.
Sent from my GT-I9300 using XDA Premium HD app
Click to expand...
Click to collapse
but if u flash something not official then u wont be able to reset again. This is smt new, never was like that
As i have flashed and reset at least 50 times in the last few weeks .
Reset counter with TA.
Flash custom kernel via Odin.
Nothing bar standard rom count of 1.
Run TA still nothing and counter 0 .
I wonder if something else is triggering the red mark .
jje
i reported it in OTA thread and also to Chainfire weeks ago, but no one took notice.. if anyone wants to test, i can upload example of such sboot.bin..
still everything is back to normal with flashing old sboot.bin
tumult said:
i reported it in OTA thread and also to Chainfire weeks ago, but no one took notice.. if anyone wants to test, i can upload example of such sboot.bin..
still everything is back to normal with flashing old sboot.bin
Click to expand...
Click to collapse
yeh please upload i will try it
EdgaBimbam said:
yeh please upload i will try it
Click to expand...
Click to collapse
which one new or old? anyway at work and going to business trip right after so I'll upload it ASAP.
tumult said:
which one new or old? anyway at work and going to business trip right after so I'll upload it ASAP.
Click to expand...
Click to collapse
hmmm if i want to remove that flash counter 1 with red exlamation mark i need to flash old one?
EdgaBimbam said:
hmmm if i want to remove that flash counter 1 with red exlamation mark i need to flash old one?
Click to expand...
Click to collapse
yes,
here is zip with old sboot.bin (from XXALEF), this is all i can do ATM, you have to unzip it and pack in tar (quick search gave me this link for making tar http://forum.xda-developers.com/showthread.php?t=1777579)..
and all standard things apply i am not responsible and blah blah if anything goes wrong, flashing bootloader is a sucker and may brick your phone..
edit: att. removed, look few posts bellow.
tumult said:
yes,
here is zip with old sboot.bin (from XXALEF), this is all i can do ATM, you have to unzip it and pack in tar (quick search gave me this link for making tar http://forum.xda-developers.com/showthread.php?t=1777579)..
and all standard things apply i am not responsible and blah blah if anything goes wrong, flashing bootloader is a sucker and may brick your phone..
1F0035205D32C9A06A3624E9E4C40E4F *sboot.zip
Click to expand...
Click to collapse
maybe there is who couls make .tar or cwm package of this file. Im not so good at developing and other things so dont want to mess things
EdgaBimbam said:
maybe there is who couls make .tar or cwm package of this file. Im not so good at developing and other things so dont want to mess things
Click to expand...
Click to collapse
i tried to make tar via phone, but got some error.. have to drive now, sorry
ps. there is thread in general section from as i9000 user with firmwares if i remember correctly with old bootloader
there, a Odin flashable tar.. tested by myself and my phone booted. see iff it helps with triangle away. thanks to secret unknown for instructions of making tar .
WARNING! if you brick it, you got to stick with it
D55F04C26C83CAA552B62F529E4434C2 *BEWARE_of_BRICK_i9300XXALEF_sboot.tar
edit: i flashed it via odin 3.04, edited .ini file to enable boot update and placed it in bootloader box.. don't know if editing ini is needed, but that's what i did and it worked.
PhoneBootUpdate=1
tumult said:
there, a Odin flashable tar.. tested by myself and my phone booted. see iff it helps with triangle away. thanks to secret unknown for instructions of making tar .
WARNING! if you brick it, you got to stick with it
D55F04C26C83CAA552B62F529E4434C2 *BEWARE_of_BRICK_i9300XXALEF_sboot.tar
edit: i flashed it via odin 3.04, edited .ini file to enable boot update and placed it in bootloader box.. don't know if editing ini is needed, but that's what i did and it worked.
PhoneBootUpdate=1
Click to expand...
Click to collapse
thx will try it
JJEgan said:
As i have flashed and reset at least 50 times in the last few weeks .
Reset counter with TA.
Flash custom kernel via Odin.
Nothing bar standard rom count of 1.
Run TA still nothing and counter 0 .
I wonder if something else is triggering the red mark .
jje
Click to expand...
Click to collapse
this was sboot that was problematic for me, i don't know if i gor it in one of NEE OTA JB leaks or in my country ICS official OTA update.
I have a spare galaxy s5 at home that I would like to get up and going, it's kltedv. Every time it boots the phone restarts and gives android crash errors. I've flashed stock onto it and it still does the same thing. Is there a way to rebuild everything using Odin that may fix it?
Sent from my SM-G900I using Tapatalk
chainzy said:
I have a spare galaxy s5 at home that I would like to get up and going, it's kltedv. Every time it boots the phone restarts and gives android crash errors. I've flashed stock onto it and it still does the same thing. Is there a way to rebuild everything using Odin that may fix it?
Sent from my SM-G900I using Tapatalk
Click to expand...
Click to collapse
Sounds like you didn't factory reset your device. Before you factory reset, I recommend flashing TWRP recovery, mount your phone in recovery so you can back up important files to your PC if required.
After you've backed-up your files
Reboot (yes reboot, so switch your device off first) into the recovery menu (hold vol up + home + power), then select wipe data. This will wipe all data from your phone.
chainzy said:
I have a spare galaxy s5 at home that I would like to get up and going, it's kltedv. Every time it boots the phone restarts and gives android crash errors. I've flashed stock onto it and it still does the same thing. Is there a way to rebuild everything using Odin that may fix it?
Sent from my SM-G900I using Tapatalk
Click to expand...
Click to collapse
Where you cumming frop lolipop rom and flashed marshmallow or nougat rom ? If yes have you tick bootloader update in odin ? Rom will never boot without this update ! Try this if the previous good advice from Saber didn't help .
Everything is wiped. This is what happens when booting. Lines going across the screen. What originally happened was the person I got it from he had tried to do a update and the phone turned off. So I just flashed stock firmware but still get these lines.. Something is corrupted?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SM-G900I using Tapatalk
When it boots in everything crashes in setup, get the error message unfortunately has stopped
Sent from my SM-G900I using Tapatalk
Looks like your phone needs a new main logic board because of defective memory.
chainzy said:
When it boots in everything crashes in setup, get the error message unfortunately has stopped
Click to expand...
Click to collapse
Here's my two cents if you've done what @Saber and @1981sebas suggested and still had no luck.
First, make sure the stock you've flashed is the latest MM XSA version to ensure you have the latest bootloader and modem. You can get it from sammobile or updato. It may take a couple of attempts so don't panic if it doesn't stick first time.
If it's still not right, hunt up the PIT files for your device and repartition it. Make sure you get legit files that others have used and had success with. You don't want to flash the wrong PIT. Then try flashing stock again.
Incidentally, have you tried flashing a solid custom ROM like RR or Cosmic? Maybe it's just an issue with your stock file being a bit corrupt if you haven't checked the md5 and any intact ROM will work fine.
My last option would be to try KIES because I personally find it iffy but others have had success with the recover phone option or whatever it's called. If you have KIES installed, just make sure it's disabled when you're using Odin and vice versa.
If none of this works, it may be a hardware issue. Good luck.
Sent from my Samsung SM-G900I using XDA Labs
I have tried a pit file I have but it didn't seem to do anything with that and re partition checked. I have tried several stock roms. Even tried the firmware with kies and still the same thing happens. Custom rom does the same.. The lines only come up on the screen when its booting.. They never come up in recovery or anything like that
Sent from my SM-G900I using Tapatalk
Dirty Flasher said:
hunt up the PIT files for your device and repartition it
Click to expand...
Click to collapse
That may be the case.
I'd try to download the latest "low_ship" factory firmware via Samfirm.
It contains a proper pit file in the CSC so it's necessary simply to flash it via Odin to repartition the device and clean everything on it.
EDIT 2022-06-30: FOUND A RELIABLE SOLUTION FOR MY NEW T307U TABLET! May work for other models! https://forum.xda-developers.com/t/...e-it-as-a-normal-tablet.4316969/post-87091297
Original post from 2021-08-09 below:
Following this thread to no avail: https://forum.xda-developers.com/t/doordash-knox-customized-tablet-unable-to-remove.3890522/
Setup requires an internet connection, at which point it sets up MobiControl:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My friend's an IT so he set up Meraki for me which I can enroll in instead of MobiControl, but a minute later this pops up:
I still have access to the settings but cannot enable USB Debugging.
I flashed a combination file which got me to the "factory binary" where I can unlock OEM and enable USB Debugging, but I don't know where to go from here:
I flashed a stock ROM, but that doesn't get rid of doordash and MobiControl during setup.
Please help!
Which Android version did you flash? Did you finally get rid of MobiControl?
XDA.Samsung said:
Which Android version didn't you flash? Did you finally get rid of MobiControl?
Click to expand...
Click to collapse
I solved this. Basically, I accidentally bricked the tablet, which I assume is what caused Samsung Knox to fail and thus Mobi Control didn't try installing on a fresh flash of Android 8.1. Fuller story below:
After 3 days straight of trying to reset the tablet, including flashing the combo file, trying anything I can think of, re-flashing the stock rom and seeing if the problem is gone, I finally fixed it.
What ended up happening was, while re-flashing the stock rom on my 4th attempt, I flashed the AP but not one of the other things (I guess CP?) which resulted in the tablet getting bricked.
Long story short, I held both volume buttons and power to boot into a blue download mode (as opposed to a black one via holding power down + volume and selecting download mode, since the volume down + power nor the volume up + power combos weren't working) and flashed the stock rom to it properly.
Upon setup, I was still required to set up wi-fi, but it didn't attempt to install mobicontrol! I've been using the tablet normally since. Who would have known accidentally bricking the tablet was all I needed to do!
genesisboy4 said:
I solved this. Basically, I accidentally bricked the tablet, which I assume is what caused Samsung Knox to fail and thus Mobi Control didn't try installing on a fresh flash of Android 8.1. Fuller story below:
After 3 days straight of trying to reset the tablet, including flashing the combo file, trying anything I can think of, re-flashing the stock rom and seeing if the problem is gone, I finally fixed it.
What ended up happening was, while re-flashing the stock rom on my 4th attempt, I flashed the AP but not one of the other things (I guess CP?) which resulted in the tablet getting bricked.
Long story short, I held both volume buttons and power to boot into a blue download mode (as opposed to a black one via holding power down + volume and selecting download mode, since the volume down + power nor the volume up + power combos weren't working) and flashed the stock rom to it properly.
Upon setup, I was still required to set up wi-fi, but it didn't attempt to install mobicontrol! I've been using the tablet normally since. Who would have known accidentally bricking the tablet was all I needed to do!
Click to expand...
Click to collapse
Good to know. Congratulation. Does it still show secured by knox on boot screen?
I had no luck. I can't flash anything, got error "MDM mode, can't download ".
XDA.Samsung said:
Good to know. Congratulation. Does it still show secured by knox on boot screen?
Click to expand...
Click to collapse
Yes, it does.
XDA.Samsung said:
I had no luck. I can't flash anything, got error "MDM mode, can't download ".
Click to expand...
Click to collapse
Make sure you're using the right version of odin for your tablet and you're flashing the right version of android.
genesisboy4 said:
Yes, it does.
Make sure you're using the right version of odin for your tablet and you're flashing the right version of android.
Click to expand...
Click to collapse
Which version of Odin did you use?
XDA.Samsung said:
Which version of Odin did you use?
Click to expand...
Click to collapse
Odin3_v3.13.3
genesisboy4 said:
Odin3_v3.13.3
Click to expand...
Click to collapse
After tried 5 versions of Odin, include 2 different v3.13.3, finally got a good news. I can flash T387v firmware Andriod 8.1 and 9. But the bad news is I cannot brick it, no matter flashed only AP or BL. I tried to flash with T387W or T387T firmware, I got PIT error messages.
Which version of firmware were you using?
XDA.Samsung said:
After tried 5 versions of Odin, include 2 different v3.13.3, finally got a good news. I can flash T387v firmware Andriod 8.1 and 9. But the bad news is I cannot brick it, no matter flashed only AP or BL. I tried to flash with T387W or T387T firmware, I got PIT error messages.
Which version of firmware were you using?
Click to expand...
Click to collapse
I think I installed android version SM-T387V_1_20200520121029_yelpqjg66y_fac.
genesisboy4 said:
I think I installed android version SM-T387V_1_20200520121029_yelpqjg66y_fac.
Click to expand...
Click to collapse
Thank you. It looks like it's Android 9. Did you update it to Android 10?
XDA.Samsung said:
Thank you. It looks like it's Android 9. Did you update it to Android 10?
Click to expand...
Click to collapse
It's Android 8.1. If that file I mentioned is 9, then it's not the one I flashed, but was instead on my to-do list of troubleshooting steps. I was going to try flashing Android 9 and 10 but I got it working with 8.1 so I'm keeping it on that. Plus, the newer the android, the more secure Samsung Knox will be, so it will be harder breaking it.
Any idea where you downloaded it from? I cant seem to find a link.
quiqsilverr said:
Any idea where you downloaded it from? I cant seem to find a link.
Click to expand...
Click to collapse
Android 10: https://samfrew.com/download/Galaxy__Tab__A__/1hjk/VZW/T387VVRU3CUI2/T387VVZW3CUI2/
"The fact that it has MobiControl installed suggests it's a company device, and is therefore administered by that company's IT department. It's probably going to be difficult to remove MobiControl unless you talk to that IT department about it."
The above is a quote I found regarding Knox and the MobiControl app. Which tells me that this thread, although likely unintentional, is violating XDA Forum Rule #9:
9. Don't get us into trouble.
Don't post copyrighted materials or do other things which will obviously lead to legal trouble. If you wouldn't do it on your own homepage, you probably shouldn't do it here either. This does not mean that we agree with everything that the software piracy lobby try to impose on us. It simply means that you cannot break any laws here, since we'll end up dealing with the legal hassle caused by you. Please use common sense: respect the forum, its users and those that write great code.
Click to expand...
Click to collapse
XDA does not wish to be held liable for circumventing device security regardless of intent of the user, which is why I'm closing this thread.
-Regards: Badger50