Bricked I8190? - Galaxy S III Mini Q&A, Help & Troubleshooting

Hey,
I have my I8190 from about a year, and from then I always installed some custom roms. From a month I were in Cyanogenmod 10.2 from Maclaw, and this week strange things stared happening, specially with battery. It could drain from 100% to 5 in a 1-2 hours. And if it falled below 5% system started to reset and then it was in bootloop. But when I connected telephone to charger system normally started. I decided to install pure stock in Odin, but then I could't turn on my phone even for a second, because I had bootlop all time, I tried with 4-5 roms. Then I found :
http://forum.xda-developers.com/showthread.php?t=2157105
I followed this instructions and installed this branded rom, and everything worked. Till I installed another stock, then after 2-3 minutes system restarted and fall in bootloop again. And now I can't install any stock rom, because when I try to do this i get this error :
""<ID:0/005> system.img
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.""
And get this information on my phone :
"Frimware upragade encounted an issue. Please select recovery mode in Kies & try again"
I tried with 2 diffrent cables and with 2 diffrent computer. What could I do? Is my phone bricked?
Thanks for help and sorry for my english.

voximdo said:
Hey,
I have my I8190 from about a year, and from then I always installed some custom roms. From a month I were in Cyanogenmod 10.2 from Maclaw, and this week strange things stared happening, specially with battery. It could drain from 100% to 5 in a 1-2 hours. And if it falled below 5% system started to reset and then it was in bootloop. But when I connected telephone to charger system normally started. I decided to install pure stock in Odin, but then I could't turn on my phone even for a second, because I had bootlop all time, I tried with 4-5 roms. Then I found :
http://forum.xda-developers.com/showthread.php?t=2157105
I followed this instructions and installed this branded rom, and everything worked. Till I installed another stock, then after 2-3 minutes system restarted and fall in bootloop again. And now I can't install any stock rom, because when I try to do this i get this error :
""<ID:0/005> system.img
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.""
And get this information on my phone :
"Frimware upragade encounted an issue. Please select recovery mode in Kies & try again"
I tried with 2 diffrent cables and with 2 diffrent computer. What could I do? Is my phone bricked?
Thanks for help and sorry for my english.
Click to expand...
Click to collapse
i will tell you what i would do if i have this issues:
- download 3 Button combo
- download branded lafleur ROM
- download custom recovery (TWRP or CWM - search here on xda)
- flash 3 Button combo via Odin
- flash lafleur ROM via Odin
- flash custom recovery
- boot into recovery
- wipe cache and dalvik
- reboot
download a custom ROM you like such as carbon or omni or ... (as zip)
copy it to your device
- reboot into recovery
- flahs custom ROM with TWRP or CWM
- wipe again
- reboot.
J.

Related

[Q] Bricked Gnote, no experience on the field

so i have been running Paranoid android for a while, and wanted to try this out:
http://forum.xda-developers.com/showthread.php?t=2051904
flashed the latest cm10.1 kernel, and then formated cache, dalvic, battery stats, etc.
then i managed to reboot before i had flashed the new rom and got stuck in bootloop. could not access CWM any more
after this i downloaded odin after a few forum reads, and flashed different versions of CWM to see if i could get back in to flash the rom.
the latest one i have in it is this:
http://fs1.d-h.st/download/00033/pQK/GT-I9100_JB_ClockworkMod-Recovery_6.0.2.9.tar
as it was recommended in some un-brick thread. still no access to CWM
after this i flashed a stock rom, as i could not find any .md5 or .tar roms to use with odin, and i got at least a samsung logo on hte screen, before i got back to boot screen and was stuck there again.
CWM still not working, or showing up in any way.
out of obvious options i now tried flashing the pit file trough odin from this thread
http://forum.xda-developers.com/showthread.php?t=1424997
and after this the samsung boot logo did not show up anymore. only boot loop
i am now going to try and download the older ginger bread rom and flash it trough odin, but i got no idea if it will make any difference.
otherwise phone goes to download mode just fine, and i got working drivers in windows trough kies.
im quite new to this, and dont really know what would work from here. ill end up hard bricking the phone if i don't get some help, and the trash can will be my n7000 next home.
any advice is welcome
--------------------------------------------------------------------
EDIT:
flashing official rom again after the pit file acrually gave me a working phone again. also i now got 50 gb of drop box storrage for free, so thats nice

Help! Odin keeps failing!!

So I wanted to install a Android 4.4 on my aunt's Galaxy Note using Cyanogenmod 11. So now I've been trying all day and night to install a custom recovery. But I still didn't succeed because Odin keeps failing!
So basically I closely followed this guide in order to get CWM Recovery Advanced installed on this Note. But every time I try Odin fails again and again ( it says "<ID:0/007> Complete(Write) operation failed. <OSM> All threads completed. (succeed 0 / failed 1)" ).
I tried everything, restarting again and again (and again...) trying different USB ports, different USB cables different versions of Odin, different custom recovery files, restarting PC, restarting Odin, not restarting Odin... but unfortunately nothing worked yet..
As this is genuinely frustrating, I would really appreciate any help in this, so thanks in advance.
UPDATE: So I decided to maybe try a different approach. I download the Android 4.1.2 Samsung stock ROM (I forgot to mention before it was on Android 2.3.6) and installed it using Odin... surprisingly this time Odin DID work. However, when I retried installing the custom recovery Odin again failed. Indeed Odin hates me.
UPDATE 2: Finally I was able to install a custom recovery! The file PhilZ-cwm6-XXLT9-ORA-5.08.5.tar.md5 from here worked in Odin. So I then tried to installed the new version of CWM Recovery Advanced through the custom recovery that did install in Odin, but well it failed again.. I think something might be wrong with that custom recovery, I'll try a different one. Anyway I can say I bypassed the main obstacle, so no need for help now.
The Philz new recovery file you are trying to flash will never flash using odin no matter how much you try.
As you already have cwm recovery, flash raw r6 kernel from recovery, then reboot into the new recovery and flash kitkat roms.

Softbricked AT&T Galaxy S5

I purchased a soft bricked sm-g900a phone off of Ebay with the idea of using Odin to reflash and recover the phone. Since the phone was purchased soft bricked I do not have a history on what firmware was running on the phone or what the previous owner flashed that may have caused the phone not to boot to the OS or into recovery. I am assuming the previous owner was on 5.0 and tried to downgrade and ran into problems.
Short description of the current state of the phone:
1. Phone will boot into Odin Mode and can be flashed using Odin.
2. Phone will start to boot to recovery but sticks at "Recovery Booting. . . ." and reboots after about 30 seconds
3. Phone boots to Samsung logo and reboots after about 30 seconds.
What works:
Using Odin I can flash the following without errors: After flashing the phone exhibits the behavior above.
G900A_OC4_Stock_Kernel.tar.md5,
G900A_OA1_Stock_Kernel.tar.md5
G900A_OC4_Stock_Modem.tar.md5,
G900A_OC4_Stock_Partitions.tar.md5
G900AUCU3BOC4_OneClick..exe - reboots to recovery and "Recovery Booting. . . ."
I can flash SM-G900A_pit.pit with Odin 3.07 but not 3.09 or 3.10.
What does not work.
Tried flashing G900A_Downgrade_to_NCE.tar.md5 - Odin reports error
<ID:0/005> system.img.ext4
<ID:0/005> FAIL! (Auth)
Phone reports errors
SYS REV CHECK FAIL :Refer 2> Binary 1
SECURE CHECK FAIL : System
Tried flashing SM-G900A 4.4.2 G900AUCU1ANCE Firmware - AP_G900AUCU1ANCE_964333_REV00_user_low_ship_MULTI_CERT.tar.md5 in AP slot
Same errors as above .
Tried to use Kies to recover the phone. It goes through the process of recovering with 4.4.2 and crashes about the same place flashing wit Odin does.
I assume if I could get into recovery to do a factory wipe I would be able to get the phone to boot. I have read multiple forum posts and blogs on getting the bricked phone to work where most recommend flashing G900A_Downgrade_to_NCE.tar.md5 and then if you can't get into recovery to flash either G900A_OC4_Stock_Kernel.tar.md5 or G900A_OA1_Stock_Kernel.tar.md5 and then you should be able to get into recovery. This of course has not worked for me.
Does anyone have any idea how I might go about getting this phone to boot into recovery? Also is it possible to have the local AT&T store re flash 5.0 on the phone.
I know it is a risk buying soft bricked phones but I sure would not like to have an expensive paper weight.
Bogiemaker said:
I purchased a soft bricked sm-g900a phone off of Ebay with the idea of using Odin to reflash and recover the phone. Since the phone was purchased soft bricked I do not have a history on what firmware was running on the phone or what the previous owner flashed that may have caused the phone not to boot to the OS or into recovery. I am assuming the previous owner was on 5.0 and tried to downgrade and ran into problems.
Short description of the current state of the phone:
1. Phone will boot into Odin Mode and can be flashed using Odin.
2. Phone will start to boot to recovery but sticks at "Recovery Booting. . . ." and reboots after about 30 seconds
3. Phone boots to Samsung logo and reboots after about 30 seconds.
What works:
Using Odin I can flash the following without errors: After flashing the phone exhibits the behavior above.
G900A_OC4_Stock_Kernel.tar.md5,
G900A_OA1_Stock_Kernel.tar.md5
G900A_OC4_Stock_Modem.tar.md5,
G900A_OC4_Stock_Partitions.tar.md5
G900AUCU3BOC4_OneClick..exe - reboots to recovery and "Recovery Booting. . . ."
I can flash SM-G900A_pit.pit with Odin 3.07 but not 3.09 or 3.10.
What does not work.
Tried flashing G900A_Downgrade_to_NCE.tar.md5 - Odin reports error
<ID:0/005> system.img.ext4
<ID:0/005> FAIL! (Auth)
Phone reports errors
SYS REV CHECK FAIL :Refer 2> Binary 1
SECURE CHECK FAIL : System
Tried flashing SM-G900A 4.4.2 G900AUCU1ANCE Firmware - AP_G900AUCU1ANCE_964333_REV00_user_low_ship_MULTI_CERT.tar.md5 in AP slot
Same errors as above .
Tried to use Kies to recover the phone. It goes through the process of recovering with 4.4.2 and crashes about the same place flashing wit Odin does.
I assume if I could get into recovery to do a factory wipe I would be able to get the phone to boot. I have read multiple forum posts and blogs on getting the bricked phone to work where most recommend flashing G900A_Downgrade_to_NCE.tar.md5 and then if you can't get into recovery to flash either G900A_OC4_Stock_Kernel.tar.md5 or G900A_OA1_Stock_Kernel.tar.md5 and then you should be able to get into recovery. This of course has not worked for me.
Does anyone have any idea how I might go about getting this phone to boot into recovery? Also is it possible to have the local AT&T store re flash 5.0 on the phone.
I know it is a risk buying soft bricked phones but I sure would not like to have an expensive paper weight.
Click to expand...
Click to collapse
Its hard to tell what version it was on previously since recovery wont even boot, but from how its acting i'd say it was on LP and bricked for a KK flash, so you flashing NCE(Kitkat) is doing zilch. Seeing as there is no option for you to root, and im assuming you arent interested in that anyway, i would just take it to bestbuy or the att store and get them to reflash it, just say you got it off ebay and it was like that.
Sent from my Tw5ted SM-G900A using Tapatalk
I took the phone to BestBuy and the guy there flashed it with 5.0.1 with the same results. Boots to the Recovery Booting. . . . screen for about 30 seconds and then reboots. My daughter is taking it to an AT&T repair center to see if they have any better luck.
Have you tried flashing the boot image?
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
Boot image. Not sure which file you are talking about.
Could you give me a little more information or a link to the file?
Re: Softbricked AT&amp;amp;amp;amp;amp;T Galaxy S5
If you have the oc4 update zip, in the zip should be a boot image, create an md5 tar file from it then flash in AP. If that doesn't work, you flashed a bad kernel and may have to use jtag to fully recover. Or bring it to a repair facility to have them do it.
My daughter took the phone to an AT&T repair center and they also could not successfully flash the phone. The only OC4 update i have found is the G900AUCU3BOC4_OneClick..exe update and I do not believe I can extract the boot image from that update. Is there another source of the OC4 update available where I could obtain the boot image.
Thanks for the help everyone.
I'll look for the DL link. But if they tried flashing it, and it didn't work. You may be SOL.
Bogiemaker said:
I purchased a soft bricked sm-g900a phone off of Ebay with the idea of using Odin to reflash and recover the phone. Since the phone was purchased soft bricked I do not have a history on what firmware was running on the phone or what the previous owner flashed that may have caused the phone not to boot to the OS or into recovery. I am assuming the previous owner was on 5.0 and tried to downgrade and ran into problems.
Short description of the current state of the phone:
1. Phone will boot into Odin Mode and can be flashed using Odin.
2. Phone will start to boot to recovery but sticks at "Recovery Booting. . . ." and reboots after about 30 seconds
3. Phone boots to Samsung logo and reboots after about 30 seconds.
What works:
Using Odin I can flash the following without errors: After flashing the phone exhibits the behavior above.
G900A_OC4_Stock_Kernel.tar.md5,
G900A_OA1_Stock_Kernel.tar.md5
G900A_OC4_Stock_Modem.tar.md5,
G900A_OC4_Stock_Partitions.tar.md5
G900AUCU3BOC4_OneClick..exe - reboots to recovery and "Recovery Booting. . . ."
I can flash SM-G900A_pit.pit with Odin 3.07 but not 3.09 or 3.10.
What does not work.
Tried flashing G900A_Downgrade_to_NCE.tar.md5 - Odin reports error
<ID:0/005> system.img.ext4
<ID:0/005> FAIL! (Auth)
Phone reports errors
SYS REV CHECK FAIL :Refer 2> Binary 1
SECURE CHECK FAIL : System
Tried flashing SM-G900A 4.4.2 G900AUCU1ANCE Firmware - AP_G900AUCU1ANCE_964333_REV00_user_low_ship_MULTI_CERT.tar.md5 in AP slot
Same errors as above .
Tried to use Kies to recover the phone. It goes through the process of recovering with 4.4.2 and crashes about the same place flashing wit Odin does.
I assume if I could get into recovery to do a factory wipe I would be able to get the phone to boot. I have read multiple forum posts and blogs on getting the bricked phone to work where most recommend flashing G900A_Downgrade_to_NCE.tar.md5 and then if you can't get into recovery to flash either G900A_OC4_Stock_Kernel.tar.md5 or G900A_OA1_Stock_Kernel.tar.md5 and then you should be able to get into recovery. This of course has not worked for me.
Does anyone have any idea how I might go about getting this phone to boot into recovery? Also is it possible to have the local AT&T store re flash 5.0 on the phone.
I know it is a risk buying soft bricked phones but I sure would not like to have an expensive paper weight.
Click to expand...
Click to collapse
Hello! OP...are you still around?
Did you ever recover this phone?
I was in the same situation...maybe worse...and I was finally able to recover it.
Please let me know what happened with yours?
THANKS!
jebep said:
Hello! OP...are you still around?
Did you ever recover this phone?
I was in the same situation...maybe worse...and I was finally able to recover it.
Please let me know what happened with yours?
THANKS!
Click to expand...
Click to collapse
How did you recover yours?

Bricked or not?

Hi everybody
Im new here and to flahing new Roms and stuff.
i believe my phone is bricked and im struggling to get it opperational. Here is what happened...
I have a GT-N7000 on 4. 1. 2 Jelly Bean, which i rooted and flashed to custom ROM CynoganenMod 12 on 5. 0 Lollipop. All was going fine, i rooted my phone, installation went accordingly. After a week or so whithout any problems, my phone started to freez, slag and hang which it never did before, so i decided to flash it back on 4. 1. 2 Jelly Bean I did all as is step by step on Odin 3.-v1.8. When my booted, it booted into System Recovery...
reboot system now (I did)
apply update from ADB
apply update from external storage (I did)
wipe data/factory reset
wipe cache partion
apply update from cache
-----------------------------------------------
# MANUAL MODE #
-- Applying Multi-CSC. . .
E : All failed to mount and open in red ( Invalid argument )
Nothing seems to work, so when i pull out the battery but it back and press "Volume down, Menu and Power button it takes me to the screen with the Warning and yellow triangle where i can install a custom ROM...
Volume up : Continue
Volume down : Cancel ( restart ) (I did)
When i Volume up it takes me to...
ODIN MODE
CUSTOM BINARY DOWNLOAD : NO
CURRANT BINARY : SAMSUNG OFFICIAL
My problem is i have no clue what my PDA nor my CSC code is. Im from South Africa and not sure either which of these are correct.... XFV, XFC, XFM, XFA (im not network locked) so i dont know which firmware to flash with Odin to make my phone opperational again? Any help please guys.
Johan
Download Philz kernel in tar.md5 format and flash using Odin... Then try to boot into recovery. You should see cwm. Factory reset and flash a stock rom again.
nokiamodeln91 said:
Download Philz kernel in tar.md5 format and flash using Odin... Then try to boot into recovery. You should see cwm. Factory reset and flash a stock rom again.
Click to expand...
Click to collapse
I have tried Phillz and did as you suggested. Im confident that i dont have the correct firmware. I downloaded this from Sammobile : N7000XXLSZ_N7000OJVLSB_N7000LSO_HOME.tar.md5.
Not sure how to go about this....
Doesn't matter what firmware you had.. Once you do a factory reset you can flash any rom made for the n7000
Were you able to get into Philz cwm recovery after you flashed the kernel?
Hi there.
I am happy to report that my phone is back to its original state. Phew, that wat too close for comfort.
I figured that it was obivously bricked or something close to it.
The problem was that i repartitioned it with the wrong PIT file and wrong kernel. Why i did that, i dont know? So i found firmware i thought would be the correct one! In its bricked state i copied the file superuser to my external, so can unzipit in CWM recovery. I download a file flashprogram Samsung N7000 +Pit. I then unzipped it and found the .Pit file which i flashed onOdin3 v1.85 at the same time with the firmware, have it repartitioned, and install the firmware.
It passed with success. Go Green!!! )
It booted to Philz recovery and installed the zip file superuser, took your advice then rebooted.
My phone switched on but a page came up where i had to give a password decrypting the device storage. Freaked out repeated the same prosesswith Odin and it started up normaly and suprised to see it restored to its original state* *smile*
*Just be carefull not to go flash the wrong stuff on your phone if your not sure what you are doing ( like i did! )*
I took your advice to heart and want to thank you for your expertieze. I learned alot from my phone the past 3days.
Regards.Johan

Cannot instal STOCK ROM after instlling CM12/13

Hi!
I have installed TWRP and CM13 on my S5 mini (G800F), but i got many bugs and restarts, so i decided to go back to Stock ROM, unfortunatelly i cannot do this.
When i open Odin and try to install STOCK Rom from samsungmobile everything is good, till the and, when i got:
Write finished (filed)
<OSM> All threads completed. (succeed 0 / failed 1)
I tried on laptop and deskop using various USB port but everytime i get the same message.
And when i get the battery out and power on i get:
"firmware upgrade enountered an issue. Please select recoery mode in Kies and try again"
I tried to connet it with Kies in recovery odin mode but Kies does not recogenize it.
Then i need my phone so i decided to move back to CM this time i have installed the CM12, after using it, one day and having many restarst i tried one more to move to STOCK ROM. I downloaded the older verios of STOCK ROM then i had before. But i got the same messege.
Then someone tell mi to make full wipe, so using TWRP i done the full wipe, cache, data, system and internal storage/sd.
After wipeing internal storage i get only:
"firmware upgrade enountered an issue. Please select recoery mode in Kies and try again"
and cannot even install recovery via Odin any more, beacouse i get bugs ;/ ;/ ;/
as a result i cannot even use my phone with CM12/13.
1. Do You have any tips or solution of this problem?
2. How can I instal STOCK ROM or even CM?
3. Can I install the CM via Odin?
4. Do You have any other recovery for S5 mini G800F?
He there, sorry to hear you're having troubles with the phone. I experienced a similar problem and found that this worked:
Try and flash your stock firmware, when it fails, take out battery, put it back in and restart into recovery mode (stock recovery). From there, do a factory reset and wipe (not using Team Win Recovery Project, using the stock Recovery).
Now go back to odin and try flashing again.
Hope this helps...it worked for me.
Do this when error occurs after flashing stock firmware!
1. Flash stock firmware
2. Get error message
3. Remove battery and start in Recovery Mode
4. Flash hidden.img that you can extract of the stock file!
Quote from reddit.com:
If you've tried to flash firmware off of Sammobile, and had your heart stop when the flash fails, fear no longer.
To fix the soft brick:
Open the firmware file in winrar and extract the hidden.img. Rename it as hidden.img.tar.
Load the new file into the PDA tab, and flash.
When the phone boots, the displayed image will be touchwiz teal, there will be a little android and GALAXY spelt above it. Don't freak out.
Give it a minute and it should boot.
Hi, jest i did happend after flashing a stock firmware, but fortunatelly now it work.
How do i manage to fix it? I do not know. I just tried to flash it with a stock firmware one more time, and than tried to flash TWRP recovery via Odin. It get a fail. But the phone got power on, and it works till now !!!!
What was the problem? I have read that if you have the other CSC than XEO and want to flash the ROM with XEO CSC on S5 mini this problem occurs on many phone. Espesially on that from UK, so mine was.
thanks!!
Kuba

Categories

Resources