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.
Related
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
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 ?
I have a Att galaxy s4 i337 and I'm running black box ROM I don't know what happen but every time I try to go into recovery it brings up a yellow icon and its says Att found unsupported soft wear. Can some please help me fix this issue I tried flashing the stock tar file in Odin but it won't pass.I need some serious help. Can some assist me!
That sounds more like download mode. There are a bunch of quick boot/recovery apps in the play store. Those would be easiest.
Sent from my TARDIS
0p3nsrc said:
That sounds more like download mode. There are a bunch of quick boot/recovery apps in the play store. Those would be easiest.
Sent from my TARDIS
Click to expand...
Click to collapse
But the thing is I can get into download mode but not my recovery
swaggsexy said:
But the thing is I can get into download mode but not my recovery
Click to expand...
Click to collapse
0p3nsrc actually answers this.
Two steps: #1. Download an app like Quickboot and then #2. start that app and use it to reboot either recovery or download mode (your choice). It should work.
I have had the same problem of the "unauthorized software" in the past and got around it by doing the manual process to get into recovery.
That is #1. turn off phone
#2. hold Volume up and keep holding it while pressing power button to start the phone
#3. Keep holding power+Volume UP button until you see the recovery indications (small print on top left part of screen).
#4. RElease the power button but DONT let go of the volume up button until you're actually in recovery. . .
you may have to try it a few times in a row to get it going, but it eventually WILL get you into recovery!
markbc01 said:
0p3nsrc actually answers this.
Two steps: #1. Download an app like Quickboot and then #2. start that app and use it to reboot either recovery or download mode (your choice). It should work.
I have had the same problem of the "unauthorized software" in the past and got around it by doing the manual process to get into recovery.
That is #1. turn off phone
#2. hold Volume up and keep holding it while pressing power button to start the phone
#3. Keep holding power+Volume UP button until you see the recovery indications (small print on top left part of screen).
#4. RElease the power button but DONT let go of the volume up button until you're actually in recovery. . .
you may have to try it a few times in a row to get it going, but it eventually WILL get you into recovery!
Click to expand...
Click to collapse
It won't work its saying. In Lil orange writting on top left kernel fail don't know what to do!
swaggsexy said:
I have a Att galaxy s4 i337 and I'm running black box ROM I don't know what happen but every time I try to go into recovery it brings up a yellow icon and its says Att found unsupported soft wear. Can some please help me fix this issue I tried flashing the stock tar file in Odin but it won't pass.I need some serious help. Can some assist me!
Click to expand...
Click to collapse
Hay "sexy" what base are you?
MDL or MF3
your profile lacks your phone and its base
Sent from my SAMSUNG-SGH-1337 using xda app-developers app
No matter which galaxy I had (s i9000, s2 i777, or my current s4), I've always has issues with the button combo for recovery. The safest/easiest had always been the quickboot app.
To the OP: black box ROM is ONLY meant for the international s4 (i9500). Major difference in hardware from the att s4 is the octocore processor. You are most likely getting kernel failure due to the ROM/kernel combo. Not 100% sure, though. Aside from kernel fail, any other parts to the error message? Post a screenshot of your "about device" under system settings > more..
For example, mine:
{
"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 TARDIS
that is what im getting is kernel fail on the top left hand corner
andriod system erased
if i accidentally erased my system on my phone how can i get tht back on a att galaxy s4
swaggsexy said:
if i accidentally erased my system on my phone how can i get tht back on a att galaxy s4
Click to expand...
Click to collapse
Explain.... How did you erase your system? Furthermore, are you talking about: your whole phone, the /system directory, or your internal sdcard? I've seen some people on the xda forums using 'system' a little too open-endedly.
If you mean /system, you're only option is flashing a ROM, unless you had a nandroid backup, in which case, depending on your recovery, you'd be able to do an advanced restore of the backup.
The same holds true if the whole phone has been wiped.
Sent from my TARDIS
swaggsexy said:
that is what im getting is kernel fail on the top left hand corner
Click to expand...
Click to collapse
swaggsexy said:
if i accidentally erased my system on my phone how can i get tht back on a att galaxy s4
Click to expand...
Click to collapse
swaggsexy said:
It won't work its saying. In Lil orange writting on top left kernel fail don't know what to do!
Click to expand...
Click to collapse
swaggsexy said:
But the thing is I can get into download mode but not my recovery
Click to expand...
Click to collapse
swaggsexy said:
I have a Att galaxy s4 i337 and I'm running black box ROM I don't know what happen but every time I try to go into recovery it brings up a yellow icon and its says Att found unsupported soft wear. Can some please help me fix this issue I tried flashing the stock tar file in Odin but it won't pass.I need some serious help. Can some assist me!
Click to expand...
Click to collapse
Since you can't get into recovery, based on what you've described, this means that you 1) flashed a recovery that was NOT loki'd 2) flashed a boot.img that was NOT loki'd.
This is most definitely something that can be fixed, depending on what Firmware your device is on.
If you know FOR A FACT that you have the MF3 bootloader, then I can walk you through how to use Heimdall to flash the phone back to an "out-of-the-box" state with MF3 firmware on it.
Is the Heiman method good to bring bacc to stock
jakew02 said:
Since you can't get into recovery, based on what you've described, this means that you 1) flashed a recovery that was NOT loki'd 2) flashed a boot.img that was NOT loki'd.
This is most definitely something that can be fixed, depending on what Firmware your device is on.
If you know FOR A FACT that you have the MF3 bootloader, then I can walk you through how to use Heimdall to flash the phone back to an "out-of-the-box" state with MF3 firmware on it.
Click to expand...
Click to collapse
If u can that would be appreciated. And the only thing I did was out a new room black box rom and root nothing going else done to the phone
swaggsexy said:
If u can that would be appreciated. And the only thing I did was out a new room black box rom and root nothing going else done to the phone
Click to expand...
Click to collapse
are you 100% positive that you were on MDL firmware? as in, you DID NOT take the OTA update for MF3? if you are on the wrong bootloader then this will brick your device.
honestly it's safer, you could just take it to BestBuy and tell them it "turned off during an update" or that you just want it reset
jakew02 said:
are you 100% positive that you were on MDL firmware? as in, you DID NOT take the OTA update for MF3? if you are on the wrong bootloader then this will brick your device.
honestly it's safer, you could just take it to BestBuy and tell them it "turned off during an update" or that you just want it reset
Click to expand...
Click to collapse
I fixed everything I just took of the Md5 off the tar file and put into Odin and it flashed just fine. Thanks for the input guys
swaggsexy said:
I fixed everything I just took of the MF3 or the tar file and put into Odin and it flashed just fine. Thanks for the input guys
Click to expand...
Click to collapse
awesome, sounds good.
as long as you have a bootloader from any firmware PRIOR to MF3, then you can just flash loki-doki as a precaution, otherwise you'll need to use SafeStrap, and I have not looked into that as I personally have no need to
I created a spot on my website for the stock Odin Tar's that I use for the P600.
I posted the US / XAR Region Stock Odin. I also posted the ML1 Asian base I used as well.
As I gather newer ones I will put them up and updated this thread.
Although this guide is written for the p600 it would, in theory work on any P60x device so long as you have the proper Odin files!
Note: This will not "untrip knox"!!!!!!!!
Here is the download page on my site:
MOD EDIT: Link removed as domain has expired. Thread closed until new links can be installed
Enjoy!
Currently Hosted:
P600UEUBMK1_P600XARBMK1_XAR (Shipped US ROM / XAR Region)
P600ZTUBML1_P600ZZTBML1_BRI (Asian Based ROM / BRI Region)
Other Odin Tar resources: Sammobile. Must be a member but they have tons of them.
How to Return to stock
This mini guide assumes the following...
You were able to root and or install a custom recovery or ROM therefore the drivers are installed on your PC for the tablet. So here we go...
Download Odin from the links in the OP
Extract the the .md5 file from the zip file you downloaded above.
Boot tablet into "Download" mode. You can do this by holding Power and Volume - (down) when the device is shut off. I note on this device it can be a little trickier so you may have to try a couple times. You should now see this on your tablet
{
"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"
}
Connect Tablet to PC using known good USB Cable
Start Odin and Press the "AP" button to load the tar.md5 file. This may take a minute as it is also calculating the MD5 to ensure you have a good file. A bad file means bad issues and it wont let you flash it (good fail safe).
Once Odin sees the Tar and loads it completely AND Odin sees the tablet press the Start button to begin. Can takes about 5 to 10 minutes so be patient. Do NOT check or uncheck mark ANY other Options in Odin unless you know what you are doing!
Once it complete you will have a factory image on your tablet. Yay!
But we are not done. You may also want to, at this point, reboot to recovery and do a full data wipe. This method of Odin leaves the SD card and user data intact. To get into recovery hold Power and Volume + until you see the stock Android recovery. Select format Data, reboot. Boom, your tablet is like brand new!
Guided added!
I am not the best technical writer so if you need help understanding what I am saying dont hesitate to ask!
Bumped so people can find this...
Mods moved it so no one looking will actually see it...
scrosler said:
Bumped so people can find this...
Mods moved it so no one looking will actually see it...
Click to expand...
Click to collapse
I'm glad you bumped it. I still haven't tried to install any custom ROM in this tablet, but this post will sure come in handy soon!
Vexelius said:
I'm glad you bumped it. I still haven't tried to install any custom ROM in this tablet, but this post will sure come in handy soon!
Click to expand...
Click to collapse
Indeed!
What happens if I failed to root (according to TWRP) and am stuck in the Samsung splash screen? I was obviously able to install TWRP so hopefully that is enough for Odin to get me back to stock
Will this work?
kaneelias said:
What happens if I failed to root (according to TWRP) and am stuck in the Samsung splash screen? I was obviously able to install TWRP so hopefully that is enough for Odin to get me back to stock
Will this work?
Click to expand...
Click to collapse
If you can see samsung screen you can odin back to stock.
The directions I posted should hold true about getting to Odin / Download Mode
Thanks for this guide, I agree, it should definitely be in the development section.
Hello
So will I get the OTA updates after this? How do I untrip knox?
thanks
Thanks for this Scott and a great ROM!!!!
Sent from my SAMSUNG-SGH-I317 using Tapatalk
tahrang said:
Hello
So will I get the OTA updates after this? How do I untrip knox?
thanks
Click to expand...
Click to collapse
Yes, this is returning you to stock like when you turned it on for the very first time.
No one knows how to untrip knox.
Is it Knox that blocks the ota updates, or is it the rooting itself?
starfall42 said:
Is it Knox that blocks the ota updates, or is it the rooting itself?
Click to expand...
Click to collapse
Not sure. Never tried to Ota with KNOX.
Maybe ask in the Q/A forums.
Just to be safe, and If I do this the tablet will be as if it was completely new, right? I'm going to exchange it for another one and I want to be sure it's as new. Are there any flash counters or stuff like that I should be worried about?
Sent from my Nexus 5
So when a system update comes out we could use these directions to flash the stock rom with out loosing data, apps, settings, etc? Then be able to get the stock OTA?
Coming from the Nexus world, This is a bit different. Google seems to have no interest in the 10 inch sector though, so here we are.
Never have we had a tablet so heavily defended with so many issues. 6 tablets and this one stands out.
Via my Note 3
Tripping out?
scrosler said:
Note: This will not "untrip knox"!!!!!!!!
Click to expand...
Click to collapse
I think I understand what you are saying, but I'm new to Android, and would appreciate a sanity check::cyclops:
1. Knox "trips" (i.e. opens a fusible link in the hardware) if you root the tab and (or?) boot with a non-factory ROM. Once it trips, it cannot ever be "untripped", even if you return to a factory ROM image. (Hence the emphatic statement in the quote.)
2. Question: If a tablet is currently, and has always been, unrooted and stock, will using Odin and these instructions with a factory ROM trip knox? For example, to upgrade to the factory KitKat image
3. Follow-up question: If I flash KitKat as above, can I return to the original release by following your guide, again without tripping knox?
Thanks for the guide and software, and for your help.
iTelegraph said:
I think I understand what you are saying, but I'm new to Android, and would appreciate a sanity check::cyclops:
1. Knox "trips" (i.e. opens a fusible link in the hardware) if you root the tab and (or?) boot with a non-factory ROM. Once it trips, it cannot ever be "untripped", even if you return to a factory ROM image. (Hence the emphatic statement in the quote.)
2. Question: If a tablet is currently, and has always been, unrooted and stock, will using Odin and these instructions with a factory ROM trip knox? For example, to upgrade to the factory KitKat image
3. Follow-up question: If I flash KitKat as above, can I return to the original release by following your guide, again without tripping knox?
Thanks for the guide and software, and for your help.
Click to expand...
Click to collapse
1. As far as anyone knows, Knox cannot be untripped.
2. If you Odin a FACTORY IMAGE it WILL NOT trip Knox. Only custom roms/rooting trips AFAIK.
3. I'm not 100% sure as I haven't tried, but I think I've seen discussions where the bootloader wasn't changed so you could go back. Again, I'm not 100% sure. Maybe we could get clarification from someone who tried.
Sent from my SM-P600 using Tapatalk
Okay, so I've had this issue for a few months now where no matter what I tried, I could not update my Baseband. I tried everything I could think of - flashed the full stock Rom, used mobile ODIN, flashed twice, etc. but no matter what, the baseband would stick to the old one. I tried googling and looking around but the same tricks as above were posted again and again to no avail.
I eventually found the answer, it was a single post buried in a thread on here. As I keep seeing posts from other users with the same issue, I figured I'd write a quick guide so that hopefully those searching for the problem will find it.
So to reiterate - you've just updated to a new firmware (custom or otherwise) but your radio (aka baseband) has not changed. You then try to flash the radio directly but it still won't change. What gives?
Well to fix it, you're going to need the following:
Odin 3.07
Triangle Away (Thanks to Chainfire, as always)
A Method of rooting your device (I'm leaving this up to you as it's a warranty voiding experience and I presume you know how to do that by this point).
An official Samsung firmware containing the radio you want to update to
If you're currently on an AOSP based ROM, then I have bad news - you'll need to flash back to touchwiz to do this. Once you're done, you can flash back though.
Remember to make a backup of all your data, as you will be doing a lot of flashing here.
Note: You may be able to fix your stuck radio problem without flashing back to a completely stock firmware and cutting corners elsewhere, however I wanted this guide to be bulletproof, deviating slightly may produce different results. If all else fails, follow each step below exactly!
Remember: This guide is specifically for those of you who have tried other methods and are still stuck on an old baseband. If you're just looking how to flash your radio, there are easier and less involved methods that don't require any wiping - I strongly advise you to try those first.
Okay, by this point I'm going to assume you've done all your backups and are ready to start flashing.
Step 1: Reboot your phone into DOWNLOAD mode (aka Odin). To do this, hold down POWER, VOL-DOWN and HOME at the same time until you see the following screens:
{
"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"
}
Remember to let go of the above buttons and press "volume up" to continue.
Step 2: Open up Odin 3.07, click on the "PDA" button and select the stock firmware file you have downloaded (file should have a ".tar.md5" extension, if you downloaded a .zip file you'll need to extract it but DO NOT EXTRACT MORE THAN THIS, you want a single .tar.md5 file).
Step 3: With your phone connected to your PC running ODIN, click "start". This will take a few mins, so be patient.
Step 4: Root. Now your phone should be rebooting into some pretty awful stock Samsung firmware. Boo. However this is a necessary evil. Here you need to root your phone. CF-Auto-Root is my preferred method but this trips Knox so do what you feel is best.
Step 5: Install and run Triangle Away. Triangle Away requires a Stock samsung kernel, which is why you've just flashed a full Samsung firmware. Triangle away requires root, which is why you've just performed Step 4.
Step 6: Install the Stock Firmware. Again.
That's right, repeat steps 2 and 3 once more to flash that stock Samsung firmware all over again. Except this time, your system is reporting that it's "official" and TriangleAway has cleared some flags that were preventing the updated radio from installing. When your phone reboots, your radio should have updated.
You're done! From here, you can do whatever you like - flash another custom ROM (you're still rooted at this point), wipe and restore a backup you made earlier, switch to AOSP or whatever. Personally, I would go buy Chainfire a beer as TriangleAway is what makes this all possible.
Nice....it helped me :good:
Thanks :highfive:
neoKushan said:
Okay, so I've had this issue for a few months now where no matter what I tried, I could not update my Baseband. I tried everything I could think of - flashed the full stock Rom, used mobile ODIN, flashed twice, etc. but no matter what, the baseband would stick to the old one. I tried googling and looking around but the same tricks as above were posted again and again to no avail.
I eventually found the answer, it was a single post buried in a thread on here. As I keep seeing posts from other users with the same issue, I figured I'd write a quick guide so that hopefully those searching for the problem will find it.
So to reiterate - you've just updated to a new firmware (custom or otherwise) but your radio (aka baseband) has not changed. You then try to flash the radio directly but it still won't change. What gives?
Well to fix it, you're going to need the following:
Odin 3.07
Triangle Away (Thanks to Chainfire, as always)
A Method of rooting your device (I'm leaving this up to you as it's a warranty voiding experience and I presume you know how to do that by this point).
An official Samsung firmware containing the radio you want to update to
If you're currently on an AOSP based ROM, then I have bad news - you'll need to flash back to touchwiz to do this. Once you're done, you can flash back though.
Remember to make a backup of all your data, as you will be doing a lot of flashing here.
Note: You may be able to fix your stuck radio problem without flashing back to a completely stock firmware and cutting corners elsewhere, however I wanted this guide to be bulletproof, deviating slightly may produce different results. If all else fails, follow each step below exactly!
Okay, by this point I'm going to assume you've done all your backups and are ready to start flashing.
Step 1: Reboot your phone into DOWNLOAD mode (aka Odin). To do this, hold down POWER, VOL-DOWN and HOME at the same time until you see the following screens:
Remember to let go of the above buttons and press "volume up" to continue.
Step 2: Open up Odin 3.07, click on the "PDA" button and select the stock firmware file you have downloaded (file should have a ".tar.md5" extension, if you downloaded a .zip file you'll need to extract it but DO NOT EXTRACT MORE THAN THIS, you want a single .tar.md5 file).
Step 3: With your phone connected to your PC running ODIN, click "start". This will take a few mins, so be patient.
Step 4: Root. Now your phone should be rebooting into some pretty awful stock Samsung firmware. Boo. However this is a necessary evil. Here you need to root your phone. CF-Auto-Root is my preferred method but this trips Knox so do what you feel is best.
Step 5: Install and run Triangle Away. Triangle Away requires a Stock samsung kernel, which is why you've just flashed a full Samsung firmware. Triangle away requires root, which is why you've just performed Step 4.
Step 6: Install the Stock Firmware. Again.
That's right, repeat steps 2 and 3 once more to flash that stock Samsung firmware all over again. Except this time, your system is reporting that it's "official" and TriangleAway has cleared some flags that were preventing the updated radio from installing. When your phone reboots, your radio should have updated.
You're done! From here, you can do whatever you like - flash another custom ROM (you're still rooted at this point), wipe and restore a backup you made earlier, switch to AOSP or whatever. Personally, I would go buy Chainfire a beer as TriangleAway is what makes this all possible.
Click to expand...
Click to collapse
No need this,too complicated。
Only turn off the phone, then remove the battery ,
install it
and get into download model ,
Flash the radio.
that you can update the baseband
nforce4 said:
No need this,too complicated。
Only turn off the phone, then remove the battery ,
install it
and get into download model ,
Flash the radio.
that you can update the baseband
Click to expand...
Click to collapse
Thanks, but unfortunately that didn't work for me.
neoKushan said:
Thanks, but unfortunately that didn't work for me.
Click to expand...
Click to collapse
Turn off your phone manually. Leave it for 10 sec, dont need to remove battery, Put the modem on Phone, NOT PDA connect your phone and flash it. It is simple.
IzArsha said:
Turn off your phone manually. Leave it for 10 sec, dont need to remove battery, Put the modem on Phone, NOT PDA connect your phone and flash it. It is simple.
Click to expand...
Click to collapse
Believe me when I say that I tried that, I tried just about everything before it would finally stick. Removing battery, leaving it off for 10s+ (I did this numerous times as TriangleAway demands it due to the risk if bricking your phone and one time left it off/unplugged for a good 20mins to no avail). There was some kind of write protection in place, Mobile ODIN (yeah tried that as well) mentioned it when trying to flash the Radio - hence why TriangleAway is needed.
Before it got "Stuck", I had manually updated my Modem a few times without issue. I've had the Note 3 since launch and voided Knox within about 2 days of getting it - believe me, I've been there and done that
Nothing worked for me also until I tried this method...
Sent from my SM-N9005 using XDA Premium 4 mobile app
Here's what I don't like, and what I "Do" Like...
Like....
1) A post in the proper forum that seems to help a few people fix their issue when other methods didn't seem to work.
Dislike...
1) Somebody coming in touting their own method (which may or may not work for a particular user). This, believe it or not, only adds to confusion when a person looks for an answer. Now there are different methods in the same thread topic.
2) 2 pages of back and forth arguing as a result of the above ^^^
So, I'll delete all posts concerning this debate on procedures.
Folks, don't go poaching other users threads please. If they provide a solution that helps a few users, then that is GREAT!!! Not all normal solutions work for all users. Stick around long and you will discover this on your own one day.
Cleaned thread, please don't make me come back and do it again.
MD
Thanks Moscow. I apologise for what happened, I didn't mean to cause a fuss.
To show there's no hard feelings, I've updated the OP with a warning that this is specifically for those who are still stuck after trying out other methods. Hopefully that's enough to keep everyone happy.
neoKushan said:
Thanks Moscow. I apologise for what happened, I didn't mean to cause a fuss.
To show there's no hard feelings, I've updated the OP with a warning that this is specifically for those who are still stuck after trying out other methods. Hopefully that's enough to keep everyone happy.
Click to expand...
Click to collapse
Much better. I didn't mean to start an argument... But it happened somehow.
Good detailed guide however. See you around XDA.
I'm having Baseband: Unknown issue, and flashing different modems are not changing it.
Can this method help ?
thanks
MuhammadZeeshan7 said:
I'm having Baseband: Unknown issue, and flashing different modems are not changing it.
Can this method help ?
thanks
Click to expand...
Click to collapse
Hmm, I really don't know man. I've not seen that error before so I can't comment. Perhaps this can help?
neoKushan said:
Hmm, I really don't know man. I've not seen that error before so I can't comment. Perhaps this can help?
Click to expand...
Click to collapse
I've done almost every method, but not yours. BTW I don't have any other triangle icon except the yellow triangle at the start of Download mode.
MuhammadZeeshan7 said:
I'm having Baseband: Unknown issue, and flashing different modems are not changing it.
Can this method help ?
thanks
Click to expand...
Click to collapse
Unpack the tar file, and flash just the modem.bin into phone (not pda) in Odin.
not working on SM-N900w8
Didn't work on my note 3 sm-n900w8, modem still previous version :crying:
any other suggestion please?
jsecruzvalencia said:
Didn't work on my note 3 sm-n900w8, modem still previous version :crying:
any other suggestion please?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=53632129&postcount=1
In the first box.