Develop Bugs

Need Help Unbricking

I bricked my Galaxy Ace GT-5830 and I need help un-bricking it with a stock ROM or one of these shiny Cyanogen ROMs. I've got all the tools I need from what I understand and hopefully someone can help guide this noob through the process and perhaps help me upgrade to a new OS. The phone will boot to and hang on the Samsung logo and to recovery mode but there seems to be some issue putting it into download mode so I'm stuck at the point of connecting it to Oden for download mode.
What I have:
Bricked phone
Oden 3.07 and 3.09
SD Card
Stock Firmware S5830XWKPY_S5830CPWKP1_CPW
My issues:
Firstly the stock ROM for a UK Carphone Warehouse phone I need that I found on SamMobile and another hosting site isn't in a tar.md5 format but I'm trying another stock ROM which is in the proper format for another UK provider to see if it will work, I'm not aware of how this would effect the phone if at all.
Secondly booting the phone to download mode doesn't seem to work as no connection is made with Oden. The phone boots to an empty charging battery which will disappear after a minute or so before the phone switches itself off again. Oden does recognise the phone when it boots and hangs on the Samsung boot logo and also when it boots into recovery mode. Multiple installs/versions of the USB drivers and Oden running in admin have been unsuccessfully attempted with various Samsung USB cables. Should I try to start Oden when a connection is made it hangs on setupconnection but I guess that is because it needs to be in download mode?
When attempting to wipe data/factory reset and cache partition it returns with the errors rfs format failed on /dev/stl13 and /dev/stl14.

brianx87 said:
I bricked my Galaxy Ace GT-5830 and I need help un-bricking it with a stock ROM or one of these shiny Cyanogen ROMs. I've got all the tools I need from what I understand and hopefully someone can help guide this noob through the process and perhaps help me upgrade to a new OS. The phone will boot to and hang on the Samsung logo and to recovery mode but there seems to be some issue putting it into download mode so I'm stuck at the point of connecting it to Oden for download mode.
What I have:
Bricked phone
Oden 3.07 and 3.09
SD Card
Stock Firmware S5830XWKPY_S5830CPWKP1_CPW
My issues:
Firstly the stock ROM for a UK Carphone Warehouse phone I need that I found on SamMobile and another hosting site isn't in a tar.md5 format but I'm trying another stock ROM which is in the proper format for another UK provider to see if it will work, I'm not aware of how this would effect the phone if at all.
Secondly booting the phone to download mode doesn't seem to work as no connection is made with Oden. The phone boots to an empty charging battery which will disappear after a minute or so before the phone switches itself off again. Oden does recognise the phone when it boots and hangs on the Samsung boot logo and also when it boots into recovery mode. Multiple installs/versions of the USB drivers and Oden running in admin have been unsuccessfully attempted with various Samsung USB cables. Should I try to start Oden when a connection is made it hangs on setupconnection but I guess that is because it needs to be in download mode?
When attempting to wipe data/factory reset and cache partition it returns with the errors rfs format failed on /dev/stl13 and /dev/stl14.
Click to expand...
Click to collapse
You forgot to tell us how you got it bricked in the first place. Was your device rooted and do you have stock recovery or CWM? Try taking out the battery and then put it back. Press and hold Vol Down+ Home+ Power button and see if you enter the Download Mode. Once you are in the Download Mode, there should be a yellow text saying "Downloading". Do post the result.

mahithm said:
You forgot to tell us how you got it bricked in the first place. Was your device rooted and do you have stock recovery or CWM? Try taking out the battery and then put it back. Press and hold Vol Down+ Home+ Power button and see if you enter the Download Mode. Once you are in the Download Mode, there should be a yellow text saying "Downloading". Do post the result.
Click to expand...
Click to collapse
I rooted the device and tried installing a custom ROM through recovery mode from what I remember and it's using a stock recovery. I've tried removing the battery and replacing while holding Vol Down+ Home+ Power button and it goes straight to the yellow text saying "Downloading" at which point the usb connection becomes unrecognised by my PC. Tried several different ports with various cables using the USB drivers from Samsung Kies and standalone drivers and I have yet to get it to recognise the device. What about "Emergency Download Mode," the device is recognised then but of course Oden hangs on the "setupconnection."

brianx87 said:
I rooted the device and tried installing a custom ROM through recovery mode from what I remember and it's using a stock recovery. I've tried removing the battery and replacing while holding Vol Down+ Home+ Power button and it goes straight to the yellow text saying "Downloading" at which point the usb connection becomes unrecognised by my PC. Tried several different ports with various cables using the USB drivers from Samsung Kies and standalone drivers and I have yet to get it to recognise the device. What about "Emergency Download Mode," the device is recognised then but of course Oden hangs on the "setupconnection."
Click to expand...
Click to collapse
It's just a soft-brick so nothing to very about The reason it was bricked was because you tried to install the custom rom from stock recovery mode. Always make sure to install custom rom from custom recovery mode like CWM. The reason your odin can't identify your device is because the odin is probably outdated and/ or maybe due to drivers. You can never use Emergency Download Mode to flash back stock rom from odin. When you use Emergency Download Mode, your connection will be recognized but you will end up getting set up connection error while flashing. Now to unbrick your device, just use the following thread,
[Share] All Samsung Galaxy Ace S5830 Stock Firmwares (2.3.X) Ever Released
First download the required firmware for your region from the first post. Once you have done that, go to the link in the second post. Download all the files (usb drivers, odin and ops) except firmwares (which you have already downloaded from the first post) in the "Preparation" section. Now install the USB drivers and follow the "Single Firmware File Installation". Once you have finished flashing, go to stock recovery mod and do a wipe data/ factory reset & wipe cache (otherwise bootloop might occur). Then restart. Now you have successfully flashed the stock rom. Here is the link for rooting and installing CWM 5 on Samsung Galaxy Ace which you can install from stock recovery mode (always root first and then install CWM),
How To Root and Unroot Samsung Galaxy Ace?
CWM 5.0.2.6 fix for Samsung Galaxy Ace S5830
Once you have installed CWM, you can flash any custom rom. CM 11 (KitKat) roms usually need CWM 6 but there is one CM 11 rom name KitKat for All that works well with CWM 5. Do post the result. Hope I Helped

My GT5830 Galaxy Ace is stuck in bootloop. I was flashing some file using recovery mode. Now the PC can not recognise the phone when it is in downloading mode although the PC recognise it in Emergency Download mode. I have tried all the USB drivers suggested in this forum.
Please help me.

[Q] I Killed My 12.2 (SM-T900). Please Help

I got the Tab Pro 12.2 a couple of weeks ago (refurb). It worked flawlessly, so I decided to root it, etc. It no longer works.
Two points.
(BOOT 1) - On a 'normal' boot it will get past the blue swirl with about 1 second of audio, then stops with "SAMSUNG" on the screen.
(BOOT 2) - On a Pwr on/Vol- (hard) boot, it will come up with "press vol +)" at which time it boots to ODIN. No way can I get it to boot to TWRP (see following)
Conditions: Windows 10 Tech Preview, Dell XPS 18 (USB 2 and 3), latest USB driver from Samsung, ODIN 3.10, Kies 3. The tablet connects with ODIN.
I loaded CF-Auto-Root (CF-Auto-Root-v2wifi-v2wifixx-smt900.tar.md5). Success, BUT tablet reboots to BOOT 1, above.
I loaded "openrecovery-twrp-2.8.5.0-v2wifixx.img.tar". Success, BUT reboots to BOOT1 above.
If I do a "hard" boot, I'm back with ODIN. TWRP won't boot. Tried the same with CWM (getting stupid here). Boots to ODIN. Basically, I can't boot into any recovery program.
Tried loading "SM-T900_XAR_1_20140508111550_703bt27ewy.tar". Again, loads but no joy.
Loaded the original ROM from SamMoblie. Again, no dice.
Am I screwed or what? Please help if you can. Thanks.
-- CatHerder12

Try a different ODIN version.
I've come up with something similar in the past.
ODIN reports OK but nothing is really written to the Tab.

guanellaluigi said:
Try a different ODIN version.
I've come up with something similar in the past.
ODIN reports OK but nothing is really written to the Tab.
Click to expand...
Click to collapse
Thanks for the reply. I have tried a few versions of ODIN. One or two of the older ones didn't work at all.. Currently using 3.10.6. Maybe I'll go back and retry a couple.
With tablet in download mode: I tried Kies and it reported the tablet as an unrecognized device. Tried ADB. It didn't see the tablet at all.
Any great insights (or guesses) would be appreciated!
Thanks

CatHerder12 said:
Tried ADB. It didn't see the tablet at all.
Any great insights (or guesses) would be appreciated!
Thanks
Click to expand...
Click to collapse
Plug in the Tab and check in your computer device manager list that the device shows connected to the USB port and the drive installed is Samsung Android ADB Interface, if it isn't change it to this driver.
Make sure you are using the original USB cable and its plugged directly into the PC and not via any Hubs.

CatHerder12 said:
Thanks for the reply. I have tried a few versions of ODIN. One or two of the older ones didn't work at all.. Currently using 3.10.6. Maybe I'll go back and retry a couple.
With tablet in download mode: I tried Kies and it reported the tablet as an unrecognized device. Tried ADB. It didn't see the tablet at all.
Any great insights (or guesses) would be appreciated!
Thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=50492301#post50492301
Try loading this in odin(P900XXUANB3-RecoveryImg.tar) then see if you can get into stock recovery and wipe cache and data to return to default settings. See if your stock rom loads.... If so then
flash CF-Auto-Root-v1awifi-v1awifixx-smp900.tar.md5 in odin then reboot
If all is working then flash
openrecovery-twrp-2.8.0.0-v2wifixx.img.tar
instead of the openrecovery-twrp-2.8.5.0-v2wifixx.img.tar( this seemed to not load on my tablet pro 12.2)
See if it boots up for you.
Then you can install custom rom if you want from twrp.

jvilla785 said:
http://forum.xda-developers.com/showthread.php?p=50492301#post50492301
Try loading this in odin(P900XXUANB3-RecoveryImg.tar) then see if you can get into stock recovery and wipe cache and data to return to default settings. See if your stock rom loads.... If so then
flash CF-Auto-Root-v1awifi-v1awifixx-smp900.tar.md5 in odin then reboot
If all is working then flash
openrecovery-twrp-2.8.0.0-v2wifixx.img.tar
instead of the openrecovery-twrp-2.8.5.0-v2wifixx.img.tar( this seemed to not load on my tablet pro 12.2)
See if it boots up for you.
Then you can install custom rom if you want from twrp.
Click to expand...
Click to collapse
Hi guys
, i had the same problem, but i follow ur steps and it worked. the only diference i installed the twrp-2.8.5.0-v1awifi.img.tar and it stuck, i have the SM-T900, v2wifi and it is working.
All the other didint stuck
thanks

jvilla785 said:
http://forum.xda-developers.com/showthread.php?p=50492301#post50492301
Try loading this in odin(P900XXUANB3-RecoveryImg.tar) then see if you can get into stock recovery and wipe cache and data to return to default settings. See if your stock rom loads.... If so then
flash CF-Auto-Root-v1awifi-v1awifixx-smp900.tar.md5 in odin then reboot
If all is working then flash
openrecovery-twrp-2.8.0.0-v2wifixx.img.tar
instead of the openrecovery-twrp-2.8.5.0-v2wifixx.img.tar( this seemed to not load on my tablet pro 12.2)
See if it boots up for you.
Then you can install custom rom if you want from twrp.
Click to expand...
Click to collapse
Thanks for the advice. I couldn't find a download link for the 2.8.0.0 but found openrecovery-twrp-v1a3gxx.img.tar. I'm guessing it's for a 3G version but it works. I used ODIN3 v3.10.6.exe on the PC. So far, I have twrp and the stock ROM running and everything works nicely. I still haven't managed to root it. Keeps getting stuck on cache. Can it be rooted after twrp has been loaded?
I actually may try to use the tablet for a while instead of continually poking and reloading it.

Did I brick my SM-T900 by rooting from Virtualbox?

Hello,
I just bought a Samsung Galaxy Tab Pro 12.2 (sm-t900). It's my first Android device.
I don't know what I was thinking, but I tried to root it from Windows 7 installed in Virtualbox.
My host OS is Linux.
Now the tablet is stuck at splash screen - it's looping from SM-T900 to Samsung.
I can still power it down to download mode though.
I used this tutorial - http://forum.xda-developers.com/gal...-how-to-root-install-custom-recovery-t3087451.
What I did was (in Virutalbox):
1. Installed Samsung drivers.
2. Downloaded CF-Auto-Root-v2wifi-v2wifixx-smt900.zip.
3. Run Odin.
4. Powered off the tablet into download mode and Attached it to Virtualbox.
5. Selected zip in Odin via PDA and clicked start.
6. It looked like everything went ok, but it was here where tablet tablet was reset.​And I think, it's also here, when things went bad, because tablet was detached from Virtualbox.
And my guess is that Odin couldn't finish flashing.
Or maybe it did, because flashing instructions that was displayed on tablet looked ok.
After 10 seconds it was reset.
And splash screen loop started.
Odin did show "PASS" though, but I don't know how was that possible, since the tablet was detached from Virtualbox.
I can still turn the downloading mode on.
Is there any help or is it trashed?
It serves me right I guess.

as long as you can access download mode it should be re-flashable, also first boot might take awhile (1-5 minutes) after flashing the firmware.
you can try samsung kies 3 if odin gave you problems.
no idea if virtualbox will cause problems, but I would flash from a real windows pc... to avoid problems like this

Hello,
Just to be sure - I only tried to root the tablet.
I have not flashed custom recovery or custom ROM.
And Android version on the tablet is 5.1.1, if I remember correctly from briefly skimming through system settings (before rooting).
To be honest, I am a little bit afraid to do anything now.
However, I have been testing some possibilities and here is what I was able to do:
1. I can go into download mode by pressing power+volume down+home.
2. I can go into recovery (stock, no twrp) by pressing power+volume up+home.
3. While in download mode, Odin says Added.
4. After pressing power for ~ 10 seconds, this information appears:​
SDCARD MODE
UP KEY: NORMAL BOOTING
DOWN KEY: DOWNLOAD MODE
But there is no effect after pressing up or down key.​
So I don't know if I should now:
Try rooting again (no virtualbox of course this time)?
Factory reset? Would it work after aforementioned rooting attempt?
Try flashing stock rom?
Unroot?​If anyone knows what is the best action to take now, I would much appreciate it.

I tried wipe data/factory reset (power+volume up+home) - no effect.
I also tried rooting again and this time on real Windows PC (rooting passed) - no effect.
So after sifting through the forums, my understanding is, that the rooting process at http://forum.xda-developers.com/gal...-how-to-root-install-custom-recovery-t3087451 is for Android 4.x.x.
And since the tablet I bought had 5.1.1, that is the reason it can not now boot.
I will try now recovering to stock ROM (Android 4.x.x).
I just don't know which country the tablet is from.
But after reading similar threads, it seems it is possible to install any official stock ROM.
Just which one to pick?

So I installed stock ROM with Android 4.4.2.
After that rooting worked as expected.
Then I installed TWRP recovery and CM 12.

Bricked Galaxy Tab3 7.0 SM-T210, can't enter download or recovery modes

I have a Galaxy Tab3 7.0 SM-T210 that we've owned for a long time, but I now want to use it for more things and find it a little clunky and slow compared to our more up to date smart phones. So i wanted to flash with a newer version of Android, but the tablet now appears to be bricked showing the "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again" screen and it won't do anything else. It won't enter download mode or recovery mode.
I came across these instructions to take me from a stock tab, and upgrade to Android 9.0 theupgradeguide.com/2019/09/17/install-android-9-0-pie-on-samsung-galaxy-tab-3-7-0-lineageos-16-how-to-guide
I loaded TWRP successfully using Odin and was able to set up a Nandroid backup. I then moved on to part 5 to perform a factory reset of the device, which was successful. This is where it started to go wrong though! I chose the reboot option after the wipe, rather than as per the instructions going back to the TWRP main menu. The tab rebooted and would't get past the Samsung logo. It went back in to download mode when I tried, and then tried to flash with a stock version of KitKat Android. Odin recognised the tab connected, it accepted the .tar flash file, and the tab showed the progress bar showing the download happening. Then Odin failed after a few minutes, and then the firmware upgrade failure error message appeared.
After lots of internet searching I've tried the following:
1. Putting it in download mode, doesn't work!
2. Putting it in recovery mode, doesn't work!
3. Connecting it to Kies, device not recognised and latest version of Kies doesn't have the option to manually select your device to reload the firmware!
4. Tried using ADB, device isn't recognised!
So i'm at a loss what to do to fix it, can anyone help?!

I was just trying to do the same yesterday. It all went fine with backing up and wiping, but TWRP didnt accept the image I downloaded.
It is so sad to have a capable hardware limited due lack of manufacturer care (not even saying updates, because they updated the android version at the time, but lack of optimization and how my tablet became sluggish, gave me disgust of any samsung branded device).
Can't you get to TWRP screen anymore?
If you can get to Odin download mode, trying reflashing Odin (perhaps a different version).

Erase some apk with adb and stuck on reboot

Hi! I hope some one knows how to restore apk on a Galaxy S9 plus
I was trying to get rid of Bixby and erase some apks using adb app control, I have a backup of the apks in the computer, the problem right now it's that the phone has many photos and most of them are important , I would like to know if there is a way to avoid wipe data/ factory reset, via adb or Odin.
I'm stuck on loop after the operator logo.
It doesn't boot in safe mode.
I already have android 10 ROM but I'm afraid that if I flash it with Odin , it will wipe the user data, if there is way to Just update, or restore this files please let me know.
Thank you very much for you help.

dr.rokr said:
Hi! I hope some one knows how to restore apk on a Galaxy S9 plus
I was trying to get rid of Bixby and erase some apks using adb app control, I have a backup of the apks in the computer, the problem right now it's that the phone has many photos and most of them are important , I would like to know if there is a way to avoid wipe data/ factory reset, via adb or Odin.
I'm stuck on loop after the operator logo.
It doesn't boot in safe mode.
I already have android 10 ROM but I'm afraid that if I flash it with Odin , it will wipe the user data, if there is way to Just update, or restore this files please let me know.
Thank you
Click to expand...
Click to collapse
put phone in recovery mode. flash official firmware using odin. use The BL,AP,CP files and for the CSC use the one marked HOME.

TormentedHeart said:
put phone in recovery mode. flash official firmware using odin. use The BL,AP,CP files and for the CSC use the one marked HOME.
Click to expand...
Click to collapse
Hi! I have tried several times, and I get failure to start, the phone is detected but the flash doesn't initiate, sometimes I get this screen, sometimes it says fail .
I have installed Samsung USB drivers, from the
Samsung Android USB Driver | Samsung Developers
You need the driver only if you are developing on Windows and want to connect a Samsung Android device to your development environment over USB.
developer.samsung.com
And Odin from here
Patched Odin 3.13.1
For those looking for a modified, modded, or patched odin that is a newer build than all the fake and renamed prince comsy 3.12.3 versions floating around. I patch recent Odin versions to offer similar functionality to the princecomsy; in that...
forum.xda-developers.com
I used the original Samsung USB cable and tried the 3 USB ports in the laptop
What else can be happening?
Thank you very much!

dr.rokr said:
Hi! I have tried several times, and I get failure to start, the phone is detected but the flash doesn't initiate, sometimes I get this screen, sometimes it says fail .
I have installed Samsung USB drivers, from the
Samsung Android USB Driver | Samsung Developers
You need the driver only if you are developing on Windows and want to connect a Samsung Android device to your development environment over USB.
developer.samsung.com
And Odin from here
Patched Odin 3.13.1
For those looking for a modified, modded, or patched odin that is a newer build than all the fake and renamed prince comsy 3.12.3 versions floating around. I patch recent Odin versions to offer similar functionality to the princecomsy; in that...
forum.xda-developers.com
I used the original Samsung USB cable and tryed the 3 USB ports in the laptop
What else can be happening?
Thank you very much!
Click to expand...
Click to collapse
did you try booting into the download mode twice?
Once and then again and then start the odin.
I had to do that.
I had to flash the official firmware myself because my phone keeps crashing on the homescreen.
Didnt solve it but I did flash it properly.

bruno2030 said:
did you try booting into the download mode twice?
Once and then again and then start the odin.
I had to do that.
I had to flash the official firmware myself because my phone keeps crashing on the homescreen.
Didnt solve it but I did flash it properly.
Click to expand...
Click to collapse
Hi! Yes I have tried but the phone seems unresponsive in download mode, I have tried with all the Odin versions , and 2 USB cablesi
I don't know what else can I do

dr.rokr said:
Hi! Yes I have tried but the phone seems unresponsive in download mode, I have tried with all the Odin versions , and 2 USB cablesi
I don't know what else can I do
Click to expand...
Click to collapse
go to the recovery.
connect to the PC.
open odin.
click on "reboot to bootloader"
It should go to to download mode.
what does your download mode screen say?
When I was doing this process I tried reflashing the latest rom but that didn't solve my boot loop issue.
So I flashed an older version of the rom.
Make sure the version you download is compatible with your phone.
You have G9650ZHU9FUG2 so only roms with 9 will work.
I flashed that old version and it didn't work, phone still stuck.
Then I flashed the latest one again and then my phone worked.
I used odin from the link you posted.
Odin3 v3.13.1

actually what i would suggest is downloading/re-downloading samsung usb drivers. otherwise most phones won't respond to odin even in download mode without it

dr.rokr said:
Hi! Yes I have tried but the phone seems unresponsive in download mode, I have tried with all the Odin versions , and 2 USB cablesi
I don't know what else can I do
Click to expand...
Click to collapse
TormentedHeart said:
actually what i would suggest is downloading/re-downloading samsung usb drivers. otherwise most phones won't respond to odin even in download mode without it
Click to expand...
Click to collapse
Hi! I have uninstalled everything and then install the drivers again without luck

TormentedHeart said:
put phone in recovery mode. flash official firmware using odin. use The BL,AP,CP files and for the CSC use the one marked HOME.
Click to expand...
Click to collapse
Hi! Today I have successfully flashed the exact firmware that the phone had ( there is no newer) using a different laptop (it's true if the problem persist with Odin, use another laptop)
I got success message, at the very first time, and when the phone reboot, nothing , stuck as it was before, so I erased cache partition and no luck, still stuck on reboot, I have also tried repair apps , and reboot sistem now, what else should I do?
Thank you very much!

Hi! I want the community to know that using the APK adb app for Samsung it's a bad idea, after successfuly flashing the firmware and performing a factory reset several times the phone remain stucked, I downloaded about 10 different firmwares and flash them all times without an error, and the phone was bricked and stuck in boot. So I took it to the official service and nothing, still the same, then I found an external service that flash the device with a little box that they said they paid in advance for credits for using that box, it took them one full week to revive the phone, also they had to flash it several times. In conclusion, if you buy Samsung, stick with the garbage apps the throw, if you mess with the system in some way as the official technician said, the phone will be nearly unrecoverable for privacy benefits for the user. Thank you very much for the help to the community!